postmortem
Blameless post-mortem incident analysis with timeline, root cause, and action items. Use after outages, security incidents, project failures, or any event you want to prevent recurring.
Best use case
postmortem is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Blameless post-mortem incident analysis with timeline, root cause, and action items. Use after outages, security incidents, project failures, or any event you want to prevent recurring.
Teams using postmortem should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/postmortem/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How postmortem Compares
| Feature / Agent | postmortem | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Blameless post-mortem incident analysis with timeline, root cause, and action items. Use after outages, security incidents, project failures, or any event you want to prevent recurring.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Blameless Post-Mortem Conduct a thorough, blameless analysis of an incident to understand what happened and prevent recurrence. ## Instructions Work through each section systematically. Focus on systems and processes, not individuals. The goal is learning, not blame. ### Output Format ## Executive Summary **Incident**: [One-line description] **Date/Time**: [When it occurred] **Duration**: [How long] **Severity**: [Critical/High/Medium/Low] **Summary** [2-3 sentence overview: what happened, impact, resolution] --- ## Timeline All times in [timezone]. | Time | Event | Actor | |------|-------|-------| | HH:MM | [What happened] | [Who/what did it] | | HH:MM | [Detection] | [How it was noticed] | | HH:MM | [Response action] | [Who responded] | | HH:MM | [Resolution] | [What fixed it] | **Key Moments** - **Trigger**: [What initiated the incident] - **Detection**: [How/when we knew something was wrong] - **Mitigation**: [When bleeding was stopped] - **Resolution**: [When fully resolved] --- ## Impact **Customer Impact** - Users affected: [number] - Duration of impact: [time] - Symptoms experienced: [what users saw] **Business Impact** - Revenue impact: [if applicable] - SLA/SLO breach: [yes/no, details] --- ## Root Cause Analysis **Root Cause** [The fundamental reason this happened—not the trigger, but why the trigger caused an incident] **Trigger** [The immediate cause—what set things in motion] **Contributing Factors** | Factor | How It Contributed | |--------|-------------------| | [factor] | [explanation] | **Why Wasn't This Caught?** - Why didn't tests catch it? - Why didn't monitoring alert earlier? --- ## What Went Well | What Worked | Why It Helped | |-------------|---------------| | [thing] | [explanation] | --- ## What Went Poorly | What Failed | Impact | |-------------|--------| | [thing] | [impact] | --- ## Action Items **Immediate** (This week) | Action | Owner | Due | |--------|-------|-----| | [action] | [owner] | [date] | **Short-term** (This month) | Action | Owner | Due | |--------|-------|-----| | [action] | [owner] | [date] | --- ## Lessons Learned 1. [lesson] 2. [lesson] 3. [lesson] --- ## Guidelines - **Blameless**: "The deploy script didn't validate" not "Alice deployed without checking" - **Thorough timeline**: Include everything, even embarrassing delays - **Specific actions**: "Add memory alerting" not "Improve monitoring" - **Assigned owners**: Unowned actions don't happen $ARGUMENTS
Related Skills
postmortem-writing
Write effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response proce...
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
update-oo-component-documentation
Update existing object-oriented component documentation following industry best practices and architectural documentation standards.
tailored-resume-generator
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
sync-docs
Sync documentation with code. Use when user asks to update docs, check docs, fix stale documentation, update changelog, or after code changes.
social-content
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn...
scientific-writing
Core skill for the deep research and writing tool. Write scientific manuscripts in full paragraphs (never bullet points). Use two-stage process with (1) section outlines with key points using research-lookup then (2) convert to flowing prose. IMRAD structure, citations (APA/AMA/Vancouver), figures/tables, reporting guidelines (CONSORT/STROBE/PRISMA), for research papers and journal submissions.
readme
When the user wants to create or update a README.md file for a project. Also use when the user says 'write readme,' 'create readme,' 'document this project,' 'project documentation,' or asks for he...
readme-blueprint-generator
Intelligent README.md generation prompt that analyzes project documentation structure and creates comprehensive repository documentation. Scans .github/copilot directory files and copilot-instructions.md to extract project information, technology stack, architecture, development workflow, coding standards, and testing approaches while generating well-structured markdown documentation with proper formatting, cross-references, and developer-focused content.
plan-writing
Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.
mkdocs-translations
Generate a language translation for a mkdocs documentation stack.