kiro-spec-status

Reports specification phase progress, task completion, and blockers from Kiro spec files.

Updated Jun 23, 2026
One-click install
npx skills add https://github.com/j5ik2o/marp-ai-base --skill kiro-spec-status-j5ik2o
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kiro-spec-status
Source: https://github.com/j5ik2o/marp-ai-base/tree/main/.agents/skills/kiro-spec-status
Command: npx skills add https://github.com/j5ik2o/marp-ai-base --skill kiro-spec-status-j5ik2o

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams working with Kiro spec-driven development lose visibility into where each specification stands across requirements, design, and task phases, making it hard to spot blockers and next actions. ## Core Features & Use Cases - Phase Progress Tracking: Parses spec.json, requirements.md, design.md, and tasks.md to compute completion percentages per phase. - Task Breakdown: Counts completed versus pending checklist items and surfaces approval status. - Boundary & Revalidation Context: Highlights upstream/downstream dependencies and specs likely needing revalidation when changes occur. - Use Case: A developer returns to a project after a week and asks for the status of the 'user-auth' spec to see which tasks remain, what phase it is in, and what is blocking approval. ## Quick Start Ask the assistant to show the specification status and progress for a given spec name, or list all specs to see every spec's current phase.

Frequently Asked Questions about kiro-spec-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check the status of a Kiro specification?▼

Invoke the skill with the spec name to read its spec.json and phase files under .kiro/specs. It reports the current phase, completion percentages, task counts, and blockers. Running it without an argument lists all specs with their status.

How is spec task progress calculated?▼

Task progress is computed by parsing tasks.md and counting completed items marked with '- [x]' against total items marked with '- [ ]'. The report shows completed versus remaining counts along with per-phase completion percentages.

What files does a Kiro spec need for status reporting?▼

The skill reads spec.json for metadata and approvals, plus requirements.md, design.md, and tasks.md if they exist. Missing files are flagged as warnings with a pointer to the next phase command rather than causing failure.

What happens if the spec name does not exist?▼

The skill returns a message stating no spec was found for the given name and lists the available spec directories under .kiro/specs so you can pick a valid one.

Can the status report show dependencies between specs?▼

Yes, it surfaces boundary context from brief.md and design.md, including upstream and downstream relationships, and builds a revalidation watchlist of neighboring specs likely affected by changes to the current spec.