clarifying-requirementsAnalyzes user prompts for gaps, ambiguities, and unstated assumptions, then asks clarifying questions before work begins. Use when requests are vague, lack acceptance criteria, or have hidden complexity.
writing-adrsGuides writing concise, effective Architecture Decision Records. Use when creating ADRs, extracting decisions from specs, or reviewing ADR quality.
writing-developer-guidesStructures developer guides for optimal AI agent and human consumption. Use when creating or updating a project's developer guides, or when documentation needs to support autonomous coding agents.
writing-for-humansWrites user-facing prose a non-developer can read: release notes, changelog entries, READMEs, package descriptions, docs guides and concept pages, blog posts, UI microcopy, and error messages. Use when writing or reviewing any copy a person (not a coding agent) will read.