postmortem

Name: postmortem
Availability: InStock
Author: Prestarius

Synthesize a blameless incident postmortem with impact, timeline, and follow-up actions.

1|Updated Jun 9, 2026

Search Tags:#timeline #adr #postmortem #follow-up #incident #blameless #to-issues

Ready to run

npx skills add https://github.com/prestarius/jet-skills-stack --skill postmortem-prestarius

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: postmortem
Source: https://github.com/prestarius/jet-skills-stack/tree/main/skills/postmortem
Command: npx skills add https://github.com/prestarius/jet-skills-stack --skill postmortem-prestarius

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write a blameless incident postmortem that clearly documents impact, timeline, contributing factors, and actionable follow-up decisions.

Core Features & Use Cases

Structured incident reports capturing Summary, Timeline, Contributing factors, What went well/poorly, and Follow-up actions.
Enables blameless culture and traceable workflow integration (to-issues, ADRs).
Suitable for post-incident reviews across teams to improve reliability and learning.

Quick Start

Provide incident details and run the postmortem skill to generate a structured blameless report.

Frequently Asked Questions about postmortem

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

FAQPage Schema

How do I write a blameless incident postmortem that captures impact and timeline?▼

To write a blameless incident postmortem, synthesize incident data into a structured report capturing Summary, Timeline, Contributing factors, What went well/poorly, and Follow-up actions using only verifiable facts.

What is the best way to document contributing factors in an incident report?▼

Documenting contributing factors in an incident report requires structuring them within a blameless postmortem, clearly separating what went well from what went poorly to drive actionable follow-up decisions.

How do I generate follow-up actions and convert postmortem findings to issues?▼

Generate follow-up actions by synthesizing incident data into a structured postmortem report, then apply to-issues integration guidelines to convert actionable findings into tracked tickets.

Can I integrate architectural decision records into a post-incident review?▼

Yes, you can integrate architectural decision records into a post-incident review by applying ADR integration guidelines during blameless postmortem synthesis to trace follow-up decisions.

How should I handle missing data when creating an incident timeline?▼

When creating an incident timeline with missing data, clearly mark unknowns with TODO placeholders rather than guessing, ensuring the blameless postmortem relies strictly on verifiable facts.

Does this postmortem process work for outage diagnosis sessions across teams?▼

Yes, the postmortem process works for outage diagnosis sessions and incidents across teams, producing structured blameless reports suitable for archival and cross-team reliability learning.