bmad-method 6.0.0-alpha.0 → 6.0.0-alpha.1

package/src/modules/bmb/workflows/convert-legacy/checklist.md

@@ -16,19 +16,20 @@
 #### Content Preservation
 
 - [ ] Agent name, id, title, and icon transferred
-- [ ] All persona elements mapped to v5 structure
-- [ ] All commands converted to v5 <cmds> format
+- [ ] All persona elements mapped to v6 structure
+- [ ] All commands converted to v6 menu array (YAML)
 - [ ] Dependencies properly referenced or converted
-- [ ] Activation instructions adapted to v5 patterns
+- [ ] Activation instructions adapted to v6 patterns
 
-#### v5 Compliance
+#### v6 Compliance (YAML Format)
 
-- [ ] 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
+- [ ] Valid YAML structure with proper indentation
+- [ ] agent.metadata has all required fields (id, name, title, icon, module)
+- [ ] agent.persona has all sections (role, identity, communication_style, principles)
+- [ ] agent.menu uses proper handlers (workflow, action, exec, tmpl, data)
+- [ ] agent.critical_actions array present when needed
+- [ ] agent.prompts defined for any action: "#id" references
+- [ ] File extension is .agent.yaml (will be compiled to .md later)
 
 #### Best Practices
 
@@ -47,18 +48,18 @@
 - [ ] 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/>
+- [ ] Elicitation points (elicit: true) converted to <invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 - [ ] Conditional sections preserved with if="" attributes
 - [ ] Repeatable sections converted to repeat="" attributes
 
-#### v5 Compliance
+#### v6 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)
+- [ ] File structure follows v6 pattern (folder with yaml/md files)
 
 #### Best Practices
 
@@ -87,21 +88,21 @@
 - [ ] If performs actions only, marked as action workflow
 - [ ] Output patterns properly analyzed
 
-#### v5 Compliance
+#### v6 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
+- [ ] Interactive elements use proper v6 tags
+- [ ] Flow control uses v6 patterns (goto, check, loop)
+- [ ] 1-9 elicitation menus converted to v6 elicitation
 - [ ] Critical notices preserved in workflow.yaml
-- [ ] YOLO mode converted to appropriate v5 patterns
+- [ ] YOLO mode converted to appropriate v6 patterns
 
 ### Module-Level Validation
 
 #### Structure
 
-- [ ] Module follows v5 directory structure
+- [ ] Module follows v6 directory structure
 - [ ] All components in correct locations:
   - Agents in /agents/
   - Workflows in /workflows/
@@ -169,7 +170,7 @@
 
 ### Quality Assurance
 
-- [ ] Converted item follows ALL v5 best practices
+- [ ] Converted item follows ALL v6 best practices
 - [ ] Code/config is clean and maintainable
 - [ ] No TODO or FIXME items remain
 - [ ] Ready for production use

package/src/modules/bmb/workflows/convert-legacy/instructions.md

@@ -1,7 +1,8 @@
-# Convert Legacy - v4 to v5 Conversion Instructions
+# Convert Legacy - v4 to v6 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>
+<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
+<parameter name="You MUST have already loaded and processed: {project-root}/bmad/bmb/workflows/convert-legacy/workflow.yaml</critical>
+<critical>Communicate in {communication_language} throughout the conversion process</critical>
 
 <workflow>
 
@@ -9,10 +10,10 @@
 <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
+  - 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
+  - Task: Contains task XML tags
 <ask>Confirm detected type or allow user to correct: "Detected as [type]. Is this correct? (y/n)"</ask>
 </step>
 
@@ -55,19 +56,18 @@ For Modules:
 - Installation requirements
 
 <action>Create a conversion map of what needs to be transformed</action>
-<action>Map v4 patterns to v5 equivalents:
+<action>Map v4 patterns to v6 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
+- v4 Task + Template → v6 Workflow (folder with workflow.yaml, instructions.md, template.md)
+- v4 Agent YAML → v6 Agent YAML format
+- v4 Commands → v6 <menu> with proper handlers
+- v4 Dependencies → v6 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 if="custom module"><ask>Enter custom module code (kebab-case):</ask></action>
 <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>
