BMAD-METHOD/docs/v6-open-items.md

# v6 Pending Items

Before calling this beta

- finalize web bundler
- some subagents working again
- knowledge base for bmad

## Needed Beta → v0 release

Aside from stability and bug fixes found during the alpha period - the main focus will be on the following:

- knowledge base for BMM
- Module repository and submission process defined
- MCP Injections based on installation selection
- sub agent for open-code and claude code optimization
- TDD Workflow Integration
readme updates and open items published 2025-09-29 10:13:22 -05:00			`# v6 Pending Items`

update open items list 2025-10-27 18:27:10 -05:00			`Before calling this beta`

fix: Add missing adv-elicit-methods.csv to workflow bundles - Add adv-elicit-methods.csv dependency to all workflows using adv-elicit.xml - architecture workflow - prd workflow - tech-spec workflow - Include BMM web bundles (8 agents + team-fullstack) - Update v6 open items list This fixes runtime failures when advanced elicitation is invoked in bundled workflows by ensuring the 39 elicitation methods CSV is properly included. Note: Web bundler still has optimizations and known issues to address in upcoming commits. 2025-11-07 00:38:28 -06:00			`- finalize web bundler`
			`- some subagents working again`
			`- knowledge base for bmad`
update open items list 2025-10-27 18:27:10 -05:00
doc updates 2025-10-26 23:25:48 -05:00			`## Needed Beta → v0 release`
readme updates and open items published 2025-09-29 10:13:22 -05:00
			`Aside from stability and bug fixes found during the alpha period - the main focus will be on the following:`

doc updates 2025-10-26 23:25:48 -05:00			`- knowledge base for BMM`
readme updates and open items published 2025-09-29 10:13:22 -05:00			`- Module repository and submission process defined`
			`- MCP Injections based on installation selection`
refactor(bmm,cis,core): Align diagram workflows with agile roles and distribute capabilities ## The Tale of the Frame Expert Once upon a time, BMad Method had a specialized agent called Frame Expert. This agent was the master of all visual artifacts - flowcharts, diagrams, wireframes, data flows. Whenever anyone needed a diagram, they called upon Frame Expert. The agent lived in its own isolated domain with four dedicated workflows and a library of shared templates. ## The Awakening But something felt wrong. Teams using BMad Method were meant to mirror real agile teams - Product Managers, Architects, UX Designers, Tech Writers, Developers. Each agent represented an authentic role you'd find in any software team. Except Frame Expert. No real agile team has a "Frame Expert" or "Diagram Specialist" who creates all visual artifacts. In real teams, Architects diagram system architecture. PMs flowchart processes. UX Designers wireframe interfaces. Tech Writers create documentation diagrams. The visuals emerge from the domain experts who need them, not from a centralized diagram factory. Frame Expert was an abstraction that made technical sense but violated the very soul of BMad Method - authentic agile role modeling. ## The Transformation And so Frame Expert was dissolved, its knowledge distributed to those who truly needed it: The Architect inherited system architecture diagrams and data flows - the blueprints of technical systems they design. The Product Manager received process flowcharts - the visual maps of features and workflows they orchestrate. The UX Designer claimed wireframes - the interface sketches that bring their vision to life. The Tech Writer gained all diagram types - the visual aids that clarify their documentation. Each agent now creates diagrams in their domain, using their expertise, serving their purpose. ## The Shared Knowledge But the wisdom of diagram creation itself - the Excalidraw templates, the component libraries, the validation patterns - this knowledge was too valuable to scatter. It was elevated to core resources, where both BMM agents AND the new CIS presentation-master agent could draw upon it. Shared infrastructure for common needs. Distributed execution for domain expertise. ## The Ripple Effects With diagrams now properly distributed, other misalignments became visible: Epic creation was happening in Phase 2 (Planning), before Architecture existed. But epics need architectural context - API contracts, data models, technical decisions. So epic creation migrated to Phase 3 (Solutioning), after Architecture provides that foundation. Workflow paths were updated. Documentation gained visual flowcharts showing the complete journey. Agent naming standards were clarified - filenames are stable roles, persona names are user dreams. ## What Changed Removed: - frame-expert.agent.yaml (the centralized specialist) - All frame-expert workflows and shared resources - Phase 2 epic creation workflow (wrong timing) - game-design workflow path (consolidated to method track) - v6-open-items.md (planning doc, now complete) Distributed Diagram Capabilities: - Architect: create-excalidraw-diagram, create-excalidraw-dataflow - PM: create-excalidraw-flowchart - Tech Writer: create-excalidraw-{diagram,dataflow,flowchart}, generate-mermaid - UX Designer: create-excalidraw-wireframe Created: - src/core/resources/ (shared diagram context for all modules) - src/modules/cis/agents/presentation-master.agent.yaml (visual comms specialist) - src/modules/bmm/workflows/3-solutioning/create-epics-and-stories/ (epic creation's new home) - src/modules/bmm/workflows/diagrams/ (distributed diagram implementations) - src/modules/bmm/docs/images/ (workflow visualization assets) Enhanced: - All agent definitions with domain-appropriate diagram workflows - Documentation with embedded workflow diagrams and visual guides - Agent compilation docs with critical naming convention rules - All 4 workflow paths (enterprise/method × brownfield/greenfield) Fixed: - Epic creation now in Phase 3 after Architecture - Story context path variables in BMGD module - PRD workflow descriptions (epics moved to Phase 3) ## For Users The Frame Expert commands are gone. In their place: - Need architecture diagrams? Ask `/architect` - Need process flows? Ask `/pm` - Need wireframes? Ask `/ux-designer` - Need documentation visuals? Ask `/tech-writer` Each expert creates diagrams in their domain, with their context, using their judgment. This is how real teams work. 2025-11-18 21:54:48 -06:00			`- sub agent for open-code and claude code optimization`
readme updates and open items published 2025-09-29 10:13:22 -05:00			`- TDD Workflow Integration`