story-review renamed code-review and dev-agent performs this

src/modules/bmm/workflows/4-implementation/dev-story/README.md

@@ -4,7 +4,7 @@ The dev-story workflow is where v6's just-in-time context approach delivers its
 
 The workflow operates with two critical inputs: the story file (created by SM's create-story) containing acceptance criteria, tasks, and requirements; and the story-context XML (generated by SM's story-context) providing just-in-time expertise injection tailored to the story's technical needs. This dual-input approach ensures the developer has both the "what" (from the story) and the "how" (from the context) needed for successful implementation. The workflow iterates through tasks sequentially, implementing code, writing tests, and updating the story document's allowed sections until all tasks are complete.
 
-A critical aspect of v6 flow is that dev-story may be run multiple times for the same story. Initially run to implement the story, it may be run again after review-story identifies issues that need correction. The workflow intelligently resumes from incomplete tasks, making it ideal for both initial implementation and post-review fixes. The DEV agent maintains strict boundaries on what can be modified in the story file—only Tasks/Subtasks checkboxes, Dev Agent Record, File List, Change Log, and Status may be updated, preserving the story's requirements integrity.
+A critical aspect of v6 flow is that dev-story may be run multiple times for the same story. Initially run to implement the story, it may be run again after code-review identifies issues that need correction. The workflow intelligently resumes from incomplete tasks, making it ideal for both initial implementation and post-review fixes. The DEV agent maintains strict boundaries on what can be modified in the story file—only Tasks/Subtasks checkboxes, Dev Agent Record, File List, Change Log, and Status may be updated, preserving the story's requirements integrity.
 
 ## Usage
 
@@ -20,7 +20,7 @@ The DEV runs this workflow:
 
 - After SM completes both create-story and story-context
 - When a story status is "Draft" or "Approved" (ready for development)
-- After review-story identifies issues requiring fixes
+- After code-review identifies issues requiring fixes
 - To resume work on a partially completed story
 
 ## Inputs
@@ -82,7 +82,7 @@ The DEV runs this workflow:
 
 **Test-Driven Approach**: For each task, the workflow emphasizes writing tests that verify acceptance criteria before or alongside implementation, ensuring requirements are actually met.
 
-**Resumable Implementation**: If the workflow is run again on a story with incomplete tasks (e.g., after review-story finds issues), it intelligently resumes from where it left off rather than starting over.
+**Resumable Implementation**: If the workflow is run again on a story with incomplete tasks (e.g., after code-review finds issues), it intelligently resumes from where it left off rather than starting over.
 
 ## Integration with v6 Flow
 
@@ -91,7 +91,7 @@ The dev-story workflow is step 3 in the v6 implementation cycle:
 1. SM: create-story (generates the story specification)
 2. SM: story-context (adds JIT technical expertise)
 3. **DEV: dev-story** ← You are here (initial implementation)
-4. DEV/SR: review-story (validates completion)
+4. DEV/SR: code-review (validates completion)
 5. If issues found: **DEV: dev-story** ← May return here for fixes
 6. After epic: retrospective (captures learnings)
 
@@ -182,7 +182,7 @@ As a {role}, I want to {action} so that {benefit}
 
 **Update Incrementally**: Update the story file after each task completion rather than batching updates at the end.
 
-**Respect Boundaries**: Never modify acceptance criteria or story description. If they seem wrong, that's a review-story or correct-course issue, not a dev-story fix.
+**Respect Boundaries**: Never modify acceptance criteria or story description. If they seem wrong, that's a code-review or correct-course issue, not a dev-story fix.
 
 **Use Context Guidance**: Actively reference the story-context for patterns, gotchas, and best practices. It's there to help you succeed.
 
@@ -196,11 +196,11 @@ As a {role}, I want to {action} so that {benefit}
 
 **Can't Modify Story Section**: Remember only Tasks, Dev Agent Record, File List, Change Log, and Status can be modified. Other sections are immutable.
 
-**Resuming After Review**: If review-story found issues, the workflow automatically picks up from incomplete tasks when run again.
+**Resuming After Review**: If code-review found issues, the workflow automatically picks up from incomplete tasks when run again.
 
 ## Related Workflows
 
 - **create-story**: Creates the story specification (run by SM)
 - **story-context**: Generates the context XML (run by SM)
-- **review-story**: Validates implementation (run by SR/DEV)
+- **code-review**: Validates implementation (run by SR/DEV)
 - **correct-course**: Handles major issues or scope changes (run by SM)

src/modules/bmm/workflows/4-implementation/dev-story/instructions.md

@@ -188,7 +188,7 @@ Story is marked Ready for Review in file, but sprint-status.yaml may be out of s
       - Review the implemented story yourself and test the changes
       - Verify all acceptance criteria are met
       - Ensure deployment readiness if applicable
-      - Run `review-story` workflow for peer review
+      - Run `code-review` workflow for peer review
       - Check sprint-status.yaml to see project progress
     </action>
     <action>Remain flexible - allow user to choose their own path or ask for other assistance</action>