design-debate

Orchestrates structured design debates among agents to surface trade-offs.

234|55|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/Owl-Listener/designpowers --skill design-debate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-debate
Source: https://github.com/Owl-Listener/designpowers/tree/main/skills/design-debate
Command: npx skills add https://github.com/Owl-Listener/designpowers --skill design-debate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When teams converge on a single direction too quickly, critical trade-offs can be overlooked. This skill orchestrates structured debates between agents to surface competing viewpoints, ensuring the user can make an informed decision.

Core Features & Use Cases

  • Frame and formalize design questions to guide debates with clear objectives.
  • Assign advocates from specialized agents to present the strongest cases and challenge assumptions.
  • Include cross-examination and accessibility checks to surface weaknesses and ensure inclusive, robust outcomes.
  • Record decisions and reasoning for future reference and learning.

Quick Start

Initiate a design debate by selecting 2–3 Advocates and presenting a clear design question for evaluation.

Frequently Asked Questions about design-debate

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

FAQPage Schema
How do I use structured debates to surface design trade-offs and avoid premature consensus?

To surface design trade-offs, assign 2–3 specialized advocates to present opposing design directions. Include cross-examination and accessibility reviews to challenge assumptions before logging decisions, ensuring divergent reasoning prevents premature consensus.

What is the best way to facilitate design decision-making when my team has multiple viable directions?

Orchestrate a formal design debate where advocates challenge assumptions and cross-examine multiple viable directions. Adding an accessibility check ensures robust outcomes, while logging the reasoning creates an auditable record for future reference.

When do I need to formalize the design process to evaluate accessibility and trade-offs?

You need to formalize the design process when a strategist identifies multiple viable directions or the user requests options. It defines a step-by-step process with advocates, cross-examination, and accessibility review to surface trade-offs before converging.

Can I include an accessibility review during a design debate to ensure inclusive outcomes?

Yes, the design debate process integrates accessibility checks alongside advocate cross-examination to surface weaknesses in proposed directions, ensuring the final decision supports inclusive and robust outcomes.

How does cross-examination work in a collaborative design debate?

Cross-examination works by having assigned advocates challenge each other's assumptions and present the strongest cases for competing design directions, surfacing hidden weaknesses and trade-offs before a decision is recorded.

What are the limitations of using advocates to prevent premature consensus in design decisions?

A limitation is that using advocates requires selecting 2–3 specialized agents and a clearly framed design question. Without clear objectives or multiple viable directions, the debate process may add unnecessary overhead to the design workflow.