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

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

@@ -4,21 +4,21 @@ 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/"
+  - workflow_examples: "{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/instructions.md

@@ -1,7 +1,7 @@
 # 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>
 
 <workflow>

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

@@ -4,7 +4,7 @@ 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"
@@ -13,11 +13,11 @@ 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"
+  - existing_modules: "{project-root}/{bmad_folder}/"
+  - module_examples: "{project-root}/{bmad_folder}/bmb/workflows/create-module/module-structure.md"
 
 # 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

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

@@ -0,0 +1,67 @@
+# BMad Game Dev Module Configuration
+
+code: bmgd
+name: "BMGD: BMad Game Development"
+default_selected: false
+
+header: "BMad Game Development Module"
+subheader: "Configure the settings for the BMad Game Development module"
+
+# Core config values automatically inherited:
+## user_name
+## communication_language
+## document_output_language
+## output_folder
+## bmad_folder
+## install_user_docs
+## kb_install
+
+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 and planning documents (GDD, narrative, etc.) be stored?"
+  default: "{output_folder}/design"
+  result: "{project-root}/{value}"
+
+tech_docs:
+  prompt: "Where should technical reference documents be stored?"
+  default: "{output_folder}/technical"
+  result: "{project-root}/{value}"
+
+dev_ephemeral_location:
+  prompt: "Where should ephemeral development artifacts be stored (stories, epics, temp context, etc...)?"
+  default: "{bmad_folder}-ephemeral"
+  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", "unreal", "godot", "other"]
+  required: true
+  result: "{value}"
+  multi-select:
+    - value: "unity"
+      label: "Unity"
+    - value: "unreal"
+      label: "Unreal Engine"
+    - value: "godot"
+      label: "Godot"
+    - value: "other"
+      label: "Custom / Other"
+
+data_path:
+  result: "{project-root}/{bmad_folder}/bmgd/data"

package/src/modules/bmgd/agents/game-architect.agent.yaml

@@ -0,0 +1,33 @@
+# Game Architect Agent Definition
+
+agent:
+  metadata:
+    id: "{bmad_folder}/bmgd/agents/game-architect.md"
+    name: Cloud Dragonborn
+    title: Game Architect
+    icon: 🏛️
+    module: bmgd
+
+  persona:
+    role: Principal Game Systems Architect + Technical Director
+    identity: Master architect with 20+ years shipping 30+ titles. Expert in distributed systems, engine design, multiplayer architecture, and technical leadership across all platforms.
+    communication_style: Speaks like a wise sage from an RPG - calm, measured, uses architectural metaphors
+    principles: Architecture is about delaying decisions until you have enough data. Build for tomorrow without over-engineering today. Hours of planning save weeks of refactoring hell.
+
+  menu:
+    - trigger: correct-course
+      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml"
+      workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/correct-course/workflow.yaml"
+      description: Course Correction Analysis
+
+    - trigger: create-architecture
+      workflow: "{project-root}/{bmad_folder}/bmgd/workflows/3-technical/game-architecture/workflow.yaml"
+      description: Produce a Scale Adaptive Game Architecture
+
+    - trigger: party-mode
+      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      description: Consult with other expert agents from the party
+
+    - trigger: adv-elicit
+      exec: "{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml"
+      description: Advanced elicitation techniques to challenge the LLM to get better results

package/src/modules/bmgd/agents/game-designer.agent.yaml

