See the rebuttal, not just the conclusion.
Debate a question through opposing roles, then run it through a Red Team rebuttal before deciding. You see the conclusion and the risks before you commit.
Where this helps
Only supporting opinions show up
Debate assigns opposing roles so dissenting views get surfaced too.
Decisions get made before risks are fully mapped
Red Team runs a final rebuttal against the conclusion to catch what's been missed.
Judging debate quality feels subjective
Seven-metric scoring gives you a quantified read on the quality of the discussion.
Discussions sprawl without landing on a conclusion
Choose from three algorithms — Debate+Synthesis+RedTeam, Tree of Debate, or Issue-by-Issue — to structure the argument.
From debate to decision
Put the question to Debate
Example: set "Should we continue or pull funding from new venture A?" as the topic.
Choose the role split
Pick from two to five participants across seven available roles.
Pick the algorithm
Use Issue-by-Issue to structure the points systematically, or Debate+Synthesis+RedTeam to argue both sides in full.
Review the Red Team rebuttal
Check the final rebuttal against the conclusion for risks you might have missed.
Turn it into a decision memo in Chat
Carry the key points and the rebuttal into Chat and write up the decision memo.
Features you'll use
Debate
Three algorithms, two to five participants, seven roles to draw from.
Red Team
Runs a final rebuttal against the conclusion to reduce blind spots.
Seven-metric scoring
Check the quality of a discussion against quantified metrics.
Turn count
Adjust the depth of the debate from 1 to 10 turns (default 4).
Handover between modes
Carry a debate's conclusion into Chat and turn it into a decision memo.
Related pages
Try the leadership and decisions pattern on the free plan.
Start free