OpenParable
Skip to content
← Back to skills

Kiro Spec Init

Development
kiro-spec-init

Kiro Spec Init is an Agent Skill for development published in the gotalab/cc-sdd repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Initialize a new specification with detailed project description

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/gotalab/cc-sdd/blob/HEAD/tools/cc-sdd/templates/agents/antigravity-skills/skills/kiro-spec-init/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/kiro-spec-init, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Spec Initialization

Execution Steps

  1. Check for Brief: If {{KIRO_DIR}}/specs/{feature-name}/brief.md exists (created by /kiro-discovery), read it. The brief contains problem, approach, scope, and constraints from the discovery session. Use this to pre-fill the project description and skip clarification questions that the brief already answers.
  2. Clarify Intent: The Project Description in requirements.md must contain three elements: (a) who has the problem, (b) current situation, (c) what should change. If a brief.md exists and covers these, skip to step 3. Otherwise, ask the user to clarify before proceeding. Ask as many questions as needed; do not fill in gaps with your own assumptions.
  3. Check Uniqueness: Verify {{KIRO_DIR}}/specs/ for naming conflicts. If the directory already exists with only brief.md (no spec.json), use that directory (discovery created it).
  4. Create Directory: {{KIRO_DIR}}/specs/[feature-name]/ (skip if already exists from discovery)
  5. Initialize Files Using Templates:
    • Read {{KIRO_DIR}}/settings/templates/specs/init.json
    • Read {{KIRO_DIR}}/settings/templates/specs/requirements-init.md
    • Replace placeholders:
      • {{FEATURE_NAME}} → generated feature name
      • {{TIMESTAMP}} → current ISO 8601 timestamp
      • {{PROJECT_DESCRIPTION}} → from brief.md if available, otherwise $ARGUMENTS
      • {{LANG_CODE}} → language code (detect from user's input language, default to en)
    • Write spec.json and requirements.md to spec directory

Important Constraints

  • Do NOT generate requirements, design, or tasks. This skill only creates spec.json and requirements.md.

Output Description

Provide output in the language specified in spec.json with the following structure:

  1. Generated Feature Name: feature-name format with 1-2 sentence rationale
  2. Project Summary: Brief summary (1 sentence)
  3. Created Files: Bullet list with full paths
  4. Next Step: Command block showing /kiro-spec-requirements <feature-name>

Format Requirements:

  • Use Markdown headings (##, ###)
  • Wrap commands in code blocks
  • Keep total output concise (under 250 words)
  • Use clear, professional language per spec.json.language

Safety & Fallback

  • Ambiguous Feature Name: If feature name generation is unclear, propose 2-3 options and ask user to select
  • Template Missing: If template files don't exist in {{KIRO_DIR}}/settings/templates/specs/, report error with specific missing file path and suggest checking repository setup
  • Directory Conflict: If feature name already exists, append numeric suffix (e.g., feature-name-2) and notify user of automatic conflict resolution
  • Write Failure: Report error with specific path and suggest checking permissions or disk space