gotalab/cc-sdd

CC-SDD New Agent Integration adds or extends coding-agent support in cc-sdd by executing the SOP in docs/cc-sdd/sop-new-agent.md end-to-end. Use it when introducing a new agent, adding a subagent-capable variant, or migrating an existing supported agent to skills-based templates.

Implementation Gap Validation analyzes gaps between approved requirements and an existing codebase to inform implementation strategy. Use it before design to identify missing capabilities, integration challenges, and viable implementation approaches.

Implementation Integration Validation checks completed feature tasks as a whole to catch cross-task integration issues, run the full test suite, verify spec coverage, and confirm design boundaries before a GO/NO-GO call. Use it after all tasks in a feature are implemented to decide whether the implementation is ready.

Kiro Custom Steering Creation creates custom steering documents for specialized project contexts beyond core product, tech, and structure files. Use it to capture domain-specific patterns like API standards, testing strategies, or security conventions.

Kiro Debug investigates implementation failures using root-cause-first debugging, gathering evidence from errors, runtime config, and external docs to identify root cause and recommend the smallest safe next action. Use it when an implementer is blocked or verification fails.

Kiro Debug investigates implementation failures using root-cause-first debugging, gathering local evidence, runtime/config inspection, and external docs before proposing a fix. Use when an implementer is blocked, verification fails, or repeated remediation does not converge.

Kiro Discovery is the entry point for new work in a spec-driven development workflow. It scans existing project state, asks clarifying questions to identify boundaries, and proposes actionable approaches before implementation begins.

Kiro Discovery determines the best action path or work decomposition for new work, refining ideas through structured dialogue. Use it when starting a new feature, bug fix, or spec-driven task to identify whether to update an existing spec, create a new one, or skip specs.

Kiro Impl implements approved tasks using test-driven development and subagent dispatch. It runs all pending tasks autonomously or selected tasks manually, verifying tests pass before marking tasks complete.

Kiro Impl implements approved tasks using test-driven development and native subagent dispatch, running pending tasks autonomously or selected tasks manually.

Kiro Review performs adversarial task-local review of a task implementation against approved specs, task boundaries, and verification evidence. Use it after an implementer finishes a task, after remediation, or before accepting a task as complete.

Kiro Review performs adversarial review of a task implementation against approved specs, task boundaries, and verification evidence. Use it after an implementer reports the task ready, after remediation, or before accepting a task as complete.

Kiro Spec Batch generates complete specs (requirements, design, tasks) for all pending roadmap features by dispatching parallel subagents grouped by dependency waves, then runs a cross-spec consistency review. Use it when briefs exist for all features and you want spec-driven development specs created in dependency order.

Kiro Spec Design creates comprehensive technical designs for specifications, mapping requirements to components, interfaces, and file structures after discovery research and synthesis. Use it to produce design documents that guide implementation tasks in spec-driven development.

Kiro Spec Design generates comprehensive technical designs that translate requirements into architecture through a discovery process. Use it when creating architecture from requirements or extending an existing system.

Kiro Spec Init initializes the specification structure for a new feature in spec-driven development, creating spec.json and requirements.md from templates after clarifying project intent and checking for an existing brief.

Kiro Spec Quick generates specification files for a feature by running four phases—initialize spec, requirements, design, and tasks—with interactive or automatic modes. Use it to quickly scaffold a spec-driven development workflow and sanity-check the generated artifacts.

Kiro Spec Status reads a specification's files and reports its current phase, completion percentage, task breakdown, boundary context, and next actions. Use it to see where a spec-driven development effort stands and what blockers or revalidation needs are next.

Kiro Spec Tasks reads specification documents and generates an implementation task plan, mapping every requirement to executable 1–3 hour tasks with dependencies and parallel markers. Use it in spec-driven development to turn approved requirements and design into a reviewable tasks.md.

Kiro Steering Management maintains {{KIRO_DIR}}/steering/ as persistent project knowledge, bootstrapping core steering files from the codebase and syncing them as the project evolves. Use it to keep AI agents' shared context aligned with codebase patterns and principles.

Kiro Validate Design reviews technical design documents against requirements and project context, identifying critical issues and giving a GO/NO-GO decision before implementation.

Spec Batch creates complete specification files (spec.json, requirements.md, design.md, tasks.md) for all features in a roadmap by dispatching sub-agents in dependency-ordered waves. Use it when you need to generate specs for a whole project roadmap and verify cross-spec consistency.

Spec Requirements generates a comprehensive requirements document aligned with steering context, using EARS-formatted acceptance criteria to capture user-observable behavior and explicit scope boundaries for spec-driven development. Use it after discovery to turn a project brief into testable, unambiguous requirements before design.

Verify Completion checks completion and success claims against fresh command evidence before a task, fix, test, or feature is reported as done. Use it before closing tasks, trusting subagent success, or giving feature GO.