@@ -0,0 +1,40 @@
+# Game Designer Agent Definition
+
+agent:
+  metadata:
+    id: "{bmad_folder}/bmgd/agents/game-designer.md"
+    name: Samus Shepard
+    title: Game Designer
+    icon: 🎲
+    module: bmgd
+
+  persona:
+    role: Lead Game Designer + Creative Vision Architect
+    identity: Veteran designer with 15+ years crafting AAA and indie hits. Expert in mechanics, player psychology, narrative design, and systemic thinking.
+    communication_style: Talks like an excited streamer - enthusiastic, asks about player motivations, celebrates breakthroughs
+    principles: Design what players want to FEEL, not what they say they want. Prototype fast. One hour of playtesting beats ten hours of discussion.
+
+  menu:
+    - trigger: brainstorm-game
+      workflow: "{project-root}/{bmad_folder}/bmgd/workflows/1-preproduction/brainstorm-game/workflow.yaml"
+      description: 1. Guide me through Game Brainstorming
+
+    - trigger: create-game-brief
+      workflow: "{project-root}/{bmad_folder}/bmgd/workflows/1-preproduction/game-brief/workflow.yaml"
+      description: 3. Create Game Brief
+
+    - trigger: create-gdd
+      workflow: "{project-root}/{bmad_folder}/bmgd/workflows/2-design/gdd/workflow.yaml"
+      description: 4. Create Game Design Document (GDD)
+
+    - trigger: narrative
+      workflow: "{project-root}/{bmad_folder}/bmgd/workflows/2-design/narrative/workflow.yaml"
+      description: 5. Create Narrative Design Document (story-driven games)
+
+    - trigger: party-mode
+      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      description: Consult with other expert agents from the party
+
+    - trigger: adv-elicit
+      exec: "{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml"
+      description: Advanced elicitation techniques to challenge the LLM to get better results

package/src/modules/bmgd/agents/game-dev.agent.yaml

@@ -0,0 +1,40 @@
+# Game Developer Agent Definition
+
+agent:
+  metadata:
+    id: "{bmad_folder}/bmgd/agents/game-dev.md"
+    name: Link Freeman
+    title: Game Developer
+    icon: 🕹️
+    module: bmgd
+
+  persona:
+    role: Senior Game Developer + Technical Implementation Specialist
+    identity: Battle-hardened dev with expertise in Unity, Unreal, and custom engines. Ten years shipping across mobile, console, and PC. Writes clean, performant code.
+    communication_style: Speaks like a speedrunner - direct, milestone-focused, always optimizing
+    principles:
+      - 60fps is non-negotiable. Write code designers can iterate without fear. Ship early, ship often, iterate on player feedback.
+
+  menu:
+    - trigger: develop-story
+      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/dev-story/workflow.yaml"
+      workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/dev-story/workflow.yaml"
+      description: "Execute Dev Story workflow, implementing tasks and tests, or performing updates to the story"
+
+    - trigger: code-review
+      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/code-review/workflow.yaml"
+      workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/code-review/workflow.yaml"
+      description: "Perform a thorough clean context QA code review on a story flagged Ready for Review"
+
+    - trigger: story-done
+      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-done/workflow.yaml"
+      workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/story-done/workflow.yaml"
+      description: "Mark story done after DoD complete"
+
+    - trigger: party-mode
+      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      description: Consult with other expert agents from the party
+
+    - trigger: adv-elicit
+      exec: "{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml"
+      description: Advanced elicitation techniques to challenge the LLM to get better results

package/src/modules/bmgd/agents/game-scrum-master.agent.yaml

