What problem does it solve? Turning a rough feature idea into a consistent, plannable specification is slow and error-prone: branch names drift, specs lack acceptance criteria, and downstream planning re-litigates decisions. This Skill converts a short description into a saved, templated spec document with draft BDD scenarios, a classified work type, and a dedicated git branch. ## Core Features & Use Cases - Spec Generation: Derives a Title Case feature title, a git-safe slug, and a branch name from a short idea, then writes a markdown spec following the project's template. - Example Mapping Scenarios: Converts each acceptance criterion into draft Given/When/Then scenarios using Specification by Example and Ubiquitous Language, flagging uncertainties as open questions. - Work-Type Classification: Labels the work as new-capability, change-to, or fix-infra, and creates a draft feature doc skeleton only when a genuinely new capability is introduced. - Use Case: After running a discovery session, pass the increment slug to continue from its discovery.md, or simply describe a new dashboard card component and receive a branch, spec file, and draft feature doc ready for planning. ## Quick Start Ask the assistant to create a spec for a short feature idea, for example: run the spec skill with the argument "card component for dashboard stats".
