bmad-adversarial-review

Identifies ten or more weaknesses in documents, artifacts, or code diffs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/KatTate/Bmad-for-Replit --skill bmad-adversarial-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-adversarial-review
Source: https://github.com/KatTate/Bmad-for-Replit/tree/main/.agents/skills/bmad-adversarial-review
Command: npx skills add https://github.com/KatTate/Bmad-for-Replit --skill bmad-adversarial-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a highly critical and skeptical review of any document, code diff, or artifact, ensuring that potential issues are identified before they become problems.

Core Features & Use Cases

  • Cynical Quality Assurance: Applies a rigorous, problem-seeking lens to any content.
  • Issue Identification: Guarantees the discovery of at least ten distinct issues or areas for improvement.
  • Use Case: Submit a draft of a new product requirements document (PRD) to this Skill to receive a harsh critique, highlighting ambiguities, missing sections, and potential flaws in the proposed features.

Quick Start

Perform an adversarial review on the attached document.

Frequently Asked Questions about bmad-adversarial-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform an adversarial review on a document or code diff?▼

To perform an adversarial review, submit your document, code diff, or artifact for analysis. The process applies a cynical, skeptical lens to identify at least ten distinct issues, omissions, or areas for improvement before release.

What is an adversarial review for quality assurance?▼

An adversarial review for quality assurance is a rigorous, problem-seeking analysis of artifacts. It uncovers ambiguities, missing sections, and potential flaws by deliberately applying a highly critical and skeptical lens to the content.

Can I use a cynical critique to find flaws in a product requirements document?▼

Yes, you can submit a product requirements document (PRD) to receive a harsh critique. The review highlights ambiguities, missing sections, and potential flaws in the proposed features to ensure robust pre-release validation.

Does this artifact analysis guarantee a minimum number of issues found?▼

Yes, the artifact analysis guarantees the discovery of at least ten distinct issues. It requires a robust analytical process to uncover omissions and flaws, ensuring comprehensive risk assessment for your workflow.

What is the best way to validate artifacts before a release?▼

The best way to validate artifacts before a release is to apply a skeptical, problem-seeking review. This pre-release validation workflow identifies hidden flaws and omissions in documents or code diffs before they escalate into problems.

When do I need a skeptical risk assessment for my artifacts?▼

You need a skeptical risk assessment for your artifacts when preparing for pre-release validation. This process ensures potential flaws and omissions in documents or code diffs are identified early through rigorous, cynical analysis.