f17e4ef0b7
## 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 | ||
| docs | ||
| sub-modules/claude-code | ||
| teams | ||
| testarch | ||
| workflows | ||
| README.md | ||
README.md
BMM - BMad Method Module
Core orchestration system for AI-driven agile development, providing comprehensive lifecycle management through specialized agents and workflows.
📚 Complete Documentation
👉 BMM Documentation Hub - Start here for complete guides, tutorials, and references
Quick Links:
- Quick Start Guide - New to BMM? Start here (15 min)
- Agents Guide - Meet your 12 specialized AI agents (45 min)
- Scale Adaptive System - How BMM adapts to project size (42 min)
- FAQ - Quick answers to common questions
- Glossary - Key terminology reference
🏗️ Module Structure
This module contains:
bmm/
├── agents/ # 12 specialized AI agents (PM, Architect, SM, DEV, TEA, etc.)
├── workflows/ # 34 workflows across 4 phases + testing
├── teams/ # Pre-configured agent groups
├── tasks/ # Atomic work units
├── testarch/ # Comprehensive testing infrastructure
└── docs/ # Complete user documentation
Agent Roster
Core Development: PM, Analyst, Architect, SM, DEV, TEA, UX Designer, Technical Writer Game Development: Game Designer, Game Developer, Game Architect Orchestration: BMad Master (from Core)
👉 Full Agents Guide - Roles, workflows, and when to use each agent
Workflow Phases
Phase 0: Documentation (brownfield only) Phase 1: Analysis (optional) - 5 workflows Phase 2: Planning (required) - 6 workflows Phase 3: Solutioning (Level 3-4) - 2 workflows Phase 4: Implementation (iterative) - 10 workflows Testing: Quality assurance (parallel) - 9 workflows
👉 Workflow Guides - Detailed documentation for each phase
🚀 Getting Started
New Project:
# Install BMM
npx bmad-method@alpha install
# Load Analyst agent in your IDE, then:
*workflow-init
Existing Project (Brownfield):
# Document your codebase first
*document-project
# Then initialize
*workflow-init
👉 Quick Start Guide - Complete setup and first project walkthrough
🎯 Key Concepts
Scale-Adaptive Design
BMM automatically adjusts to project complexity (Levels 0-4):
- Level 0-1: Quick Spec Flow for bug fixes and small features
- Level 2: PRD with optional architecture
- Level 3-4: Full PRD + comprehensive architecture
👉 Scale Adaptive System - Complete level breakdown
Story-Centric Implementation
Stories move through a defined lifecycle: backlog → drafted → ready → in-progress → review → done
Just-in-time epic context and story context provide exact expertise when needed.
👉 Implementation Workflows - Complete story lifecycle guide
Multi-Agent Collaboration
Use party mode to engage all 19+ agents (from BMM, CIS, BMB, custom modules) in group discussions for strategic decisions, creative brainstorming, and complex problem-solving.
👉 Party Mode Guide - How to orchestrate multi-agent collaboration
📖 Additional Resources
- Brownfield Guide - Working with existing codebases
- Quick Spec Flow - Fast-track for Level 0-1 projects
- Enterprise Agentic Development - Team collaboration patterns
- Troubleshooting - Common issues and solutions
- IDE Setup Guides - Configure Claude Code, Cursor, Windsurf, etc.
🤝 Community
- Discord - Get help, share feedback (#general-dev, #bugs-issues)
- GitHub Issues - Report bugs or request features
- YouTube - Video tutorials and walkthroughs
Ready to build? → Start with the Quick Start Guide