bmad-review-adversarial-general

Identify at least ten hidden flaws in code diffs, documentation, or project specifications.

Updated Jul 11, 2026
One-click install
npx skills add https://github.com/marcmontecalvo/kinward --skill bmad-review-adversarial-general-marcmontecalvo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-review-adversarial-general
Source: https://github.com/marcmontecalvo/kinward/tree/main/.agents/skills/bmad-review-adversarial-general
Command: npx skills add https://github.com/marcmontecalvo/kinward --skill bmad-review-adversarial-general-marcmontecalvo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the tendency to overlook critical flaws in documentation, code, or project specifications by applying a structured, adversarial review process that forces the identification of potential failure points.

Core Features & Use Cases

  • Adversarial Analysis: Systematically identifies at least ten potential issues or missing elements in any provided artifact.
  • Critical Perspective: Adopts a jaded, skeptical persona to ensure that assumptions are challenged and sloppy work is exposed.
  • Use Case: Use this skill when you have a draft project specification or a complex pull request and need a rigorous, cynical audit to ensure no edge cases or logical gaps were missed before final submission.

Quick Start

Ask the agent to perform an adversarial review of the provided document or code diff to identify at least ten potential issues.

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 project specification?

To perform an adversarial review, provide the content of your code diff, documentation, or project specification to the agent and request a cynical audit to identify at least ten potential issues or missing requirements.

What is an adversarial review and when do I need it for technical documentation?

Adversarial review is a critical analysis process that applies a jaded, skeptical perspective to technical artifacts to expose hidden flaws and challenge assumptions. You need it when high-quality output is required before final submission of drafts or complex pull requests.

Can I use this critical analysis approach for both code and documentation?

Yes, this critical analysis approach works on code diffs, documentation, and project specifications by systematically identifying potential failure points and missing requirements across any provided technical or project artifact.

What are the limitations of using a cynical audit for quality assurance?

The cynical audit requires you to input the content to be analyzed and is designed to identify at least ten potential issues, meaning it focuses exclusively on exposing flaws and missing requirements rather than suggesting fixes or validating correct implementations.