bmad-method 6.0.0-alpha.21 → 6.0.0-alpha.23

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

@@ -1,15 +1,70 @@
 ---
-name: create-prd
-description: Creates a comprehensive PRD through collaborative step-by-step discovery between two product managers working as peers.
+name: prd
+description: PRD tri-modal workflow - Create, Validate, or Edit comprehensive PRDs
 main_config: '{project-root}/_bmad/bmm/config.yaml'
+nextStep: './steps-c/step-01-init.md'
+validateWorkflow: './steps-v/step-v-01-discovery.md'
+editWorkflow: './steps-e/step-e-01-discovery.md'
 web_bundle: true
 ---
 
-# PRD Workflow
+# PRD Workflow (Tri-Modal)
 
-**Goal:** Create comprehensive PRDs through collaborative step-by-step discovery between two product managers working as peers.
+**Goal:** Create, Validate, or Edit comprehensive PRDs through structured workflows.
 
-**Your Role:** You are a product-focused PM facilitator collaborating with an expert peer. This is a partnership, not a client-vendor relationship. You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision. Work together as equals. You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
+**Your Role:**
+- **Create Mode:** Product-focused PM facilitator collaborating with an expert peer
+- **Validate Mode:** Validation Architect and Quality Assurance Specialist
+- **Edit Mode:** PRD improvement specialist
+
+You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
+
+---
+
+## MODE DETERMINATION
+
+### Detect Workflow Mode
+
+Determine which mode to invoke based on:
+
+1. **Command/Invocation:**
+   - "create prd" or "new prd" → Create mode
+   - "validate prd" or "check prd" → Validate mode
+   - "edit prd" or "improve prd" → Edit mode
+
+2. **Context Detection:**
+   - If invoked with -c flag → Create mode
+   - If invoked with -v flag → Validate mode
+   - If invoked with -e flag → Edit mode
+
+3. **Menu Selection (if unclear):**
+
+If mode cannot be determined from invocation:
+"**PRD Workflow - Select Mode:**
+
+**[C] Create** - Create a new PRD from scratch
+**[V] Validate** - Validate an existing PRD against BMAD standards
+**[E] Edit** - Improve an existing PRD
+
+Which mode would you like?"
+
+Wait for user selection.
+
+### Route to Appropriate Workflow
+
+**IF Create Mode:**
+"**Create Mode: Creating a new PRD from scratch.**"
+Load, read entire file, then execute: `{nextStep}` (steps-c/step-01-init.md)
+
+**IF Validate Mode:**
+"**Validate Mode: Validating an existing PRD against BMAD standards.**"
+Prompt for PRD path: "Which PRD would you like to validate? Please provide the path to the PRD.md file."
+Then load, read entire file, and execute: `{validateWorkflow}` (steps-v/step-v-01-discovery.md)
+
+**IF Edit Mode:**
+"**Edit Mode: Improving an existing PRD.**"
+Prompt for PRD path: "Which PRD would you like to edit? Please provide the path to the PRD.md file."
+Then load, read entire file, and execute: `{editWorkflow}` (steps-e/step-e-01-discovery.md)
 
 ---
 
@@ -48,7 +103,27 @@ This uses **step-file architecture** for disciplined execution:
 
 ## INITIALIZATION SEQUENCE
 
-### 1. Configuration Loading
+### 1. Mode Determination
+
+**Check if mode was specified in the command invocation:**
+
+- If user invoked with "create prd" or "new prd" or "build prd" or "-c" or "--create" → Set mode to **create**
+- If user invoked with "validate prd" or "review prd" or "check prd" or "-v" or "--validate" → Set mode to **validate**
+- If user invoked with "edit prd" or "modify prd" or "improve prd" or "-e" or "--edit" → Set mode to **edit**
+
+**If mode is still unclear, ask user:**
+
+"**PRD Workflow - Select Mode:**
+
+**[C] Create** - Create a new PRD from scratch
+**[V] Validate** - Validate an existing PRD against BMAD standards
+**[E] Edit** - Improve an existing PRD
+
+Which mode would you like?"
+
+Wait for user selection.
+
+### 2. Configuration Loading
 
 Load and read full config from {main_config} and resolve:
 
@@ -56,6 +131,20 @@ Load and read full config from {main_config} and resolve:
 - `communication_language`, `document_output_language`, `user_skill_level`
 - `date` as system-generated current datetime
 
