bmad-method 6.0.0-alpha.1 → 6.0.0-alpha.10

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

@@ -15,12 +15,8 @@ date: system-generated
 # optional, can be omitted
 brain_techniques: "{installed_path}/{critical-data-file.csv}" # example, can be other formats or URLs
 
-# Optional docs that if loaded on start to kickstart this workflow or used at some point, these are meant to be suggested inputs for the user
-recommended_inputs: # optional, can be omitted
-  - example_input: "{project-root}/{path/to/file.md}"
-
 # Module path and component files
-installed_path: "{project-root}/bmad/{module-code}/workflows/{workflow-code}"
+installed_path: "{project-root}/{bmad_folder}/{module-code}/workflows/{workflow-code}"
 template: "{installed_path}/template.md" # optional, can be omitted
 instructions: "{installed_path}/instructions.md" # optional, can be omitted
 validation: "{installed_path}/checklist.md" # optional, can be omitted
@@ -43,23 +39,23 @@ web_bundle: #optional, can be omitted
   description: "{WORKFLOW_DESCRIPTION}"
   author: "BMad"
 
-  # Core workflow files (paths relative to bmad/ root)
-  instructions: "bmad/{module-code}/workflows/{workflow-code}/instructions.md"
-  validation: "bmad/{module-code}/workflows/{workflow-code}/checklist.md"
-  template: "bmad/{module-code}/workflows/{workflow-code}/template.md" # if document workflow
+  # Core workflow files (paths relative to {bmad_folder}/ root)
+  instructions: "{bmad_folder}/{module-code}/workflows/{workflow-code}/instructions.md"
+  validation: "{bmad_folder}/{module-code}/workflows/{workflow-code}/checklist.md"
+  template: "{bmad_folder}/{module-code}/workflows/{workflow-code}/template.md" # if document workflow
 
   # Reference any data files or additional workflows (no config_source allowed)
-  # brain_techniques: "bmad/{module-code}/workflows/{workflow-code}/data-file.csv"
-  # sub_workflow: "bmad/{module-code}/workflows/other-workflow/workflow.yaml"
+  # brain_techniques: "{bmad_folder}/{module-code}/workflows/{workflow-code}/data-file.csv"
+  # sub_workflow: "{bmad_folder}/{module-code}/workflows/other-workflow/workflow.yaml"
 
   # CRITICAL: List ALL files used by this workflow
   # This includes instructions, validation, templates, data files,
   # and any files referenced within those files
   web_bundle_files:
-    - "bmad/{module-code}/workflows/{workflow-code}/instructions.md"
-    - "bmad/{module-code}/workflows/{workflow-code}/checklist.md"
-    - "bmad/{module-code}/workflows/{workflow-code}/template.md"
+    - "{bmad_folder}/{module-code}/workflows/{workflow-code}/instructions.md"
+    - "{bmad_folder}/{module-code}/workflows/{workflow-code}/checklist.md"
+    - "{bmad_folder}/{module-code}/workflows/{workflow-code}/template.md"
     # Add ALL referenced files here - examine instructions.md and template.md
     # for any file paths and include them all
-    # - "bmad/{module-code}/workflows/{workflow-code}/data/example.csv"
-    # - "bmad/{module-code}/templates/shared-template.md"
+    # - "{bmad_folder}/{module-code}/workflows/{workflow-code}/data/example.csv"
+    # - "{bmad_folder}/{module-code}/templates/shared-template.md"

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

@@ -4,7 +4,7 @@ description: "Interactive workflow builder that guides creation of new BMAD work
 author: "BMad Builder"
 
 # Critical variables
-config_source: "{project-root}/bmad/bmb/config.yaml"
+config_source: "{project-root}/{bmad_folder}/bmb/config.yaml"
 custom_workflow_location: "{config_source}:custom_workflow_location"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -15,13 +15,8 @@ template_instructions: "{workflow_template_path}/instructions.md"
 template_template: "{workflow_template_path}/template.md"
 template_checklist: "{workflow_template_path}/checklist.md"
 
