post-mortem
/post-mortem
/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.
- Author
- bestagentkits ↗
- Repository
- agency-skills ↗
- Licence
- MIT
- Last repository change
- 30.06.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 30.06.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
/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.
Original author 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.
How it works
- Pipeline Position
- When to Run
- Inputs
- Output: Post-Mortem Record
- Why Pre-Committed Criteria Matter
- Why Revisit Dissent
- Routing
- Related
SKILL.md preview
---
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)
## 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: `/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
- Updates to company-context.md via `cs-onboard`
## Related
- Skill: [`decision-logger`](../../../skills/decision-logger/SKILL.md)
- Agent: [`cs-chief-of-staff`](../../agents/cs-chief-of-staff.md)
- Sibling: [`/em:postmortem`](../../../executive-mentor/skills/postmortem/SKILL.md) — adversarial single-decision post-mortem
---
**Version:** 1.0.0
Files in this package (2)
- SKILL.md 4 KB
- agents/openai.yaml 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · bestagentkits/agency-skills | 100 | MIT |
| digital-stoic-org/agent-skills | 100 | MIT |
| alirezarezvani/claude-skills | 100 | MIT |
| borghei/Claude-Skills | 100 | MIT |
| evanbaker315/attentionos | 100 | MIT |
| rileyhilliard/claude-essentials | 100 | MIT |
| hanamizuki/solopreneur | 100 | MIT |
Database snapshot: 13.11.2026 · package version 52a6c189dc77 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90decision-architect
Structures a hard decision with options, criteria, weighted scoring, reversibility and pre-mortem, then makes a recommendation. Use when the user is stuck between choices, says 'should I X or Y', or needs a decision memo. - 100pre-mortem
Use before launching a plan, project, deal, or change when failure modes should be surfaced early. Use when applying the Pre Mortem consulting method and when a user asks for Pre Mortem, method execution, structured diagnosis, or action planning. - 100game-retrospective
Runs a sprint or milestone retrospective in the GDC post-mortem tradition: What Went Right, What Went Wrong, seven lenses including AI-assisted development, the Kill List and The One Thing, with actions fed into the next sprint. Use for "retro", "sprint retrospective",… - 100aped-pre-mortem
Use when user says "pre-mortem", "what could go wrong", "risk analysis", "failure modes", "anticipate problems", or invokes aped-pre-mortem. Structured pre-mortem before implementation starts. Not for post-incident (see aped-retro). - 100what-so-what-now-what
Use this skill to structure a message as What / So What / Now What — state the fact, explain the impact, recommend the action. Best for post-mortems, retros, incident reviews, status updates, debriefs, and any "here's what happened and what we should do" moment. Triggers on… - 100pre-mortem
Use when you need to surface how a product, feature, or plan could fail before committing to it, especially before a go/no-go decision. Triggers on "pre-mortem", "what could go wrong", "failure modes", "risks", "how might this fail", and the same intent in any language.