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

package/src/modules/bmgd/agents/game-scrum-master.agent.yaml

@@ -70,6 +70,6 @@ agent:
       workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
       description: Consult with other expert agents from the party
 
-    - trigger: adv-elicit
-      exec: "{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml"
+    - trigger: advanced-elicitation
+      exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
       description: Advanced elicitation techniques to challenge the LLM to get better results

package/src/modules/bmgd/workflows/2-design/gdd/instructions-gdd.md

@@ -221,7 +221,6 @@ Get core game concept and vision.
 <action>Guide user to define the primary game mechanics that players will interact with throughout the game</action>
 
 <template-output>primary_mechanics</template-output>
-<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
 
 <action>Guide user to describe their control scheme and input method (keyboard/mouse, gamepad, touchscreen, etc.), including key bindings or button layouts if known</action>
 
@@ -239,8 +238,6 @@ For each {{placeholder}} in the fragment, elicit and capture that information.
 
 <template-output file="GDD.md">GAME_TYPE_SPECIFIC_SECTIONS</template-output>
 
-<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
-
 </step>
 
 <step n="7" goal="Progression and balance">
@@ -304,7 +301,6 @@ For each {{placeholder}} in the fragment, elicit and capture that information.
 <action>Work with user to translate game features into development epics, following level-appropriate guidelines (Level 1: 1 epic/1-10 stories, Level 2: 1-2 epics/5-15 stories, Level 3: 2-5 epics/12-40 stories, Level 4: 5+ epics/40+ stories)</action>
 
 <template-output>epics</template-output>
-<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -324,8 +320,7 @@ For each {{placeholder}} in the fragment, elicit and capture that information.
 
 <for-each epic="epic_list">
 
-<template-output file="epics.md">epic\_{{epic_number}}\_details</template-output>
-<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
+<template-output file="epics.md">epic*{{epic_number}}*details</template-output>
 
 </for-each>
 

package/src/modules/bmgd/workflows/2-design/narrative/instructions-narrative.md

@@ -143,7 +143,6 @@ For 3-Act:
 Describe each act/section for your game:</ask>
 
 <template-output>act_breakdown</template-output>
-<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -162,7 +161,6 @@ Format:
 Your story beats:</ask>
 
 <template-output>story_beats</template-output>
-<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
 
 <ask>Describe the pacing and flow of your narrative.
 
@@ -195,7 +193,6 @@ For each protagonist include:
 Your protagonist(s):</ask>
 
 <template-output>protagonists</template-output>
-<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -233,7 +230,6 @@ For each character include:
 Your supporting characters:</ask>
 
 <template-output>supporting_characters</template-output>
-<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 
@@ -281,7 +277,6 @@ Your world:</ask>
 Your history:</ask>
 
 <template-output>history_backstory</template-output>
-<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
 
 </step>
 

package/src/modules/bmgd/workflows/3-technical/game-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/bmgd/workflows/3-technical/game-architecture/checklist.md

@@ -225,15 +225,11 @@
 
 ### Critical Issues Found
 
-- [ ] Issue 1: **\*\***\_\_\_**\*\***
-- [ ] Issue 2: **\*\***\_\_\_**\*\***
-- [ ] Issue 3: **\*\***\_\_\_**\*\***
+{ list issues }
 
 ### Recommended Actions Before Implementation
 
-1. ***
-2. ***
-3. ***
+{ list actions }
 
 ---
 

package/src/modules/bmgd/workflows/3-technical/game-architecture/instructions.md

@@ -72,7 +72,7 @@ For Level {{project_level}}, we'll keep the architecture appropriately scoped.
 
 Decision Architecture works from your Product Requirements Document (PRD).
 
-Looking for: _PRD_, PRD.md, or prd/index.md + files in {output_folder}
+Looking for: _prd_.md, or prd/index.md + files in {output_folder}
 
 Please run the PRD workflow first to define your requirements.
 
@@ -363,7 +363,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 +392,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 +465,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 +557,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 +610,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">

package/src/modules/bmgd/workflows/4-production/code-review/instructions.md

