Help us improve
Share bugs, ideas, or general feedback.
From c-level-agents
/cs:post-mortem <decision> — Honest retrospective on an executed decision, scored against original assumptions and dissent. Closes the strategic sprint loop.
npx claudepluginhub kruxshnx/claude-skills-devin --plugin c-level-agentsHow this skill is triggered — by the user, by Claude, or both
Slash command
/c-level-agents:post-mortemThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Command:** `/cs:post-mortem <decision-path>`
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Share bugs, ideas, or general feedback.
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.
/cs:office-hours → /cs:brief → /cs:boardroom → /cs:decide → /cs:execute → /cs:post-mortem
↑ you are here
/cs:decide)/cs:decide)/cs:execute)Saved to ~/.claude/postmortems/YYYY-MM-DD-<slug>.md:
# 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
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.
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.
/cs:brief — if the post-mortem surfaces a new decision/cs:freeze — if the post-mortem reveals a process gap that needs cooldown enforcementcs-onboarddecision-loggercs-chief-of-staff/em:postmortem — adversarial single-decision post-mortemVersion: 1.0.0