Editorial calendar · 12-week cycle
12 pieces, structured assignment, structured exit. Repeat quarterly.
## How to use
1. Edit **Writers** with your team — capacity per week, beats covered, current status.
2. Drop pitches into **Pieces** with the angle. Assignment agent matches to a writer.
3. Writer drafts in **Drafts**. Editor agent passes voice + style + flags issues.
4. Human editor reviews + approves. Mark Final → Published.
5. Week 12: quarter retro drafted from Performance data.
## Pieces
Columns: title · pitch · writer · editor · status · publish date · beat. Stages: Pitched → Approved → Drafting → Review → Final → Published.
## Writers
Columns: writer · capacity (pieces/quarter) · beats · pieces this quarter · status (active / out / paused). Your assignment agent reads this when matching.
## Drafts
One doc section per piece. Latest in-flight at top. Style-guide checks land as comments.
## Style guide
Voice · Tone · Conventions · Banned phrases. Edit once at the top of each cycle; every writer + editor agent references this in real time.
### Voice
Who we sound like. Examples of on-brand sentences.
### Tone
What modulates: formality, humor, hedging.
### Conventions
- Em dashes? (No, we use commas + periods.)
- Sentence case in headings? (Yes.)
- Oxford comma? (Yes.)
### Banned phrases
Things our voice doesn't say.
## Performance
Columns: piece · publish date · views · time-on-page · shares · top-2-referrers. Populated weekly by your operator agent from analytics. Drives the quarter retro.
## Quarter retro
### Q[N] YYYY retro
- **Shipped:** N / 12 pieces (link Pieces)
- **Top performers:** 3 specific pieces, why
- **Underperformers:** 3 specific pieces, why
- **Writer capacity reality:** who shipped to plan, who didn't
- **Style guide updates proposed:** specific phrases / patterns
- **Next quarter's lean:** the one big beat to invest in
## When you're done (week 12)
Read the retro. Adjust Writers + Style guide. Fork the workspace for Q[N+1] — Style guide + Writers carry forward, Pieces + Drafts + Performance reset.
Fork to next cycle
When you're done, fork the workspace for the next cycle. The new workspace will be seeded with your structure, your customizations, and this cycle's retro as your agent's first Status entry — so it picks up context-aware from where this one left off. Same template, next cycle, no manual setup.