adversarial-review

A stalled code review requires fundamental critique to diagnose root causes of persistent feedback loops. Providing the PR diff and design brief allows an adversarial review to output structured critique levels and concrete alternative directions for implementers.

Adversarial review is a fundamental critique process that challenges core assumptions and identifies misaligned design choices in software engineering. It diagnoses root causes of persistent code review failures to pivot the approach and uncover alternative directions.

To perform root cause analysis on a failing PR, provide the latest diff and design brief to an adversarial review process. This outputs structured critiques identifying fundamental, structural, or nit-pick level issues and proposes alternative approaches.

Yes, you can use structured critique to redirect a stalled design analysis by challenging core assumptions. It applies to design requirements where feedback stalls, providing concrete alternative directions and evaluation criteria for implementers.

You should not use adversarial review for code review when feedback is actively progressing and addressing the core direction. It is specifically designed for stalled PRs where feedback recurs without progress and requires a new strategic direction.