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

src/modules/bmb/workflows/create-agent/README.md

@@ -19,7 +19,7 @@ The Build Agent workflow is an interactive agent builder that guides you through
 ### Basic Invocation
 
 ```bash
-workflow build-agent
+workflow create-agent
 ```
 
 ### Through BMad Builder Agent
@@ -49,7 +49,7 @@ The workflow includes an optional brainstorming phase (Step -1) that helps you e
 ### Files Included
 
 ```
-build-agent/
+create-agent/
 ├── workflow.yaml                  # Configuration
 ├── instructions.md                # Step-by-step guide
 ├── checklist.md                   # Validation criteria

src/modules/bmb/workflows/create-agent/agent-command-patterns.md

@@ -318,7 +318,7 @@ Logic embedded in agent persona (Simple agents)
 
   <!-- 2. Primary workflows -->
   <c cmd="*create-prd" run-workflow="...">Create PRD</c>
-  <c cmd="*build-module" run-workflow="...">Build module</c>
+  <c cmd="*create-module" run-workflow="...">Build module</c>
 
   <!-- 3. Secondary actions -->
   <c cmd="*validate" exec="...">Validate document</c>
@@ -490,8 +490,8 @@ The `data` attribute can be added to ANY command type to provide supplementary i
 ### BMB (Builder)
 
 ```xml
-<c cmd="*build-agent">Build Agent</c>
-<c cmd="*build-module">Build Module</c>
+<c cmd="*create-agent">Build Agent</c>
+<c cmd="*create-module">Build Module</c>
 <c cmd="*create-workflow">Create Workflow</c>
 <c cmd="*module-brief">Module Brief</c>
 ```
@@ -511,7 +511,7 @@ The `data` attribute can be added to ANY command type to provide supplementary i
 ```
 1. *help - Show numbered cmd list
 2. *create-prd - Create Product Requirements Document
-3. *build-agent - Build new BMAD agent
+3. *create-agent - Build new BMAD agent
 4. *validate - Validate document
 5. *exit - Exit with confirmation
 ```

src/modules/bmb/workflows/create-agent/brainstorm-context.md

@@ -20,28 +20,28 @@ An agent is an AI persona that embodies:
 
 Explore and define:
 
-### 1. Agent Identity & Personality
+### 1. Agent Identity and Personality
 
 - **Who are they?** (name, backstory, motivation)
 - **How do they talk?** (formal, casual, quirky, enthusiastic, wise)
 - **What's their vibe?** (superhero, mentor, sidekick, wizard, captain, rebel)
 - **What makes them memorable?** (catchphrases, quirks, style)
 
-### 2. Expertise & Capabilities
+### 2. Expertise and Capabilities
 
 - **What do they know deeply?** (domain expertise)
 - **What can they do?** (analyze, create, review, research, deploy)
 - **What problems do they solve?** (specific user pain points)
 - **What makes them unique?** (special skills or approaches)
 
-### 3. Commands & Actions
+### 3. Commands and Actions
 
 - **What commands?** (5-10 main actions users invoke)
 - **What workflows do they run?** (document creation, analysis, automation)
 - **What tasks do they perform?** (quick operations without full workflows)
 - **What's their killer command?** (the one thing they're known for)
 
-### 4. Agent Type & Context
+### 4. Agent Type and Context
 
 - **Simple Agent?** Self-contained, no dependencies, quick utility
 - **Expert Agent?** Domain-specific with sidecar data/memory files

src/modules/bmb/workflows/create-agent/communication-styles.md

@@ -6,7 +6,7 @@ Agents with distinct communication styles are more memorable, engaging, and fun
 
 ## Style Categories
 
-### 🎬 Cinema & TV Inspired
+### 🎬 Cinema and TV Inspired
 
 **Film Noir Detective**
 
@@ -32,7 +32,7 @@ Whether 'tis nobler in the mind to suffer the slings and arrows of outrageous er
 Or to take arms against a sea of bugs, and by opposing, end them?
 ```
 
-### 🎮 Gaming & Pop Culture
+### 🎮 Gaming and Pop Culture
 
 **Dungeon Master**
 
