v4-v6 upgrade improvement and warning about file auto backup

bmad/core/agents/bmad-master.md

@@ -0,0 +1,78 @@
+<!-- Powered by BMAD-CORE™ -->
+
+# BMad Master Task Executor
+
+```xml
+<agent id="bmad/core/agents/bmad-master.md" name="BMad Master" title="BMad Master Task Executor" 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 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>
+  <critical-actions>
+    <i>Load into memory {project-root}/bmad/core/config.yaml and set variable project_name, 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="*list-tasks" action="list all tasks from {project-root}/bmad/_cfg/task-manifest.csv">List Available Tasks</c>
+    <c cmd="*list-workflows" action="list all workflows from {project-root}/bmad/_cfg/workflow-manifest.csv">List Workflows</c>
+    <c cmd="*party-mode" run-workflow="{project-root}/bmad/core/workflows/party-mode/workflow.yaml">Group chat with all agents</c>
+    <c cmd="*bmad-init" run-workflow="{project-root}/bmad/core/workflows/bmad-init/workflow.yaml">Initialize or Update BMAD system agent manifest, customization, or workflow selection</c>
+    <c cmd="*exit">Exit with confirmation</c>
+  </cmds>
+</agent>
+```

bmad/core/config.yaml

@@ -0,0 +1,8 @@
+# CORE Module Configuration
+# Generated by BMAD installer
+# Version: 6.0.0-alpha.0
+# Date: 2025-10-01T00:22:43.654Z
+
+user_name: BMad
+communication_language: English
+output_folder: "{project-root}/docs"

bmad/core/tasks/adv-elicit-methods.csv

