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

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

@@ -25,8 +25,6 @@ web_bundle: true
 - Detailed research sections with proper citations
 - Executive summary and conclusions
 
----
-
 ## WORKFLOW ARCHITECTURE
 
 This uses **micro-file architecture** with **routing-based discovery**:
@@ -34,9 +32,7 @@ This uses **micro-file architecture** with **routing-based discovery**:
 - Each research type has its own step folder
 - Step 01 discovers research type and routes to appropriate sub-workflow
 - Sequential progression within each research type
-- Document state tracked in frontmatter
-
----
+- Document state tracked in output frontmatter
 
 ## INITIALIZATION
 
@@ -44,25 +40,20 @@ This uses **micro-file architecture** with **routing-based discovery**:
 
 Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 
-- `project_name`, `output_folder`, `user_name`
+- `project_name`, `output_folder`, , `planning_artifacts`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`
 - `date` as a system-generated value
-- `enable_web_research = true` (web research is default behavior)
 
 ### Paths
 
 - `installed_path` = `{project-root}/_bmad/bmm/workflows/1-analysis/research`
 - `template_path` = `{installed_path}/research.template.md`
-- `default_output_file` = `{output_folder}/analysis/research/{{research_type}}-{{topic}}-research-{{date}}.md` (dynamic based on research type)
-
----
+- `default_output_file` = `{planning_artifacts}/research/{{research_type}}-{{topic}}-research-{{date}}.md` (dynamic based on research type)
 
 ## PREREQUISITE
 
 **⛔ Web search required.** If unavailable, abort and tell the user.
 
----
-
 ## RESEARCH BEHAVIOR
 
 ### Web Research Standards
@@ -81,9 +72,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 - **Critical Claims**: Market size, growth rates, competitive data need verification
 - **Fact Checking**: Apply fact-checking to critical data points
 
----
-
-## EXECUTION
+## Implementation Instructions
 
 Execute research type discovery and routing:
 
@@ -156,49 +145,29 @@ After understanding the research topic and goals, identify the most appropriate
 
 ### Research Type Routing
 
-Based on user selection, route to appropriate sub-workflow with the discovered topic:
+<critical>Based on user selection, route to appropriate sub-workflow with the discovered topic using the following IF block sets of instructions.</critical>
 
 #### If Market Research:
 
 - Set `research_type = "market"`
 - Set `research_topic = [discovered topic from discussion]`
-- Set output file: `{output_folder}/analysis/research/market-{{research_topic}}-research-{{date}}.md`
+- Create the starter output file: `{planning_artifacts}/research/market-{{research_topic}}-research-{{date}}.md` with exact copy of the ./research.template.md contents
 - Load: `./market-steps/step-01-init.md` with topic context
 
 #### If Domain Research:
 
 - Set `research_type = "domain"`
 - Set `research_topic = [discovered topic from discussion]`
-- Set output file: `{output_folder}/analysis/research/domain-{{research_topic}}-research-{{date}}.md`
+- Create the starter output file: `{planning_artifacts}/research/domain-{{research_topic}}-research-{{date}}.md` with exact copy of the ./research.template.md contents
 - Load: `./domain-steps/step-01-init.md` with topic context
 
 #### If Technical Research:
 
 - Set `research_type = "technical"`
 - Set `research_topic = [discovered topic from discussion]`
-- Set output file: `{output_folder}/analysis/research/technical-{{research_topic}}-research-{{date}}.md`
+- Create the starter output file: `{planning_artifacts}/research/technical-{{research_topic}}-research-{{date}}.md` with exact copy of the ./research.template.md contents
 - Load: `./technical-steps/step-01-init.md` with topic context
 
 **Important**: The discovered topic from the collaborative discussion should be passed to the research initialization steps, so they don't need to ask "What do you want to research?" again - they can focus on refining the scope for their specific research type.
 
-### Document Initialization
-
-Create research document with proper metadata:
-
-```yaml
----
-stepsCompleted: [1]
-inputDocuments: []
-workflowType: 'research'
-lastStep: 1
-research_type: '{{research_type}}'
-research_topic: '{{research_topic}}'
-research_goals: '{{research_goals}}'
-user_name: '{{user_name}}'
-date: '{{date}}'
-web_research_enabled: true
-source_verification: true
----
-```
-
 **Note:** All research workflows require web search for current data and source verification.

package/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-01-init.md

@@ -35,7 +35,7 @@ Initialize the UX design workflow by detecting continuation state and setting up
 
 First, check if the output document already exists:
 
-- Look for file at `{output_folder}/ux-design-specification.md`
+- Look for file at `{planning_artifacts}/ux-design-specification.md`
 - If exists, read the complete file including frontmatter
 - If not exists, this is a fresh workflow
 
@@ -57,23 +57,23 @@ Discover and load context documents using smart discovery:
 
 **PRD (Priority: Analysis → Main → Sharded → Whole):**
 
-1. Check analysis folder: `{output_folder}/analysis/*prd*.md`
-2. If no analysis files: Try main folder: `{output_folder}/*prd*.md`
-3. If no main files: Check for sharded PRD folder: `{output_folder}/*prd*/**/*.md`
+1. Check analysis folder: `{planning_artifacts}/*prd*.md`
+2. If no files: Try main folder: `{output_folder}/*prd*.md`
+3. If no main files: Check for sharded PRD folder: `**/*prd*/**/*.md`
 4. If sharded folder exists: Load EVERY file in that folder completely for UX context
 5. Add discovered files to `inputDocuments` frontmatter
 
 **Product Brief (Priority: Analysis → Main → Sharded → Whole):**
 
-1. Check analysis folder: `{output_folder}/analysis/*brief*.md`
+1. Check analysis folder: `{planning_artifacts}/*brief*.md`
 2. If no analysis files: Try main folder: `{output_folder}/*brief*.md`
-3. If no main files: Check for sharded brief folder: `{output_folder}/*brief*/**/*.md`
+3. If no main files: Check for sharded brief folder: `**/*brief*/**/*.md`
 4. If sharded folder exists: Load EVERY file in that folder completely
 5. Add discovered files to `inputDocuments` frontmatter
 
 **Research Documents (Priority: Analysis → Main → Sharded → Whole):**
 
-1. Check analysis folder: `{output_folder}/analysis/research/*research*.md`
+1. Check analysis folder: `{planning_artifacts}/research/*research*.md`
 2. If no analysis files: Try main folder: `{output_folder}/*research*.md`
 3. If no main files: Check for sharded research folder: `{output_folder}/*research*/**/*.md`
 4. Load useful research files completely
@@ -92,7 +92,7 @@ Discover and load context documents using smart discovery:
 
 #### B. Create Initial Document
 
-Copy the template from `{installed_path}/ux-design-template.md` to `{output_folder}/ux-design-specification.md`
+Copy the template from `{installed_path}/ux-design-template.md` to `{planning_artifacts}/ux-design-specification.md`
 Initialize frontmatter with:
 
 ```yaml
@@ -113,7 +113,7 @@ Complete setup and report to user:
 
 **Document Setup:**
 
-- Created: `{output_folder}/ux-design-specification.md` from template
+- Created: `{planning_artifacts}/ux-design-specification.md` from template
 - Initialized frontmatter with workflow state
 
 **Input Documents Discovered:**
@@ -132,6 +132,12 @@ Do you have any other documents you'd like me to include, or shall we continue t
 
 [C] Continue to UX discovery"
 
+## NEXT STEP:
+
+After user selects [C] to continue, load `./step-02-discovery.md` to begin the UX discovery phase.
+
+Remember: Do NOT proceed to step-02 until output file has been updated and user explicitly selects [C] to continue!
+
 ## SUCCESS METRICS:
 
 ✅ Existing workflow detected and handed off to step-01b correctly
@@ -151,9 +157,3 @@ Do you have any other documents you'd like me to include, or shall we continue t
 ❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
 ❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
 ❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
-
-## NEXT STEP:
-
-After user selects [C] to continue, load `./step-02-discovery.md` to begin the UX discovery phase.
-
-Remember: Do NOT proceed to step-02 until user explicitly selects [C] to continue!

package/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-02-discovery.md

@@ -29,8 +29,8 @@ This step will generate content and present choices:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -146,37 +146,19 @@ Show the generated project understanding content and present choices:
 [Show the complete markdown content from step 5]
 
 **What would you like to do?**
-[A] Advanced Elicitation - Let's dive deeper into project understanding
-[P] Party Mode - Bring different perspectives on user needs and challenges
 [C] Continue - Save this to the document and move to core experience definition"
 
 ### 7. Handle Menu Selection
 
-#### If 'A' (Advanced Elicitation):
-
-- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current project understanding content
-- Process the enhanced project insights that come back
-- Ask user: "Accept these improvements to the project understanding? (y/n)"
-- If yes: Update content with improvements, then return to A/P/C menu
-- If no: Keep original content, then return to A/P/C menu
-
-#### If 'P' (Party Mode):
-
-- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current project understanding
-- Process the collaborative insights and different perspectives that come back
-- Ask user: "Accept these changes to the project understanding? (y/n)"
-- If yes: Update content with improvements, then return to A/P/C menu
-- If no: Keep original content, then return to A/P/C menu
-
 #### If 'C' (Continue):
 
-- Append the final content to `{output_folder}/ux-design-specification.md`
+- Append the final content to `{planning_artifacts}/ux-design-specification.md`
 - Update frontmatter: `stepsCompleted: [1, 2]`
 - Load `./step-03-core-experience.md`
 
 ## APPEND TO DOCUMENT:
 
-When user selects 'C', append the content directly to the document using the structure from step 5.
+When user selects 'C', append the content directly to the document. Only after the content is saved to document, load `./step-03-core-experience.md` and execute the instructions.
 
 ## SUCCESS METRICS:
 
@@ -204,6 +186,4 @@ When user selects 'C', append the content directly to the document using the str
 
 ## NEXT STEP:
 
-After user selects 'C' and content is saved to document, load `./step-03-core-experience.md` to define the core user experience.
-
-Remember: Do NOT proceed to step-03 until user explicitly selects 'C' from the A/P/C menu and content is saved!
+Remember: Do NOT proceed to step-03 until user explicitly selects 'C' from the menu and content is saved!

package/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-03-core-experience.md

@@ -29,8 +29,8 @@ This step will generate content and present choices:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -160,7 +160,7 @@ Show the generated core experience content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current core experience content
+- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current core experience content
 - Process the enhanced experience insights that come back
 - Ask user: "Accept these improvements to the core experience definition? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -168,7 +168,7 @@ Show the generated core experience content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current core experience definition
+- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current core experience definition
 - Process the collaborative experience improvements that come back
 - Ask user: "Accept these changes to the core experience definition? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -176,7 +176,7 @@ Show the generated core experience content and present choices:
 
 #### If 'C' (Continue):
 
-- Append the final content to `{output_folder}/ux-design-specification.md`
+- Append the final content to `{planning_artifacts}/ux-design-specification.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3]`
 - Load `./step-04-emotional-response.md`
 

package/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-04-emotional-response.md

@@ -29,8 +29,8 @@ This step will generate content and present choices:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -163,7 +163,7 @@ Show the generated emotional response content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current emotional response content
+- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current emotional response content
 - Process the enhanced emotional insights that come back
 - Ask user: "Accept these improvements to the emotional response definition? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -171,7 +171,7 @@ Show the generated emotional response content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current emotional response definition
+- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current emotional response definition
 - Process the collaborative emotional insights that come back
 - Ask user: "Accept these changes to the emotional response definition? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -179,7 +179,7 @@ Show the generated emotional response content and present choices:
 
 #### If 'C' (Continue):
 
-- Append the final content to `{output_folder}/ux-design-specification.md`
+- Append the final content to `{planning_artifacts}/ux-design-specification.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
 - Load `./step-05-inspiration.md`
 

package/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-05-inspiration.md

@@ -29,8 +29,8 @@ This step will generate content and present choices:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -178,7 +178,7 @@ Show the generated inspiration analysis content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current inspiration analysis content
+- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current inspiration analysis content
 - Process the enhanced pattern insights that come back
 - Ask user: "Accept these improvements to the inspiration analysis? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -186,7 +186,7 @@ Show the generated inspiration analysis content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current inspiration analysis
+- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current inspiration analysis
 - Process the collaborative pattern insights that come back
 - Ask user: "Accept these changes to the inspiration analysis? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -194,9 +194,9 @@ Show the generated inspiration analysis content and present choices:
 
 #### If 'C' (Continue):
 
-- Append the final content to `{output_folder}/ux-design-specification.md`
+- Append the final content to `{planning_artifacts}/ux-design-specification.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
-- Load `./step-06-design-system.md`
+- Load and execute`./step-06-design-system.md`
 
 ## APPEND TO DOCUMENT:
 

package/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-06-design-system.md

@@ -29,8 +29,8 @@ This step will generate content and present choices:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -196,7 +196,7 @@ Show the generated design system content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current design system content
+- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current design system content
 - Process the enhanced design system insights that come back
 - Ask user: "Accept these improvements to the design system decision? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -204,7 +204,7 @@ Show the generated design system content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current design system choice
+- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current design system choice
 - Process the collaborative design system insights that come back
 - Ask user: "Accept these changes to the design system decision? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -212,7 +212,7 @@ Show the generated design system content and present choices:
 
 #### If 'C' (Continue):
 
-- Append the final content to `{output_folder}/ux-design-specification.md`
+- Append the final content to `{planning_artifacts}/ux-design-specification.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6]`
 - Load `./step-07-defining-experience.md`
 

package/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-07-defining-experience.md

@@ -29,8 +29,8 @@ This step will generate content and present choices:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -198,7 +198,7 @@ Show the generated defining experience content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current defining experience content
+- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current defining experience content
 - Process the enhanced experience insights that come back
 - Ask user: "Accept these improvements to the defining experience? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -206,7 +206,7 @@ Show the generated defining experience content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current defining experience
+- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current defining experience
 - Process the collaborative experience insights that come back
 - Ask user: "Accept these changes to the defining experience? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -214,7 +214,7 @@ Show the generated defining experience content and present choices:
 
 #### If 'C' (Continue):
 
-- Append the final content to `{output_folder}/ux-design-specification.md`
+- Append the final content to `{planning_artifacts}/ux-design-specification.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6, 7]`
 - Load `./step-08-visual-foundation.md`
 

package/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-08-visual-foundation.md

@@ -29,8 +29,8 @@ This step will generate content and present choices:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -168,7 +168,7 @@ Show the generated visual foundation content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current visual foundation content
+- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current visual foundation content
 - Process the enhanced visual insights that come back
 - Ask user: "Accept these improvements to the visual foundation? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -176,7 +176,7 @@ Show the generated visual foundation content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current visual foundation
+- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current visual foundation
 - Process the collaborative visual insights that come back
 - Ask user: "Accept these changes to the visual foundation? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -184,7 +184,7 @@ Show the generated visual foundation content and present choices:
 
 #### If 'C' (Continue):
 
-- Append the final content to `{output_folder}/ux-design-specification.md`
+- Append the final content to `{planning_artifacts}/ux-design-specification.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8]`
 - Load `./step-09-design-directions.md`
 

package/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-09-design-directions.md

@@ -29,8 +29,8 @@ This step will generate content and present choices:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -168,7 +168,7 @@ Show the generated design direction content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current design direction content
+- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current design direction content
 - Process the enhanced design insights that come back
 - Ask user: "Accept these improvements to the design direction? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -176,7 +176,7 @@ Show the generated design direction content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current design direction
+- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current design direction
 - Process the collaborative design insights that come back
 - Ask user: "Accept these changes to the design direction? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -184,7 +184,7 @@ Show the generated design direction content and present choices:
 
 #### If 'C' (Continue):
 
-- Append the final content to `{output_folder}/ux-design-specification.md`
+- Append the final content to `{planning_artifacts}/ux-design-specification.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8, 9]`
 - Load `./step-10-user-journeys.md`
 

package/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-10-user-journeys.md

@@ -29,8 +29,8 @@ This step will generate content and present choices:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -186,7 +186,7 @@ Show the generated user journey content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current user journey content
+- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current user journey content
 - Process the enhanced journey insights that come back
 - Ask user: "Accept these improvements to the user journeys? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -194,7 +194,7 @@ Show the generated user journey content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current user journeys
+- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current user journeys
 - Process the collaborative journey insights that come back
 - Ask user: "Accept these changes to the user journeys? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -202,7 +202,7 @@ Show the generated user journey content and present choices:
 
 #### If 'C' (Continue):
 
-- Append the final content to `{output_folder}/ux-design-specification.md`
+- Append the final content to `{planning_artifacts}/ux-design-specification.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8, 9, 10]`
 - Load `./step-11-component-strategy.md`
 

package/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-11-component-strategy.md

@@ -29,8 +29,8 @@ This step will generate content and present choices:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -192,7 +192,7 @@ Show the generated component strategy content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current component strategy content
+- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current component strategy content
 - Process the enhanced component insights that come back
 - Ask user: "Accept these improvements to the component strategy? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -200,7 +200,7 @@ Show the generated component strategy content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current component strategy
+- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current component strategy
 - Process the collaborative component insights that come back
 - Ask user: "Accept these changes to the component strategy? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -208,7 +208,7 @@ Show the generated component strategy content and present choices:
 
 #### If 'C' (Continue):
 
-- Append the final content to `{output_folder}/ux-design-specification.md`
+- Append the final content to `{planning_artifacts}/ux-design-specification.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11]`
 - Load `./step-12-ux-patterns.md`
 

package/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-12-ux-patterns.md

@@ -29,8 +29,8 @@ This step will generate content and present choices:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md
+- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
+- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -181,7 +181,7 @@ Show the generated UX patterns content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current UX patterns content
+- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current UX patterns content
 - Process the enhanced pattern insights that come back
 - Ask user: "Accept these improvements to the UX patterns? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -189,7 +189,7 @@ Show the generated UX patterns content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current UX patterns
+- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current UX patterns
 - Process the collaborative pattern insights that come back
 - Ask user: "Accept these changes to the UX patterns? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -197,7 +197,7 @@ Show the generated UX patterns content and present choices:
 
 #### If 'C' (Continue):
 
-- Append the final content to `{output_folder}/ux-design-specification.md`
+- Append the final content to `{planning_artifacts}/ux-design-specification.md`
 - Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12]`
 - Load `./step-13-responsive-accessibility.md`