When something breaks in production or a project goes sideways, you need a structured way to figure out what happened without it turning into a blame session. This walks you through running a proper postmortem, helping you document the timeline, identify root causes, and extract actionable lessons. It's the kind of thing that separates teams that repeat mistakes from ones that actually learn. The framework keeps discussions productive and ensures you capture insights while they're fresh. Best used right after an incident when everyone's still around and the details haven't gotten fuzzy.
npx skills add https://github.com/alirezarezvani/claude-skills --skill postmortem