bmad-method 6.0.0-alpha.6 → 6.0.0-alpha.7

package/bmad/_cfg/workflow-manifest.csv

@@ -11,34 +11,7 @@ name,description,module,path,standalone
 "edit-workflow","Edit existing BMAD workflows while following all best practices and conventions","bmb","bmad/bmb/workflows/edit-workflow/workflow.yaml","true"
 "module-brief","Create a comprehensive Module Brief that serves as the blueprint for building new BMAD modules using strategic analysis and creative vision","bmb","bmad/bmb/workflows/module-brief/workflow.yaml","true"
 "redoc","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.","bmb","bmad/bmb/workflows/redoc/workflow.yaml","true"
-"brainstorm-project","Facilitate project brainstorming sessions by orchestrating the CIS brainstorming workflow with project-specific context and guidance.","bmm","bmad/bmm/workflows/1-analysis/brainstorm-project/workflow.yaml","true"
-"product-brief","Interactive product brief creation workflow that guides users through defining their product vision with multiple input sources and conversational collaboration","bmm","bmad/bmm/workflows/1-analysis/product-brief/workflow.yaml","true"
-"research","Adaptive research workflow supporting multiple research types: market research, deep research prompt generation, technical/architecture evaluation, competitive intelligence, user research, and domain analysis","bmm","bmad/bmm/workflows/1-analysis/research/workflow.yaml","true"
-"create-ux-design","Collaborative UX design facilitation workflow that creates exceptional user experiences through visual exploration and informed decision-making. Unlike template-driven approaches, this workflow facilitates discovery, generates visual options, and collaboratively designs the UX with the user at every step.","bmm","bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml","true"
-"narrative","Narrative design workflow for story-driven games and applications. Creates comprehensive narrative documentation including story structure, character arcs, dialogue systems, and narrative implementation guidance.","bmm","bmad/bmm/workflows/2-plan-workflows/narrative/workflow.yaml","true"
-"create-epics-and-stories","Transform PRD requirements into bite-sized stories organized in epics for 200k context dev agents","bmm","bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/workflow.yaml","true"
-"prd","Unified PRD workflow for BMad Method and Enterprise Method tracks. Produces strategic PRD and tactical epic breakdown. Hands off to architecture workflow for technical design. Note: Quick Flow track uses tech-spec workflow.","bmm","bmad/bmm/workflows/2-plan-workflows/prd/workflow.yaml","true"
-"tech-spec","Technical specification workflow for Level 0 projects (single atomic changes). Creates focused tech spec for bug fixes, single endpoint additions, or small isolated changes. Tech-spec only - no PRD needed.","bmm","bmad/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml","true"
-"architecture","Collaborative architectural decision facilitation for AI-agent consistency. Replaces template-driven architecture with intelligent, adaptive conversation that produces a decision-focused architecture document optimized for preventing agent conflicts.","bmm","bmad/bmm/workflows/3-solutioning/architecture/workflow.yaml","true"
-"solutioning-gate-check","Systematically validate that all planning and solutioning phases are complete and properly aligned before transitioning to Phase 4 implementation. Ensures PRD, architecture, and stories are cohesive with no gaps or contradictions.","bmm","bmad/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml","true"
-"code-review","Perform a Senior Developer code review on a completed story flagged Ready for Review, leveraging story-context, epic tech-spec, repo docs, MCP servers for latest best-practices, and web search as fallback. Appends structured review notes to the story.","bmm","bmad/bmm/workflows/4-implementation/code-review/workflow.yaml","true"
-"correct-course","Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation","bmm","bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml","true"
-"create-story","Create the next user story markdown from epics/PRD and architecture, using a standard template and saving to the stories folder","bmm","bmad/bmm/workflows/4-implementation/create-story/workflow.yaml","true"
-"dev-story","Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria","bmm","bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml","true"
-"epic-tech-context","Generate a comprehensive Technical Specification from PRD and Architecture with acceptance criteria and traceability mapping","bmm","bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml","true"
-"retrospective","Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic","bmm","bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml","true"
-"sprint-planning","Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle","bmm","bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml","true"
-"story-context","Assemble a dynamic Story Context XML by pulling latest documentation and existing code/library artifacts relevant to a drafted story","bmm","bmad/bmm/workflows/4-implementation/story-context/workflow.yaml","true"
-"story-done","Marks a story as done (DoD complete) and moves it from its current status → DONE in the status file. Advances the story queue. Simple status-update workflow with no searching required.","bmm","bmad/bmm/workflows/4-implementation/story-done/workflow.yaml","true"
-"story-ready","Marks a drafted story as ready for development and moves it from TODO → IN PROGRESS in the status file. Simple status-update workflow with no searching required.","bmm","bmad/bmm/workflows/4-implementation/story-ready/workflow.yaml","true"
-"document-project","Analyzes and documents brownfield projects by scanning codebase, architecture, and patterns to create comprehensive reference documentation for AI-assisted development","bmm","bmad/bmm/workflows/document-project/workflow.yaml","true"
-"testarch-atdd","Generate failing acceptance tests before implementation using TDD red-green-refactor cycle","bmm","bmad/bmm/workflows/testarch/atdd/workflow.yaml","false"
-"testarch-automate","Expand test automation coverage after implementation or analyze existing codebase to generate comprehensive test suite","bmm","bmad/bmm/workflows/testarch/automate/workflow.yaml","false"
-"testarch-ci","Scaffold CI/CD quality pipeline with test execution, burn-in loops, and artifact collection","bmm","bmad/bmm/workflows/testarch/ci/workflow.yaml","false"
-"testarch-framework","Initialize production-ready test framework architecture (Playwright or Cypress) with fixtures, helpers, and configuration","bmm","bmad/bmm/workflows/testarch/framework/workflow.yaml","false"
-"testarch-nfr","Assess non-functional requirements (performance, security, reliability, maintainability) before release with evidence-based validation","bmm","bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml","false"
-"testarch-test-design","Plan risk mitigation and test coverage strategy before development with risk assessment and prioritization","bmm","bmad/bmm/workflows/testarch/test-design/workflow.yaml","false"
-"testarch-test-review","Review test quality using comprehensive knowledge base and best practices validation","bmm","bmad/bmm/workflows/testarch/test-review/workflow.yaml","false"
-"testarch-trace","Generate requirements-to-tests traceability matrix, analyze coverage, and make quality gate decision (PASS/CONCERNS/FAIL/WAIVED)","bmm","bmad/bmm/workflows/testarch/trace/workflow.yaml","false"
-"workflow-init","Initialize a new BMM project by determining level, type, and creating workflow path","bmm","bmad/bmm/workflows/workflow-status/init/workflow.yaml","true"
-"workflow-status","Lightweight status checker - answers ""what should I do now?"" for any agent. Reads YAML status file for workflow tracking. Use workflow-init for new projects.","bmm","bmad/bmm/workflows/workflow-status/workflow.yaml","true"
+"brainstorming","Facilitate interactive brainstorming sessions using diverse creative techniques. This workflow facilitates interactive brainstorming sessions using diverse creative techniques. The session is highly interactive, with the AI acting as a facilitator to guide the user through various ideation methods to generate and refine creative solutions.","core","bmad/core/workflows/brainstorming/workflow.yaml","true"
+"party-mode","Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations","core","bmad/core/workflows/party-mode/workflow.yaml","true"
+"brainstorming","Facilitate interactive brainstorming sessions using diverse creative techniques. This workflow facilitates interactive brainstorming sessions using diverse creative techniques. The session is highly interactive, with the AI acting as a facilitator to guide the user through various ideation methods to generate and refine creative solutions.","core","bmad/core/workflows/brainstorming/workflow.yaml","true"
+"party-mode","Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations","core","bmad/core/workflows/party-mode/workflow.yaml","true"

