bmad-method 6.0.0-alpha.8 → 6.0.0-alpha.9

package/src/modules/bmm/workflows/3-solutioning/architecture/architecture-patterns.yaml

@@ -319,29 +319,3 @@ decision_rules:
       - quick_prototype: "Railway"
       - global_edge: "Fly.io"
       - kubernetes_needed: "GCP or AWS EKS"
-
-# Anti-patterns to avoid
-anti_patterns:
-  overengineering:
-    signs:
-      - "Microservices for < 10k users"
-      - "Kubernetes for single app"
-      - "GraphQL for 5 endpoints"
-      - "Event sourcing for CRUD app"
-    recommendation: "Start simple, evolve as needed"
-
-  underengineering:
-    signs:
-      - "No authentication strategy"
-      - "No error handling plan"
-      - "No monitoring approach"
-      - "No backup strategy"
-    recommendation: "Cover the fundamentals"
-
-  technology_soup:
-    signs:
-      - "5+ different databases"
-      - "Multiple frontend frameworks"
-      - "Inconsistent patterns"
-      - "Too many languages"
-    recommendation: "Maintain consistency"

package/src/modules/bmm/workflows/3-solutioning/architecture/checklist.md

@@ -225,19 +225,15 @@
 
 ### Critical Issues Found
 
-- [ ] Issue 1: **\*\***\_\_\_**\*\***
-- [ ] Issue 2: **\*\***\_\_\_**\*\***
-- [ ] Issue 3: **\*\***\_\_\_**\*\***
+<!-- replace with list of critical issues found, or N/A -->
 
 ### Recommended Actions Before Implementation
 
-1. ***
-2. ***
-3. ***
+<!-- replace with list of recommended actions, or N/A -->
 
 ---
 
-**Next Step**: Run the **solutioning-gate-check** workflow to validate alignment between PRD, Architecture, and Stories before beginning implementation.
+**Next Step**: Run the **solutioning-gate-check** workflow to validate alignment between PRD, UX, Architecture, and Stories before beginning implementation.
 
 ---
 

package/src/modules/bmm/workflows/3-solutioning/architecture/instructions.md

@@ -16,7 +16,7 @@
 <action>Check if {output_folder}/bmm-workflow-status.yaml exists</action>
 
 <check if="status file not found">
-  <output>No workflow status file found. Decision Architecture can run standalone or as part of BMM workflow path.</output>
+  <output>No workflow status file found. Create Architecture can run standalone or as part of BMM workflow path.</output>
   <output>**Recommended:** Run `workflow-init` first for project context tracking and workflow sequencing.</output>
   <ask>Continue in standalone mode or exit to run workflow-init? (continue/exit)</ask>
   <check if="continue">
@@ -33,17 +33,9 @@
   <action>Check status of "create-architecture" workflow</action>
   <action>Get project_level from YAML metadata</action>
   <action>Find first non-completed workflow (next expected workflow)</action>
-
-  <check if="project_level < 3">
-    <output>**Note: Level {{project_level}} Project**
-
-The Detailed Architecture is typically for Level 3-4 projects, but can be used for any project that needs architectural planning.
-
-For Level {{project_level}}, we'll keep the architecture appropriately scoped.
-</output>
 </check>
 
-  <check if="create-architecture status is file path (already completed)">
+  <check if="create-architecture status is indicates already completed">
     <output>⚠️ Architecture already completed: {{create-architecture status}}</output>
     <ask>Re-running will overwrite the existing architecture. Continue? (y/n)</ask>
     <check if="n">
@@ -62,7 +54,6 @@ For Level {{project_level}}, we'll keep the architecture appropriately scoped.
   </check>
 
 <action>Set standalone_mode = false</action>
-</check>
 
 <action>Check for existing PRD and epics files using fuzzy matching</action>
 
@@ -70,32 +61,37 @@ For Level {{project_level}}, we'll keep the architecture appropriately scoped.
 <check if="PRD_not_found">
 <output>**PRD Not Found**
 
