bmad-review-adversarial-general

Critique submitted content and produce a structured Markdown findings report.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Yukine5377/common --skill bmad-review-adversarial-general-yukine5377
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-review-adversarial-general
Source: https://github.com/Yukine5377/common/tree/main/.cursor/skills/bmad-review-adversarial-general
Command: npx skills add https://github.com/Yukine5377/common --skill bmad-review-adversarial-general-yukine5377

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Content review often requires a skeptical, structured approach to identify gaps, inconsistencies, and risks. This Skill provides a disciplined adversarial review workflow that yields a concise findings report, helping teams improve quality and reduce blind spots.

Core Features & Use Cases

  • Adversarial analysis: Rigorously critiques input content to surface issues beyond surface-level critique.
  • Structured findings: Outputs a clear, prioritized list of issues with actionable recommendations.
  • Use Case: Use when you need a critical evaluation of specifications, design docs, or proposals to strengthen quality and compliance.

Quick Start

Provide the content you want reviewed and I will return 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
What is adversarial content review and how does it identify documentation risks?

Adversarial content review is a skeptical critique process that rigorously analyzes specifications, diffs, and docs to surface gaps, inconsistencies, and risks. It identifies at least ten issues and presents them in a structured Markdown findings report to reduce blind spots.

How do I conduct a cynical review of a design document or specification?

To conduct a cynical review, provide the design document or specification content directly. The review will rigorously critique the input to surface issues beyond surface-level flaws, yielding a prioritized findings report with actionable recommendations in Markdown format.

Can I use this adversarial review on code diffs and user stories?

Yes, you can use this adversarial review on code diffs, user stories, specifications, and other documentation artifacts. It applies a skeptical critique across various content types to identify at least ten issues and produce a structured findings report.

What's the best way to get structured findings from a quality assurance content review?

The best way to get structured findings is to submit your content for a disciplined adversarial review. This process yields a concise, prioritized Markdown list of at least ten identified issues with actionable recommendations for improving quality and compliance.

Does the content review output a fixed number of issues, or does it vary by input?

The content review output identifies at least ten issues per submission, ensuring a thorough adversarial analysis. It presents these findings in a clear, structured Markdown list with actionable recommendations, regardless of input size.

When should I not use an adversarial approach for content review?

You should not use an adversarial approach when you need a quick, surface-level approval rather than a deep, skeptical critique. This method is designed to rigorously identify at least ten issues, which may be excessive for straightforward content checks.