What problem does it solve? Teams ship AI-generated code faster but lack shared intelligence across the incident lifecycle, so the same failures recur and recovery work never compounds into prevention. This Skill applies PlayerZero-style compounding ROI methods—shared lifecycle graphs, prevention recipes, and hawk metrics—without buying any SaaS product. ## Core Features & Use Cases - Lifecycle handoff validation: Uses evaluate_lifecycle_handoff to require a shared context id across stages (sre, quality, review, planning) or fail closed. - Hawk metrics evaluation: Uses evaluate_hawk_metrics to rank work by WQTU, paywall attempt-to-success rate, incident recurrence, and escape rate instead of PR velocity. - Prevention recipes: Uses evaluate_prevention_recipe to encode every resolved incident as a pattern plus an executable gate, so recovery without a gate is rejected. - Use Case: After resolving a paywall incident where paywall_view events had zero purchase_attempt, run the compounding ROI script with the incident context id, recurrence metrics, and a gate command; the claim of compounding ROI is allowed only when every JSON check returns ok and the process exits 0. ## Quick Start Ask the assistant to evaluate whether your resolved incident qualifies as compounding ROI by running the compounding_roi script with your source stage, target stages, context id, metrics, pattern, and gate.
