kiro-spec-status

1# Specification Status
2 
3<background_information>
4- **Success Criteria**:
5  - Show current phase and completion status
6  - Identify next actions and blockers
7  - Provide clear visibility into progress
8  - Surface boundary readiness, upstream/downstream context, and likely revalidation needs when available
9</background_information>
10 
11<instructions>
12## Execution Steps
13 
14### Step 1: Load Spec Context
15- Read `{{KIRO_DIR}}/specs/$1/spec.json` for metadata and phase status
16- Read `{{KIRO_DIR}}/specs/$1/brief.md` if it exists
17- Read existing files: `requirements.md`, `design.md`, `tasks.md` (if they exist)
18- Check `{{KIRO_DIR}}/specs/$1/` directory for available files
19- Read `{{KIRO_DIR}}/steering/roadmap.md` if it exists and this spec appears in it
20 
21### Step 2: Analyze Status
22 
23**Parse each phase**:
24- **Requirements**: Count requirements and acceptance criteria
25- **Design**: Check for architecture, components, diagrams, and whether boundary sections are present
26- **Tasks**: Count completed vs total tasks (parse `- [x]` vs `- [ ]`)
27- **Approvals**: Check approval status in spec.json
28- **Boundary context**:
29  - From brief.md: note `Boundary Candidates`, `Upstream / Downstream`, and `Existing Spec Touchpoints` if present
30  - From design.md: note `Boundary Commitments`, `Out of Boundary`, `Allowed Dependencies`, and `Revalidation Triggers` if present
31  - From roadmap.md: note upstream dependencies and whether this spec is adjacent to `Existing Spec Updates`
32- **Revalidation watchlist**:
33…