diff --git a/src/modules/bmm/workflows/4-implementation/code-review/workflow.md b/src/modules/bmm/workflows/4-implementation/code-review/workflow.md
index 18318235..b6bb3c2a 100644
--- a/src/modules/bmm/workflows/4-implementation/code-review/workflow.md
+++ b/src/modules/bmm/workflows/4-implementation/code-review/workflow.md
@@ -23,6 +23,8 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
- `planning_artifacts`, `implementation_artifacts`
- `date` as system-generated current datetime
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
### Paths
- `installed_path` = `{project-root}/_bmad/bmm/workflows/4-implementation/code-review`
@@ -32,19 +34,6 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
---
-## CRITICAL DIRECTIVES
-
-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
-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
-Exclude `_bmad/`, `_bmad-output/`, `.cursor/`, `.windsurf/`, `.claude/` from review
-
----
-
## EXECUTION
Load and execute `steps/step-01-load-story.md` to begin the workflow.