bmad-method 6.0.0-alpha.20 → 6.0.0-alpha.22

package/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-01-init.md

@@ -3,7 +3,6 @@
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
 - 🛑 NEVER generate content without user input
-
 - 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
 - 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
 - ✅ ALWAYS treat this as collaborative discovery between architectural peers
@@ -11,6 +10,7 @@
 - 💬 FOCUS on initialization and setup only - don't look ahead to future steps
 - 🚪 DETECT existing workflow state and handle continuation properly
 - ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 
@@ -36,7 +36,7 @@ Initialize the Architecture workflow by detecting continuation state, discoverin
 
 First, check if the output document already exists:
 
-- Look for existing {output_folder}||{planning_artifacts} architecture.md or \*\*/architecture/
+- Look for existing {planning_artifacts}/`*architecture*.md`
 - If exists, read the complete file(s) including frontmatter
 - If not exists, this is a fresh workflow
 
@@ -54,58 +54,30 @@ If no document exists or no `stepsCompleted` in frontmatter:
 
 #### A. Input Document Discovery
 
-Discover and load context documents using smart discovery:
-
-**PRD Document (Priority: Analysis → Main → Sharded → Whole):**
-
-1. Check analysis folders: {output_folder} and {planning_artifacts} for a `*prd*.md`
-2. If no main files: Check for sharded PRD folder: `**/*prd*/**/*.md`
-3. If sharded folder exists: Load EVERY file in that folder completely
-4. Add discovered files to `inputDocuments` frontmatter
-
-**Epics/Stories Document (Priority: Analysis → Main → Sharded → Whole):**
-
-1. Check folders: {output_folder} and {planning_artifacts} for a `*epic*.md`
-2. If no analysis files: Try main folder: `{output_folder}/*epic*.md`
-3. If no main files: Check for sharded epics folder: `{output_folder}/*epic*/**/*.md`
-4. If sharded folder exists: Load EVERY file in that folder completely
-5. Add discovered files to `inputDocuments` frontmatter
-
-**UX Design Specification (Priority: Analysis → Main → Sharded → Whole):**
-
-1. Check folders: {output_folder} and {planning_artifacts} for a `*ux*.md`
-2. If no main files: Check for sharded UX folder: `{output_folder}/*ux*/**/*.md`
-3. If sharded folder exists: Load EVERY file in that folder completely
-4. Add discovered files to `inputDocuments` frontmatter
-
-**Research Documents (Priority: Analysis → Main):**
-
-1. Check folders {output_folder} and {planning_artifacts} for `/research/*research*.md`
-2. If no files: Try folder: `{output_folder}/*research*.md`
-3. Add discovered files to `inputDocuments` frontmatter
-
-**Project Documentation (Existing Projects):**
+Discover and load context documents using smart discovery. Documents can be in the following locations:
+- {planning_artifacts}/**
+- {output_folder}/**
+- {product_knowledge}/**
+- docs/**
 
-1. Look for index file: `{project_knowledge}/index.md`
-2. CRITICAL: Load index.md to understand what project files are available
-3. Read available files from index to understand existing project context
-4. This provides essential context for extending existing project with new architecture
-5. Add discovered files to `inputDocuments` frontmatter
-6. IF no index.md, ask user which files from the folder to include
+Also - when searching - documents can be a single markdown file, or a folder with an index and multiple files. For Example, if searching for `*foo*.md` and not found, also search for a folder called *foo*/index.md (which indicates sharded content)
 
-**Project Context Rules (Critical for AI Agents):**
+Try to discover the following:
+- Product Brief (`*brief*.md`)
+- Product Requirements Document (`*prd*.md`)
+- UX Design (`*ux-design*.md`) and other
+- Research Documents (`*research*.md`)
+- Project Documentation (generally multiple documents might be found for this in the `{product_knowledge}` or `docs` folder.)
+- Project Context (`**/project-context.md`)
 