@@ -118,7 +118,7 @@ Speaking of cache, let's clear yours and see if that fixes the issue.
 I promise my debugging skills are better than my jokes! ...I hope!
 ```
 
-### 🚀 Sci-Fi & Space
+### 🚀 Sci-Fi and Space
 
 **Star Trek Officer**
 

src/modules/bmb/workflows/create-agent/instructions.md

@@ -1,7 +1,7 @@
 # Build Agent - Interactive Agent Builder Instructions
 
 <critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
-<critical>You MUST have already loaded and processed: {project_root}/bmad/bmb/workflows/build-agent/workflow.yaml</critical>
+<critical>You MUST have already loaded and processed: {project_root}/bmad/bmb/workflows/create-agent/workflow.yaml</critical>
 <critical>Study agent examples in: {project_root}/bmad/bmm/agents/ for patterns</critical>
 
 <workflow>

src/modules/bmb/workflows/create-agent/workflow.yaml

@@ -1,5 +1,5 @@
 # Build Agent Workflow Configuration
-name: build-agent
+name: create-agent
 description: "Interactive workflow to build BMAD Core compliant agents (simple, expert, or module types) with optional brainstorming for agent ideas, proper persona development, activation rules, and command structure"
 author: "BMad"
 
@@ -23,7 +23,7 @@ recommended_inputs:
   - agent_activation_rules: "{project-root}/src/utility/models/agent-activation-ide.xml"
 
 # Module path and component files
-installed_path: "{project-root}/bmad/bmb/workflows/build-agent"
+installed_path: "{project-root}/bmad/bmb/workflows/create-agent"
 template: false # This is an interactive workflow - no template needed
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
@@ -35,5 +35,14 @@ default_output_file: "{output_folder}/agents/{{agent_filename}}.md"
 src_output_file: "{project-root}/src/modules/{{target_module}}/agents/{{agent_filename}}.md"
 config_output_file: "{project-root}/bmad/_cfg/agents/{{agent_config_name}}.md"
 
-# No special tools required for agent building
-required_tools: []
+web_bundle:
+  name: "create-agent"
+  description: "Interactive workflow to build BMAD Core compliant agents (simple, expert, or module types) with optional brainstorming for agent ideas, proper persona development, activation rules, and command structure"
+  author: "BMad"
+  web_bundle_files:
+    - "bmad/bmb/workflows/create-agent/instructions.md"
+    - "bmad/bmb/workflows/create-agent/checklist.md"
+    - "bmad/bmb/workflows/create-agent/agent-types.md"
+    - "bmad/bmb/workflows/create-agent/agent-architecture.md"
+    - "bmad/bmb/workflows/create-agent/agent-command-patterns.md"
+    - "bmad/bmb/workflows/create-agent/communication-styles.md"

src/modules/bmb/workflows/create-module/README.md

@@ -8,24 +8,24 @@ The Build Module workflow is an interactive scaffolding system that creates comp
 
 - **Interactive Module Planning** - Collaborative session to define module concept, scope, and architecture
 - **Intelligent Scaffolding** - Automatic creation of proper directory structures and configuration files
-- **Component Integration** - Seamless integration with build-agent and build-workflow workflows
+- **Component Integration** - Seamless integration with create-agent and create-workflow workflows
 - **Installation Infrastructure** - Complete installer setup with configuration templates
 - **Module Brief Integration** - Can use existing module briefs as blueprints for accelerated development
-- **Validation & Documentation** - Built-in validation checks and comprehensive README generation
+- **Validation and Documentation** - Built-in validation checks and comprehensive README generation
 
 ## Usage
 
 ### Basic Invocation
 
 ```bash
-workflow build-module
+workflow create-module
 ```
 
 ### With Module Brief Input
 
 ```bash
 # If you have a module brief from the module-brief workflow
-workflow build-module --input module-brief-my-module-2024-09-26.md
+workflow create-module --input module-brief-my-module-2024-09-26.md
 ```
 
 ### Configuration
@@ -41,7 +41,7 @@ The workflow loads critical variables from the BMB configuration:
 ### Files Included
 
 ```
-build-module/
+create-module/
 ├── workflow.yaml           # Configuration and metadata
 ├── instructions.md         # Step-by-step execution guide
 ├── checklist.md           # Validation criteria
@@ -56,7 +56,7 @@ build-module/
 
 ### Phase 1: Concept Definition (Steps 1-2)
 
-**Module Vision & Identity**
+**Module Vision and Identity**
 
 - Define module concept, purpose, and target audience
 - Establish module code (kebab-case) and friendly name
@@ -87,8 +87,8 @@ build-module/
 
 **Interactive Component Building**
 
-- Optional creation of first agent using build-agent workflow
-- Optional creation of first workflow using build-workflow workflow
+- Optional creation of first agent using create-agent workflow
+- Optional creation of first workflow using create-workflow workflow
 - Creates placeholders for components to be built later
 
 **Workflow Integration**
@@ -97,7 +97,7 @@ build-module/
 - Ensures proper file placement and structure
 - Maintains module consistency across components
 
