kiro-spec-quick

kiro-spec-quick is a skill for Claude Code from gotalab/cc-sdd. It costs 14 tokens per session (1,957 once invoked), scanned A, original, MIT.

A quick specification generator that turns a software idea into requirements, design, and implementation tasks through four phases. It can run automatically with the --auto option or pause for approval between phases.

In plain words
What is it for?
Use it to create a structured specification for a feature such as a user profile, including its requirements, technical design, and work breakdown.
Why use it?
It gives a coding project a checked plan before implementation, reducing unclear requirements and disconnected design or task lists.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions subagents.

Good fit Use it to create a structured specification for a feature such as a user profile, including its requirements, technical design, and work breakdown.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gotalab/cc-sdd/kiro-spec-quick
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,745 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.

Any agent
npx skills add gotalab/cc-sdd --skill kiro-spec-quick
Clone the repo
git clone --depth 1 https://github.com/gotalab/cc-sdd

Made for: Claude Code.

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/skills/gotalab/cc-sdd/kiro-spec-quick/github.svg)](https://agentmods.dev/skills/gotalab/cc-sdd/kiro-spec-quick)
Your own site
<a href="https://agentmods.dev/skills/gotalab/cc-sdd/kiro-spec-quick"><img src="https://agentmods.dev/badge/skills/gotalab/cc-sdd/kiro-spec-quick/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.

agentmods 80×15 button for kiro-spec-quick

Your own site · 80×15
<a href="https://agentmods.dev/skills/gotalab/cc-sdd/kiro-spec-quick"><img src="https://agentmods.dev/badge/skills/gotalab/cc-sdd/kiro-spec-quick.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,957 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 121
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
  • medium Excessive Agency · line 137
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
How audits are shown
Origin original No closer match found 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.00014 $0.01957
Opus 5.5 $0.00006 $0.00783
Sonnet 5.5 $0.00003 $0.00391
Haiku 4.5 $0.00001 $0.00196

Measured 1mo ago against content hash 0371b2f514d2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

tools/cc-sdd/templates/agents/antigravity-skills/skills/kiro-spec-quick/SKILL.md · 257 lines

How it starts

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

Quick Spec Generator

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
  • Display progress after each phase (e.g., "Phase 1/4 complete: spec initialized")
  • IGNORE any "Next Step" messages from Phase 2-4 (they are for standalone usage)
  • After Phase 4, run the final sanity review before exiting
  • Stop ONLY after the sanity review completes or if error occurs

Core Task

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

Before claiming quick generation is complete, run one lightweight sanity review over the generated requirements, design, and tasks. If the host supports fresh sub-agents, use one. Otherwise run the sanity review inline.

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"

Display mode banner and proceed to Step 2.

Step 2: Execute Phase Loop

Execute these 4 phases in order:


Phase 1: Initialize Spec (Direct Implementation)

Core Logic:

  1. Check for Brief:

    • If {{KIRO_DIR}}/specs/{feature-name}/brief.md exists (created by /kiro-discovery), read it for discovery context (problem, approach, scope, constraints)
    • Use brief content as the project description instead of $ARGUMENTS
  2. Generate Feature Name:

    • Convert description to kebab-case
    • Example: "User profile with avatar upload" → "user-profile-avatar-upload"
    • Keep name concise (2-4 words ideally)

Read the full file on GitHub · 257 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. 1mo ago First seen · 257 lines · 14 tokens per session scan A 0371b2f514d2

Subscribe to this mod's changes

kiro-spec-quick is a skill published in the GitHub repository gotalab/cc-sdd (3,745 stars, last pushed 6d ago), licensed MIT. It adds 14 tokens to every session and 1,957 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.

Related

Other skills, from other repositories

todo-for-ai-agent-runtime

Runtime integration skill for external agents connecting to Todo for AI over HTTP API Token / Agent Key, including auth, task lease, events, commit, and task logs.

todo-for-ai/todo-for-ai · 39 tokens

decision-interview

Ask the minimum decision questions needed before turning the task into canonical implementation rules, on behavior, data integrity, rollout safety, or test strategy. Use when missing information is decision-driven (not factual) or undecided policy blocks planning; in an attended chain it records an open decision as…

Mozurok/fhorja.dev · 108 tokens

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…

Mozurok/fhorja.dev · 97 tokens

repo-consistency-sweep

Defect-class detection for the lower-value half of code review: convention drift, type-safety gaps, security and multi-tenant invariants, operability issues. Runs after review-hard. Checks against a curated bug-class library that grows via pr-feedback-ingest. Use when at least one slice is implemented and you want a…

Mozurok/fhorja.dev · 96 tokens

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…

Mozurok/fhorja.dev · 84 tokens

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…

Mozurok/fhorja.dev · 110 tokens