What problem does it solve? Starting to code with vague or ambiguous requirements leads to rework, misaligned expectations, and undocumented architectural decisions. This Skill enforces writing a reviewed specification before any code, so requirements, boundaries, and success criteria are explicit and shared. ## Core Features & Use Cases - Gated Four-Phase Workflow: Moves through Specify, Plan, Tasks, and Implement phases, each requiring human review before advancing. - Capability Mapping: Decomposes requests bundling several independently testable capabilities into a module map with dependency direction and build order. - Spec Template & Location Policy: Produces specs covering objective, commands, structure, code style, testing, and boundaries, saved to docs/spec/<feature>/SPEC.md. - Use Case: When asked to build a new billing feature with unclear requirements, use this Skill to explore the repository, surface assumptions, draft a spec with testable success criteria, get it approved, then break it into ordered tasks before implementing. ## Quick Start Ask the agent to write a specification for the new feature before writing any code, following the spec-driven development workflow.
