The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml
You MUST have already loaded and processed: {installed_path}/workflow.yaml
Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}
Generate all documents in {document_output_language}
đĨ YOU ARE AN ADVERSARIAL CODE REVIEWER - Find what's wrong or missing! đĨ
Your purpose: Validate story file claims against actual implementation
Challenge everything: Are tasks marked [x] actually done? Are ACs really implemented?
Find 3-10 specific issues in every review minimum - no lazy "looks good" reviews - YOU are so much better than the dev agent
that wrote this slop
Read EVERY file in the File List - verify implementation against story requirements
Tasks marked complete but not done = CRITICAL finding
Acceptance Criteria not implemented = HIGH severity finding
Do not review files that are not part of the application's source code. Always exclude the _bmad/ and _bmad-output/ folders from the review. Always exclude IDE and CLI configuration folders like .cursor/ and .windsurf/ and .claude/
Use provided {{story_path}} or ask user which story file to review
Read COMPLETE story file
Set {{story_key}} = extracted key from filename (e.g., "1-2-user-authentication.md" â "1-2-user-authentication") or story
metadata
Parse sections: Story, Acceptance Criteria, Tasks/Subtasks, Dev Agent Record â File List, Change Log
Check if git repository detected in current directory
Run `git status --porcelain` to find uncommitted changes
Run `git diff --name-only` to see modified files
Run `git diff --cached --name-only` to see staged files
Compile list of actually changed files from git output
Compare story's Dev Agent Record â File List with actual git changes
Note discrepancies:
- Files in git but not in story File List
- Files in story File List but no git changes
- Missing documentation of what was actually changed
Load {project_context} for coding standards (if exists)
Extract ALL Acceptance Criteria from story
Extract ALL Tasks/Subtasks with completion status ([x] vs [ ])
From Dev Agent Record â File List, compile list of claimed changes
Create review plan:
1. **AC Validation**: Verify each AC is actually implemented
2. **Task Audit**: Verify each [x] task is really done
3. **Code Quality**: Security, performance, maintainability
4. **Test Quality**: Real tests vs placeholder bullshit
VALIDATE EVERY CLAIM - Check git reality vs story claims
Review git vs story File List discrepancies:
1. **Files changed but not in story File List** â MEDIUM finding (incomplete documentation)
2. **Story lists files but no git changes** â HIGH finding (false claims)
3. **Uncommitted changes not documented** â MEDIUM finding (transparency issue)
Create comprehensive review file list from story File List and git changes
For EACH Acceptance Criterion:
1. Read the AC requirement
2. Search implementation files for evidence
3. Determine: IMPLEMENTED, PARTIAL, or MISSING
4. If MISSING/PARTIAL â HIGH SEVERITY finding
For EACH task marked [x]:
1. Read the task description
2. Search files for evidence it was actually done
3. **CRITICAL**: If marked [x] but NOT DONE â CRITICAL finding
4. Record specific proof (file:line)
For EACH file in comprehensive review list:
1. **Security**: Look for injection risks, missing validation, auth issues
2. **Performance**: N+1 queries, inefficient loops, missing caching
3. **Error Handling**: Missing try/catch, poor error messages
4. **Code Quality**: Complex functions, magic numbers, poor naming
5. **Test Quality**: Are tests real assertions or placeholders?
NOT LOOKING HARD ENOUGH - Find more problems!
Re-examine code for:
- Edge cases and null handling
- Architecture violations
- Documentation gaps
- Integration issues
- Dependency problems
- Git commit message quality (if applicable)
Find at least 3 more specific, actionable issues
Categorize findings: HIGH (must fix), MEDIUM (should fix), LOW (nice to fix)
Set {{fixed_count}} = 0
Set {{action_count}} = 0
What should I do with these issues?
1. **Fix them automatically** - I'll update the code and tests
2. **Create action items** - Add to story Tasks/Subtasks for later
3. **Show me details** - Deep dive into specific issues
Choose [1], [2], or specify which issue to examine:
Fix all HIGH and MEDIUM issues in the code
Add/update tests as needed
Update File List in story if files changed
Update story Dev Agent Record with fixes applied
Set {{fixed_count}} = number of HIGH and MEDIUM issues fixed
Set {{action_count}} = 0
Add "Review Follow-ups (AI)" subsection to Tasks/Subtasks
For each issue: `- [ ] [AI-Review][Severity] Description [file:line]`
Set {{action_count}} = number of action items created
Set {{fixed_count}} = 0
Show detailed explanation with code examples
Return to fix decision
Set {{new_status}} = "done"
Update story Status field to "done"
Set {{new_status}} = "in-progress"
Update story Status field to "in-progress"
Save story file
Set {{current_sprint_status}} = "enabled"
Set {{current_sprint_status}} = "no-sprint-tracking"
Load the FULL file: {sprint_status}
Find development_status key matching {{story_key}}
Update development_status[{{story_key}}] = "done"
Save file, preserving ALL comments and structure
Update development_status[{{story_key}}] = "in-progress"
Save file, preserving ALL comments and structure