kiro-spec-quick

kiro-spec-quick is a command for coding agents from gotalab/cc-sdd. It costs 8 tokens per session (2,589 once invoked), scanned A, a copy of spec-quick, MIT.

A command that creates a software specification in four stages: setup, requirements, design, and implementation tasks. It can either pause for approval between stages or run all stages automatically.

In plain words
What is it for?
Use it to turn a software idea or change into requirements, a design, and a task list for implementation.
Why use it?
It gathers the planning work into one repeatable command instead of requiring each specification stage to be started separately.

Command

About the project

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.

gotalab/cc-sdd · 3,652 stars · on GitHub

Install

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.

agentmods
npx agentmods add commands/gotalab/cc-sdd/kiro-spec-quick
Clone the repo
git clone --depth 1 https://github.com/gotalab/cc-sdd

Wrote 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.

agentmods badge for kiro-spec-quick

README.md
[![agentmods](https://agentmods.dev/badge/commands/gotalab/cc-sdd/kiro-spec-quick.svg)](https://agentmods.dev/commands/gotalab/cc-sdd/kiro-spec-quick)
Your own site
<a href="https://agentmods.dev/commands/gotalab/cc-sdd/kiro-spec-quick"><img src="https://agentmods.dev/badge/commands/gotalab/cc-sdd/kiro-spec-quick.svg" alt="Measured on agentmods" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,589 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 98% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00008 $0.02589
Opus 5 $0.00004 $0.01295
Sonnet 5 $0.00002 $0.00518
Haiku 4.5 $0.00001 $0.00259

Measured 6d ago against content hash 291526be836d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

kiro-spec-quick 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 6d 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.

Origin

This is a copy

98% identical to spec-quick — 26 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

tools/cc-sdd/templates/agents/opencode-agent/commands/kiro-spec-quick.md · 359 lines

How it starts

The opening of the file, as written. The whole thing — 359 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Quick Spec Generator

<background_information>

  • Mission: Execute all spec phases (init → requirements → design → tasks) in a single command
  • Success Criteria:
    • Interactive mode: User controls progression with approval prompts at each phase
    • Automatic mode: All phases execute without interruption when --auto flag provided
    • All generated specs maintain quality comparable to manual workflow </background_information>

If --auto flag is present in $ARGUMENTS, you are in AUTOMATIC MODE.

In Automatic Mode:

  • Execute ALL 4 phases in a continuous loop without stopping
  • Use TodoWrite to track progress (4 tasks: init, requirements, design, tasks)
  • Each phase completion updates TodoWrite and continues immediately
  • IGNORE any "Next Step" messages from Phase 2-4 (they are for standalone usage)
  • Stop ONLY after Phase 4 completes or if error occurs

Progress tracking with TodoWrite:

  • Phase 1 complete = 1/4 tasks done → Continue to Phase 2
  • Phase 2 complete = 2/4 tasks done → Continue to Phase 3
  • Phase 3 complete = 3/4 tasks done → Continue to Phase 4
  • Phase 4 complete = 4/4 tasks done → Output summary and exit

Core Task

Execute 4 spec phases sequentially. In automatic mode, execute all phases without stopping. In interactive mode, prompt user for approval between phases.

Execution Steps

Step 1: Parse Arguments and Initialize

Parse $ARGUMENTS:

  • If contains --auto: Automatic Mode (execute all 4 phases)
  • Otherwise: Interactive Mode (prompt at each phase)
  • Extract description (remove --auto flag if present)

Example:

"User profile with avatar upload --auto" → mode=automatic, description="User profile with avatar upload"
"User profile feature" → mode=interactive, description="User profile feature"

Create TodoWrite task list:

[
  {"content": "Initialize spec", "activeForm": "Initializing spec", "status": "pending"},
  {"content": "Generate requirements", "activeForm": "Generating requirements", "status": "pending"},
  {"content": "Generate design", "activeForm": "Generating design", "status": "pending"},
  {"content": "Generate tasks", "activeForm": "Generating tasks", "status": "pending"}
]

Read the full file on GitHub · 359 lines

Changes

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.

  1. 6d ago First seen · 359 lines · 8 tokens per session scan A 291526be836d

Subscribe to this mod's changes

kiro-spec-quick is a command published in the GitHub repository gotalab/cc-sdd (3,652 stars, last pushed 3mo ago), licensed MIT. It adds 8 tokens to every session and 2,589 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to spec-quick, differing in 26 lines, and is treated as a copy.

Related

Other commands, from other repositories

implementation-plan

Define an incremental, reviewable, production-safe implementation plan for the active task and persist it as IMPLEMENTATIONPLAN.md plus a TASKSTATE.md update. Breaks work into the smallest safe slices with objective, exact scope, ordering rationale, key risks, validation approach, exit criteria, and work complexity…

Mozurok/fhorja.dev · 207 tokens

slice-closure

Decide whether the current slice is ready to close, distinguishing slice completion from full task completion, then persist the result in slice notes and TASKSTATE.md as explicit reviewable closure notes. For single-slice tasks may route directly to delivery. Returns no-op when slice memory would not materially…

Mozurok/fhorja.dev · 146 tokens

task-close

Perform the terminal task lifecycle transition for a finished task: verify the spec done-conditions, set TASKSTATE.md to its final closed state, and move the task folder from active/ to archive/. The symmetric counterpart to task-init and the only official way to close a whole task. Use when every slice is closed, the…

Mozurok/fhorja.dev · 177 tokens

task-init

Initialize the official task folder and base task memory inside projects/ /active/YYYY-MM-DD /. Creates README.md, TASKSTATE.md, SOURCEOFTRUTH.md, DECISIONS.md, IMPLEMENTATIONPLAN.md; seeds from PROJECTCHARTER.md when present; emits a multi-repo.

Mozurok/fhorja.dev · 70 tokens

decision-interview

Ask the minimum set of high-value decision questions needed before turning the task into canonical implementation rules. Decisions that would change runtime behavior, data integrity, rollout safety, or test strategy. Use when the missing information is decision-driven (not factual), different answers would change…

Mozurok/fhorja.dev · 146 tokens

godot-scene-plan

Plan the Godot scene and node structure for a 2D or 3D game feature before any GDScript is written: the scene tree, node types and responsibilities, autoloads (singletons), signal wiring, the input map, and the resources and sub-scenes to create. Produces GODOTSCENEPLAN.md, a design-time plan an MCP-driven editor or a…

Mozurok/fhorja.dev · 226 tokens