post-mortem

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

/cs:post-mortem — Honest Retrospective

/cs:post-mortem — 坦诚复盘

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:post-mortem <decision-path>

闭环战略冲刺流程。对照决策前（而非事后补加）制定的成功和终止标准对决策进行评分，并回顾留存的反对意见。这种严谨性会随着时间不断积累价值。

Pipeline Position

流程位置

/cs:office-hours  →  /cs:brief  →  /cs:boardroom  →  /cs:decide  →  /cs:execute  →  /cs:post-mortem
                                                                                       ↑ you are here

/cs:office-hours  →  /cs:brief  →  /cs:boardroom  →  /cs:decide  →  /cs:execute  →  /cs:post-mortem
                                                                                       ↑ 当前位置

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

90天检查点（由
```
/cs:decide
```
自动调度）
触发终止标准时
重大决策被推翻后
每季度对过去季度的所有决策进行复盘

Inputs

输入项

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

决策记录（
```
/cs:decide
```
的输出）
执行计划（
```
/cs:execute
```
的输出）
实际结果（指标、事件、客户反馈信号）

Output: Post-Mortem Record

输出：复盘记录

Saved to

~/.claude/postmortems/YYYY-MM-DD-<slug>.md

markdown

undefined

保存至

~/.claude/postmortems/YYYY-MM-DD-<slug>.md

：

markdown

undefined

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

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>

<factor 1>
<factor 2>

What We Got Wrong

<factor 1>
<factor 2>

<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>

[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>

[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

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>

<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

undefined

WIN → archive, log lesson
LOSS → schedule follow-up boardroom:
```
/cs:brief
```
for the next call

undefined

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.

复盘时最大的诱惑是事后合理化：“我们一直都知道X，所以才做了Y。”在

/cs:decide

阶段确定并签署的预定义标准，可以杜绝这种行为。数据要么符合标准，要么不符合。

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.

/cs:boardroom

中的反对意见栏是组织最有价值的记忆片段之一。大多数情况下，提出反对意见的人在方向上是正确的。回顾并评分这些意见，能在多年间帮助团队校准判断。

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
```

```
/cs:brief
```
— 若复盘发现需要做出新决策
```
/cs:freeze
```
— 若复盘揭示出需要强制执行冷却期的流程漏洞
通过
```
cs-onboard
```
更新company-context.md

post-mortem

Original

Translation

/cs:post-mortem — Honest Retrospective

/cs:post-mortem — 坦诚复盘

Pipeline Position

流程位置

When to Run

运行时机

Inputs

输入项

Output: Post-Mortem Record

输出：复盘记录

Post-Mortem: <decision title>

Post-Mortem: <decision title>

Outcome Scoring (against pre-committed criteria)

Outcome Scoring (against pre-committed criteria)

What We Got Right

What We Got Right

What We Got Wrong

What We Got Wrong

Preserved Dissent — Revisited

Preserved Dissent — Revisited

Assumption Audit

Assumption Audit

Process Lessons

Process Lessons

Forward Actions

Forward Actions

Status

Status

Why Pre-Committed Criteria Matter

预定义标准的重要性

Why Revisit Dissent

回顾反对意见的原因

Routing

后续流程

Related

相关内容