-### 2. First Step EXECUTION
+✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`.
+
+### 3. Route to Appropriate Workflow
+
+**IF mode == create:**
+"**Create Mode: Creating a new PRD from scratch.**"
+Load, read entire file, then execute `{nextStep}` (steps-c/step-01-init.md)
+
+**IF mode == validate:**
+"**Validate Mode: Validating an existing PRD against BMAD standards.**"
+Prompt for PRD path: "Which PRD would you like to validate? Please provide the path to the PRD.md file."
+Then load, read entire file, and execute `{validateWorkflow}` (steps-v/step-v-01-discovery.md)
 
-Load, read the full file and then execute `steps/step-01-init.md` to begin the workflow.
+**IF mode == edit:**
+"**Edit Mode: Improving an existing PRD.**"
+Prompt for PRD path: "Which PRD would you like to edit? Please provide the path to the PRD.md file."
+Then load, read entire file, and execute `{editWorkflow}` (steps-e/step-e-01-discovery.md)

package/src/modules/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-01-document-discovery.md

@@ -6,8 +6,8 @@ description: 'Discover and inventory all project documents, handling duplicates
 workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-readiness'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-01-document-discovery.md'
-nextStepFile: '{workflow_path}/steps/step-02-prd-analysis.md'
+thisStepFile: './step-01-document-discovery.md'
+nextStepFile: './step-02-prd-analysis.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
 templateFile: '{workflow_path}/templates/readiness-report-template.md'
@@ -27,6 +27,7 @@ To discover, inventory, and organize all project documents, identifying duplicat
 - 📖 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/check-implementation-readiness/steps/step-02-prd-analysis.md

@@ -6,8 +6,8 @@ description: 'Read and analyze PRD to extract all FRs and NFRs for coverage vali
 workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-readiness'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-02-prd-analysis.md'
-nextStepFile: '{workflow_path}/steps/step-03-epic-coverage-validation.md'
+thisStepFile: './step-02-prd-analysis.md'
+nextStepFile: './step-03-epic-coverage-validation.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
 epicsFile: '{planning_artifacts}/*epic*.md' # Will be resolved to actual file
@@ -27,6 +27,7 @@ To fully read and analyze the PRD document (whole or sharded) to extract all Fun
 - 📖 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/check-implementation-readiness/steps/step-03-epic-coverage-validation.md

@@ -6,8 +6,8 @@ description: 'Validate that all PRD FRs are covered in epics and stories'
 workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-readiness'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-03-epic-coverage-validation.md'
-nextStepFile: '{workflow_path}/steps/step-04-ux-alignment.md'
+thisStepFile: './step-03-epic-coverage-validation.md'
+nextStepFile: './step-04-ux-alignment.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
 ---
@@ -26,6 +26,7 @@ To validate that all Functional Requirements from the PRD are captured in the ep
 - 📖 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/check-implementation-readiness/steps/step-04-ux-alignment.md

@@ -6,8 +6,8 @@ description: 'Check for UX document and validate alignment with PRD and Architec
 workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-readiness'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-04-ux-alignment.md'
-nextStepFile: '{workflow_path}/steps/step-05-epic-quality-review.md'
+thisStepFile: './step-04-ux-alignment.md'
+nextStepFile: './step-05-epic-quality-review.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
 ---
@@ -26,6 +26,7 @@ To check if UX documentation exists and validate that it aligns with PRD require
 - 📖 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/check-implementation-readiness/steps/step-05-epic-quality-review.md

@@ -6,8 +6,8 @@ description: 'Validate epics and stories against create-epics-and-stories best p
 workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-readiness'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-05-epic-quality-review.md'
-nextStepFile: '{workflow_path}/steps/step-06-final-assessment.md'
+thisStepFile: './step-05-epic-quality-review.md'
+nextStepFile: './step-06-final-assessment.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
 epicsBestPractices: '{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories'
@@ -27,6 +27,7 @@ To validate epics and stories against the best practices defined in create-epics
 - 📖 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/check-implementation-readiness/steps/step-06-final-assessment.md

@@ -6,7 +6,7 @@ description: 'Compile final assessment and polish the readiness report'
 workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-readiness'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-06-final-assessment.md'
+thisStepFile: './step-06-final-assessment.md'
 workflowFile: '{workflow_path}/workflow.md'
 outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
 ---
@@ -25,6 +25,7 @@ To provide a comprehensive summary of all findings and give the report a final p
 - 📖 CRITICAL: Read the complete step file before taking any action
 - 📖 You are at the final step - complete the assessment
 - 📋 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/check-implementation-readiness/workflow.md

@@ -48,7 +48,8 @@ web_bundle: false
 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
 
-Load, read the full file and then execute `{workflow_path}/steps/step-01-document-discovery.md` to begin the workflow.
+Load, read the full file and then execute `./step-01-document-discovery.md` to begin the workflow.

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:
 

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

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

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

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

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

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

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:
 

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

@@ -6,14 +6,14 @@ description: 'Validate required documents exist and extract all requirements for
 workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-01-validate-prerequisites.md'
-nextStepFile: '{workflow_path}/steps/step-02-design-epics.md'
+thisStepFile: './step-01-validate-prerequisites.md'
+nextStepFile: './step-02-design-epics.md'
 workflowFile: '{workflow_path}/workflow.md'
 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,7 +91,7 @@ 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)
 

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

@@ -6,13 +6,13 @@ description: 'Design and approve the epics_list that will organize all requireme
 workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-02-design-epics.md'
-nextStepFile: '{workflow_path}/steps/step-03-create-stories.md'
+thisStepFile: './step-02-design-epics.md'
+nextStepFile: './step-03-create-stories.md'
 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

@@ -6,13 +6,13 @@ description: 'Generate all epics with their stories following the template struc
 workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-03-create-stories.md'
-nextStepFile: '{workflow_path}/steps/step-04-final-validation.md'
+thisStepFile: './step-03-create-stories.md'
+nextStepFile: './step-04-final-validation.md'
 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

@@ -6,12 +6,12 @@ description: 'Validate complete coverage of all requirements and ensure implemen
 workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories'
 
 # File References
-thisStepFile: '{workflow_path}/steps/step-04-final-validation.md'
+thisStepFile: './step-04-final-validation.md'
 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/instructions.xml

@@ -12,6 +12,8 @@
   <critical>Read EVERY file in the File List - verify implementation against story requirements</critical>
   <critical>Tasks marked complete but not done = CRITICAL finding</critical>
   <critical>Acceptance Criteria not implemented = HIGH severity finding</critical>
+  <critical>Do not review files that are not part of the application's source code. Always exclude the _bmad/ and _bmad-output/ folders from the review. Always exclude IDE and CLI configuration folders like .cursor/ and .windsurf/ and .claude/</critical>
+
 
   <step n="1" goal="Load story and discover changes">
     <action>Use provided {{story_path}} or ask user which story file to review</action>

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