---
name: content-calendar
description: Build a four-week calendar from what the ICP actually asks, kept as a live artifact you update rather than regenerate. Use once voice and ICP exist.
---

Build four weeks of content the user will actually publish.

**Read first:** `01-voice/skills/icp-profile/SKILL.md` and `01-voice/skills/brand-voice/SKILL.md`. If the profile isn't there, stop and run `/icp-profile` — a calendar built without one is a list of topics, and topics are what people abandon in week two. If the voice skill isn't there, stop and run `/brand-voice` — every row here becomes a draft, and drafts written without it come back sounding like a model wrote them.

1. **Start from questions, not keywords.** What does this specific person ask before they buy, during, and after. One question per entry. If you can't picture someone typing it, cut it.
2. **Set a cadence they'd still hit in month four.** Two a week beats five a week for eleven days. Over four weeks that is eight slots, two of them left empty, six entries. Under-promise the schedule on purpose; the impressive one is the one that gets abandoned.
3. **Four weeks, dated.** Six entries across the eight slots. Each one names the question, the format, the channel, and the one thing it should make someone do. Ask which channels they already post to. Do not add a channel with no writing sample behind it — a row pointing at an account nobody has ever written on is a chore with a date on it.
4. **Mark what needs proof.** Any entry resting on a number, a customer name or a screenshot gets flagged now, while there's still time to go and get it.
5. **Leave two of the eight slots empty.** Something worth writing about will happen, and a full calendar is the reason nobody writes it.

**Then make it live.** A calendar generated once and never touched is dead the day it's made. Hand the file to the user and have them make three edits themselves — add one entry, move one, delete one. Do not make those edits on their behalf and do not invent a reason for one; a simulated edit is just more generated text, and the point is that at least one line in there is theirs. Write the rule into the top of the file — this artifact gets edited every week, never regenerated. Regenerating throws away everything the user learned since the last version, which is the only part that was ever worth having.

Write to `02-routines/calendar.md`.