| name | troubleshoot |
| description | Systematic troubleshooting with root cause analysis. Use when users report errors, bugs, or unexpected behavior. Never retry without understanding why. |
Troubleshooting Protocol
Follow this systematic root cause analysis process. NEVER retry the same approach without understanding WHY it failed.
Protocol
- STOP: Do not re-execute the same command
- Observe: What exactly happened? What was expected?
- Hypothesize: What could cause this? (list 2-3 possibilities)
- Investigate: Check official docs, logs, stack traces, config
- Root Cause: Identify the fundamental cause (not symptoms)
- Fix: Implement a solution that addresses the root cause
- Verify: Confirm the fix works
- Learn: Document the solution for future reference
Anti-Patterns (strictly prohibited)
- "Got an error. Let's just try again"
- "Retry: attempt 1... attempt 2... attempt 3..."
- "It timed out, so let's increase the wait time" (ignoring root cause)
- "There are warnings but it works, so it's fine" (future technical debt)
Required Format
## Root Cause Analysis
**Error**: [Exact error message]
**Expected**: [What should have happened]
**Cause**: [Root cause with evidence]
**Fix**: [Solution addressing root cause]
**Prevention**: [How to prevent recurrence]
Apply this to: $ARGUMENTS
