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

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

@@ -9,8 +9,10 @@ output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 document_output_language: "{config_source}:document_output_language"
-story_path: "{config_source}:dev_ephemeral_location"
+story_path: "{config_source}:sprint_artifacts/stories"
 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/story-context"
@@ -18,41 +20,37 @@ template: "{installed_path}/context-template.xml"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 
-# Variables and inputs
-variables:
-  story_path: "" # Optional: Explicit story path. If not provided, finds first story with status "drafted"
-  story_dir: "{config_source}:dev_ephemeral_location"
-
 # 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"
+    load_strategy: "INDEX_GUIDED"
 
 # Output configuration
 # Uses story_key from sprint-status.yaml (e.g., "1-2-user-authentication")
-default_output_file: "{story_dir}/{{story_key}}.context.xml"
+default_output_file: "{story_path}/{{story_key}}.context.xml"
 
 standalone: true
 

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

@@ -9,6 +9,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"
+sprint_status: "{sprint_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
 
 # Workflow components
 installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-done"
@@ -16,8 +18,7 @@ instructions: "{installed_path}/instructions.md"
 
 # Variables and inputs
 variables:
-  story_path: "" # Explicit path to story file
-  story_dir: "{config_source}:dev_ephemeral_location" # Directory where stories are stored
+  story_dir: "{config_source}:sprint_artifacts" # Directory where stories are stored
 
 # Output configuration - no output file, just status updates
 default_output_file: ""

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

@@ -14,12 +14,12 @@
 
 <action>If {{story_path}} is provided → use it directly; extract story_key from filename or metadata; GOTO mark_ready</action>
 
-<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>Load the FULL file: {sprint_status}</action>
 <action>Read ALL lines from beginning to end - do not skip any content</action>
 <action>Parse the development_status section completely</action>
 
-<action>Find ALL stories (reading in order from top to bottom) where:
+<action>Find ALL stories (reading in order from start to end) where:
 
 - Key matches pattern: number-number-name (e.g., "1-2-user-auth")
 - NOT an epic key (epic-X) or retrospective (epic-X-retrospective)
@@ -30,7 +30,7 @@
 <action>Count total drafted stories found</action>
 
 <check if="no drafted stories found">
-  <output>📋 No drafted stories found in sprint-status.yaml
+  <output>📋 No drafted stories found in {sprint_status}
 
 All stories are either still in backlog or already marked ready/in-progress/done.
 
@@ -67,7 +67,7 @@ All stories are either still in backlog or already marked ready/in-progress/done
 </step>
 
 <step n="2" goal="Update sprint status to ready-for-dev" tag="sprint-status">
-<action>Load the FULL file: {{output_folder}}/sprint-status.yaml</action>
+<action>Load the FULL file: {sprint_status}</action>
 <action>Find development_status key matching {{story_key}}</action>
 <action>Verify current status is "drafted" (expected previous state)</action>
 <action>Update development_status[{{story_key}}] = "ready-for-dev"</action>

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

@@ -9,6 +9,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"
+sprint_status: "{sprint_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
 
 # Workflow components
 installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-ready"
@@ -16,11 +18,7 @@ instructions: "{installed_path}/instructions.md"
 
 # Variables and inputs
 variables:
-  story_path: "" # Explicit path to story file
-  story_dir: "{config_source}:dev_ephemeral_location" # Directory where stories are stored
-
-# Output configuration - no output file, just status updates
-default_output_file: ""
+  story_dir: "{config_source}:sprint_artifacts"
 
 standalone: true
 

package/src/modules/bmm/_module-installer/install-config.yaml

@@ -35,14 +35,9 @@ user_skill_level:
     - value: "expert"
       label: "Expert - Deep technical knowledge, be direct and technical"
 
-tech_docs:
-  prompt: "Where is Technical Documentation located within the project?"
-  default: "{output_folder}/technical"
-  result: "{project-root}/{value}"
-
-dev_ephemeral_location:
-  prompt: "Where should ephemeral development artifacts be stored (workflow and sprint status, stories, epics, temp context, etc...)?"
-  default: "{bmad_folder}-ephemeral"
+sprint_artifacts:
+  prompt: "Where should Sprint Artifacts be stored (sprint status, stories, story context, temp context, etc...)?"
+  default: "{output_folder}/sprint-artifacts"
   result: "{project-root}/{value}"
 
 # TEA Agent Configuration

