Menu
Systematic debugging using scientific method for evidence-based root cause analysis
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Quality bug fixes (P1/P2). Full TDD cycle, branch from master via feature/, no production deploy.
Execute ONE executable leaf workstream with TDD, guard enforcement, and ws-verdict output
Deployment orchestration. Creates PR to master (after @oneshot) or merges for release.
System design with progressive disclosure, produces workstream files
Feature planning orchestrator (discovery -> idea -> ux -> design -> workstream tree)
Emergency P0 fixes. Fast-track production deployment with minimal changes. Branch from master, immediate deploy.
| name | debug |
| description | Systematic debugging using scientific method for evidence-based root cause analysis |
| version | 2.0.0 |
| changes | ["Converted to LLM-agnostic format","Removed tool-specific API references","Focus on WHAT, not HOW to invoke"] |
Evidence-based debugging using scientific method. Not "try stuff and see" -- systematic investigation.
When user invokes @debug "<issue>":
Goal: Collect evidence WITHOUT forming hypotheses
Actions:
Output: Observation log with timestamps, error messages, environment state
Goal: Create testable theories about root cause
Process:
Output: Hypothesis list with ranked theories
Goal: Run targeted tests to confirm/deny hypotheses
Actions:
Output: Experiment results with pass/fail
Goal: Confirm root cause and verify fix
Actions:
Output: Root cause report + fix
| Pitfall | Problem |
|---|---|
| Skipping observation | Jumping to conclusions |
| Testing multiple things | Can't isolate cause |
| Confirmation bias | Only looking for proving evidence |
| Stopping at first fix | Not understanding WHY it worked |
@bugfix - Quality bug fixes (P1/P2)@hotfix - Emergency fixes (P0)@issue - Bug classification and routing