find-root-causes

# Root Cause Analysis

Delegated investigation: symptom → hypothesis → elimination → root cause → prevention.

## Steps

1. Load the `outfitter:debugging` skill for systematic investigation
2. Apply elimination techniques from this skill's references
3. Document investigation trail using RCA templates
4. Deliver root cause report with prevention recommendations

<when_to_use>

- Diagnosing system failures or unexpected behavior
- Investigating incidents or outages
- Finding the actual cause vs surface symptoms
- Preventing recurrence through understanding
- Post-incident reviews requiring formal documentation

NOT for: known issues with documented fixes, simple configuration errors, routine debugging (use `debugging` skill directly)

</when_to_use>

<rca_focus>

This skill extends `debugging` with formal RCA practices:

| Aspect | Debugging | Root Cause Analysis |
|--------|-----------|---------------------|
| Scope | Fix the immediate issue | Understand why it happened |
| Output | Working code | RCA report + prevention |
| Documentation | Investigation notes | Formal templates |
| Goal | Resolution | Prevention of recurrence |

Use `debugging` for day-to-day bug fixes. Use `find-root-causes` for incidents requiring formal investigation and documentation.

</rca_focus>

<elimination_techniques>

Three core techniques for narrowing to root cause:

| Technique | When to Use | Method |
|-----------|-------------|--------|
| **Binary Search** | Large problem space, ordered changes | Bisect the change range |
| **Variable Isolation** | Multiple variables, need causation | Control all but one |
| **Process of Elimination** | Finite set of possible causes | Rule out systematically |

See [elimination-techniques.md](references/elimination-techniques.md) for detailed methods and examples.

</elimination_techniques>

<documentation>

## Investigation Trail

Log every step for handoff and pattern recognition:

```
[TIME] STAGE: Action → Result
[10:15] DISCOVERY: Gathered erro