kiro-spec-statuslisted

# 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/specs/$ARGUMENTS/spec.json` for metadata and phase status - Read `.kiro/specs/$ARGUMENTS/brief.md` if it exists - Read existing files: `requirements.md`, `design.md`, `tasks.md` (if they exist) - Check `.kiro/specs/$ARGUMENTS/` directory for available files - Read `.kiro/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, 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` - **Revalidation watchlist**: - Identify downstream specs, neighboring existing-sp