team-brainstorm

Adversarial brainstorming is orchestrated by spawning independent agent teams with structured roles like Devil's Advocate and Technical Architect to deeply analyze and refine complex system designs. It enforces task-based coordination to capture diverse viewpoints.

Multi-perspective agent debate improves high-stakes feature planning by assigning roles such as Optimist and Researcher to critique, defend, and refine proposals. This structured synthesis captures agreement and contention to avoid shallow conclusions.

Structured ideation generates detailed documentation artifacts including team findings, final syntheses, and Architecture Decision Records (ADRs). These outputs ensure that the debate results are suitable for direct implementation guidance and planning.

An adversarial team approach should be used for strategic pivots when high-stakes decisions require diverse viewpoints to validate ideas. It is ideal for complex proposals where independent critique prevents shallow conclusions.

Yes, you can use agent teams to generate ADRs from a feature proposal debate. The orchestration captures the structured debate and produces Architecture Decision Records alongside a detailed team report to guide implementation.