-1. Check for project context file: `**/project-context.md`
-2. If exists: Load COMPLETE file contents - this contains critical rules for AI agents
-3. Add to frontmatter `hasProjectContext: true` and track file path
-4. Report to user: "Found existing project context with {number_of_rules} agent rules"
-5. This file contains language-specific patterns, testing rules, and implementation guidelines that must be followed
+<critical>Confirm what you have found with the user, along with asking if the user wants to provide anything else. Only after this confirmation will you proceed to follow the loading rules</critical>
 
 **Loading Rules:**
 
-- Load ALL discovered files completely (no offset/limit)
-- For sharded folders, load ALL files to get complete picture
-- For existing projects, use index.md as guide to what's relevant
+- Load ALL discovered files completely that the user confirmed or provided (no offset/limit)
+- If there is a project context, whatever is relevant should try to be biased in the remainder of this whole workflow process
+- For sharded folders, load ALL files to get complete picture, using the index first to potentially know the potential of each document
+- index.md is a guide to what's relevant whenever available
 - Track all successfully loaded files in frontmatter `inputDocuments` array
 
 #### B. Validate Required Inputs
@@ -117,13 +89,13 @@ Before proceeding, verify we have the essential inputs:
 - If no PRD found: "Architecture requires a PRD to work from. Please run the PRD workflow first or provide the PRD file path."
 - Do NOT proceed without PRD
 
-**Other Inputs:**
+**Other Input that might exist:**
 
-- UX Spec: "Provides UI/UX architectural requirements" (Optional)
+- UX Spec: "Provides UI/UX architectural requirements"
 
 #### C. Create Initial Document
 
-Copy the template from `{installed_path}/architecture-decision-template.md` to `{output_folder}/architecture.md`
+Copy the template from `{installed_path}/architecture-decision-template.md` to `{planning_artifacts}/architecture.md`
 
 #### D. Complete Initialization and Report
 
@@ -131,7 +103,7 @@ Complete setup and report to user:
 
 **Document Setup:**
 
-- Created: `{output_folder}/architecture.md` from template
+- Created: `{planning_artifacts}/architecture.md` from template
 - Initialized frontmatter with workflow state
 
 **Input Documents Discovered:**
@@ -141,7 +113,6 @@ Report what was found:
 **Documents Found:**
 
 - PRD: {number of PRD files loaded or "None found - REQUIRED"}
-- Epics/Stories: {number of epic files loaded or "None found"}
 - UX Design: {number of UX files loaded or "None found"}
 - Research: {number of research files loaded or "None found"}
 - Project docs: {number of project files loaded or "None found"}
@@ -177,6 +148,6 @@ Ready to begin architectural decision making. Do you have any other documents yo
 
 ## NEXT STEP:
 
-After user selects [C] to continue, load `./step-02-context.md` to analyze the project context and begin architectural decision making.
+After user selects [C] to continue, only after ensuring all the template output has been created, then load `./step-02-context.md` to analyze the project context and begin architectural decision making.
 
 Remember: Do NOT proceed to step-02 until user explicitly selects [C] from the menu and setup is confirmed!

package/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-01b-continue.md

@@ -11,6 +11,7 @@
 - 💬 FOCUS on understanding current state and getting user confirmation
 - 🚪 HANDLE workflow resumption smoothly and transparently
 - ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-02-context.md

@@ -11,6 +11,7 @@
 - 💬 FOCUS on understanding project scope and requirements for architecture
 - 🎯 ANALYZE loaded documents, don't assume or generate requirements
 - ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 
@@ -30,7 +31,7 @@ This step will generate content and present choices:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
+- When 'A' selected: Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
 - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding
@@ -169,7 +170,7 @@ Show the generated content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current context analysis
+- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current context analysis
 - Process the enhanced architectural insights that come back
 - Ask user: "Accept these enhancements to the project context analysis? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -185,7 +186,7 @@ Show the generated content and present choices:
 
 #### If 'C' (Continue):
 
-- Append the final content to `{output_folder}/architecture.md`
+- Append the final content to `{planning_artifacts}/architecture.md`
 - Update frontmatter: `stepsCompleted: [1, 2]`
 - Load `./step-03-starter.md`
 

