Claude Code Spec Workflow is a collection of automated workflows that guides Claude Code through feature development and bug fixing. Developers use it to move from requirements to design, tasks, and implementation, or from a bug report through analysis, fixing, and verification, with the catalogue providing its commands and specialized agents.
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.
git clone --depth 1 https://github.com/Pimzino/claude-code-spec-workflowWrote 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/pimzino/claude-code-spec-workflow/bug-status)<a href="https://agentmods.dev/commands/pimzino/claude-code-spec-workflow/bug-status"><img src="https://agentmods.dev/badge/commands/pimzino/claude-code-spec-workflow/bug-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/pimzino/claude-code-spec-workflow/bug-status"><img src="https://agentmods.dev/badge/commands/pimzino/claude-code-spec-workflow/bug-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.00000 | $0.00301 |
| Opus 5.5 | $0.00000 | $0.00120 |
| Sonnet 5.5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
bug-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
1 near-identical copy found in the catalogue:
- bug-status — 100% identical, 0 lines differ
What it actually says
Bug Status Command
Show current status of all bug fixes or a specific bug fix.
Usage
/bug-status [bug-name]
Instructions
Display the current status of bug fix workflows.
-
If no bug-name provided:
- List all bugs in
.claude/bugs/directory - Show current phase for each bug
- Display completion status
- List all bugs in
-
If bug-name provided:
- Show detailed status for that bug
- Display current workflow phase
- Show completed vs pending phases
- List next recommended actions
-
Status Information:
- Report: [Complete/In Progress/Pending]
- Analysis: [Complete/In Progress/Pending]
- Fix: [Complete/In Progress/Pending]
- Verification: [Complete/In Progress/Pending]
-
Output Format:
Bug: login-timeout Phase: Fix Implementation Progress: Report ✅ | Analysis ✅ | Fix 🔄 | Verification ⏳ Status: Implementing fix for session timeout issue Next: Complete implementation and verify fix works
Bug Fix Phases
- Report: Bug description and impact assessment
- Analysis: Root cause investigation and solution planning
- Fix: Implementation of the planned solution
- Verification: Testing and confirmation of resolution
- Complete: Bug fully resolved and verified
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 · 45 lines · 0 tokens per session scan A 03b8ecf17e32
bug-status is a command published in the GitHub repository Pimzino/claude-code-spec-workflow (3,859 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 301 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-30.
Other commands, from other repositories
bug-report
Draft a bug report issue for lean4-skills.
triage
Query open Node bugs, classify by priority and sub-team, suggest assignments, and generate a triage summary.
speckit.companion.doctor
Report on a spec's run health — unfinished steps, unjournaled tasks, step bleed, drift you can judge, a step that closed having verified nothing, a step that closed without the file it promised, and why completion did not land (read-only, retroactive, never halts).
postmortem
Deliver a structured post-mortem after incidents, mistakes, or stuck sessions. Use when the user requests a structured post-mortem after incidents, mistakes, or stuck sessions.
audit
Audit closed tickets for regressions against today's code (unchanged, evolved, implemented wrong, not implemented), plus duplicate and groupable open ones.
harness:maintenance-pipeline
On-demand, report-first maintenance sweep — runs overdue checks via harness maintenance run, triages findings, and asks the human in plain text before dispatching any fix.