“spec-driven development”

Use when the user wants a spec-driven development workflow for implementing a feature in the current codebase, from fuzzy idea or existing active spec through…

Creates specs before coding.

Detailed implementation plans and spec-driven development

Use when executing a written implementation plan with independent tasks in the current session where delegation beats inline coordination cost; otherwise…

Execute an approved plan by delegating isolatable steps to isolated child sessions (Host serializes writers), then review diffs and verify in the parent.

Spec-Driven Development workflow for OpenClaw.

Execute an approved plan by delegating isolatable steps to isolated child sessions (Host serializes writers), then review diffs and verify in the parent.

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

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

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

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.

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.

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.