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/dotclaude 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
Internal helper for /think Step 11. Renders SOW.md + Spec.md as an integrated Astro view and returns a dev server URL.
development
Extract repository spec while detecting bugs, spec gaps, and consistency drift via dual-purpose documentation. OUTCOME.md-axis question-driven exploration with ephemeral output. Do NOT use for code review (use /audit or /polish), feature implementation (use /code), planning only (use /think), or single-bug fix (use /fix).
development
Discover undocumented design decisions and challenge each candidate via critic-design before promotion. Rank by impact and reversibility, produce ADR promotion candidates. Treat each candidate as a position arguing for ADR status, not a fact to be filed. Pairs with audit-adr-drift, which scans existing ADRs for drift against code.
development
Scan ADR Decision sections against current code and report drift with modification direction and priority. Do NOT use for repos without ADRs (use audit-adr-gaps instead).