What problem does it solve? Products accumulate behavior that is defined implicitly across state machines, handlers, and tests, with no single place describing what the user sees and what happens when they act. This Skill builds a product-description repo: prose documents written from the outside in, drafted from code and tests, then verified against the running product, with suspected defects triaged into one bug list. ## Core Features & Use Cases - Uniform document skeleton: Every feature document follows the same eight-section template (summary, simple case, event-by-event interaction, modifiers, cancel/interrupt table, cross-cutting concerns, edge cases, open questions) so gaps and inconsistencies surface by comparison. - Phased build workflow: Scope decisions, scaffolding (README, glossary, goal.md), a pilot plus foundations, parallel drafting with subagents, a consistency pass with a link checker, hand-verification checklists, and bug triage. - Product-kind mapping: Reference guidance adapts the template to pointer-driven editors, form-and-page web apps, CLIs, and chat/agent products by fixing the unit of interaction, variant axis, interrupt list, and cross-cutting concerns. - Use Case: Point the Skill at a web app's source repo to produce a full set of feature documents, verification checklists with stable IDs, and a deduplicated bug-triage file with severity and decisions needed. ## Quick Start Ask the assistant to build a product description repo for your application by pointing it at the source repository and the surface you want documented.
