skills/analyzing-root-causes/SKILL.md
Root cause analysis with 5 Whys. Use when: root cause, 5 Whys, なぜなぜ分析, 根本原因, 原因分析, symptom fix, 対症療法.
npx skillsauth add thkt/dotclaude analyzing-root-causesInstall 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.
| Type | Example | Result | | ----------- | -------------------------- | ------------- | | Symptom Fix | setTimeout to wait for DOM | Breaks later | | Root Cause | Use React ref properly | Permanent fix | | Symptom Fix | Add flag for double-submit | Complexity ↑ | | Root Cause | Disable button on submit | Simple fix |
| Step | Question | Reveals | | ---- | ----------------------------- | ------------------------ | | 1 | Why does this occur? | Observable fact | | 2 | Why does that happen? | Implementation detail | | 3 | Why is that the case? | Design decision | | 4 | Why does that exist? | Architectural constraint | | 5 | Why was it designed this way? | Root cause |
| Topic | File |
| -------- | ---------------------------------------------------- |
| 5 Whys | ${CLAUDE_SKILL_DIR}/references/five-whys.md |
| Patterns | ${CLAUDE_SKILL_DIR}/references/symptom-patterns.md |
documentation
Generates and updates .claude/OUTCOME.md interactively. When the file is absent or empty (no Behavior / all sections TBD), collects content via AskUserQuestion and writes the stub; when present, shows the current state and applies updates.
development
Judge a SKILL.md against craft axes (single responsibility, description distinctiveness, imperative voice, verifiable completion, calibration, progressive disclosure) and apply the fixes the audit surfaces. Do not use for format-presence-only checks (use reviewer-prompt) or reproducibility loops (use /tuning).
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).