Individual skill
postmortem
A blameless incident postmortem: summary with impact numbers, a timeline, root cause and contributing factors, what went well and badly, and action items with owners.
packages/content/assets/open-design/skills/postmortem/SKILL.md
Source commit 400641fd6781fa0febad445984ee76440374736d
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,044
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- codex Repository topic
- cursor Repository topic
- dashboard Repository topic
- design Repository topic
- design-systems Repository topic
- design-tokens Repository topic
- figma Repository topic
- github-copilot Repository topic
- mcp Repository topic
- postmortem Declared skill tag
- incident Declared skill tag
- retrospective Declared skill tag
- sre Declared skill tag
- outage Declared skill tag
- 事故复盘 Declared skill tag
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
.od-local-overlayasset · 82 bytesSKILL.mdcore · 3,738 bytes
Read excerpt
# Postmortem
**Intent.** A blameless account of an incident that helps the team learn and prevents a repeat. It describes systems and decisions, never blames people.
## Ground it
Write only what the sources say. Gather them yourself before writing a word:
- the incident notes, chat or pager timeline, and dashboards the user provides. Ask for them if they're missing: **never invent an incident, a timestamp or an impact number**;
- the commits that caused and fixed it (`git log --since … --until …`, `git show <sha>`), and the code paths involved.
Keep the list of files, commits and refs you read: they go in a **Sources** section at the bottom of the page and in `sources` when you register (`register_open_design_artifact` with kind `html`). If something the document needs isn't in the sources, ask the user, or mark it plainly as an open question. Never invent numbers, dates, names or quotes.
## Structure