cc-sdd

Investigate implementation failures using root-cause-first debugging. Use when an implementer is blocked, verification fails, or repeated remediation does not converge.

Entry point for new work. Determines the best action path or work decomposition (update existing spec, create new spec, mixed decomposition, or no spec needed) and refines ideas through structured dialogue.

Implement approved tasks using TDD with subagent dispatch. Runs all pending tasks autonomously or selected tasks manually.

Review a task implementation against approved specs, task boundaries, and verification evidence. Use after an implementer finishes a task, after remediation, or before accepting a task as complete.

Create complete specs (requirements, design, tasks) for all features in roadmap.md using parallel sub-agent dispatch by dependency wave.

Create comprehensive technical design for a specification

Initialize a new specification with detailed project description

Quick spec generation with interactive or automatic mode

Generate comprehensive requirements for a specification

Show specification status and progress

Generate implementation tasks for a specification

Create custom steering documents for specialized project contexts

Manage {{KIRO_DIR}}/steering/ as persistent project knowledge

Interactive technical design quality review and validation

Analyze implementation gap between requirements and existing codebase

Validate feature-level integration after all tasks are implemented. Checks cross-task consistency, full test suite, and overall spec coverage.

Verify completion and success claims with fresh evidence. Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO.

Implement approved tasks using TDD with native subagent dispatch. Runs all pending tasks autonomously or selected tasks manually.

Create complete specs (requirements, design, tasks) for all features in roadmap.md using parallel subagent dispatch by dependency wave.

Generate comprehensive technical design translating requirements (WHAT) into architecture (HOW) with discovery process. Use when creating architecture from requirements.

Generate EARS-format requirements based on project description and steering context. Use when generating requirements from project description.

Generate implementation tasks from requirements and design. Use when creating actionable task lists.

Create custom steering documents for specialized project contexts. Use when creating domain-specific steering files.

Maintain {{KIRO_DIR}}/steering/ as persistent project memory (bootstrap/sync). Use when initializing or updating steering documents.

Interactive technical design quality review and validation. Use when reviewing design before implementation.

Analyze implementation gap between requirements and existing codebase. Use when planning integration with existing systems.