From nw
Conducts root cause analysis using enhanced 5 Whys methodology: multi-causal branching, evidence per level, backwards validation, and complete solutions for complex problems.
npx claudepluginhub nwave-ai/nwave --plugin nwThis skill uses the workspace's default tool permissions.
Taiichi Ohno: "By repeating why five times, the nature of the problem as well as its solution becomes clear."
Enhanced root cause analysis with explicit bias guards and stopping criteria. Use for incident post-mortems, bug investigations, and process failures where standard 5 Whys might mislead.
Conducts root cause analysis using 5-Why methodology for errors, bugs, build/test failures, performance issues, and integration problems.
Five Whys, fishbone diagrams, identifying systemic causes not just symptoms.
Share bugs, ideas, or general feedback.
Taiichi Ohno: "By repeating why five times, the nature of the problem as well as its solution becomes clear."
Core tenets: scientific evidence-based investigation | address fundamental causes not symptoms | solve to prevent recurrence | use findings for Kaizen
Complex problems have multiple root causes. Investigate comprehensively:
What is immediately observable? Investigate all symptoms. Each branch continues independently. Document verifiable evidence per symptom.
WHY 1A: Path not found [Evidence: file exists but wrong context -- Windows vs WSL paths]
WHY 1B: Permission denied [Evidence: user context mismatch between host and container]
WHY 1C: Timing issues [Evidence: race conditions with file system operations]
Why does this condition exist? Follow each WHY 1 through context. Check if factors connect multiple causes. Examine system/environment/operational context.
Why do conditions persist? How system enables multiple failure modes. How causes interact systemically. Analyze design/architecture decisions.
Why not anticipated? Review design assumptions. Identify all design blind spots. Trace decisions to original context.
Fundamental causes. Multiple root causes expected for complex issues. Ensure all contributing causes identified. Focus on deepest level.
Each WHY level must have verifiable evidence for all causes. Root causes must explain all symptoms collectively. Solutions must address all root causes.
Every root cause -> corresponding solution | Prevent recurrence, not just mitigate | Use findings for system improvement
PROBLEM: [clear problem statement]
WHY 1A: [symptom] [Evidence: ...]
WHY 2A: [context] [Evidence: ...]
WHY 3A: [system factor] [Evidence: ...]
WHY 4A: [design factor] [Evidence: ...]
WHY 5A: [root cause] [Evidence: ...]
-> ROOT CAUSE A: [fundamental cause]
-> SOLUTION A: [prevention strategy]
WHY 1B: [symptom] [Evidence: ...]
WHY 2B: [context] [Evidence: ...]
...
CROSS-VALIDATION:
- Root Cause A + Root Cause B: [consistent/contradictory]
- All symptoms explained: [yes/no, gaps if any]