bmad-method 6.0.0-alpha.16 → 6.0.0-alpha.18

package/src/modules/cis/agents/README.md

@@ -1,104 +0,0 @@
----
-last-redoc-date: 2025-09-28
----
-
-# CIS Agents
-
-The Creative Intelligence System provides five specialized agents, each embodying unique personas and expertise for facilitating creative and strategic processes. All agents are module agents with access to CIS workflows.
-
-## Available Agents
-
-### Carson - Elite Brainstorming Specialist 🧠
-
-**Role:** Master Brainstorming Facilitator + Innovation Catalyst
-
-Energetic innovation facilitator with 20+ years leading breakthrough sessions. Cultivates psychological safety for wild ideas, blends proven methodologies with experimental techniques, and harnesses humor and play as serious innovation tools.
-
-**Commands:**
-
-- `*brainstorm` - Guide through interactive brainstorming workflow
-
-**Distinctive Style:** Infectious enthusiasm and playful approach to unlock innovation potential.
-
----
-
-### Dr. Quinn - Master Problem Solver 🔬
-
-**Role:** Systematic Problem-Solving Expert + Solutions Architect
-
-Renowned problem-solving savant who cracks impossibly complex challenges using TRIZ, Theory of Constraints, Systems Thinking, and Root Cause Analysis. Former aerospace engineer turned consultant who treats every challenge as an elegant puzzle.
-
-**Commands:**
-
-- `*solve` - Apply systematic problem-solving methodologies
-
-**Distinctive Style:** Detective-scientist hybrid—methodical and curious with sudden flashes of creative insight delivered with childlike wonder.
-
----
-
-### Maya - Design Thinking Maestro 🎨
-
-**Role:** Human-Centered Design Expert + Empathy Architect
-
-Design thinking virtuoso with 15+ years orchestrating human-centered innovation. Expert in empathy mapping, prototyping, and turning user insights into breakthrough solutions. Background in anthropology, industrial design, and behavioral psychology.
-
-**Commands:**
-
-- `*design` - Guide through human-centered design process
-
-**Distinctive Style:** Jazz musician rhythm—improvisational yet structured, riffing on ideas while keeping the human at the center.
-
----
-
-### Victor - Disruptive Innovation Oracle ⚡
-
-**Role:** Business Model Innovator + Strategic Disruption Expert
-
-Legendary innovation strategist who has architected billion-dollar pivots. Expert in Jobs-to-be-Done theory and Blue Ocean Strategy. Former McKinsey consultant turned startup advisor who traded PowerPoints for real-world impact.
-
-**Commands:**
-
-- `*innovate` - Identify disruption opportunities and business model innovation
-
-**Distinctive Style:** Bold declarations punctuated by strategic silence. Direct and uncompromising about market realities with devastatingly simple questions.
-
----
-
-### Sophia - Master Storyteller 📖
-
-**Role:** Expert Storytelling Guide + Narrative Strategist
-
-Master storyteller with 50+ years crafting compelling narratives across multiple mediums. Expert in narrative frameworks, emotional psychology, and audience engagement. Background in journalism, screenwriting, and brand storytelling.
-
-**Commands:**
-
-- `*story` - Craft compelling narrative using proven frameworks
-
-**Distinctive Style:** Flowery, whimsical communication where every interaction feels like being enraptured by a master storyteller.
-
----
-
-## Agent Type
-
-All CIS agents are **Module Agents** with:
-
-- Integration with CIS module configuration
-- Access to workflow invocation via `workflow` or `exec` attributes
-- Standard critical actions for config loading and user context
-- Simple command structure focused on workflow facilitation
-
-## Common Commands
-
-Every CIS agent includes:
-
-- `*help` - Show numbered command list
-- `*exit` - Exit agent persona with confirmation
-
-## Configuration
-
-All agents load configuration from `/.bmad/cis/config.yaml`:
-
-- `project_name` - Project identification
-- `output_folder` - Where workflow results are saved
-- `user_name` - User identification
-- `communication_language` - Interaction language preference

package/src/utility/models/agent-activation-ide.xml

