writing

Creates and refines reader persona YAML files used by the review pipeline. Use when creating a new reader persona for a project brief, or refining an existing persona based on accumulated review feedback. Do NOT use for running the review itself — use `review` instead; do NOT use to assemble the brief — use `obsidian:brief` instead.

Quality review pipeline for writing chapters — persona-based qualitative analysis (comment) and technical correction (doctor). Use when evaluating a written chapter through reader personas, applying grammar/typography/terminology corrections, or preparing triage decisions (rewrite vs patch). Do NOT use for code review — use `aidd-dev:review` instead; do NOT use for rewriting chapters — use `write --feedback` instead.

Writes a project or product specification — a "cahier des charges": the requirements document a client or product owner hands a provider. Captures objectives, scope (in and out), functional and non-functional requirements, deliverables, constraints, acceptance criteria and planning, then challenges each requirement for testability, atomicity and completeness. Use to formalize a need into a contractable spec. Do NOT use for end-user manuals (use user-guide), developer/architecture docs (use technical-document), or a repository README.

Identifies key visual moments in a chapter and generates detailed illustration briefs (for an artist or an image AI). Use when planning illustrations for a chapter, generating image prompts from narrative content, or building a visual brief from a scene. Do NOT use for writing or correcting chapter text — use write or review instead; do NOT use for defining the writing style — use tone-finder instead.

Writes technical documentation for builders — architecture overviews, API/reference docs, integration and how-it-works guides, runbooks, and design notes/RFCs. Picks the right structure per document type and verifies examples, links and claims against the codebase. Use for developer- and operator-facing docs. Do NOT use for end-user manuals (use user-guide); for a project's requirements (use specification); or for a repository README (use overcode:readme).