## The Tale of the Frame Expert
Once upon a time, BMad Method had a specialized agent called Frame Expert.
This agent was the master of all visual artifacts - flowcharts, diagrams,
wireframes, data flows. Whenever anyone needed a diagram, they called upon
Frame Expert. The agent lived in its own isolated domain with four dedicated
workflows and a library of shared templates.
## The Awakening
But something felt wrong. Teams using BMad Method were meant to mirror real
agile teams - Product Managers, Architects, UX Designers, Tech Writers,
Developers. Each agent represented an authentic role you'd find in any
software team.
Except Frame Expert.
No real agile team has a "Frame Expert" or "Diagram Specialist" who creates
all visual artifacts. In real teams, Architects diagram system architecture.
PMs flowchart processes. UX Designers wireframe interfaces. Tech Writers
create documentation diagrams. The visuals emerge from the domain experts
who need them, not from a centralized diagram factory.
Frame Expert was an abstraction that made technical sense but violated the
very soul of BMad Method - authentic agile role modeling.
## The Transformation
And so Frame Expert was dissolved, its knowledge distributed to those who
truly needed it:
**The Architect** inherited system architecture diagrams and data flows -
the blueprints of technical systems they design.
**The Product Manager** received process flowcharts - the visual maps of
features and workflows they orchestrate.
**The UX Designer** claimed wireframes - the interface sketches that bring
their vision to life.
**The Tech Writer** gained all diagram types - the visual aids that clarify
their documentation.
Each agent now creates diagrams in their domain, using their expertise,
serving their purpose.
## The Shared Knowledge
But the wisdom of diagram creation itself - the Excalidraw templates, the
component libraries, the validation patterns - this knowledge was too
valuable to scatter. It was elevated to core resources, where both BMM
agents AND the new CIS presentation-master agent could draw upon it.
Shared infrastructure for common needs. Distributed execution for domain
expertise.
## The Ripple Effects
With diagrams now properly distributed, other misalignments became visible:
Epic creation was happening in Phase 2 (Planning), before Architecture
existed. But epics need architectural context - API contracts, data models,
technical decisions. So epic creation migrated to Phase 3 (Solutioning),
after Architecture provides that foundation.
Workflow paths were updated. Documentation gained visual flowcharts showing
the complete journey. Agent naming standards were clarified - filenames are
stable roles, persona names are user dreams.
## What Changed
**Removed:**
- frame-expert.agent.yaml (the centralized specialist)
- All frame-expert workflows and shared resources
- Phase 2 epic creation workflow (wrong timing)
- game-design workflow path (consolidated to method track)
- v6-open-items.md (planning doc, now complete)
**Distributed Diagram Capabilities:**
- Architect: create-excalidraw-diagram, create-excalidraw-dataflow
- PM: create-excalidraw-flowchart
- Tech Writer: create-excalidraw-{diagram,dataflow,flowchart}, generate-mermaid
- UX Designer: create-excalidraw-wireframe
**Created:**
- src/core/resources/ (shared diagram context for all modules)
- src/modules/cis/agents/presentation-master.agent.yaml (visual comms specialist)
- src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/ (epic creation's new home)
- src/modules/bmm/workflows/diagrams/ (distributed diagram implementations)
- src/modules/bmm/docs/images/ (workflow visualization assets)
**Enhanced:**
- All agent definitions with domain-appropriate diagram workflows
- Documentation with embedded workflow diagrams and visual guides
- Agent compilation docs with critical naming convention rules
- All 4 workflow paths (enterprise/method × brownfield/greenfield)
**Fixed:**
- Epic creation now in Phase 3 after Architecture
- Story context path variables in BMGD module
- PRD workflow descriptions (epics moved to Phase 3)
## For Users
The Frame Expert commands are gone. In their place:
- Need architecture diagrams? Ask `/architect`
- Need process flows? Ask `/pm`
- Need wireframes? Ask `/ux-designer`
- Need documentation visuals? Ask `/tech-writer`
Each expert creates diagrams in their domain, with their context, using
their judgment.
This is how real teams work.
|
||
|---|---|---|
| .. | ||
| _module-installer | ||
| agents | ||
| teams | ||
| workflows | ||
| README.md | ||
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
- Brainstorm concepts with
brainstorm-gameworkflow - Define the vision with
game-briefworkflow - Design mechanics and progression with
gddworkflow - Craft character arcs and story with
narrativeworkflow - Architect technical systems with
game-architectureworkflow - 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:
- Add new agents using
/bmad:bmb:workflows:create-agent - Add new workflows using
/bmad:bmb:workflows:create-workflow - 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