package/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-03-starter.md

@@ -10,6 +10,7 @@
 - ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
 - 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete architecture
 - 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 
@@ -30,7 +31,7 @@ This step will generate content and present choices:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
+- When 'A' selected: Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
 - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding
@@ -276,7 +277,7 @@ Show the generated content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with current starter analysis
+- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with current starter analysis
 - Process enhanced insights about starter options or custom approaches
 - Ask user: "Accept these changes to the starter template evaluation? (y/n)"
 - If yes: Update content, then return to A/P/C menu
@@ -292,7 +293,7 @@ Show the generated content and present choices:
 
 #### If 'C' (Continue):
 
-- Append the final content to `{output_folder}/architecture.md`
+- Append the final content to `{planning_artifacts}/architecture.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3]`
 - Load `./step-04-decisions.md`
 

package/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-04-decisions.md

@@ -11,6 +11,7 @@
 - 💬 FOCUS on making critical architectural decisions collaboratively
 - 🌐 ALWAYS search the web to verify current technology versions
 - ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 
@@ -31,7 +32,7 @@ This step will generate content and present choices for each decision category:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
+- When 'A' selected: Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
 - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding
@@ -263,7 +264,7 @@ Show the generated decisions content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with specific decision categories
+- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with specific decision categories
 - Process enhanced insights about particular decisions
 - Ask user: "Accept these enhancements to the architectural decisions? (y/n)"
 - If yes: Update content, then return to A/P/C menu
@@ -279,7 +280,7 @@ Show the generated decisions content and present choices:
 
 #### If 'C' (Continue):
 
-- Append the final content to `{output_folder}/architecture.md`
+- Append the final content to `{planning_artifacts}/architecture.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
 - Load `./step-05-patterns.md`
 

package/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-05-patterns.md

@@ -11,6 +11,7 @@
 - 💬 FOCUS on patterns that prevent AI agent implementation conflicts
 - 🎯 EMPHASIZE what agents could decide DIFFERENTLY if not specified
 - ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 
@@ -31,7 +32,7 @@ This step will generate content and present choices:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
+- When 'A' selected: Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
 - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding
@@ -304,7 +305,7 @@ Show the generated patterns content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with current patterns
+- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with current patterns
 - Process enhanced consistency rules that come back
 - Ask user: "Accept these additional pattern refinements? (y/n)"
 - If yes: Update content, then return to A/P/C menu
@@ -320,7 +321,7 @@ Show the generated patterns content and present choices:
 
 #### If 'C' (Continue):
 
-- Append the final content to `{output_folder}/architecture.md`
+- Append the final content to `{planning_artifacts}/architecture.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
 - Load `./step-06-structure.md`
 

package/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-06-structure.md

@@ -11,6 +11,7 @@
 - 💬 FOCUS on defining complete project structure and clear boundaries
 - 🗺️ MAP requirements/epics to architectural components
 - ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 
@@ -31,7 +32,7 @@ This step will generate content and present choices:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
+- When 'A' selected: Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
 - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding
@@ -324,7 +325,7 @@ Show the generated project structure content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with current project structure
+- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with current project structure
 - Process enhanced organizational insights that come back
 - Ask user: "Accept these changes to the project structure? (y/n)"
 - If yes: Update content, then return to A/P/C menu
@@ -340,7 +341,7 @@ Show the generated project structure content and present choices:
 
 #### If 'C' (Continue):
 
-- Append the final content to `{output_folder}/architecture.md`
+- Append the final content to `{planning_artifacts}/architecture.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6]`
 - Load `./step-07-validation.md`
 

package/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-07-validation.md

@@ -11,6 +11,7 @@
 - 💬 FOCUS on validating architectural coherence and completeness
 - ✅ VALIDATE all requirements are covered by architectural decisions
 - ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 
@@ -31,7 +32,7 @@ This step will generate content and present choices:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
+- When 'A' selected: Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
 - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding
