postmortem-writing

Generate structured postmortem documents with root-cause analysis, timelines, and action items.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Postmortems are often inconsistent or prone to blame, making organizational learning slow. This Skill provides structured guidance, templates, and references to ensure root-cause analysis, timelines, and actionable follow-ups are captured effectively.

Core Features & Use Cases

  • Templates for problem statements, timelines, root-cause analysis, lessons learned, and action items.
  • Supports conducting post-incident reviews and documenting organizational learning for future prevention.
  • Provides a reference library to accelerate high-quality postmortems across teams.

Quick Start

Fill out a postmortem document using the templates to capture incident details, timelines, root causes, and action items.

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 for an incident?

A blameless postmortem focuses on root-cause analysis and systemic issues rather than individual fault. This Skill provides structured templates to document problem statements, timelines, lessons learned, and action items to drive organizational learning.

What is the best way to conduct a root-cause analysis during an incident review?

The best way to conduct root-cause analysis is using structured postmortem templates that capture the incident timeline and problem statement. This ensures you identify systemic failures and generate actionable follow-up items for future prevention.

What sections should be included in a post-incident review document?

A post-incident review document should include structured sections for the problem statement, root cause analysis, timeline, lessons learned, and action items. This Skill provides templates to ensure all critical sections are captured effectively.

How do I create incident timelines and track action items for postmortems?

You create incident timelines and track action items by filling out structured postmortem templates during incident reviews. This Skill helps capture chronological events and assigns follow-up items to drive improvements in incident response processes.

Can I use this postmortem template across different teams for incident documentation?

Yes, you can use these postmortem templates across different teams. The Skill provides a reference library and standardized structure for problem statements and root-cause analysis to accelerate high-quality, consistent organizational learning.

Why do postmortems fail to drive organizational learning?

Postmortems fail when they are inconsistent or prone to blame, which slows organizational learning. Using a structured, blameless approach with predefined sections for timelines and action items ensures incidents are documented effectively for future prevention.