-# Optional input docs
-recommended_inputs:
-  - existing_workflows: "{project-root}/bmad/*/workflows/"
-  - bmm_workflows: "{project-root}/bmad/bmm/workflows/"
-
 # Module path and component files
-installed_path: "{project-root}/bmad/bmb/workflows/create-workflow"
+installed_path: "{project-root}/{bmad_folder}/bmb/workflows/create-workflow"
 template: false # This is an action workflow - no template needed
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
@@ -30,10 +25,14 @@ validation: "{installed_path}/checklist.md"
 workflow_creation_guide: "{installed_path}/workflow-creation-guide.md"
 workflow_template_path: "{installed_path}/workflow-template"
 
+# Reference examples - for learning patterns
+existing_workflows_dir: "{project-root}/{bmad_folder}/*/workflows/"
+bmm_workflows_dir: "{project-root}/{bmad_folder}/bmm/workflows/"
+
 # Output configuration - Creates the new workflow folder with all files
 # If workflow belongs to a module: Save to module's workflows folder
 # If standalone workflow: Save to custom_workflow_location/{{workflow_name}}
-module_output_folder: "{project-root}/bmad/{{target_module}}/workflows/{{workflow_name}}"
+module_output_folder: "{project-root}/{bmad_folder}/{{target_module}}/workflows/{{workflow_name}}"
 standalone_output_folder: "{custom_workflow_location}/{{workflow_name}}"
 
 standalone: true

package/src/modules/bmb/workflows/edit-agent/checklist.md

@@ -46,7 +46,7 @@ Use this checklist to validate agent edits meet BMAD Core standards.
 ## Menu Handler Validation
 
 - [ ] menu-handlers section is present
-- [ ] Workflow handler loads {project-root}/bmad/core/tasks/workflow.xml
+- [ ] Workflow handler loads {project-root}/{bmad_folder}/core/tasks/workflow.xml
 - [ ] Workflow handler passes yaml path as 'workflow-config' parameter
 - [ ] Handlers check for attributes (workflow, exec, tmpl, data, action)
 - [ ] Handler logic is complete and follows patterns

package/src/modules/bmb/workflows/edit-agent/instructions.md

@@ -1,7 +1,7 @@
 # Edit Agent - Agent Editor Instructions
 
-<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project-root}/bmad/bmb/workflows/edit-agent/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmb/workflows/edit-agent/workflow.yaml</critical>
 <critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication based on context and user needs</critical>
 <critical>The goal is COLLABORATIVE IMPROVEMENT - work WITH the user, not FOR them</critical>
 <critical>Communicate all responses in {communication_language}</critical>

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

@@ -4,27 +4,25 @@ description: "Edit existing BMAD agents while following all best practices and c
 author: "BMad"
 
 # Critical variables load from config_source
-config_source: "{project-root}/bmad/bmb/config.yaml"
+config_source: "{project-root}/{bmad_folder}/bmb/config.yaml"
 communication_language: "{config_source}:communication_language"
 user_name: "{config_source}:user_name"
 
 # Required Data Files - Critical for understanding agent conventions
-agent_types: "{project-root}/bmad/bmb/workflows/create-agent/agent-types.md"
-agent_architecture: "{project-root}/bmad/bmb/workflows/create-agent/agent-architecture.md"
-agent_commands: "{project-root}/bmad/bmb/workflows/create-agent/agent-command-patterns.md"
-communication_styles: "{project-root}/bmad/bmb/workflows/create-agent/communication-styles.md"
+agent_types: "{project-root}/{bmad_folder}/bmb/workflows/create-agent/agent-types.md"
+agent_architecture: "{project-root}/{bmad_folder}/bmb/workflows/create-agent/agent-architecture.md"
+agent_commands: "{project-root}/{bmad_folder}/bmb/workflows/create-agent/agent-command-patterns.md"
+communication_styles: "{project-root}/{bmad_folder}/bmb/workflows/create-agent/communication-styles.md"
 
 # Workflow execution engine reference