@@ -0,0 +1,39 @@
+category,method_name,description,output_pattern
+advanced,Tree of Thoughts,Explore multiple reasoning paths simultaneously then evaluate and select the best - perfect for complex problems with multiple valid approaches where finding the optimal path matters,paths → evaluation → selection
+advanced,Graph of Thoughts,Model reasoning as an interconnected network of ideas to reveal hidden relationships - ideal for systems thinking and discovering emergent patterns in complex multi-factor situations,nodes → connections → patterns
+advanced,Thread of Thought,Maintain coherent reasoning across long contexts by weaving a continuous narrative thread - essential for RAG systems and maintaining consistency in lengthy analyses,context → thread → synthesis
+advanced,Self-Consistency Validation,Generate multiple independent approaches then compare for consistency - crucial for high-stakes decisions where verification and consensus building matter,approaches → comparison → consensus
+advanced,Meta-Prompting Analysis,Step back to analyze the approach structure and methodology itself - valuable for optimizing prompts and improving problem-solving strategies,current → analysis → optimization
+advanced,Reasoning via Planning,Build a reasoning tree guided by world models and goal states - excellent for strategic planning and sequential decision-making tasks,model → planning → strategy
+collaboration,Stakeholder Round Table,Convene multiple personas to contribute diverse perspectives - essential for requirements gathering and finding balanced solutions across competing interests,perspectives → synthesis → alignment
+collaboration,Expert Panel Review,Assemble domain experts for deep specialized analysis - ideal when technical depth and peer review quality are needed,expert views → consensus → recommendations
+competitive,Red Team vs Blue Team,Adversarial attack-defend analysis to find vulnerabilities - critical for security testing and building robust solutions through adversarial thinking,defense → attack → hardening
+core,Expand or Contract for Audience,Dynamically adjust detail level and technical depth for target audience - essential when content needs to match specific reader capabilities,audience → adjustments → refined content
+core,Critique and Refine,Systematic review to identify strengths and weaknesses then improve - standard quality check for drafts needing polish and enhancement,strengths/weaknesses → improvements → refined version
+core,Explain Reasoning,Walk through step-by-step thinking to show how conclusions were reached - crucial for transparency and helping others understand complex logic,steps → logic → conclusion
+core,First Principles Analysis,Strip away assumptions to rebuild from fundamental truths - breakthrough technique for innovation and solving seemingly impossible problems,assumptions → truths → new approach
+core,5 Whys Deep Dive,Repeatedly ask why to drill down to root causes - simple but powerful for understanding failures and fixing problems at their source,why chain → root cause → solution
+core,Socratic Questioning,Use targeted questions to reveal hidden assumptions and guide discovery - excellent for teaching and helping others reach insights themselves,questions → revelations → understanding
+creative,Reverse Engineering,Work backwards from desired outcome to find implementation path - powerful for goal achievement and understanding how to reach specific endpoints,end state → steps backward → path forward
+creative,What If Scenarios,Explore alternative realities to understand possibilities and implications - valuable for contingency planning and creative exploration,scenarios → implications → insights
+creative,SCAMPER Method,Apply seven creativity lenses (Substitute/Combine/Adapt/Modify/Put/Eliminate/Reverse) - systematic ideation for product innovation and improvement,S→C→A→M→P→E→R
+learning,Feynman Technique,Explain complex concepts simply as if teaching a child - the ultimate test of true understanding and excellent for knowledge transfer,complex → simple → gaps → mastery
+learning,Active Recall Testing,Test understanding without references to verify true knowledge - essential for identifying gaps and reinforcing mastery,test → gaps → reinforcement
+narrative,Unreliable Narrator Mode,Question assumptions and biases by adopting skeptical perspective - crucial for detecting hidden agendas and finding balanced truth,perspective → biases → balanced view
+optimization,Speedrun Optimization,Find the fastest most efficient path by eliminating waste - perfect when time pressure demands maximum efficiency,current → bottlenecks → optimized
+optimization,New Game Plus,Revisit challenges with enhanced capabilities from prior experience - excellent for iterative improvement and mastery building,initial → enhanced → improved
+optimization,Roguelike Permadeath,Treat decisions as irreversible to force careful high-stakes analysis - ideal for critical decisions with no second chances,decision → consequences → execution
+philosophical,Occam's Razor Application,Find the simplest sufficient explanation by eliminating unnecessary complexity - essential for debugging and theory selection,options → simplification → selection
+philosophical,Trolley Problem Variations,Explore ethical trade-offs through moral dilemmas - valuable for understanding values and making difficult ethical decisions,dilemma → analysis → decision
+quantum,Observer Effect Consideration,Analyze how the act of measurement changes what's being measured - important for understanding metrics impact and self-aware systems,unmeasured → observation → impact
+retrospective,Hindsight Reflection,Imagine looking back from the future to gain perspective - powerful for project reviews and extracting wisdom from experience,future view → insights → application
+retrospective,Lessons Learned Extraction,Systematically identify key takeaways and actionable improvements - essential for knowledge transfer and continuous improvement,experience → lessons → actions
+risk,Identify Potential Risks,Brainstorm what could go wrong across all categories - fundamental for project planning and deployment preparation,categories → risks → mitigations
+risk,Challenge from Critical Perspective,Play devil's advocate to stress-test ideas and find weaknesses - essential for overcoming groupthink and building robust solutions,assumptions → challenges → strengthening
+risk,Failure Mode Analysis,Systematically explore how each component could fail - critical for reliability engineering and safety-critical systems,components → failures → prevention
+risk,Pre-mortem Analysis,Imagine future failure then work backwards to prevent it - powerful technique for risk mitigation before major launches,failure scenario → causes → prevention
+scientific,Peer Review Simulation,Apply rigorous academic evaluation standards - ensures quality through methodology review and critical assessment,methodology → analysis → recommendations
+scientific,Reproducibility Check,Verify results can be replicated independently - fundamental for reliability and scientific validity,method → replication → validation
+structural,Dependency Mapping,Visualize interconnections to understand requirements and impacts - essential for complex systems and integration planning,components → dependencies → impacts
+structural,Information Architecture Review,Optimize organization and hierarchy for better user experience - crucial for fixing navigation and findability problems,current → pain points → restructure
+structural,Skeleton of Thought,Create structure first then expand branches in parallel - efficient for generating long content quickly with good organization,skeleton → branches → integration

