Back to Details

decide

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

/cs:decide — Log the Decision

/cs:decide — 记录决策

Command: 
/cs:decide <memo-path>
Logs the founder's decision via the 
decision-logger
skill. This is the gate where in-session deliberation becomes durable company memory.
命令： 
/cs:decide <memo-path>
通过
decision-logger
技能记录创始人的决策。这是将会话中的审议内容转化为持久化公司记忆的关键节点。

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

Two-Layer Memory Model

双层记忆模型

The 
decision-logger
skill maintains two layers:
  1. Raw transcripts — every boardroom session, every advisor's Phase 2 position, every dissent. Stored under 
    ~/.claude/decisions/raw/
    . Reference only, never feeds back automatically.
  2. Approved decisions — only the founder-signed memos. Stored under 
    ~/.claude/decisions/approved/
    . Feeds into future 
    /cs:office-hours
    and 
    /cs:founder-mode
    calls.
This split prevents the system from "remembering" unresolved debates as if they were decisions.
decision-logger
技能维护两层记忆：
  1. 原始记录 — 每次董事会会议、每位顾问的第二阶段立场、所有异议。存储在
    ~/.claude/decisions/raw/
    下。仅作参考，不会自动反馈到系统中。
  2. 已批准决策 — 仅包含创始人签署的备忘录。存储在
    ~/.claude/decisions/approved/
    下。会被用于未来的
    /cs:office-hours
    和
    /cs:founder-mode
    调用。
这种分离可防止系统将未解决的辩论当作已做出的决策来“记忆”。

Input

输入

A board memo file (output of 
/cs:boardroom
).
一份董事会备忘录文件（
/cs:boardroom
的输出）。

Workflow

工作流程

  1. Read the memo path
  2. Verify it has founder approval (status: APPROVED)
  3. Extract structured decision record:
    • Decision title
    • Date decided
    • Option chosen
    • Success + kill criteria
    • Dissent (preserved)
    • Review checkpoint date
  4. Append to 
    ~/.claude/decisions/approved/<YYYY-MM-DD>-<slug>.md
  5. Update the raw transcript pointer
  6. If llm-wiki bridge configured, write to vault (
    ~/company-vault/10-decisions/
    )
  7. Schedule auto-revisit (90 days)
  1. 读取备忘录路径
  2. 验证其是否获得创始人批准（状态：APPROVED）
  3. 提取结构化决策记录：
    • 决策标题
    • 决策日期
    • 选定的方案
    • 成功标准与终止标准
    • 异议（被保留）
    • 复查节点日期
  4. 追加到
    ~/.claude/decisions/approved/<YYYY-MM-DD>-<slug>.md
  5. 更新原始记录指针
  6. 如果配置了llm-wiki bridge，则写入到库中（
    ~/company-vault/10-decisions/
    ）
  7. 自动安排回访（默认90天）

Output Record Format

输出记录格式

markdown
undefined
markdown
undefined

Decision: <title>

Decision: <title>

Decided: YYYY-MM-DD By: <founder name> Memo: <link to boardroom memo> Brief: <link to original brief> Review checkpoint: YYYY-MM-DD (90d default)
Decided: YYYY-MM-DD By: <founder name> Memo: <link to boardroom memo> Brief: <link to original brief> Review checkpoint: YYYY-MM-DD (90d default)

Decision

Decision

Chose: <option> Rejected: <other options + one-line why>
Chose: <option> Rejected: <other options + one-line why>

Success Criteria (binding)

Success Criteria (binding)

  • <metric, threshold, timeframe>
  • <metric, threshold, timeframe>

Kill Criteria (binding)

Kill Criteria (binding)

  • <metric, threshold, action>
  • <metric, threshold, action>

Preserved Dissent

Preserved Dissent

  • <dissenter>: <unresolved concern>
  • (preserved verbatim; dissent never erased)
  • <dissenter>: <unresolved concern>
  • (preserved verbatim; dissent never erased)

Next Action

Next Action

  • /cs:execute
    → 90-day plan due <date>
  • /cs:execute
    → 90-day plan due <date>

Status History

Status History

  • YYYY-MM-DD: APPROVED
undefined
  • YYYY-MM-DD: APPROVED
undefined

Why Preserved Dissent

为何保留异议

The biggest risk in approved decisions is forgetting why someone disagreed. When the kill criteria trigger, the dissent often turns out to have been correct. Preserving it verbatim — not summarized — keeps the company honest at post-mortem time.
已批准决策的最大风险是忘记有人提出异议的原因。当终止标准触发时，这些异议往往被证明是正确的。逐字保留而非总结异议，能让公司在事后复盘时保持客观公正。

Routing

路由

  • /cs:execute <decision>
    — build the 90-day plan
  • /cs:freeze <decision> <days>
    — lock if irreversible
  • (Auto-scheduled) 
    /cs:post-mortem <decision>
    — at 90-day checkpoint
  • /cs:execute <decision>
    — 制定90天计划
  • /cs:freeze <decision> <days>
    — 若决策不可逆转则锁定
  • （自动安排）
    /cs:post-mortem <decision>
    — 在90天复查节点执行

Stale-Decision Audit

过期决策审计

cs-chief-of-staff
runs a weekly stale audit:
  • Decisions > 90 days without revisit → flag for 
    /cs:post-mortem
  • Decisions with kill criteria triggered → flag immediately
  • Decisions whose company-context.md basis has changed → flag for re-examination
cs-chief-of-staff
每周运行一次过期审计：
  • 超过90天未回访的决策 → 标记为需执行
    /cs:post-mortem
  • 触发终止标准的决策 → 立即标记
  • 基于
    company-context.md
    的决策依据发生变化 → 标记为需重新审议

Related

相关内容

  • Skill: 
    decision-logger
  • Agent: 
    cs-chief-of-staff
  • Bridge: 
    ../../references/llm-wiki-bridge.md
Version: 1.0.0
  • 技能：
    decision-logger
  • Agent：
    cs-chief-of-staff
  • 桥接工具：
    ../../references/llm-wiki-bridge.md
版本： 1.0.0