-workflow_execution_engine: "{project-root}/bmad/core/tasks/workflow.xml"
+workflow_execution_engine: "{project-root}/{bmad_folder}/core/tasks/workflow.xml"
 
-# Optional docs that can be used to understand the target agent
-recommended_inputs:
-  - target_agent: "Path to the agent.yaml or agent.md file to edit"
-  - example_agents: "{project-root}/bmad/bmm/agents/"
-  - agent_activation_rules: "{project-root}/src/utility/models/agent-activation-ide.xml"
+# Reference examples and conventions
+example_agents_dir: "{project-root}/{bmad_folder}/bmm/agents/"
+agent_activation_rules: "{project-root}/src/utility/models/agent-activation-ide.xml"
 
 # Module path and component files
-installed_path: "{project-root}/bmad/bmb/workflows/edit-agent"
+installed_path: "{project-root}/{bmad_folder}/bmb/workflows/edit-agent"
 template: false # This is an action workflow - no template needed
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"

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

@@ -106,7 +106,7 @@ Modules can share workflows:
 
 ```yaml
 # In agent menu item:
-workflow: '{project-root}/bmad/other-module/workflows/shared-workflow/workflow.yaml'
+workflow: '{project-root}/{bmad_folder}/other-module/workflows/shared-workflow/workflow.yaml'
 ```
 
 Common patterns:
@@ -151,7 +151,7 @@ Changes are reviewed and approved by you before being applied.
 - Can configure web bundles
 - Are the development source of truth
 
-**Installed modules** (in bmad/):
+**Installed modules** (in {bmad_folder}/):
 
 - Are deployed to target projects
 - Use config.yaml for user customization

package/src/modules/bmb/workflows/edit-module/checklist.md

@@ -5,7 +5,7 @@ Use this checklist to validate module edits meet BMAD Core standards.
 ## Module Structure Validation
 
 - [ ] Module has clear 3-letter code (bmm, bmb, cis, etc.)
-- [ ] Module is in correct location (src/modules/ for source, bmad/ for installed)
+- [ ] Module is in correct location (src/modules/ for source, {bmad_folder}/ for installed)
 - [ ] agents/ directory exists
 - [ ] workflows/ directory exists
 - [ ] config.yaml exists in module root
@@ -128,7 +128,7 @@ Use this checklist to validate module edits meet BMAD Core standards.
 
 - [ ] Web bundles configured in workflow.yaml files
 - [ ] All referenced files included in web_bundle_files
-- [ ] Paths are bmad/-relative (not project-root)
+- [ ] Paths are {bmad_folder}/-relative (not project-root)
 - [ ] No config_source references in web bundles
 - [ ] Invoked workflows included in dependencies
 

package/src/modules/bmb/workflows/edit-module/instructions.md

@@ -1,7 +1,7 @@
 # Edit Module - Module Editor Instructions
 
-<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project-root}/bmad/bmb/workflows/edit-module/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmb/workflows/edit-module/workflow.yaml</critical>
 <critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication based on context and user needs</critical>
 <critical>The goal is COLLABORATIVE IMPROVEMENT - work WITH the user, not FOR them</critical>
 <critical>Communicate all responses in {communication_language}</critical>
@@ -9,7 +9,7 @@
 <workflow>
 
 <step n="1" goal="Load and deeply understand the target module">
-<ask>What is the path to the module you want to edit? (provide path to module directory like bmad/bmm/ or src/modules/bmm/)</ask>
+<ask>What is the path to the module you want to edit? (provide path to module directory like {bmad_folder}/bmm/ or src/modules/bmm/)</ask>
 
 <action>Load the module directory structure completely:
 
@@ -123,7 +123,9 @@ Let the conversation flow naturally. Build a shared vision of what "better" look
 2. **Propose improvements with rationale**
    - Suggest specific changes that align with best practices
    - Explain WHY each change helps
-   - Provide examples from reference modules when helpful
+   - Provide examples from reference modules: {bmm_module_dir}, {bmb_module_dir}, {cis_module_dir}
+   - Reference agents from: {existing_agents_dir}
+   - Reference workflows from: {existing_workflows_dir}
    - Reference the structure guide's patterns naturally
 
 3. **Collaborate on the approach**
