Customer Outage Notice Skill

During an outage, customers don't need engineering detail — they need to know you're aware, that you're on it, and when you'll update them next. This skill writes the notifications across the whole incident lifecycle, in calm, plain language that reduces support tickets instead of generating them. (For a security/data incident or a PR crisis, use incident-public-statement or pr-crisis-response.)

Working from a brief

Given "checkout is down for some users", produce the full set of phased notices anyway — infer the affected scope and a plausible update cadence, label assumptions, and bracket the specific facts (start time, services, ETA) to fill in. Never wait for full detail; teams paste these live and edit the brackets.

Required Inputs

Ask for these only if they aren't already provided (else infer and label):