← ClaudeAtlas

review-enginelisted

5-question review framework (result, execution, plan, strategy, analysis), KPI propagation monitoring with 4-layer anomaly patterns, One-Way/Two-Way Door classification, withdrawal decision protocol, and assumption provenance auditing. Use during periodic reviews, buffer zone changes, or when evaluating why results diverge from expectations.
Ingramradical235/anty-framework · ★ 0 · AI & Automation · score 75
Install: claude install-skill Ingramradical235/anty-framework
# Review Engine ## When to Apply - After each periodic scan - When buffer zone changes - When Actions complete but Goal doesn't progress - Quarterly strategy reviews - When the founder asks "why isn't this working?" ## Core Framework ### 5-Question Review (Strict Priority Order) Start at Question 1. Only proceed deeper if the answer is "yes" (problem isn't at that level): | Priority | Question | Scope | If "No" | |---|---|---|---| | 1 | Has the Goal progressed since last review? | WHERE | Re-run WHERE analysis to locate new gap | | 2 | Were approved Actions executed as planned? | Execution | Investigate blockers, check relay runner compliance | | 3 | Was the Action plan well-constructed? | Planning | Review Step breakdown, batch config, template fit | | 4 | Were the chosen Actions appropriate? | HOW | Re-run 3-option choice with different approaches | | 5 | Was the root-cause analysis correct? | WHY | Rebuild causal structure diagram from scratch | This prevents the common trap of never questioning upstream assumptions. ### KPI Propagation Monitoring (4-Layer) Actions are monitored for whether effects propagate upward through the causal chain: ``` Action: "Post 4 thought-leadership threads per week" | KPI Layer 1 (Execution): Threads posted per week -> "Is the Action being executed?" (target: 4/week) | KPI Layer 2 (Propagation): Engagement rate per thread -> "Is it producing the expected intermediate effect?" | KPI Layer 3 (Driver metric): Monthly new