New Content

---
name: new-content
description: Scaffold a piece of content in content/: folder, brief and draft skeleton with wired frontmatter. Use when asked to start, draft or create a blog post, email, LinkedIn post, case study or any piece.
license: MIT
metadata:
  kind: workflow
  area: core
  needs: []
  writes: repo
  runs: person
---

# New content piece

## Procedure

1. **Load context**: `strategy/` (positioning, messaging, ICP, personas)
   and `brand/voice.md`. If they're unfilled templates, stop and suggest
   `/setup`. If a file says `source: context-layer`, read the document over
   MCP instead (see `integrations/context-layer.md`); if `last_reviewed` is
   older than 90 days, say so before drafting.
2. **Pin down the piece**: working title, channel, owner, and the project it
   belongs to (check `projects/`; if none fits, ask whether this is
   standalone or needs a `new-project` first).
3. **Create the folder**: `content/YYYY-MM-<slug>/` copied from
   `content/_template/`. Fill the brief properly (the argument section is
   the work: derive it from the messaging pillars, don't leave placeholders),
   and wire the draft frontmatter (`project`, `status: brief`, `channel`,
   `owner`).
4. **Cross-link**: add the piece to the owning project's brief under
   Deliverables (name + path; status stays in the piece's frontmatter).
5. **Stop at the brief** unless asked to draft. The brief is the reviewable
   unit; offer to draft once the human has glanced at it.

## Rules

- If SEO-driven, check `data/seo/keywords.csv` for the target keyword; if
  it's not tracked, note that in the brief rather than silently adding it.
- Drafting later: follow the brief's argument, write in `brand/voice.md`
  voice, and run `review` before proposing `status: in-review`.