What problem does it solve? After an outage, teams struggle to communicate with customers honestly: they either hide behind passive voice, bury bad news about data loss, name individual engineers, or make promises that never land. This Skill provides a proven structure and honesty rules for writing postmortems that preserve customer trust. ## Core Features & Use Cases - Structured Postmortem Template: Covers what happened in customer terms, UTC timeline with local notes, specific impact, honest root cause, remediation, and dated preventive changes. - Honesty and Tone Rules: Enforces active voice ("we deployed a change that..."), forbids naming individuals, and requires data loss or exposure to be disclosed in the first paragraph. - Commitment Discipline: Limits commitments to work already scheduled with an owner, and blocks overstated fixes or "it cannot happen again" promises. - Use Case: After a two-hour API outage that delayed customer webhook deliveries, use this Skill to draft a status-page postmortem that states the data delay upfront, explains the cause without internal detail, and lists only confirmed follow-up work. ## Quick Start Write a customer-facing postmortem for yesterday's 90-minute checkout outage that delayed order confirmation emails.
