Skip to content
Development
Command

/kiro-spec-quick

Quick spec generation with interactive or automatic mode

From plugin
cc-sdd
3.6k35 skills14 agents35 commands
Install
$ npx -y skills add gotalab/cc-sdd --agent claude-code

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/kiro-spec-quick

Context preview

What this command does when you run it.

Quick spec generation with interactive or automatic mode

Command definition

kiro-spec-quick.md
description: Quick spec generation with interactive or automatic mode

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>

<instructions>

⚠️ CRITICAL: Automatic Mode Execution Rules

**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"}
]

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)

**Update TodoWrite**: Mark task 1 as `in_progress`.

**Core Logic**:

1. **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)

2. **Check Uniqueness**:

  • Use Glob to check `{{KIRO_DIR}}/specs/*/`
  • If feature name exists, append `-2`, `-3`, etc.

3. **Create Directory**:

  • Use Bash: `mkdir -p {{KIRO_DIR}}/specs/{feature-name}`

4. **Initialize Files from Templates**:

a. Read templates:

   - {{KIRO_DIR}}/settings/templates/specs/init.json
   - {{KIRO_DIR}}/settings/templates/specs/requirements-init.md

b. Replace placeholders:

   {{FEATURE_NAME}} → feature-name
   {{TIMESTAMP}} → current ISO 8601 timestamp (use `date -u +"%Y-%m-%dT%H:%M:%SZ"`)
   {{PROJECT_DESCRIPTION}} → description

c. Write files using Write tool:

   - {{KIRO_DIR}}/specs/{feature-name}/spec.json
   - {{KIRO_DIR}}/specs/{feature-name}/requirements.md

5. **Update TodoWrite**: Mark task 1 as `completed`, task 2 as `in_progress`.

6. **Output Progress**:

   ✅ Spec initialized at {{KIRO_DIR}}/specs/{feature-name}/

**Automatic Mode**: IMMEDIATELY continue to Phase 2.

**Interactive Mode**: Prompt "Continue to requirements generation? (yes/no)"

  • If "no": Stop, show current state
  • If "yes": Continue to Phase 2

---

Phase 2: Generate Requirements

**Task 2 is already `in_progress` from Phase 1.**

**Execute SlashCommand**:

/kiro-spec-requirements {feature-name}

Wait for completion. Subagent will return with "次のステップ" message.

**IMPORTANT**: In Automatic Mode, IGNORE the "次のステップ" message. It is for standalone usage.

**Update TodoWrite**: Mark task 2 as `completed`, task 3 as `in_progress`.

**Output Progress**:

✅ Requirements generated → Continuing to design...

**Automatic Mode**: Task list shows 2/4 complete. IMMEDIATELY continue to Phase 3.

**Interactive Mode**: Prompt "Continue to design generation? (yes/no)"

  • If "no": Stop, show current state
  • If "yes": Continue to Phase 3

---

Phase 3: Generate Design

**Task 3 is already `in_progress` from Phase 2.**

**Execute SlashCommand**:

/kiro-spec-design {feature-name} -y

Note: `-y` flag auto-approves requirements.

Wait for completion. Subagent will return with "次のステップ" message.

**IMPORTANT**: In Automatic Mode, IGNORE the "次のステップ" message.

**Update TodoWrite**: Mark task 3 as `completed`, task 4 as `in_progress`.

**Output Progress**:

✅ Design generated → Continuing to tasks...

**Automatic Mode**: Task list shows 3/4 complete. IMMEDIATELY continue to Phase 4.

**Interactive Mode**: Prompt "Continue to tasks generation? (yes/no)"

  • If "no": Stop, show current state
  • If "yes": Continue to Phase 4

---

Phase 4: Generate Tasks

**Task 4 is already `in_progress` from Phase 3.**

**Execute SlashCommand**:

/kiro-spec-tasks {feature-name} -y

Note: `-y` flag auto-approves design.

Wait for completion.

**Update TodoWrite**: Mark task 4 as `completed`.

**All 4 tasks complete. Loop is DONE.**

Output final completion summary (see Output Description section) and exit.

---

Important Constraints

Phase 1 Implementation Notes

  • Feature name generation should be deterministic and readable
  • Always check for conflicts before creating directory
  • Validate templates exist before reading
  • Use ISO 8601 format for timestamp: `YYYY-MM-DDT
Read more
Ships withcc-sdd

Package README: English | 日本語 | 繁體中文

Get the whole plugin