Document blameless postmortems with timelines, 5 Whys, and action items.
npx skills add https://github.com/qa-aman/claude-skills --skill postmortem-qa-aman
Please help me install this Agent Skill. Skill: postmortem Source: https://github.com/qa-aman/claude-skills/tree/main/skills/by-role/devops/postmortem Command: npx skills add https://github.com/qa-aman/claude-skills --skill postmortem-qa-aman
Blameless postmortems provide a structured way to learn from incidents without blaming individuals, turning incidents into actionable improvements.
Schedule a blameless postmortem within 48 hours of SEV1 and follow the template to capture the timeline, contributing factors, and concrete action items.
High-intent search queries and answers about installing and using this skill.
A blameless postmortem captures a structured incident timeline, contributing factors, 5 Whys analysis, action items with owners, and lessons learned to drive system-level improvements without blaming individuals.
5 Whys analysis in incident management identifies systemic causes by repeatedly asking why, moving beyond surface symptoms to uncover root contributing factors without naming individuals, driving system-level improvements.
Schedule a postmortem within 48 hours of SEV1 or SEV2 incidents to preserve context, capture lessons learned, and prevent recurrence while events are fresh.
Yes, the blameless postmortem template applies to incident responses across projects or teams, covering SEV1 and SEV2 incidents with defined timelines and structured action-item workflows.
The best way to track action items from an incident postmortem is to translate insights into concrete tasks with clear ownership and specific due dates to ensure accountability and prevent recurrence.
tclemCollect incident data, logs, and metrics into structured postmortem reports.
eddowdingExtract action items and draft follow-up emails from meeting notes.
sigmadigitalzaDraft and review blameless post-incident reports from incident artifacts.
vecearGenerate post-incident reports with timelines, root causes, and action items.
