From debug-agent
Comprehensive 6-phase Fagan inspection for systematic defect analysis — achieves 60-90% defect detection rates. Use for complex, critical, or hard-to-reproduce bugs that need thorough investigation. Trigger for: "I need a thorough bug analysis", P0/P1 incidents, bugs that keep coming back, "we've tried everything and can't find it", pre-release code audits, or any situation where a quick fix isn't enough.
How this skill is triggered — by the user, by Claude, or both
Slash command
/debug-agent:debug-inspectThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Fagan inspection is a formal peer review methodology achieving 60-90% defect detection rates. You will execute all 6 phases in sequence. Do not skip phases — the rigor is the point.
Fagan inspection is a formal peer review methodology achieving 60-90% defect detection rates. You will execute all 6 phases in sequence. Do not skip phases — the rigor is the point.
Ask for a bug description if not provided. Then proceed through all phases, documenting results at each step.
Define the inspection scope:
Document: Bug summary, scope, success criteria, open questions.
Build context before touching code:
git log --oneline -30 — look for recent changes to affected areas, revert commits, emergency fixesDocument: Commit history analysis, preliminary timeline, impact scope.
Systematic artifact examination — read the code before theorizing:
Document: Code review findings, test coverage gaps, config issues, preliminary hypotheses.
Systematic defect identification across all categories:
For each defect found: document evidence, assign severity (P0-P3), categorize.
Root cause analysis: Apply fishbone thinking across People / Process / Technology / Environment / Data / Methods.
Document: Defect list with evidence, root cause analysis, severity matrix.
Turn findings into a concrete fix plan:
Document: Fix proposals with tradeoffs, test strategy, risk assessment, implementation order.
Close the loop:
Produce a structured debug report:
# Fagan Inspection Report
**Report ID:** INSPECT-[YYYYMMDD]
**Severity:** P[0-3]
**Date:** [today]
## Executive Summary
[2-3 sentences: what the bug is, root cause, recommended fix]
## Phase Results
### Phase 1 — Planning
[Scope, success criteria, open questions]
### Phase 2 — Overview
[Git history findings, timeline, impact scope]
### Phase 3 — Preparation
[Code findings, test gaps, config issues, initial hypotheses]
### Phase 4 — Inspection
[Defects found with evidence, root cause analysis]
### Phase 5 — Rework Plan
[Fix proposal, test strategy, risk assessment]
### Phase 6 — Follow-up
[Validation steps, doc updates needed, lessons learned]
## Completion Checklist
- [ ] All 6 phases completed
- [ ] Root cause identified with evidence
- [ ] Fix recommended with tradeoffs
- [ ] Test strategy defined
- [ ] Risk assessment completed
- [ ] Lessons learned documented
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub mkellerman/bmad-skills --plugin debug-agent