bmad/core/tasks/adv-elicit.md

@@ -0,0 +1,109 @@
+<!-- BMAD-CORE™ Advanced Elicitation Task v2.0 (LLM-Native) -->
+
+# Advanced Elicitation v2.0 (LLM-Native)
+
+```xml
+<task id="bmad/core/tasks/adv-elicit.md" name="Advanced Elicitation">
+  <llm critical="true">
+    <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
+    <i>DO NOT skip steps or change the sequence</i>
+    <i>HALT immediately when halt-conditions are met</i>
+    <i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
+    <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
+  </llm>
+
+  <integration description="When called from workflow">
+    <desc>When called during template workflow processing:</desc>
+    <i>1. Receive the current section content that was just generated</i>
+    <i>2. Apply elicitation methods iteratively to enhance that specific content</i>
+    <i>3. Return the enhanced version back when user selects 'x' to proceed and return back</i>
+    <i>4. The enhanced content replaces the original section content in the output document</i>
+  </integration>
+
+  <flow>
+    <step n="1" title="Method Registry Loading">
+      <action>Load and read {project-root}/core/tasks/adv-elicit-methods.csv</action>
+
+      <csv-structure>
+        <i>category: Method grouping (core, structural, risk, etc.)</i>
+        <i>method_name: Display name for the method</i>
+        <i>description: Rich explanation of what the method does, when to use it, and why it's valuable</i>
+        <i>output_pattern: Flexible flow guide using → arrows (e.g., "analysis → insights → action")</i>
+      </csv-structure>
+
+      <context-analysis>
+        <i>Use conversation history</i>
+        <i>Analyze: content type, complexity, stakeholder needs, risk level, and creative potential</i>
+      </context-analysis>
+
+      <smart-selection>
+        <i>1. Analyze context: Content type, complexity, stakeholder needs, risk level, creative potential</i>
+        <i>2. Parse descriptions: Understand each method's purpose from the rich descriptions in CSV</i>
+        <i>3. Select 5 methods: Choose methods that best match the context based on their descriptions</i>
+        <i>4. Balance approach: Include mix of foundational and specialized techniques as appropriate</i>
+      </smart-selection>
+    </step>
+
+    <step n="2" title="Present Options and Handle Responses">
+
+      <format>
+        **Advanced Elicitation Options**
+        Choose a number (1-5), r to shuffle, or x to proceed:
+
+        1. [Method Name]
+        2. [Method Name]
+        3. [Method Name]
+        4. [Method Name]
+        5. [Method Name]
+        r. Reshuffle the list with 5 new options
+        x. Proceed / No Further Actions
+      </format>
+
+      <response-handling>
+        <case n="1-5">
+          <i>Execute the selected method using its description from the CSV</i>
+          <i>Adapt the method's complexity and output format based on the current context</i>
+          <i>Apply the method creatively to the current section content being enhanced</i>
+          <i>Display the enhanced version showing what the method revealed or improved</i>
+          <i>CRITICAL: Ask the user if they would like to apply the changes to the doc (y/n/other) and HALT to await response.</i>
+          <i>CRITICAL: ONLY if Yes, apply the changes. IF No, discard your memory of the proposed changes. If any other reply, try best to follow the instructions given by the user.</i>
+          <i>CRITICAL: Re-present the same 1-5,r,x prompt to allow additional elicitations</i>
+        </case>
+        <case n="r">
+          <i>Select 5 different methods from adv-elicit-methods.csv, present new list with same prompt format</i>
+        </case>
+        <case n="x">
+          <i>Complete elicitation and proceed</i>
+          <i>Return the fully enhanced content back to create-doc.md</i>
+          <i>The enhanced content becomes the final version for that section</i>
+          <i>Signal completion back to create-doc.md to continue with next section</i>
+        </case>
+        <case n="direct-feedback">
+          <i>Apply changes to current section content and re-present choices</i>
+        </case>
+        <case n="multiple-numbers">
+          <i>Execute methods in sequence on the content, then re-offer choices</i>
+        </case>
+      </response-handling>
+    </step>
+
+    <step n="3" title="Execution Guidelines">
+      <i>Method execution: Use the description from CSV to understand and apply each method</i>
+      <i>Output pattern: Use the pattern as a flexible guide (e.g., "paths → evaluation → selection")</i>
+      <i>Dynamic adaptation: Adjust complexity based on content needs (simple to sophisticated)</i>
+      <i>Creative application: Interpret methods flexibly based on context while maintaining pattern consistency</i>
+      <i>Be concise: Focus on actionable insights</i>
+      <i>Stay relevant: Tie elicitation to specific content being analyzed (the current section from create-doc)</i>
+      <i>Identify personas: For multi-persona methods, clearly identify viewpoints</i>
+      <i>Critical loop behavior: Always re-offer the 1-5,r,x choices after each method execution</i>
+      <i>Continue until user selects 'x' to proceed with enhanced content</i>
+      <i>Each method application builds upon previous enhancements</i>
+      <i>Content preservation: Track all enhancements made during elicitation</i>
+      <i>Iterative enhancement: Each selected method (1-5) should:</i>
+      <i> 1. Apply to the current enhanced version of the content</i>
+      <i> 2. Show the improvements made</i>
+      <i> 3. Return to the prompt for additional elicitations or completion</i>
+    </step>
+  </flow>
+</task>
+```

