postmortem-writing

Create blameless postmortem documents with root-cause analysis and action items.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/vorynkavitaliy/openclaw-assistent --skill postmortem-writing-vorynkavitaliy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: postmortem-writing
Source: https://github.com/vorynkavitaliy/openclaw-assistent/tree/main/.agents/skills/postmortem-writing
Command: npx skills add https://github.com/vorynkavitaliy/openclaw-assistent --skill postmortem-writing-vorynkavitaliy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Blameless postmortems provide a structured, non-punitive framework to capture incident details, analyze root causes, and create actionable improvements that reduce recurrence.

Core Features & Use Cases

  • Standard templates for postmortems, including timelines, executive summaries, root-cause analysis, and action items
  • Facilitation guidance for blameless discussions and cross-team learning
  • Templates and best-practice guidance (e.g., 5 Whys analysis) to support consistent incident reviews

Quick Start

Schedule a blameless postmortem within 24–48 hours of an incident and follow the standard template to document timeline, root causes, and actionable follow-up items.

Frequently Asked Questions about postmortem-writing

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

FAQPage Schema
What is a blameless postmortem and when should I conduct one after an incident?▼

A blameless postmortem is a structured, non-punitive review to capture incident details and analyze root causes. You should schedule a blameless postmortem within 24 to 48 hours of an incident while details are fresh.

How do I write a postmortem document using root-cause analysis?▼

To write a postmortem document, use standard templates to map the incident timeline, apply root-cause analysis like 5 Whys, and document actionable follow-up items to drive cross-team learning and reduce recurrence.

What is the best way to facilitate a blameless postmortem meeting across engineering and operations teams?▼

The best way to facilitate a blameless postmortem is to follow provided facilitation guidance and templates, ensuring discussions remain non-punitive and focus on extracting learning and creating actionable improvements across teams.

Can I use these postmortem templates for product incident reviews, or are they only for engineering operations?▼

You can use these postmortem templates across engineering, operations, and product teams. The framework applies broadly to any incident review requiring a timeline, executive summary, and actionable follow-up items.

Does blameless postmortem methodology work with 5 Whys analysis for root-cause investigation?▼

Yes, blameless postmortem methodology works with 5 Whys analysis. The framework provides best-practice guidance specifically supporting 5 Whys to ensure consistent root-cause investigation during incident reviews.