Download tools/cc-sdd/templates/agents/antigravity-skills/skills/kiro-spec-quick/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does kiro-spec-quick live?
The publisher keeps it at https://github.com/gotalab/cc-sdd.
Which agents can use kiro-spec-quick?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.
Quick spec generation with interactive or automatic mode
name: kiro-spec-quick
description: Quick spec generation with interactive or automatic mode
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)
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
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)
Check Uniqueness:
Use Glob to check {{KIRO_DIR}}/specs/*/
If directory exists with only brief.md (no spec.json), use that directory (discovery created it)
Otherwise if feature name exists, append -2, -3, etc.
Create Directory:
Use Bash: mkdir -p {{KIRO_DIR}}/specs/{feature-name} (skip if already exists from discovery)
After Phase 4, run a lightweight sanity review before claiming completion.
Review requirements.md, design.md, and tasks.md directly from disk. If brief.md exists, use it only as supporting context.
Prefer a fresh review sub-agent when the host supports it. Pass only file paths and the review objective; the reviewer should read the generated files itself.
Review focus:
Do requirements, design, and tasks tell a coherent story?
Are there obvious contradictions, missing prerequisites, or missing task coverage for required design work?
Are _Depends:_, _Boundary:_, and (P) markers plausible for implementation?
If the review finds only task-plan-local issues, repair or update the generated tasks.md once, then re-run the sanity review.
If the review finds a real requirements/design gap or contradiction, stop and report follow-up instead of claiming the quick spec is implementation-ready.
All 4 phases plus sanity review complete.
Output final completion summary (see Output Description section) and exit.
Important Constraints
Error Handling
Any phase failure stops the workflow
Display error and current state
Suggest manual recovery command
Output Description
Mode Banners
Interactive Mode:
Quick Spec Generation (Interactive Mode)
You will be prompted at each phase.
Note: Skips gap analysis and design validation.
Automatic Mode:
Quick Spec Generation (Automatic Mode)
All phases execute automatically without prompts.
Note: Skips optional validations (gap analysis, design review) and user approval prompts. Internal review gates still run.
Final sanity review still runs.
Intermediate Output
After each phase, show brief progress:
Spec initialized at {{KIRO_DIR}}/specs/{feature}/
Requirements generated → Continuing to design...
Design generated → Continuing to tasks...
Final Completion Summary
Provide output in the language specified in spec.json:
Suggest: "Continue manually from /kiro-spec-{next-phase} {feature}"
Sanity Review Failed:
Stop workflow
Report the exact contradiction, missing prerequisite, or task-plan issue
Suggest targeted follow-up with /kiro-spec-design {feature}, /kiro-spec-tasks {feature}, or manual edits depending on the finding
User Cancellation (Interactive Mode):
Stop gracefully
Show completed phases
Suggest manual continuation
How do I install kiro-spec-quick?
Download tools/cc-sdd/templates/agents/antigravity-skills/skills/kiro-spec-quick/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does kiro-spec-quick live?
The publisher keeps it at https://github.com/gotalab/cc-sdd.
Which agents can use kiro-spec-quick?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.