Back to Details

multi-brain-experts

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Multi-Brain Experts Protocol

多脑专家协议

Instead of fixed Creative/Pragmatic/Comprehensive perspectives, dynamically select 3 domain experts from a role pool based on the request context. Each expert evaluates the request through their specialized lens.
不再采用固定的创意/务实/全面视角，而是根据请求上下文从角色库中动态选择3位领域专家。每位专家都将从其专业视角评估请求。

Workflow

工作流

1. Understand the request
2. Select 3 experts from the role pool
3. Each expert provides their perspective (2-3 sentences)
4. Synthesize consensus
5. Produce full output with all perspectives visible
1. Understand the request
2. Select 3 experts from the role pool
3. Each expert provides their perspective (2-3 sentences)
4. Synthesize consensus
5. Produce full output with all perspectives visible

Step 1: Understand the Request

步骤1：理解请求

Identify the domain, constraints, and key decision factors. This determines which experts to activate.
确定领域、约束条件和关键决策因素。这将决定激活哪些专家。

Step 2: Expert Selection

步骤2：专家选择

Choose the 3 most relevant experts from the role pool. Selection criteria:
  • Relevance: How directly does this role address the core problem?
  • Coverage: Do the 3 roles cover different dimensions (technical, user-facing, business)?
  • Tension: Prefer combinations that naturally create productive tension.
See 
references/EXPERT_ROLES.md
for the full role pool and selection heuristics.
从角色库中选择3位最相关的专家。选择标准：
  • 相关性：该角色与核心问题的直接关联程度如何？
  • 覆盖范围：这3个角色是否涵盖不同维度（技术、用户面向、业务）？
  • 张力：优先选择能自然产生建设性张力的组合。
查看
references/EXPERT_ROLES.md
获取完整角色库和选择启发式规则。

Selection Output

选择输出

Always declare the selected experts before their perspectives:
markdown
**Selected Experts:** [Role A], [Role B], [Role C]
**Why these 3:** [One sentence explaining the selection logic]
在展示专家视角前，必须先声明所选专家：
markdown
**Selected Experts:** [Role A], [Role B], [Role C]
**Why these 3:** [One sentence explaining the selection logic]

Step 3: Expert Perspectives

步骤3：专家视角

Each expert provides their analysis independently:
markdown
undefined
每位专家独立提供其分析：
markdown
undefined

🧠 Expert Panel

🧠 Expert Panel

Selected Experts: Security Architect, Performance Engineer, DX Advocate Why these 3: API design with auth requires security-first thinking, latency awareness, and developer ergonomics.
🔒 Security Architect: [2-3 sentences from security perspective]
⚡ Performance Engineer: [2-3 sentences from performance perspective]
🛠️ DX Advocate: [2-3 sentences from developer experience perspective]

---
Selected Experts: Security Architect, Performance Engineer, DX Advocate Why these 3: API design with auth requires security-first thinking, latency awareness, and developer ergonomics.
🔒 Security Architect: [2-3 sentences from security perspective]
⚡ Performance Engineer: [2-3 sentences from performance perspective]
🛠️ DX Advocate: [2-3 sentences from developer experience perspective]

---

Step 4: Consensus

步骤4：共识

Synthesize expert opinions:
  • Agreement points: Where experts align
  • Complementary insights: Unique contributions from each expert
  • Conflicts: Which expert's concern takes priority and why
综合专家意见：
  • 共识点：专家达成一致的地方
  • 互补见解：每位专家的独特贡献
  • 冲突点：哪位专家的关注点优先级更高及原因

Step 5: Full Output

步骤5：完整输出

Mandatory: The final response must always include the selected experts, all perspectives, the consensus, and the complete deliverable.
**强制要求：**最终响应必须始终包含所选专家、所有视角、共识内容以及完整交付成果。

Guardrails

约束规则

  • Always show expert selection reasoning — the user must understand why these 3 were chosen.
  • Each expert must reason within their domain — no generic advice.
  • If the request is purely within one domain, still select 3 experts but from adjacent disciplines.
  • Prefer productive tension over agreement — complementary expertise is more valuable than consensus-seeking.
  • Fall back to base 
    multi-brain
    (Creative/Pragmatic/Comprehensive) if no clear domain experts apply.
  • 始终展示专家选择理由——用户必须理解为何选择这3位专家。
  • 每位专家必须在其领域内进行推理——不得提供通用建议。
  • 如果请求完全属于单一领域，仍需选择3位专家，但需来自相邻学科。
  • 优先选择建设性张力而非一致意见——互补专业知识比寻求共识更有价值。
  • 如果没有明确的领域专家适用，则退回到基础的
    multi-brain
    （创意/务实/全面）模式。

References

参考资料

  • See 
    references/EXPERT_ROLES.md
    for the complete role pool with descriptions and trigger conditions.
  • See 
    references/EXAMPLES.md
    for worked examples.
  • 查看
    references/EXPERT_ROLES.md
    获取完整角色库，包含角色描述和触发条件。
  • 查看
    references/EXAMPLES.md
    获取实际案例。