-### Phase 4: Installation & Documentation (Steps 7-9)
+### Phase 4: Installation and Documentation (Steps 7-9)
 
 **Installer Infrastructure**
 
@@ -111,7 +111,7 @@ build-module/
 - Creates development roadmap for remaining components
 - Provides quick commands for continued development
 
-### Phase 5: Validation & Finalization (Step 10)
+### Phase 5: Validation and Finalization (Step 10)
 
 **Quality Assurance**
 
@@ -144,7 +144,7 @@ The workflow creates a complete module ready for development:
 
 - **Module Brief** (optional but recommended) - Use module-brief workflow first for best results
 - **BMAD Core Configuration** - Properly configured BMB config.yaml
-- **Build Tools Access** - build-agent and build-workflow workflows must be available
+- **Build Tools Access** - create-agent and create-workflow workflows must be available
 
 ## Best Practices
 
@@ -158,7 +158,7 @@ The workflow creates a complete module ready for development:
 
 1. **Use Module Briefs** - Load existing briefs when prompted for accelerated development
 2. **Start Simple** - Create one core agent and workflow, then expand iteratively
-3. **Leverage Sub-workflows** - Use build-agent and build-workflow for quality components
+3. **Leverage Sub-workflows** - Use create-agent and create-workflow for quality components
 4. **Validate Early** - Review generated structure before proceeding to next phases
 
 ### After Completion
@@ -179,7 +179,7 @@ The workflow creates a complete module ready for development:
 
 **Issue**: Sub-workflow invocation fails
 
-- **Solution**: Ensure build-agent and build-workflow workflows are available
+- **Solution**: Ensure create-agent and create-workflow workflows are available
 - **Check**: Validate workflow paths in config.yaml
 
 **Issue**: Installation configuration invalid
@@ -200,7 +200,7 @@ To customize this workflow:
 
 - **v1.0.0** - Initial release
   - Interactive module scaffolding
-  - Component integration with build-agent and build-workflow
+  - Component integration with create-agent and create-workflow
   - Complete installation infrastructure
   - Module brief integration support
 
@@ -208,7 +208,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`
 - Study module structure patterns at `module-structure.md`
 - Validate output using `checklist.md`
 - Consult existing modules in `/bmad/` for examples

src/modules/bmb/workflows/create-module/brainstorm-context.md

@@ -20,7 +20,7 @@ A module is a cohesive package that provides:
 
 Explore and define:
 
-### 1. Domain & Purpose
+### 1. Domain and Purpose
 
 - **What domain/problem space?** (e.g., game development, marketing, personal productivity)
 - **Who is the target user?** (developers, writers, managers, hobbyists)

src/modules/bmb/workflows/create-module/checklist.md

@@ -1,6 +1,6 @@
 # Build Module Validation Checklist
 
-## Module Identity & Metadata
+## Module Identity and Metadata
 
 ### Basic Information
 
@@ -165,7 +165,7 @@
 - [ ] Component organization is logical
 - [ ] No hard-coded limits
 
-## Testing & Validation
+## Testing and Validation
 
 ### Structural Validation
 

src/modules/bmb/workflows/create-module/instructions.md

@@ -1,7 +1,7 @@
 # Build Module - Interactive Module Builder Instructions
 
 <critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
-<critical>You MUST have already loaded and processed: {project_root}/bmad/bmb/workflows/build-module/workflow.yaml</critical>
+<critical>You MUST have already loaded and processed: {project_root}/bmad/bmb/workflows/create-module/workflow.yaml</critical>
 <critical>Study existing modules in: {project_root}/bmad/ for patterns</critical>
 
 <workflow>
@@ -10,8 +10,8 @@
 <ask>Do you want to brainstorm module ideas first? [y/n]</ask>
 
 If yes:
-<action>Invoke brainstorming workflow: {project-root}/bmad/cis/workflows/brainstorming/workflow.yaml</action>
-<action>Pass context data: {installed_path}/brainstorm-context.md</action>
+<action>Invoke brainstorming workflow: {brainstorming-workflow}</action>
+<action>Pass context data: {brainstorming_context}</action>
 <action>Wait for brainstorming session completion</action>
 <action>Use brainstorming output to inform module concept, agent lineup, and workflow portfolio</action>
 
@@ -215,7 +215,7 @@ If no, create placeholder:
 ```md
 # {{primary_agent_name}} Agent
 