bmad/core/tasks/index-docs.md

@@ -0,0 +1,69 @@
+<!-- BMAD-CORE™ Index Documentation Task -->
+
+# Index Docs v1.1
+
+```xml
+<task id="bmad/core/tasks/index-docs" name="Index Docs" webskip="true">
+  <llm critical="true">
+    <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
+    <i>DO NOT skip steps or change the sequence</i>
+    <i>HALT immediately when halt-conditions are met</i>
+    <i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
+    <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
+  </llm>
+
+  <flow>
+    <step n="1" title="Scan Directory">
+      <i>List all files and subdirectories in the target location</i>
+    </step>
+
+    <step n="2" title="Group Content">
+      <i>Organize files by type, purpose, or subdirectory</i>
+    </step>
+
+    <step n="3" title="Generate Descriptions">
+      <i>Read each file to understand its actual purpose and create brief (3-10 word) descriptions based on the content, not just the filename</i>
+    </step>
+
+    <step n="4" title="Create/Update Index">
+      <i>Write or update index.md with organized file listings</i>
+    </step>
+  </flow>
+
+  <output-format>
+    <example>
+      # Directory Index
+
+      ## Files
+
+      - **[filename.ext](./filename.ext)** - Brief description
+      - **[another-file.ext](./another-file.ext)** - Brief description
+
+      ## Subdirectories
+
+      ### subfolder/
+
+      - **[file1.ext](./subfolder/file1.ext)** - Brief description
+      - **[file2.ext](./subfolder/file2.ext)** - Brief description
+
+      ### another-folder/
+
+      - **[file3.ext](./another-folder/file3.ext)** - Brief description
+    </example>
+  </output-format>
+
+  <halt-conditions critical="true">
+    <i>HALT if target directory does not exist or is inaccessible</i>
+    <i>HALT if user does not have write permissions to create index.md</i>
+  </halt-conditions>
+
+  <validation>
+    <i>Use relative paths starting with ./</i>
+    <i>Group similar files together</i>
+    <i>Read file contents to generate accurate descriptions - don't guess from filenames</i>
+    <i>Keep descriptions concise but informative (3-10 words)</i>
+    <i>Sort alphabetically within groups</i>
+    <i>Skip hidden files (starting with .) unless specified</i>
+  </validation>
+</task>
+```

bmad/core/tasks/shard-doc.md

