What problem does it solve? When an alert fires, teams often waste the critical first minutes debating causes instead of assessing impact. This Skill provides a structured triage method that turns an alert into a severity level, a named owner, and a disprovable first hypothesis within minutes. ## Core Features & Use Cases - Ordered impact assessment: Answers four questions in sequence — who is affected, what is broken, since when, and whether it is getting worse — to establish blast radius before cause. - Impact-based severity setting: Assigns severity from user impact rather than from a known cause, with a single named owner instead of a team. - Testable first hypothesis: Names the most recent change touching the failing path and defines how to disprove it in under five minutes. - Use Case: An on-call engineer receives a latency alert for one region. The Skill walks them through scoping the impact, declaring a severity with reasoning, identifying the last deployment on that path as the hypothesis, and posting a status update with a committed next update time. ## Quick Start Triage this alert: error rate spiked on the payments endpoint in eu-west starting 20 minutes ago, right after deploy 1.4.2.
