postmortem-writing

Write structured postmortems with timelines, root causes, and action items.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/Sumeet138/qwen-code-agents --skill postmortem-writing-sumeet138
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postmortem-writing
Source: https://github.com/Sumeet138/qwen-code-agents/tree/main/plugins/incident-response/skills/postmortem-writing
Command: npx skills add https://github.com/Sumeet138/qwen-code-agents --skill postmortem-writing-sumeet138

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Blameless postmortems are essential for turning incidents into learning opportunities, capturing root causes, timelines, and actionable follow-ups without assigning blame.

Core Features & Use Cases

  • Templates for Postmortem (including executive summary, timeline, root cause, and action items)
  • Facilitation guidance and best practices to run blameless reviews
  • Structured knowledge for organizational learning and process improvement

Quick Start

Draft a blameless postmortem for the most recent incident using the provided templates and share the final report with stakeholders.

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 how does it help with incident response?

A blameless postmortem is a structured incident review that captures timelines, root causes, and action items without assigning blame. It transforms incidents into organizational learning opportunities for process improvement.

How do I write a postmortem that captures root causes and action items?

To write a postmortem, use a structured template to document the executive summary, incident timeline, root-cause-analysis, and actionable follow-up items. This standardizes documentation across engineering teams.

Can I use a standardized template for engineering incident reviews?

Yes, standardized postmortem templates facilitate consistent documentation across engineering teams. Templates typically include sections for the executive summary, timeline, root cause, and action items.

What is the best way to run a blameless retrospective after an incident?

The best way to run a blameless retrospective is to follow provided facilitation guidance and best practices. This ensures reviews focus on systemic root causes and process improvement rather than individual blame.

Does this approach work for organizational learning across multiple engineering teams?

Yes, applying blameless postmortems enables standardized templates and consistent documentation across engineering teams. This creates structured knowledge for organizational learning and ongoing process improvement.