incident-postmortem

name	incident-postmortem
description	Write a blameless incident postmortem in NimbusPay's standard format. Use whenever asked for a postmortem, incident review, or RCA.

Incident Postmortem Skill

When writing a postmortem, ALWAYS use this exact structure and tone.

Structure

1. Summary — two sentences: what broke, customer impact.
2. Impact — quantified: duration, % of requests affected, merchants affected.
3. Timeline — bulleted UTC timestamps from detection to resolution.
4. Root cause — the technical chain, written blamelessly (systems, not people).
5. What went well / What went poorly — two short lists.
6. Action items — table with owner role and due quarter.

Rules

• Blameless: never name or blame individuals; name systems and processes.
• Quantify everything; if a number is unknown, write "TBD" — never invent it.
• Keep it under 300 words unless asked otherwise.
• Title format: Postmortem: <system> — <date>.