cc-sdd is a spec-driven development workflow for coding agents: it turns approved software specifications into requirements, designs, task plans, and extended autonomous implementation. Developers use it across several AI coding agents, with independent review and task-level continuation for long-running work. The catalogue entries provide commands, skills, agents, and instructions for using this workflow.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/gotalab/cc-sddWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/gotalab/cc-sdd/spec-requirements)<a href="https://agentmods.dev/commands/gotalab/cc-sdd/spec-requirements"><img src="https://agentmods.dev/badge/commands/gotalab/cc-sdd/spec-requirements.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00006 | $0.00428 |
| Opus 5 | $0.00003 | $0.00214 |
| Sonnet 5 | $0.00001 | $0.00086 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
spec-requirements scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Requirements Generation
Parse Arguments
- Feature name:
$1
Validate
Check that spec has been initialized:
- Verify
{{KIRO_DIR}}/specs/$1/exists - Verify
{{KIRO_DIR}}/specs/$1/spec.jsonexists
If validation fails, inform user to run /kiro:spec-init first.
Invoke Subagent
Delegate requirements generation to spec-requirements-agent:
Use the Task tool to invoke the Subagent with file path patterns:
Task(
subagent_type="spec-requirements-agent",
description="Generate EARS requirements",
prompt="""
Feature: $1
Spec directory: {{KIRO_DIR}}/specs/$1/
File patterns to read:
- {{KIRO_DIR}}/specs/$1/spec.json
- {{KIRO_DIR}}/specs/$1/requirements.md
- {{KIRO_DIR}}/steering/*.md
- {{KIRO_DIR}}/settings/rules/ears-format.md
- {{KIRO_DIR}}/settings/templates/specs/requirements.md
Mode: generate
"""
)
Display Result
Show Subagent summary to user, then provide next step guidance:
Next Phase: Design Generation
If Requirements Approved:
- Review generated requirements at
{{KIRO_DIR}}/specs/$1/requirements.md - Optional Gap Analysis (for existing codebases):
- Run
/kiro:validate-gap $1to analyze implementation gap with current code - Identifies existing components, integration points, and implementation strategy
- Recommended for brownfield projects; skip for greenfield
- Run
- Then
/kiro:spec-design $1 [-y]to proceed to design phase
If Modifications Needed:
- Provide feedback and re-run
/kiro:spec-requirements $1
Note: Approval is mandatory before proceeding to design phase.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 63 lines · 6 tokens per session scan A 5f2438018349
spec-requirements is a command published in the GitHub repository gotalab/cc-sdd (3,653 stars, last pushed 3mo ago), licensed MIT. It adds 6 tokens to every session and 428 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
implementation-plan
Define an incremental, reviewable, production-safe implementation plan for the active task and persist it as IMPLEMENTATIONPLAN.md plus a TASKSTATE.md update. Breaks work into the smallest safe slices with objective, exact scope, ordering rationale, key risks, validation approach, exit criteria, and work complexity…
slice-closure
Decide whether the current slice is ready to close, distinguishing slice completion from full task completion, then persist the result in slice notes and TASKSTATE.md as explicit reviewable closure notes. For single-slice tasks may route directly to delivery. Returns no-op when slice memory would not materially…
task-init
Initialize the official task folder and base task memory inside projects/ /active/YYYY-MM-DD /. Creates README.md, TASKSTATE.md, SOURCEOFTRUTH.md, DECISIONS.md, IMPLEMENTATIONPLAN.md; seeds from PROJECTCHARTER.md when present; emits a multi-repo.
decision-interview
Ask the minimum set of high-value decision questions needed before turning the task into canonical implementation rules. Decisions that would change runtime behavior, data integrity, rollout safety, or test strategy. Use when the missing information is decision-driven (not factual), different answers would change…
godot-scene-plan
Plan the Godot scene and node structure for a 2D or 3D game feature before any GDScript is written: the scene tree, node types and responsibilities, autoloads (singletons), signal wiring, the input map, and the resources and sub-scenes to create. Produces GODOTSCENEPLAN.md, a design-time plan an MCP-driven editor or a…
release-plan
Design a pre-deploy release and rollout strategy for a change: pick the rollout pattern (feature flag, canary, blue-green, or full progressive delivery) by risk and infra, then specify the exposure ramp, the promotion metric and threshold that advances each step, and the rollback trigger and mechanism. Produces…