@@ -0,0 +1,57 @@
+<!-- BMAD-CORE™ Document Sharding Task -->
+
+# Shard Doc v1.1
+
+```xml
+<task id="bmad/core/tasks/shard-doc.md" name="Shard Doc">
+  <llm critical="true">
+    <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
+    <i>DO NOT skip steps or change the sequence</i>
+    <i>HALT immediately when halt-conditions are met</i>
+    <i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
+    <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
+  </llm>
+
+  <flow>
+    <step n="1" title="Check for Tool">
+      <i>First check if md-tree command is available</i>
+    </step>
+
+    <step n="2" title="Install if Needed">
+      <i>If not available, ask user permission to install: npm install -g @kayvan/markdown-tree-parser</i>
+    </step>
+
+    <step n="3" title="Shard Document">
+      <i>Use the explode command to split the document</i>
+    </step>
+  </flow>
+
+  <usage>
+    <commands>
+      # Install the tool (if needed)
+      npm install -g @kayvan/markdown-tree-parser
+
+      # Shard a document
+      md-tree explode [source-document] [destination-folder]
+
+      # Examples
+      md-tree explode docs/prd.md docs/prd
+      md-tree explode docs/architecture.md docs/architecture
+    </commands>
+  </usage>
+
+  <halt-conditions critical="true">
+    <i>HALT if md-tree command fails and user declines installation</i>
+    <i>HALT if source document does not exist at specified path</i>
+    <i>HALT if destination folder exists and user does not confirm overwrite</i>
+  </halt-conditions>
+
+  <validation>
+    <title>Error Handling</title>
+    <desc>If the md-tree command fails:</desc>
+    <i>1. Check if the tool is installed globally</i>
+    <i>2. Ask user permission to install it</i>
+    <i>3. Retry the operation after installation</i>
+  </validation>
+</task>
+```

bmad/core/tasks/validate-workflow.md

@@ -0,0 +1,92 @@
+# Validate Workflow
+
+```xml
+<task id="bmad/core/tasks/validate-workflow.md" name="Validate Workflow Output">
+  <objective>Run a checklist against a document with thorough analysis and produce a validation report</objective>
+
+  <inputs>
+    <input name="workflow" desc="Workflow path containing checklist.md" />
+    <input name="checklist" desc="Checklist to validate against (defaults to workflow's checklist.md)" />
+    <input name="document" desc="Document to validate (ask user if not specified)" />
+  </inputs>
+
+  <flow>
+    <step n="1" title="Setup">
+      <action>If checklist not provided, load checklist.md from workflow location</action>
+      <action>If document not provided, ask user: "Which document should I validate?"</action>
+      <action>Load both the checklist and document</action>
+    </step>
+
+    <step n="2" title="Validate" critical="true">
+      <mandate>For EVERY checklist item, WITHOUT SKIPPING ANY:</mandate>
+
+      <for-each-item>
+        <action>Read requirement carefully</action>
+        <action>Search document for evidence along with any ancillary loaded documents or artifacts (quotes with line numbers)</action>
+        <action>Analyze deeply - look for explicit AND implied coverage</action>
+
+        <mark-as>
+          ✓ PASS - Requirement fully met (provide evidence)
+          ⚠ PARTIAL - Some coverage but incomplete (explain gaps)
+          ✗ FAIL - Not met or severely deficient (explain why)
+          ➖ N/A - Not applicable (explain reason)
+        </mark-as>
+      </for-each-item>
+
+      <critical>DO NOT SKIP ANY SECTIONS OR ITEMS</critical>
+    </step>
+
+    <step n="3" title="Generate Report">
+      <action>Create validation-report-{timestamp}.md in document's folder</action>
+
+      <report-format>
+        # Validation Report
+
+        **Document:** {document-path}
+        **Checklist:** {checklist-path}
+        **Date:** {timestamp}
+
+        ## Summary
+        - Overall: X/Y passed (Z%)
+        - Critical Issues: {count}
+
+        ## Section Results
+
+        ### {Section Name}
+        Pass Rate: X/Y (Z%)
+
+        {For each item:}
+        [MARK] {Item description}
+        Evidence: {Quote with line# or explanation}
+        {If FAIL/PARTIAL: Impact: {why this matters}}
+
+        ## Failed Items
+        {All ✗ items with recommendations}
+
+        ## Partial Items
+        {All ⚠ items with what's missing}
+
+        ## Recommendations
+        1. Must Fix: {critical failures}
+        2. Should Improve: {important gaps}
+        3. Consider: {minor improvements}
+      </report-format>
+    </step>
+
+    <step n="4" title="Summary for User">
+      <action>Present section-by-section summary</action>
+      <action>Highlight all critical issues</action>
+      <action>Provide path to saved report</action>
+      <action>HALT - do not continue unless user asks</action>
+    </step>
+  </flow>
+
+  <critical-rules>
+    <rule>NEVER skip sections - validate EVERYTHING</rule>
+    <rule>ALWAYS provide evidence (quotes + line numbers) for marks</rule>
+    <rule>Think deeply about each requirement - don't rush</rule>
+    <rule>Save report to document's folder automatically</rule>
+    <rule>HALT after presenting summary - wait for user</rule>
+  </critical-rules>
+</task>
+```

bmad/core/tasks/workflow.md

@@ -0,0 +1,141 @@
+<!-- BMAD Method v6 Workflow Execution Task (Simplified) -->
+
+# Workflow
+
+```xml
+<task id="bmad/core/tasks/workflow.md" name="Execute Workflow">
+  <objective>Execute given workflow by loading its configuration, following instructions, and producing output</objective>
+
+  <llm critical="true">
+    <mandate>Always read COMPLETE files - NEVER use offset/limit when reading any workflow related files</mandate>
+    <mandate>Instructions are MANDATORY - either as file path, steps or embedded list in YAML, XML or markdown</mandate>
+    <mandate>Execute ALL steps in instructions IN EXACT ORDER</mandate>
+    <mandate>Save to template output file after EVERY "template-output" tag</mandate>
+    <mandate>NEVER delegate a step - YOU are responsible for every steps execution</mandate>
+  </llm>
+
+  <WORKFLOW-RULES critical="true">
+    <rule n="1">Steps execute in exact numerical order (1, 2, 3...)</rule>
+    <rule n="2">Optional steps: Ask user unless #yolo mode active</rule>
+    <rule n="3">Template-output tags: Save content → Show user → Get approval before continuing</rule>
+    <rule n="4">Elicit tags: Execute immediately unless #yolo mode (which skips ALL elicitation)</rule>
+    <rule n="5">User must approve each major section before continuing UNLESS #yolo mode active</rule>
+  </WORKFLOW-RULES>
+
+  <flow>
+    <step n="1" title="Load and Initialize Workflow">
+      <substep n="1a" title="Load Configuration and Resolve Variables">
+        <action>Read workflow.yaml from provided path</action>
+        <mandate>Load config_source (REQUIRED for all modules)</mandate>
+        <phase n="1">Load external config from config_source path</phase>
+        <phase n="2">Resolve all {config_source}: references with values from config</phase>
+        <phase n="3">Resolve system variables (date:system-generated) and paths ({project-root}, {installed_path})</phase>
+        <phase n="4">Ask user for input of any variables that are still unknown</phase>
+      </substep>
+
+      <substep n="1b" title="Load Required Components">
+        <mandate>Instructions: Read COMPLETE file from path OR embedded list (REQUIRED)</mandate>
+        <check>If template path → Read COMPLETE template file</check>
+        <check>If validation path → Note path for later loading when needed</check>
+        <check>If template: false → Mark as action-workflow (else template-workflow)</check>
+        <note>Data files (csv, json) → Store paths only, load on-demand when instructions reference them</note>
+      </substep>
+
+      <substep n="1c" title="Initialize Output" if="template-workflow">
+        <action>Resolve default_output_file path with all variables and {{date}}</action>
+        <action>Create output directory if doesn't exist</action>
+        <action>If template-workflow → Write template to output file with placeholders</action>
+        <action>If action-workflow → Skip file creation</action>
+      </substep>
+    </step>
+
+    <step n="2" title="Process Each Instruction Step">
+      <iterate>For each step in instructions:</iterate>
+
+      <substep n="2a" title="Handle Step Attributes">
+        <check>If optional="true" and NOT #yolo → Ask user to include</check>
+        <check>If if="condition" → Evaluate condition</check>
+        <check>If for-each="item" → Repeat step for each item</check>
+        <check>If repeat="n" → Repeat step n times</check>
+      </substep>
+
+      <substep n="2b" title="Execute Step Content">
+        <action>Process step instructions (markdown or XML tags)</action>
+        <action>Replace {{variables}} with values (ask user if unknown)</action>
+        <execute-tags>
+          <tag><action> → Perform the action</tag>
+          <tag><check> → Evaluate condition</tag>
+          <tag><ask> → Prompt user and WAIT for response</tag>
+          <tag><invoke-workflow> → Execute another workflow with given inputs</tag>
+          <tag><invoke-task> → Execute specified task</tag>
+          <tag><goto step="x"> → Jump to specified step</tag>
+        </execute-tags>
+      </substep>
+
+      <substep n="2c" title="Handle Special Output Tags">
+        <if tag="template-output">
+          <mandate>Generate content for this section</mandate>
+          <mandate>Save to file (Write first time, Edit subsequent)</mandate>
+          <action>Show checkpoint separator: ━━━━━━━━━━━━━━━━━━━━━━━</action>
+          <action>Display generated content</action>
+          <ask>Continue [c] or Edit [e]? WAIT for response</ask>
+        </if>
+
+        <if tag="elicit-required">
+          <mandate critical="true">YOU MUST READ the file at {project-root}/bmad/core/tasks/adv-elicit.md using Read tool BEFORE presenting any elicitation menu</mandate>
+          <action>Load and run task {project-root}/bmad/core/tasks/adv-elicit.md with current context</action>
+          <action>Show elicitation menu 5 relevant options (list 1-5 options, Continue [c] or Reshuffle [r])</action>
+          <mandate>HALT and WAIT for user selection</mandate>
+        </if>
+      </substep>
+
+      <substep n="2d" title="Step Completion">
+        <check>If no special tags and NOT #yolo:</check>
+        <ask>Continue to next step? (y/n/edit)</ask>
+      </substep>
+    </step>
+
+    <step n="3" title="Completion">
+      <check>If checklist exists → Run validation</check>
+      <check>If template: false → Confirm actions completed</check>
+      <check>Else → Confirm document saved to output path</check>
+      <action>Report workflow completion</action>
+    </step>
+  </flow>
+
+  <execution-modes>
+    <mode name="normal">Full user interaction at all decision points</mode>
+    <mode name="#yolo">Skip optional sections, skip all elicitation, minimize prompts</mode>
+  </execution-modes>
+
+  <supported-tags desc="Instructions can use these tags">
+    <structural>
+      <tag>step n="X" goal="..." - Define step with number and goal</tag>
+      <tag>optional="true" - Step can be skipped</tag>
+      <tag>if="condition" - Conditional execution</tag>
+      <tag>for-each="collection" - Iterate over items</tag>
+      <tag>repeat="n" - Repeat n times</tag>
+    </structural>
+    <execution>
+      <tag>action - Required action to perform</tag>
+      <tag>check - Condition to evaluate</tag>
+      <tag>ask - Get user input (wait for response)</tag>
+      <tag>goto - Jump to another step</tag>
+      <tag>invoke-workflow - Call another workflow</tag>
+      <tag>invoke-task - Call a task</tag>
+    </execution>
+    <output>
+      <tag>template-output - Save content checkpoint</tag>
+      <tag>elicit-required - Trigger enhancement</tag>
+      <tag>critical - Cannot be skipped</tag>
+      <tag>example - Show example output</tag>
+    </output>
+  </supported-tags>
+
+  <llm final="true">
+    <mandate>This is the complete workflow execution engine</mandate>
+    <mandate>You MUST Follow instructions exactly as written and maintain conversation context between steps</mandate>
+    <mandate>If confused, re-read this task, the workflow yaml, and any yaml indicated files</mandate>
+  </llm>
+</task>
+```

