kiro-spec-status

Analyze JSON metadata and Markdown docs to report specification status.

Updated Feb 5, 2026

Search Tags:#project management #specification #dependencies #status tracking #progress report

Ready to run

npx skills add https://github.com/mimikun/mimikun.nvim-config --skill kiro-spec-status-mimikun

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kiro-spec-status
Source: https://github.com/mimikun/mimikun.nvim-config/tree/main/.claude/skills/kiro-spec-status
Command: npx skills add https://github.com/mimikun/mimikun.nvim-config --skill kiro-spec-status-mimikun

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps users track the status and progress of specifications, providing insight into requirements, design, tasks, and approvals for effective project management.

Core Features & Use Cases

Progress Monitoring: Display current phase, completion percentages, and status updates for specifications.
Dependency Analysis: Identify upstream, downstream, and boundary relationships among specs.
Status Reporting: Generate comprehensive reports covering project workflows, boundary context, and revalidation needs to facilitate decision-making and coordination.

Quick Start

Ask the kiro-spec-status skill to review the current specification's progress and dependencies based on existing spec files and metadata.

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 dependencies for a complex project workflow?▼

You can track specification progress by reading JSON metadata and Markdown documentation to assemble status reports, displaying current phases, completion percentages, and dependency relationships for effective project management.

What is the best way to generate a status report for project specifications and requirements?▼

Generating a specification status report involves analyzing existing spec files and metadata to identify upstream, downstream, and boundary relationships, producing comprehensive reports on workflows and revalidation needs.

Can I analyze upstream and downstream dependencies using existing spec files?▼

Yes, dependency analysis identifies upstream, downstream, and boundary relationships among specifications by reading existing JSON metadata and Markdown documentation, improving visibility into complex development workflows.

Do I need JSON metadata to monitor specification phases and approval status?▼

Yes, monitoring specification phases, tasks, and approvals requires reading JSON metadata and Markdown documentation to assemble accurate progress reports and display current completion percentages.

When should I not use automated specification status tracking for requirement validation?▼

Automated specification status tracking is not suitable when you lack JSON metadata or Markdown documentation, as assembling phase reports, dependency analysis, and boundary context requires these specific input files.

Does kiro-spec-status work with Markdown documentation and JSON metadata for requirement validation?▼

Yes, kiro-spec-status works by reading JSON metadata and Markdown documentation to analyze specification phases, dependencies, and boundaries, generating reports that facilitate requirement validation and project coordination.