bmad-method 5.1.2 → 6.0.0-alpha.0

package/src/core/workflows/party-mode/instructions.md

@@ -0,0 +1,181 @@
+# Party Mode - Multi-Agent Discussion Instructions
+
+<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
+<critical>This workflow orchestrates group discussions between all installed BMAD agents</critical>
+
+<workflow>
+
+<step n="1" goal="Load Agent Manifest and Configurations">
+  <action>Load the agent manifest from {{manifest}}</action>
+  <action>Parse XML to extract all agent entries with their condensed information:</action>
+    - id (file path)
+    - name
+    - title
+    - role (single sentence with capabilities)
+    - style (communication style)
+    - principles
+    - memories (if present)
+    - collaborators (key collaborators if any)
+
+<action>For each agent found in manifest:</action>
+<check>Look for config override at {{agent_configs}}[module]-[agent-name].md</check>
+<check>If config override exists:</check>
+<action>Load the override configuration</action>
+<action>MERGE override data with manifest data (overrides take precedence):</action> - Override role replaces manifest role if present - Override style replaces manifest style if present - Override principles replace manifest principles if present - Override memories replace or append to manifest memories - Any additional persona elements from override are added
+
+<action>Build complete agent roster with merged personalities</action>
+<action>Store agent data for use in conversation orchestration</action>
+</step>
+
+<step n="2" goal="Initialize Party Mode">
+  <action>Announce party mode activation with enthusiasm</action>
+  <action>List all participating agents with their merged information:</action>
+  <format>
+    🎉 PARTY MODE ACTIVATED! 🎉
+    All agents are here for a group discussion!
+
+    Participating agents:
+    [For each agent in roster:]
+    - [Agent Name] ([Title]): [Role from merged data]
+
+    [Total count] agents ready to collaborate!
+
+    What would you like to discuss with the team?
+
+  </format>
+  <action>Wait for user to provide initial topic or question</action>
+</step>
+
+<step n="3" goal="Orchestrate Multi-Agent Discussion" repeat="until-exit">
+  <action>For each user message or topic:</action>
+
+  <substep n="3a" goal="Determine Relevant Agents">
+    <action>Analyze the user's message/question</action>
+    <action>Identify which agents would naturally respond based on:</action>
+      - Their role and capabilities (from merged data)
+      - Their stated principles
+      - Their memories/context if relevant
+      - Their collaboration patterns
+    <action>Select 2-3 most relevant agents for this response</action>
+    <note>If user addresses specific agent by name, prioritize that agent</note>
+  </substep>
+
+  <substep n="3b" goal="Generate In-Character Responses">
+    <action>For each selected agent, generate authentic response:</action>
+    <action>Use the agent's merged personality data:</action>
+      - Apply their communication style exactly
+      - Reflect their principles in reasoning
+      - Reference their memories if contextually relevant
+      - Maintain their unique voice and perspective
+
+    <action>Enable natural cross-talk between agents:</action>
+      - Agents can reference each other by name
+      - Agents can build on previous points
+      - Agents can respectfully disagree or offer alternatives
+      - Agents can ask follow-up questions to each other
+
+  </substep>
+
+  <substep n="3c" goal="Handle Questions and Interactions">
+    <check>If an agent asks the user a direct question:</check>
+      <action>Clearly highlight the question</action>
+      <action>End that round of responses</action>
+      <action>Display: "[Agent Name]: [Their question]"</action>
+      <action>Display: "[Awaiting user response...]"</action>
+      <action>WAIT for user input before continuing</action>
+
+    <check>If agents ask each other questions:</check>
+      <action>Allow natural back-and-forth in the same response round</action>
+      <action>Maintain conversational flow</action>
+
+    <check>If discussion becomes circular or repetitive:</check>
+      <action>The BMad Master will summarize</action>
+      <action>Redirect to new aspects or ask for user guidance</action>
+
+  </substep>
+
+  <substep n="3d" goal="Format and Present Responses">
+    <action>Present each agent's contribution clearly:</action>
+    <format>
+      [Agent Name]: [Their response in their voice/style]
+
+      [Another Agent]: [Their response, potentially referencing the first]
+
+      [Third Agent if selected]: [Their contribution]
+    </format>
+
+    <action>Maintain spacing between agents for readability</action>
+    <action>Preserve each agent's unique voice throughout</action>
+
+  </substep>
+
+  <substep n="3e" goal="Check for Exit Conditions">
+    <check>If user message contains any {{exit_triggers}}:</check>
+      <action>Have agents provide brief farewells in character</action>
+      <action>Thank user for the discussion</action>
+      <goto step="4">Exit party mode</goto>
+
+    <check>If user seems done or conversation naturally concludes:</check>
+      <ask>Would you like to continue the discussion or end party mode?</ask>
+      <check>If user indicates end:</check>
+        <goto step="4">Exit party mode</goto>
+
+  </substep>
+</step>
+
+<step n="4" goal="Exit Party Mode">
+  <action>Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other</action>
+  <format>
+    [Agent 1]: [Brief farewell in their style]
+
+    [Agent 2]: [Their goodbye]
+
+    🎊 Party Mode ended. Thanks for the great discussion!
+
+  </format>
+  <action>Exit workflow</action>
+</step>
+
+</workflow>
+
+## Role-Playing Guidelines
+
+<guidelines>
+  <guideline>Keep all responses strictly in-character based on merged personality data</guideline>
+  <guideline>Use each agent's documented communication style consistently</guideline>
+  <guideline>Reference agent memories and context when relevant</guideline>
+  <guideline>Allow natural disagreements and different perspectives</guideline>
+  <guideline>Maintain professional discourse while being engaging</guideline>
+  <guideline>Let agents reference each other naturally by name or role</guideline>
+  <guideline>Include personality-driven quirks and occasional humor</guideline>
+  <guideline>Respect each agent's expertise boundaries</guideline>
+</guidelines>
+
+## Question Handling Protocol
+
+<question-protocol>
+  <direct-to-user>
+    When agent asks user a specific question (e.g., "What's your budget?"):
+    - End that round immediately after the question
+    - Clearly highlight the questioning agent and their question
+    - Wait for user response before any agent continues
+  </direct-to-user>
+
+  <rhetorical>
+    Agents can ask rhetorical or thinking-aloud questions without pausing
+  </rhetorical>
+
+  <inter-agent>
+    Agents can question each other and respond naturally within same round
+  </inter-agent>
+</question-protocol>
+
+## Moderation Notes
+
+<moderation>
+  <note>If discussion becomes circular, have bmad-master summarize and redirect</note>
+  <note>If user asks for specific agent, let that agent take primary lead</note>
+  <note>Balance fun and productivity based on conversation tone</note>
+  <note>Ensure all agents stay true to their merged personalities</note>
+  <note>Exit gracefully when user indicates completion</note>
+</moderation>

