bmad-method 6.0.0-alpha.0 → 6.0.0-alpha.2

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

@@ -1,15 +1,13 @@
 # Build Agent Workflow Configuration
-name: build-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"
+name: create-agent
+description: "Interactive workflow to build BMAD Core compliant agents (YAML source compiled to .md during install) with optional brainstorming, persona development, and command structure"
 author: "BMad"
 
 # Critical variables load from config_source
 config_source: "{project-root}/bmad/bmb/config.yaml"
-output_folder: "{config_source}:output_folder"
+custom_agent_location: "{config_source}:custom_agent_location"
 user_name: "{config_source}:user_name"
-src_impact: "{config_source}:src_impact"
 communication_language: "{config_source}:communication_language"
-date: system-generated
 
 # Technical documentation for agent building
 agent_types: "{installed_path}/agent-types.md"
@@ -23,17 +21,29 @@ 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"
 
-# Output configuration - dynamic based on src_impact and agent type
-# If src_impact=true: Save to src/modules/{{target_module}}/agents/
-# If src_impact=false: Save to output_folder/agents/
-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"
+# Output configuration - YAML agents compiled to .md at install time
+# Module agents: Save to bmad/{{target_module}}/agents/
+# Standalone agents: Save to custom_agent_location/
+module_output_file: "{project-root}/bmad/{{target_module}}/agents/{{agent_filename}}.agent.yaml"
+standalone_output_file: "{custom_agent_location}/{{agent_filename}}.agent.yaml"
+# Optional user override file (auto-created by installer if missing)
+config_output_file: "{project-root}/bmad/_cfg/agents/{{target_module}}-{{agent_filename}}.customize.yaml"
 
-# No special tools required for agent building
-required_tools: []
+standalone: true
+
+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"

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

@@ -8,31 +8,31 @@ 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
 
 The workflow loads critical variables from the BMB configuration:
 
-- **output_folder**: Where the module will be created
+- **custom_module_location**: Where custom modules are created (default: `bmad/`)
 - **user_name**: Module author information
 - **date**: Automatic timestamp for versioning
 
@@ -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
@@ -79,7 +79,7 @@ build-module/
 
 **Module Configuration**
 
-- Generates main config.yaml with module metadata
+- Defines configuration questions in install-config.yaml (config.yaml generated during installation)
 - Configures component counts and references
 - Sets up output and data folder specifications
 
@@ -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,11 +97,11 @@ 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**
 
-- Creates install-module-config.yaml for deployment
+- Creates install-config.yaml with configuration questions for deployment
 - Sets up optional installer.js for complex installation logic
 - Configures post-install messaging and instructions
 
@@ -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**
 
@@ -125,7 +125,9 @@ build-module/
 ### Generated Files
 
 - **Module Directory**: Complete module structure at `{project-root}/bmad/{module_code}/`
-- **Configuration Files**: config.yaml, install-module-config.yaml
+- **Configuration Files**:
+  - Source: install-config.yaml (configuration questions)
+  - Target: config.yaml (generated from user answers during installation)
 - **Documentation**: README.md, TODO.md development roadmap
 - **Component Placeholders**: Structured folders for agents, workflows, and tasks
 
@@ -144,7 +146,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 +160,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,12 +181,12 @@ 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
 
-- **Solution**: Review install-module-config.yaml syntax and paths
+- **Solution**: Review install-config.yaml syntax and paths
 - **Check**: Ensure all referenced paths use {project-root} variables correctly
 
 ## Customization
@@ -200,7 +202,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,11 +210,11 @@ 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
 
 ---
 
-_Part of the BMad Method v5 - BMB (Builder) Module_
+_Part of the BMad Method v6 - BMB (Builder) Module_

package/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)

package/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
 
@@ -26,16 +26,15 @@
 - [ ] `/tasks` directory exists (if tasks planned)
 - [ ] `/templates` directory exists (if templates used)
 - [ ] `/data` directory exists (if data files needed)
-- [ ] `config.yaml` present in module root
+- [ ] `/_module-installer/install-config.yaml` present (defines configuration questions)
 - [ ] `README.md` present with documentation
 
-### Runtime Directories (bmad/{module-code}/)
+### Installed Module Structure (generated in target after installation)
 
-- [ ] `/_module-installer` directory created
+- [ ] `/agents` directory for compiled agents
+- [ ] `/workflows` directory for workflow instances
 - [ ] `/data` directory for user data
-- [ ] `/agents` directory for overrides
-- [ ] `/workflows` directory for instances
-- [ ] Runtime `config.yaml` present
+- [ ] `config.yaml` generated from install-config.yaml during installation
 
 ## Component Planning
 
@@ -63,22 +62,22 @@
 
 ## Configuration Files
 
-### Module config.yaml
+### Installation Configuration (install-config.yaml)
 
