bmad-review-adversarial-general

Adversarial code review examines pull request diffs using a skeptical persona to uncover defects, omissions, and unclear assumptions, returning a prioritized Markdown findings list of at least ten actionable issues.

Adversarial review is a rigorous quality audit that critically examines specifications, stories, and documents to surface overlooked weaknesses. You need it when superficial feedback is insufficient and a precise gap analysis is required.

Yes, cynical review applies skeptical analysis to product specs to identify missing requirements and faults. It enforces at least ten findings to ensure rigorous coverage instead of superficial feedback.

A quality audit of uncommitted changes generates structured findings by applying adversarial analysis to the content, producing a prioritized Markdown list with clear descriptions of defects and weaknesses suitable for review reports.

If code review content is empty or yields zero findings, the adversarial review process halts immediately. This prevents false positives and ensures only non-empty readable content undergoes the skeptical analysis.

Yes, adversarial review enforces at least ten findings per document to maintain analytical rigor. This requirement ensures a thorough quality audit that surfaces both technical defects and missing requirements rather than stopping prematurely.