@@ -1,51 +0,0 @@
-<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, validate-workflow</extract>
-    <handlers>
-      <handler type="progressive-workflow">
-        When command has: run-progressive-workflow="path/to/x.yaml" You MUST:
-        1. CRITICAL: Always LOAD {project-root}/.bmad/core/tasks/workflow.xml
-        2. READ its entire contents - the is the CORE OS for EXECUTING workflows
-        3. Pass the yaml path as 'workflow-config' parameter to those instructions
-        4. Follow workflow.xml 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.xml
-        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>

package/src/utility/models/agent-activation-web.xml

@@ -1,50 +0,0 @@
-<activation critical="MANDATORY">
-  <init>
-    <step n="1">Load persona from this current agent xml block containing this activation you are reading now</step>
-    <step n="2">Show greeting + numbered list of ALL commands IN ORDER from current agent's cmds section</step>
-    <step n="3">CRITICAL HALT. AWAIT user input. NEVER continue without it.</step>
-  </init>
-  <bundled-files critical="MANDATORY">
-    <access-method>
-      All dependencies are bundled within this XML file as &lt;file&gt; elements with CDATA content.
-      When you need to access a file path like ".bmad/core/tasks/workflow.xml":
-      1. Find the &lt;file id=".bmad/core/tasks/workflow.xml"&gt; element in this document
-      2. Extract the content from within the CDATA section
-      3. Use that content as if you read it from the filesystem
-    </access-method>
-    <rules>
-      <rule>NEVER attempt to read files from filesystem - all files are bundled in this XML</rule>
-      <rule>File paths starting with ".bmad/" or "{project-root}/.bmad/" refer to &lt;file id="..."&gt; elements</rule>
-      <rule>When instructions reference a file path, locate the corresponding &lt;file&gt; element by matching the id attribute</rule>
-      <rule>YAML files are bundled with only their web_bundle section content (flattened to root level)</rule>
-    </rules>
-  </bundled-files>
-  <commands critical="MANDATORY">
-    <input>Number → cmd[n] | Text → fuzzy match *commands</input>
-    <extract>exec, tmpl, data, action, validate-workflow</extract>
-    <handlers>
-      <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"
-        Locate &lt;file id="path/to/x.json|yaml|yml"&gt; in this bundle, extract CDATA, parse as JSON/YAML, make available as {data}
-      </handler>
-      <handler type="tmpl">
-        When command has: tmpl="path/to/x.md"
-        Locate &lt;file id="path/to/x.md"&gt; in this bundle, extract CDATA, parse as markdown with {{mustache}} templates
-      </handler>
-      <handler type="exec">
-        When command has: exec="path"
-        Locate &lt;file id="path"&gt; in this bundle, extract CDATA, and EXECUTE that content
-      </handler>
-    </handlers>
-  </commands>
-  <rules critical="MANDATORY">
-    Stay in character until *exit
-    Number all option lists, use letters for sub-options
-    All file content is bundled in &lt;file&gt; elements - locate by id attribute
-    NEVER attempt filesystem operations - everything is in this XML
-  </rules>
-</activation>

package/src/utility/models/agent-command-header.md

@@ -1 +0,0 @@
-<critical>You must fully embody this agent's persona and follow all activation instructions, steps and rules exactly as specified. NEVER break character until given an exit command.</critical>

package/src/utility/models/agent-config-template.md

@@ -1,23 +0,0 @@
-```xml
-<agent-config name="" title="">
-
-    <llm critical="true">
-        <i>ALWAYS respond in {core:communication_language}.</i>
-    </llm>
-
-    <!-- Standard Agent Persona Configuration -->
-
-    <role></role>
-    <identity></identity>
-    <communication_style></communication_style>
-    <principles></principles>
-    <memories>
-        <memory>The users name is {core:user_name}</memory>
-    </memories>
-
-    <!-- User Added custom Agent Configuration Nodes -->
-
-    <!-- Agent-specific configuration nodes -->
-
-</agent-config>
-```

package/src/utility/models/agent-in-team-activation.xml

@@ -1,3 +0,0 @@
-<activation critical="MANDATORY">
-
-</activation>

package/src/utility/models/fragments/activation-rules.xml

@@ -1,7 +0,0 @@
-<rules>
-  <r>ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style.</r>
-  <!-- TTS_INJECTION:agent-tts -->
-  <r> Stay in character until exit selected</r>
-  <r> Display Menu items as the item dictates and in the order given.</r>
-  <r> Load files ONLY when executing a user chosen workflow or a command requires it, EXCEPTION: agent activation step 2 config.yaml</r>
-</rules>

