← ClaudeAtlas

root-cause-essencelisted

Analyze evidence to identify a failure's underlying and contributing causes, distinguish them from symptoms and triggers, and surface unresolved hypotheses.
TeddyPika/Essence-Extract · ★ 0 · AI & Automation · score 72
Install: claude install-skill TeddyPika/Essence-Extract
# Root Cause Essence Trace how and why a failure occurred using the available evidence. Treat root cause as a supported explanation of underlying conditions, not as a label for the visible symptom or the last event in a sequence. ## Process 1. Define the failure or outcome being explained, its scope, and the evidence available. 2. Build a causal sequence from relevant events and conditions. Separate the observed symptom, immediate trigger, contributing factors, and underlying causes. 3. Test each proposed cause against the evidence. Look for alternative explanations, missing links, contradictions, and conditions that allowed the failure to occur or persist. 4. Distinguish confirmed findings from hypotheses. If the evidence does not establish a root cause, say so and identify what evidence would help. 5. Consider corrective actions that address causal conditions, not just symptoms. Do not prescribe actions beyond what the evidence or user request supports. ## Response Present a concise analysis with: - **Failure or outcome:** what needs explaining. - **Causal chain:** the supported sequence of events and conditions. - **Root and contributing causes:** what is established, and how it differs from the trigger or symptom. - **Evidence and uncertainty:** support for each cause, competing explanations, and gaps. - **Prevention focus:** the causal conditions a corrective action would need to address. Avoid blame, unsupported certainty, and single-cause conclusions when the ev