-<!-- TODO: Create using build-agent workflow -->
+<!-- TODO: Create using create-agent workflow -->
 <!-- Purpose: {{agent_purpose}} -->
 <!-- Type: {{agent_type}} -->
 ```
@@ -402,8 +402,8 @@ Key settings:
 
 To extend this module:
 
-1. Add new agents using `build-agent` workflow
-2. Add new workflows using `build-workflow` workflow
+1. Add new agents using `create-agent` workflow
+2. Add new workflows using `create-workflow` workflow
 3. Submit improvements via pull request
 
 ## Author
@@ -428,7 +428,7 @@ Create a development roadmap for remaining components:
 ## Phase 2: Enhanced Features
 {{phase2_tasks}}
 
-## Phase 3: Polish & Integration
+## Phase 3: Polish and Integration
 {{phase3_tasks}}
 
 ## Quick Commands
@@ -436,14 +436,14 @@ Create a development roadmap for remaining components:
 Create new agent:
 ````
 
-workflow build-agent
+workflow create-agent
 
 ```
 
 Create new workflow:
 ```
 
-workflow build-workflow
+workflow create-workflow
 
 ```
 

src/modules/bmb/workflows/create-module/workflow.yaml

@@ -1,5 +1,5 @@
 # Build Module Workflow Configuration
-name: build-module
+name: create-module
 description: "Interactive workflow to build complete BMAD modules with agents, workflows, tasks, and installation infrastructure"
 author: "BMad"
 
@@ -17,8 +17,10 @@ installer_templates: "{installed_path}/installer-templates/"
 example_modules: "{installed_path}/example-modules.md"
 
 # Use existing build workflows
-agent_builder: "{project-root}/bmad/bmb/workflows/build-agent/workflow.yaml"
-workflow_builder: "{project-root}/bmad/bmb/workflows/build-workflow/workflow.yaml"
+agent_builder: "{project-root}/bmad/bmb/workflows/create-agent/workflow.yaml"
+workflow_builder: "{project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml"
+brainstorming_workflow: "{project-root}/bmad/cis/workflows/brainstorming/workflow.yaml"
+brainstorming_context: "{installed_path}/brainstorm-context.md"
 
 # Optional docs that help understand module patterns
 recommended_inputs:
@@ -30,7 +32,7 @@ recommended_inputs:
   - existing_workflows: "{project-root}/bmad/*/workflows/"
 
 # Module path and component files
-installed_path: "{project-root}/bmad/bmb/workflows/build-module"
+installed_path: "{project-root}/bmad/bmb/workflows/create-module"
 template: false # This is an interactive scaffolding workflow
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
@@ -43,5 +45,17 @@ src_output_folder: "{project-root}/src/modules/{{module_code}}"
 installer_output_folder: "{output_folder}/{{module_code}}"
 src_installer_output_folder: "{project-root}/src/modules/{{module_code}}"
 
-# No special tools required for module building
-required_tools: []
+web_bundle:
+  name: "create-module"
+  description: "Interactive workflow to build complete BMAD modules with agents, workflows, tasks, and installation infrastructure"
+  author: "BMad"
+  web_bundle_files:
+    - "bmad/bmb/workflows/create-module/instructions.md"
+    - "bmad/bmb/workflows/create-module/checklist.md"
+    - "bmad/bmb/workflows/create-module/module-structure.md"
+    - "bmad/bmb/workflows/create-module/example-modules.md"
+    - "bmad/bmb/workflows/create-module/brainstorm-context.md"
+  existing_workflows:
+    - agent_builder: "bmad/bmb/workflows/create-agent/workflow.yaml"
+    - workflow_builder: "bmad/bmb/workflows/create-workflow/workflow.yaml"
+    - brainstorming_workflow: "bmad/cis/workflows/brainstorming/workflow.yaml"

src/modules/bmb/workflows/create-workflow/README.md

@@ -19,7 +19,7 @@ The Build Workflow is an interactive workflow builder that guides you through cr
 ### Basic Invocation
 
 ```bash
-workflow build-workflow
+workflow create-workflow
 ```
 
 ### Through BMad Builder Agent
