skills.rest
miyamo2
miyamo2COMMUNITY
Explore all skills by this author →
GitHub

kiro-spec-status

Analyze specification lifecycle metadata to generate structured status reports.

Updated Jan 26, 2026
Search Tags:#workflow#planning#specification#reporting#governance#status#progress
One-click install
npx skills add https://github.com/miyamo2/braider --skill kiro-spec-status-miyamo2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kiro-spec-status
Source: https://github.com/miyamo2/braider/tree/main/.gemini/skills/kiro-spec-status
Command: npx skills add https://github.com/miyamo2/braider --skill kiro-spec-status-miyamo2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly understand where a specification stands in its lifecycle, what is completed, what remains, and what actions are required to move forward.

Core Features & Use Cases

  • Load spec context from .kiro/specs/$1/spec.json and related files (brief.md if present) to establish the current state.
  • Analyze the status across phases (Requirements, Design, Tasks, Approvals) and surface boundary context and revalidation needs.
  • Generate a concise status report highlighting progress, blockers, and next actions.
  • Identify downstream or adjacent specs or updates that may require revalidation when changes occur.
  • Support governance and planning reviews by providing an actionable view of the spec lifecycle.

Quick Start

Run kiro-spec-status against a target spec to generate the current status report.

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 specification progress and lifecycle status at a glance?▼

Specification progress is tracked by parsing .kiro/specs metadata and related brief notes to surface phases, tasks, and blockers. This generates a structured status report showing current completion states for timely governance and planning decision making.

What is the best way to assess phase completion across specification workstreams?▼

Assessing phase completion involves analyzing spec lifecycle context across Requirements, Design, Tasks, and Approvals phases. The analysis reads spec.json and brief.md files to establish current state and surface boundary context or revalidation needs for actionable governance reviews.

How do I identify spec blockers and next actions for planning reviews?▼

Spec blockers and next actions are identified by analyzing specification lifecycle context and parsing .kiro/specs metadata. This produces a concise status report highlighting current progress, active blockers, and required downstream revalidation when changes occur.

Does generating a spec status report require any external dependencies?▼

Generating a spec status report requires no external dependencies. It parses local .kiro/specs metadata, spec.json files, and brief.md notes directly to assess phase completion and produce structured reporting without additional environment setup.

Can I detect which downstream specs require revalidation when changes occur?▼

Downstream or adjacent specs requiring revalidation are identified by analyzing specification lifecycle context and boundary conditions. The status report surfaces these dependencies by parsing .kiro/specs metadata to ensure timely governance and planning updates.

Related Skills

Explore More Product & Management Skills→
shimaMatzshimaMatz

kiro-spec-init

Initialize KiRo spec files from a project description and templates.

Community
Advanced
ryu-satoryu-sato

kiro-spec-status

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

Community
Intermediate
notta50notta50

kiro-spec-status

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

Community
Intermediate
taku-otaku-o
1

kiro-spec-status

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

Community
Intermediate