/cs: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
Installs just this skill. Get the whole plugin for auto-invocation.
โก How it fires
How this skill gets triggered: by you, by Claude, or both.
Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/post-mortem
๐๏ธ Context preview
The summary Claude sees to decide when to auto-load this skill.
/cs: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
๐ Stats
Stars23,060
Forks3,139
LanguagePython
LicenseMIT
๐ฆ Ships with claude-skills
</> SKILL.md
post-mortem.SKILL.md
---name: "post-mortem"
description: "/cs: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."
---# /cs:post-mortem โ Honest Retrospective
**Command:** `/cs: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
```
/cs:office-hours โ /cs:brief โ /cs:boardroom โ /cs:decide โ /cs:execute โ /cs:post-mortem
โ you are here
```
## When to Run
- At the 90-day checkpoint (auto-scheduled by `/cs: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 `/cs:decide`)
- The execution plan (output of `/cs:execute`)
- Actual outcomes (metrics, events, customer signals)
| 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: `/cs: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 `/cs:decide` time, eliminate that move. The numbers either matched or they didn't.
## Why Revisit Dissent
The dissent column from `/cs: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
- `/cs:brief` โ if the post-mortem surfaces a new decision
- `/cs:freeze` โ if the post-mortem reveals a process gap that needs cooldown enforcement