post-mortem

Generate blameless post-mortem reports from incident data using a standard template.

2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/kscius/KS-Cursor-Orchestrator --skill post-mortem-kscius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-mortem
Source: https://github.com/kscius/KS-Cursor-Orchestrator/tree/main/skills/post-mortem
Command: npx skills add https://github.com/kscius/KS-Cursor-Orchestrator --skill post-mortem-kscius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Incident post-mortems are often manual, inconsistent, and time-consuming to produce. This skill automatically generates a structured, blameless post-mortem document from incident data, ensuring a consistent format and actionable outcomes.

Core Features & Use Cases

  • Automatically compiles timeline, root cause, contributing factors, and action items into a standard template.
  • Generates a ready-for-review document that can be shared with stakeholders and archived for knowledge retention.
  • Use case: after a production incident, provide incident notes and let this skill produce the final post-mortem for review.

Quick Start

Provide incident details (timeline, impact, and findings) and let the skill generate a structured post-mortem.

Frequently Asked Questions about post-mortem

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

FAQPage Schema
How do I write a blameless post-mortem after a production incident?

To write a blameless post-mortem, compile your incident notes, timeline, and root cause findings. The skill uses this input to automatically generate a structured report documenting contributing factors and action items for team review.

What is a blameless post-mortem and what should it include?

A blameless post-mortem is an incident report focusing on systemic issues rather than individual fault. It should include an incident timeline, root causes, contributing factors, and actionable items to prevent recurrence.

How do I generate an incident retrospective document from raw timeline notes?

You generate an incident retrospective by providing raw timeline notes, impact details, and findings. The skill compiles this data into a standard post-mortem template, outputting a ready-for-review document for stakeholders.

Can I automatically format root-cause analysis findings into a standard template?

Yes, you can format root-cause analysis findings by feeding them into the skill. It applies a standard post-mortem template to your data, producing a structured document with timeline, causes, and action items.

What is the best way to document contributing factors and action items for an outage?

The best way to document contributing factors and action items for an outage is using a structured post-mortem. Provide your incident data, and the skill compiles it into a standardized, blameless report for knowledge retention.

Does this post-mortem generator require specific incident management platform data?

No specific platform data is required. You simply provide incident details like timeline notes, impact descriptions, and root cause findings, and the skill generates the blameless post-mortem document without platform dependencies.