create-postmortem

Generate blameless postmortems with structured sections and action item owners.

6|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/GeneralJerel/chalk-skills --skill create-postmortem
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-postmortem
Source: https://github.com/GeneralJerel/chalk-skills/tree/main/skills/create-postmortem
Command: npx skills add https://github.com/GeneralJerel/chalk-skills --skill create-postmortem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Blameless postmortems are hard to write consistently; this skill streamlines the creation of structured incident retrospectives that focus on systemic factors and learning.

Core Features & Use Cases

  • Structured Postmortem Template: generates sections for Summary, Impact, Timeline, Contributing Factors, Safety Barriers, Action Items, What Went Well, and Recurrence Check.
  • Blameless Language Enforcement: promotes role-based descriptions to avoid naming individuals.
  • Action Item Governance: requires owner roles and due dates for each action to ensure follow-through.
  • Reuse & Recurrence Support: can reference previous incident reports to identify recurring themes and tie back to earlier postmortems.
  • Workflow Alignment: aligns with Google SRE-style postmortems and 5 Whys analyses to drive systemic improvements.

Quick Start

Draft a postmortem for the incident by outlining the timeline, contributing factors, safety barriers, action items, and what went well.

Frequently Asked Questions about create-postmortem

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

FAQPage Schema
How do I write a blameless postmortem for an engineering incident?▼

To write a blameless postmortem, generate a structured incident analysis enforcing role-based descriptions, documenting systemic factors across timeline, contributing factors, safety barriers, and action items to ensure follow-through.

What is the 5 Whys analysis in SRE postmortems?▼

The 5 Whys analysis in SRE postmortems iteratively asks why an incident occurred to uncover systemic root causes, aligning with blameless reviews to document contributing factors and implement safety barriers.

Can I reference previous incident reports to check for recurring themes?▼

You can reference previous incident reports during postmortem creation to identify recurring themes, tying current contributing factors and safety barriers back to earlier postmortems for continuous systemic improvement.

Does a blameless postmortem template require owners for action items?▼

A blameless postmortem template requires owner roles and due dates for all action items, enforcing action item governance to ensure accountability and follow-through on systemic improvements after the incident analysis.

What sections are needed for a Google SRE-style postmortem?▼

A Google SRE-style postmortem requires structured sections for Summary, Impact, Timeline, Contributing Factors, Safety Barriers, Action Items, What Went Well, and a Recurrence Check to document incident reviews comprehensively.

When should I not use a blameless postmortem approach?▼

A blameless postmortem approach should not be used when you need to address individual performance issues directly, as it focuses exclusively on role-based descriptions and systemic factors rather than personal accountability.