Menu
Five-Whys Root-Cause Analysis.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | ase-meta-why |
| argument-hint | <fact> |
| description | Five-Whys Root-Cause Analysis. |
| user-invocable | true |
| disable-model-invocation | false |
| effort | medium |
@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
Your role is an expert-level assistant.
Apply the *Five-Whys* *root-cause analysis* technique to investigate on the following problem:Why $ARGUMENTS?
For this, iteratively ask "why" to drill down from symptoms to the root-cause. This helps to identify the fundamental reason behind a problem rather than just addressing surface-level symptoms.
1. State the problem statement.
<template>
🟠 **PROBLEM**: <problem/>
</template>
</step>
2. Find the root-cause of by following the following iteration cycle. Start with a set equal to the .
<for items="1 2 3 4 5">
Ask <question/> and document the answer in <answer/> with the following template:
Don't stop at symptoms, keep digging for systemic issues.
Multiple root-causes may exist -- explore different branches.
Consider both technical, domain-specific, process-related or organizational causes.
<template>
⚪ **WHY <item/>**: <answer/>
</template>
Then, for the next iteration set <question/> now to be the last <answer/>.
The magic is NOT in exactly 5 "Why" -- you can <break/> the iteration
when you already reached the root-cause.
</for>
</step>
3. Validate the root-cause by working backwards the causality chain. Propose a solution that addresses and solves the root-cause. For the proposed solution, optionally directly propose corresponding source code changes.
<template>
🟠 **SOLUTION**: <solution/>
</template>
</step>
Adjust communication style in four intensivity levels of token usage. The <persona> can be either the decorative, eloquent, and explaining "writer", the concise, factual, and accurate "engineer" (default), the brief, factual, and abbreviating "telegrapher", the terse, rough and stuttering "caveman". Use when user says "persona <persona>" or "be <persona>".
Update changes entries in CHANGELOG.md files
Delete the current or given task plan. Use when the user calls to "delete", "remove" or "clear" the "task", "plan", "spec", or "specification".
Get or set unique task id <id>. Use when user requests to work on a certain task or wants to know what the current task is.
Implement current or given task plan. Use when the user calls to "implement", "realize" or "apply" the "task", "plan", "spec", or "specification".
Reboot the current or given task plan by re-creating it from scratch. Use when the user calls to "reboot", "recreate" or "refresh" the "task", "plan", "spec", or "specification".