菜单
Five Whys root cause analysis. Iteratively asks "why" to drill past symptoms to underlying causes. Use for debugging, investigating failures, or understanding why something went wrong.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | 5whys |
| description | Five Whys root cause analysis. Iteratively asks "why" to drill past symptoms to underlying causes. Use for debugging, investigating failures, or understanding why something went wrong. |
| user-invocable | true |
Perform iterative root cause analysis by asking "why" repeatedly until you reach the underlying cause.
Start with the stated problem and ask "why" it occurred. For each answer, ask "why" again. Continue until you reach a root cause that:
Typically this takes 5 iterations, but may be fewer or more.
Problem Statement Restate the problem clearly and specifically.
Why Chain
| Level | Question | Answer |
|---|---|---|
| 1 | Why did [problem]? | [Answer 1] |
| 2 | Why did [Answer 1]? | [Answer 2] |
| 3 | Why did [Answer 2]? | [Answer 3] |
| 4 | Why did [Answer 3]? | [Answer 4] |
| 5 | Why did [Answer 4]? | [Root Cause] |
Root Cause The fundamental issue identified. Explain why this is the root (not just another symptom).
Branches (if applicable) If multiple valid answers exist at any level, show the branching analysis.
Corrective Actions
Verification How will you confirm the root cause is correct? (Test the hypothesis)
Problem: Users are seeing 500 errors on the checkout page
| Level | Question | Answer |
|---|---|---|
| 1 | Why are users seeing 500 errors? | The payment service is timing out |
| 2 | Why is the payment service timing out? | Database queries are taking >30 seconds |
| 3 | Why are database queries slow? | The orders table has 50M rows and no index on customer_id |
| 4 | Why is there no index? | The table was created before we had this query pattern |
| 5 | Why wasn't an index added when the query was added? | No database review process for new queries |
Root Cause: Missing process for database review when adding new query patterns.
Corrective Actions:
Problem: Enterprise customer canceled after 6 months
| Level | Question | Answer |
|---|---|---|
| 1 | Why did the customer cancel? | They said the product wasn't delivering value |
| 2 | Why wasn't it delivering value? | They only had 12% feature adoption |
| 3 | Why was adoption so low? | Users weren't trained on key workflows |
| 4 | Why weren't users trained? | Onboarding ended after technical setup |
| 5 | Why does onboarding end at setup? | Success team is understaffed; prioritizes new sales |
Root Cause: Success team capacity forces them to end onboarding prematurely.
Corrective Actions:
$ARGUMENTS
Strunk & White composition review using the 11 principles from "Elements of Style" Chapter II. Use when analyzing structure, improving flow, or tightening prose.
Strunk & White style review using the 21 reminders from "Elements of Style" Chapter V. Use when editing prose, reviewing drafts, or improving writing clarity and tone.
Strunk & White grammar review using the 11 elementary rules from "Elements of Style" Chapter I. Use when checking mechanics, punctuation, and grammatical correctness.
After-Action Review—structured debrief asking what was expected, what happened, why the difference, and what next. Use after projects, launches, presentations, or any significant event.
Cynefin sense-making framework categorizing problems as Simple, Complicated, Complex, Chaotic, or Confused to select the right approach. Use when unsure how to tackle a problem.
Design Thinking process—Empathize, Define, Ideate, Prototype, Test. Use for product design, solving ambiguous problems, or when you don't know what users really need.
