freeze

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

/cs:freeze — Cooldown Lock on a Decision

/cs:freeze — 决策冷却锁定

Command:

/cs:freeze <decision-path> <days>

Locks a decision for a defined cooldown period. During the freeze, the chief-of-staff router refuses to re-litigate the decision unless a kill criterion explicitly triggers.

Inspired by gstack's

/freeze

and

/guard

safety primitives — adapted from code-scoping to strategic-scoping.

命令：

/cs:freeze <决策路径> <天数>

为指定的决策设置一段冷却锁定期。在冻结期间，cs-chief-of-staff 路由程序将拒绝重新讨论该决策，除非触发明确的终止条件。

灵感来源于gstack的

/freeze

和

/guard

安全原语——从代码范围适配到战略决策范围。

When to Use

使用场景

Founders are pattern-matchers; pattern-matching after a tough decision often produces a reversal that's actually just decision fatigue. The freeze enforces a discipline:

After any irreversible or high-cost-to-reverse decision (fundraise, layoff, market entry)
After a split-vote boardroom (preserve the call against second-guessing)
After a founder gut-feel override of unanimous advisor consensus (let it run)
During a personnel transition (lock the strategy so the new exec can execute, not redebate)

创始人是模式匹配者；在艰难决策后进行模式匹配往往会导致决策反悔，而这实际上只是决策疲劳的表现。冻结机制强制遵循以下原则：

在做出任何不可逆或反悔成本极高的决策后（融资、裁员、市场进入）
在董事会投票分歧后（维持既定决策，避免事后质疑）
在创始人凭直觉否决全体顾问一致意见后（让决策落地执行）
在人事过渡期间（锁定战略方向，让新任高管专注执行而非重新辩论）

Default Freeze Periods

默认冷却期

Decision type	Default freeze
Fundraise round size / lead choice	30 days
Pricing change	60 days
Market entry / exit	90 days
Layoff / RIF	30 days
Strategic pivot	90 days
Personnel (exec hire / fire)	60 days
M&A LOI	30 days
Custom	specify in command

决策类型	默认冷却期
融资轮次规模/领投方选择	30天
定价调整	60天
市场进入/退出	90天
裁员/RIF	30天
战略转型	90天
人事变动（高管招聘/解雇）	60天
并购意向书（M&A LOI）	30天
自定义	在命令中指定

Workflow

工作流程

Read the decision record
Validate it has APPROVED status
Apply freeze: write
```
freeze_until: YYYY-MM-DD
```
to the decision record
Add to active-freezes index at
```
~/.claude/freezes/active.md
```
cs-chief-of-staff router now refuses to re-route this topic to the boardroom until:
- The freeze period expires, OR
- A kill criterion explicitly triggers

查阅决策记录
验证决策状态为已批准（APPROVED）
应用冻结：在决策记录中写入
```
freeze_until: YYYY-MM-DD
```
添加至活跃冻结索引文件
```
~/.claude/freezes/active.md
```
cs-chief-of-staff 路由程序将拒绝把该议题重新提交至董事会，直到：
- 冻结期结束，或
- 触发明确的终止条件

Output

输出结果

The decision record is updated in place:

markdown

undefined

决策记录将就地更新：

markdown

undefined

Decision: <title>

... Status: FROZEN Frozen until: YYYY-MM-DD Reason for freeze: <text> Override condition: Kill criterion <name> triggers OR founder issues

/cs:unfreeze

with stated reason


The active-freezes index is updated:

```markdown

... Status: FROZEN Frozen until: YYYY-MM-DD Reason for freeze: <text> Override condition: Kill criterion <name> triggers OR founder issues

/cs:unfreeze

with stated reason


活跃冻结索引文件将更新：

```markdown

Active Freezes

Updated: YYYY-MM-DD

Decision	Frozen until	Override condition
<decision title>	YYYY-MM-DD	<kill criterion or /cs:unfreeze>

undefined

Updated: YYYY-MM-DD

Decision	Frozen until	Override condition
<decision title>	YYYY-MM-DD	<kill criterion or /cs:unfreeze>

undefined

Override

解除冻结

To unfreeze before the period ends, the founder runs:

/cs:unfreeze <decision> <reason>

The unfreeze is logged in the decision history (preserved permanently). Forced overrides create a paper trail that surfaces at post-mortem.

若要在冻结期结束前解除冻结，创始人需执行：

/cs:unfreeze <决策内容> <理由>

解除冻结操作将被永久记录在决策历史中。强制解除冻结会留下书面记录，以便在事后复盘时查看。

Auto-Override

自动解除冻结

If a kill criterion in the decision triggers, the freeze auto-releases and the chief-of-staff routes immediately to

/cs:post-mortem

. The freeze does not protect against reality; it protects against impulse.

如果决策中的终止条件被触发，冻结将自动解除，cs-chief-of-staff 会立即将议题路由至

/cs:post-mortem

。冻结机制不保护错误决策，只防止冲动反悔。

Why This Beats "Just Don't Re-Decide"

为何优于"只是不要重新决策"

Founders have authority. Without an explicit lock + log, every wobble produces a "let's discuss this again" — which is exhausting for advisors and erodes the value of the boardroom. The freeze is a process, not a rule; it logs every override so the post-mortem can audit founder discipline.

创始人拥有决策权。如果没有明确的锁定+记录机制，任何动摇都会引发"我们再讨论一下"的提议——这会让顾问疲惫不堪，也会削弱董事会的价值。冻结是一个流程，而非规则；它会记录每一次解除冻结操作，以便事后复盘时评估创始人的决策纪律。

Routing

路由规则

```
/cs:unfreeze
```
— explicit early release
```
/cs:post-mortem
```
— auto-triggered if kill criterion fires
```
/cs:boardroom
```
— blocked until unfreeze or expiry

```
/cs:unfreeze
```
— 提前手动解除冻结
```
/cs:post-mortem
```
— 终止条件触发时自动触发
```
/cs:boardroom
```
— 冻结期间禁止访问，直到解除冻结或冻结期结束

freeze

Original

Translation

/cs:freeze — Cooldown Lock on a Decision

/cs:freeze — 决策冷却锁定

When to Use

使用场景

Default Freeze Periods

默认冷却期

Workflow

工作流程

Output

输出结果

Decision: <title>

Decision: <title>

Active Freezes

Active Freezes

Override

解除冻结

Auto-Override

自动解除冻结

Why This Beats "Just Don't Re-Decide"

为何优于"只是不要重新决策"

Routing

路由规则

Related

相关内容