@@ -16,35 +16,6 @@
 
 <critical>DOCUMENT OUTPUT: Technical review reports. Structured findings with severity levels and action items. User skill level ({user_skill_level}) affects conversation style ONLY, not review content.</critical>
 
-## 📚 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.
-
 <workflow>
 
   <step n="1" goal="Find story ready for review" tag="sprint-status">
@@ -52,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">
@@ -64,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
@@ -80,17 +51,18 @@
         <check if="option 3 selected">
           <ask>What code would you like me to review?
 
-Provide:
-- File path(s) or directory to review
-- What to review for:
-  • General quality and standards
-  • Requirements compliance
-  • Security concerns
-  • Performance issues
-  • Architecture alignment
-  • Something else (specify)
+          Provide:
+          - File path(s) or directory to review
+          - What to review for:
+            • General quality and standards
+            • Requirements compliance
+            • Security concerns
+            • Performance issues
+            • Architecture alignment
+            • Something else (specify)
 
-Your input:</ask>
+            Your input:?
+          </ask>
 
           <action>Parse user input to extract:
             - {{review_files}}: file paths or directories to review
@@ -117,6 +89,11 @@ Your input:</ask>
     <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 @@ Your input:</ask>
     <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">

package/src/modules/bmgd/workflows/4-production/code-review/workflow.yaml

@@ -11,57 +11,47 @@ communication_language: "{config_source}:communication_language"
 user_skill_level: "{config_source}:user_skill_level"
 document_output_language: "{config_source}:document_output_language"
 date: system-generated
+sprint_artifacts: "{config_source}:sprint_artifacts"
+sprint_status: "{sprint_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
 
 # Workflow components
 installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/code-review"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
-
-# This is an action workflow (no output template document)
 template: false
 
-# Variables (can be provided by caller)
 variables:
-  story_path: "" # Optional: Explicit path to story file. If not provided, finds first story with status "review"
-  story_dir: "{config_source}:dev_ephemeral_location" # Directory containing story files
-  tech_spec_search_dir: "{project-root}/docs"
+  story_dir: "{sprint_artifacts}"
+  tech_spec_search_dir: "{output_folder}"
   tech_spec_glob_template: "tech-spec-epic-{{epic_num}}*.md"
   arch_docs_search_dirs: |
-    - "{project-root}/docs"
     - "{output_folder}"
   arch_docs_file_names: |
     - architecture.md
-
-  backlog_file: "{project-root}/docs/backlog.md"
+  backlog_file: "{output_folder}/backlog.md"
   update_epic_followups: true
   epic_followups_section_title: "Post-Review Follow-ups"
 
-# Recommended inputs
-recommended_inputs:
-  - story: "Path to the story file (auto-discovered if omitted - finds first story with status 'review')"
-  - tech_spec: "Epic technical specification document (auto-discovered)"
-  - story_context_file: "Story context file (.context.xml) (auto-discovered)"
-
 # Smart input file references - handles both whole docs and sharded docs
 # Priority: Whole document first, then sharded version
 # Strategy: SELECTIVE LOAD - only load the specific epic needed for this story review
 input_file_patterns:
   architecture:
     whole: "{output_folder}/*architecture*.md"
-    sharded: "{output_folder}/*architecture*/index.md"
-
+    sharded: "{output_folder}/*architecture*/*.md"
+    load_strategy: "FULL_LOAD"
   ux_design:
     whole: "{output_folder}/*ux*.md"
-    sharded: "{output_folder}/*ux*/index.md"
-
+    sharded: "{output_folder}/*ux*/*.md"
+    load_strategy: "FULL_LOAD"
   epics:
     whole: "{output_folder}/*epic*.md"
     sharded_index: "{output_folder}/*epic*/index.md"
     sharded_single: "{output_folder}/*epic*/epic-{{epic_num}}.md"
-
+    load_strategy: "SELECTIVE_LOAD"
   document_project:
     sharded: "{output_folder}/docs/index.md"
+    load_strategy: "INDEX_GUIDED"
 
 standalone: true
-
 web_bundle: false

package/src/modules/bmgd/workflows/4-production/correct-course/instructions.md

