sdd

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

1. Create directory flows/sdd-[name]/.
2. Copy templates from flows/.templates/sdd/.
3. Create _status.md with phase = REQUIREMENTS.
4. Begin requirements elicitation with user.

resume [name] - Resume existing flow

1. Read flows/sdd-[name]/_status.md to determine current phase.
2. Read all existing artifacts in the spec dir.
3. Report current state to user.
4. Continue from where left off.

fork [existing] [new] - Fork for context recovery

1. Copy flows/sdd-[existing]/ to flows/sdd-[new]/.
2. Update _status.md to note the fork origin.
3. Ask user what adjustments to make.
4. Continue from current phase with modifications.

status - Show all active SDD flows

1. List all flows/sdd-*/ directories.
2. 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.