bmad-review-adversarial-general

To perform an adversarial review on a code diff, submit the diff or uncommitted changes for skeptical inspection to identify defects, omissions, and inconsistencies, receiving a concise Markdown list of actionable issues.

An adversarial spec review critically examines specifications and stories to find missing requirements and vague logic before implementation. You need it when a skeptical inspection is required to surface weaknesses before they become costly mistakes.

To get a findings report for uncommitted changes, provide the branch changes to the review process. It produces a findings-only Markdown list of at least ten actionable issues instead of a narrative summary.

Yes, you can review a story spec before implementation. It applies adversarial inspection to specifications and stories, catching missing requirements, vague logic, and hidden risks by generating a precise list of actionable issues.

A limitation of automated adversarial code review is that it requires readable input and halts when the submitted content is empty or unreadable. It also strictly outputs a findings list rather than providing narrative summaries or fixes.

No, the adversarial review output does not include suggested fixes. It produces a findings-only Markdown list of actionable issues, focusing entirely on exposing defects, omissions, and inconsistencies rather than implementing solutions.