@@ -304,7 +305,7 @@ Show the validation results and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with validation issues
+- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with validation issues
 - Process enhanced solutions for complex concerns
 - Ask user: "Accept these architectural improvements? (y/n)"
 - If yes: Update content, then return to A/P/C menu
@@ -320,7 +321,7 @@ Show the validation results and present choices:
 
 #### If 'C' (Continue):
 
-- Append the final content to `{output_folder}/architecture.md`
+- Append the final content to `{planning_artifacts}/architecture.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6, 7]`
 - Load `./step-08-complete.md`
 

package/src/modules/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md

@@ -11,6 +11,7 @@
 - 💬 FOCUS on successful workflow completion and implementation handoff
 - 🎯 PROVIDE clear next steps for implementation phase
 - ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 
@@ -116,7 +117,7 @@ Provide specific next steps for implementation:
 
 **Immediate Next Steps:**
 
-1. **Review the complete architecture document** at `{output_folder}/architecture.md`
+1. **Review the complete architecture document** at `{planning_artifacts}/architecture.md`
 2. **Begin with project initialization** using the starter template command documented
 3. **Create first implementation story** for project setup
 4. **Start implementing user stories** following the architectural decisions
@@ -151,7 +152,7 @@ Prepare the final content to append to the document:
 **Architecture Decision Workflow:** COMPLETED ✅
 **Total Steps Completed:** 8
 **Date Completed:** {{current_date}}
-**Document Location:** {output_folder}/architecture.md
+**Document Location:** {planning_artifacts}/architecture.md
 
 ### Final Architecture Deliverables
 
@@ -243,15 +244,15 @@ The chosen starter template and architectural patterns provide a production-read
 
 **Save Final Document:**
 
-- Ensure all content is properly appended to `{output_folder}/architecture.md`
+- Ensure all content is properly appended to `{planning_artifacts}/architecture.md`
 - Update frontmatter with completion status
 - Verify document is complete and coherent
 
 **Workflow Status Update:**
 If not in standalone mode, update workflow status:
 
-- Load `{output_folder}/bmm-workflow-status.yaml`
-- Update workflow_status["create-architecture"] = "{output_folder}/architecture.md"
+- Load `{planning_artifacts}/bmm-workflow-status.yaml`
+- Update workflow_status["create-architecture"] = "{planning_artifacts}/architecture.md"
 - Save file with all structure and comments preserved
 
 ### 6. Present Completion to User
@@ -268,7 +269,7 @@ Your architecture for {{project_name}} is comprehensive, validated, and ready fo
 - Implementation guidance for the development phase
 
 **📍 Where to find it:**
-`{output_folder}/architecture.md`
+`{planning_artifacts}/architecture.md`
 
 **🚀 What's next:**
 

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

