debate-workflow

Facilitate structured multi-perspective debates for architectural decisions.

1|Updated Nov 14, 2025
One-click install
npx skills add https://github.com/rysweet/AzureHayMaker --skill debate-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debate-workflow
Source: https://github.com/rysweet/AzureHayMaker/tree/main/.claude/skills/debate-workflow
Command: npx skills add https://github.com/rysweet/AzureHayMaker --skill debate-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Complex architectural decisions and trade-offs often involve conflicting viewpoints. This Skill orchestrates a multi-perspective debate to surface the best path forward.

Core Features & Use Cases

  • Multi-perspective setup (security, performance, simplicity, etc.)
  • Defined debate rounds and convergence criteria
  • Structured documentation of positions, challenges, and synthesis
  • Suitable for major framework selections and high-risk changes

Quick Start

Start a debate on a critical decision: "Should we adopt Architecture X for feature Y?"

Frequently Asked Questions about debate-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a debate for architectural decisions across multiple perspectives?

Structured multi-perspective debate orchestrates competing viewpoints on architectural decisions by configuring debate rounds, assigning role-based agents to represent distinct perspectives (security, performance, simplicity, etc.), and converging toward consensus through defined criteria. This surfaces trade-offs and builds auditable decision records.

When should I use a multi-perspective debate instead of deciding alone?

Use multi-perspective debate for major architectural decisions, complex trade-offs, controversial changes, and high-impact initiatives where conflicting viewpoints exist. It prevents blind spots by systematically challenging assumptions and documenting reasoning across 3, 5, or 7 configured perspectives.

How many debate rounds and perspectives do I need for an architectural decision?

Configure 2–5 debate rounds and 3, 5, or 7 perspectives depending on decision complexity and team size. Fewer rounds suit simpler trade-offs; more rounds and perspectives increase rigor for high-risk or controversial architectural changes affecting multiple domains.

What does a debate output include, and how do I document the decision?

Debate output includes structured documentation of positions held by each perspective, explicit challenges raised, and synthesis toward convergence. The result is an auditable, consensus-oriented decision record showing how competing viewpoints were weighed.

Can I use debate for framework selection or only for trade-off analysis?

Debate applies to framework selection, trade-off analysis, and any high-impact decision. It excels when choosing between competing architectures, adoption decisions for major technologies, or resolving disagreement on implementation direction across teams.