statuspage-and-comms-ops

Incident communications for an AI SaaS outage require strict audience separation, routing internal operational updates differently from customer-safe status page messages. This skill drafts those distinct messages while enforcing update cadence and ETA discipline for both groups.

Update cadence and ETA discipline during service degradation are maintained by enforcing scheduled communication intervals and realistic recovery timelines. This skill manages approval ownership and generates cadence-compliant templates to ensure timely, accurate customer-facing updates.

Planned maintenance and post-incident recovery messaging are fully supported alongside real-time outage responses. The skill applies customer-safe wording and clear next steps to draft closure messaging, ensuring consistent communications operations across all incident types.

Routing approvals for status page updates involves designating communication ownership and enforcing approval workflows before external publication. This skill structures the approval routing process to ensure all customer-safe templates and incident updates are reviewed by the correct stakeholders.

Customer-safe wording in incident communications prevents panic, avoids speculative technical blame, and maintains trust during outages. This skill enforces customer-safe wording directly within its status page templates and degradation messaging drafts.

Automated incident communication templates cannot replace real-time engineering diagnostics or dynamic internal decision-making during complex AI service outages. This skill provides structurally safe messaging frameworks and cadence enforcement, but requires human approval ownership before external publication.