mirror of
https://github.com/bmadcode/BMAD-METHOD.git
synced 2025-12-29 16:14:59 +00:00
refactor(bmm,cis,core): Align diagram workflows with agile roles and distribute capabilities
## 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.
This commit is contained in:
Brian Madison
@@ -60,24 +60,12 @@ phases:
|
||||
agent: "pm"
|
||||
command: "validate-prd"
|
||||
|
||||
- id: "create-epics-and-stories"
|
||||
optional: true
|
||||
agent: "pm"
|
||||
command: "create-epics-and-stories"
|
||||
note: "Optional: Create epic breakdown early (basic structure only)"
|
||||
|
||||
- id: "create-design"
|
||||
recommended: true
|
||||
agent: "ux-designer"
|
||||
command: "create-design"
|
||||
note: "Recommended - must integrate with existing UX patterns"
|
||||
|
||||
- id: "create-epics-and-stories-after-ux"
|
||||
optional: true
|
||||
agent: "pm"
|
||||
command: "create-epics-and-stories"
|
||||
note: "Optional: Create epic breakdown with UX context"
|
||||
|
||||
- phase: 2
|
||||
name: "Solutioning"
|
||||
required: true
|
||||
@@ -89,6 +77,12 @@ phases:
|
||||
output: "Integration architecture with enterprise considerations"
|
||||
note: "Distills brownfield context + adds security/scalability/compliance design"
|
||||
|
||||
- id: "create-epics-and-stories"
|
||||
required: true
|
||||
agent: "pm"
|
||||
command: "create-epics-and-stories"
|
||||
note: "Required: Break down PRD into implementable epics and stories with full context (PRD + UX + Architecture)"
|
||||
|
||||
- id: "test-design"
|
||||
required: true
|
||||
agent: "tea"
|
||||
@@ -96,31 +90,25 @@ phases:
|
||||
output: "System-level testability review"
|
||||
note: "Enterprise requires testability validation - auto-detects system-level mode"
|
||||
|
||||
- id: "create-security-architecture"
|
||||
optional: true
|
||||
agent: "architect"
|
||||
command: "create-security-architecture"
|
||||
output: "Security architecture for brownfield integration"
|
||||
note: "Future workflow - optional extended enterprise workflow for threat model, auth integration, audit requirements"
|
||||
# - id: "create-security-architecture"
|
||||
# optional: true
|
||||
# agent: "architect"
|
||||
# command: "create-security-architecture"
|
||||
# output: "Security architecture for brownfield integration"
|
||||
# note: "Future workflow - optional extended enterprise workflow for threat model, auth integration, audit requirements"
|
||||
|
||||
- id: "create-devops-strategy"
|
||||
optional: true
|
||||
agent: "architect"
|
||||
command: "create-devops-strategy"
|
||||
output: "DevOps strategy for brownfield deployment"
|
||||
note: "Future workflow - optional extended enterprise workflow for CI/CD integration, deployment strategy, monitoring"
|
||||
# - id: "create-devops-strategy"
|
||||
# optional: true
|
||||
# agent: "architect"
|
||||
# command: "create-devops-strategy"
|
||||
# output: "DevOps strategy for brownfield deployment"
|
||||
# note: "Future workflow - optional extended enterprise workflow for CI/CD integration, deployment strategy, monitoring"
|
||||
|
||||
- id: "validate-architecture"
|
||||
recommended: true
|
||||
agent: "architect"
|
||||
command: "validate-architecture"
|
||||
|
||||
- id: "create-epics-and-stories-final"
|
||||
required: true
|
||||
agent: "pm"
|
||||
command: "create-epics-and-stories"
|
||||
note: "Required: Create final epic breakdown with full context (PRD + UX + Architecture)"
|
||||
|
||||
- id: "implementation-readiness"
|
||||
required: true
|
||||
agent: "architect"
|
||||
|
||||
@@ -48,24 +48,12 @@ phases:
|
||||
agent: "pm"
|
||||
command: "validate-prd"
|
||||
|
||||
- id: "create-epics-and-stories"
|
||||
optional: true
|
||||
agent: "pm"
|
||||
command: "create-epics-and-stories"
|
||||
note: "Optional: Create epic breakdown early (basic structure only)"
|
||||
|
||||
- id: "create-design"
|
||||
recommended: true
|
||||
agent: "ux-designer"
|
||||
command: "create-design"
|
||||
note: "Highly recommended for enterprise - design system and patterns"
|
||||
|
||||
- id: "create-epics-and-stories-after-ux"
|
||||
optional: true
|
||||
agent: "pm"
|
||||
command: "create-epics-and-stories"
|
||||
note: "Optional: Create epic breakdown with UX context"
|
||||
|
||||
- phase: 2
|
||||
name: "Solutioning"
|
||||
required: true
|
||||
@@ -103,11 +91,11 @@ phases:
|
||||
agent: "architect"
|
||||
command: "validate-architecture"
|
||||
|
||||
- id: "create-epics-and-stories-final"
|
||||
- id: "create-epics-and-stories"
|
||||
required: true
|
||||
agent: "pm"
|
||||
command: "create-epics-and-stories"
|
||||
note: "Required: Create final epic breakdown with full context (PRD + UX + Architecture)"
|
||||
note: "Required: Break down PRD into implementable epics and stories with full context (PRD + UX + Architecture)"
|
||||
|
||||
- id: "implementation-readiness"
|
||||
required: true
|
||||
|
||||
@@ -1,52 +0,0 @@
|
||||
# Game Development - Use BMGD Module
|
||||
# Game development workflows have been moved to the BMad Game Development module
|
||||
|
||||
project_type: "game"
|
||||
level: "all"
|
||||
field_type: "any"
|
||||
description: "⚠️ Game development requires the BMGD module"
|
||||
|
||||
error_message: |
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
|
||||
🎮 **GAME DEVELOPMENT DETECTED**
|
||||
|
||||
Game development workflows are now part of the **BMad Game Development (BMGD)** module,
|
||||
which provides specialized workflows and agents for game creation.
|
||||
|
||||
**To proceed with game development:**
|
||||
|
||||
1. Install the BMGD module:
|
||||
```bash
|
||||
bmad install bmgd
|
||||
```
|
||||
|
||||
2. The BMGD module includes:
|
||||
- Game Designer, Game Developer, Game Architect agents
|
||||
- Game Dev Scrum Master for sprint coordination
|
||||
- Industry-standard game dev workflows:
|
||||
• Phase 1 (Preproduction): brainstorm-game, game-brief
|
||||
• Phase 2 (Design): GDD, narrative design
|
||||
• Phase 3 (Technical): game architecture
|
||||
• Phase 4 (Production): sprint planning, story management
|
||||
|
||||
3. After installation, load the Game Designer or Game Dev Scrum Master agent
|
||||
to begin your game development workflow
|
||||
|
||||
**Why a separate module?**
|
||||
- Game development follows different phases than software development
|
||||
- Specialized agents understand game-specific terminology and patterns
|
||||
- Workflows configured for game development needs (playtesting, balancing, etc.)
|
||||
- Can be used standalone or alongside BMM for complete coverage
|
||||
|
||||
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
||||
|
||||
# Placeholder phases - this file should not be used for actual workflow tracking
|
||||
# Users should install BMGD module instead
|
||||
phases:
|
||||
- phase: 1
|
||||
name: "ERROR - Install BMGD Module"
|
||||
workflows:
|
||||
- id: "install-bmgd"
|
||||
required: true
|
||||
note: "Run: bmad install bmgd"
|
||||
@@ -59,23 +59,11 @@ phases:
|
||||
agent: "pm"
|
||||
command: "validate-prd"
|
||||
|
||||
- id: "create-epics-and-stories"
|
||||
optional: true
|
||||
agent: "pm"
|
||||
command: "create-epics-and-stories"
|
||||
note: "Optional: Create epic breakdown early (basic structure only)"
|
||||
|
||||
- id: "create-design"
|
||||
conditional: "if_has_ui"
|
||||
agent: "ux-designer"
|
||||
command: "create-design"
|
||||
|
||||
- id: "create-epics-and-stories-after-ux"
|
||||
optional: true
|
||||
agent: "pm"
|
||||
command: "create-epics-and-stories"
|
||||
note: "Optional: Create epic breakdown with UX context"
|
||||
|
||||
- phase: 2
|
||||
name: "Solutioning"
|
||||
required: true
|
||||
@@ -87,11 +75,11 @@ phases:
|
||||
output: "Integration architecture - solution design for THIS project"
|
||||
note: "HIGHLY RECOMMENDED: Distills massive brownfield context into focused solution design. Prevents agent confusion."
|
||||
|
||||
- id: "create-epics-and-stories-final"
|
||||
- id: "create-epics-and-stories"
|
||||
required: true
|
||||
agent: "pm"
|
||||
command: "create-epics-and-stories"
|
||||
note: "Required: Create final epic breakdown with full context (PRD + UX + Architecture)"
|
||||
note: "Required: Break down PRD into implementable epics and stories with full context (PRD + UX + Architecture)"
|
||||
|
||||
- id: "test-design"
|
||||
recommended: true
|
||||
|
||||
@@ -48,24 +48,12 @@ phases:
|
||||
command: "validate-prd"
|
||||
note: "Quality check for PRD completeness"
|
||||
|
||||
- id: "create-epics-and-stories"
|
||||
optional: true
|
||||
agent: "pm"
|
||||
command: "create-epics-and-stories"
|
||||
note: "Optional: Create epic breakdown early (basic structure only)"
|
||||
|
||||
- id: "create-design"
|
||||
conditional: "if_has_ui"
|
||||
agent: "ux-designer"
|
||||
command: "create-design"
|
||||
note: "Determined after PRD - user/agent decides if needed"
|
||||
|
||||
- id: "create-epics-and-stories-after-ux"
|
||||
optional: true
|
||||
agent: "pm"
|
||||
command: "create-epics-and-stories"
|
||||
note: "Optional: Create epic breakdown with UX context"
|
||||
|
||||
- phase: 2
|
||||
name: "Solutioning"
|
||||
required: true
|
||||
@@ -77,11 +65,11 @@ phases:
|
||||
output: "System architecture document"
|
||||
note: "Complete system design for greenfield projects"
|
||||
|
||||
- id: "create-epics-and-stories-final"
|
||||
- id: "create-epics-and-stories"
|
||||
required: true
|
||||
agent: "pm"
|
||||
command: "create-epics-and-stories"
|
||||
note: "Required: Create final epic breakdown with full context (PRD + UX + Architecture)"
|
||||
note: "Required: Break down PRD into implementable epics and stories with full context (PRD + UX + Architecture)"
|
||||
|
||||
- id: "test-design"
|
||||
recommended: true
|
||||
|
||||
Reference in New Issue
Block a user