-Decision Architecture works from your Product Requirements Document (PRD).
+Creation of an Architecture works from your Product Requirements Document (PRD), along with an optional UX Design and other assets.
 
-Looking for: _PRD_, PRD.md, or prd/index.md + files in {output_folder}
+Looking for: _prd_.md, or prd/\* + files in {output_folder}
 
-Please run the PRD workflow first to define your requirements.
-
-Architect: `create-prd`
+Please talk to the PM Agent to run the Create PRD workflow first to define your requirements, or if I am mistaken and it does exist, provide the file now.
 </output>
-<action>Exit workflow - PRD required</action>
+<ask>Would you like to exit, or can you provide a PRD?
+<action if='yes to exit'>Exit workflow - PRD required</action>
+<action if='prd provided'>Proceed to Step 1</action>
+</ask>
 </check>
 
 </step>
 
+<step n="0.5" goal="Discover and load input documents">
+<invoke-protocol name="discover_inputs" />
+<note>After discovery, these content variables are available: {prd_content}, {epics_content}, {ux_design_content}, {document_project_content}</note>
+</step>
+
 <step n="1" goal="Load and understand project context">
-  <action>Load the PRD using fuzzy matching: {prd_file}, if the PRD is mulitple files in a folder, load the index file and all files associated with the PRD</action>
-  <action>Load epics file using fuzzy matching: {epics_file}</action>
+  <action>Review loaded PRD: {prd_content} (auto-loaded in Step 0.5 - handles both whole and sharded documents)</action>
+  <action>Review loaded epics: {epics_content}</action>
 
-<action>Check for UX specification using fuzzy matching:
-<action>Attempt to locate: {ux_spec_file}</action>
-<check if="ux_spec_found">
-<action>Load UX spec and extract architectural implications: - Component complexity (simple forms vs rich interactions) - Animation/transition requirements - Real-time update needs (live data, collaborative features) - Platform-specific UI requirements - Accessibility standards (WCAG compliance level) - Responsive design breakpoints - Offline capability requirements - Performance expectations (load times, interaction responsiveness)
+<action>Check for UX specification:
+<check if="{ux_design_content} is not empty">
+<action>Extract architectural implications from {ux_design_content}: - Component complexity (simple forms vs rich interactions) - Animation/transition requirements - Real-time update needs (live data, collaborative features) - Platform-specific UI requirements - Accessibility standards (WCAG compliance level) - Responsive design breakpoints - Offline capability requirements - Performance expectations (load times, interaction responsiveness)
 </action>
 </check>
 </action>
 
-<action>Extract and understand from PRD: - Functional Requirements (what it must do) - Non-Functional Requirements (performance, security, compliance, etc.) - Epic structure and user stories - Acceptance criteria - Any technical constraints mentioned
+<action>Extract and understand from {prd_content}: - Functional Requirements (what it must do) - Non-Functional Requirements (performance, security, compliance, etc.) - Epic structure and user stories - Acceptance criteria - Any technical constraints mentioned
 </action>
 
 <action>Count and assess project scale: - Number of epics: {{epic_count}} - Number of stories: {{story_count}} - Complexity indicators (real-time, multi-tenant, regulated, etc.) - UX complexity level (if UX spec exists) - Novel features
@@ -363,7 +359,6 @@ Provided by Starter: {{yes_if_from_starter}}
 </action>
 
 <template-output>decision_record</template-output>
-<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
 <step n="5" goal="Address cross-cutting concerns">
@@ -393,7 +388,6 @@ Provided by Starter: {{yes_if_from_starter}}
 </action>
 
 <template-output>project_structure</template-output>
-<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
 <step n="7" goal="Design novel architectural patterns" optional="true">
@@ -467,7 +461,6 @@ Provided by Starter: {{yes_if_from_starter}}
   </check>
 
 <template-output>novel_pattern_designs</template-output>
-<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
 <step n="8" goal="Define implementation patterns to prevent agent conflicts">
