kiro-spec-initlisted

# Spec Initialization <instructions> ## Core Task Generate a unique feature name from the project description ($ARGUMENTS) and initialize the specification structure. ## Execution Steps 1. **Check for Brief**: If `.kiro/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/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/specs/[feature-name]/` (skip if already exists from discovery) 5. **Initialize Files Using Templates**: - Read `.kiro/settings/templates/specs/init.json` - Read `.kiro/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 $ARGU