council

To prevent groupthink during architectural decisions, use structured adversarial evaluation with independent subagent roles to force disagreement and surface tradeoffs objectively. This prevents cognitive biases like anchoring by isolating context and stress-testing proposed paths through distinct skeptic and critic perspectives.

Structured adversarial decision-making for technical tradeoffs is a process that convenes multiple independent roles—Architect, Skeptic, Pragmatist, and Critic—to analyze complex project dilemmas. It forces independent feedback to surface tradeoffs and prevent bias when choosing between valid paths like monorepo versus polyrepo.

To evaluate tradeoffs for migrating to a distributed database architecture, convene a multi-voice advisory council to facilitate structured disagreement. By assigning independent subagent roles to analyze the decision framing, you ensure objective, adversarial evaluation of the proposed migration path and its inherent tradeoffs.

Yes, you can use independent subagents to stress-test production rollout readiness by convening an adversarial council. The subagents operate as distinct roles—such as a Skeptic and Pragmatist—to provide fresh, unbiased feedback on complex trade-offs, ensuring objective evaluation of the feature's readiness.

Yes, this adversarial evaluation approach requires clear decision framing and context isolation to function correctly. Establishing strict boundaries around the strategic decision ensures that the independent subagent roles can objectively analyze the tradeoffs without anchoring bias interfering with the evaluation.

You should not use adversarial consensus building for project dilemmas when the technical decision lacks ambiguity or valid alternative paths. If there is only one clear solution without complex tradeoffs to surface, the structured disagreement and independent subagent evaluation process provides unnecessary overhead.