@@ -560,7 +553,6 @@ Enforcement: "All agents MUST follow this pattern"
 </action>
 
 <template-output>implementation_patterns</template-output>
-<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
 <step n="9" goal="Validate architectural coherence">
@@ -614,7 +606,6 @@ Enforcement: "All agents MUST follow this pattern"
   </action>
 
 <template-output>architecture_document</template-output>
-<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
 <step n="11" goal="Validate document completeness">
@@ -623,14 +614,15 @@ Enforcement: "All agents MUST follow this pattern"
 <action>Run validation checklist from {installed_path}/checklist.md</action>
 
 <action>Verify MANDATORY items:
-□ Decision table has Version column with specific versions
-□ Every epic is mapped to architecture components
-□ Source tree is complete, not generic
-□ No placeholder text remains
-□ All FRs from PRD have architectural support
-□ All NFRs from PRD are addressed
-□ Implementation patterns cover all potential conflicts
-□ Novel patterns are fully documented (if applicable)
+
+- [] Decision table has Version column with specific versions
+- [] Every epic is mapped to architecture components
+- [] Source tree is complete, not generic
+- [] No placeholder text remains
+- [] All FRs from PRD have architectural support
+- [] All NFRs from PRD are addressed
+- [] Implementation patterns cover all potential conflicts
+- [] Novel patterns are fully documented (if applicable)
 </action>
 
   <check if="validation_failed">

package/src/modules/bmm/workflows/3-solutioning/architecture/workflow.yaml

@@ -12,29 +12,25 @@ document_output_language: "{config_source}:document_output_language"
 user_skill_level: "{config_source}:user_skill_level"
 date: system-generated
 
-# Input requirements - We work from PRD, Epics, and optionally UX Spec
-recommended_inputs:
-  - prd: "Product Requirements Document with FRs and NFRs"
-  - epics: "Epic definitions with user stories and acceptance criteria"
-  - ux_spec: "UX specification with interface designs and interaction patterns (optional)"
-
 # Smart input file references - handles both whole docs and sharded docs
 # Priority: Whole document first, then sharded version
+# Strategy: How to load sharded documents (FULL_LOAD, SELECTIVE_LOAD, INDEX_GUIDED)
 input_file_patterns:
   prd:
     whole: "{output_folder}/*prd*.md"
     sharded: "{output_folder}/*prd*/index.md"
-
+    load_strategy: "FULL_LOAD"
   epics:
     whole: "{output_folder}/*epic*.md"
     sharded: "{output_folder}/*epic*/index.md"
-
+    load_strategy: "FULL_LOAD"
   ux_design:
     whole: "{output_folder}/*ux*.md"
     sharded: "{output_folder}/*ux*/index.md"
-
+    load_strategy: "FULL_LOAD"
   document_project:
-    sharded: "{output_folder}/docs/index.md"
+    sharded: "{output_folder}/index.md"
+    load_strategy: "INDEX_GUIDED"
 
 # Module path and component files
 installed_path: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/architecture"
@@ -50,20 +46,6 @@ pattern_categories: "{installed_path}/pattern-categories.csv"
 # Output configuration
 default_output_file: "{output_folder}/architecture.md"
 
-# Workflow metadata
-version: "1.3.2"
-replaces: "architecture"
-paradigm: "facilitation-driven"
-execution_time: "30-90 minutes depending on user skill level"
-features:
-  - "Starter template discovery and integration"
-  - "Dynamic version verification via web search"
-  - "Adaptive facilitation by skill level"
-  - "Decision-focused architecture"
-  - "Novel pattern design for unique concepts"
-  - "Intelligent pattern identification - LLM figures out what patterns matter"
-  - "Implementation patterns for agent consistency"
-
 standalone: true
 
 # Web bundle configuration for standalone deployment
@@ -83,7 +65,7 @@ web_bundle:
   pattern_categories: "{bmad_folder}/bmm/workflows/3-solutioning/architecture/pattern-categories.csv"
 
   # Task dependencies
-  adv_elicit_task: "{bmad_folder}/core/tasks/adv-elicit.xml"
+  adv_elicit_task: "{bmad_folder}/core/tasks/advanced-elicitation.xml"
 
   # Default configuration values (can be overridden during bundle setup)
   defaults:
@@ -110,5 +92,5 @@ web_bundle:
 
     # Task dependencies (referenced in instructions.md)
     - "{bmad_folder}/core/tasks/workflow.xml"
-    - "{bmad_folder}/core/tasks/adv-elicit.xml"
-    - "{bmad_folder}/core/tasks/adv-elicit-methods.csv"
+    - "{bmad_folder}/core/tasks/advanced-elicitation.xml"
+    - "{bmad_folder}/core/tasks/advanced-elicitation-methods.csv"

package/src/modules/bmm/workflows/3-solutioning/solutioning-gate-check/checklist.md

@@ -4,10 +4,10 @@
 
 ### Core Planning Documents
 
-- [ ] PRD exists and is complete (Level 2-4 projects)
+- [ ] PRD exists and is complete
 - [ ] PRD contains measurable success criteria
 - [ ] PRD defines clear scope boundaries and exclusions
-- [ ] Architecture document exists (architecture\*.md) (Level 3-4 projects)
+- [ ] Architecture document exists (architecture\*.md)
 - [ ] Technical Specification exists with implementation details
 - [ ] Epic and story breakdown document exists
 - [ ] All documents are dated and versioned
@@ -22,7 +22,7 @@
 
 ## Alignment Verification
 
-### PRD to Architecture Alignment (Level 3-4)
+### PRD to Architecture Alignment
 
 - [ ] Every functional requirement in PRD has architectural support documented
 - [ ] All non-functional requirements from PRD are addressed in architecture
@@ -33,7 +33,7 @@
 - [ ] If architecture.md: All technology choices have verified versions
 - [ ] If UX spec exists: Architecture supports UX requirements
 
-### PRD to Stories Coverage (Level 2-4)
+### PRD to Stories Coverage
 
 - [ ] Every PRD requirement maps to at least one story
 - [ ] All user journeys in PRD have complete story coverage
@@ -154,21 +154,15 @@
 
 ### Critical Issues Found
 
-- [ ] ***
-- [ ] ***
-- [ ] ***
+<!-- checklist of critical issues or N/A -->
 
 ### High Priority Issues Found
 
-- [ ] ***
-- [ ] ***
-- [ ] ***
+<!-- checklist of high priority issues or N/A -->
 
 ### Medium Priority Issues Found
 
-- [ ] ***
-- [ ] ***
-- [ ] ***
+<!-- checklist of medium priority issues or N/A -->
 
 ---
 

package/src/modules/bmm/workflows/3-solutioning/solutioning-gate-check/instructions.md

@@ -8,7 +8,7 @@
 <workflow>
 
 <step n="0" goal="Validate workflow readiness" tag="workflow-status">
-<action>Check if {output_folder}/bmm-workflow-status.yaml exists</action>
+<action>Check if {workflow_status_file} exists</action>
 
 <check if="status file not found">
   <output>No workflow status file found. Implementation Ready Check can run standalone or as part of BMM workflow path.</output>
@@ -23,14 +23,13 @@
 </check>
 
 <check if="status file found">
-  <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
+  <action>Load the FULL file:  {workflow_status_file}</action>
   <action>Parse workflow_status section</action>
   <action>Check status of "solutioning-gate-check" workflow</action>
-  <action>Get project_level from YAML metadata</action>
+  <action>Get {selected_track} (quick-flow, bmad-method, or enterprise-bmad-method)</action>
   <action>Find first non-completed workflow (next expected workflow)</action>
 
-<action>Based on the project_level, understand what artifacts should exist: - Level 0-1: Tech spec and simple stories only (no PRD, minimal solutioning) - Level 2: PRD, tech spec, epics/stories (no separate architecture doc) - Level 3-4: Full suite - PRD, architecture document, epics/stories, possible UX artifacts
-</action>
+<action>Based on the selected_track, understand what artifacts should exist: - quick-flow: Tech spec and simple stories in an epic only (no PRD, minimal solutioning) - bmad-method and enterprise-bmad-method: PRD, tech spec, epics/stories, architecture, possible UX artifacts</action>
 
   <check if="solutioning-gate-check status is file path (already completed)">
     <output>⚠️ Gate check already completed: {{solutioning-gate-check status}}</output>
@@ -53,53 +52,48 @@
 <action>Set standalone_mode = false</action>
 </check>
 
-<critical>The validation approach must adapt to the project level - don't look for documents that shouldn't exist at lower levels</critical>
-
 <template-output>project_context</template-output>
 </step>
 
-<step n="1" goal="Discover and inventory project artifacts">
-<action>Search the {output_folder} for relevant planning and solutioning documents based on project level identified in Step 0</action>
-
-<action>For Level 0-1 projects, locate:
+<step n="0.5" goal="Discover and load input documents">
+<invoke-protocol name="discover_inputs" />
+<note>After discovery, these content variables are available: {prd_content}, {epics_content}, {architecture_content}, {ux_design_content}, {tech_spec_content}, {document_project_content}</note>
+</step>
 
-- Technical specification document(s)
-- Story/task lists or simple epic breakdowns
-- Any API or interface definitions
-  </action>
+<step n="1" goal="Inventory loaded project artifacts">
+<action>Review the content loaded by Step 0.5 and create an inventory</action>
 
-<action>For Level 2-4 projects, locate:
+<action>Inventory of available documents:
 
-- Product Requirements Document (PRD)
-- Architecture document (architecture.md) (Level 3-4 only)
-- Technical Specification (Level 2 includes architecture within)
-- Epic and story breakdowns
-- UX artifacts if the active path includes UX workflow
-- Any supplementary planning documents
+- PRD: {prd_content} (loaded if available)
+- Architecture: {architecture_content} (loaded if available)
+- Epics: {epics_content} (loaded if available)
+- UX Design: {ux_design_content} (loaded if available)
+- Tech Spec: {tech_spec_content} (loaded if available, Quick Flow track)
+- Brownfield docs: {document_project_content} (loaded via INDEX_GUIDED if available)
   </action>
 
-<action>Create an inventory of found documents with:
+<action>For each loaded document, extract:
 
 - Document type and purpose
-- File path and last modified date
-- Brief description of what each contains
-- Any missing expected documents flagged as potential issues
+- Brief description of what it contains
+- Flag any expected documents that are missing as potential issues
   </action>
 
 <template-output>document_inventory</template-output>
 </step>
 
 <step n="2" goal="Deep analysis of core planning documents">
-<action>Load and thoroughly analyze each discovered document to extract:
-- Core requirements and success criteria
-- Architectural decisions and constraints
-- Technical implementation approaches
-- User stories and acceptance criteria
-- Dependencies and sequencing requirements
-- Any assumptions or risks documented
+<action>Thoroughly analyze each loaded document to extract:
+  - Core requirements and success criteria
+  - Architectural decisions and constraints
+  - Technical implementation approaches
+  - User stories and acceptance criteria
+  - Dependencies and sequencing requirements
+  - Any assumptions or risks documented
 </action>
 
-<action>For PRD analysis (Level 2-4), focus on:
+<action>For PRD analysis, focus on:
 
 - User requirements and use cases
 - Functional and non-functional requirements
@@ -131,9 +125,8 @@
 </step>
 
 <step n="3" goal="Cross-reference validation and alignment check">
-<action>Systematically validate alignment between all artifacts, adapting validation based on project level</action>
 
-<action>PRD ↔ Architecture Alignment (Level 3-4):
+<action>PRD ↔ Architecture Alignment:
 
 - Verify every PRD requirement has corresponding architectural support
 - Check that architectural decisions don't contradict PRD constraints
@@ -142,7 +135,7 @@
 - If using new architecture workflow: verify implementation patterns are defined
   </action>
 