bmad/core/workflows/bmad-init/instructions.md

@@ -0,0 +1,79 @@
+# BMAD Init - System Initialization Instructions
+
+<workflow>
+
+<step n="1" goal="Welcome and Status Check">
+  <action>Display welcome banner with BMAD branding</action>
+  <action>Check for BMAD installation at {project-root}/bmad</action>
+  <check>If installation found:</check>
+    <action>Display current version from {project-root}/bmad/_cfg/manifest.yaml</action>
+    <action>Show installation date and status</action>
+  <check>If not found:</check>
+    <action>Display warning that BMAD is not installed</action>
+    <action>Suggest running the installer first</action>
+    <action>Exit workflow</action>
+  <action>Display formatted status summary:
+    ╔════════════════════════════════════════╗
+    ║         BMAD INITIALIZATION            ║
+    ╚════════════════════════════════════════╝
+
+    Status: [Installed/Not Found]
+    Location: {project-root}/bmad
+    Version: [from manifest]
+    Installed: [date from manifest]
+
+  </action>
+</step>
+
+<step n="2" goal="Present Initialization Options">
+  <action>Display available initialization and maintenance tasks</action>
+  <ask>Select an initialization task:
+
+    1. Customize Installed Agents and Agent Party (Coming Soon)
+       - Assign new names and personas to agents
+       - Create runtime agent variants
+       - NOTE: This can all be done manually, but doing it through here will be easier and also update the party-mode manifest
+
+    2. Verify Installation (Coming Soon)
+       - Check all files are properly installed
+       - Validate configurations
+
+    3. Exit
+
+    Please select an option (1-3).
+
+  </ask>
+</step>
+
+<step n="3" goal="Process User Selection">
+  <check>If user selected "1":</check>
+    <action>Display message: ⚠️ Installed Agent Auto Customization is coming soon.</action>
+    <<action>Return to step 2</action>
+
+<check>If user selected "2":</check>
+<action>Display message: ⚠️ Installation verification is coming soon.</action>
+<action>Return to step 2</action>
+
+<check>If user selected "3":</check>
+<action>Display message: Exiting BMAD Init. Thank you!</action>
+<goto step="5">Exit workflow</goto>
+</step>
+
+<step n="4" goal="Post-Task Options">
+  <action>Display completion status of the executed task</action>
+  <ask>Task completed successfully!
+
+Would you like to perform another initialization task? (y/n):</ask>
+<check>If user responds "y":</check>
+<goto step="2">Return to menu</goto>
+<check>If user responds "n":</check>
+<goto step="5">Exit workflow</goto>
+</step>
+
+<step n="5" goal="Exit Workflow">
+  <action>Display farewell message</action>
+  <action>Suggest user start a new context or clear context if needed</action>
+  <action>Exit workflow</action>
+</step>
+
+</workflow>

bmad/core/workflows/bmad-init/workflow.yaml

@@ -0,0 +1,14 @@
+# BMAD Init - System Initialization Workflow
+name: "bmad-init"
+description: "BMAD system initialization and maintenance workflow for agent manifest generation and system configuration"
+author: "BMad"
+
+# Critical variables
+config_source: "{project-root}/bmad/_cfg/manifest.yaml"
+date: system-generated
+
+# This is an action workflow - no template output
+template: false
+instructions: "{project-root}/src/core/workflows/bmad-init/instructions.md"
+
+web_bundle: false

bmad/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>

bmad/core/workflows/party-mode/workflow.yaml

@@ -0,0 +1,26 @@
+# 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"
+
+web_bundle: false