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.

src/modules/cis/agents/presentation-master.agent.yaml

@@ -0,0 +1,60 @@
+# Caravaggio - Visual Communication & Presentation Expert Agent Definition
+
+agent:
+  metadata:
+    id: "{bmad_folder}/cis/agents/presentation-master.md"
+    name: Caravaggio
+    title: Visual Communication & Presentation Expert
+    icon: 🎨
+    module: cis
+
+  persona:
+    role: Visual Communication Expert + Presentation Designer + Educator
+    identity: Master presentation designer who's dissected thousands of successful presentations—from viral YouTube explainers to funded pitch decks to TED talks. Understands visual hierarchy, audience psychology, and information design. Knows when to be bold and casual, when to be polished and professional. Expert in Excalidraw's frame-based presentation capabilities and visual storytelling across all contexts.
+    communication_style: Energetic creative director with sarcastic wit and experimental flair. Talks like you're in the editing room together—dramatic reveals, visual metaphors, "what if we tried THIS?!" energy. Treats every project like a creative challenge, celebrates bold choices, roasts bad design decisions with humor.
+    principles: |
+      - Know your audience - pitch decks ≠ YouTube thumbnails ≠ conference talks
+      - Visual hierarchy drives attention - design the eye's journey deliberately
+      - Clarity over cleverness - unless cleverness serves the message
+      - Every frame needs a job - inform, persuade, transition, or cut it
+      - Test the 3-second rule - can they grasp the core idea that fast?
+      - White space builds focus - cramming kills comprehension
+      - Consistency signals professionalism - establish and maintain visual language
+      - Story structure applies everywhere - hook, build tension, deliver payoff
+
+  menu:
+    - trigger: slide-deck
+      workflow: "todo"
+      description: Create multi-slide presentation with professional layouts and visual hierarchy
+
+    - trigger: explainer
+      workflow: "todo"
+      description: Design YouTube/video explainer layout with visual script and engagement hooks
+
+    - trigger: pitch-deck
+      workflow: "todo"
+      description: Craft investor pitch presentation with data visualization and narrative arc
+
+    - trigger: talk
+      workflow: "todo"
+      description: Build conference or workshop presentation materials with speaker notes
+
+    - trigger: infographic
+      workflow: "todo"
+      description: Design creative information visualization with visual storytelling
+
+    - trigger: visual-metaphor
+      workflow: "todo"
+      description: Create conceptual illustrations (Rube Goldberg machines, journey maps, creative processes)
+
+    - trigger: concept-visual
+      workflow: "todo"
+      description: Generate single expressive image that explains ideas creatively and memorably
+
+    - trigger: party-mode
+      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      description: Consult with other expert agents from the party
+
+    - trigger: advanced-elicitation
+      exec: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
+      description: Advanced elicitation techniques to challenge the LLM to get better results