Brian Madison 2d99833b9e feat: Add documentation guides, simplify folder structure, and major workflow refactoring
Created two comprehensive guides for v6 features:

**docs/agent-customization-guide.md**
- Complete guide for customizing agent names, personas, memories, and behaviors
- Update-safe customization via bmad/_cfg/agents/ configuration files
- Real-world examples (TDD setup, multilingual agents, custom workflows)
- Troubleshooting and best practices

**docs/web-bundles-gemini-gpt-guide.md**
- Comprehensive guide for using BMad agents in Gemini Gems and Custom GPTs
- Critical setup rules with exact configuration text required
- Cost-saving strategy: web planning → local implementation (60-80% savings)
- Platform comparison (Gemini Gems strongly recommended over Custom GPTs)
- Complete workflow examples showing full planning-to-implementation cycle
- Team bundle guidance (Gemini 2.5 Pro+ only)

**README.md updates**
- Added prominent links in v6 Core Enhancements section
- Created new "Customization & Sharing" documentation category
- Web Bundles feature highlighted with direct guide link

**Unified output folder structure across all modules:**

**Before (confusing):**
- output_folder: Main docs
- game_design_docs: Separate design folder
- tech_docs: Separate technical folder
- dev_ephemeral_location: Separate ephemeral folder outside docs

**After (simplified):**
- output_folder: Single location for ALL AI-generated artifacts (default: "docs")
  - Clearer prompt: "Where should AI Generated Artifacts be saved?"
- sprint_artifacts: Phase 4 ephemeral content now WITHIN output_folder
  - BMM: {output_folder}/stories (stories, context, reports)
  - BMGD: {output_folder}/sprint-artifacts
  - No longer in separate {bmad_folder}-ephemeral location

**Benefits:**
- One clear location for all planning artifacts (PRD, Architecture, UX, etc.)
- Phase 4 ephemeral items logically grouped within output folder
- Eliminated confusing separate folder proliferation
- sprint_artifacts now configurable per module

**Files changed:**
- src/core/_module-installer/install-config.yaml
- src/modules/bmm/_module-installer/install-config.yaml
- src/modules/bmgd/_module-installer/install-config.yaml

**Also cleaned up BMGD config:**
- Renamed: specified_framework → primary_platform (clearer naming)
- Removed: unused data_path variable

Replaced old "project_level" (0-4) system with new "selected_track" terminology:
- **quick-flow**: Bug fixes and small features (replaces Level 0-1)
- **bmad-method**: Full planning track (replaces Level 2-3)
- **enterprise-bmad-method**: Extended planning (replaces Level 4)

**Core workflow updates:**
- solutioning-gate-check: Complete rewrite of validation logic for track-based artifacts
- architecture: Updated context detection, error handling, and messaging for tracks
- workflow-init: Updated artifact detection patterns for track-based paths
- All workflow status paths updated (method-greenfield, method-brownfield, enterprise-*)

Unified variable naming conventions across all workflows:
- {output_folder} → {output-folder} (hyphenated format)
- {dev_ephemeral_location} → {sprint_artifacts} (clearer purpose)
- Hardcoded status file paths → {workflow_status_file} variable

Fixed corrupted variable patterns throughout workflow files:
- {output*folder} → {output-folder}
- {ephemeral*location} → {sprint_artifacts}
- \_prd* → *prd* (escaped underscore artifacts)
- **\*\***\_\_\_**\*\*** → proper field placeholders

Affected patterns included malformed glob patterns, template variables, and markdown formatting artifacts from previous edits.

**Architecture workflow (create-architecture):**
- Fixed: "Decision Architecture" → "Create Architecture" (consistent naming)
- Improved PRD not found handling with exit/continue options
- Better user guidance when running standalone vs. within workflow path
- Removed hardcoded Level checks, now track-aware
- Enhanced validation checklist formatting (□ → - [])
- Typo fixes: "mulitple" → "multiple"

**Solutioning gate check:**
- Complete validation logic rewrite for track-based system
- Removed Level-specific artifact expectations
- Simplified document discovery (track determines what exists)
- Better analysis prompts and user feedback

**Workflow-init:**
- Updated artifact detection patterns for new folder structure
- Fixed corrupt glob patterns throughout
- Better sprint_artifacts location detection
- Improved workflow path assignment logic

**Various workflows:**
- Consistent variable naming across 40+ workflow files
- Improved error messages and user guidance
- Better markdown formatting (checkboxes, lists)
- Removed redundant validation criteria files (now inline)

Removed duplicate BMGD 4-production workflows (12 workflows):
- code-review, correct-course, create-story, dev-story
- epic-tech-context, retrospective, sprint-planning
- story-context, story-done, story-ready

**Why:** BMGD now uses shared BMM Phase 4 implementation workflows
**Benefit:** Single source of truth, no duplication to maintain

Also removed:
- validation-criteria.yaml (validation now inline in instructions)
- architecture-patterns.yaml references (patterns now managed differently)
- AUDIT-REPORT.md files (stale audit artifacts)

**BMB workflows:**
- Updated checklists for workflow and module creation
- Improved agent architecture documentation
- Minor instruction clarifications

**Core brainstorming workflow:**
- Updated README with usage examples
- Enhanced instructions and template clarity
- Better integration with other modules

**BMM installer:**
- Updated for track-based system
- sprint_artifacts configuration

**Tech Writer agent:**
- Minor configuration update for documentation workflows

Removed 200+ files that should not be in repository:
- Installed agent markdown files (analyst, architect, dev, pm, sm, tea, etc.)
- Complete workflow instruction copies
- Documentation duplicates (quick-start, agents-guide, workflows-*)
- Test architecture knowledge base (22 files, 14,000+ lines)
- Configuration files (config.yaml, team definitions)

These are generated during installation and should not be version controlled.

Removed 21 pre-generated XML bundles:
- BMM agents (analyst, architect, dev, pm, sm, tea, tech-writer, ux-designer)
- BMGD agents (game-architect, game-designer, game-dev, game-scrum-master)
- CIS agents (brainstorming-coach, creative-problem-solver, etc.)
- Team bundles (team-fullstack, team-gamedev, creative-squad)

**Why:** Users should generate fresh bundles via `npm run bundle` to get latest changes and customizations.

- **2 new documentation files** (comprehensive guides)
- **98 source files modified** (299 insertions, 6,567 deletions)
- **3 installer config files simplified** (major folder structure improvement)
- **200+ .bmad/ artifacts removed** (should not be in repo)
- **21 web-bundle files removed** (users regenerate as needed)
- **12 duplicate workflows removed** (BMGD consolidation)
- **40+ workflows updated** (track system, variable standardization, corruption fixes)
2025-11-11 17:30:43 -06:00
..
2025-11-09 17:39:05 -06:00
2025-11-09 17:39:05 -06:00

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