-- [ ] All required fields present (name, code, version, author)
-- [ ] Component lists accurate (agents, workflows, tasks)
-- [ ] Paths use proper variables ({project-root}, etc.)
-- [ ] Output folders configured
-- [ ] Custom settings documented
+- [ ] `install-config.yaml` exists in `_module-installer`
+- [ ] Module metadata present (code, name, version)
+- [ ] Configuration questions defined for user input
+- [ ] Default values provided for all questions
+- [ ] Prompt text is clear and helpful
+- [ ] Result templates use proper variable substitution
+- [ ] Paths use proper variables ({project-root}, {value}, etc.)
 
-### Install Configuration
+### Generated Config (config.yaml in target)
 
-- [ ] `install-module-config.yaml` exists in `_module-installer`
-- [ ] Installation steps defined
-- [ ] Directory creation steps present
-- [ ] File copy operations specified
-- [ ] Module registration included
-- [ ] Post-install message defined
+- [ ] Generated during installation from install-config.yaml
+- [ ] Contains all user-provided configuration values
+- [ ] Module metadata included
+- [ ] No config.yaml should exist in source module
 
 ## Installation Infrastructure
 
@@ -165,7 +164,7 @@
 - [ ] Component organization is logical
 - [ ] No hard-coded limits
 
-## Testing & Validation
+## Testing and Validation
 
 ### Structural Validation
 

package/src/modules/bmb/workflows/create-module/installer-templates/install-config.yaml

@@ -0,0 +1,92 @@
+# {{MODULE_NAME}} Module Configuration
+# This file defines installation questions and module configuration values
+
+code: "{{MODULE_CODE}}"
+name: "{{MODULE_NAME}}"
+default_selected: "{{DEFAULT_SELECTED}}" # true if this should be selected by default
+
+# Welcome message shown during installation
+prompt:
+  - "{{WELCOME_MESSAGE_LINE_1}}"
+  - "{{WELCOME_MESSAGE_LINE_2}}"
+# Core config values are automatically inherited:
+## user_name
+## communication_language
+## document_output_language
+## output_folder
+
+# ============================================================================
+# CONFIGURATION FIELDS
+# ============================================================================
+#
+# Each field can be:
+# 1. INTERACTIVE (has 'prompt' - asks user during installation)
+# 2. STATIC (no 'prompt' - just uses 'result' value)
+#
+# Field structure:
+#   field_name:
+#     prompt: "Question to ask user" (optional - omit for static values)
+#     default: "default_value" (optional)
+#     result: "{value}" or "static-value"
+#     single-select: [...] (optional - for dropdown)
+#     multi-select: [...] (optional - for checkboxes)
+#
+# Special placeholders in result:
+#   {value} - replaced with user's answer
+#   {project-root} - replaced with project root path
+#   {directory_name} - replaced with project directory name
+#   {module_code} - replaced with this module's code
+# ============================================================================
+
+# EXAMPLE: Interactive text input
+# example_project_name:
+#   prompt: "What is your project name?"
+#   default: "{directory_name}"
+#   result: "{value}"
+
+# EXAMPLE: Interactive single-select dropdown
+# example_skill_level:
+#   prompt: "What is your experience level?"
+#   default: "intermediate"
+#   result: "{value}"
+#   single-select:
+#     - value: "beginner"
+#       label: "Beginner - New to this domain"
+#     - value: "intermediate"
+#       label: "Intermediate - Familiar with basics"
+#     - value: "expert"
+#       label: "Expert - Deep knowledge"
+
+# EXAMPLE: Interactive multi-select checkboxes
+# example_features:
+#   prompt:
+#     - "Which features do you want to enable?"
+#     - "(Select all that apply)"
+#   result: "{value}"
+#   multi-select:
+#     - "Feature A"
+#     - "Feature B"
+#     - "Feature C"
+
+# EXAMPLE: Interactive path input
+# example_output_path:
+#   prompt: "Where should outputs be saved?"
+#   default: "output/{{MODULE_CODE}}"
+#   result: "{project-root}/{value}"
+
+# EXAMPLE: Static value (no user prompt)
+# example_static_setting:
+#   result: "hardcoded-value"
+
+# EXAMPLE: Static path
+# module_data_path:
+#   result: "{project-root}/bmad/{{MODULE_CODE}}/data"
+
+# ============================================================================
+# YOUR MODULE CONFIGURATION FIELDS
+# ============================================================================
+# Replace examples above with your module's actual configuration needs.
+# Delete this comment block and the examples when implementing.
+# ============================================================================
+
+# TODO: INSERT {MODULE_CONFIG_FIELDS} HERE

package/src/modules/bmb/workflows/create-module/installer-templates/installer.js

@@ -178,7 +178,7 @@ async function initDatabase(/* config */) {
   console.log('   Initializing database...');
 
   // TODO: Add database initialization
-  // This function can be called from install-module-config.yaml
+  // This function can be called from install-config.yaml
 
   console.log('   ✓ Database initialized');
 }