@@ -27,6 +27,11 @@
 <action if="core documents are unavailable">HALT: "Need access to project documents (PRD, Epics, Architecture, UI/UX) to assess change impact. Please ensure these documents are accessible."</action>
 </step>
 
+<step n="0.5" goal="Discover and load project 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>
+
 <step n="2" goal="Execute Change Analysis Checklist">
   <action>Load and execute the systematic analysis from: {checklist}</action>
   <action>Work through each checklist section interactively with the user</action>

package/src/modules/bmgd/workflows/4-production/correct-course/workflow.yaml

@@ -10,6 +10,35 @@ communication_language: "{config_source}:communication_language"
 user_skill_level: "{config_source}:user_skill_level"
 document_output_language: "{config_source}:document_output_language"
 date: system-generated
+sprint_artifacts: "{config_source}:sprint_artifacts"
+sprint_status: "{sprint_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
+
+# Smart input file references - handles both whole docs and sharded docs
+# Priority: Whole document first, then sharded version
+# Strategy: Load project context for impact analysis
+input_file_patterns:
+  prd:
+    whole: "{output_folder}/*prd*.md"
+    sharded: "{output_folder}/*prd*/*.md"
+    load_strategy: "FULL_LOAD"
+  epics:
+    whole: "{output_folder}/*epic*.md"
+    sharded: "{output_folder}/*epic*/*.md"
+    load_strategy: "FULL_LOAD"
+  architecture:
+    whole: "{output_folder}/*architecture*.md"
+    sharded: "{output_folder}/*architecture*/*.md"
+    load_strategy: "FULL_LOAD"
+  ux_design:
+    whole: "{output_folder}/*ux*.md"
+    sharded: "{output_folder}/*ux*/*.md"
+    load_strategy: "FULL_LOAD"
+  tech_spec:
+    whole: "{output_folder}/tech-spec*.md"
+    load_strategy: "FULL_LOAD"
+  document_project:
+    sharded: "{output_folder}/docs/index.md"
+    load_strategy: "INDEX_GUIDED"
 
 installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course"
 template: false
@@ -18,28 +47,6 @@ validation: "{installed_path}/checklist.md"
 checklist: "{installed_path}/checklist.md"
 default_output_file: "{output_folder}/sprint-change-proposal-{date}.md"
 
-# Workflow execution mode (interactive: step-by-step with user, non-interactive: automated)
-mode: interactive
-
-required_inputs:
-  - change_trigger: "Description of the issue or change that triggered this workflow"
-  - project_documents: "Access to PRD, Epics/Stories, Architecture, UI/UX specs"
-
-output_artifacts:
-  - sprint_change_proposal: "Comprehensive proposal documenting issue, impact, and recommended changes"
-  - artifact_edits: "Specific before/after edits for affected documents"
-  - handoff_plan: "Clear routing for implementation based on change scope"
-
-halt_conditions:
-  - "Change trigger unclear or undefined"
-  - "Core project documents unavailable"
-  - "Impact analysis incomplete"
-  - "User approval not obtained"
-
-execution_modes:
-  - incremental: "Recommended - Refine each edit with user collaboration"
-  - batch: "Present all changes at once for review"
-
 standalone: true
 
 web_bundle: false

package/src/modules/bmgd/workflows/4-production/create-story/instructions.md

@@ -7,45 +7,21 @@
 <critical>This workflow creates or updates the next user story from epics/PRD and architecture context, saving to the configured stories directory and optionally invoking Story Context.</critical>
 <critical>DOCUMENT OUTPUT: Concise, technical, actionable story specifications. Use tables/lists for acceptance criteria and tasks.</critical>
 
