bmad-review-adversarial-general

Review content adversarially and generate at least ten critical findings as Markdown.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill provides a skeptical, adversarial review of any content—code diffs, specifications, stories, or documents—and delivers a concise list of critical issues, helping users quickly identify hidden problems.

Core Features & Use Cases

  • Adversarial analysis: Generates at least ten critical findings for the supplied artifact.
  • Versatile input: Accepts various content types such as diffs, specs, stories, or documents.
  • Focused output: Returns findings as a plain Markdown list, ready for inclusion in reports or further discussion.

Quick Start

Ask the skill to review your document and return a list of critical 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 of a code diff or specification?

To perform an adversarial review, supply the skill with your code diff, specification, or document content, and it will output a concise Markdown list of at least ten critical findings.

What is adversarial analysis and how does it find critical issues in documents?

Adversarial analysis applies a skeptical critique to provided content like stories or documents, systematically probing for vulnerabilities to deliver a focused list of critical issues.

Can I use this adversarial review skill on any type of project document?

Yes, the skill accepts versatile input formats including code diffs, specifications, stories, and general documents, requiring only the content input to generate its critical findings.

What's the best way to get a concise list of critical findings from a spec?

The best way to get concise findings from a spec is to run an adversarial review, which processes the provided content and outputs a plain Markdown list of at least ten critical issues.

Do I need any additional dependencies to generate critical findings for my code?

No dependencies are required; the skill needs only the content input and optionally additional considerations to perform the review and output the critical findings list.