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

package/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-13-responsive-accessibility.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
 
@@ -208,7 +208,7 @@ Show the generated responsive and accessibility content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current responsive/accessibility content
+- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current responsive/accessibility content
 - Process the enhanced insights that come back
 - Ask user: "Accept these improvements to the responsive/accessibility strategy? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -216,7 +216,7 @@ Show the generated responsive and accessibility content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current responsive/accessibility strategy
+- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current responsive/accessibility strategy
 - Process the collaborative insights that come back
 - Ask user: "Accept these changes to the responsive/accessibility strategy? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -224,7 +224,7 @@ Show the generated responsive and accessibility 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, 13]`
 - Load `./step-14-complete.md`
 

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

@@ -60,7 +60,7 @@ I've successfully collaborated with you to create a comprehensive UX design spec
 - ✅ UX consistency patterns for common interactions
 - ✅ Responsive design and accessibility strategy
 
-**The complete UX design specification is now available at:** `{output_folder}/ux-design-specification.md`
+**The complete UX design specification is now available at:** `{planning_artifacts}/ux-design-specification.md`
 
 **Supporting Visual Assets:**
 
@@ -221,6 +221,6 @@ This UX design workflow is now complete. The specification serves as the foundat
 
 **Core Deliverables:**
 
-- ✅ UX Design Specification: `{output_folder}/ux-design-specification.md`
+- ✅ UX Design Specification: `{planning_artifacts}/ux-design-specification.md`
 - ✅ Color Themes Visualizer: `{output_folder}/ux-color-themes.html`
 - ✅ Design Directions: `{output_folder}/ux-design-directions.html`

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

@@ -27,7 +27,7 @@ This uses **micro-file architecture** for disciplined execution:
 
 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 system-generated current datetime
 
@@ -35,7 +35,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 
 - `installed_path` = `{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design`
 - `template_path` = `{installed_path}/ux-design-template.md`
-- `default_output_file` = `{output_folder}/ux-design-specification.md`
+- `default_output_file` = `{planning_artifacts}/ux-design-specification.md`
 
 ### Output Files
 
@@ -46,14 +46,12 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 
 Discover context documents for UX context (Priority: Analysis folder first, then main folder, then sharded):
 
-- PRD: `{output_folder}/analysis/*prd*.md` or `{output_folder}/*prd*.md` or `{output_folder}/*prd*/**/*.md`
+- PRD: `{planning_artifacts}/*prd*.md` or `{output_folder}/*prd*.md` or `{output_folder}/*prd*/**/*.md`
 - Product brief: `{output_folder}/analysis/*brief*.md` or `{output_folder}/*brief*.md` or `{output_folder}/*brief*/**/*.md`
 - Epics: `{output_folder}/analysis/*epic*.md` or `{output_folder}/*epic*.md` or `{output_folder}/*epic*/**/*.md`
 - Research: `{output_folder}/analysis/research/*research*.md` or `{output_folder}/*research*.md` or `{output_folder}/*research*/**/*.md`
 - Brainstorming: `{output_folder}/analysis/brainstorming/*brainstorming*.md` or `{output_folder}/*brainstorming*.md`
 
----
-
 ## EXECUTION
 
 Load and execute `steps/step-01-init.md` to begin the UX design workflow.

package/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-03-success.md

@@ -49,8 +49,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
 
@@ -228,7 +228,7 @@ Show the generated content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current success criteria content
+- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current success criteria content
 - Process the enhanced success metrics that come back
 - Ask user: "Accept these improvements to the success criteria? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -236,7 +236,7 @@ Show the generated content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current success criteria
+- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current success criteria
 - Process the collaborative improvements to metrics and scope
 - Ask user: "Accept these changes to the success criteria? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu

package/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-04-journeys.md

@@ -49,8 +49,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
 
@@ -222,7 +222,7 @@ Show the generated journey content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current journey content
+- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current 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
@@ -230,7 +230,7 @@ Show the generated journey content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current journeys
+- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current journeys
 - Process the collaborative journey improvements and additions
 - Ask user: "Accept these changes to the user journeys? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu

package/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-05-domain.md

@@ -52,8 +52,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
 
@@ -207,7 +207,7 @@ Show the generated domain content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current domain content
+- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current domain content
 - Process the enhanced domain insights that come back
 - Ask user: "Accept these domain requirement improvements? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -215,7 +215,7 @@ Show the generated domain content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current domain requirements
+- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current domain requirements
 - Process the collaborative domain expertise and validation
 - Ask user: "Accept these changes to domain requirements? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu

package/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-06-innovation.md

