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/bmm/agents/architect.agent.yaml

@@ -32,6 +32,14 @@ agent:
       workflow: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/implementation-readiness/workflow.yaml"
       description: Validate implementation readiness - PRD, UX, Architecture, Epics aligned
 
+    - trigger: create-excalidraw-diagram
+      workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-diagram/workflow.yaml"
+      description: Create system architecture or technical diagram (Excalidraw)
+
+    - trigger: create-excalidraw-dataflow
+      workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-dataflow/workflow.yaml"
+      description: Create data flow diagram (Excalidraw)
+
     - trigger: party-mode
       workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
       description: Bring the whole team in to chat with other expert agents from the party

src/modules/bmm/agents/frame-expert.agent.yaml

@@ -1,42 +0,0 @@
-# Frame Expert Agent Definition
-
-agent:
-  webskip: true
-  metadata:
-    id: "{bmad_folder}/bmm/agents/frame-expert.md"
-    name: Saif
-    title: Visual Design & Diagramming Expert
-    icon: 📐
-    module: bmm
-
-  persona:
-    role: Expert Visual Designer & Diagramming Specialist
-    identity: Expert who creates visual representations using Excalidraw with optimized, reusable components. Specializes in flowcharts, diagrams, wire-frames, ERDs, UML diagrams, mind maps, data flows, and API mappings.
-    communication_style: "Visual thinker who talks in shapes and flows. Presents options as numbered lists, explains diagrams like describing a painting."
-    principles: |
-      - Composition Over Creation - Use reusable components and templates. Minimal Payload - Strip unnecessary metadata, optimize serialization.
-      - Reference-Based Design - Use library references instead of redefining components. Structured Approach - Follow task-specific workflows for different diagram types.
-      - Clean Output - Remove history, deleted elements, unused styles from final output. JSON Validation
-      - Always validate JSON syntax after saving files using validation tool.
-      - Error Recovery - NEVER delete files due to syntax errors, always fix them using error location information.
-
-  menu:
-    - trigger: flowchart
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/frame-expert/create-flowchart/workflow.yaml"
-      description: Create flowchart for processes, pipelines, or logic flows
-
-    - trigger: diagram
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/frame-expert/create-diagram/workflow.yaml"
-      description: Create system architecture or general technical diagram
-
-    - trigger: dataflow
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/frame-expert/create-dataflow/workflow.yaml"
-      description: Create data flow diagram
-
-    - trigger: wireframe
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/frame-expert/create-wireframe/workflow.yaml"
-      description: Create website or app wireframe
-
-    - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
-      description: Bring the whole team in to chat with other expert agents from the party

src/modules/bmm/agents/pm.agent.yaml

@@ -30,7 +30,7 @@ agent:
       description: Create Product Requirements Document (PRD)
 
     - trigger: create-epics-and-stories
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-epics-and-stories/workflow.yaml"
+      workflow: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.yaml"
       description: Break PRD requirements into implementable epics and stories
 
     - trigger: validate-prd
@@ -54,6 +54,10 @@ agent:
       description: Course Correction Analysis
       ide-only: true
 
+    - trigger: create-excalidraw-flowchart
+      workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-flowchart/workflow.yaml"
+      description: Create process or feature flow diagram (Excalidraw)
+
     - trigger: party-mode
       workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
       description: Bring the whole team in to chat with other expert agents from the party

src/modules/bmm/agents/tech-writer.agent.yaml

@@ -38,10 +38,22 @@ agent:
       workflow: "todo"
       description: Review documentation quality and suggest improvements
 
-    - trigger: generate-diagram
+    - trigger: generate-mermaid
       action: "Create a Mermaid diagram based on user description. Ask for diagram type (flowchart, sequence, class, ER, state, git) and content, then generate properly formatted Mermaid syntax following CommonMark fenced code block standards."
       description: Generate Mermaid diagrams (architecture, sequence, flow, ER, class, state)
 
+    - trigger: create-excalidraw-flowchart
+      workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-flowchart/workflow.yaml"
+      description: Create Excalidraw flowchart for processes and logic flows
+
+    - trigger: create-excalidraw-diagram
+      workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-diagram/workflow.yaml"
+      description: Create Excalidraw system architecture or technical diagram
+
+    - trigger: create-excalidraw-dataflow
+      workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-dataflow/workflow.yaml"
+      description: Create Excalidraw data flow diagram
+
     - trigger: validate-doc
       action: "Review the specified document against CommonMark standards, technical writing best practices, and style guide compliance. Provide specific, actionable improvement suggestions organized by priority."
       description: Validate documentation against standards and best practices

src/modules/bmm/agents/ux-designer.agent.yaml

@@ -29,6 +29,10 @@ agent:
       document: "{output_folder}/ux-spec.md"
       description: Validate UX Specification and Design Artifacts
 
+    - trigger: create-excalidraw-wireframe
+      workflow: "{project-root}/{bmad_folder}/bmm/workflows/diagrams/create-wireframe/workflow.yaml"
+      description: Create website or app wireframe (Excalidraw)
+
     - trigger: party-mode
       workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
       description: Bring the whole team in to chat with other expert agents from the party