External/BMAD-METHOD
1
0
Fork 0
mirror of https://github.com/bmadcode/BMAD-METHOD.git synced 2025-12-29 16:14:59 +00:00
Code Issues Packages Projects Releases Wiki Activity
BMAD-METHOD/docs/modules/bmm-bmad-method/images/workflow-method-greenfield.excalidraw

5034 lines
116 KiB
Plaintext
Raw Permalink Normal View History

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:54:48 -06:00
{
"type": "excalidraw",
"version": 2,
"source": "https://marketplace.visualstudio.com/items?itemName=pomdtr.excalidraw-editor",
"elements": [
{
"id": "title",
"type": "text",
"x": 284.6321356748704,
"y": 20,
"width": 673.7520141601562,
"height": 37.15738334525602,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"fontSize": 29.725906676204815,
"fontFamily": 1,
"text": "BMad Method Workflow - Standard Greenfield",
"textAlign": "center",
"verticalAlign": "top",
"locked": false,
"version": 67,
"versionNonce": 1431078555,
"index": "a0",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522299028,
"link": null,
"containerId": null,
"originalText": "BMad Method Workflow - Standard Greenfield",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "start-ellipse",
"type": "ellipse",
"x": 60,
"y": 80,
"width": 120,
"height": 60,
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "#e3f2fd",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"start-group"
],
"boundElements": [
{
"type": "text",
"id": "start-text"
},
{
"type": "arrow",
"id": "arrow-start-discovery"
}
],
"locked": false,
"version": 2,
"versionNonce": 1364787547,
"index": "a1",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"updated": 1763522171079,
"link": null
},
{
"id": "start-text",
"type": "text",
"x": 93,
"y": 98,
"width": 54,
"height": 25,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"start-group"
],
"fontSize": 20,
"fontFamily": 1,
"text": "Start",
"textAlign": "center",
"verticalAlign": "middle",
"containerId": "start-ellipse",
"locked": false,
"version": 2,
"versionNonce": 1303811541,
"index": "a2",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522171079,
"link": null,
"originalText": "Start",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "phase1-header",
"type": "text",
"x": 13.742901708014983,
"y": 180.0057616006372,
"width": 200,
"height": 30,
"angle": 0,
"strokeColor": "#2e7d32",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"fontSize": 24,
"fontFamily": 1,
"text": "PHASE 1",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
"version": 18,
"versionNonce": 1987415189,
"index": "a3",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522322404,
"link": null,
"containerId": null,
"originalText": "PHASE 1",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "phase1-subtitle",
"type": "text",
"x": 140.26189010000303,
"y": 168.98316506386624,
"width": 75.31195068359375,
"height": 40,
"angle": 0,
"strokeColor": "#666666",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"fontSize": 16,
"fontFamily": 1,
"text": "Discovery\n(Optional)",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
"version": 225,
"versionNonce": 1515322069,
"index": "a4",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522324513,
"link": null,
"containerId": null,
"originalText": "Discovery\n(Optional)",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "arrow-start-discovery",
"type": "arrow",
"x": 120,
"y": 140,
"width": 0,
"height": 100,
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
"elementId": "start-ellipse",
"focus": 0,
"gap": 1
},
"endBinding": {
"elementId": "decision-discovery",
"focus": 0,
"gap": 1
},
"points": [
[
0,
0
],
[
0,
100
]
],
"lastCommittedPoint": null,
"version": 2,
"versionNonce": 2116462235,
"index": "a5",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522171079,
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow"
},
{
"id": "decision-discovery",
"type": "diamond",
"x": 40,
"y": 240,
"width": 160,
"height": 100,
"angle": 0,
"strokeColor": "#f57c00",
"backgroundColor": "#fff3e0",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"decision-discovery-group"
],
"boundElements": [
{
"type": "text",
"id": "decision-discovery-text"
},
{
"type": "arrow",
"id": "arrow-start-discovery"
},
{
"type": "arrow",
"id": "arrow-discovery-yes"
},
{
"type": "arrow",
"id": "arrow-discovery-no"
}
],
"locked": false,
"version": 2,
"versionNonce": 1508959381,
"index": "a6",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"updated": 1763522171079,
"link": null
},
{
"id": "decision-discovery-text",
"type": "text",
"x": 55,
"y": 265,
"width": 130,
"height": 50,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"decision-discovery-group"
],
"fontSize": 16,
"fontFamily": 1,
"text": "Include\nDiscovery?",
"textAlign": "center",
"verticalAlign": "middle",
"containerId": "decision-discovery",
"locked": false,
"version": 2,
"versionNonce": 627907387,
"index": "a7",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522171079,
"link": null,
"originalText": "Include\nDiscovery?",
"autoResize": true,
"lineHeight": 1.5625
},
{
"id": "arrow-discovery-yes",
"type": "arrow",
"x": 120,
"y": 340,
"width": 0,
"height": 40,
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
"elementId": "decision-discovery",
"focus": 0,
"gap": 1
},
"endBinding": {
"elementId": "proc-brainstorm",
"focus": 0,
"gap": 1
},
"points": [
[
0,
0
],
[
0,
40
]
],
"lastCommittedPoint": null,
"version": 2,
"versionNonce": 133270005,
"index": "a8",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522171079,
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow"
},
{
"id": "label-yes-discovery",
"type": "text",
"x": 130,
"y": 350,
"width": 30,
"height": 20,
"angle": 0,
"strokeColor": "#2e7d32",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"fontSize": 16,
"fontFamily": 1,
"text": "Yes",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
"version": 2,
"versionNonce": 1362885595,
"index": "a9",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522171079,
"link": null,
"containerId": null,
"originalText": "Yes",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "proc-brainstorm",
"type": "rectangle",
"x": 40,
"y": 380,
"width": 160,
"height": 80,
"angle": 0,
"strokeColor": "#00acc1",
"backgroundColor": "#b2ebf2",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"roundness": {
"type": 3,
"value": 8
},
"groupIds": [
"proc-brainstorm-group"
],
"boundElements": [
{
"type": "text",
"id": "proc-brainstorm-text"
},
{
"type": "arrow",
"id": "arrow-discovery-yes"
},
{
"type": "arrow",
"id": "arrow-brainstorm-research"
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
},
{
"id": "jv0rnlK2D9JKIGTO7pUtT",
"type": "arrow"
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:54:48 -06:00
}
],
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 3,
"versionNonce": 115423290,
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:54:48 -06:00
"index": "aA",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191341773,
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:54:48 -06:00
"link": null
},
{
"id": "proc-brainstorm-text",
"type": "text",
"x": 50,
"y": 395,
"width": 140,
"height": 50,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"proc-brainstorm-group"
],
"fontSize": 14,
"fontFamily": 1,
"text": "Brainstorm\n<<optional>>",
"textAlign": "center",
"verticalAlign": "middle",
"containerId": "proc-brainstorm",
"locked": false,
"version": 2,
"versionNonce": 765839483,
"index": "aB",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522171079,
"link": null,
"originalText": "Brainstorm\n<<optional>>",
"autoResize": true,
"lineHeight": 1.7857142857142858
},
{
"id": "arrow-brainstorm-research",
"type": "arrow",
"x": 120,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"y": 460.45161416125165,
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:54:48 -06:00
"width": 0,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"height": 29.096771677496633,
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:54:48 -06:00
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
"elementId": "proc-brainstorm",
"focus": 0,
"gap": 1
},
"endBinding": {
"elementId": "proc-research",
"focus": 0,
"gap": 1
},
"points": [
[
0,
0
],
[
0,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
29.096771677496633
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:54:48 -06:00
]
],
"lastCommittedPoint": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 3,
"versionNonce": 828709094,
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:54:48 -06:00
"index": "aC",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191023838,
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:54:48 -06:00
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow"
},
{
"id": "proc-research",
"type": "rectangle",
"x": 40,
"y": 490,
"width": 160,
"height": 80,
"angle": 0,
"strokeColor": "#00acc1",
"backgroundColor": "#b2ebf2",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"roundness": {
"type": 3,
"value": 8
},
"groupIds": [
"proc-research-group"
],
"boundElements": [
{
"type": "text",
"id": "proc-research-text"
},
{
"type": "arrow",
"id": "arrow-brainstorm-research"
},
{
"type": "arrow",
"id": "arrow-research-brief"
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
},
{
"id": "RF10FfKbmG72P77I2IoP4",
"type": "arrow"
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:54:48 -06:00
}
],
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 5,
"versionNonce": 987493562,
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:54:48 -06:00
"index": "aD",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191042826,
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:54:48 -06:00
"link": null
},
{
"id": "proc-research-text",
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 78.26604461669922,
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:54:48 -06:00
"y": 505,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"width": 83.46791076660156,
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:54:48 -06:00
"height": 50,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"proc-research-group"
],
"fontSize": 14,
"fontFamily": 1,
"text": "Research\n<<optional>>",
"textAlign": "center",
"verticalAlign": "middle",
"containerId": "proc-research",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 5,
"versionNonce": 92329914,
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:54:48 -06:00
"index": "aE",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191023838,
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:54:48 -06:00
"link": null,
"originalText": "Research\n<<optional>>",
"autoResize": true,
"lineHeight": 1.7857142857142858
},
{
"id": "arrow-research-brief",
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 120.00000000000001,
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:54:48 -06:00
"y": 570.4516141612517,
"width": 0,
"height": 29.09677167749669,
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
"elementId": "proc-research",
"focus": 0,
"gap": 1
},
"endBinding": {
"elementId": "proc-product-brief",
"focus": 0,
"gap": 1
},
"points": [
[
0,
0
],
[
0,
29.09677167749669
]
],
"lastCommittedPoint": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 4,
"versionNonce": 1012730918,
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:54:48 -06:00
"index": "aF",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191023838,
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:54:48 -06:00
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow"
},
{
"id": "proc-product-brief",
"type": "rectangle",
"x": 40,
"y": 600,
"width": 160,
"height": 80,
"angle": 0,
"strokeColor": "#00acc1",
"backgroundColor": "#b2ebf2",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"roundness": {
"type": 3,
"value": 8
},
"groupIds": [
"proc-product-brief-group"
],
"boundElements": [
{
"type": "text",
"id": "proc-product-brief-text"
},
{
"type": "arrow",
"id": "arrow-research-brief"
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
},
{
"id": "arrow-phase1-to-phase2",
"type": "arrow"
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:54:48 -06:00
}
],
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 6,
"versionNonce": 1568298662,
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:54:48 -06:00
"index": "aG",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190985483,
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:54:48 -06:00
"link": null
},
{
"id": "proc-product-brief-text",
"type": "text",
"x": 72.69404602050781,
"y": 615,
"width": 94.61190795898438,
"height": 50,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"proc-product-brief-group"
],
"fontSize": 14,
"fontFamily": 1,
"text": "Product Brief\n<<optional>>",
"textAlign": "center",
"verticalAlign": "middle",
"containerId": "proc-product-brief",
"locked": false,
"version": 3,
"versionNonce": 1653785435,
"index": "aH",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522366663,
"link": null,
"originalText": "Product Brief\n<<optional>>",
"autoResize": true,
"lineHeight": 1.7857142857142858
},
{
"id": "arrow-discovery-no",
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 199.68944196572753,
"y": 290.14813727772287,
"width": 154.38771404438515,
"height": 0.2869361997344413,
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:54:48 -06:00
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
"elementId": "decision-discovery",
"focus": 0,
"gap": 1
},
"endBinding": {
"elementId": "proc-prd",
"focus": 0,
"gap": 5.918648042715176
},
"points": [
[
0,
0
],
[
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
154.38771404438515,
0.2869361997344413
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:54:48 -06:00
]
],
"lastCommittedPoint": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 134,
"versionNonce": 1651808102,
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:54:48 -06:00
"index": "aI",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191023838,
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:54:48 -06:00
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow"
},
{
"id": "label-no-discovery",
"type": "text",
"x": 220,
"y": 270,
"width": 25,
"height": 20,
"angle": 0,
"strokeColor": "#d32f2f",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"fontSize": 16,
"fontFamily": 1,
"text": "No",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
"version": 2,
"versionNonce": 198980347,
"index": "aJ",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522171079,
"link": null,
"containerId": null,
"originalText": "No",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "arrow-phase1-to-phase2",
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 200.89221334296062,
"y": 647.2552625380853,
"width": 155.54926796151912,
"height": 344.1924874570816,
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:54:48 -06:00
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"startBinding": {
"elementId": "proc-product-brief",
"focus": 0.6109361701343846,
"gap": 1
},
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:54:48 -06:00
"endBinding": {
"elementId": "proc-prd",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"focus": 0.48602478253370496,
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:54:48 -06:00
"gap": 3.21773034122549
},
"points": [
[
0,
0
],
[
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
71.35560764925268,
-38.29318660613865
],
[
84.68337472706096,
-292.7672603376131
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:54:48 -06:00
],
[
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
155.54926796151912,
-344.1924874570816
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:54:48 -06:00
]
],
"lastCommittedPoint": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 1393,
"versionNonce": 261518822,
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:54:48 -06:00
"index": "aK",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": {
"type": 2
},
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191023838,
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:54:48 -06:00
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow",
"elbowed": false
},
{
"id": "phase2-header",
"type": "text",
"x": 340,
"y": 180,
"width": 200,
"height": 30,
"angle": 0,
"strokeColor": "#2e7d32",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"fontSize": 24,
"fontFamily": 1,
"text": "PHASE 2",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
"version": 2,
"versionNonce": 292690843,
"index": "aL",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522171079,
"link": null,
"containerId": null,
"originalText": "PHASE 2",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "phase2-subtitle",
"type": "text",
"x": 340,
"y": 210,
"width": 200,
"height": 20,
"angle": 0,
"strokeColor": "#666666",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"fontSize": 16,
"fontFamily": 1,
"text": "Planning (Required)",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
"version": 2,
"versionNonce": 184762261,
"index": "aM",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522171079,
"link": null,
"containerId": null,
"originalText": "Planning (Required)",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "proc-prd",
"type": "rectangle",
"x": 359.2970847222632,
"y": 250.5934448656302,
"width": 160,
"height": 80,
"angle": 0,
"strokeColor": "#43a047",
"backgroundColor": "#c8e6c9",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"roundness": {
"type": 3,
"value": 8
},
"groupIds": [
"proc-prd-group"
],
"boundElements": [
{
"type": "text",
"id": "proc-prd-text"
},
{
"type": "arrow",
"id": "arrow-discovery-no"
},
{
"id": "arrow-phase1-to-phase2",
"type": "arrow"
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
},
{
"id": "RF10FfKbmG72P77I2IoP4",
"type": "arrow"
},
{
"id": "jv0rnlK2D9JKIGTO7pUtT",
"type": "arrow"
},
{
"id": "arrow-has-ui-no",
"type": "arrow"
fix(bmm): remove stale validate-prd references (fixes #1030) (#1038) - Remove validate-prd workflow references from all workflow path YAML files - Update Excalidraw diagram: remove Validate PRD box and zombie JSON elements - Re-export SVG at 1x scale - Standardize implementation-readiness descriptions across all docs - Add validation script (validate-svg-changes.sh) and README for SVG export process - Correct Excalidraw timestamps 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Brian <bmadcode@gmail.com>
2025-12-05 19:35:46 -08:00
},
{
"id": "arrow-prd-hasui",
"type": "arrow"
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:54:48 -06:00
}
],
"locked": false,
fix(bmm): remove stale validate-prd references (fixes #1030) (#1038) - Remove validate-prd workflow references from all workflow path YAML files - Update Excalidraw diagram: remove Validate PRD box and zombie JSON elements - Re-export SVG at 1x scale - Standardize implementation-readiness descriptions across all docs - Add validation script (validate-svg-changes.sh) and README for SVG export process - Correct Excalidraw timestamps 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Brian <bmadcode@gmail.com>
2025-12-05 19:35:46 -08:00
"version": 108,
"versionNonce": 930129275,
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:54:48 -06:00
"index": "aN",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
fix(bmm): remove stale validate-prd references (fixes #1030) (#1038) - Remove validate-prd workflow references from all workflow path YAML files - Update Excalidraw diagram: remove Validate PRD box and zombie JSON elements - Re-export SVG at 1x scale - Standardize implementation-readiness descriptions across all docs - Add validation script (validate-svg-changes.sh) and README for SVG export process - Correct Excalidraw timestamps 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Brian <bmadcode@gmail.com>
2025-12-05 19:35:46 -08:00
"updated": 1764952855000,
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:54:48 -06:00
"link": null
},
{
"id": "proc-prd-text",
"type": "text",
"x": 418.107097539646,
"y": 278.0934448656302,
"width": 42.379974365234375,
"height": 25,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"proc-prd-group"
],
"fontSize": 20,
"fontFamily": 1,
"text": "PRD",
"textAlign": "center",
"verticalAlign": "middle",
"containerId": "proc-prd",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 103,
"versionNonce": 1402977702,
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:54:48 -06:00
"index": "aO",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191023837,
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:54:48 -06:00
"link": null,
"originalText": "PRD",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "decision-has-ui",
"type": "diamond",
"x": 360,
"y": 470,
"width": 160,
"height": 100,
"angle": 0,
"strokeColor": "#f57c00",
"backgroundColor": "#fff3e0",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"decision-has-ui-group"
],
"boundElements": [
{
"type": "text",
"id": "decision-has-ui-text"
},
{
"type": "arrow",
fix(bmm): remove stale validate-prd references (fixes #1030) (#1038) - Remove validate-prd workflow references from all workflow path YAML files - Update Excalidraw diagram: remove Validate PRD box and zombie JSON elements - Re-export SVG at 1x scale - Standardize implementation-readiness descriptions across all docs - Add validation script (validate-svg-changes.sh) and README for SVG export process - Correct Excalidraw timestamps 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Brian <bmadcode@gmail.com>
2025-12-05 19:35:46 -08:00
"id": "arrow-prd-hasui"
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:54:48 -06:00
},
{
"type": "arrow",
"id": "arrow-has-ui-yes"
},
{
"type": "arrow",
"id": "arrow-has-ui-no"
}
],
"locked": false,
fix(bmm): remove stale validate-prd references (fixes #1030) (#1038) - Remove validate-prd workflow references from all workflow path YAML files - Update Excalidraw diagram: remove Validate PRD box and zombie JSON elements - Re-export SVG at 1x scale - Standardize implementation-readiness descriptions across all docs - Add validation script (validate-svg-changes.sh) and README for SVG export process - Correct Excalidraw timestamps 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Brian <bmadcode@gmail.com>
2025-12-05 19:35:46 -08:00
"version": 3,
"versionNonce": 1003877916,
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:54:48 -06:00
"index": "aT",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
fix(bmm): remove stale validate-prd references (fixes #1030) (#1038) - Remove validate-prd workflow references from all workflow path YAML files - Update Excalidraw diagram: remove Validate PRD box and zombie JSON elements - Re-export SVG at 1x scale - Standardize implementation-readiness descriptions across all docs - Add validation script (validate-svg-changes.sh) and README for SVG export process - Correct Excalidraw timestamps 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Brian <bmadcode@gmail.com>
2025-12-05 19:35:46 -08:00
"updated": 1764952855000,
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:54:48 -06:00
"link": null
},
{
"id": "decision-has-ui-text",
"type": "text",
"x": 375,
"y": 495,
"width": 130,
"height": 50,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"decision-has-ui-group"
],
"fontSize": 16,
"fontFamily": 1,
"text": "Has UI?",
"textAlign": "center",
"verticalAlign": "middle",
"containerId": "decision-has-ui",
"locked": false,
"version": 2,
"versionNonce": 222317845,
"index": "aU",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522171080,
"link": null,
"originalText": "Has UI?",
"autoResize": true,
"lineHeight": 3.125
},
{
"id": "arrow-has-ui-yes",
"type": "arrow",
"x": 440,
"y": 570,
"width": 0,
"height": 30,
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
"elementId": "decision-has-ui",
"focus": 0,
"gap": 1
},
"endBinding": {
"elementId": "proc-ux-design",
"focus": 0,
"gap": 1
},
"points": [
[
0,
0
],
[
0,
30
]
],
"lastCommittedPoint": null,
"version": 2,
"versionNonce": 528906939,
"index": "aV",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522171080,
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow"
},
{
"id": "label-yes-ui",
"type": "text",
"x": 450,
"y": 580,
"width": 30,
"height": 20,
"angle": 0,
"strokeColor": "#2e7d32",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"fontSize": 16,
"fontFamily": 1,
"text": "Yes",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
"version": 2,
"versionNonce": 1581245045,
"index": "aW",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522171080,
"link": null,
"containerId": null,
"originalText": "Yes",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "proc-ux-design",
"type": "rectangle",
"x": 360,
"y": 600,
"width": 160,
"height": 80,
"angle": 0,
"strokeColor": "#8e24aa",
"backgroundColor": "#e1bee7",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"roundness": {
"type": 3,
"value": 8
},
"groupIds": [
"proc-ux-design-group"
],
"boundElements": [
{
"type": "text",
"id": "proc-ux-design-text"
},
{
"type": "arrow",
"id": "arrow-has-ui-yes"
},
{
"type": "arrow",
"id": "arrow-ux-to-phase3"
}
],
"locked": false,
"version": 2,
"versionNonce": 268266331,
"index": "aX",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"updated": 1763522171080,
"link": null
},
{
"id": "proc-ux-design-text",
"type": "text",
"x": 370,
"y": 628,
"width": 140,
"height": 25,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"proc-ux-design-group"
],
"fontSize": 20,
"fontFamily": 1,
"text": "Create UX",
"textAlign": "center",
"verticalAlign": "middle",
"containerId": "proc-ux-design",
"locked": false,
"version": 2,
"versionNonce": 157666261,
"index": "aY",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522171080,
"link": null,
"originalText": "Create UX",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "arrow-has-ui-no",
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 517.6863546461885,
"y": 287.4640953051147,
"width": 158.4487370618814,
"height": 25.521141112371026,
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:54:48 -06:00
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"elementId": "proc-prd",
"focus": -0.13686633304390483,
"gap": 1.6107300760746739
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:54:48 -06:00
},
"endBinding": {
"elementId": "proc-architecture",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"focus": 0.16050512337240405,
"gap": 6.573819526326588
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:54:48 -06:00
},
"points": [
[
0,
0
],
[
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
65.15287677643596,
2.2657676476494544
],
[
111.59197355857077,
25.521141112371026
],
[
158.4487370618814,
24.060724236900796
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:54:48 -06:00
]
],
"lastCommittedPoint": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 831,
"versionNonce": 1382987110,
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:54:48 -06:00
"index": "aZ",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"roundness": {
"type": 2
},
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:54:48 -06:00
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191570205,
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:54:48 -06:00
"link": null,
"locked": false,
"startArrowhead": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"endArrowhead": "arrow",
"elbowed": false
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:54:48 -06:00
},
{
"id": "label-no-ui",
"type": "text",
"x": 540,
"y": 500,
"width": 25,
"height": 20,
"angle": 0,
"strokeColor": "#d32f2f",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"fontSize": 16,
"fontFamily": 1,
"text": "No",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 5,
"versionNonce": 183981370,
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:54:48 -06:00
"index": "aa",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"boundElements": [
{
"id": "arrow-has-ui-no",
"type": "arrow"
}
],
"updated": 1764191508105,
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:54:48 -06:00
"link": null,
"containerId": null,
"originalText": "No",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "arrow-ux-to-phase3",
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 523.3221723982787,
"y": 642.0805139439535,
"width": 158.4945254931572,
"height": 296.63050159541245,
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:54:48 -06:00
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
"elementId": "proc-ux-design",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"focus": 0.5906867967554547,
"gap": 3.322172398278667
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:54:48 -06:00
},
"endBinding": {
"elementId": "proc-architecture",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"focus": 0.3856343135512404,
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:54:48 -06:00
"gap": 1
},
"points": [
[
0,
0
],
[
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
76.98345162139776,
-45.99075822656016
],
[
116.19277860378315,
-258.3973533698057
],
[
158.4945254931572,
-296.63050159541245
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:54:48 -06:00
]
],
"lastCommittedPoint": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 328,
"versionNonce": 517434918,
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:54:48 -06:00
"index": "ab",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"roundness": {
"type": 2
},
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:54:48 -06:00
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191529677,
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:54:48 -06:00
"link": null,
"locked": false,
"startArrowhead": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"endArrowhead": "arrow",
"elbowed": false
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:54:48 -06:00
},
{
"id": "phase3-header",
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 709.0199784799299,
"y": 181.88359184111607,
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:54:48 -06:00
"width": 200,
"height": 30,
"angle": 0,
"strokeColor": "#2e7d32",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"fontSize": 24,
"fontFamily": 1,
"text": "PHASE 3",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 32,
"versionNonce": 1258326202,
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:54:48 -06:00
"index": "ac",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190667244,
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:54:48 -06:00
"link": null,
"containerId": null,
"originalText": "PHASE 3",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "phase3-subtitle",
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 687.4485256281371,
"y": 215.63080811867223,
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:54:48 -06:00
"width": 220,
"height": 20,
"angle": 0,
"strokeColor": "#666666",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"fontSize": 16,
"fontFamily": 1,
"text": "Solutioning (Required)",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 35,
"versionNonce": 360954426,
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:54:48 -06:00
"index": "ad",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190669111,
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:54:48 -06:00
"link": null,
"containerId": null,
"originalText": "Solutioning (Required)",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "proc-architecture",
"type": "rectangle",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 682.7089112343965,
"y": 275.64692474279855,
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:54:48 -06:00
"width": 160,
"height": 80,
"angle": 0,
"strokeColor": "#f4511e",
"backgroundColor": "#ffccbc",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"roundness": {
"type": 3,
"value": 8
},
"groupIds": [
"proc-architecture-group"
],
"boundElements": [
{
"type": "text",
"id": "proc-architecture-text"
},
{
"type": "arrow",
"id": "arrow-ux-to-phase3"
},
{
"type": "arrow",
"id": "arrow-arch-epics"
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
},
{
"id": "arrow-has-ui-no",
"type": "arrow"
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:54:48 -06:00
}
],
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 90,
"versionNonce": 1912262330,
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:54:48 -06:00
"index": "ae",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191508105,
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:54:48 -06:00
"link": null
},
{
"id": "proc-architecture-text",
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 692.7089112343965,
"y": 303.64692474279855,
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:54:48 -06:00
"width": 140,
"height": 25,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"proc-architecture-group"
],
"fontSize": 20,
"fontFamily": 1,
"text": "Architecture",
"textAlign": "center",
"verticalAlign": "middle",
"containerId": "proc-architecture",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 88,
"versionNonce": 452440186,
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:54:48 -06:00
"index": "af",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191451669,
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:54:48 -06:00
"link": null,
"originalText": "Architecture",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "arrow-arch-epics",
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 760.6640738654764,
"y": 358.02872135607737,
"width": 0.007789277755136936,
"height": 35.679359419065065,
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:54:48 -06:00
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
"elementId": "proc-architecture",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"focus": 0.025673321057619772,
"gap": 2.381796613278823
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:54:48 -06:00
},
"endBinding": {
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"elementId": "proc-validate-arch",
"focus": -0.09156227842994098,
"gap": 2.5273595258319688
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:54:48 -06:00
},
"points": [
[
0,
0
],
[
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
0.007789277755136936,
35.679359419065065
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:54:48 -06:00
]
],
"lastCommittedPoint": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 549,
"versionNonce": 1665519674,
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:54:48 -06:00
"index": "ag",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191459184,
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:54:48 -06:00
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow"
},
{
"id": "proc-epics",
"type": "rectangle",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 670.1028230821919,
"y": 510.76268244350774,
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:54:48 -06:00
"width": 160,
"height": 80,
"angle": 0,
"strokeColor": "#43a047",
"backgroundColor": "#c8e6c9",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"roundness": {
"type": 3,
"value": 8
},
"groupIds": [
"proc-epics-group"
],
"boundElements": [
{
"type": "text",
"id": "proc-epics-text"
},
{
"type": "arrow",
"id": "arrow-arch-epics"
},
{
"type": "arrow",
"id": "arrow-epics-test"
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
},
{
"id": "arrow-validate-ready",
"type": "arrow"
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:54:48 -06:00
}
],
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 178,
"versionNonce": 1597058278,
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:54:48 -06:00
"index": "ah",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191442604,
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:54:48 -06:00
"link": null
},
{
"id": "proc-epics-text",
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 680.1028230821919,
"y": 538.7626824435077,
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:54:48 -06:00
"width": 140,
"height": 25,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"proc-epics-group"
],
"fontSize": 20,
"fontFamily": 1,
"text": "Epics/Stories",
"textAlign": "center",
"verticalAlign": "middle",
"containerId": "proc-epics",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 177,
"versionNonce": 2105920614,
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:54:48 -06:00
"index": "ai",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191427908,
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:54:48 -06:00
"link": null,
"originalText": "Epics/Stories",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "arrow-epics-test",
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 750.5489606775325,
"y": 591.2142966047594,
"width": 0.4387418927216231,
"height": 60.43894121748178,
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:54:48 -06:00
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
"elementId": "proc-epics",
"focus": 0,
"gap": 1
},
"endBinding": {
"elementId": "proc-test-design",
"focus": 0,
"gap": 1
},
"points": [
[
0,
0
],
[
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
0.4387418927216231,
60.43894121748178
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:54:48 -06:00
]
],
"lastCommittedPoint": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 358,
"versionNonce": 1168009958,
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:54:48 -06:00
"index": "aj",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191427908,
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:54:48 -06:00
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow"
},
{
"id": "proc-test-design",
"type": "rectangle",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 671.2209977440557,
"y": 652.1048519834928,
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:54:48 -06:00
"width": 160,
"height": 80,
"angle": 0,
"strokeColor": "#e91e63",
"backgroundColor": "#f8bbd0",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"roundness": {
"type": 3,
"value": 8
},
"groupIds": [
"proc-test-design-group"
],
"boundElements": [
{
"type": "text",
"id": "proc-test-design-text"
},
{
"type": "arrow",
"id": "arrow-epics-test"
},
{
"type": "arrow",
"id": "arrow-test-validate"
}
],
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 124,
"versionNonce": 456543462,
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:54:48 -06:00
"index": "ak",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191425140,
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:54:48 -06:00
"link": null
},
{
"id": "proc-test-design-text",
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 709.1090363793096,
"y": 667.1048519834928,
"width": 84.22392272949219,
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:54:48 -06:00
"height": 50,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"proc-test-design-group"
],
"fontSize": 14,
"fontFamily": 1,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"text": "Test Design\n<<optional>>",
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:54:48 -06:00
"textAlign": "center",
"verticalAlign": "middle",
"containerId": "proc-test-design",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 133,
"versionNonce": 1038598182,
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:54:48 -06:00
"index": "al",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191425140,
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:54:48 -06:00
"link": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"originalText": "Test Design\n<<optional>>",
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:54:48 -06:00
"autoResize": true,
"lineHeight": 1.7857142857142858
},
{
"id": "arrow-test-validate",
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 742.3164554890545,
"y": 732.7428812826017,
"width": 0.2331013464803391,
"height": 41.16039866169126,
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:54:48 -06:00
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
"elementId": "proc-test-design",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"focus": 0.11090307971902064,
"gap": 1.407314849962063
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:54:48 -06:00
},
"endBinding": {
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"elementId": "proc-impl-ready",
"focus": -0.07891534010655449,
"gap": 6.845537084300759
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:54:48 -06:00
},
"points": [
[
0,
0
],
[
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
0.2331013464803391,
41.16039866169126
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:54:48 -06:00
]
],
"lastCommittedPoint": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 482,
"versionNonce": 362456762,
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:54:48 -06:00
"index": "am",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191475964,
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:54:48 -06:00
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow"
},
{
"id": "proc-validate-arch",
"type": "rectangle",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 688.0069292751327,
"y": 396.2354403009744,
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:54:48 -06:00
"width": 160,
"height": 80,
"angle": 0,
"strokeColor": "#f4511e",
"backgroundColor": "#ffccbc",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"roundness": {
"type": 3,
"value": 8
},
"groupIds": [
"proc-validate-arch-group"
],
"boundElements": [
{
"type": "text",
"id": "proc-validate-arch-text"
},
{
"type": "arrow",
"id": "arrow-test-validate"
},
{
"type": "arrow",
"id": "arrow-validate-ready"
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
},
{
"id": "arrow-arch-epics",
"type": "arrow"
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:54:48 -06:00
}
],
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 234,
"versionNonce": 940473658,
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:54:48 -06:00
"index": "an",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191449834,
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:54:48 -06:00
"link": null
},
{
"id": "proc-validate-arch-text",
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 698.0069292751327,
"y": 411.2354403009744,
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:54:48 -06:00
"width": 140,
"height": 50,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"proc-validate-arch-group"
],
"fontSize": 14,
"fontFamily": 1,
"text": "Validate Arch\n<<optional>>",
"textAlign": "center",
"verticalAlign": "middle",
"containerId": "proc-validate-arch",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 233,
"versionNonce": 41862650,
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:54:48 -06:00
"index": "ao",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191449834,
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:54:48 -06:00
"link": null,
"originalText": "Validate Arch\n<<optional>>",
"autoResize": true,
"lineHeight": 1.7857142857142858
},
{
"id": "arrow-validate-ready",
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 756.1926048905458,
"y": 477.82525825285865,
"width": 2.6030810941729214,
"height": 34.90186599521081,
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:54:48 -06:00
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
"elementId": "proc-validate-arch",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"focus": 0.10499022285337105,
"gap": 1.5898179518842426
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:54:48 -06:00
},
"endBinding": {
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"elementId": "proc-epics",
"focus": 0.007831693483179265,
"gap": 1.9644418045617158
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:54:48 -06:00
},
"points": [
[
0,
0
],
[
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
-2.6030810941729214,
34.90186599521081
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:54:48 -06:00
]
],
"lastCommittedPoint": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 527,
"versionNonce": 679932090,
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:54:48 -06:00
"index": "ap",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191469649,
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:54:48 -06:00
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow"
},
{
"id": "proc-impl-ready",
"type": "rectangle",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 669.3773407122919,
"y": 777.1531869468762,
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:54:48 -06:00
"width": 160,
"height": 80,
"angle": 0,
"strokeColor": "#f4511e",
"backgroundColor": "#ffccbc",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"roundness": {
"type": 3,
"value": 8
},
"groupIds": [
"proc-impl-ready-group"
],
"boundElements": [
{
"type": "text",
"id": "proc-impl-ready-text"
},
{
"type": "arrow",
"id": "arrow-validate-ready"
},
{
"type": "arrow",
"id": "arrow-phase3-to-phase4"
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
},
{
"id": "arrow-test-validate",
"type": "arrow"
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:54:48 -06:00
}
],
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 102,
"versionNonce": 1799933050,
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:54:48 -06:00
"index": "aq",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191475963,
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:54:48 -06:00
"link": null
},
{
"id": "proc-impl-ready-text",
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 679.3773407122919,
"y": 792.1531869468762,
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:54:48 -06:00
"width": 140,
"height": 50,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"proc-impl-ready-group"
],
"fontSize": 16,
"fontFamily": 1,
"text": "Implementation\nReadiness",
"textAlign": "center",
"verticalAlign": "middle",
"containerId": "proc-impl-ready",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 101,
"versionNonce": 1345137978,
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:54:48 -06:00
"index": "ar",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191475963,
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:54:48 -06:00
"link": null,
"originalText": "Implementation\nReadiness",
"autoResize": true,
"lineHeight": 1.5625
},
{
"id": "arrow-phase3-to-phase4",
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 832.3758366994932,
"y": 828.1314512149465,
"width": 332.79883769023445,
"height": 519.9927682908395,
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:54:48 -06:00
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
"elementId": "proc-impl-ready",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"focus": 0.8094917779899522,
"gap": 3.380037483859951
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:54:48 -06:00
},
"endBinding": {
"elementId": "proc-sprint-planning",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"focus": 0.538276991056649,
"gap": 1.1436349518342013
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:54:48 -06:00
},
"points": [
[
0,
0
],
[
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
80.82567439689569,
-94.83900216621896
],
[
159.28426317101867,
-458.225799867337
],
[
332.79883769023445,
-519.9927682908395
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:54:48 -06:00
]
],
"lastCommittedPoint": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 1116,
"versionNonce": 55014906,
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:54:48 -06:00
"index": "as",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"roundness": {
"type": 2
},
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:54:48 -06:00
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764191475964,
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:54:48 -06:00
"link": null,
"locked": false,
"startArrowhead": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"endArrowhead": "arrow",
"elbowed": false
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:54:48 -06:00
},
{
"id": "phase4-header",
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1175.3730315866237,
"y": 167.81322734599433,
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:54:48 -06:00
"width": 200,
"height": 30,
"angle": 0,
"strokeColor": "#2e7d32",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"fontSize": 24,
"fontFamily": 1,
"text": "PHASE 4",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 271,
"versionNonce": 866534438,
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:54:48 -06:00
"index": "at",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null,
"containerId": null,
"originalText": "PHASE 4",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "phase4-subtitle",
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1139.1188804963076,
"y": 204.18282943768378,
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:54:48 -06:00
"width": 260,
"height": 20,
"angle": 0,
"strokeColor": "#666666",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"fontSize": 16,
"fontFamily": 1,
"text": "Implementation (Required)",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 238,
"versionNonce": 198627174,
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:54:48 -06:00
"index": "au",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null,
"containerId": null,
"originalText": "Implementation (Required)",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "proc-sprint-planning",
"type": "rectangle",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1166.1946812371566,
"y": 276.1576920193427,
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:54:48 -06:00
"width": 160,
"height": 80,
"angle": 0,
"strokeColor": "#1e88e5",
"backgroundColor": "#bbdefb",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"roundness": {
"type": 3,
"value": 8
},
"groupIds": [
"proc-sprint-planning-group"
],
"boundElements": [
{
"type": "text",
"id": "proc-sprint-planning-text"
},
{
"type": "arrow",
"id": "arrow-phase3-to-phase4"
},
{
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"id": "arrow-validate-epic-story",
"type": "arrow"
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:54:48 -06:00
}
],
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 379,
"versionNonce": 2085876390,
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:54:48 -06:00
"index": "av",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null
},
{
"id": "proc-sprint-planning-text",
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1176.1946812371566,
"y": 304.1576920193427,
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:54:48 -06:00
"width": 140,
"height": 25,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"proc-sprint-planning-group"
],
"fontSize": 20,
"fontFamily": 1,
"text": "Sprint Plan",
"textAlign": "center",
"verticalAlign": "middle",
"containerId": "proc-sprint-planning",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 377,
"versionNonce": 2143989222,
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:54:48 -06:00
"index": "aw",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null,
"originalText": "Sprint Plan",
"autoResize": true,
"lineHeight": 1.25
},
{
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"id": "label-story-loop",
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:54:48 -06:00
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1176.2977877917795,
"y": 441.904906795244,
"width": 130.87991333007812,
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:54:48 -06:00
"height": 25,
"angle": 0,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"strokeColor": "#e65100",
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:54:48 -06:00
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"fontSize": 20,
"fontFamily": 1,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"text": "STORY LOOP",
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:54:48 -06:00
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 603,
"versionNonce": 40529830,
"index": "b04",
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:54:48 -06:00
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null,
"containerId": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"originalText": "STORY LOOP",
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:54:48 -06:00
"autoResize": true,
"lineHeight": 1.25
},
{
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"id": "arrow-validate-epic-story",
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:54:48 -06:00
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1249.6597155437828,
"y": 357.36880197268204,
"width": 2.9293448190794606,
"height": 208.61271744725804,
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:54:48 -06:00
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
"elementId": "proc-sprint-planning",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"focus": -0.050194107916528306,
"gap": 1.21110995333936
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:54:48 -06:00
},
"endBinding": {
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"elementId": "proc-create-story",
"focus": -0.004614835874420464,
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:54:48 -06:00
"gap": 1
},
"points": [
[
0,
0
],
[
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
-2.9293448190794606,
208.61271744725804
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:54:48 -06:00
]
],
"lastCommittedPoint": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 951,
"versionNonce": 1394233274,
"index": "b05",
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:54:48 -06:00
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763619,
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:54:48 -06:00
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow"
},
{
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"id": "proc-create-story",
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:54:48 -06:00
"type": "rectangle",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1166.5341271166512,
"y": 566.4331335811917,
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:54:48 -06:00
"width": 160,
"height": 80,
"angle": 0,
"strokeColor": "#1e88e5",
"backgroundColor": "#bbdefb",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"roundness": {
"type": 3,
"value": 8
},
"groupIds": [
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"proc-create-story-group"
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:54:48 -06:00
],
"boundElements": [
{
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"id": "proc-create-story-text"
},
{
"type": "arrow",
"id": "arrow-validate-epic-story"
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:54:48 -06:00
},
{
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"id": "arrow-create-validate-story"
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:54:48 -06:00
},
{
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"id": "arrow-more-stories-yes"
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:54:48 -06:00
}
],
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 282,
"versionNonce": 966999590,
"index": "b06",
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:54:48 -06:00
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null
},
{
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"id": "proc-create-story-text",
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:54:48 -06:00
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1176.5341271166512,
"y": 594.4331335811917,
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:54:48 -06:00
"width": 140,
"height": 25,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"proc-create-story-group"
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:54:48 -06:00
],
"fontSize": 20,
"fontFamily": 1,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"text": "Create Story",
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:54:48 -06:00
"textAlign": "center",
"verticalAlign": "middle",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"containerId": "proc-create-story",
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:54:48 -06:00
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 282,
"versionNonce": 2082769254,
"index": "b07",
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:54:48 -06:00
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"originalText": "Create Story",
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:54:48 -06:00
"autoResize": true,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"lineHeight": 1.25
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:54:48 -06:00
},
{
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"id": "arrow-create-validate-story",
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:54:48 -06:00
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1246.5341271166512,
"y": 646.4331335811917,
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:54:48 -06:00
"width": 0,
"height": 30,
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"elementId": "proc-create-story",
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:54:48 -06:00
"focus": 0,
"gap": 1
},
"endBinding": {
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"elementId": "proc-validate-story",
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:54:48 -06:00
"focus": 0,
"gap": 1
},
"points": [
[
0,
0
],
[
0,
30
]
],
"lastCommittedPoint": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 848,
"versionNonce": 1820404026,
"index": "b08",
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:54:48 -06:00
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763619,
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:54:48 -06:00
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow"
},
{
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"id": "proc-validate-story",
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:54:48 -06:00
"type": "rectangle",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1166.5341271166512,
"y": 676.4331335811917,
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:54:48 -06:00
"width": 160,
"height": 80,
"angle": 0,
"strokeColor": "#1e88e5",
"backgroundColor": "#bbdefb",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"roundness": {
"type": 3,
"value": 8
},
"groupIds": [
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"proc-validate-story-group"
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:54:48 -06:00
],
"boundElements": [
{
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"id": "proc-validate-story-text"
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:54:48 -06:00
},
{
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"id": "arrow-create-validate-story"
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:54:48 -06:00
},
{
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"id": "arrow-validate-story-decision"
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:54:48 -06:00
}
],
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 282,
"versionNonce": 282699366,
"index": "b09",
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:54:48 -06:00
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null
},
{
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"id": "proc-validate-story-text",
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:54:48 -06:00
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1176.5341271166512,
"y": 691.4331335811917,
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:54:48 -06:00
"width": 140,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"height": 50,
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:54:48 -06:00
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"proc-validate-story-group"
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:54:48 -06:00
],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"fontSize": 14,
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:54:48 -06:00
"fontFamily": 1,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"text": "Validate Story\n<<optional>>",
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:54:48 -06:00
"textAlign": "center",
"verticalAlign": "middle",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"containerId": "proc-validate-story",
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:54:48 -06:00
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 282,
"versionNonce": 686025126,
"index": "b0A",
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:54:48 -06:00
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"originalText": "Validate Story\n<<optional>>",
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:54:48 -06:00
"autoResize": true,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"lineHeight": 1.7857142857142858
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:54:48 -06:00
},
{
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"id": "arrow-validate-story-decision",
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:54:48 -06:00
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1246.5341271166512,
"y": 756.4331335811917,
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:54:48 -06:00
"width": 0,
"height": 30,
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"elementId": "proc-validate-story",
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:54:48 -06:00
"focus": 0,
"gap": 1
},
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"endBinding": null,
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:54:48 -06:00
"points": [
[
0,
0
],
[
0,
30
]
],
"lastCommittedPoint": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 566,
"versionNonce": 1807479290,
"index": "b0B",
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:54:48 -06:00
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763619,
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:54:48 -06:00
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow"
},
{
"id": "proc-dev-story",
"type": "rectangle",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1164.0395418694,
"y": 788.7867016847945,
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:54:48 -06:00
"width": 160,
"height": 80,
"angle": 0,
"strokeColor": "#3f51b5",
"backgroundColor": "#c5cae9",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"roundness": {
"type": 3,
"value": 8
},
"groupIds": [
"proc-dev-story-group"
],
"boundElements": [
{
"type": "text",
"id": "proc-dev-story-text"
},
{
"type": "arrow",
"id": "arrow-dev-review"
}
],
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 367,
"versionNonce": 935782054,
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:54:48 -06:00
"index": "b0R",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null
},
{
"id": "proc-dev-story-text",
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1174.0395418694,
"y": 816.7867016847945,
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:54:48 -06:00
"width": 140,
"height": 25,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"proc-dev-story-group"
],
"fontSize": 20,
"fontFamily": 1,
"text": "Develop Story",
"textAlign": "center",
"verticalAlign": "middle",
"containerId": "proc-dev-story",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 364,
"versionNonce": 952050150,
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:54:48 -06:00
"index": "b0S",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null,
"originalText": "Develop Story",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "arrow-dev-review",
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1244.2149450712877,
"y": 869.2383158460461,
"width": 5.032331195699953,
"height": 76.6679634046609,
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:54:48 -06:00
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
"elementId": "proc-dev-story",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"focus": 0.030012029555609845,
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:54:48 -06:00
"gap": 1
},
"endBinding": {
docs: remove stale references to deleted Phase 4 workflows Removes references to epic-tech-context, story-context, story-done, and story-ready workflows that were deleted in the Phase 4 transformation. Also renames mislabeled excalidraw element IDs from proc-story-done to proc-code-review to match the actual displayed text. Fixes #1088
2025-12-09 19:29:33 -07:00
"elementId": "proc-code-review",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"focus": 0.04241833499478815,
"gap": 1.3466869862454587
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:54:48 -06:00
},
"points": [
[
0,
0
],
[
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
5.032331195699953,
76.6679634046609
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:54:48 -06:00
]
],
"lastCommittedPoint": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 1191,
"versionNonce": 2052012922,
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:54:48 -06:00
"index": "b0T",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763619,
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:54:48 -06:00
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow"
},
{
"id": "decision-code-review",
"type": "diamond",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1156.5341271166512,
"y": 1156.4331335811917,
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:54:48 -06:00
"width": 180,
"height": 120,
"angle": 0,
"strokeColor": "#f57c00",
"backgroundColor": "#fff3e0",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"decision-code-review-group"
],
"boundElements": [
{
"type": "text",
"id": "decision-code-review-text"
},
{
"type": "arrow",
"id": "arrow-dev-review"
},
{
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"id": "arrow-review-fail"
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:54:48 -06:00
},
{
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"id": "arrow-done-more-stories",
"type": "arrow"
},
{
"id": "4chQ7PksRKpPe5YX-TfFJ",
"type": "arrow"
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:54:48 -06:00
}
],
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 285,
"versionNonce": 46359462,
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:54:48 -06:00
"index": "b0U",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null
},
{
"id": "decision-code-review-text",
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1171.5341271166512,
"y": 1191.4331335811917,
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:54:48 -06:00
"width": 150,
"height": 50,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"decision-code-review-group"
],
"fontSize": 16,
"fontFamily": 1,
"text": "Code Review\nPass?",
"textAlign": "center",
"verticalAlign": "middle",
"containerId": "decision-code-review",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 282,
"versionNonce": 1227095782,
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:54:48 -06:00
"index": "b0V",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null,
"originalText": "Code Review\nPass?",
"autoResize": true,
"lineHeight": 1.5625
},
{
"id": "arrow-review-fail",
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1151.5341271166512,
"y": 1216.3331335811918,
"width": 42.50541475274872,
"height": 387.6464318963972,
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:54:48 -06:00
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": null,
"endBinding": null,
"points": [
[
0,
0
],
[
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
-35,
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:54:48 -06:00
0
],
[
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
-35,
-387.6464318963972
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:54:48 -06:00
],
[
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
7.50541475274872,
-387.6464318963972
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:54:48 -06:00
]
],
"lastCommittedPoint": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"elbowed": true,
"version": 319,
"versionNonce": 405929318,
"index": "b0W",
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:54:48 -06:00
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null,
"locked": false,
"startArrowhead": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"endArrowhead": "arrow",
"fixedSegments": null,
"startIsSpecial": null,
"endIsSpecial": null
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:54:48 -06:00
},
{
"id": "label-fail",
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1065.6231186673836,
"y": 1185.462969542075,
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:54:48 -06:00
"width": 35,
"height": 20,
"angle": 0,
"strokeColor": "#d32f2f",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"fontSize": 16,
"fontFamily": 1,
"text": "Fail",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 316,
"versionNonce": 1897488550,
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:54:48 -06:00
"index": "b0Y",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null,
"containerId": null,
"originalText": "Fail",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"autoResize": true,
"lineHeight": 1.25
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:54:48 -06:00
},
{
"id": "label-pass",
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1229.6819134569105,
"y": 1281.2421635916448,
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:54:48 -06:00
"width": 40,
"height": 20,
"angle": 0,
"strokeColor": "#2e7d32",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"fontSize": 16,
"fontFamily": 1,
"text": "Pass",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 408,
"versionNonce": 1437752294,
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:54:48 -06:00
"index": "b0a",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"boundElements": [
{
"id": "4chQ7PksRKpPe5YX-TfFJ",
"type": "arrow"
}
],
"updated": 1764190763204,
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:54:48 -06:00
"link": null,
"containerId": null,
"originalText": "Pass",
"autoResize": true,
"lineHeight": 1.25
},
{
docs: remove stale references to deleted Phase 4 workflows Removes references to epic-tech-context, story-context, story-done, and story-ready workflows that were deleted in the Phase 4 transformation. Also renames mislabeled excalidraw element IDs from proc-story-done to proc-code-review to match the actual displayed text. Fixes #1088
2025-12-09 19:29:33 -07:00
"id": "proc-code-review",
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:54:48 -06:00
"type": "rectangle",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1169.3991588878014,
"y": 947.2529662369525,
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:54:48 -06:00
"width": 160,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"height": 110,
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:54:48 -06:00
"angle": 0,
"strokeColor": "#3f51b5",
"backgroundColor": "#c5cae9",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"roundness": {
"type": 3,
"value": 8
},
"groupIds": [
docs: remove stale references to deleted Phase 4 workflows Removes references to epic-tech-context, story-context, story-done, and story-ready workflows that were deleted in the Phase 4 transformation. Also renames mislabeled excalidraw element IDs from proc-story-done to proc-code-review to match the actual displayed text. Fixes #1088
2025-12-09 19:29:33 -07:00
"proc-code-review-group"
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:54:48 -06:00
],
"boundElements": [
{
"type": "text",
docs: remove stale references to deleted Phase 4 workflows Removes references to epic-tech-context, story-context, story-done, and story-ready workflows that were deleted in the Phase 4 transformation. Also renames mislabeled excalidraw element IDs from proc-story-done to proc-code-review to match the actual displayed text. Fixes #1088
2025-12-09 19:29:33 -07:00
"id": "proc-code-review-text"
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:54:48 -06:00
},
{
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"id": "arrow-done-more-stories"
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:54:48 -06:00
},
{
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"id": "arrow-dev-review",
"type": "arrow"
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:54:48 -06:00
}
],
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 453,
"versionNonce": 277682790,
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:54:48 -06:00
"index": "b0b",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null
},
{
docs: remove stale references to deleted Phase 4 workflows Removes references to epic-tech-context, story-context, story-done, and story-ready workflows that were deleted in the Phase 4 transformation. Also renames mislabeled excalidraw element IDs from proc-story-done to proc-code-review to match the actual displayed text. Fixes #1088
2025-12-09 19:29:33 -07:00
"id": "proc-code-review-text",
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:54:48 -06:00
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1187.9272045420983,
"y": 972.2529662369525,
"width": 122.94390869140625,
"height": 60,
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:54:48 -06:00
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
docs: remove stale references to deleted Phase 4 workflows Removes references to epic-tech-context, story-context, story-done, and story-ready workflows that were deleted in the Phase 4 transformation. Also renames mislabeled excalidraw element IDs from proc-story-done to proc-code-review to match the actual displayed text. Fixes #1088
2025-12-09 19:29:33 -07:00
"proc-code-review-group"
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:54:48 -06:00
],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"fontSize": 16,
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:54:48 -06:00
"fontFamily": 1,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"text": "Code Review\n<<use different\nLLM>>",
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:54:48 -06:00
"textAlign": "center",
"verticalAlign": "middle",
docs: remove stale references to deleted Phase 4 workflows Removes references to epic-tech-context, story-context, story-done, and story-ready workflows that were deleted in the Phase 4 transformation. Also renames mislabeled excalidraw element IDs from proc-story-done to proc-code-review to match the actual displayed text. Fixes #1088
2025-12-09 19:29:33 -07:00
"containerId": "proc-code-review",
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:54:48 -06:00
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 502,
"versionNonce": 1242095014,
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:54:48 -06:00
"index": "b0c",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"originalText": "Code Review\n<<use different LLM>>",
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:54:48 -06:00
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "arrow-done-more-stories",
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1249.4681490735618,
"y": 1065.5372616587838,
"width": 1.7879398006109568,
"height": 90.97426236326123,
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:54:48 -06:00
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
docs: remove stale references to deleted Phase 4 workflows Removes references to epic-tech-context, story-context, story-done, and story-ready workflows that were deleted in the Phase 4 transformation. Also renames mislabeled excalidraw element IDs from proc-story-done to proc-code-review to match the actual displayed text. Fixes #1088
2025-12-09 19:29:33 -07:00
"elementId": "proc-code-review",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"focus": 0.014488632877232727,
"gap": 8.284295421831303
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:54:48 -06:00
},
"endBinding": {
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"elementId": "decision-code-review",
"focus": 0.09832693417954867,
"gap": 2.039543956918169
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:54:48 -06:00
},
"points": [
[
0,
0
],
[
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
1.7879398006109568,
90.97426236326123
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:54:48 -06:00
]
],
"lastCommittedPoint": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 1093,
"versionNonce": 146679034,
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:54:48 -06:00
"index": "b0d",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763619,
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:54:48 -06:00
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow"
},
{
"id": "decision-more-stories",
"type": "diamond",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1163.8719002449689,
"y": 1363.600308336051,
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:54:48 -06:00
"width": 180,
"height": 120,
"angle": 0,
"strokeColor": "#f57c00",
"backgroundColor": "#fff3e0",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"decision-more-stories-group"
],
"boundElements": [
{
"type": "text",
"id": "decision-more-stories-text"
},
{
"type": "arrow",
"id": "arrow-done-more-stories"
},
{
"type": "arrow",
"id": "arrow-more-stories-yes"
},
{
"type": "arrow",
"id": "arrow-more-stories-no"
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
},
{
"id": "4chQ7PksRKpPe5YX-TfFJ",
"type": "arrow"
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:54:48 -06:00
}
],
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 441,
"versionNonce": 886168230,
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:54:48 -06:00
"index": "b0e",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null
},
{
"id": "decision-more-stories-text",
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1178.8719002449689,
"y": 1398.600308336051,
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:54:48 -06:00
"width": 150,
"height": 50,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"decision-more-stories-group"
],
"fontSize": 16,
"fontFamily": 1,
"text": "More Stories\nin Epic?",
"textAlign": "center",
"verticalAlign": "middle",
"containerId": "decision-more-stories",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 440,
"versionNonce": 1078695398,
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:54:48 -06:00
"index": "b0f",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null,
"originalText": "More Stories\nin Epic?",
"autoResize": true,
"lineHeight": 1.5625
},
{
"id": "arrow-more-stories-yes",
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1158.8719002449689,
"y": 1423.5003083360511,
"width": 141.95595587699154,
"height": 827.0007685048595,
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:54:48 -06:00
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"startBinding": {
"elementId": "decision-more-stories",
"fixedPoint": [
-0.027777777777777776,
0.4991666666666674
],
"focus": 0,
"gap": 0
},
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:54:48 -06:00
"endBinding": null,
"points": [
[
0,
0
],
[
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
-140.44216650530916,
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:54:48 -06:00
0
],
[
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
-140.44216650530916,
-827.0007685048595
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:54:48 -06:00
],
[
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
1.5137893716823783,
-827.0007685048595
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:54:48 -06:00
]
],
"lastCommittedPoint": null,
"elbowed": true,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 954,
"versionNonce": 2094428902,
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:54:48 -06:00
"index": "b0g",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow",
"fixedSegments": [
{
"index": 2,
"start": [
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
-140.44216650530916,
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:54:48 -06:00
0
],
"end": [
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
-140.44216650530916,
-827.0007685048595
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:54:48 -06:00
]
}
],
"startIsSpecial": false,
"endIsSpecial": false
},
{
"id": "label-more-stories-yes",
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1024.8322929694286,
"y": 1455.9672274720815,
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:54:48 -06:00
"width": 30,
"height": 20,
"angle": 0,
"strokeColor": "#2e7d32",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"fontSize": 16,
"fontFamily": 1,
"text": "Yes",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 320,
"versionNonce": 76752422,
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:54:48 -06:00
"index": "b0h",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null,
"containerId": null,
"originalText": "Yes",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "arrow-more-stories-no",
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1254.2299747445697,
"y": 1484.1816612705734,
"width": 0.09067340460524065,
"height": 69.22388536244944,
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:54:48 -06:00
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
"elementId": "decision-more-stories",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"focus": -0.004645359638607261,
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:54:48 -06:00
"gap": 1
},
"endBinding": {
"elementId": "proc-retrospective",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"focus": -0.000007722345339971072,
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:54:48 -06:00
"gap": 1
},
"points": [
[
0,
0
],
[
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
0.09067340460524065,
69.22388536244944
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:54:48 -06:00
]
],
"lastCommittedPoint": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 1115,
"versionNonce": 1285598842,
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:54:48 -06:00
"index": "b0i",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763619,
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:54:48 -06:00
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow"
},
{
"id": "label-more-stories-no",
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1273.6656161640394,
"y": 1506.317970130127,
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:54:48 -06:00
"width": 25,
"height": 20,
"angle": 0,
"strokeColor": "#d32f2f",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"fontSize": 16,
"fontFamily": 1,
"text": "No",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 327,
"versionNonce": 1022383270,
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:54:48 -06:00
"index": "b0j",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null,
"containerId": null,
"originalText": "No",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "proc-retrospective",
"type": "rectangle",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1174.3742521794413,
"y": 1553.8571607942745,
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:54:48 -06:00
"width": 160,
"height": 80,
"angle": 0,
"strokeColor": "#1e88e5",
"backgroundColor": "#bbdefb",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"roundness": {
"type": 3,
"value": 8
},
"groupIds": [
"proc-retrospective-group"
],
"boundElements": [
{
"type": "text",
"id": "proc-retrospective-text"
},
{
"type": "arrow",
"id": "arrow-more-stories-no"
},
{
"type": "arrow",
"id": "arrow-retro-more-epics"
}
],
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 391,
"versionNonce": 1921699814,
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:54:48 -06:00
"index": "b0k",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null
},
{
"id": "proc-retrospective-text",
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1184.3742521794413,
"y": 1581.8571607942745,
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:54:48 -06:00
"width": 140,
"height": 25,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"proc-retrospective-group"
],
"fontSize": 20,
"fontFamily": 1,
"text": "Retrospective",
"textAlign": "center",
"verticalAlign": "middle",
"containerId": "proc-retrospective",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 391,
"versionNonce": 1572070182,
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:54:48 -06:00
"index": "b0l",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null,
"originalText": "Retrospective",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "arrow-retro-more-epics",
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1252.261821627823,
"y": 1634.3087749555261,
"width": 2.2496323163620673,
"height": 42.83146813764597,
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:54:48 -06:00
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
"elementId": "proc-retrospective",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"focus": -0.00014865809573961995,
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:54:48 -06:00
"gap": 1
},
"endBinding": {
"elementId": "decision-more-epics",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"focus": 0.006063807827498143,
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:54:48 -06:00
"gap": 1
},
"points": [
[
0,
0
],
[
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
-2.2496323163620673,
42.83146813764597
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:54:48 -06:00
]
],
"lastCommittedPoint": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 957,
"versionNonce": 1972295674,
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:54:48 -06:00
"index": "b0m",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763619,
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:54:48 -06:00
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow"
},
{
"id": "decision-more-epics",
"type": "diamond",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1156.5341271166512,
"y": 1676.4331335811917,
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:54:48 -06:00
"width": 180,
"height": 120,
"angle": 0,
"strokeColor": "#f57c00",
"backgroundColor": "#fff3e0",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"decision-more-epics-group"
],
"boundElements": [
{
"type": "text",
"id": "decision-more-epics-text"
},
{
"type": "arrow",
"id": "arrow-retro-more-epics"
},
{
"type": "arrow",
"id": "arrow-more-epics-yes"
},
{
"type": "arrow",
"id": "arrow-more-epics-no"
}
],
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 282,
"versionNonce": 101589030,
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:54:48 -06:00
"index": "b0n",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null
},
{
"id": "decision-more-epics-text",
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1171.5341271166512,
"y": 1711.4331335811917,
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:54:48 -06:00
"width": 150,
"height": 50,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"decision-more-epics-group"
],
"fontSize": 16,
"fontFamily": 1,
"text": "More Epics?",
"textAlign": "center",
"verticalAlign": "middle",
"containerId": "decision-more-epics",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 282,
"versionNonce": 2095262566,
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:54:48 -06:00
"index": "b0o",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null,
"originalText": "More Epics?",
"autoResize": true,
"lineHeight": 3.125
},
{
"id": "arrow-more-epics-yes",
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1151.5341271166512,
"y": 1736.3331335811918,
"width": 194.92191691435096,
"height": 1138.0678409916745,
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:54:48 -06:00
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
"elementId": "decision-more-epics",
"fixedPoint": [
-0.027777777777777776,
0.4991666666666674
],
"focus": 0,
"gap": 0
},
"endBinding": null,
"points": [
[
0,
0
],
[
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
-184.89984110690511,
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:54:48 -06:00
0
],
[
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
-184.89984110690511,
-1138.0678409916745
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:54:48 -06:00
],
[
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
10.022075807445844,
-1138.0678409916745
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:54:48 -06:00
]
],
"lastCommittedPoint": null,
"elbowed": true,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 1805,
"versionNonce": 1424088358,
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:54:48 -06:00
"index": "b0p",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow",
"fixedSegments": [
{
"index": 2,
"start": [
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
-184.89984110690511,
0
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:54:48 -06:00
],
"end": [
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
-184.89984110690511,
-1138.0678409916745
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:54:48 -06:00
]
}
],
"startIsSpecial": false,
"endIsSpecial": false
},
{
"id": "label-more-epics-yes",
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1016.7607529532588,
"y": 1704.1213622982812,
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:54:48 -06:00
"width": 30,
"height": 20,
"angle": 0,
"strokeColor": "#2e7d32",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"fontSize": 16,
"fontFamily": 1,
"text": "Yes",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 395,
"versionNonce": 339167334,
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:54:48 -06:00
"index": "b0q",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null,
"containerId": null,
"originalText": "Yes",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "arrow-more-epics-no",
"type": "arrow",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1246.5341271166512,
"y": 1796.4331335811921,
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:54:48 -06:00
"width": 0,
"height": 50,
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"elementId": "label-more-epics-no",
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:54:48 -06:00
"focus": 0,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"gap": 14.142135623730951
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:54:48 -06:00
},
"endBinding": {
"elementId": "end-ellipse",
"focus": 0,
"gap": 1
},
"points": [
[
0,
0
],
[
0,
50
]
],
"lastCommittedPoint": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 848,
"versionNonce": 757113210,
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:54:48 -06:00
"index": "b0r",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763620,
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:54:48 -06:00
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow"
},
{
"id": "label-more-epics-no",
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1256.5341271166512,
"y": 1806.4331335811921,
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:54:48 -06:00
"width": 25,
"height": 20,
"angle": 0,
"strokeColor": "#d32f2f",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"fontSize": 16,
"fontFamily": 1,
"text": "No",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 283,
"versionNonce": 1126229734,
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:54:48 -06:00
"index": "b0s",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"boundElements": [
{
"id": "arrow-more-epics-no",
"type": "arrow"
}
],
"updated": 1764190763204,
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:54:48 -06:00
"link": null,
"containerId": null,
"originalText": "No",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "end-ellipse",
"type": "ellipse",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1186.5341271166512,
"y": 1846.4331335811921,
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:54:48 -06:00
"width": 120,
"height": 60,
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "#e3f2fd",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"end-group"
],
"boundElements": [
{
"type": "text",
"id": "end-text"
},
{
"type": "arrow",
"id": "arrow-more-epics-no"
}
],
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 282,
"versionNonce": 370468198,
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:54:48 -06:00
"index": "b0t",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null
},
{
"id": "end-text",
"type": "text",
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"x": 1223.5341271166512,
"y": 1864.4331335811921,
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:54:48 -06:00
"width": 46,
"height": 25,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"end-group"
],
"fontSize": 20,
"fontFamily": 1,
"text": "End",
"textAlign": "center",
"verticalAlign": "middle",
"containerId": "end-ellipse",
"locked": false,
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"version": 282,
"versionNonce": 39798950,
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:54:48 -06:00
"index": "b0u",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
"updated": 1764190763204,
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:54:48 -06:00
"link": null,
"originalText": "End",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "legend-box",
"type": "rectangle",
"x": -383.37044904818777,
"y": 130.62309916565027,
"width": 280,
"height": 240,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "#ffffff",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"FOWhENd6l0IWkDrktqohE"
],
"roundness": {
"type": 3,
"value": 8
},
"locked": false,
"version": 240,
"versionNonce": 899126491,
"index": "b0v",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"boundElements": [],
"updated": 1763522286451,
"link": null
},
{
"id": "legend-title",
"type": "text",
"x": -303.37044904818777,
"y": 140.62309916565027,
"width": 120,
"height": 25,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"FOWhENd6l0IWkDrktqohE"
],
"fontSize": 20,
"fontFamily": 1,
"text": "Agent Legend",
"textAlign": "center",
"verticalAlign": "top",
"locked": false,
"version": 187,
"versionNonce": 354828667,
"index": "b0w",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522286451,
"link": null,
"containerId": null,
"originalText": "Agent Legend",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "legend-analyst",
"type": "rectangle",
"x": -373.37044904818777,
"y": 180.62309916565027,
"width": 20,
"height": 20,
"angle": 0,
"strokeColor": "#00acc1",
"backgroundColor": "#b2ebf2",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"FOWhENd6l0IWkDrktqohE"
],
"locked": false,
"version": 187,
"versionNonce": 863394331,
"index": "b0x",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522286451,
"link": null
},
{
"id": "legend-analyst-text",
"type": "text",
"x": -343.37044904818777,
"y": 182.62309916565027,
"width": 70,
"height": 20,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"FOWhENd6l0IWkDrktqohE"
],
"fontSize": 16,
"fontFamily": 1,
"text": "Analyst",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
"version": 187,
"versionNonce": 226123451,
"index": "b0y",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522286451,
"link": null,
"containerId": null,
"originalText": "Analyst",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "legend-pm",
"type": "rectangle",
"x": -373.37044904818777,
"y": 210.62309916565027,
"width": 20,
"height": 20,
"angle": 0,
"strokeColor": "#43a047",
"backgroundColor": "#c8e6c9",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"FOWhENd6l0IWkDrktqohE"
],
"locked": false,
"version": 187,
"versionNonce": 1574227803,
"index": "b0z",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522286451,
"link": null
},
{
"id": "legend-pm-text",
"type": "text",
"x": -343.37044904818777,
"y": 212.62309916565027,
"width": 30,
"height": 20,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"FOWhENd6l0IWkDrktqohE"
],
"fontSize": 16,
"fontFamily": 1,
"text": "PM",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
"version": 187,
"versionNonce": 1725443067,
"index": "b10",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522286451,
"link": null,
"containerId": null,
"originalText": "PM",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "legend-ux",
"type": "rectangle",
"x": -373.37044904818777,
"y": 240.62309916565027,
"width": 20,
"height": 20,
"angle": 0,
"strokeColor": "#8e24aa",
"backgroundColor": "#e1bee7",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"FOWhENd6l0IWkDrktqohE"
],
"locked": false,
"version": 187,
"versionNonce": 2089219227,
"index": "b11",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522286451,
"link": null
},
{
"id": "legend-ux-text",
"type": "text",
"x": -343.37044904818777,
"y": 242.62309916565027,
"width": 110,
"height": 20,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"FOWhENd6l0IWkDrktqohE"
],
"fontSize": 16,
"fontFamily": 1,
"text": "UX Designer",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
"version": 187,
"versionNonce": 1318299963,
"index": "b12",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522286451,
"link": null,
"containerId": null,
"originalText": "UX Designer",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "legend-architect",
"type": "rectangle",
"x": -373.37044904818777,
"y": 270.6230991656503,
"width": 20,
"height": 20,
"angle": 0,
"strokeColor": "#f4511e",
"backgroundColor": "#ffccbc",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"FOWhENd6l0IWkDrktqohE"
],
"locked": false,
"version": 187,
"versionNonce": 1918945755,
"index": "b13",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522286451,
"link": null
},
{
"id": "legend-architect-text",
"type": "text",
"x": -343.37044904818777,
"y": 272.6230991656503,
"width": 80,
"height": 20,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"FOWhENd6l0IWkDrktqohE"
],
"fontSize": 16,
"fontFamily": 1,
"text": "Architect",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
"version": 187,
"versionNonce": 755029627,
"index": "b14",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522286451,
"link": null,
"containerId": null,
"originalText": "Architect",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "legend-tea",
"type": "rectangle",
"x": -373.37044904818777,
"y": 300.6230991656503,
"width": 20,
"height": 20,
"angle": 0,
"strokeColor": "#e91e63",
"backgroundColor": "#f8bbd0",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"FOWhENd6l0IWkDrktqohE"
],
"locked": false,
"version": 187,
"versionNonce": 2100711195,
"index": "b15",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522286451,
"link": null
},
{
"id": "legend-tea-text",
"type": "text",
"x": -343.37044904818777,
"y": 302.6230991656503,
"width": 40,
"height": 20,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"FOWhENd6l0IWkDrktqohE"
],
"fontSize": 16,
"fontFamily": 1,
"text": "TEA",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
"version": 187,
"versionNonce": 1702081467,
"index": "b16",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522286451,
"link": null,
"containerId": null,
"originalText": "TEA",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "legend-sm",
"type": "rectangle",
"x": -373.37044904818777,
"y": 330.6230991656503,
"width": 20,
"height": 20,
"angle": 0,
"strokeColor": "#1e88e5",
"backgroundColor": "#bbdefb",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"FOWhENd6l0IWkDrktqohE"
],
"locked": false,
"version": 187,
"versionNonce": 1977320539,
"index": "b17",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522286451,
"link": null
},
{
"id": "legend-sm-text",
"type": "text",
"x": -343.37044904818777,
"y": 332.6230991656503,
"width": 30,
"height": 20,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"FOWhENd6l0IWkDrktqohE"
],
"fontSize": 16,
"fontFamily": 1,
"text": "SM",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
"version": 187,
"versionNonce": 373309691,
"index": "b18",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522286451,
"link": null,
"containerId": null,
"originalText": "SM",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "legend-dev",
"type": "rectangle",
"x": -223.37044904818777,
"y": 180.62309916565027,
"width": 20,
"height": 20,
"angle": 0,
"strokeColor": "#3f51b5",
"backgroundColor": "#c5cae9",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"FOWhENd6l0IWkDrktqohE"
],
"locked": false,
"version": 187,
"versionNonce": 270821787,
"index": "b19",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522286451,
"link": null
},
{
"id": "legend-dev-text",
"type": "text",
"x": -193.37044904818777,
"y": 182.62309916565027,
"width": 40,
"height": 20,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"FOWhENd6l0IWkDrktqohE"
],
"fontSize": 16,
"fontFamily": 1,
"text": "DEV",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
"version": 187,
"versionNonce": 1488617019,
"index": "b1A",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522286451,
"link": null,
"containerId": null,
"originalText": "DEV",
"autoResize": true,
"lineHeight": 1.25
},
{
"id": "legend-decision",
"type": "diamond",
"x": -223.37044904818777,
"y": 210.62309916565027,
"width": 30,
"height": 30,
"angle": 0,
"strokeColor": "#f57c00",
"backgroundColor": "#fff3e0",
"fillStyle": "solid",
"strokeWidth": 1,
"roughness": 0,
"opacity": 100,
"groupIds": [
"FOWhENd6l0IWkDrktqohE"
],
"locked": false,
"version": 187,
"versionNonce": 451215067,
"index": "b1B",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522286451,
"link": null
},
{
"id": "legend-decision-text",
"type": "text",
"x": -183.37044904818777,
"y": 217.62309916565027,
"width": 70,
"height": 20,
"angle": 0,
"strokeColor": "#1e1e1e",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [
"FOWhENd6l0IWkDrktqohE"
],
"fontSize": 16,
"fontFamily": 1,
"text": "Decision",
"textAlign": "left",
"verticalAlign": "top",
"locked": false,
"version": 187,
"versionNonce": 20343675,
"index": "b1C",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1763522286451,
"link": null,
"containerId": null,
"originalText": "Decision",
"autoResize": true,
"lineHeight": 1.25
standard greenfield workflow updated diagrams
2025-11-26 15:14:16 -06:00
},
{
"id": "4chQ7PksRKpPe5YX-TfFJ",
"type": "arrow",
"x": 1250.9718703296421,
"y": 1311.0799578560604,
"width": 3.1071377799139555,
"height": 47.57227388165256,
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
"elementId": "label-pass",
"focus": 0.0002774287102738527,
"gap": 9.837794264415606
},
"endBinding": {
"elementId": "decision-more-stories",
"focus": 0.07415216095379644,
"gap": 5.01120144889627
},
"points": [
[
0,
0
],
[
3.1071377799139555,
47.57227388165256
]
],
"lastCommittedPoint": null,
"version": 1485,
"versionNonce": 384699130,
"index": "b1D",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1128360742,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1764190763620,
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow"
},
{
"id": "jv0rnlK2D9JKIGTO7pUtT",
"type": "arrow",
"x": 199.95091169427553,
"y": 434.3642722686245,
"width": 152.18808817436843,
"height": 126.81486476828513,
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
"elementId": "proc-brainstorm",
"focus": 0.3249856938901564,
"gap": 1
},
"endBinding": {
"elementId": "proc-prd",
"focus": 0.40022808683972894,
"gap": 7.158084853619243
},
"points": [
[
0,
0
],
[
69.77818267983719,
0.8988822936652241
],
[
84.43045426782976,
-84.30283196996788
],
[
152.18808817436843,
-125.91598247461991
]
],
"lastCommittedPoint": null,
"version": 2008,
"versionNonce": 1304633062,
"index": "b1F",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 753809018,
"frameId": null,
"roundness": {
"type": 2
},
"boundElements": [],
"updated": 1764191372763,
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow",
"elbowed": false
},
{
"id": "RF10FfKbmG72P77I2IoP4",
"type": "arrow",
"x": 200.50999902520755,
"y": 524.3440535408814,
"width": 155.72897460360434,
"height": 217.43940257292877,
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
"elementId": "proc-research",
"focus": 0.2547348377789515,
"gap": 1
},
"endBinding": {
"elementId": "proc-prd",
"focus": 0.3948133447078272,
"gap": 3.0581110934513163
},
"points": [
[
0,
0
],
[
71.74164413965786,
-18.904836665604307
],
[
83.93792495248488,
-172.66332121061578
],
[
155.72897460360434,
-217.43940257292877
]
],
"lastCommittedPoint": null,
"version": 2022,
"versionNonce": 1289623162,
"index": "b1G",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 389493926,
"frameId": null,
"roundness": {
"type": 2
},
"boundElements": [],
"updated": 1764191336778,
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow",
"elbowed": false
},
{
"id": "FDR4ZvEvNmPvkP3HfQMY4",
"type": "arrow",
"x": 523.1179307657023,
"y": 528.6598293249855,
"width": 156.49193140361945,
"height": 211.37494429949584,
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": null,
"endBinding": null,
"points": [
[
0,
0
],
[
67.6421465593952,
-30.201232355758236
],
[
96.50992722652438,
-178.58566948715793
],
[
156.49193140361945,
-211.37494429949584
]
],
"lastCommittedPoint": null,
"version": 672,
"versionNonce": 1827754470,
"index": "b1I",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 310318758,
"frameId": null,
"roundness": {
"type": 2
},
"boundElements": [],
"updated": 1764191558236,
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow",
"elbowed": false
fix(bmm): remove stale validate-prd references (fixes #1030) (#1038) - Remove validate-prd workflow references from all workflow path YAML files - Update Excalidraw diagram: remove Validate PRD box and zombie JSON elements - Re-export SVG at 1x scale - Standardize implementation-readiness descriptions across all docs - Add validation script (validate-svg-changes.sh) and README for SVG export process - Correct Excalidraw timestamps 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Brian <bmadcode@gmail.com>
2025-12-05 19:35:46 -08:00
},
{
"id": "arrow-prd-hasui",
"type": "arrow",
"x": 440,
"y": 330,
"width": 0,
"height": 140,
"angle": 0,
"strokeColor": "#1976d2",
"backgroundColor": "transparent",
"fillStyle": "solid",
"strokeWidth": 2,
"roughness": 0,
"opacity": 100,
"groupIds": [],
"startBinding": {
"elementId": "proc-prd",
"focus": 0,
"gap": 1
},
"endBinding": {
"elementId": "decision-has-ui",
"focus": 0,
"gap": 1
},
"points": [
[
0,
0
],
[
0,
140
]
],
"lastCommittedPoint": null,
"version": 1,
"versionNonce": 1,
"index": "b1J",
"isDeleted": false,
"strokeStyle": "solid",
"seed": 1,
"frameId": null,
"roundness": null,
"boundElements": [],
"updated": 1764952855000,
"link": null,
"locked": false,
"startArrowhead": null,
"endArrowhead": "arrow"
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:54:48 -06:00
}
],
"appState": {
"gridSize": 20,
"gridStep": 5,
"gridModeEnabled": false,
"viewBackgroundColor": "#ffffff"
},
"files": {}
}
Reference in New Issue Copy Permalink