What problem does it solve? Ambiguous or incomplete requirements cause rework, scope creep, and misaligned implementations. This Skill enforces a gated Specify → Plan → Tasks → Implement workflow so significant changes start from a validated, evidence-backed specification instead of assumptions. ## Core Features & Use Cases - Gated Four-Phase Workflow: Progresses through Specify, Plan, Tasks, and Implement phases, each requiring human review before advancing. - Evidence-Based Specification: Requires citing exact path:line references for repository claims, separating observations from inferences and decisions, and recording prior-art searches. - Structured Spec Template: Covers six core areas — Objective, Commands, Project Structure, Code Style, Testing Strategy, and three-tier Boundaries (Always / Ask First / Never). - Use Case: When starting a multi-module feature that would take more than 30 minutes, use this Skill to surface assumptions, reframe vague requirements into testable success criteria, and produce a version-controlled spec before writing code. ## Quick Start Ask the agent to write a specification for your new feature using the spec-driven development workflow before any implementation begins.