package/bmad/bmb/config.yaml

@@ -1,7 +1,7 @@
 # BMB Module Configuration
 # Generated by BMAD installer
-# Version: 6.0.0-alpha.5
-# Date: 2025-11-05T04:14:53.510Z
+# Version: 6.0.0-alpha.6
+# Date: 2025-11-07T04:40:13.951Z
 
 custom_agent_location: "{project-root}/bmad/agents"
 custom_workflow_location: "{project-root}/bmad/workflows"

package/bmad/bmb/workflows/create-agent/instructions.md

@@ -193,9 +193,23 @@ menu:
   - trigger: [emerging from conversation]
     workflow: [path based on capability]
     description: [user's words refined]
-```
+
+# For cross-module workflow references (advanced):
+
+- trigger: [another capability]
+  workflow: "{project-root}/bmad/SOURCE_MODULE/workflows/path/to/workflow.yaml"
+  workflow-install: "{project-root}/bmad/THIS_MODULE/workflows/vendored/path/workflow.yaml"
+  description: [description]
+
+`````
 </example>
 
+<note>**Workflow Vendoring (Advanced):**
+When an agent needs workflows from another module, use both `workflow` (source) and `workflow-install` (destination).
+During installation, the workflow will be copied and configured for this module, making it standalone.
+This is typically used when creating specialized modules that reuse common workflows with different configurations.
+</note>
+
 <template-output>agent_commands</template-output>
 </step>
 
@@ -298,14 +312,16 @@ menu: {{The capabilities built}}
 
 **Folder Structure:**
 
-```
+`````
+
 {{agent_filename}}-sidecar/
-├── memories.md         # Persistent memory
-├── instructions.md     # Private directives
-├── knowledge/         # Knowledge base
-│   └── README.md
-└── sessions/          # Session notes
-```
+├── memories.md # Persistent memory
+├── instructions.md # Private directives
+├── knowledge/ # Knowledge base
+│ └── README.md
+└── sessions/ # Session notes
+
+````
 
 **File: memories.md**
 
@@ -323,7 +339,7 @@ menu: {{The capabilities built}}
 ## Personal Notes
 
 <!-- My observations and insights -->
-```
+````
 
 **File: instructions.md**
 

package/bmad/bmb/workflows/create-module/module-structure.md

@@ -136,6 +136,40 @@ Tasks should be used for:
 - Declare dependencies in config.yaml
 - Version compatibility notes
 
+### Workflow Vendoring (Advanced)
+
+For modules that need workflows from other modules but want to remain standalone, use **workflow vendoring**:
+
+**In Agent YAML:**
+
+```yaml
+menu:
+  - trigger: command-name
+    workflow: '{project-root}/bmad/SOURCE_MODULE/workflows/path/workflow.yaml'
+    workflow-install: '{project-root}/bmad/THIS_MODULE/workflows/vendored/workflow.yaml'
+    description: 'Command description'
+```
+
+**What Happens:**
+
+- During installation, workflows are copied from `workflow` to `workflow-install` location
+- Vendored workflows get `config_source` updated to reference this module's config
+- Compiled agent only references the `workflow-install` path
+- Module becomes fully standalone - no source module dependency required
+
+**Use Cases:**
+
+- Specialized modules that reuse common workflows with different configs
+- Domain-specific adaptations (e.g., game dev using standard dev workflows)
+- Testing workflows in isolation
+
+**Benefits:**
+
+- Module independence (no forced dependencies)
+- Clean namespace (workflows in your module)
+- Config isolation (use your module's settings)
+- Customization ready (modify vendored workflows freely)
+
 ## Installation Infrastructure
 
 ### Required: \_module-installer/install-config.yaml

package/bmad/core/config.yaml

@@ -1,7 +1,7 @@
 # CORE Module Configuration
 # Generated by BMAD installer
-# Version: 6.0.0-alpha.5
-# Date: 2025-11-05T04:14:53.511Z
+# Version: 6.0.0-alpha.6
+# Date: 2025-11-07T04:40:13.952Z
 
 user_name: BMad
 communication_language: English

package/docs/installers-bundlers/installers-modules-platforms-reference.md

@@ -311,6 +311,66 @@ bmad status -v      # Detailed status
 - Agent references (cross-module)
 - Template dependencies
 - Partial module installation (only required files)
+- Workflow vendoring for standalone module operation
+
+## Workflow Vendoring
+
+**Problem**: Modules that reference workflows from other modules create dependencies, forcing users to install multiple modules even when they only need one.
+
+**Solution**: Workflow vendoring allows modules to copy workflows from other modules during installation, making them fully standalone.
+
+### How It Works
+
+Agents can specify both `workflow` (source location) and `workflow-install` (destination location) in their menu items:
+
+```yaml
+menu:
+  - trigger: create-story
+    workflow: '{project-root}/bmad/bmm/workflows/4-implementation/create-story/workflow.yaml'
+    workflow-install: '{project-root}/bmad/bmgd/workflows/4-production/create-story/workflow.yaml'
+    description: 'Create a game feature story'
+```
+
+**During Installation:**
+
+1. **Vendoring Phase**: Before copying module files, the installer:
+   - Scans source agent YAML files for `workflow-install` attributes
+   - Copies entire workflow folders from `workflow` path to `workflow-install` path
+   - Updates vendored `workflow.yaml` files to reference target module's config
+
+2. **Compilation Phase**: When compiling agents:
+   - If `workflow-install` exists, uses its value for the `workflow` attribute
+   - `workflow-install` is build-time metadata only, never appears in final XML
+   - Compiled agent references vendored workflow location
+
+3. **Config Update**: Vendored workflows get their `config_source` updated:
+
+   ```yaml
+   # Source workflow (in bmm):
+   config_source: "{project-root}/bmad/bmm/config.yaml"
+
+   # Vendored workflow (in bmgd):
+   config_source: "{project-root}/bmad/bmgd/config.yaml"
+   ```
+
+**Result**: Modules become completely standalone with their own copies of needed workflows, configured for their specific use case.
+
+### Example Use Case: BMGD Module
+
+The BMad Game Development module vendors implementation workflows from BMM:
+
+- Game Dev Scrum Master agent references BMM workflows
+- During installation, workflows are copied to `bmgd/workflows/4-production/`
+- Vendored workflows use BMGD's config (with game-specific settings)
+- BMGD can be installed without BMM dependency
+
+### Benefits
+
+✅ **Module Independence** - No forced dependencies
+✅ **Clean Namespace** - Workflows live in their module
+✅ **Config Isolation** - Each module uses its own configuration
+✅ **Customization Ready** - Vendored workflows can be modified independently
+✅ **No User Confusion** - Avoid partial module installations
 
 ### File Processing
 
@@ -318,6 +378,7 @@ bmad status -v      # Detailed status
 - Excludes `_module-installer/` directories
 - Replaces path placeholders at runtime
 - Injects activation blocks
+- Vendors cross-module workflows (see Workflow Vendoring below)
 
 ### Web Bundling
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "6.0.0-alpha.6",
+  "version": "6.0.0-alpha.7",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",
@@ -39,8 +39,10 @@
     "release:minor": "gh workflow run \"Manual Release\" -f version_bump=minor",
     "release:patch": "gh workflow run \"Manual Release\" -f version_bump=patch",
     "release:watch": "gh run watch",
-    "test": "node test/test-agent-schema.js",
-    "test:coverage": "c8 --reporter=text --reporter=html node test/test-agent-schema.js",
+    "test": "npm run test:schemas && npm run test:install && npm run validate:bundles && npm run validate:schemas && npm run lint && npm run format:check",
+    "test:coverage": "c8 --reporter=text --reporter=html npm run test:schemas",
+    "test:install": "node test/test-installation-components.js",
+    "test:schemas": "node test/test-agent-schema.js",
     "validate:bundles": "node tools/validate-bundles.js",
     "validate:schemas": "node tools/validate-agent-schema.js"
   },

package/src/core/tasks/adv-elicit.xml

@@ -1,4 +1,4 @@
-<task id="bmad/core/tasks/adv-elicit.xml" name="Advanced Elicitation">
+<task id="bmad/core/tasks/adv-elicit.xml" name="Advanced Elicitation" standalone="true">
   <llm critical="true">
     <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
     <i>DO NOT skip steps or change the sequence</i>

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

@@ -193,9 +193,23 @@ menu:
   - trigger: [emerging from conversation]
     workflow: [path based on capability]
     description: [user's words refined]
-```
+
+# For cross-module workflow references (advanced):
+
+- trigger: [another capability]
+  workflow: "{project-root}/bmad/SOURCE_MODULE/workflows/path/to/workflow.yaml"
+  workflow-install: "{project-root}/bmad/THIS_MODULE/workflows/vendored/path/workflow.yaml"
+  description: [description]
+
+`````
 </example>
 
+<note>**Workflow Vendoring (Advanced):**
+When an agent needs workflows from another module, use both `workflow` (source) and `workflow-install` (destination).
+During installation, the workflow will be copied and configured for this module, making it standalone.
+This is typically used when creating specialized modules that reuse common workflows with different configurations.
+</note>
+
 <template-output>agent_commands</template-output>
 </step>
 
@@ -298,14 +312,16 @@ menu: {{The capabilities built}}
 
 **Folder Structure:**
 
-```
+`````
+
 {{agent_filename}}-sidecar/
-├── memories.md         # Persistent memory
-├── instructions.md     # Private directives
-├── knowledge/         # Knowledge base
-│   └── README.md
-└── sessions/          # Session notes
-```
+├── memories.md # Persistent memory
+├── instructions.md # Private directives
+├── knowledge/ # Knowledge base
+│ └── README.md
+└── sessions/ # Session notes
+
+````
 
 **File: memories.md**
 
@@ -323,7 +339,7 @@ menu: {{The capabilities built}}
 ## Personal Notes
 
 <!-- My observations and insights -->
-```
+````
 
 **File: instructions.md**
 

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

@@ -136,6 +136,40 @@ Tasks should be used for:
 - Declare dependencies in config.yaml
 - Version compatibility notes
 
+### Workflow Vendoring (Advanced)
+
+For modules that need workflows from other modules but want to remain standalone, use **workflow vendoring**:
+
+**In Agent YAML:**
+
+```yaml
+menu:
+  - trigger: command-name
+    workflow: '{project-root}/bmad/SOURCE_MODULE/workflows/path/workflow.yaml'
+    workflow-install: '{project-root}/bmad/THIS_MODULE/workflows/vendored/workflow.yaml'
+    description: 'Command description'
+```
+
+**What Happens:**
+
+- During installation, workflows are copied from `workflow` to `workflow-install` location
+- Vendored workflows get `config_source` updated to reference this module's config
+- Compiled agent only references the `workflow-install` path
+- Module becomes fully standalone - no source module dependency required
+
+**Use Cases:**
+
+- Specialized modules that reuse common workflows with different configs
+- Domain-specific adaptations (e.g., game dev using standard dev workflows)
+- Testing workflows in isolation
+
+**Benefits:**
+
+- Module independence (no forced dependencies)
+- Clean namespace (workflows in your module)
+- Config isolation (use your module's settings)
+- Customization ready (modify vendored workflows freely)
+
 ## Installation Infrastructure
 
 ### Required: \_module-installer/install-config.yaml

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

package/src/modules/bmgd/_module-installer/install-config.yaml

@@ -0,0 +1,66 @@
+# BMad Game Dev Module Configuration
+
+code: bmgd
+name: "BMGD: BMad Game Development"
+default_selected: false
+
+prompt:
+  - "Welcome to the BMad Game Development Module!"
+  - "This module provides specialized agents and workflows for game creation,"
+  - "from initial concept through production, covering all major game dev phases."
+  - "All paths are relative to project root, with no leading slash."
+
+# Core config values automatically inherited:
+## user_name
+## communication_language
+## document_output_language
+## output_folder
+
+game_project_name:
+  prompt: "What is the name of your game project?"
+  default: "{directory_name}"
+  result: "{value}"
+
+game_design_docs:
+  prompt: "Where should game design documents (GDD, narrative, etc.) be stored?"
+  default: "docs/design"
+  result: "{project-root}/{value}"
+
+game_tech_docs:
+  prompt: "Where should game technical documentation be stored?"
+  default: "docs/technical"
+  result: "{project-root}/{value}"
+
+game_story_location:
+  prompt: "Where should game development stories be stored?"
+  default: "docs/stories"
+  result: "{project-root}/{value}"
+
+game_dev_experience:
+  prompt: "What is your game development experience level?"
+  default: "intermediate"
+  result: "{value}"
+  single-select:
+    - value: "beginner"
+      label: "Beginner - New to game development, provide detailed guidance"
+    - value: "intermediate"
+      label: "Intermediate - Familiar with game dev concepts, balanced approach"
+    - value: "expert"
+      label: "Expert - Experienced game developer, be direct and technical"
+
+specified_framework:
+  prompt: "Which game development framework or engine do you want to install support for?"
+  default: "unity"
+  result: "{value}"
+  multi-select:
+    - value: "unity"
+      label: "Unity"
+    - value: "unreal"
+      label: "Unreal Engine"
+    - value: "godot"
+      label: "Godot"
+    - value: "custom"
+      label: "Custom / Other"
+
+data_path:
+  result: "{project-root}/bmad/bmgd/data"