bmad-review-adversarial-general

Review content for weaknesses, omissions, and defects with a Markdown findings list.

1|Updated Dec 22, 2022
One-click install
npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-review-adversarial-general-rinzler78
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-review-adversarial-general
Source: https://github.com/Rinzler78/osmosis-launcher/tree/main/.agents/skills/bmad-review-adversarial-general
Command: npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-review-adversarial-general-rinzler78

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you critically review content for gaps, weaknesses, and mistakes that a superficial pass would miss. It is designed for situations where you need a skeptical second opinion on a spec, diff, document, or other artifact.

Core Features & Use Cases

  • Adversarial Review: Examines content with extreme skepticism and looks for missing details, contradictions, and weak assumptions.
  • Findings Report: Produces a concise Markdown list of issues to fix or improve.
  • Use Case: Use it to review a proposal, change set, or design doc when you want a rigorous critique before moving forward.

Quick Start

Ask the skill to perform an adversarial review of the provided content and return the findings as a Markdown list.

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 design document?

An adversarial review examines content with extreme skepticism to identify missing details, contradictions, and weak assumptions that a casual read would miss. It outputs a concise Markdown list of issues requiring fixes or improvements.

Can I use this for critical analysis of code diffs and specs?

Yes, critical analysis of code diffs and specs is supported. The review evaluates these artifacts for gaps, weaknesses, and mistakes, returning a structured Markdown findings list to ensure rigorous critique before moving forward.

What is the best way to find flaws in a proposal before moving forward?

The best way to find flaws is requesting a skeptical evaluation of the proposal. This process identifies omissions, defects, and contradictions, producing a Markdown findings list that highlights issues to fix before proceeding.

Does this adversarial review require any external components or dependencies?

No external components or dependencies are required. The review relies entirely on careful issue identification to evaluate documents, diffs, and specs, producing a standalone Markdown findings list without needing external integrations.

What format does the findings report use for identified document weaknesses?

The findings report uses a concise Markdown list format. It details the weaknesses, omissions, and defects discovered during the skeptical evaluation, providing a structured output for fixing or improving the reviewed artifact.