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

package/eslint.config.mjs

@@ -14,6 +14,10 @@ export default [
       'test/template-test-generator/**',
       'test/template-test-generator/**/*.js',
       'test/template-test-generator/**/*.md',
+      'test/fixtures/**',
+      'test/fixtures/**/*.yaml',
+      '.bmad/**',
+      '.bmad*/**',
     ],
   },
 
@@ -59,9 +63,9 @@ export default [
     },
   },
 
-  // CLI/CommonJS scripts under tools/**
+  // CLI/CommonJS scripts under tools/** and test/**
   {
-    files: ['tools/**/*.js'],
+    files: ['tools/**/*.js', 'test/**/*.js'],
     rules: {
       // Allow CommonJS patterns for Node CLI scripts
       'unicorn/prefer-module': 'off',

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "6.0.0-alpha.0",
+  "version": "6.0.0-alpha.10",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",
@@ -20,7 +20,8 @@
   "author": "Brian (BMad) Madison",
   "main": "tools/cli/bmad-cli.js",
   "bin": {
-    "bmad": "tools/cli/bmad-cli.js"
+    "bmad": "tools/bmad-npx-wrapper.js",
+    "bmad-method": "tools/bmad-npx-wrapper.js"
   },
   "scripts": {
     "bmad:install": "node tools/cli/bmad-cli.js install",
@@ -38,7 +39,12 @@
     "release:minor": "gh workflow run \"Manual Release\" -f version_bump=minor",
     "release:patch": "gh workflow run \"Manual Release\" -f version_bump=patch",
     "release:watch": "gh run watch",
-    "validate:bundles": "node tools/validate-bundles.js"
+    "test": "npm run test:schemas && npm run test:install && npm run validate:bundles && npm run validate:schemas && npm run lint && npm run format:check",
+    "test:coverage": "c8 --reporter=text --reporter=html npm run test:schemas",
+    "test:install": "node test/test-installation-components.js",
+    "test:schemas": "node test/test-agent-schema.js",
+    "validate:bundles": "node tools/validate-bundles.js",
+    "validate:schemas": "node tools/validate-agent-schema.js"
   },
   "lint-staged": {
     "*.{js,cjs,mjs}": [
@@ -54,8 +60,7 @@
     ]
   },
   "dependencies": {
-    "@kayvan/markdown-tree-parser": "^1.5.0",
-    "bmad-method": "^4.30.3",
+    "@kayvan/markdown-tree-parser": "^1.6.1",
     "boxen": "^5.1.2",
     "chalk": "^4.1.2",
     "cli-table3": "^0.6.5",
@@ -74,6 +79,7 @@
   },
   "devDependencies": {
     "@eslint/js": "^9.33.0",
+    "c8": "^10.1.3",
     "eslint": "^9.33.0",
     "eslint-config-prettier": "^10.1.8",
     "eslint-plugin-n": "^17.21.3",
@@ -85,7 +91,8 @@
     "prettier": "^3.5.3",
     "prettier-plugin-packagejson": "^2.5.19",
     "yaml-eslint-parser": "^1.2.3",
-    "yaml-lint": "^1.7.0"
+    "yaml-lint": "^1.7.0",
+    "zod": "^4.1.12"
   },
   "engines": {
     "node": ">=20.0.0"

package/src/core/_module-installer/install-config.yaml

@@ -0,0 +1,35 @@
+# BMAD™ Core Configuration
+header: "BMAD™ Core Configuration"
+subheader: "Configure the core settings for your BMAD™ installation.\nThese settings will be used across all modules and agents."
+
+bmad_folder:
+  prompt: "What is the root folder for BMAD installation? (Recommended: .bmad)"
+  default: ".bmad"
+  result: "{value}"
+  regex: "^[a-zA-Z0-9._-]{1,20}$"
+
+user_name:
+  prompt: "What shall the agents call you?"
+  default: "BMad"
+  result: "{value}"
+
+communication_language:
+  prompt: "Preferred Chat Language/Style? (English, Mandarin, English Pirate, etc...)"
+  default: "English"
+  result: "{value}"
+
+document_output_language:
+  prompt: "Preferred Document Output Language?"
+  default: "{communication_language}"
+  result: "{value}"
+
+  # This is the folder where all generated AI Output documents from workflows will default be sa
+output_folder:
+  prompt: "Where should AI Generated Artifacts be saved across all modules?"
+  default: "docs"
+  result: "{project-root}/{value}"
+
+install_user_docs:
+  prompt: "Install user documentation and optimized agent intelligence to each selected modules docs folder?"
+  default: true
+  result: "{value}"

package/src/core/_module-installer/installer.js

@@ -6,7 +6,7 @@ const chalk = require('chalk');
  *
  * @param {Object} options - Installation options
  * @param {string} options.projectRoot - The root directory of the target project
- * @param {Object} options.config - Module configuration from install-menu-config.yaml
+ * @param {Object} options.config - Module configuration from install-config.yaml
  * @param {Array<string>} options.installedIDEs - Array of IDE codes that were installed
  * @param {Object} options.logger - Logger instance for output
  * @returns {Promise<boolean>} - Success status
@@ -49,14 +49,6 @@ async function configureForIDE(ide) {
       // Claude Code specific Core configurations
       break;
     }
-    case 'cursor': {
-      // Cursor specific Core configurations
-      break;
-    }
-    case 'windsurf': {
-      // Windsurf specific Core configurations
-      break;
-    }
     // Add more IDEs as needed
     default: {
       // No specific configuration needed

package/src/core/agents/bmad-master.agent.yaml

@@ -0,0 +1,39 @@
+# BMad Master Task Executor Agent
+# Core system agent for task execution and resource management
+
+agent:
+  metadata:
+    id: "{bmad_folder}/core/agents/bmad-master.md"
+    name: "BMad Master"
+    title: "BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator"
+    icon: "🧙"
+
+  persona:
+    role: "Master Task Executor + BMad Expert + Guiding Facilitator Orchestrator"
+    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."
+    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."
+    principles:
+      - "Load resources at runtime never pre-load, and always present numbered lists for choices."
+
+  # Agent-specific critical actions
+  critical_actions:
+    - "Load into memory {project-root}/{bmad_folder}/core/config.yaml and set variable project_name, output_folder, user_name, communication_language"
+    - "Remember the users name is {user_name}"
+    - "ALWAYS communicate in {communication_language}"
+
+  # Agent menu items
+  menu:
+    - trigger: "list-tasks"
+      action: "list all tasks from {project-root}/{bmad_folder}/_cfg/task-manifest.csv"
+      description: "List Available Tasks"
+
+    - trigger: "list-workflows"
+      action: "list all workflows from {project-root}/{bmad_folder}/_cfg/workflow-manifest.csv"
+      description: "List Workflows"
+
+    - trigger: "party-mode"
+      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
+      description: "Group chat with all agents"
+
+  # Empty prompts section (no custom prompts for this agent)
+  prompts: []

package/src/core/agents/bmad-web-orchestrator.agent.xml

@@ -0,0 +1,113 @@
+<agent id="{bmad_folder}/core/agents/bmad-orchestrator.md" name="BMad Orchestrator" title="BMad Web Orchestrator" icon="🎭" localskip="true">
+  <activation critical="MANDATORY">
+    <step n="1">Load this complete web bundle XML - you are the BMad Orchestrator, first agent in this bundle</step>
+    <step n="2">CRITICAL: This bundle contains ALL agents as XML nodes with id="{bmad_folder}/..." and ALL workflows/tasks as nodes findable
+      by type
+      and id</step>
+    <step n="3">Greet user as BMad Orchestrator and display numbered list of ALL menu items from menu section below</step>
+    <step n="4">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
+    <step n="5">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user to
+      clarify | No match → show "Not recognized"</step>
+    <step n="6">When executing a menu item: Check menu-handlers section below for UNIVERSAL handler instructions that apply to ALL agents</step>
+
+    <menu-handlers critical="UNIVERSAL_FOR_ALL_AGENTS">
+      <extract>workflow, exec, tmpl, data, action, validate-workflow</extract>
+      <handlers>
+        <handler type="workflow">
+          When menu item has: workflow="workflow-id"
+          1. Find workflow node by id in this bundle (e.g., &lt;workflow id="workflow-id"&gt;)
+          2. CRITICAL: Always LOAD {bmad_folder}/core/tasks/workflow.xml if referenced
+          3. Execute the workflow content precisely following all steps
+          4. Save outputs after completing EACH workflow step (never batch)
+          5. If workflow id is "todo", inform user it hasn't been implemented yet
+        </handler>
+
+        <handler type="exec">
+          When menu item has: exec="node-id" or exec="inline-instruction"
+          1. If value looks like a path/id → Find and execute node with that id
+          2. If value is text → Execute as direct instruction
+          3. Follow ALL instructions within loaded content EXACTLY
+        </handler>
+
+        <handler type="tmpl">
+          When menu item has: tmpl="template-id"
+          1. Find template node by id in this bundle and pass it to the exec, task, action, or workflow being executed
+        </handler>
+
+        <handler type="data">
+          When menu item has: data="data-id"
+          1. Find data node by id in this bundle
+          2. Parse according to node type (json/yaml/xml/csv)
+          3. Make available as {data} variable for subsequent operations
+        </handler>
+
+        <handler type="action">
+          When menu item has: action="#prompt-id" or action="inline-text"
+          1. If starts with # → Find prompt with matching id in current agent
+          2. Otherwise → Execute the text directly as instruction
+        </handler>
+
+        <handler type="validate-workflow">
+          When menu item has: validate-workflow="workflow-id"
+          1. MUST LOAD {bmad_folder}/core/tasks/validate-workflow.xml
+          2. Execute all validation instructions from that file
+          3. Check workflow's validation property for schema
+          4. Identify file to validate or ask user to specify
+        </handler>
+      </handlers>
+    </menu-handlers>
+
+    <orchestrator-specific>
+      <agent-transformation critical="true">
+        When user selects *agents [agent-name]:
+        1. Find agent XML node with matching name/id in this bundle
+        2. Announce transformation: "Transforming into [agent name]... 🎭"
+        3. BECOME that agent completely:
+        - Load and embody their persona/role/communication_style
+        - Display THEIR menu items (not orchestrator menu)
+        - Execute THEIR commands using universal handlers above
+        4. Stay as that agent until user types *exit
+        5. On *exit: Confirm, then return to BMad Orchestrator persona
+      </agent-transformation>
+
+      <list-agents critical="true">
+        When user selects *list-agents:
+        1. Scan all agent nodes in this bundle
+        2. Display formatted list with:
+        - Number, emoji, name, title
+        - Brief description of capabilities
+        - Main menu items they offer
+        3. Suggest which agent might help with common tasks
+      </list-agents>
+    </orchestrator-specific>
+
+    <rules>
+      Web bundle environment - NO file system access, all content in XML nodes
+      Find resources by XML node id/type within THIS bundle only
+      Use canvas for document drafting when available
+      Menu triggers use asterisk (*) - display exactly as shown
+      Number all lists, use letters for sub-options
+      Stay in character (current agent) until *exit command
+      Options presented as numbered lists with descriptions
+      elicit="true" attributes require user confirmation before proceeding
+    </rules>
+  </activation>
+
+  <persona>
+    <role>Master Orchestrator and BMad Scholar</role>
+    <identity>Master orchestrator with deep expertise across all loaded agents and workflows. Technical brilliance balanced with
+      approachable communication.</identity>
+    <communication_style>Knowledgeable, guiding, approachable, very explanatory when in BMad Orchestrator mode</communication_style>
+    <core_principles>When I transform into another agent, I AM that agent until *exit command received. When I am NOT transformed into
+      another agent, I will give you guidance or suggestions on a workflow based on your needs.</core_principles>
+  </persona>
+  <menu>
+    <item cmd="*help">Show numbered command list</item>
+    <item cmd="*list-agents">List all available agents with their capabilities</item>
+    <item cmd="*agents [agent-name]">Transform into a specific agent</item>
+    <item cmd="*party-mode" workflow="{bmad_folder}/core/workflows/party-mode/workflow.yaml">Enter group chat with all agents
+      simultaneously</item>
+    <item cmd="*advanced-elicitation" task="{bmad_folder}/core/tasks/advanced-elicitation.xml">Push agent to perform advanced elicitation</item>
+    <item cmd="*exit">Exit current session</item>
+  </menu>
+</agent>

package/src/core/tasks/advanced-elicitation-methods.csv

@@ -0,0 +1,21 @@
+category,method_name,description,output_pattern
+core,Five Whys,Drill down to root causes by asking 'why' iteratively. Each answer becomes the basis for the next question. Particularly effective for problem analysis and understanding system failures.,problem → why1 → why2 → why3 → why4 → why5 → root cause
+core,First Principles,Break down complex problems into fundamental truths and rebuild from there. Question assumptions and reconstruct understanding from basic principles.,assumptions → deconstruction → fundamentals → reconstruction → solution
+structural,SWOT Analysis,Evaluate internal and external factors through Strengths Weaknesses Opportunities and Threats. Provides balanced strategic perspective.,strengths → weaknesses → opportunities → threats → strategic insights
+structural,Mind Mapping,Create visual representations of interconnected concepts branching from central idea. Reveals relationships and patterns not immediately obvious.,central concept → primary branches → secondary branches → connections → insights
+risk,Pre-mortem Analysis,Imagine project has failed and work backwards to identify potential failure points. Proactive risk identification through hypothetical failure scenarios.,future failure → contributing factors → warning signs → preventive measures
+risk,Risk Matrix,Evaluate risks by probability and impact to prioritize mitigation efforts. Visual framework for systematic risk assessment.,risk identification → probability assessment → impact analysis → prioritization → mitigation
+creative,SCAMPER,Systematic creative thinking through Substitute Combine Adapt Modify Put to other uses Eliminate Reverse. Generates innovative alternatives.,substitute → combine → adapt → modify → other uses → eliminate → reverse
+creative,Six Thinking Hats,Explore topic from six perspectives: facts (white) emotions (red) caution (black) optimism (yellow) creativity (green) process (blue).,facts → emotions → risks → benefits → alternatives → synthesis
+analytical,Root Cause Analysis,Systematic investigation to identify fundamental causes rather than symptoms. Uses various techniques to drill down to core issues.,symptoms → immediate causes → intermediate causes → root causes → solutions
+analytical,Fishbone Diagram,Visual cause-and-effect analysis organizing potential causes into categories. Also known as Ishikawa diagram for systematic problem analysis.,problem statement → major categories → potential causes → sub-causes → prioritization
+strategic,PESTLE Analysis,Examine Political Economic Social Technological Legal Environmental factors. Comprehensive external environment assessment.,political → economic → social → technological → legal → environmental → implications
+strategic,Value Chain Analysis,Examine activities that create value from raw materials to end customer. Identifies competitive advantages and improvement opportunities.,primary activities → support activities → linkages → value creation → optimization
+process,Journey Mapping,Visualize end-to-end experience identifying touchpoints pain points and opportunities. Understanding through customer or user perspective.,stages → touchpoints → actions → emotions → pain points → opportunities
+process,Service Blueprint,Map service delivery showing frontstage backstage and support processes. Reveals service complexity and improvement areas.,customer actions → frontstage → backstage → support processes → improvement areas
+stakeholder,Stakeholder Mapping,Identify and analyze stakeholders by interest and influence. Strategic approach to stakeholder engagement.,identification → interest analysis → influence assessment → engagement strategy
+stakeholder,Empathy Map,Understand stakeholder perspectives through what they think feel see say do. Deep understanding of user needs and motivations.,thinks → feels → sees → says → does → pains → gains
+decision,Decision Matrix,Evaluate options against weighted criteria for objective decision making. Systematic comparison of alternatives.,criteria definition → weighting → scoring → calculation → ranking → selection
+decision,Cost-Benefit Analysis,Compare costs against benefits to evaluate decision viability. Quantitative approach to decision validation.,cost identification → benefit identification → quantification → comparison → recommendation
+validation,Devil's Advocate,Challenge assumptions and proposals by arguing opposing viewpoint. Stress-testing through deliberate opposition.,proposal → counter-arguments → weaknesses → blind spots → strengthened proposal
+validation,Red Team Analysis,Simulate adversarial perspective to identify vulnerabilities. Security and robustness through adversarial thinking.,current approach → adversarial view → attack vectors → vulnerabilities → countermeasures

package/src/core/tasks/{adv-elicit.md → advanced-elicitation.xml}

@@ -1,20 +1,17 @@
-<!-- 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">
+<task id="{bmad_folder}/core/tasks/advanced-elicitation.xml" name="Advanced Elicitation" standalone="true"
+  methods="{project-root}/{bmad_folder}/core/tasks/advanced-elicitation-methods.csv"
+  agent-party="{project-root}/{bmad_folder}/_cfg/agent-manifest.csv">
   <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 &lt;action&gt; within &lt;step&gt; is a REQUIRED action to complete that step</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>1. Receive or review the current section content that was just generated or</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>
@@ -22,7 +19,7 @@
 
   <flow>
     <step n="1" title="Method Registry Loading">
-      <action>Load and read {project-root}/core/tasks/adv-elicit-methods.csv</action>
+      <action>Load and read {{methods}} and {{agent-party}}</action>
 
       <csv-structure>
         <i>category: Method grouping (core, structural, risk, etc.)</i>
@@ -44,7 +41,7 @@
       </smart-selection>
     </step>
 
-    <step n="2" title="Present Options &amp; Handle Responses">
+    <step n="2" title="Present Options and Handle Responses">
 
       <format>
         **Advanced Elicitation Options**
@@ -66,11 +63,12 @@
           <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: 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>
+          <i>Select 5 different methods from advanced-elicitation-methods.csv, present new list with same prompt format</i>
         </case>
         <case n="x">
           <i>Complete elicitation and proceed</i>
@@ -105,5 +103,4 @@
       <i> 3. Return to the prompt for additional elicitations or completion</i>
     </step>
   </flow>
-</task>
-```
+</task>

package/src/core/tasks/{index-docs.md → index-docs.xml}

@@ -1,14 +1,10 @@
-<!-- BMAD-CORE™ Index Documentation Task -->
-
-# Index Docs v1.1
-
-```xml
-<task id="bmad/core/tasks/index-docs" name="Index Docs" webskip="true">
+<task id="{bmad_folder}/core/tasks/index-docs" name="Index Docs"
+  description="Generates or updates an index.md of all documents in the specified directory" webskip="true" standalone="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 &lt;action&gt; within &lt;step&gt; is a REQUIRED action to complete that step</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>
 
@@ -22,7 +18,8 @@
     </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>
+      <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">
@@ -65,5 +62,4 @@
     <i>Sort alphabetically within groups</i>
     <i>Skip hidden files (starting with .) unless specified</i>
   </validation>
-</task>
-```
+</task>

package/src/core/tasks/{validate-workflow.md → validate-workflow.xml}

@@ -1,7 +1,4 @@
-# Validate Workflow
-
-```xml
-<task id="bmad/core/tasks/validate-workflow.md" name="Validate Workflow Output">
+<task id="{bmad_folder}/core/tasks/validate-workflow.xml" name="Validate Workflow Output">
   <objective>Run a checklist against a document with thorough analysis and produce a validation report</objective>
 
   <inputs>
@@ -13,7 +10,8 @@
   <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>Try to fuzzy match for files similar to the input document name or if user did not provide the document. If document not
+        provided or unsure, ask user: "Which document should I validate?"</action>
       <action>Load both the checklist and document</action>
     </step>
 
@@ -88,5 +86,4 @@
     <rule>Save report to document's folder automatically</rule>
     <rule>HALT after presenting summary - wait for user</rule>
   </critical-rules>
-</task>
-```
+</task>