A command that reports the status of a feature specification. A specification is a written plan describing what a feature should do, how it should work, and what tasks remain.

Use it to check a feature's phase, completion, requirements, acceptance criteria, design, and implementation progress.

It gathers the available requirements, design, task, and metadata files into one progress report instead of requiring manual inspection.

spec-status — Command by kbwo

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/kbwo/ccmanager/spec-status

Clone the repo

git clone --depth 1 https://github.com/kbwo/ccmanager

Made for: Claude Code.

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 770 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.

Model	Per session	Once invoked
Fable 5	$0.00005	$0.00770
Opus 5	$0.00003	$0.00385
Sonnet 5	$0.00001	$0.00154
Haiku 4.5	$0.00001	$0.00077

Measured 2d ago against content hash 7a9f912cb707, 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 2d 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

Copies of this mod

1 near-identical copy found in the catalogue:

kiro:spec-status — 86% identical, 19 lines differ

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

How it starts

The opening of the file, as written. The whole thing — 97 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: $1

Spec Context

Spec Files

Spec directory: !bash -c 'ls -la .kiro/specs/$1/ 2>/dev/null || echo "No spec directory found"'
Spec metadata: .kiro/specs/$1/spec.json
Requirements: .kiro/specs/$1/requirements.md
Design: .kiro/specs/$1/design.md
Tasks: .kiro/specs/$1/tasks.md

All Specs Overview

Available specs: !bash -c 'ls -la .kiro/specs/ 2>/dev/null || echo "No specs directory found"'
Active specs: !bash -c 'find .kiro/specs/ -name "spec.json" -exec grep -l "implementation_ready.*true" {} \; 2>/dev/null || echo "No active specs"'

Task: Generate Status Report

Create comprehensive status report for the specification in the language specified in spec.json (check .kiro/specs/$1/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 · 97 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.

2d ago First seen · 97 lines · 5 tokens per session scan A 7a9f912cb707

Subscribe to this mod's changes

spec-status is a command published in the GitHub repository kbwo/ccmanager (1,229 stars, last pushed 3d ago), licensed MIT. It adds 5 tokens to every session and 770 once invoked, about $0.0000 per session on Opus 5. 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-30.

Planning claude claude-code cli gemini gemini-cli vibe-coding

spec-status