From 15a94a94b6f5e526735a01ca80005d027f11366c Mon Sep 17 00:00:00 2001
From: Brian Madison <brianmadison@Brians-MacBook-Pro.local>
Date: Wed, 12 Nov 2025 22:46:48 -0600
Subject: [PATCH] accept a story status of review or ready-for-review, treat
 them the same.

---
 .../workflows/4-production/code-review/instructions.md    | 8 ++++----
 .../4-implementation/code-review/instructions.md          | 8 ++++----
 2 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/src/modules/bmgd/workflows/4-production/code-review/instructions.md b/src/modules/bmgd/workflows/4-production/code-review/instructions.md
index 59b6ca6c..6280b8eb 100644
--- a/src/modules/bmgd/workflows/4-production/code-review/instructions.md
+++ b/src/modules/bmgd/workflows/4-production/code-review/instructions.md
@@ -23,7 +23,7 @@
       <action>Use {{story_path}} directly</action>
       <action>Read COMPLETE story file and parse sections</action>
       <action>Extract story_key from filename or story metadata</action>
-      <action>Verify Status is "review" - if not, HALT with message: "Story status must be 'review' to proceed"</action>
+      <action>Verify Status is "review" or "ready-for-review" - if not, HALT with message: "Story status must be 'review' or 'ready-for-review' to proceed"</action>
     </check>
 
     <check if="{{story_path}} is NOT provided">
@@ -35,11 +35,11 @@
       <action>Find FIRST story (reading in order from top to bottom) where:
         - Key matches pattern: number-number-name (e.g., "1-2-user-auth")
         - NOT an epic key (epic-X) or retrospective (epic-X-retrospective)
-        - Status value equals "review"
+        - Status value equals "review" OR "ready-for-review"
       </action>
 
-      <check if="no story with status 'review' found">
-        <output>📋 No stories with status "review" found
+      <check if="no story with status 'review' or 'ready-for-review' found">
+        <output>📋 No stories with status "review" or "ready-for-review" found
 
 **What would you like to do?**
 1. Run `dev-story` to implement and mark a story ready for review
diff --git a/src/modules/bmm/workflows/4-implementation/code-review/instructions.md b/src/modules/bmm/workflows/4-implementation/code-review/instructions.md
index 59b6ca6c..6280b8eb 100644
--- a/src/modules/bmm/workflows/4-implementation/code-review/instructions.md
+++ b/src/modules/bmm/workflows/4-implementation/code-review/instructions.md
@@ -23,7 +23,7 @@
       <action>Use {{story_path}} directly</action>
       <action>Read COMPLETE story file and parse sections</action>
       <action>Extract story_key from filename or story metadata</action>
-      <action>Verify Status is "review" - if not, HALT with message: "Story status must be 'review' to proceed"</action>
+      <action>Verify Status is "review" or "ready-for-review" - if not, HALT with message: "Story status must be 'review' or 'ready-for-review' to proceed"</action>
     </check>
 
     <check if="{{story_path}} is NOT provided">
@@ -35,11 +35,11 @@
       <action>Find FIRST story (reading in order from top to bottom) where:
         - Key matches pattern: number-number-name (e.g., "1-2-user-auth")
         - NOT an epic key (epic-X) or retrospective (epic-X-retrospective)
-        - Status value equals "review"
+        - Status value equals "review" OR "ready-for-review"
       </action>
 
-      <check if="no story with status 'review' found">
-        <output>📋 No stories with status "review" found
+      <check if="no story with status 'review' or 'ready-for-review' found">
+        <output>📋 No stories with status "review" or "ready-for-review" found
 
 **What would you like to do?**
 1. Run `dev-story` to implement and mark a story ready for review