1---2name: new-content3description: New content piece4---56# New content piece78## Procedure9101. **Load context**: `strategy/` (positioning, messaging, ICP, personas)11 and `brand/voice.md`. If they're unfilled templates, stop and suggest12 `/setup`. If a file says `source: context-layer`, read the document over13 MCP instead (see `integrations/context-layer.md`); if `last_reviewed` is14 older than 90 days, say so before drafting.152. **Pin down the piece**: working title, channel, owner, and the project it16 belongs to (check `projects/`; if none fits, ask whether this is17 standalone or needs a `new-project` first).183. **Create the folder**: `content/YYYY-MM-<slug>/` copied from19 `content/_template/`. Fill the brief properly (the argument section is20 the work: derive it from the messaging pillars, don't leave placeholders),21 and wire the draft frontmatter (`project`, `status: brief`, `channel`,22 `owner`).234. **Cross-link**: add the piece to the owning project's brief under24 Deliverables (name + path; status stays in the piece's frontmatter).255. **Stop at the brief** unless asked to draft. The brief is the reviewable26 unit; offer to draft once the human has glanced at it.2728## Rules2930- If SEO-driven, check `data/seo/keywords.csv` for the target keyword; if31 it's not tracked, note that in the brief rather than silently adding it.32- Drafting later: follow the brief's argument, write in `brand/voice.md`33 voice, and run `review` before proposing `status: in-review`.