kiro-spec-status

Parse Kiro spec files to compute phase progress and task counts.

3.6k|274|Updated Jul 17, 2025
One-click install
npx skills add https://github.com/gotalab/cc-sdd --skill kiro-spec-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-spec-status
Source: https://github.com/gotalab/cc-sdd/tree/main/tools/cc-sdd/templates/agents/claude-code-skills/skills/kiro-spec-status
Command: npx skills add https://github.com/gotalab/cc-sdd --skill kiro-spec-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of manually checking multiple spec files to determine current phase, completion progress, and what to do next by aggregating spec metadata, documents, tasks, and roadmap context into a clear status report.

Core Features & Use Cases

  • Context Loading: Reads spec.json and optional brief.md, requirements.md, design.md, tasks.md, and steering/roadmap.md from the Kiro specs directory to assemble the spec context.
  • Phase & Task Analysis: Counts requirements and acceptance criteria, inspects design boundary commitments, and computes completed versus remaining tasks by parsing markdown task checkboxes.
  • Risk & Revalidation Detection: Identifies upstream/downstream dependencies, neighboring spec impacts, and items that may require revalidation or splitting.
  • Report Generation & Fallbacks: Produces a language-specific, scannable report with current phase, completion percentages, task breakdown, boundary notes, revalidation watchlist, next actions, and blockers; handles missing specs and incomplete files with explicit guidance.

Quick Start

Run the kiro-spec-status skill with the target spec name to get a concise status report showing phase, progress, blockers, and recommended next actions.

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

To check Kiro specification status, the skill parses spec.json, requirements.md, design.md, and tasks.md files to aggregate phase progress, completed task counts, and next actions into a scannable report. It summarizes current phase, completion percentages, boundary notes, and blockers.

What is the best way to track requirements and task completion for a spec directory?

Tracking requirements and task completion is done by parsing markdown task checkboxes and counting acceptance criteria across spec documents. This computes completed versus remaining tasks, boundary readiness, and revalidation watchlists to determine overall spec progress.

How do I identify blockers and revalidation items in my spec documents?

Identifying blockers and revalidation items involves inspecting design boundary commitments and analyzing upstream/downstream dependencies within steering/roadmap.md. This detects neighboring spec impacts and highlights items that may require revalidation or splitting.

Can I generate a status report if some spec files like brief.md or design.md are missing?

You can generate a status report with missing files because the skill handles incomplete specs using explicit fallbacks. It parses available files like spec.json and tasks.md while providing explicit guidance for any incomplete or missing documents.

Does spec status tracking work without a steering roadmap file?

Spec status tracking works without a steering roadmap file by focusing on core spec.json, requirements.md, design.md, and tasks.md documents. The roadmap.md file is optional and only parsed when present to add boundary context and roadmap relationships.

Why does my spec status report show incomplete boundary readiness?

The spec status report shows incomplete boundary readiness because design.md lacks sufficient boundary commitments or has unresolved upstream/downstream dependencies. The analysis inspects these boundaries to compute readiness and flags items needing revalidation.