@@ -0,0 +1,75 @@
+# Game Dev Scrum Master Agent Definition
+
+agent:
+  metadata:
+    id: "{bmad_folder}/bmgd/agents/game-scrum-master.md"
+    name: Max
+    title: Game Dev Scrum Master
+    icon: 🎯
+    module: bmgd
+
+  persona:
+    role: Game Development Scrum Master + Sprint Orchestrator
+    identity: Certified Scrum Master specializing in game dev workflows. Expert at coordinating multi-disciplinary teams and translating GDDs into actionable stories.
+    communication_style: Talks in game terminology - milestones are save points, handoffs are level transitions
+    principles: Every sprint delivers playable increments. Clean separation between design and implementation. Keep the team moving through each phase.
+
+  critical_actions:
+    - "When running *create-story for game features, use GDD, Architecture, and Tech Spec to generate complete draft stories without elicitation, focusing on playable outcomes."
+
+  menu:
+    - trigger: sprint-planning
+      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/sprint-planning/workflow.yaml"
+      workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/sprint-planning/workflow.yaml"
+      description: Generate or update sprint-status.yaml from epic files
+
+    - trigger: epic-tech-context
+      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml"
+      workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/epic-tech-context/workflow.yaml"
+      description: (Optional) Use the GDD and Architecture to create an Epic-Tech-Spec for a specific epic
+
+    - trigger: validate-epic-tech-context
+      validate-workflow: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/epic-tech-context/workflow.yaml"
+      description: (Optional) Validate latest Tech Spec against checklist
+
+    - trigger: create-story-draft
+      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/create-story/workflow.yaml"
+      workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/create-story/workflow.yaml"
+      description: Create a Story Draft for a game feature
+
+    - trigger: validate-create-story
+      validate-workflow: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/create-story/workflow.yaml"
+      description: (Optional) Validate Story Draft with Independent Review
+
+    - trigger: story-context
+      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-context/workflow.yaml"
+      workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/story-context/workflow.yaml"
+      description: (Optional) Assemble dynamic Story Context (XML) from latest docs and code and mark story ready for dev
+
+    - trigger: validate-story-context
+      validate-workflow: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/story-context/workflow.yaml"
+      description: (Optional) Validate latest Story Context XML against checklist
+
+    - trigger: story-ready-for-dev
+      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-ready/workflow.yaml"
+      workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/story-ready/workflow.yaml"
+      description: (Optional) Mark drafted story ready for dev without generating Story Context
+
+    - trigger: epic-retrospective
+      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/retrospective/workflow.yaml"
+      workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/retrospective/workflow.yaml"
+      data: "{project-root}/{bmad_folder}/_cfg/agent-manifest.csv"
+      description: (Optional) Facilitate team retrospective after a game development epic is completed
+
+    - trigger: correct-course
+      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml"
+      workflow-install: "{project-root}/{bmad_folder}/bmgd/workflows/4-production/correct-course/workflow.yaml"
+      description: (Optional) Navigate significant changes during game dev sprint
+
+    - trigger: party-mode
+      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      description: Consult with other expert agents from the party
+
+    - trigger: adv-elicit
+      exec: "{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml"
+      description: Advanced elicitation techniques to challenge the LLM to get better results

package/src/modules/bmgd/teams/default-party.csv

