Skip to content

Start Here

Copilot (and the AI dev toolchain around it) is changing fast across VS Code, GitHub.com, IDEs, and the CLI. This repo turns that flood into a monthly newsletter draft, plus a trail in workspace/ showing how it got there.

Two links up front: - Runnable repo: briancl2/CustomerNewsletter - Published February issue: Discussion #18

Also in this folder: - Case study - Timeline

Full technical report (long, technical): - Feb 2026 system report

VS Code Copilot Chat

  1. Open the repo in VS Code.
  2. Open Copilot Chat and select the customer_newsletter agent.
  3. Paste this prompt:
i want you to generate a from-scratch brand new february newsletter using the dates Dec 5 2025 to Feb 13 2026

If you want a cleaner, more repeatable run, follow up with:

Run it as a clean cycle (no reuse) for START=2025-12-05 and END=2026-02-13.

At the end, run the repo's validators and fix what they flag.

If something's consistently off, fix the rule/skill so it stays fixed.

Copilot CLI

Headless mode:

copilot --agent customer_newsletter \
  --model claude-opus-4.6 \
  --allow-all \
  --no-ask-user \
  -p "i want you to generate a from-scratch brand new february newsletter using the dates Dec 5 2025 to Feb 13 2026"

Interactive mode:

copilot --agent customer_newsletter --model claude-opus-4.6 -i

Then paste the same prompt from the VS Code section.

What You Should See

  • Final draft written to output/2026-02_february_newsletter.md
  • A paper trail in workspace/ showing what was collected and curated along the way

Two Prompts That Did Most of the Work

Kickoff prompt (verbatim excerpt):

Fleet deployed: i want to plan for a large project that will take multiple steps,
multiple agents, and a number of subdivided tasks. I want this plan to generate a
large discovery to start and then generate a detailed multi-stage migration plan for
the Newsletter portion of this repo.

the work is to 1) extract the Newsletter portion of this repo (e.g., a) newsletter
archive, b) newsletter generation mechanisms such as prompts, agents, skills, and
reference material, and c) any other related components that will be useful in the new
standalone Newsletter repo) and 2) setup the Newsletter system in a new standalone repo
with after migrating the parts from number one over.

Full kickoff prompt: - Timeline (kickoff prompt)

Why the one-line run prompt works: - It names the output (a newsletter) and pins a date window. - "from-scratch" forces a full run, not a patch. - If you only change one thing, change the dates.