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-impl)<a href="https://agentmods.dev/commands/gotalab/cc-sdd/spec-impl"><img src="https://agentmods.dev/badge/commands/gotalab/cc-sdd/spec-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/spec-impl"><img src="https://agentmods.dev/badge/commands/gotalab/cc-sdd/spec-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.00007 | $0.00509 |
| Opus 5.5 | $0.00003 | $0.00204 |
| Sonnet 5.5 | $0.00001 | $0.00102 |
| Haiku 4.5 | $0.00001 | $0.00051 |
Grade A, and why
spec-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- spec-impl — 86% identical, 12 lines differ
What it actually says
Implementation Task Executor
Parse Arguments
- Feature name:
$1 - Task numbers:
$2(optional)- Format: "1.1" (single task) or "1,2,3" (multiple tasks)
- If not provided: Execute all pending tasks
Validate
Check that tasks have been generated:
- Verify
{{KIRO_DIR}}/specs/$1/exists - Verify
{{KIRO_DIR}}/specs/$1/tasks.mdexists
If validation fails, inform user to complete tasks generation first.
Task Selection Logic
Parse task numbers from $2 (perform this in Slash Command before invoking Subagent):
- If
$2provided: Parse task numbers (e.g., "1.1", "1,2,3") - Otherwise: Read
{{KIRO_DIR}}/specs/$1/tasks.mdand find all unchecked tasks (- [ ])
Invoke Subagent
Delegate TDD implementation to spec-tdd-impl-agent:
Use the Task tool to invoke the Subagent with file path patterns:
Task(
subagent_type="spec-tdd-impl-agent",
description="Execute TDD implementation",
prompt="""
Feature: $1
Spec directory: {{KIRO_DIR}}/specs/$1/
Target tasks: {parsed task numbers or "all pending"}
File patterns to read:
- {{KIRO_DIR}}/specs/$1/*.{json,md}
- {{KIRO_DIR}}/steering/*.md
TDD Mode: strict (test-first)
"""
)
Display Result
Show Subagent summary to user, then provide next step guidance:
Task Execution
Execute specific task(s):
/kiro:spec-impl $1 1.1- Single task/kiro:spec-impl $1 1,2,3- Multiple tasks
Execute all pending:
/kiro:spec-impl $1- All unchecked tasks
Before Starting Implementation:
- IMPORTANT: Clear conversation history and free up context before running
/kiro:spec-impl - This applies when starting first task OR switching between tasks
- Fresh context ensures clean state and proper task focus
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 · 69 lines · 7 tokens per session scan A ddf3a127bebd
spec-impl is a command published in the GitHub repository gotalab/cc-sdd (3,719 stars, last pushed 4d ago), licensed MIT. It adds 7 tokens to every session and 509 once invoked, about $0.0000 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 commands, from other repositories
implement-approved-slice
Implement only the approved slice with minimal changes, then persist execution evidence in slice notes and TASKSTATE.md. The official execution path. Opt-in test-first mode via --tdd. Use when the plan and slice are approved, ambiguity is resolved and files in scope are known. Do not use during discovery or planning…
test-strategy
Define the smallest set of meaningful tests that protects behavior and reduces the regression risk for the active task, persisted as TESTSTRATEGY.md. Use when a change affects behavior, contracts, data flow or regression risk, or auth, biometric or runtime-risk scope lacks one, even if small. Do not use when the…
implement
Execute tasks from a track's implementation plan following TDD workflow.
test
Run TDD workflow — write failing tests, implement, verify. For bugs, use the Prove-It pattern.
api-aqa-flow
Workflow for backend API test automation: TMS / Issue Tracker test cases → automated API tests, HITL-gated.
api-aqa-flow-test-case-specification
Phase 4 Test Case Specification of api-aqa-flow (HITL APPROVAL GATE).