incident-commander

Incident severity assessment requires evaluating users affected, data risk, revenue impact, and workaround availability. This Skill guides you through classifying outages and major degradations to establish a clear severity rating for structured response prioritization.

Incident status updates should explain what is broken, who is affected, what mitigation action is underway, and when the next update will arrive. This Skill generates clear, non-technical stakeholder communications during active alert-driven response scenarios.

A blameless postmortem turns a resolved incident into a factual, timestamped timeline, root-cause analysis, impact summary, and actionable follow-ups with assigned owners. This Skill structures the postmortem process to focus on systemic factors rather than individual blame.

Yes, this Skill triages production outages like API 500 errors by applying structured impact assessment to determine severity, draft immediate status updates, and coordinate mitigation efforts with clear communication.

Incident response workflows for major degradations should follow a strict order: triage, severity assessment, stakeholder communication, and postmortem writing. This Skill enforces that sequence to maintain focus and speed during alert-driven response scenarios.