bmad-review-adversarial-general

Review submitted content for weaknesses and missing information.

Updated May 17, 2026
One-click install
npx skills add https://github.com/thuantan2060/facebook-sale-tracking --skill bmad-review-adversarial-general-thuantan2060
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-review-adversarial-general
Source: https://github.com/thuantan2060/facebook-sale-tracking/tree/main/.agents/skills/bmad-review-adversarial-general
Command: npx skills add https://github.com/thuantan2060/facebook-sale-tracking --skill bmad-review-adversarial-general-thuantan2060

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you critically assess content (like diffs, specs, or docs) by uncovering missing context, weaknesses, and risks before they become expensive problems.

Core Features & Use Cases

  • Cynical adversarial analysis: Reviews submitted material with deliberate skepticism to surface overlooked issues.
  • Actionable findings report: Produces a clear Markdown list of findings aimed at improvement rather than politeness.
  • Supports multiple artifact types: Works for diffs, specs, stories, and general documentation workflows.

Quick Start

Ask the skill to adversarially review the provided content and return at least ten concrete findings as a Markdown 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 document or specification?

To perform an adversarial review, submit your document or specification to the Skill, which analyzes the content with deliberate skepticism to identify weaknesses and missing information, returning a Markdown list of at least ten actionable findings.

What is adversarial spec review and how does it identify risks?

Adversarial spec review is a critical assessment technique that examines specifications with deliberate skepticism to surface overlooked issues, missing context, and risks, producing actionable feedback aimed at improvement rather than politeness.

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

Yes, you can review code diffs and technical stories. The Skill supports multiple artifact types including diffs, specifications, stories, and general documentation workflows to provide critical feedback.

What happens if the submitted content is empty or has zero findings?

If the submitted content is empty or the adversarial review produces zero findings, the Skill will halt processing to ensure that only valid, readable input generates a meaningful critical feedback report.

How do I get critical feedback for quality assurance on my documentation?

You get critical feedback for quality assurance by loading your documentation into the Skill, which cynically reviews the material and outputs a Markdown list of at least ten concrete findings targeting weaknesses and missing information.