postmortem

Convert ralphy session chat history into a seven-file postmortem document set.

118|12|Updated May 5, 2026
One-click install
npx skills add https://github.com/alecs5am/ralphy --skill postmortem-alecs5am
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postmortem
Source: https://github.com/alecs5am/ralphy/tree/main/.agents/skills/postmortem
Command: npx skills add https://github.com/alecs5am/ralphy --skill postmortem-alecs5am

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a durable, multi-document postmortem template that records a ralphy session's chat history, decisions, and outcomes as a split 7-file set, enabling reproducible retrospectives and future learnings.

Core Features & Use Cases

  • Splits retrospectives into 7 focused documents: 01-chat-history.md, 02-lessons.md, 03-cli-issues.md, 04-models-and-cost.md, 05-workflow-fixes.md, 06-units.md, and 00-INDEX.md.
  • Enforces append-only iteration by appending new addenda to existing files rather than overwriting history.
  • Links to templates and reference materials to ensure traceability and alignment with organizational playbooks.

Quick Start

Run the postmortem skill to generate the 7-document set for the active project and append new addenda on subsequent iterations.

Frequently Asked Questions about postmortem

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

FAQPage Schema
How do I create a durable postmortem from a chat history?

To create a durable postmortem from a chat history, you can use a skill that converts session artifacts and conversations into a multi-document set. It splits retrospectives into seven focused files including chat history, lessons, and workflow fixes.

What is the best way to document lessons learned without overwriting previous retrospectives?

Documenting lessons learned without overwriting previous retrospectives requires an append-only iteration approach. This skill enforces append-only history by adding new addenda to existing files, ensuring past decisions and context are preserved for future iterations.

Can I link my retrospective documents to existing templates and reference materials?

Yes, you can link retrospective documents to existing templates and reference materials. The generated postmortem set includes cross-links to templates and source materials, ensuring traceability and alignment with organizational playbooks.

How do I track model costs and CLI issues during a project retrospective?

You can track model costs and CLI issues during a project retrospective by generating a split multi-document set. This includes dedicated files for tracking CLI issues and logging models and costs alongside the main chat history and lessons learned.

When do I need a multi-document postmortem set for a project session?

You need a multi-document postmortem set for a project session when it concludes or when explicitly requested as a retro or lessons learned exercise. It records decisions and outcomes as a seven-file set, enabling reproducible retrospectives and future learnings.