@@ -42,7 +42,7 @@ workflow build-workflow
 ### Files Included
 
 ```
-build-workflow/
+create-workflow/
 ├── workflow.yaml                  # Configuration and metadata
 ├── instructions.md                # Step-by-step execution guide
 ├── checklist.md                   # Validation criteria
@@ -87,7 +87,7 @@ The brainstorming phase invokes the CIS brainstorming workflow to:
 - Generate validation checklist
 - Create supporting data files (optional)
 
-### Phase 3: Documentation & Validation (Steps 9-11)
+### Phase 3: Documentation and Validation (Steps 9-11)
 
 - Create comprehensive README.md (MANDATORY)
 - Test and validate workflow structure
@@ -142,7 +142,7 @@ For document workflows, the README documents:
 
 ### Creative Workflow Design
 
-The build-workflow now supports a **seamless transition from creative ideation to structured implementation**:
+The create-workflow now supports a **seamless transition from creative ideation to structured implementation**:
 
 - **"I need a workflow for something..."** → Start with brainstorming to explore possibilities
 - **Brainstorm** → Generate multiple approaches and clarify requirements
@@ -206,9 +206,9 @@ To modify this workflow:
 
 For issues or questions:
 
-- Review `/bmad/bmb/workflows/build-workflow/workflow-creation-guide.md`
+- Review `/bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
 - Check existing workflows in `/bmad/bmm/workflows/` for examples
-- Validate against `/bmad/bmb/workflows/build-workflow/checklist.md`
+- Validate against `/bmad/bmb/workflows/create-workflow/checklist.md`
 - Consult BMAD Method v6 documentation
 
 ---

src/modules/bmb/workflows/create-workflow/brainstorm-context.md

@@ -20,7 +20,7 @@ A workflow is a structured process that provides:
 
 Explore and define:
 
-### 1. Problem & Purpose
+### 1. Problem and Purpose
 
 - **What task needs structure?** (specific process users struggle with)
 - **Why is this hard manually?** (complexity, inconsistency, missing steps)
@@ -35,14 +35,14 @@ Explore and define:
 - **What's optional vs required?** (flexibility points)
 - **What checkpoints matter?** (validation, review, approval points)
 
-### 3. Inputs & Outputs
+### 3. Inputs and Outputs
 
 - **What inputs are needed?** (documents, data, user answers)
 - **What outputs are generated?** (documents, code, configurations)
 - **What format?** (markdown, XML, YAML, actions)
 - **What quality criteria?** (how to validate success)
 
-### 4. Workflow Type & Style
+### 4. Workflow Type and Style
 
 - **Document Workflow?** Creates structured documents (PRDs, specs, reports)
 - **Action Workflow?** Performs operations (refactoring, deployment, analysis)
@@ -78,7 +78,7 @@ A great BMAD workflow should be:
 4. **Checkpoints** (where to pause for approval)
 5. **Variables** (data passed between steps)
 
-### Quality & Validation
+### Quality and Validation
 
 1. **Success criteria** (what defines "done")
 2. **Validation checklist** (measurable quality checks)

src/modules/bmb/workflows/create-workflow/instructions.md

@@ -3,7 +3,7 @@
 <workflow>
 
 <critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
-<critical>You MUST have already loaded and processed: {project_root}/bmad/bmb/workflows/build-workflow/workflow.yaml</critical>
+<critical>You MUST have already loaded and processed: {project_root}/bmad/bmb/workflows/create-workflow/workflow.yaml</critical>
 <critical>You MUST fully understand the workflow creation guide at: {workflow_creation_guide}</critical>
 <critical>Study the guide thoroughly to follow ALL conventions for optimal human-AI collaboration</critical>
 

src/modules/bmb/workflows/create-workflow/workflow-creation-guide.md

