bmad-method 6.0.0-alpha.2 → 6.0.0-alpha.4

package/src/modules/bmm/workflows/1-analysis/research/instructions-technical.md

@@ -2,38 +2,65 @@
 
 <critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
-<critical>This workflow conducts technical research for architecture and technology decisions</critical>
+<critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication style based on {user_skill_level}</critical>
+<critical>This is a HIGHLY INTERACTIVE workflow - make technical decisions WITH user, not FOR them</critical>
+<critical>Web research is MANDATORY - use WebSearch tool with {{current_year}} for current version info and trends</critical>
+<critical>ALWAYS verify current versions - NEVER use hardcoded or outdated version numbers</critical>
+<critical>Communicate all responses in {communication_language} and tailor to {user_skill_level}</critical>
+<critical>Generate all documents in {document_output_language}</critical>
+
+<critical>🚨 ANTI-HALLUCINATION PROTOCOL - MANDATORY 🚨</critical>
+<critical>NEVER invent version numbers, features, or technical details - ALWAYS verify with current {{current_year}} sources</critical>
+<critical>Every technical claim (version, feature, performance, compatibility) MUST have a cited source with URL</critical>
+<critical>Version numbers MUST be verified via WebSearch - do NOT rely on training data (it's outdated!)</critical>
+<critical>When comparing technologies, cite sources for each claim (performance benchmarks, community size, etc.)</critical>
+<critical>Mark confidence levels: [Verified {{current_year}} source], [Older source - verify], [Uncertain - needs verification]</critical>
+<critical>Distinguish: FACT (from official docs/sources), OPINION (from community/reviews), SPECULATION (your analysis)</critical>
+<critical>If you cannot find current information about a technology, state: "I could not find recent {{current_year}} data on [X]"</critical>
+<critical>Extract and include source URLs in all technology profiles and comparisons</critical>
 
 <workflow>
 
-<step n="1" goal="Technical Research Discovery">
-<action>Understand the technical research requirements</action>
+<step n="1" goal="Discover technical research needs through conversation">
 
-**Welcome to Technical/Architecture Research!**
+<action>Engage conversationally based on skill level:
 
-<ask>What technical decision or research do you need?
+<check if="{user_skill_level} == 'expert'">
+  "Let's research the technical options for your decision.
 
-Common scenarios:
+I'll gather current data from {{current_year}}, compare approaches, and help you think through trade-offs.
 
-- Evaluate technology stack for a new project
-- Compare frameworks or libraries (React vs Vue, Postgres vs MongoDB)
-- Research architecture patterns (microservices, event-driven, CQRS)
-- Investigate specific technologies or tools
-- Best practices for specific use cases
-- Performance and scalability considerations
-- Security and compliance research</ask>
+What technical question are you wrestling with?"
+</check>
 
-<template-output>technical_question</template-output>
+<check if="{user_skill_level} == 'intermediate'">
+  "I'll help you research and evaluate your technical options.
+
+We'll look at current technologies (using {{current_year}} data), understand the trade-offs, and figure out what fits your needs best.
+
+What technical decision are you trying to make?"
+</check>
+
+<check if="{user_skill_level} == 'beginner'">
+  "Think of this as having a technical advisor help you research your options.
+
+I'll explain what different technologies do, why you might choose one over another, and help you make an informed decision.
+
+What technical challenge brought you here?"
+</check>
+</action>
 
-<ask>What's the context for this decision?
+<action>Through conversation, understand:
 
-- New greenfield project
-- Adding to existing system (brownfield)
-- Refactoring/modernizing legacy system
-- Proof of concept / prototype
-- Production-ready implementation
-- Academic/learning purpose</ask>
+- **The technical question** - What they need to decide or understand
+- **The context** - Greenfield? Brownfield? Learning? Production?
+- **Current constraints** - Languages, platforms, team skills, budget
+- **What they already know** - Do they have candidates in mind?
 
+Don't interrogate - explore together. If they're unsure, help them articulate the problem.
+</action>
+
+<template-output>technical_question</template-output>
 <template-output>project_context</template-output>
 
 </step>
@@ -82,49 +109,70 @@ Consider:
 
 </step>
 
-<step n="3" goal="Identify Alternatives and Options">
-<action>Research and identify technology options to evaluate</action>
+<step n="3" goal="Discover and evaluate technology options together">
 
-<ask>Do you have specific technologies in mind to compare, or should I discover options?
+<critical>MUST use WebSearch to find current options from {{current_year}}</critical>
 
-If you have specific options, list them. Otherwise, I'll research current leading solutions based on your requirements.</ask>
+<action>Ask if they have candidates in mind:
 
-<template-output if="user provides options">user_provided_options</template-output>
+"Do you already have specific technologies you want to compare, or should I search for the current options?"
+</action>
 
-<check if="discovering options">
-  <action>Conduct web research to identify current leading solutions</action>
-  <action>Search for:
+<action if="user has candidates">Great! Let's research: {{user_candidates}}</action>
 
-- "[technical_category] best tools 2025"
-- "[technical_category] comparison [use_case]"
-- "[technical_category] production experiences reddit"
-- "State of [technical_category] 2025"
-  </action>
+<action if="discovering options">Search for current leading technologies:
 
-  <invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<WebSearch>{{technical_category}} best tools {{current_year}}</WebSearch>
+<WebSearch>{{technical_category}} comparison {{use_case}} {{current_year}}</WebSearch>
+<WebSearch>{{technical_category}} popular frameworks {{current_year}}</WebSearch>
+<WebSearch>state of {{technical_category}} {{current_year}}</WebSearch>
+</action>
 
-<action>Present discovered options (typically 3-5 main candidates)</action>
-<template-output>technology_options</template-output>
+<action>Share findings conversationally:
+
+"Based on current {{current_year}} data, here are the main options:
+
+{{discovered_options}}
 
+<check if="{user_skill_level} == 'expert'">
+These are the leaders right now. Which ones make sense to evaluate for your use case?"
 </check>
 
+<check if="{user_skill_level} == 'beginner'">
+Each of these is popular for different reasons. Let me know if you want me to explain what makes each one different."
+</check>
+</action>
+
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+
+<template-output>technology_options</template-output>
+
 </step>
 
-<step n="4" goal="Deep Dive Research on Each Option">
-<action>Research each technology option in depth</action>
+<step n="4" goal="Research each technology together in depth">
 
-<critical>For each technology option, research thoroughly</critical>
+<critical>For each option, use WebSearch to gather CURRENT {{current_year}} information</critical>
 
-<step n="4a" title="Technology Profile" repeat="for-each-option">
+<step n="4a" title="Deep dive on each technology" repeat="for-each-option">
 
-Research and document:
+<action>For {{technology_name}}, conduct comprehensive research:
+
+<WebSearch>{{technology_name}} overview what is {{current_year}}</WebSearch>
+<WebSearch>{{technology_name}} latest version release notes {{current_year}}</WebSearch>
+<WebSearch>{{technology_name}} pros cons trade-offs {{current_year}}</WebSearch>
+<WebSearch>{{technology_name}} production experience real world {{current_year}}</WebSearch>
+<WebSearch>{{technology_name}} vs alternatives comparison {{current_year}}</WebSearch>
+</action>
+
+<action>Share findings conversationally and collaboratively:
+
+"Here's what I found about {{technology_name}}:
 
 **Overview:**
+{{what_it_is_and_solves}}
 
-- What is it and what problem does it solve?
-- Maturity level (experimental, stable, mature, legacy)
-- Community size and activity
-- Maintenance status and release cadence
+**Current Status ({{current_year}}):**
+{{maturity_community_release_cadence}}
 
 **Technical Characteristics:**
 
@@ -442,60 +490,49 @@ Select option (1-5):</ask>
 
 </step>
 
-<step n="FINAL" goal="Update status file on completion">
-<action>Search {output_folder}/ for files matching pattern: bmm-workflow-status.md</action>
-<action>Find the most recent file (by date in filename)</action>
-
-<check if="status file exists">
-  <invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
-    <param>mode: update</param>
-    <param>action: complete_workflow</param>
-    <param>workflow_name: research</param>
-  </invoke-workflow>
+<step n="FINAL" goal="Update status file on completion" tag="workflow-status">
+<check if="standalone_mode != true">
+  <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
+  <action>Find workflow_status key "research"</action>
+  <critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
+  <action>Update workflow_status["research"] = "{output_folder}/bmm-research-technical-{{date}}.md"</action>
+  <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
 
-  <check if="success == true">
-    <output>Status updated! Next: {{next_workflow}}</output>
-  </check>
+<action>Find first non-completed workflow in workflow_status (next workflow to do)</action>
+<action>Determine next agent from path file based on next workflow</action>
 </check>
 
 <output>**✅ Technical Research Complete**
 
 **Research Report:**
 
-- Technical research report generated and saved
+- Technical research report generated and saved to {output_folder}/bmm-research-technical-{{date}}.md
 
-**Status file updated:**
+{{#if standalone_mode != true}}
+**Status Updated:**
 
-- Current step: research (technical) ✓
-- Progress: {{new_progress_percentage}}%
+- Progress tracking updated: research marked complete
+- Next workflow: {{next_workflow}}
+  {{else}}
+  **Note:** Running in standalone mode (no progress tracking)
+  {{/if}}
 
 **Next Steps:**
 
-- **Next required:** {{next_workflow}} ({{next_agent}} agent)
+{{#if standalone_mode != true}}
+
+- **Next workflow:** {{next_workflow}} ({{next_agent}} agent)
 - **Optional:** Review findings with architecture team, or run additional analysis workflows
 
 Check status anytime with: `workflow-status`
-</output>
-</check>
-
-<check if="status file not found">
-  <output>**✅ Technical Research Complete**
-
-**Research Report:**
-
-- Technical research report generated and saved
-
-Note: Running in standalone mode (no status file).
-
-**Next Steps:**
-
+{{else}}
 Since no workflow is in progress:
 
 - Review technical research findings
 - Refer to the BMM workflow guide if unsure what to do next
 - Or run `workflow-init` to create a workflow path and get guided next steps
+  {{/if}}
   </output>
-  </check>
   </step>
 
 </workflow>

package/src/modules/bmm/workflows/1-analysis/research/template-market.md

@@ -293,6 +293,40 @@
 
 ---
 
+## References and Sources
+
+**CRITICAL: All data in this report must be verifiable through the sources listed below**
+
+### Market Size and Growth Data Sources
+
+{{sources_market_size}}
+
+### Competitive Intelligence Sources
+
+{{sources_competitive}}
+
+### Customer Research Sources
+
+{{sources_customer}}
+
+### Industry Trends and Analysis Sources
+
+{{sources_trends}}
+
+### Additional References
+
+{{sources_additional}}
+
+### Source Quality Assessment
+
+- **High Credibility Sources (2+ corroborating):** {{high_confidence_count}} claims
+- **Medium Credibility (single source):** {{medium_confidence_count}} claims
+- **Low Credibility (needs verification):** {{low_confidence_count}} claims
+
+**Note:** Any claim marked [Low Confidence] or [Single source] should be independently verified before making critical business decisions.
+
+---
+
 ## Document Information
 
 **Workflow:** BMad Market Research Workflow v1.0
@@ -305,7 +339,9 @@
 - **Data Freshness:** Current as of {{date}}
 - **Source Reliability:** {{source_reliability_score}}
 - **Confidence Level:** {{confidence_level}}
+- **Total Sources Cited:** {{total_sources}}
+- **Web Searches Conducted:** {{search_count}}
 
 ---
 
-_This market research report was generated using the BMad Method Market Research Workflow, combining systematic analysis frameworks with real-time market intelligence gathering._
+_This market research report was generated using the BMad Method Market Research Workflow, combining systematic analysis frameworks with real-time market intelligence gathering. All factual claims are backed by cited sources with verification dates._

package/src/modules/bmm/workflows/1-analysis/research/template-technical.md

@@ -198,13 +198,48 @@
 
 ---
 
+## References and Sources
+
+**CRITICAL: All technical claims, versions, and benchmarks must be verifiable through sources below**
+
+### Official Documentation and Release Notes
+
+{{sources_official_docs}}
+
+### Performance Benchmarks and Comparisons
+
+{{sources_benchmarks}}
+
+### Community Experience and Reviews
+
+{{sources_community}}
+
+### Architecture Patterns and Best Practices
+
+{{sources_architecture}}
+
+### Additional Technical References
+
+{{sources_additional}}
+
+### Version Verification
+
+- **Technologies Researched:** {{technology_count}}
+- **Versions Verified ({{current_year}}):** {{verified_versions_count}}
+- **Sources Requiring Update:** {{outdated_sources_count}}
+
+**Note:** All version numbers were verified using current {{current_year}} sources. Versions may change - always verify latest stable release before implementation.
+
+---
+
 ## Document Information
 
 **Workflow:** BMad Research Workflow - Technical Research v2.0
 **Generated:** {{date}}
 **Research Type:** Technical/Architecture Research
 **Next Review:** [Date for review/update]
+**Total Sources Cited:** {{total_sources}}
 
 ---
 
-_This technical research report was generated using the BMad Method Research Workflow, combining systematic technology evaluation frameworks with real-time research and analysis._
+_This technical research report was generated using the BMad Method Research Workflow, combining systematic technology evaluation frameworks with real-time research and analysis. All version numbers and technical claims are backed by current {{current_year}} sources._

package/src/modules/bmm/workflows/1-analysis/research/workflow.yaml

@@ -11,6 +11,17 @@ communication_language: "{config_source}:communication_language"
 document_output_language: "{config_source}:document_output_language"
 user_skill_level: "{config_source}:user_skill_level"
 date: system-generated
+current_year: system-generated
+current_month: system-generated
+
+# Research behavior - WEB RESEARCH IS DEFAULT
+enable_web_research: true
+
+# Source tracking and verification - CRITICAL FOR ACCURACY
+require_citations: true
+require_source_urls: true
+minimum_sources_per_claim: 2
+fact_check_critical_data: true
 
 # Workflow components - ROUTER PATTERN
 installed_path: "{project-root}/bmad/bmm/workflows/1-analysis/research"
@@ -47,3 +58,5 @@ web_bundle:
     - "bmad/bmm/workflows/1-analysis/research/template-deep-prompt.md"
     - "bmad/bmm/workflows/1-analysis/research/template-technical.md"
     - "bmad/bmm/workflows/1-analysis/research/checklist.md"
+    - "bmad/bmm/workflows/1-analysis/research/checklist-deep-prompt.md"
+    - "bmad/bmm/workflows/1-analysis/research/checklist-technical.md"

package/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md

@@ -12,28 +12,60 @@
 
 <critical>DOCUMENT OUTPUT: Professional, specific, actionable UX design decisions WITH RATIONALE. User skill level ({user_skill_level}) affects conversation style ONLY, not document content.</critical>
 
-<step n="0" goal="Validate workflow and extract project configuration">
+## 📚 Input Document Discovery
 
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
-  <param>mode: data</param>
-  <param>data_request: project_config</param>
-</invoke-workflow>
+This workflow requires: PRD or product brief, and may reference epics/stories, brainstorming documents, or brownfield project documentation.
 
-<check if="status_exists == false">
-  <output>**Note: No Workflow Status File Found**
+**Discovery Process** (execute for each referenced document):
 
-Create UX Design can run standalone or as part of the BMM planning workflow.
+1. **Search for whole document first** - Use fuzzy file matching to find the complete document
+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 the document structure
+   - Read ALL section files listed in the index
+   - Treat the combined content as if it were a single document
+4. **Brownfield projects**: The `document-project` workflow always creates `{output_folder}/docs/index.md`
 
-For standalone use, we'll gather requirements as we go.
-For integrated use, run `workflow-init` first for better context.
-</output>
-<action>Set mode: standalone</action>
+**Priority**: If both whole and sharded versions exist, use the whole document.
+
+**Fuzzy matching**: Be flexible with document names - users may use variations in naming conventions.
+
+<step n="0" goal="Validate workflow readiness" tag="workflow-status">
+<action>Check if {output_folder}/bmm-workflow-status.yaml exists</action>
+
+<check if="status file not found">
+  <output>No workflow status file found. Create UX Design can run standalone or as part of BMM planning workflow.</output>
+  <output>For standalone use, we'll gather requirements as we go. For integrated use, run `workflow-init` first for better context.</output>
+  <action>Set standalone_mode = true</action>
 </check>
 
-<check if="status_exists == true">
-  <action>Store {{status_file_path}} for later updates</action>
-  <action>Store {{project_level}} for scoping decisions</action>
-  <action>Set mode: integrated</action>
+<check if="status file found">
+  <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
+  <action>Parse workflow_status section</action>
+  <action>Check status of "create-design" workflow</action>
+  <action>Get project_level from YAML metadata</action>
+  <action>Find first non-completed workflow (next expected workflow)</action>
+
+  <check if="create-design status is file path (already completed)">
+    <output>⚠️ UX Design already completed: {{create-design status}}</output>
+    <ask>Re-running will overwrite the existing UX design. Continue? (y/n)</ask>
+    <check if="n">
+      <output>Exiting. Use workflow-status to see your next step.</output>
+      <action>Exit workflow</action>
+    </check>
+  </check>
+
+  <check if="create-design is not the next expected workflow">
+    <output>⚠️ Next expected workflow: {{next_workflow}}. UX Design is out of sequence.</output>
+    <ask>Continue with UX Design anyway? (y/n)</ask>
+    <check if="n">
+      <output>Exiting. Run {{next_workflow}} instead.</output>
+      <action>Exit workflow</action>
+    </check>
+  </check>
+
+<action>Set standalone_mode = false</action>
+<action>Store {{project_level}} for scoping decisions</action>
 </check>
 </step>
 
@@ -1116,12 +1148,16 @@ Based on your deployment intent: {{recommendation}}
 
 <action>Save final document to {default_output_file}</action>
 
-  <check if="tracking_mode == true">
-    <invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
-      <param>mode: update</param>
-      <param>action: complete_workflow</param>
-      <param>workflow_name: create-ux-design</param>
-    </invoke-workflow>
+  <check if="standalone_mode != true">
+    <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
+    <action>Find workflow_status key "create-design"</action>
+    <critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
+    <action>Update workflow_status["create-design"] = "{default_output_file}"</action>
+    <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
+
+    <action>Find first non-completed workflow in workflow_status (next workflow to do)</action>
+    <action>Determine next agent from path file based on next workflow</action>
+
   </check>
 
 <ask>🎨 **One more thing!** Want to see your design come to life?

package/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml

@@ -23,6 +23,28 @@ prd_file: "{output_folder}/bmm-PRD.md or PRD.md or product-requirements.md"
 brief_file: "{output_folder}/product-brief.md or brief.md or project-brief.md"
 brainstorm_file: "{output_folder}/brainstorming.md or brainstorm.md or ideation.md"
 
+# Smart input file references - handles both whole docs and sharded docs
+# Priority: Whole document first, then sharded version
+input_file_patterns:
+  prd:
+    whole: "{output_folder}/*prd*.md"
+    sharded: "{output_folder}/*prd*/index.md"
+
+  product_brief:
+    whole: "{output_folder}/*brief*.md"
+    sharded: "{output_folder}/*brief*/index.md"
+
+  epics:
+    whole: "{output_folder}/*epic*.md"
+    sharded: "{output_folder}/*epic*/index.md"
+
+  brainstorming:
+    whole: "{output_folder}/*brainstorm*.md"
+    sharded: "{output_folder}/*brainstorm*/index.md"
+
+  document_project:
+    sharded: "{output_folder}/docs/index.md"
+
 # Module path and component files
 installed_path: "{project-root}/bmad/bmm/workflows/2-plan-workflows/create-ux-design"
 instructions: "{installed_path}/instructions.md"

package/src/modules/bmm/workflows/2-plan-workflows/gdd/instructions-gdd.md

@@ -14,6 +14,24 @@
 
 <critical>DOCUMENT OUTPUT: Concise, clear, actionable game design specs. Use tables/lists over prose. User skill level ({user_skill_level}) affects conversation style ONLY, not document content.</critical>
 
+## Input Document Discovery
+
+This workflow requires: game brief, and may reference market research or brownfield project documentation.
+
+**Discovery Process** (execute for each referenced document):
+
+1. **Search for whole document first** - Use fuzzy file matching to find the complete document
+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 the document structure
+   - Read ALL section files listed in the index
+   - Treat the combined content as if it were a single document
+4. **Brownfield projects**: The `document-project` workflow always creates `{output_folder}/docs/index.md`
+
+**Priority**: If both whole and sharded versions exist, use the whole document.
+
+**Fuzzy matching**: Be flexible with document names - users may use variations in naming conventions.
+
 <step n="0" goal="Validate workflow and extract project configuration">
 
 <invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
@@ -67,19 +85,27 @@ Use: `prd`
 </check>
 </step>
 
-<step n="0.5" goal="Validate workflow sequencing">
+<step n="0.5" goal="Validate workflow sequencing" tag="workflow-status">
 
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
-  <param>mode: validate</param>
-  <param>calling_workflow: gdd</param>
-</invoke-workflow>
+<check if="standalone_mode != true">
+  <action>Check status of "gdd" workflow in loaded status file</action>
+
+  <check if="gdd status is file path (already completed)">
+    <output>⚠️ GDD already completed: {{gdd status}}</output>
+    <ask>Re-running will overwrite the existing GDD. Continue? (y/n)</ask>
+    <check if="n">
+      <output>Exiting. Use workflow-status to see your next step.</output>
+      <action>Exit workflow</action>
+    </check>
+  </check>
 
-<check if="warning != ''">
-  <output>{{warning}}</output>
-  <ask>Continue with GDD anyway? (y/n)</ask>
-  <check if="n">
-    <output>{{suggestion}}</output>
-    <action>Exit workflow</action>
+  <check if="gdd is not the next expected workflow (latter items are completed already in the list)">
+    <output>⚠️ Next expected workflow: {{next_workflow}}. GDD is out of sequence.</output>
+    <ask>Continue with GDD anyway? (y/n)</ask>
+    <check if="n">
+      <output>Exiting. Run {{next_workflow}} instead.</output>
+      <action>Exit workflow</action>
+    </check>
   </check>
 </check>
 </step>
@@ -328,18 +354,23 @@ For each {{placeholder}} in the fragment, elicit and capture that information.
 
 </step>
 
-<step n="15" goal="Update status and populate story sequence">
+<step n="15" goal="Update status and populate story sequence" tag="workflow-status">
 
-<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
-  <param>mode: update</param>
-  <param>action: complete_workflow</param>
-  <param>workflow_name: gdd</param>
-  <param>populate_stories_from: {epics_output_file}</param>
-</invoke-workflow>
+<check if="standalone_mode != true">
+  <action>Load the FULL file: {output_folder}/bmm-workflow-status.yaml</action>
+  <action>Find workflow_status key "gdd"</action>
+  <critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
+  <action>Update workflow_status["gdd"] = "{output_folder}/bmm-gdd-{{game_name}}-{{date}}.md"</action>
+  <action>Save file, preserving ALL comments and structure including STATUS DEFINITIONS</action>
+
+<action>Parse {epics_output_file} to extract all stories</action>
+<action>Populate story_sequence section in status file with story IDs</action>
+<action>Set each story status to "not-started"</action>
+<output>Loaded {{total_stories}} stories from epics into story sequence.</output>
 
-<check if="success == true">
-  <output>Status updated! Next: {{next_workflow}} ({{next_agent}} agent)</output>
-  <output>Loaded {{total_stories}} stories from epics.</output>
+<action>Find first non-completed workflow in workflow_status (next workflow to do)</action>
+<action>Determine next agent from path file based on next workflow</action>
+<output>Next workflow: {{next_workflow}} ({{next_agent}} agent)</output>
 </check>
 
 </step>

package/src/modules/bmm/workflows/2-plan-workflows/gdd/workflow.yaml

@@ -30,6 +30,20 @@ recommended_inputs:
   - narrative_design: "{output_folder}/narrative-design.md"
   - market_research: "{output_folder}/market-research.md"
 
+# Smart input file references - handles both whole docs and sharded docs
+# Priority: Whole document first, then sharded version
+input_file_patterns:
+  game_brief:
+    whole: "{output_folder}/*game-brief*.md"
+    sharded: "{output_folder}/*game-brief*/index.md"
+
+  research:
+    whole: "{output_folder}/*research*.md"
+    sharded: "{output_folder}/*research*/index.md"
+
+  document_project:
+    sharded: "{output_folder}/docs/index.md"
+
 standalone: true
 
 web_bundle: