incident-postmortem
Write a structured incident postmortem or post-incident review. Use when asked to write a postmortem, incident report, P1/P2 review, outage report, or RCA (root cause analysis). Produces a blameless postmortem with timeline, root cause, contributing factors, impact summary, and action items.
npx skills add mohitagw15856/pm-claude-skills --skill incident-postmortem --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Incident Postmortem Skill This skill produces a complete, blameless incident postmortem document following industry-standard format. Output enforces blameless framing throughout — system gaps over individual failures — and drives toward specific, closeable action items rather than vague process commitments. ## Proposes Actions The action items don't have to stay on the page: hand them to [`action-runner`](../action-runner/SKILL.md), which previews them (dry-run, risk-rated), runs only what you approve via the connected action MCP, and records what was done back to the brain. Typical: **file a follow-up issue per action item** (🟡), assigned to its owner with a due date. This skill proposes; action-runner gates and runs — never silently. ## Required Inputs Ask the user for these if not provided: - **Incident title / ID** - **Severity** (P1 / P2 / P3 or SEV1 / SEV2 / SEV3) - **Date and duration** of the incident - **What happened** (rough notes are fine — the skill will structure them) - **Services or systems affected** - **Customer impact** (how many users, what was degraded) - **How it was detected** - **How it was resolved** - **Initial thoughts on root cause** - **Action items
- Proposes Actions
- Required Inputs
- Reads from / Writes to the Brain
- Deeper Materials
- Output Format
- Executive Summary
- Impact
- Timeline
- Root Cause
- Detection
- Resolution
- Action Items
- What Went Well
- Lessons Learned
What does the incident-postmortem skill do?
Write a structured incident postmortem or post-incident review. Use when asked to write a postmortem, incident report, P1/P2 review, outage report, or RCA (root cause analysis). Produces a blameless postmortem with timeline, root cause, contributing factors, impact summary, and action items.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill incident-postmortem --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.