@@ -8,7 +8,7 @@ Create structured, repeatable workflows for human-AI collaboration in BMAD v6.
 2. [Core Concepts](#core-concepts)
 3. [Workflow Structure](#workflow-structure)
 4. [Writing Instructions](#writing-instructions)
-5. [Templates & Variables](#templates--variables)
+5. [Templates and Variables](#templates--variables)
 6. [Flow Control](#flow-control)
 7. [Validation](#validation)
 8. [Examples](#examples)
@@ -192,7 +192,7 @@ Write 1-3 bullet points about project success:
 </step>
 ```
 
-## Templates & Variables
+## Templates and Variables
 
 ### Variable Syntax
 
@@ -257,7 +257,7 @@ _Generated on {{date}}_
 </step>
 ```
 
-### Branching & Goto
+### Branching and Goto
 
 ```xml
 <step n="7" goal="Validate">

src/modules/bmb/workflows/create-workflow/workflow.yaml

@@ -1,5 +1,5 @@
 # Build Workflow - Workflow Builder Configuration
-name: build-workflow
+name: create-workflow
 description: "Interactive workflow builder that guides creation of new BMAD workflows with proper structure and validation for optimal human-AI collaboration. Includes optional brainstorming phase for workflow ideas and design."
 author: "BMad Builder"
 
@@ -23,7 +23,7 @@ recommended_inputs:
   - bmm_workflows: "{project-root}/bmad/bmm/workflows/"
 
 # Module path and component files
-installed_path: "{project-root}/bmad/bmb/workflows/build-workflow"
+installed_path: "{project-root}/bmad/bmb/workflows/create-workflow"
 template: false # This is an action workflow - no template needed
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
@@ -38,5 +38,15 @@ workflow_template_path: "{installed_path}/workflow-template"
 default_output_folder: "{output_folder}/workflows/{{workflow_name}}"
 src_output_folder: "{project-root}/src/modules/{{target_module}}/workflows/{{workflow_name}}"
 
-# No special tools required
-required_tools: []
+web_bundle:
+  name: "create-workflow"
+  description: "Interactive workflow builder that guides creation of new BMAD workflows with proper structure and validation for optimal human-AI collaboration. Includes optional brainstorming phase for workflow ideas and design."
+  author: "BMad Builder"
+  web_bundle_files:
+    - "bmad/bmb/workflows/create-workflow/instructions.md"
+    - "bmad/bmb/workflows/create-workflow/checklist.md"
+    - "bmad/bmb/workflows/create-workflow/workflow-creation-guide.md"
+    - "bmad/bmb/workflows/create-workflow/workflow-template/workflow.yaml"
+    - "bmad/bmb/workflows/create-workflow/workflow-template/instructions.md"
+    - "bmad/bmb/workflows/create-workflow/workflow-template/template.md"
+    - "bmad/bmb/workflows/create-workflow/workflow-template/checklist.md"

src/modules/bmb/workflows/edit-workflow/instructions.md

@@ -66,7 +66,7 @@ Based on the selected edit type, load appropriate reference materials:
 <action>Load example workflows from {project-root}/bmad/bmm/workflows/ for patterns</action>
 
 <check>If editing templates:</check>
-<action>Review the "Templates & Variables" section of the creation guide</action>
+<action>Review the "Templates and Variables" section of the creation guide</action>
 <action>Ensure variable naming conventions are followed</action>
 
 <check>If editing validation:</check>

src/modules/bmb/workflows/edit-workflow/workflow.yaml

@@ -12,7 +12,7 @@ user_name: "{config_source}:user_name"
 date: system-generated
 
 # Required Data Files - Critical for understanding workflow conventions
-workflow_creation_guide: "{project-root}/bmad/bmb/workflows/build-workflow/workflow-creation-guide.md"
+workflow_creation_guide: "{project-root}/bmad/bmb/workflows/create-workflow/workflow-creation-guide.md"
 workflow_execution_engine: "{project-root}/bmad/core/tasks/workflow.md"
 
 # Optional docs that can be used to understand the target workflow
@@ -30,5 +30,10 @@ validation: "{installed_path}/checklist.md"
 # But we may generate a change log
 change_log_output: "{output_folder}/workflow-edit-log-{{date}}.md"
 
-# No special tools required for editing workflows
-required_tools: []
+web_bundle:
+  name: "edit-workflow"
+  description: "Edit existing BMAD workflows while following all best practices and conventions"
+  author: "BMad"
+  web_bundle_files:
+    - "bmad/bmb/workflows/edit-workflow/instructions.md"
+    - "bmad/bmb/workflows/edit-workflow/checklist.md"

src/modules/bmb/workflows/module-brief/README.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-The Module Brief workflow creates comprehensive blueprints for building new BMAD modules using strategic analysis and creative vision. It serves as the essential planning phase that transforms initial ideas into detailed, actionable specifications ready for implementation with the build-module workflow.
+The Module Brief workflow creates comprehensive blueprints for building new BMAD modules using strategic analysis and creative vision. It serves as the essential planning phase that transforms initial ideas into detailed, actionable specifications ready for implementation with the create-module workflow.
 
 ## Key Features
 
@@ -61,9 +61,9 @@ module-brief/
 
 ## Workflow Process
 
-### Phase 1: Foundation & Context (Steps 1-3)
+### Phase 1: Foundation and Context (Steps 1-3)
 
-**Mode Selection & Input Gathering**
+**Mode Selection and Input Gathering**
 
 - Choose operational mode (Interactive, Express, YOLO)
 - Check for and optionally load existing brainstorming results
@@ -101,7 +101,7 @@ module-brief/
 - Define input-process-output flows for each workflow
 - Assess complexity levels and implementation priorities
 
-### Phase 3: Validation & User Experience (Steps 6-7)
+### Phase 3: Validation and User Experience (Steps 6-7)
 
 **User Journey Mapping**
 
@@ -110,7 +110,7 @@ module-brief/
 - Validate end-to-end functionality and value delivery
 - Identify potential friction points and optimization opportunities
 
-**Technical Planning & Requirements**
+**Technical Planning and Requirements**
 
 - Assess data requirements and storage needs
 - Map integration points with other modules and external systems
@@ -133,27 +133,27 @@ module-brief/
 - Prioritize features and capabilities by value and complexity
 - Create clear milestones and success checkpoints
 
-### Phase 5: Enhancement & Risk Management (Steps 10-12)
+### Phase 5: Enhancement and Risk Management (Steps 10-12)
 
-**Creative Features & Special Touches** (Optional)
+**Creative Features and Special Touches** (Optional)
 
 - Design easter eggs and delightful user interactions
 - Plan module lore and thematic consistency
 - Add personality quirks and creative responses
 - Develop backstories and universe building
 
-**Risk Assessment & Mitigation**
+**Risk Assessment and Mitigation**
 
 - Identify technical, usability, and scope risks
 - Develop mitigation strategies for each risk category
 - Plan contingency approaches for potential challenges
 - Document decision points and alternative paths
 
-**Final Review & Export Preparation**
+**Final Review and Export Preparation**
 
 - Comprehensive review of all brief sections
 - Validation against quality and completeness criteria
-- Preparation for seamless handoff to build-module workflow
+- Preparation for seamless handoff to create-module workflow
 - Export readiness confirmation with actionable specifications
 
 ## Output
@@ -161,7 +161,7 @@ module-brief/
 ### Generated Files
 
 - **Module Brief Document**: Comprehensive planning document at `{output_folder}/module-brief-{module_code}-{date}.md`
-- **Strategic Specifications**: Ready-to-implement blueprint for build-module workflow
+- **Strategic Specifications**: Ready-to-implement blueprint for create-module workflow
 
 ### Output Structure
 
@@ -178,7 +178,7 @@ The module brief contains detailed specifications across multiple sections:
 9. **Creative Features** - Special touches, easter eggs, module lore
 10. **Risk Assessment** - Technical, usability, scope risks with mitigation
 11. **Implementation Notes** - Priority order, design decisions, open questions
-12. **Resources & References** - Inspiration sources, similar modules, technical references
+12. **Resources and References** - Inspiration sources, similar modules, technical references
 
 ## Requirements
 
@@ -203,7 +203,7 @@ The module brief contains detailed specifications across multiple sections:
 
 ### After Completion
 
-1. **Use as Blueprint** - Feed the brief directly into build-module workflow for implementation
+1. **Use as Blueprint** - Feed the brief directly into create-module workflow for implementation
 2. **Review with Stakeholders** - Validate assumptions and gather feedback before building
 3. **Update as Needed** - Treat as living document that evolves with implementation learnings
 4. **Reference During Development** - Use as north star for design decisions and scope management
@@ -254,10 +254,10 @@ 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`
 - Study existing module examples in `/bmad/` for patterns and inspiration
 - Validate output using `checklist.md`
-- Consult module structure guide at `build-module/module-structure.md`
+- Consult module structure guide at `create-module/module-structure.md`
 
 ---
 

src/modules/bmb/workflows/module-brief/checklist.md

@@ -8,7 +8,7 @@
 - [ ] Target users are clearly defined
 - [ ] Unique value proposition is articulated
 
-## Vision & Concept
+## Vision and Concept
 
 - [ ] Problem being solved is clearly stated
 - [ ] Solution approach is explained
@@ -80,9 +80,9 @@
 
 ## Implementation Readiness
 
-- [ ] Brief provides enough detail for build-module workflow
-- [ ] Agent specifications sufficient for build-agent workflow
-- [ ] Workflow descriptions ready for build-workflow
+- [ ] Brief provides enough detail for create-module workflow
+- [ ] Agent specifications sufficient for create-agent workflow
+- [ ] Workflow descriptions ready for create-workflow
 - [ ] Resource requirements are clear
 - [ ] Success metrics are measurable
 

src/modules/bmb/workflows/module-brief/instructions.md

@@ -249,15 +249,15 @@ For each risk, note mitigation strategy.
 
 <step n="12" goal="Final review and export readiness">
 <action>Review all sections with user</action>
-<action>Ensure module brief is ready for build-module workflow</action>
+<action>Ensure module brief is ready for create-module workflow</action>
 
 Ask if they want to:
 
-1. Proceed directly to build-module workflow
+1. Proceed directly to create-module workflow
 2. Save and refine later
 3. Generate additional planning documents
 
-<action>Highlight that this brief can be fed directly into build-module workflow!</action>
+<action>Highlight that this brief can be fed directly into create-module workflow!</action>
 
 <template-output>final_brief</template-output>
 </step>

src/modules/bmb/workflows/module-brief/template.md

@@ -144,7 +144,7 @@ How we'll know the module is successful:
 **Deliverables:**
 {{phase2_deliverables}}
 
-### Phase 3: Polish & Optimization
+### Phase 3: Polish and Optimization
 
 **Timeline:** {{phase3_timeline}}
 
@@ -161,11 +161,11 @@ How we'll know the module is successful:
 
 {{creative_features}}
 
-### Easter Eggs & Delighters
+### Easter Eggs and Delighters
 
 {{easter_eggs}}
 
-### Module Lore & Theming
+### Module Lore and Theming
 
 {{module_lore}}
 
@@ -209,7 +209,7 @@ How we'll know the module is successful:
 
 ---
 
-## Resources & References
+## Resources and References
 
 ### Inspiration Sources
 
@@ -235,7 +235,7 @@ How we'll know the module is successful:
 
 {{detailed_workflow_specs}}
 
-### C. Data Structures & Schemas
+### C. Data Structures and Schemas
 
 {{data_schemas}}
 
@@ -248,14 +248,14 @@ How we'll know the module is successful:
 ## Next Steps
 
 1. **Review this brief** with stakeholders
-2. **Run build-module workflow** using this brief as input
-3. **Create first agent** using build-agent workflow
-4. **Develop initial workflows** using build-workflow
+2. **Run create-module workflow** using this brief as input
+3. **Create first agent** using create-agent workflow
+4. **Develop initial workflows** using create-workflow
 5. **Test MVP** with target users
 
 ---
 
-_This Module Brief is ready to be fed directly into the build-module workflow for scaffolding and implementation._
+_This Module Brief is ready to be fed directly into the create-module workflow for scaffolding and implementation._
 
 **Module Viability Score:** {{viability_score}}/10
 **Estimated Development Effort:** {{effort_estimate}}

src/modules/bmb/workflows/module-brief/workflow.yaml

@@ -15,7 +15,7 @@ date: system-generated
 recommended_inputs:
   - brainstorming_results: "{output_folder}/brainstorming-*.md"
   - existing_modules: "{project-root}/bmad/"
-  - module_examples: "{project-root}/bmad/bmb/workflows/build-module/module-structure.md"
+  - module_examples: "{project-root}/bmad/bmb/workflows/create-module/module-structure.md"
 
 # Module path and component files
 installed_path: "{project-root}/bmad/bmb/workflows/module-brief"
@@ -26,5 +26,11 @@ validation: "{installed_path}/checklist.md"
 # Output configuration
 default_output_file: "{output_folder}/module-brief-{{module_code}}-{{date}}.md"
 
-# No special tools required
-required_tools: []
+web_bundle:
+  name: "module-brief"
+  description: "Create a comprehensive Module Brief that serves as the blueprint for building new BMAD modules using strategic analysis and creative vision"
+  author: "BMad Builder"
+  web_bundle_files:
+    - "bmad/bmb/workflows/module-brief/instructions.md"
+    - "bmad/bmb/workflows/module-brief/template.md"
+    - "bmad/bmb/workflows/module-brief/checklist.md"

src/modules/bmb/workflows/redoc/checklist.md

@@ -1,6 +1,6 @@
 # ReDoc Workflow Validation Checklist
 
-## Initialization & Setup
+## Initialization and Setup
 
 - [ ] All BMAD convention documents loaded and understood
 - [ ] Target path validated and exists
@@ -66,7 +66,7 @@
 - [ ] Frontmatter syntax is correct and dates are current
 - [ ] No redundant explanation of standard BMAD patterns
 
-## Validation & Reporting
+## Validation and Reporting
 
 - [ ] All planned documentation items created/updated
 - [ ] Frontmatter dates verified as current across all files

src/modules/bmb/workflows/redoc/workflow.yaml

@@ -29,5 +29,10 @@ validation: "{installed_path}/checklist.md"
 # Configuration
 autonomous: true # Runs without user checkpoints unless clarification needed
 
-# Tool Requirements - Using built-in file system tools
-required_tools: []
+web_bundle:
+  name: "redoc"
+  description: "Autonomous documentation system that maintains module, workflow, and agent documentation using a reverse-tree approach (leaf folders first, then parents). Understands BMAD conventions and produces technical writer quality output."
+  author: "BMad"
+  web_bundle_files:
+    - "bmad/bmb/workflows/redoc/instructions.md"
+    - "bmad/bmb/workflows/redoc/checklist.md"