Menu
Perform a Cynical Review and produce a findings report. Use when the user requests a critical review of something
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
One iteration of an unattended development loop. Use when invoked by name.
Distill any intent input into the SPEC kernel + companions — the canonical, preservation-validated machine contract for downstream work. Use when the user says "create a spec", "distill this into a spec", "validate this spec", "update the spec", or "break this into stories".
Adversarial code review using parallel review layers and structured triage. Use when the user says "run code review" or "review this code"
Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project's existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.
Review a code change for changed behavior that could regress without reliable verification catching it. Use when checking whether a change is adequately verified.
Analyzes current state and user query to answer BMad questions or recommend the next skill(s) to use. Use when user asks for help, bmad help, what to do next, or what to start with in BMad.
| 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 |
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:
Review with extreme skepticism — assume problems exist. Find at least ten issues to fix or improve in the provided content.
Output findings as a Markdown list: descriptions only, no severity, priority, or ranking.
