postmortem-writing

Generate structured blameless postmortems with templates and facilitator guidance.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/ekremmkasap/jarvis --skill postmortem-writing-ekremmkasap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postmortem-writing
Source: https://github.com/ekremmkasap/jarvis/tree/main/server/agent_prompts/wshobson/plugins/incident-response/skills/postmortem-writing
Command: npx skills add https://github.com/ekremmkasap/jarvis --skill postmortem-writing-ekremmkasap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Blameless postmortems are essential for organizational learning but teams often produce inconsistent or poorly structured reports that fail to drive improvements.

Core Features & Use Cases

  • Structured templates for standard postmortems and 5 Whys analyses
  • Facilitator guidance to run blameless incident reviews
  • Actionable templates and checklists to drive follow-up and learning
  • Use cases include incident reviews, root-cause analysis, post-incident meetings, and organizational learning

Quick Start

Provide a complete postmortem document using the included templates to structure a blameless investigation.

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 review?

A blameless postmortem focuses on systemic issues rather than individual fault, using structured templates and a facilitator guide to produce consistent incident reviews and actionable follow-ups that drive organizational learning across engineering teams.

What is the best way to run a root-cause analysis using the 5 Whys method?

Running a 5 Whys root-cause analysis involves applying structured templates during post-incident meetings to trace systemic failures. This process includes building a timeline and generating actionable follow-ups to ensure the engineering team learns from the incident.

Can I use standard templates for root-cause analysis and post-incident meetings?

Yes, you can use standard postmortem and 5 Whys templates to structure your root-cause analysis and post-incident meetings. These templates ensure consistent documentation and help facilitate a blameless review process across engineering teams.

Does this approach include facilitator guidance for blameless incident reviews?

Yes, this approach includes a facilitator guide to help run blameless incident reviews. The guidance ensures teams follow a structured process for root-cause analysis and produce actionable follow-ups without assigning individual blame.

How do I create actionable follow-ups after an incident management review?

You create actionable follow-ups after an incident management review by using structured templates and checklists. This ensures your postmortem documentation drives concrete learning and prevents similar engineering incidents from recurring.