bmad-review-adversarial-general

Identify defects, gaps, and weak assumptions in submitted content with Markdown findings.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-review-adversarial-general-geneducation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-review-adversarial-general
Source: https://github.com/GenEducation/GenedUIProject/tree/main/.gemini/skills/bmad-review-adversarial-general
Command: npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-review-adversarial-general-geneducation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a skeptical review of submitted content so weak assumptions, missing requirements, and hidden defects are surfaced before the work is accepted.

Core Features & Use Cases

  • Adversarial Analysis: Inspects diffs, specs, stories, documents, or other artifacts with a critical mindset.
  • Findings Report: Produces a concise Markdown list of issues to fix or improve.
  • Use Case: A reviewer can run it on a branch diff or design spec to quickly collect actionable concerns before merge or approval.

Quick Start

Ask the skill to perform an adversarial review of the provided document and return a Markdown list of at least ten 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 review on a branch diff or design spec?

Adversarial review inspects diffs, specs, stories, and documents with a critical mindset to identify hidden defects and weak assumptions. You submit the content and receive a concise Markdown list of actionable issues to fix before approval or merge.

What is the best way to find weak assumptions in a draft document?

Finding weak assumptions requires a skeptical review of the submitted draft to surface missing requirements and gaps. Submitting the document for an adversarial analysis generates a Markdown list of at least ten concrete findings for improvement.

Can I use this adversarial critique on uncommitted changes?

Adversarial critique applies to uncommitted changes, branch diffs, and submitted artifacts. It requires readable input text to function; the review process halts if the provided content is empty or unreadable.

How many findings does an adversarial document review return?

An adversarial document review returns a Markdown list containing at least ten concrete findings. These findings detail specific defects, gaps, and weak assumptions discovered during the skeptical inspection of the submitted content.

What happens if I submit an empty document for a skeptical review?

Submitting an empty or unreadable document for skeptical review causes the process to halt immediately. The analysis requires valid, readable input text to identify defects and generate the Markdown findings report.