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 | ||
| teams | ||
| workflows | ||
| readme.md | ||
readme.md
CIS - Creative Intelligence Suite
AI-powered creative facilitation transforming strategic thinking through expert coaching across five specialized domains.
Table of Contents
- Core Capabilities
- Specialized Agents
- Interactive Workflows
- Quick Start
- Key Differentiators
- Configuration
Core Capabilities
CIS provides structured creative methodologies through distinctive agent personas who act as master facilitators, drawing out insights through strategic questioning rather than generating solutions directly.
Specialized Agents
View detailed agent descriptions →
- Carson - Brainstorming Specialist (energetic facilitator)
- Maya - Design Thinking Maestro (jazz-like improviser)
- Dr. Quinn - Problem Solver (detective-scientist hybrid)
- Victor - Innovation Oracle (bold strategic precision)
- Sophia - Master Storyteller (whimsical narrator)
Interactive Workflows
5 Workflows with 150+ Creative Techniques:
Brainstorming
36 techniques across 7 categories for ideation
- Divergent/convergent thinking
- Lateral connections
- Forced associations
Design Thinking
Complete 5-phase human-centered process
- Empathize → Define → Ideate → Prototype → Test
- User journey mapping
- Rapid iteration
Problem Solving
Systematic root cause analysis
- 5 Whys, Fishbone diagrams
- Solution generation
- Impact assessment
Innovation Strategy
Business model disruption
- Blue Ocean Strategy
- Jobs-to-be-Done
- Disruptive innovation patterns
Storytelling
25 narrative frameworks
- Hero's Journey
- Story circles
- Compelling pitch structures
Quick Start
Direct Workflow
# Start interactive session
workflow brainstorming
# With context document
workflow design-thinking --data /path/to/context.md
Agent-Facilitated
# Load agent
agent cis/brainstorming-coach
# Start workflow
> *brainstorm
Key Differentiators
- Facilitation Over Generation - Guides discovery through questions
- Energy-Aware Sessions - Adapts to engagement levels
- Context Integration - Domain-specific guidance support
- Persona-Driven - Unique communication styles
- Rich Method Libraries - 150+ proven techniques
Configuration
Edit /{bmad_folder}/cis/config.yaml:
output_folder: ./creative-outputs
user_name: Your Name
communication_language: english
Module Structure
cis/
├── agents/ # 5 specialized facilitators
├── workflows/ # 5 interactive processes
│ ├── brainstorming/
│ ├── design-thinking/
│ ├── innovation-strategy/
│ ├── problem-solving/
│ └── storytelling/
├── tasks/ # Supporting operations
└── teams/ # Agent collaborations
Integration Points
CIS workflows integrate with:
- BMM - Powers project brainstorming
- BMB - Creative module design
- Custom Modules - Shared creative resource
Best Practices
- Set clear objectives before starting sessions
- Provide context documents for domain relevance
- Trust the process - Let facilitation guide you
- Take breaks when energy flags
- Document insights as they emerge
Related Documentation
- Workflow Guide - Detailed workflow instructions
- Agent Personas - Full agent descriptions
- BMM Integration - Development workflow connection
Part of BMad Method v6.0 - Transform creative potential through expert AI facilitation.