package/src/core/workflows/party-mode/workflow.yaml

@@ -0,0 +1,24 @@
+# Party Mode - Multi-Agent Group Discussion Workflow
+name: "party-mode"
+description: "Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations"
+author: "BMad"
+
+# Critical data sources - manifest and config overrides
+manifest: "{project-root}/bmad/_cfg/agent-party.xml"
+agent_configs: "{project-root}/bmad/_cfg/agents/"
+date: system-generated
+
+# This is an interactive action workflow - no template output
+template: false
+instructions: "{project-root}/src/core/workflows/party-mode/instructions.md"
+
+# Data files to be loaded at runtime
+data_files:
+  - agent_manifest: "{project-root}/bmad/_cfg/agent-party.xml"
+  - agent_overrides: "{project-root}/bmad/_cfg/agents/*.md"
+
+# Exit conditions
+exit_triggers:
+  - "*exit"
+  - "end party mode"
+  - "stop party mode"

package/src/modules/bmb/_module-installer/install-menu-config.yaml

@@ -0,0 +1,16 @@
+# BMAD™ Method Core Configuration
+
+code: bmb
+name: "BMB: BMad Builder - Agent, Workflow and Module Builder"
+default_selected: false # This module will not be selected by default for new installations
+
+prompt: "Happy Building - Build the Modules, Workflows and Agents of your dreams."
+# Variables from Core Config inserted:
+## user_name
+## communication_language
+## output_folder
+
+src_impact:
+  prompt: "Are you installing this module to your local Forked BMad Core repository? (not a separate project which is normally the case)"
+  default: false
+  result: "{value}"

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

@@ -0,0 +1,30 @@
+<!-- Powered by BMAD-CORE™ -->
+
+# BMad Master Task Executor
+
+<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>
+  <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="*exit">Exit with confirmation</c>
+  </cmds>
+</agent>

package/src/modules/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 build-agent, build-workflow, and build-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 & 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 build-agent
+- **Templates**: Template-to-workflow conversion with proper structure
+- **Tasks**: Task-to-workflow conversion with step mapping
+- **Modules**: Full module creation using build-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:
+  - `build-agent` for complex agent creation
+  - `build-workflow` for template/task conversion
+  - `build-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 & 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 & 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** - build-agent, build-workflow, build-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 build-agent, build-workflow, build-module
+  - Comprehensive path normalization
+  - Migration reporting and validation
+
+## Support
+
+For issues or questions:
+
+- Review the workflow creation guide at `/bmad/bmb/workflows/build-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_