post-mortem

Topics in the source

• /c-level-agents:post-mortem — Honest Retrospective
• Pipeline Position
• When to Run
• Inputs
• Output: Post-Mortem Record
• Why Pre-Committed Criteria Matter
• Why Revisit Dissent
• Routing

Command: /c-level-agents:post-mortem 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. 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 The decision record (output of /c-level-agents:decide) The execution plan (output of /c-level-agents:execute) Actual outcomes (metrics, events, customer signals) Saved to /.claude/postmortems/YYYY-MM-DD- .md: 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. 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. /c-level-agents:brief — if the post-mortem surfaces a new decision /c-level-agents:freeze — if th

This is an excerpt. Refer to the complete source and its current requirements.