bmad-review-adversarial-general

Name: bmad-review-adversarial-general
Availability: InStock
Author: ImaginerLabs

Perform adversarial reviews of artifacts and produce prioritized Markdown findings.

Updated Apr 10, 2026

Search Tags:#quality-assurance #code-review #documentation-review #findings #adversarial-review #critical-review

Ready to run

npx skills add https://github.com/ImaginerLabs/skill-manager --skill bmad-review-adversarial-general-imaginerlabs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-review-adversarial-general
Source: https://github.com/ImaginerLabs/skill-manager/tree/main/.trae/skills/bmad-review-adversarial-general
Command: npx skills add https://github.com/ImaginerLabs/skill-manager --skill bmad-review-adversarial-general-imaginerlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a forceful, adversarial review to uncover overlooked defects, omissions, and weaknesses in artifacts so stakeholders receive a precise findings report instead of superficial feedback.

Core Features & Use Cases

Adversarial analysis: Adopt a skeptical reviewer persona to identify faults, gaps, and unclear assumptions across diffs, specs, stories, and documentation.
Structured output: Produce a prioritized Markdown list of findings with clear descriptions suitable for code reviews, design critiques, and audit reports.
Enforced rigor: Require at least ten findings and include halt conditions when content is empty or produces zero findings to avoid false positives.
Use Case: Run this on a pull request diff or product spec when you need a rigorous quality audit that surfaces both technical defects and missing requirements.

Quick Start

Run a cynical adversarial review on the provided document and return a Markdown list of at least ten prioritized findings.

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 code review on a pull request diff?▼

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.

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

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.

Can I use a cynical review approach to find missing requirements in product specs?▼

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.

How do I get structured findings from a quality audit of uncommitted changes?▼

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.

What happens if my code review content is empty or yields zero findings?▼

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.

Does the adversarial review enforce a minimum number of findings per document?▼

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.