Menú
Perform a Cynical Review and produce a findings report. Use when the user requests a critical review of something
Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"
Break requirements into epics and user stories. Use when the user says "create the epics and stories list"
Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code"
Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]"
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.
Facilitate a brainstorming session using diverse creative techniques. Use when the user says 'help me brainstorm' or 'help me ideate'.
| 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).
