What problem does it solve? Starting to code without clear requirements leads to rework, misaligned expectations, and architectural decisions made on the fly. This Skill enforces writing a reviewed specification before any implementation begins, surfacing assumptions and ambiguities early. ## Core Features & Use Cases - Gated Four-Phase Workflow: Progresses through Specify, Plan, Tasks, and Implement phases, each requiring human review before advancing. - Six-Area Spec Template: Covers objective, commands, project structure, code style, testing strategy, and boundaries (Always/Ask First/Never rules). - Assumption Surfacing: Forces explicit listing of assumptions and reframes vague requirements into testable success criteria. - Use Case: When asked to build a new feature with only a vague description, use this Skill to interview the stakeholder, produce a spec document with acceptance criteria, break it into dependency-ordered tasks, and only then begin implementation. ## Quick Start Ask the agent to write a specification for your new feature before writing any code, covering objectives, tech stack, testing strategy, and success criteria.
