bmad-review-adversarial-general

Analyze provided content to surface gaps and risks in a findings report.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cynically critique content to surface problems, gaps, and risks, then produce a findings report.

Core Features & Use Cases

  • Adversarial analysis: Identify gaps, ambiguities, and weaknesses in artifacts.
  • Structured findings: Produce a clear, prioritized list of issues and recommendations.
  • Use Case: Review a doc, spec, or code diff to surface actionable improvements.

Quick Start

Provide a cynical adversarial review of the provided content and deliver 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 conduct an adversarial review of a technical specification?

To conduct an adversarial review, provide the specification content for cynical critique. The review surfaces defects, gaps, and risks in requirements and design, then delivers a structured findings report with prioritized issues and actionable recommendations.

What is adversarial content analysis for risk identification?

Adversarial content analysis is a cynical critique process that uncovers hidden issues in documents or code. It exposes weaknesses in requirements, design, and implementation by identifying ambiguities and structural gaps across various artifacts.

Can I use this to review code diffs and documentation for quality assurance?

Yes, you can review code diffs and documentation for quality assurance. The analysis works across documents, specs, code diffs, and narratives to expose weaknesses and deliver a prioritized findings report with actionable improvements.

How do I get a structured findings report for document weaknesses?

You get a structured findings report by submitting your content for cynical adversarial review. The report delivers a clear, prioritized list of identified issues and actionable recommendations to improve the artifact.

What is the best way to surface hidden risks in a project narrative?

The best way to surface hidden risks in a project narrative is applying cynical adversarial critique. This process identifies gaps, ambiguities, and weaknesses, producing a prioritized findings report with actionable recommendations.

When should I not use an adversarial review approach?

You should not use an adversarial review when seeking positive reinforcement or validation of content. This approach cynically critiques artifacts to surface problems, gaps, and risks, focusing entirely on exposing weaknesses rather than confirming strengths.