Pressure-test a decision, plan, or proposal by dispatching parallel sub-agents that argue it from deliberately opposed perspectives, then synthesising their debate into one verdict that preserves dissent.

Scope: decisions and designs only. Reviewing a diff is /code-review's job — don't point the roundtable at code changes.

Process

1. Frame the motion

Restate the user's question as a single debatable motion — a claim the table can support or oppose ("We should extract X into its own service"), not an open question ("What should we do about X?"). If the user's ask is too vague to frame, ask them to sharpen it first; if it's still fog, suggest running /grilling before convening the table.

Then assemble the evidence pack yourself, in the main thread: relevant file paths and excerpts, constraints, decisions already made, anything the user attached. Finding facts is the chair's job, not the seats' — sub-agents don't hunt on their own, so the whole table debates the same evidence.

Before dispatching anyone, confirm the motion is one sentence and the evidence pack is complete enough to argue from. A muddled motion should fail here — not inside four parallel sub-agents.

2. Seat the table

Default four seats: