postmortem-writinglisted

# Postmortem Writing Use this skill when authoring or reviewing an incident report (IR) for the Lorekeeper project. Every incident must produce durable process improvements — not just a fix but encoding the lesson into review patterns and checklists. ## When to Use - A production incident occurs (P0/P1) - A CI pipeline breaks on `main` - A bug with systemic root cause (not a one-off typo) - The fix changes architecture patterns, not just code ## Mandatory Deliverables Every IR MUST deliver all of: | # | Deliverable | Location | Why | | --- | ------------------------------------------------------- | -------------------------------------------------- | -------------------------------------- | | 1 | `docs/incidents/IR-NNN-description.md` | Repo `docs/incidents/` | Permanent record | | 2 | BLOCKER pattern(s) added to `lorekeeper-code-reviewer` | `.hermes/skills/lorekeeper-code-reviewer/SKILL.md` | Prevents same bug class passing review | | 3 | Checklist items added to `github-code-review-checklist` | Skills directory | Catches in general review too | | 4 | Engineering docs (if the pattern needs explanation) | `docs/engineering/` | Reference for future readers | | 5 | Action items tracked to