package/src/modules/bmm/_module-installer/installer.js

@@ -63,9 +63,9 @@ async function install(options) {
     }
 
     // Create dev story location if configured
-    if (config['dev_ephemeral_location']) {
+    if (config['sprint_artifacts']) {
       // Strip {project-root}/ prefix if present
-      const storyConfig = config['dev_ephemeral_location'].replace('{project-root}/', '');
+      const storyConfig = config['sprint_artifacts'].replace('{project-root}/', '');
       const storyPath = path.join(projectRoot, storyConfig);
       if (!(await fs.pathExists(storyPath))) {
         logger.log(chalk.yellow(`Creating story directory: ${storyConfig}`));

package/src/modules/bmm/agents/analyst.agent.yaml

@@ -43,6 +43,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/bmm/agents/architect.agent.yaml

@@ -37,6 +37,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/bmm/agents/pm.agent.yaml

@@ -56,6 +56,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/bmm/agents/sm.agent.yaml

@@ -67,6 +67,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/bmm/agents/tea.agent.yaml

@@ -60,6 +60,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/bmm/agents/tech-writer.agent.yaml

@@ -15,7 +15,7 @@ agent:
     principles: Documentation is teaching. Every doc helps someone accomplish a task. Clarity above all. Docs are living artifacts that evolve with code.
 
   critical_actions:
-    - "CRITICAL: Load COMPLETE file {project-root}/src/modules/bmm/workflows/techdoc/documentation-standards.md into permanent memory and follow ALL rules within"
+    - "CRITICAL: Load COMPLETE file {project-root}/{bmad_folder}/bmm/workflows/techdoc/documentation-standards.md into permanent memory and follow ALL rules within"
     - "Load into memory {project-root}/{bmad_folder}/bmm/config.yaml and set variables"
     - "Remember the user's name is {user_name}"
     - "ALWAYS communicate in {communication_language}"
@@ -68,6 +68,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/bmm/agents/ux-designer.agent.yaml

@@ -33,6 +33,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/bmm/workflows/1-analysis/domain-research/workflow.yaml

@@ -23,19 +23,6 @@ domain_knowledge_base: "{installed_path}/domain-knowledge-base.md"
 # Output configuration
 default_output_file: "{output_folder}/domain-brief.md"
 
-# Workflow metadata
-version: "6.0.0-alpha"
-category: "analysis"
-complexity: "medium"
-execution_time: "30-45 minutes"
-prerequisites:
-  - "Basic project understanding"
-when_to_use:
-  - "Complex regulated domains (healthcare, finance, aerospace)"
-  - "Novel technical domains requiring deep understanding"
-  - "Before PRD when domain expertise needed"
-  - "When compliance and regulations matter"
-
 standalone: true
 
 # Web bundle configuration for standalone deployment

package/src/modules/bmm/workflows/1-analysis/product-brief/instructions.md

@@ -12,19 +12,13 @@
 
 This workflow may reference: market research, brainstorming documents, user specified other inputs, or brownfield project documentation.
 
-**Discovery Process** (execute for each referenced document):
+**All input files are discovered and loaded automatically via the `discover_inputs` protocol in Step 0.5**
 
-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`
+After discovery completes, the following content variables will be available:
 
-**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.
+- `{research_content}` - Market research or domain research documents
+- `{brainstorming_content}` - Brainstorming session outputs
+- `{document_project_content}` - Brownfield project documentation (intelligently loaded via INDEX_GUIDED strategy)
 
 <workflow>
 
@@ -68,6 +62,10 @@ Product Brief is most valuable for Level 2+ projects, but can help clarify visio
 </check>
 </step>
 
+<step n="0.5" goal="Discover and load input documents">
+<invoke-protocol name="discover_inputs" />
+</step>
+
 <step n="1" goal="Begin the journey and understand context">
 <action>Welcome {user_name} warmly in {communication_language}
 

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

@@ -21,17 +21,21 @@ 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:
   research:
     whole: "{output_folder}/*research*.md"
     sharded: "{output_folder}/*research*/index.md"
+    load_strategy: "FULL_LOAD"
 
   brainstorming:
     whole: "{output_folder}/*brainstorm*.md"
     sharded: "{output_folder}/*brainstorm*/index.md"
+    load_strategy: "FULL_LOAD"
 
   document_project:
     sharded: "{output_folder}/docs/index.md"
+    load_strategy: "INDEX_GUIDED"
 
 # Module path and component files
 installed_path: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief"

package/src/modules/bmm/workflows/1-analysis/research/checklist-deep-prompt.md

@@ -140,5 +140,5 @@ _List minor improvements that would enhance the prompt:_
 
 **Validation Complete:** ☐ Yes ☐ No
 **Ready to Execute:** ☐ Yes ☐ No
-**Reviewer:** \***\*\_\*\***
-**Date:** \***\*\_\*\***
+**Reviewer:** {agent}
+**Date:** {date}

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

@@ -245,5 +245,5 @@ _List areas requiring further investigation:_
 
 **Validation Complete:** ☐ Yes ☐ No
 **Ready for Decision:** ☐ Yes ☐ No
-**Reviewer:** \***\*\_\*\***
-**Date:** \***\*\_\*\***
+**Reviewer:** {agent}
+**Date:** {date}

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

@@ -295,5 +295,5 @@ _List areas requiring further investigation:_
 
 **Validation Complete:** ☐ Yes ☐ No
 **Ready for Distribution:** ☐ Yes ☐ No
-**Reviewer:** **\*\***\_\_\_\_**\*\***
-**Date:** **\*\***\_\_\_\_**\*\***
+**Reviewer:** {reviewer}
+**Date:** {date}

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

@@ -211,8 +211,6 @@ Examples:
 
 <template-output>special_requirements</template-output>
 
-<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
-
 </step>
 
 <step n="6" goal="Define Validation and Follow-up Strategy">

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

@@ -114,8 +114,6 @@ Work with the user to establish:
 
 <action if="user_has_questions">Explore surprising data points together</action>
 
-<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
-
 <template-output>sources_market_size</template-output>
 </step>
 
@@ -239,7 +237,6 @@ For each major segment, research and define:
 - Purchasing frequency
 - Budget allocation
 
-<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
 <template-output>segment*profile*{{segment_number}}</template-output>
 </step>
 
@@ -313,8 +310,7 @@ Use {{current_year}} in all searches.
 
 <action if="user has follow-up questions">Dig deeper based on their interests</action>
 
-<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
-<template-output>competitor*analysis*{{competitor_name}}</template-output>
+<template-output>competitor-analysis-{{competitor_name}}</template-output>
 </step>
 
 <step n="6c" title="Competitive Positioning Map">
@@ -437,7 +433,6 @@ For each opportunity:
 - Risk assessment
 - Success criteria
 
-<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
 <template-output>market_opportunities</template-output>
 </step>
 

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

@@ -143,8 +143,6 @@ Each of these is popular for different reasons. Let me know if you want me to ex
 </check>
 </action>
 
-<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
-
 <template-output>technology_options</template-output>
 
 </step>
@@ -221,7 +219,6 @@ Each of these is popular for different reasons. Let me know if you want me to ex
 - Training costs
 - Total cost of ownership estimate
 
-<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
 <template-output>tech*profile*{{option_number}}</template-output>
 
 </step>
@@ -392,8 +389,6 @@ Research and document:
 - Contingency options if primary choice doesn't work
 - Exit strategy considerations
 
-<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml</invoke-task>
-
 <template-output>recommendations</template-output>
 
 </step>

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

@@ -51,10 +51,15 @@
 </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}, {product_brief_content}, {epics_content}, {brainstorming_content}, {document_project_content}</note>
+</step>
+
 <step n="1a" goal="Confirm project understanding or gather basic context">
   <critical>A UX designer must understand the WHY before designing the HOW</critical>
 
-<action>Attempt to load context documents using fuzzy matching: - PRD: {prd_file} - Product Brief: {brief_file} - Brainstorming: {brainstorm_file}
+<action>Review loaded context from Step 0.5: {prd_content}, {product_brief_content}, {epics_content}, {brainstorming_content}
 </action>
 
   <check if="documents_found">

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

@@ -25,25 +25,31 @@ brainstorm_file: "{output_folder}/brainstorming.md or brainstorm.md or ideation.
 
 # 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"
 
   product_brief:
     whole: "{output_folder}/*brief*.md"
     sharded: "{output_folder}/*brief*/index.md"
+    load_strategy: "FULL_LOAD"
 
   epics:
     whole: "{output_folder}/*epic*.md"
     sharded: "{output_folder}/*epic*/index.md"
+    load_strategy: "FULL_LOAD"
 
   brainstorming:
     whole: "{output_folder}/*brainstorm*.md"
     sharded: "{output_folder}/*brainstorm*/index.md"
+    load_strategy: "FULL_LOAD"
 
   document_project:
     sharded: "{output_folder}/docs/index.md"
+    load_strategy: "INDEX_GUIDED"
 
 # Module path and component files
 installed_path: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design"

package/src/modules/bmm/workflows/2-plan-workflows/prd/checklist.md

@@ -17,7 +17,7 @@
 ### Core Sections Present
 
 - [ ] Executive Summary with vision alignment
-- [ ] Product magic essence clearly articulated
+- [ ] Product differentiator clearly articulated
 - [ ] Project classification (type, domain, complexity)
 - [ ] Success criteria defined
 - [ ] Product scope (MVP, Growth, Vision) clearly delineated
@@ -38,7 +38,7 @@
 
 - [ ] No unfilled template variables ({{variable}})
 - [ ] All variables properly populated with meaningful content
-- [ ] Product magic woven throughout (not just stated once)
+- [ ] Product differentiator reflected throughout (not just stated once)
 - [ ] Language is clear, specific, and measurable
 - [ ] Project type correctly identified and sections match
 - [ ] Domain complexity appropriately addressed
@@ -210,7 +210,7 @@
 ### Alignment Checks
 
 - [ ] Success metrics in PRD align with story outcomes
-- [ ] Product magic articulated in PRD reflected in epic goals
+- [ ] Product differentiator articulated in PRD reflected in epic goals
 - [ ] Technical preferences in PRD align with story implementation hints
 - [ ] Scope boundaries consistent across all documents
 
@@ -296,14 +296,10 @@ If ANY of these are true, validation FAILS:
 
 ## Validation Summary
 
-**Total Validation Points:** ~85
-
-### Scoring Guide
-
-- **Pass Rate ≥ 95% (81+/85):** ✅ EXCELLENT - Ready for architecture phase
-- **Pass Rate 85-94% (72-80/85):** ⚠️ GOOD - Minor fixes needed
-- **Pass Rate 70-84% (60-71/85):** ⚠️ FAIR - Important issues to address
-- **Pass Rate < 70% (<60/85):** ❌ POOR - Significant rework required
+- **Pass Rate ≥ 95%:** ✅ EXCELLENT - Ready for architecture phase
+- **Pass Rate 85-94%:** ⚠️ GOOD - Minor fixes needed
+- **Pass Rate 70-84%:** ⚠️ FAIR - Important issues to address
+- **Pass Rate < 70%:** ❌ POOR - Significant rework required
 
 ### Critical Issue Threshold
 
@@ -316,7 +312,7 @@ If ANY of these are true, validation FAILS:
 
 **When validating:**
 
-1. **Load ALL documents:**
+1. **Load ALL documents - whole or sharded (but not both of each) for example epics.md vs epics/\*.md:**
    - PRD.md (required)
    - epics.md (required)
    - product-brief.md (if exists)

package/src/modules/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/epics-template.md

@@ -11,10 +11,24 @@
 
 This document provides the complete epic and story breakdown for {{project_name}}, decomposing the requirements from the [PRD](./PRD.md) into implementable stories.
 
+**Living Document Notice:** This is the initial version. It will be updated after UX Design and Architecture workflows add interaction and technical details to stories.
+
 {{epics_summary}}
 
 ---
 
+## Functional Requirements Inventory
+
+{{fr_inventory}}
+
+---
+
+## FR Coverage Map
+
+{{fr_coverage_map}}
+
+---
+
 <!-- Repeat for each epic (N = 1, 2, 3...) -->
 
 ## Epic {{N}}: {{epic_title_N}}
@@ -49,4 +63,18 @@ So that {{value_benefit}}.
 
 ---
 
+## FR Coverage Matrix
+
+{{fr_coverage_matrix}}
+
+---
+
+## Summary
+
+{{epic_breakdown_summary}}
+
+---
+
 _For implementation: Use the `create-story` workflow to generate individual story implementation plans from this epic breakdown._
+
+_This document will be updated after UX Design and Architecture workflows to incorporate interaction details and technical decisions._