Incident Communications

•
6
•

Drafts structured internal escalation notes, public status page updates, and blameless postmortems during active production outages.

Incident Communications provides product managers and incident responders with battle-tested communication templates grounded in Google SRE and Atlassian incident management practices. When production services degrade or break, this skill rapidly generates four critical, audience-specific artifacts: an internal escalation note with support holding lines, disciplined customer-facing status updates tied to committed update cadences, all-clear resolution announcements, and an executive-ready blameless postmortem. It eliminates the chaos of emergency comms by enforcing strict separation between internal debugging details and public messaging, preventing trust-eroding pitfalls like speculative ETAs or premature all-clears.

Características Principales

01Produces executive-level postmortems complete with plain-language timelines and accountable prevention action items
02Separates technical diagnostic details and internal blame from public user-facing impact statements
03Generates four discrete artifacts: internal escalations, customer status notes, all-clears, and blameless postmortems
04Enforces strict cadence management linked to severity levels (SEV1, SEV2, SEV3) to maintain stakeholder trust
05Includes self-contained, verbatim holding lines for customer support teams to minimize inbound escalation
066 GitHub stars

Casos de Uso

01Aligning internal stakeholders, support teams, and leadership with structured SEV escalation notes mid-outage
02Writing a blameless postmortem for executive leadership following incident mitigation and verification
03Drafting immediate status page updates and in-app error banners during unexpected production downtime