-<action>PRD ↔ Stories Coverage (Level 2-4):
+<action>PRD ↔ Stories Coverage:
 
 - Map each PRD requirement to implementing stories
 - Identify any PRD requirements without story coverage
@@ -158,13 +151,6 @@
 - Ensure infrastructure and setup stories exist for architectural components
   </action>
 
-<action>For Level 0-1 projects (Tech Spec only):
-
-- Validate internal consistency within tech spec
-- Check that all specified features have corresponding stories
-- Verify story sequencing matches technical dependencies
-  </action>
-
 <template-output>alignment_validation</template-output>
 </step>
 
@@ -204,24 +190,35 @@
 - Over-engineering indicators
   </action>
 
+<action>Check Testability Review (if test-design exists in Phase 3):
+
+**Note:** test-design is recommended for BMad Method, required for Enterprise Method
+
+- Check if {output_folder}/test-design-system.md exists
+- If exists: Review testability assessment (Controllability, Observability, Reliability)
+- If testability concerns documented: Flag for gate decision
+- If missing AND track is Enterprise: Flag as CRITICAL gap
+- If missing AND track is Method: Note as recommendation (not blocker)
+  </action>
+
 <template-output>gap_risk_analysis</template-output>
 </step>
 
 <step n="5" goal="UX and special concerns validation" optional="true">
-<check if="UX artifacts exist or UX workflow in active path">
-<action>Review UX artifacts and validate integration:
-- Check that UX requirements are reflected in PRD
-- Verify stories include UX implementation tasks
-- Ensure architecture supports UX requirements (performance, responsiveness)
-- Identify any UX concerns not addressed in stories
-</action>
-
-<action>Validate accessibility and usability coverage:
+  <check if="UX artifacts exist or UX workflow in active path">
+    <action>Review UX artifacts and validate integration:
+      - Check that UX requirements are reflected in PRD
+      - Verify stories include UX implementation tasks
+      - Ensure architecture supports UX requirements (performance, responsiveness)
+      - Identify any UX concerns not addressed in stories
+    </action>
+
+    <action>Validate accessibility and usability coverage:
+      - Check for accessibility requirement coverage in stories
+      - Verify responsive design considerations if applicable
+      - Ensure user flow completeness across stories
+    </action>
 
-- Check for accessibility requirement coverage in stories
-- Verify responsive design considerations if applicable
-- Ensure user flow completeness across stories
-  </action>
   </check>
 
 <template-output>ux_validation</template-output>
@@ -258,7 +255,7 @@
 
 <step n="7" goal="Update status and complete" tag="workflow-status">
 <check if="standalone_mode != true">
-  <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
+  <action>Load the FULL file: {workflow_status_file}</action>
   <action>Find workflow_status key "solutioning-gate-check"</action>
   <critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
   <action>Update workflow_status["solutioning-gate-check"] = "{output_folder}/bmm-readiness-assessment-{{date}}.md"</action>

package/src/modules/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml

@@ -14,6 +14,7 @@ date: system-generated
 # Workflow status integration
 workflow_status_workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml"
 workflow_paths_dir: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/paths"
+workflow_status_file: "{output_folder}/bmm-workflow-status.yaml"
 
 # Module path and component files
 installed_path: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/solutioning-gate-check"
@@ -34,32 +35,31 @@ recommended_inputs:
 
 # Smart input file references - handles both whole docs and sharded docs
 # Priority: Whole document first, then sharded version
+# Strategy: How to load sharded documents (FULL_LOAD, SELECTIVE_LOAD, INDEX_GUIDED)
 input_file_patterns:
   prd:
     whole: "{output_folder}/*prd*.md"
     sharded: "{output_folder}/*prd*/index.md"
-
+    load_strategy: "FULL_LOAD"
   epics:
     whole: "{output_folder}/*epic*.md"
     sharded: "{output_folder}/*epic*/index.md"
-
+    load_strategy: "FULL_LOAD"
   architecture:
     whole: "{output_folder}/*architecture*.md"
     sharded: "{output_folder}/*architecture*/index.md"
