What problem does it solve? Teams write success metrics at intake but rarely verify whether shipped features actually moved those numbers, leaving launch success as an unverified claim. This Skill closes the measurement loop by comparing realized post-launch data against the north-star and input metrics promised at business-context-intake. ## Core Features & Use Cases - Metric Verification: Reads the business-context document's north-star and input metrics, pulls realized values from cited re-runnable sources (dashboards, queries, analytics events), and renders moved / did-not-move / inconclusive verdicts per metric. - HEART-Aware Timing: Applies Google HEART framework timelines so metrics are not declared failed before their earliest meaningful read (1-2 sprints for engagement, 1-3 cohorts for retention). - Launch Decision: Rolls metric verdicts up into a Lean Startup persevere / iterate / kill decision and feeds it back to portfolio WSJF re-ranking. - Use Case: A checkout feature shipped 32 days ago with a promised 85% completion target. Run this Skill to pull the actual completion rate from the analytics dashboard, check PR-FAQ assumptions, and record an evidence-backed persevere or iterate decision. ## Quick Start Run the outcome-review skill on the feature that shipped last month to check whether its north-star metric moved against the intake target.
