“spec-driven development”

Spec-driven development pipeline — use when starting any non-trivial coding task to specify before coding, then design, implement, review, and test.

SDD — Spec-Driven Development: run the full pipeline automatically.

SDD — Spec-Driven Development: write a lean implementation plan.

SDD — Spec-Driven Development: scaffold a new Architectural Decision Record.

Use when the user requests delegated implementation or multiple substantial tasks are genuinely independent without shared state.

SDD — Spec-Driven Development: generate a lean phased task list.

Use when /virtual-team:implement --sdd is active — defines orchestration protocol for fresh subagent per task with two-stage review

SDD — Spec-Driven Development: scaffold .sdd/ and adopt living specs for an existing repo, one area at a time.

Use before changing behavior or fixing a bug when a focused test can prove the change.

Kiro for Claude Code

heisebaiyun

Spec-driven development with Claude Code - inspired by Kiro

Staff Strategic Orchestrator for Spec-Driven Development (SDD).

Use when executing a written implementation plan (TSP) whose tasks are independent, in the current session.

Use when implementing or reviewing framework-specific code that should be verified against current official docs, versioned guidance, or source-cited examples…

Use when implementing a high-risk behavior change, reproduced regression, or costly contract.

Use when executing implementation plans with independent tasks by delegating each task to a fresh herdr sibling pane

Execute complex, long-running development work through a living ExecPlan organized into phases and bounded tasks.

Compatibility entrypoint for delegated execution of approved tasks.

Subject every non-trivial decision to fresh-context adversarial review before it stands.

SDD — Spec-Driven Development: show spec states dashboard.

Grounds every implementation decision in official documentation.

Write software using the RED-GREEN-REFACTOR cycle for reliable, well-tested code

Use when executing implementation plans with independent tasks in the current session

SDD — Spec-Driven Development: pause a spec to prevent auto-advance.

SDD — Spec-Driven Development: advance to the next pipeline step.