brief

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

/cs:brief — One-Page Strategy Brief

/cs:brief — 一页战略简报

Command:

/cs:brief <topic>

/cs:brief <office-hours-output>

Turns intake (raw question or office-hours output) into a one-page strategy brief that the boardroom can deliberate on. This is Step 1 of the strategic sprint pipeline.

命令：

/cs:brief <主题>

或

/cs:brief <办公时间输出内容>

将收集的信息（原始问题或办公时间输出内容）转化为可供董事会审议的一页战略简报。这是战略冲刺流程的第1步。

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
                       ↑ 当前所处位置

Inputs

输入

A topic string, or
An office-hours brief (preferred — more rigor)
```
~/.claude/company-context.md
```
(loaded automatically)

主题字符串，或
办公时间简报（优先选择——更严谨）
```
~/.claude/company-context.md
```
（自动加载）

Output

输出

A single Markdown file under

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

with this structure:

markdown

undefined

一个保存至

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

的Markdown文件，结构如下：

markdown

undefined

Strategy Brief: <topic>

战略简报：<主题>

Date: YYYY-MM-DD Author: cs-chief-of-staff Status: DRAFT | UNDER REVIEW | APPROVED | RETIRED

日期： YYYY-MM-DD 作者： cs-chief-of-staff 状态： 草稿 | 审核中 | 已批准 | 已归档

Context

背景

[1-2 paragraphs: where the company sits today on this topic — pulled from company-context.md]

[1-2段落：公司当前在该主题上的定位——摘自company-context.md]

Question

问题

[The one sentence question the boardroom must answer]

[董事会必须回答的一句话问题]

Options

选项

Option A: <name> — <one-sentence summary>
Option B: <name> — <one-sentence summary>
Option C: <name> — <one-sentence summary>

(Minimum 2 options. "Do nothing" is always an option.)

选项A： <名称> — <一句话概述>
选项B： <名称> — <一句话概述>
选项C： <名称> — <一句话概述>

（至少2个选项。“不采取任何行动”始终是一个选项。）

Assumptions

假设

<assumption 1 — explicit>
<assumption 2>
<assumption 3>

<假设1 — 明确说明>
<假设2>
<假设3>

Constraints

约束条件

Time: <by when must this decide>
Money: <budget envelope>
People: <who can / can't be reallocated>
Reversibility: <one-way door | two-way door>

时间：<必须在何时做出决定>
资金：<预算范围>
人员：<可以/不可以重新调配的人员>
可逆性：<单向决策 | 双向决策>

Affected Roles

受影响角色

Success Criteria

成功标准

[Measurable outcomes that define success — set BEFORE the decision]

<metric 1, threshold, timeframe>
<metric 2, threshold, timeframe>

[定义成功的可衡量结果——需在决策前确定]

<指标1，阈值，时间范围>
<指标2，阈值，时间范围>

Kill Criteria

终止标准

[What signal would tell you in 90 days that this was the wrong call]

<metric, threshold, action if missed>

undefined

[90天内哪些信号会表明这是错误的决策]

<指标，阈值，未达标时的行动>

undefined

Workflow

工作流程

Load company-context.md via context-engine
If input is office-hours output, parse the 6 answers
If input is a raw topic, prompt the founder for the missing pieces
Draft 2-3 options (never just one — every brief needs a counterfactual)
Make assumptions and constraints explicit
Identify affected roles → drives panel composition for
```
/cs:boardroom
```
Write success + kill criteria BEFORE the decision (this is the rigor moment)
Save to
```
~/.claude/briefs/
```

通过context-engine加载company-context.md
如果输入是办公时间输出内容，解析其中的6个答案
如果输入是原始主题，提示创始人补充缺失的信息
草拟2-3个选项（绝不能只有一个——每份简报都需要反事实选项）
明确说明假设和约束条件
确定受影响角色 → 决定
```
/cs:boardroom
```
的参会人员构成
在决策前撰写成功+终止标准（这是确保严谨性的环节）
保存至
```
~/.claude/briefs/
```

Why This Step Exists

此步骤的意义

The biggest decision-making failure is debating implementation before agreeing on the question. The brief locks the question, options, and success criteria so the boardroom can deliberate without scope creep.

This is also the artifact handoff — the next command consumes this file, not your memory.

决策失败的最大原因是在就问题达成一致之前就讨论实施方案。简报锁定问题、选项和成功标准，使董事会能够在没有范围蔓延的情况下进行审议。

这也是工件交接环节——下一个命令将使用此文件，而非依赖你的记忆。

Routing

后续路由

```
/cs:boardroom <brief>
```
— multi-role deliberation
```
/cs:cross-eval <brief>
```
— multi-model sanity check before boardroom (for high-stakes)
```
/cs:freeze <brief>
```
— cooldown lock for irreversible decisions

```
/cs:boardroom <简报>
```
— 多角色审议
```
/cs:cross-eval <简报>
```
— 董事会审议前的多模型合理性检查（针对高风险决策）
```
/cs:freeze <简报>
```
— 针对不可逆决策的冷却锁定