doc-postmortem

Generate structured post-mortem documentation from predefined templates.

7|3|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/eriklieben/agentic-dev-workflow --skill doc-postmortem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-postmortem
Source: https://github.com/eriklieben/agentic-dev-workflow/tree/main/.claude/skills/doc-postmortem
Command: npx skills add https://github.com/eriklieben/agentic-dev-workflow --skill doc-postmortem

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill removes the friction and anxiety associated with incident reporting by providing a structured, blameless framework for documenting outages and production failures.

Core Features & Use Cases

  • Template-Driven Generation: Automatically populates standardized post-mortem structures based on project-specific templates.
  • Blameless Methodology: Enforces system-focused language and root-cause analysis to ensure constructive team learning.
  • Use Case: After a production incident, use this skill to quickly generate a report that captures the timeline, impact, and actionable items to prevent recurrence.

Quick Start

Ask the agent to generate a post-mortem for the recent database outage using the doc-postmortem skill.

Frequently Asked Questions about doc-postmortem

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

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

To generate a blameless post-mortem, the skill uses predefined templates to automatically populate standardized documentation structures focused on system-focused language and constructive team learning.

What is a blameless post-mortem and how does it improve incident response?

A blameless post-mortem is a structured incident report that enforces root-cause analysis and system-focused language. It improves incident response by capturing timelines, impact, and actionable items to constructively prevent recurrence.

How do I create incident reports across multiple repositories?

You can create incident reports across multiple repositories by resolving template paths via project configuration or local directory structures, allowing the skill to adapt to your specific multi-repository workflows.

What sections are required for a structured post-mortem document?

Structured post-mortem documents require specific sections for timelines, root causes, and actionable remediation items to ensure technical accuracy and accountability during incident analysis.

Can I use custom templates for documenting production outages?

Yes, you can use custom templates for documenting production outages. The skill automatically populates standardized post-mortem structures based on your project-specific templates.

Does generating incident documentation require external dependencies?

Generating incident documentation does not require external dependencies. The skill operates independently using scripts to resolve templates and output structured post-mortem reports.