postmortem-writing

Draft blameless postmortems with root cause analysis and action items.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/act70255/SkillsBundle --skill postmortem-writing-act70255
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postmortem-writing
Source: https://github.com/act70255/SkillsBundle/tree/main/deployment/skills/postmortem-writing
Command: npx skills add https://github.com/act70255/SkillsBundle --skill postmortem-writing-act70255

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating detailed postmortems that analyze incident root causes and outline actionable improvements, enhancing incident response and organizational learning.

Core Features & Use Cases

  • Postmortem Drafting: Create comprehensive incident reports with structured timelines and root cause analysis.
  • Blameless Analysis: Facilitate a blameless culture with guidelines for timeline review and analysis.
  • Actionable Follow-up: Generate and track action items to prevent future incidents.

Quick Start

Run the 'postmortem-writing' skill to start a new postmortem document for a recent incident.

Frequently Asked Questions about postmortem-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a blameless postmortem for incident analysis?

To write a blameless postmortem, you draft comprehensive incident reports with structured timelines and root cause analysis, focusing on systemic issues rather than individual faults. This approach facilitates a blameless culture and generates actionable follow-up items.

What is root cause analysis in incident review processes?

Root cause analysis in incident review processes identifies the underlying systemic failures that led to an event. It involves structured incident documentation and timeline review to generate organizational learning and prevent future incidents.

How do I create actionable follow-up items after an incident?

You create actionable follow-up items by executing a structured postmortem analysis that identifies root causes and outlines actionable improvements. This process requires collaboration tools for tracking action items to prevent future incidents.

Can I use this approach for organizational learning after incidents?

Yes, you can use this approach for organizational learning after incidents. It streamlines creating detailed postmortems that analyze root causes and outline actionable improvements, directly enhancing incident response and organizational learning.

Does postmortem writing require specific collaboration tools?

Postmortem writing requires collaboration tools for tracking action items generated during the incident analysis. You need these tools to manage the structured approach to incident documentation and ensure actionable follow-up items are executed.

What is the best way to structure incident documentation for postmortems?

The best way to structure incident documentation for postmortems is using a structured analysis format that includes comprehensive timelines and root cause identification. This ensures the postmortem drafting process yields actionable insights for incident review.