Post Mortem

Run a fast, blame-free project retrospective — what worked, what didn't, root causes and three concrete changes — and append a structured entry to LESSONS.md.

6 starsOther

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add MarcoZorn/agencykit --skill post-mortem
Manual install
git clone --depth 1 https://github.com/MarcoZorn/agencykit.git /tmp/agencykit
mkdir -p ~/.claude/skills
cp -r /tmp/agencykit/.claude/skills/post-mortem ~/.claude/skills/post-mortem

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Post-Mortem

## When to use this skill

**English:** "post-mortem", "retrospective", "project done", "lessons learned", "wrap-up", "close out the project".

**Italiano:** "post-mortem", "retrospettiva", "progetto chiuso", "lezioni apprese", "chiusura progetto".

## What this skill does

Runs a tight retrospective on a finished project and turns it into learning the agency keeps. It separates what to keep doing from what to stop, digs one level past the symptom to the root cause, and commits to three concrete changes for next time. Then it appends a structured entry to `LESSONS.md` in the project root, so the lesson survives past the meeting nobody wrote down.

## Inputs required

1. **Project name** and a one-line description of what it was.
2. **Outcome** — delivered on time / late, on budget / over, client happy / not.
3. **What the team felt went well and badly** — gather a few honest points; if the user only gives one side, prompt for the other.
4. **Any hard numbers** — hours vs estimate, revisions, margin if known.

The tone is blame-free. The goal is better systems, not a search for who to fault. If the input names a person as "the problem", reframe it as a process gap.

## Output format

1. **WHAT WORKED** — keep doing.
2. **WHAT DIDN'T** — stop or fix.
3. **ROOT CAUSES** — 1–2 per issue, one level past the symptom.
4. **THREE CHANGES** — concrete actions for the next similar project.
Read the full skill on GitHub

Details

Skill name
post-mortem
Path
.claude/skills/post-mortem/SKILL.md
License
MIT
Repo updated
7 July 2026

FAQ

What does the Post Mortem skill do?

Run a fast, blame-free project retrospective — what worked, what didn't, root causes and three concrete changes — and append a structured entry to LESSONS.md.

How do I install the Post Mortem skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add MarcoZorn/agencykit --skill post-mortem. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Post Mortem popular?

It lives in MarcoZorn/agencykit, which has 6 GitHub stars and 0 forks.

Related skills

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.