cc-sdd skill
Kiro-style spec-driven development: a skill set that takes work from idea through requirements and design to autonomous implementation
- 3,746 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Autonomous implementation writes code and runs tests in the project
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/cc-sddDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Autonomous implementation writes code and runs tests in the project
This is third-party code. Review the repository files before installing.
What it does
A single npx command installs 17 kiro-* skills into the project. The kiro-discovery skill analyzes the request and decides whether to create a spec, extend an existing one or implement directly. The agent then writes requirements, a design with a file structure plan and tasks, and a human approves each phase. The kiro-impl skill runs tasks one at a time with TDD, an independent reviewer and a separate debug pass when work gets stuck.
Who it is for. For teams and developers who want the agent to follow an approved spec rather than one-off prompts.
Good fit when
- You need to build a large feature in phases with human review
- You need to split a big initiative into several specs
- You want long-running autonomous implementation with per-task review
Not a fit when
- A small edit or one-off bug where a spec is overkill
- The team will not approve documents at each phase
Example request
/kiro-discovery add subscription billing with a trial period to the serviceLimitations
Stable in Claude Code and Codex; Cursor, Copilot, Windsurf, OpenCode, Gemini CLI and Antigravity support is in beta. The process produces many documents and spends tokens on reviews and subagents.
How to disable. Delete the kiro-* skill folders from the agent's skills directory in the project.
FAQ
Is it compatible with Kiro?
Yes, existing Kiro specs remain compatible and portable.
Can documents be in another language?
The installer takes a --lang flag and supports 13 languages; see the package README for the list.
Discussion
No questions or reviews yet.
Related
SkillsTwo skills for spec-driven development: /spec asks questions and saves a document to specs/, /spec-impl implements an approved spec step by step
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
An evidence-first development skill: the agent wraps code in a spec and a gauntlet of checks so line-by-line review becomes optional
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Eleven skills for the development loop: interview and spec, TDD build, UI, docs and codebase maintenance
Eleven skills take an agent from an idea to verified code through a PRD and RFCs kept as files in the repository
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| cc-sdd (this entry) | no | 3,746 | ||
| Fernando Skills | no | 348 | two skills for spec-driven development | |
| Spec-Driven Development MCP server: prompts for spec-first work | no | not required | 439 | three MCP prompts walk an agent from EARS-style requirements to a |
| Dryforge | no | 430 | a plugin with ready |
README in short
The README explains the approach: the spec is a contract between parts of the system while code stays the source of truth. Version 3.0 is rebuilt around Agent Skills with kiro-discovery, kiro-impl, kiro-spec-batch and boundary-first design.md. Installation is one npx command with agent and language flags, plus a table of common workflows and a migration guide. MIT licensed.
README badge
Original SKILL.md
---
name: kiro-discovery
description: 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.
disable-model-invocation: true
allowed-tools: Read, Write, Glob, Grep, Agent, WebSearch, WebFetch, AskUserQuestion
argument-hint: <idea-or-request>
---
# kiro-discovery Skill
## Core Mission
- **Success Criteria**:
- Correct action path or work decomposition identified based on existing project state
- User's intent clarified through questions, not assumptions
- Output is an actionable next step (not just a description)
## Execution Steps
### Step 1: Lightweight Scan
Gather **only metadata** to determine the action path. Do NOT read full file contents yet.
- **Specs inventory**: Glob `{{KIRO_DIR}}/specs/*/spec.json`, read each spec.json for `name`, `phase` fields and `approvals` status. Note feature names and their current status.
- **Steering existence**: Check which files exist in `{{KIRO_DIR}}/steering/` (product.md, tech.md, structure.md, roadmap.md). Do NOT read their contents yet.
- **Roadmap check**: If `{{KIRO_DIR}}/steering/roadmap.md` exists, read it. This contains project-level context (approach, scope, constraints, spec list) from a previous discovery session. Use it to restore project context.
- **Top-level structure**: List the project root directory to note key directories and files. Do NOT recurse into subdirectories.
This step should consume minimal context. If `specs/` is empty and no steering exists, note "greenfield project" and move to Step 2.
### Step 2: Determine Action Path
Based on the user's request and the metadata from Step 1, determine which path applies:
**Path A: Existing spec covers this**
- The request is an extension, enhancement, or fix within an existing spec's domain
- Every meaningful part of the request fits that same spec boundary
- Any remaining small follow-up work can be handled directly without creating a new spec
- Skip remaining steps