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.
npx skills add gotalab/cc-sdd --skill kiro-spec-requirementsgit 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/skills/gotalab/cc-sdd/kiro-spec-requirements)<a href="https://agentmods.dev/skills/gotalab/cc-sdd/kiro-spec-requirements"><img src="https://agentmods.dev/badge/skills/gotalab/cc-sdd/kiro-spec-requirements/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/gotalab/cc-sdd/kiro-spec-requirements"><img src="https://agentmods.dev/badge/skills/gotalab/cc-sdd/kiro-spec-requirements.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00013 | $0.01814 |
| Opus 5.5 | $0.00005 | $0.00726 |
| Sonnet 5.5 | $0.00003 | $0.00363 |
| Haiku 4.5 | $0.00001 | $0.00181 |
Grade A, and why
kiro-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 1mo 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- kiro-spec-requirements — 95% identical, 22 lines differ
- kiro-spec-requirements — 89% identical, 109 lines differ
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements Generation
<background_information>
- Success Criteria:
- Create complete requirements document aligned with steering context
- Follow the project's EARS patterns and constraints for all acceptance criteria
- Focus on core functionality without implementation details
- Make inclusion/exclusion boundaries explicit when scope could otherwise be misread
- Update metadata to track generation status </background_information>
-
Load Context:
- Read
{{KIRO_DIR}}/specs/$1/spec.jsonfor language and metadata - Read
{{KIRO_DIR}}/specs/$1/brief.mdif it exists (discovery context: problem, approach, scope decisions, boundary candidates) - Read
{{KIRO_DIR}}/specs/$1/requirements.mdfor project description - Core steering context:
product.md,tech.md,structure.md - Additional steering files only when directly relevant to feature scope, user personas, business/domain rules, compliance/security constraints, operational constraints, or existing product boundaries
- Use explicitly requested skills and task-relevant local skills/playbooks, including design, accessibility, and UX. Select by description and read only needed guidance, even for small tasks; preserve required checks and host/project rules.
- Read
-
Read Guidelines:
- Read
rules/ears-format.mdfrom this skill's directory for EARS syntax rules - Read
rules/requirements-review-gate.mdfrom this skill's directory for pre-write review criteria - Read
{{KIRO_DIR}}/settings/templates/specs/requirements.mdfor document structure
- Read
Parallel Research (sub-agent dispatch)
The following research areas are independent. Decide the optimal decomposition based on project complexity -- split, merge, add, or skip sub-agents as needed.
In main context (essential for requirements generation):
- Spec files: spec.json, brief.md, requirements.md (project description)
- EARS format rules, requirements review gate, requirements template
- Core steering: product.md, tech.md (directly inform scope and constraints)
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.
- 1mo ago Changed 66ce682dc510
- 1mo ago First seen · 143 lines · 13 tokens per session scan A 79d3d5af09c3
kiro-spec-requirements is a skill published in the GitHub repository gotalab/cc-sdd (3,745 stars, last pushed 6d ago), licensed MIT. It adds 13 tokens to every session and 1,814 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
todo-for-ai-agent-runtime
Runtime integration skill for external agents connecting to Todo for AI over HTTP API Token / Agent Key, including auth, task lease, events, commit, and task logs.
decision-interview
Ask the minimum decision questions needed before turning the task into canonical implementation rules, on behavior, data integrity, rollout safety, or test strategy. Use when missing information is decision-driven (not factual) or undecided policy blocks planning; in an attended chain it records an open decision as…
implementation-plan
Define an incremental plan for the active task as IMPLEMENTATIONPLAN.md plus a TASKSTATE.md update: smallest safe slices with scope, validation and exit criteria. No code is written. A --spec mode derives slices from a spec or PRD. A retrofit mode annotates in-progress plans so they can adopt implement-fleet. Do not…
repo-consistency-sweep
Defect-class detection for the lower-value half of code review: convention drift, type-safety gaps, security and multi-tenant invariants, operability issues. Runs after review-hard. Checks against a curated bug-class library that grows via pr-feedback-ingest. Use when at least one slice is implemented and you want a…
slice-closure
Decide whether the current slice is ready to close, separating slice completion from task completion, and record the result in slice notes and TASKSTATE.md. Use when a slice was implemented, validated or reviewed and may be ready to close. Do not use before slice implementation, during planning, or for overall task…
task-close
Close a whole finished task: verify the spec done-conditions, set TASKSTATE.md to its final closed state, and move the folder from active/ to archive/. Use when all slices are closed, the work is merged or explicitly waived, and the task is ending. Do not use for one slice (use slice-closure), unfinished work…