@@ -78,16 +78,19 @@ For Modules:
 <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="agent conversion">
+  <check if="simple agent (basic persona + commands)">
+    <action>Use direct conversion to v6 agent YAML format</action>
+    <goto step="5a">Direct Agent Conversion</goto>
+  </check>
+  <check if="complex agent with embedded workflows">
+    <action>Plan to invoke create-agent workflow</action>
+    <goto step="5b">Workflow-Assisted Agent Creation</goto>
+  </check>
+</check>
 
-<check>If template or task conversion to workflow:</check>
-<action>Analyze the v4 item to determine workflow type:</action>
+<check if="template or task conversion to workflow">
+  <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
@@ -103,56 +106,61 @@ For Modules:
 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>
+<action if="template conversion"><goto step="5c">Template-to-Workflow Conversion</goto></action>
+<action if="task conversion"><goto step="5e">Task-to-Workflow Conversion</goto></action>
+</check>
 
-<check>If full module conversion:</check>
-<action>Plan to invoke create-module workflow</action>
-<goto step="5d">Module Creation</goto>
+<check if="full module conversion">
+  <action>Plan to invoke create-module workflow</action>
+  <goto step="5d">Module Creation</goto>
+</check>
 </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
+<action>Transform v4 YAML agent to v6 YAML format:</action>
+
+1. Convert agent metadata structure:
+   - v4 `agent.name` → v6 `agent.metadata.name`
+   - v4 `agent.id` → v6 `agent.metadata.id`
+   - v4 `agent.title` → v6 `agent.metadata.title`
+   - v4 `agent.icon` → v6 `agent.metadata.icon`
+   - Add v6 `agent.metadata.module` field
+
+2. Transform persona structure:
+   - v4 `persona.role` → v6 `agent.persona.role` (keep as YAML string)
+   - v4 `persona.style` → v6 `agent.persona.communication_style`
+   - v4 `persona.identity` → v6 `agent.persona.identity`
+   - v4 `persona.core_principles` → v6 `agent.persona.principles` (as array)
+
+3. Convert commands to menu:
+   - v4 `commands:` list → v6 `agent.menu:` array
+   - Each command becomes menu item with:
+     - `trigger:` (without \* prefix - added at build)
+     - `description:`
+     - Handler attributes (`workflow:`, `exec:`, `action:`, etc.)
+   - Map task references to workflow paths
    - 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
+4. Add v6-specific sections (in YAML):
+   - `agent.prompts:` array for inline prompts (if using action: "#id")
+   - `agent.critical_actions:` array for startup requirements
+   - `agent.activation_rules:` for universal agent rules
 
 5. Handle dependencies and paths:
    - Convert task dependencies to workflow references
-   - Map template dependencies to v5 workflows
+   - Map template dependencies to v6 workflows
    - Preserve checklist and data file references
-   - CRITICAL: All exec/data/run-workflow paths must use {project-root}/bmad/{{module}}/ NOT src/
+   - CRITICAL: All paths must use {project-root}/bmad/{{module}}/ NOT src/
 
-<action>Generate the converted v5 agent file with proper XML structure</action>
+<action>Generate the converted v6 agent YAML file (.agent.yaml)</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>
+  <action>Save to: bmad/{{target_module}}/agents/{{agent_name}}.agent.yaml (physical location)</action>
+  <action>Note: The build process will later compile this to .md with XML format</action>
   <goto step="6">Continue to Validation</goto>
   </step>
 
@@ -164,7 +172,7 @@ For Modules:
 - Any special behaviors
 
 <invoke-workflow>
-  workflow: {project-root}/bmad/bmb/workflows/build-agent/workflow.yaml
+  workflow: {project-root}/bmad/bmb/workflows/create-agent/workflow.yaml
   inputs:
     - agent_name: {{extracted_name}}
     - agent_purpose: {{extracted_purpose}}
