Editorial cadence.

The reason you don't ship 50 pieces a year isn't talent. It's calendar.

You have the briefs you could run. You have the voice file from Module 013. You have the four-stage loop from Module 012. What you don't have is a plan for when each piece leaves your hands, who reviews it, and when the next one starts. So pieces clump into Q4, spread thin in Q2, and two-thirds of your intended output never ships.

Cadence is the silent killer of agent-assisted publishing. Everyone focuses on writing faster. The real unlock is writing predictably.

This module is 90 minutes of building the calendar, the cadence agent, and the review rhythm that turns "I want to write more" into "here's what ships this quarter." By the end, you'll have:

• A 90-day editorial calendar you can actually hit.
• A cadence agent that runs a weekly planning session with you.
• A review loop that catches calendar drift before it costs you a quarter.
• A scalable rhythm: solo, pair, or small team.

This module assumes you've done Modules 012 and 013. If you haven't, the four-stage loop and the voice file are the fuel. Cadence is the engine. Both are needed.

Thinker takes it from here, why cadence beats bursts.

Most writers think output is a function of inspiration. It isn't. Output is a function of cadence, which is a function of capacity, which you can model in a spreadsheet.

Three models compete:

1. Inspiration. You write when moved. Output: 6 pieces/year, spaced erratically.
2. Push. You force a weekly publishing schedule. Output: 48 pieces/year, quality crashes by month 3.
3. Cadence. You run a calendar with slack and review gates. Output: 40-50 pieces/year, quality holds.

The third model is what publications use. It's boring. It works. The key is treating the calendar as the primary artifact, and the pieces as outputs of the calendar.

Capacity math

Solo: one 90-minute loop per piece, one 60-minute planning block per week. That's 7.5 hours/week for 2 pieces/week = 100 pieces/year ceiling. Realistic target: 40-50 pieces with slack for life.

Team of three: shared calendar, shared briefs, individual loops. 6-8 pieces/week is sustainable. 300+ pieces/year ceiling. Realistic target: 150-200.

Why the calendar matters more than the piece

A piece you wrote is a single event. A calendar you kept is a compounding asset. The calendar tells you which topics repeat, which angles are unexplored, which weeks were thin. Six months of calendar data is worth more than six months of pieces, because the calendar tells you what to do next.

Talker has the planning prompt that runs on the calendar.

Two prompts. The 90-day calendar prompt (run once per quarter). The weekly planning prompt (run every Monday).

The 90-day calendar prompt

You are a planning agent. Produce a 90-day editorial calendar
as a markdown table.

Context:
- Voice file: [paste contents]
- Target audience: [one sentence]
- Business goals this quarter: [list up to 3]
- Recurring themes from last quarter: [list]
- Available capacity per week: [number of pieces]

Calendar rules:
- One row per publish slot.
- Columns: Week, Publish date, Working title, Angle,
  Target length, Status (idea/briefed/drafted/shipped).
- Distribute themes evenly. No more than 2 pieces on the
  same topic in any 3-week window.
- Leave 20% of slots blank for reactive pieces.
- Mark 2 slots as "review weeks" with no new pieces.

Return only the markdown table. Then below it, list any
assumptions you made.

Save the output as ~/.bot/calendar/Q[N].md. This is the spine of your quarter.

The weekly planning prompt

You are a cadence agent. I'm sending you:
1. The current 90-day calendar.
2. This week's status update.

Produce three things:
- A ranked list of which pieces to move on this week.
- Any calendar adjustments if a piece is stuck or late.
- One flag: what's the biggest risk to the next 30 days
  of the calendar?

Keep it under 250 words total. Be specific.

Run this every Monday. 10 minutes. You leave the week knowing exactly what to work on and where the calendar is wobbling.

Rememberer has where all this lives.

The calendar is the most important file in your writing stack. It lives in one place, with a predictable structure.

~/.bot/
  calendar/
    Q1-2026.md
    Q2-2026.md
    Q3-2026.md
    weekly-notes/
      2026-04-07.md
      2026-04-14.md
  drafts/            (from Module 012)
  voice.md           (from Module 013)

The calendar files are markdown tables. Weekly notes are 5-line summaries of what shipped, what slipped, and what got added. After a year you have 52 weekly notes, which is a surprisingly rich history.

Status field discipline

Each calendar row has a status: idea, briefed, drafted, shipped. Update the status the same day the change happens. If you wait until Monday, you won't remember.

A common failure: everything stays in "idea" until the week before deadline. The cadence agent can't plan against that. Status is the signal.

What not to put in the calendar

Keep it dated, titled, angled, and status-marked. Don't put the full brief in the calendar, that lives in drafts/. Don't put the draft in the calendar. The calendar is a map, not a warehouse.

Doer builds a real 90-day calendar in 12 minutes.

Twelve minutes to produce a 90-day calendar you can actually hit.

Voice: [paste voice.md, or 3-line summary]
Audience: [one sentence]
Goals this quarter:
  1. [goal]
  2. [goal]
Recurring themes (from last quarter):
  - [theme]
  - [theme]
Capacity: [2 pieces/week, 1 review week per month]

