ccc-agent-writinglisted

# CCC Agent Writing ## Overview Good writing is testable. If an agent (or a beginner developer) can't follow your doc, it's broken. This skill teaches agents to write specs, PRDs, PR descriptions, and documentation that are clear, persuasive, and structured to be acted on. For long-form content and brand-voice alignment, delegate to the `content-strategist` persona. ## Core Principle **Write for a reader, not for yourself.** Every piece of writing has one reader and one outcome. Name them both before writing a word. ## The Writing Process ### Step 1: Define Reader + Outcome Before writing anything: - Who is the reader? (junior dev, senior reviewer, product stakeholder, future-you) - What should they DO after reading? (approve, implement, understand, install) - What's the format? (spec, PRD, PR description, README section, runbook) ### Step 2: Choose a Structure | Writing Type | Structure | |---|---| | Spec / PRD | Problem → Context → Requirements → Acceptance Criteria → Out-of-scope | | PR Description | Summary → Changes → Test plan → Screenshots (if UI) | | README section | What → Why → How (in that order) | | Runbook | Trigger → Steps → Expected result → Rollback | | Technical doc | Concept → Example → Edge cases → See also | ### Step 3: Lead with the Answer Bury the lede = broken writing. The first sentence answers: "What is this and why do I care?" - ❌ "This PR refactors the authentication module to improve code quality and make future changes easier." - ✅ "F