11 added, 3 removed. Audit A to A.
---
name: kiro-spec-status
description: Show specification status and progress
allowed-tools: Read, Glob, Grep
argument-hint: <feature-name>
---
# kiro-spec-status Skill
## Core Mission
- **Success Criteria**:
- Show current phase and completion status
- Identify next actions and blockers
- Provide clear visibility into progress
+ - Surface boundary readiness, upstream/downstream context, and likely revalidation needs when available
## Execution Steps
### Step 1: Load Spec Context
- Read `{{KIRO_DIR}}/specs/$ARGUMENTS/spec.json` for metadata and phase status
+ - Read `{{KIRO_DIR}}/specs/$ARGUMENTS/brief.md` if it exists
- Read existing files: `requirements.md`, `design.md`, `tasks.md` (if they exist)
- Check `{{KIRO_DIR}}/specs/$ARGUMENTS/` directory for available files
+ - Read `{{KIRO_DIR}}/steering/roadmap.md` if it exists and this spec appears in it
### Step 2: Analyze Status
**Parse each phase**:
- **Requirements**: Count requirements and acceptance criteria
- - **Design**: Check for architecture, components, diagrams
+ - **Design**: Check for architecture, components, diagrams, and whether boundary sections are present
- **Tasks**: Count completed vs total tasks (parse `- [x]` vs `- [ ]`)
- **Approvals**: Check approval status in spec.json
+ - **Boundary context**:
+ - From brief.md: note `Boundary Candidates`, `Upstream / Downstream`, and `Existing Spec Touchpoints` if present
+ - From design.md: note `Boundary Commitments`, `Out of Boundary`, `Allowed Dependencies`, and `Revalidation Triggers` if present
+ - From roadmap.md: note upstream dependencies and whether this spec is adjacent to `Existing Spec Updates`
### Step 3: Generate Report
Create report in the language specified in spec.json covering:
1. **Current Phase & Progress**: Where the spec is in the workflow
2. **Completion Status**: Percentage complete for each phase
3. **Task Breakdown**: If tasks exist, show completed/remaining counts
- 4. **Next Actions**: What needs to be done next
- 5. **Blockers**: Any issues preventing progress
+ 4. **Boundary Context**: Upstream/downstream, out-of-boundary, and revalidation notes when available
+ 5. **Next Actions**: What needs to be done next
+ 6. **Blockers**: Any issues preventing progress
**Format**: Clear, scannable format with emojis for status
## Safety & Fallback
### Error Scenarios
**Spec Not Found**:
- **Message**: "No spec found for `$ARGUMENTS`. Check available specs in `{{KIRO_DIR}}/specs/`"
- **Action**: List available spec directories
**Incomplete Spec**:
- **Warning**: Identify which files are missing
- **Suggested Action**: Point to next phase command
### List All Specs
To see all available specs:
- Run with no argument or use wildcard
- Shows all specs in `{{KIRO_DIR}}/specs/` with their status