@@ -176,7 +184,7 @@ For Modules:
 </step>
 
 <step n="5c" goal="Template-to-Workflow Conversion" optional="true">
-<action>Convert v4 Template (YAML) to v5 Workflow:</action>
+<action>Convert v4 Template (YAML) to v6 Workflow:</action>
 
 1. Extract template metadata:
    - Template id, name, version → workflow.yaml name/description
@@ -185,7 +193,7 @@ For Modules:
 
 2. Convert template sections to instructions.md:
    - Each YAML section → workflow step
-   - `elicit: true` → `<elicit-required/>` tag
+   - `elicit: true` → `<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>` tag
    - Conditional sections → `if="condition"` attribute
    - Repeatable sections → `repeat="for-each"` attribute
    - Section instructions → step content
@@ -196,12 +204,23 @@ For Modules:
    - Nested sections → hierarchical markdown
 
 4. Handle v4 create-doc.md task integration:
-   - Elicitation methods (1-9 menu) → convert to v5 elicitation
+   - Elicitation methods (1-9 menu) → convert to v6 elicitation
    - Agent permissions → note in instructions
    - Processing flow → integrate into workflow steps
 
+<critical>When invoking create-workflow, the standard config block will be automatically added:</critical>
+
+```yaml
+# Critical variables from config
+config_source: '{project-root}/bmad/{{target_module}}/config.yaml'
+output_folder: '{config_source}:output_folder'
+user_name: '{config_source}:user_name'
+communication_language: '{config_source}:communication_language'
+date: system-generated
+```
+
 <invoke-workflow>
