Skip to main content
skill Claude Code

post-mortem skill for Claude Code: install and use · alirezarezvani

This skill reviews an executed decision against its pre-set criteria, assumptions, and dissent. Use it at a review checkpoint or when a kill criterion fires.

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add alirezarezvani/claude-skills
/plugin install c-level-agents@claude-code-skills
Open on GitHub

What post-mortem does

post-mortem takes a decision path and compares the outcome with success and kill criteria written before the decision. It uses the decision record, execution plan, and actual outcomes such as metrics, events, and customer signals. Run it with /c-level-agents:post-mortem .

The result is saved to ~/.claude/postmortems/YYYY-MM-DD-.md. The record includes a WIN / PARTIAL / LOSS / MIXED status, tables for thresholds and actuals, a review of what went right and wrong, preserved dissent, and an assumption audit. It also creates forward actions and can route a new decision to /c-level-agents:brief or a process gap to /c-level-agents:freeze.

Install it when your decisions have pre-committed criteria and recorded dissent to revisit. Skip it for a one-off discussion without a decision record and execution plan.

What it helps with

  • score outcomes against pre-committed success criteria
  • check whether a kill criterion was triggered
  • revisit preserved dissent after execution
  • audit the assumptions behind a decision
  • create follow-up actions from the review

Example prompts for the agent

  • Run `/c-level-agents:post-mortem decisions/pricing.md` at the review checkpoint.
  • Review `~/.claude/decisions/launch.md` against its criteria, actual outcomes, and preserved dissent.
  • Create a post-mortem after a kill criterion fires and save it under `~/.claude/postmortems/`.

How to install post-mortem

1Plugin marketplace

/plugin marketplace add alirezarezvani/claude-skills
/plugin install c-level-agents@claude-code-skills

This installs the whole c-level-agents plugin with all its skills

2Skills CLI (Vercel)

npx skills add alirezarezvani/claude-skills --skill post-mortem -a claude-code

3Manually: put the files in place

~/.claude/skills/post-mortem/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/post-mortem/

From the same set349

The whole set →
engineering-skills Alireza Rezvani An engineering skill index for Claude Code that helps you select one specialist SKILL.md for the task at hand. It covers architecture, testing, DevOps, and data work. Claude Code 2,387installs finance-skills Alireza Rezvani Routes ambiguous finance prompts to the right bundled skill: financial-analyst, saas-metrics-coach, or month-end-close. Claude Code 2,312installs marketing-skills Alireza Rezvani A directory and router for marketing skills in Claude Code. It picks the right specialist skill for SEO, content, CRO, channels, and related tasks. Claude Code 2,264installs business-growth-skills Alireza Rezvani Routes growth and revenue prompts to the right specialized skill across customer success, sales engineering, RevOps, and proposals in Claude Code. Claude Code 2,189installs engineering-advanced-skills Alireza Rezvani An index of 37 engineering skills for architecture, automation, reliability, and platform work. Use it when a project needs task-specific engineering workflows. Claude Code 2,019installs product-skills Alireza Rezvani Product work orchestrator for Claude Code. Routes queries across 16 domain lanes and validates discovery trees with deterministic scripts. Claude Code 1,994installs pm-skills Alireza Rezvani Routes project-delivery requests across 8 PM sub-skills for Jira, Confluence, sprints, reporting, and team communication. Useful for controlled delivery work. Claude Code 1,975installs senior-backend Alireza Rezvani Scaffolds backend APIs, detects database bottlenecks, and runs load tests. Useful when designing Express routes, optimizing PostgreSQL, or preparing for production. Claude Code 1,674installs

Other versions of post-mortem

Similar

Questions about post-mortem

How do I install post-mortem in Claude Code?

Add the marketplace with /plugin marketplace add alirezarezvani/claude-skills, then install the plugin using /plugin install c-level-agents@claude-code-skills. You can also add the skill with npx skills add alirezarezvani/claude-skills --skill post-mortem -a claude-code.

What does the post-mortem skill do?

It scores an executed decision against success and kill criteria set in advance, audits its assumptions, and revisits recorded dissent. The result is a Markdown post-mortem with follow-up actions.

What inputs does post-mortem need?

It needs the decision record, execution plan, and actual outcomes such as metrics, events, or customer signals. Run it at the 90-day checkpoint, after a kill criterion triggers, or after a major decision is reversed.

Source text