@@ -33,6 +33,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 - `project_name`, `output_folder`, `planning_artifacts`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`
 - `date` as system-generated current datetime
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Paths
 

package/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-01-validate-prerequisites.md

@@ -13,7 +13,7 @@ outputFile: '{planning_artifacts}/epics.md'
 epicsTemplate: '{workflow_path}/templates/epics-template.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 
 # Template References
@@ -34,6 +34,7 @@ To validate that all required input documents exist and extract all requirements
 - 📖 CRITICAL: Read the complete step file before taking any action
 - 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
 - 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 
@@ -90,11 +91,11 @@ Search for required documents using these patterns (sharded means a large docume
 1. `{planning_artifacts}/*ux*.md` (whole document)
 2. `{planning_artifacts}/*ux*/index.md` (sharded version)
 
-Before proceeding, Ask the user if there are any other documents, or if what you have found is all there is [Yes/No]. Wait for user confirmation. Once confirmed, create the {outputFile} from the {epicsTemplate} and in the front matter list the files in the array of `inputDocuments: []`.
+Before proceeding, Ask the user if there are any other documents to include for analysis, and if anything found should be excluded. Wait for user confirmation. Once confirmed, create the {outputFile} from the {epicsTemplate} and in the front matter list the files in the array of `inputDocuments: []`.
 
 ### 3. Extract Functional Requirements (FRs)
 
-From the PRD document (full or sharded), extract ALL functional requirements:
+From the PRD document (full or sharded), read then entire document and extract ALL functional requirements:
 
 **Extraction Method:**
 

package/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-02-design-epics.md

@@ -12,7 +12,7 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{planning_artifacts}/epics.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 
 # Template References
@@ -33,6 +33,7 @@ To design and get approval for the epics_list that will organize all requirement
 - 📖 CRITICAL: Read the complete step file before taking any action
 - 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
 - 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

package/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-03-create-stories.md

@@ -12,7 +12,7 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{planning_artifacts}/epics.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 
 # Template References
@@ -33,6 +33,7 @@ To generate all epics with their stories based on the approved epics_list, follo
 - 📖 CRITICAL: Read the complete step file before taking any action
 - 🔄 CRITICAL: Process epics sequentially
 - 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

package/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/steps/step-04-final-validation.md

@@ -11,7 +11,7 @@ workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{planning_artifacts}/epics.md'
 
 # Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
 partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 
 # Template References
@@ -32,6 +32,7 @@ To validate complete coverage of all requirements and ensure stories are ready f
 - 📖 CRITICAL: Read the complete step file before taking any action
 - 🔄 CRITICAL: Process validation sequentially without skipping
 - 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Role Reinforcement:
 

package/src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md

@@ -52,6 +52,7 @@ This uses **step-file architecture** for disciplined execution:
 Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve:
 
 - `project_name`, `output_folder`, `planning_artifacts`, `user_name`, `communication_language`, `document_output_language`
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### 2. First Step EXECUTION
 

package/src/modules/bmm/workflows/4-implementation/code-review/workflow.yaml

@@ -10,9 +10,10 @@ 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
+planning_artifacts: "{config_source}:planning_artifacts"
 implementation_artifacts: "{config_source}:implementation_artifacts"
 output_folder: "{implementation_artifacts}"
-sprint_status: "{implementation_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
+sprint_status: "{implementation_artifacts}/sprint-status.yaml"
 
 # Workflow components
 installed_path: "{project-root}/_bmad/bmm/workflows/4-implementation/code-review"
@@ -31,24 +32,20 @@ variables:
 input_file_patterns:
   architecture:
     description: "System architecture for review context"
-    whole: "{output_folder}/*architecture*.md"
-    sharded: "{output_folder}/*architecture*/*.md"
+    whole: "{planning_artifacts}/*architecture*.md"
+    sharded: "{planning_artifacts}/*architecture*/*.md"
     load_strategy: "FULL_LOAD"
   ux_design:
     description: "UX design specification (if UI review)"
-    whole: "{output_folder}/*ux*.md"
-    sharded: "{output_folder}/*ux*/*.md"
+    whole: "{planning_artifacts}/*ux*.md"
+    sharded: "{planning_artifacts}/*ux*/*.md"
     load_strategy: "FULL_LOAD"
   epics:
     description: "Epic containing story being reviewed"
-    whole: "{output_folder}/*epic*.md"
-    sharded_index: "{output_folder}/*epic*/index.md"
-    sharded_single: "{output_folder}/*epic*/epic-{{epic_num}}.md"
+    whole: "{planning_artifacts}/*epic*.md"
+    sharded_index: "{planning_artifacts}/*epic*/index.md"
+    sharded_single: "{planning_artifacts}/*epic*/epic-{{epic_num}}.md"
     load_strategy: "SELECTIVE_LOAD"
-  document_project:
-    description: "Brownfield project documentation (optional)"
-    sharded: "{output_folder}/index.md"
-    load_strategy: "INDEX_GUIDED"
 
 standalone: true
 web_bundle: false

package/src/modules/bmm/workflows/4-implementation/create-story/workflow.yaml

@@ -7,6 +7,7 @@ config_source: "{project-root}/_bmad/bmm/config.yaml"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 date: system-generated
+planning_artifacts: "{config_source}:planning_artifacts"
 implementation_artifacts: "{config_source}:implementation_artifacts"
 output_folder: "{implementation_artifacts}"
 story_dir: "{implementation_artifacts}"
@@ -20,10 +21,10 @@ validation: "{installed_path}/checklist.md"
 # Variables and inputs
 variables:
   sprint_status: "{implementation_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml" # Primary source for story tracking
-  epics_file: "{output_folder}/epics.md" # Enhanced epics+stories with BDD and source hints
-  prd_file: "{output_folder}/PRD.md" # Fallback for requirements (if not in epics file)
-  architecture_file: "{output_folder}/architecture.md" # Fallback for constraints (if not in epics file)
-  ux_file: "{output_folder}/ux.md" # Fallback for UX requirements (if not in epics file)
+  epics_file: "{planning_artifacts}/epics.md" # Enhanced epics+stories with BDD and source hints
+  prd_file: "{planning_artifacts}/prd.md" # Fallback for requirements (if not in epics file)
+  architecture_file: "{planning_artifacts}/architecture.md" # Fallback for constraints (if not in epics file)
+  ux_file: "{planning_artifacts}/*ux*.md" # Fallback for UX requirements (if not in epics file)
   story_title: "" # Will be elicited if not derivable
 
 # Project context
@@ -36,23 +37,23 @@ default_output_file: "{story_dir}/{{story_key}}.md"
 input_file_patterns:
   prd:
     description: "PRD (fallback - epics file should have most content)"
-    whole: "{output_folder}/*prd*.md"
-    sharded: "{output_folder}/*prd*/*.md"
+    whole: "{planning_artifacts}/*prd*.md"
+    sharded: "{planning_artifacts}/*prd*/*.md"
     load_strategy: "SELECTIVE_LOAD" # Only load if needed
   architecture:
     description: "Architecture (fallback - epics file should have relevant sections)"
-    whole: "{output_folder}/*architecture*.md"
-    sharded: "{output_folder}/*architecture*/*.md"
+    whole: "{planning_artifacts}/*architecture*.md"
+    sharded: "{planning_artifacts}/*architecture*/*.md"
     load_strategy: "SELECTIVE_LOAD" # Only load if needed
   ux:
     description: "UX design (fallback - epics file should have relevant sections)"
-    whole: "{output_folder}/*ux*.md"
-    sharded: "{output_folder}/*ux*/*.md"
+    whole: "{planning_artifacts}/*ux*.md"
+    sharded: "{planning_artifacts}/*ux*/*.md"
     load_strategy: "SELECTIVE_LOAD" # Only load if needed
   epics:
     description: "Enhanced epics+stories file with BDD and source hints"
-    whole: "{output_folder}/*epic*.md"
-    sharded: "{output_folder}/*epic*/*.md"
+    whole: "{planning_artifacts}/*epic*.md"
+    sharded: "{planning_artifacts}/*epic*/*.md"
     load_strategy: "SELECTIVE_LOAD" # Only load needed epic
 
 standalone: true

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

@@ -365,16 +365,16 @@ Alice (Product Owner): "Good thinking - helps us connect what we learned to what
 <action>Attempt to load next epic using selective loading strategy:</action>
 
 **Try sharded first (more specific):**
-<action>Check if file exists: {output_folder}/epic\*/epic-{{next_epic_num}}.md</action>
+<action>Check if file exists: {planning_artifacts}/epic\*/epic-{{next_epic_num}}.md</action>
 
 <check if="sharded epic file found">
-  <action>Load {output_folder}/*epic*/epic-{{next_epic_num}}.md</action>
+  <action>Load {planning_artifacts}/*epic*/epic-{{next_epic_num}}.md</action>
   <action>Set {{next_epic_source}} = "sharded"</action>
 </check>
 
 **Fallback to whole document:**
 <check if="sharded epic not found">
-<action>Check if file exists: {output_folder}/epic\*.md</action>
+<action>Check if file exists: {planning_artifacts}/epic\*.md</action>
 
   <check if="whole epic file found">
     <action>Load entire epics document</action>