workflow builder has template LOD output options

src/modules/bmb/docs/workflows/architecture.md

@@ -69,7 +69,7 @@ workflow-folder/
 Standard variables in step files:
 
 ```yaml
-workflow_path: '{project-root}/{bmad_folder}/bmb/reference/workflows/[workflow-name]'
+workflow_path: '{project-root}/{*bmad_folder*}/bmb/reference/workflows/[workflow-name]'
 thisStepFile: '{workflow_path}/steps/step-[N]-[name].md'
 nextStepFile: '{workflow_path}/steps/step-[N+1]-[name].md'
 workflowFile: '{workflow_path}/workflow.md'

src/modules/bmb/docs/workflows/templates/step-01-init-continuable-template.md

@@ -13,7 +13,7 @@ description: 'Initialize the [workflow-type] workflow by detecting continuation
 
 <!-- Path Definitions -->
 
-workflow_path: '{project-root}/{bmad_folder}/[module-path]/workflows/[workflow-name]'
+workflow*path: '{project-root}/{\_bmad_folder*}/[module-path]/workflows/[workflow-name]'
 
 # File References (all use {variable} format in file)
 

src/modules/bmb/docs/workflows/templates/step-1b-template.md

@@ -13,7 +13,7 @@ description: 'Handle workflow continuation from previous session'
 
 <!-- Path Definitions -->
 
-workflow_path: '{project-root}/{bmad_folder}/[module-path]/workflows/[workflow-name]'
+workflow*path: '{project-root}/{\_bmad_folder*}/[module-path]/workflows/[workflow-name]'
 
 # File References (all use {variable} format in file)
 

src/modules/bmb/docs/workflows/templates/step-file.md

@@ -3,7 +3,7 @@ name: "step-{{stepNumber}}-{{stepName}}"
 description: "{{stepDescription}}"
 
 # Path Definitions
-workflow_path: "{project-root}/{bmad_folder}/{{targetModule}}/workflows/{{workflowName}}"
+workflow_path: "{project-root}/{*bmad_folder*}/{{targetModule}}/workflows/{{workflowName}}"
 
 # File References
 thisStepFile: "{workflow_path}/steps/step-{{stepNumber}}-{{stepName}}.md"
@@ -15,9 +15,9 @@ workflowFile: "{workflow_path}/workflow.md"
 outputFile: "{output_folder}/{{outputFileName}}-{project_name}.md"
 {{/hasOutput}}
 
-# Task References
-advancedElicitationTask: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
-partyModeWorkflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
+# Task References (list only if used in THIS step file instance and only the ones used, there might be others)
+advancedElicitationTask: "{project-root}/{*bmad_folder*}/core/tasks/advanced-elicitation.xml"
+partyModeWorkflow: "{project-root}/{*bmad_folder*}/core/workflows/party-mode/workflow.md"
 
 {{#hasTemplates}}
 # Template References

src/modules/bmb/docs/workflows/templates/step-template.md

@@ -11,7 +11,7 @@ description: '[Brief description of what this step accomplishes]'
 
 <!-- Path Definitions -->
 
-workflow_path: '{project-root}/{bmad_folder}/bmb/reference/workflows/[workflow-name]' # the folder the workflow.md file is in
+workflow*path: '{project-root}/{\_bmad_folder*}/bmb/reference/workflows/[workflow-name]' # the folder the workflow.md file is in
 
 # File References (all use {variable} format in file)
 
@@ -23,8 +23,8 @@ outputFile: '{output_folder}/[output-file-name]-{project_name}.md'
 
 # Task References (IF THE workflow uses and it makes sense in this step to have these )
 
-advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md'
+advancedElicitationTask: '{project-root}/{_bmad_folder_}/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/{_bmad_folder_}/core/workflows/party-mode/workflow.md'
 
 # Template References (if this step uses a specific templates)
 

src/modules/bmb/docs/workflows/templates/workflow-template.md

@@ -53,7 +53,7 @@ web_bundle: [true/false] # Set to true for inclusion in web bundle builds
 
 ### 1. Module Configuration Loading
 
-Load and read full config from {project-root}/{bmad_folder}/[MODULE FOLDER]/config.yaml and resolve:
+Load and read full config from {project-root}/{_bmad_folder_}/[MODULE FOLDER]/config.yaml and resolve:
 
 - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, [MODULE VARS]
 

src/modules/bmb/docs/workflows/templates/workflow.md

@@ -49,7 +49,7 @@ This uses **step-file architecture** for disciplined execution:
 
 ### 1. Configuration Loading
 
-Load and read full config from {project-root}/{bmad_folder}/{{targetModule}}/config.yaml and resolve:
+Load and read full config from {project-root}/{_bmad_folder_}/{{targetModule}}/config.yaml and resolve:
 
 - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
 

src/modules/bmb/workflows/create-workflow/steps/step-07-build.md

@@ -117,7 +117,7 @@ Load and follow {workflowTemplate}:
 
 - Create workflow.md using template structure
 - Insert workflow name and description
-- Configure all path variables ({project-root}, {bmad_folder}, {workflow_path})
+- Configure all path variables ({project-root}, {_bmad_folder_}, {workflow_path})
 - Set web_bundle flag to true unless user has indicated otherwise
 - Define role and goal
 - Include initialization path to step-01

src/modules/bmb/workflows/workflow-compliance-check/steps/step-02-workflow-validation.md

@@ -132,10 +132,10 @@ For each deviation:
 
 "**Initialization Validation:**"
 
-- Configuration Loading uses correct path format: `{project-root}/{bmad_folder}/[module]/config.yaml` (variable substitution pattern)
+- Configuration Loading uses correct path format: `{project-root}/{*bmad_folder*}/[module]/config.yaml` (variable substitution pattern)
 - First step follows pattern: `step-01-init.md` OR documented deviation
 - Required config variables properly listed
-- Variables use proper substitution pattern: {project-root}, {bmad_folder}, {workflow_path}, etc.
+- Variables use proper substitution pattern: {project-root}, {_bmad_folder_}, {workflow_path}, etc.
 
 For violations:
 
@@ -198,7 +198,7 @@ Append to {complianceReportFile}:
 
 "**Phase 1 Complete:** Workflow.md validation finished with detailed violation analysis.
 
-**Ready for Phase 2:** Step-by-step validation against step-template.md
+**Ready for Phase 3:** Step-by-step validation against step-template.md
 
 This will check each step file for:
 

src/modules/bmb/workflows/workflow-compliance-check/steps/step-03-step-validation.md

@@ -138,8 +138,8 @@ Check for proper references:
 
 ```yaml
 # Task References
-advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md'
+advancedElicitationTask: '{project-root}/{*bmad_folder*}/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/{*bmad_folder*}/core/workflows/party-mode/workflow.md'
 ```
 
 **Violations to document:**
@@ -186,7 +186,7 @@ For each step:
 
 "**Path Variable Validation:**"
 
-- Check format: `{project-root}/{bmad_folder}/bmb/...` vs `{project-root}/src/modules/bmb/...`
+- Check format: `{project-root}/{*bmad_folder*}/bmb/...` vs `{project-root}/src/modules/bmb/...`
 - Ensure consistent variable usage across all step files
 - Validate relative vs absolute path usage
 
@@ -232,13 +232,13 @@ For each step file with violations:
 2. [Second most frequent]
 3. [Third most frequent]
 
-**Ready for Phase 3:** Holistic workflow analysis
+**Ready for Phase 4:** File Validation workflow analysis
 
 - Flow optimization assessment
 - Goal alignment verification
 - Meta-workflow failure analysis
 
-**Select an Option:** [C] Continue to Holistic Analysis [X] Exit"
+**Select an Option:** [C] Continue to File Validation [X] Exit"
 
 ## Menu Handling Logic:
 

src/modules/bmb/workflows/workflow-compliance-check/steps/step-04-file-validation.md

@@ -253,7 +253,7 @@ For each file with issues:
 - **Formatting Standards:** [summary of markdown compliance issues]
 - **Data Validation:** [summary of CSV standards compliance]
 
-**Ready for Phase 5:** Holistic workflow analysis
+**Ready for Phase 5:** Intent Spectrum Validation analysis
 
 - Flow validation and goal alignment
 - Meta-workflow failure analysis

src/modules/bmb/workflows/workflow-compliance-check/steps/step-05-intent-spectrum-validation.md

@@ -222,7 +222,7 @@ Append to {complianceReportFile}:
 - **User Understanding:** Confirmed implications and benefits
 - **Implementation Ready:** Guidance provided for maintaining position
 
-**Ready for Phase 6:** Holistic workflow analysis
+**Ready for Phase 6:** Web Subprocess Validation analysis
 
 - Flow validation and completion paths
 - Goal alignment and optimization assessment

src/modules/bmb/workflows/workflow-compliance-check/steps/step-06-web-subprocess-validation.md

@@ -315,7 +315,7 @@ Append to {complianceReportFile}:
 - **Performance Impact:** [expected efficiency gains]
 - **User Experience Benefits:** [specific improvements]
 
-**Ready for Phase 6:** Holistic workflow analysis
+**Ready for Phase 7:** Holistic workflow analysis
 
 - Flow validation and completion paths
 - Goal alignment with optimized resources

src/modules/bmb/workflows/workflow-compliance-check/steps/step-07-holistic-analysis.md

@@ -215,7 +215,7 @@ Evaluate workflow from user perspective:
 - **Optimization Opportunities:** [number key improvements identified]
 - **Meta-Workflow Failures:** [number issues that should have been prevented]
 
-**Ready for Phase 6:** Comprehensive compliance report generation
+**Ready for Phase 8:** Comprehensive compliance report generation
 
 - All findings compiled into structured report
 - Severity-ranked violation list