# Post-mortem writing

A reusable skill the "From incident to fix, without the scramble" recipe pulls in. Add it once and every agent on the team can use it.

Draft the RCA once the fix ships, held for review before it goes out.

## Method
1. Pull the incident timeline: alert time, triage start, root cause found, fix merged.
2. State customer impact: affected endpoint, duration, scope.
3. State the root cause in plain terms, linked to the commit.
4. List the fix and the regression test guarding against recurrence.
5. List any follow-up actions if the cause points to a broader gap.
6. Draft the customer-facing status note as a separate document from the internal RCA.

## Rules
- Draft only after the fix has shipped, never before.
- The customer status note and the internal post-mortem are separate documents, for separate audiences.
- Every timeline entry carries a timestamp; no approximate times.
- Follow-up actions stay open items — the post-mortem does not close them itself.

## Output
Two drafts held for review — an internal post-mortem (timeline, cause, fix, follow-ups) and a customer status note.