ai-prose

# Prose ## Quick start ``` /ai-prose content blog /ai-prose content sprint-review --audience manager /ai-prose content architecture-board ``` ## Workflow 1. Detect content type from prompt (blog / pitch / sprint-review / architecture-board / solution-intent / presentation). 2. Read existing source material — notes, transcripts, data, real output. 3. Pick audience (developer / manager / executive); apply tone + jargon table. 4. Edit, do not generate. Every sentence earns its place. 5. Apply shared rules: active voice, present tense, no filler ("basically", "simply", "just"). Router skill for content writing. Dispatches to handler files based on content type. Always: clear structure, audience-appropriate, no fluff. ## When to Use - Creating pitch decks, sprint reviews, blog posts, architecture board presentations, solution intent documents. - NOT for documentation artifacts (README, CHANGELOG, API docs) -- use `/ai-docs`. - NOT for marketing content (social posts, investor materials, outreach) -- use `/ai-marketing`. - NOT for code explanations -- use `/ai-explain`. ## Writing Philosophy Edit, don't generate. Start from what exists: notes, transcripts, data, examples, real output. Every sentence must earn its place. Template language is a failure mode, not a starting point. ## Routing Single sub-command `content` (default) — handler `handlers/content.md` covers articles, pitches, presentations, sprint reviews, architecture board, solution intent. The handler dispatch...