kiro-spec-status

To check spec progress, aggregate spec.json, brief.md, requirements.md, design.md, and tasks.md from your .kiro/specs directory to compute phase completion percentages and task counts. This generates a scannable report showing current phase, open tasks, and next actions.

Spec revalidation tracking identifies boundary candidates and upstream/downstream context from brief.md, design.md, and roadmap entries to surface blockers. You need it when managing dependencies across multiple specs to ensure changes in one specification do not break another.

Count completed versus open tasks by parsing markdown task lists within tasks.md files. The analysis reads checkbox syntax to tally finished items, compares them against total tasks, and surfaces the approval status stored in spec.json.

Yes, you can list available specs when none or a wildcard is provided. The discovery feature scans the .kiro/specs directory, reports any missing files for existing specs, and suggests next-phase actions for each found specification.

Yes, spec status reports support multiple languages. The output report is generated in the language declared within the spec.json file, ensuring the multi-part progress analysis matches the language configured for that specific specification.

If requirements.md or design.md is missing, the analysis handles the error by reporting the missing files explicitly. It still aggregates available files to compute partial completion percentages and suggests next-phase actions to fill the gaps.