postmortem-blameless-write-up
/postmortem-blameless-write-up
Write the postmortem without naming culprits, so the record focuses on what the system permitted rather than on whom it embarrassed. Use when the incident is closed and a shared learning document is expected to prevent the next occurrence
- Author
- Wsh7Ash ↗
- Repository
- patchwise ↗
- Licence
- MIT
- Last repository change
- 28.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Write the postmortem without naming culprits, so the record focuses on what the system permitted rather than on whom it embarrassed. Use when the incident is closed and a shared learning document is expected to prevent the next occurrence
Original author description
Write the postmortem without naming culprits, so the record focuses on what the system permitted rather than on whom it embarrassed. Use when the incident is closed and a shared learning document is expected to prevent the next occurrence
How it works
- Procedure
- Signals
- Patterns
- Pitfalls
- Done when
- References
SKILL.md preview
--- name: postmortem-blameless-write-up description: "Write the postmortem without naming culprits, so the record focuses on what the system permitted rather than on whom it embarrassed. Use when the incident is closed and a shared learning document is expected to prevent the next occurrence" pack: patchwise version: 1.0.0 category: defensive-security tags: [postmortem, blameless, process] --- # Blameless Postmortem Write-Up > Write the postmortem without naming culprits, so the record focuses on what the system permitted rather than on whom it embarrassed **Use when:** the incident is closed and a shared learning document is expected to prevent the next occurrence **Avoid when:** the organization already tracks learning elsewhere, and a second postmortem would duplicate existing records ## Procedure 1. Reconstruct the timeline factually, with timestamps, and specify what each step of evidence confirmed at the time. 2. Narrate the system's state at each point: what checks existed, what monitoring was watching, what permissions were exercised. 3. Analyze contributing factors without naming individuals, and prefer phrasing like 'the interface permitted' over 'engineer X missed'. 4. Track each action item: what it addresses, who owns it, when it lands and when it is verified to have landed. 5. Pre-register what would make the same incident recur, turning vague bet-hedging into a concrete follow-up. 6. Share the postmortem with the people who will use it: responders, reviewers and maintainers of the affected surface. ## Signals - Action items from the postmortem drift toward non-technical or hypothetical once they begin landing later. - Timeline facts do not match the fix record, indicating two contradictory truths one needs to be authoritative. - The postmortem skips pre-registering recurrence conditions, so vague claims ride freely without facing rules. - Same-class defect reappears with no correspondence to any of the postmortem's pre-registered recurrence signals. ## Patterns **1. Timeline** ```text T-0 report accepted T+2h triage T+6h contained T+2d fix shipped T+3d verified T+4d disclosed ``` **2. Contributing** ```text system permitted query w/o owner filter monitoring had no detection rule playbook missing ``` **3. Action item** ```text AC-01: query lint rule, owner: platform, due 2026-11-15, verified on merge ``` ## Pitfalls - Writing postmortem culprits into a document that is otherwise blameless, which restores the shame geometry in one paragraph. - Recording action items without owners, which converts the postmortem into an aspiration rather than a plan. - Failing to distinguish between the timeline and the judgments, so future readers cannot tell evidence from narrative. ## Done when - The postmortem carries a factual timeline, narrative system state, contributing factors and no individual blame. - Every action item has an owner, a due date and a verification path, and recurrence signals are pre-registered rather than vague. ## References - [Google SRE - postmortem culture](https://sre.google/sre-book/postmortem-culture/) - [NIST SP 800-61 - incident response](https://csrc.nist.gov/pubs/sp/800/61/r2/final)
Versions
The database has no other skills named postmortem-blameless-write-up.
Database snapshot: 13.11.2026 · package version 5eccf37635dd (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100create-postmortem
Create a blameless postmortem when the user asks to write a postmortem, document what went wrong, analyze an incident, or run a 5 Whys analysis - 90incident-postmortem
Write a blameless postmortem or incident report from logs, alerts, chat transcripts, tickets and notes. Use when the user says "write the postmortem", "incident report", "RCA", "what happened during the outage", or pastes an incident timeline or Slack thread. - 100postmortem
Write a blameless postmortem after an incident. Use when the user says "postmortem", "post-incident review", "PIR", "what happened in that incident", "incident review", "blameless postmortem", "5 whys", "how do we prevent this again", or needs to document learnings from a… - 100ops-postmortem
Use when a SEV1 or SEV2 incident is over. Write a blameless postmortem with the timeline, the contributing factors, and action items that each have an owner and a date. - 100incident-postmortem-blameless-rca-authoring
Use this skill when facilitate and author blameless incident postmortems identifying timeline and actionable fixes. - 100incident-postmortem
Write a blameless postmortem after a production incident is resolved. Use for an RCA, or when the user says postmortem/RCA/writeup. Produces timeline, 5-whys root cause, and tracked action items.