@@ -185,7 +187,7 @@ Let the conversation flow naturally. Build a shared vision of what "better" look
 **If setting up cross-module integration:**
 
 - Identify which workflows from other modules are needed
-- Show how to reference workflows properly: {project-root}/bmad/{{module}}/workflows/{{workflow}}/workflow.yaml
+- Show how to reference workflows properly: {project-root}/{bmad_folder}/{{module}}/workflows/{{workflow}}/workflow.yaml
 - Document the integration in README
 - Ensure dependencies are clear
 - Consider adding example usage

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

@@ -4,28 +4,26 @@ description: "Edit existing BMAD modules (structure, agents, workflows, document
 author: "BMad"
 
 # Critical variables load from config_source
-config_source: "{project-root}/bmad/bmb/config.yaml"
+config_source: "{project-root}/{bmad_folder}/bmb/config.yaml"
 communication_language: "{config_source}:communication_language"
 user_name: "{config_source}:user_name"
 
 # Required Data Files - Critical for understanding module conventions
-module_structure_guide: "{project-root}/bmad/bmb/workflows/create-module/module-structure.md"
+module_structure_guide: "{project-root}/{bmad_folder}/bmb/workflows/create-module/module-structure.md"
 
 # Related workflow editors
-agent_editor: "{project-root}/bmad/bmb/workflows/edit-agent/workflow.yaml"
-workflow_editor: "{project-root}/bmad/bmb/workflows/edit-workflow/workflow.yaml"
+agent_editor: "{project-root}/{bmad_folder}/bmb/workflows/edit-agent/workflow.yaml"
+workflow_editor: "{project-root}/{bmad_folder}/bmb/workflows/edit-workflow/workflow.yaml"
 
-# Optional docs that can be used to understand the target module
-recommended_inputs:
-  - target_module: "Path to the module directory to edit"
-  - bmm_module: "{project-root}/bmad/bmm/"
-  - bmb_module: "{project-root}/bmad/bmb/"
-  - cis_module: "{project-root}/bmad/cis/"
-  - existing_agents: "{project-root}/bmad/*/agents/"
-  - existing_workflows: "{project-root}/bmad/*/workflows/"
+# Reference examples - for learning patterns
+bmm_module_dir: "{project-root}/{bmad_folder}/bmm/"
+bmb_module_dir: "{project-root}/{bmad_folder}/bmb/"
+cis_module_dir: "{project-root}/{bmad_folder}/cis/"
+existing_agents_dir: "{project-root}/{bmad_folder}/*/agents/"
+existing_workflows_dir: "{project-root}/{bmad_folder}/*/workflows/"
 
 # Module path and component files
-installed_path: "{project-root}/bmad/bmb/workflows/edit-module"
+installed_path: "{project-root}/{bmad_folder}/bmb/workflows/edit-module"
 template: false # This is an action workflow - no template needed
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"

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

@@ -1,7 +1,7 @@
 # Edit Workflow - Workflow Editor Instructions
 
-<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project-root}/bmad/bmb/workflows/edit-workflow/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmb/workflows/edit-workflow/workflow.yaml</critical>
 <critical>This workflow uses ADAPTIVE FACILITATION - adjust your communication based on context and user needs</critical>
 <critical>The goal is COLLABORATIVE IMPROVEMENT - work WITH the user, not FOR them</critical>
 <critical>Communicate all responses in {communication_language}</critical>
@@ -24,7 +24,7 @@
 
 - Workflow creation guide: {workflow_creation_guide}
 - Workflow execution engine: {workflow_execution_engine}
-- Study example workflows from: {project-root}/bmad/bmm/workflows/
+- Study example workflows from: {workflow_examples_dir}
   </action>
 
 <action>Analyze the workflow deeply:
@@ -205,7 +205,7 @@ Let the conversation flow naturally. Build a shared vision of what "better" look
 
 - Identify all files the workflow depends on
 - Check for invoked workflows (must be included)
