skills.rest
shimaMatz
shimaMatzCOMMUNITY
Explore all skills by this author →
GitHub

kiro-spec-status

Analyze KiRo spec files to report phase, completion, and blockers.

Updated Apr 5, 2026
Search Tags:#reporting#risk-management#progress-tracking#spec-status#boundary-context
One-click install
npx skills add https://github.com/shimaMatz/driver-copilot --skill kiro-spec-status-shimamatz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kiro-spec-status
Source: https://github.com/shimaMatz/driver-copilot/tree/main/.cursor/skills/kiro-spec-status
Command: npx skills add https://github.com/shimaMatz/driver-copilot --skill kiro-spec-status-shimamatz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to visualize the current status of KiRo specs, including phase, progress, and blockers. KiRo-spec-status consolidates relevant spec data to provide a clear, actionable view for decision makers.

Core Features & Use Cases

  • Parse spec.json and related files (brief.md if present, requirements.md, design.md, tasks.md) to compute phase progress and identify gaps.
  • Surface boundary context (upstream/downstream relationships) and potential revalidation needs for governance.
  • Generate a concise status report that highlights next actions and blockers for stakeholders.

Quick Start

Use kiro-spec-status to generate a live status report for a given KiRo 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 track spec progress and identify blockers in KiRo specs?▼

Track spec progress and blockers by parsing spec.json, brief.md, requirements.md, design.md, and tasks.md to compute phase completion. This produces a boundary-aware status report highlighting current phase, gaps, and next actions for stakeholders.

How does spec status reporting handle upstream and downstream boundary context?▼

Spec status reporting surfaces upstream and downstream boundary context by analyzing spec relationships to identify revalidation needs. This reveals dependencies and escalation points for governance and decision-making.

Can I generate a decision-ready status summary from KiRo spec.json files?▼

Yes, generate a decision-ready status summary from spec.json by computing phase progress and identifying gaps across related spec documents. The structured output highlights next actions and escalation needs for stakeholders.

What is the best way to visualize KiRo spec phase completion for stakeholders?▼

Visualize KiRo spec phase completion by consolidating spec.json and related files into a concise status report. This surfaces blockers, next actions, and boundary context for stakeholders.

Do I need brief.md to compute spec status, or is spec.json enough?▼

spec.json is the primary file for computing spec status, while brief.md is optional. Parsing spec.json alongside requirements.md, design.md, and tasks.md provides sufficient data to compute phase progress and identify gaps.

Related Skills

Explore More Product & Management Skills→
notta50notta50

kiro-spec-status

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

Community
Intermediate
t0ddc3byt0ddc3by
58

blocker-review

Diagnose onboarding blockers and route escalations using an escalation matrix.

Community
Advanced
mizchimizchi
320

upstream-fix-and-pin

Pin downstream dependencies to upstream git refs and track merge SHAs.

Community
Advanced
dether-netdether-net
2

surface

Analyze Dethernety threat models to generate attack surface summaries.

Official
Advanced