postmortem

Summarize coding session outcomes into a Markdown postmortem report.

Updated Dec 29, 2025

Search Tags:#retrospective #improvements #postmortem #root-cause #lessons-learned #session-review

Ready to run

npx skills add https://github.com/yu-iskw/dbt-artifacts-parser-ts --skill postmortem-yu-iskw

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: postmortem
Source: https://github.com/yu-iskw/dbt-artifacts-parser-ts/tree/main/.claude/skills/postmortem
Command: npx skills add https://github.com/yu-iskw/dbt-artifacts-parser-ts --skill postmortem-yu-iskw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Streamlines end-of-session reflection by generating a concise postmortem report that captures outcomes, failures, inefficiencies, and root causes so teams can learn and improve.

Core Features & Use Cases

Generate a concise postmortem report from session notes.
Rank improvements for the next session and prioritize actions.
Output a Markdown report suitable for chat or documentation without editing project files.

Quick Start

Provide a concise postmortem report in chat based on your session notes.

Frequently Asked Questions about postmortem

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

FAQPage Schema

How do I generate a postmortem report from session notes?▼

Generate a postmortem report by providing session notes to summarize outcomes, failures, and root causes. The skill applies a postmortem template to structure sections and outputs a Markdown report directly in chat.

What is the best way to capture lessons learned after a coding session?▼

Capturing lessons learned is done by summarizing a coding session's outcomes into a concise postmortem report. This process highlights failures, inefficiencies, and root causes so teams can learn and improve.

Can I rank improvements for the next session automatically?▼

Yes, you can rank improvements for the next session. The report generation process includes prioritizing actions, allowing teams to focus on the most critical improvements derived from the session's root-cause analysis.

Does the postmortem report edit project files?▼

No, the postmortem report does not edit project files. It outputs a Markdown report suitable for chat or documentation, ensuring your project file structure remains untouched while capturing session insights.

What should a postmortem template include for root-cause analysis?▼

A postmortem template for root-cause analysis should include sections for summarizing outcomes, capturing failures, identifying root causes, documenting lessons learned, and listing prioritized improvements.

When do I need a postmortem report for my coding session?▼

You need a postmortem report at the end of a session to capture failures, root causes, and lessons learned. It streamlines reflection by generating a concise summary of outcomes and prioritized improvements.