What problem does it solve? Starting to code from vague or ambiguous requirements leads to rework, hidden assumptions, and features nobody asked for. This Skill forces a written, human-approved specification before any implementation, turning unclear ideas into testable success criteria. ## Core Features & Use Cases - Gated Four-Phase Workflow: Moves through Specify, Plan, Tasks, and Implement phases, each requiring human review before advancing. - Capability Decomposition: Detects when one request bundles several independently testable capabilities and proposes a capability map with module ids, dependencies, and build order before any spec is written. - Assumption Surfacing and Reframing: Lists assumptions explicitly and translates vague requirements (e.g. "make it faster") into concrete, measurable success criteria. - Use Case: When asked to build a new billing feature with unclear requirements, use this Skill to draft a spec covering objective, commands, structure, style, testing, and boundaries, get it approved, then break it into dependency-ordered tasks. ## Quick Start Ask the agent to write a specification for the new feature before writing any code, including success criteria and boundaries for review.