-
+    load_strategy: "FULL_LOAD"
   ux_design:
     whole: "{output_folder}/*ux*.md"
     sharded: "{output_folder}/*ux*/index.md"
-
+    load_strategy: "FULL_LOAD"
   tech_spec:
     whole: "{output_folder}/*tech-spec*.md"
     sharded: "{output_folder}/*tech-spec*/index.md"
-
+    load_strategy: "FULL_LOAD"
   document_project:
     sharded: "{output_folder}/docs/index.md"
-
-# Validation criteria data
-validation_criteria: "{installed_path}/validation-criteria.yaml"
+    load_strategy: "INDEX_GUIDED"
 
 standalone: true
 

package/src/modules/bmm/workflows/4-implementation/code-review/instructions.md

@@ -19,39 +19,11 @@
 <workflow>
 
   <step n="1" goal="Find story ready for review" tag="sprint-status">
-    Document Discovery - Selective Epic Loading
-
-    **Strategy**: This workflow needs only ONE specific epic and its stories for review context, not all epics. This provides huge efficiency gains when epics are sharded.
-
-    **Epic Discovery Process (SELECTIVE OPTIMIZATION):**
-
-    1. **Determine which epic** you need (epic_num from story being reviewed - e.g., story "3-2-feature-name" needs Epic 3)
-    2. **Check for sharded version**: Look for `epics/index.md`
-    3. **If sharded version found**:
-      - Read `index.md` to understand structure
-      - **Load ONLY `epic-{epic_num}.md`** (e.g., `epics/epic-3.md` for Epic 3)
-      - DO NOT load all epic files - only the one needed!
-      - This is the key efficiency optimization for large multi-epic projects
-    4. **If whole document found**: Load the complete `epics.md` file and extract the relevant epic
-
-    **Other Documents (architecture, ux-design) - Full Load:**
-
-    1. **Search for whole document first** - Use fuzzy file matching
-    2. **Check for sharded version** - If whole document not found, look for `{doc-name}/index.md`
-    3. **If sharded version found**:
-      - Read `index.md` to understand structure
-      - Read ALL section files listed in the index
-      - Treat combined content as single document
-    4. **Brownfield projects**: The `document-project` workflow creates `{output_folder}/docs/index.md`
-
-    **Priority**: If both whole and sharded versions exist, use the whole document.
-
-    **UX-Heavy Projects**: Always check for ux-design documentation as it provides critical context for reviewing UI-focused stories.
     <check if="{{story_path}} is provided">
       <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">
@@ -63,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
@@ -117,6 +89,11 @@
     <action if="story cannot be read">HALT with message: "Unable to read story file"</action>
   </step>
 
+  <step n="1.5" goal="Discover and load project documents">
+    <invoke-protocol name="discover_inputs" />
+    <note>After discovery, these content variables are available: {architecture_content}, {ux_design_content}, {epics_content} (loads only epic for this story if sharded), {document_project_content}</note>
+  </step>
+
   <step n="2" goal="Resolve story context file and specification inputs">
     <action>Locate story context file: Under Dev Agent Record → Context Reference, read referenced path(s). If missing, search {{output_folder}} for files matching pattern "story-{{epic_num}}.{{story_num}}*.context.xml" and use the most recent.</action>
     <action if="no story context file found">Continue but record a WARNING in review notes: "No story context file found"</action>
@@ -125,6 +102,7 @@
     <action if="no tech spec found">Continue but record a WARNING in review notes: "No Tech Spec found for epic {{epic_num}}"</action>
 
     <action>Load architecture/standards docs: For each file name in {{arch_docs_file_names}} within {{arch_docs_search_dirs}}, read if exists. Collect testing, coding standards, security, and architectural patterns.</action>
+    <note>Architecture and brownfield docs were pre-loaded in Step 1.5 as {architecture_content} and {document_project_content}</note>
   </step>
 
   <step n="3" goal="Detect tech stack and establish best-practice reference set">