workflows indicate web_bundle file inclusions

src/modules/bmb/workflows/convert-legacy/README.md

@@ -8,7 +8,7 @@ The Convert Legacy workflow is a comprehensive migration tool that converts BMAD
 
 - **Multi-Format Detection** - Automatically identifies v4 agents, workflows, tasks, templates, and modules
 - **Intelligent Conversion** - Smart mapping from v4 patterns to v5 equivalents with structural improvements
-- **Sub-Workflow Integration** - Leverages build-agent, build-workflow, and build-module workflows for quality output
+- **Sub-Workflow Integration** - Leverages create-agent, create-workflow, and create-module workflows for quality output
 - **Structure Modernization** - Converts YAML-based agents to XML, templates to workflows, tasks to structured workflows
 - **Path Normalization** - Updates all references to use proper v5 path conventions
 - **Validation System** - Comprehensive validation of converted items before finalization
@@ -60,7 +60,7 @@ convert-legacy/
 
 ### Phase 1: Legacy Analysis (Steps 1-3)
 
-**Item Identification & Loading**
+**Item Identification and Loading**
 
 - Accepts file path or directory from user
 - Loads complete file/folder structure for analysis
@@ -91,10 +91,10 @@ convert-legacy/
 **Strategy Selection Based on Item Type**
 
 - **Simple Agents**: Direct XML conversion with metadata mapping
-- **Complex Agents**: Workflow-assisted creation using build-agent
+- **Complex Agents**: Workflow-assisted creation using create-agent
 - **Templates**: Template-to-workflow conversion with proper structure
 - **Tasks**: Task-to-workflow conversion with step mapping
-- **Modules**: Full module creation using build-module workflow
+- **Modules**: Full module creation using create-module workflow
 
 **Workflow Type Determination**
 
@@ -118,9 +118,9 @@ convert-legacy/
 
 - Extracts key information from legacy items
 - Invokes appropriate sub-workflows:
-  - `build-agent` for complex agent creation
-  - `build-workflow` for template/task conversion
-  - `build-module` for full module migration
+  - `create-agent` for complex agent creation
+  - `create-workflow` for template/task conversion
+  - `create-module` for full module migration
 - Ensures proper v5 structure and conventions
 
 **Template-to-Workflow Conversion (5c)**
@@ -139,7 +139,7 @@ convert-legacy/
 - Maps 1-9 elicitation menus to v5 elicitation patterns
 - Preserves execution logic and critical notices
 
-### Phase 4: Validation & Finalization (Steps 6-8)
+### Phase 4: Validation and Finalization (Steps 6-8)
 
 **Comprehensive Validation**
 
@@ -155,7 +155,7 @@ convert-legacy/
 - Notes manual adjustments needed
 - Provides warnings and recommendations
 
-**Cleanup & Archival**
+**Cleanup and Archival**
 
 - Optional archival of original v4 files
 - Final location confirmation
@@ -182,7 +182,7 @@ Converted items follow v5 conventions:
 
 - **Legacy v4 Items** - Source files or directories to convert
 - **Target Module Access** - Write permissions to target module directories
-- **Sub-Workflow Availability** - build-agent, build-workflow, build-module workflows accessible
+- **Sub-Workflow Availability** - create-agent, create-workflow, create-module workflows accessible
 - **Conversion Mappings** (optional) - v4-to-v5 pattern mappings for complex conversions
 
 ## Best Practices
@@ -244,7 +244,7 @@ To customize this workflow:
 
 - **v1.0.0** - Initial release
   - Multi-format v4 item detection and conversion
-  - Integration with build-agent, build-workflow, build-module
+  - Integration with create-agent, create-workflow, create-module
   - Comprehensive path normalization
   - Migration reporting and validation
 
@@ -252,7 +252,7 @@ To customize this workflow:
 
 For issues or questions:
 
-- Review the workflow creation guide at `/bmad/bmb/workflows/build-workflow/workflow-creation-guide.md`
+- Review the workflow creation guide at `/bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
 - Check conversion mappings at `/bmad/bmb/data/v4-to-v5-mappings.yaml`
 - Validate output using `checklist.md`
 - Consult BMAD v5 documentation for proper conventions

src/modules/bmb/workflows/convert-legacy/instructions.md

@@ -9,10 +9,10 @@
 <action>Ask user for the path to the v4 item to convert (agent, workflow, or module)</action>
 <action>Load the complete file/folder structure</action>
 <action>Detect item type based on structure and content patterns:</action>
-  - Agent: Contains `<agent>` or `<prompt>` XML tags, single file
+  - Agent: Contains agent or prompt XML tags, single file
   - Workflow: Contains workflow YAML or instruction patterns, usually folder
   - Module: Contains multiple agents/workflows in organized structure
-  - Task: Contains `<task>` XML tags
+  - Task: Contains task XML tags
 <ask>Confirm detected type or allow user to correct: "Detected as [type]. Is this correct? (y/n)"</ask>
 </step>
 
@@ -164,7 +164,7 @@ For Modules:
 - Any special behaviors
 
 <invoke-workflow>
-  workflow: {project-root}/bmad/bmb/workflows/build-agent/workflow.yaml
+  workflow: {project-root}/bmad/bmb/workflows/create-agent/workflow.yaml
   inputs:
     - agent_name: {{extracted_name}}
     - agent_purpose: {{extracted_purpose}}
@@ -201,7 +201,7 @@ For Modules:
    - Processing flow → integrate into workflow steps
 
 <invoke-workflow>
-  workflow: {project-root}/bmad/bmb/workflows/build-workflow/workflow.yaml
+  workflow: {project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml
   inputs:
     - workflow_name: {{template_name}}
     - workflow_type: document
@@ -217,7 +217,7 @@ For Modules:
 <action>Create module blueprint with all components</action>
 
 <invoke-workflow>
-  workflow: {project-root}/bmad/bmb/workflows/build-module/workflow.yaml
+  workflow: {project-root}/bmad/bmb/workflows/create-module/workflow.yaml
   inputs:
     - module_name: {{module_name}}
     - components: {{component_list}}
@@ -259,7 +259,7 @@ For Modules:
    - Critical notices → workflow.yaml comments
 
 <invoke-workflow>
-  workflow: {project-root}/bmad/bmb/workflows/build-workflow/workflow.yaml
+  workflow: {project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml
   inputs:
     - workflow_name: {{task_name}}
     - workflow_type: {{confirmed_workflow_type}}

src/modules/bmb/workflows/convert-legacy/workflow.yaml

@@ -14,7 +14,6 @@ date: system-generated
 # Optional docs that can be provided as input
 recommended_inputs:
   - legacy_file: "Path to v4 agent, workflow, or module to convert"
-  - conversion_mappings: "{project-root}/bmad/bmb/data/v4-to-v5-mappings.yaml"
 
 # Module path and component files
 installed_path: "{project-root}/bmad/bmb/workflows/convert-legacy"
@@ -27,9 +26,8 @@ default_output_folder: "{project-root}/bmad/{{target_module}}/{{item_type}}/{{it
 
 # Sub-workflows that may be invoked for conversion
 sub_workflows:
-  - create_agent: "{project-root}/bmad/bmb/workflows/build-agent/workflow.yaml"
-  - create_workflow: "{project-root}/bmad/bmb/workflows/build-workflow/workflow.yaml"
-  - create_module: "{project-root}/bmad/bmb/workflows/build-module/workflow.yaml"
+  - create_agent: "{project-root}/bmad/bmb/workflows/create-agent/workflow.yaml"
+  - create_workflow: "{project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml"
+  - create_module: "{project-root}/bmad/bmb/workflows/create-module/workflow.yaml"
 
-# No special tools required beyond standard BMAD capabilities
-required_tools: []
+web_bundle: false