@@ -52,8 +52,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 innovation content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current innovation content
+- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current innovation content
 - Process the enhanced innovation insights that come back
 - Ask user: "Accept these improvements to the innovation analysis? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -194,7 +194,7 @@ Show the generated innovation content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current innovation content
+- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current innovation content
 - Process the collaborative innovation exploration and ideation
 - Ask user: "Accept these changes to the innovation analysis? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu

package/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-07-project-type.md

@@ -52,8 +52,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
 
@@ -182,7 +182,7 @@ Show the generated project-type content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current project-type content
+- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current project-type content
 - Process the enhanced technical insights that come back
 - Ask user: "Accept these improvements to the technical requirements? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -190,7 +190,7 @@ Show the generated project-type content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current project-type requirements
+- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current project-type requirements
 - Process the collaborative technical expertise and validation
 - Ask user: "Accept these changes to the technical requirements? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu

package/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-08-scoping.md

@@ -50,8 +50,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 display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding
 
@@ -243,7 +243,7 @@ Show the scoping decisions and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with current scoping analysis
+- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with current scoping analysis
 - Process enhanced scoping insights that come back
 - Ask user: "Accept these improvements to the scoping decisions? (y/n)"
 - If yes: Update content, then return to A/P/C menu
@@ -251,7 +251,7 @@ Show the scoping decisions and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with scoping context
+- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with scoping context
 - Process collaborative insights on MVP and roadmap decisions
 - Ask user: "Accept these changes to the scoping decisions? (y/n)"
 - If yes: Update content, then return to A/P/C menu

package/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-09-functional.md

@@ -49,8 +49,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
 
@@ -209,7 +209,7 @@ Show the generated functional requirements and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current FR list
+- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current FR list
 - Process the enhanced capability coverage that comes back
 - Ask user: "Accept these additions to the functional requirements? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -217,7 +217,7 @@ Show the generated functional requirements and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current FR list
+- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current FR list
 - Process the collaborative capability validation and additions
 - Ask user: "Accept these changes to the functional requirements? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu

package/src/modules/bmm/workflows/2-plan-workflows/prd/steps/step-10-nonfunctional.md

@@ -49,8 +49,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
 
@@ -209,7 +209,7 @@ Show the generated NFR content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute {project-root}/\_bmad/core/tasks/advanced-elicitation.xml with the current NFR content
+- Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml with the current NFR content
 - Process the enhanced quality attribute insights that come back
 - Ask user: "Accept these improvements to the non-functional requirements? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -217,7 +217,7 @@ Show the generated NFR content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current NFR list
+- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current NFR list
 - Process the collaborative technical validation and additions
 - Ask user: "Accept these changes to the non-functional requirements? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu

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

@@ -9,7 +9,7 @@ workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-
 thisStepFile: '{workflow_path}/steps/step-01-document-discovery.md'
 nextStepFile: '{workflow_path}/steps/step-02-prd-analysis.md'
 workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{output_folder}/implementation-readiness-report-{{date}}.md'
+outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
 templateFile: '{workflow_path}/templates/readiness-report-template.md'
 ---
 

package/src/modules/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-02-prd-analysis.md

@@ -9,7 +9,7 @@ workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-
 thisStepFile: '{workflow_path}/steps/step-02-prd-analysis.md'
 nextStepFile: '{workflow_path}/steps/step-03-epic-coverage-validation.md'
 workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{output_folder}/implementation-readiness-report-{{date}}.md'
+outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
 epicsFile: '{output_folder}/*epic*.md' # Will be resolved to actual file
 ---
 

package/src/modules/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-03-epic-coverage-validation.md

@@ -9,7 +9,7 @@ workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-
 thisStepFile: '{workflow_path}/steps/step-03-epic-coverage-validation.md'
 nextStepFile: '{workflow_path}/steps/step-04-ux-alignment.md'
 workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{output_folder}/implementation-readiness-report-{{date}}.md'
+outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
 ---
 
 # Step 3: Epic Coverage Validation

package/src/modules/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-04-ux-alignment.md

@@ -9,7 +9,7 @@ workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-
 thisStepFile: '{workflow_path}/steps/step-04-ux-alignment.md'
 nextStepFile: '{workflow_path}/steps/step-05-epic-quality-review.md'
 workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{output_folder}/implementation-readiness-report-{{date}}.md'
+outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
 ---
 
 # Step 4: UX Alignment

package/src/modules/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-05-epic-quality-review.md

@@ -9,7 +9,7 @@ workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-
 thisStepFile: '{workflow_path}/steps/step-05-epic-quality-review.md'
 nextStepFile: '{workflow_path}/steps/step-06-final-assessment.md'
 workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{output_folder}/implementation-readiness-report-{{date}}.md'
+outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
 epicsBestPractices: '{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories'
 ---
 

package/src/modules/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md

@@ -8,7 +8,7 @@ workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-
 # File References
 thisStepFile: '{workflow_path}/steps/step-06-final-assessment.md'
 workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{output_folder}/implementation-readiness-report-{{date}}.md'
+outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
 ---
 
 # Step 6: Final Assessment

package/src/modules/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md

@@ -45,9 +45,9 @@ web_bundle: false
 
 ### 1. Module Configuration Loading
 
-Load and read full config from {project-root}/\_bmad/bmm/config.yaml and resolve:
+Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve:
 
-- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
+- `project_name`, `output_folder`, `planning_artifacts`, `user_name`, `communication_language`, `document_output_language`
 
 ### 2. First Step EXECUTION
 

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

@@ -2,7 +2,6 @@
 stepsCompleted: []
 inputDocuments: []
 workflowType: 'architecture'
-lastStep: 0
 project_name: '{{project_name}}'
 user_name: '{{user_name}}'
 date: '{{date}}'

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

@@ -36,8 +36,8 @@ Initialize the Architecture workflow by detecting continuation state, discoverin
 
 First, check if the output document already exists:
 
-- Look for file at `{output_folder}/architecture.md`
-- If exists, read the complete file including frontmatter
+- Look for existing {output_folder}||{planning_artifacts} architecture.md or \*\*/architecture/
+- If exists, read the complete file(s) including frontmatter
 - If not exists, this is a fresh workflow
 
 ### 2. Handle Continuation (If Document Exists)
@@ -58,14 +58,14 @@ Discover and load context documents using smart discovery:
 
 **PRD Document (Priority: Analysis → Main → Sharded → Whole):**
 
-1. Check analysis folder: `{output_folder}/*prd*.md`
-2. If no main files: Check for sharded PRD folder: `{output_folder}/*prd*/**/*.md`
+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 analysis folder: `{output_folder}/analysis/*epic*.md`
+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
@@ -73,24 +73,25 @@ Discover and load context documents using smart discovery:
 
 **UX Design Specification (Priority: Analysis → Main → Sharded → Whole):**
 
-1. Check folder: `{output_folder}/*ux*.md`
+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 folder: `{output_folder}/research/*research*.md`
+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):**
 
-1. Look for index file: `{output_folder/index.md`
+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
 
 **Project Context Rules (Critical for AI Agents):**
 
@@ -123,19 +124,6 @@ Before proceeding, verify we have the essential inputs:
 #### C. Create Initial Document
 
 Copy the template from `{installed_path}/architecture-decision-template.md` to `{output_folder}/architecture.md`
-Initialize frontmatter with:
-
-```yaml
----
-stepsCompleted: []
-inputDocuments: []
-workflowType: 'architecture'
-lastStep: 0
-project_name: '{{project_name}}'
-user_name: '{{user_name}}'
-date: '{{date}}'
----
-```
 
 #### D. Complete Initialization and Report
 

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

@@ -30,8 +30,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 display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding
 
@@ -169,7 +169,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/tasks/advanced-elicitation.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
@@ -177,7 +177,7 @@ Show the generated content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with the current project context
+- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current project context
 - Process the collaborative improvements to architectural understanding
 - Ask user: "Accept these changes 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

@@ -30,8 +30,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 display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding
 

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

@@ -31,8 +31,8 @@ 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 '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 display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding
 
@@ -263,7 +263,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/tasks/advanced-elicitation.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
@@ -271,7 +271,7 @@ Show the generated decisions content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with architectural decisions context
+- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with architectural decisions context
 - Process collaborative insights about decision trade-offs
 - Ask user: "Accept these changes 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

@@ -31,8 +31,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 display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding
 
@@ -304,7 +304,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/tasks/advanced-elicitation.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
@@ -312,7 +312,7 @@ Show the generated patterns content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with implementation patterns context
+- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with implementation patterns context
 - Process collaborative insights about potential conflicts
 - Ask user: "Accept these changes to the implementation patterns? (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

@@ -31,8 +31,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 display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding
 
@@ -324,7 +324,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/tasks/advanced-elicitation.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
@@ -332,7 +332,7 @@ Show the generated project structure content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute {project-root}/\_bmad/core/workflows/party-mode/workflow.md with project structure context
+- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with project structure context
 - Process collaborative insights about organization trade-offs
 - Ask user: "Accept these changes to the project structure? (y/n)"
 - If yes: Update content, then return to A/P/C menu