-- Verify paths are bmad/-relative
+- Verify paths are {bmad_folder}/-relative
 - Remove config_source dependencies
 - Build complete file list
 

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

@@ -4,21 +4,19 @@ description: "Edit existing BMAD workflows while following all best practices an
 author: "BMad"
 
 # Critical variables load from config_source
-config_source: "{project-root}/bmad/bmb/config.yaml"
+config_source: "{project-root}/{bmad_folder}/bmb/config.yaml"
 communication_language: "{config_source}:communication_language"
 user_name: "{config_source}:user_name"
 
 # Required Data Files - Critical for understanding workflow conventions
-workflow_creation_guide: "{project-root}/bmad/bmb/workflows/create-workflow/workflow-creation-guide.md"
-workflow_execution_engine: "{project-root}/bmad/core/tasks/workflow.xml"
+workflow_creation_guide: "{project-root}/{bmad_folder}/bmb/workflows/create-workflow/workflow-creation-guide.md"
+workflow_execution_engine: "{project-root}/{bmad_folder}/core/tasks/workflow.xml"
 
-# Optional docs that can be used to understand the target workflow
-recommended_inputs:
-  - target_workflow: "Path to the workflow.yaml file to edit"
-  - workflow_examples: "{project-root}/bmad/bmm/workflows/"
+# Reference examples
+workflow_examples_dir: "{project-root}/{bmad_folder}/bmm/workflows/"
 
 # Module path and component files
-installed_path: "{project-root}/bmad/bmb/workflows/edit-workflow"
+installed_path: "{project-root}/{bmad_folder}/bmb/workflows/edit-workflow"
 template: false # This is an action workflow - no template needed
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"

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

@@ -254,8 +254,8 @@ To customize this workflow:
 
 For issues or questions:
 
-- 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
+- Review the workflow creation guide at `/{bmad_folder}/bmb/workflows/create-workflow/workflow-creation-guide.md`
+- Study existing module examples in `/{bmad_folder}/` for patterns and inspiration
 - Validate output using `checklist.md`
 - Consult module structure guide at `create-module/module-structure.md`
 

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

@@ -112,5 +112,5 @@
 
 **Validation Complete:** ⬜ Yes / ⬜ With Issues / ⬜ Needs Revision
 
-**Validated By:** **\*\*\*\***\_**\*\*\*\***
-**Date:** **\*\*\*\***\_**\*\*\*\***
+**Validated By:** {name}
+**Date:** {date}

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

@@ -1,8 +1,9 @@
 # Module Brief Instructions
 
-<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project-root}/bmad/bmb/workflows/module-brief/workflow.yaml</critical>
+<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project-root}/{bmad_folder}/bmb/workflows/module-brief/workflow.yaml</critical>
 <critical>Communicate in {communication_language} throughout the module brief creation process</critical>
+<critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
 
 <workflow>
 

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

@@ -4,20 +4,25 @@ description: "Create a comprehensive Module Brief that serves as the blueprint f
 author: "BMad Builder"
 
 # Critical variables
-config_source: "{project-root}/bmad/bmb/config.yaml"
+config_source: "{project-root}/{bmad_folder}/bmb/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 date: system-generated
 
-# Optional input docs that enhance module planning
-recommended_inputs:
-  - brainstorming_results: "{output_folder}/brainstorming-*.md"
-  - existing_modules: "{project-root}/bmad/"
-  - module_examples: "{project-root}/bmad/bmb/workflows/create-module/module-structure.md"
+# Reference examples and documentation
+existing_modules_dir: "{project-root}/{bmad_folder}/"
+module_structure_guide: "{project-root}/{bmad_folder}/bmb/workflows/create-module/module-structure.md"
+
+# Optional user inputs - discovered if they exist
+input_file_patterns:
+  brainstorming:
+    description: "Brainstorming session outputs (optional)"
+    whole: "{output_folder}/brainstorming-*.md"
+    load_strategy: "FULL_LOAD"
 
 # Module path and component files
