bmad-review-adversarial-general

Critique user-provided artifacts adversarially and produce a findings report.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/clovernguyen1010-ship-it/Clover_Nguyen --skill bmad-review-adversarial-general-clovernguyen1010-ship-it
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-review-adversarial-general
Source: https://github.com/clovernguyen1010-ship-it/Clover_Nguyen/tree/main/_bmad/core/bmad-review-adversarial-general
Command: npx skills add https://github.com/clovernguyen1010-ship-it/Clover_Nguyen --skill bmad-review-adversarial-general-clovernguyen1010-ship-it

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables users to perform adversarial, skeptical reviews of content and produce structured findings reports that highlight gaps, inconsistencies, and risks.

Core Features & Use Cases

  • Adversarial Analysis: Rigorously question assumptions and identify a broad set of issues or improvement opportunities in the provided content.
  • Findings Report: Generate a concise, professional report detailing problems, impacts, and recommended fixes.
  • Flexible Artifacts: Suitable for reviewing diffs, specs, stories, docs, or any artifact the user provides.

Quick Start

Provide a cynical review of the provided content and generate a findings report.

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 of my documentation to find gaps?

To perform an adversarial content review, you provide your artifacts and the Skill applies a skeptical lens to rigorously question assumptions. It then generates a concise findings report detailing problems, impacts, and recommended fixes.

What is an adversarial content review and when should I use it?

An adversarial content review is a skeptical analysis technique used to surface hidden issues and gaps in artifacts like diffs, specs, or stories. You need it when you want to rigorously question assumptions and identify risks before finalizing content.

Can I use this to review code diffs and technical specifications?

Yes, you can review code diffs and technical specifications. The adversarial review process is flexible and suitable for analyzing various artifacts, including diffs, specs, stories, and any documentation provided by the user.

How do I generate a structured findings report from a content critique?

To generate a structured findings report from a content critique, the Skill identifies at least ten issues and produces a concise professional report. This report explicitly details the discovered problems, their impacts, and recommended fixes.

What is the difference between a standard quality assurance check and a cynical review?

A cynical review goes beyond standard quality assurance by actively applying a skeptical lens to question underlying assumptions. It focuses on adversarial findings to surface deep inconsistencies and gaps rather than just checking for surface-level errors.

Are there limitations to what an adversarial review can analyze?

The primary limitation is that the adversarial review requires the user to provide the artifacts explicitly. It focuses on analyzing the supplied content like docs or specs rather than autonomously discovering or pulling external data for review.