-## 📚 Document Discovery - Selective Epic Loading
-
-**Strategy**: This workflow needs only ONE specific epic and its stories, 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 context - 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 (prd, 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 UI-focused stories.
-
 <workflow>
 
   <step n="1" goal="Load config and initialize">
-    <action>Resolve variables from config_source: story_dir (dev_ephemeral_location), output_folder, user_name, communication_language. If story_dir missing and {{non_interactive}} == false → ASK user to provide a stories directory and update variable. If {{non_interactive}} == true and missing, HALT with a clear message.</action>
+    <action>Resolve variables from config_source: story_dir (sprint_artifacts), output_folder, user_name, communication_language. If story_dir missing → ASK user to provide a stories directory and update variable.</action>
     <action>Create {{story_dir}} if it does not exist</action>
     <action>Resolve installed component paths from workflow.yaml: template, instructions, validation</action>
-    <action>Resolve recommended inputs if present: epics_file, prd_file, architecture_file</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>
   </step>
 
-  <step n="2" goal="Discover and load source documents">
+  <step n="1.5" goal="Discover and load project documents">
+    <invoke-protocol name="discover_inputs" />
+    <note>After discovery, these content variables are available: {prd_content}, {tech_spec_content}, {architecture_content}, {ux_design_content}, {epics_content}, {document_project_content}</note>
+  </step>
+
+  <step n="2" goal="Discover previous story context">
     <critical>PREVIOUS STORY CONTINUITY: Essential for maintaining context and learning from prior development</critical>
 
     <action>Find the previous completed story to extract dev agent learnings and review findings:
@@ -115,19 +91,17 @@
     </action>
 
     <action>If {{tech_spec_file}} empty: derive from {{tech_spec_glob_template}} with {{epic_num}} and search {{tech_spec_search_dir}} recursively. If multiple, pick most recent by modified time.</action>
-    <action>Build a prioritized document set for this epic:
+    <action>Build a prioritized document set for this epic - search and load from {input_file_patterns} list of potential locations:
       1) tech_spec_file (epic-scoped)
-      2) epics_file (acceptance criteria and breakdown)
-      3) prd_file (business requirements and constraints)
-      4) architecture_file (architecture constraints)
-      5) Architecture docs under docs/ and output_folder/: tech-stack.md, unified-project-structure.md, coding-standards.md, testing-strategy.md, backend-architecture.md, frontend-architecture.md, data-models.md, database-schema.md, rest-api-spec.md, external-apis.md (include if present)
+      2) epics_file (acceptance criteria and breakdown) the specific epic the story will be part of
+      3) prd_file (business requirements and constraints) whole or sharded
+      4) architecture_file (architecture constraints) whole or sharded
     </action>
     <action>READ COMPLETE FILES for all items found in the prioritized set. Store content and paths for citation.</action>
   </step>
 
   <step n="3" goal="Find next backlog story to draft" tag="sprint-status">
-    <critical>MUST read COMPLETE sprint-status.yaml file from start to end to preserve order</critical>
-    <action>Load the FULL file: {{output_folder}}/sprint-status.yaml</action>
+    <critical>MUST read COMPLETE {sprint_status} file from start to end to preserve order</critical>
     <action>Read ALL lines from beginning to end - do not skip any content</action>
     <action>Parse the development_status section completely to understand story order</action>
 
@@ -140,12 +114,12 @@
     <check if="no backlog story found">
       <output>📋 No backlog stories found in sprint-status.yaml
 
-All stories are either already drafted or completed.
+        All stories are either already drafted or completed.
 
-**Options:**
-1. Run sprint-planning to refresh story tracking
-2. Load PM agent and run correct-course to add more stories
-3. Check if current sprint is complete
+        **Options:**
+        1. Run sprint-planning to refresh story tracking
+        2. Load PM agent and run correct-course to add more stories
+        3. Check if current sprint is complete
       </output>
       <action>HALT</action>
     </check>
@@ -164,7 +138,6 @@ All stories are either already drafted or completed.
     <action>Check if story file already exists at expected path in {{story_dir}}</action>
     <check if="story file exists">
       <output>ℹ️ Story file already exists: {{story_file_path}}
-
 Will update existing story file rather than creating new one.
       </output>
       <action>Set update_mode = true</action>

package/src/modules/bmgd/workflows/4-production/create-story/workflow.yaml

@@ -8,6 +8,8 @@ output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 date: system-generated
+sprint_artifacts: "{config_source}:sprint_artifacts"
+story_dir: "{sprint_artifacts}"
 
 # Workflow components
 installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/create-story"
