What problem does it solve? Product behavior is usually defined implicitly across state machines, handlers, and tests, with no single plain-language source describing what users see and can do. This Skill produces a complete behavior-spec repository that documents the product as a state chart, feature by feature, from the user's point of view. ## Core Features & Use Cases - Structured documentation pipeline: A six-phase workflow (scope, scaffold, pilot, parallel drafting, consistency pass, verification) that produces README, glossary, goal, feature documents, verification checklists, and a bug-triage file on one shared skeleton. - Product-kind adaptation: Reference guidance maps the template onto canvas editors, form-based web apps, CLIs, and chat products by fixing the unit of interaction, variant axis, interrupt list, and cross-cutting concerns. - Verification and defect triage: Generates hand-verification checklists with stable IDs and priorities, plus a deduplicated bug-triage file with severity, root cause, and decisions needed; includes a link and anchor checker script. - Use Case: Point the Skill at a web app's source repo and request a product-description repository; it drafts per-feature documents from code and tests, then verifies claims against the running product and collects suspected defects into bug-triage.md. ## Quick Start Create a product-description repository for the app in ./src, documenting each feature's behavior from the code and tests and verifying it against the running product.
