challenge-that

Critically evaluate a software design proposal by analyzing it from five adversarial perspectives: Skeptic, Pragmatist, Edge Case Hunter, Structural Critic, and Root Cause Analyst. This systematic critical thinking identifies unstated tradeoffs and prevents premature consensus on flawed requirements.

Adversarial analysis for decision making is a risk assessment technique that critiques proposals from multiple opposing viewpoints to surface actionable concerns. It forces critical evaluation of unchallenged assumptions and design decisions to prevent under-examined requirements from reaching development.

Use multiple perspectives to review requirements when proposals are accepted without pushback, when design decisions have unstated tradeoffs, or when premature consensus occurs. This triggers critical evaluation to identify architectural conflicts and specific weaknesses before committing to implementation.

Yes, you can use critical thinking techniques to find edge cases by applying adversarial analysis roles like Edge Case Hunter and Skeptic. This proposal review process identifies specific actionable concerns and areas for improvement in any given feature decision or requirement.

The best way to challenge assumptions in a technical proposal is synthesizing concerns from five distinct viewpoints including Structural Critic and Root Cause Analyst. This adversarial analysis identifies unstated tradeoffs and architectural conflicts, producing actionable weaknesses for improvement before development begins.

Adversarial perspectives for risk assessment focus on identifying flaws and actionable concerns rather than generating solutions. This critical evaluation approach critiques existing proposals but requires a separate proposal review step to synthesize the identified weaknesses into a revised, improved design decision.