Files
BMAD-METHOD/src/modules/bmm/docs/README.md
Brian Madison f17e4ef0b7 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.
2025-11-18 21:55:47 -06:00

7.5 KiB

BMM Documentation

Complete guides for the BMad Method Module (BMM) - AI-powered agile development workflows that adapt to your project's complexity.


🚀 Getting Started

New to BMM? Start here:

  • Quick Start Guide - Step-by-step guide to building your first project (15 min read)
    • Installation and setup
    • Understanding the four phases
    • Running your first workflows
    • Agent-based development flow

Quick Path: Install → workflow-init → Follow agent guidance

📊 Visual Overview

Complete Workflow Diagram - Visual flowchart showing all phases, agents (color-coded), and decision points for the BMad Method standard greenfield track.


📖 Core Concepts

Understanding how BMM adapts to your needs:

  • Scale Adaptive System - How BMM adapts to project size and complexity (42 min read)

    • Three planning tracks (Quick Flow, BMad Method, Enterprise Method)
    • Automatic track recommendation
    • Documentation requirements per track
    • Planning workflow routing
  • Quick Spec Flow - Fast-track workflow for Quick Flow track (26 min read)

    • Bug fixes and small features
    • Rapid prototyping approach
    • Auto-detection of stack and patterns
    • Minutes to implementation

🤖 Agents and Collaboration

Complete guide to BMM's AI agent team:

  • Agents Guide - Comprehensive agent reference (45 min read)

    • 12 specialized BMM agents + BMad Master
    • Agent roles, workflows, and when to use them
    • Agent customization system
    • Best practices and common patterns
  • Party Mode Guide - Multi-agent collaboration (20 min read)

    • How party mode works (19+ agents collaborate in real-time)
    • When to use it (strategic, creative, cross-functional, complex)
    • Example party compositions
    • Multi-module integration (BMM + CIS + BMB + custom)
    • Agent customization in party mode
    • Best practices

🔧 Working with Existing Code

Comprehensive guide for brownfield development:

  • Brownfield Development Guide - Complete guide for existing codebases (53 min read)
    • Documentation phase strategies
    • Track selection for brownfield
    • Integration with existing patterns
    • Phase-by-phase workflow guidance
    • Common scenarios

📚 Quick References

Essential reference materials:


🎯 Choose Your Path

I need to...

Build something new (greenfield) → Start with Quick Start Guide → Then review Scale Adaptive System to understand tracks

Fix a bug or add small feature → Go directly to Quick Spec Flow

Work with existing codebase (brownfield) → Read Brownfield Development Guide → Pay special attention to Phase 0 documentation requirements

Understand planning tracks and methodology → See Scale Adaptive System

Find specific commands or answers → Check FAQ


📋 Workflow Guides

Comprehensive documentation for all BMM workflows organized by phase:

  • Phase 1: Analysis Workflows - Optional exploration and research workflows (595 lines)

    • brainstorm-project, product-brief, research, and more
    • When to use analysis workflows
    • Creative and strategic tools
  • Phase 2: Planning Workflows - Scale-adaptive planning (967 lines)

    • prd, tech-spec, gdd, narrative, ux
    • Track-based planning approach (Quick Flow, BMad Method, Enterprise Method)
    • Which planning workflow to use
  • Phase 3: Solutioning Workflows - Architecture and validation (638 lines)

    • architecture, create-epics-and-stories, implementation-readiness
    • V6: Epics created AFTER architecture for better quality
    • Required for BMad Method and Enterprise Method tracks
    • Preventing agent conflicts
  • Phase 4: Implementation Workflows - Sprint-based development (1,634 lines)

    • sprint-planning, create-story, dev-story, code-review
    • Complete story lifecycle
    • One-story-at-a-time discipline
  • Testing & QA Workflows - Comprehensive quality assurance (1,420 lines)

    • Test strategy, automation, quality gates
    • TEA agent and test healing
    • BMad-integrated vs standalone modes

Total: 34 workflows documented across all phases

Advanced Workflow References

For detailed technical documentation on specific complex workflows:

  • Document Project Workflow Reference - Technical deep-dive (445 lines)

    • v1.2.0 context-safe architecture
    • Scan levels, resumability, write-as-you-go
    • Multi-part project detection
    • Deep-dive mode for targeted analysis
  • Architecture Workflow Reference - Decision architecture guide (320 lines)

    • Starter template intelligence
    • Novel pattern design
    • Implementation patterns for agent consistency
    • Adaptive facilitation approach

🧪 Testing and Quality

Quality assurance guidance:

  • Test design workflows
  • Quality gates
  • Risk assessment
  • NFR validation

🏗️ Module Structure

Understanding BMM components:

  • BMM Module README - Overview of module structure
    • Agent roster and roles
    • Workflow organization
    • Teams and collaboration
    • Best practices

🌐 External Resources

Community and Support

Additional Documentation

  • IDE Setup Guides - Configure your development environment
    • Claude Code
    • Cursor
    • Windsurf
    • VS Code
    • Other IDEs

📊 Documentation Map

flowchart TD
    START[New to BMM?]
    START --> QS[Quick Start Guide]

    QS --> DECIDE{What are you building?}

    DECIDE -->|Bug fix or<br/>small feature| QSF[Quick Spec Flow]
    DECIDE -->|New project| SAS[Scale Adaptive System]
    DECIDE -->|Existing codebase| BF[Brownfield Guide]

    QSF --> IMPL[Implementation]
    SAS --> IMPL
    BF --> IMPL

    IMPL --> REF[Quick References<br/>Glossary, FAQ]

    style START fill:#bfb,stroke:#333,stroke-width:2px,color:#000
    style QS fill:#bbf,stroke:#333,stroke-width:2px,color:#000
    style DECIDE fill:#ffb,stroke:#333,stroke-width:2px,color:#000
    style IMPL fill:#f9f,stroke:#333,stroke-width:2px,color:#000

💡 Tips for Using This Documentation

  1. Start with Quick Start if you're new - it provides the essential foundation
  2. Use the FAQ to find quick answers without reading entire guides
  3. Bookmark Glossary for terminology references while reading other docs
  4. Follow the suggested paths above based on your specific situation
  5. Join Discord for interactive help and community insights

Ready to begin?Start with the Quick Start Guide