skills.rest
taku-o
taku-oCOMMUNITY
Explore all skills by this author →
Website𝕏@taku_oGitHub

kiro-spec-status

Summarizes Kiato spec phases, completion counts, approvals, blockers, and next actions from .kairo/specs data.

1|Updated Apr 15, 2026
Search Tags:#roadmap#spec#tasks#status#kiro#boundary#revalidation
One-click install
npx skills add https://github.com/taku-o/gitignore-merge --skill kiro-spec-status-taku-o
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kiro-spec-status
Source: https://github.com/taku-o/gitignore-merge/tree/main/.claude/skills/kiro-spec-status
Command: npx skills add https://github.com/taku-o/gitignore-merge --skill kiro-spec-status-taku-o

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides clear, scannable visibility into the current phase, completion progress, and blockers for a specification so stakeholders can quickly understand readiness, next steps, and revalidation needs.

Core Features & Use Cases

  • Context Loading: Reads spec metadata and supporting documents from the .kiro/specs directory to assemble a complete view of a feature spec.
  • Phase & Progress Analysis: Counts requirements and acceptance criteria, evaluates design and boundary sections, tallies completed versus remaining tasks, and checks approval status.
  • Boundary & Revalidation Watchlist: Surfaces upstream/downstream dependencies, boundary commitments, and nearby work that may require revalidation if the spec changes.
  • Use Cases: Prepare concise reports for steering meetings, identify blockers before design reviews, and track readiness during roadmap planning.

Quick Start

Run the skill with the feature name to produce a language-specific status report for that spec.

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 and completion progress of a Kiro specification?▼

To check Kiro specification status, read the spec.json, brief.md, design.md, and tasks.md files under .kiro/specs to count requirements, tally completed tasks, and identify blockers for a scannable readiness report.

What is the best way to track task completion and roadmap progress from markdown specs?▼

Tracking task completion from markdown specs involves parsing tasks.md entries and roadmap metadata to tally completed versus remaining items, evaluating design sections, and outputting a scannable progress summary with next actions.

Can I identify boundary dependencies and revalidation needs from a feature spec?▼

Yes, you can identify boundary dependencies and revalidation needs by parsing boundary context in design.md and roadmap entries to surface upstream and downstream commitments that may require revalidation if the spec changes.

How do I prepare a concise spec status report for steering meetings or design reviews?▼

Preparing a concise spec status report involves assembling spec metadata, counting acceptance criteria, checking approval status, and summarizing phases and blockers into a language-specific scannable output for stakeholders.

Does the spec status summary require any external dependencies or components?▼

No, the spec status summary requires no external dependencies or components, relying solely on parsing the JSON metadata and markdown content already stored within the .kiro/specs directory structure.

Related Skills

Explore More Product & Management Skills→
notta50notta50

kiro-spec-status

Parse spec metadata and markdown task lists to report phase progress.

Community
Intermediate
manatagomanatago

kiro-spec-status

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

Community
Intermediate
BarryYinBarryYin

kiro-spec-status

Parse .kiro/specs files to compute phase completion and identify blockers.

Community
Intermediate
ryu-satoryu-sato

kiro-spec-status

Load .kiro/specs/$ARGUMENTS/spec.json and related files to generate a structured spec status report.

Community
Intermediate