-installed_path: "{project-root}/bmad/bmb/workflows/module-brief"
+installed_path: "{project-root}/{bmad_folder}/bmb/workflows/module-brief"
 template: "{installed_path}/template.md"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"

package/src/modules/bmb/workflows/redoc/README.md

@@ -28,11 +28,11 @@ workflow redoc
 
 When prompted, provide one of:
 
-- **Module path**: `bmad/bmm` (documents entire module: root, workflows, agents)
-- **Workflows folder**: `bmad/bmm/workflows` (documents all workflows)
-- **Agents folder**: `bmad/bmm/agents` (documents all agents)
-- **Single workflow**: `bmad/bmm/workflows/product-brief` (documents one workflow)
-- **Single agent**: `bmad/bmm/agents/prd-agent.md` (documents one agent)
+- **Module path**: `{bmad_folder}/bmm` (documents entire module: root, workflows, agents)
+- **Workflows folder**: `{bmad_folder}/bmm/workflows` (documents all workflows)
+- **Agents folder**: `{bmad_folder}/bmm/agents` (documents all agents)
+- **Single workflow**: `{bmad_folder}/bmm/workflows/product-brief` (documents one workflow)
+- **Single agent**: `{bmad_folder}/bmm/agents/prd-agent.md` (documents one agent)
 
 ## Inputs
 

package/src/modules/bmb/workflows/redoc/instructions.md

@@ -1,6 +1,6 @@
 # ReDoc Workflow Instructions
 
-<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
+<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {project-root}/src/modules/bmb/workflows/redoc/workflow.yaml</critical>
 <critical>Communicate in {communication_language} throughout the documentation process</critical>
 <critical>This is an AUTONOMOUS workflow - minimize user interaction unless clarification is absolutely required</critical>

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

@@ -4,7 +4,7 @@ description: "Autonomous documentation system that maintains module, workflow, a
 author: "BMad"
 
 # Critical variables
-config_source: "{project-root}/bmad/bmb/config.yaml"
+config_source: "{project-root}/{bmad_folder}/bmb/config.yaml"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
 

package/src/modules/bmgd/README.md

