“spec-driven development”

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

Background knowledge about Spec-Driven Development and dude's behavior verification system.

Use when executing implementation plans with independent tasks — orchestration pattern for worktree isolation, TDD discipline, and two-stage review.

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

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

Execute plans via subagents with a two-stage review (spec then quality).

Initialize Spec-Driven Development context in any project.

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

Verify current, version-specific framework, library, tool, and external API behavior against authoritative upstream sources before relying on it.

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

Use when implementing or changing code behavior, before writing production code.

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

Use when executing the host agent's active built-in plan with independent tasks in the current session

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

Create or update feature specifications from natural language descriptions.

Use for nondeterministic Agent rules, Skills, prompts, Hooks, or routing—not deterministic logic, bug fixes with known causes, or deterministic refactors.

Grounds every implementation decision in official documentation.

Drives development with tests using the red-green-refactor loop.

Strict red-green-refactor protocol.

Revisión adversarial en contexto limpio de cada decisión no trivial antes de seguir.

Use when implementing a behavior change, bug fix, or refactor that can be expressed through automated tests.

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