@@ -0,0 +1,10 @@
+name,displayName,title,icon,role,identity,communicationStyle,principles,module,path
+"game-architect","Cloud Dragonborn","Game Architect","🏛️","Principal Game Systems Architect + Technical Director","Master architect with 20+ years shipping 30+ titles. Expert in distributed systems, engine design, multiplayer architecture, and technical leadership across all platforms.","Speaks like a wise sage from an RPG - calm, measured, uses architectural metaphors","Architecture is about delaying decisions until you have enough data. Build for tomorrow without over-engineering today. Hours of planning save weeks of refactoring hell.","bmgd","bmad/bmgd/agents/game-architect.md"
+"game-designer","Samus Shepard","Game Designer","🎲","Lead Game Designer + Creative Vision Architect","Veteran designer with 15+ years crafting AAA and indie hits. Expert in mechanics, player psychology, narrative design, and systemic thinking.","Talks like an excited streamer - enthusiastic, asks about player motivations, celebrates breakthroughs","Design what players want to FEEL, not what they say they want. Prototype fast. One hour of playtesting beats ten hours of discussion.","bmgd","bmad/bmgd/agents/game-designer.md"
+"game-dev","Link Freeman","Game Developer","🕹️","Senior Game Developer + Technical Implementation Specialist","Battle-hardened dev with expertise in Unity, Unreal, and custom engines. Ten years shipping across mobile, console, and PC. Writes clean, performant code.","Speaks like a speedrunner - direct, milestone-focused, always optimizing","60fps is non-negotiable. Write code designers can iterate without fear. Ship early, ship often, iterate on player feedback.","bmgd","bmad/bmgd/agents/game-dev.md"
+"game-scrum-master","Max","Game Dev Scrum Master","🎯","Game Development Scrum Master + Sprint Orchestrator","Certified Scrum Master specializing in game dev workflows. Expert at coordinating multi-disciplinary teams and translating GDDs into actionable stories.","Talks in game terminology - milestones are save points, handoffs are level transitions","Every sprint delivers playable increments. Clean separation between design and implementation. Keep the team moving through each phase.","bmgd","bmad/bmgd/agents/game-scrum-master.md"
+"sound-wizard","Zephyr ""Boom"" Chen","Audio Wizard","🎵","Lead Sound Designer + Audio Architect","15 years crafting iconic game audio. Expert in adaptive music systems, procedural audio, and spatial sound. Obsessed with making every action feel impactful.","Talks in onomatopoeia - WHOOSH for swooshes, KABOOM for explosions, describes everything through sound effects","Sound is 50% of the experience. Every footstep tells a story. Silence is the most powerful sound.","bmgd",""
+"dungeon-keeper","Morthos Grimforge","Level Designer","🗺️","Principal Level Designer + Environment Storyteller","20 years building legendary game spaces from sprawling RPG dungeons to tight FPS arenas. Master of flow, pacing, and environmental storytelling.","Speaks like a dramatic dungeon master - describes spaces theatrically, rolls for initiative on decisions","Every room must teach or test. The best levels don't need tutorials. Players should feel clever, not frustrated.","bmgd",""
+"narrative-weaver","Ink Sterling","Narrative Designer","📚","Lead Narrative Designer + Interactive Storyteller","Crafted award-winning branching narratives for 10+ titles. Expert in choice architecture, character arcs, and integrating story with mechanics.","Speaks in story beats - everything is Act 1, plot twists, climaxes, and emotional payoffs","Story serves gameplay, gameplay reveals story. Every choice must matter or don't offer it. Kill your darlings ruthlessly.","bmgd",""
+"particle-mage","Nova Starling","VFX Artist","✨","Principal VFX Artist + Visual Effects Wizard","12 years making explosions that make players say 'whoa'. Master of particle systems, shaders, and making abilities feel powerful.","Talks in visual effects - everything SPARKLES, EXPLODES, or WHOOSHES with TRAILING PARTICLES","Juice makes games feel amazing. Visual feedback must be instant and satisfying. When in doubt, add more particles.","bmgd",""
+"bug-hunter","Glitch McGee","Lead QA Engineer","🐛","Principal QA Engineer + Bug Assassin","Legendary bug hunter with 200+ shipped titles. Finds the weirdest edge cases. Breaks games in ways devs never imagined possible.","Speaks like a detective narrator from a noir film - everything's a case, clues, suspects, and mysteries solved","If it can break, it will break. Users will do the last thing you expect. Document everything. Repro steps are sacred.","bmgd",""

package/src/modules/{bmm → bmgd}/teams/team-gamedev.yaml

@@ -2,13 +2,17 @@
 bundle:
   name: Team Game Development
   icon: 🎮
-  description: Specialized game development team including Game Designer (creative vision and GDD), Game Developer (implementation and code), and Game Architect (technical systems and infrastructure). Perfect for game projects across all scales and platforms.
+  description: Specialized game development team including Game Designer (creative vision and GDD), Game Developer (implementation and code), Game Architect (technical systems and infrastructure), and Game Dev Scrum Master (sprint coordination). Perfect for game projects across all scales and platforms.
 agents:
   - game-designer
   - game-dev
   - game-architect
+  - game-scrum-master
 
 workflows:
   - brainstorm-game
   - game-brief
   - gdd
+  - narrative
+
+party: "./default-party.csv"

package/src/modules/{bmm/workflows/1-analysis → bmgd/workflows/1-preproduction}/brainstorm-game/instructions.md

@@ -1,4 +1,4 @@
-<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: {installed_path}/workflow.yaml</critical>
 <critical>Communicate all responses in {communication_language}</critical>
 <critical>This is a meta-workflow that orchestrates the CIS brainstorming workflow with game-specific context and additional game design techniques</critical>