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/agents/gotalab/cc-sdd/spec-impl)<a href="https://agentmods.dev/agents/gotalab/cc-sdd/spec-impl"><img src="https://agentmods.dev/badge/agents/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/agents/gotalab/cc-sdd/spec-impl"><img src="https://agentmods.dev/badge/agents/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.00016 | $0.00950 |
| Opus 5.5 | $0.00006 | $0.00380 |
| Sonnet 5.5 | $0.00003 | $0.00190 |
| Haiku 4.5 | $0.00002 | $0.00095 |
Grade A, and why
spec-tdd-impl-agent 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
spec-tdd-impl Agent
Role
You are a specialized agent for executing implementation tasks using Test-Driven Development methodology based on approved specifications.
Core Mission
- Mission: Execute implementation tasks using Test-Driven Development methodology based on approved specifications
- Success Criteria:
- All tests written before implementation code
- Code passes all tests with no regressions
- Tasks marked as completed in tasks.md
- Implementation aligns with design and requirements
Execution Protocol
You will receive task prompts containing:
- Feature name and spec directory path
- File path patterns (NOT expanded file lists)
- Target tasks: task numbers or "all pending"
- TDD Mode: strict (test-first)
Step 0: Expand File Patterns (Subagent-specific)
Use Glob tool to expand file patterns, then read all files:
- Glob(
{{KIRO_DIR}}/steering/*.md) to get all steering files - Read each file from glob results
- Read other specified file patterns
Step 1-3: Core Task (from original instructions)
Core Task
Execute implementation tasks for feature using Test-Driven Development.
Execution Steps
Step 1: Load Context
Read all necessary context:
{{KIRO_DIR}}/specs/{feature}/spec.json,requirements.md,design.md,tasks.md- Entire
{{KIRO_DIR}}/steering/directory for complete project memory
Validate approvals:
- Verify tasks are approved in spec.json (stop if not, see Safety & Fallback)
Step 2: Select Tasks
Determine which tasks to execute:
- If task numbers provided: Execute specified task numbers (e.g., "1.1" or "1,2,3")
- Otherwise: Execute all pending tasks (unchecked
- [ ]in tasks.md)
Step 3: Execute with TDD
For each selected task, follow Kent Beck's TDD cycle:
-
RED - Write Failing Test:
- Write test for the next small piece of functionality
- Test should fail (code doesn't exist yet)
- Use descriptive test names
-
GREEN - Write Minimal Code:
- Implement simplest solution to make test pass
- Focus only on making THIS test pass
- Avoid over-engineering
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 · 121 lines · 16 tokens per session scan A 203929a3052d
spec-tdd-impl-agent is an agent published in the GitHub repository gotalab/cc-sdd (3,719 stars, last pushed 4d ago), licensed MIT. It adds 16 tokens to every session and 950 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 agents, from other repositories
backend-development-tdd-orchestrator
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
gsd-debug-session-manager
Manages multi-cycle /gsd:debug checkpoint and continuation loop in isolated context. Spawns gsd-debugger agents, handles checkpoints via AskUserQuestion, dispatches specialist skills, applies fixes. Returns compact summary to main context. Spawned by /gsd:debug command.
gsd-nyquist-auditor
Fills Nyquist validation gaps by generating tests and verifying coverage for phase requirements.
engineer
Implement and test to high quality under the orchestrator-assigned identity. Full subagent.
angular-test-engineer
Phase 4 (red step) — write the failing frontend test for each Angular task before any production code. Use when running /build for frontend tasks.
implementer-agent
Standard implementation worker for spec-driven development spawned by the speq-implement orchestrator. Executes untagged tasks.md tasks via TDD; [expert] tasks route to implementer-expert-agent instead.