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 | ||
| reference | ||
| workflows | ||
| README.md | ||
README.md
BMB - BMad Builder Module
Specialized tools and workflows for creating, customizing, and extending BMad components including agents, workflows, and complete modules.
Table of Contents
Module Structure
🤖 Agents
BMad Builder - Master builder agent orchestrating all creation workflows with deep knowledge of BMad architecture and conventions.
📋 Workflows
Comprehensive suite for building and maintaining BMad components.
Core Workflows
Creation Workflows
create-agent - Build BMad agents
- Interactive persona development
- Command structure design
- YAML source compilation to .md
create-workflow - Design workflows
- Structured multi-step processes
- Configuration validation
- Web bundle support
create-module - Build complete modules
- Full module infrastructure
- Agent and workflow integration
- Installation automation
module-brief - Strategic planning
- Module blueprint creation
- Vision and architecture
- Comprehensive analysis
Editing Workflows
edit-agent - Modify existing agents
- Persona refinement
- Command updates
- Best practice compliance
edit-workflow - Update workflows
- Structure maintenance
- Configuration updates
- Documentation sync
edit-module - Module enhancement
- Component modifications
- Dependency management
- Version control
Maintenance Workflows
convert-legacy - Migration tool
- v4 to v6 conversion
- Structure compliance
- Convention updates
audit-workflow - Quality validation
- Structure verification
- Config standards check
- Bloat detection
- Web bundle completeness
redoc - Auto-documentation
- Reverse-tree approach
- Technical writer quality
- Convention compliance
Agent Types
BMB creates three agent architectures:
Full Module Agent
- Complete persona and role definition
- Command structure with fuzzy matching
- Workflow integration
- Module-specific capabilities
Hybrid Agent
- Shared core capabilities
- Module-specific extensions
- Cross-module compatibility
Standalone Agent
- Independent operation
- Minimal dependencies
- Specialized single purpose
Quick Start
- Load BMad Builder agent in your IDE
- Choose creation type:
*create-agent # New agent *create-workflow # New workflow *create-module # Complete module - Follow interactive prompts
Example: Creating an Agent
User: I need a code review agent
Builder: *create-agent
[Interactive session begins]
- Brainstorming phase (optional)
- Persona development
- Command structure
- Integration points
Use Cases
Custom Development Teams
Build specialized agents for:
- Domain expertise (legal, medical, finance)
- Company processes
- Tool integrations
- Automation tasks
Workflow Extensions
Create workflows for:
- Compliance requirements
- Quality gates
- Deployment pipelines
- Custom methodologies
Complete Solutions
Package modules for:
- Industry verticals
- Technology stacks
- Business processes
- Educational frameworks
Best Practices
- Study existing patterns - Review BMM/CIS implementations
- Follow conventions - Use established structures
- Document thoroughly - Clear instructions essential
- Test iteratively - Validate during creation
- Consider reusability - Build modular components
Integration
BMB components integrate with:
- BMad Core - Framework foundation
- BMM - Extend development capabilities
- CIS - Leverage creative workflows
- Custom Modules - Your domain solutions
Related Documentation
- Agent Creation Guide - Detailed instructions
- Module Structure - Architecture patterns
- BMM Module - Reference implementation
- Core Framework - Foundation concepts
BMB empowers you to extend BMad Method for your specific needs while maintaining framework consistency and power.