kiro-spec-status

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides clear visibility into the status and progress of a specification stored in a project's .kiro/specs directory, helping teams understand what is done, what remains, and what blocks delivery.

Core Features & Use Cases

  • Phase Analysis: Detects current phase and computes completion percentages for requirements, design, and tasks by parsing spec.json and related files.
  • Task & Approval Insights: Counts completed vs. remaining tasks, surfaces approvals and blockers, and identifies missing or incomplete files.
  • Boundary & Revalidation Context: Summarizes upstream/downstream dependencies, boundary commitments, and a revalidation watchlist to flag adjacent specs or rollout-sensitive areas.
  • Use Case: Product managers and engineers can run this on a feature spec to quickly get a one-page status report that guides next actions and identifies who to coordinate with.

Quick Start

Show the status for the spec named feishu-summary.

Frequently Asked Questions about kiro-spec-status

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

FAQPage Schema
How do I track spec progress and identify blockers in a .kiro/specs folder?

To track spec progress, parse spec.json, brief.md, requirements.md, design.md, and tasks.md to compute phase completion percentages, count remaining tasks, and surface approval blockers for a named spec.

What is the best way to visualize specification status and next actions for a feature?

Visualizing specification status involves parsing roadmap.md and related spec files to generate a one-page status report, summarizing boundary commitments, upstream dependencies, and a revalidation watchlist.

How do I check if requirements, design, and tasks phases are complete for a spec?

Checking phase completion requires parsing spec.json and associated markdown files to compute completion percentages for requirements, design, and tasks, while identifying any missing or incomplete files.

Does this spec status tool work with roadmap.md to find revalidation watchlist items?

Yes, the tool parses roadmap.md when present to summarize boundary context, downstream dependencies, and generate a revalidation watchlist flagging adjacent specs and rollout-sensitive areas.

Can product managers get task counts and approval insights from markdown spec files?

Product managers can parse tasks.md and spec.json to count completed versus remaining tasks, surface pending approvals, and identify blockers guiding next coordination actions.

Why are missing spec files causing incomplete phase analysis for my requirements?

Missing files like brief.md or design.md prevent the parser from computing accurate phase completion percentages, resulting in incomplete boundary context and an invalid revalidation watchlist.