kiro-spec-status

Parse spec files and roadmap to report phase, completion, and blockers.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/manatago/gion --skill kiro-spec-status-manatago
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-spec-status
Source: https://github.com/manatago/gion/tree/main/.claude/skills/kiro-spec-status
Command: npx skills add https://github.com/manatago/gion --skill kiro-spec-status-manatago

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many specs live in repository directories and stakeholders lack a concise, up-to-date view of a spec's phase, completion percentage, boundary context, and outstanding blockers; this Skill automates collecting that information and surfacing clear next actions and revalidation needs.

Core Features & Use Cases

  • Automated status aggregation: Reads .kiro/specs/<feature>/spec.json and associated Markdown files to determine current phase, approvals, and metadata.
  • Progress & task analysis: Counts requirements and acceptance criteria, parses task checklists (- [x] vs - [ ]) to compute completion percentages and remaining work.
  • Boundary and context insights: Extracts Boundary Candidates, Upstream/Downstream notes, design boundary commitments, and roadmap touchpoints to produce a revalidation watchlist.
  • Scannable reports: Produces language-specific, emoji-enhanced summaries showing current phase, per-phase completion, task breakdown, blockers, next actions, and likely impacted specs.
  • Use case: Product managers or engineering leads preparing a spec review can generate a one-page actionable report to drive planning meetings.

Quick Start

Run kiro-spec-status for feature-name to generate a scannable progress report with next actions and blockers.

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 completion status of a feature spec in my repository?

To check feature spec status, parse the .kiro/specs directory to aggregate spec.json metadata and markdown files. This process counts task checklists and acceptance criteria, outputting a scannable report with phase percentages and remaining work for the named feature.

What is the best way to track requirements progress and identify spec blockers?

Tracking requirements progress involves parsing markdown task checklists and extracting boundary candidates from design files. The system calculates completion percentages, flags outstanding blockers, and generates a revalidation watchlist based on roadmap touchpoints and upstream notes.

How do I generate a spec review report for a planning meeting?

Generate a spec review report by analyzing spec.json, brief.md, requirements.md, design.md, and tasks.md files. The tool outputs a language-specific summary showing current phase, per-phase completion, task breakdown, and next actions to drive planning meetings.

Does spec status tracking work without a formal roadmap file?

Spec status tracking works without a roadmap file by relying on the core spec files within the .kiro/specs directory. It parses available JSON and markdown files to compute phase state, although roadmap touchpoints and boundary context are enriched when roadmap.md is present.

How are revalidation needs detected for software specifications?

Revalidation needs are detected by extracting boundary candidates, upstream and downstream notes, and design boundary commitments from spec files. The system consults the roadmap to produce a dedicated revalidation watchlist highlighting likely impacted specs.