BMAD-METHOD/src/modules/bmgd
Brian Madison 48cf5c8056 feat(workflows): Implement intelligent file discovery protocol and Phase 4 BMGD workflows
## Core Workflow Engine Enhancements

### discover_inputs Protocol (MAJOR)
- Added reusable `discover_inputs` protocol to workflow.xml for intelligent file loading
- Supports three loading strategies:
  - FULL_LOAD: Load all shards for PRD, Architecture, UX (changed pattern from /index.md to /*/*.md)
  - SELECTIVE_LOAD: Load specific shard via template variable (e.g., epic-{{epic_num}}.md)
  - INDEX_GUIDED: Load index, analyze TOC, intelligently load relevant docs (with "DO NOT BE LAZY" mandate)
- Auto-discovers whole vs sharded documents with proper fallback
- Provides transparent reporting of loaded content with file counts
- Invoked via <invoke-protocol name="discover_inputs" /> tag in workflow instructions

### Advanced Elicitation Improvements
- Renamed adv-elicit.xml to advanced-elicitation.xml for clarity
- Updated all references across agents and commands

### Shard Document Tool Enhancement
- Added Step 6: Handle Original Document with three options:
  - [d] Delete - Remove original (recommended, prevents confusion)
  - [m] Move to archive - Backup original to archive folder
  - [k] Keep - Warning about defeating sharding purpose
- Prevents issue where both whole and sharded versions exist, confusing discover_inputs protocol

## BMM Module - Input File Pattern Standardization

### Phase 1 - Analysis (1 workflow)
- product-brief: Added load_strategy (FULL_LOAD for research/brainstorming, INDEX_GUIDED for document_project)
- Updated instructions.md to use invoke-protocol, replaced manual fuzzy matching

### Phase 2 - Planning (4 workflows)
- prd: Added load_strategy, updated instructions to reference {product_brief_content}, {research_content}
- create-ux-design: Added load_strategy, removed fuzzy matching from instructions
- tech-spec: Added load_strategy for brownfield context discovery
- All epics patterns updated to support SELECTIVE_LOAD for specific epic shards

### Phase 3 - Solutioning (2 workflows)
- architecture: Added load_strategy, updated instructions to use pre-loaded {prd_content}, {epics_content}, {ux_design_content}
- solutioning-gate-check: Added load_strategy, replaced manual discovery with protocol invocation

### Phase 4 - Implementation (8 workflows)
- code-review: Added load_strategy, fixed sharded patterns to /*/*.md, added step 1.5 for protocol
- correct-course: Added complete input_file_patterns section (was missing), added step 0.5
- create-story: Added load_strategy, updated to SELECTIVE_LOAD for epics, added step 1.5
- dev-story: Added complete input_file_patterns section (was missing), added step 0.5
- epic-tech-context: Added load_strategy, updated PRD extraction to use {prd_content}, added step 1.5
- retrospective: Added load_strategy for architecture/prd (FULL_LOAD), epics (SELECTIVE_LOAD), added step 0.5
- sprint-planning: Fixed sharded pattern to load ALL epics (/*/*.md), added step 0.5
- story-context: Added load_strategy, updated doc collection to reference pre-loaded content, added step 1.5

### Sprint Artifacts Path Corrections
- story-done: Added missing sprint_artifacts variable, fixed sprint_status path from {context_dir} to {sprint_artifacts}
- story-ready: Added missing sprint_artifacts variable
- story-context: Fixed undefined {context_dir} -> {sprint_artifacts}
- correct-course: Added sprint_artifacts and sprint_status variables

## BMGD Module - Phase 4 Production Workflows (NEW)

Added complete Phase 4 implementation workflows for game development:
- code-review: Senior developer review for completed game features
- correct-course: Sprint change management for game projects
- create-story: Story generation for game mechanics/features
- dev-story: Feature implementation workflow
- epic-tech-context: Technical spec generation per game epic
- retrospective: Epic completion review and lessons learned
- sprint-planning: Game development sprint status tracking
- story-context: Dynamic context assembly for game stories
- story-done: Story completion workflow
- story-ready: Story readiness workflow

All BMGD workflows follow BMM patterns with game-specific adaptations.

## Agent Updates

### BMM Agents
- Updated all 7 BMM agents (analyst, architect, dev, pm, sm, tea, tech-writer, ux-designer)
- Standardized web bundle configurations

### BMGD Agents
- Updated 4 game development agents (game-architect, game-designer, game-dev, game-scrum-master)
- Aligned with BMM agent structure

### CIS Agents
- Updated 5 creative intelligence agents for consistency

## Documentation & Configuration

- Updated CHANGELOG.md with Phase 4 workflow additions
- Updated files-manifest.csv and task-manifest.csv
- Updated .claude commands for all agents
- Fixed formatting issues from previous commits

## Breaking Changes

NONE - All changes are backward compatible. Workflows without input_file_patterns continue to work.
Workflows with input_file_patterns now benefit from intelligent auto-loading.

## Migration Notes

Existing workflows can gradually adopt discover_inputs protocol by:
1. Adding load_strategy to existing input_file_patterns in workflow.yaml
2. Adding <invoke-protocol name="discover_inputs" /> step in instructions.md
3. Replacing manual file loading with references to {pattern_name_content} variables
2025-11-12 19:18:38 -06:00
..
_module-installer feat: Add documentation guides, simplify folder structure, and major workflow refactoring 2025-11-11 17:30:43 -06:00
agents feat(workflows): Implement intelligent file discovery protocol and Phase 4 BMGD workflows 2025-11-12 19:18:38 -06:00
teams Major Enhancements: 2025-11-09 17:39:05 -06:00
workflows feat(workflows): Implement intelligent file discovery protocol and Phase 4 BMGD workflows 2025-11-12 19:18:38 -06:00
README.md The install directory is now configurable, with a few minute issues 2025-11-08 13:58:43 -06:00

README.md

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

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