# Issue

> Analyze bugs, classify severity (P0-P3), route to appropriate fix command (@hotfix, @bugfix, or backlog). Use when this capability is needed.

- Skill: `tomevault-io/issue-3` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/issue-3`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/issue-3/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/issue-3

---


# @issue

Classify bugs and route to fix command.

## Severity → Route

| Severity | Signals | Route |
|----------|---------|-------|
| P0 | "production down", "crash", "blocked" | @hotfix |
| P1 | "doesn't work", "failing", "broken" | @bugfix |
| P2 | "edge case", "sometimes" | backlog |
| P3 | "cosmetic", "typo" | defer |

## Workflow

1. Document symptom, reproduction, environment
2. Form hypotheses, rank by likelihood
3. Test systematically
4. Classify per table above
5. `bd create --title="Bug: {desc}" --type=bug --priority={0-3}`
6. Route: @hotfix (P0), @bugfix (P1), or schedule WS (P2/P3)

## Output

Issue file, routing recommendation.

## See Also

- @debug — Root cause analysis
- @hotfix — P0
- @bugfix — P1/P2

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/fall-out-bug) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-11 -->

