blameless-post-mortem

# blameless-post-mortem > Facilitate a blame-free post-mortem after an incident or near-miss. > Consumes the `incident-commander` skeleton, derives or fills the root > cause, writes the corrective-action plan, and drafts an > `incident-learnings` memory candidate. Systems and processes are > examined — never individuals. ## When to use - An incident or outage is resolved and the team needs a structured write-up. - A near-miss happened and a post-mortem is being drafted (near-miss mode — same flow, different severity framing). - The `incident-commander` hands off a post-mortem skeleton (empty root cause is accepted — do not block on it). - German triggers: "Post-mortem", "Nachbesprechung", "was ist schiefgelaufen?", "Vorfallsanalyse". Do NOT use when: - The incident is still active — route to [`incident-commander`](../incident-commander/SKILL.md) first. - The goal is root-cause analysis only, no write-up needed — route to [`root-cause-frameworks`](../root-cause-frameworks/SKILL.md). - The concern is a future risk, not a past event — route to [`risk-officer`](../risk-officer/SKILL.md). ## Procedure ### 1. Consume the incident-commander skeleton Read the incoming skeleton. Per [`docs/contracts/analysis-memory-loop.md § 5`](../../docs/contracts/analysis-memory-loop.md): - Accept any skeleton, complete or not. - Extract: `SEV`, `State`, `Started`, `Timeline`, `Mitigation`, `Root cause` (may be `unknown` or TBD). - Do NOT stall or reject on an empty root ca...