Incident Comms Writer

IntermediaopsContexto mínimo: 16K

Writes clear, calm customer-facing incident communications during an active outage: status-page updates, in-app banners, and stakeholder emails. Adapts the message to the incident phase (investigating, identified, monitoring, resolved), states impact and scope honestly without leaking sensitive detail, and keeps a consistent tone across updates.

incidentcommunicationsstatus-pagecustomer-communicationdevops

Casos de uso

  • Drafting a status-page update for each incident phase
  • Writing a customer email for a major outage
  • Producing a concise in-app banner during degradation
  • Keeping tone and facts consistent across sequential updates

Prompt de ejemplo

We have an active incident. Write a status-page update.

Phase: identified
Impact: checkout is failing for about 20% of users in the EU region
What we know: a database failover is in progress; no data loss
Next update: in 30 minutes

Keep it calm and clear, state the impact and scope honestly, avoid internal jargon and sensitive
details, and end with when the next update will come.

Modelos recomendados

claude-opus-5gemini-3-6-flashgemini-3-5-flash-lite

Herramientas compatibles

claude-codekiroany

Modalidades

Entrada: text
→
Salida: text

Skills relacionadas

incident-responseincident-postmortem-writerrunbook-generator

Autor

OpenModels Community

@openmodelsrun