bmad-review-adversarial-general

An adversarial review applies skeptical analysis to your specs or documentation to surface missing requirements, weak reasoning, and practical failure points early. It generates a Markdown list of at least ten findings to triage potential issues.

To perform a cynical spec review, submit your diff, spec, story, or documentation content. The analysis systematically searches for missing or weak elements, returning a Markdown list of at least ten actionable risk findings.

Yes, you can use adversarial review for diffs, specs, stories, and documentation quality assurance. It flexibly processes these input types to detect missing or weak elements early before artifacts ship.

The best way to surface practical failure points is a cynical adversarial analysis that assumes incompleteness rather than validity. It generates a findings-focused Markdown list containing descriptions of issues for easy triage.

The adversarial review output includes descriptions only, formatted as a Markdown list. It focuses on surfacing at least ten actionable findings rather than providing detailed remediation steps or implementation guidance.

You need an adversarial review for compliance and governance artifacts when you must detect missing requirements, weak reasoning, and practical failure points early. It ensures skeptical analysis is applied before shipping.