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-spec-tasks)<a href="https://agentmods.dev/commands/gotalab/cc-sdd/kiro-spec-tasks"><img src="https://agentmods.dev/badge/commands/gotalab/cc-sdd/kiro-spec-tasks/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-spec-tasks"><img src="https://agentmods.dev/badge/commands/gotalab/cc-sdd/kiro-spec-tasks.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.01434 |
| Opus 5.5 | $0.00000 | $0.00574 |
| Sonnet 5.5 | $0.00000 | $0.00287 |
| Haiku 4.5 | $0.00000 | $0.00143 |
Grade A, and why
kiro-spec-tasks 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 2mo 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
3 near-identical copies found in the catalogue:
- spec-tasks — 89% identical, 46 lines differ
- spec-tasks — 89% identical, 44 lines differ
- kiro-spec-tasks — 88% identical, 20 lines differ
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 Tasks Generator
<background_information>
- Mission: Generate detailed, actionable implementation tasks that translate technical design into executable work items
- Success Criteria:
- All requirements mapped to specific tasks
- Tasks properly sized (1-3 hours each)
- Clear task progression with proper hierarchy
- Natural language descriptions focused on capabilities </background_information>
Execution Steps
Step 1: Load Context
Read all necessary context:
{{KIRO_DIR}}/specs/$1/spec.json,requirements.md,design.md{{KIRO_DIR}}/specs/$1/tasks.md(if exists, for merge mode)- Entire
{{KIRO_DIR}}/steering/directory for complete project memory
Validate approvals:
- If
-yflag provided ($2 == "-y"): Auto-approve requirements and design in spec.json - Otherwise: Verify both approved (stop if not, see Safety & Fallback)
- Determine sequential mode based on presence of
--sequential
Step 2: Generate Implementation Tasks
Load generation rules and template:
- Read
{{KIRO_DIR}}/settings/rules/tasks-generation.mdfor principles - If
sequentialis false: Read{{KIRO_DIR}}/settings/rules/tasks-parallel-analysis.mdfor parallel judgement criteria - Read
{{KIRO_DIR}}/settings/templates/specs/tasks.mdfor format (supports(P)markers)
Generate task list following all rules:
- Use language specified in spec.json
- Map all requirements to tasks
- When documenting requirement coverage, list numeric requirement IDs only (comma-separated) without descriptive suffixes, parentheses, translations, or free-form labels
- Ensure all design components included
- Verify task progression is logical and incremental
- Collapse single-subtask structures by promoting them to major tasks and avoid duplicating details on container-only major tasks (use template patterns accordingly)
- Apply
(P)markers to tasks that satisfy parallel criteria (omit markers when sequential mode requested) - Mark optional test coverage subtasks with
- [ ]*only when they strictly cover acceptance criteria already satisfied by core implementation and can be deferred post-MVP - If existing tasks.md found, merge with new content
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.
- 2mo ago First seen · 141 lines · 0 tokens per session scan A 53bd962257d7
kiro-spec-tasks is a command published in the GitHub repository gotalab/cc-sdd (3,745 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,434 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
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…
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…
autonomous-run
Run one approved task in one supervised session with the direct-use reference dispatcher, delegating verifiable slices to existing commands and emitting PROPOSED diffs only and never creating commits or attestation refs. Use when a maintainer invokes Fhorja directly after approve-plan and a BOOT verdict from…
direction-adjust
Capture a small-to-medium course correction found mid-task in your own work: record a D-N entry in DECISIONS.md, update TASKSTATE.md, and route back to the command. Use when it is worth recording, does not invalidate the whole approach, and the current slice stays recoverable with a small plan change. Do not use for…
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…