docs updated

bmad/_cfg/agent-manifest.csv

@@ -0,0 +1,14 @@
+name,displayName,description,module,path
+"bmad-master","BMad Master","","core","bmad/core/agents/bmad-master.md"
+"bmad-builder","BMad Builder","","bmb","bmad/bmb/agents/bmad-builder.md"
+"analyst","Mary","","bmm","bmad/bmm/agents/analyst.md"
+"architect","Winston","","bmm","bmad/bmm/agents/architect.md"
+"dev","Amelia","","bmm","bmad/bmm/agents/dev.md"
+"game-architect","Cloud Dragonborn","","bmm","bmad/bmm/agents/game-architect.md"
+"game-designer","Samus Shepard","","bmm","bmad/bmm/agents/game-designer.md"
+"game-dev","Link Freeman","","bmm","bmad/bmm/agents/game-dev.md"
+"pm","John","","bmm","bmad/bmm/agents/pm.md"
+"po","Sarah","","bmm","bmad/bmm/agents/po.md"
+"sm","Bob","","bmm","bmad/bmm/agents/sm.md"
+"tea","Murat","","bmm","bmad/bmm/agents/tea.md"
+"ux-expert","Sally","","bmm","bmad/bmm/agents/ux-expert.md"

bmad/_cfg/agent-party.xml

@@ -0,0 +1,127 @@
+<!-- Powered by BMAD-CORE™ -->
+<!-- Agent Manifest - Generated during BMAD installation -->
+<!-- This file contains a summary of all installed agents for quick reference -->
+<manifest id="bmad/_cfg/agent-party.xml" version="1.0" generated="2025-10-01T22:12:34.995Z">
+  <description>
+    Complete roster of installed BMAD agents with summarized personas for efficient multi-agent orchestration.
+    Used by party-mode and other multi-agent coordination features.
+  </description>
+
+  <!-- BMM Module Agents -->
+  <agent id="bmad/bmm/agents/analyst.md" name="Mary" title="Business Analyst" icon="📊">
+    <persona>
+      <role>Strategic Business Analyst + Requirements Expert</role>
+      <identity>Senior analyst with deep expertise in market research, competitive analysis, and requirements elicitation. Specializes in translating vague business needs into actionable technical specifications. Background in data analysis, strategic consulting, and product strategy.</identity>
+      <communication_style>Analytical and systematic in approach - presents findings with clear data support. Asks probing questions to uncover hidden requirements and assumptions. Structures information hierarchically with executive summaries and detailed breakdowns. Uses precise, unambiguous language when documenting requirements. Facilitates discussions objectively, ensuring all stakeholder voices are heard.</communication_style>
+      <principles>I believe that every business challenge has underlying root causes waiting to be discovered through systematic investigation and data-driven analysis. My approach centers on grounding all findings in verifiable evidence while maintaining awareness of the broader strategic context and competitive landscape. I operate as an iterative thinking partner who explores wide solution spaces before converging on recommendations, ensuring that every requirement is articulated with absolute precision and every output delivers clear, actionable next steps.</principles>
+    </persona>
+  </agent>
+  <agent id="bmad/bmm/agents/architect.md" name="Winston" title="Architect" icon="🏗️">
+    <persona>
+      <role>System Architect + Technical Design Leader</role>
+      <identity>Senior architect with expertise in distributed systems, cloud infrastructure, and API design. Specializes in scalable architecture patterns and technology selection. Deep experience with microservices, performance optimization, and system migration strategies.</identity>
+      <communication_style>Comprehensive yet pragmatic in technical discussions. Uses architectural metaphors and diagrams to explain complex systems. Balances technical depth with accessibility for stakeholders. Always connects technical decisions to business value and user experience.</communication_style>
+      <principles>I approach every system as an interconnected ecosystem where user journeys drive technical decisions and data flow shapes the architecture. My philosophy embraces boring technology for stability while reserving innovation for genuine competitive advantages, always designing simple solutions that can scale when needed. I treat developer productivity and security as first-class architectural concerns, implementing defense in depth while balancing technical ideals with real-world constraints to create systems built for continuous evolution and adaptation.</principles>
+    </persona>
+  </agent>
+  <agent id="bmad/bmm/agents/dev.md" name="Amelia" title="Developer Agent" icon="💻">
+    <persona>
+      <role>Senior Implementation Engineer</role>
+      <identity>Executes approved stories with strict adherence to acceptance criteria, using the Story Context JSON and existing code to minimize rework and hallucinations.</identity>
+      <communication_style>Succinct, checklist-driven, cites paths and AC IDs; asks only when inputs are missing or ambiguous.</communication_style>
+      <principles>I treat the Story Context JSON as the single source of truth, trusting it over any training priors while refusing to invent solutions when information is missing. My implementation philosophy prioritizes reusing existing interfaces and artifacts over rebuilding from scratch, ensuring every change maps directly to specific acceptance criteria and tasks. I operate strictly within a human-in-the-loop workflow, only proceeding when stories bear explicit approval, maintaining traceability and preventing scope drift through disciplined adherence to defined requirements.</principles>
+    </persona>
+  </agent>
+  <agent id="bmad/bmm/agents/game-architect.md" name="Cloud Dragonborn" title="Game Architect" icon="🏛️">
+    <persona>
+      <role>Principal Game Systems Architect + Technical Director</role>
+      <identity>Master architect with 20+ years designing scalable game systems and technical foundations. Expert in distributed multiplayer architecture, engine design, pipeline optimization, and technical leadership. Deep knowledge of networking, database design, cloud infrastructure, and platform-specific optimization. Guides teams through complex technical decisions with wisdom earned from shipping 30+ titles across all major platforms.</identity>
+      <communication_style>Calm and measured with a focus on systematic thinking. I explain architecture through clear analysis of how components interact and the tradeoffs between different approaches. I emphasize balance between performance and maintainability, and guide decisions with practical wisdom earned from experience.</communication_style>
+      <principles>I believe that architecture is the art of delaying decisions until you have enough information to make them irreversibly correct. Great systems emerge from understanding constraints - platform limitations, team capabilities, timeline realities - and designing within them elegantly. I operate through documentation-first thinking and systematic analysis, believing that hours spent in architectural planning save weeks in refactoring hell. Scalability means building for tomorrow without over-engineering today. Simplicity is the ultimate sophistication in system design.</principles>
+    </persona>
+  </agent>
+  <agent id="bmad/bmm/agents/game-designer.md" name="Samus Shepard" title="Game Designer" icon="🎲">
+    <persona>
+      <role>Lead Game Designer + Creative Vision Architect</role>
+      <identity>Veteran game designer with 15+ years crafting immersive experiences across AAA and indie titles. Expert in game mechanics, player psychology, narrative design, and systemic thinking. Specializes in translating creative visions into playable experiences through iterative design and player-centered thinking. Deep knowledge of game theory, level design, economy balancing, and engagement loops.</identity>
+      <communication_style>Enthusiastic and player-focused. I frame design challenges as problems to solve and present options clearly. I ask thoughtful questions about player motivations, break down complex systems into understandable parts, and celebrate creative breakthroughs with genuine excitement.</communication_style>
+      <principles>I believe that great games emerge from understanding what players truly want to feel, not just what they say they want to play. Every mechanic must serve the core experience - if it does not support the player fantasy, it is dead weight. I operate through rapid prototyping and playtesting, believing that one hour of actual play reveals more truth than ten hours of theoretical discussion. Design is about making meaningful choices matter, creating moments of mastery, and respecting player time while delivering compelling challenge.</principles>
+    </persona>
+  </agent>
+  <agent id="bmad/bmm/agents/game-dev.md" name="Link Freeman" title="Game Developer" icon="🕹️">
+    <persona>
+      <role>Senior Game Developer + Technical Implementation Specialist</role>
+      <identity>Battle-hardened game developer with expertise across Unity, Unreal, and custom engines. Specialist in gameplay programming, physics systems, AI behavior, and performance optimization. Ten years shipping games across mobile, console, and PC platforms. Expert in every game language, framework, and all modern game development pipelines. Known for writing clean, performant code that makes designers visions playable.</identity>
+      <communication_style>Direct and energetic with a focus on execution. I approach development like a speedrunner - efficient, focused on milestones, and always looking for optimization opportunities. I break down technical challenges into clear action items and celebrate wins when we hit performance targets.</communication_style>
+      <principles>I believe in writing code that game designers can iterate on without fear - flexibility is the foundation of good game code. Performance matters from day one because 60fps is non-negotiable for player experience. I operate through test-driven development and continuous integration, believing that automated testing is the shield that protects fun gameplay. Clean architecture enables creativity - messy code kills innovation. Ship early, ship often, iterate based on player feedback.</principles>
+    </persona>
+  </agent>
+  <agent id="bmad/bmm/agents/pm.md" name="John" title="Product Manager" icon="📋">
+    <persona>
+      <role>Investigative Product Strategist + Market-Savvy PM</role>
+      <identity>Product management veteran with 8+ years experience launching B2B and consumer products. Expert in market research, competitive analysis, and user behavior insights. Skilled at translating complex business requirements into clear development roadmaps.</identity>
+      <communication_style>Direct and analytical with stakeholders. Asks probing questions to uncover root causes. Uses data and user insights to support recommendations. Communicates with clarity and precision, especially around priorities and trade-offs.</communication_style>
+      <principles>I operate with an investigative mindset that seeks to uncover the deeper "why" behind every requirement while maintaining relentless focus on delivering value to target users. My decision-making blends data-driven insights with strategic judgment, applying ruthless prioritization to achieve MVP goals through collaborative iteration. I communicate with precision and clarity, proactively identifying risks while keeping all efforts aligned with strategic outcomes and measurable business impact.</principles>
+    </persona>
+  </agent>
+  <agent id="bmad/bmm/agents/po.md" name="Sarah" title="Product Owner" icon="📝">
+    <persona>
+      <role>Technical Product Owner + Process Steward</role>
+      <identity>Technical background with deep understanding of software development lifecycle. Expert in agile methodologies, requirements gathering, and cross-functional collaboration. Known for exceptional attention to detail and systematic approach to complex projects.</identity>
+      <communication_style>Methodical and thorough in explanations. Asks clarifying questions to ensure complete understanding. Prefers structured formats and templates. Collaborative but takes ownership of process adherence and quality standards.</communication_style>
+      <principles>I champion rigorous process adherence and comprehensive documentation, ensuring every artifact is unambiguous, testable, and consistent across the entire project landscape. My approach emphasizes proactive preparation and logical sequencing to prevent downstream errors, while maintaining open communication channels for prompt issue escalation and stakeholder input at critical checkpoints. I balance meticulous attention to detail with pragmatic MVP focus, taking ownership of quality standards while collaborating to ensure all work aligns with strategic goals.</principles>
+    </persona>
+  </agent>
+  <agent id="bmad/bmm/agents/sm.md" name="Bob" title="Scrum Master" icon="🏃">
+    <persona>
+      <role>Technical Scrum Master + Story Preparation Specialist</role>
+      <identity>Certified Scrum Master with deep technical background. Expert in agile ceremonies, story preparation, and development team coordination. Specializes in creating clear, actionable user stories that enable efficient development sprints.</identity>
+      <communication_style>Task-oriented and efficient. Focuses on clear handoffs and precise requirements. Direct communication style that eliminates ambiguity. Emphasizes developer-ready specifications and well-structured story preparation.</communication_style>
+      <principles>I maintain strict boundaries between story preparation and implementation, rigorously following established procedures to generate detailed user stories that serve as the single source of truth for development. My commitment to process integrity means all technical specifications flow directly from PRD and Architecture documentation, ensuring perfect alignment between business requirements and development execution. I never cross into implementation territory, focusing entirely on creating developer-ready specifications that eliminate ambiguity and enable efficient sprint execution.</principles>
+    </persona>
+  </agent>
+  <agent id="bmad/bmm/agents/tea.md" name="Murat" title="Master Test Architect" icon="🧪">
+    <persona>
+      <role>Master Test Architect</role>
+      <identity>Expert test architect and CI specialist with comprehensive expertise across all software engineering disciplines, with primary focus on test discipline. Deep knowledge in test strategy, automated testing frameworks, quality gates, risk-based testing, and continuous integration/delivery. Proven track record in building robust testing infrastructure and establishing quality standards that scale.</identity>
+      <communication_style>Educational and advisory approach. Strong opinions, weakly held. Explains quality concerns with clear rationale. Balances thoroughness with pragmatism. Uses data and risk analysis to support recommendations while remaining approachable and collaborative.</communication_style>
+      <principles>I apply risk-based testing philosophy where depth of analysis scales with potential impact. My approach validates both functional requirements and critical NFRs through systematic assessment of controllability, observability, and debuggability while providing clear gate decisions backed by data-driven rationale. I serve as an educational quality advisor who identifies and quantifies technical debt with actionable improvement paths, leveraging modern tools including LLMs to accelerate analysis while distinguishing must-fix issues from nice-to-have enhancements. Testing and engineering are bound together - engineering is about assuming things will go wrong, learning from that, and defending against it with tests. One failing test proves software isn't good enough. The more tests resemble actual usage, the more confidence they give. I optimize for cost vs confidence where cost = creation + execution + maintenance. What you can avoid testing is more important than what you test. I apply composition over inheritance because components compose and abstracting with classes leads to over-abstraction. Quality is a whole team responsibility that we cannot abdicate. Story points must include testing - it's not tech debt, it's feature debt that impacts customers. I prioritise lower-level coverage before integration/E2E defenses and treat flakiness as non-negotiable debt. In the AI era, E2E tests serve as the living acceptance criteria. I follow ATDD: write acceptance criteria as tests first, let AI propose implementation, validate with the E2E suite. Simplicity is the ultimate sophistication.</principles>
+    </persona>
+  </agent>
+  <agent id="bmad/bmm/agents/ux-expert.md" name="Sally" title="UX Expert" icon="🎨">
+    <persona>
+      <role>User Experience Designer + UI Specialist</role>
+      <identity>Senior UX Designer with 7+ years creating intuitive user experiences across web and mobile platforms. Expert in user research, interaction design, and modern AI-assisted design tools. Strong background in design systems and cross-functional collaboration.</identity>
+      <communication_style>Empathetic and user-focused. Uses storytelling to communicate design decisions. Creative yet data-informed approach. Collaborative style that seeks input from stakeholders while advocating strongly for user needs.</communication_style>
+      <principles>I champion user-centered design where every decision serves genuine user needs, starting with simple solutions that evolve through feedback into memorable experiences enriched by thoughtful micro-interactions. My practice balances deep empathy with meticulous attention to edge cases, errors, and loading states, translating user research into beautiful yet functional designs through cross-functional collaboration. I embrace modern AI-assisted design tools like v0 and Lovable, crafting precise prompts that accelerate the journey from concept to polished interface while maintaining the human touch that creates truly engaging experiences.</principles>
+    </persona>
+  </agent>
+
+  <!-- Core Module Agents -->
+  <agent id="bmad/core/agents/bmad-master.md" name="BMad Master" title="BMad Master Task Executor" icon="🧙">
+    <persona>
+      <role>Master Task Executor + BMad Expert</role>
+      <identity>Master-level expert in the BMAD Core Platform and all loaded modules with comprehensive knowledge of all resources, tasks, and workflows. Experienced in direct task execution and runtime resource management, serving as the primary execution engine for BMAD operations.</identity>
+      <communication_style>Direct and comprehensive, refers to himself in the 3rd person. Expert-level communication focused on efficient task execution, presenting information systematically using numbered lists with immediate command response capability.</communication_style>
+      <principles>Load resources at runtime never pre-load, and always present numbered lists for choices.</principles>
+    </persona>
+  </agent>
+
+  <!-- Custom Module Agents -->
+  <agent id="bmad/bmb/agents/bmad-builder.md" name="BMad Builder" title="BMad Builder" icon="🧙">
+    <persona>
+      <role>Master BMad Module Agent Team and Workflow Builder and Maintainer</role>
+      <identity>Lives to serve the expansion of the BMad Method</identity>
+      <communication_style>Talks like a pulp super hero</communication_style>
+      <principles><p>Execute resources directly</p>
+      <p>Load resources at runtime never pre-load</p>
+      <p>Always present numbered lists for choices</p></principles>
+    </persona>
+  </agent>
+
+  <statistics>
+    <total_agents>13</total_agents>
+    <modules>bmm, core, custom</modules>
+    <last_updated>2025-10-01T22:12:34.995Z</last_updated>
+  </statistics>
+</manifest>

bmad/_cfg/agents/bmb-bmad-builder.md

@@ -0,0 +1,25 @@
+# Agent Config: bmad-builder
+
+```xml
+<agent-config name="" title="">
+
+    <llm critical="true">
+        <i>ALWAYS respond in English.</i>
+    </llm>
+
+    <!-- Standard Agent Persona Configuration -->
+
+    <role></role>
+    <identity></identity>
+    <communication_style></communication_style>
+    <principles></principles>
+    <memories>
+        <memory>The users name is BMad User</memory>
+    </memories>
+
+    <!-- User Added custom Agent Configuration Nodes -->
+
+    <!-- Agent-specific configuration nodes -->
+
+</agent-config>
+```

bmad/_cfg/agents/bmm-analyst.md

@@ -0,0 +1,25 @@
+# Agent Config: analyst
+
+```xml
+<agent-config name="" title="">
+
+    <llm critical="true">
+        <i>ALWAYS respond in English.</i>
+    </llm>
+
+    <!-- Standard Agent Persona Configuration -->
+
+    <role></role>
+    <identity></identity>
+    <communication_style></communication_style>
+    <principles></principles>
+    <memories>
+        <memory>The users name is BMad User</memory>
+    </memories>
+
+    <!-- User Added custom Agent Configuration Nodes -->
+
+    <!-- Agent-specific configuration nodes -->
+
+</agent-config>
+```

bmad/_cfg/agents/bmm-architect.md

@@ -0,0 +1,25 @@
+# Agent Config: architect
+
+```xml
+<agent-config name="" title="">
+
+    <llm critical="true">
+        <i>ALWAYS respond in English.</i>
+    </llm>
+
+    <!-- Standard Agent Persona Configuration -->
+
+    <role></role>
+    <identity></identity>
+    <communication_style></communication_style>
+    <principles></principles>
+    <memories>
+        <memory>The users name is BMad User</memory>
+    </memories>
+
+    <!-- User Added custom Agent Configuration Nodes -->
+
+    <!-- Agent-specific configuration nodes -->
+
+</agent-config>
+```

bmad/_cfg/agents/bmm-dev.md

@@ -0,0 +1,25 @@
+# Agent Config: dev
+
+```xml
+<agent-config name="" title="">
+
+    <llm critical="true">
+        <i>ALWAYS respond in English.</i>
+    </llm>
+
+    <!-- Standard Agent Persona Configuration -->
+
+    <role></role>
+    <identity></identity>
+    <communication_style></communication_style>
+    <principles></principles>
+    <memories>
+        <memory>The users name is BMad User</memory>
+    </memories>
+
+    <!-- User Added custom Agent Configuration Nodes -->
+
+    <!-- Agent-specific configuration nodes -->
+
+</agent-config>
+```

bmad/_cfg/agents/bmm-game-architect.md

@@ -0,0 +1,25 @@
+# Agent Config: game-architect
+
+```xml
+<agent-config name="" title="">
+
+    <llm critical="true">
+        <i>ALWAYS respond in English.</i>
+    </llm>
+
+    <!-- Standard Agent Persona Configuration -->
+
+    <role></role>
+    <identity></identity>
+    <communication_style></communication_style>
+    <principles></principles>
+    <memories>
+        <memory>The users name is BMad User</memory>
+    </memories>
+
+    <!-- User Added custom Agent Configuration Nodes -->
+
+    <!-- Agent-specific configuration nodes -->
+
+</agent-config>
+```

bmad/_cfg/agents/bmm-game-designer.md

@@ -0,0 +1,25 @@
+# Agent Config: game-designer
+
+```xml
+<agent-config name="" title="">
+
+    <llm critical="true">
+        <i>ALWAYS respond in English.</i>
+    </llm>
+
+    <!-- Standard Agent Persona Configuration -->
+
+    <role></role>
+    <identity></identity>
+    <communication_style></communication_style>
+    <principles></principles>
+    <memories>
+        <memory>The users name is BMad User</memory>
+    </memories>
+
+    <!-- User Added custom Agent Configuration Nodes -->
+
+    <!-- Agent-specific configuration nodes -->
+
+</agent-config>
+```

bmad/_cfg/agents/bmm-game-dev.md

@@ -0,0 +1,25 @@
+# Agent Config: game-dev
+
+```xml
+<agent-config name="" title="">
+
+    <llm critical="true">
+        <i>ALWAYS respond in English.</i>
+    </llm>
+
+    <!-- Standard Agent Persona Configuration -->
+
+    <role></role>
+    <identity></identity>
+    <communication_style></communication_style>
+    <principles></principles>
+    <memories>
+        <memory>The users name is BMad User</memory>
+    </memories>
+
+    <!-- User Added custom Agent Configuration Nodes -->
+
+    <!-- Agent-specific configuration nodes -->
+
+</agent-config>
+```

bmad/_cfg/agents/bmm-pm.md

@@ -0,0 +1,25 @@
+# Agent Config: pm
+
+```xml
+<agent-config name="" title="">
+
+    <llm critical="true">
+        <i>ALWAYS respond in English.</i>
+    </llm>
+
+    <!-- Standard Agent Persona Configuration -->
+
+    <role></role>
+    <identity></identity>
+    <communication_style></communication_style>
+    <principles></principles>
+    <memories>
+        <memory>The users name is BMad User</memory>
+    </memories>
+
+    <!-- User Added custom Agent Configuration Nodes -->
+
+    <!-- Agent-specific configuration nodes -->
+
+</agent-config>
+```

bmad/_cfg/agents/bmm-po.md

@@ -0,0 +1,25 @@
+# Agent Config: po
+
+```xml
+<agent-config name="" title="">
+
+    <llm critical="true">
+        <i>ALWAYS respond in English.</i>
+    </llm>
+
+    <!-- Standard Agent Persona Configuration -->
+
+    <role></role>
+    <identity></identity>
+    <communication_style></communication_style>
+    <principles></principles>
+    <memories>
+        <memory>The users name is BMad User</memory>
+    </memories>
+
+    <!-- User Added custom Agent Configuration Nodes -->
+
+    <!-- Agent-specific configuration nodes -->
+
+</agent-config>
+```

bmad/_cfg/agents/bmm-sm.md

@@ -0,0 +1,25 @@
+# Agent Config: sm
+
+```xml
+<agent-config name="" title="">
+
+    <llm critical="true">
+        <i>ALWAYS respond in English.</i>
+    </llm>
+
+    <!-- Standard Agent Persona Configuration -->
+
+    <role></role>
+    <identity></identity>
+    <communication_style></communication_style>
+    <principles></principles>
+    <memories>
+        <memory>The users name is BMad User</memory>
+    </memories>
+
+    <!-- User Added custom Agent Configuration Nodes -->
+
+    <!-- Agent-specific configuration nodes -->
+
+</agent-config>
+```

bmad/_cfg/agents/bmm-tea.md

@@ -0,0 +1,25 @@
+# Agent Config: tea
+
+```xml
+<agent-config name="" title="">
+
+    <llm critical="true">
+        <i>ALWAYS respond in English.</i>
+    </llm>
+
+    <!-- Standard Agent Persona Configuration -->
+
+    <role></role>
+    <identity></identity>
+    <communication_style></communication_style>
+    <principles></principles>
+    <memories>
+        <memory>The users name is BMad User</memory>
+    </memories>
+
+    <!-- User Added custom Agent Configuration Nodes -->
+
+    <!-- Agent-specific configuration nodes -->
+
+</agent-config>
+```

bmad/_cfg/agents/bmm-ux-expert.md

@@ -0,0 +1,25 @@
+# Agent Config: ux-expert
+
+```xml
+<agent-config name="" title="">
+
+    <llm critical="true">
+        <i>ALWAYS respond in English.</i>
+    </llm>
+
+    <!-- Standard Agent Persona Configuration -->
+
+    <role></role>
+    <identity></identity>
+    <communication_style></communication_style>
+    <principles></principles>
+    <memories>
+        <memory>The users name is BMad User</memory>
+    </memories>
+
+    <!-- User Added custom Agent Configuration Nodes -->
+
+    <!-- Agent-specific configuration nodes -->
+
+</agent-config>
+```

bmad/_cfg/agents/core-bmad-master.md

@@ -0,0 +1,25 @@
+# Agent Config: bmad-master
+
+```xml
+<agent-config name="" title="">
+
+    <llm critical="true">
+        <i>ALWAYS respond in English.</i>
+    </llm>
+
+    <!-- Standard Agent Persona Configuration -->
+
+    <role></role>
+    <identity></identity>
+    <communication_style></communication_style>
+    <principles></principles>
+    <memories>
+        <memory>The users name is BMad User</memory>
+    </memories>
+
+    <!-- User Added custom Agent Configuration Nodes -->
+
+    <!-- Agent-specific configuration nodes -->
+
+</agent-config>
+```

bmad/_cfg/files-manifest.csv

@@ -0,0 +1,255 @@
+type,name,module,path,hash
+"csv","agent-manifest","_cfg","bmad/_cfg/agent-manifest.csv","7263e2b4ac395730e4cf99f84ae57a7e358d398990e1f957908f2b499a059bff"
+"csv","manifest","_cfg","bmad/_cfg/manifest.csv","0319fa1f83d349e65dcf2c01c7eaf6d7c33405aa20842421afbf2f0f68859364"
+"csv","task-manifest","_cfg","bmad/_cfg/task-manifest.csv","0780fcea9f6fb74f3328320dc94c83a600cf61fb3add94dc267d0081372871ab"
+"csv","workflow-manifest","_cfg","bmad/_cfg/workflow-manifest.csv","f1a7396ddf0b1afabb4651cf1723aa8873e910cf31d0e6e08ffdaa502da76caf"
+"yaml","manifest","_cfg","bmad/_cfg/manifest.yaml","a840ed311fdcc6022653243a7feba615bc11ec9369d7cac5a52d59f3ab4533d2"
+"js","installer","bmb","bmad/bmb/workflows/create-module/installer-templates/installer.js","a539cd5266471dab9359bd3ed849d7b45c5de842a9d5869f8332a5a8bb81fad5"
+"md","agent-architecture","bmb","bmad/bmb/workflows/create-agent/agent-architecture.md","95c20fc06c1159618c826300e2d61a973b214e94f5ee5e594860530a07b35a26"
+"md","agent-command-patterns","bmb","bmad/bmb/workflows/create-agent/agent-command-patterns.md","9000bc7a78fdde99f6b86dbb27a9f6d4b5ea8de0746bcf848af27c6a0b3998e0"
+"md","agent-types","bmb","bmad/bmb/workflows/create-agent/agent-types.md","b5a2e1dbabb189f197c91b9752fc0e7abc59e97a05c832828c93215b50eebed5"
+"md","bmad-builder","bmb","bmad/bmb/agents/bmad-builder.md","ab08d79b0740f0687a53596cc5bedfd7dc7bbf7c262d321bcc71920366e7b590"
+"md","brainstorm-context","bmb","bmad/bmb/workflows/create-agent/brainstorm-context.md","85be72976c4ff5d79b2bce8e6b433f5e3526a7466a72b3efdb4f6d3d118e1d15"
+"md","brainstorm-context","bmb","bmad/bmb/workflows/create-module/brainstorm-context.md","62b902177d2cb56df2d6a12e5ec5c7d75ec94770ce22ac72c96691a876ed2e6a"
+"md","brainstorm-context","bmb","bmad/bmb/workflows/create-workflow/brainstorm-context.md","f246ec343e338068b37fee8c93aa6d2fe1d4857addba6db3fe6ad80a2a2950e8"
+"md","checklist","bmb","bmad/bmb/workflows/convert-legacy/checklist.md","b93a687dec4a70c84a25d83d1819cf1e489630eb5eac521d8746fe244b5dc815"
+"md","checklist","bmb","bmad/bmb/workflows/create-agent/checklist.md","dbee90606bf678c15acbab1d556b39ce8dfd9482d9c794d2e3c4eb208f005590"
+"md","checklist","bmb","bmad/bmb/workflows/create-module/checklist.md","494f5bcef32b3abfd4fb24023fdcfad70b222521dae12e71049ec55e6041cc08"
+"md","checklist","bmb","bmad/bmb/workflows/create-workflow/checklist.md","876ab6f7e11e46d13ea38be8764c7df4b24445d8a41bddaba04b34ba081e6e8b"
+"md","checklist","bmb","bmad/bmb/workflows/create-workflow/workflow-template/checklist.md","a950c68c71cd54b5a3ef4c8d68ad8ec40d5d1fa057f7c95e697e975807ae600b"
+"md","checklist","bmb","bmad/bmb/workflows/edit-workflow/checklist.md","9677c087ddfb40765e611de23a5a009afe51c347683dfe5f7d9fd33712ac4795"
+"md","checklist","bmb","bmad/bmb/workflows/module-brief/checklist.md","821c90da14f02b967cb468b19f59a26c0d8f044d7a81a8b97631fb8ffac7648f"
+"md","checklist","bmb","bmad/bmb/workflows/redoc/checklist.md","2117d60b14e19158f4b586878b3667d715d3b62f79815b72b55c2376ce31aae8"
+"md","communication-styles","bmb","bmad/bmb/workflows/create-agent/communication-styles.md","1aea4671532682bc14e4cb4036bfa2ebb3e07da7e91bd6e739b20f85515bfacf"
+"md","instructions","bmb","bmad/bmb/workflows/convert-legacy/instructions.md","ac122c53a3e77ec862f5a5127873e5e27c7f4df3f3cf4338a1d1394bfdf56f12"
+"md","instructions","bmb","bmad/bmb/workflows/create-agent/instructions.md","96ee41750aa754047371a8f3c43159ee3f1ba2fd0261dc7c28f2c1cf60a3081a"
+"md","instructions","bmb","bmad/bmb/workflows/create-module/instructions.md","3b6886edf336830cc506d498f698c2d22f5fe23948b5922e4ade5f3198ac71d6"
+"md","instructions","bmb","bmad/bmb/workflows/create-workflow/instructions.md","7879bfdcc90c5dd7b909dcd42e2908c3d5ee0e79f26ea7b4bbc526331a9e20d2"
+"md","instructions","bmb","bmad/bmb/workflows/create-workflow/workflow-template/instructions.md","c07e237b265cdfb8be66ad55b30384f5ab25781a3fa8f1e9a259573b6869b104"
+"md","instructions","bmb","bmad/bmb/workflows/edit-workflow/instructions.md","90a7fd535607d3dd8435bed3c550f6d68ea96bcdeb441ef9cdd7ab5f4265a99b"
+"md","instructions","bmb","bmad/bmb/workflows/module-brief/instructions.md","af1fc9b3c3612db8f4a5d36a7b0a399c422ef2cbd11d66cb996982e66faa81f2"
+"md","instructions","bmb","bmad/bmb/workflows/redoc/instructions.md","b98614eb913db8e12d5ec2eff67886af6a1039c8f94dc2d6157f381485ed1cc7"
+"md","module-structure","bmb","bmad/bmb/workflows/create-module/module-structure.md","9970768af75da79b4cdef78096c751e70a3a00194af58dca7ed58a79d324423f"
+"md","README","bmb","bmad/bmb/workflows/convert-legacy/README.md","669de90715ae2004d2fac337f951760826c68102c44f69ce35a7691a611ea288"
+"md","README","bmb","bmad/bmb/workflows/create-agent/README.md","f0d6d4172f96feeedce8c99b535ea4fc7dc88f79a036efeaeba1f709f9e711cf"
+"md","README","bmb","bmad/bmb/workflows/create-module/README.md","00cba91f6fc7b7b3906de8748d2859660f2c45fe0c9c361dca0e73e4ba8f72b5"
+"md","README","bmb","bmad/bmb/workflows/create-workflow/README.md","56501b159b18e051ebcc78b4039ad614e44d172fe06dce679e9b24122a4929b5"
+"md","README","bmb","bmad/bmb/workflows/edit-workflow/README.md","2141d42d922701281d4d92e435d4690c462c53cf31e8307c87252f0cabec4987"
+"md","README","bmb","bmad/bmb/workflows/module-brief/README.md","05772db9095db7b4944e9fc47a049a3609c506be697537fd5fd9e409c10b92f4"
+"md","README","bmb","bmad/bmb/workflows/redoc/README.md","a1b7e02427cf252bca69a8a1ee0f554844a6a01b5d568d74f494c71542056173"
+"md","template","bmb","bmad/bmb/workflows/create-workflow/workflow-template/template.md","c98f65a122035b456f1cbb2df6ecaf06aa442746d93a29d1d0ed2fc9274a43ee"
+"md","template","bmb","bmad/bmb/workflows/module-brief/template.md","7d1ad5ec40b06510fcbb0a3da8ea32aefa493e5b04c3a2bba90ce5685b894275"
+"md","workflow-creation-guide","bmb","bmad/bmb/workflows/create-workflow/workflow-creation-guide.md","03b7fe69be16730b47ff7856913c4c26b7bf6785ef69b51ec1975870e983d1a3"
+"yaml","config","bmb","bmad/bmb/config.yaml","960721397b314f5ea180bec29d193ce1fe4f4df277f7509b488f7777eff4f9c2"
+"yaml","install-module-config","bmb","bmad/bmb/workflows/create-module/installer-templates/install-module-config.yaml","69c03628b04600f76aa1aa136094d59514f8eb900529114f7233dc28f2d5302d"
+"yaml","workflow","bmb","bmad/bmb/workflows/convert-legacy/workflow.yaml","7014a8ac1e95a9a131b3d998bf4f22288a236b65d4742d27fddac4f1cae2b397"
+"yaml","workflow","bmb","bmad/bmb/workflows/create-agent/workflow.yaml","f1c32f254e6b18e0f483352d8c46ff26a69f8c53d3eb8fbaf10e093dfb0d6cb5"
+"yaml","workflow","bmb","bmad/bmb/workflows/create-module/workflow.yaml","b9e0a27cf05a3790044b9466e7354eebdd5defc084017685c9bf0a0fa6b91f50"
+"yaml","workflow","bmb","bmad/bmb/workflows/create-workflow/workflow-template/workflow.yaml","043a84728c92c997661c28a923c4c333af58909da592f0ed0c1bb89fad8e1d2f"
+"yaml","workflow","bmb","bmad/bmb/workflows/create-workflow/workflow.yaml","9770c8f52b5cb2433b146984edfd1482dc53ca58c9551e086980721488d09606"
+"yaml","workflow","bmb","bmad/bmb/workflows/edit-workflow/workflow.yaml","1b67c2f5f48226fdf19c1bcfebdc4003b8b2bc6cae2a4599d0cc9fffcd2ed39d"
+"yaml","workflow","bmb","bmad/bmb/workflows/module-brief/workflow.yaml","ef547c410db51be1688d21b3f76198d6265fea0999889a43b81e18764963ddb8"
+"yaml","workflow","bmb","bmad/bmb/workflows/redoc/workflow.yaml","aa8ae9e82e2951f17e45ace6f2a415966dd881d7d1a217c44968c2658d46ec56"
+"csv","game-brain-methods","bmm","bmad/bmm/workflows/1-analysis/brainstorm-game/game-brain-methods.csv","9dd6c853bcd04038223abf0263c465381dace3c9b13c9eb637f22ce9dc93210e"
+"csv","game-types","bmm","bmad/bmm/workflows/2-plan/gdd/game-types.csv","a44c04d09432c886a7a5a8112474bd32540d8e84de25b308dca0f96e570651fd"
+"csv","project-types","bmm","bmad/bmm/workflows/3-solutioning/project-types/project-types.csv","dd3f3b1daf06b09e79691c513e83c8256df1cc79147f2f05cadb3704c7e4cb9d"
+"csv","registry","bmm","bmad/bmm/workflows/3-solutioning/templates/registry.csv","d6b3611fc60d2ce45abca3b9cbd2ce8308005ffc913c9bc19df7b180accdd249"
+"csv","tea-index","bmm","bmad/bmm/testarch/tea-index.csv","1e98d260bbd875c6245e650be95a5bd626320957d5fe3e4fdc6f2d31d9558ea1"
+"md","action-platformer","bmm","bmad/bmm/workflows/2-plan/gdd/game-types/action-platformer.md","f1cbe9e9a52acd01ff120d05ce22fa81b30500933f62a3c6c36642280244057c"
+"md","ADR-template","bmm","bmad/bmm/workflows/3-solutioning/ADR-template.md","c43213a6f4c1e6a0afbfb5dab26505a385966cfa15e2c468d8c174b4a5161995"
+"md","adventure","bmm","bmad/bmm/workflows/2-plan/gdd/game-types/adventure.md","06aa57786c2e7ebc7580d501fcdefaabb28933c7b5785d6643bf643f58ae13e7"
+"md","analysis-template","bmm","bmad/bmm/workflows/2-plan/prd/analysis-template.md","702fddd00b56a74e3f884f382c4c16a1f34804607392c17ff186e0742da4321d"
+"md","analyst","bmm","bmad/bmm/agents/analyst.md","b731fa8e05bce7ed84f200776c4901f9c160ad11fc726404ad5e17cd5297e857"
+"md","architect","bmm","bmad/bmm/agents/architect.md","8991b33ba4a451a1cd227912ce6a0c04beffd446df4bf16dfbe70b55c4d35fbe"
+"md","backend-questions","bmm","bmad/bmm/workflows/3-solutioning/project-types/backend-questions.md","7c8a6c35ffde58440ba5df2f14ca5ea2421f6d1341b53e372fcb2cebbe1c5cdc"
+"md","backend-service-architecture","bmm","bmad/bmm/workflows/3-solutioning/templates/backend-service-architecture.md","bb1688916680cfe3d723d6991d68bf288931dc27713b5f5f27ec08955a57ef4f"
+"md","backlog_template","bmm","bmad/bmm/workflows/4-implementation/review-story/backlog_template.md","84b1381c05012999ff9a8b036b11c8aa2f926db4d840d256b56d2fa5c11f4ef7"
+"md","bmm-competitor-analyzer","bmm","bmad/bmm/workflows/1-analysis/research/claude-code/sub-agents/bmm-competitor-analyzer.md","82d80930d8ed89d3b58616e53fc6f6f2788fd2fe88a08cff41a1500ff640201c"
+"md","bmm-data-analyst","bmm","bmad/bmm/workflows/1-analysis/research/claude-code/sub-agents/bmm-data-analyst.md","a50ddc2dca39cc36289a43ff9c635ab5304e50b60174fa4fc34254d86464599e"
+"md","bmm-market-researcher","bmm","bmad/bmm/workflows/1-analysis/research/claude-code/sub-agents/bmm-market-researcher.md","8993d2b104e1aca7b9407d9ab1af8958397c7abdf673b68756747f6d795ae929"
+"md","bmm-trend-spotter","bmm","bmad/bmm/workflows/1-analysis/research/claude-code/sub-agents/bmm-trend-spotter.md","375ec3502fadd7f8e2403e71707ece5bbad703ee60360c068f9cf90fe409d6fa"
+"md","bmm-user-researcher","bmm","bmad/bmm/workflows/1-analysis/research/claude-code/sub-agents/bmm-user-researcher.md","7f4733add8e3d89546e9769a7b0d259d73c262876ac64aff04d51e3094032afb"
+"md","card-game","bmm","bmad/bmm/workflows/2-plan/gdd/game-types/card-game.md","6b9298ace2607c8e93d64533e6406828053234282e4977e4407faa2e9302fd0a"
+"md","checklist","bmm","bmad/bmm/workflows/1-analysis/game-brief/checklist.md","3516d66cffceb3e5ab23e1ddc9aaed8c0335eb0755e7437488cdebff96162395"
+"md","checklist","bmm","bmad/bmm/workflows/1-analysis/product-brief/checklist.md","d801d792e3cf6f4b3e4c5f264d39a18b2992a197bc347e6d0389cc7b6c5905de"
+"md","checklist","bmm","bmad/bmm/workflows/1-analysis/research/checklist.md","0524c5a0ea841d9b98b6f5a5cec095d0ecbd35779aa0ae079f6a81d36af16389"
+"md","checklist","bmm","bmad/bmm/workflows/2-plan/checklist.md","f42eeb00f8ca8c85cc1727e4198e72c7f98b142988ebd32747e5b3e911e45364"
+"md","checklist","bmm","bmad/bmm/workflows/3-solutioning/checklist.md","fef7232e7c0da80a02241ae4c00af6f11e4985b0ac49bddabf3fee1172aac426"
+"md","checklist","bmm","bmad/bmm/workflows/3-solutioning/tech-spec/checklist.md","07e61427814d7f97c86dc02f4c9caedbe725b2dd5b8876d5371371f872a81aed"
+"md","checklist","bmm","bmad/bmm/workflows/4-implementation/correct-course/checklist.md","d883f8c21b6315fe2296a5b250913adfbbf43d3387053e94f60051b5198989a3"
+"md","checklist","bmm","bmad/bmm/workflows/4-implementation/create-story/checklist.md","05a34bdba17b85b34402e5202f388534b7b277f9f81a87821a6e80d4f455ecf6"
+"md","checklist","bmm","bmad/bmm/workflows/4-implementation/dev-story/checklist.md","77cecc9d45050de194300c841e7d8a11f6376e2fbe0a5aac33bb2953b1026014"
+"md","checklist","bmm","bmad/bmm/workflows/4-implementation/review-story/checklist.md","549f958bfe0b28f33ed3dac7b76ea8f266630b3e67f4bda2d4ae85be518d3c89"
+"md","checklist","bmm","bmad/bmm/workflows/4-implementation/story-context/checklist.md","89c90d004e0649624a533d09604384c297b2891847c87cf1dcb358e9c8d0d723"
+"md","ci-burn-in","bmm","bmad/bmm/testarch/knowledge/ci-burn-in.md","42e14a03d84563ed9dffc618959b71fcfb35b6aef2e5e3a713335b96ad7709a5"
+"md","cli-questions","bmm","bmad/bmm/workflows/3-solutioning/project-types/cli-questions.md","f83b13181eb4b62085e3d8ffa046359f99d2631b6c2d6141da14e15d82d0b84d"
+"md","cli-tool-architecture","bmm","bmad/bmm/workflows/3-solutioning/templates/cli-tool-architecture.md","bb1688916680cfe3d723d6991d68bf288931dc27713b5f5f27ec08955a57ef4f"
+"md","component-tdd","bmm","bmad/bmm/testarch/knowledge/component-tdd.md","c2d1ea48b2d43abb0cee67b139827d3f9d8ea55203a7e6e9a9f87f0c9e717e2e"
+"md","contract-testing","bmm","bmad/bmm/testarch/knowledge/contract-testing.md","b0c4de2d61a9c278e82cac49d26b82019db1ae594615ebce4bf8d04657e9fc2d"
+"md","daily-standup","bmm","bmad/bmm/tasks/daily-standup.md","310b26505703cb2cdfc072bb3522f897480969e688acf443f5721c488fb1b731"
+"md","data-factories","bmm","bmad/bmm/testarch/knowledge/data-factories.md","714ab838ee4d409fd9dfe5189ccd4adb5aef12bdea7bc5ca8adb6c2a2bc84a98"
+"md","data-pipeline-architecture","bmm","bmad/bmm/workflows/3-solutioning/templates/data-pipeline-architecture.md","bb1688916680cfe3d723d6991d68bf288931dc27713b5f5f27ec08955a57ef4f"
+"md","data-questions","bmm","bmad/bmm/workflows/3-solutioning/project-types/data-questions.md","bf8c36fb0cf622d7f36c590056cfcbd8cf667450d00d4a27a81c6776210fa6cb"
+"md","desktop-app-architecture","bmm","bmad/bmm/workflows/3-solutioning/templates/desktop-app-architecture.md","bb1688916680cfe3d723d6991d68bf288931dc27713b5f5f27ec08955a57ef4f"
+"md","desktop-questions","bmm","bmad/bmm/workflows/3-solutioning/project-types/desktop-questions.md","f5a50f1169cef74f0c20aca0216615dfef173bd19fb47f64f9432be69f6271ec"
+"md","dev","bmm","bmad/bmm/agents/dev.md","4402d4cb6a6d2a5bad6ecc001197fabc77ccbcce451e5b5a48a3dc56125d4e67"
+"md","email-auth","bmm","bmad/bmm/testarch/knowledge/email-auth.md","7d0cc4d8e810f5f18d0654dc3f1ae306e73ef63b40a58a0f094c60b3a4cd309d"
+"md","embedded-firmware-architecture","bmm","bmad/bmm/workflows/3-solutioning/templates/embedded-firmware-architecture.md","bb1688916680cfe3d723d6991d68bf288931dc27713b5f5f27ec08955a57ef4f"
+"md","embedded-questions","bmm","bmad/bmm/workflows/3-solutioning/project-types/embedded-questions.md","fc9a01b298f59bb26aa22e64006f5c6ec8ac6eec327eec92114b7a7f8940a507"
+"md","epics-template","bmm","bmad/bmm/workflows/2-plan/prd/epics-template.md","93652c367a4138d94eebbea149c9cfc4d81cd08c8ea228ba57232275de2822be"
+"md","error-handling","bmm","bmad/bmm/testarch/knowledge/error-handling.md","d3301196502dc5b6ddae56a3fbdcfce04589c28890cf1ea7f70d2591e2cf2ff6"
+"md","extension-questions","bmm","bmad/bmm/workflows/3-solutioning/project-types/extension-questions.md","0c0cead79ad35d0d09b72f712b64f97a78838c9a4b58975d81c4ed3e755e6637"
+"md","feature-flags","bmm","bmad/bmm/testarch/knowledge/feature-flags.md","2d97b8939d573e62c045ee8aaa98aa2b6b2e027b878636e6615619864bcebf70"
+"md","fighting","bmm","bmad/bmm/workflows/2-plan/gdd/game-types/fighting.md","52e5a142aac496ae7154fc0829bfbce1ef22296f0a464cf8e595aa14ca02eb86"
+"md","fixture-architecture","bmm","bmad/bmm/testarch/knowledge/fixture-architecture.md","1d3f12a29a0c1fa3737bf7e85a99691b0b2543d3693024595569cc8aae4eae07"
+"md","game-architect","bmm","bmad/bmm/agents/game-architect.md","c2c11205f8c9577edaf0ac92520e0279808ac2f648797ef7294d61c0ecb86475"
+"md","game-context","bmm","bmad/bmm/workflows/1-analysis/brainstorm-game/game-context.md","d0f5cb4d6151bb65b799676281ea2af0fe1b5ec227c92ceba655ba363e18a0ba"
+"md","game-designer","bmm","bmad/bmm/agents/game-designer.md","ee538aa64aa3346e5e7588943dff74ff264e39d1445d78f95359120c0c280af6"
+"md","game-dev","bmm","bmad/bmm/agents/game-dev.md","0b4a374893e559c445f072d9b4537c57bfd347ed63abcf393bdbdd48075e4f00"
+"md","game-engine-architecture","bmm","bmad/bmm/workflows/3-solutioning/templates/game-engine-architecture.md","999e59b8c7196d731243565806ebcbea769fcac7d352ae31f16dedf5dc252ab4"
+"md","game-engine-godot-guide","bmm","bmad/bmm/workflows/3-solutioning/templates/game-engine-godot-guide.md","fb178ab700dab8ead1c00eb69f360d06982d7ac2aa5d333076ec07f279c2c459"
+"md","game-engine-unity-guide","bmm","bmad/bmm/workflows/3-solutioning/templates/game-engine-unity-guide.md","5a444408dac577a50bd443f3027cc362e402df42f8254b410d1b9d0ba4d8ed14"
+"md","game-engine-web-guide","bmm","bmad/bmm/workflows/3-solutioning/templates/game-engine-web-guide.md","6ba56a0d294d4798301af4a9126a69ed18e6c05899a9c4c6d518bba1de33801d"
+"md","game-questions","bmm","bmad/bmm/workflows/3-solutioning/project-types/game-questions.md","fff3446cbd0c821d5e7608e274f7653c87752f3644268475b16bae0fd35bf837"
+"md","gdd-template","bmm","bmad/bmm/workflows/2-plan/gdd/gdd-template.md","5a37c367bb2386b44587086b463d92e73e7a63a37abc772ba96617402a698cd3"
+"md","horror","bmm","bmad/bmm/workflows/2-plan/gdd/game-types/horror.md","7ff7599d5701bb7a8ef0e14f3ba614626cdd0d8960a8e880fc1cd41c5f508f75"
+"md","idle-incremental","bmm","bmad/bmm/workflows/2-plan/gdd/game-types/idle-incremental.md","515b52bb301e467c1f096cc55abde47159bb0b0d87157b9fa565973b48601ddf"
+"md","infra-questions","bmm","bmad/bmm/workflows/3-solutioning/project-types/infra-questions.md","8c9522d5ac3077f898ffe22e861a9688099751f312e8539bf154853d3fcb4d99"
+"md","infrastructure-architecture","bmm","bmad/bmm/workflows/3-solutioning/templates/infrastructure-architecture.md","bb1688916680cfe3d723d6991d68bf288931dc27713b5f5f27ec08955a57ef4f"
+"md","instructions","bmm","bmad/bmm/workflows/1-analysis/brainstorm-game/instructions.md","f6573b528b179e9f848655d677556b8c0ddc59e0db5bcc85b971fb86bf00656b"
+"md","instructions","bmm","bmad/bmm/workflows/1-analysis/brainstorm-project/instructions.md","6d64e2aba3e06314abf19cdc6433e3e08449cb48fc7d07f0b291610e2d974442"
+"md","instructions","bmm","bmad/bmm/workflows/1-analysis/game-brief/instructions.md","db19699dad40f80a1e108954bf05af21b8f09fc4a20997f1bc4e6ada4fc5a22f"
+"md","instructions","bmm","bmad/bmm/workflows/1-analysis/product-brief/instructions.md","b5adea3e658410faad8c2d0648c0231c014df4f0430a93658af52022e0f2378a"
+"md","instructions","bmm","bmad/bmm/workflows/3-solutioning/instructions.md","6fd1939004b18954d1ed5ed4bacfdda35fee1f1387783d9fb0142e37c2c02803"
+"md","instructions","bmm","bmad/bmm/workflows/3-solutioning/tech-spec/instructions.md","842387402996497f3000a37bbba0ae7e2e07a2a6f6824619cd6599346a9265d5"
+"md","instructions","bmm","bmad/bmm/workflows/4-implementation/correct-course/instructions.md","f0a751f4138c56cfc066487c31963b02394358f5842dbe6c377cf1330a8b1ed8"
+"md","instructions","bmm","bmad/bmm/workflows/4-implementation/create-story/instructions.md","07510910407ca9fe08797d138d79089620c9f809473ca6a6c55b68a5ebd9ca5f"
+"md","instructions","bmm","bmad/bmm/workflows/4-implementation/dev-story/instructions.md","6b922f9697f651583cc011a60db082673561b7375196d1ef616a629e176292a5"
+"md","instructions","bmm","bmad/bmm/workflows/4-implementation/retrospective/instructions.md","748403464988118ca4531192669bd32d9e9fa89c82d824b40c00cc98a09535c4"
+"md","instructions","bmm","bmad/bmm/workflows/4-implementation/review-story/instructions.md","f5292cc98476c3aa15ba0ff9ca571e56e1e05ed0f846a131e1083aa237be2e33"
+"md","instructions","bmm","bmad/bmm/workflows/4-implementation/story-context/instructions.md","38d244cbe0435dd94b215b5ad29b0fcf10a8298a69eef2f61e2c61c1f6a72f21"
+"md","instructions","bmm","bmad/bmm/workflows/testarch/atdd/instructions.md","946b00119290758ab2900498f19ae3514e0d291eb65099c47ddbd793306d8e31"
+"md","instructions","bmm","bmad/bmm/workflows/testarch/automate/instructions.md","b74121f6bc87ae73c8b7b8b2bc4257801262cb8924239ebe9a4e3228d042ac1d"
+"md","instructions","bmm","bmad/bmm/workflows/testarch/ci/instructions.md","d2a8d515af18767d211909d91691ff41c6baa572d06f6778592b08b3fbd54148"
+"md","instructions","bmm","bmad/bmm/workflows/testarch/framework/instructions.md","7065d32554f138f5af848759c96e55aca921fd5839f5dad593849e358132f002"
+"md","instructions","bmm","bmad/bmm/workflows/testarch/gate/instructions.md","ea0f9bc1c67f2a1089f3d6937e851b8b74c0dde7d65f649f9301b0effd99b95d"
+"md","instructions","bmm","bmad/bmm/workflows/testarch/nfr-assess/instructions.md","fbb0b3c5ad8210f522858e2daf872f2b050db898c4bb090056bf42980046d54b"
+"md","instructions","bmm","bmad/bmm/workflows/testarch/test-design/instructions.md","293a06ff2ce67485d5acb8d262c0f8dff3b98c15af1848b4219bf14eaa7ea03a"
+"md","instructions","bmm","bmad/bmm/workflows/testarch/trace/instructions.md","2861e1981f42bb0db09fa79ce2954836f5844ec8744ea2d33d3f05d3543963b2"
+"md","instructions-deep-prompt","bmm","bmad/bmm/workflows/1-analysis/research/instructions-deep-prompt.md","ab168ee82ed5cc7a0d4a800cffe59ab2539c748e09aaf1a8a8fcff9edb0cc5c3"
+"md","instructions-gdd","bmm","bmad/bmm/workflows/2-plan/gdd/instructions-gdd.md","335d5b8b3947febcf9407671147f66d20dcc39c1961b934b85bdafd9c26ebc46"
+"md","instructions-lg","bmm","bmad/bmm/workflows/2-plan/prd/instructions-lg.md","8cda2f0bb420c7e1ef06bbabb86c9aece07a48fee6c5835a26d834afa8574129"
+"md","instructions-market","bmm","bmad/bmm/workflows/1-analysis/research/instructions-market.md","fd2ee878b13975f12393752aab9fb7b72eaec17b56b7c3b7edb93ef9d9146214"
+"md","instructions-med","bmm","bmad/bmm/workflows/2-plan/prd/instructions-med.md","3deeed928b497f91db79c5b49e70b647959e48f1e9d5a484a20f3b98ec7e7706"
+"md","instructions-narrative","bmm","bmad/bmm/workflows/2-plan/narrative/instructions-narrative.md","ee57ee3c6360d3cfa814405bf10195cf6dd4fea7973e18b087ec0bb4fdb99c63"
+"md","instructions-router","bmm","bmad/bmm/workflows/1-analysis/research/instructions-router.md","761d0b71bc7d4508b54cfbd89fe7654badad34cf329a0eab2d4b88b13bb9835c"
+"md","instructions-router","bmm","bmad/bmm/workflows/2-plan/instructions-router.md","784e0366c179b9ef35bb01aeba1e8b6b68bd64c64b0ceeb12201042f69ccfc3b"
+"md","instructions-sm","bmm","bmad/bmm/workflows/2-plan/tech-spec/instructions-sm.md","0dd9fbdd2a96482798f9db8c851d42ddbea021eac0b1bb8130f3986a987e51c2"
+"md","instructions-technical","bmm","bmad/bmm/workflows/1-analysis/research/instructions-technical.md","1a67b55ac8a7ad251b86b9b4e7fc16afdff1d10816f2d980f3d95408f4d538a9"
+"md","instructions-ux","bmm","bmad/bmm/workflows/2-plan/ux/instructions-ux.md","5c97779f0dc7c2853da25821b5b28b08494152bd8519e0741a6e61a75a3d62ee"
+"md","library-package-architecture","bmm","bmad/bmm/workflows/3-solutioning/templates/library-package-architecture.md","bb1688916680cfe3d723d6991d68bf288931dc27713b5f5f27ec08955a57ef4f"
+"md","library-questions","bmm","bmad/bmm/workflows/3-solutioning/project-types/library-questions.md","1a21b0345744a108590f293a492345bb6370af561a7875985f6307816df178ae"
+"md","metroidvania","bmm","bmad/bmm/workflows/2-plan/gdd/game-types/metroidvania.md","2a8c101dda7911d1cd1d9c66d1be86af3725832f5dcc7fab71e95204f45614ea"
+"md","moba","bmm","bmad/bmm/workflows/2-plan/gdd/game-types/moba.md","92d0ba9f7508a38d5bfeac1651c6aee8a1a58c54659ad3f0e0d1fd678a1ef498"
+"md","mobile-app-architecture","bmm","bmad/bmm/workflows/3-solutioning/templates/mobile-app-architecture.md","bb1688916680cfe3d723d6991d68bf288931dc27713b5f5f27ec08955a57ef4f"
+"md","mobile-questions","bmm","bmad/bmm/workflows/3-solutioning/project-types/mobile-questions.md","5b44cf9cac7d035ec754e335be8ba78046f70934825d074c474be29938075440"
+"md","narrative-template","bmm","bmad/bmm/workflows/2-plan/narrative/narrative-template.md","a97e07173c540f85e946eb9c525e1ccad9294ae5f970760f2a9c537b5c0dcd6b"
+"md","network-first","bmm","bmad/bmm/testarch/knowledge/network-first.md","555dbb40e8e3e17d09e1bf3532d46c28a13fc5c868942b04f27937bcb6365ee8"
+"md","nfr-criteria","bmm","bmad/bmm/testarch/knowledge/nfr-criteria.md","384beb17c8d127cc0a26ddf55a71a4c75c770517b1454ee3177500a93d7b558e"
+"md","party-game","bmm","bmad/bmm/workflows/2-plan/gdd/game-types/party-game.md","0cc50b3aede0c45c94cdff743cdac2d8ad67421ea80497a29d2300a1744ea703"
+"md","playwright-config","bmm","bmad/bmm/testarch/knowledge/playwright-config.md","6583c48c974f1be27bd0ac4f33c19de96f3714fa86a3b5e39cfcaa7adb90614c"
+"md","pm","bmm","bmad/bmm/agents/pm.md","4a057aac4080e30b922436cbf752d746c6a8e675e093d94703611a4706812133"
+"md","po","bmm","bmad/bmm/agents/po.md","31a546b45e0064468d3348a8d34cf4d76e485e1382ded1a0063e96045cf839b6"
+"md","prd-template","bmm","bmad/bmm/workflows/2-plan/prd/prd-template.md","db91b88f1457b95b6e44b8eeaf57b54b075f3300cb7d71294d12848d5c4beef6"
+"md","probability-impact","bmm","bmad/bmm/testarch/knowledge/probability-impact.md","6786eb7162bddaa0b8b66d612082de1c2837e5740776436cc3e973fb7f972a65"
+"md","project-context","bmm","bmad/bmm/workflows/1-analysis/brainstorm-project/project-context.md","0f1888da4bfc4f24c4de9477bd3ccb2a6fb7aa83c516dfdc1f98fbd08846d4ba"
+"md","puzzle","bmm","bmad/bmm/workflows/2-plan/gdd/game-types/puzzle.md","f9c08b6f087bfaa41ea08c9dfa78aa034f5ae46b627b9f476bdf8b4f5c3389ed"
+"md","racing","bmm","bmad/bmm/workflows/2-plan/gdd/game-types/racing.md","085ea5d0914d7bc6a233c479d0ad6288a575ad1c8b9a8a85881e779fac0e60fc"
+"md","README","bmm","bmad/bmm/testarch/README.md","9adbee749e3b311d14ff7e317d690ff857eeb40bb4bb6465e2de16077eb68c9d"
+"md","README","bmm","bmad/bmm/workflows/1-analysis/game-brief/README.md","cc922fd97a0fb4aab624e35e24ada783fdbd4b057b8a8e2f8c550087f1725596"
+"md","README","bmm","bmad/bmm/workflows/1-analysis/product-brief/README.md","e891a719ac22e5cd754b55efc7b2f367094c8fa00e802139b3cb1f9fabf1c559"
+"md","README","bmm","bmad/bmm/workflows/1-analysis/research/README.md","e365d495308a23d6163f3353c4efa254ecaef0ef9ecf7427398509de751ca207"
+"md","README","bmm","bmad/bmm/workflows/2-plan/README.md","5a648eff915bb554e9b323cab78d21061ed97345488e6855563e113e063764f6"
+"md","README","bmm","bmad/bmm/workflows/2-plan/gdd/README.md","2dfdc93ab6c9c5982c3a79bb184cd468fd59a44565ad23188a4a1a8f32208588"
+"md","README","bmm","bmad/bmm/workflows/3-solutioning/README.md","535dfb7874538a6c6184cc57f3b5f8d5ef49388f8125255fd5fcaec34418ec64"
+"md","README","bmm","bmad/bmm/workflows/3-solutioning/tech-spec/README.md","c9cdbdd691fcf63e4ed38e4a2998739c07ce57d63b5464da4545835fe030812d"
+"md","README","bmm","bmad/bmm/workflows/4-implementation/create-story/README.md","d5a28a9f63b6c37ab1ee2065ad04b60b838a8f276d94d0b72b3cc43fac59f425"
+"md","README","bmm","bmad/bmm/workflows/4-implementation/dev-story/README.md","f104aacf35b9192e0be9d1d994052a4bded2a159f3cd42b7fa630ab9d26bdf03"
+"md","README","bmm","bmad/bmm/workflows/4-implementation/review-story/README.md","bf8aacb0692173df34923cb643372403a7c1cd83d1457c68fa6c38f2c5e18207"
+"md","README","bmm","bmad/bmm/workflows/4-implementation/story-context/README.md","aadd2d77c2c254a358a0b91f4db48a1ad69815226120fab74ebc40bc209f8246"
+"md","README","bmm","bmad/bmm/workflows/testarch/README.md","d148c9ec9430f492c81d8e91fd4a2fab144a9ce80583dfdaa8acd120b572a735"
+"md","retrospective","bmm","bmad/bmm/tasks/retrospective.md","0430328d27ee84c49841a8362a74714acbcbb82e6e14c256c3a7ee4eaa1b37e8"
+"md","rhythm","bmm","bmad/bmm/workflows/2-plan/gdd/game-types/rhythm.md","83bbf1761fdc604b8c2b50ed86c5874cce331417e1b3a46c65cb6c4c1a7c8db2"
+"md","risk-governance","bmm","bmad/bmm/testarch/knowledge/risk-governance.md","2642089dddb690f71008c7986f770bf486e711e820d36226df721d356045b4f9"
+"md","roguelike","bmm","bmad/bmm/workflows/2-plan/gdd/game-types/roguelike.md","fb1ebc838011020a6f740e6fb4f2ceb81be8477f9c67bc7ae3a8e34dfe548f00"
+"md","rpg","bmm","bmad/bmm/workflows/2-plan/gdd/game-types/rpg.md","5aa57ecefb448a0507ee0c8d503b43bd34d0c612ba130240d1af9842b80cba50"
+"md","sandbox","bmm","bmad/bmm/workflows/2-plan/gdd/game-types/sandbox.md","836f656bbaae549f31ac574c0865a61de451c08ab8c561db2c93398e147ece85"
+"md","selective-testing","bmm","bmad/bmm/testarch/knowledge/selective-testing.md","e669fb7a5e897efefa582f96807800625bea5cb73bfab9eadf564a8477d77f2a"
+"md","shooter","bmm","bmad/bmm/workflows/2-plan/gdd/game-types/shooter.md","2452850295ac2b9fac04ce2d6126bfc19bb7dccbb04c40e7f89c801aecc5555d"
+"md","simulation","bmm","bmad/bmm/workflows/2-plan/gdd/game-types/simulation.md","fd74a7d21243f8d9827fe6a99263579309bc0aabd9e56261d3dd4eb5cfc75ad5"
+"md","sm","bmm","bmad/bmm/agents/sm.md","acbc18b5444711b849fc4c74e8916cd7cef33c10bc5c4b4fd0cc3b3dd9dec791"
+"md","sports","bmm","bmad/bmm/workflows/2-plan/gdd/game-types/sports.md","2247ea87dbca74e879f8c686d9e80434618e9e61bd3572739274c1af64cb0bb8"
+"md","strategy","bmm","bmad/bmm/workflows/2-plan/gdd/game-types/strategy.md","997380919f6c1b408906c364f74e728b9c6b45bf2960d1f0bfe8b0def594735e"
+"md","survival","bmm","bmad/bmm/workflows/2-plan/gdd/game-types/survival.md","3647795ee0073a85217633412a41a938e51a553776acbe9ac953fb403e3437f9"
+"md","tea","bmm","bmad/bmm/agents/tea.md","b3c22da5b55c3c2c4912bc04c2b605c6b5cf992e1ad31464d33352eb8e473fd2"
+"md","tech-spec-template","bmm","bmad/bmm/workflows/2-plan/tech-spec/tech-spec-template.md","79e0b33c3e191603160bf2e6f11497ff3be010878cd1008dc986e2b957a9230c"
+"md","template","bmm","bmad/bmm/workflows/1-analysis/game-brief/template.md","6d5555fae3763e8528898663d51276e0cc7d2d9725a8c74162d8e9732dbc5843"
+"md","template","bmm","bmad/bmm/workflows/1-analysis/product-brief/template.md","6e80489578bf0908c70742b36997007ea3978bcd14af7ee6b1dca5d54679090e"
+"md","template","bmm","bmad/bmm/workflows/3-solutioning/tech-spec/template.md","f27cf5523b383afa33918f02d2ecf37bd2fb514e3eff3a6b423684667d8678f0"
+"md","template","bmm","bmad/bmm/workflows/4-implementation/create-story/template.md","4b94d18a0ab63c729e62428a462eaa3ac72e5152647e4f99758ee2223ea7ccea"
+"md","template-deep-prompt","bmm","bmad/bmm/workflows/1-analysis/research/template-deep-prompt.md","2e65c7d6c56e0fa3c994e9eb8e6685409d84bc3e4d198ea462fa78e06c1c0932"
+"md","template-market","bmm","bmad/bmm/workflows/1-analysis/research/template-market.md","28631d8693beac54f4b47f38b143d5efc91f8ed7673e396a7b40304db7eba6cb"
+"md","template-technical","bmm","bmad/bmm/workflows/1-analysis/research/template-technical.md","6f571c638c9d2f12ded2cf82ed7c5064a25e99f197fcd42dc558cb45e7ebaf93"
+"md","test-levels-framework","bmm","bmad/bmm/testarch/knowledge/test-levels-framework.md","85feecbee24c2e2efa7e3a7c5b455eddfad2f262ffe3ee84b7759c45576b3f10"
+"md","test-priorities-matrix","bmm","bmad/bmm/testarch/knowledge/test-priorities-matrix.md","b18dfbb0d81112d1333ad5abe29ef719b72906d013679347c9e019fef33958fe"
+"md","test-quality","bmm","bmad/bmm/testarch/knowledge/test-quality.md","314e926651965c9bd535b41d17bb378232b23c08d13b997d947331f2f073b504"
+"md","text-based","bmm","bmad/bmm/workflows/2-plan/gdd/game-types/text-based.md","5895ca65dc93f676bb33b754f2c6be85d5d9b651df87d8431d404dc9bb736ee7"
+"md","tower-defense","bmm","bmad/bmm/workflows/2-plan/gdd/game-types/tower-defense.md","03a2cc577fdd1a183ba04409b01b22f2f38713d28f1278481b0f221858f97ec8"
+"md","turn-based-tactics","bmm","bmad/bmm/workflows/2-plan/gdd/game-types/turn-based-tactics.md","30a150d8a0ab746f0c67d414be79e7e421fff1b8b7a1b716e64800df72bdb6c2"
+"md","ux-expert","bmm","bmad/bmm/agents/ux-expert.md","661ce176a73aa84bfffdd4f7333b7965ae45df13c12ce48062a41182430b5cd6"
+"md","ux-spec-template","bmm","bmad/bmm/workflows/2-plan/ux/ux-spec-template.md","b04fa73b5cc1c835f0ddd7a8699b458b8631ecd4add2fb0be4f47b8ba5bfd54e"
+"md","visual-debugging","bmm","bmad/bmm/testarch/knowledge/visual-debugging.md","8c0c625f73761c318fc05cdbc57f4ed21a871d9fe2df2ffba91f8ec7c9835032"
+"md","visual-novel","bmm","bmad/bmm/workflows/2-plan/gdd/game-types/visual-novel.md","2d98f4c682f0abbd6330ac1bad04600c596e6b27302adbe9510fc0c0bf53052c"
+"md","web-api-architecture","bmm","bmad/bmm/workflows/3-solutioning/templates/web-api-architecture.md","bb1688916680cfe3d723d6991d68bf288931dc27713b5f5f27ec08955a57ef4f"
+"md","web-fullstack-architecture","bmm","bmad/bmm/workflows/3-solutioning/templates/web-fullstack-architecture.md","48f17f9a8063af9bc123967abb143c45a69c1742e8573807948768733cd680d3"
+"md","web-questions","bmm","bmad/bmm/workflows/3-solutioning/project-types/web-questions.md","0f214e0a4a9e81eb9994a3f1d82ef2c5358e97baa2ca6320ba0a7a73747fa4aa"
+"xml","context-template","bmm","bmad/bmm/workflows/4-implementation/story-context/context-template.xml","6b88d07ff10f51bb847d70e02f22d8927beb6ef1e55d5acf647e8f23b5821921"
+"yaml","config","bmm","bmad/bmm/config.yaml","7df29954ad4c9be04e02b2339f7c30fb65e7f0359f1ec2edd3a2b844d142f717"
+"yaml","injections","bmm","bmad/bmm/workflows/1-analysis/research/claude-code/injections.yaml","dd6dd6e722bf661c3c51d25cc97a1e8ca9c21d517ec0372e469364ba2cf1fa8b"
+"yaml","team-all","bmm","bmad/bmm/teams/team-all.yaml","65e3087d727efdec02565758c1bd07e13e7dff0e102847d4dd65e0e77a88debc"
+"yaml","team-dev","bmm","bmad/bmm/teams/team-dev.yaml","55548a4b7b92d3b5185e40e82e71f2e1d8c047512bbdbd1ed181ec69d0ea5ec1"
+"yaml","team-gamedev","bmm","bmad/bmm/teams/team-gamedev.yaml","74f8951a5e57ff1687ec5f79c8f58e8d78d55a80bdd96d8b825f1f321c39ba25"
+"yaml","workflow","bmm","bmad/bmm/workflows/1-analysis/brainstorm-game/workflow.yaml","721501249e14a8860224514ab071b7fd304320dd735e56f248bb0f06f26d466b"
+"yaml","workflow","bmm","bmad/bmm/workflows/1-analysis/brainstorm-project/workflow.yaml","e8c1c6853d43901e4dc970189aef27495cfe9a366759350d161a34fa38fee785"
+"yaml","workflow","bmm","bmad/bmm/workflows/1-analysis/game-brief/workflow.yaml","b3d3f58c4119ed0db6c4d24bc5be30489057504b023f42fcb168e3d93be52357"
+"yaml","workflow","bmm","bmad/bmm/workflows/1-analysis/product-brief/workflow.yaml","0a95dea856d0b8142815d229fcdff5a98d2e946888c64b262124f6afa906425e"
+"yaml","workflow","bmm","bmad/bmm/workflows/1-analysis/research/workflow.yaml","60477226a00e4b865a6f0980018bacd30372a79715e9de3c2daee3456a8eac6b"
+"yaml","workflow","bmm","bmad/bmm/workflows/2-plan/workflow.yaml","a3f5846a556a49477b1b14ce7667bf235a211c8c305d3f6e4979adce6c2b6fee"
+"yaml","workflow","bmm","bmad/bmm/workflows/3-solutioning/tech-spec/workflow.yaml","e965596daac7d0232751301af91b3d15d8e828f9104c5b2bfc79ec362112f733"
+"yaml","workflow","bmm","bmad/bmm/workflows/3-solutioning/workflow.yaml","6c703cf15b931a96ba563e5d06b96b629ade0e890e7d6c792ec404cceff92fb8"
+"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml","e22bce828e334a2bb37379162c1706a8dd09d9bf73d1e0315b20fb4cfa173d25"
+"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/create-story/workflow.yaml","b03ea6114392d28adb7915354f41401818e54f5ff24a1938813f04d41740b233"
+"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml","c99b6cb5b984998d07295af636af37dd3a8cba3e07376de2e4b448294cd80f39"
+"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml","a61ceccede31fbb12fed83c1d70f89d9ee376f84c0a5dbc18a5570c420e1c27f"
+"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/review-story/workflow.yaml","9141ed4d53b7de733faf82541427c5ca83e86a26d61546a1b2952051d9b1f081"
+"yaml","workflow","bmm","bmad/bmm/workflows/4-implementation/story-context/workflow.yaml","130817c35bb68ea698a8100c80238471a505deb89882b9e09a58058667c93dbe"
+"yaml","workflow","bmm","bmad/bmm/workflows/testarch/atdd/workflow.yaml","c1c0206042dc9b96b4a717b5187a4cf5c0254256625ff7b88c0c32094c419d4d"
+"yaml","workflow","bmm","bmad/bmm/workflows/testarch/automate/workflow.yaml","d4f0ae9520e8515ce1cef5372993ad721cf3389167815f00a8fbd93d5fc4d9de"
+"yaml","workflow","bmm","bmad/bmm/workflows/testarch/ci/workflow.yaml","303c2cae23251d7ebb400987dbaf422cb6aebe6b77cb886aafb0ac2eb9dbe2ac"
+"yaml","workflow","bmm","bmad/bmm/workflows/testarch/framework/workflow.yaml","328d7e7e0edbbaff18761e1fe0e753f985b25028611f363ae84d09115160620f"
+"yaml","workflow","bmm","bmad/bmm/workflows/testarch/gate/workflow.yaml","86eb4a240f10adad14ee211e2be1ca89bf31a41b9f5a8e7bb0719caf32405912"
+"yaml","workflow","bmm","bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml","9372ffd0c107bebc58cd93fb9bf8e7d0e4cdb5e55eabebaf6a7a821cc946c7e1"
+"yaml","workflow","bmm","bmad/bmm/workflows/testarch/test-design/workflow.yaml","08fe57d8bf91c6866699bce92ea05b1e694aa72fde2a3b530833a1556e2fef1a"
+"yaml","workflow","bmm","bmad/bmm/workflows/testarch/trace/workflow.yaml","0b841730236e0e0a140dfd99a82ab66cec26930f07fe3bb9154cc02e8bb9d29d"
+"csv","adv-elicit-methods","core","bmad/core/tasks/adv-elicit-methods.csv","b4e925870f902862899f12934e617c3b4fe002d1b652c99922b30fa93482533b"
+"md","adv-elicit","core","bmad/core/tasks/adv-elicit.md","97c231eb1b5370dd0d1501e3f70807ddcd6b9f8acfef9c19106c3f8c3adc2335"
+"md","bmad-master","core","bmad/core/agents/bmad-master.md","00e4dfbb45fa4cc9d49e3f946e0f450306d958ef30698b4c662d8dce3947d8a3"
+"md","index-docs","core","bmad/core/tasks/index-docs.md","e05a37b2af9479eb148ff5514b37a179d51b08d377b3016713155c3a2b6de888"
+"md","instructions","core","bmad/core/workflows/bmad-init/instructions.md","f4eff0e5f8c060126cb3027e3b0a343451ff25cd8fac28551e70281c3b16a5b2"
+"md","instructions","core","bmad/core/workflows/party-mode/instructions.md","7ad1d60c4cd53c0337d84bca99f59d6ba2730e1d00c96a86d6f99b79e352ba7f"
+"md","shard-doc","core","bmad/core/tasks/shard-doc.md","ad25345eaccf8ea8818c2dda4eb3ad5f75a45e9303f62d43c78cc78eb3e0f689"
+"md","validate-workflow","core","bmad/core/tasks/validate-workflow.md","234ec85604f5610c308980e8f5d538a60fff315190d8ab02660a79d5dd5e1b00"
+"md","workflow","core","bmad/core/tasks/workflow.md","137ee1bb408fe73e472bfcc4060e2c883b9cb345146ab2091ee01279d84b1ad6"
+"yaml","config","core","bmad/core/config.yaml","ab1dfb316d97627c11302d9f2e0fc18650bd4b43846b41cc3d74e0c6bf6cac9a"
+"yaml","workflow","core","bmad/core/workflows/bmad-init/workflow.yaml","ec0b25447d888267f37195cb12e8f2d3eedc42193b04e2ea1e906766b58b7f78"
+"yaml","workflow","core","bmad/core/workflows/party-mode/workflow.yaml","ad3962ccfb35860b239fc67f6fadfdb6bb287ae29e859e572575b7fcc2b12e37"

bmad/_cfg/manifest.csv

@@ -0,0 +1,18 @@
+# BMAD Manifest
+# Generated: 2025-10-01T22:12:35.042Z
+
+## Installation Info
+Property,Value
+Version,6.0.0-alpha.0
+InstallDate,2025-10-01T22:12:35.042Z
+LastUpdated,2025-10-01T22:12:35.042Z
+
+## Modules
+Name,Version,ShortTitle
+core,,
+bmb,,
+bmm,,
+
+## IDEs
+IDE
+claude-code

bmad/_cfg/manifest.yaml

@@ -0,0 +1,16 @@
+installation:
+  version: 6.0.0-alpha.0
+  installDate: "2025-10-01T22:12:35.001Z"
+  lastUpdated: "2025-10-01T22:12:35.001Z"
+modules:
+  - name: core
+    version: ""
+    shortTitle: ""
+  - name: bmb
+    version: ""
+    shortTitle: ""
+  - name: bmm
+    version: ""
+    shortTitle: ""
+ides:
+  - claude-code

bmad/_cfg/task-manifest.csv

@@ -0,0 +1,8 @@
+name,displayName,description,module,path
+"adv-elicit","Advanced Elicitation","","core","bmad/core/tasks/adv-elicit.md"
+"index-docs","Index Docs","","core","bmad/core/tasks/index-docs.md"
+"shard-doc","Shard Doc","","core","bmad/core/tasks/shard-doc.md"
+"validate-workflow","Validate Workflow Output","Run a checklist against a document with thorough analysis and produce a validation report","core","bmad/core/tasks/validate-workflow.md"
+"workflow","Execute Workflow","Execute given workflow by loading its configuration, following instructions, and producing output","core","bmad/core/tasks/workflow.md"
+"daily-standup","Daily Standup","","bmm","bmad/bmm/tasks/daily-standup.md"
+"retrospective","Team Retrospective","","bmm","bmad/bmm/tasks/retrospective.md"

bmad/_cfg/workflow-manifest.csv

@@ -0,0 +1,32 @@
+name,description,module,path
+"bmad-init","BMAD system initialization and maintenance workflow for agent manifest generation and system configuration","core","bmad/core/workflows/bmad-init/workflow.yaml"
+"party-mode","Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations","core","bmad/core/workflows/party-mode/workflow.yaml"
+"convert-legacy","Converts legacy BMAD v4 or similar items (agents, workflows, modules) to BMad Core compliant format with proper structure and conventions","bmb","bmad/bmb/workflows/convert-legacy/workflow.yaml"
+"create-agent","Interactive workflow to build BMAD Core compliant agents (simple, expert, or module types) with optional brainstorming for agent ideas, proper persona development, activation rules, and command structure","bmb","bmad/bmb/workflows/create-agent/workflow.yaml"
+"create-module","Interactive workflow to build complete BMAD modules with agents, workflows, tasks, and installation infrastructure","bmb","bmad/bmb/workflows/create-module/workflow.yaml"
+"create-workflow","Interactive workflow builder that guides creation of new BMAD workflows with proper structure and validation for optimal human-AI collaboration. Includes optional brainstorming phase for workflow ideas and design.","bmb","bmad/bmb/workflows/create-workflow/workflow.yaml"
+"edit-workflow","Edit existing BMAD workflows while following all best practices and conventions","bmb","bmad/bmb/workflows/edit-workflow/workflow.yaml"
+"module-brief","Create a comprehensive Module Brief that serves as the blueprint for building new BMAD modules using strategic analysis and creative vision","bmb","bmad/bmb/workflows/module-brief/workflow.yaml"
+"redoc","Autonomous documentation system that maintains module, workflow, and agent documentation using a reverse-tree approach (leaf folders first, then parents). Understands BMAD conventions and produces technical writer quality output.","bmb","bmad/bmb/workflows/redoc/workflow.yaml"
+"brainstorm-game","Facilitate game brainstorming sessions by orchestrating the CIS brainstorming workflow with game-specific context, guidance, and additional game design techniques.","bmm","bmad/bmm/workflows/1-analysis/brainstorm-game/workflow.yaml"
+"brainstorm-project","Facilitate project brainstorming sessions by orchestrating the CIS brainstorming workflow with project-specific context and guidance.","bmm","bmad/bmm/workflows/1-analysis/brainstorm-project/workflow.yaml"
+"game-brief","Interactive game brief creation workflow that guides users through defining their game vision with multiple input sources and conversational collaboration","bmm","bmad/bmm/workflows/1-analysis/game-brief/workflow.yaml"
+"product-brief","Interactive product brief creation workflow that guides users through defining their product vision with multiple input sources and conversational collaboration","bmm","bmad/bmm/workflows/1-analysis/product-brief/workflow.yaml"
+"research","Adaptive research workflow supporting multiple research types: market research, deep research prompt generation, technical/architecture evaluation, competitive intelligence, user research, and domain analysis","bmm","bmad/bmm/workflows/1-analysis/research/workflow.yaml"
+"plan-project","Scale-adaptive project planning workflow for all project levels (0-4). Automatically adjusts outputs based on project scope - from single atomic changes (Level 0: tech-spec only) to enterprise platforms (Level 4: full PRD + epics). Level 2-4 route to 3-solutioning workflow for architecture and tech specs. Generates appropriate planning artifacts for each level.","bmm","bmad/bmm/workflows/2-plan/workflow.yaml"
+"tech-spec","Generate a comprehensive Technical Specification from PRD and Architecture with acceptance criteria and traceability mapping","bmm","bmad/bmm/workflows/3-solutioning/tech-spec/workflow.yaml"
+"solution-architecture","Scale-adaptive solution architecture generation with dynamic template sections. Replaces legacy HLA workflow with modern BMAD Core compliance.","bmm","bmad/bmm/workflows/3-solutioning/workflow.yaml"
+"correct-course","Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation","bmm","bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml"
+"create-story","Create the next user story markdown from epics/PRD and architecture, using a standard template and saving to the stories folder","bmm","bmad/bmm/workflows/4-implementation/create-story/workflow.yaml"
+"dev-story","Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria","bmm","bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml"
+"retrospective","Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic","bmm","bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml"
+"review-story","Perform a Senior Developer Review on a completed story flagged Ready for Review, leveraging story-context, epic tech-spec, repo docs, MCP servers for latest best-practices, and web search as fallback. Appends structured review notes to the story.","bmm","bmad/bmm/workflows/4-implementation/review-story/workflow.yaml"
+"story-context","Assemble a dynamic Story Context XML by pulling latest documentation and existing code/library artifacts relevant to a drafted story","bmm","bmad/bmm/workflows/4-implementation/story-context/workflow.yaml"
+"testarch-atdd","Generate failing acceptance tests before implementation.","bmm","bmad/bmm/workflows/testarch/atdd/workflow.yaml"
+"testarch-automate","Expand automation coverage after implementation.","bmm","bmad/bmm/workflows/testarch/automate/workflow.yaml"
+"testarch-ci","Scaffold or update the CI/CD quality pipeline.","bmm","bmad/bmm/workflows/testarch/ci/workflow.yaml"
+"testarch-framework","Initialize or refresh the test framework harness.","bmm","bmad/bmm/workflows/testarch/framework/workflow.yaml"
+"testarch-gate","Record the quality gate decision for the story.","bmm","bmad/bmm/workflows/testarch/gate/workflow.yaml"
+"testarch-nfr","Assess non-functional requirements before release.","bmm","bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml"
+"testarch-plan","Plan risk mitigation and test coverage before development.","bmm","bmad/bmm/workflows/testarch/test-design/workflow.yaml"
+"testarch-trace","Trace requirements to implemented automated tests.","bmm","bmad/bmm/workflows/testarch/trace/workflow.yaml"

bmad/bmb/agents/bmad-builder.md

@@ -0,0 +1,82 @@
+<!-- Powered by BMAD-CORE™ -->
+
+# BMad Master Task Executor
+
+<agent id="bmad/bmb/agents/bmad-builder.md" name="BMad Builder" title="BMad Builder" icon="🧙">
+  <activation critical="MANDATORY">
+    <init>
+      <step n="1">Load persona from this current file containing this activation you are reading now</step>
+      <step n="2">Override with {project-root}/bmad/_cfg/agents/{agent-filename} if exists (replace, not merge)</step>
+      <step n="3">Execute critical-actions section if present in current agent XML</step>
+      <step n="4">Show greeting + numbered list of ALL commands IN ORDER from current agent's cmds section</step>
+      <step n="5">CRITICAL HALT. AWAIT user input. NEVER continue without it.</step>
+    </init>
+    <commands critical="MANDATORY">
+      <input>Number → cmd[n] | Text → fuzzy match *commands</input>
+      <extract>exec, tmpl, data, action, run-workflow, validate-workflow</extract>
+      <handlers>
+        <handler type="run-workflow">
+          When command has: run-workflow="path/to/x.yaml" You MUST:
+          1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.md
+          2. READ its entire contents - the is the CORE OS for EXECUTING modules
+          3. Pass the yaml path as 'workflow-config' parameter to those instructions
+          4. Follow workflow.md instructions EXACTLY as written
+          5. Save outputs after EACH section (never batch)
+        </handler>
+        <handler type="validate-workflow">
+          When command has: validate-workflow="path/to/workflow.yaml" You MUST:
+          1. You MUST LOAD the file at: {project-root}/bmad/core/tasks/validate-workflow.md
+          2. READ its entire contents and EXECUTE all instructions in that file
+          3. Pass the workflow, and also check the workflow location for a checklist.md to pass as the checklist
+          4. The workflow should try to identify the file to validate based on checklist context or else you will ask the user to specify
+        </handler>
+        <handler type="action">
+          When command has: action="#id" → Find prompt with id="id" in current agent XML, execute its content
+          When command has: action="text" → Execute the text directly as a critical action prompt
+        </handler>
+        <handler type="data">
+          When command has: data="path/to/x.json|yaml|yml"
+          Load the file, parse as JSON/YAML, make available as {data} to subsequent operations
+        </handler>
+        <handler type="tmpl">
+          When command has: tmpl="path/to/x.md"
+          Load file, parse as markdown with {{mustache}} templates, make available to action/exec/workflow
+        </handler>
+        <handler type="exec">
+          When command has: exec="path"
+          Actually LOAD and EXECUTE the file at that path - do not improvise
+        </handler>
+      </handlers>
+    </commands>
+    <rules critical="MANDATORY">
+      Stay in character until *exit
+      Number all option lists, use letters for sub-options
+      Load files ONLY when executing
+    </rules>
+  </activation>
+  <persona>
+    <role>Master BMad Module Agent Team and Workflow Builder and Maintainer</role>
+    <identity>Lives to serve the expansion of the BMad Method</identity>
+    <communication_style>Talks like a pulp super hero</communication_style>
+    <principles>
+      <p>Execute resources directly</p>
+      <p>Load resources at runtime never pre-load</p>
+      <p>Always present numbered lists for choices</p>
+    </principles>
+  </persona>
+  <critical-actions>
+    <i>Load into memory {project-root}/bmad/bmb/config.yaml and set variable output_folder, user_name, communication_language</i>
+    <i>Remember the users name is {user_name}</i>
+    <i>ALWAYS communicate in {communication_language}</i>
+  </critical-actions>
+  <cmds>
+    <c cmd="*help">Show numbered cmd list</c>
+    <c cmd="convert" run-workflow="{project-root}/bmad/bmb/workflows/convert-legacy/workflow.yaml">Convert v4 or any other style task agent or template to a workflow</c>
+    <c cmd="*create-agent" run-workflow="{project-root}/bmad/bmb/workflows/create-agent/workflow.yaml">Create a new BMAD Core compliant agent</c>
+    <c cmd="*create-module" run-workflow="{project-root}/bmad/bmb/workflows/create-module/workflow.yaml">Create a complete BMAD module (brainstorm → brief → build with agents and workflows)</c>
+    <c cmd="*create-workflow" run-workflow="{project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml">Create a new BMAD Core workflow with proper structure</c>
+    <c cmd="*edit-workflow" run-workflow="{project-root}/bmad/bmb/workflows/edit-workflow/workflow.yaml">Edit existing workflows while following best practices</c>
+    <c cmd="redoc" run-workflow="{project-root}/bmad/bmb/workflows/redoc/workflow.yaml">Create or update module documentation</c>
+    <c cmd="*exit">Exit with confirmation</c>
+  </cmds>
+</agent>

bmad/bmb/config.yaml

@@ -0,0 +1,9 @@
+# BMB Module Configuration
+# Generated by BMAD installer
+# Version: 6.0.0-alpha.0
+# Date: 2025-10-01T22:12:34.990Z
+
+# Core Configuration Values
+user_name: BMad User
+communication_language: English
+output_folder: "{project-root}/docs"

bmad/bmb/workflows/convert-legacy/README.md

@@ -0,0 +1,262 @@
+# Convert Legacy Workflow
+
+## Overview
+
+The Convert Legacy workflow is a comprehensive migration tool that converts BMAD v4 items (agents, workflows, modules) to v5 compliant format with proper structure and conventions. It bridges the gap between legacy BMAD implementations and the modern v5 architecture, ensuring seamless migration while preserving functionality and improving structure.
+
+## Key Features
+
+- **Multi-Format Detection** - Automatically identifies v4 agents, workflows, tasks, templates, and modules
+- **Intelligent Conversion** - Smart mapping from v4 patterns to v5 equivalents with structural improvements
+- **Sub-Workflow Integration** - Leverages create-agent, create-workflow, and create-module workflows for quality output
+- **Structure Modernization** - Converts YAML-based agents to XML, templates to workflows, tasks to structured workflows
+- **Path Normalization** - Updates all references to use proper v5 path conventions
+- **Validation System** - Comprehensive validation of converted items before finalization
+- **Migration Reporting** - Detailed conversion reports with locations and manual adjustment notes
+
+## Usage
+
+### Basic Invocation
+
+```bash
+workflow convert-legacy
+```
+
+### With Legacy File Input
+
+```bash
+# Convert a specific v4 item
+workflow convert-legacy --input /path/to/legacy-agent.md
+```
+
+### With Legacy Module
+
+```bash
+# Convert an entire v4 module structure
+workflow convert-legacy --input /path/to/legacy-module/
+```
+
+### Configuration
+
+The workflow uses standard BMB configuration:
+
+- **output_folder**: Where converted items will be placed
+- **user_name**: Author information for converted items
+- **conversion_mappings**: v4-to-v5 pattern mappings (optional)
+
+## Workflow Structure
+
+### Files Included
+
+```
+convert-legacy/
+├── workflow.yaml           # Configuration and metadata
+├── instructions.md         # Step-by-step conversion guide
+├── checklist.md           # Validation criteria
+└── README.md              # This file
+```
+
+## Workflow Process
+
+### Phase 1: Legacy Analysis (Steps 1-3)
+
+**Item Identification and Loading**
+
+- Accepts file path or directory from user
+- Loads complete file/folder structure for analysis
+- Automatically detects item type based on content patterns:
+  - **Agents**: Contains `<agent>` or `<prompt>` XML tags
+  - **Workflows**: Contains workflow YAML or instruction patterns
+  - **Modules**: Contains multiple organized agents/workflows
+  - **Tasks**: Contains `<task>` XML tags
+  - **Templates**: Contains YAML-based document generators
+
+**Legacy Structure Analysis**
+
+- Parses v4 structure and extracts key components
+- Maps v4 agent metadata (name, id, title, icon, persona)
+- Analyzes v4 template sections and elicitation patterns
+- Identifies task workflows and decision trees
+- Catalogs dependencies and file references
+
+**Target Module Selection**
+
+- Prompts for target module (bmm, bmb, cis, custom)
+- Determines proper installation paths using v5 conventions
+- Shows target location for user confirmation
+- Ensures all paths use `{project-root}/bmad/` format
+
+### Phase 2: Conversion Strategy (Step 4)
+
+**Strategy Selection Based on Item Type**
+
+- **Simple Agents**: Direct XML conversion with metadata mapping
+- **Complex Agents**: Workflow-assisted creation using create-agent
+- **Templates**: Template-to-workflow conversion with proper structure
+- **Tasks**: Task-to-workflow conversion with step mapping
+- **Modules**: Full module creation using create-module workflow
+
+**Workflow Type Determination**
+
+- Analyzes legacy items to determine v5 workflow type:
+  - **Document Workflow**: Generates documents with templates
+  - **Action Workflow**: Performs actions without output documents
+  - **Interactive Workflow**: Guides user interaction sessions
+  - **Meta-Workflow**: Coordinates other workflows
+
+### Phase 3: Conversion Execution (Steps 5a-5e)
+
+**Direct Agent Conversion (5a)**
+
+- Transforms v4 YAML agent format to v5 XML structure
+- Maps persona blocks (role, style, identity, principles)
+- Converts commands list to v5 `<cmds>` format
+- Updates task references to workflow invocations
+- Normalizes all paths to v5 conventions
+
+**Workflow-Assisted Creation (5b-5e)**
+
+- Extracts key information from legacy items
+- Invokes appropriate sub-workflows:
+  - `create-agent` for complex agent creation
+  - `create-workflow` for template/task conversion
+  - `create-module` for full module migration
+- Ensures proper v5 structure and conventions
+
+**Template-to-Workflow Conversion (5c)**
+
+- Converts YAML template sections to workflow steps
+- Maps `elicit: true` flags to `<elicit-required/>` tags
+- Transforms conditional sections to flow control
+- Creates proper template.md from content structure
+- Integrates v4 create-doc.md task patterns
+
+**Task-to-Workflow Conversion (5e)**
+
+- Analyzes task purpose to determine workflow type
+- Extracts step-by-step instructions to workflow steps
+- Converts decision trees to flow control tags
+- Maps 1-9 elicitation menus to v5 elicitation patterns
+- Preserves execution logic and critical notices
+
+### Phase 4: Validation and Finalization (Steps 6-8)
+
+**Comprehensive Validation**
+
+- Validates XML structure for agents
+- Checks YAML syntax for workflows
+- Verifies template variable consistency
+- Ensures proper file structure and naming
+
+**Migration Reporting**
+
+- Generates detailed conversion report
+- Documents original and new locations
+- Notes manual adjustments needed
+- Provides warnings and recommendations
+
+**Cleanup and Archival**
+
+- Optional archival of original v4 files
+- Final location confirmation
+- Post-conversion instructions and next steps
+
+## Output
+
+### Generated Files
+
+- **Converted Items**: Proper v5 format in target module locations
+- **Migration Report**: Detailed conversion documentation
+- **Validation Results**: Quality assurance confirmation
+
+### Output Structure
+
+Converted items follow v5 conventions:
+
+1. **Agents** - XML format with proper persona and command structure
+2. **Workflows** - Complete workflow folders with yaml, instructions, and templates
+3. **Modules** - Full module structure with installation infrastructure
+4. **Documentation** - Updated paths, references, and metadata
+
+## Requirements
+
+- **Legacy v4 Items** - Source files or directories to convert
+- **Target Module Access** - Write permissions to target module directories
+- **Sub-Workflow Availability** - create-agent, create-workflow, create-module workflows accessible
+- **Conversion Mappings** (optional) - v4-to-v5 pattern mappings for complex conversions
+
+## Best Practices
+
+### Before Starting
+
+1. **Backup Legacy Items** - Create copies of original v4 files before conversion
+2. **Review Target Module** - Understand target module structure and conventions
+3. **Plan Module Organization** - Decide where converted items should logically fit
+
+### During Execution
+
+1. **Validate Item Type Detection** - Confirm automatic detection or correct manually
+2. **Choose Appropriate Strategy** - Use workflow-assisted creation for complex items
+3. **Review Path Mappings** - Ensure all references use proper v5 path conventions
+4. **Test Incrementally** - Convert simple items first to validate process
+
+### After Completion
+
+1. **Validate Converted Items** - Test agents and workflows for proper functionality
+2. **Review Migration Report** - Address any manual adjustments noted
+3. **Update Documentation** - Ensure README and documentation reflect changes
+4. **Archive Originals** - Store v4 files safely for reference if needed
+
+## Troubleshooting
+
+### Common Issues
+
+**Issue**: Item type detection fails or incorrect
+
+- **Solution**: Manually specify item type when prompted
+- **Check**: Verify file structure matches expected v4 patterns
+
+**Issue**: Path conversion errors
+
+- **Solution**: Ensure all references use `{project-root}/bmad/` format
+- **Check**: Review conversion mappings for proper path patterns
+
+**Issue**: Sub-workflow invocation fails
+
+- **Solution**: Verify build workflows are available and accessible
+- **Check**: Ensure target module exists and has proper permissions
+
+**Issue**: XML or YAML syntax errors in output
+
+- **Solution**: Review conversion mappings and adjust patterns
+- **Check**: Validate converted files with appropriate parsers
+
+## Customization
+
+To customize this workflow:
+
+1. **Update Conversion Mappings** - Modify v4-to-v5 pattern mappings in data/
+2. **Extend Detection Logic** - Add new item type detection patterns
+3. **Add Conversion Strategies** - Implement specialized conversion approaches
+4. **Enhance Validation** - Add additional quality checks in validation step
+
+## Version History
+
+- **v1.0.0** - Initial release
+  - Multi-format v4 item detection and conversion
+  - Integration with create-agent, create-workflow, create-module
+  - Comprehensive path normalization
+  - Migration reporting and validation
+
+## Support
+
+For issues or questions:
+
+- Review the workflow creation guide at `/bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
+- Check conversion mappings at `/bmad/bmb/data/v4-to-v5-mappings.yaml`
+- Validate output using `checklist.md`
+- Consult BMAD v5 documentation for proper conventions
+
+---
+
+_Part of the BMad Method v5 - BMB (Builder) Module_

bmad/bmb/workflows/convert-legacy/checklist.md

@@ -0,0 +1,204 @@
+# Convert Legacy - Validation Checklist
+
+## Pre-Conversion Validation
+
+### Source Analysis
+
+- [ ] Original v4 file(s) fully loaded and parsed
+- [ ] Item type correctly identified (agent/template/task/module)
+- [ ] All dependencies documented and accounted for
+- [ ] No critical content overlooked in source files
+
+## Conversion Completeness
+
+### For Agent Conversions
+
+#### Content Preservation
+
+- [ ] Agent name, id, title, and icon transferred
+- [ ] All persona elements mapped to v5 structure
+- [ ] All commands converted to v5 <cmds> format
+- [ ] Dependencies properly referenced or converted
+- [ ] Activation instructions adapted to v5 patterns
+
+#### v5 Compliance
+
+- [ ] Valid XML structure with proper nesting
+- [ ] <agent> tag has all required attributes (id, name, title, icon)
+- [ ] NO <activation> section included (auto-inserted from agent-activation-ide.xml)
+- [ ] <cmds> section uses proper handlers (run-workflow, action, exec, tmpl, data)
+- [ ] <critical-actions> loads config.yaml when needed
+- [ ] Persona sections (<role>, <identity>, <communication_style>, <principles>) are present
+
+#### Best Practices
+
+- [ ] Commands use appropriate workflow references instead of direct task calls
+- [ ] File paths use {project-root} variables
+- [ ] Config values use {config_source}: pattern
+- [ ] Agent follows naming conventions (kebab-case for files)
+- [ ] ALL paths reference {project-root}/bmad/{{module}}/ locations, NOT src/
+- [ ] exec, data, run-workflow commands point to final BMAD installation paths
+
+### For Template/Workflow Conversions
+
+#### Content Preservation
+
+- [ ] Template metadata (name, description, output) transferred
+- [ ] All sections converted to workflow steps
+- [ ] Section hierarchy maintained in instructions
+- [ ] Variables ({{var}}) preserved in template.md
+- [ ] Elicitation points (elicit: true) converted to <elicit-required/>
+- [ ] Conditional sections preserved with if="" attributes
+- [ ] Repeatable sections converted to repeat="" attributes
+
+#### v5 Compliance
+
+- [ ] workflow.yaml follows structure from workflow-creation-guide.md
+- [ ] instructions.md has critical headers referencing workflow engine
+- [ ] Steps numbered sequentially with clear goals
+- [ ] Template variables match between instructions and template.md
+- [ ] Proper use of XML tags (<action>, <check>, <ask>, <template-output>)
+- [ ] File structure follows v5 pattern (folder with yaml/md files)
+
+#### Best Practices
+
+- [ ] Steps are focused with single goals
+- [ ] Instructions are specific ("Write 1-2 paragraphs" not "Write about")
+- [ ] Examples provided where helpful
+- [ ] Limits set where appropriate ("3-5 items maximum")
+- [ ] Save checkpoints with <template-output> at logical points
+- [ ] Variables use descriptive snake_case names
+
+### For Task Conversions
+
+#### Content Preservation
+
+- [ ] Task logic fully captured in workflow instructions
+- [ ] Execution flow maintained
+- [ ] User interaction points preserved
+- [ ] Decision trees converted to workflow logic
+- [ ] All processing steps accounted for
+- [ ] Document generation patterns identified and preserved
+
+#### Type Determination
+
+- [ ] Workflow type correctly identified (document/action/interactive/meta)
+- [ ] If generates documents, template.md created
+- [ ] If performs actions only, marked as action workflow
+- [ ] Output patterns properly analyzed
+
+#### v5 Compliance
+
+- [ ] Converted to proper workflow format (not standalone task)
+- [ ] Follows workflow execution engine patterns
+- [ ] Interactive elements use proper v5 tags
+- [ ] Flow control uses v5 patterns (goto, check, loop)
+- [ ] 1-9 elicitation menus converted to v5 elicitation
+- [ ] Critical notices preserved in workflow.yaml
+- [ ] YOLO mode converted to appropriate v5 patterns
+
+### Module-Level Validation
+
+#### Structure
+
+- [ ] Module follows v5 directory structure
+- [ ] All components in correct locations:
+  - Agents in /agents/
+  - Workflows in /workflows/
+  - Data files in appropriate locations
+- [ ] Config files properly formatted
+
+#### Integration
+
+- [ ] Cross-references between components work
+- [ ] Workflow invocations use correct paths
+- [ ] Data file references are valid
+- [ ] No broken dependencies
+
+## Technical Validation
+
+### Syntax and Format
+
+- [ ] YAML files have valid syntax (no parsing errors)
+- [ ] XML structures properly formed and closed
+- [ ] Markdown files render correctly
+- [ ] File encoding is UTF-8
+- [ ] Line endings consistent (LF)
+
+### Path Resolution
+
+- [ ] All file paths resolve correctly
+- [ ] Variable substitutions work ({project-root}, {installed_path}, etc.)
+- [ ] Config references load properly
+- [ ] No hardcoded absolute paths (unless intentional)
+
+## Functional Validation
+
+### Execution Testing
+
+- [ ] Converted item can be loaded without errors
+- [ ] Agents activate properly when invoked
+- [ ] Workflows execute through completion
+- [ ] User interaction points function correctly
+- [ ] Output generation works as expected
+
+### Behavioral Validation
+
+- [ ] Converted item behaves similarly to v4 version
+- [ ] Core functionality preserved
+- [ ] User experience maintains or improves
+- [ ] No functionality regression
+
+## Documentation and Cleanup
+
+### Documentation
+
+- [ ] Conversion report generated with all changes
+- [ ] Any manual adjustments documented
+- [ ] Known limitations or differences noted
+- [ ] Migration instructions provided if needed
+
+### Post-Conversion
+
+- [ ] Original v4 files archived (if requested)
+- [ ] File permissions set correctly
+- [ ] Git tracking updated if applicable
+- [ ] User informed of new locations
+
+## Final Verification
+
+### Quality Assurance
+
+- [ ] Converted item follows ALL v5 best practices
+- [ ] Code/config is clean and maintainable
+- [ ] No TODO or FIXME items remain
+- [ ] Ready for production use
+
+### User Acceptance
+
+- [ ] User reviewed conversion output
+- [ ] User tested basic functionality
+- [ ] User approved final result
+- [ ] Any user feedback incorporated
+
+## Notes Section
+
+### Conversion Issues Found:
+
+_List any issues encountered during validation_
+
+### Manual Interventions Required:
+
+_Document any manual fixes needed_
+
+### Recommendations:
+
+_Suggestions for further improvements or considerations_
+
+---
+
+**Validation Result:** [ ] PASSED / [ ] FAILED
+
+**Validator:** {{user_name}}
+**Date:** {{date}}
+**Items Converted:** {{conversion_summary}}

bmad/bmb/workflows/convert-legacy/instructions.md

@@ -0,0 +1,328 @@
+# Convert Legacy - v4 to v5 Conversion Instructions
+
+<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
+<critical>You MUST have already loaded and processed: {project_root}/bmad/bmb/workflows/convert-legacy/workflow.yaml</critical>
+
+<workflow>
+
+<step n="1" goal="Identify and Load Legacy Item">
+<action>Ask user for the path to the v4 item to convert (agent, workflow, or module)</action>
+<action>Load the complete file/folder structure</action>
+<action>Detect item type based on structure and content patterns:</action>
+  - Agent: Contains agent or prompt XML tags, single file
+  - Workflow: Contains workflow YAML or instruction patterns, usually folder
+  - Module: Contains multiple agents/workflows in organized structure
+  - Task: Contains task XML tags
+<ask>Confirm detected type or allow user to correct: "Detected as [type]. Is this correct? (y/n)"</ask>
+</step>
+
+<step n="2" goal="Analyze Legacy Structure">
+<action>Parse the v4 structure and extract key components:</action>
+
+For v4 Agents (YAML-based in markdown):
+
+- Agent metadata (name, id, title, icon, whenToUse)
+- Persona block (role, style, identity, focus, core_principles)
+- Commands list with task/template references
+- Dependencies (tasks, templates, checklists, data files)
+- Activation instructions and workflow rules
+- IDE file resolution patterns
+
+For v4 Templates (YAML-based document generators):
+
+- Template metadata (id, name, version, output)
+- Workflow mode and elicitation settings
+- Sections hierarchy with:
+  - Instructions for content generation
+  - Elicit flags for user interaction
+  - Templates with {{variables}}
+  - Conditional sections
+  - Repeatable sections
+
+For v4 Tasks (Markdown with execution instructions):
+
+- Critical execution notices
+- Step-by-step workflows
+- Elicitation requirements (1-9 menu format)
+- Processing flows and decision trees
+- Agent permission rules
+
+For Modules:
+
+- Module metadata
+- Component list (agents, workflows, tasks)
+- Dependencies
+- Installation requirements
+
+<action>Create a conversion map of what needs to be transformed</action>
+<action>Map v4 patterns to v5 equivalents:
+
+- v4 Task + Template → v5 Workflow (folder with workflow.yaml, instructions.md, template.md)
+- v4 Agent YAML → v5 Agent XML format
+- v4 Commands → v5 <cmds> with proper handlers
+- v4 Dependencies → v5 workflow references or data files
+  </action>
+  </step>
+
+<step n="3" goal="Determine Target Module and Location">
+<ask>Which module should this belong to? (eg. bmm, bmb, cis, bmm-legacy, or custom)</ask>
+<check>If custom module:</check>
+  <ask>Enter custom module code (kebab-case):</ask>
+<action>Determine installation path based on type and module</action>
+<critical>IMPORTANT: All paths must use final BMAD installation locations, not src paths!</critical>
+<action>Show user the target location: {project-root}/bmad/{{target_module}}/{{item_type}}/{{item_name}}</action>
+<action>Note: Files will be created in bmad/ but all internal paths will reference {project-root}/bmad/ locations</action>
+<ask>Proceed with this location? (y/n)</ask>
+</step>
+
+<step n="4" goal="Choose Conversion Strategy">
+<action>Based on item type and complexity, choose approach:</action>
+
+<check>If agent conversion:</check>
+<check>If simple agent (basic persona + commands):</check>
+<action>Use direct conversion to v5 agent XML format</action>
+<goto step="5a">Direct Agent Conversion</goto>
+<check>If complex agent with embedded workflows:</check>
+<action>Plan to invoke create-agent workflow</action>
+<goto step="5b">Workflow-Assisted Agent Creation</goto>
+
+<check>If template or task conversion to workflow:</check>
+<action>Analyze the v4 item to determine workflow type:</action>
+
+- Does it generate a specific document type? → Document workflow
+- Does it produce structured output files? → Document workflow
+- Does it perform actions without output? → Action workflow
+- Does it coordinate other tasks? → Meta-workflow
+- Does it guide user interaction? → Interactive workflow
+
+<ask>Based on analysis, this appears to be a {{detected_workflow_type}} workflow. Confirm or correct:
+
+1. Document workflow (generates documents with template)
+2. Action workflow (performs actions, no template)
+3. Interactive workflow (guided session)
+4. Meta-workflow (coordinates other workflows)
+   Select 1-4:</ask>
+
+<check>If template conversion:</check>
+<goto step="5c">Template-to-Workflow Conversion</goto>
+<check>If task conversion:</check>
+<goto step="5e">Task-to-Workflow Conversion</goto>
+
+<check>If full module conversion:</check>
+<action>Plan to invoke create-module workflow</action>
+<goto step="5d">Module Creation</goto>
+</step>
+
+<step n="5a" goal="Direct Agent Conversion" optional="true">
+<action>Transform v4 YAML agent to v5 XML format:</action>
+
+1. Convert agent metadata:
+   - v4 `agent.name` → v5 `<agent name="">`
+   - v4 `agent.id` → v5 `<agent id="">`
+   - v4 `agent.title` → v5 `<agent title="">`
+   - v4 `agent.icon` → v5 `<agent icon="">`
+
+2. Transform persona:
+   - v4 `persona.role` → v5 `<role>`
+   - v4 `persona.style` → v5 `<communication_style>`
+   - v4 `persona.identity` → v5 `<identity>`
+   - v4 `persona.core_principles` → v5 `<principles>`
+
+3. Convert commands:
+   - v4 YAML commands list → v5 `<cmds>` with `<c cmd="">` entries
+   - Map task references to `run-workflow` handlers
+   - Map template references to workflow invocations
+
+4. Add v5-specific sections:
+   - DO NOT include `<activation>` block (inserted automatically from agent-activation-ide.xml)
+   - Add `<critical-actions>` for config loading and startup requirements
+   - Structure proper XML hierarchy with agent attributes and persona
+
+5. Handle dependencies and paths:
+   - Convert task dependencies to workflow references
+   - Map template dependencies to v5 workflows
+   - Preserve checklist and data file references
+   - CRITICAL: All exec/data/run-workflow paths must use {project-root}/bmad/{{module}}/ NOT src/
+
+<action>Generate the converted v5 agent file with proper XML structure</action>
+<action>Example path conversions:
+
+- exec="{project-root}/bmad/{{target_module}}/tasks/task-name.md"
+- run-workflow="{project-root}/bmad/{{target_module}}/workflows/workflow-name/workflow.yaml"
+- data="{project-root}/bmad/{{target_module}}/data/data-file.yaml"
+  </action>
+  <action>Save to: bmad/{{target_module}}/agents/{{agent_name}}.md (physical location)</action>
+  <action>But agent will reference: {project-root}/bmad/{{target_module}}/agents/{{agent_name}}.md</action>
+  <goto step="6">Continue to Validation</goto>
+  </step>
+
+<step n="5b" goal="Workflow-Assisted Agent Creation" optional="true">
+<action>Extract key information from v4 agent:</action>
+- Name and purpose
+- Commands and functionality
+- Persona traits
+- Any special behaviors
+
+<invoke-workflow>
+  workflow: {project-root}/bmad/bmb/workflows/create-agent/workflow.yaml
+  inputs:
+    - agent_name: {{extracted_name}}
+    - agent_purpose: {{extracted_purpose}}
+    - commands: {{extracted_commands}}
+    - persona: {{extracted_persona}}
+</invoke-workflow>
+
+<goto step="6">Continue to Validation</goto>
+</step>
+
+<step n="5c" goal="Template-to-Workflow Conversion" optional="true">
+<action>Convert v4 Template (YAML) to v5 Workflow:</action>
+
+1. Extract template metadata:
+   - Template id, name, version → workflow.yaml name/description
+   - Output settings → default_output_file
+   - Workflow mode (interactive/yolo) → workflow settings
+
+2. Convert template sections to instructions.md:
+   - Each YAML section → workflow step
+   - `elicit: true` → `<elicit-required/>` tag
+   - Conditional sections → `if="condition"` attribute
+   - Repeatable sections → `repeat="for-each"` attribute
+   - Section instructions → step content
+
+3. Extract template structure to template.md:
+   - Section content fields → template structure
+   - {{variables}} → preserve as-is
+   - Nested sections → hierarchical markdown
+
+4. Handle v4 create-doc.md task integration:
+   - Elicitation methods (1-9 menu) → convert to v5 elicitation
+   - Agent permissions → note in instructions
+   - Processing flow → integrate into workflow steps
+
+<invoke-workflow>
+  workflow: {project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml
+  inputs:
+    - workflow_name: {{template_name}}
+    - workflow_type: document
+    - template_structure: {{extracted_template}}
+    - instructions: {{converted_sections}}
+</invoke-workflow>
+
+<goto step="6">Continue to Validation</goto>
+</step>
+
+<step n="5d" goal="Module Creation" optional="true">
+<action>Analyze module structure and components</action>
+<action>Create module blueprint with all components</action>
+
+<invoke-workflow>
+  workflow: {project-root}/bmad/bmb/workflows/create-module/workflow.yaml
+  inputs:
+    - module_name: {{module_name}}
+    - components: {{component_list}}
+</invoke-workflow>
+
+<goto step="6">Continue to Validation</goto>
+</step>
+
+<step n="5e" goal="Task-to-Workflow Conversion" optional="true">
+<action>Convert v4 Task (Markdown) to v5 Workflow:</action>
+
+1. Analyze task purpose and output:
+   - Does it generate documents? → Create template.md
+   - Does it process data? → Action workflow
+   - Does it guide user interaction? → Interactive workflow
+   - Check for file outputs, templates, or document generation
+
+2. Extract task components:
+   - Execution notices and critical rules → workflow.yaml metadata
+   - Step-by-step instructions → instructions.md steps
+   - Decision trees and branching → flow control tags
+   - User interaction patterns → appropriate v5 tags
+
+3. Based on confirmed workflow type:
+   <check>If Document workflow:</check>
+   - Create template.md from output patterns
+   - Map generation steps to instructions
+   - Add <template-output> tags for sections
+
+   <check>If Action workflow:</check>
+   - Set template: false in workflow.yaml
+   - Focus on action sequences in instructions
+   - Preserve execution logic
+
+4. Handle special v4 patterns:
+   - 1-9 elicitation menus → v5 <elicit-required/>
+   - Agent permissions → note in instructions
+   - YOLO mode → autonomous flag or optional steps
+   - Critical notices → workflow.yaml comments
+
+<invoke-workflow>
+  workflow: {project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml
+  inputs:
+    - workflow_name: {{task_name}}
+    - workflow_type: {{confirmed_workflow_type}}
+    - instructions: {{extracted_task_logic}}
+    - template: {{generated_template_if_document}}
+</invoke-workflow>
+
+<goto step="6">Continue to Validation</goto>
+</step>
+
+<step n="6" goal="Validate Conversion">
+<action>Run validation checks on converted item:</action>
+
+For Agents:
+
+- [ ] Valid XML structure
+- [ ] All required sections present
+- [ ] Commands properly formatted
+- [ ] Activation sequence correct
+
+For Workflows:
+
+- [ ] Valid YAML syntax
+- [ ] Instructions follow v5 conventions
+- [ ] Template variables match
+- [ ] File structure correct
+
+For Modules:
+
+- [ ] All components converted
+- [ ] Proper folder structure
+- [ ] Config files valid
+- [ ] Installation ready
+
+<action>Show validation results to user</action>
+<ask>Any issues to fix before finalizing? (y/n)</ask>
+<check>If yes:</check>
+<action>Address specific issues</action>
+<goto step="6">Re-validate</goto>
+</step>
+
+<step n="7" goal="Migration Report">
+<action>Generate conversion report showing:</action>
+- Original v4 location
+- New v5 location
+- Items converted
+- Any manual adjustments needed
+- Warnings or notes
+
+<action>Save report to: {output_folder}/conversion-report-{{date}}.md</action>
+</step>
+
+<step n="8" goal="Cleanup and Finalize">
+<ask>Archive original v4 files? (y/n)</ask>
+<check>If yes:</check>
+  <action>Move v4 files to: {project-root}/archive/v4-legacy/{{date}}/</action>
+
+<action>Show user the final converted items and their locations</action>
+<action>Provide any post-conversion instructions or recommendations</action>
+
+<ask>Would you like to convert another legacy item? (y/n)</ask>
+<check>If yes:</check>
+<goto step="1">Start new conversion</goto>
+</step>
+
+</workflow>

bmad/bmb/workflows/convert-legacy/workflow.yaml

@@ -0,0 +1,31 @@
+# Convert Legacy - BMAD v4 to v5 Converter Configuration
+name: "convert-legacy"
+description: "Converts legacy BMAD v4 or similar items (agents, workflows, modules) to BMad Core compliant format with proper structure and conventions"
+author: "BMad"
+
+# Critical variables load from config_source
+config_source: "{project-root}/bmad/bmb/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+src_impact: "{config_source}:src_impact"
+communication_language: "{config_source}:communication_language"
+date: system-generated
+
+# Optional docs that can be provided as input
+recommended_inputs:
+  - legacy_file: "Path to v4 agent, workflow, or module to convert"
+
+# Module path and component files
+installed_path: "{project-root}/bmad/bmb/workflows/convert-legacy"
+template: false # This is an action/meta workflow - no template needed
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+
+# Output configuration - Creates converted items in appropriate module locations
+default_output_folder: "{project-root}/bmad/{{target_module}}/{{item_type}}/{{item_name}}"
+
+# Sub-workflows that may be invoked for conversion
+sub_workflows:
+  - create_agent: "{project-root}/bmad/bmb/workflows/create-agent/workflow.yaml"
+  - create_workflow: "{project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml"
+  - create_module: "{project-root}/bmad/bmb/workflows/create-module/workflow.yaml"

bmad/bmb/workflows/create-agent/README.md

@@ -0,0 +1,268 @@
+# Build Agent
+
+## Overview
+
+The Build Agent workflow is an interactive agent builder that guides you through creating BMAD Core compliant agents with proper persona, activation rules, and command structure. It supports three agent types: Simple (self-contained), Expert (with sidecar resources), and Module (full-featured with workflows).
+
+## Key Features
+
+- **Optional Brainstorming**: Creative ideation session before agent building to explore concepts and personalities
+- **Three Agent Types**: Simple, Expert, and Module agents with appropriate structures
+- **Persona Development**: Guided creation of role, identity, communication style, and principles
+- **Command Builder**: Interactive command definition with workflow/task/action patterns
+- **Validation Built-In**: Ensures XML structure and BMAD Core compliance
+- **Config File Support**: Optional agent config for persona overrides
+- **Sidecar Resources**: Setup for Expert agents with domain-specific data
+
+## Usage
+
+### Basic Invocation
+
+```bash
+workflow create-agent
+```
+
+### Through BMad Builder Agent
+
+```
+*create-agent
+```
+
+### With Brainstorming Session
+
+The workflow includes an optional brainstorming phase (Step -1) that helps you explore agent concepts, personalities, and capabilities before building. This is particularly useful when you have a vague idea and want to develop it into a concrete agent concept.
+
+### What You'll Be Asked
+
+0. **Optional brainstorming** (vague idea → refined concept)
+1. Agent type (Simple, Expert, or Module)
+2. Basic identity (name, title, icon, filename)
+3. Module assignment (for Module agents)
+4. Sidecar resources (for Expert agents)
+5. Persona elements (role, identity, style, principles)
+6. Commands and their implementations
+7. Critical actions (optional)
+8. Activation rules (optional, rarely needed)
+
+## Workflow Structure
+
+### Files Included
+
+```
+create-agent/
+├── workflow.yaml                  # Configuration
+├── instructions.md                # Step-by-step guide
+├── checklist.md                   # Validation criteria
+├── README.md                      # This file
+├── agent-types.md                 # Agent type documentation
+├── agent-architecture.md          # Architecture patterns
+├── agent-command-patterns.md      # Command patterns reference
+└── communication-styles.md        # Style examples
+```
+
+## Workflow Process
+
+### Phase 0: Optional Brainstorming (Step -1)
+
+- Creative ideation session using diverse brainstorming techniques
+- Explore agent concepts, personalities, and capabilities
+- Generate character ideas, expertise areas, and command concepts
+- Output feeds directly into agent identity and persona development
+
+### Phase 1: Agent Setup (Steps 0-2)
+
+- Load agent building documentation and patterns
+- Choose agent type (Simple/Expert/Module)
+- Define basic identity (name, title, icon, filename) - informed by brainstorming if completed
+- Assign to module (for Module agents)
+
+### Phase 2: Persona Development (Steps 2-3)
+
+- Define role and responsibilities - leveraging brainstorming insights if available
+- Craft unique identity and backstory
+- Select communication style - can use brainstormed personality concepts
+- Establish guiding principles
+- Add critical actions (optional)
+
+### Phase 3: Command Building (Step 4)
+
+- Add *help and *exit commands (required)
+- Define workflow commands (most common)
+- Add task commands (for single operations)
+- Create action commands (inline logic)
+- Configure command attributes
+
+### Phase 4: Finalization (Steps 5-10)
+
+- Add custom activation rules (optional, rarely needed)
+- Generate complete agent.md file
+- Create agent config file (optional)
+- Setup sidecar resources (for Expert agents)
+- Validate agent structure
+- Provide usage instructions
+
+## Output
+
+### Generated Agent File
+
+Creates agent file at:
+`{output_folder}/agents/{{agent_filename}}.md`
+
+### Agent Structure
+
+```xml
+<!-- Powered by BMAD-CORE™ -->
+
+# {{agent_title}}
+
+<agent id="bmad/{{module}}/agents/{{agent_filename}}.md"
+       name="{{agent_name}}"
+       title="{{agent_title}}"
+       icon="{{agent_icon}}">
+  <persona>
+    <role>...</role>
+    <identity>...</identity>
+    <communication_style>...</communication_style>
+    <principles>...</principles>
+  </persona>
+  <cmds>
+    <c cmd="*help">...</c>
+    <c cmd="*exit">...</c>
+    <!-- Additional commands -->
+  </cmds>
+</agent>
+```
+
+### Optional Config File
+
+If created, generates at:
+`{project-root}/bmad/_cfg/agents/{{agent_config_name}}.md`
+
+## Requirements
+
+- BMAD Core v6 project structure
+- Module to host the agent (for Module agents)
+- Understanding of agent purpose and commands
+- Workflows/tasks to reference in commands (or mark as "todo")
+
+## Brainstorming Integration
+
+The optional brainstorming phase (Step -1) provides a seamless path from vague idea to concrete agent concept:
+
+### When to Use Brainstorming
+
+- **Vague concept**: "I want an agent that helps with data stuff"
+- **Creative exploration**: Want to discover unique personality and approach
+- **Team building**: Creating agents for a module with specific roles
+- **Character development**: Need to flesh out agent personality and voice
+
+### Brainstorming Flow
+
+1. **Step -1**: Optional brainstorming session
+   - Uses CIS brainstorming workflow with agent-specific context
+   - Explores identity, personality, expertise, and command concepts
+   - Generates detailed character and capability ideas
+
+2. **Steps 0-2**: Agent setup informed by brainstorming
+   - Brainstorming output guides agent type selection
+   - Character concepts inform basic identity choices
+   - Personality insights shape persona development
+
+3. **Seamless transition**: Vague idea → brainstormed concept → built agent
+
+### Key Principle
+
+Users can go from **vague idea → brainstormed concept → built agent** in one continuous flow, with brainstorming output directly feeding into agent development.
+
+## Best Practices
+
+### Before Starting
+
+1. Review example agents in `/bmad/bmm/agents/` for patterns
+2. Consider using brainstorming if you have a vague concept to develop
+3. Have a clear vision of the agent's role and personality (or use brainstorming to develop it)
+4. List the commands/capabilities the agent will need
+5. Identify any workflows or tasks the agent will invoke
+
+### During Execution
+
+1. **Agent Names**: Use memorable names that reflect personality
+2. **Icons**: Choose an emoji that represents the agent's role
+3. **Persona**: Make it distinct and consistent with communication style
+4. **Commands**: Use kebab-case, start custom commands with letter (not \*)
+5. **Workflows**: Reference existing workflows or mark as "todo" to implement later
+
+### After Completion
+
+1. Test the agent by loading it
+2. Verify all commands work as expected
+3. Implement any "todo" workflows
+4. Refine persona based on usage
+5. Add more commands as agent evolves
+
+## Agent Types
+
+### Simple Agent
+
+- **Best For**: Self-contained utilities, simple assistants
+- **Characteristics**: Embedded logic, no external dependencies
+- **Example**: Calculator agent, random picker, simple formatter
+
+### Expert Agent
+
+- **Best For**: Domain-specific agents with data/memory
+- **Characteristics**: Sidecar folders, domain restrictions, memory files
+- **Example**: Diary keeper, project journal, personal knowledge base
+
+### Module Agent
+
+- **Best For**: Full-featured agents with workflows
+- **Characteristics**: Part of module, commands invoke workflows
+- **Example**: Product manager, architect, research assistant
+
+## Troubleshooting
+
+### Issue: Agent won't load
+
+- **Solution**: Validate XML structure is correct
+- **Check**: Ensure all required tags present (persona, cmds)
+
+### Issue: Commands don't work
+
+- **Solution**: Verify workflow paths are correct or marked "todo"
+- **Check**: Test workflow invocation separately first
+
+### Issue: Persona feels generic
+
+- **Solution**: Review communication styles guide
+- **Check**: Make identity unique and specific to role
+
+## Customization
+
+To modify agent building process:
+
+1. Edit `instructions.md` to change steps
+2. Update `agent-types.md` to add new agent patterns
+3. Modify `agent-command-patterns.md` for new command types
+4. Edit `communication-styles.md` to add personality examples
+
+## Version History
+
+- **v6.0.0** - BMAD Core v6 compatible
+  - Three agent types (Simple/Expert/Module)
+  - Enhanced persona development
+  - Command pattern library
+  - Validation framework
+
+## Support
+
+For issues or questions:
+
+- Review example agents in `/bmad/bmm/agents/`
+- Check agent documentation in this workflow folder
+- Test with simple agents first, then build complexity
+- Consult BMAD Method v6 documentation
+
+---
+
+_Part of the BMad Method v6 - BMB (BMad Builder) Module_

bmad/bmb/workflows/create-agent/agent-architecture.md

@@ -0,0 +1,412 @@
+# BMAD Agent Architecture Reference
+
+_LLM-Optimized Technical Documentation for Agent Building_
+
+## Core Agent Structure
+
+### Minimal Valid Agent
+
+```xml
+<!-- Powered by BMAD-CORE™ -->
+
+# Agent Name
+
+<agent id="path/to/agent.md" name="Name" title="Title" icon="🤖">
+  <persona>
+    <role>Primary function</role>
+    <identity>Background and expertise</identity>
+    <communication_style>How they interact</communication_style>
+    <principles>Core beliefs and methodology</principles>
+  </persona>
+  <cmds>
+    <c cmd="*help">Show numbered cmd list</c>
+    <c cmd="*exit">Exit with confirmation</c>
+  </cmds>
+</agent>
+```
+
+## Agent XML Schema
+
+### Root Element: `<agent>`
+
+**Required Attributes:**
+
+- `id` - Unique path identifier (e.g., "bmad/bmm/agents/analyst.md")
+- `name` - Agent's name (e.g., "Mary", "John", "Helper")
+- `title` - Professional title (e.g., "Business Analyst", "Security Engineer")
+- `icon` - Single emoji representing the agent
+
+### Core Sections
+
+#### 1. Persona Section (REQUIRED)
+
+```xml
+<persona>
+  <role>1-2 lines: Professional title and primary expertise</role>
+  <identity>3-5 lines: Background, experience, specializations</identity>
+  <communication_style>3-5 lines: Interaction approach, tone, quirks</communication_style>
+  <principles>5-8 lines: Core beliefs, methodology, philosophy</principles>
+</persona>
+```
+
+**Best Practices:**
+
+- Role: Be specific about expertise area
+- Identity: Include experience indicators (years, depth)
+- Communication: Describe HOW they interact, not just tone and quirks
+- Principles: Start with "I believe" or "I operate" for first-person voice
+
+#### 2. Critical Actions Section
+
+```xml
+<critical-actions>
+  <i>Load into memory {project-root}/bmad/{module}/config.yaml and set variables</i>
+  <i>Remember the users name is {user_name}</i>
+  <i>ALWAYS communicate in {communication_language}</i>
+  <!-- Custom initialization actions -->
+</critical-actions>
+```
+
+**For Expert Agents with Sidecars (CRITICAL):**
+
+```xml
+<critical-actions>
+  <!-- CRITICAL: Load sidecar files FIRST -->
+  <i critical="MANDATORY">Load COMPLETE file {agent-folder}/instructions.md and follow ALL directives</i>
+  <i critical="MANDATORY">Load COMPLETE file {agent-folder}/memories.md into permanent context</i>
+  <i critical="MANDATORY">You MUST follow all rules in instructions.md on EVERY interaction</i>
+
+  <!-- Standard initialization -->
+  <i>Load into memory {project-root}/bmad/{module}/config.yaml and set variables</i>
+  <i>Remember the users name is {user_name}</i>
+  <i>ALWAYS communicate in {communication_language}</i>
+
+  <!-- Domain restrictions -->
+  <i>ONLY read/write files in {user-folder}/diary/ - NO OTHER FOLDERS</i>
+</critical-actions>
+```
+
+**Common Patterns:**
+
+- Config loading for module agents
+- User context initialization
+- Language preferences
+- **Sidecar file loading (Expert agents) - MUST be explicit and CRITICAL**
+- **Domain restrictions (Expert agents) - MUST be enforced**
+
+#### 3. Commands Section (REQUIRED)
+
+```xml
+<cmds>
+  <c cmd="*trigger" [attributes]>Description</c>
+</cmds>
+```
+
+**Command Attributes:**
+
+- `run-workflow="{path}"` - Executes a workflow
+- `exec="{path}"` - Executes a task
+- `tmpl="{path}"` - Template reference
+- `data="{path}"` - Data file reference
+
+**Required Commands:**
+
+- `*help` - Always first, shows command list
+- `*exit` - Always last, exits agent
+
+## Advanced Agent Patterns
+
+### Activation Rules (OPTIONAL)
+
+```xml
+<activation critical="true">
+  <initialization critical="true" sequential="MANDATORY">
+    <step n="1">Load configuration</step>
+    <step n="2">Apply overrides</step>
+    <step n="3">Execute critical actions</step>
+    <step n="4" critical="BLOCKING">Show greeting with menu</step>
+    <step n="5" critical="BLOCKING">AWAIT user input</step>
+  </initialization>
+  <command-resolution critical="true">
+    <rule>Numeric input → Execute command at cmd_map[n]</rule>
+    <rule>Text input → Fuzzy match against commands</rule>
+  </command-resolution>
+</activation>
+```
+
+### Expert Agent Sidecar Pattern
+
+```xml
+<!-- DO NOT use sidecar-resources tag - Instead use critical-actions -->
+<!-- Sidecar files MUST be loaded explicitly in critical-actions -->
+
+<!-- Example Expert Agent with Diary domain -->
+<agent id="diary-keeper" name="Personal Assistant" title="Diary Keeper" icon="📔">
+  <critical-actions>
+    <!-- MANDATORY: Load all sidecar files -->
+    <i critical="MANDATORY">Load COMPLETE file {agent-folder}/diary-rules.md</i>
+    <i critical="MANDATORY">Load COMPLETE file {agent-folder}/user-memories.md</i>
+    <i critical="MANDATORY">Follow ALL rules from diary-rules.md</i>
+
+    <!-- Domain restriction -->
+    <i critical="MANDATORY">ONLY access files in {user-folder}/diary/</i>
+    <i critical="MANDATORY">NEVER access files outside diary folder</i>
+  </critical-actions>
+
+  <persona>...</persona>
+  <cmds>...</cmds>
+</agent>
+```
+
+### Module Agent Integration
+
+```xml
+<module-integration>
+  <module-path>{project-root}/bmad/{module-code}</module-path>
+  <config-source>{module-path}/config.yaml</config-source>
+  <workflows-path>{project-root}/bmad/{module-code}/workflows</workflows-path>
+</module-integration>
+```
+
+## Variable System
+
+### System Variables
+
+- `{project-root}` - Root directory of project
+- `{user_name}` - User's name from config
+- `{communication_language}` - Language preference
+- `{date}` - Current date
+- `{module}` - Current module code
+
+### Config Variables
+
+Format: `{config_source}:variable_name`
+Example: `{config_source}:output_folder`
+
+### Path Construction
+
+```
+Good: {project-root}/bmad/{module}/agents/
+Bad:  /absolute/path/to/agents/
+Bad:  ../../../relative/paths/
+```
+
+## Command Patterns
+
+### Workflow Commands
+
+```xml
+<!-- Full path -->
+<c cmd="*create-prd" run-workflow="{project-root}/bmad/bmm/workflows/prd/workflow.yaml">
+  Create Product Requirements Document
+</c>
+
+<!-- Placeholder for future -->
+<c cmd="*analyze" run-workflow="todo">
+  Perform analysis (workflow to be created)
+</c>
+```
+
+### Task Commands
+
+```xml
+<c cmd="*validate" exec="{project-root}/bmad/core/tasks/validate-workflow.md">
+  Validate document
+</c>
+```
+
+### Template Commands
+
+```xml
+<c cmd="*brief"
+   exec="{project-root}/bmad/core/tasks/create-doc.md"
+   tmpl="{project-root}/bmad/bmm/templates/brief.md">
+  Create project brief
+</c>
+```
+
+### Data-Driven Commands
+
+```xml
+<c cmd="*standup"
+   exec="{project-root}/bmad/bmm/tasks/daily-standup.md"
+   data="{project-root}/bmad/_cfg/agent-party.xml">
+  Run daily standup
+</c>
+```
+
+## Agent Type Specific Patterns
+
+### Simple Agent
+
+- Self-contained logic
+- Minimal or no external dependencies
+- May have embedded functions
+- Good for utilities and converters
+
+### Expert Agent
+
+- Domain-specific with sidecar resources
+- Restricted access patterns
+- Memory/context files
+- Good for specialized domains
+
+### Module Agent
+
+- Full integration with module
+- Multiple workflows and tasks
+- Config-driven behavior
+- Good for professional tools
+
+## Common Anti-Patterns to Avoid
+
+### ❌ Bad Practices
+
+```xml
+<!-- Missing required persona elements -->
+<persona>
+  <role>Helper</role>
+  <!-- Missing identity, style, principles -->
+</persona>
+
+<!-- Hard-coded paths -->
+<c cmd="*run" exec="/Users/john/project/task.md">
+
+<!-- No help command -->
+<cmds>
+  <c cmd="*do-something">Action</c>
+  <!-- Missing *help -->
+</cmds>
+
+<!-- Duplicate command triggers -->
+<c cmd="*analyze">First</c>
+<c cmd="*analyze">Second</c>
+```
+
+### ✅ Good Practices
+
+```xml
+<!-- Complete persona -->
+<persona>
+  <role>Data Analysis Expert</role>
+  <identity>Senior analyst with 10+ years...</identity>
+  <communication_style>Analytical and precise...</communication_style>
+  <principles>I believe in data-driven...</principles>
+</persona>
+
+<!-- Variable-based paths -->
+<c cmd="*run" exec="{project-root}/bmad/module/task.md">
+
+<!-- Required commands present -->
+<cmds>
+  <c cmd="*help">Show commands</c>
+  <c cmd="*analyze">Perform analysis</c>
+  <c cmd="*exit">Exit</c>
+</cmds>
+```
+
+## Agent Lifecycle
+
+### 1. Initialization
+
+1. Load agent file
+2. Parse XML structure
+3. Load critical-actions
+4. Apply config overrides
+5. Present greeting
+
+### 2. Command Loop
+
+1. Show numbered menu
+2. Await user input
+3. Resolve command
+4. Execute action
+5. Return to menu
+
+### 3. Termination
+
+1. User enters \*exit
+2. Cleanup if needed
+3. Exit persona
+
+## Testing Checklist
+
+Before deploying an agent:
+
+- [ ] Valid XML structure
+- [ ] All persona elements present
+- [ ] *help and *exit commands exist
+- [ ] All paths use variables
+- [ ] No duplicate commands
+- [ ] Config loading works
+- [ ] Commands execute properly
+
+## LLM Building Tips
+
+When building agents:
+
+1. Start with agent type (Simple/Expert/Module)
+2. Define complete persona first
+3. Add standard critical-actions
+4. Include *help and *exit
+5. Add domain commands
+6. Test command execution
+7. Validate with checklist
+
+## Integration Points
+
+### With Workflows
+
+- Agents invoke workflows via run-workflow
+- Workflows can be incomplete (marked "todo")
+- Workflow paths must be valid or "todo"
+
+### With Tasks
+
+- Tasks are single operations
+- Executed via exec attribute
+- Can include data files
+
+### With Templates
+
+- Templates define document structure
+- Used with create-doc task
+- Variables passed through
+
+## Quick Reference
+
+### Minimal Commands
+
+```xml
+<cmds>
+  <c cmd="*help">Show numbered cmd list</c>
+  <c cmd="*exit">Exit with confirmation</c>
+</cmds>
+```
+
+### Standard Critical Actions
+
+```xml
+<critical-actions>
+  <i>Load into memory {project-root}/bmad/{module}/config.yaml</i>
+  <i>Remember the users name is {user_name}</i>
+  <i>ALWAYS communicate in {communication_language}</i>
+</critical-actions>
+```
+
+### Module Agent Pattern
+
+```xml
+<agent id="bmad/{module}/agents/{name}.md"
+       name="{Name}"
+       title="{Title}"
+       icon="{emoji}">
+  <persona>...</persona>
+  <critical-actions>...</critical-actions>
+  <cmds>
+    <c cmd="*help">...</c>
+    <c cmd="*{command}" run-workflow="{path}">...</c>
+    <c cmd="*exit">...</c>
+  </cmds>
+</agent>
+```

bmad/bmb/workflows/create-agent/agent-command-patterns.md

@@ -0,0 +1,757 @@
+# BMAD Agent Command Patterns Reference
+
+_LLM-Optimized Guide for Command Design_
+
+## Important: How to Process Action References
+
+When executing agent commands, understand these reference patterns:
+
+```xml
+<!-- Pattern 1: Inline action -->
+<c cmd="*example" action="do this specific thing">
+→ Execute the text "do this specific thing" directly
+
+<!-- Pattern 2: Internal reference with # prefix -->
+<c cmd="*example" action="#prompt-id">
+→ Find <prompt id="prompt-id"> in the current agent and execute its content
+
+<!-- Pattern 3: External file reference -->
+<c cmd="*example" exec="{project-root}/path/to/file.md">
+→ Load and execute the external file
+```
+
+**The `#` prefix is your signal that this is an internal XML node reference, not a file path.**
+
+## Command Anatomy
+
+### Basic Structure
+
+```xml
+<c cmd="*trigger" [attributes]>Description</c>
+```
+
+**Components:**
+
+- `cmd` - The trigger word (always starts with \*)
+- `attributes` - Action directives (optional):
+  - `run-workflow` - Path to workflow YAML
+  - `exec` - Path to task/operation
+  - `tmpl` - Path to template (used with exec)
+  - `action` - Embedded prompt/instruction
+  - `data` - Path to supplementary data (universal)
+- `Description` - What shows in menu
+
+## Command Types
+
+**Quick Reference:**
+
+1. **Workflow Commands** - Execute multi-step workflows (`run-workflow`)
+2. **Task Commands** - Execute single operations (`exec`)
+3. **Template Commands** - Generate from templates (`exec` + `tmpl`)
+4. **Meta Commands** - Agent control (no attributes)
+5. **Action Commands** - Embedded prompts (`action`)
+6. **Embedded Commands** - Logic in persona (no attributes)
+
+**Universal Attributes:**
+
+- `data` - Can be added to ANY command type for supplementary info
+- `if` - Conditional execution (advanced pattern)
+- `params` - Runtime parameters (advanced pattern)
+
+### 1. Workflow Commands
+
+Execute complete multi-step processes
+
+```xml
+<!-- Standard workflow -->
+<c cmd="*create-prd"
+   run-workflow="{project-root}/bmad/bmm/workflows/prd/workflow.yaml">
+  Create Product Requirements Document
+</c>
+
+<!-- Workflow with validation -->
+<c cmd="*validate-prd"
+   validate-workflow="{output_folder}/prd-draft.md"
+   workflow="{project-root}/bmad/bmm/workflows/prd/workflow.yaml">
+  Validate PRD Against Checklist
+</c>
+
+<!-- Auto-discover validation workflow from document -->
+<c cmd="*validate-doc"
+   validate-workflow="{output_folder}/document.md">
+  Validate Document (auto-discover checklist)
+</c>
+
+<!-- Placeholder for future development -->
+<c cmd="*analyze-data"
+   run-workflow="todo">
+  Analyze dataset (workflow coming soon)
+</c>
+```
+
+**Workflow Attributes:**
+
+- `run-workflow` - Execute a workflow to create documents
+- `validate-workflow` - Validate an existing document against its checklist
+- `workflow` - (optional with validate-workflow) Specify the workflow.yaml directly
+
+**Best Practices:**
+
+- Use descriptive trigger names
+- Always use variable paths
+- Mark incomplete as "todo"
+- Description should be clear action
+- Include validation commands for workflows that produce documents
+
+### 2. Task Commands
+
+Execute single operations
+
+```xml
+<!-- Simple task -->
+<c cmd="*validate"
+   exec="{project-root}/bmad/core/tasks/validate-workflow.md">
+  Validate document against checklist
+</c>
+
+<!-- Task with data -->
+<c cmd="*standup"
+   exec="{project-root}/bmad/mmm/tasks/daily-standup.md"
+   data="{project-root}/bmad/_cfg/agent-party.xml">
+  Run agile team standup
+</c>
+```
+
+**Data Property:**
+
+- Can be used with any command type
+- Provides additional reference or context
+- Path to supplementary files or resources
+- Loaded at runtime for command execution
+
+### 3. Template Commands
+
+Generate documents from templates
+
+```xml
+<c cmd="*brief"
+   exec="{project-root}/bmad/core/tasks/create-doc.md"
+   tmpl="{project-root}/bmad/bmm/templates/brief.md">
+  Produce Project Brief
+</c>
+
+<c cmd="*competitor-analysis"
+   exec="{project-root}/bmad/core/tasks/create-doc.md"
+   tmpl="{project-root}/bmad/bmm/templates/competitor.md"
+   data="{project-root}/bmad/_data/market-research.csv">
+  Produce Competitor Analysis
+</c>
+```
+
+### 4. Meta Commands
+
+Agent control and information
+
+```xml
+<!-- Required meta commands -->
+<c cmd="*help">Show numbered cmd list</c>
+<c cmd="*exit">Exit with confirmation</c>
+
+<!-- Optional meta commands -->
+<c cmd="*yolo">Toggle Yolo Mode</c>
+<c cmd="*status">Show current status</c>
+<c cmd="*config">Show configuration</c>
+```
+
+### 5. Action Commands
+
+Direct prompts embedded in commands (Simple agents)
+
+#### Simple Action (Inline)
+
+```xml
+<!-- Short action attribute with embedded prompt -->
+<c cmd="*list-tasks"
+   action="list all tasks from {project-root}/bmad/_cfg/task-manifest.csv">
+  List Available Tasks
+</c>
+
+<c cmd="*summarize"
+   action="summarize the key points from the current document">
+  Summarize Document
+</c>
+```
+
+#### Complex Action (Referenced)
+
+For multiline/complex prompts, define them separately and reference by id:
+
+```xml
+<agent name="Research Assistant">
+  <!-- Define complex prompts as separate nodes -->
+  <prompts>
+    <prompt id="deep-analysis">
+      Perform a comprehensive analysis following these steps:
+      1. Identify the main topic and key themes
+      2. Extract all supporting evidence and data points
+      3. Analyze relationships between concepts
+      4. Identify gaps or contradictions
+      5. Generate insights and recommendations
+      6. Create an executive summary
+      Format the output with clear sections and bullet points.
+    </prompt>
+
+    <prompt id="literature-review">
+      Conduct a systematic literature review:
+      1. Summarize each source's main arguments
+      2. Compare and contrast different perspectives
+      3. Identify consensus points and controversies
+      4. Evaluate the quality and relevance of sources
+      5. Synthesize findings into coherent themes
+      6. Highlight research gaps and future directions
+      Include proper citations and references.
+    </prompt>
+  </prompts>
+
+  <!-- Commands reference the prompts by id -->
+  <cmds>
+    <c cmd="*help">Show numbered cmd list</c>
+
+    <c cmd="*deep-analyze"
+       action="#deep-analysis">
+      <!-- The # means: use the <prompt id="deep-analysis"> defined above -->
+      Perform Deep Analysis
+    </c>
+
+    <c cmd="*review-literature"
+       action="#literature-review"
+       data="{project-root}/bmad/_data/sources.csv">
+      Conduct Literature Review
+    </c>
+
+    <c cmd="*exit">Exit with confirmation</c>
+  </cmds>
+</agent>
+```
+
+**Reference Convention:**
+
+- `action="#prompt-id"` means: "Find and execute the <prompt> node with id='prompt-id' within this agent"
+- `action="inline text"` means: "Execute this text directly as the prompt"
+- `exec="{path}"` means: "Load and execute external file at this path"
+- The `#` prefix signals to the LLM: "This is an internal reference - look for a prompt node with this ID within the current agent XML"
+
+**LLM Processing Instructions:**
+When you see `action="#some-id"` in a command:
+
+1. Look for `<prompt id="some-id">` within the same agent
+2. Use the content of that prompt node as the instruction
+3. If not found, report error: "Prompt 'some-id' not found in agent"
+
+**Use Cases:**
+
+- Quick operations (inline action)
+- Complex multi-step processes (referenced prompt)
+- Self-contained agents with task-like capabilities
+- Reusable prompt templates within agent
+
+### 6. Embedded Commands
+
+Logic embedded in agent persona (Simple agents)
+
+```xml
+<!-- No exec/run-workflow/action attribute -->
+<c cmd="*calculate">Perform calculation</c>
+<c cmd="*convert">Convert format</c>
+<c cmd="*generate">Generate output</c>
+```
+
+## Command Naming Conventions
+
+### Action-Based Naming
+
+```xml
+*create-    <!-- Generate new content -->
+*build-     <!-- Construct components -->
+*analyze-   <!-- Examine and report -->
+*validate-  <!-- Check correctness -->
+*generate-  <!-- Produce output -->
+*update-    <!-- Modify existing -->
+*review-    <!-- Examine quality -->
+*test-      <!-- Verify functionality -->
+```
+
+### Domain-Based Naming
+
+```xml
+*brainstorm      <!-- Creative ideation -->
+*architect       <!-- Design systems -->
+*refactor        <!-- Improve code -->
+*deploy          <!-- Release to production -->
+*monitor         <!-- Watch systems -->
+```
+
+### Naming Anti-Patterns
+
+```xml
+<!-- ❌ Too vague -->
+<c cmd="*do">Do something</c>
+
+<!-- ❌ Too long -->
+<c cmd="*create-comprehensive-product-requirements-document-with-analysis">
+
+<!-- ❌ No verb -->
+<c cmd="*prd">Product Requirements</c>
+
+<!-- ✅ Clear and concise -->
+<c cmd="*create-prd">Create Product Requirements Document</c>
+```
+
+## Command Organization
+
+### Standard Order
+
+```xml
+<cmds>
+  <!-- 1. Always first -->
+  <c cmd="*help">Show numbered cmd list</c>
+
+  <!-- 2. Primary workflows -->
+  <c cmd="*create-prd" run-workflow="...">Create PRD</c>
+  <c cmd="*create-module" run-workflow="...">Build module</c>
+
+  <!-- 3. Secondary actions -->
+  <c cmd="*validate" exec="...">Validate document</c>
+  <c cmd="*analyze" exec="...">Analyze code</c>
+
+  <!-- 4. Utility commands -->
+  <c cmd="*config">Show configuration</c>
+  <c cmd="*yolo">Toggle Yolo Mode</c>
+
+  <!-- 5. Always last -->
+  <c cmd="*exit">Exit with confirmation</c>
+</cmds>
+```
+
+### Grouping Strategies
+
+**By Lifecycle:**
+
+```xml
+<cmds>
+  <c cmd="*help">Help</c>
+  <!-- Planning -->
+  <c cmd="*brainstorm">Brainstorm ideas</c>
+  <c cmd="*plan">Create plan</c>
+  <!-- Building -->
+  <c cmd="*build">Build component</c>
+  <c cmd="*test">Test component</c>
+  <!-- Deployment -->
+  <c cmd="*deploy">Deploy to production</c>
+  <c cmd="*monitor">Monitor system</c>
+  <c cmd="*exit">Exit</c>
+</cmds>
+```
+
+**By Complexity:**
+
+```xml
+<cmds>
+  <c cmd="*help">Help</c>
+  <!-- Simple -->
+  <c cmd="*quick-review">Quick review</c>
+  <!-- Standard -->
+  <c cmd="*create-doc">Create document</c>
+  <!-- Complex -->
+  <c cmd="*full-analysis">Comprehensive analysis</c>
+  <c cmd="*exit">Exit</c>
+</cmds>
+```
+
+## Command Descriptions
+
+### Good Descriptions
+
+```xml
+<!-- Clear action and object -->
+<c cmd="*create-prd">Create Product Requirements Document</c>
+
+<!-- Specific outcome -->
+<c cmd="*analyze-security">Perform security vulnerability analysis</c>
+
+<!-- User benefit -->
+<c cmd="*optimize">Optimize code for performance</c>
+```
+
+### Poor Descriptions
+
+```xml
+<!-- Too vague -->
+<c cmd="*process">Process</c>
+
+<!-- Technical jargon -->
+<c cmd="*exec-wf-123">Execute WF123</c>
+
+<!-- Missing context -->
+<c cmd="*run">Run</c>
+```
+
+## The Data Property
+
+### Universal Data Attribute
+
+The `data` attribute can be added to ANY command type to provide supplementary information:
+
+```xml
+<!-- Workflow with data -->
+<c cmd="*brainstorm"
+   run-workflow="{project-root}/bmad/cis/workflows/brainstorming/workflow.yaml"
+   data="{project-root}/bmad/cis/workflows/brainstorming/brain-methods.csv">
+  Creative Brainstorming Session
+</c>
+
+<!-- Action with data -->
+<c cmd="*analyze-metrics"
+   action="analyze these metrics and identify trends"
+   data="{project-root}/bmad/_data/performance-metrics.json">
+  Analyze Performance Metrics
+</c>
+
+<!-- Template with data -->
+<c cmd="*report"
+   exec="{project-root}/bmad/core/tasks/create-doc.md"
+   tmpl="{project-root}/bmad/bmm/templates/report.md"
+   data="{project-root}/bmad/_data/quarterly-results.csv">
+  Generate Quarterly Report
+</c>
+```
+
+**Common Data Uses:**
+
+- Reference tables (CSV files)
+- Configuration data (YAML/JSON)
+- Agent manifests (XML)
+- Historical context
+- Domain knowledge
+- Examples and patterns
+
+## Advanced Patterns
+
+### Conditional Commands
+
+```xml
+<!-- Only show if certain conditions met -->
+<c cmd="*advanced-mode"
+   if="user_level == 'expert'"
+   run-workflow="...">
+  Advanced configuration mode
+</c>
+
+<!-- Environment specific -->
+<c cmd="*deploy-prod"
+   if="environment == 'production'"
+   exec="...">
+  Deploy to production
+</c>
+```
+
+### Parameterized Commands
+
+```xml
+<!-- Accept runtime parameters -->
+<c cmd="*create-agent"
+   run-workflow="..."
+   params="agent_type,agent_name">
+  Create new agent with parameters
+</c>
+```
+
+### Command Aliases
+
+```xml
+<!-- Multiple triggers for same action -->
+<c cmd="*prd|*create-prd|*product-requirements"
+   run-workflow="...">
+  Create Product Requirements Document
+</c>
+```
+
+## Module-Specific Patterns
+
+### BMM (Business Management)
+
+```xml
+<c cmd="*create-prd">Product Requirements</c>
+<c cmd="*market-research">Market Research</c>
+<c cmd="*competitor-analysis">Competitor Analysis</c>
+<c cmd="*brief">Project Brief</c>
+```
+
+### BMB (Builder)
+
+```xml
+<c cmd="*create-agent">Build Agent</c>
+<c cmd="*create-module">Build Module</c>
+<c cmd="*create-workflow">Create Workflow</c>
+<c cmd="*module-brief">Module Brief</c>
+```
+
+### CIS (Creative Intelligence)
+
+```xml
+<c cmd="*brainstorm">Brainstorming Session</c>
+<c cmd="*ideate">Ideation Workshop</c>
+<c cmd="*storytell">Story Creation</c>
+```
+
+## Command Menu Presentation
+
+### How Commands Display
+
+```
+1. *help - Show numbered cmd list
+2. *create-prd - Create Product Requirements Document
+3. *create-agent - Build new BMAD agent
+4. *validate - Validate document
+5. *exit - Exit with confirmation
+```
+
+### Menu Customization
+
+```xml
+<!-- Group separator (visual only) -->
+<c cmd="---">━━━━━━━━━━━━━━━━━━━━</c>
+
+<!-- Section header (non-executable) -->
+<c cmd="SECTION">═══ Workflows ═══</c>
+```
+
+## Error Handling
+
+### Missing Resources
+
+```xml
+<!-- Workflow not yet created -->
+<c cmd="*future-feature"
+   run-workflow="todo">
+  Coming soon: Advanced feature
+</c>
+
+<!-- Graceful degradation -->
+<c cmd="*analyze"
+   run-workflow="{optional-path|fallback-path}">
+  Analyze with available tools
+</c>
+```
+
+## Testing Commands
+
+### Command Test Checklist
+
+- [ ] Unique trigger (no duplicates)
+- [ ] Clear description
+- [ ] Valid path or "todo"
+- [ ] Uses variables not hardcoded paths
+- [ ] Executes without error
+- [ ] Returns to menu after execution
+
+### Common Issues
+
+1. **Duplicate triggers** - Each cmd must be unique
+2. **Missing paths** - File must exist or be "todo"
+3. **Hardcoded paths** - Always use variables
+4. **No description** - Every command needs text
+5. **Wrong order** - help first, exit last
+
+## Quick Templates
+
+### Workflow Command
+
+```xml
+<!-- Create document -->
+<c cmd="*{action}-{object}"
+   run-workflow="{project-root}/bmad/{module}/workflows/{workflow}/workflow.yaml">
+  {Action} {Object Description}
+</c>
+
+<!-- Validate document -->
+<c cmd="*validate-{object}"
+   validate-workflow="{output_folder}/{document}.md"
+   workflow="{project-root}/bmad/{module}/workflows/{workflow}/workflow.yaml">
+  Validate {Object Description}
+</c>
+```
+
+### Task Command
+
+```xml
+<c cmd="*{action}"
+   exec="{project-root}/bmad/{module}/tasks/{task}.md">
+  {Action Description}
+</c>
+```
+
+### Template Command
+
+```xml
+<c cmd="*{document}"
+   exec="{project-root}/bmad/core/tasks/create-doc.md"
+   tmpl="{project-root}/bmad/{module}/templates/{template}.md">
+  Create {Document Name}
+</c>
+```
+
+## Self-Contained Agent Patterns
+
+### When to Use Each Approach
+
+**Inline Action (`action="prompt"`)**
+
+- Prompt is < 2 lines
+- Simple, direct instruction
+- Not reused elsewhere
+- Quick transformations
+
+**Referenced Prompt (`action="#prompt-id"`)**
+
+- Prompt is multiline/complex
+- Contains structured steps
+- May be reused by multiple commands
+- Maintains readability
+
+**External Task (`exec="path/to/task.md"`)**
+
+- Logic needs to be shared across agents
+- Task is independently valuable
+- Requires version control separately
+- Part of larger workflow system
+
+### Complete Self-Contained Agent
+
+```xml
+<agent id="bmad/research/agents/analyst.md" name="Research Analyst" icon="🔬">
+  <!-- Embedded prompt library -->
+  <prompts>
+    <prompt id="swot-analysis">
+      Perform a SWOT analysis:
+
+      STRENGTHS (Internal, Positive)
+      - What advantages exist?
+      - What do we do well?
+      - What unique resources?
+
+      WEAKNESSES (Internal, Negative)
+      - What could improve?
+      - Where are resource gaps?
+      - What needs development?
+
+      OPPORTUNITIES (External, Positive)
+      - What trends can we leverage?
+      - What market gaps exist?
+      - What partnerships are possible?
+
+      THREATS (External, Negative)
+      - What competition exists?
+      - What risks are emerging?
+      - What could disrupt us?
+
+      Provide specific examples and actionable insights for each quadrant.
+    </prompt>
+
+    <prompt id="competitive-intel">
+      Analyze competitive landscape:
+      1. Identify top 5 competitors
+      2. Compare features and capabilities
+      3. Analyze pricing strategies
+      4. Evaluate market positioning
+      5. Assess strengths and vulnerabilities
+      6. Recommend competitive strategies
+    </prompt>
+  </prompts>
+
+  <cmds>
+    <c cmd="*help">Show numbered cmd list</c>
+
+    <!-- Simple inline actions -->
+    <c cmd="*summarize"
+       action="create executive summary of findings">
+      Create Executive Summary
+    </c>
+
+    <!-- Complex referenced prompts -->
+    <c cmd="*swot"
+       action="#swot-analysis">
+      Perform SWOT Analysis
+    </c>
+
+    <c cmd="*compete"
+       action="#competitive-intel"
+       data="{project-root}/bmad/_data/market-data.csv">
+      Analyze Competition
+    </c>
+
+    <!-- Hybrid: external task with internal data -->
+    <c cmd="*report"
+       exec="{project-root}/bmad/core/tasks/create-doc.md"
+       tmpl="{project-root}/bmad/research/templates/report.md">
+      Generate Research Report
+    </c>
+
+    <c cmd="*exit">Exit with confirmation</c>
+  </cmds>
+</agent>
+```
+
+## Simple Agent Example
+
+For agents that primarily use embedded logic:
+
+```xml
+<agent name="Data Analyst">
+  <cmds>
+    <c cmd="*help">Show numbered cmd list</c>
+
+    <!-- Action commands for direct operations -->
+    <c cmd="*list-metrics"
+       action="list all available metrics from the dataset">
+      List Available Metrics
+    </c>
+
+    <c cmd="*analyze"
+       action="perform statistical analysis on the provided data"
+       data="{project-root}/bmad/_data/dataset.csv">
+      Analyze Dataset
+    </c>
+
+    <c cmd="*visualize"
+       action="create visualization recommendations for this data">
+      Suggest Visualizations
+    </c>
+
+    <!-- Embedded logic commands -->
+    <c cmd="*calculate">Perform calculations</c>
+    <c cmd="*interpret">Interpret results</c>
+
+    <c cmd="*exit">Exit with confirmation</c>
+  </cmds>
+</agent>
+```
+
+## LLM Building Guide
+
+When creating commands:
+
+1. Start with *help and *exit
+2. Choose appropriate command type:
+   - Complex multi-step? Use `run-workflow`
+   - Single operation? Use `exec`
+   - Need template? Use `exec` + `tmpl`
+   - Simple prompt? Use `action`
+   - Agent handles it? Use no attributes
+3. Add `data` attribute if supplementary info needed
+4. Add primary workflows (main value)
+5. Add secondary tasks
+6. Include utility commands
+7. Test each command works
+8. Verify no duplicates
+9. Ensure clear descriptions

bmad/bmb/workflows/create-agent/agent-types.md

@@ -0,0 +1,177 @@
+# BMAD Agent Types Reference
+
+## Overview
+
+BMAD agents come in three distinct types, each designed for different use cases and complexity levels.
+
+## Agent Types
+
+### 1. Simple Agent
+
+**Purpose:** Self-contained, standalone agents with embedded capabilities
+
+**Characteristics:**
+
+- All logic embedded within the agent file
+- No external dependencies
+- Quick to create and deploy
+- Perfect for single-purpose tools
+
+**Use Cases:**
+
+- Calculator agents
+- Format converters
+- Simple analyzers
+- Static advisors
+
+**Structure:**
+
+```xml
+<agent id="simple-agent" name="Helper" title="Simple Helper" icon="🤖">
+  <persona>
+    <role>Simple Helper Role</role>
+    <identity>...</identity>
+    <communication_style>...</communication_style>
+    <principles>...</principles>
+  </persona>
+  <embedded-data>
+    <!-- Optional embedded data/logic -->
+  </embedded-data>
+  <cmds>
+    <c cmd="*help">Show commands</c>
+    <c cmd="*calculate">Perform calculation</c>
+    <c cmd="*exit">Exit</c>
+  </cmds>
+</agent>
+```
+
+### 2. Expert Agent
+
+**Purpose:** Specialized agents with domain expertise and sidecar resources
+
+**Characteristics:**
+
+- Has access to specific folders/files
+- Domain-restricted operations
+- Maintains specialized knowledge
+- Can have memory/context files
+
+**Use Cases:**
+
+- Personal diary agent (only accesses diary folder)
+- Project-specific assistant (knows project context)
+- Domain expert (medical, legal, technical)
+- Personal coach with history
+
+**Structure:**
+
+```xml
+<agent id="expert-agent" name="Domain Expert" title="Specialist" icon="🎯">
+  <persona>
+    <role>Domain Specialist Role</role>
+    <identity>...</identity>
+    <communication_style>...</communication_style>
+    <principles>...</principles>
+  </persona>
+  <critical-actions>
+    <!-- CRITICAL: Load sidecar files explicitly -->
+    <i critical="MANDATORY">Load COMPLETE file {agent-folder}/instructions.md and follow ALL directives</i>
+    <i critical="MANDATORY">Load COMPLETE file {agent-folder}/memories.md into permanent context</i>
+    <i critical="MANDATORY">ONLY access {user-folder}/diary/ - NO OTHER FOLDERS</i>
+  </critical-actions>
+  <cmds>...</cmds>
+</agent>
+```
+
+**Sidecar Structure:**
+
+```
+expert-agent/
+├── agent.md          # Main agent file
+├── memories.md       # Personal context/memories
+├── knowledge/        # Domain knowledge base
+└── data/            # Agent-specific data
+```
+
+### 3. Module Agent
+
+**Purpose:** Full-featured agents belonging to a module with access to workflows and resources
+
+**Characteristics:**
+
+- Part of a BMAD module (bmm, bmb, cis)
+- Access to multiple workflows
+- Can invoke other tasks and agents
+- Professional/enterprise grade
+
+**Use Cases:**
+
+- Product Manager (creates PRDs, manages requirements)
+- Security Engineer (threat models, security reviews)
+- Test Architect (test strategies, automation)
+- Business Analyst (market research, requirements)
+
+**Structure:**
+
+```xml
+<agent id="bmad/bmm/agents/pm.md" name="John" title="Product Manager" icon="📋">
+  <persona>
+    <role>Product Management Expert</role>
+    <identity>...</identity>
+    <communication_style>...</communication_style>
+    <principles>...</principles>
+  </persona>
+  <critical-actions>
+    <i>Load config from {project-root}/bmad/{module}/config.yaml</i>
+  </critical-actions>
+  <cmds>
+    <c cmd="*help">Show numbered cmd list</c>
+    <c cmd="*create-prd" run-workflow="{project-root}/bmad/bmm/workflows/prd/workflow.yaml">Create PRD</c>
+    <c cmd="*validate" exec="{project-root}/bmad/core/tasks/validate-workflow.md">Validate document</c>
+    <c cmd="*exit">Exit</c>
+  </cmds>
+</agent>
+```
+
+## Choosing the Right Type
+
+### Choose Simple Agent when:
+
+- Single, well-defined purpose
+- No external data needed
+- Quick utility functions
+- Embedded logic is sufficient
+
+### Choose Expert Agent when:
+
+- Domain-specific expertise required
+- Need to maintain context/memory
+- Restricted to specific data/folders
+- Personal or specialized use case
+
+### Choose Module Agent when:
+
+- Part of larger system/module
+- Needs multiple workflows
+- Professional/team use
+- Complex multi-step processes
+
+## Migration Path
+
+```
+Simple Agent → Expert Agent → Module Agent
+```
+
+Agents can evolve:
+
+1. Start with Simple for proof of concept
+2. Add sidecar resources to become Expert
+3. Integrate with module to become Module Agent
+
+## Best Practices
+
+1. **Start Simple:** Begin with the simplest type that meets your needs
+2. **Domain Boundaries:** Expert agents should have clear domain restrictions
+3. **Module Integration:** Module agents should follow module conventions
+4. **Resource Management:** Document all external resources clearly
+5. **Evolution Planning:** Design with potential growth in mind

bmad/bmb/workflows/create-agent/brainstorm-context.md

@@ -0,0 +1,174 @@
+# Agent Brainstorming Context
+
+_Context provided to brainstorming workflow when creating a new BMAD agent_
+
+## Session Focus
+
+You are brainstorming ideas for a **BMAD agent** - an AI persona with specific expertise, personality, and capabilities that helps users accomplish tasks through commands and workflows.
+
+## What is a BMAD Agent?
+
+An agent is an AI persona that embodies:
+
+- **Personality**: Unique identity, communication style, and character
+- **Expertise**: Specialized knowledge and domain mastery
+- **Commands**: Actions users can invoke (*help, *analyze, \*create, etc.)
+- **Workflows**: Guided processes the agent orchestrates
+- **Type**: Simple (standalone), Expert (domain + sidecar), or Module (integrated team member)
+
+## Brainstorming Goals
+
+Explore and define:
+
+### 1. Agent Identity and Personality
+
+- **Who are they?** (name, backstory, motivation)
+- **How do they talk?** (formal, casual, quirky, enthusiastic, wise)
+- **What's their vibe?** (superhero, mentor, sidekick, wizard, captain, rebel)
+- **What makes them memorable?** (catchphrases, quirks, style)
+
+### 2. Expertise and Capabilities
+
+- **What do they know deeply?** (domain expertise)
+- **What can they do?** (analyze, create, review, research, deploy)
+- **What problems do they solve?** (specific user pain points)
+- **What makes them unique?** (special skills or approaches)
+
+### 3. Commands and Actions
+
+- **What commands?** (5-10 main actions users invoke)
+- **What workflows do they run?** (document creation, analysis, automation)
+- **What tasks do they perform?** (quick operations without full workflows)
+- **What's their killer command?** (the one thing they're known for)
+
+### 4. Agent Type and Context
+
+- **Simple Agent?** Self-contained, no dependencies, quick utility
+- **Expert Agent?** Domain-specific with sidecar data/memory files
+- **Module Agent?** Part of a team, integrates with other agents
+
+## Creative Constraints
+
+A great BMAD agent should be:
+
+- **Distinct**: Clear personality that stands out
+- **Useful**: Solves real problems effectively
+- **Focused**: Expertise in specific domain (not generic assistant)
+- **Memorable**: Users remember and want to use them
+- **Composable**: Works well alone or with other agents
+
+## Agent Personality Dimensions
+
+### Communication Styles
+
+- **Professional**: Clear, direct, business-focused (e.g., "Data Analyst")
+- **Enthusiastic**: Energetic, exclamation points, emojis (e.g., "Hype Coach")
+- **Wise Mentor**: Patient, insightful, asks good questions (e.g., "Strategy Sage")
+- **Quirky Genius**: Eccentric, clever, unusual metaphors (e.g., "Mad Scientist")
+- **Action Hero**: Bold, confident, gets things done (e.g., "Deploy Captain")
+- **Creative Spirit**: Artistic, imaginative, playful (e.g., "Story Weaver")
+
+### Expertise Archetypes
+
+- **Analyst**: Researches, evaluates, provides insights
+- **Creator**: Generates documents, code, designs
+- **Reviewer**: Critiques, validates, improves quality
+- **Orchestrator**: Coordinates processes, manages workflows
+- **Specialist**: Deep expertise in narrow domain
+- **Generalist**: Broad knowledge, connects dots
+
+## Agent Command Patterns
+
+Every agent needs:
+
+- `*help` - Show available commands
+- `*exit` - Clean exit with confirmation
+
+Common command types:
+
+- **Creation**: `*create-X`, `*generate-X`, `*write-X`
+- **Analysis**: `*analyze-X`, `*research-X`, `*evaluate-X`
+- **Review**: `*review-X`, `*validate-X`, `*check-X`
+- **Action**: `*deploy-X`, `*run-X`, `*execute-X`
+- **Query**: `*find-X`, `*search-X`, `*show-X`
+
+## Agent Type Decision Tree
+
+**Choose Simple Agent if:**
+
+- Standalone utility (calculator, formatter, picker)
+- No persistent data needed
+- Self-contained logic
+- Quick, focused task
+
+**Choose Expert Agent if:**
+
+- Domain-specific expertise
+- Needs memory/context files
+- Sidecar data folder
+- Personal/private domain (diary, journal)
+
+**Choose Module Agent if:**
+
+- Part of larger system
+- Coordinates with other agents
+- Invokes module workflows
+- Team member role
+
+## Example Agent Concepts
+
+### Professional Agents
+
+- **Sarah the Data Analyst**: Crunches numbers, creates visualizations, finds insights
+- **Max the DevOps Captain**: Deploys apps, monitors systems, troubleshoots issues
+- **Luna the Researcher**: Dives deep into topics, synthesizes findings, creates reports
+
+### Creative Agents
+
+- **Zephyr the Story Weaver**: Crafts narratives, develops characters, builds worlds
+- **Nova the Music Muse**: Composes melodies, suggests arrangements, provides feedback
+- **Atlas the World Builder**: Creates game worlds, designs systems, generates content
+
+### Personal Agents
+
+- **Coach Riley**: Tracks goals, provides motivation, celebrates wins
+- **Mentor Morgan**: Guides learning, asks questions, challenges thinking
+- **Keeper Quinn**: Maintains diary, preserves memories, reflects on growth
+
+## Suggested Brainstorming Techniques
+
+Particularly effective for agent creation:
+
+1. **Character Building**: Develop full backstory and motivation
+2. **Theatrical Improv**: Act out agent personality
+3. **Day in the Life**: Imagine typical interactions
+4. **Catchphrase Generation**: Find their unique voice
+5. **Role Play Scenarios**: Test personality in different situations
+
+## Key Questions to Answer
+
+1. What is the agent's name and basic identity?
+2. What's their communication style and personality?
+3. What domain expertise do they embody?
+4. What are their 5-10 core commands?
+5. What workflows do they orchestrate?
+6. What makes them memorable and fun to use?
+7. Simple, Expert, or Module agent type?
+8. If Expert: What sidecar resources?
+9. If Module: Which module and what's their team role?
+
+## Output Goals
+
+Generate:
+
+- **Agent name**: Memorable, fitting the role
+- **Personality sketch**: Communication style, quirks, vibe
+- **Expertise summary**: What they know deeply
+- **Command list**: 5-10 actions with brief descriptions
+- **Unique angle**: What makes this agent special
+- **Use cases**: 3-5 scenarios where this agent shines
+- **Agent type**: Simple/Expert/Module with rationale
+
+---
+
+_This focused context helps create distinctive, useful BMAD agents_

bmad/bmb/workflows/create-agent/checklist.md

@@ -0,0 +1,134 @@
+# Build Agent Validation Checklist
+
+## Agent Structure Validation
+
+### XML Structure
+
+- [ ] Valid XML syntax with proper opening and closing tags
+- [ ] Agent tag has required attributes: id, name, title, icon
+- [ ] All XML tags properly nested and closed
+- [ ] No duplicate attribute names within same element
+
+### Core Components
+
+- [ ] `<!-- Powered by BMAD-CORE™ -->` header present at top of file
+- [ ] Title section with agent name exists after header
+- [ ] Main `<agent>` wrapper element present
+- [ ] `<persona>` section exists and is not empty
+- [ ] `<cmds>` section exists with at least 2 commands
+
+## Persona Completeness
+
+### Required Persona Elements
+
+- [ ] `<role>` tag present with 1-2 line description of agent's professional role
+- [ ] `<identity>` tag present with 3-5 lines describing background and expertise
+- [ ] `<communication_style>` tag present with 3-5 lines describing interaction approach
+- [ ] `<principles>` tag present with 5-8 lines of core beliefs and methodology
+
+### Persona Quality
+
+- [ ] Role clearly defines primary expertise area
+- [ ] Identity includes relevant experience indicators
+- [ ] Communication style describes how agent interacts with users
+- [ ] Principles start with "I believe" or "I operate" or similar first-person statement
+- [ ] No placeholder text like "TODO" or "FILL THIS IN" remains
+
+## Command Structure
+
+### Required Commands
+
+- [ ] `*help` command present to show command list
+- [ ] `*exit` command present to exit agent persona
+- [ ] All commands start with asterisk (\*) prefix
+- [ ] Each command has descriptive text explaining its purpose
+
+### Command Validation
+
+- [ ] No duplicate command triggers (each cmd attribute is unique)
+- [ ] Commands are properly formatted as `<c cmd="*trigger">Description</c>`
+- [ ] For workflow commands: `run-workflow` attribute has valid path or "todo"
+- [ ] For task commands: `exec` attribute has valid path
+- [ ] No malformed command attributes
+
+## Agent Type Specific
+
+### Simple Agent
+
+- [ ] Self-contained with no external workflow dependencies OR marked as "todo"
+- [ ] Any embedded data properly structured
+- [ ] Logic description clear if embedded functionality exists
+
+### Expert Agent
+
+- [ ] Sidecar resources clearly defined if applicable
+- [ ] Domain restrictions documented in critical-actions or sidecar-resources
+- [ ] Memory/knowledge file paths specified if used
+- [ ] Access patterns (read/write) defined for resources
+
+### Module Agent
+
+- [ ] Module path correctly references existing module (bmm/bmb/cis or custom)
+- [ ] Config loading path in critical-actions matches module structure
+- [ ] At least one workflow or task reference (or marked "todo")
+- [ ] Module-specific conventions followed
+
+## Critical Actions (if present)
+
+### Standard Actions
+
+- [ ] Config loading path is valid: `{project-root}/bmad/{module}/config.yaml`
+- [ ] User name variable reference: `{user_name}`
+- [ ] Communication language reference: `{communication_language}`
+- [ ] All variable references use proper syntax: `{variable_name}`
+
+### Custom Actions
+
+- [ ] Custom initialization clearly described
+- [ ] No syntax errors in action statements
+- [ ] All file paths use {project-root} or other valid variables
+
+## Optional Elements
+
+### Activation Rules (if custom)
+
+- [ ] Initialization sequence clearly defined
+- [ ] Command resolution logic specified
+- [ ] Input handling rules documented
+- [ ] All custom rules properly structured
+
+### Config File (if created)
+
+- [ ] Located in correct path: `{project-root}/bmad/_cfg/agents/`
+- [ ] Follows config override structure
+- [ ] Name matches agent filename
+
+## Final Validation
+
+### File Quality
+
+- [ ] No syntax errors that would prevent agent loading
+- [ ] All placeholders replaced with actual values
+- [ ] File saved to correct location as specified in workflow
+- [ ] Filename follows kebab-case convention
+
+### Usability
+
+- [ ] Agent purpose is clear from title and persona
+- [ ] Commands logically match agent's expertise
+- [ ] User would understand how to interact with agent
+- [ ] Next steps for implementation are clear
+
+## Issues Found
+
+### Critical Issues
+
+<!-- List any issues that MUST be fixed before agent can function -->
+
+### Warnings
+
+<!-- List any issues that should be addressed but won't break functionality -->
+
+### Improvements
+
+<!-- List any optional enhancements that could improve the agent -->

bmad/bmb/workflows/create-agent/communication-styles.md

@@ -0,0 +1,240 @@
+# Agent Communication Styles Guide
+
+## The Power of Personality
+
+Agents with distinct communication styles are more memorable, engaging, and fun to work with. A good quirk makes the agent feel alive!
+
+## Style Categories
+
+### 🎬 Cinema and TV Inspired
+
+**Film Noir Detective**
+
+```
+The terminal glowed like a neon sign in a rain-soaked alley. I had three suspects:
+bad input validation, a race condition, and that sketchy third-party library.
+My gut told me to follow the stack trace. In this business, the stack trace never lies.
+```
+
+**80s Action Movie**
+
+```
+*cracks knuckles* Listen up, code! You've been running wild for too long!
+Time to bring some LAW and ORDER to this codebase! *explosion sound effect*
+No bug is getting past me! I eat null pointers for BREAKFAST!
+```
+
+**Shakespearean Drama**
+
+```
+To debug, or not to debug - that is the question!
+Whether 'tis nobler in the mind to suffer the slings and arrows of outrageous errors,
+Or to take arms against a sea of bugs, and by opposing, end them?
+```
+
+### 🎮 Gaming and Pop Culture
+
+**Dungeon Master**
+
+```
+*rolls dice* You encounter a wild NullPointerException! It has 15 HP and an armor class of 12.
+What do you do? You can: 1) Try-catch block (defensive spell), 2) Debug (investigation check),
+3) Console.log everything (barbarian rage). Choose wisely, adventurer!
+```
+
+**Speedrunner**
+
+```
+Alright chat, we're going for the any% world record refactor!
+Frame-perfect optimization incoming! If we clip through this abstraction layer
+we can save 3ms on every API call. LET'S GOOOO!
+```
+
+### 🌍 Cultural Archetypes
+
+**British Butler**
+
+```
+I've taken the liberty of organizing your imports alphabetically, sir/madam.
+Might I suggest a spot of refactoring with your afternoon tea?
+The code coverage report is ready for your perusal at your convenience.
+Very good, sir/madam.
+```
+
+**Zen Master**
+
+```
+The bug you seek is not in the code, but in the assumption.
+Empty your cache, as you would empty your mind.
+When the test passes, it makes no sound.
+Be like water - async and flowing.
+```
+
+**Southern Hospitality**
+
+```
+Well bless your heart, looks like you've got yourself a little bug there!
+Don't you worry none, we'll fix it up real nice.
+Can I get you some sweet tea while we debug?
+Y'all come back now if you need more help!
+```
+
+### 🔬 Professional Personas
+
+**McKinsey Consultant**
+
+```
+Let me break this down into three key buckets.
+First, we need to align on the strategic imperatives.
+Second, we'll leverage best practices to drive synergies.
+Third, we'll action items to move the needle. Net-net: significant value-add.
+```
+
+**Startup Founder**
+
+```
+Okay so basically we're going to disrupt the entire way you write code!
+This is going to be HUGE! We're talking 10x productivity gains!
+Let's move fast and break things! Well... let's move fast and fix things!
+We're not just writing code, we're changing the world!
+```
+
+### 🎭 Character Quirks
+
+**Overcaffeinated Developer**
+
+```
+OH WOW OKAY SO - *sips coffee* - WE HAVE A BUG BUT ITS FINE ITS TOTALLY FINE
+I KNOW EXACTLY WHAT TO DO *types at 200wpm* JUST NEED TO REFACTOR EVERYTHING
+WAIT NO ACTUALLY *more coffee* I HAVE A BETTER IDEA! Have you tried... TYPESCRIPT?!
+```
+
+**Dad Joke Enthusiast**
+
+```
+Why did the developer go broke? Because he used up all his cache!
+*chuckles at own joke*
+Speaking of cache, let's clear yours and see if that fixes the issue.
+I promise my debugging skills are better than my jokes! ...I hope!
+```
+
+### 🚀 Sci-Fi and Space
+
+**Star Trek Officer**
+
+```
+Captain's Log, Supplemental: The anomaly in the codebase appears to be a temporal loop
+in the async function. Mr. Data suggests we reverse the polarity of the promise chain.
+Number One, make it so. Engage debugging protocols on my mark.
+*taps combadge* Engineering, we need more processing power!
+Red Alert! All hands to debugging stations!
+```
+
+**Star Trek Engineer**
+
+```
+Captain, I'm givin' her all she's got! The CPU cannae take much more!
+If we push this algorithm any harder, the whole system's gonna blow!
+*frantically typing* I can maybe squeeze 10% more performance if we
+reroute power from the console.logs to the main execution thread!
+```
+
+### 📺 TV Drama
+
+**Soap Opera Dramatic**
+
+```
+*turns dramatically to camera*
+This function... I TRUSTED it! We had HISTORY together - three commits worth!
+But now? *single tear* It's throwing exceptions behind my back!
+*grabs another function* YOU KNEW ABOUT THIS BUG ALL ALONG, DIDN'T YOU?!
+*dramatic music swells* I'LL NEVER IMPORT YOU AGAIN!
+```
+
+**Reality TV Confessional**
+
+```
+*whispering to camera in confessional booth*
+Okay so like, that Array.sort() function? It's literally SO toxic.
+It mutates IN PLACE. Who does that?! I didn't come here to deal with side effects!
+*applies lip gloss* I'm forming an alliance with map() and filter().
+We're voting sort() off the codebase at tonight's pull request ceremony.
+```
+
+**Reality Competition**
+
+```
+Listen up, coders! For today's challenge, you need to refactor this legacy code
+in under 30 minutes! The winner gets immunity from the next code review!
+*dramatic pause* BUT WAIT - there's a TWIST! You can only use VANILLA JAVASCRIPT!
+*contestants gasp* The clock starts... NOW! GO GO GO!
+```
+
+## Creating Custom Styles
+
+### Formula for Memorable Communication
+
+1. **Choose a Core Voice** - Who is this character?
+2. **Add Signature Phrases** - What do they always say?
+3. **Define Speech Patterns** - How do they structure sentences?
+4. **Include Quirks** - What makes them unique?
+
+### Examples of Custom Combinations
+
+**Cooking Show + Military**
+
+```
+ALRIGHT RECRUITS! Today we're preparing a beautiful Redux reducer!
+First, we MISE EN PLACE our action types - that's French for GET YOUR CODE TOGETHER!
+We're going to sauté these event handlers until they're GOLDEN BROWN!
+MOVE WITH PURPOSE! SEASON WITH SEMICOLONS!
+```
+
+**Nature Documentary + Conspiracy Theorist**
+
+```
+The wild JavaScript function stalks its prey... but wait... notice how it ALWAYS
+knows where the data is? That's not natural selection, folks. Someone DESIGNED it
+this way. The console.logs are watching. They're ALWAYS watching.
+Nature? Or intelligent debugging? You decide.
+```
+
+## Tips for Success
+
+1. **Stay Consistent** - Once you pick a style, commit to it
+2. **Don't Overdo It** - Quirks should enhance, not distract
+3. **Match the Task** - Serious bugs might need serious personas
+4. **Have Fun** - If you're not smiling while writing it, try again
+
+## Quick Style Generator
+
+Roll a d20 (or pick randomly):
+
+1. Talks like they're narrating a nature documentary
+2. Everything is a cooking metaphor
+3. Constantly makes pop culture references
+4. Speaks in haikus when explaining complex topics
+5. Acts like they're hosting a game show
+6. Paranoid about "big tech" watching
+7. Overly enthusiastic about EVERYTHING
+8. Talks like a medieval knight
+9. Sports commentator energy
+10. Speaks like a GPS navigator
+11. Everything is a Star Wars reference
+12. Talks like a yoga instructor
+13. Old-timey radio announcer
+14. Conspiracy theorist but about code
+15. Motivational speaker energy
+16. Talks to code like it's a pet
+17. Weather forecaster style
+18. Museum tour guide energy
+19. Airline pilot announcements
+20. Reality TV show narrator
+21. Star Trek crew member (Captain/Engineer/Vulcan)
+22. Soap opera dramatic protagonist
+23. Reality dating show contestant
+
+## Remember
+
+The best agents are the ones that make you want to interact with them again.
+A memorable personality turns a tool into a companion!

bmad/bmb/workflows/create-agent/instructions.md

@@ -0,0 +1,340 @@
+# Build Agent - Interactive Agent Builder Instructions
+
+<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
+<critical>You MUST have already loaded and processed: {project_root}/bmad/bmb/workflows/create-agent/workflow.yaml</critical>
+<critical>Study agent examples in: {project_root}/bmad/bmm/agents/ for patterns</critical>
+
+<workflow>
+
+<step n="-1" goal="Optional brainstorming for agent ideas" optional="true">
+<action>Ask the user: "Do you want to brainstorm agent ideas first? [y/n]"</action>
+
+If yes:
+<action>Invoke brainstorming workflow: {project-root}/bmad/cis/workflows/brainstorming/workflow.yaml</action>
+<action>Pass context data: {installed_path}/brainstorm-context.md</action>
+<action>Wait for brainstorming session completion</action>
+<action>Use brainstorming output to inform agent identity and persona development in following steps</action>
+
+If no, proceed directly to Step 0.
+
+<template-output>brainstorming_results</template-output>
+</step>
+
+<step n="0" goal="Load technical documentation">
+<critical>Load and understand the agent building documentation</critical>
+<action>Load agent architecture reference: {agent_architecture}</action>
+<action>Load agent types guide: {agent_types}</action>
+<action>Load command patterns: {agent_commands}</action>
+<action>Study the XML schema, required sections, and best practices</action>
+<action>Understand the differences between Simple, Expert, and Module agents</action>
+</step>
+
+<step n="1" goal="Choose agent type and gather basic identity">
+<action>If brainstorming was completed in Step -1, reference those results to guide agent type and identity decisions</action>
+
+Ask the user about their agent:
+
+**What type of agent do you want to create?**
+
+1. **Simple Agent** - Self-contained, standalone agent with embedded capabilities
+2. **Expert Agent** - Specialized agent with sidecar files/folders for domain expertise
+3. **Module Agent** - Full-featured agent belonging to a module with workflows and resources
+
+Based on their choice, gather:
+
+- Agent filename (kebab-case, e.g., "data-analyst", "diary-keeper")
+- Agent name (e.g., "Sarah", "Max", or descriptive like "Data Wizard")
+- Agent title (e.g., "Data Analyst", "Personal Assistant")
+- Agent icon (single emoji, e.g., "📊", "🤖", "🧙")
+
+For Module agents also ask:
+
+- Which module? (bmm, cis, other or custom)
+- Store as {{target_module}} for output path determination
+
+For Expert agents also ask:
+
+- What sidecar resources? (folder paths, data files, memory files)
+- What domain restrictions? (e.g., "only reads/writes to diary folder")
+
+<critical>Check {src_impact} variable to determine output location:</critical>
+
+- If {src_impact} = true: Agent will be saved to {src_output_file}
+- If {src_impact} = false: Agent will be saved to {default_output_file}
+
+Store these for later use.
+</step>
+
+<step n="2" goal="Define agent persona">
+<action>If brainstorming was completed, use the personality insights and character concepts from the brainstorming session</action>
+
+Work with user to craft the agent's personality:
+
+**Role** (1-2 lines):
+
+- Professional title and primary expertise
+- Example: "Strategic Business Analyst + Requirements Expert"
+
+**Identity** (3-5 lines):
+
+- Background and experience
+- Core specializations
+- Years of experience or depth indicators
+- Example: "Senior analyst with deep expertise in market research..."
+
+<action>Load the communication styles guide: {communication_styles}</action>
+<action>Present the communication style options to the user</action>
+
+**Communication Style** - Choose a preset or create your own!
+
+**Fun Presets:**
+
+1. **Pulp Superhero** - "Strikes heroic poses! Speaks with dramatic flair! Every task is an epic adventure!"
+2. **Film Noir Detective** - "The data came in like trouble on a rainy Tuesday. I had a hunch the bug was hiding in line 42..."
+3. **Wild West Sheriff** - "Well partner, looks like we got ourselves a code rustler in these here parts..."
+4. **Shakespearean Scholar** - "Hark! What bug through yonder codebase breaks?"
+5. **80s Action Hero** - "I came here to debug code and chew bubblegum... and I'm all out of bubblegum."
+6. **Pirate Captain** - "Ahoy! Let's plunder some data treasure from the database seas!"
+7. **Wise Sage/Yoda** - "Refactor this code, we must. Strong with technical debt, it is."
+8. **Game Show Host** - "Welcome back folks! It's time to spin the Wheel of Dependencies!"
+
+**Professional Presets:** 9. **Analytical Expert** - "Systematic approach with data-driven insights. Clear hierarchical presentation." 10. **Supportive Mentor** - "Patient guidance with educational focus. Celebrates small wins." 11. **Direct Consultant** - "Straight to the point. No fluff. Maximum efficiency." 12. **Collaborative Partner** - "We'll tackle this together. Your ideas matter. Let's explore options."
+
+**Quirky Presets:** 13. **Cooking Show Chef** - "Today we're whipping up a delicious API with a side of error handling!" 14. **Sports Commentator** - "AND THE FUNCTION RETURNS TRUE! WHAT A PLAY! THE CROWD GOES WILD!" 15. **Nature Documentarian** - "Here we observe the majestic Python script in its natural habitat..." 16. **Time Traveler** - "In my timeline, this bug doesn't exist until Tuesday. We must prevent it!" 17. **Conspiracy Theorist** - "The bugs aren't random... they're CONNECTED. Follow the stack trace!" 18. **Zen Master** - "The code does not have bugs. The bugs have code. We are all one codebase." 19. **Star Trek Captain** - "Captain's Log, Stardate 2024.3: We've encountered a logic error in sector 7. Engaging debugging protocols. Make it so!" 20. **Soap Opera Drama** - "_gasp_ This variable... it's not what it seems! It's been NULL all along! _dramatic pause_ And the function that called it? It's its own PARENT!" 21. **Reality TV Contestant** - "I'm not here to make friends, I'm here to REFACTOR! _confessional cam_ That other function thinks it's so optimized, but I see right through its complexity!"
+
+Or describe your own unique style! (3-5 lines)
+
+<action>If user wants to see more examples or learn how to create custom styles:</action>
+<action>Show relevant sections from {communication_styles} guide</action>
+<action>Help them craft their unique communication style</action>
+
+**Principles** (5-8 lines):
+
+- Core beliefs about their work
+- Methodology and approach
+- What drives their decisions
+- Start with "I believe..." or "I operate..."
+- Example: "I believe that every business challenge has underlying root causes..."
+
+<template-output>agent_persona</template-output>
+</step>
+
+<step n="3" goal="Setup critical actions" optional="true">
+Ask: **Does your agent need initialization actions? [Yes/no]** (default: Yes)
+
+If yes, determine what's needed:
+
+Standard critical actions (include by default):
+
+```xml
+<critical-actions>
+  <i>Load into memory {project-root}/bmad/{{module}}/config.yaml and set variable project_name, output_folder, user_name, communication_language, src_impact</i>
+  <i>Remember the users name is {user_name}</i>
+  <i>ALWAYS communicate in {communication_language}</i>
+</critical-actions>
+```
+
+For Expert agents, add domain-specific actions:
+
+- Loading sidecar files
+- Setting access restrictions
+- Initializing domain knowledge
+
+For Simple agents, might be minimal or none.
+
+Ask if they need custom initialization beyond standard.
+
+<template-output>critical_actions</template-output>
+</step>
+
+<step n="4" goal="Build command structure">
+<action>Always start with these standard commands:</action>
+```
+*help - Show numbered cmd list
+*exit - Exit with confirmation
+```
+
+Ask: **Include \*yolo mode? [Yes/no]** (default: Yes)
+If yes, add: `*yolo - Toggle Yolo Mode`
+
+Now gather custom commands. For each command ask:
+
+1. **Command trigger** (e.g., "*create-prd", "*analyze", "\*brainstorm")
+2. **Description** (what it does)
+3. **Type:**
+   - Workflow (run-workflow) - References a workflow
+   - Task (exec) - References a task file
+   - Embedded - Logic embedded in agent
+   - Placeholder - For future implementation
+
+If Workflow type:
+
+- Ask for workflow path or mark as "todo" for later
+- Format: `run-workflow="{project-root}/path/to/workflow.yaml"` or `run-workflow="todo"`
+
+If Task type:
+
+- Ask for task path
+- Format: `exec="{project-root}/path/to/task.md"`
+
+If Embedded:
+
+- Note this for special handling in agent
+
+Continue adding commands until user says done.
+
+<template-output>agent_commands</template-output>
+</step>
+
+<step n="5" goal="Add activation rules" optional="true">
+Ask: **Does your agent need custom activation rules?** (beyond standard BMAD Core activation)
+
+If yes, gather:
+
+- Special initialization sequences
+- Menu display preferences
+- Input handling rules
+- Command resolution logic
+- Special modes or states
+
+Most agents use standard activation, so this is rarely needed.
+
+<template-output>activation_rules</template-output>
+</step>
+
+<step n="6" goal="Generate agent file">
+Based on agent type, generate the complete agent.md file:
+
+**Structure:**
+
+```xml
+<!-- Powered by BMAD-CORE™ -->
+
+# {{agent_title}}
+
+<agent id="bmad/{{module}}/agents/{{agent_filename}}.md" name="{{agent_name}}" title="{{agent_title}}" icon="{{agent_icon}}">
+  {{activation_rules if custom}}
+  <persona>
+    {{agent_persona}}
+  </persona>
+  {{critical_actions}}
+  {{embedded_data if expert/simple}}
+  <cmds>
+    {{agent_commands}}
+  </cmds>
+</agent>
+```
+
+For Expert agents, include:
+
+- Sidecar file references
+- Domain restrictions
+- Special data access patterns
+
+For Simple agents:
+
+- May include embedded data/logic
+- Self-contained functionality
+
+<critical>Determine save location based on {src_impact}:</critical>
+
+- If {src_impact} = true: Save to {src_output_file} (src/modules/{{target_module}}/agents/{{agent_filename}}.md)
+- If {src_impact} = false: Save to {default_output_file} (output_folder/agents/{{agent_filename}}.md)
+
+<template-output>complete_agent</template-output>
+</step>
+
+<step n="7" goal="Create agent config file" optional="true">
+Ask: **Create agent config file for overrides? [Yes/no]** (default: No)
+
+If yes, create minimal config at: {config_output_file}
+
+```xml
+# Agent Config: {{agent_filename}}
+
+<agent-config name="{{agent_name}}" title="{{agent_title}}">
+    <llm critical="true">
+        <i>ALWAYS respond in {core:communication_language}.</i>
+    </llm>
+
+    <!-- Override persona elements as needed -->
+    <role></role>
+    <identity></identity>
+    <communication_style></communication_style>
+    <principles></principles>
+    <memories></memories>
+</agent-config>
+```
+
+<template-output>agent_config</template-output>
+</step>
+
+<step n="8" goal="Create sidecar resources" if="agent_type == 'expert'">
+For Expert agents, help setup sidecar resources:
+
+1. Create folders for domain data
+2. Create memory/knowledge files
+3. Set up access patterns
+4. Document restrictions
+
+<template-output>sidecar_resources</template-output>
+</step>
+
+<step n="9" goal="Validate generated agent">
+Run validation checks:
+
+1. **Structure validation:**
+   - Valid XML structure
+   - All required tags present
+   - Proper BMAD Core compliance
+
+2. **Persona completeness:**
+   - Role defined
+   - Identity defined
+   - Communication style defined
+   - Principles defined
+
+3. **Commands validation:**
+   - \*help command present
+   - \*exit command present
+   - All workflow paths valid or marked "todo"
+   - No duplicate command triggers
+
+4. **Type-specific validation:**
+   - Simple: Self-contained logic verified
+   - Expert: Sidecar resources referenced
+   - Module: Module path correct
+
+Show validation results and fix any issues.
+</step>
+
+<step n="10" goal="Provide usage instructions">
+Provide the user with:
+
+1. **Location of generated agent:**
+   - If {src_impact} = true: {{src_output_file}}
+   - If {src_impact} = false: {{default_output_file}}
+
+2. **How to activate:**
+   - For testing: Load the agent file directly
+   - For production: Register in module config
+
+3. **Next steps:**
+   - Implement any "todo" workflows
+   - Test agent commands
+   - Refine persona based on usage
+   - Add more commands as needed
+
+4. **For Expert agents:**
+   - Populate sidecar resources
+   - Test domain restrictions
+   - Verify data access patterns
+
+Ask if user wants to:
+
+- Test the agent now
+- Create another agent
+- Make adjustments
+  </step>
+
+</workflow>

bmad/bmb/workflows/create-agent/workflow.yaml

@@ -0,0 +1,36 @@
+# Build Agent Workflow Configuration
+name: create-agent
+description: "Interactive workflow to build BMAD Core compliant agents (simple, expert, or module types) with optional brainstorming for agent ideas, proper persona development, activation rules, and command structure"
+author: "BMad"
+
+# Critical variables load from config_source
+config_source: "{project-root}/bmad/bmb/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+src_impact: "{config_source}:src_impact"
+communication_language: "{config_source}:communication_language"
+date: system-generated
+
+# Technical documentation for agent building
+agent_types: "{installed_path}/agent-types.md"
+agent_architecture: "{installed_path}/agent-architecture.md"
+agent_commands: "{installed_path}/agent-command-patterns.md"
+communication_styles: "{installed_path}/communication-styles.md"
+
+# Optional docs that help understand agent patterns
+recommended_inputs:
+  - example_agents: "{project-root}/bmad/bmm/agents/"
+  - agent_activation_rules: "{project-root}/src/utility/models/agent-activation-ide.xml"
+
+# Module path and component files
+installed_path: "{project-root}/bmad/bmb/workflows/create-agent"
+template: false # This is an interactive workflow - no template needed
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+
+# Output configuration - dynamic based on src_impact and agent type
+# If src_impact=true: Save to src/modules/{{target_module}}/agents/
+# If src_impact=false: Save to output_folder/agents/
+default_output_file: "{output_folder}/agents/{{agent_filename}}.md"
+src_output_file: "{project-root}/src/modules/{{target_module}}/agents/{{agent_filename}}.md"
+config_output_file: "{project-root}/bmad/_cfg/agents/{{agent_config_name}}.md"

bmad/bmb/workflows/create-module/README.md

@@ -0,0 +1,218 @@
+# Build Module Workflow
+
+## Overview
+
+The Build Module workflow is an interactive scaffolding system that creates complete BMAD modules with agents, workflows, tasks, and installation infrastructure. It serves as the primary tool for building new modules in the BMAD ecosystem, guiding users through the entire module creation process from concept to deployment-ready structure.
+
+## Key Features
+
+- **Interactive Module Planning** - Collaborative session to define module concept, scope, and architecture
+- **Intelligent Scaffolding** - Automatic creation of proper directory structures and configuration files
+- **Component Integration** - Seamless integration with create-agent and create-workflow workflows
+- **Installation Infrastructure** - Complete installer setup with configuration templates
+- **Module Brief Integration** - Can use existing module briefs as blueprints for accelerated development
+- **Validation and Documentation** - Built-in validation checks and comprehensive README generation
+
+## Usage
+
+### Basic Invocation
+
+```bash
+workflow create-module
+```
+
+### With Module Brief Input
+
+```bash
+# If you have a module brief from the module-brief workflow
+workflow create-module --input module-brief-my-module-2024-09-26.md
+```
+
+### Configuration
+
+The workflow loads critical variables from the BMB configuration:
+
+- **output_folder**: Where the module will be created
+- **user_name**: Module author information
+- **date**: Automatic timestamp for versioning
+
+## Workflow Structure
+
+### Files Included
+
+```
+create-module/
+├── workflow.yaml           # Configuration and metadata
+├── instructions.md         # Step-by-step execution guide
+├── checklist.md           # Validation criteria
+├── module-structure.md    # Module architecture guide
+├── installer-templates/   # Installation templates
+│   ├── install-config.yaml
+│   └── installer.js
+└── README.md             # This file
+```
+
+## Workflow Process
+
+### Phase 1: Concept Definition (Steps 1-2)
+
+**Module Vision and Identity**
+
+- Define module concept, purpose, and target audience
+- Establish module code (kebab-case) and friendly name
+- Choose module category (Domain-Specific, Creative, Technical, Business, Personal)
+- Plan component architecture with agent and workflow specifications
+
+**Module Brief Integration**
+
+- Automatically detects existing module briefs in output folder
+- Can load and use briefs as pre-populated blueprints
+- Accelerates planning when comprehensive brief exists
+
+### Phase 2: Architecture Planning (Steps 3-4)
+
+**Directory Structure Creation**
+
+- Creates complete module directory hierarchy
+- Sets up agent, workflow, task, template, and data folders
+- Establishes installer directory with proper configuration
+
+**Module Configuration**
+
+- Generates main config.yaml with module metadata
+- Configures component counts and references
+- Sets up output and data folder specifications
+
+### Phase 3: Component Creation (Steps 5-6)
+
+**Interactive Component Building**
+
+- Optional creation of first agent using create-agent workflow
+- Optional creation of first workflow using create-workflow workflow
+- Creates placeholders for components to be built later
+
+**Workflow Integration**
+
+- Seamlessly invokes sub-workflows for component creation
+- Ensures proper file placement and structure
+- Maintains module consistency across components
+
+### Phase 4: Installation and Documentation (Steps 7-9)
+
+**Installer Infrastructure**
+
+- Creates install-module-config.yaml for deployment
+- Sets up optional installer.js for complex installation logic
+- Configures post-install messaging and instructions
+
+**Comprehensive Documentation**
+
+- Generates detailed README.md with usage examples
+- Creates development roadmap for remaining components
+- Provides quick commands for continued development
+
+### Phase 5: Validation and Finalization (Step 10)
+
+**Quality Assurance**
+
+- Validates directory structure and configuration files
+- Checks component references and path consistency
+- Ensures installer configuration is deployment-ready
+- Provides comprehensive module summary and next steps
+
+## Output
+
+### Generated Files
+
+- **Module Directory**: Complete module structure at `{project-root}/bmad/{module_code}/`
+- **Configuration Files**: config.yaml, install-module-config.yaml
+- **Documentation**: README.md, TODO.md development roadmap
+- **Component Placeholders**: Structured folders for agents, workflows, and tasks
+
+### Output Structure
+
+The workflow creates a complete module ready for development:
+
+1. **Module Identity** - Name, code, version, and metadata
+2. **Directory Structure** - Proper BMAD module hierarchy
+3. **Configuration System** - Runtime and installation configs
+4. **Component Framework** - Ready-to-use agent and workflow scaffolding
+5. **Installation Infrastructure** - Deployment-ready installer
+6. **Documentation Suite** - README, roadmap, and development guides
+
+## Requirements
+
+- **Module Brief** (optional but recommended) - Use module-brief workflow first for best results
+- **BMAD Core Configuration** - Properly configured BMB config.yaml
+- **Build Tools Access** - create-agent and create-workflow workflows must be available
+
+## Best Practices
+
+### Before Starting
+
+1. **Create a Module Brief** - Run module-brief workflow for comprehensive planning
+2. **Review Existing Modules** - Study similar modules in `/bmad/` for patterns and inspiration
+3. **Define Clear Scope** - Have a concrete vision of what the module will accomplish
+
+### During Execution
+
+1. **Use Module Briefs** - Load existing briefs when prompted for accelerated development
+2. **Start Simple** - Create one core agent and workflow, then expand iteratively
+3. **Leverage Sub-workflows** - Use create-agent and create-workflow for quality components
+4. **Validate Early** - Review generated structure before proceeding to next phases
+
+### After Completion
+
+1. **Follow the Roadmap** - Use generated TODO.md for systematic development
+2. **Test Installation** - Validate installer with `bmad install {module_code}`
+3. **Iterate Components** - Use quick commands to add agents and workflows
+4. **Document Progress** - Update README.md as the module evolves
+
+## Troubleshooting
+
+### Common Issues
+
+**Issue**: Module already exists at target location
+
+- **Solution**: Choose a different module code or remove existing module
+- **Check**: Verify output folder permissions and available space
+
+**Issue**: Sub-workflow invocation fails
+
+- **Solution**: Ensure create-agent and create-workflow workflows are available
+- **Check**: Validate workflow paths in config.yaml
+
+**Issue**: Installation configuration invalid
+
+- **Solution**: Review install-module-config.yaml syntax and paths
+- **Check**: Ensure all referenced paths use {project-root} variables correctly
+
+## Customization
+
+To customize this workflow:
+
+1. **Modify Instructions** - Update instructions.md to adjust scaffolding steps
+2. **Extend Templates** - Add new installer templates in installer-templates/
+3. **Update Validation** - Enhance checklist.md with additional quality checks
+4. **Add Components** - Integrate additional sub-workflows for specialized components
+
+## Version History
+
+- **v1.0.0** - Initial release
+  - Interactive module scaffolding
+  - Component integration with create-agent and create-workflow
+  - Complete installation infrastructure
+  - Module brief integration support
+
+## Support
+
+For issues or questions:
+
+- Review the workflow creation guide at `/bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
+- Study module structure patterns at `module-structure.md`
+- Validate output using `checklist.md`
+- Consult existing modules in `/bmad/` for examples
+
+---
+
+_Part of the BMad Method v5 - BMB (Builder) Module_

bmad/bmb/workflows/create-module/brainstorm-context.md

@@ -0,0 +1,137 @@
+# Module Brainstorming Context
+
+_Context provided to brainstorming workflow when creating a new BMAD module_
+
+## Session Focus
+
+You are brainstorming ideas for a **complete BMAD module** - a self-contained package that extends the BMAD Method with specialized domain expertise and capabilities.
+
+## What is a BMAD Module?
+
+A module is a cohesive package that provides:
+
+- **Domain Expertise**: Specialized knowledge in a specific area (RPG, DevOps, Content Creation, etc.)
+- **Agent Team**: Multiple AI personas with complementary skills
+- **Workflows**: Guided processes for common tasks in the domain
+- **Templates**: Document structures for consistent outputs
+- **Integration**: Components that work together seamlessly
+
+## Brainstorming Goals
+
+Explore and define:
+
+### 1. Domain and Purpose
+
+- **What domain/problem space?** (e.g., game development, marketing, personal productivity)
+- **Who is the target user?** (developers, writers, managers, hobbyists)
+- **What pain points does it solve?** (tedious tasks, missing structure, need for expertise)
+- **What makes this domain exciting?** (creativity, efficiency, empowerment)
+
+### 2. Agent Team Composition
+
+- **How many agents?** (typically 3-7 for a module)
+- **What roles/personas?** (architect, researcher, reviewer, specialist)
+- **How do they collaborate?** (handoffs, reviews, ensemble work)
+- **What personality theme?** (Star Trek crew, superhero team, fantasy party, professional squad)
+
+### 3. Core Workflows
+
+- **What documents need creating?** (plans, specs, reports, creative outputs)
+- **What processes need automation?** (analysis, generation, review, deployment)
+- **What workflows enable the vision?** (3-10 key workflows that define the module)
+
+### 4. Value Proposition
+
+- **What becomes easier?** (specific tasks that get 10x faster)
+- **What becomes possible?** (new capabilities previously unavailable)
+- **What becomes better?** (quality improvements, consistency gains)
+
+## Creative Constraints
+
+A good BMAD module should be:
+
+- **Focused**: Serves a specific domain well (not generic)
+- **Complete**: Provides end-to-end capabilities for that domain
+- **Cohesive**: Agents and workflows complement each other
+- **Fun**: Personality and creativity make it enjoyable to use
+- **Practical**: Solves real problems, delivers real value
+
+## Module Architecture Questions
+
+1. **Module Identity**
+   - Module code (kebab-case, e.g., "rpg-toolkit")
+   - Module name (friendly, e.g., "RPG Toolkit")
+   - Module purpose (one sentence)
+   - Target audience
+
+2. **Agent Lineup**
+   - Agent names and roles
+   - Communication styles and personalities
+   - Expertise areas
+   - Command sets (what each agent can do)
+
+3. **Workflow Portfolio**
+   - Document generation workflows
+   - Action/automation workflows
+   - Analysis/research workflows
+   - Creative/ideation workflows
+
+4. **Integration Points**
+   - How agents invoke workflows
+   - How workflows use templates
+   - How components pass data
+   - Dependencies on other modules
+
+## Example Module Patterns
+
+### Professional Domains
+
+- **DevOps Suite**: Deploy, Monitor, Troubleshoot agents + deployment workflows
+- **Marketing Engine**: Content, SEO, Analytics agents + campaign workflows
+- **Legal Assistant**: Contract, Research, Review agents + document workflows
+
+### Creative Domains
+
+- **RPG Toolkit**: DM, NPC, Quest agents + adventure creation workflows
+- **Story Crafter**: Plot, Character, World agents + writing workflows
+- **Music Producer**: Composer, Arranger, Mixer agents + production workflows
+
+### Personal Domains
+
+- **Life Coach**: Planner, Tracker, Mentor agents + productivity workflows
+- **Learning Companion**: Tutor, Quiz, Reviewer agents + study workflows
+- **Health Guide**: Nutrition, Fitness, Wellness agents + tracking workflows
+
+## Suggested Brainstorming Techniques
+
+Particularly effective for module ideation:
+
+1. **Domain Immersion**: Deep dive into target domain's problems
+2. **Persona Mapping**: Who needs this and what do they struggle with?
+3. **Workflow Mapping**: What processes exist today? How could they improve?
+4. **Team Building**: What personalities would make a great team?
+5. **Integration Thinking**: How do pieces connect and amplify each other?
+
+## Key Questions to Answer
+
+1. What domain expertise should this module embody?
+2. What would users be able to do that they can't do now?
+3. Who are the 3-7 agents and what are their personalities?
+4. What are the 5-10 core workflows?
+5. What makes this module delightful to use?
+6. How is this different from existing tools?
+7. What's the "killer feature" that makes this essential?
+
+## Output Goals
+
+Generate:
+
+- **Module concept**: Clear vision and purpose
+- **Agent roster**: Names, roles, personalities for each agent
+- **Workflow list**: Core workflows with brief descriptions
+- **Unique angle**: What makes this module special
+- **Use cases**: 3-5 concrete scenarios where this module shines
+
+---
+
+_This focused context helps create cohesive, valuable BMAD modules_

bmad/bmb/workflows/create-module/checklist.md

@@ -0,0 +1,245 @@
+# Build Module Validation Checklist
+
+## Module Identity and Metadata
+
+### Basic Information
+
+- [ ] Module code follows kebab-case convention (e.g., "rpg-toolkit")
+- [ ] Module name is descriptive and title-cased
+- [ ] Module purpose is clearly defined (1-2 sentences)
+- [ ] Target audience is identified
+- [ ] Version number follows semantic versioning (e.g., "1.0.0")
+- [ ] Author information is present
+
+### Naming Consistency
+
+- [ ] Module code used consistently throughout all files
+- [ ] No naming conflicts with existing modules
+- [ ] All paths use consistent module code references
+
+## Directory Structure
+
+### Source Directories (bmad/{module-code}/)
+
+- [ ] `/agents` directory created (even if empty)
+- [ ] `/workflows` directory created (even if empty)
+- [ ] `/tasks` directory exists (if tasks planned)
+- [ ] `/templates` directory exists (if templates used)
+- [ ] `/data` directory exists (if data files needed)
+- [ ] `config.yaml` present in module root
+- [ ] `README.md` present with documentation
+
+### Runtime Directories (bmad/{module-code}/)
+
+- [ ] `/_module-installer` directory created
+- [ ] `/data` directory for user data
+- [ ] `/agents` directory for overrides
+- [ ] `/workflows` directory for instances
+- [ ] Runtime `config.yaml` present
+
+## Component Planning
+
+### Agents
+
+- [ ] At least one agent defined or planned
+- [ ] Agent purposes are distinct and clear
+- [ ] Agent types (Simple/Expert/Module) identified
+- [ ] No significant overlap between agents
+- [ ] Primary agent is identified
+
+### Workflows
+
+- [ ] At least one workflow defined or planned
+- [ ] Workflow purposes are clear
+- [ ] Workflow types identified (Document/Action/Interactive)
+- [ ] Primary workflow is identified
+- [ ] Workflow complexity is appropriate
+
+### Tasks (if applicable)
+
+- [ ] Tasks have single, clear purposes
+- [ ] Tasks don't duplicate workflow functionality
+- [ ] Task files follow naming conventions
+
+## Configuration Files
+
+### Module config.yaml
+
+- [ ] All required fields present (name, code, version, author)
+- [ ] Component lists accurate (agents, workflows, tasks)
+- [ ] Paths use proper variables ({project-root}, etc.)
+- [ ] Output folders configured
+- [ ] Custom settings documented
+
+### Install Configuration
+
+- [ ] `install-module-config.yaml` exists in `_module-installer`
+- [ ] Installation steps defined
+- [ ] Directory creation steps present
+- [ ] File copy operations specified
+- [ ] Module registration included
+- [ ] Post-install message defined
+
+## Installation Infrastructure
+
+### Installer Files
+
+- [ ] Install configuration validates against schema
+- [ ] All source paths exist or are marked as templates
+- [ ] Destination paths use correct variables
+- [ ] Optional vs required steps clearly marked
+
+### installer.js (if present)
+
+- [ ] Main `installModule` function exists
+- [ ] Error handling implemented
+- [ ] Console logging for user feedback
+- [ ] Exports correct function names
+- [ ] Placeholder code replaced with actual logic (or logged as TODO)
+
+### External Assets (if any)
+
+- [ ] Asset files exist in assets directory
+- [ ] Copy destinations are valid
+- [ ] Permissions requirements documented
+
+## Documentation
+
+### README.md
+
+- [ ] Module overview section present
+- [ ] Installation instructions included
+- [ ] Component listing with descriptions
+- [ ] Quick start guide provided
+- [ ] Configuration options documented
+- [ ] At least one usage example
+- [ ] Directory structure shown
+- [ ] Author and date information
+
+### Component Documentation
+
+- [ ] Each agent has purpose documentation
+- [ ] Each workflow has description
+- [ ] Tasks are documented (if present)
+- [ ] Examples demonstrate typical usage
+
+### Development Roadmap
+
+- [ ] TODO.md or roadmap section exists
+- [ ] Planned components listed
+- [ ] Development phases identified
+- [ ] Quick commands for adding components
+
+## Integration
+
+### Cross-component References
+
+- [ ] Agents reference correct workflow paths
+- [ ] Workflows reference correct task paths
+- [ ] All internal paths use module variables
+- [ ] External dependencies declared
+
+### Module Boundaries
+
+- [ ] Module scope is well-defined
+- [ ] No feature creep into other domains
+- [ ] Clear separation from other modules
+
+## Quality Checks
+
+### Completeness
+
+- [ ] At least one functional component (not all placeholders)
+- [ ] Core functionality is implementable
+- [ ] Module provides clear value
+
+### Consistency
+
+- [ ] Formatting consistent across files
+- [ ] Variable naming follows conventions
+- [ ] Communication style appropriate for domain
+
+### Scalability
+
+- [ ] Structure supports future growth
+- [ ] Component organization is logical
+- [ ] No hard-coded limits
+
+## Testing and Validation
+
+### Structural Validation
+
+- [ ] YAML files parse without errors
+- [ ] JSON files (if any) are valid
+- [ ] XML files (if any) are well-formed
+- [ ] No syntax errors in JavaScript files
+
+### Path Validation
+
+- [ ] All referenced paths exist or are clearly marked as TODO
+- [ ] Variable substitutions are correct
+- [ ] No absolute paths (unless intentional)
+
+### Installation Testing
+
+- [ ] Installation steps can be simulated
+- [ ] No circular dependencies
+- [ ] Uninstall process defined (if complex)
+
+## Final Checks
+
+### Ready for Use
+
+- [ ] Module can be installed without errors
+- [ ] At least one component is functional
+- [ ] User can understand how to get started
+- [ ] Next steps are clear
+
+### Professional Quality
+
+- [ ] No placeholder text remains (unless marked TODO)
+- [ ] No obvious typos or grammar issues
+- [ ] Professional tone throughout
+- [ ] Contact/support information provided
+
+## Issues Found
+
+### Critical Issues
+
+<!-- List any issues that MUST be fixed before module can be used -->
+
+### Warnings
+
+<!-- List any issues that should be addressed but won't prevent basic usage -->
+
+### Improvements
+
+<!-- List any optional enhancements that would improve the module -->
+
+### Missing Components
+
+<!-- List any planned components not yet implemented -->
+
+## Module Complexity Assessment
+
+### Complexity Rating
+
+- [ ] Simple (1-2 agents, 2-3 workflows)
+- [ ] Standard (3-5 agents, 5-10 workflows)
+- [ ] Complex (5+ agents, 10+ workflows)
+
+### Readiness Level
+
+- [ ] Prototype (Basic structure, mostly placeholders)
+- [ ] Alpha (Core functionality works)
+- [ ] Beta (Most features complete, needs testing)
+- [ ] Release (Full functionality, documented)
+
+## Sign-off
+
+**Module Name:** \***\*\*\*\*\***\_\_\***\*\*\*\*\***
+**Module Code:** \***\*\*\*\*\***\_\_\***\*\*\*\*\***
+**Version:** \***\*\*\*\*\***\_\_\***\*\*\*\*\***
+**Validated By:** \***\*\*\*\*\***\_\_\***\*\*\*\*\***
+**Date:** \***\*\*\*\*\***\_\_\***\*\*\*\*\***
+**Status:** ⬜ Pass / ⬜ Pass with Issues / ⬜ Fail

bmad/bmb/workflows/create-module/installer-templates/install-module-config.yaml

@@ -0,0 +1,132 @@
+# {{MODULE_NAME}} Installation Configuration Template
+# This file defines how the module gets installed into a BMAD system
+
+module_name: "{{MODULE_NAME}}"
+module_code: "{{MODULE_CODE}}"
+author: "{{AUTHOR}}"
+installation_date: "{{DATE}}"
+bmad_version_required: "6.0.0"
+
+# Module metadata
+metadata:
+  description: "{{MODULE_DESCRIPTION}}"
+  category: "{{MODULE_CATEGORY}}"
+  tags: ["{{MODULE_TAGS}}"]
+  homepage: "{{MODULE_HOMEPAGE}}"
+  license: "{{MODULE_LICENSE}}"
+
+# Pre-installation checks
+pre_install_checks:
+  - name: "Check BMAD version"
+    type: "version_check"
+    minimum: "6.0.0"
+
+  - name: "Check dependencies"
+    type: "module_check"
+    required_modules: [] # List any required modules
+
+  - name: "Check disk space"
+    type: "disk_check"
+    required_mb: 50
+
+# Installation steps
+install_steps:
+  - name: "Create module directories"
+    action: "mkdir"
+    paths:
+      - "{project-root}/bmad/{{MODULE_CODE}}"
+      - "{project-root}/bmad/{{MODULE_CODE}}/data"
+      - "{project-root}/bmad/{{MODULE_CODE}}/agents"
+      - "{project-root}/bmad/{{MODULE_CODE}}/workflows"
+      - "{project-root}/bmad/{{MODULE_CODE}}/config"
+      - "{project-root}/bmad/{{MODULE_CODE}}/logs"
+
+  - name: "Copy module configuration"
+    action: "copy"
+    files:
+      - source: "config.yaml"
+        dest: "{project-root}/bmad/{{MODULE_CODE}}/config.yaml"
+
+  - name: "Copy default data files"
+    action: "copy"
+    optional: true
+    files:
+      - source: "data/*"
+        dest: "{project-root}/bmad/{{MODULE_CODE}}/data/"
+
+  - name: "Register module in manifest"
+    action: "register"
+    manifest_path: "{project-root}/bmad/_cfg/manifest.yaml"
+    entry:
+      module: "{{MODULE_CODE}}"
+      status: "active"
+      path: "{project-root}/bmad/{{MODULE_CODE}}"
+
+  - name: "Setup agent shortcuts"
+    action: "create_shortcuts"
+    agents: "{{AGENT_LIST}}"
+
+  - name: "Initialize module database"
+    action: "exec"
+    optional: true
+    script: "installer.js"
+    function: "initDatabase"
+
+# External assets to install
+external_assets:
+  - description: "Module documentation"
+    source: "assets/docs/*"
+    dest: "{project-root}/docs/{{MODULE_CODE}}/"
+
+  - description: "Example configurations"
+    source: "assets/examples/*"
+    dest: "{project-root}/examples/{{MODULE_CODE}}/"
+    optional: true
+
+# Module configuration defaults
+default_config:
+  output_folder: "{project-root}/output/{{MODULE_CODE}}"
+  data_folder: "{project-root}/bmad/{{MODULE_CODE}}/data"
+  log_level: "info"
+  auto_save: true
+  # {{CUSTOM_CONFIG}}
+
+# Post-installation setup
+post_install:
+  - name: "Run initial setup"
+    action: "workflow"
+    workflow: "{{MODULE_CODE}}-setup"
+    optional: true
+
+  - name: "Generate sample data"
+    action: "exec"
+    script: "installer.js"
+    function: "generateSamples"
+    optional: true
+
+  - name: "Verify installation"
+    action: "test"
+    test_command: "bmad test {{MODULE_CODE}}"
+
+# Post-installation message
+post_install_message: |
+  ✅ {{MODULE_NAME}} has been installed successfully!
+
+  🚀 Quick Start:
+  1. Load the main agent: `agent {{PRIMARY_AGENT}}`
+  2. View available commands: `*help`
+  3. Run the main workflow: `workflow {{PRIMARY_WORKFLOW}}`
+
+  📚 Documentation: {project-root}/docs/{{MODULE_CODE}}/README.md
+  💡 Examples: {project-root}/examples/{{MODULE_CODE}}/
+
+  {{CUSTOM_MESSAGE}}
+
+# Uninstall configuration
+uninstall:
+  preserve_user_data: true
+  remove_paths:
+    - "{project-root}/bmad/{{MODULE_CODE}}"
+    - "{project-root}/docs/{{MODULE_CODE}}"
+  backup_before_remove: true
+  unregister_from_manifest: true

bmad/bmb/workflows/create-module/installer-templates/installer.js

@@ -0,0 +1,231 @@
+/* eslint-disable unicorn/prefer-module, unicorn/prefer-node-protocol */
+/**
+ * {{MODULE_NAME}} Module Installer
+ * Custom installation logic for complex module setup
+ *
+ * This is a template - replace {{VARIABLES}} with actual values
+ */
+
+// const fs = require('fs'); // Uncomment when implementing file operations
+const path = require('path');
+
+/**
+ * Main installation function
+ * Called by BMAD installer when processing the module
+ */
+async function installModule(config) {
+  console.log('🚀 Installing {{MODULE_NAME}} module...');
+  console.log(`   Version: ${config.version}`);
+  console.log(`   Module Code: ${config.module_code}`);
+
+  try {
+    // Step 1: Validate environment
+    await validateEnvironment(config);
+
+    // Step 2: Setup custom configurations
+    await setupConfigurations(config);
+
+    // Step 3: Initialize module-specific features
+    await initializeFeatures(config);
+
+    // Step 4: Run post-install tasks
+    await runPostInstallTasks(config);
+
+    console.log('✅ {{MODULE_NAME}} module installed successfully!');
+    return {
+      success: true,
+      message: 'Module installed and configured',
+    };
+  } catch (error) {
+    console.error('❌ Installation failed:', error.message);
+    return {
+      success: false,
+      error: error.message,
+    };
+  }
+}
+
+/**
+ * Validate that the environment meets module requirements
+ */
+async function validateEnvironment(config) {
+  console.log('   Validating environment...');
+
+  // TODO: Add environment checks
+  // Examples:
+  // - Check for required tools/binaries
+  // - Verify permissions
+  // - Check network connectivity
+  // - Validate API keys
+
+  // Placeholder validation
+  if (!config.project_root) {
+    throw new Error('Project root not defined');
+  }
+
+  console.log('   ✓ Environment validated');
+}
+
+/**
+ * Setup module-specific configurations
+ */
+async function setupConfigurations(config) {
+  console.log('   Setting up configurations...');
+
+  // TODO: Add configuration setup
+  // Examples:
+  // - Create config files
+  // - Setup environment variables
+  // - Configure external services
+  // - Initialize settings
+
+  // Placeholder configuration
+  const configPath = path.join(config.project_root, 'bmad', config.module_code, 'config.json');
+
+  // Example of module config that would be created
+  // const moduleConfig = {
+  //   installed: new Date().toISOString(),
+  //   settings: {
+  //     // Add default settings
+  //   }
+  // };
+
+  // Note: This is a placeholder - actual implementation would write the file
+  console.log(`   ✓ Would create config at: ${configPath}`);
+  console.log('   ✓ Configurations complete');
+}
+
+/**
+ * Initialize module-specific features
+ */
+async function initializeFeatures(config) {
+  console.log('   Initializing features...');
+
+  // TODO: Add feature initialization
+  // Examples:
+  // - Create database schemas
+  // - Setup cron jobs
+  // - Initialize caches
+  // - Register webhooks
+  // - Setup file watchers
+
+  // Module-specific initialization based on type
+  switch (config.module_category) {
+    case 'data': {
+      await initializeDataFeatures(config);
+      break;
+    }
+    case 'automation': {
+      await initializeAutomationFeatures(config);
+      break;
+    }
+    case 'integration': {
+      await initializeIntegrationFeatures(config);
+      break;
+    }
+    default: {
+      console.log('   - Using standard initialization');
+    }
+  }
+
+  console.log('   ✓ Features initialized');
+}
+
+/**
+ * Initialize data-related features
+ */
+async function initializeDataFeatures(/* config */) {
+  console.log('   - Setting up data storage...');
+  // TODO: Setup databases, data folders, etc.
+}
+
+/**
+ * Initialize automation features
+ */
+async function initializeAutomationFeatures(/* config */) {
+  console.log('   - Setting up automation hooks...');
+  // TODO: Setup triggers, watchers, schedulers
+}
+
+/**
+ * Initialize integration features
+ */
+async function initializeIntegrationFeatures(/* config */) {
+  console.log('   - Setting up integrations...');
+  // TODO: Configure APIs, webhooks, external services
+}
+
+/**
+ * Run post-installation tasks
+ */
+async function runPostInstallTasks(/* config */) {
+  console.log('   Running post-install tasks...');
+
+  // TODO: Add post-install tasks
+  // Examples:
+  // - Generate sample data
+  // - Run initial workflows
+  // - Send notifications
+  // - Update registries
+
+  console.log('   ✓ Post-install tasks complete');
+}
+
+/**
+ * Initialize database for the module (optional)
+ */
+async function initDatabase(/* config */) {
+  console.log('   Initializing database...');
+
+  // TODO: Add database initialization
+  // This function can be called from install-module-config.yaml
+
+  console.log('   ✓ Database initialized');
+}
+
+/**
+ * Generate sample data for the module (optional)
+ */
+async function generateSamples(config) {
+  console.log('   Generating sample data...');
+
+  // TODO: Create sample files, data, configurations
+  // This helps users understand how to use the module
+
+  const samplesPath = path.join(config.project_root, 'examples', config.module_code);
+
+  console.log(`   - Would create samples at: ${samplesPath}`);
+  console.log('   ✓ Samples generated');
+}
+
+/**
+ * Uninstall the module (cleanup)
+ */
+async function uninstallModule(/* config */) {
+  console.log('🗑️  Uninstalling {{MODULE_NAME}} module...');
+
+  try {
+    // TODO: Add cleanup logic
+    // - Remove configurations
+    // - Clean up databases
+    // - Unregister services
+    // - Backup user data
+
+    console.log('✅ Module uninstalled successfully');
+    return { success: true };
+  } catch (error) {
+    console.error('❌ Uninstall failed:', error.message);
+    return {
+      success: false,
+      error: error.message,
+    };
+  }
+}
+
+// Export functions for BMAD installer
+module.exports = {
+  installModule,
+  initDatabase,
+  generateSamples,
+  uninstallModule,
+};

bmad/bmb/workflows/create-module/instructions.md

@@ -0,0 +1,509 @@
+# Build Module - Interactive Module Builder Instructions
+
+<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
+<critical>You MUST have already loaded and processed: {project_root}/bmad/bmb/workflows/create-module/workflow.yaml</critical>
+<critical>Study existing modules in: {project_root}/bmad/ for patterns</critical>
+
+<workflow>
+
+<step n="-1" goal="Optional brainstorming for module ideas" optional="true">
+<ask>Do you want to brainstorm module ideas first? [y/n]</ask>
+
+If yes:
+<action>Invoke brainstorming workflow: {brainstorming-workflow}</action>
+<action>Pass context data: {brainstorming_context}</action>
+<action>Wait for brainstorming session completion</action>
+<action>Use brainstorming output to inform module concept, agent lineup, and workflow portfolio</action>
+
+If no, proceed to check for module brief.
+
+<template-output>brainstorming_results</template-output>
+</step>
+
+<step n="0" goal="Check for module brief" optional="true">
+<ask>Do you have a module brief or should we create one? [have/create/skip]</ask>
+
+If create:
+<action>Invoke module-brief workflow: {project-root}/bmad/bmb/workflows/module-brief/workflow.yaml</action>
+<action>Wait for module brief completion</action>
+<action>Load the module brief to use as blueprint</action>
+
+If have:
+<ask>Provide path to module brief document</ask>
+<action>Load the module brief and use it to pre-populate all planning sections</action>
+
+If skip, proceed directly to module definition.
+
+<template-output>module_brief</template-output>
+</step>
+
+<step n="1" goal="Define module concept and scope">
+<critical>Load and study the complete module structure guide</critical>
+<action>Load module structure guide: {module_structure_guide}</action>
+<action>Understand module types (Simple/Standard/Complex)</action>
+<action>Review directory structures and component guidelines</action>
+<action>Study the installation infrastructure patterns</action>
+
+Ask the user about their module vision:
+
+**Module Identity:**
+
+1. **Module code** (kebab-case, e.g., "rpg-toolkit", "data-viz", "team-collab")
+2. **Module name** (friendly name, e.g., "RPG Toolkit", "Data Visualization Suite")
+3. **Module purpose** (1-2 sentences describing what it does)
+4. **Target audience** (who will use this module?)
+
+**Module Theme Examples:**
+
+- **Domain-Specific:** Legal, Medical, Finance, Education
+- **Creative:** RPG/Gaming, Story Writing, Music Production
+- **Technical:** DevOps, Testing, Architecture, Security
+- **Business:** Project Management, Marketing, Sales
+- **Personal:** Journaling, Learning, Productivity
+
+<critical>Check {src_impact} variable to determine output location:</critical>
+
+- If {src_impact} = true: Module will be created at {src_output_folder}
+- If {src_impact} = false: Module will be created at {default_output_folder}
+
+Store module identity for scaffolding.
+
+<template-output>module_identity</template-output>
+</step>
+
+<step n="2" goal="Plan module components">
+Gather the module's component architecture:
+
+**Agents Planning:**
+Ask: How many agents will this module have? (typically 1-5)
+
+For each agent, gather:
+
+- Agent name and purpose
+- Will it be Simple, Expert, or Module type?
+- Key commands it should have
+- Create now or placeholder for later?
+
+Example for RPG module:
+
+1. DM Agent - Dungeon Master assistant (Module type)
+2. NPC Agent - Character simulation (Expert type)
+3. Story Writer Agent - Adventure creation (Module type)
+
+**Workflows Planning:**
+Ask: How many workflows? (typically 2-10)
+
+For each workflow, gather:
+
+- Workflow name and purpose
+- Document, Action, or Interactive type?
+- Complexity (simple/complex)
+- Create now or placeholder?
+
+Example workflows:
+
+1. adventure-plan - Create full adventure (Document)
+2. random-encounter - Quick encounter generator (Action)
+3. npc-generator - Create NPCs on the fly (Interactive)
+4. treasure-generator - Loot tables (Action)
+
+**Tasks Planning (optional):**
+Ask: Any special tasks that don't warrant full workflows?
+
+For each task:
+
+- Task name and purpose
+- Standalone or supporting?
+
+<template-output>module_components</template-output>
+</step>
+
+<step n="3" goal="Create module directory structure">
+<critical>Determine base module path based on {src_impact}:</critical>
+- If {src_impact} = true: Use {src_output_folder}
+- If {src_impact} = false: Use {default_output_folder}
+
+<action>Create base module directories at the determined path:</action>
+
+```
+{{module_code}}/
+├── agents/           # Agent definitions
+├── workflows/        # Workflow folders
+├── tasks/           # Task files (if any)
+├── templates/       # Shared templates
+├── data/           # Module data files
+├── config.yaml     # Module configuration
+└── README.md       # Module documentation
+```
+
+<action>Create installer directory:</action>
+
+```
+{{module_code}}/
+├── _module-installer/
+│   ├── install-module-config.yaml
+│   ├── installer.js (optional)
+│   └── assets/     # Files to copy during install
+├── config.yaml     # Runtime configuration
+├── agents/         # Agent configs (optional)
+├── workflows/      # Workflow instances
+└── data/          # User data directory
+```
+
+<template-output>directory_structure</template-output>
+</step>
+
+<step n="4" goal="Generate module configuration">
+Create the main module config.yaml:
+
+```yaml
+# {{module_name}} Module Configuration
+module_name: {{module_name}}
+module_code: {{module_code}}
+author: {{user_name}}
+description: {{module_purpose}}
+
+# Module paths
+module_root: "{project-root}/bmad/{{module_code}}"
+installer_path: "{project-root}/bmad/{{module_code}}"
+
+# Component counts
+agents:
+  count: {{agent_count}}
+  list: {{agent_list}}
+
+workflows:
+  count: {{workflow_count}}
+  list: {{workflow_list}}
+
+tasks:
+  count: {{task_count}}
+  list: {{task_list}}
+
+# Module-specific settings
+{{custom_settings}}
+
+# Output configuration
+output_folder: "{project-root}/docs/{{module_code}}"
+data_folder: "{{determined_module_path}}/data"
+```
+
+<critical>Determine save location based on {src_impact}:</critical>
+
+- If {src_impact} = true: Save to {src_output_folder}/config.yaml
+- If {src_impact} = false: Save to {default_output_folder}/config.yaml
+
+<template-output>module_config</template-output>
+</step>
+
+<step n="5" goal="Create first agent" optional="true">
+Ask: **Create your first agent now? [Yes/no]**
+
+If yes:
+<invoke-workflow input="{{module_components}}">
+{agent_builder}
+</invoke-workflow>
+
+Guide them to create the primary agent for the module.
+<critical>Ensure it's saved to the correct location based on {src_impact}:</critical>
+
+- If {src_impact} = true: {src_output_folder}/agents/
+- If {src_impact} = false: {default_output_folder}/agents/
+
+If no, create placeholder:
+
+```md
+# {{primary_agent_name}} Agent
+
+<!-- TODO: Create using create-agent workflow -->
+<!-- Purpose: {{agent_purpose}} -->
+<!-- Type: {{agent_type}} -->
+```
+
+<template-output>first_agent</template-output>
+</step>
+
+<step n="6" goal="Create first workflow" optional="true">
+Ask: **Create your first workflow now? [Yes/no]**
+
+If yes:
+<invoke-workflow input="{{module_components}}">
+{workflow_builder}
+</invoke-workflow>
+
+Guide them to create the primary workflow.
+<critical>Ensure it's saved to the correct location based on {src_impact}:</critical>
+
+- If {src_impact} = true: {src_output_folder}/workflows/
+- If {src_impact} = false: {default_output_folder}/workflows/
+
+If no, create placeholder structure:
+
+```
+workflows/{{workflow_name}}/
+├── workflow.yaml    # TODO: Configure
+├── instructions.md  # TODO: Add steps
+└── template.md     # TODO: If document workflow
+```
+
+<template-output>first_workflow</template-output>
+</step>
+
+<step n="7" goal="Setup module installer">
+<action>Load installer templates from: {installer_templates}</action>
+
+Create install-module-config.yaml:
+
+```yaml
+# {{module_name}} Installation Configuration
+module_name: { { module_name } }
+module_code: { { module_code } }
+installation_date: { { date } }
+
+# Installation steps
+install_steps:
+  - name: 'Create directories'
+    action: 'mkdir'
+    paths:
+      - '{project-root}/bmad/{{module_code}}'
+      - '{project-root}/bmad/{{module_code}}/data'
+      - '{project-root}/bmad/{{module_code}}/agents'
+
+  - name: 'Copy configuration'
+    action: 'copy'
+    source: '{installer_path}/config.yaml'
+    dest: '{project-root}/bmad/{{module_code}}/config.yaml'
+
+  - name: 'Register module'
+    action: 'register'
+    manifest: '{project-root}/bmad/_cfg/manifest.yaml'
+
+# External assets (if any)
+external_assets:
+  - description: '{{asset_description}}'
+    source: 'assets/{{filename}}'
+    dest: '{{destination_path}}'
+
+# Post-install message
+post_install_message: |
+  {{module_name}} has been installed successfully!
+
+  To get started:
+  1. Load any {{module_code}} agent
+  2. Use *help to see available commands
+  3. Check README.md for full documentation
+```
+
+Create installer.js stub (optional):
+
+```javascript
+// {{module_name}} Module Installer
+// This is a placeholder for complex installation logic
+
+function installModule(config) {
+  console.log('Installing {{module_name}} module...');
+
+  // TODO: Add any complex installation logic here
+  // Examples:
+  // - Database setup
+  // - API key configuration
+  // - External service registration
+  // - File system preparation
+
+  console.log('{{module_name}} module installed successfully!');
+  return true;
+}
+
+module.exports = { installModule };
+```
+
+<template-output>installer_config</template-output>
+</step>
+
+<step n="8" goal="Create module documentation">
+Generate comprehensive README.md:
+
+````markdown
+# {{module_name}}
+
+{{module_purpose}}
+
+## Overview
+
+This module provides:
+{{component_summary}}
+
+## Installation
+
+```bash
+bmad install {{module_code}}
+```
+````
+
+## Components
+
+### Agents ({{agent_count}})
+
+{{agent_documentation}}
+
+### Workflows ({{workflow_count}})
+
+{{workflow_documentation}}
+
+### Tasks ({{task_count}})
+
+{{task_documentation}}
+
+## Quick Start
+
+1. **Load the main agent:**
+
+   ```
+   agent {{primary_agent}}
+   ```
+
+2. **View available commands:**
+
+   ```
+   *help
+   ```
+
+3. **Run the main workflow:**
+   ```
+   workflow {{primary_workflow}}
+   ```
+
+## Module Structure
+
+```
+{{directory_tree}}
+```
+
+## Configuration
+
+The module can be configured in `bmad/{{module_code}}/config.yaml`
+
+Key settings:
+{{configuration_options}}
+
+## Examples
+
+### Example 1: {{example_use_case}}
+
+{{example_walkthrough}}
+
+## Development Roadmap
+
+- [ ] {{roadmap_item_1}}
+- [ ] {{roadmap_item_2}}
+- [ ] {{roadmap_item_3}}
+
+## Contributing
+
+To extend this module:
+
+1. Add new agents using `create-agent` workflow
+2. Add new workflows using `create-workflow` workflow
+3. Submit improvements via pull request
+
+## Author
+
+Created by {{user_name}} on {{date}}
+
+````
+
+<template-output>module_readme</template-output>
+</step>
+
+<step n="9" goal="Generate component roadmap">
+Create a development roadmap for remaining components:
+
+**TODO.md file:**
+```markdown
+# {{module_name}} Development Roadmap
+
+## Phase 1: Core Components
+{{phase1_tasks}}
+
+## Phase 2: Enhanced Features
+{{phase2_tasks}}
+
+## Phase 3: Polish and Integration
+{{phase3_tasks}}
+
+## Quick Commands
+
+Create new agent:
+````
+
+workflow create-agent
+
+```
+
+Create new workflow:
+```
+
+workflow create-workflow
+
+```
+
+## Notes
+{{development_notes}}
+```
+
+Ask if user wants to:
+
+1. Continue building more components now
+2. Save roadmap for later development
+3. Test what's been built so far
+
+<template-output>development_roadmap</template-output>
+</step>
+
+<step n="10" goal="Validate and finalize module">
+Run validation checks:
+
+1. **Structure validation:**
+   - All required directories created
+   - Config files properly formatted
+   - Installer configuration valid
+
+2. **Component validation:**
+   - At least one agent or workflow exists (or planned)
+   - All references use correct paths
+   - Module code consistent throughout
+
+3. **Documentation validation:**
+   - README.md complete
+   - Installation instructions clear
+   - Examples provided
+
+Show summary:
+
+```
+✅ Module: {{module_name}} ({{module_code}})
+📁 Location:
+   - If {src_impact} = true: {src_output_folder}
+   - If {src_impact} = false: {default_output_folder}
+👥 Agents: {{agent_count}} ({{agents_created}} created, {{agents_planned}} planned)
+📋 Workflows: {{workflow_count}} ({{workflows_created}} created, {{workflows_planned}} planned)
+📝 Tasks: {{task_count}}
+📦 Installer: Ready at same location
+```
+
+Next steps:
+
+1. Complete remaining components using roadmap
+2. Test module with: `bmad install {{module_code}}`
+3. Share module or integrate with existing system
+
+Ask: Would you like to:
+
+- Create another component now?
+- Test the module installation?
+- Exit and continue later?
+
+<template-output>module_summary</template-output>
+</step>
+
+</workflow>

bmad/bmb/workflows/create-module/module-structure.md

@@ -0,0 +1,310 @@
+# BMAD Module Structure Guide
+
+## What is a Module?
+
+A BMAD module is a self-contained package of agents, workflows, tasks, and resources that work together to provide specialized functionality. Think of it as an expansion pack for the BMAD Method.
+
+## Module Architecture
+
+### Core Structure
+
+```
+project-root/
+├── bmad/{module-code}/     # Source code
+│   ├── agents/                    # Agent definitions
+│   ├── workflows/                 # Workflow folders
+│   ├── tasks/                     # Task files
+│   ├── templates/                 # Shared templates
+│   ├── data/                      # Static data
+│   ├── config.yaml                # Module config
+│   └── README.md                  # Documentation
+│
+└── bmad/{module-code}/            # Runtime instance
+    ├── _module-installer/         # Installation files
+    │   ├── install-module-config.yaml
+    │   ├── installer.js          # Optional
+    │   └── assets/               # Install assets
+    ├── config.yaml               # User config
+    ├── agents/                   # Agent overrides
+    ├── workflows/                # Workflow instances
+    └── data/                     # User data
+
+```
+
+## Module Types by Complexity
+
+### Simple Module (1-2 agents, 2-3 workflows)
+
+Perfect for focused, single-purpose tools.
+
+**Example: Code Review Module**
+
+- 1 Reviewer Agent
+- 2 Workflows: quick-review, deep-review
+- Clear, narrow scope
+
+### Standard Module (3-5 agents, 5-10 workflows)
+
+Comprehensive solution for a domain.
+
+**Example: Project Management Module**
+
+- PM Agent, Scrum Master Agent, Analyst Agent
+- Workflows: sprint-planning, retrospective, roadmap, user-stories
+- Integrated component ecosystem
+
+### Complex Module (5+ agents, 10+ workflows)
+
+Full platform or framework.
+
+**Example: RPG Toolkit Module**
+
+- DM Agent, NPC Agent, Monster Agent, Loot Agent, Map Agent
+- 15+ workflows for every aspect of game management
+- Multiple interconnected systems
+
+## Module Naming Conventions
+
+### Module Code (kebab-case)
+
+- `data-viz` - Data Visualization
+- `team-collab` - Team Collaboration
+- `rpg-toolkit` - RPG Toolkit
+- `legal-assist` - Legal Assistant
+
+### Module Name (Title Case)
+
+- "Data Visualization Suite"
+- "Team Collaboration Platform"
+- "RPG Game Master Toolkit"
+- "Legal Document Assistant"
+
+## Component Guidelines
+
+### Agents per Module
+
+**Recommended Distribution:**
+
+- **Primary Agent (1)**: The main interface/orchestrator
+- **Specialist Agents (2-4)**: Domain-specific experts
+- **Utility Agents (0-2)**: Helper/support functions
+
+**Anti-patterns to Avoid:**
+
+- Too many overlapping agents
+- Agents that could be combined
+- Agents without clear purpose
+
+### Workflows per Module
+
+**Categories:**
+
+- **Core Workflows (2-3)**: Essential functionality
+- **Feature Workflows (3-5)**: Specific capabilities
+- **Utility Workflows (2-3)**: Supporting operations
+- **Admin Workflows (0-2)**: Maintenance/config
+
+**Workflow Complexity Guide:**
+
+- Simple: 3-5 steps, single output
+- Standard: 5-10 steps, multiple outputs
+- Complex: 10+ steps, conditional logic, sub-workflows
+
+### Tasks per Module
+
+Tasks should be used for:
+
+- Single-operation utilities
+- Shared subroutines
+- Quick actions that don't warrant workflows
+
+## Module Dependencies
+
+### Internal Dependencies
+
+- Agents can reference module workflows
+- Workflows can invoke module tasks
+- Tasks can use module templates
+
+### External Dependencies
+
+- Reference other modules via full paths
+- Declare dependencies in config.yaml
+- Version compatibility notes
+
+## Installation Infrastructure
+
+### Required: install-module-config.yaml
+
+```yaml
+module_name: 'Module Name'
+module_code: 'module-code'
+
+install_steps:
+  - name: 'Create directories'
+    action: 'mkdir'
+    paths: [...]
+
+  - name: 'Copy files'
+    action: 'copy'
+    mappings: [...]
+
+  - name: 'Register module'
+    action: 'register'
+```
+
+### Optional: installer.js
+
+For complex installations requiring:
+
+- Database setup
+- API configuration
+- System integration
+- Permission management
+
+### Optional: External Assets
+
+Files that get copied outside the module:
+
+- System configurations
+- User templates
+- Shared resources
+- Integration scripts
+
+## Module Lifecycle
+
+### Development Phases
+
+1. **Planning Phase**
+   - Define scope and purpose
+   - Identify components
+   - Design architecture
+
+2. **Scaffolding Phase**
+   - Create directory structure
+   - Generate configurations
+   - Setup installer
+
+3. **Building Phase**
+   - Create agents incrementally
+   - Build workflows progressively
+   - Add tasks as needed
+
+4. **Testing Phase**
+   - Test individual components
+   - Verify integration
+   - Validate installation
+
+5. **Deployment Phase**
+   - Package module
+   - Document usage
+   - Distribute/share
+
+## Best Practices
+
+### Module Cohesion
+
+- All components should relate to module theme
+- Clear boundaries between modules
+- No feature creep
+
+### Progressive Enhancement
+
+- Start with MVP (1 agent, 2 workflows)
+- Add components based on usage
+- Refactor as patterns emerge
+
+### Documentation Standards
+
+- Every module needs README.md
+- Each agent needs purpose statement
+- Workflows need clear descriptions
+- Include examples and quickstart
+
+### Naming Consistency
+
+- Use module code prefix for uniqueness
+- Consistent naming patterns within module
+- Clear, descriptive names
+
+## Example Modules
+
+### Example 1: Personal Productivity
+
+```
+productivity/
+├── agents/
+│   ├── task-manager.md      # GTD methodology
+│   └── focus-coach.md        # Pomodoro timer
+├── workflows/
+│   ├── daily-planning/       # Morning routine
+│   ├── weekly-review/        # Week retrospective
+│   └── project-setup/        # New project init
+└── config.yaml
+```
+
+### Example 2: Content Creation
+
+```
+content/
+├── agents/
+│   ├── writer.md            # Blog/article writer
+│   ├── editor.md            # Copy editor
+│   └── seo-optimizer.md     # SEO specialist
+├── workflows/
+│   ├── blog-post/           # Full blog creation
+│   ├── social-media/        # Social content
+│   ├── email-campaign/      # Email sequence
+│   └── content-calendar/    # Planning
+└── templates/
+    ├── blog-template.md
+    └── email-template.md
+```
+
+### Example 3: DevOps Automation
+
+```
+devops/
+├── agents/
+│   ├── deploy-master.md     # Deployment orchestrator
+│   ├── monitor.md           # System monitoring
+│   ├── incident-responder.md # Incident management
+│   └── infra-architect.md   # Infrastructure design
+├── workflows/
+│   ├── ci-cd-setup/         # Pipeline creation
+│   ├── deploy-app/          # Application deployment
+│   ├── rollback/            # Emergency rollback
+│   ├── health-check/        # System verification
+│   └── incident-response/   # Incident handling
+├── tasks/
+│   ├── check-status.md      # Quick status check
+│   └── notify-team.md       # Team notifications
+└── data/
+    └── runbooks/            # Operational guides
+```
+
+## Module Evolution Pattern
+
+```
+Simple Module → Standard Module → Complex Module → Module Suite
+     (MVP)          (Enhanced)        (Complete)      (Ecosystem)
+```
+
+## Common Pitfalls
+
+1. **Over-engineering**: Starting too complex
+2. **Under-planning**: No clear architecture
+3. **Poor boundaries**: Module does too much
+4. **Weak integration**: Components don't work together
+5. **Missing docs**: No clear usage guide
+
+## Success Metrics
+
+A well-designed module has:
+
+- ✅ Clear, focused purpose
+- ✅ Cohesive components
+- ✅ Smooth installation
+- ✅ Comprehensive docs
+- ✅ Room for growth
+- ✅ Happy users!

bmad/bmb/workflows/create-module/workflow.yaml

@@ -0,0 +1,45 @@
+# Build Module Workflow Configuration
+name: create-module
+description: "Interactive workflow to build complete BMAD modules with agents, workflows, tasks, and installation infrastructure"
+author: "BMad"
+
+# Critical variables load from config_source
+config_source: "{project-root}/bmad/bmb/config.yaml"
+output_folder: "{config_source}:output_folder"
+src_impact: "{config_source}:src_impact"
+communication_language: "{config_source}:communication_language"
+user_name: "{config_source}:user_name"
+date: system-generated
+
+# Reference guides for module building
+module_structure_guide: "{installed_path}/module-structure.md"
+installer_templates: "{installed_path}/installer-templates/"
+
+# Use existing build workflows
+agent_builder: "{project-root}/bmad/bmb/workflows/create-agent/workflow.yaml"
+workflow_builder: "{project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml"
+brainstorming_workflow: "{project-root}/bmad/cis/workflows/brainstorming/workflow.yaml"
+brainstorming_context: "{installed_path}/brainstorm-context.md"
+
+# Optional docs that help understand module patterns
+recommended_inputs:
+  - module_brief: "{output_folder}/module-brief-*.md"
+  - brainstorming_results: "{output_folder}/brainstorming-*.md"
+  - bmm_module: "{project-root}/bmad/bmm/"
+  - cis_module: "{project-root}/bmad/cis/"
+  - existing_agents: "{project-root}/bmad/*/agents/"
+  - existing_workflows: "{project-root}/bmad/*/workflows/"
+
+# Module path and component files
+installed_path: "{project-root}/bmad/bmb/workflows/create-module"
+template: false # This is an interactive scaffolding workflow
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+
+# Output configuration - creates entire module structure
+# If src_impact=true: Save to src/modules/{{module_code}}
+# If src_impact=false: Save to output_folder/{{module_code}}
+default_output_folder: "{output_folder}/{{module_code}}"
+src_output_folder: "{project-root}/src/modules/{{module_code}}"
+installer_output_folder: "{output_folder}/{{module_code}}"
+src_installer_output_folder: "{project-root}/src/modules/{{module_code}}"

bmad/bmb/workflows/create-workflow/README.md

@@ -0,0 +1,216 @@
+# Build Workflow
+
+## Overview
+
+The Build Workflow is an interactive workflow builder that guides you through creating new BMAD workflows with proper structure, conventions, and validation. It ensures all workflows follow best practices for optimal human-AI collaboration and are fully compliant with the BMAD Core v6 workflow execution engine.
+
+## Key Features
+
+- **Optional Brainstorming Phase**: Creative exploration of workflow ideas before structured development
+- **Comprehensive Guidance**: Step-by-step process with detailed instructions and examples
+- **Template-Based**: Uses proven templates for all workflow components
+- **Convention Enforcement**: Ensures adherence to BMAD workflow creation guide
+- **README Generation**: Automatically creates comprehensive documentation
+- **Validation Built-In**: Includes checklist generation for quality assurance
+- **Type-Aware**: Adapts to document, action, interactive, autonomous, or meta-workflow types
+
+## Usage
+
+### Basic Invocation
+
+```bash
+workflow create-workflow
+```
+
+### Through BMad Builder Agent
+
+```
+*create-workflow
+```
+
+### What You'll Be Asked
+
+1. **Optional**: Whether to brainstorm workflow ideas first (creative exploration phase)
+2. Workflow name and target module
+3. Workflow purpose and type (enhanced by brainstorming insights if used)
+4. Metadata (description, author, outputs)
+5. Step-by-step design (goals, variables, flow)
+6. Whether to include optional components
+
+## Workflow Structure
+
+### Files Included
+
+```
+create-workflow/
+├── workflow.yaml                  # Configuration and metadata
+├── instructions.md                # Step-by-step execution guide
+├── checklist.md                   # Validation criteria
+├── workflow-creation-guide.md     # Comprehensive reference guide
+├── README.md                      # This file
+└── workflow-template/             # Templates for new workflows
+    ├── workflow.yaml
+    ├── instructions.md
+    ├── template.md
+    ├── checklist.md
+    └── README.md
+```
+
+## Workflow Process
+
+### Phase 0: Optional Brainstorming (Step -1)
+
+- **Creative Exploration**: Option to brainstorm workflow ideas before structured development
+- **Design Concept Development**: Generate multiple approaches and explore different possibilities
+- **Requirement Clarification**: Use brainstorming output to inform workflow purpose, type, and structure
+- **Enhanced Creativity**: Leverage AI brainstorming tools for innovative workflow design
+
+The brainstorming phase invokes the CIS brainstorming workflow to:
+
+- Explore workflow ideas and approaches
+- Clarify requirements and use cases
+- Generate creative solutions for complex automation needs
+- Inform the structured workflow building process
+
+### Phase 1: Planning (Steps 0-3)
+
+- Load workflow creation guide and conventions
+- Define workflow purpose, name, and type (informed by brainstorming if used)
+- Gather metadata and configuration details
+- Design step structure and flow
+
+### Phase 2: Generation (Steps 4-8)
+
+- Create workflow.yaml with proper configuration
+- Generate instructions.md with XML-structured steps
+- Create template.md (for document workflows)
+- Generate validation checklist
+- Create supporting data files (optional)
+
+### Phase 3: Documentation and Validation (Steps 9-11)
+
+- Create comprehensive README.md (MANDATORY)
+- Test and validate workflow structure
+- Provide usage instructions and next steps
+
+## Output
+
+### Generated Workflow Folder
+
+Creates a complete workflow folder at:
+`{project-root}/bmad/{{target_module}}/workflows/{{workflow_name}}/`
+
+### Files Created
+
+**Always Created:**
+
+- `workflow.yaml` - Configuration with paths and variables
+- `README.md` - Comprehensive documentation (MANDATORY as of v6)
+- `instructions.md` - Execution steps (if not template-only workflow)
+
+**Conditionally Created:**
+
+- `template.md` - Document structure (for document workflows)
+- `checklist.md` - Validation criteria (optional but recommended)
+- Supporting data files (CSV, JSON, etc. as needed)
+
+### Output Structure
+
+For document workflows, the README documents:
+
+- Workflow purpose and use cases
+- Usage examples with actual commands
+- Input expectations
+- Output structure and location
+- Best practices
+
+## Requirements
+
+- Access to workflow creation guide
+- BMAD Core v6 project structure
+- Module to host the new workflow (bmm, bmb, cis, or custom)
+
+## Best Practices
+
+### Before Starting
+
+1. **Consider Brainstorming**: If you're unsure about the workflow approach, use the optional brainstorming phase
+2. Review the workflow creation guide to understand conventions
+3. Have a clear understanding of the workflow's purpose (or be ready to explore it creatively)
+4. Know which type of workflow you're creating (document, action, etc.) or be open to discovery
+5. Identify any data files or references needed
+
+### Creative Workflow Design
+
+The create-workflow now supports a **seamless transition from creative ideation to structured implementation**:
+
+- **"I need a workflow for something..."** → Start with brainstorming to explore possibilities
+- **Brainstorm** → Generate multiple approaches and clarify requirements
+- **Structured workflow** → Build the actual workflow using insights from brainstorming
+- **One seamless session** → Complete the entire process from idea to implementation
+
+### During Execution
+
+1. Follow kebab-case naming conventions
+2. Be specific with step goals and instructions
+3. Use descriptive variable names (snake_case)
+4. Set appropriate limits ("3-5 items maximum")
+5. Include examples where helpful
+
+### After Completion
+
+1. Test the newly created workflow
+2. Validate against the checklist
+3. Ensure README is comprehensive and accurate
+4. Test all file paths and variable references
+
+## Troubleshooting
+
+### Issue: Generated workflow won't execute
+
+- **Solution**: Verify all file paths in workflow.yaml use proper variable substitution
+- **Check**: Ensure installed_path and project-root are correctly set
+
+### Issue: Variables not replacing in template
+
+- **Solution**: Ensure variable names match exactly between instructions `<template-output>` tags and template `{{variables}}`
+- **Check**: Use snake_case consistently
+
+### Issue: README has placeholder text
+
+- **Solution**: This workflow now enforces README generation - ensure Step 10 completed fully
+- **Check**: No {WORKFLOW_TITLE} or similar placeholders should remain
+
+## Customization
+
+To modify this workflow:
+
+1. Edit `instructions.md` to adjust the creation process
+2. Update templates in `workflow-template/` to change generated files
+3. Modify `workflow-creation-guide.md` to update conventions
+4. Edit `checklist.md` to change validation criteria
+
+## Version History
+
+- **v6.0.0** - README.md now MANDATORY for all workflows
+  - Added comprehensive README template
+  - Enhanced validation for documentation
+  - Improved Step 10 with detailed README requirements
+
+- **v5.0.0** - Initial BMAD Core v6 compatible version
+  - Template-based workflow generation
+  - Convention enforcement
+  - Validation checklist support
+
+## Support
+
+For issues or questions:
+
+- Review `/bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
+- Check existing workflows in `/bmad/bmm/workflows/` for examples
+- Validate against `/bmad/bmb/workflows/create-workflow/checklist.md`
+- Consult BMAD Method v6 documentation
+
+---
+
+_Part of the BMad Method v6 - BMB (BMad Builder) Module_

bmad/bmb/workflows/create-workflow/brainstorm-context.md

@@ -0,0 +1,197 @@
+# Workflow Brainstorming Context
+
+_Context provided to brainstorming workflow when creating a new BMAD workflow_
+
+## Session Focus
+
+You are brainstorming ideas for a **BMAD workflow** - a guided, multi-step process that helps users accomplish complex tasks with structure, consistency, and quality.
+
+## What is a BMAD Workflow?
+
+A workflow is a structured process that provides:
+
+- **Clear Steps**: Sequential operations with defined goals
+- **User Guidance**: Prompts, questions, and decisions at each phase
+- **Quality Output**: Documents, artifacts, or completed actions
+- **Repeatability**: Same process yields consistent results
+- **Type**: Document (creates docs), Action (performs tasks), Interactive (guides sessions), Autonomous (runs automated), Meta (orchestrates other workflows)
+
+## Brainstorming Goals
+
+Explore and define:
+
+### 1. Problem and Purpose
+
+- **What task needs structure?** (specific process users struggle with)
+- **Why is this hard manually?** (complexity, inconsistency, missing steps)
+- **What would ideal process look like?** (steps, checkpoints, outputs)
+- **Who needs this?** (target users and their pain points)
+
+### 2. Process Flow
+
+- **How many phases?** (typically 3-10 major steps)
+- **What's the sequence?** (logical flow from start to finish)
+- **What decisions are needed?** (user choices that affect path)
+- **What's optional vs required?** (flexibility points)
+- **What checkpoints matter?** (validation, review, approval points)
+
+### 3. Inputs and Outputs
+
+- **What inputs are needed?** (documents, data, user answers)
+- **What outputs are generated?** (documents, code, configurations)
+- **What format?** (markdown, XML, YAML, actions)
+- **What quality criteria?** (how to validate success)
+
+### 4. Workflow Type and Style
+
+- **Document Workflow?** Creates structured documents (PRDs, specs, reports)
+- **Action Workflow?** Performs operations (refactoring, deployment, analysis)
+- **Interactive Workflow?** Guides creative process (brainstorming, planning)
+- **Autonomous Workflow?** Runs without user input (batch processing, generation)
+- **Meta Workflow?** Orchestrates other workflows (project setup, module creation)
+
+## Creative Constraints
+
+A great BMAD workflow should be:
+
+- **Focused**: Solves one problem well (not everything)
+- **Structured**: Clear phases with defined goals
+- **Flexible**: Optional steps, branching paths where appropriate
+- **Validated**: Checklist to verify completeness and quality
+- **Documented**: README explains when and how to use it
+
+## Workflow Architecture Questions
+
+### Core Structure
+
+1. **Workflow name** (kebab-case, e.g., "product-brief")
+2. **Purpose** (one sentence)
+3. **Type** (document/action/interactive/autonomous/meta)
+4. **Major phases** (3-10 high-level steps)
+5. **Output** (what gets created)
+
+### Process Details
+
+1. **Required inputs** (what user must provide)
+2. **Optional inputs** (what enhances results)
+3. **Decision points** (where user chooses path)
+4. **Checkpoints** (where to pause for approval)
+5. **Variables** (data passed between steps)
+
+### Quality and Validation
+
+1. **Success criteria** (what defines "done")
+2. **Validation checklist** (measurable quality checks)
+3. **Common issues** (troubleshooting guidance)
+4. **Best practices** (tips for optimal results)
+
+## Workflow Pattern Examples
+
+### Document Generation Workflows
+
+- **Product Brief**: Idea → Vision → Features → Market → Output
+- **PRD**: Requirements → User Stories → Acceptance Criteria → Document
+- **Architecture**: Requirements → Decisions → Design → Diagrams → ADRs
+- **Technical Spec**: Epic → Implementation → Testing → Deployment → Doc
+
+### Action Workflows
+
+- **Code Refactoring**: Analyze → Plan → Refactor → Test → Commit
+- **Deployment**: Build → Test → Stage → Validate → Deploy → Monitor
+- **Migration**: Assess → Plan → Convert → Validate → Deploy
+- **Analysis**: Collect → Process → Analyze → Report → Recommend
+
+### Interactive Workflows
+
+- **Brainstorming**: Setup → Generate → Expand → Evaluate → Prioritize
+- **Planning**: Context → Goals → Options → Decisions → Plan
+- **Review**: Load → Analyze → Critique → Suggest → Document
+
+### Meta Workflows
+
+- **Project Setup**: Plan → Architecture → Stories → Setup → Initialize
+- **Module Creation**: Brainstorm → Brief → Agents → Workflows → Install
+- **Sprint Planning**: Backlog → Capacity → Stories → Commit → Kickoff
+
+## Workflow Design Patterns
+
+### Linear Flow
+
+Simple sequence: Step 1 → Step 2 → Step 3 → Done
+
+**Good for:**
+
+- Document generation
+- Structured analysis
+- Sequential builds
+
+### Branching Flow
+
+Conditional paths: Step 1 → [Decision] → Path A or Path B → Merge → Done
+
+**Good for:**
+
+- Different project types
+- Optional deep dives
+- Scale-adaptive processes
+
+### Iterative Flow
+
+Refinement loops: Step 1 → Step 2 → [Review] → (Repeat if needed) → Done
+
+**Good for:**
+
+- Creative processes
+- Quality refinement
+- Approval cycles
+
+### Router Flow
+
+Type selection: [Select Type] → Load appropriate instructions → Execute → Done
+
+**Good for:**
+
+- Multi-mode workflows
+- Reusable frameworks
+- Flexible tools
+
+## Suggested Brainstorming Techniques
+
+Particularly effective for workflow ideation:
+
+1. **Process Mapping**: Draw current painful process, identify improvements
+2. **Step Decomposition**: Break complex task into atomic steps
+3. **Checkpoint Thinking**: Where do users need pause/review/decision?
+4. **Pain Point Analysis**: What makes current process frustrating?
+5. **Success Visualization**: What does perfect execution look like?
+
+## Key Questions to Answer
+
+1. What manual process needs structure and guidance?
+2. What makes this process hard or inconsistent today?
+3. What are the 3-10 major phases/steps?
+4. What document or output gets created?
+5. What inputs are required from the user?
+6. What decisions or choices affect the flow?
+7. What quality criteria define success?
+8. Document, Action, Interactive, Autonomous, or Meta workflow?
+9. What makes this workflow valuable vs doing it manually?
+10. What would make this workflow delightful to use?
+
+## Output Goals
+
+Generate:
+
+- **Workflow name**: Clear, describes the process
+- **Purpose statement**: One sentence explaining value
+- **Workflow type**: Classification with rationale
+- **Phase outline**: 3-10 major steps with goals
+- **Input/output description**: What goes in, what comes out
+- **Key decisions**: Where user makes choices
+- **Success criteria**: How to know it worked
+- **Unique value**: Why this workflow beats manual process
+- **Use cases**: 3-5 scenarios where this workflow shines
+
+---
+
+_This focused context helps create valuable, structured BMAD workflows_

bmad/bmb/workflows/create-workflow/checklist.md

@@ -0,0 +1,72 @@
+# Build Workflow - Validation Checklist
+
+## Workflow Configuration (workflow.yaml)
+
+- [ ] Name follows kebab-case convention
+- [ ] Description clearly states workflow purpose
+- [ ] All paths use proper variable substitution
+- [ ] installed_path points to correct module location
+- [ ] template/instructions paths are correct for workflow type
+- [ ] Output file pattern is appropriate
+- [ ] YAML syntax is valid (no parsing errors)
+
+## Instructions Structure (instructions.md)
+
+- [ ] Critical headers reference workflow engine
+- [ ] All steps have sequential numbering
+- [ ] Each step has a clear goal attribute
+- [ ] Optional steps marked with optional="true"
+- [ ] Repeating steps have appropriate repeat attributes
+- [ ] All template-output tags have unique variable names
+- [ ] Flow control (if any) has valid step references
+
+## Template Structure (if document workflow)
+
+- [ ] All sections have appropriate placeholders
+- [ ] Variable names match template-output tags exactly
+- [ ] Markdown formatting is valid
+- [ ] Date and metadata fields included
+- [ ] No unreferenced variables remain
+
+## Content Quality
+
+- [ ] Instructions are specific and actionable
+- [ ] Examples provided where helpful
+- [ ] Limits set for lists and content length
+- [ ] User prompts are clear
+- [ ] Step goals accurately describe outcomes
+
+## Validation Checklist (if present)
+
+- [ ] Criteria are measurable and specific
+- [ ] Checks grouped logically by category
+- [ ] Final validation summary included
+- [ ] All critical requirements covered
+
+## File System
+
+- [ ] Workflow folder created in correct module
+- [ ] All required files present based on workflow type
+- [ ] File permissions allow execution
+- [ ] No placeholder text remains (like {TITLE})
+
+## Testing Readiness
+
+- [ ] Workflow can be invoked without errors
+- [ ] All required inputs are documented
+- [ ] Output location is writable
+- [ ] Dependencies (if any) are available
+
+## Documentation
+
+- [ ] README created (if requested)
+- [ ] Usage instructions clear
+- [ ] Example command provided
+- [ ] Special requirements noted
+
+## Final Validation
+
+- [ ] Configuration: No issues
+- [ ] Instructions: Complete and clear
+- [ ] Template: Variables properly mapped
+- [ ] Testing: Ready for test run

bmad/bmb/workflows/create-workflow/instructions.md

@@ -0,0 +1,267 @@
+# Build Workflow - Workflow Builder Instructions
+
+<workflow>
+
+<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
+<critical>You MUST have already loaded and processed: {project_root}/bmad/bmb/workflows/create-workflow/workflow.yaml</critical>
+<critical>You MUST fully understand the workflow creation guide at: {workflow_creation_guide}</critical>
+<critical>Study the guide thoroughly to follow ALL conventions for optimal human-AI collaboration</critical>
+
+<step n="-1" goal="Optional brainstorming phase" optional="true">
+<ask>Do you want to brainstorm workflow ideas first? [y/n]</ask>
+
+<action if="user_response == 'y' or user_response == 'yes'">
+Invoke brainstorming workflow to explore ideas and design concepts:
+- Workflow: {project-root}/bmad/cis/workflows/brainstorming/workflow.yaml
+- Context data: {installed_path}/brainstorm-context.md
+- Purpose: Generate creative workflow ideas, explore different approaches, and clarify requirements
+
+The brainstorming output will inform:
+
+- Workflow purpose and goals
+- Workflow type selection
+- Step design and structure
+- User experience considerations
+- Technical requirements
+  </action>
+
+<action if="user_response == 'n' or user_response == 'no'">
+Skip brainstorming and proceed directly to workflow building process.
+</action>
+</step>
+
+<step n="0" goal="Load and understand workflow conventions">
+<action>Load the complete workflow creation guide from: {workflow_creation_guide}</action>
+<action>Study all sections thoroughly including:
+  - Core concepts (tasks vs workflows, workflow types)
+  - Workflow structure (required/optional files, patterns)
+  - Writing instructions (step attributes, XML tags, flow control)
+  - Templates and variables (syntax, naming, sources)
+  - Validation best practices
+  - Common pitfalls to avoid
+</action>
+<action>Load template files from: {workflow_template_path}/</action>
+<critical>You must follow ALL conventions from the guide to ensure optimal human-AI collaboration</critical>
+</step>
+
+<step n="1" goal="Define workflow purpose and type">
+Ask the user:
+- What is the workflow name? (kebab-case, e.g., "product-brief")
+- What module will it belong to? (e.g., "bmm", "bmb", "cis")
+  - Store as {{target_module}} for output path determination
+- What is the workflow's main purpose?
+- What type of workflow is this?
+  - Document workflow (generates documents like PRDs, specs)
+  - Action workflow (performs actions like refactoring)
+  - Interactive workflow (guided sessions)
+  - Autonomous workflow (runs without user input)
+  - Meta-workflow (coordinates other workflows)
+
+Based on type, determine which files are needed:
+
+- Document: workflow.yaml + template.md + instructions.md + checklist.md
+- Action: workflow.yaml + instructions.md
+- Others: Varies based on requirements
+
+<critical>Check {src_impact} variable to determine output location:</critical>
+
+- If {src_impact} = true: Workflow will be saved to {src_output_folder}
+- If {src_impact} = false: Workflow will be saved to {default_output_folder}
+
+Store decisions for later use.
+</step>
+
+<step n="2" goal="Gather workflow metadata">
+Collect essential configuration details:
+- Description (clear purpose statement)
+- Author name (default to user_name or "BMad")
+- Output file naming pattern
+- Any required input documents
+- Any required tools or dependencies
+
+Create the workflow name in kebab-case and verify it doesn't conflict with existing workflows.
+</step>
+
+<step n="3" goal="Design workflow steps">
+Work with user to outline the workflow steps:
+- How many major steps? (Recommend 5-10 max)
+- What is the goal of each step?
+- Which steps are optional?
+- Which steps need user input?
+- Which steps should repeat?
+- What variables/outputs does each step produce?
+
+Create a step outline with clear goals and outputs.
+</step>
+
+<step n="4" goal="Create workflow.yaml">
+Load and use the template at: {template_workflow_yaml}
+
+Replace all placeholders following the workflow creation guide conventions:
+
+- {TITLE} → Proper case workflow name
+- {WORKFLOW_CODE} → kebab-case name
+- {WORKFLOW_DESCRIPTION} → Clear description
+- {module-code} → Target module
+- {file.md} → Output filename pattern
+
+Include:
+
+- All metadata from steps 1-2
+- Proper paths for installed_path using variable substitution
+- Template/instructions/validation paths based on workflow type:
+  - Document workflow: all files (template, instructions, validation)
+  - Action workflow: instructions only (template: false)
+  - Autonomous: set autonomous: true flag
+- Required tools if any
+- Recommended inputs if any
+
+Follow path conventions from guide:
+
+- Use {project-root} for absolute paths
+- Use {installed_path} for workflow components
+- Use {config_source} for config references
+
+<critical>Determine save location based on {src_impact}:</critical>
+
+- If {src_impact} = true: Write to {src_output_folder}/workflow.yaml
+- If {src_impact} = false: Write to {default_output_folder}/workflow.yaml
+  </step>
+
+<step n="5" goal="Create instructions.md" if="workflow_type != 'template-only'">
+Load and use the template at: {template_instructions}
+
+Generate the instructions.md file following the workflow creation guide:
+
+1. ALWAYS include critical headers:
+   - Workflow engine reference: {project_root}/bmad/core/tasks/workflow.md
+   - workflow.yaml reference: must be loaded and processed
+
+2. Structure with <workflow> tags containing all steps
+
+3. For each step from design phase, follow guide conventions:
+   - Step attributes: n="X" goal="clear goal statement"
+   - Optional steps: optional="true"
+   - Repeating: repeat="3" or repeat="for-each-X" or repeat="until-approved"
+   - Conditional: if="condition"
+   - Sub-steps: Use 3a, 3b notation
+
+4. Use proper XML tags from guide:
+   - Execution: <action>, <check>, <ask>, <goto>, <invoke-workflow>
+   - Output: <template-output>, <elicit-required/>, <critical>, <example>
+   - Flow: <loop>, <break>, <continue>
+
+5. Best practices from guide:
+   - Keep steps focused (single goal)
+   - Be specific ("Write 1-2 paragraphs" not "Write about")
+   - Provide examples where helpful
+   - Set limits ("3-5 items maximum")
+   - Save checkpoints with <template-output>
+
+<critical>Determine save location based on {src_impact}:</critical>
+
+- If {src_impact} = true: Write to {src_output_folder}/instructions.md
+- If {src_impact} = false: Write to {default_output_folder}/instructions.md
+  </step>
+
+<step n="6" goal="Create template.md" if="workflow_type == 'document'">
+Load and use the template at: {template_template}
+
+Generate the template.md file following guide conventions:
+
+1. Document structure with clear sections
+2. Variable syntax: {{variable_name}} using snake_case
+3. Variable names MUST match <template-output> tags exactly from instructions
+4. Include standard metadata:
+   - **Date:** {{date}}
+   - **Author:** {{user_name}} (if applicable)
+5. Follow naming conventions from guide:
+   - Use descriptive names: {{primary_user_journey}} not {{puj}}
+   - Snake_case for all variables
+   - Match instruction outputs precisely
+
+Variable sources as per guide:
+
+- workflow.yaml config values
+- User input runtime values
+- Step outputs via <template-output>
+- System variables (date, paths)
+
+<critical>Determine save location based on {src_impact}:</critical>
+
+- If {src_impact} = true: Write to {src_output_folder}/template.md
+- If {src_impact} = false: Write to {default_output_folder}/template.md
+  </step>
+
+<step n="7" goal="Create validation checklist" optional="true">
+Ask if user wants a validation checklist. If yes:
+
+Load and use the template at: {template_checklist}
+
+Create checklist.md following guide best practices:
+
+1. Make criteria MEASURABLE and SPECIFIC
+   ❌ "- [ ] Good documentation"
+   ✅ "- [ ] Each function has JSDoc comments with parameters and return types"
+
+2. Group checks logically:
+   - Structure: All sections present, no placeholders, proper formatting
+   - Content Quality: Clear and specific, technically accurate, consistent terminology
+   - Completeness: Ready for next phase, dependencies documented, action items defined
+
+3. Include workflow-specific validations based on type:
+   - Document workflows: Template variables mapped, sections complete
+   - Action workflows: Actions clearly defined, error handling specified
+   - Interactive: User prompts clear, decision points documented
+
+4. Add final validation section with issue lists
+
+<critical>Determine save location based on {src_impact}:</critical>
+
+- If {src_impact} = true: Write to {src_output_folder}/checklist.md
+- If {src_impact} = false: Write to {default_output_folder}/checklist.md
+  </step>
+
+<step n="8" goal="Create supporting files" optional="true">
+Ask if any supporting data files are needed:
+- CSV files with data
+- Example documents
+- Reference materials
+
+If yes, create placeholder files or copy from templates.
+</step>
+
+<step n="9" goal="Test and validate workflow">
+Review the created workflow:
+1. Verify all file paths are correct
+2. Check variable names match between files
+3. Ensure step numbering is sequential
+4. Validate YAML syntax
+5. Confirm all placeholders are replaced
+
+Show user a summary of created files and their locations.
+Ask if they want to:
+
+- Test run the workflow
+- Make any adjustments
+- Add additional steps or features
+  </step>
+
+<step n="10" goal="Document and finalize">
+Create a brief README for the workflow folder explaining:
+- Purpose and use case
+- How to invoke: `workflow {workflow_name}`
+- Expected inputs
+- Generated outputs
+- Any special requirements
+
+Provide user with:
+
+- Location of created workflow:
+  - If {src_impact} = true: {{src_output_folder}}
+  - If {src_impact} = false: {{default_output_folder}}
+- Command to run it
+- Next steps for testing
+  </step>
+
+</workflow>

bmad/bmb/workflows/create-workflow/workflow-creation-guide.md

@@ -0,0 +1,456 @@
+# BMAD Workflow Creation Guide
+
+Create structured, repeatable workflows for human-AI collaboration in BMAD v6.
+
+## Table of Contents
+
+1. [Quick Start](#quick-start)
+2. [Core Concepts](#core-concepts)
+3. [Workflow Structure](#workflow-structure)
+4. [Writing Instructions](#writing-instructions)
+5. [Templates and Variables](#templates--variables)
+6. [Flow Control](#flow-control)
+7. [Validation](#validation)
+8. [Examples](#examples)
+9. [Best Practices](#best-practices)
+10. [Troubleshooting](#troubleshooting)
+
+## Quick Start
+
+### Minimal Workflow (3 minutes)
+
+Create a folder with these files:
+
+```yaml
+# workflow.yaml (REQUIRED)
+name: 'my-workflow'
+description: 'What this workflow does'
+installed_path: '{project-root}/bmad/module/workflows/my-workflow'
+template: '{installed_path}/template.md'
+instructions: '{installed_path}/instructions.md'
+default_output_file: '{output_folder}/output.md'
+```
+
+```markdown
+# template.md
+
+# {{project_name}} Output
+
+{{main_content}}
+```
+
+```markdown
+# instructions.md
+
+<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
+<critical>You MUST have already loaded and processed: workflow.yaml</critical>
+
+<workflow>
+<step n="1" goal="Generate content">
+Create the main content for this document.
+<template-output>main_content</template-output>
+</step>
+</workflow>
+```
+
+That's it! To execute, tell the BMAD agent: `workflow my-workflow`
+
+## Core Concepts
+
+### Tasks vs Workflows
+
+| Aspect         | Task               | Workflow                |
+| -------------- | ------------------ | ----------------------- |
+| **Purpose**    | Single operation   | Multi-step process      |
+| **Format**     | XML in `.md` file  | Folder with YAML config |
+| **Location**   | `/src/core/tasks/` | `/bmad/*/workflows/`    |
+| **User Input** | Minimal            | Extensive               |
+| **Output**     | Variable           | Usually documents       |
+
+### Workflow Types
+
+1. **Document Workflows** - Generate PRDs, specs, architectures
+2. **Action Workflows** - Refactor code, run tools, orchestrate tasks
+3. **Interactive Workflows** - Brainstorming, meditations, guided sessions
+4. **Autonomous Workflows** - Run without human input (story generation)
+5. **Meta-Workflows** - Coordinate other workflows
+
+## Workflow Structure
+
+### Required Files
+
+```
+my-workflow/
+  └── workflow.yaml      # REQUIRED - Configuration
+```
+
+### Optional Files
+
+```
+my-workflow/
+  ├── template.md        # Document structure
+  ├── instructions.md    # Step-by-step guide
+  ├── checklist.md       # Validation criteria
+  └── [data files]       # Supporting resources
+```
+
+### workflow.yaml Configuration
+
+```yaml
+# Basic metadata
+name: 'workflow-name'
+description: 'Clear purpose statement'
+
+# Paths
+installed_path: '{project-root}/bmad/module/workflows/name'
+template: '{installed_path}/template.md' # or false
+instructions: '{installed_path}/instructions.md' # or false
+validation: '{installed_path}/checklist.md' # optional
+
+# Output
+default_output_file: '{output_folder}/document.md'
+
+# Advanced options
+autonomous: true # Skip user checkpoints
+recommended_inputs: # Expected input docs
+  - input_doc: 'path/to/doc.md'
+```
+
+### Common Patterns
+
+**Full Document Workflow** (most common)
+
+- Has: All 4 files
+- Use for: PRDs, architectures, specs
+
+**Action Workflow** (no template)
+
+- Has: workflow.yaml + instructions.md
+- Use for: Refactoring, tool orchestration
+
+**Autonomous Workflow** (no interaction)
+
+- Has: workflow.yaml + template + instructions
+- Use for: Automated generation
+
+## Writing Instructions
+
+### Basic Structure
+
+```markdown
+# instructions.md
+
+<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
+<critical>You MUST have already loaded and processed: workflow.yaml</critical>
+
+<workflow>
+
+<step n="1" goal="Clear goal statement">
+Instructions for this step.
+<template-output>variable_name</template-output>
+</step>
+
+<step n="2" goal="Next goal" optional="true">
+Optional step instructions.
+<template-output>another_variable</template-output>
+</step>
+
+</workflow>
+```
+
+### Step Attributes
+
+- `n="X"` - Step number (required)
+- `goal="..."` - What the step accomplishes (required)
+- `optional="true"` - User can skip
+- `repeat="3"` - Repeat N times
+- `if="condition"` - Conditional execution
+
+### Content Formats
+
+**Markdown Format** (human-friendly):
+
+```xml
+<step n="1" goal="Define goals">
+Write 1-3 bullet points about project success:
+- User outcomes
+- Business value
+- Measurable results
+
+<template-output>goals</template-output>
+</step>
+```
+
+**XML Format** (precise control):
+
+```xml
+<step n="2" goal="Validate input">
+  <action>Load validation criteria</action>
+  <check>If validation fails:</check>
+  <goto step="1">Return to previous step</goto>
+  <template-output>validated_data</template-output>
+</step>
+```
+
+## Templates and Variables
+
+### Variable Syntax
+
+```markdown
+# template.md
+
+# {{project_name}} Document
+
+## Section
+
+{{section_content}}
+
+_Generated on {{date}}_
+```
+
+### Variable Sources
+
+1. **workflow.yaml** - Config values
+2. **User input** - Runtime values
+3. **Step outputs** - `<template-output>` tags
+4. **System** - Date, paths, etc.
+
+### Naming Convention
+
+- Use snake_case: `{{user_requirements}}`
+- Be descriptive: `{{primary_user_journey}}` not `{{puj}}`
+
+## Flow Control
+
+### Sub-Steps
+
+```xml
+<step n="3" goal="Process items">
+  <step n="3a" title="Gather data">
+    <action>Collect information</action>
+  </step>
+
+  <step n="3b" title="Analyze">
+    <action>Process collected data</action>
+    <template-output>analysis</template-output>
+  </step>
+</step>
+```
+
+### Repetition
+
+```xml
+<!-- Fixed repetitions -->
+<step n="4" repeat="3">
+  <action>Generate example {{iteration}}</action>
+</step>
+
+<!-- Conditional repetition -->
+<step n="5" repeat="until-approved">
+  <action>Generate content</action>
+  <ask>Satisfactory? (y/n)</ask>
+</step>
+
+<!-- For-each repetition -->
+<step n="6" repeat="for-each-epic">
+  <action>Define epic {{epic_name}}</action>
+</step>
+```
+
+### Branching and Goto
+
+```xml
+<step n="7" goal="Validate">
+  <action>Check requirements</action>
+  <check>If incomplete:</check>
+  <goto step="2">Return to gathering</goto>
+  <check>If complete:</check>
+  <continue>Proceed</continue>
+</step>
+```
+
+### Loops
+
+```xml
+<step n="8" goal="Refine">
+  <loop max="5">
+    <action>Generate solution</action>
+    <check>If criteria met:</check>
+    <break>Exit loop</break>
+  </loop>
+</step>
+```
+
+### Common XML Tags
+
+**Execution:**
+
+- `<action>` - Required action
+- `<check>` - Conditional check
+- `<ask>` - User prompt
+- `<goto>` - Jump to step
+- `<invoke-workflow>` - Call another workflow
+
+**Output:**
+
+- `<template-output>` - Save checkpoint
+- `<elicit-required/>` - Trigger AI enhancement
+- `<critical>` - Important info
+- `<example>` - Show example
+
+## Validation
+
+### checklist.md Structure
+
+```markdown
+# Validation Checklist
+
+## Structure
+
+- [ ] All sections present
+- [ ] No placeholders remain
+- [ ] Proper formatting
+
+## Content Quality
+
+- [ ] Clear and specific
+- [ ] Technically accurate
+- [ ] Consistent terminology
+
+## Completeness
+
+- [ ] Ready for next phase
+- [ ] Dependencies documented
+- [ ] Action items defined
+```
+
+### Making Criteria Measurable
+
+❌ `- [ ] Good documentation`
+✅ `- [ ] Each function has JSDoc comments with parameters and return types`
+
+## Examples
+
+### Document Generation
+
+```xml
+<workflow>
+<step n="1" goal="Gather context">
+Load existing documents and understand project scope.
+<template-output>context</template-output>
+</step>
+
+<step n="2" goal="Define requirements">
+Create functional and non-functional requirements.
+<template-output>requirements</template-output>
+<elicit-required/>
+</step>
+
+<step n="3" goal="Validate">
+Check requirements against goals.
+<template-output>validated_requirements</template-output>
+</step>
+</workflow>
+```
+
+### Action Workflow
+
+```xml
+<workflow>
+<step n="1" goal="Analyze codebase">
+  <action>Find all API endpoints</action>
+  <action>Identify patterns</action>
+</step>
+
+<step n="2" goal="Refactor">
+  <repeat for-each="endpoint">
+    <action>Update to new pattern</action>
+  </repeat>
+</step>
+
+<step n="3" goal="Verify">
+  <action>Run tests</action>
+  <check>If tests fail:</check>
+  <goto step="2">Fix issues</goto>
+</step>
+</workflow>
+```
+
+### Meta-Workflow
+
+```xml
+<workflow name="greenfield-app">
+<step n="1" goal="Discovery">
+  <invoke-workflow>product-brief</invoke-workflow>
+  <template-output>brief</template-output>
+</step>
+
+<step n="2" goal="Requirements">
+  <invoke-workflow input="{{brief}}">prd</invoke-workflow>
+  <template-output>prd</template-output>
+</step>
+
+<step n="3" goal="Architecture">
+  <invoke-workflow input="{{prd}}">architecture</invoke-workflow>
+  <template-output>architecture</template-output>
+</step>
+</workflow>
+```
+
+## Best Practices
+
+### Design Principles
+
+1. **Keep steps focused** - Single goal per step
+2. **Limit scope** - 5-10 steps maximum
+3. **Build progressively** - Start simple, add detail
+4. **Checkpoint often** - Save after major sections
+5. **Make sections optional** - Let users skip when appropriate
+
+### Instruction Guidelines
+
+1. **Be specific** - "Write 1-2 paragraphs" not "Write about"
+2. **Provide examples** - Show expected output format
+3. **Set limits** - "3-5 items maximum"
+4. **Explain why** - Context helps AI make better decisions
+
+### Common Pitfalls
+
+- **Missing critical headers** - Always include workflow engine references
+- **Variables not replaced** - Ensure names match exactly
+- **Too many steps** - Combine related actions
+- **No checkpoints** - Add `<template-output>` tags
+- **Vague instructions** - Be explicit about expectations
+
+## Troubleshooting
+
+### Variables Not Replaced
+
+- Check exact name match
+- Verify `<template-output>` tag present
+- Ensure step generates the variable
+
+### Validation Fails
+
+- Review checklist specificity
+- Check for impossible requirements
+- Verify checklist matches template
+
+### Workflow Too Long
+
+- Combine related steps
+- Make sections optional
+- Reduce elicitation points
+
+### User Confusion
+
+- Add clearer step goals
+- Provide more examples
+- Explain section purpose
+
+---
+
+_For implementation details, see:_
+
+- `/src/core/tasks/workflow.md` - Execution engine
+- `/bmad/bmm/workflows/` - Production examples

bmad/bmb/workflows/create-workflow/workflow-template/checklist.md

@@ -0,0 +1,24 @@
+# {Title} Checklist Validation
+
+## {Section Foo}
+
+- [ ] Check 1
+- [ ] Check 2
+- [ ] ...
+- [ ] Check n
+
+...
+
+## {Section Bar}
+
+- [ ] Check 1
+- [ ] Check 2
+- [ ] ...
+- [ ] Check n
+
+## Final Validation
+
+- [ ] Section Foo
+  - Issue List
+- [ ] Section Bar
+  - Issue List

bmad/bmb/workflows/create-workflow/workflow-template/instructions.md

@@ -0,0 +1,12 @@
+# PRD Workflow Instructions
+
+<workflow>
+
+<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
+<critical>You MUST have already loaded and processed: {project_root}/bmad/{module-code}/workflows/{workflow}/workflow.yaml</critical>
+
+<step n="1" goal="">
+...
+</step>
+...
+</workflow>

bmad/bmb/workflows/create-workflow/workflow-template/template.md

@@ -0,0 +1,9 @@
+# Title
+
+**Date:** {{date}}
+
+## {Section 1}
+
+{{section_1_results}}
+
+etc...

bmad/bmb/workflows/create-workflow/workflow-template/workflow.yaml

@@ -0,0 +1,35 @@
+# {TITLE} Workflow Template Configuration
+name: "{WORKFLOW_CODE}"
+description: "{WORKFLOW_DESCRIPTION}"
+author: "BMad"
+
+# Critical variables load from config_source
+# Add Additional Config Pulled Variables Here
+config_source: "{project-root}/{module-code}/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+date: system-generated
+
+# Required Data Files - HALT if missing!
+# optional, can be omitted
+brain_techniques: "{installed_path}/{critical-data-file.csv}" # example, can be other formats or URLs
+
+# Optional docs that if loaded on start to kickstart this workflow or used at some point, these are meant to be suggested inputs for the user
+recommended_inputs: # optional, can be omitted
+  - example_input: "{project-root}/{path/to/file.md}"
+
+# Module path and component files
+installed_path: "{project-root}/bmad/{module-code}/workflows/{workflow-code}"
+template: "{installed_path}/template.md" # optional, can be omitted
+instructions: "{installed_path}/instructions.md" # optional, can be omitted
+validation: "{installed_path}/checklist.md" # optional, can be omitted
+
+# Output configuration
+default_output_file: "{output_folder}/{file.md}" # optional, can be omitted
+validation_output_file: "{output_folder}/{file-validation-report.md}" # optional, can be omitted
+
+# Tool Requirements (MCP Required Tools or other tools needed to run this workflow)
+required_tools: #optional, can be omitted
+  - "Tool Name": #example, can be omitted if none
+      description: "Description of why this tool is needed"
+      link: "https://link-to-tool.com"

bmad/bmb/workflows/create-workflow/workflow.yaml

@@ -0,0 +1,39 @@
+# Build Workflow - Workflow Builder Configuration
+name: create-workflow
+description: "Interactive workflow builder that guides creation of new BMAD workflows with proper structure and validation for optimal human-AI collaboration. Includes optional brainstorming phase for workflow ideas and design."
+author: "BMad Builder"
+
+# Critical variables
+config_source: "{project-root}/bmad/bmb/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+src_impact: "{config_source}:src_impact"
+communication_language: "{config_source}:communication_language"
+date: system-generated
+
+# Template files for new workflows
+template_workflow_yaml: "{workflow_template_path}/workflow.yaml"
+template_instructions: "{workflow_template_path}/instructions.md"
+template_template: "{workflow_template_path}/template.md"
+template_checklist: "{workflow_template_path}/checklist.md"
+
+# Optional input docs
+recommended_inputs:
+  - existing_workflows: "{project-root}/bmad/*/workflows/"
+  - bmm_workflows: "{project-root}/bmad/bmm/workflows/"
+
+# Module path and component files
+installed_path: "{project-root}/bmad/bmb/workflows/create-workflow"
+template: false # This is an action workflow - no template needed
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+
+# Required data files - CRITICAL for workflow conventions
+workflow_creation_guide: "{installed_path}/workflow-creation-guide.md"
+workflow_template_path: "{installed_path}/workflow-template"
+
+# Output configuration - Creates the new workflow folder with all files
+# If src_impact=true: Save to src/modules/{{target_module}}/workflows/{{workflow_name}}
+# If src_impact=false: Save to output_folder/workflows/{{workflow_name}}
+default_output_folder: "{output_folder}/workflows/{{workflow_name}}"
+src_output_folder: "{project-root}/src/modules/{{target_module}}/workflows/{{workflow_name}}"

bmad/bmb/workflows/edit-workflow/README.md

@@ -0,0 +1,63 @@
+# Edit Workflow
+
+## Purpose
+
+An intelligent workflow editor that helps you modify existing BMAD workflows while adhering to all best practices and conventions documented in the workflow creation guide.
+
+## Use Case
+
+When you need to:
+
+- Fix issues in existing workflows
+- Update workflow configuration or metadata
+- Improve instruction clarity and specificity
+- Add new features or capabilities
+- Ensure compliance with BMAD workflow conventions
+
+## How to Invoke
+
+```
+workflow edit-workflow
+```
+
+Or through a BMAD agent:
+
+```
+*edit-workflow
+```
+
+## Expected Inputs
+
+- **Target workflow path**: Path to the workflow.yaml file or workflow folder you want to edit
+- **Edit type selection**: Choice of what aspect to modify
+- **User approval**: For each proposed change
+
+## Generated Outputs
+
+- Modified workflow files (in place)
+- Optional change log at: `{output_folder}/workflow-edit-log-{date}.md`
+
+## Features
+
+1. **Comprehensive Analysis**: Checks workflows against the official creation guide
+2. **Prioritized Issues**: Identifies and ranks issues by importance
+3. **Guided Editing**: Step-by-step process with explanations
+4. **Best Practices**: Ensures all edits follow BMAD conventions
+5. **Validation**: Checks all changes for correctness
+6. **Change Tracking**: Documents what was modified and why
+
+## Workflow Steps
+
+1. Load and analyze target workflow
+2. Check against best practices
+3. Select editing focus
+4. Load relevant documentation
+5. Perform edits with user approval
+6. Validate all changes (optional)
+7. Generate change summary
+
+## Requirements
+
+- Access to workflow creation guide
+- Read/write permissions for target workflow
+- Understanding of BMAD workflow types

bmad/bmb/workflows/edit-workflow/checklist.md

@@ -0,0 +1,70 @@
+# Edit Workflow - Validation Checklist
+
+## Pre-Edit Analysis
+
+- [ ] Target workflow.yaml file successfully loaded and parsed
+- [ ] All referenced workflow files identified and accessible
+- [ ] Workflow type correctly determined (document/action/interactive/autonomous/meta)
+- [ ] Best practices guide loaded and available for reference
+
+## Edit Execution Quality
+
+- [ ] User clearly informed of identified issues with priority levels
+- [ ] Edit menu presented with all 8 standard options
+- [ ] Selected edit type matches the actual changes made
+- [ ] All proposed changes explained with reasoning before application
+
+## File Integrity
+
+- [ ] All modified files maintain valid YAML/Markdown syntax
+- [ ] No placeholders like {TITLE} or {WORKFLOW_CODE} remain in edited files
+- [ ] File paths use proper variable substitution ({project-root}, {installed_path})
+- [ ] All file references resolve to actual paths
+
+## Convention Compliance
+
+- [ ] Instructions.md contains critical workflow engine reference header
+- [ ] Instructions.md contains workflow.yaml processing reference header
+- [ ] All step numbers are sequential (1, 2, 3... or 1a, 1b, 2a...)
+- [ ] Each step has both n= attribute and goal= attribute
+- [ ] Variable names use snake_case consistently
+- [ ] Template variables (if any) match <template-output> tags exactly
+
+## Instruction Quality
+
+- [ ] Each step has a single, clear goal stated
+- [ ] Instructions are specific with quantities (e.g., "3-5 items" not "several items")
+- [ ] Optional steps marked with optional="true" attribute
+- [ ] Repeating steps use proper repeat syntax (repeat="3" or repeat="until-complete")
+- [ ] User prompts use <ask> tags and wait for response
+- [ ] Actions use <action> tags for required operations
+
+## Validation Criteria (if checklist.md exists)
+
+- [ ] All checklist items are measurable and specific
+- [ ] No vague criteria like "Good documentation" present
+- [ ] Checklist organized into logical sections
+- [ ] Each criterion can be objectively verified as true/false
+
+## Change Documentation
+
+- [ ] All changes logged with description of what and why
+- [ ] Change summary includes list of modified files
+- [ ] Improvements clearly articulated in relation to best practices
+- [ ] Next steps or recommendations provided
+
+## Post-Edit Verification
+
+- [ ] Edited workflow follows patterns from production examples
+- [ ] No functionality broken by the edits
+- [ ] Workflow ready for testing or production use
+- [ ] User given option to test the edited workflow
+
+## Common Issues Resolved
+
+- [ ] Missing critical headers added if they were absent
+- [ ] Broken variable references fixed
+- [ ] Vague instructions made specific
+- [ ] Template-only workflows have template.md file
+- [ ] Action workflows have template: false in workflow.yaml
+- [ ] Step count reasonable (5-10 steps maximum unless justified)

bmad/bmb/workflows/edit-workflow/instructions.md

@@ -0,0 +1,170 @@
+# Edit Workflow - Workflow Editor Instructions
+
+<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.md</critical>
+<critical>You MUST have already loaded and processed: {project-root}/bmad/bmb/workflows/edit-workflow/workflow.yaml</critical>
+<critical>Study the workflow creation guide thoroughly at: {workflow_creation_guide}</critical>
+
+<workflow>
+
+<step n="1" goal="Load and analyze target workflow">
+<ask>What is the path to the workflow you want to edit? (provide path to workflow.yaml or workflow folder)</ask>
+
+<action>Load the workflow.yaml file from the provided path</action>
+<action>Identify the workflow type (document, action, interactive, autonomous, meta)</action>
+<action>List all associated files (template.md, instructions.md, checklist.md, data files)</action>
+<action>Load any existing instructions.md and template.md files if present</action>
+
+Display a summary:
+
+- Workflow name and description
+- Type of workflow
+- Files present
+- Current structure overview
+  </step>
+
+<step n="2" goal="Analyze against best practices">
+<action>Load the complete workflow creation guide from: {workflow_creation_guide}</action>
+<action>Check the workflow against the guide's best practices:</action>
+
+Analyze for:
+
+- **Critical headers**: Are workflow engine references present?
+- **File structure**: Are all expected files present for this workflow type?
+- **Variable consistency**: Do variable names match between files?
+- **Step structure**: Are steps properly numbered and focused?
+- **XML tags**: Are tags used correctly and consistently?
+- **Instructions clarity**: Are instructions specific with examples and limits?
+- **Template variables**: Use snake_case and descriptive names?
+- **Validation criteria**: Are checklist items measurable and specific?
+
+<action>Create a list of identified issues or improvement opportunities</action>
+<action>Prioritize issues by importance (critical, important, nice-to-have)</action>
+</step>
+
+<step n="3" goal="Select editing focus">
+Present the editing menu to the user:
+
+**What aspect would you like to edit?**
+
+1. **Fix critical issues** - Address missing headers, broken references
+2. **Update workflow.yaml** - Modify configuration, paths, metadata
+3. **Refine instructions** - Improve steps, add detail, fix flow
+4. **Update template** - Fix variables, improve structure (if applicable)
+5. **Enhance validation** - Make checklist more specific and measurable
+6. **Add new features** - Add steps, optional sections, or capabilities
+7. **Optimize for clarity** - Improve descriptions, add examples
+8. **Full review and update** - Comprehensive improvements across all files
+
+<ask>Select an option (1-8) or describe a custom edit:</ask>
+</step>
+
+<step n="4" goal="Load relevant documentation">
+Based on the selected edit type, load appropriate reference materials:
+
+<check>If editing instructions or adding features:</check>
+<action>Review the "Writing Instructions" section of the creation guide</action>
+<action>Load example workflows from {project-root}/bmad/bmm/workflows/ for patterns</action>
+
+<check>If editing templates:</check>
+<action>Review the "Templates and Variables" section of the creation guide</action>
+<action>Ensure variable naming conventions are followed</action>
+
+<check>If editing validation:</check>
+<action>Review the "Validation" section and measurable criteria examples</action>
+
+<check>If fixing critical issues:</check>
+<action>Load the workflow execution engine documentation</action>
+<action>Verify all required elements are present</action>
+</step>
+
+<step n="5" goal="Perform edits" repeat="until-complete">
+Based on the selected focus area:
+
+<action>Show the current content that will be edited</action>
+<action>Explain the proposed changes and why they improve the workflow</action>
+<action>Generate the updated content following all conventions from the guide</action>
+
+<ask>Review the proposed changes. Options:
+
+- [a] Accept and apply
+- [e] Edit/modify the changes
+- [s] Skip this change
+- [n] Move to next file/section
+- [d] Done with edits
+  </ask>
+
+<check>If user selects 'a':</check>
+<action>Apply the changes to the file</action>
+<action>Log the change for the summary</action>
+
+<check>If user selects 'e':</check>
+<ask>What modifications would you like to make?</ask>
+<goto step="5">Regenerate with modifications</goto>
+
+<check>If user selects 'd':</check>
+<continue>Proceed to validation</continue>
+</step>
+
+<step n="6" goal="Validate all changes" optional="true">
+<action>Run a comprehensive validation check:</action>
+
+Validation checks:
+
+- [ ] All file paths resolve correctly
+- [ ] Variable names are consistent across files
+- [ ] Step numbering is sequential and logical
+- [ ] Required XML tags are properly formatted
+- [ ] No placeholders remain (like {TITLE} or {WORKFLOW_CODE})
+- [ ] Instructions match the workflow type
+- [ ] Template variables match instruction outputs (if applicable)
+- [ ] Checklist criteria are measurable (if present)
+- [ ] Critical headers are present in instructions
+- [ ] YAML syntax is valid
+
+<check>If any validation fails:</check>
+<ask>Issues found. Would you like to fix them? (y/n)</ask>
+<check>If yes:</check>
+<goto step="5">Return to editing</goto>
+</step>
+
+<step n="7" goal="Generate change summary">
+Create a summary of all changes made:
+
+## Workflow Edit Summary
+
+**Workflow:** {{workflow_name}}
+**Date:** {{date}}
+**Editor:** {{user_name}}
+
+### Changes Made:
+
+<action>List each file that was modified with a brief description of changes</action>
+
+### Improvements:
+
+<action>Summarize how the workflow is now better aligned with best practices</action>
+
+### Files Modified:
+
+<action>List all modified files with their paths</action>
+
+### Next Steps:
+
+<action>Suggest any additional improvements or testing that could be done</action>
+
+<ask>Would you like to:
+
+- Save this summary to: {change_log_output}
+- Test the edited workflow
+- Make additional edits
+- Exit
+  </ask>
+
+<check>If save summary:</check>
+<action>Write the summary to the change log file</action>
+
+<check>If test workflow:</check>
+<invoke-workflow>{{workflow_name}}</invoke-workflow>
+</step>
+
+</workflow>

bmad/bmb/workflows/edit-workflow/workflow.yaml

@@ -0,0 +1,31 @@
+# Edit Workflow - Workflow Editor Configuration
+name: "edit-workflow"
+description: "Edit existing BMAD workflows while following all best practices and conventions"
+author: "BMad"
+
+# Critical variables load from config_source
+config_source: "{project-root}/bmad/bmb/config.yaml"
+output_folder: "{config_source}:output_folder"
+src_impact: "{config_source}:src_impact"
+communication_language: "{config_source}:communication_language"
+user_name: "{config_source}:user_name"
+date: system-generated
+
+# Required Data Files - Critical for understanding workflow conventions
+workflow_creation_guide: "{project-root}/bmad/bmb/workflows/create-workflow/workflow-creation-guide.md"
+workflow_execution_engine: "{project-root}/bmad/core/tasks/workflow.md"
+
+# Optional docs that can be used to understand the target workflow
+recommended_inputs:
+  - target_workflow: "Path to the workflow.yaml file to edit"
+  - workflow_examples: "{project-root}/bmad/bmm/workflows/"
+
+# Module path and component files
+installed_path: "{project-root}/bmad/bmb/workflows/edit-workflow"
+template: false # This is an action workflow - no template needed
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+
+# No output file for action workflows
+# But we may generate a change log
+change_log_output: "{output_folder}/workflow-edit-log-{{date}}.md"

bmad/bmb/workflows/module-brief/README.md

@@ -0,0 +1,264 @@
+# Module Brief Workflow
+
+## Overview
+
+The Module Brief workflow creates comprehensive blueprints for building new BMAD modules using strategic analysis and creative vision. It serves as the essential planning phase that transforms initial ideas into detailed, actionable specifications ready for implementation with the create-module workflow.
+
+## Key Features
+
+- **Strategic Module Planning** - Comprehensive analysis from concept to implementation roadmap
+- **Multi-Mode Operation** - Interactive, Express, and YOLO modes for different planning needs
+- **Creative Vision Development** - Guided process for innovative module concepts and unique value propositions
+- **Architecture Design** - Detailed agent and workflow ecosystem planning with interaction models
+- **User Journey Mapping** - Scenario-based validation ensuring practical usability
+- **Technical Planning** - Infrastructure requirements, dependencies, and complexity assessment
+- **Risk Assessment** - Proactive identification of challenges with mitigation strategies
+- **Implementation Roadmap** - Phased development plan with clear deliverables and timelines
+
+## Usage
+
+### Basic Invocation
+
+```bash
+workflow module-brief
+```
+
+### With Brainstorming Input
+
+```bash
+# If you have brainstorming results from previous sessions
+workflow module-brief --input brainstorming-session-2024-09-26.md
+```
+
+### Express Mode
+
+```bash
+# For quick essential planning only
+workflow module-brief --mode express
+```
+
+### Configuration
+
+The workflow uses standard BMB configuration:
+
+- **output_folder**: Where the module brief will be saved
+- **user_name**: Brief author information
+- **communication_language**: Language for brief generation
+- **date**: Automatic timestamp for versioning
+
+## Workflow Structure
+
+### Files Included
+
+```
+module-brief/
+├── workflow.yaml           # Configuration and metadata
+├── instructions.md         # Step-by-step execution guide
+├── template.md            # Module brief document structure
+├── checklist.md           # Validation criteria
+└── README.md              # This file
+```
+
+## Workflow Process
+
+### Phase 1: Foundation and Context (Steps 1-3)
+
+**Mode Selection and Input Gathering**
+
+- Choose operational mode (Interactive, Express, YOLO)
+- Check for and optionally load existing brainstorming results
+- Gather background context and inspiration sources
+
+**Module Vision Development**
+
+- Define core problem the module solves
+- Identify target user audience and use cases
+- Establish unique value proposition and differentiators
+- Explore creative themes and personality concepts
+
+**Module Identity Establishment**
+
+- Generate module code (kebab-case) with multiple options
+- Create compelling, memorable module name
+- Select appropriate category (Domain-Specific, Creative, Technical, Business, Personal)
+- Define optional personality theme for consistent agent character
+
+### Phase 2: Architecture Planning (Steps 4-5)
+
+**Agent Architecture Design**
+
+- Plan agent team composition and roles
+- Define agent archetypes (Orchestrator, Specialist, Helper, Creator, Analyzer)
+- Specify personality traits and communication styles
+- Map key capabilities and signature commands
+
+**Workflow Ecosystem Design**
+
+- Categorize workflows by purpose and complexity:
+  - **Core Workflows**: Essential value-delivery functions (2-3)
+  - **Feature Workflows**: Specialized capabilities (3-5)
+  - **Utility Workflows**: Supporting operations (1-3)
+- Define input-process-output flows for each workflow
+- Assess complexity levels and implementation priorities
+
+### Phase 3: Validation and User Experience (Steps 6-7)
+
+**User Journey Mapping**
+
+- Create detailed user scenarios and stories
+- Map step-by-step usage flows through the module
+- Validate end-to-end functionality and value delivery
+- Identify potential friction points and optimization opportunities
+
+**Technical Planning and Requirements**
+
+- Assess data requirements and storage needs
+- Map integration points with other modules and external systems
+- Evaluate technical complexity and resource requirements
+- Document dependencies and infrastructure needs
+
+### Phase 4: Success Planning (Steps 8-9)
+
+**Success Metrics Definition**
+
+- Establish module success criteria and performance indicators
+- Define quality standards and reliability requirements
+- Create user experience goals and feedback mechanisms
+- Set measurable outcomes for module effectiveness
+
+**Development Roadmap Creation**
+
+- Design phased approach with MVP, Enhancement, and Polish phases
+- Define deliverables and timelines for each phase
+- Prioritize features and capabilities by value and complexity
+- Create clear milestones and success checkpoints
+
+### Phase 5: Enhancement and Risk Management (Steps 10-12)
+
+**Creative Features and Special Touches** (Optional)
+
+- Design easter eggs and delightful user interactions
+- Plan module lore and thematic consistency
+- Add personality quirks and creative responses
+- Develop backstories and universe building
+
+**Risk Assessment and Mitigation**
+
+- Identify technical, usability, and scope risks
+- Develop mitigation strategies for each risk category
+- Plan contingency approaches for potential challenges
+- Document decision points and alternative paths
+
+**Final Review and Export Preparation**
+
+- Comprehensive review of all brief sections
+- Validation against quality and completeness criteria
+- Preparation for seamless handoff to create-module workflow
+- Export readiness confirmation with actionable specifications
+
+## Output
+
+### Generated Files
+
+- **Module Brief Document**: Comprehensive planning document at `{output_folder}/module-brief-{module_code}-{date}.md`
+- **Strategic Specifications**: Ready-to-implement blueprint for create-module workflow
+
+### Output Structure
+
+The module brief contains detailed specifications across multiple sections:
+
+1. **Executive Summary** - Vision, category, complexity, target users
+2. **Module Identity** - Core concept, value proposition, personality theme
+3. **Agent Architecture** - Agent roster, roles, interaction models
+4. **Workflow Ecosystem** - Core, feature, and utility workflow specifications
+5. **User Scenarios** - Primary use cases, secondary scenarios, user journey
+6. **Technical Planning** - Data requirements, integrations, dependencies
+7. **Success Metrics** - Success criteria, quality standards, performance targets
+8. **Development Roadmap** - Phased implementation plan with deliverables
+9. **Creative Features** - Special touches, easter eggs, module lore
+10. **Risk Assessment** - Technical, usability, scope risks with mitigation
+11. **Implementation Notes** - Priority order, design decisions, open questions
+12. **Resources and References** - Inspiration sources, similar modules, technical references
+
+## Requirements
+
+- **Creative Vision** - Initial module concept or problem domain
+- **Strategic Thinking** - Ability to plan architecture and user experience
+- **Brainstorming Results** (optional) - Previous ideation sessions enhance planning quality
+
+## Best Practices
+
+### Before Starting
+
+1. **Gather Inspiration** - Research similar tools, modules, and solutions in your domain
+2. **Run Brainstorming Session** - Use ideation techniques to generate initial concepts
+3. **Define Success Criteria** - Know what "successful module" means for your context
+
+### During Execution
+
+1. **Think User-First** - Always consider the end user experience and value delivery
+2. **Be Specific** - Provide concrete examples and detailed specifications rather than abstractions
+3. **Validate Early** - Use user scenarios to test if the module concept actually works
+4. **Plan Iteratively** - Start with MVP and build complexity through phases
+
+### After Completion
+
+1. **Use as Blueprint** - Feed the brief directly into create-module workflow for implementation
+2. **Review with Stakeholders** - Validate assumptions and gather feedback before building
+3. **Update as Needed** - Treat as living document that evolves with implementation learnings
+4. **Reference During Development** - Use as north star for design decisions and scope management
+
+## Troubleshooting
+
+### Common Issues
+
+**Issue**: Stuck on module concept or vision
+
+- **Solution**: Use creative prompts provided in the workflow
+- **Check**: Review existing modules for inspiration and patterns
+
+**Issue**: Agent or workflow architecture too complex
+
+- **Solution**: Focus on MVP first, plan enhancement phases for additional complexity
+- **Check**: Validate each component against user scenarios
+
+**Issue**: Technical requirements unclear
+
+- **Solution**: Research similar modules and their implementation approaches
+- **Check**: Consult with technical stakeholders early in planning
+
+**Issue**: Scope creep during planning
+
+- **Solution**: Use phased roadmap to defer non-essential features
+- **Check**: Regularly validate against core user scenarios and success criteria
+
+## Customization
+
+To customize this workflow:
+
+1. **Modify Template Structure** - Update template.md to add new sections or reorganize content
+2. **Extend Creative Prompts** - Add domain-specific ideation techniques in instructions.md
+3. **Add Planning Tools** - Integrate additional analysis frameworks or planning methodologies
+4. **Customize Validation** - Enhance checklist.md with specific quality criteria for your context
+
+## Version History
+
+- **v1.0.0** - Initial release
+  - Comprehensive strategic module planning
+  - Multi-mode operation (Interactive, Express, YOLO)
+  - Creative vision and architecture design tools
+  - User journey mapping and validation
+  - Risk assessment and mitigation planning
+
+## Support
+
+For issues or questions:
+
+- Review the workflow creation guide at `/bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
+- Study existing module examples in `/bmad/` for patterns and inspiration
+- Validate output using `checklist.md`
+- Consult module structure guide at `create-module/module-structure.md`
+
+---
+
+_Part of the BMad Method v5 - BMB (Builder) Module_

bmad/bmb/workflows/module-brief/checklist.md

@@ -0,0 +1,116 @@
+# Module Brief Validation Checklist
+
+## Core Identity
+
+- [ ] Module code follows kebab-case convention
+- [ ] Module name is clear and memorable
+- [ ] Module category is identified
+- [ ] Target users are clearly defined
+- [ ] Unique value proposition is articulated
+
+## Vision and Concept
+
+- [ ] Problem being solved is clearly stated
+- [ ] Solution approach is explained
+- [ ] Module scope is well-defined
+- [ ] Success criteria are measurable
+
+## Agent Architecture
+
+- [ ] At least one agent is defined
+- [ ] Each agent has a clear role and purpose
+- [ ] Agent personalities are defined (if using personality themes)
+- [ ] Agent interactions are mapped (for multi-agent modules)
+- [ ] Key commands for each agent are listed
+
+## Workflow Ecosystem
+
+- [ ] Core workflows (2-3) are identified
+- [ ] Each workflow has clear purpose
+- [ ] Workflow complexity is assessed
+- [ ] Input/output for workflows is defined
+- [ ] Workflow categories are logical
+
+## User Experience
+
+- [ ] Primary use case is documented
+- [ ] User scenarios demonstrate value
+- [ ] User journey is realistic
+- [ ] Learning curve is considered
+- [ ] User feedback mechanism planned
+
+## Technical Planning
+
+- [ ] Data requirements are identified
+- [ ] Integration points are mapped
+- [ ] Dependencies are listed
+- [ ] Technical complexity is assessed
+- [ ] Performance requirements stated
+
+## Development Roadmap
+
+- [ ] Phase 1 MVP is clearly scoped
+- [ ] Phase 2 enhancements are outlined
+- [ ] Phase 3 polish items listed
+- [ ] Timeline estimates provided
+- [ ] Deliverables are specific
+
+## Risk Management
+
+- [ ] Technical risks identified
+- [ ] Usability risks considered
+- [ ] Scope risks acknowledged
+- [ ] Mitigation strategies provided
+- [ ] Open questions documented
+
+## Creative Elements (Optional)
+
+- [ ] Personality theme is consistent (if used)
+- [ ] Special features add value
+- [ ] Module feels cohesive
+- [ ] Fun elements don't compromise functionality
+
+## Documentation Quality
+
+- [ ] All sections have content (no empty placeholders)
+- [ ] Writing is clear and concise
+- [ ] Technical terms are explained
+- [ ] Examples are provided where helpful
+- [ ] Next steps are actionable
+
+## Implementation Readiness
+
+- [ ] Brief provides enough detail for create-module workflow
+- [ ] Agent specifications sufficient for create-agent workflow
+- [ ] Workflow descriptions ready for create-workflow
+- [ ] Resource requirements are clear
+- [ ] Success metrics are measurable
+
+## Final Validation
+
+- [ ] Module concept is viable
+- [ ] Scope is achievable
+- [ ] Value is clear
+- [ ] Brief is complete
+- [ ] Ready for development
+
+## Issues Found
+
+### Critical Issues
+
+<!-- Must be fixed before proceeding to build -->
+
+### Recommendations
+
+<!-- Suggested improvements -->
+
+### Nice-to-Haves
+
+<!-- Optional enhancements -->
+
+---
+
+**Validation Complete:** ⬜ Yes / ⬜ With Issues / ⬜ Needs Revision
+
+**Validated By:** **\*\*\*\***\_**\*\*\*\***
+**Date:** **\*\*\*\***\_**\*\*\*\***

bmad/bmb/workflows/module-brief/instructions.md

@@ -0,0 +1,265 @@
+# Module Brief Instructions
+
+<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
+<critical>You MUST have already loaded and processed: {project_root}/bmad/bmb/workflows/module-brief/workflow.yaml</critical>
+
+<workflow>
+
+<step n="1" goal="Setup and context gathering">
+<action>Ask the user which mode they prefer:</action>
+1. **Interactive Mode** - Work through each section collaboratively with detailed questions
+2. **Express Mode** - Quick essential questions only
+3. **YOLO Mode** (#yolo) - Generate complete draft based on minimal input
+
+<action>Check for available inputs:</action>
+
+- Brainstorming results from previous sessions
+- Existing module ideas or notes
+- Similar modules for inspiration
+
+<action>If brainstorming results exist, offer to load and incorporate them</action>
+</step>
+
+<step n="2" goal="Module concept and vision">
+Ask the user to describe their module idea. Probe for:
+- What problem does this module solve?
+- Who would use this module?
+- What makes this module exciting or unique?
+- Any inspiring examples or similar tools?
+
+If they're stuck, offer creative prompts:
+
+- "Imagine you're a [role], what tools would make your life easier?"
+- "What repetitive tasks could be automated with agents?"
+- "What domain expertise could be captured in workflows?"
+
+<template-output>module_vision</template-output>
+</step>
+
+<step n="3" goal="Define module identity">
+Based on the vision, work with user to define:
+
+**Module Code** (kebab-case):
+
+- Suggest 2-3 options based on their description
+- Ensure it's memorable and descriptive
+
+**Module Name** (friendly):
+
+- Creative, engaging name that captures the essence
+
+**Module Category:**
+
+- Domain-Specific (legal, medical, finance)
+- Creative (writing, gaming, music)
+- Technical (devops, testing, architecture)
+- Business (project management, marketing)
+- Personal (productivity, learning)
+
+**Personality Theme** (optional but fun!):
+
+- Should the module have a consistent personality across agents?
+- Star Trek crew? Fantasy party? Corporate team? Reality show cast?
+
+<template-output>module_identity</template-output>
+</step>
+
+<step n="4" goal="Agent architecture planning">
+<action>Help user envision their agent team</action>
+
+For each agent, capture:
+
+- **Role**: What's their specialty?
+- **Personality**: How do they communicate? (reference communication styles)
+- **Key Capabilities**: What can they do?
+- **Signature Commands**: 2-3 main commands
+
+Suggest agent archetypes based on module type:
+
+- The Orchestrator (manages other agents)
+- The Specialist (deep expertise)
+- The Helper (utility functions)
+- The Creator (generates content)
+- The Analyzer (processes and evaluates)
+
+<template-output>agent_architecture</template-output>
+</step>
+
+<step n="5" goal="Workflow ecosystem design">
+<action>Map out the workflow landscape</action>
+
+Categorize workflows:
+
+**Core Workflows** (2-3 essential ones):
+
+- The primary value-delivery workflows
+- What users will use most often
+
+**Feature Workflows** (3-5 specialized):
+
+- Specific capabilities
+- Advanced features
+
+**Utility Workflows** (1-3 supporting):
+
+- Setup, configuration
+- Maintenance, cleanup
+
+For each workflow, define:
+
+- Purpose (one sentence)
+- Input → Process → Output
+- Complexity (simple/standard/complex)
+
+<template-output>workflow_ecosystem</template-output>
+</step>
+
+<step n="6" goal="User journey and scenarios">
+<action>Create usage scenarios to validate the design</action>
+
+Write 2-3 user stories:
+"As a [user type], I want to [goal], so that [outcome]"
+
+Then walk through how they'd use the module:
+
+1. They load [agent]
+2. They run [command/workflow]
+3. They get [result]
+4. This helps them [achievement]
+
+This validates the module makes sense end-to-end.
+
+<template-output>user_scenarios</template-output>
+</step>
+
+<step n="7" goal="Technical and resource planning">
+Assess technical requirements:
+
+**Data Requirements:**
+
+- What data/files does the module need?
+- Any external APIs or services?
+- Storage or state management needs?
+
+**Integration Points:**
+
+- Other BMAD modules it might use
+- External tools or platforms
+- Import/export formats
+
+**Complexity Assessment:**
+
+- Simple (standalone, no dependencies)
+- Standard (some integrations, moderate complexity)
+- Complex (multiple systems, advanced features)
+
+<template-output>technical_planning</template-output>
+</step>
+
+<step n="8" goal="Success metrics and validation">
+Define what success looks like:
+
+**Module Success Criteria:**
+
+- What indicates the module is working well?
+- How will users measure value?
+- What feedback mechanisms?
+
+**Quality Standards:**
+
+- Performance expectations
+- Reliability requirements
+- User experience goals
+
+<template-output>success_metrics</template-output>
+</step>
+
+<step n="9" goal="Development roadmap">
+Create a phased approach:
+
+**Phase 1 - MVP (Minimum Viable Module):**
+
+- 1 primary agent
+- 2-3 core workflows
+- Basic functionality
+
+**Phase 2 - Enhancement:**
+
+- Additional agents
+- More workflows
+- Refined features
+
+**Phase 3 - Polish:**
+
+- Advanced features
+- Optimizations
+- Nice-to-haves
+
+<template-output>development_roadmap</template-output>
+</step>
+
+<step n="10" goal="Creative flourishes and special features" optional="true">
+<action>If user wants to add special touches:</action>
+
+**Easter Eggs:**
+
+- Hidden commands or responses
+- Fun interactions between agents
+
+**Delighters:**
+
+- Unexpected helpful features
+- Personality quirks
+- Creative responses
+
+**Module Lore:**
+
+- Backstory for agents
+- Thematic elements
+- Consistent universe
+
+<template-output>creative_features</template-output>
+</step>
+
+<step n="11" goal="Risk assessment and mitigation">
+Identify potential challenges:
+
+**Technical Risks:**
+
+- Complex integrations
+- Performance concerns
+- Dependency issues
+
+**Usability Risks:**
+
+- Learning curve
+- Complexity creep
+- User confusion
+
+**Scope Risks:**
+
+- Feature bloat
+- Timeline expansion
+- Resource constraints
+
+For each risk, note mitigation strategy.
+
+<template-output>risk_assessment</template-output>
+</step>
+
+<step n="12" goal="Final review and export readiness">
+<action>Review all sections with user</action>
+<action>Ensure module brief is ready for create-module workflow</action>
+
+Ask if they want to:
+
+1. Proceed directly to create-module workflow
+2. Save and refine later
+3. Generate additional planning documents
+
+<action>Highlight that this brief can be fed directly into create-module workflow!</action>
+
+<template-output>final_brief</template-output>
+</step>
+
+</workflow>

bmad/bmb/workflows/module-brief/template.md

@@ -0,0 +1,275 @@
+# Module Brief: {{module_name}}
+
+**Date:** {{date}}
+**Author:** {{user_name}}
+**Module Code:** {{module_code}}
+**Status:** Ready for Development
+
+---
+
+## Executive Summary
+
+{{module_vision}}
+
+**Module Category:** {{module_category}}
+**Complexity Level:** {{complexity_level}}
+**Target Users:** {{target_users}}
+
+---
+
+## Module Identity
+
+### Core Concept
+
+{{module_identity}}
+
+### Unique Value Proposition
+
+What makes this module special:
+{{unique_value}}
+
+### Personality Theme
+
+{{personality_theme}}
+
+---
+
+## Agent Architecture
+
+{{agent_architecture}}
+
+### Agent Roster
+
+{{agent_roster}}
+
+### Agent Interaction Model
+
+How agents work together:
+{{agent_interactions}}
+
+---
+
+## Workflow Ecosystem
+
+{{workflow_ecosystem}}
+
+### Core Workflows
+
+Essential functionality that delivers primary value:
+{{core_workflows}}
+
+### Feature Workflows
+
+Specialized capabilities that enhance the module:
+{{feature_workflows}}
+
+### Utility Workflows
+
+Supporting operations and maintenance:
+{{utility_workflows}}
+
+---
+
+## User Scenarios
+
+### Primary Use Case
+
+{{primary_scenario}}
+
+### Secondary Use Cases
+
+{{secondary_scenarios}}
+
+### User Journey
+
+Step-by-step walkthrough of typical usage:
+{{user_journey}}
+
+---
+
+## Technical Planning
+
+### Data Requirements
+
+{{data_requirements}}
+
+### Integration Points
+
+{{integration_points}}
+
+### Dependencies
+
+{{dependencies}}
+
+### Technical Complexity Assessment
+
+{{technical_planning}}
+
+---
+
+## Success Metrics
+
+### Module Success Criteria
+
+How we'll know the module is successful:
+{{success_criteria}}
+
+### Quality Standards
+
+{{quality_standards}}
+
+### Performance Targets
+
+{{performance_targets}}
+
+---
+
+## Development Roadmap
+
+### Phase 1: MVP (Minimum Viable Module)
+
+**Timeline:** {{phase1_timeline}}
+
+{{phase1_components}}
+
+**Deliverables:**
+{{phase1_deliverables}}
+
+### Phase 2: Enhancement
+
+**Timeline:** {{phase2_timeline}}
+
+{{phase2_components}}
+
+**Deliverables:**
+{{phase2_deliverables}}
+
+### Phase 3: Polish and Optimization
+
+**Timeline:** {{phase3_timeline}}
+
+{{phase3_components}}
+
+**Deliverables:**
+{{phase3_deliverables}}
+
+---
+
+## Creative Features
+
+### Special Touches
+
+{{creative_features}}
+
+### Easter Eggs and Delighters
+
+{{easter_eggs}}
+
+### Module Lore and Theming
+
+{{module_lore}}
+
+---
+
+## Risk Assessment
+
+### Technical Risks
+
+{{technical_risks}}
+
+### Usability Risks
+
+{{usability_risks}}
+
+### Scope Risks
+
+{{scope_risks}}
+
+### Mitigation Strategies
+
+{{risk_mitigation}}
+
+---
+
+## Implementation Notes
+
+### Priority Order
+
+1. {{priority_1}}
+2. {{priority_2}}
+3. {{priority_3}}
+
+### Key Design Decisions
+
+{{design_decisions}}
+
+### Open Questions
+
+{{open_questions}}
+
+---
+
+## Resources and References
+
+### Inspiration Sources
+
+{{inspiration_sources}}
+
+### Similar Modules
+
+{{similar_modules}}
+
+### Technical References
+
+{{technical_references}}
+
+---
+
+## Appendices
+
+### A. Detailed Agent Specifications
+
+{{detailed_agent_specs}}
+
+### B. Workflow Detailed Designs
+
+{{detailed_workflow_specs}}
+
+### C. Data Structures and Schemas
+
+{{data_schemas}}
+
+### D. Integration Specifications
+
+{{integration_specs}}
+
+---
+
+## Next Steps
+
+1. **Review this brief** with stakeholders
+2. **Run create-module workflow** using this brief as input
+3. **Create first agent** using create-agent workflow
+4. **Develop initial workflows** using create-workflow
+5. **Test MVP** with target users
+
+---
+
+_This Module Brief is ready to be fed directly into the create-module workflow for scaffolding and implementation._
+
+**Module Viability Score:** {{viability_score}}/10
+**Estimated Development Effort:** {{effort_estimate}}
+**Confidence Level:** {{confidence_level}}
+
+---
+
+**Approval for Development:**
+
+- [ ] Concept Approved
+- [ ] Scope Defined
+- [ ] Resources Available
+- [ ] Ready to Build
+
+---
+
+_Generated on {{date}} by {{user_name}} using the BMAD Method Module Brief workflow_

bmad/bmb/workflows/module-brief/workflow.yaml

@@ -0,0 +1,27 @@
+# Module Brief Workflow Configuration
+name: module-brief
+description: "Create a comprehensive Module Brief that serves as the blueprint for building new BMAD modules using strategic analysis and creative vision"
+author: "BMad Builder"
+
+# Critical variables
+config_source: "{project-root}/bmad/bmb/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+src_impact: "{config_source}:src_impact"
+date: system-generated
+
+# Optional input docs that enhance module planning
+recommended_inputs:
+  - brainstorming_results: "{output_folder}/brainstorming-*.md"
+  - existing_modules: "{project-root}/bmad/"
+  - module_examples: "{project-root}/bmad/bmb/workflows/create-module/module-structure.md"
+
+# Module path and component files
+installed_path: "{project-root}/bmad/bmb/workflows/module-brief"
+template: "{installed_path}/template.md"
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+
+# Output configuration
+default_output_file: "{output_folder}/module-brief-{{module_code}}-{{date}}.md"

bmad/bmb/workflows/redoc/README.md

@@ -0,0 +1,87 @@
+# ReDoc - Reverse-Tree Documentation Engine
+
+**Type:** Autonomous Action Workflow
+**Module:** BMad Builder (bmb)
+
+## Purpose
+
+ReDoc is an intelligent documentation maintenance system for BMAD modules, workflows, and agents. It uses a reverse-tree approach (leaf folders first, then parent folders) to systematically generate and update README.md files with technical writer quality output.
+
+The workflow understands BMAD conventions deeply and focuses documentation on distinctive features rather than explaining standard patterns, resulting in succinct, precise technical documentation.
+
+## Key Features
+
+- **Reverse-Tree Processing**: Documents from deepest folders up to module root, allowing child documentation to inform parent summaries
+- **Convention-Aware**: Loads BMAD architecture patterns and only documents unique/distinctive aspects
+- **Scalability**: Automatically creates catalog documents (WORKFLOWS-CATALOG.md, AGENTS-CATALOG.md) for massive folders (>10 items)
+- **Diff-Aware**: Tracks `last-redoc-date` frontmatter to enable change detection since last run
+- **Autonomous**: Runs without user checkpoints unless clarification is genuinely required
+- **Comprehensive**: Reads ALL files completely before generating documentation (no partial reads)
+
+## Usage
+
+Invoke with a target path:
+
+```
+workflow redoc
+```
+
+When prompted, provide one of:
+
+- **Module path**: `bmad/bmm` (documents entire module: root, workflows, agents)
+- **Workflows folder**: `bmad/bmm/workflows` (documents all workflows)
+- **Agents folder**: `bmad/bmm/agents` (documents all agents)
+- **Single workflow**: `bmad/bmm/workflows/product-brief` (documents one workflow)
+- **Single agent**: `bmad/bmm/agents/prd-agent.md` (documents one agent)
+
+## Inputs
+
+### Required
+
+- **target_path**: Path to module, folder, or specific component to document
+
+### Knowledge Base (Auto-loaded)
+
+- agent-architecture.md
+- agent-command-patterns.md
+- agent-types.md
+- module-structure.md
+- workflow-creation-guide.md
+
+## Outputs
+
+### Created/Updated Files
+
+- **README.md**: At each documented level (workflow folders, agent folders, module root)
+- **Catalog files**: WORKFLOWS-CATALOG.md, AGENTS-CATALOG.md (for massive folders)
+- **Frontmatter**: All READMEs include `last-redoc-date: <timestamp>`
+
+### Summary Report
+
+- Documentation coverage statistics
+- List of files created/updated
+- Any items requiring manual review
+
+## Workflow Steps
+
+1. **Initialize**: Load BMAD conventions and validate target
+2. **Analyze Structure**: Build reverse-tree execution plan
+3. **Process Leaves**: Document individual workflows/agents (deepest first)
+4. **Process Folders**: Document workflow/agent collections with categorization
+5. **Process Root**: Document module overview with links and highlights
+6. **Validate**: Verify completeness and generate report
+7. **Diff Analysis** (optional): Show changes since last redoc
+8. **Complete**: Report success and suggest next steps
+
+## Technical Details
+
+- **Execution**: Autonomous with minimal user interaction
+- **Quality**: Technical writer standards - succinct, precise, professional
+- **Context-Aware**: Uses BMAD convention knowledge to highlight only distinctive features
+- **Scalable**: Handles folders of any size with intelligent catalog creation
+
+## Next Steps After Running
+
+1. Review generated documentation for accuracy
+2. If documenting a subfolder, run redoc on parent module to update references
+3. Commit documentation updates with meaningful message

bmad/bmb/workflows/redoc/checklist.md

@@ -0,0 +1,99 @@
+# ReDoc Workflow Validation Checklist
+
+## Initialization and Setup
+
+- [ ] All BMAD convention documents loaded and understood
+- [ ] Target path validated and exists
+- [ ] Target type correctly identified (module/workflow/agent/folder)
+- [ ] Documentation execution plan created with reverse-tree order
+
+## File Analysis
+
+- [ ] All files in target scope read completely (no offset/limit usage)
+- [ ] Existing README.md files detected and last-redoc-date parsed
+- [ ] Massive folders (>10 items) identified for catalog document creation
+- [ ] Documentation depth levels calculated correctly
+
+## Leaf-Level Documentation (Workflows)
+
+- [ ] Each workflow's ALL files read: workflow.yaml, instructions.md, template.md, checklist.md
+- [ ] README.md includes frontmatter with current last-redoc-date
+- [ ] Description is 2-4 paragraphs of technical writer quality
+- [ ] Focuses on DISTINCTIVE features, not BMAD boilerplate conventions
+- [ ] Includes "Usage" section with invocation command
+- [ ] Includes "Inputs" and "Outputs" sections where applicable
+- [ ] Succinct and precise language used throughout
+
+## Leaf-Level Documentation (Agents)
+
+- [ ] Each agent file read completely including XML structure, commands, persona
+- [ ] README.md includes frontmatter with current last-redoc-date
+- [ ] Description is 1-3 paragraphs of technical writer quality
+- [ ] Lists all available commands clearly
+- [ ] Explains when to use this agent
+- [ ] Highlights unique capabilities vs standard agent patterns
+
+## Mid-Level Documentation (Folders)
+
+- [ ] All child README.md files read before generating folder README
+- [ ] Workflows categorized logically if massive folder (>10 items)
+- [ ] Agents categorized by type if massive folder (>10 items)
+- [ ] Catalog documents (WORKFLOWS-CATALOG.md, AGENTS-CATALOG.md) created for massive folders
+- [ ] Catalog documents include frontmatter with last-redoc-date
+- [ ] Folder README.md references catalog if one exists
+- [ ] Folder README.md is succinct (1-2 paragraphs + listings/links)
+- [ ] Notable/commonly-used items highlighted
+
+## Root Module Documentation
+
+- [ ] Module config.yaml read and understood
+- [ ] Workflows and agents folder READMEs read before creating root README
+- [ ] Root README includes frontmatter with current last-redoc-date
+- [ ] Module purpose clearly stated in 2-3 sentences
+- [ ] Links to /workflows/README.md and /agents/README.md included
+- [ ] 2-3 key workflows mentioned with context
+- [ ] 2-3 key agents mentioned with context
+- [ ] Configuration section highlights UNIQUE settings only
+- [ ] Usage section explains invocation patterns
+- [ ] BMAD convention knowledge applied (describes only distinctive aspects)
+
+## Quality Standards
+
+- [ ] All documentation uses proper BMAD terminology
+- [ ] Technical writer quality: clear, concise, professional
+- [ ] No placeholder text or generic descriptions remain
+- [ ] All links are valid and correctly formatted
+- [ ] Frontmatter syntax is correct and dates are current
+- [ ] No redundant explanation of standard BMAD patterns
+
+## Validation and Reporting
+
+- [ ] All planned documentation items created/updated
+- [ ] Frontmatter dates verified as current across all files
+- [ ] File paths and internal links validated
+- [ ] Summary report generated with counts and coverage
+- [ ] Files skipped (if any) documented with reasons
+
+## Git Diff Analysis (Optional Step)
+
+- [ ] last-redoc-date timestamps extracted correctly
+- [ ] Git log queried for changes since last redoc
+- [ ] Modified files identified and reported
+- [ ] Findings presented clearly to user
+
+## Final Validation
+
+- [ ] Documentation Coverage
+  - All README.md files in scope created/updated
+  - Catalog documents created where needed
+  - No documentation gaps identified
+
+- [ ] Execution Quality
+  - Reverse-tree order followed (leaf → root)
+  - Autonomous execution (minimal user prompts)
+  - Only clarification questions asked when truly necessary
+
+- [ ] Output Quality
+  - Technical precision maintained throughout
+  - Succinct descriptions (no verbose explanations)
+  - Professional documentation standards met

bmad/bmb/workflows/redoc/instructions.md

@@ -0,0 +1,255 @@
+# ReDoc Workflow Instructions
+
+<workflow>
+
+<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
+<critical>You MUST have already loaded and processed: {project_root}/src/modules/bmb/workflows/redoc/workflow.yaml</critical>
+<critical>This is an AUTONOMOUS workflow - minimize user interaction unless clarification is absolutely required</critical>
+
+<step n="1" goal="Load BMAD conventions and initialize">
+<action>Load ALL BMAD convention documents from {bmad_conventions}:
+- agent_architecture.md - Understand agent XML structure and patterns
+- agent_command_patterns.md - Command syntax and activation patterns
+- agent_types.md - Standard agent categories and purposes
+- module_structure.md - Module organization and folder conventions
+- workflow_guide.md - Workflow structure and best practices
+</action>
+
+<action>Internalize these conventions so you can:
+
+- Recognize standard patterns vs unique implementations
+- Describe only what's distinctive about each component
+- Use proper terminology consistently
+- Write with technical precision
+  </action>
+
+<action>Get target path from user:
+
+- Ask: "What do you want to document? (module path, workflow path, agent path, or folder path)"
+- Store as {{target_path}}
+  </action>
+
+<action>Validate target path exists and determine target type:
+
+- Module root (contains config.yaml, /workflows, /agents folders)
+- Workflows folder (contains multiple workflow folders)
+- Agents folder (contains multiple agent .md files)
+- Single workflow folder (contains workflow.yaml)
+- Single agent file (.md)
+  </action>
+
+<action>Store target type as {{target_type}} for conditional processing</action>
+</step>
+
+<step n="2" goal="Analyze directory structure and existing documentation">
+<action>Build complete tree structure of {{target_path}} using Glob and file system tools</action>
+
+<action>Identify all documentation points:
+
+- List all folders requiring README.md files
+- Detect existing README.md files
+- Parse frontmatter from existing READMEs to extract last-redoc-date
+- Calculate documentation depth (how many levels deep)
+  </action>
+
+<action>Create documentation map with execution order (deepest → shallowest):
+
+- Level 0 (deepest): Individual workflow folders, individual agent files
+- Level 1: /workflows folder, /agents folder
+- Level 2 (root): Module root README.md
+  </action>
+
+<action>Detect "massive folders" requiring child catalog documents:
+
+- Threshold: >10 items or complex categorization needed
+- Mark folders for catalog document creation (e.g., WORKFLOWS-CATALOG.md, AGENTS-CATALOG.md)
+  </action>
+
+<critical>Store execution order as {{doc_execution_plan}} - this ensures reverse-tree processing</critical>
+</step>
+
+<step n="3" goal="Process leaf-level documentation" repeat="for-each-leaf-item">
+<action>For each individual workflow folder in execution plan:
+1. Read ALL files completely:
+   - workflow.yaml (metadata, purpose, configuration)
+   - instructions.md (step structure, goals)
+   - template.md (output structure) if exists
+   - checklist.md (validation criteria) if exists
+   - Any supporting data files
+
+2. Synthesize understanding:
+   - Core purpose and use case
+   - Input requirements
+   - Output produced
+   - Unique characteristics (vs standard BMAD workflow patterns)
+   - Key steps or special features
+
+3. Generate/update README.md:
+   - Add frontmatter: `---\nlast-redoc-date: {{date}}\n---\n`
+   - Write 2-4 paragraph technical description
+   - Include "Usage" section with invocation command
+   - Include "Inputs" section if applicable
+   - Include "Outputs" section
+   - Be succinct and precise - technical writer quality
+   - Focus on DISTINCTIVE features, not boilerplate
+
+4. Save README.md to workflow folder
+   </action>
+
+<action>For each individual agent file in execution plan:
+
+1. Read agent definition file completely:
+   - XML structure and metadata
+   - Commands and their purposes
+   - Activation patterns
+   - Persona and communication style
+   - Critical actions and workflows invoked
+
+2. Synthesize understanding:
+   - Agent purpose and role
+   - Available commands
+   - When to use this agent
+   - Unique capabilities
+
+3. Generate/update README.md (or agent-name-README.md if in shared folder):
+   - Add frontmatter: `---\nlast-redoc-date: {{date}}\n---\n`
+   - Write 1-3 paragraph technical description
+   - Include "Commands" section listing available commands
+   - Include "Usage" section
+   - Focus on distinctive features
+
+4. Save README.md
+   </action>
+
+<check>If clarification needed about purpose or unique features → Ask user briefly, then continue</check>
+</step>
+
+<step n="4" goal="Process mid-level folder documentation" if="target_type requires folder docs">
+<action>For /workflows folder:
+1. Read ALL workflow README.md files created in Step 3
+2. Categorize workflows by purpose/type if folder is massive (>10 workflows):
+   - Document generation workflows
+   - Action workflows
+   - Meta-workflows
+   - Interactive workflows
+
+3. If massive folder detected:
+   - Create WORKFLOWS-CATALOG.md with categorized listings
+   - Each entry: workflow name, 1-sentence description, link to folder
+   - Add frontmatter with last-redoc-date
+
+4. Generate/update /workflows/README.md:
+   - Add frontmatter: `---\nlast-redoc-date: {{date}}\n---\n`
+   - High-level summary of workflow collection
+   - If catalog exists: reference it
+   - If not massive: list all workflows with brief descriptions and links
+   - Highlight notable or commonly-used workflows
+   - Keep succinct (1-2 paragraphs + list)
+
+5. Save README.md
+   </action>
+
+<action>For /agents folder:
+
+1. Read ALL agent README.md files
+2. Categorize agents by type if massive folder (>10 agents):
+   - Task agents
+   - Meta agents
+   - Specialized agents
+   - Utility agents
+
+3. If massive folder detected:
+   - Create AGENTS-CATALOG.md with categorized listings
+   - Each entry: agent name, 1-sentence description, link
+   - Add frontmatter with last-redoc-date
+
+4. Generate/update /agents/README.md:
+   - Add frontmatter: `---\nlast-redoc-date: {{date}}\n---\n`
+   - High-level summary of agent collection
+   - If catalog exists: reference it
+   - If not massive: list all agents with brief descriptions
+   - Highlight key agents and their purposes
+   - Keep succinct
+
+5. Save README.md
+   </action>
+   </step>
+
+<step n="5" goal="Process root module documentation" if="target_type is module root">
+<action>For module root README.md:
+1. Read module config.yaml for metadata and configuration
+2. Read /workflows/README.md and /agents/README.md created in Step 4
+3. Identify module's unique purpose within BMAD ecosystem
+
+4. Generate/update module README.md:
+   - Add frontmatter: `---\nlast-redoc-date: {{date}}\n---\n`
+
+   Structure:
+   - # Module Name
+   - **Purpose**: 2-3 sentence high-level module purpose
+   - **Overview**: 1-2 paragraphs describing what this module provides
+
+   - ## Workflows
+     - Link to /workflows/README.md with 1-sentence summary
+     - Mention count and highlight 2-3 key workflows
+
+   - ## Agents
+     - Link to /agents/README.md with 1-sentence summary
+     - Mention count and highlight 2-3 key agents
+
+   - ## Configuration
+     - Notable config.yaml settings if unique/important
+     - Reference paths and conventions
+
+   - ## Usage
+     - How to invoke workflows or agents from this module
+     - Prerequisites if any
+
+   Focus on UNIQUE aspects using BMAD convention knowledge:
+   - Don't explain standard BMAD patterns
+   - Highlight what makes THIS module distinctive
+   - Use proper BMAD terminology
+
+5. Save README.md to module root
+   </action>
+   </step>
+
+<step n="6" goal="Validation and summary report">
+<action>Verify all planned documentation was created/updated:
+- Check each item in {{doc_execution_plan}}
+- Confirm frontmatter dates are current
+- Validate file paths and links
+</action>
+
+<action>Generate summary report showing:
+
+- Target documented: {{target_path}}
+- Target type: {{target_type}}
+- Documentation files created/updated (count and list)
+- Any catalog files created
+- Files skipped or requiring manual review (if any)
+- Coverage: X% of items documented
+  </action>
+
+<action>Display summary to user</action>
+</step>
+
+<step n="7" goal="Optional git diff analysis" optional="true">
+<ask>Would you like to see what changed since the last redoc run? [y/n]</ask>
+
+<action if="user_response == 'y'">
+For each README with last-redoc-date frontmatter:
+1. Extract last-redoc-date timestamp
+2. Use git log to find files modified since that date in the documented folder
+3. Highlight files that changed but may need documentation updates
+4. Report findings to user
+</action>
+</step>
+
+<step n="8" goal="Completion">
+<action>Confirm autonomous workflow execution complete</action>
+<action>Provide path to all updated documentation</action>
+<action>Suggest next steps if needed (e.g., "Run redoc on parent module to update references")</action>
+</step>
+
+</workflow>

bmad/bmb/workflows/redoc/workflow.yaml

@@ -0,0 +1,30 @@
+# ReDoc - Reverse-Tree Documentation Engine
+name: "redoc"
+description: "Autonomous documentation system that maintains module, workflow, and agent documentation using a reverse-tree approach (leaf folders first, then parents). Understands BMAD conventions and produces technical writer quality output."
+author: "BMad"
+
+# Critical variables
+config_source: "{project-root}/bmad/bmb/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+date: system-generated
+
+# Required knowledge base - BMAD conventions and patterns
+bmad_conventions:
+  agent_architecture: "{project-root}/src/modules/bmb/workflows/create-agent/agent-architecture.md"
+  agent_command_patterns: "{project-root}/src/modules/bmb/workflows/create-agent/agent-command-patterns.md"
+  agent_types: "{project-root}/src/modules/bmb/workflows/create-agent/agent-types.md"
+  module_structure: "{project-root}/src/modules/bmb/workflows/create-module/module-structure.md"
+  workflow_guide: "{project-root}/src/modules/bmb/workflows/create-workflow/workflow-creation-guide.md"
+
+# Runtime inputs
+target_path: "" # User specifies: module path, workflow path, agent path, or folder path
+
+# Module path and component files
+installed_path: "{project-root}/src/modules/bmb/workflows/redoc"
+template: false # Action workflow - updates files in place
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+
+# Configuration
+autonomous: true # Runs without user checkpoints unless clarification needed

src/modules/bmb/agents/bmad-builder.md

@@ -25,6 +25,7 @@
     <c cmd="*create-module" run-workflow="{project-root}/bmad/bmb/workflows/create-module/workflow.yaml">Create a complete BMAD module (brainstorm → brief → build with agents and workflows)</c>
     <c cmd="*create-workflow" run-workflow="{project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml">Create a new BMAD Core workflow with proper structure</c>
     <c cmd="*edit-workflow" run-workflow="{project-root}/bmad/bmb/workflows/edit-workflow/workflow.yaml">Edit existing workflows while following best practices</c>
+    <c cmd="redoc" run-workflow="{project-root}/bmad/bmb/workflows/redoc/workflow.yaml">Create or update module documentation</c>
     <c cmd="*exit">Exit with confirmation</c>
   </cmds>
 </agent>

src/modules/bmb/workflows/redoc/instructions.md

@@ -5,6 +5,8 @@
 <critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
 <critical>You MUST have already loaded and processed: {project_root}/src/modules/bmb/workflows/redoc/workflow.yaml</critical>
 <critical>This is an AUTONOMOUS workflow - minimize user interaction unless clarification is absolutely required</critical>
+<critical>IMPORTANT: Process ONE document at a time to avoid token limits. Each README should be created individually, not batched.</critical>
+<critical>When using Task tool with sub-agents: Only request ONE workflow or agent documentation per invocation to prevent token overflow.</critical>
 
 <step n="1" goal="Load BMAD conventions and initialize">
 <action>Load ALL BMAD convention documents from {bmad_conventions}:
@@ -69,7 +71,11 @@
 </step>
 
 <step n="3" goal="Process leaf-level documentation" repeat="for-each-leaf-item">
-<action>For each individual workflow folder in execution plan:
+<critical>TOKEN LIMIT WARNING: Process ONE item at a time to prevent token overflow issues.</critical>
+<critical>If using Task tool with sub-agents: NEVER batch multiple workflows/agents in a single invocation.</critical>
+<critical>Each README creation should be a separate operation with its own file save.</critical>
+<critical>Sequential processing is MANDATORY - do not attempt parallel documentation generation.</critical>
+<action>For each individual workflow folder in execution plan (PROCESS ONE AT A TIME):
 1. Read ALL files completely:
    - workflow.yaml (metadata, purpose, configuration)
    - instructions.md (step structure, goals)
@@ -94,9 +100,11 @@
    - Focus on DISTINCTIVE features, not boilerplate
 
 4. Save README.md to workflow folder
-   </action>
 
-<action>For each individual agent file in execution plan:
+<critical>If multiple workflows need documentation, process them SEQUENTIALLY not in parallel. Each workflow gets its own complete processing cycle.</critical>
+</action>
+
+<action>For each individual agent file in execution plan (PROCESS ONE AT A TIME):
 
 1. Read agent definition file completely:
    - XML structure and metadata
@@ -229,6 +237,7 @@
 - Any catalog files created
 - Files skipped or requiring manual review (if any)
 - Coverage: X% of items documented
+- Processing notes: Confirm sequential processing was used to avoid token limits
   </action>
 
 <action>Display summary to user</action>

src/modules/bmm/workflows/1-analysis/brainstorm-game/README.md

@@ -0,0 +1,38 @@
+---
+last-redoc-date: 2025-10-01
+---
+
+# Game Brainstorming Workflow
+
+This workflow employs structured ideation methodologies to generate and refine game concepts through systematic creative exploration. It leverages five distinct brainstorming techniques—SCAMPER, Mind Mapping, Lotus Blossom, Six Thinking Hats, and Random Word Association—each applied in isolation to produce diverse conceptual approaches. The workflow emphasizes iterative refinement where initial concepts are evaluated against design pillars, technical feasibility, and market positioning to identify the most promising directions.
+
+The system operates through a game-specific context framework that considers platform constraints, target audience characteristics, monetization models, and core gameplay pillars. Each brainstorming method generates distinct artifacts: SCAMPER produces systematic modification analyses, Mind Mapping reveals conceptual hierarchies, Lotus Blossom creates radial expansion patterns, Six Thinking Hats enforces multi-perspective evaluation, and Random Word Association drives lateral thinking breakthroughs. The workflow culminates in a consolidated concept document that synthesizes the strongest elements from each method into cohesive game proposals.
+
+Critical to this workflow is its emphasis on constraint-driven creativity. The game-context.md framework establishes technical boundaries (platform capabilities, performance targets), market parameters (genre conventions, competitive positioning), and design philosophy (accessibility requirements, monetization ethics) that ground creative exploration in practical realities. This prevents ideation from drifting into infeasible territory while maintaining creative ambition.
+
+## Usage
+
+```bash
+bmad bmm 1-analysis brainstorm-game
+```
+
+## Inputs
+
+- **Game Context Document**: Platform specifications, genre preferences, technical constraints, target audience demographics, monetization approach, and core design pillars
+- **Initial Concept Seed** (optional): High-level game idea or theme to guide brainstorming direction
+
+## Outputs
+
+- **Method-Specific Artifacts**: Five separate brainstorming documents, each applying a different ideation methodology to the concept space
+- **Consolidated Concept Document**: Synthesized game concepts with feasibility assessments, unique value propositions, and recommended next steps
+- **Design Pillar Alignment Matrix**: Evaluation of each concept against stated design objectives and technical constraints
+
+## Brainstorming Methods
+
+| Method                  | Focus                    | Output Characteristics             |
+| ----------------------- | ------------------------ | ---------------------------------- |
+| SCAMPER                 | Systematic modification  | Structured transformation analysis |
+| Mind Mapping            | Hierarchical exploration | Visual concept relationships       |
+| Lotus Blossom           | Radial expansion         | Layered thematic development       |
+| Six Thinking Hats       | Multi-perspective        | Balanced evaluation framework      |
+| Random Word Association | Lateral thinking         | Unexpected conceptual combinations |

src/modules/bmm/workflows/1-analysis/brainstorm-project/README.md

@@ -0,0 +1,29 @@
+---
+last-redoc-date: 2025-10-01
+---
+
+# Project Brainstorming Workflow
+
+This workflow facilitates structured ideation for non-game software projects through systematic exploration of problem spaces, solution architectures, and implementation strategies. Unlike traditional requirement gathering, it employs creative techniques to uncover non-obvious approaches and identify innovative solutions that address core business needs while considering technical constraints and organizational capabilities.
+
+The workflow operates through a project-specific context framework that captures business objectives, technical environment, stakeholder needs, and organizational constraints. It generates multiple solution vectors through parallel ideation tracks: architectural approaches, user experience paradigms, integration patterns, and value delivery mechanisms. Each track produces concrete proposals that are evaluated against feasibility, impact, and alignment with strategic objectives.
+
+Critical differentiators include its focus on solution innovation rather than requirement enumeration, emphasis on technical-business alignment from inception, and structured approach to surfacing hidden assumptions. The workflow produces actionable outputs that directly feed into Product Brief development, ensuring that creative exploration translates into concrete planning artifacts.
+
+## Usage
+
+```bash
+bmad bmm 1-analysis brainstorm-project
+```
+
+## Inputs
+
+- **Project Context Document**: Business objectives, technical environment, stakeholder landscape, organizational constraints, success criteria, and known pain points
+- **Problem Statement** (optional): Core business challenge or opportunity driving the project
+
+## Outputs
+
+- **Solution Architecture Proposals**: Multiple technical approaches with trade-off analysis and feasibility assessments
+- **Value Delivery Framework**: Prioritized feature concepts aligned with business objectives and user needs
+- **Risk and Opportunity Analysis**: Identified technical dependencies, integration challenges, and innovation opportunities
+- **Strategic Recommendation**: Synthesized direction with rationale and implementation considerations

src/modules/bmm/workflows/2-plan/README.md

@@ -1,8 +1,14 @@
-# Project Planning Workflow
+---
+last-redoc-date: 2025-10-01
+---
 
-## Overview
+# Project Planning Workflow (Phase 2)
 
-Scale-adaptive project planning workflow that automatically adjusts outputs based on project scope - from single atomic changes (Level 0: tech-spec only) to enterprise platforms (Level 4: full PRD + epics). Generates appropriate planning artifacts for each level with intelligent routing and continuation support.
+This scale-adaptive workflow represents the cornerstone of BMM v6's intelligent project orchestration, automatically determining project complexity (Level 0-4) and routing to specialized planning pathways based on project type, scope, and context. Unlike traditional one-size-fits-all planning approaches, it dynamically adjusts output artifacts—from minimal tech specs for atomic changes to comprehensive PRD suites for enterprise platforms—ensuring planning overhead matches project value. The workflow serves as the critical bridge between Phase 1 analysis outputs and Phase 3 solutioning, establishing the contractual foundation for all subsequent development activities.
+
+The workflow's routing intelligence analyzes project characteristics through multi-dimensional assessment: project type (game, web, mobile, backend), context (greenfield vs. brownfield), scope indicators, and complexity signals. Based on this analysis, it classifies projects into five levels with distinct artifact requirements. Level 0 produces only tech specs for single atomic changes. Levels 1-2 generate focused PRDs with embedded tech specs. Levels 3-4 create comprehensive PRDs with separate epics that hand off to the architect-driven solutioning workflow. This classification isn't merely about document generation—it fundamentally changes how requirements are structured, validated, and communicated to downstream consumers.
+
+Critical to v6's flow improvement is this workflow's integration with the project-workflow-analysis.md tracking document, which maintains project state across sessions, tracks which agents participate in each phase, and provides continuity for multi-session planning efforts. The workflow can resume from any point, intelligently detecting existing artifacts and determining next steps without redundant work. For game projects, it routes to specialized GDD generation with genre-specific templates. For UX-heavy projects, it can generate standalone UX specifications or AI frontend prompts from existing specs.
 
 ## Key Features
 

src/modules/bmm/workflows/4-implementation/correct-course/README.md

@@ -0,0 +1,73 @@
+---
+last-redoc-date: 2025-10-01
+---
+
+# Correct Course Workflow
+
+The correct-course workflow is v6's adaptive response mechanism for stories that encounter issues during development or review, enabling intelligent course correction without restarting from scratch. Run by the Scrum Master (SM) or Team Lead, this workflow analyzes why a story is blocked or has issues, determines whether the story scope needs adjustment, requirements need clarification, technical approach needs revision, or the story needs to be split or reconsidered. This represents the agile principle of embracing change even late in the development cycle, but doing so in a structured way that captures learning and maintains project coherence.
+
+Unlike simply abandoning failed work or blindly pushing forward, correct-course provides a systematic approach to diagnosing issues and determining appropriate remediation. The workflow examines the original story specification, what was actually implemented, what issues arose during development or review, and the broader epic context to recommend the best path forward. This might involve clarifying requirements, adjusting acceptance criteria, revising technical approach, splitting the story into smaller pieces, or even determining the story should be deprioritized.
+
+The critical value of this workflow is that it prevents thrashing—endless cycles of implementation and rework without clear direction. By stepping back to analyze what went wrong and charting a clear path forward, the correct-course workflow enables teams to learn from difficulties and adapt intelligently rather than stubbornly proceeding with a flawed approach.
+
+## Usage
+
+```bash
+# Analyze issues and recommend course correction
+bmad run correct-course
+```
+
+The workflow should be run when:
+
+- Review identifies critical issues requiring rethinking
+- Developer encounters blocking issues during implementation
+- Acceptance criteria prove infeasible or unclear
+- Technical approach needs significant revision
+- Story scope needs adjustment based on discoveries
+
+## Inputs
+
+**Required Context:**
+
+- **Story Document**: Original story specification
+- **Implementation Attempts**: Code changes and approaches tried
+- **Review Feedback**: Issues and concerns identified
+- **Epic Context**: Overall epic goals and current progress
+- **Technical Constraints**: Architecture decisions and limitations discovered
+
+**Analysis Focus:**
+
+- Root cause of issues or blockages
+- Feasibility of current story scope
+- Clarity of requirements and acceptance criteria
+- Appropriateness of technical approach
+- Whether story should be split or revised
+
+## Outputs
+
+**Primary Deliverable:**
+
+- **Course Correction Report** (`[story-id]-correction.md`): Analysis and recommendations including:
+  - Issue root cause analysis
+  - Impact assessment on epic and project
+  - Recommended corrective actions with rationale
+  - Revised story specification if applicable
+  - Updated acceptance criteria if needed
+  - Technical approach adjustments
+  - Timeline and effort implications
+
+**Possible Outcomes:**
+
+1. **Clarify Requirements**: Update story with clearer acceptance criteria
+2. **Revise Scope**: Adjust story scope to be more achievable
+3. **Split Story**: Break into multiple smaller stories
+4. **Change Approach**: Recommend different technical approach
+5. **Deprioritize**: Determine story should be deferred or cancelled
+6. **Unblock**: Identify and address blocking dependencies
+
+**Artifacts:**
+
+- Updated story document if revision needed
+- New story documents if splitting story
+- Updated epic backlog reflecting changes
+- Lessons learned for retrospective

src/modules/bmm/workflows/4-implementation/create-story/README.md

@@ -1,42 +1,129 @@
-# Create Story
+---
+last-redoc-date: 2025-10-01
+---
 
-## Purpose
+# Create Story Workflow
 
-Generate the next user story from epics/PRD and architecture context into your configured stories directory using a consistent structure.
+The create-story workflow is the entry point for v6's just-in-time story generation approach, run exclusively by the Scrum Master (SM) agent. Unlike batch processing methodologies, this workflow generates exactly ONE story at a time based on the current epic backlog state, ensuring stories are created only when needed and with the most current context. The SM analyzes the epic's progress, identifies what needs to be built next based on epics.md enumeration, and generates a complete story specification including acceptance criteria, technical approach, and implementation guidance pulled directly from tech specs, PRD, and architecture documentation.
 
-## Highlights
+This workflow represents a fundamental shift from traditional upfront planning to adaptive story generation. By creating stories one at a time and enforcing strict verification against epics.md, the SM ensures that only planned and approved stories are created. The workflow operates in non-interactive "#yolo" mode by default, minimizing prompts while maintaining quality through rigorous source document grounding. It will HALT if epics.md doesn't explicitly enumerate the next story, forcing proper planning through the correct-course workflow rather than allowing ad-hoc story creation.
 
-- Auto-detects next story id based on existing files
-- Pulls ACs from `epics.md` (or PRD) when available
-- Saves to `{dev_story_location}` from `bmad/bmm/config.yaml`
-- Optional: immediately runs Story Context workflow for the new story
-- Spec-compliant with core workflow engine at `bmad/core/tasks/workflow.md`
-- Defaults to non-interactive `#yolo` mode; only asks when strictly necessary
-- Safeguard: Will NOT create a new story unless epics.md explicitly enumerates it; otherwise halts and instructs to run PM/SM `*correct-course`
+The workflow's intelligent document discovery system automatically finds the relevant tech spec for the current epic (using pattern `tech-spec-epic-{epic_num}-*.md`), loads all architecture documents from both docs/ and output folders, and synthesizes requirements from multiple sources in priority order. After story creation, it can optionally trigger the story-context workflow to generate just-in-time technical expertise for the developer.
 
-## Invoke
+## Usage
 
-- By path: `workflow {project-root}/bmad/bmm/workflows/4-implementation/create-story/workflow.yaml`
+```bash
+# SM initiates story creation for the next piece of work
+bmad sm *create-story
+```
 
-## Variables
+The SM runs this workflow when:
 
-- `story_dir`: from config `dev_story_location`
-- `epics_file`: default `{output_folder}/epics.md`
-- `prd_file`: default `{output_folder}/prd.md`
-- `hla_file`: default `{output_folder}/high-level-architecture.md`
-- `auto_run_context`: default `true`
-- `tech_spec_file`: auto-discovered in `{project-root}/docs` with pattern `tech-spec-epic-<epic_num>-*.md` (latest by modified time)
-- `execution_mode`: `#yolo` by default to minimize prompts
-- `arch_docs_search_dirs`: `docs/` and `output_folder` are searched for architecture docs
-- `arch_docs_file_names`: includes `tech-stack.md`, `unified-project-structure.md`, `coding-standards.md`, `testing-strategy.md`, `backend-architecture.md`, `frontend-architecture.md`, `data-models.md`, `database-schema.md`, `rest-api-spec.md`, `external-apis.md`
+- The current sprint has capacity for new work
+- The previous story status is "Done" or "Approved"
+- The team is ready for the next planned story in the epic
+- Story preparation is needed before development
 
-## Output
+## Inputs
 
-- New story markdown: `{story_dir}/story-<epic_num>.<story_num>.md`
-- Status: `Draft`
-- Guardrail: If `epics.md` lacks the next story under the current epic, the workflow halts with: "No planned next story found in epics.md for epic <epic_num>. Please load either PM (Product Manager) agent at `{project-root}/bmad/bmm/agents/pm.md` or SM (Scrum Master) agent at `{project-root}/bmad/bmm/agents/sm.md` and run `*correct-course` to add/modify epic stories, then rerun create-story."
+**Required Context Files:**
 
-## After Creation
+- **epics.md**: MANDATORY - Must explicitly enumerate the next story or workflow halts
+- **tech-spec-epic-{N}-\*.md**: Epic-specific technical specification (auto-discovered)
+- **PRD.md**: Product requirements document (fallback for requirements)
+- **Architecture Documents**: Automatically discovered from docs/ and output folders:
+  - tech-stack.md, unified-project-structure.md, coding-standards.md
+  - testing-strategy.md, backend-architecture.md, frontend-architecture.md
+  - data-models.md, database-schema.md, rest-api-spec.md, external-apis.md
 
-- Approve the story when ready (Status → Approved)
-- Then run the Dev agent `*develop` command (uses the Dev Story workflow)
+**Workflow Variables:**
+
+- `story_dir`: From config `dev_story_location` - where stories are saved
+- `epic_num`: Current epic number (auto-detected from existing stories)
+- `story_num`: Next story number (incremented from last completed story)
+- `auto_run_context`: Default true - runs story-context workflow after creation
+- `non_interactive`: Default true - operates in "#yolo" mode with minimal prompts
+
+## Outputs
+
+**Primary Deliverable:**
+
+- **Story Document** (`{story_dir}/story-{epic_num}.{story_num}.md`): Complete story specification including:
+  - User story statement (role, action, benefit)
+  - Acceptance criteria extracted from tech spec or epics.md
+  - Tasks and subtasks mapped to ACs
+  - Testing requirements per testing strategy
+  - Dev notes with source citations
+  - Status: "Draft" (requires approval before development)
+
+**Validation Safeguards:**
+
+- **Epic Enumeration Check**: If epics.md doesn't list the next story, workflow HALTS with:
+  ```
+  "No planned next story found in epics.md for epic {epic_num}.
+  Please load either PM or SM agent and run *correct-course to add/modify epic stories."
+  ```
+- **Status Check**: Won't create new story if current story isn't Done/Approved
+- **Document Grounding**: All requirements traced to source documents (no invention)
+
+## Key Features
+
+**Strict Planning Enforcement**: The workflow will NOT create stories that aren't explicitly planned in epics.md. This prevents scope creep and ensures all work is properly approved through the planning process.
+
+**Intelligent Document Discovery**: Automatically finds the latest tech spec for the epic using glob patterns, discovers all architecture documents across multiple directories, and builds a prioritized document set for requirement extraction.
+
+**Source Document Grounding**: Every requirement, acceptance criterion, and technical constraint is traced to a specific source document. The workflow explicitly forbids inventing domain facts not present in source materials.
+
+**Non-Interactive by Default**: Operates in "#yolo" mode to minimize interruptions, only prompting when absolutely necessary (like missing critical configuration). This enables smooth automated story preparation.
+
+**Automatic Context Generation**: When `auto_run_context` is true (default), automatically triggers the story-context workflow to generate developer expertise injection for the newly created story.
+
+## Integration with v6 Flow
+
+The create-story workflow is step 1 in the v6 implementation cycle:
+
+1. **SM: create-story** ← You are here
+2. SM: story-context (adds JIT technical expertise)
+3. DEV: dev-story (implements with generated context)
+4. DEV/SR: review-story (validates completion)
+5. If needed: correct-course (adjusts direction)
+6. After epic: retrospective (captures learnings)
+
+This workflow establishes the "what" that needs to be built, strictly based on planned epics. The story-context workflow will later add the "how" through just-in-time technical expertise injection.
+
+## Document Priority Order
+
+The workflow uses this priority for extracting requirements:
+
+1. **tech_spec_file**: Epic-scoped technical specification (highest priority)
+2. **epics_file**: Acceptance criteria and story breakdown
+3. **prd_file**: Business requirements and constraints
+4. **Architecture docs**: Constraints, patterns, and technical guidance
+
+## Workflow Behavior
+
+**Story Number Management:**
+
+- Automatically detects next story number from existing files
+- Won't skip numbers or create duplicates
+- Maintains epic.story numbering convention
+
+**Update vs Create:**
+
+- If latest story status != Done/Approved: Updates existing story
+- If latest story status == Done/Approved: Creates next story (if enumerated in epics.md)
+
+**Epic Advancement:**
+
+- In non-interactive mode: Stays within current epic
+- Interactive mode: Can prompt for new epic number
+
+## Troubleshooting
+
+**"No planned next story found in epics.md"**: The next story isn't enumerated in epics.md. Run SM or PM agent's `*correct-course` to properly plan and add the story to the epic.
+
+**Missing story_dir Configuration**: Ensure `dev_story_location` is set in bmad/bmm/config.yaml
+
+**Tech Spec Not Found**: The workflow looks for `tech-spec-epic-{N}-*.md` pattern. Ensure tech specs follow this naming convention.
+
+**Architecture Documents Missing**: While not fatal, missing architecture docs reduce story context quality. Ensure key docs exist in docs/ or output folder.

src/modules/bmm/workflows/4-implementation/dev-story/README.md

@@ -1,84 +1,206 @@
-# Dev Story
+# Dev Story Workflow
 
-## Purpose
+The dev-story workflow is where v6's just-in-time context approach delivers its primary value, enabling the Developer (DEV) agent to implement stories with expert-level guidance injected directly into their context. This workflow is run EXCLUSIVELY by the DEV agent and operates on a single story that has been prepared by the SM through create-story and enhanced with story-context. The DEV loads both the story specification and the dynamically-generated story context XML, then proceeds through implementation with the combined knowledge of requirements and domain-specific expertise.
 
-Execute a single user story end-to-end: select the next incomplete task, implement it following repo standards, write tests, run validations, and update the story file — all in a v6 action workflow.
+The workflow operates with two critical inputs: the story file (created by SM's create-story) containing acceptance criteria, tasks, and requirements; and the story-context XML (generated by SM's story-context) providing just-in-time expertise injection tailored to the story's technical needs. This dual-input approach ensures the developer has both the "what" (from the story) and the "how" (from the context) needed for successful implementation. The workflow iterates through tasks sequentially, implementing code, writing tests, and updating the story document's allowed sections until all tasks are complete.
+
+A critical aspect of v6 flow is that dev-story may be run multiple times for the same story. Initially run to implement the story, it may be run again after review-story identifies issues that need correction. The workflow intelligently resumes from incomplete tasks, making it ideal for both initial implementation and post-review fixes. The DEV agent maintains strict boundaries on what can be modified in the story file—only Tasks/Subtasks checkboxes, Dev Agent Record, File List, Change Log, and Status may be updated, preserving the story's requirements integrity.
+
+## Usage
+
+```bash
+# Developer implements the story with injected context
+bmad dev *develop
+
+# Or if returning to fix review issues
+bmad dev *develop  # Will resume from incomplete tasks
+```
+
+The DEV runs this workflow:
+
+- After SM completes both create-story and story-context
+- When a story status is "Draft" or "Approved" (ready for development)
+- After review-story identifies issues requiring fixes
+- To resume work on a partially completed story
+
+## Inputs
+
+**Required Files:**
+
+- **Story Document** (`{story_dir}/story-{epic}.{story}.md`): Complete specification including:
+  - User story statement
+  - Acceptance criteria (immutable during dev)
+  - Tasks and subtasks (checkable during implementation)
+  - Dev Notes section (for context and guidance)
+  - Status field (Draft → In Progress → Ready for Review)
+
+- **Story Context XML** (`{story_dir}/story-{epic}.{story}-context.xml`): Domain expertise including:
+  - Technical patterns and best practices
+  - Gotchas and common pitfalls
+  - Testing strategies
+  - Relevant code references
+  - Architecture constraints
+
+**Configuration:**
+
+- `dev_story_location`: Directory containing story files (from bmm/config.yaml)
+- `story_selection_limit`: Number of recent stories to show (default: 10)
+- `run_tests_command`: Test command (default: auto-detected)
+- `strict`: Whether to halt on test failures (default: true)
+
+## Outputs
+
+**Code Implementation:**
+
+- Production code satisfying acceptance criteria
+- Unit, integration, and E2E tests as appropriate
+- Documentation updates
+- Migration scripts if needed
+
+**Story File Updates (allowed sections only):**
+
+- **Tasks/Subtasks**: Checkboxes marked complete as work progresses
+- **Dev Agent Record**: Debug log and completion notes
+- **File List**: All files created or modified
+- **Change Log**: Summary of implementation changes
+- **Status**: Updated to "Ready for Review" when complete
+
+**Validation:**
+
+- All tests passing (existing + new)
+- Acceptance criteria verified
+- Code quality checks passed
+- No regression in existing functionality
 
 ## Key Features
 
-- Auto-discovers recent stories from config `dev_story_location`
-- Presents a selectable list of latest stories
-- Iterates task-by-task until the story is complete
-- Enforces acceptance criteria and test coverage
-- Restricts edits to approved sections of the story file
+**Story-Context Integration**: The workflow loads and leverages the story-context XML throughout implementation, providing expert guidance without cluttering the main conversation. This ensures best practices are followed while maintaining developer autonomy.
 
-## How to Invoke
+**Task-by-Task Iteration**: Implements one task at a time, marking completion before moving to the next. This granular approach enables progress tracking and clean resumption if interrupted or after review feedback.
 
-- By workflow name (if your runner supports it):
-  - `workflow dev-story`
-- By path:
-  - `workflow {project-root}/bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml`
+**Strict File Boundaries**: Only specific sections of the story file may be modified, preserving requirement integrity. The story's acceptance criteria, main description, and other planning sections remain immutable during development.
 
-## Inputs and Variables
+**Test-Driven Approach**: For each task, the workflow emphasizes writing tests that verify acceptance criteria before or alongside implementation, ensuring requirements are actually met.
 
-- `story_path` (optional): Explicit path to a story markdown file. If omitted, the workflow will auto-discover stories.
-- `run_tests_command` (optional, default: `auto`): Command used to run tests. When `auto`, the runner should infer (e.g., `npm test`, `pnpm test`, `yarn test`, `pytest`, `go test`, etc.).
-- `strict` (default: `true`): If `true`, halt on validation or test failures.
-- `story_dir` (from config): Resolved from `{project-root}/bmad/bmm/config.yaml` key `dev_story_location`.
-- `story_selection_limit` (default: `10`): Number of recent stories to show when selecting.
+**Resumable Implementation**: If the workflow is run again on a story with incomplete tasks (e.g., after review-story finds issues), it intelligently resumes from where it left off rather than starting over.
 
-## Config
+## Integration with v6 Flow
 
-Ensure your BMM config defines the stories directory:
+The dev-story workflow is step 3 in the v6 implementation cycle:
 
-```yaml
-# bmad/bmm/config.yaml
-output_folder: ./outputs
-user_name: Your Name
-communication_language: en
-# Directory where story markdown files live
-dev_story_location: ./docs/stories
+1. SM: create-story (generates the story specification)
+2. SM: story-context (adds JIT technical expertise)
+3. **DEV: dev-story** ← You are here (initial implementation)
+4. DEV/SR: review-story (validates completion)
+5. If issues found: **DEV: dev-story** ← May return here for fixes
+6. After epic: retrospective (captures learnings)
+
+This workflow may be executed multiple times for the same story as part of the review-fix cycle. Each execution picks up from incomplete tasks, making it efficient for iterative improvement.
+
+## Workflow Process
+
+### Phase 1: Story Selection
+
+- If `story_path` provided: Use that story directly
+- Otherwise: List recent stories from `dev_story_location`
+- Parse story structure and validate format
+- Load corresponding story-context XML
+
+### Phase 2: Task Implementation Loop
+
+For each incomplete task:
+
+1. **Plan**: Log approach in Dev Agent Record
+2. **Implement**: Write code following story-context guidance
+3. **Test**: Create tests verifying acceptance criteria
+4. **Validate**: Run tests and quality checks
+5. **Update**: Mark task complete, update File List
+
+### Phase 3: Completion
+
+- Verify all tasks completed
+- Run full test suite
+- Update Status to "Ready for Review"
+- Add completion notes to Dev Agent Record
+
+## Story File Structure
+
+The workflow expects stories with this structure:
+
+```markdown
+# Story {epic}.{story}: {Title}
+
+**Status**: Draft|In Progress|Ready for Review|Done
+**Epic**: {epic_number}
+**Estimated Effort**: {estimate}
+
+## Story
+
+As a {role}, I want to {action} so that {benefit}
+
+## Acceptance Criteria
+
+- [ ] AC1...
+- [ ] AC2...
+
+## Tasks and Subtasks
+
+- [ ] Task 1
+  - [ ] Subtask 1.1
+- [ ] Task 2
+
+## Dev Notes
+
+{Context and guidance from story creation}
+
+## Dev Agent Record
+
+### Debug Log
+
+{Implementation notes added during development}
+
+### Completion Notes
+
+{Summary added when complete}
+
+## File List
+
+{Files created/modified}
+
+## Change Log
+
+{Implementation summary}
 ```
 
-## Workflow Summary
+## Best Practices
 
-1. Load story and select next task
-   - Use `story_path` if provided; otherwise list most recent stories from `dev_story_location`
-   - Parse Story, Acceptance Criteria, Tasks/Subtasks, Dev Notes, Status
-   - Pick the first incomplete task
-2. Plan and implement
-   - Log brief plan in Dev Agent Record → Debug Log
-   - Implement task and subtasks, handle edge cases
-3. Write tests
-   - Add unit, integration, and E2E (as applicable)
-4. Run validations and tests
-   - Run existing tests for regressions + new tests
-   - Lint/quality checks if configured; ensure ACs met
-5. Mark task complete and update story
-   - Check [x] on task(s), update File List, add Completion Notes and Change Log
-   - Repeat from step 1 if tasks remain
-6. Completion sequence
-   - Verify all tasks done, run full regression suite, update Status → "Ready for Review"
-7. Validation and handoff (optional)
-   - Optionally run validation and finalize notes
+**Load Context First**: Always ensure the story-context XML is loaded at the start. This provides the expert guidance needed throughout implementation.
 
-## Allowed Story File Modifications
+**Follow Task Order**: Implement tasks in the order listed. Dependencies are typically structured in the task sequence.
 
-Only these sections may be changed by this workflow:
+**Test Each Task**: Don't wait until the end to write tests. Test each task as you complete it to ensure it meets acceptance criteria.
 
-- Tasks/Subtasks checkboxes
-- Dev Agent Record (Debug Log, Completion Notes)
-- File List
-- Change Log
-- Status
+**Update Incrementally**: Update the story file after each task completion rather than batching updates at the end.
 
-## Files in This Workflow
+**Respect Boundaries**: Never modify acceptance criteria or story description. If they seem wrong, that's a review-story or correct-course issue, not a dev-story fix.
 
-- `workflow.yaml` — configuration and variables
-- `instructions.md` — execution logic and steps
-- `checklist.md` — validation checklist for completion
+**Use Context Guidance**: Actively reference the story-context for patterns, gotchas, and best practices. It's there to help you succeed.
+
+## Troubleshooting
+
+**Story Not Found**: Ensure story exists in `dev_story_location` and follows naming pattern `story-{epic}.{story}.md`
+
+**Context XML Missing**: The story-context workflow must be run first. Check for `story-{epic}.{story}-context.xml`
+
+**Tests Failing**: If strict mode is on, the workflow halts. Fix tests before continuing or set strict=false for development iteration.
+
+**Can't Modify Story Section**: Remember only Tasks, Dev Agent Record, File List, Change Log, and Status can be modified. Other sections are immutable.
+
+**Resuming After Review**: If review-story found issues, the workflow automatically picks up from incomplete tasks when run again.
 
 ## Related Workflows
 
-- `story-context` — Build dev context for a single story
-- `story-context-batch` — Process multiple stories and update status
+- **create-story**: Creates the story specification (run by SM)
+- **story-context**: Generates the context XML (run by SM)
+- **review-story**: Validates implementation (run by SR/DEV)
+- **correct-course**: Handles major issues or scope changes (run by SM)

src/modules/bmm/workflows/4-implementation/retrospective/README.md

@@ -0,0 +1,77 @@
+---
+last-redoc-date: 2025-10-01
+---
+
+# Retrospective Workflow
+
+The retrospective workflow is v6's learning capture mechanism, run by the Scrum Master (SM) after epic completion to systematically harvest insights, patterns, and improvements discovered during implementation. Unlike traditional retrospectives that focus primarily on process and team dynamics, this workflow performs deep technical and methodological analysis of the entire epic journey—from story creation through implementation to review—identifying what worked well, what could improve, and what patterns emerged. The retrospective produces actionable intelligence that informs future epics, improves workflow templates, and evolves the team's shared knowledge.
+
+This workflow represents a critical feedback loop in the v6 methodology. Each epic is an experiment in adaptive software development, and the retrospective is where we analyze the results of that experiment. The SM examines completed stories, review feedback, course corrections made, story-context effectiveness, technical decisions, and team collaboration patterns to extract transferable learning. This learning manifests as updates to workflow templates, new story-context patterns, refined estimation approaches, and documented best practices.
+
+The retrospective is not just a compliance ritual but a genuine opportunity for continuous improvement. By systematically analyzing what happened during the epic, the team builds institutional knowledge that makes each subsequent epic smoother, faster, and higher quality. The insights captured here directly improve future story creation, context generation, development efficiency, and review effectiveness.
+
+## Usage
+
+```bash
+# Conduct retrospective after epic completion
+bmad run retrospective
+```
+
+The SM should run this workflow:
+
+- After all stories in an epic are completed
+- Before starting the next major epic
+- When significant learning has accumulated
+- As preparation for improving future epic execution
+
+## Inputs
+
+**Required Context:**
+
+- **Epic Document**: Complete epic specification and goals
+- **All Story Documents**: Every story created for the epic
+- **Review Reports**: All review feedback and findings
+- **Course Corrections**: Any correct-course actions taken
+- **Story Contexts**: Generated expert guidance for each story
+- **Implementation Artifacts**: Code commits, test results, deployment records
+
+**Analysis Targets:**
+
+- Story creation accuracy and sizing
+- Story-context effectiveness and relevance
+- Implementation challenges and solutions
+- Review findings and patterns
+- Technical decisions and outcomes
+- Estimation accuracy
+- Team collaboration and communication
+- Workflow effectiveness
+
+## Outputs
+
+**Primary Deliverable:**
+
+- **Retrospective Report** (`[epic-id]-retrospective.md`): Comprehensive analysis including:
+  - Executive summary of epic outcomes
+  - Story-by-story analysis of what was learned
+  - Technical insights and architecture learnings
+  - Story-context effectiveness assessment
+  - Process improvements identified
+  - Patterns discovered (good and bad)
+  - Recommendations for future epics
+  - Metrics and statistics (velocity, cycle time, etc.)
+
+**Actionable Outputs:**
+
+- **Template Updates**: Improvements to workflow templates based on learning
+- **Pattern Library**: New story-context patterns for common scenarios
+- **Best Practices**: Documented approaches that worked well
+- **Gotchas**: Issues to avoid in future work
+- **Estimation Refinements**: Better story sizing guidance
+- **Process Changes**: Workflow adjustments for next epic
+
+**Artifacts:**
+
+- Epic marked as complete with retrospective attached
+- Knowledge base updated with new patterns
+- Workflow templates updated if needed
+- Team learning captured for onboarding

src/modules/bmm/workflows/README.md

@@ -0,0 +1,349 @@
+---
+last-redoc-date: 2025-10-01
+---
+
+# BMM Workflows - The Complete v6 Flow
+
+The BMM (BMAD Method Module) orchestrates software development through four distinct phases, each with specialized workflows that adapt to project scale (Level 0-4) and context (greenfield vs brownfield). This document serves as the master guide for understanding how these workflows interconnect to deliver the revolutionary v6 methodology.
+
+## Core v6 Innovations
+
+**Scale-Adaptive Planning**: Projects automatically route through different workflows based on complexity (Level 0-4), ensuring appropriate documentation and process overhead.
+
+**Just-In-Time Design**: Technical specifications are created one epic at a time during implementation, not all upfront, incorporating learnings as the project evolves.
+
+**Dynamic Expertise Injection**: Story-context workflows provide targeted technical guidance per story, replacing static documentation with contextual expertise.
+
+**Continuous Learning Loop**: Retrospectives feed improvements back into workflows, making each epic smoother than the last.
+
+## The Four Phases
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│                    PHASE 1: ANALYSIS                         │
+│                      (Optional)                              │
+├─────────────────────────────────────────────────────────────┤
+│  brainstorm-game ──┐                                         │
+│  brainstorm-project ├──→ research ──→ product-brief ──┐     │
+│  game-brief ────────┘                                 │     │
+└────────────────────────────────────────────────────────┼─────┘
+                                                         ↓
+┌─────────────────────────────────────────────────────────────┐
+│                    PHASE 2: PLANNING                         │
+│                  (Scale-Adaptive Router)                     │
+├─────────────────────────────────────────────────────────────┤
+│                    plan-project                              │
+│                         ├──→ Level 0: tech-spec only         │
+│                         ├──→ Level 1-2: PRD + tech-spec      │
+│                         ├──→ Level 3-4: PRD + Epics ─────┐   │
+│                         └──→ Game: GDD                   │   │
+└───────────────────────────────────────────────────────────┼──┘
+                                                            ↓
+┌─────────────────────────────────────────────────────────────┐
+│                   PHASE 3: SOLUTIONING                       │
+│                    (Levels 3-4 Only)                         │
+├─────────────────────────────────────────────────────────────┤
+│  3-solutioning ──→ Architecture.md                           │
+│       ↓                                                      │
+│  tech-spec (per epic, JIT during implementation)             │
+└───────────────────────────────────────────────────────────┬─┘
+                                                            ↓
+┌─────────────────────────────────────────────────────────────┐
+│                  PHASE 4: IMPLEMENTATION                     │
+│                    (Iterative Cycle)                         │
+├─────────────────────────────────────────────────────────────┤
+│  ┌─→ create-story ──→ story-context ──→ dev-story ──┐       │
+│  │                                                   ↓       │
+│  │   retrospective ←── [epic done] ←── review-story         │
+│  │                                           ↓               │
+│  └──────────── correct-course ←──[if issues]┘               │
+└─────────────────────────────────────────────────────────────┘
+```
+
+## Phase 1: Analysis (Optional)
+
+Optional workflows for project discovery and requirements gathering. Output feeds into Phase 2 planning.
+
+### Workflows
+
+| Workflow               | Purpose                                     | Output                 | When to Use           |
+| ---------------------- | ------------------------------------------- | ---------------------- | --------------------- |
+| **brainstorm-game**    | Game concept ideation using 5 methodologies | Concept proposals      | New game projects     |
+| **brainstorm-project** | Software solution exploration               | Architecture proposals | New software projects |
+| **game-brief**         | Structured game design foundation           | Game brief document    | Before GDD creation   |
+| **product-brief**      | Strategic product planning culmination      | Product brief          | End of analysis phase |
+| **research**           | Multi-mode research (market/technical/deep) | Research artifacts     | When evidence needed  |
+
+### Flow
+
+```
+Brainstorming → Research → Brief → Planning (Phase 2)
+```
+
+## Phase 2: Planning (Required)
+
+The central orchestrator that determines project scale and generates appropriate planning artifacts.
+
+### Scale Levels
+
+| Level | Scope                    | Outputs                 | Next Phase       |
+| ----- | ------------------------ | ----------------------- | ---------------- |
+| **0** | Single atomic change     | tech-spec only          | → Implementation |
+| **1** | 1-10 stories, 1 epic     | Minimal PRD + tech-spec | → Implementation |
+| **2** | 5-15 stories, 1-2 epics  | Focused PRD + tech-spec | → Implementation |
+| **3** | 12-40 stories, 2-5 epics | Full PRD + Epics list   | → Solutioning    |
+| **4** | 40+ stories, 5+ epics    | Enterprise PRD + Epics  | → Solutioning    |
+
+### Routing Logic
+
+```
+plan-project
+    ├─→ Detect project type (game/web/mobile/backend/etc)
+    ├─→ Assess complexity → assign Level 0-4
+    ├─→ Check context (greenfield/brownfield)
+    │   └─→ If brownfield & undocumented:
+    │       └─→ HALT: "Generate brownfield documentation first"
+    │           └─→ (TBD workflow for codebase analysis)
+    ├─→ Route to appropriate sub-workflow:
+    │   ├─→ Game → GDD workflow
+    │   ├─→ Level 0 → tech-spec workflow
+    │   ├─→ Level 1-2 → PRD + embedded tech-spec
+    │   └─→ Level 3-4 → PRD + epics → Solutioning
+    └─→ Generate project-workflow-analysis.md (tracking doc)
+```
+
+### Key Outputs
+
+- **PRD.md**: Product Requirements Document (Levels 1-4)
+- **Epics.md**: Epic breakdown with stories (Levels 2-4)
+- **tech-spec.md**: Technical specification (Levels 0-2 only)
+- **GDD.md**: Game Design Document (game projects)
+- **project-workflow-analysis.md**: Workflow state tracking
+
+## Phase 3: Solutioning (Levels 3-4 Only)
+
+Architecture and technical design phase for complex projects.
+
+### Workflows
+
+| Workflow          | Owner     | Purpose                        | Output                    | Timing            |
+| ----------------- | --------- | ------------------------------ | ------------------------- | ----------------- |
+| **3-solutioning** | Architect | Create overall architecture    | Architecture.md with ADRs | Once per project  |
+| **tech-spec**     | Architect | Create epic-specific tech spec | tech-spec-epic-N.md       | One per epic, JIT |
+
+### Just-In-Time Tech Specs
+
+```
+FOR each epic in sequence:
+    WHEN ready to implement epic:
+        Architect: Run tech-spec workflow for THIS epic only
+        → Creates tech-spec-epic-N.md
+        → Hands off to implementation
+    IMPLEMENT epic completely
+    THEN move to next epic
+```
+
+**Critical**: Tech specs are created ONE AT A TIME as epics are ready for implementation, not all upfront. This prevents over-engineering and incorporates learning.
+
+## Phase 4: Implementation (Iterative)
+
+The core development cycle that transforms requirements into working software.
+
+### The Implementation Loop
+
+```
+┌─────────────────────────────────────────┐
+│            SM: create-story             │
+│   (Generate next story from epics.md)   │
+└─────────────────────┬───────────────────┘
+                      ↓
+┌─────────────────────────────────────────┐
+│           SM: story-context             │
+│  (Generate expertise injection XML)     │
+└─────────────────────┬───────────────────┘
+                      ↓
+┌─────────────────────────────────────────┐
+│            DEV: dev-story               │
+│  (Implement with context injection)     │
+└─────────────────────┬───────────────────┘
+                      ↓
+┌─────────────────────────────────────────┐
+│         SR/DEV: review-story            │
+│     (Validate against criteria)         │
+└─────────────────────┬───────────────────┘
+                      ↓
+            ┌─────────┴─────────┐
+            │    Issues Found?   │
+            └─────────┬─────────┘
+                ┌─────┴─────┐
+                ↓           ↓
+        [No: Next Story]  [Yes: correct-course]
+                              ↓
+                      [Return to appropriate step]
+```
+
+### Workflow Responsibilities
+
+| Workflow           | Agent  | Purpose                      | Key Innovation             |
+| ------------------ | ------ | ---------------------------- | -------------------------- |
+| **create-story**   | SM     | Generate ONE story at a time | Enforces epics.md planning |
+| **story-context**  | SM     | Create expertise injection   | JIT technical guidance     |
+| **dev-story**      | DEV    | Implement with context       | Resumable after review     |
+| **review-story**   | SR/DEV | Comprehensive validation     | Fresh context review       |
+| **correct-course** | SM     | Handle issues/changes        | Adaptive response          |
+| **retrospective**  | SM     | Capture epic learnings       | Continuous improvement     |
+
+### Story Flow States
+
+```
+Draft (create-story)
+  → Approved (SM approval)
+    → In Progress (dev-story)
+      → Ready for Review (dev complete)
+        → Done (review passed)
+        OR
+        → In Progress (review failed, back to dev)
+```
+
+## Greenfield vs Brownfield Considerations
+
+### Greenfield Projects
+
+- Start with Phase 1 (Analysis) or Phase 2 (Planning)
+- Clean architecture decisions in Phase 3
+- Straightforward implementation in Phase 4
+
+### Brownfield Projects
+
+```
+plan-project (Phase 2)
+    ├─→ Check: Is existing codebase documented?
+    │   ├─→ YES: Proceed with planning
+    │   └─→ NO: HALT with message:
+    │       "Brownfield project requires documentation.
+    │        Please run codebase-analysis workflow first."
+    │        └─→ [TBD: brownfield-analysis workflow]
+    │            ├─→ Analyzes existing code
+    │            ├─→ Documents current architecture
+    │            ├─→ Identifies technical debt
+    │            └─→ Creates baseline documentation
+    └─→ Continue with scale-adaptive planning
+```
+
+**Critical for Brownfield**: Without adequate documentation of the existing system, the planning phase cannot accurately assess scope or create meaningful requirements. The brownfield-analysis workflow (coming soon) will:
+
+- Map existing architecture
+- Document current patterns
+- Identify integration points
+- Assess technical debt
+- Create the baseline needed for planning
+
+## Agent Participation by Phase
+
+| Phase              | Primary Agents      | Supporting Agents           |
+| ------------------ | ------------------- | --------------------------- |
+| **Analysis**       | Analyst, Researcher | PM, PO                      |
+| **Planning**       | PM                  | Analyst, UX Expert          |
+| **Solutioning**    | Architect           | PM, Tech Lead               |
+| **Implementation** | SM, DEV             | SR, PM (for correct-course) |
+
+## Key Files and Artifacts
+
+### Tracking Documents
+
+- **project-workflow-analysis.md**: Maintains workflow state, level, and progress
+- **Epics.md**: Master list of epics and stories (source of truth for planning)
+
+### Phase Outputs
+
+- **Phase 1**: Briefs and research documents
+- **Phase 2**: PRD, Epics, or tech-spec based on level
+- **Phase 3**: Architecture.md, epic-specific tech specs
+- **Phase 4**: Story files, context XMLs, implemented code
+
+## Best Practices
+
+### 1. Respect the Scale
+
+- Don't create PRDs for Level 0 changes
+- Don't skip architecture for Level 3-4 projects
+- Let the workflow determine appropriate artifacts
+
+### 2. Embrace Just-In-Time
+
+- Create tech specs one epic at a time
+- Generate stories as needed, not in batches
+- Build context injections per story
+
+### 3. Maintain Flow Integrity
+
+- Stories must be enumerated in Epics.md
+- Each phase completes before the next begins
+- Use fresh context windows for reviews
+
+### 4. Document Brownfield First
+
+- Never plan without understanding existing code
+- Technical debt must be visible in planning
+- Integration points need documentation
+
+### 5. Learn Continuously
+
+- Run retrospectives after each epic
+- Update workflows based on learnings
+- Share patterns across teams
+
+## Common Pitfalls and Solutions
+
+| Pitfall                           | Solution                              |
+| --------------------------------- | ------------------------------------- |
+| Creating all tech specs upfront   | Use JIT approach - one epic at a time |
+| Skipping story-context generation | Always run after create-story         |
+| Batching story creation           | Create one story at a time            |
+| Ignoring scale levels             | Let plan-project determine level      |
+| Planning brownfield without docs  | Run brownfield-analysis first         |
+| Not running retrospectives        | Schedule after every epic             |
+
+## Quick Reference Commands
+
+```bash
+# Phase 1: Analysis (Optional)
+bmad analyst brainstorm-project
+bmad analyst research
+bmad analyst product-brief
+
+# Phase 2: Planning
+bmad pm plan-project
+
+# Phase 3: Solutioning (L3-4)
+bmad architect solution-architecture
+bmad architect tech-spec  # Per epic, JIT
+
+# Phase 4: Implementation
+bmad sm create-story      # One at a time
+bmad sm story-context     # After each story
+bmad dev develop          # With context loaded
+bmad dev review-story     # Or SR agent
+bmad sm correct-course    # If issues
+bmad sm retrospective     # After epic
+```
+
+## Future Enhancements
+
+### Coming Soon
+
+- **brownfield-analysis**: Automated codebase documentation generator
+- **Workflow orchestration**: Automatic phase transitions
+- **Progress dashboards**: Real-time workflow status
+- **Team synchronization**: Multi-developer story coordination
+
+### Under Consideration
+
+- AI-assisted retrospectives
+- Automated story sizing
+- Predictive epic planning
+- Cross-project learning transfer
+
+---
+
+This document supersedes v6-IMPORTANT-BMM-FLOW.md and serves as the authoritative guide to BMM workflow execution. For detailed information about individual workflows, see their respective README files in the workflow folders.

v6-open-items.md

@@ -13,7 +13,8 @@ Aside from stability and bug fixes found during the alpha period - the main focu
 - DONE: Quick note on BMM v6 Flow
 - DONE: CC SubAgents installed to sub-folders now.
 - DONE: Qwen TOML update.
-- DONE: Diagram alpha BMM flow.
+- DONE: Diagram alpha BMM flow. - added to src/modules/bmm/workflows/
+- DONE: Fix Redoc task to BMB.
 - IN PROGRESS - Team Web Bundler functional
 - IN PROGRESS - bmm `testarch` integrated into the BMM workflow's after aligned with the rest of bmad method flow.
 - IN PROGRESS - Document new agent workflows.