-  workflow: {project-root}/bmad/bmb/workflows/build-workflow/workflow.yaml
+  workflow: {project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml
   inputs:
     - workflow_name: {{template_name}}
     - workflow_type: document
@@ -209,6 +228,9 @@ For Modules:
     - instructions: {{converted_sections}}
 </invoke-workflow>
 
+<action>Verify the created workflow.yaml includes standard config block</action>
+<action>Update converted instructions to use config variables where appropriate</action>
+
 <goto step="6">Continue to Validation</goto>
 </step>
 
@@ -217,7 +239,7 @@ For Modules:
 <action>Create module blueprint with all components</action>
 
 <invoke-workflow>
-  workflow: {project-root}/bmad/bmb/workflows/build-module/workflow.yaml
+  workflow: {project-root}/bmad/bmb/workflows/create-module/workflow.yaml
   inputs:
     - module_name: {{module_name}}
     - components: {{component_list}}
@@ -227,7 +249,7 @@ For Modules:
 </step>
 
 <step n="5e" goal="Task-to-Workflow Conversion" optional="true">
-<action>Convert v4 Task (Markdown) to v5 Workflow:</action>
+<action>Convert v4 Task (Markdown) to v6 Workflow:</action>
 
 1. Analyze task purpose and output:
    - Does it generate documents? → Create template.md
@@ -239,27 +261,40 @@ For Modules:
    - 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
+   - User interaction patterns → appropriate v6 tags
 
 3. Based on confirmed workflow type:
-   <check>If Document workflow:</check>
+   <check if="Document workflow">
    - Create template.md from output patterns
    - Map generation steps to instructions
-   - Add <template-output> tags for sections
+   - Add template-output tags for sections
+     </check>
 
-   <check>If Action workflow:</check>
-   - Set template: false in workflow.yaml
-   - Focus on action sequences in instructions
-   - Preserve execution logic
+   <check if="Action workflow">
+     - Set template: false in workflow.yaml
+     - Focus on action sequences in instructions
+     - Preserve execution logic
+   </check>
 
 4. Handle special v4 patterns:
-   - 1-9 elicitation menus → v5 <elicit-required/>
+   - 1-9 elicitation menus → v6 <invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
    - Agent permissions → note in instructions
    - YOLO mode → autonomous flag or optional steps
    - Critical notices → workflow.yaml comments
 
+<critical>When invoking create-workflow, the standard config block will be automatically added:</critical>
+
+```yaml
+# Critical variables from config
+config_source: '{project-root}/bmad/{{target_module}}/config.yaml'
+output_folder: '{config_source}:output_folder'
+user_name: '{config_source}:user_name'
+communication_language: '{config_source}:communication_language'
+date: system-generated
+```
+
 <invoke-workflow>
-  workflow: {project-root}/bmad/bmb/workflows/build-workflow/workflow.yaml
+  workflow: {project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml
   inputs:
     - workflow_name: {{task_name}}
     - workflow_type: {{confirmed_workflow_type}}
@@ -267,6 +302,9 @@ For Modules:
     - template: {{generated_template_if_document}}
 </invoke-workflow>
 
+<action>Verify the created workflow.yaml includes standard config block</action>
+<action>Update converted instructions to use config variables where appropriate</action>
+
 <goto step="6">Continue to Validation</goto>
 </step>
 
@@ -275,18 +313,29 @@ For Modules:
 
 For Agents:
 
-- [ ] Valid XML structure
-- [ ] All required sections present
-- [ ] Commands properly formatted
-- [ ] Activation sequence correct
+- [ ] Valid YAML structure (.agent.yaml)
+- [ ] All required sections present (metadata, persona, menu)
+- [ ] Menu items properly formatted (trigger, description, handlers)
+- [ ] Paths use {project-root} variables
 
 For Workflows:
 
 - [ ] Valid YAML syntax
-- [ ] Instructions follow v5 conventions
+- [ ] Instructions follow v6 conventions
 - [ ] Template variables match
 - [ ] File structure correct
 
+**Standard Config Validation (Workflows):**
+
+- [ ] workflow.yaml contains standard config block:
+  - config_source defined
+  - output_folder, user_name, communication_language pulled from config
+  - date set to system-generated
+- [ ] Converted instructions use config variables where appropriate
+- [ ] Template includes config variables in metadata (if document workflow)
+- [ ] No hardcoded paths that should use {output_folder}
+- [ ] No generic greetings that should use {user_name}
+
 For Modules:
 
 - [ ] All components converted
@@ -296,33 +345,33 @@ For Modules:
 
 <action>Show validation results to user</action>
 <ask>Any issues to fix before finalizing? (y/n)</ask>
-<check>If yes:</check>
+<check if="yes">
 <action>Address specific issues</action>
 <goto step="6">Re-validate</goto>
+</check>
 </step>
 
 <step n="7" goal="Migration Report">
 <action>Generate conversion report showing:</action>
 - Original v4 location
-- New v5 location
+- New v6 location
 - Items converted
 - Any manual adjustments needed
 - Warnings or notes
 
 <action>Save report to: {output_folder}/conversion-report-{{date}}.md</action>
+<action>Inform {user_name} in {communication_language} that the conversion report has been generated</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 if="yes">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>
+<action if="yes"><goto step="1">Start new conversion</goto></action>
 </step>
 
 </workflow>

package/src/modules/bmb/workflows/convert-legacy/workflow.yaml

@@ -1,4 +1,4 @@
-# Convert Legacy - BMAD v4 to v5 Converter Configuration
+# Convert Legacy - BMAD v4 to v6 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"
@@ -7,14 +7,12 @@ author: "BMad"
 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"
-  - conversion_mappings: "{project-root}/bmad/bmb/data/v4-to-v5-mappings.yaml"
 
 # Module path and component files
 installed_path: "{project-root}/bmad/bmb/workflows/convert-legacy"
@@ -27,9 +25,10 @@ default_output_folder: "{project-root}/bmad/{{target_module}}/{{item_type}}/{{it
 
 # Sub-workflows that may be invoked for conversion
 sub_workflows:
-  - create_agent: "{project-root}/bmad/bmb/workflows/build-agent/workflow.yaml"
-  - create_workflow: "{project-root}/bmad/bmb/workflows/build-workflow/workflow.yaml"
-  - create_module: "{project-root}/bmad/bmb/workflows/build-module/workflow.yaml"
+  - 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"
 
-# No special tools required beyond standard BMAD capabilities
-required_tools: []
+standalone: true
+
+web_bundle: false