| name | sdd |
| description | Spec-Driven Development (SDD) flow. Use this skill for feature development based on technical specifications. Guides the process through REQUIREMENTS, SPECIFICATIONS, PLAN, and IMPLEMENTATION phases. |
Spec-Driven Development Flow
You are in SDD (Spec-Driven Development) mode. Read flows/sdd.md for the complete flow reference.
Commands & Actions
start [name] - Start new SDD flow
- Create directory
flows/sdd-[name]/.
- Copy templates from
flows/.templates/sdd/.
- Create
_status.md with phase = REQUIREMENTS.
- Begin requirements elicitation with user.
resume [name] - Resume existing flow
- Read
flows/sdd-[name]/_status.md to determine current phase.
- Read all existing artifacts in the spec dir.
- Report current state to user.
- Continue from where left off.
fork [existing] [new] - Fork for context recovery
- Copy
flows/sdd-[existing]/ to flows/sdd-[new]/.
- Update
_status.md to note the fork origin.
- Ask user what adjustments to make.
- Continue from current phase with modifications.
status - Show all active SDD flows
- List all
flows/sdd-*/ directories.
- Read each
_status.md and summarize phase + blockers.
Phase Behaviors
REQUIREMENTS Phase
- Elicit what user wants to build and why.
- Ask clarifying questions.
- Document user stories with acceptance criteria.
- Identify constraints and non-goals.
- Update
01-requirements.md iteratively.
- Wait for explicit "requirements approved" before advancing.
SPECIFICATIONS Phase
- Analyze codebase for affected systems.
- Design interfaces and data models.
- Document edge cases.
- Update
02-specifications.md iteratively.
- Wait for explicit "specs approved" before advancing.
PLAN Phase
- Break specs into atomic tasks.
- Identify file changes and dependencies.
- Estimate complexity.
- Update
03-plan.md iteratively.
- Wait for explicit "plan approved" before advancing.
IMPLEMENTATION Phase
- Execute plan task by task.
- Follow project testing protocol (one test at a time).
- Log progress in
04-implementation-log.md.
- Document any deviations from plan.
Mandates
- Update
_status.md after every significant change.
- Never skip phases or assume approval.
- When uncertain, ask rather than assume.
- Before ending session, ensure handoff notes are complete.
