post-mortem-writing

Draft blameless incident post-mortems with required sections and action items.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ohsonerdy/openclaw-frontier-stack --skill post-mortem-writing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-mortem-writing
Source: https://github.com/ohsonerdy/openclaw-frontier-stack/tree/main/skills/post-mortem-writing
Command: npx skills add https://github.com/ohsonerdy/openclaw-frontier-stack --skill post-mortem-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill produces a complete, blameless incident post-mortem draft after mitigation so teams document what happened, why it happened, and what will prevent recurrence—without turning the write-up into a blame exercise.

Core Features & Use Cases

  • Blameless framing guidance: Rewrites findings to focus on system conditions and actions, not evaluative blame of individuals.
  • Required-section structured output: Generates a full document draft with Summary, Impact, Timeline, Root cause and contributing factors, What went well, What went poorly, Action items, Open questions, and Distribution list.
  • Action-item discipline: Ensures every action item includes an owner, real due date, severity of skip, and a “would this have prevented it” justification, grouped by RCA bucket.
  • Audience-aware distribution: Adapts distribution recommendations for affected teams, leadership, and customer-facing needs.

Quick Start

Use this skill after a Sev 1 or Sev 2 incident is mitigated and you have the completed RCA, asking it to draft a complete post-mortem with action items marked as needs input where details are missing.

Frequently Asked Questions about post-mortem-writing

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

FAQPage Schema
How do I write a blameless incident post-mortem after a Sev 1 or Sev 2 mitigation?

To draft a blameless incident post-mortem, structure the document with required sections including Summary, Impact, Timeline, and Root Cause. Focus on system conditions rather than individual blame to drive operational excellence.

What sections are required in a blameless RCA post-mortem document?

Required sections include Summary, Impact, Timeline, Root cause and contributing factors, What went well, What went poorly, Action items, Open questions, and Distribution list. This structure drives clear ownership and operational excellence.

How do I format action items in an incident post-mortem to ensure follow-through?

Format incident post-mortem action items with an assigned owner, real due date, severity of skip, and a prevention justification. Group these items by RCA bucket to ensure accountability and operational excellence.

Can I draft a post-mortem for a near-miss or recurring incident class?

Yes, blameless post-mortem drafting applies to Sev 1/2/3 pattern incidents, near-misses, and recurring incident classes. It structures impact and timeline details while enforcing clear ownership and follow-through.

What is the best way to distribute an incident post-mortem to affected teams and leadership?

Distribute an incident post-mortem using audience-aware recommendations tailored for affected teams, leadership, and customer-facing needs. This ensures stakeholders receive appropriate context for operational excellence.

What should I do if I am missing details for certain action items during the post-mortem draft?

When missing details for action items during a post-mortem draft, mark them as needing input. The drafting process avoids inventing missing details and outputs open questions for later resolution.