bmad-review-adversarial-general

Identify defects and inconsistencies in submitted content and produce a Markdown findings report.

1|Updated Mar 31, 2026

Search Tags:#audit #analysis #review #critique #adversarial #findings

Ready to run

npx skills add https://github.com/mol4/BMAD-Board --skill bmad-review-adversarial-general-mol4

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-review-adversarial-general
Source: https://github.com/mol4/BMAD-Board/tree/main/BMAD%20board/.agents/skills/bmad-review-adversarial-general
Command: npx skills add https://github.com/mol4/BMAD-Board --skill bmad-review-adversarial-general-mol4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It finds weaknesses, omissions, and inconsistencies in submitted content when a skeptical review is needed, so issues are surfaced before they become costly mistakes.

Core Features & Use Cases

Adversarial inspection: Examines diffs, branches, uncommitted changes, documents, and specs with a critical eye.
Findings-only output: Produces a concise Markdown list of actionable issues instead of a narrative summary.
Use Case: Review a story spec before implementation, or inspect a code change before merge, to catch missing requirements, vague logic, and hidden risks.

Quick Start

Ask the skill to review the provided artifact and return a Markdown findings list.

Frequently Asked Questions about bmad-review-adversarial-general

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I perform an adversarial review on a code diff before merging?▼

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.

What is an adversarial spec review and when do I need it?▼

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.

How do I get a findings report for uncommitted changes in my branch?▼

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.

Can I use this to review a story spec before implementation?▼

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.

What are the limitations of automated adversarial code review?▼

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.

Does the adversarial review output include suggested fixes for the findings?▼

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.