Facilitate blameless postmortems with 5 Whys and fishbone diagrams.
npx skills add https://github.com/lyndonkl/claude --skill postmortem-lyndonkl
Please help me install this Agent Skill. Skill: postmortem Source: https://github.com/lyndonkl/claude/tree/main/skills/postmortem Command: npx skills add https://github.com/lyndonkl/claude --skill postmortem-lyndonkl
This Skill helps you conduct thorough, blameless postmortems to understand failures, identify root causes, and implement corrective actions, turning incidents into learning opportunities.
Use the postmortem skill to analyze the recent service outage and document lessons learned.
High-intent search queries and answers about installing and using this skill.
A blameless postmortem analysis focuses on systemic failures rather than individual blame to identify root causes. You document the incident timeline, quantify impact, and define actionable preventive measures with specific owners and deadlines.
Incident analysis root cause identification works best using structured methods like 5 Whys or fishbone diagrams. These techniques help uncover systemic process gaps and configuration errors rather than surface-level symptoms.
Tracking corrective actions to completion requires defining specific, owned, and time-bound preventive measures. You document lessons learned and monitor the corrective actions through resolution to support organizational learning.
You need a structured postmortem process after incidents, failures, or negative outcomes to prevent recurrence. It quantifies impact, identifies systemic root causes, and turns failures into learning opportunities through documented corrective actions.
Yes, 5 Whys and fishbone diagrams can be used together for root cause analysis. The postmortem process supports multiple structured methods to uncover systemic issues and define actionable preventive measures.
Building a blameless culture for incident analysis requires focusing on systems and processes, not individuals. The postmortem method facilitates transparency by identifying process gaps and defining corrective actions without assigning blame.
tclemCollect incident data, logs, and metrics into structured postmortem reports.
nimeshgurungManage CAPA workflows with root cause analysis and corrective action planning.
mverabAnalyze incident logs to identify error patterns and root causes.
leonardoteodorooGenerate blameless postmortems with root cause analysis, timelines, and action items.
