# /newsletter [action] [issue-number]

Newsletter pipeline orchestration. Invokes the `newsletter-orchestrator` agent which coordinates 9 phases.

## Actions

| Command | What it does |
|---|---|
| `/newsletter strategy [N]` | Pick topic + write brief for issue N |
| `/newsletter draft [N]` | Drafter writes issue body from brief |
| `/newsletter architect [N]` | Validate / produce the god-tier prompt (3-codebase test harness) |
| `/newsletter build [N]` | Render markdown to HTML (build.py) |
| `/newsletter audit [N]` | Quality gate — 25 mechanical + 13 semantic + regression checks |
| `/newsletter render-test [N]` | Visual gate — 20 structural + Playwright at 4 viewports |
| `/newsletter preview [N]` | Send preview email to inbox |
| `/newsletter send [N]` | Create broadcast (manual paste or API) |
| `/newsletter analyse [N]` | Day-of-send + day-7 reports |
| `/newsletter all [N]` | Run phases 1-7 sequentially, halt at preview for user review |
| `/newsletter next` | Show what issue type is next in the rotation |

## Procedure

For any sub-action: invoke `newsletter-orchestrator` agent via Task tool. Pass:
- Action
- Issue number (optional — defaults to next issue)
- Brand (optional — defaults to active brand from memory.md)

## Phase order (/newsletter all)

1. Strategy — strategist picks topic + writes brief
2. Draft — drafter writes issue body
3. Architect — prompt-architect produces / validates god-tier prompt
4. Build — `build.py` renders HTML
5. Audit — newsletter-auditor runs all checks
6. Render-test — stylist runs structural checks + Playwright
7. Preview — `send.js --preview` to inbox
8. **HALT** — user reviews preview email, says "ship" or provides corrections
9. Send — manual paste or API broadcast
10. Analyse — analyst day-of-send (4-6h after send) + day-7 reports

Each phase runs in fresh context. Halts at phase 7 for human review.

## Requires

Newsletter starter pack at `newsletter/`. See `newsletter/README.md` for setup.