← ClaudeAtlas

root-causelisted

Structured root cause analysis using WHERE (MECE decomposition) then WHY (causal structure diagrams) pipeline. Includes coin-flip detection, logical-leap detection, and vicious cycle intervention. Use when buffer enters YELLOW/RED, when metrics stall, or when Actions execute but don't produce results.
Ingramradical235/anty-framework · ★ 0 · AI & Automation · score 75
Install: claude install-skill Ingramradical235/anty-framework
# Root Cause Analysis (WHERE -> WHY) ## When to Apply - Buffer enters YELLOW or RED zone - Actions executed but metrics not moving (Layer 1 OK, Layer 2 stalling) - Significant KPI decline detected - Review engine Question 5 triggers (was root-cause analysis correct?) - Any time "why isn't this working?" is asked ## Core Framework ### Stage 1 — WHERE (Locate the Problem) MECE decomposition of the underperforming Goal into Drivers, identifying which specific Driver(s) are stalling. ``` Goal buffer: YELLOW (45% consumed, 34% progress) WHERE analysis (MECE decomposition by Driver): Social growth: 45% of target <- GAP HERE Referral program: 20% of target <- GAP HERE SEO content: 60% of target (on track) LP A/B testing: 30% of target (too early) Nurture emails: 10% of target (not started) Identified: Social growth and Referral are primary gaps. ``` **WHERE must complete before WHY begins.** This is strict and sequential. ### Stage 2 — WHY (Causal Structure Diagram) Starting from the WHERE-identified gap, build a causal structure by asking "Why?" iteratively, one layer at a time. Each node carries a verification status. ``` Social growth stalling (WHERE-identified gap) | +-- Post engagement declining [VERIFIED - analytics data] | +-- Content not resonating with ICP [HYPOTHESIS] | | +-- Tone mismatch [HYPOTHESIS] | | +-- Topic mismatch (features vs pain-points) [VERIFIED] | +-- Posting at wrong times