neurofoo/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.
npx skills add https://github.com/neurofoo/agent-skills --skill postmortem
Conduct a thorough, blameless analysis of an incident to understand what happened and prevent recurrence.
Work through each section systematically. Focus on systems and processes, not individuals. The goal is learning, not blame.
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]
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
Customer Impact
Business Impact
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?
| What Worked | Why It Helped |
|-------------|---------------|
| [thing] | [explanation] |
| What Failed | Impact |
|-------------|--------|
| [thing] | [impact] |
Immediate (This week)
| Action | Owner | Due |
|--------|-------|-----|
| [action] | [owner] | [date] |
Short-term (This month)
| Action | Owner | Due |
|--------|-------|-----|
| [action] | [owner] | [date] |
$ARGUMENTS
Take neurofoo/postmortem from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.