skills/root-cause-analysis/SKILL.md
--- name: root-cause-analysis description: Root cause analysis with 5 Whys. Use when: root cause, 5 Whys, なぜなぜ分析, 根本原因, 原因分析, symptom fix, 対症療法. allowed-tools: [Read, Grep, Glob, Task] context: fork user-invocable: false --- # Root Cause Analysis - 5 Whys ## Principle Fix the root cause, not the symptom. Symptom fixes add complexity; root-cause fixes prevent recurrence. ## 5 Whys Process Ask "why" five times, descending through abstraction levels. | Step | Level | | ----
npx skillsauth add thkt/claude-config skills/root-cause-analysisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Fix the root cause, not the symptom. Symptom fixes add complexity; root-cause fixes prevent recurrence.
Ask "why" five times, descending through abstraction levels.
| Step | Level | | ---- | ------------------------ | | 1 | Observable fact | | 2 | Implementation detail | | 3 | Design decision | | 4 | Architectural constraint | | 5 | Root cause |
| Tip | Description | | ---------------- | -------------------------------- | | Stay factual | Evidence, not assumptions | | Don't stop early | First "why" is rarely root cause | | Don't go deep | Stop when actionable | | Validate | "Because [5], therefore [4]..." | | Verify fix | "Will this prevent the problem?" |
| Topic | File |
| -------------------- | ---------------------------------------------------- |
| Worked examples | ${CLAUDE_SKILL_DIR}/references/five-whys.md |
| Symptom → Root Cause | ${CLAUDE_SKILL_DIR}/references/symptom-patterns.md |
tools
Delegate implementation to codex (coder) via the herdr-agentchat plugin and drive a two-pane conversation to completion.
development
Extract recurring patterns from past closed PRs/issues and the research findings in workspace/research/, verify them against the latest code, and propose them to docs/wiki/ via PR.
development
Create Decision Records (DR) in MADR v4 format with auto-numbering.
development
Codex review + cleanup. Findings are challenged by critic-audit, not aggregated as facts, and fixes are applied directly. Do NOT use for internal multi-reviewer deep audits or findings reports (use /audit).