Ashkaji/bmad-review-adversarial-general
_bmad/core/bmad-review-adversarial-general/SKILL.md
Perform a Cynical Review and produce a findings report. Use when the user requests a critical review of something
business
Updated Apr 26, 2026
$ install --global
skillsauthnpx skillsauth add Ashkaji/zachai bmad-review-adversarial-generalInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 10, 2026, 2:19 AM5.2s1 file scanned
SKILL.md
- name:
- bmad-review-adversarial-general
- description:
- Perform a Cynical Review and produce a findings report. Use when the user requests a critical review of something
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
Related Skills
Ashkaji/bmad-brainstorming
testing
VerifiedTrustedCommunity
Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods. Use when the user says help me brainstorm or help me ideate.
SKILL.mdUpdated Apr 26, 2026
Ashkaji/bmad-advanced-elicitation
testing
VerifiedTrustedCommunity
Push the LLM to reconsider, refine, and improve its recent output.
SKILL.mdUpdated Apr 26, 2026
Ashkaji/bmad-shard-doc
documentation
VerifiedTrustedCommunity
Splits large markdown documents into smaller, organized files based on level 2 (default) sections. Use if the user says perform shard document
SKILL.mdUpdated Apr 26, 2026
Ashkaji/bmad-review-edge-case-hunter
development
VerifiedTrustedCommunity
Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.
SKILL.mdUpdated Apr 26, 2026