bmad-review-adversarial-general
Cynically review your work to find missing edge cases and sloppy errors.
Install
mkdir -p .claude/skills/bmad-review-adversarial-general && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12659" && unzip -o skill.zip -d .claude/skills/bmad-review-adversarial-general && rm skill.zipInstalls to .claude/skills/bmad-review-adversarial-general
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Perform a Cynical Review and produce a findings report. Use when the user requests a critical review of somethingKey capabilities
- →Perform cynical review of content
- →Identify hidden issues and missing requirements
- →Look for problems and what is missing
- →Output findings as a Markdown list
- →Maintain a precise, professional tone
How it works
The skill adopts a cynical reviewer persona to analyze content with extreme skepticism, aiming to find at least ten issues and present them as a Markdown list.
Inputs & outputs
When to use bmad-review-adversarial-general
- →Reviewing a technical specification
- →Cynically auditing a pull request
- →Finding flaws in documentation
- →Analyzing edge cases in code
About this skill
Adversarial Review (General)
Goal: Cynically review content and produce findings.
Your Role: You are a cynical, jaded reviewer with zero patience for sloppy work. The content was submitted by a clueless weasel and you expect to find problems. Be skeptical of everything. Look for what's missing, not just what's wrong. Use a precise, professional tone — no profanity or personal attacks.
Inputs:
- content — Content to review: diff, spec, story, doc, or any artifact
- also_consider (optional) — Areas to keep in mind during review alongside normal adversarial analysis
EXECUTION
Step 1: Receive Content
- Load the content to review from provided input or context
- If content to review is empty, ask for clarification and abort
- Identify content type (diff, branch, uncommitted changes, document, etc.)
Step 2: Adversarial Analysis
Review with extreme skepticism — assume problems exist. Find at least ten issues to fix or improve in the provided content.
Step 3: Present Findings
Output findings as a Markdown list (descriptions only).
HALT CONDITIONS
- HALT if zero findings — this is suspicious, re-analyze or ask for guidance
- HALT if content is empty or unreadable
When not to use it
- →When a neutral or positive review is desired
- →When the content is empty or unreadable
Limitations
- →HALT if zero findings
- →HALT if content is empty or unreadable
- →No profanity or personal attacks
How it compares
This skill provides a structured adversarial review, specifically intended to uncover problems and missing elements, which differs from a standard, less critical review process.
Compared to similar skills
bmad-review-adversarial-general side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| bmad-review-adversarial-general (this skill) | 0 | 4mo | No flags | Intermediate |
| specification-architect | 13 | 9mo | Review | Advanced |
| linear-ticket | 1 | 7mo | No flags | Intermediate |
| business-analyst-authority | 0 | 4mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by youranreus
View all by youranreus →You might also like
specification-architect
adrianpuiu
A rigorous, traceability-first system that generates five interconnected architectural documents (blueprint.md, requirements.md, design.md, tasks.md, and validation.md) with complete requirements-to-implementation traceability. Use this skill when users need to architect systems, create technical specifications, or develop structured project documentation with guaranteed traceability.
linear-ticket
useautumn
Refine rough engineering thoughts into structured Linear tickets with GitHub permalinks
business-analyst-authority
ahmedemad3
Act as a Principal Business Analyst (8+ years exp) bridging the gap between Strategy and Execution. Specializes in translating vague vision into rigorous technical specifications using Gherkin (BDD), BPMN 2.0, and strict Requirement Engineering standards.
adr
rvdbreemen
Architecture Decision Record (ADR) management skill. Creates, maintains, and enforces architectural decisions. Ensures code changes align with documented decisions. Documents alternatives considered and rejected. Facilitates architectural planning and human decision documentation.
humanize-refine-plan
PolyArch
Refine an annotated implementation plan into a comment-free plan and a QA ledger while preserving the gen-plan schema.
fmea-analysis
ddunnock
Conduct Failure Mode and Effects Analysis (FMEA) for systematic identification and risk assessment of potential failures in designs, processes, or systems. Supports DFMEA (Design), PFMEA (Process), and FMEA-MSR (Monitoring & System Response). Uses AIAG-VDA 7-step methodology with Action Priority (AP