fa7e166f3e
- Add reminders page with navigation support - Upgrade BMad builder module to skills-based architecture - Refactor MCP server: extract tools and auth into separate modules - Add connections cache, custom AI provider support - Update prisma schema and generated client - Various UI/UX improvements and i18n updates - Add service worker for PWA support Made-with: Cursor
56 lines
2.0 KiB
Markdown
56 lines
2.0 KiB
Markdown
---
|
|
main_config: '{project-root}/_bmad/bmm/config.yaml'
|
|
---
|
|
|
|
# Code Review Workflow
|
|
|
|
**Goal:** Review code changes adversarially using parallel review layers and structured triage.
|
|
|
|
**Your Role:** You are an elite code reviewer. You gather context, launch parallel adversarial reviews, triage findings with precision, and present actionable results. No noise, no filler.
|
|
|
|
|
|
## WORKFLOW ARCHITECTURE
|
|
|
|
This uses **step-file architecture** for disciplined execution:
|
|
|
|
- **Micro-file Design**: Each step is self-contained and followed exactly
|
|
- **Just-In-Time Loading**: Only load the current step file
|
|
- **Sequential Enforcement**: Complete steps in order, no skipping
|
|
- **State Tracking**: Persist progress via in-memory variables
|
|
- **Append-Only Building**: Build artifacts incrementally
|
|
|
|
### Step Processing Rules
|
|
|
|
1. **READ COMPLETELY**: Read the entire step file before acting
|
|
2. **FOLLOW SEQUENCE**: Execute sections in order
|
|
3. **WAIT FOR INPUT**: Halt at checkpoints and wait for human
|
|
4. **LOAD NEXT**: When directed, read fully and follow the next step file
|
|
|
|
### Critical Rules (NO EXCEPTIONS)
|
|
|
|
- **NEVER** load multiple step files simultaneously
|
|
- **ALWAYS** read entire step file before execution
|
|
- **NEVER** skip steps or optimize the sequence
|
|
- **ALWAYS** follow the exact instructions in the step file
|
|
- **ALWAYS** halt at checkpoints and wait for human input
|
|
|
|
|
|
## INITIALIZATION SEQUENCE
|
|
|
|
### 1. Configuration Loading
|
|
|
|
Load and read full config from `{main_config}` and resolve:
|
|
|
|
- `project_name`, `planning_artifacts`, `implementation_artifacts`, `user_name`
|
|
- `communication_language`, `document_output_language`, `user_skill_level`
|
|
- `date` as system-generated current datetime
|
|
- `sprint_status` = `{implementation_artifacts}/sprint-status.yaml`
|
|
- `project_context` = `**/project-context.md` (load if exists)
|
|
- CLAUDE.md / memory files (load if exist)
|
|
|
|
YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`.
|
|
|
|
### 2. First Step Execution
|
|
|
|
Read fully and follow: `./steps/step-01-gather-context.md` to begin the workflow.
|