postmortem-writing

Generates structured, blameless postmortem documents for incident reviews.

Updated Dec 23, 2025
One-click install
npx skills add https://github.com/drgaciw/academic-compliance-hub-glm --skill postmortem-writing-drgaciw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postmortem-writing
Source: https://github.com/drgaciw/academic-compliance-hub-glm/tree/main/agents/plugins/incident-response/skills/postmortem-writing
Command: npx skills add https://github.com/drgaciw/academic-compliance-hub-glm --skill postmortem-writing-drgaciw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams conduct thorough incident reviews and create effective, blameless postmortem documents to foster organizational learning and prevent future incidents.

Core Features & Use Cases

  • Blameless Culture Guidance: Provides principles for a non-punitive review process.
  • Incident Triggers: Defines criteria for when a postmortem is necessary.
  • Templates: Offers structured templates for standard, 5 Whys, and quick postmortems.
  • Facilitation Guide: Includes a meeting structure and tips for running effective postmortem discussions.
  • Use Case: After a critical service outage, use this Skill to guide the team through writing a comprehensive postmortem that identifies root causes and generates actionable follow-up items.

Quick Start

Use the postmortem-writing skill to generate a standard postmortem document for an 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 after an incident response?

To write a blameless postmortem, use structured templates that guide root cause analysis, timeline reconstruction, and action item generation while focusing on systemic issues rather than individual blame.

When should our team create an incident postmortem document?

You should create an incident postmortem document after critical service outages or significant incidents, using defined incident triggers to determine when a formal review and root cause analysis is necessary.

What is the 5 Whys technique for root cause analysis in postmortems?

The 5 Whys technique for root cause analysis in postmortems is a structured questioning method that helps teams iteratively ask why an incident occurred to identify the underlying systemic causes.

How do I facilitate a blameless postmortem meeting for root cause analysis?

To facilitate a blameless postmortem meeting, follow a structured meeting guide that provides principles for a non-punitive review process and tips for running effective incident response discussions.

What are the best templates for incident postmortem documentation?

The best templates for incident postmortem documentation include standard, 5 Whys, and quick postmortem formats, each offering structured sections for timeline reconstruction and action item generation.

Can I use a quick postmortem template for minor incidents instead of a full review?

Yes, you can use a quick postmortem template for minor incidents, which provides a streamlined structure for root cause analysis and action item generation without the depth of a standard postmortem.