Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.
cc-sdd
Kiro-style requirements/design/tasks workflow packaged as 17 Agent Skills for 8 agents, with discovery routing, EARS requirements and long-running autonomous implementation with per-task review.
v3.1.0 released 2026-09-23; repo pushed 2026-10-22 (checked 2026-10-25)
In Spec-driven development
Where it stands apart
- How is it mainly sustained? individual side project, no revenue (6% of 18 others)
- Which shared standard or format does it mainly build on? the Kiro spec layout (requirements in EARS, design, tasks files) (11% of 19 others)
- What format are specs written in? markdown with a required requirement syntax (e.g. EARS, SHALL/WHEN scenarios) (17% of 18 others)
- How is the path from idea to code structured? adaptive: the process scales to the size of the change (11% of 19 others)
- What does it offer teams beyond sharing files in git? (if both, pick the paid product) team features in the open-source tool (shared spec stores, multi-developer or multi-agent coordination) (11% of 18 others)
What it shares with most of the community
- Is it actively maintained? active (74% of 19 others)
- How is the main thing licensed? permissive open source (MIT/Apache/BSD) (74% of 19 others)
- Can it run entirely on your own device or infrastructure, without the maker's servers? yes (79% of 19 others)
- Do you need an account to use it? no account (74% of 19 others)
- Who is it for? developers (100% of 19 others)
- Once code exists, what is the spec? a planning scaffold: code becomes the truth after implementation (53% of 19 others)
- Where do specs live? plain files in the project repository (89% of 19 others)
- Which coding agents does it work with? many agents (five or more) (78% of 18 others)
- Does a human approve the spec or plan before code is written? yes, the workflow waits for approval (50% of 18 others)
Nearest neighbors
- Superpowers 76% of 17 shared answers match
- GSD (Get Shit Done) / GSD Core 69% of 16 shared answers match
- Backlog.md 65% of 17 shared answers match
Every answer
| Question | Answer | Source |
|---|---|---|
| Is it actively maintained? | active | source 2026-10-25 |
| How is the main thing licensed? | permissive open source (MIT/Apache/BSD) MIT | source 2026-10-25 |
| How is it mainly sustained? | stands apart individual side project, no revenue Individual-owned MIT repo; no sponsor, pricing or funding links found. | source 2026-10-26 |
| Can it run entirely on your own device or infrastructure, without the maker's servers? | yes | source 2026-10-25 |
| Do you need an account to use it? | no account Skills installed via npx into your agent; no account with the maker. | source 2026-10-26 |
| Who is it for? | developers | source 2026-10-25 |
| Which shared standard or format does it mainly build on? | stands apart the Kiro spec layout (requirements in EARS, design, tasks files) Kiro-style requirements/design/tasks in EARS ('Existing Kiro specs remain compatible'), packaged as Agent Skills. | source 2026-10-26 |
| Once code exists, what is the spec? | a planning scaffold: code becomes the truth after implementation 'Code remains the source of truth'; specs are contracts at boundaries. Closest to scaffold, though specs can be extended later. | source 2026-10-25 |
| After implementation, what built-in step keeps specs and code aligned? (if several, the first that applies) | a step checks code against the spec (tests, review, or verifier) Independent per-task review checks boundary violations; validate-gap for existing systems. | source 2026-10-25 |
| What format are specs written in? | stands apart markdown with a required requirement syntax (e.g. EARS, SHALL/WHEN scenarios) requirements.md in EARS format. | source 2026-10-25 |
| Where do specs live? | plain files in the project repository | source 2026-10-25 |
| Which coding agents does it work with? | many agents (five or more) Claude Code, Codex (stable); Cursor, Copilot, Devin, OpenCode, Gemini CLI, Antigravity (beta). | source 2026-10-25 |
| What form does it mainly ship in? | prompts, skills, or slash commands installed into an agent (even if a CLI installs them) Installed as Agent Skills via npx. | source 2026-10-25 |
| How is the path from idea to code structured? | stands apart adaptive: the process scales to the size of the change /kiro-discovery routes to no spec, one spec, or multi-spec batch. | source 2026-10-25 |
| Does a human approve the spec or plan before code is written? | yes, the workflow waits for approval 'humans approve the contract at phase gates'. | source 2026-10-25 |
| By default, once a plan is approved, how is implementation run? | agents run the whole plan with automated review or verification loops /kiro-impl: fresh implementer per task, TDD, independent reviewer, auto-debug. | source 2026-10-25 |
| What does it offer teams beyond sharing files in git? (if both, pick the paid product) | stands apart team features in the open-source tool (shared spec stores, multi-developer or multi-agent coordination) /kiro-spec-batch with cross-spec review for parallel work at 'team scale'. | source 2026-10-25 |
Sources
This page was derived from:
- GitHub · github.com/gotalab/cc-sdd · read 2026-10-25
- GitHub · github.com/gotalab/cc-sdd/releases · read 2026-10-25
RSS for this project · Its own release feed
Are you a maintainer? Claiming and correcting projects is coming soon.