kiro-spec-status

To check spec status, the skill reads spec.json, brief.md, requirements.md, design.md, tasks.md, and roadmap.md from the .kiro/specs directory to compute phase completion and surface blockers. It generates a concise report showing current progress and actionable next steps.

Identifying spec blockers involves parsing each phase like Requirements, Design, Tasks, and Approvals to compute completion and highlight boundaries. The skill surfaces upstream and downstream touchpoints alongside a revalidation watchlist to guide planning and decision making.

Computing spec phase completion works by reading requirements.md, design.md, and tasks.md alongside spec.json to evaluate each phase individually. It calculates readiness for Requirements, Design, Tasks, and Approvals phases to produce a status report with boundary context and next actions.

Yes, you can track roadmap progress by reading the roadmap.md file within your spec directory structure. The skill computes phase completion and generates a revalidation watchlist to provide status discovery without needing external project management integrations.

Spec revalidation is needed when boundaries shift or upstream and downstream touchpoints change during development. The skill generates a revalidation watchlist by analyzing spec.json and related files to surface exactly when and where revalidation should occur.

Your spec status report may show incomplete phases because the skill evaluates Requirements, Design, Tasks, and Approvals separately by reading brief.md, design.md, and requirements.md. Completing tasks.md alone does not fulfill the other phase requirements needed for full completion.