What is kiro:spec-status?

A command that reports the status and progress of a Kiro feature specification. It examines the requirements, design, tasks, metadata, and implementation phase.

It shows feature details, current phase, completion percentage, and the status of requirements, design, and implementation work.

It gives developers one overview of what has been created, approved, and completed for a feature.

How reinhardhq/claude-code-spec-boilerplate configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to reinhardhq/claude-code-spec-boilerplate. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/reinhardhq/claude-code-spec-boilerplate/main/.claude/commands/kiro:spec-status.md

Clone the repo

git clone --depth 1 https://github.com/reinhardhq/claude-code-spec-boilerplate

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/reinhardhq/claude-code-spec-boilerplate/kiro-spec-status/github.svg)](https://agentmods.dev/commands/reinhardhq/claude-code-spec-boilerplate/kiro-spec-status)

Your own site

<a href="https://agentmods.dev/commands/reinhardhq/claude-code-spec-boilerplate/kiro-spec-status"><img src="https://agentmods.dev/badge/commands/reinhardhq/claude-code-spec-boilerplate/kiro-spec-status/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/reinhardhq/claude-code-spec-boilerplate/kiro-spec-status"><img src="https://agentmods.dev/badge/commands/reinhardhq/claude-code-spec-boilerplate/kiro-spec-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 732 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 86% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00005	$0.00732
Opus 5	$0.00003	$0.00366
Sonnet 5	$0.00001	$0.00146
Haiku 4.5	$0.00001	$0.00073

Measured 11d ago against content hash 2ef63539754b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

kiro:spec-status scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

86% identical to spec-status — 19 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/kiro:spec-status.md · 96 lines

How it starts

The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Specification Status

Show current status and progress for feature: $ARGUMENTS

Spec Context

Spec Files

Spec directory: !ls -la .kiro/specs/$ARGUMENTS/
Spec metadata: @.kiro/specs/$ARGUMENTS/spec.json
Requirements: @.kiro/specs/$ARGUMENTS/requirements.md
Design: @.kiro/specs/$ARGUMENTS/design.md
Tasks: @.kiro/specs/$ARGUMENTS/tasks.md

All Specs Overview

Available specs: !ls -la .kiro/specs/
Active specs: !find .kiro/specs/ -name "spec.json" -exec grep -l "implementation_ready.*true" {} \;

Task: Generate Status Report

Create comprehensive status report for the specification in the language specified in spec.json (check @.kiro/specs/$ARGUMENTS/spec.json for "language" field):

1. Specification Overview

Display:

Feature name and description
Creation date and last update
Current phase (requirements/design/tasks/implementation)
Overall completion percentage

2. Phase Status

For each phase, show:

✅ Requirements Phase: [completion %]
- Requirements count: [number]
- Acceptance criteria defined: [yes/no]
- Requirements coverage: [complete/partial/missing]
✅ Design Phase: [completion %]
- Architecture documented: [yes/no]
- Components defined: [yes/no]
- Diagrams created: [yes/no]
- Integration planned: [yes/no]
✅ Tasks Phase: [completion %]
- Total tasks: [number]
- Completed tasks: [number]
- Remaining tasks: [number]
- Blocked tasks: [number]

3. Implementation Progress

If in implementation phase:

Task completion breakdown
Current blockers or issues
Estimated time to completion
Next actions needed

Task Completion Tracking

Parse tasks.md checkbox status: - [x] (completed) vs - [ ] (pending)
Count completed vs total tasks
Show completion percentage
Identify next uncompleted task

4. Quality Metrics

Show:

Requirements coverage: [percentage]
Design completeness: [percentage]
Task granularity: [appropriate/too large/too small]
Dependencies resolved: [yes/no]

Read the full file on GitHub · 96 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

11d ago First seen · 96 lines · 5 tokens per session scan A 2ef63539754b

Subscribe to this mod's changes

kiro:spec-status is a command published in the GitHub repository reinhardhq/claude-code-spec-boilerplate (2 stars, last pushed 1y ago), licensed MIT. It adds 5 tokens to every session and 732 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to spec-status, differing in 19 lines, and is treated as a copy.

Project management

claude-code-spec-boilerplate: Command for Claude Code