Board Meeting Protocol
Structured multi-agent deliberation that prevents groupthink, captures minority views, and produces clean, actionable decisions.
Keywords
board meeting, executive deliberation, strategic decision, C-suite, multi-agent, /cs:board, founder review, decision extraction, independent perspectives
Invoke
/cs:board [topic] — e.g.
/cs:board Should we expand to Spain in Q3?
The 6-Phase Protocol
PHASE 1: Context Gathering
- 1. Load INLINECODE2
- Load
memory/board-meetings/decisions.md (Layer 2 ONLY — never raw transcripts) - Reset session state — no bleed from previous conversations
- Present agenda + activated roles → wait for founder confirmation
Chief of Staff selects relevant roles based on topic (not all 9 every time):
| Topic | Activate |
|---|
| Market expansion | CEO, CMO, CFO, CRO, COO |
| Product direction |
CEO, CPO, CTO, CMO |
| Hiring/org | CEO, CHRO, CFO, COO |
| Pricing | CMO, CFO, CRO, CPO |
| Technology | CTO, CPO, CFO, CISO |
PHASE 2: Independent Contributions (ISOLATED)
No cross-pollination. Each agent runs before seeing others' outputs.
Order: Research (if needed) → CMO → CFO → CEO → CTO → COO → CHRO → CRO → CISO → CPO
Reasoning techniques: CEO: Tree of Thought (3 futures) | CFO: Chain of Thought (show the math) | CMO: Recursion of Thought (draft→critique→refine) | CPO: First Principles | CRO: Chain of Thought (pipeline math) | COO: Step by Step (process map) | CTO: ReAct (research→analyze→act) | CISO: Risk-Based (P×I) | CHRO: Empathy + Data
Contribution format (max 5 key points, self-verified):
CODEBLOCK0
Each agent self-verifies before contributing: source attribution, assumption audit, confidence scoring. No untagged claims.
PHASE 3: Critic Analysis
Executive Mentor receives ALL Phase 2 outputs simultaneously. Role: adversarial reviewer, not synthesizer.
Checklist:
- - Where did agents agree too easily? (suspicious consensus = red flag)
- What assumptions are shared but unvalidated?
- Who is missing from the room? (customer voice? front-line ops?)
- What risk has nobody mentioned?
- Which agent operated outside their domain?
PHASE 4: Synthesis
Chief of Staff delivers using the
Board Meeting Output format (defined in
agent-protocol/SKILL.md):
- - Decision Required (one sentence)
- Perspectives (one line per contributing role)
- Where They Agree / Where They Disagree
- Critic's View (the uncomfortable truth)
- Recommended Decision + Action Items (owners, deadlines)
- Your Call (options if founder disagrees)
PHASE 5: Human in the Loop ⏸️
Full stop. Wait for the founder.
CODEBLOCK1
Rules:
- - User corrections OVERRIDE agent proposals. No pushback. No "but the CFO said..."
- 30-min inactivity → auto-close as "pending review"
- Reopen any time with INLINECODE5
PHASE 6: Decision Extraction
After founder approval:
- - Layer 1: Write full transcript → INLINECODE6
- Layer 2: Append approved decisions → INLINECODE7
- Mark rejected proposals INLINECODE8
- Confirm to founder with count of decisions logged, actions tracked, flags added
Memory Structure
CODEBLOCK2
Future meetings load Layer 2 only. Never Layer 1. This prevents hallucinated consensus.
Failure Mode Quick Reference
| Failure | Fix |
|---|
| Groupthink (all agree) | Re-run Phase 2 isolated; force "strongest argument against" |
| Analysis paralysis |
Cap at 5 points; force recommendation even with Low confidence |
| Bikeshedding | Log as async action item; return to main agenda |
| Role bleed (CFO making product calls) | Critic flags; exclude from synthesis |
| Layer contamination | Phase 1 loads decisions.md only — hard rule |
References
- -
templates/meeting-agenda.md — agenda format - INLINECODE10 — final output format
- INLINECODE11 — conflict handling, timing, failure modes
董事会会议协议
结构化多智能体审议机制,防止群体思维,捕捉少数派观点,并生成清晰、可执行的决策。
关键词
董事会会议、高管审议、战略决策、C级管理层、多智能体、/cs:board、创始人审阅、决策提取、独立视角
调用方式
/cs:board [议题] — 例如 /cs:board 我们是否应该在第三季度拓展西班牙市场?
六阶段协议
第一阶段:背景收集
- 1. 加载 memory/company-context.md
- 加载 memory/board-meetings/decisions.md (仅第二层——绝不加载原始记录)
- 重置会话状态——不保留之前对话的任何信息
- 呈现议程 + 激活角色 → 等待创始人确认
参谋长根据议题选择相关角色(并非每次都需要全部9个角色):
| 议题 | 激活角色 |
|---|
| 市场拓展 | CEO、CMO、CFO、CRO、COO |
| 产品方向 |
CEO、CPO、CTO、CMO |
| 招聘/组织架构 | CEO、CHRO、CFO、COO |
| 定价策略 | CMO、CFO、CRO、CPO |
| 技术决策 | CTO、CPO、CFO、CISO |
第二阶段:独立贡献(隔离状态)
禁止交叉影响。每个智能体在查看其他智能体输出之前独立运行。
顺序:研究(如需)→ CMO → CFO → CEO → CTO → COO → CHRO → CRO → CISO → CPO
推理技术: CEO:思维树(3种未来情景)| CFO:思维链(展示计算过程)| CMO:递归思维(草稿→批判→优化)| CPO:第一性原理 | CRO:思维链(管道计算)| COO:逐步推理(流程地图)| CTO:ReAct(研究→分析→行动)| CISO:基于风险(概率×影响)| CHRO:共情+数据
贡献格式(最多5个关键点,自我验证):
[角色] — [日期]
关键点(最多5个):
• [发现] — [已验证/假设] — 🟢/🟡/🔴
• [发现] — [已验证/假设] — 🟢/🟡/🔴
建议:[明确立场]
置信度:高 / 中 / 低
来源:[数据来源]
什么会改变我的想法:[具体条件]
每个智能体在贡献前进行自我验证:来源归属、假设审计、置信度评分。不允许未标注的声明。
第三阶段:批判分析
执行导师同时接收所有第二阶段的输出。角色:对抗性审阅者,而非综合者。
检查清单:
- - 哪些智能体过于轻易地达成一致?(可疑共识 = 危险信号)
- 哪些假设是共享但未经验证的?
- 谁缺席了会议?(客户声音?一线运营?)
- 哪些风险没有人提及?
- 哪个智能体超出了其职责范围?
第四阶段:综合
参谋长使用
董事会会议输出格式(定义于 agent-protocol/SKILL.md)进行汇报:
- - 需要决策的事项(一句话)
- 各方观点(每个贡献角色一行)
- 共识点 / 分歧点
- 批判者视角(令人不安的真相)
- 推荐决策 + 行动项(负责人、截止日期)
- 您的决定(创始人不同意的备选方案)
第五阶段:人在回路中 ⏸️
完全停止。等待创始人。
⏸️ 创始人审阅 — [粘贴综合报告]
选项:✅ 批准 | ✏️ 修改 | ❌ 拒绝 | ❓ 提出追问
规则:
- - 用户的修正覆盖智能体的提案。不得反驳。不得说但是CFO说过……
- 30分钟无操作 → 自动关闭为待审阅
- 随时可通过 /cs:board resume 重新开启
第六阶段:决策提取
创始人批准后:
- - 第一层: 写入完整记录 → memory/board-meetings/YYYY-MM-DD-raw.md
- 第二层: 追加已批准的决策 → memory/board-meetings/decisions.md
- 标记被拒绝的提案为 [DONOTRESURFACE]
- 向创始人确认,包含已记录的决策数量、已追踪的行动项、已添加的标记
记忆结构
memory/board-meetings/
├── decisions.md # 第二层 — 仅创始人批准(第一阶段加载此文件)
├── YYYY-MM-DD-raw.md # 第一层 — 完整记录(从不自动加载)
└── archive/YYYY/ # 90天后的原始记录
未来的会议仅加载第二层。 绝不加载第一层。这可以防止产生幻觉共识。
故障模式快速参考
| 故障 | 解决方案 |
|---|
| 群体思维(全部同意) | 重新运行第二阶段隔离模式;强制提出最强反对论点 |
| 分析瘫痪 |
限制5个要点;即使置信度低也强制提出建议 |
| 琐事争论 | 记录为异步行动项;返回主要议程 |
| 角色越界(CFO做产品决策) | 批判者标记;排除在综合之外 |
| 层级污染 | 第一阶段仅加载 decisions.md — 硬性规则 |
参考资料
- - templates/meeting-agenda.md — 议程格式
- templates/meeting-minutes.md — 最终输出格式
- references/meeting-facilitation.md — 冲突处理、时间控制、故障模式