cc-sdd emerging

Core approach

A faithful port of Kiro's requirements → design → tasks process into agent-agnostic tooling: npx cc-sdd@latest installs the same 17-skill set into whichever agent you use, with spec artifacts in .kiro/specs/<feature>/ (EARS-format requirements.md, design.md with a File Structure Plan, tasks.md with parallel waves) and project memory in .kiro/steering/. Its stance is that the spec is a contract between parts of the system, not a master command document — code remains the source of truth. Humans approve each phase at gates recorded in spec.json, then implementation runs autonomously with a per-task trio of fresh implementer, independent reviewer, and on-demand debugger.

Workflow

1. /kiro-discovery — entry-point router that writes brief.md and decides: extend an existing spec, implement directly with no spec, create one spec, or decompose into several
2. /kiro-spec-init — create the .kiro/specs/<feature>/ workspace
3. /kiro-spec-requirements — EARS-format requirements, then a human approval gate
4. /kiro-spec-design — design.md with Mermaid diagrams and a File Structure Plan, then an approval gate
5. /kiro-spec-tasks — task list with parallel-wave labels and boundary annotations, then an approval gate
6. /kiro-impl — autonomous implementation: per task, a fresh implementer (TDD behind feature flags), an independent reviewer, and a debugger spawned in a clean context when blocked
7. /kiro-validate-impl — feature-level validation with GO / NO-GO verdicts
8. Optional: /kiro-steering for project memory, /kiro-validate-gap for brownfield gap analysis, /kiro-spec-batch for parallel multi-spec creation with cross-spec review

Supported tools

• Claude Code
• Codex
• Cursor
• GitHub Copilot
• Windsurf
• OpenCode
• Gemini CLI
• Antigravity
• Qwen Code

Tracked projects using cc-sdd

• GROWI

  drift: none

  Team collaboration wiki (est. 2017) running feature development through Kiro-style spec folders — one folder per feature with spec.json, requirements.md, design.md, and tasks.md, plus a full steering set.

  growilabs/growi · using cc-sdd · ★ 1.5K stars · pushed 2 hours ago · Reviewed last month

  View project →

Notes

cc-sdd was created three days after AWS’s Kiro IDE went into public preview, as an explicit recreation of Kiro’s spec-driven process inside Claude Code — the homage is fossilized in every command name and the .kiro/ directory, and two-way spec compatibility with Kiro is a maintained feature. The name outgrew itself: “cc” meant Claude Code, but the same skill set now installs into eight agents. Its most articulated position is the inverse of Spec Kit’s: code, not the spec, remains the source of truth, and the spec is a human-approved contract that fixes boundaries while leaving the design space inside them to the agent. With v3.0 the project repositioned from spec generator to autonomous implementation harness, and unusually for the category it dogfoods in the open — the repo carries a live .kiro/ tree with example specs, and its own CLAUDE.md mandates the three-gate workflow for the project’s development.

Added Jul 18, 2026 · Assessment last reviewed Jul 18, 2026 · How we track