“spec-driven development”

Use when starting Claude Code projects, writing CLAUDE.md/spec.md, dispatching subagents, or requesting Agent Teams parallel development.

Start spec-driven development — write a structured specification before writing code

Spec-driven development and multi-layer verification pipeline that replaces manual code review.

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

Use when the user explicitly requests strict or test-first TDD, or when the current conversation already contains an explicit `TDD Route: strict` decision…

Articulate and define a single feature within spec-driven development — plan.md, requirements.md, and validation.md in a dated feature directory under specs/.

Spec-Driven Development workflow (constitution to specify to plan to tasks to implement to converge).

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

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

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

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

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.

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.

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

Use when implementing deterministic, reusable code where regressions would warrant a CI red light.

SDD 工作流主入口。启动 Orchestrator 驱动完整的 spec-driven development 流程：intake → spec → plan → tasks → implement → review → validate。当用户想要按 SDD 流程开发新 feature 时使用。

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