CCManager is a command-line application for managing multiple sessions of AI coding assistants across Git worktrees and projects. It is for developers working with tools such as Claude Code, Gemini CLI, Codex CLI, Cursor Agent, Copilot CLI, Cline CLI, OpenCode, and Kimi CLI, and the catalogue entries provide commands and instructions for its workflows.
Borrowing it
Nothing to install: this file belongs to kbwo/ccmanager. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kbwo/ccmanager/main/.claude/commands/kiro/spec-status.mdgit clone --depth 1 https://github.com/kbwo/ccmanagerWrote 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.
[](https://agentmods.dev/commands/kbwo/ccmanager/spec-status)<a href="https://agentmods.dev/commands/kbwo/ccmanager/spec-status"><img src="https://agentmods.dev/badge/commands/kbwo/ccmanager/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.
<a href="https://agentmods.dev/commands/kbwo/ccmanager/spec-status"><img src="https://agentmods.dev/badge/commands/kbwo/ccmanager/spec-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00770 |
| Opus 5.5 | $0.00002 | $0.00308 |
| Sonnet 5.5 | $0.00001 | $0.00154 |
| Haiku 4.5 | $0.00001 | $0.00077 |
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 1mo 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- kiro:spec-status — 86% identical, 19 lines differ
- spec-status — 84% identical, 7 lines differ
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]
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.
- 1mo ago First seen · 97 lines · 5 tokens per session scan A 7a9f912cb707
spec-status is a command published in the GitHub repository kbwo/ccmanager (1,266 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.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.
Other commands, from other repositories
maestro-odyssey
Long-running iterative cycle — one entry, seven modes (debug|improve|planex|review|security|defensive|ui). Shared archaeology/audit → fix → verify → generalize → discover → persist skeleton with mode-specific dimensions. User-invoked campaign entry; single-step fixes route via /maestro-next.
dispatch
Every task description uses structured format for clarity.
maestro-companion
Quick execution for small tasks — minimal run lifecycle (start + done) with evidence recording. Full LLM capability, scoped to mechanically clear tasks.
maestro-fork
Create or sync session worktree for parallel dev.
maestro-guard
Manage editing boundary restrictions.
converge
Bash: python /scripts/aco.py --session {rundir}/work/team report.