cd ~/.bot/
git add calendar/
git commit -m "calendar Q[N]: initial draft"

What just happened

You have a calendar, not a wish list. Every Monday you know what to work on. Every piece has a slot, not a deadline. The calendar is a living document, not a heroic push.

Rookie has the ways cadence breaks.

Three failure modes that turn a calendar into an expensive to-do list that no one follows.

Failure 1. Over-booking capacity

You set 3 pieces/week on the first quarter. It feels ambitious. By week 5, you're 3 pieces behind. By week 8, you've abandoned the calendar.

The fix: book 60% of your theoretical capacity. Life costs 40%. You can ship an extra piece when the week opens up; you can't conjure the time when it doesn't.

Failure 2. No review weeks

You schedule 12 weeks of new pieces, no pauses. Month 2, quality drops because you haven't looked back. Your voice.md is stale. Your angles repeat.

The fix: one review week per month. No new pieces. Read the three most recent pieces. Update voice.md. Refresh the calendar for the next 30 days. This is what compounding looks like.

Failure 3. Calendar abandonment

You miss the Monday ritual three weeks in a row. The calendar is now fiction. You start working from memory. Cadence collapses.

The fix: protect the Monday ritual like a paid meeting. It's 10 minutes. It's the highest-leverage 10 minutes in your week. If you can't do Monday, do Tuesday. If you can't do this week, do next Monday twice.

All three failures share a shape: treating cadence as a stretch goal instead of a floor. The calendar is not aspirational. It's the minimum. Plan for what you'll actually do.

Manager has how this scales across a team.

A team of three running the cadence model produces roughly 3x the output of a solo writer, at similar quality, if (and only if) they share one calendar.

One calendar, three authors

The team shares a single Q[N].md file. Each row has an author column. The cadence agent plans across authors, not within. That prevents two authors writing the same piece and surfaces coverage gaps.

Authors self-assign rows during the Monday planning session. The editor (or team lead) spot-checks for theme coverage. If three rows in a week are all "product updates," something's missing.

The Monday cadence meeting

15 minutes, synchronous, every Monday. Each author states:

• What shipped last week.
• What's in flight this week.
• What's blocking them.

The editor updates the calendar in real time. The cadence agent runs during the meeting, producing the ranked priority list for the week. No second meeting needed.

Quarterly planning

Once a quarter, the team does a 90-minute planning session. They read the previous quarter's calendar, update voice.md, and generate next quarter's calendar together. This is the single most important editorial meeting on the calendar. Protect it.

Editor as calendar keeper

The editor's job shifts from "approve drafts" to "maintain the calendar." Quality gates are in the shared voice.md and the critique prompt, not in the editor's inbox. The editor spot-checks 10% and tunes the system. Higher leverage work.

Chief on why this matters to the business.

Three things about cadence that matter at the executive level.

Risk 1. Cadence is a leading indicator

If your content team's cadence slips, something is wrong upstream, usually editorial capacity, strategic clarity, or tooling. Cadence is the canary. A healthy cadence means the whole writing system is functioning. A slipping cadence means you have 60 days before it becomes visible to customers as silence or inconsistency.

Watch the cadence chart, not the individual pieces. It tells you more about the health of the team.

Risk 2. Burst publishing is a brand tax

Three pieces in April, zero in May, five in June: readers read it as "these people can't decide if they're publishing or not." It erodes trust in the brand faster than mediocre content would.

Consistent cadence, even at lower volume, signals reliability. Reliability is expensive to build and cheap to lose.

Risk 3. Cadence as hiring signal

When leadership sees "we need more content," the reflex is to hire. Often, the real constraint is cadence, not capacity. A team of two with cadence will out-ship a team of five without.

Before hiring: run the cadence diagnostic for 90 days. Track what shipped, what slipped, and why. If 80% of the slips are "capacity," hire. If 80% are "calendar wasn't clear," fix the calendar first. Hiring into a broken cadence produces more chaos, not more output.

The chief's questions

• What is our target cadence, and how did we pick it?
• What's our current cadence vs. target, over the last 90 days?

If leadership can't answer both in 30 seconds, cadence is not being managed. Start there.

Founder wraps.

You, alone, with a backlog of ideas and no plan. The solo cadence loop is the thing that separates founders who ship from founders who draft.

The weekly ritual

Every Monday. 10 minutes. Non-negotiable.

• Open the 90-day calendar.
• Run the weekly planning prompt.
• Update statuses for last week.
• Pick this week's 1-2 pieces.
• Commit the changes.

The quarterly reset

Every 90 days. 90 minutes. Block it.

• Read the past quarter's 12 weekly notes.
• Note which themes worked, which didn't.
• Update voice.md if new patterns emerged.
• Generate the next 90-day calendar.
• Commit.

This is the founder's content strategy meeting with themselves. It's cheap. It compounds. After 4 quarters, you have 48 weekly notes and 4 calendars to learn from.

The three files

• ~/.bot/calendar/Q[current].md
• ~/.bot/calendar/weekly-notes/[this week].md
• ~/.bot/voice.md (from Module 013)