kiro-spec-init

1# Spec Initialization
2 
3<instructions>
4## Core Task
5Generate a unique feature name from the project description ($ARGUMENTS) and initialize the specification structure.
6 
7## Execution Steps
81. **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.
92. **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.
103. **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).
114. **Create Directory**: `{{KIRO_DIR}}/specs/[feature-name]/` (skip if already exists from discovery)
125. **Initialize Files Using Templates**:
13   - Read `{{KIRO_DIR}}/settings/templates/specs/init.json`
14   - Read `{{KIRO_DIR}}/settings/templates/specs/requirements-init.md`
15   - Replace placeholders:
16     - `{{FEATURE_NAME}}` → generated feature name
17     - `{{TIMESTAMP}}` → current ISO 8601 timestamp
18…