bmad-review-adversarial-general

Critically review content and output at least ten issues as a Markdown list.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the need for a thorough, critical review of various content types by simulating a skeptical and experienced reviewer. It helps identify potential weaknesses, omissions, and areas for improvement that might be overlooked in a standard review.

Core Features & Use Cases

  • Critical Analysis: Performs a deep, skeptical review of provided content.
  • Finding Identification: Uncovers at least ten issues or areas for improvement.
  • Structured Reporting: Outputs findings as a clear, concise Markdown list.
  • Use Case: Use this Skill when submitting a new feature specification to ensure all potential edge cases and ambiguities are addressed before development begins.

Quick Start

Use the bmad-review-adversarial-general skill to critically review the attached document.

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

An adversarial review simulates a skeptical reviewer to critically analyze your feature specification, uncovering at least ten missing elements and potential problems. It outputs findings as a structured Markdown list for easy tracking.

What is the best way to find flaws in a code diff before merging?

Finding flaws in a code diff requires a cynical critical review that applies skeptical analysis to uncover at least ten issues or areas for improvement. It outputs the findings as a clear Markdown list.

Can I critically review user stories for missing edge cases?

You can critically review user stories to ensure all potential edge cases and ambiguities are addressed. The review simulates an experienced reviewer to uncover at least ten issues or areas for improvement before development begins.

Does this critical review method work on technical documentation?

This critical review method works on technical documentation, specifications, and code diffs. It performs a deep skeptical analysis to identify at least ten issues or areas for improvement, outputting findings as a concise Markdown list.

How do I get a structured Markdown list of issues from a document review?

To get a structured Markdown list of issues, perform a cynical and critical review of your document. The process requires skeptical analysis to uncover at least ten missing elements and potential problems, outputting findings directly as a Markdown list.