debate

Multi-perspective debate surfaces blind spots in architecture decisions by creating 3-5 roles to argue diverse perspectives, identifying risks and trade-offs through 2-3 structured rounds of reasoning and critique.

Facilitating stakeholder collaboration for risk assessment works best through a multi-perspective debate, which assigns distinct roles to stakeholders and runs multiple rounds of critiquing and refining proposals to surface disagreements and reach consensus.

You structure the debate by defining your decision question, establishing 3-5 roles, and conducting 2-3 rounds of opening positions, critiquing, and refining proposals. The final synthesis outputs consensus, remaining disagreements, and a recommended path.

Yes, you can use multi-perspective debate for policy choices and product strategy. The approach applies to any complex decision by role-playing different stakeholders to surface insights, remaining disagreements, and mind changes to inform your final choice.

To start a role-based debate for decision-making, you simply need to describe your decision question. The process requires YAML frontmatter with name and description in SKILL.md and optionally supports scripts, references, and assets to guide the debate.

A role-based debate generates synthesis outputs including consensus points, remaining disagreements, and mind changes. These outputs provide stakeholders with a clear, recommended path forward based on the refined proposals from the debate rounds.