bmad-review-adversarial-general

An adversarial review of project documentation applies a skeptical persona to identify at least ten missing requirements or hidden flaws, ensuring technical specifications and code diffs are rigorously checked before final submission.

Adversarial analysis for code diffs and project documentation is a skeptical quality assurance technique that uncovers hidden flaws and missing requirements, enforcing a mandatory minimum of ten critical findings to guarantee high-quality output.

Yes, you can use an adversarial critique to find missing requirements in a pull request by applying a jaded, skeptical persona to rigorously examine code diffs, guaranteeing the identification of at least ten critical improvements or missing elements.

This critical review method works on both code and general documentation, operating across diverse content artifacts including project stories, technical specifications, and code diffs to ensure high-quality output through skeptical analysis.

A rigorous quality assurance review requires a mandatory minimum of ten findings, enforcing a deep, cynical examination of content artifacts to prevent superficial reviews and ensure potential issues are fully identified before they become problems.