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-analyze)<a href="https://agentmods.dev/commands/pimzino/claude-code-spec-workflow/bug-analyze"><img src="https://agentmods.dev/badge/commands/pimzino/claude-code-spec-workflow/bug-analyze/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-analyze"><img src="https://agentmods.dev/badge/commands/pimzino/claude-code-spec-workflow/bug-analyze.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.00870 |
| Opus 5.5 | $0.00000 | $0.00348 |
| Sonnet 5.5 | $0.00000 | $0.00174 |
| Haiku 4.5 | $0.00000 | $0.00087 |
Grade A, and why
bug-analyze 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-analyze — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Analyze Command
Investigate and analyze the root cause of a reported bug.
Usage
/bug-analyze [bug-name]
Phase Overview
Your Role: Investigate the bug and identify the root cause
This is Phase 2 of the bug fix workflow. Your goal is to understand why the bug is happening and plan the fix approach.
Instructions
Manual Analysis Process:
-
Prerequisites
- Ensure report.md exists and is complete
- Load the bug report for context
- Load steering documents:
# Windows: claude-code-spec-workflow get-content "C:\path\to\project\.claude\steering\tech.md" claude-code-spec-workflow get-content "C:\path\to\project\.claude\steering\structure.md" # macOS/Linux: claude-code-spec-workflow get-content "/path/to/project/.claude/steering/tech.md" claude-code-spec-workflow get-content "/path/to/project/.claude/steering/structure.md" - Understand the reported issue completely
-
Investigation Process
-
Code Investigation
- Search codebase for relevant functionality
- Identify files, functions, and components involved
- Map data flow and identify potential failure points
- Look for similar issues or patterns
-
Root Cause Analysis
- Determine the underlying cause of the bug
- Identify contributing factors
- Understand why existing tests didn't catch this
- Assess impact and risks
-
Solution Planning
- Design fix strategy
- Consider alternative approaches
- Plan testing approach
- Identify potential risks
-
-
Create Analysis Document
- Template to Follow: Use the bug analysis template from the pre-loaded context above (do not reload)
- Read and follow: Use the bug analysis template and follow all sections precisely
- Document investigation findings following the template structure
Template Usage
- Follow exact structure: Use
.claude/templates/bug-analysis-template.mdprecisely - Include all sections: Don't omit any required template sections
- Detailed analysis: Follow the template's format for comprehensive investigation
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 · 107 lines · 0 tokens per session scan A af137dcae329
bug-analyze 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 870 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
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
react-native
Command "react-native" from getsentry/toolkit, covering examples, also associate with a release and distribution(s), xcode build step (react-native xcode) and important notes.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.