author-product-docslisted

Create, revise, retrofit, audit, or verify product documentation — pack READMEs, journeys, tutorials, how-to guides, reference pages, and explanations. Use when asked to write, improve, restructure, audit, or verify user-facing documentation, fix a pack README, create a guide for a feature, update a journey page, or check whether docs match shipped behavior. Infers the mode from the request. Do NOT use for feature specifications (use new-spec), cross-cutting proposals (use new-rfc), decisions (use new-adr), product or market strategy, frontend implementation alone, internal maintainer runbooks without user-facing concern, or arbitrary prose editing with no documentation purpose.
eugenelim/agent-ready-repo · ★ 17 · Code & Development · score 77

Install: claude install-skill eugenelim/agent-ready-repo

# Product documentation authoring **Diátaxis determines what a page does for the reader. Canonical behavior determines what it says.** A reader who does not know any pack or skill names must still be able to begin a real task from the first screen. Create or work with product documentation — pack READMEs, journeys, and Diátaxis guides — grounded in what the product actually ships today. ## Output rendering Rationale / narrative — Use short ## headings and 2–3 sentence paragraphs. Don't force narrative into a table. Key–value / one record — For a single record's fields, use an aligned key: value list, not a two-row table. Status list — Lead each row with a status glyph (● running, ✓ done, ○ idle, ⚠ blocked). ## Procedure ### Step 1 — Resolve the mode Infer the mode from the request. Do not require the user to name it. | Mode | Signals | |---|---| | **Create** | "write a guide", "new tutorial", "create a README", "document this feature" | | **Revise** | "improve", "update", "rewrite", "restructure", "fix", "simplify" | | **Retrofit** | "connect these pages", "fix the journey", "reorganize the docs", "make it coherent" | | **Audit** | "audit", "review", "what's missing", "what's wrong", "check quality" | | **Verify** | "does this match what ships", "check accuracy", "verify against behavior" | When a request is ambiguous between create and revise, read the target file first. If it exists and is substantive, treat as revise. If absent or near-empty, treat as create. ##