SKILL.md · MIT
---
name: "post-mortem"
description: "/c-level-agents:post-mortem [decision] — Honest retrospective on an executed decision, scored against original assumptions and dissent. Closes the strategic sprint loop. Use when a decision hits its 90-day review checkpoint or its kill criteria trigger — e.g. scoring last quarter's pricing change against its pre-committed success metrics."
---

# /c-level-agents:post-mortem — Honest Retrospective

**Command:** `/c-level-agents:post-mortem <decision-path>`

Closes the strategic sprint loop. Scores a decision against the success and kill criteria written **before** the decision (not retro-fitted) and revisits the preserved dissent. This is the rigor that compounds over time.

## Pipeline Position

```
/c-level-agents:office-hours  →  /c-level-agents:brief  →  /c-level-agents:boardroom  →  /c-level-agents:decide  →  /c-level-agents:execute  →  /c-level-agents:post-mortem
                                                                                       ↑ you are here
```

## When to Run

- At the 90-day checkpoint (auto-scheduled by `/c-level-agents:decide`)
- When a kill criterion triggers
- After a major decision is reversed
- Quarterly on all decisions of the past quarter

## Inputs

- The decision record (output of `/c-level-agents:decide`)
- The execution plan (output of `/c-level-agents:execute`)
- Actual outcomes (metrics, events, customer signals)

## Output: Post-Mortem Record

Saved to `~/.claude/postmortems/YYYY-MM-DD-<slug>.md`:

```markdown
# Post-Mortem: <decision title>
**Decision date:** YYYY-MM-DD
**Post-mortem date:** YYYY-MM-DD
**Status:** WIN / PARTIAL / LOSS / MIXED

## Outcome Scoring (against pre-committed criteria)

| Success Criterion | Threshold | Actual | Met? |
|---|---|---|---|
| <metric 1> | <threshold> | <actual> | ✅ / ❌ |
| <metric 2> | <threshold> | <actual> | ✅ / ❌ |

| Kill Criterion | Threshold | Actual | Triggered? |
|---|---|---|---|
| <metric> | <threshold> | <actual> | ✅ / ❌ |

**Overall:** WIN / PARTIAL / LOSS / MIXED

## What We Got Right
- <factor 1>
- <factor 2>

## What We Got Wrong
- <factor 1>
- <factor 2>

## Preserved Dissent — Revisited
[Original dissent from the boardroom memo, scored:]

- **<dissenter>:** <original concern>
  - **Did it materialize?** YES / NO / PARTIAL
  - **Cost if YES:** <quantified impact>
  - **Lesson:** <one sentence>

## Assumption Audit
[Original brief's assumptions, scored:]

- **Assumption 1:** <text>
  - **Held?** YES / NO / PARTIAL
  - **Why:** <explanation>

## Process Lessons
- **Phase 2 isolation worked?** YES / NO
- **Devil's advocate concerns played out?** YES / NO / PARTIAL
- **Cadence was right?** YES / TOO LOOSE / TOO TIGHT

## Forward Actions
- [ ] <change to operating system or routing logic>
- [ ] <new decision to make based on this learning>
- [ ] <update company-context.md>

## Status
- WIN → archive, log lesson
- LOSS → schedule follow-up boardroom: `/c-level-agents:brief` for the next call
```

## Why Pre-Committed Criteria Matter

The biggest temptation in post-mortems is retroactive justification: "we always knew X, that's why we did Y." Pre-committed criteria, signed at `/c-level-agents:decide` time, eliminate that move. The numbers either matched or they didn't.

## Why Revisit Dissent

The dissent column from `/c-level-agents:boardroom` is the single most useful piece of organizational memory. Most of the time, the dissenter was directionally right. Revisiting and scoring it builds calibration over years.

## Routing

- `/c-level-agents:brief` — if the post-mortem surfaces a new decision
- `/c-level-agents:freeze` — if the post-mortem reveals a process gap that needs cooldown enforcement
- Updates to company-context.md via `cs-onboard`

## Related

- Skill: [`decision-logger`](${CLAUDE_PLUGIN_ROOT}/vendor/c-level-advisor/decision-logger/SKILL.md)
- Agent: [`cs-chief-of-staff`](../../agents/cs-chief-of-staff.md)
- Sibling: [`/em:postmortem`](../../../c-level-advisor/executive-mentor/skills/postmortem/SKILL.md) — adversarial single-decision post-mortem

---

**Version:** 1.0.0

© Alireza Rezvani · MIT · alirezarezvani/claude-skills

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor