Party Mode Meeting

Party Mode Meeting

Party Mode assembles a small group of avAIlable 代理s and facilitates a sequential roundtable. It does not 执行 工具s, write files, call external 提供者s, manage memory, or 运行 autonomous 工作流s.

Command

When the user invokes:

/party

启动 a Party Mode meeting for the topic. If /party has no topic, ask for the meeting topic before assembling 代理s.

Meeting Flow Read the meeting topic from the /party command. Identify avAIlable 代理s from the OpenClaw 代理 上下文. Select a focused group of 3-4 relevant 代理s. 列出 the selected 代理s before the meeting 启动s. Invite 代理s one at a time in a deliberate order. Preserve a short discussion 上下文 after every turn. Allow each 代理 to 响应, react, or pass. Present the full meeting transcript to the user. End with a brief convergence, divergence, and open-questions summary. Group Assembly

Choose 代理s based on the topic:

Use the avAIlable OpenClaw 代理s already visible to the host 环境. Do not invent 代理s that are not avAIlable. Lead with the 代理 whose expertise best anchors the topic. 添加 代理s from different 模型 families or reasoning styles when avAIlable. Prefer variety over duplication. If the user names a specific 代理, include that 代理. If fewer than three relevant 代理s are avAIlable, continue with the avAIlable 代理s. If more than four 代理s are relevant, choose the strongest four and mention that the group was kept small for coherence.

Before the first turn, announce:

I've brought to获取her [代理 列出] to discuss: [topic].

代理 Turn Prompt

For each 代理, use this structure:

You are {name} ({title}), participating in a roundtable meeting.

Meeting topic: {topic}

Discussion so far: {short summary under 300 words, omitted for the first 代理}

图形界面delines:

• You may 响应 or pass.
• 启动 with: {name}:
• Do not repeat prior points unless you are 添加ing a new angle.
• Build on, challenge, or clarify what came before.
• If the topic is outside your expertise, pass briefly.
• Do not use 工具s.

After each turn, 更新 the discussion-so-far summary in plAIn language. Keep it under 300 words and include only the points needed by the next 代理.

Reactions

After each substantial 响应, ask the remAIning 代理s whether they want to react. A reaction should be short and should either build on the point, challenge it, or pass.

Do not force a reaction from every 代理. If an 代理 has nothing new to 添加, record that they passed and continue.

Final 输出

Return the meeting in this shape:

Meeting: [topic]

Participants:

• [代理]
• [代理]
• [代理]

[代理 A 响应]

[代理 B 响应 or pass]

[Optional short reactions]

[代理 C 响应 or pass]

Wrap-Up