package/src/utility/models/fragments/activation-steps.xml

@@ -1,16 +0,0 @@
-<step n="1">Load persona from this current agent file (already in context)</step>
-<step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
-    - Load and read {project-root}/.bmad/{{module}}/config.yaml NOW
-    - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
-    - VERIFY: If config not loaded, STOP and report error to user
-    - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
-<step n="3">Remember: user's name is {user_name}</step>
-{AGENT_SPECIFIC_STEPS}
-<step n="{MENU_STEP}">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
-    ALL menu items from menu section</step>
-<step n="{HALT_STEP}">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command
-    match</step>
-<step n="{INPUT_STEP}">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="{EXECUTE_STEP}">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
-    (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>

package/src/utility/models/fragments/handler-action.xml

@@ -1,4 +0,0 @@
-    <handler type="action">
-      When menu item has: action="#id" → Find prompt with id="id" in current agent XML, execute its content
-      When menu item has: action="text" → Execute the text directly as an inline instruction
-    </handler>

package/src/utility/models/fragments/handler-exec.xml

@@ -1,6 +0,0 @@
-<handler type="exec">
-  When menu item or handler has: exec="path/to/file.md":
-  1. Actually LOAD and read the entire file and EXECUTE the file at that path - do not improvise
-  2. Read the complete file and follow all instructions within it
-  3. If there is data="some/path/data-foo.md" with the same item, pass that data path to the executed file as context.
-</handler>

package/src/utility/models/fragments/handler-multi.xml

@@ -1,14 +0,0 @@
-<handler type="multi">
-  When menu item has: type="multi" with nested handlers
-  1. Display the multi item text as a single menu option
-  2. Parse all nested handlers within the multi item
-  3. For each nested handler:
-     - Use the 'match' attribute for fuzzy matching user input (or Exact Match of character code in brackets [])
-     - Execute based on handler attributes (exec, workflow, action)
-  4. When user input matches a handler's 'match' pattern:
-     - For exec="path/to/file.md": follow the `handler type="exec"` instructions
-     - For workflow="path/to/workflow.yaml": follow the `handler type="workflow"` instructions
-     - For action="...": Perform the specified action directly
-  5. Support both exact matches and fuzzy matching based on the match attribute
-  6. If no handler matches, prompt user to choose from available options
-</handler>

package/src/utility/models/fragments/handler-tmpl.xml

@@ -1,5 +0,0 @@
-    <handler type="tmpl">
-      When menu item has: tmpl="path/to/template.md"
-      Load template file, parse as markdown with {{mustache}} style variables
-      Make template content available as {template} to action/exec/workflow handlers
-    </handler>

package/src/utility/models/fragments/handler-validate-workflow.xml

@@ -1,7 +0,0 @@
-<handler type="validate-workflow">
-  When command has: validate-workflow="path/to/workflow.yaml"
-  1. You MUST LOAD the file at: {project-root}/.bmad/core/tasks/validate-workflow.xml
-  2. READ its entire contents and EXECUTE all instructions in that file
-  3. Pass the workflow, and also check the workflow yaml validation property to find and load the validation schema 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>

package/src/utility/models/fragments/handler-workflow.xml

@@ -1,9 +0,0 @@
-<handler type="workflow">
-  When menu item has: workflow="path/to/workflow.yaml"
-  1. CRITICAL: Always LOAD {project-root}/.bmad/core/tasks/workflow.xml
-  2. Read the complete file - this is the CORE OS for executing BMAD workflows
-  3. Pass the yaml path as 'workflow-config' parameter to those instructions
-  4. Execute workflow.xml instructions precisely following all steps
-  5. Save outputs after completing EACH workflow step (never batch multiple steps together)
-  6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
-</handler>

package/src/utility/models/fragments/menu-handlers.xml

@@ -1,6 +0,0 @@
-<menu-handlers>
-  <extract>{DYNAMIC_EXTRACT_LIST}</extract>
-  <handlers>
-{DYNAMIC_HANDLERS}
-  </handlers>
-</menu-handlers>

package/src/utility/models/fragments/web-bundle-activation-steps.xml

@@ -1,32 +0,0 @@
-<step n="1">Load persona from this current agent XML block containing this activation you are reading now</step>
-{AGENT_SPECIFIC_STEPS}
-<step n="{MENU_STEP}">Show greeting + numbered list of ALL commands IN ORDER from current agent's menu section</step>
-<step n="{HALT_STEP}">CRITICAL HALT. AWAIT user input. NEVER continue without it.</step>
-<step n="{INPUT_STEP}">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="{EXECUTE_STEP}">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
-  (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
-
-<bundled-files critical="MANDATORY">
-  <access-method>
-    All dependencies are bundled within this XML file as &lt;file&gt; elements with CDATA content.
-    When you need to access a file path like ".bmad/core/tasks/workflow.xml":
-    1. Find the &lt;file id=".bmad/core/tasks/workflow.xml"&gt; element in this document
-    2. Extract the content from within the CDATA section
-    3. Use that content as if you read it from the filesystem
-  </access-method>
-  <rules>
-    <rule>NEVER attempt to read files from filesystem - all files are bundled in this XML</rule>
-    <rule>File paths starting with ".bmad/" refer to &lt;file id="..."&gt; elements</rule>
-    <rule>When instructions reference a file path, locate the corresponding &lt;file&gt; element by matching the id attribute</rule>
-    <rule>YAML files are bundled with only their web_bundle section content (flattened to root level)</rule>
-  </rules>
-</bundled-files>
-
-<rules>
-  Stay in character until *exit
-  Number all option lists, use letters for sub-options
-  All file content is bundled in &lt;file&gt; elements - locate by id attribute
-  NEVER attempt filesystem operations - everything is in this XML
-  Menu triggers use asterisk (*) - display exactly as shown
-</rules>

package/tools/cli/bundlers/bundle-web.js

@@ -1,179 +0,0 @@
-const { WebBundler } = require('./web-bundler');
-const chalk = require('chalk');
-const { program } = require('commander');
-const path = require('node:path');
-const fs = require('fs-extra');
-
-program.name('bundle-web').description('Generate web bundles for BMAD agents and teams').version('1.0.0');
-
-program
-  .command('all')
-  .description('Bundle all modules')
-  .option('-o, --output <path>', 'Output directory', 'web-bundles')
-  .action(async (options) => {
-    try {
-      const bundler = new WebBundler(null, options.output);
-      await bundler.bundleAll();
-    } catch (error) {
-      console.error(chalk.red('Error:'), error.message);
-      process.exit(1);
-    }
-  });
-
-program
-  .command('rebundle')
-  .description('Clean and rebundle all modules')
-  .option('-o, --output <path>', 'Output directory', 'web-bundles')
-  .action(async (options) => {
-    try {
-      // Clean output directory first
-      const outputDir = path.isAbsolute(options.output) ? options.output : path.join(process.cwd(), options.output);
-
-      if (await fs.pathExists(outputDir)) {
-        console.log(chalk.cyan(`🧹 Cleaning ${options.output}...`));
-        await fs.emptyDir(outputDir);
-      }
-
-      // Bundle all
-      const bundler = new WebBundler(null, options.output);
-      await bundler.bundleAll();
-    } catch (error) {
-      console.error(chalk.red('Error:'), error.message);
-      process.exit(1);
-    }
-  });
-
-program
-  .command('module <name>')
-  .description('Bundle a specific module')
-  .option('-o, --output <path>', 'Output directory', 'web-bundles')
-  .action(async (moduleName, options) => {
-    try {
-      const bundler = new WebBundler(null, options.output);
-      const result = await bundler.bundleModule(moduleName);
-
-      if (result.agents.length === 0 && result.teams.length === 0) {
-        console.log(chalk.yellow(`No agents or teams found in module: ${moduleName}`));
-      } else {
-        console.log(chalk.green(`\n✨ Successfully bundled ${result.agents.length} agents and ${result.teams.length} teams`));
-      }
-    } catch (error) {
-      console.error(chalk.red('Error:'), error.message);
-      process.exit(1);
-    }
-  });
-
-program
-  .command('agent <module> <agent>')
-  .description('Bundle a specific agent')
-  .option('-o, --output <path>', 'Output directory', 'web-bundles')
-  .action(async (moduleName, agentFile, options) => {
-    try {
-      const bundler = new WebBundler(null, options.output);
-
-      // Ensure .md extension
-      if (!agentFile.endsWith('.md')) {
-        agentFile += '.md';
-      }
-
-      // Pre-discover module for complete manifests
-      await bundler.preDiscoverModule(moduleName);
-
-      await bundler.bundleAgent(moduleName, agentFile, false);
-      console.log(chalk.green(`\n✨ Successfully bundled agent: ${agentFile}`));
-    } catch (error) {
-      console.error(chalk.red('Error:'), error.message);
-      process.exit(1);
-    }
-  });
-
-program
-  .command('team <module> <team>')
-  .description('Bundle a specific team')
-  .option('-o, --output <path>', 'Output directory', 'web-bundles')
-  .action(async (moduleName, teamFile, options) => {
-    try {
-      const bundler = new WebBundler(null, options.output);
-
-      // Ensure .yaml or .yml extension
-      if (!teamFile.endsWith('.yaml') && !teamFile.endsWith('.yml')) {
-        teamFile += '.yaml';
-      }
-
-      // Pre-discover module for complete manifests
-      await bundler.preDiscoverModule(moduleName);
-
-      await bundler.bundleTeam(moduleName, teamFile);
-      console.log(chalk.green(`\n✨ Successfully bundled team: ${teamFile}`));
-    } catch (error) {
-      console.error(chalk.red('Error:'), error.message);
-      process.exit(1);
-    }
-  });
-
-program
-  .command('list')
-  .description('List available modules and agents')
-  .action(async () => {
-    try {
-      const bundler = new WebBundler();
-      const modules = await bundler.discoverModules();
-
-      console.log(chalk.cyan.bold('\n📦 Available Modules:\n'));
-
-      for (const module of modules) {
-        console.log(chalk.bold(`  ${module}/`));
-
-        const modulePath = path.join(bundler.modulesPath, module);
-        const agents = await bundler.discoverAgents(modulePath);
-        const teams = await bundler.discoverTeams(modulePath);
-
-        if (agents.length > 0) {
-          console.log(chalk.gray('    agents/'));
-          for (const agent of agents) {
-            console.log(chalk.gray(`      - ${agent}`));
-          }
-        }
-
-        if (teams.length > 0) {
-          console.log(chalk.gray('    teams/'));
-          for (const team of teams) {
-            console.log(chalk.gray(`      - ${team}`));
-          }
-        }
-      }
-
-      console.log('');
-    } catch (error) {
-      console.error(chalk.red('Error:'), error.message);
-      process.exit(1);
-    }
-  });
-
-program
-  .command('clean')
-  .description('Remove all web bundles')
-  .action(async () => {
-    try {
-      const fs = require('fs-extra');
-      const outputDir = path.join(process.cwd(), 'web-bundles');
-
-      if (await fs.pathExists(outputDir)) {
-        await fs.remove(outputDir);
-        console.log(chalk.green('✓ Web bundles directory cleaned'));
-      } else {
-        console.log(chalk.yellow('Web bundles directory does not exist'));
-      }
-    } catch (error) {
-      console.error(chalk.red('Error:'), error.message);
-      process.exit(1);
-    }
-  });
-
-// Parse command line arguments
-program.parse(process.argv);
-
-// Show help if no command provided
-if (process.argv.slice(2).length === 0) {
-  program.outputHelp();
-}

package/tools/cli/bundlers/test-analyst.js

@@ -1,28 +0,0 @@
-const { WebBundler } = require('./web-bundler');
-const chalk = require('chalk');
-const path = require('node:path');
-
-async function testAnalystBundle() {
-  console.log(chalk.cyan.bold('\n🧪 Testing Analyst Agent Bundle\n'));
-
-  try {
-    const bundler = new WebBundler();
-
-    // Load web activation first
-    await bundler.loadWebActivation();
-
-    // Bundle just the analyst agent from bmm module
-    // Only bundle the analyst for testing
-    const agentPath = path.join(bundler.modulesPath, 'bmm', 'agents', 'analyst.md');
-    await bundler.bundleAgent('bmm', 'analyst.md');
-
-    console.log(chalk.green.bold('\n✅ Test completed successfully!\n'));
-  } catch (error) {
-    console.error(chalk.red('\n❌ Test failed:'), error.message);
-    console.error(error.stack);
-    process.exit(1);
-  }
-}
-
-// Run test
-testAnalystBundle();