bmad-review-adversarial-general

Analyze content adversarially and output a Markdown findings list.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/AhmedKaram50/research --skill bmad-review-adversarial-general-ahmedkaram50
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-review-adversarial-general
Source: https://github.com/AhmedKaram50/research/tree/main/shopify-builder/_bmad/core/skills/bmad-review-adversarial-general
Command: npx skills add https://github.com/AhmedKaram50/research --skill bmad-review-adversarial-general-ahmedkaram50

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performs a cynical, thorough evaluation of user-submitted content and delivers a structured findings report that highlights issues, gaps, and risks.

Core Features & Use Cases

  • Adversarial analysis: identify problems, gaps, and risks in content.
  • Structured findings: generate a concise, prioritized report suitable for decision-making.
  • Use Case: when you need a critical, professional critique of a document, diff, spec, or story.

Quick Start

Provide a cynical review of the given artifact and deliver a structured 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 analysis of a technical document?

Adversarial analysis of a technical document requires loading the content into a deterministic workflow that critically evaluates it for issues, gaps, and risks, ultimately outputting a prioritized Markdown findings report suitable for decision-making.

What is a cynical content review and when should I use it?

A cynical content review is a critical evaluation method used to uncover hidden problems and risks in artifacts like specs or diffs. You need this when a thorough, professional critique is required for quality assurance before finalizing documentation.

Can I use this to generate a structured findings report for a design critique?

Yes, you can use this to generate a structured findings report for a design critique. It applies adversarial analysis to any artifact requiring critical evaluation, delivering a concise, prioritized Markdown list of issues and risks.

How do I get a prioritized issues list from a code diff or spec?

To get a prioritized issues list from a code diff or spec, provide the artifact for adversarial analysis. The workflow evaluates the content and outputs a Markdown findings list highlighting problems, gaps, and risks in a professional tone.

Does this adversarial review workflow work with any document format?

The adversarial review workflow works with documents, diffs, specs, or any artifact requiring critical evaluation. It loads content from inputs and deterministically processes it to identify issues across product reviews and documentation audits.

Are there limitations to using an automated critique for quality assurance?

A limitation of automated critique for quality assurance is its deterministic and cynical nature, which focuses strictly on identifying problems, gaps, and risks rather than suggesting positive attributes or creative improvements to the content.