Writes a blameless incident post-mortem with root cause analysis
2-3 hrs → 15 min
Compared to doing it manually
/incident-post-mortemType this in Claude to run the skill
After incidents, teams either skip post-mortems (and repeat the same mistakes) or write blame-filled reports that make people defensive instead of learning.
.claude/skills/ folder in your project/incident-post-mortem in Claude to run the skillStructures sprint retrospectives with prompts, synthesis, and action items
Create CS playbooks with plays for onboarding, adoption, renewal, and expansion.
Documents team processes with quick reference checklists and detailed steps
Run structured team health checks to surface what is working and what is not.
A blameless post-mortem focuses on systems and processes, not individuals. The goal is to understand what happened and prevent recurrence — not to assign blame. Psychological safety enables honest analysis.
Include: incident summary, timeline, impact, root cause analysis (use "5 whys"), what went well, what went poorly, and concrete action items with owners and deadlines.
Download this skill and drop it in your .claude/skills/ folder.
This skill + 70+ more, context files, and agent workflows — $499