skills.rest
snicmakino
snicmakinoCOMMUNITY
Explore all skills by this author →
Website𝕏@snicmakinoGitHub

kiro-spec-status

Load spec metadata and compute phase, progress, and blockers.

2|Updated Apr 8, 2026
Search Tags:#specifications#roadmap#kiro#progress-tracking#spec-status#boundary-context
One-click install
npx skills add https://github.com/snicmakino/kolt --skill kiro-spec-status-snicmakino
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kiro-spec-status
Source: https://github.com/snicmakino/kolt/tree/main/.claude/skills/kiro-spec-status
Command: npx skills add https://github.com/snicmakino/kolt --skill kiro-spec-status-snicmakino

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams track the status and readiness of specifications by collecting metadata from .kiro/specs, briefings, and roadmaps, then presenting a clear progress snapshot.

Core Features & Use Cases

  • Load and interpret spec metadata from .kiro/specs/$ARGUMENTS/spec.json and optional brief.md to determine current phase.
  • Compute completion statuses across Requirements, Design, Tasks, and Approvals, and surface boundary context and upstream/downstream touchpoints.
  • Generate a concise, actionable report highlighting next actions, blockers, and revalidation needs when specs change.

Quick Start

Provide the spec identifier to generate its 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 current phase status in Kiro?▼

To track specification progress in Kiro, load metadata from .kiro/specs along with brief.md and roadmap files. This aggregates requirements, design, and tasks data to compute completion percentages and surface current phase status.

What is the best way to identify spec blockers and upstream touchpoints?▼

To identify spec blockers and upstream touchpoints, aggregate spec directory data including requirements.md, design.md, and tasks.md. This process surfaces boundary context and highlights dependencies affecting your specification.

How do I compute completion percentages across requirements, design, and tasks?▼

Compute completion percentages across requirements, design, and tasks by loading metadata from spec.json and related files in the .kiro/specs directory. This aggregates document statuses to return an overall completion calculation.

When do I need to revalidate specifications after roadmap changes?▼

You need to revalidate specifications after roadmap changes when the spec status report identifies modified upstream boundary context. The report generates a revalidation watchlist to flag specs requiring immediate review.

Can I generate a spec status report without a brief.md file?▼

Yes, you can generate a spec status report without a brief.md file. The system loads required metadata from spec.json and optionally includes brief.md if available to supplement the current phase and boundary context data.

What recommended next actions does a spec status report provide?▼

A spec status report provides recommended next actions based on computed progress across requirements, design, and tasks. It highlights specific blockers, revalidation needs, and boundary context to guide immediate specification workflow steps.

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
taku-otaku-o
1

kiro-spec-status

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

Community
Intermediate
BarryYinBarryYin

kiro-spec-status

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

Community
Intermediate