bmad-review-adversarial-general

Generate structured lists of at least ten critical findings from provided content.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need for a thorough, critical review of various artifacts by simulating a skeptical and experienced reviewer to identify potential flaws, omissions, and areas for improvement.

Core Features & Use Cases

  • Skeptical Analysis: Applies a critical lens to identify weaknesses in content.
  • Finding Generation: Produces a structured list of actionable findings.
  • Use Case: A software engineer submits a code diff for review. This Skill can be used to perform an adversarial review, uncovering potential bugs, security vulnerabilities, or areas where the code doesn't meet best practices.

Quick Start

Use the bmad-review-adversarial-general skill to perform a cynical review of the provided code diff.

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 code review to find critical bugs?

To perform an adversarial code review, you need a structured workflow that applies a cynical, skeptical lens to your code diff to identify at least ten potential flaws, security vulnerabilities, or best practice violations.

What is an adversarial review and when should I use it for document critique?

An adversarial review is a critical analysis process that simulates a skeptical reviewer to uncover weaknesses in documents or artifacts. Use it when you need a rigorous assessment to find omissions and areas for improvement before final delivery.

Can I use this skeptical analysis approach for non-code artifacts?

Yes, you can apply skeptical analysis to non-code artifacts. The review process is designed for document critiques and artifact analysis, generating a structured list of actionable findings wherever a critical perspective is required.

How do I generate a structured list of findings from a code diff?

You generate a structured list of findings by submitting your code diff to a cynical review workflow. The process mandates the identification of a minimum of ten issues based on professional skepticism, producing actionable critique results.

Are there limitations to using a cynical review for quality assurance?

A primary limitation of cynical review is its strict requirement to find at least ten issues, which may force negative findings on high-quality content. It focuses exclusively on critique and does not provide positive reinforcement or structural praise.