Incident Postmortem
Use after a production outage, significant degradation, data incident, or near miss to reconstruct evidence, quantify impact, identify systemic causes without blame, and create owned, dated prevention actions.
Install
npx skills add sandbaseai/workbuddy-skill --skill incident-postmortemgit clone --depth 1 https://github.com/sandbaseai/workbuddy-skill.git /tmp/workbuddy-skill
mkdir -p ~/.claude/skills
cp -r /tmp/workbuddy-skill/skills/incident-postmortem ~/.claude/skills/incident-postmortemPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Incident Post-Mortem ## Purpose and boundary Create a blameless, evidence-backed review after a production outage, material degradation, data incident, or meaningful near miss. The goal is to understand how system and process conditions allowed the event, improve detection and recovery, and assign concrete prevention work—not to identify a person to blame. Use language such as “the system did not detect” or “the process lacked a guardrail.” Do not publish private logs, credentials, customer content, personal data, or unsupported speculation. Default to an authorized document draft; do not page people, create tickets, change production, or send communications unless separately authorized. ## Review contract and evidence Capture before writing: - incident title, severity convention, detection and resolution times with timezone; - incident commander or accountable reviewer and affected services/environments; - user, traffic, data, revenue, and SLA/SLO impact, with baseline and confidence; - source revision, deploy/config changes, alerts, logs, traces, tickets, chat, and status updates; - audience, redaction policy, retention, publication path, and unresolved evidence gaps. Prefer immutable links, event IDs, timestamps, query descriptions, and redacted excerpts. Preserve the distinction between observed fact, derived measurement, hypothesis, and unknown. When evidence conflicts, record both sources and explain the resolution or leave it unresolved.
Details
- Skill name
incident-postmortem- Repository
- sandbaseai/workbuddy-skill
- Path
skills/incident-postmortem/SKILL.md- License
- MIT
- Repo updated
- 8 September 2026
FAQ
What does the Incident Postmortem skill do?
Use after a production outage, significant degradation, data incident, or near miss to reconstruct evidence, quantify impact, identify systemic causes without blame, and create owned, dated prevention actions.
How do I install the Incident Postmortem skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add sandbaseai/workbuddy-skill --skill incident-postmortem. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Incident Postmortem popular?
It lives in sandbaseai/workbuddy-skill, which has 9 GitHub stars and 3 forks.
Related skills
Access Control Security Best Practices
9sandbaseai/workbuddy-skill
Design, review, implement, and verify least-privilege access controls across users, services, tenants, resources, and administrative workflows.
Accessibility Review
9sandbaseai/workbuddy-skill
Use when reviewing a web interface or interaction for semantic, keyboard, focus, screen-reader, ARIA, and contrast accessibility risks.
Acquire Codebase Knowledge
9sandbaseai/workbuddy-skill
Use when the user asks to map, document, or onboard into an existing codebase and needs evidence-backed architecture, structure, conventions, integrations, testing, and concerns documentation.
Incident Runbook Templates
9sandbaseai/workbuddy-skill
Use when creating or reviewing an incident runbook with detection, triage, authorized mitigation, escalation, verification, rollback, and communication boundaries.
Evidence Before Claims
9sandbaseai/workbuddy-skill
Use immediately before claiming work is complete, fixed, passing, committed, published, or ready for handoff; require fresh verification evidence matched to the claim.
Incident Triage
9sandbaseai/workbuddy-skill
Use when triaging incidents, production errors, alerts, latency, error rates, queue backlogs, job failures, logs, metrics, traces, or post-incident runbooks.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.