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/spec-status)<a href="https://agentmods.dev/commands/pimzino/claude-code-spec-workflow/spec-status"><img src="https://agentmods.dev/badge/commands/pimzino/claude-code-spec-workflow/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/pimzino/claude-code-spec-workflow/spec-status"><img src="https://agentmods.dev/badge/commands/pimzino/claude-code-spec-workflow/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.00000 | $0.00288 |
| Opus 5.5 | $0.00000 | $0.00115 |
| Sonnet 5.5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
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
1 near-identical copy found in the catalogue:
- spec-status — 100% identical, 0 lines differ
What it actually says
Spec Status Command
Show current status of all specs or a specific spec.
Usage
/spec-status [feature-name]
Instructions
Display the current status of spec workflows.
-
If no feature-name provided:
- List all specs in
.claude/specs/directory - Show current phase for each spec
- Display completion status
- List all specs in
-
If feature-name provided:
- Show detailed status for that spec
- Display current workflow phase
- Show completed vs pending tasks
- List next recommended actions
-
Status Information:
- Requirements: [Complete/In Progress/Pending]
- Design: [Complete/In Progress/Pending]
- Tasks: [Complete/In Progress/Pending]
- Implementation: [X/Y tasks complete]
-
Output Format:
Spec: user-authentication Phase: Implementation Progress: Requirements ✅ | Design ✅ | Tasks ✅ Implementation: 3/8 tasks complete Next: Execute task 4 - "Implement password validation"
Workflow Phases
- Requirements: Gathering and documenting requirements
- Design: Creating technical design and architecture
- Tasks: Breaking down into implementation tasks
- Implementation: Executing individual tasks
- Complete: All tasks finished and integrated
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 4f663d90c440
spec-status is a command published in the GitHub repository Pimzino/claude-code-spec-workflow (3,860 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 288 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
template
Manage issue templates for streamlined issue creation.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.