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/kiro-validate-impl)<a href="https://agentmods.dev/commands/gotalab/cc-sdd/kiro-validate-impl"><img src="https://agentmods.dev/badge/commands/gotalab/cc-sdd/kiro-validate-impl/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/commands/gotalab/cc-sdd/kiro-validate-impl"><img src="https://agentmods.dev/badge/commands/gotalab/cc-sdd/kiro-validate-impl.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01281 |
| Opus 5.5 | $0.00000 | $0.00512 |
| Sonnet 5.5 | $0.00000 | $0.00256 |
| Haiku 4.5 | $0.00000 | $0.00128 |
Grade A, and why
kiro-validate-impl 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.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Validation
<background_information>
- Mission: Verify that implementation aligns with approved requirements, design, and tasks
- Success Criteria:
- All specified tasks marked as completed
- Tests exist and pass for implemented functionality
- Requirements traceability confirmed (EARS requirements covered)
- Design structure reflected in implementation
- No regressions in existing functionality </background_information>
Execution Steps
1. Detect Validation Target
If no arguments provided ($1 empty):
- Parse conversation history for
/prompts:kiro-spec-impl <feature> [tasks]commands - Extract feature names and task numbers from each execution
- Aggregate all implemented tasks by feature
- Report detected implementations (e.g., "user-auth: 1.1, 1.2, 1.3")
- If no history found, scan
{{KIRO_DIR}}/specs/for features with completed tasks[x]
If feature provided ($1 present, $2 empty):
- Use specified feature
- Detect all completed tasks
[x]in{{KIRO_DIR}}/specs/$1/tasks.md
If both feature and tasks provided ($1 and $2 present):
- Validate specified feature and tasks only (e.g.,
user-auth 1.1,1.2)
2. Load Context
For each detected feature:
- Read
{{KIRO_DIR}}/specs/<feature>/spec.jsonfor metadata - Read
{{KIRO_DIR}}/specs/<feature>/requirements.mdfor requirements - Read
{{KIRO_DIR}}/specs/<feature>/design.mdfor design structure - Read
{{KIRO_DIR}}/specs/<feature>/tasks.mdfor task list - Load ALL steering context: Read entire
{{KIRO_DIR}}/steering/directory including:- Default files:
structure.md,tech.md,product.md - All custom steering files (regardless of mode settings)
- Default files:
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 · 141 lines · 0 tokens per session scan A 117a910084d2
kiro-validate-impl is a command published in the GitHub repository gotalab/cc-sdd (3,727 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,281 tokens. 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
full-review
Orchestrate comprehensive multi-dimensional code review using specialized review agents across architecture, security, performance, testing, and best practices.
refactor-guided
Systematic, safety-first refactoring with verification at each step. Never refactors and adds features simultaneously.
speckit.companion.living-coverage
Report living-spec requirement→test coverage — per requirement, whether its coverage tier maps a test (opt-in, read-only, never halts).
final-review
Command "final-review" from adriannoes/awesome-agentic-ai, covering final review - comprehensive pr review & testing, step 0: determine review pass, step 1: create or update the pr, step 2: launch three review agents in parallel and agent 1: codebase consistency reviewer.
sddp-qc
Command description: Run quality control against the implemented feature. Argument hint: [optional: testing focus such as unit tests, security audit, requirements sync] Command category: feature-delivery Prerequisites: spec, plan, tasks, implementation:complete.
pr-feedback-ingest
Turn PR feedback (Greptile, CI, bots, humans) into a traceable backlog, so the next step is a narrow implement-approved-slice. Corrective scope only. Use when a PR has review feedback to map to files and slices. Do not use for a new direction or contract (use post-review-pivot), no payload, or task-memory drift only…