spec-status

spec-status is a command for Claude Code from kaze-jp/kusa. It costs 0 tokens per session (464 once invoked), scanned A, original, MIT.

A command that reports how far a feature specification has progressed. A feature specification is a set of documents describing its requirements, design, and implementation tasks.

In plain words
What is it for?
Use it to inspect a feature’s specification folder, see which planning phases are complete, count finished tasks, and calculate implementation progress.
Why use it?
It replaces checking several files by hand and highlights incomplete work, blockers, and open questions in one report.

Command for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/kaze-jp/kusa/spec-status
Clone the repo
git clone --depth 1 https://github.com/kaze-jp/kusa

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.

agentmods badge for spec-status

README.md
[![agentmods](https://agentmods.dev/badge/commands/kaze-jp/kusa/spec-status.svg)](https://agentmods.dev/commands/kaze-jp/kusa/spec-status)
Your own site
<a href="https://agentmods.dev/commands/kaze-jp/kusa/spec-status"><img src="https://agentmods.dev/badge/commands/kaze-jp/kusa/spec-status.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 464 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00464
Opus 5 $0.00000 $0.00232
Sonnet 5 $0.00000 $0.00093
Haiku 4.5 $0.00000 $0.00046

Measured 4d ago against content hash 7a28c643c998, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 4d 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.

.claude/commands/kiro/spec-status.md · 75 lines

What it actually says

Show Spec Status

Display the current status of a feature specification, including phase completion and progress.

Usage

/kiro:spec-status <feature-name>

Instructions

  1. Locate the spec directory at .kiro/specs/$FEATURE_NAME/. If it does not exist, report that no spec exists for this feature.

  2. Check each phase by looking for the corresponding files:

    Phase File Status
    Init requirements-init.md Exists?
    Requirements requirements.md Exists?
    Design design.md Exists?
    Tasks tasks.md Exists?
    Implementation (check task completion) Progress?
  3. If tasks.md exists, analyze implementation progress:

    • Count total tasks
    • Count completed tasks (checked acceptance criteria)
    • Count parallelizable tasks remaining
    • Identify current blockers (tasks with unmet dependencies that are not complete)
    • Calculate percentage complete
  4. Check for blockers:

    • Open questions in any document
    • Tasks marked as blocked
    • Design gaps noted during implementation
  5. Generate a status report:

# Spec Status: <feature-name>

## Phase Progress
- [x] Init (requirements-init.md)
- [x] Requirements (requirements.md)
- [x] Design (design.md)
- [ ] Tasks (tasks.md)
- [ ] Implementation

## Current Phase: <phase-name>
<Details about what needs to happen next>

## Implementation Progress (if applicable)
- Total tasks: X
- Completed: Y / X (Z%)
- Parallelizable remaining: N
- Blocked: M

## Blockers
- <blocker description>

## Next Steps
- <recommended next action>
  1. Display the report to the user.

Output

  • Status report displayed to the user (not written to a file)

Notes

  • If no feature name is provided, list all specs found in .kiro/specs/ with their statuses.
  • This command is read-only; it does not modify any files.
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.

  1. 4d ago First seen · 75 lines · 0 tokens per session scan A 7a28c643c998

Subscribe to this mod's changes

spec-status is a command published in the GitHub repository kaze-jp/kusa (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 464 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.