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-initgit 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-init)<a href="https://agentmods.dev/skills/gotalab/cc-sdd/kiro-spec-init"><img src="https://agentmods.dev/badge/skills/gotalab/cc-sdd/kiro-spec-init/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-init"><img src="https://agentmods.dev/badge/skills/gotalab/cc-sdd/kiro-spec-init.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.00715 |
| Opus 5.5 | $0.00005 | $0.00286 |
| Sonnet 5.5 | $0.00003 | $0.00143 |
| Haiku 4.5 | $0.00001 | $0.00072 |
Grade A, and why
kiro-spec-init 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-init — 86% identical, 16 lines differ
- kiro-spec-init — 83% identical, 18 lines differ
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Initialization
Execution Steps
- Check for Brief: If
{{KIRO_DIR}}/specs/{feature-name}/brief.mdexists (created by/kiro-discovery), read it. The brief contains problem, approach, scope, and constraints from the discovery session. Use this to pre-fill the project description and skip clarification questions that the brief already answers. - Clarify Intent: The Project Description in requirements.md must contain three elements: (a) who has the problem, (b) current situation, (c) what should change. If a brief.md exists and covers these, skip to step 3. Otherwise, ask the user to clarify before proceeding. Ask as many questions as needed; do not fill in gaps with your own assumptions.
- Check Uniqueness: Verify
{{KIRO_DIR}}/specs/for naming conflicts. If the directory already exists with onlybrief.md(nospec.json), use that directory (discovery created it). - Create Directory:
{{KIRO_DIR}}/specs/[feature-name]/(skip if already exists from discovery) - Initialize Files Using Templates:
- Read
{{KIRO_DIR}}/settings/templates/specs/init.json - Read
{{KIRO_DIR}}/settings/templates/specs/requirements-init.md - Replace placeholders:
{{FEATURE_NAME}}→ generated feature name{{TIMESTAMP}}→ current ISO 8601 timestamp{{PROJECT_DESCRIPTION}}→ from brief.md if available, otherwise $ARGUMENTS{{LANG_CODE}}→ language code (detect from user's input language, default toen)
- Write
spec.jsonandrequirements.mdto spec directory
- Read
Important Constraints
- Do NOT generate requirements, design, or tasks. This skill only creates spec.json and requirements.md.
Output Description
Provide output in the language specified in spec.json with the following structure:
- Generated Feature Name:
feature-nameformat with 1-2 sentence rationale - Project Summary: Brief summary (1 sentence)
- Created Files: Bullet list with full paths
- Next Step: Command block showing
/kiro-spec-requirements <feature-name>
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 First seen · 52 lines · 13 tokens per session scan A b5492b0f688a
kiro-spec-init 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 715 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…