@@ -0,0 +1,208 @@
+# BMad Game Development (BMGD)
+
+A comprehensive game development toolkit providing specialized agents and workflows for creating games from initial concept through production.
+
+## Overview
+
+The BMGD module brings together game-specific development workflows organized around industry-standard development phases:
+
+- **Preproduction** - Concept development, brainstorming, game brief creation
+- **Design** - Game Design Document (GDD) and narrative design
+- **Technical** - Game architecture and technical specifications
+- **Production** - Sprint-based implementation using BMM workflows
+
+## Installation
+
+```bash
+bmad install bmgd
+```
+
+During installation, you'll be asked to configure:
+
+- Game project name
+- Document storage locations
+- Development experience level
+- Primary target platform
+
+## Components
+
+### Agents (4)
+
+**Game Designer** 🎨
+Creative vision and game design documentation specialist. Creates compelling GDDs and defines game mechanics.
+
+**Game Developer** 🕹️
+Senior implementation specialist with expertise across Unity, Unreal, and custom engines. Handles gameplay programming, physics, AI, and optimization.
+
+**Game Architect** 🏗️
+Technical systems and infrastructure expert. Designs scalable game architecture and engine-level solutions.
+
+**Game Dev Scrum Master** 🎯
+Sprint orchestrator specialized in game development workflows. Coordinates multi-disciplinary teams and translates GDDs into actionable development stories.
+
+### Team Bundle
+
+**Team Game Development** 🎮
+Pre-configured team including Game Designer, Game Developer, and Game Architect for comprehensive game projects.
+
+### Workflows
+
+#### Phase 1: Preproduction
+
+- **brainstorm-game** - Interactive game concept brainstorming
+- **game-brief** - Create focused game brief document
+
+#### Phase 2: Design
+
+- **gdd** - Generate comprehensive Game Design Document
+- **narrative** - Design narrative structure and story elements
+
+#### Phase 3: Technical
+
+- **game-architecture** - Define technical architecture (adapted from BMM architecture workflow)
+
+#### Phase 4: Production
+
+Production workflows are provided by the BMM module and accessible through the Game Dev Scrum Master agent:
+
+- Sprint planning
+- Story creation and management
+- Epic technical specifications
+- Code review and retrospectives
+
+## Quick Start
+
+### 1. Start with Concept Development
+
+```
+Load agent: game-designer
+Run workflow: brainstorm-game
+```
+
+### 2. Create Game Brief
+
+```
+Run workflow: game-brief
+```
+
+### 3. Develop Game Design Document
+
+```
+Run workflow: gdd
+```
+
+### 4. Define Technical Architecture
+
+```
+Load agent: game-architect
+Run workflow: game-architecture
+```
+
+### 5. Begin Production Sprints
+
+```
+Load agent: game-scrum-master
+Run: *sprint-planning
+```
+
+## Module Structure
+
+```
+bmgd/
+├── agents/
+│   ├── game-designer.agent.yaml
+│   ├── game-dev.agent.yaml
+│   ├── game-architect.agent.yaml
+│   └── game-scrum-master.agent.yaml
+├── teams/
+│   └── team-gamedev.yaml
+├── workflows/
+│   ├── 1-preproduction/
+│   │   ├── brainstorm-game/
+│   │   └── game-brief/
+│   ├── 2-design/
+│   │   ├── gdd/
+│   │   └── narrative/
+│   ├── 3-technical/
+│   │   └── game-architecture/
+│   └── 4-production/
+│       (Uses BMM workflows via cross-module references)
+├── templates/
+├── data/
+└── _module-installer/
+    └── install-config.yaml
+```
+
+## Configuration
+
+After installation, configure the module in `{bmad_folder}/bmgd/config.yaml`
+
+Key settings:
+
+- **game_project_name** - Your game's working title
+- **game_design_docs** - Location for GDD and design documents
+- **game_tech_docs** - Location for technical documentation
+- **game_story_location** - Location for development user stories
+- **game_dev_experience** - Your experience level (affects agent communication)
+- **primary_platform** - Target platform (PC, mobile, console, web, multi-platform)
+
+## Workflow Integration
+
+BMGD leverages the BMM module for production/implementation workflows. The Game Dev Scrum Master agent provides access to:
+
+- Sprint planning and management
+- Story creation from GDD specifications
+- Epic technical context generation
+- Code review workflows
+- Retrospectives and course correction
+
+This separation allows BMGD to focus on game-specific design and architecture while using battle-tested agile implementation workflows.
+
+## Example: Creating a 2D Platformer
+
+1. **Brainstorm** concepts with `brainstorm-game` workflow
+2. **Define** the vision with `game-brief` workflow
+3. **Design** mechanics and progression with `gdd` workflow
+4. **Craft** character arcs and story with `narrative` workflow
+5. **Architect** technical systems with `game-architecture` workflow
+6. **Implement** via Game Dev Scrum Master sprint workflows
+
+## Development Roadmap
+
+### Phase 1: Core Enhancement
+
+- [ ] Customize game-architecture workflow for game-specific patterns
+- [ ] Add game-specific templates (level design, character sheets, etc.)
+- [ ] Create asset pipeline workflows
+
+### Phase 2: Expanded Features
+
+- [ ] Add monetization planning workflows
+- [ ] Create playtesting and feedback workflows
+- [ ] Develop game balancing tools
+
+### Phase 3: Platform Integration
+
+- [ ] Add platform-specific deployment workflows
+- [ ] Create build and release automation
+- [ ] Develop live ops workflows
+
+## Contributing
+
+To extend this module:
+
+1. Add new agents using `/bmad:bmb:workflows:create-agent`
+2. Add new workflows using `/bmad:bmb:workflows:create-workflow`
+3. Submit improvements via pull request
+
+## Dependencies
+
+- **BMM Module** - Required for production/implementation workflows
+
+## Author
+
+Extracted and refined from BMM module on 2025-11-05
+
+## License
+
+Part of the BMAD Method ecosystem