feature

What problem does it solve? Teams lose track of what a capability actually does once specs, plans, and code drift apart. This Skill produces a single living behavioral document per capability, written in business language, so QA can run regression testing and developers can onboard without reading source code. ## Core Features & Use Cases - BDD scenario generation: Writes Given/When/Then scenarios grouped under business Rules, with concrete values and no implementation jargon. - Test coverage mapping: Builds a coverage table linking each scenario to its test file and status, distinguishing covered, failing, uncovered, code-derived, and ruled-out rows. - From-code backfill: Reverse-engineers draft docs for undocumented capabilities by reading schema definitions, typed models, and views, flagging anything code cannot prove. - Use Case: After shipping a navigation component across three increments, run the Skill to consolidate scattered specs and tests into one feature doc that QA uses as the regression baseline. ## Quick Start Ask the assistant to generate a feature doc for a capability by passing a spec path, capability name, or code entity, for example: create a feature doc for the site navigation capability.