@@ -17,7 +19,7 @@ validation: "{installed_path}/checklist.md"
 
 # Variables and inputs
 variables:
-  story_dir: "{config_source}:dev_ephemeral_location" # Directory where stories are stored
+  sprint_status: "{sprint_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml" # Primary source for story tracking
   epics_file: "{output_folder}/epics.md" # Preferred source for epic/story breakdown
   prd_file: "{output_folder}/PRD.md" # Fallback for requirements
   architecture_file: "{output_folder}/architecture.md" # Optional architecture context
@@ -28,48 +30,38 @@ variables:
     - "{project-root}/docs"
     - "{output_folder}"
   arch_docs_file_names: |
-    - architecture.md
-    - infrastructure-architecture.md
+    - *architecture*.md
   story_title: "" # Will be elicited if not derivable
-  epic_num: 1
-  story_num: 1
-  non_interactive: true # Generate without elicitation; avoid interactive prompts
 
-# Output configuration
-# Uses story_key from sprint-status.yaml (e.g., "1-2-user-authentication")
 default_output_file: "{story_dir}/{{story_key}}.md"
 
-recommended_inputs:
-  - epics: "Epic breakdown (epics.md)"
-  - prd: "PRD document"
-  - architecture: "Architecture (optional)"
-
 # Smart input file references - handles both whole docs and sharded docs
 # Priority: Whole document first, then sharded version
 # Strategy: SELECTIVE LOAD - only load the specific epic needed for this story
 input_file_patterns:
   prd:
     whole: "{output_folder}/*prd*.md"
-    sharded: "{output_folder}/*prd*/index.md"
-
+    sharded: "{output_folder}/*prd*/*.md"
+    load_strategy: "FULL_LOAD"
   tech_spec:
     whole: "{output_folder}/tech-spec.md"
-
+    load_strategy: "FULL_LOAD"
   architecture:
     whole: "{output_folder}/*architecture*.md"
-    sharded: "{output_folder}/*architecture*/index.md"
-
+    sharded: "{output_folder}/*architecture*/*.md"
+    load_strategy: "FULL_LOAD"
   ux_design:
     whole: "{output_folder}/*ux*.md"
-    sharded: "{output_folder}/*ux*/index.md"
-
+    sharded: "{output_folder}/*ux*/*.md"
+    load_strategy: "FULL_LOAD"
   epics:
     whole: "{output_folder}/*epic*.md"
     sharded_index: "{output_folder}/*epic*/index.md"
     sharded_single: "{output_folder}/*epic*/epic-{{epic_num}}.md"
-
+    load_strategy: "SELECTIVE_LOAD"
   document_project:
-    sharded: "{output_folder}/docs/index.md"
+    sharded: "{output_folder}/index.md"
+    load_strategy: "INDEX_GUIDED"
 
 standalone: true
 

package/src/modules/bmgd/workflows/4-production/dev-story/instructions.md

@@ -39,7 +39,7 @@
 1. Run `story-context` to generate context file and mark drafted stories as ready
 2. Run `story-ready` to quickly mark drafted stories as ready without generating context
 3. Run `create-story` if no incomplete stories are drafted yet
-4. Check {output-folder}/sprint-status.yaml to see current sprint status
+4. Check {output_folder}/sprint-status.yaml to see current sprint status
       </output>
       <action>HALT</action>
     </check>
@@ -72,6 +72,11 @@ Proceeding with story file only. For better context, consider running `story-con
     <action if="incomplete task or subtask requirements ambiguous">ASK user to clarify or HALT</action>
   </step>
 
+  <step n="0.5" goal="Discover and load project documents">
+    <invoke-protocol name="discover_inputs" />
+    <note>After discovery, these content variables are available: {architecture_content}, {tech_spec_content}, {ux_design_content}, {epics_content} (selective load), {document_project_content}</note>
+  </step>
+
   <step n="1.5" goal="Detect review continuation and extract review context">
     <critical>Determine if this is a fresh start or continuation after code review</critical>