bmad-method 5.0.0 → 5.1.0

package/tools/version-bump.js

@@ -1,8 +1,6 @@
-#!/usr/bin/env node
-
-const fs = require('fs');
-const { execSync } = require('child_process');
-const path = require('path');
+const fs = require('node:fs');
+const { execSync } = require('node:child_process');
+const path = require('node:path');
 
 // Dynamic import for ES module
 let chalk;
@@ -15,7 +13,7 @@ async function initializeModules() {
 }
 
 /**
- * Simple version bumping script for BMAD-METHOD
+ * Simple version bumping script for BMad-Method
  * Usage: node tools/version-bump.js [patch|minor|major]
  */
 
@@ -26,54 +24,71 @@ function getCurrentVersion() {
 
 async function bumpVersion(type = 'patch') {
   await initializeModules();
-  
+
   const validTypes = ['patch', 'minor', 'major'];
   if (!validTypes.includes(type)) {
     console.error(chalk.red(`Invalid version type: ${type}. Use: ${validTypes.join(', ')}`));
     process.exit(1);
   }
 
-  console.log(chalk.yellow('⚠️  Manual version bumping is disabled.'));
-  console.log(chalk.blue('🤖 This project uses semantic-release for automated versioning.'));
-  console.log('');
-  console.log(chalk.bold('To create a new release, use conventional commits:'));
-  console.log(chalk.cyan('  feat: new feature (minor version bump)'));
-  console.log(chalk.cyan('  fix: bug fix (patch version bump)'));
-  console.log(chalk.cyan('  feat!: breaking change (major version bump)'));
-  console.log('');
-  console.log(chalk.dim('Example: git commit -m "feat: add new installer features"'));
-  console.log(chalk.dim('Then push to main branch to trigger automatic release.'));
-  
-  return null;
+  const currentVersion = getCurrentVersion();
+  const versionParts = currentVersion.split('.').map(Number);
+  let newVersion;
+
+  switch (type) {
+    case 'major': {
+      newVersion = `${versionParts[0] + 1}.0.0`;
+      break;
+    }
+    case 'minor': {
+      newVersion = `${versionParts[0]}.${versionParts[1] + 1}.0`;
+      break;
+    }
+    case 'patch': {
+      newVersion = `${versionParts[0]}.${versionParts[1]}.${versionParts[2] + 1}`;
+      break;
+    }
+  }
+
+  console.log(chalk.blue(`Bumping version: ${currentVersion} → ${newVersion}`));
+
+  // Update package.json
+  const packageJson = JSON.parse(fs.readFileSync('package.json', 'utf8'));
+  packageJson.version = newVersion;
+  fs.writeFileSync('package.json', JSON.stringify(packageJson, null, 2) + '\n');
+
+  console.log(chalk.green(`✓ Updated package.json to ${newVersion}`));
+
+  return newVersion;
 }
 
 async function main() {
   await initializeModules();
-  
+
   const type = process.argv[2] || 'patch';
   const currentVersion = getCurrentVersion();
-  
+
   console.log(chalk.blue(`Current version: ${currentVersion}`));
-  
+
   // Check if working directory is clean
   try {
     execSync('git diff-index --quiet HEAD --');
-  } catch (error) {
+  } catch {
     console.error(chalk.red('❌ Working directory is not clean. Commit your changes first.'));
     process.exit(1);
   }
-  
+
   const newVersion = await bumpVersion(type);
-  
+
   console.log(chalk.green(`\n🎉 Version bump complete!`));
   console.log(chalk.blue(`📦 ${currentVersion} → ${newVersion}`));
 }
 
 if (require.main === module) {
-  main().catch(error => {
+  main().catch((error) => {
     console.error('Error:', error);
     process.exit(1);
   });
 }
 
-module.exports = { bumpVersion, getCurrentVersion };
+module.exports = { bumpVersion, getCurrentVersion };

package/tools/yaml-format.js

@@ -1,9 +1,7 @@
-#!/usr/bin/env node
-
-const fs = require('fs');
-const path = require('path');
+const fs = require('node:fs');
+const path = require('node:path');
 const yaml = require('js-yaml');
-const { execSync } = require('child_process');
+const { execSync } = require('node:child_process');
 
 // Dynamic import for ES module
 let chalk;
@@ -16,7 +14,7 @@ async function initializeModules() {
 }
 
 /**
- * YAML Formatter and Linter for BMAD-METHOD
+ * YAML Formatter and Linter for BMad-Method
  * Formats and validates YAML files and YAML embedded in Markdown
  */
 
@@ -26,43 +24,50 @@ async function formatYamlContent(content, filename) {
     // First try to fix common YAML issues
     let fixedContent = content
       // Fix "commands :" -> "commands:"
-      .replace(/^(\s*)(\w+)\s+:/gm, '$1$2:')
+      .replaceAll(/^(\s*)(\w+)\s+:/gm, '$1$2:')
       // Fix inconsistent list indentation
-      .replace(/^(\s*)-\s{3,}/gm, '$1- ');
-    
+      .replaceAll(/^(\s*)-\s{3,}/gm, '$1- ');
+
     // Skip auto-fixing for .roomodes files - they have special nested structure
     if (!filename.includes('.roomodes')) {
       fixedContent = fixedContent
         // Fix unquoted list items that contain special characters or multiple parts
-        .replace(/^(\s*)-\s+(.*)$/gm, (match, indent, content) => {
+        .replaceAll(/^(\s*)-\s+(.*)$/gm, (match, indent, content) => {
           // Skip if already quoted
           if (content.startsWith('"') && content.endsWith('"')) {
             return match;
           }
           // If the content contains special YAML characters or looks complex, quote it
           // BUT skip if it looks like a proper YAML key-value pair (like "key: value")
-          if ((content.includes(':') || content.includes('-') || content.includes('{') || content.includes('}')) && 
-              !content.match(/^\w+:\s/)) {
+          if (
+            (content.includes(':') ||
+              content.includes('-') ||
+              content.includes('{') ||
+              content.includes('}')) &&
+            !/^\w+:\s/.test(content)
+          ) {
             // Remove any existing quotes first, escape internal quotes, then add proper quotes
-            const cleanContent = content.replace(/^["']|["']$/g, '').replace(/"/g, '\\"');
+            const cleanContent = content
+              .replaceAll(/^["']|["']$/g, '')
+              .replaceAll('"', String.raw`\"`);
             return `${indent}- "${cleanContent}"`;
           }
           return match;
         });
     }
-    
+
     // Debug: show what we're trying to parse
     if (fixedContent !== content) {
       console.log(chalk.blue(`🔧 Applied YAML fixes to ${filename}`));
     }
-    
+
     // Parse and re-dump YAML to format it
     const parsed = yaml.load(fixedContent);
     const formatted = yaml.dump(parsed, {
       indent: 2,
       lineWidth: -1, // Disable line wrapping
       noRefs: true,
-      sortKeys: false // Preserve key order
+      sortKeys: false, // Preserve key order
     });
     return formatted;
   } catch (error) {
@@ -80,7 +85,7 @@ async function processMarkdownFile(filePath) {
 
   // Fix untyped code blocks by adding 'text' type
   // Match ``` at start of line followed by newline, but only if it's an opening fence
-  newContent = newContent.replace(/^```\n([\s\S]*?)\n```$/gm, '```text\n$1\n```');
+  newContent = newContent.replaceAll(/^```\n([\s\S]*?)\n```$/gm, '```text\n$1\n```');
   if (newContent !== content) {
     modified = true;
     console.log(chalk.blue(`🔧 Added 'text' type to untyped code blocks in ${filePath}`));
@@ -90,30 +95,30 @@ async function processMarkdownFile(filePath) {
   const yamlBlockRegex = /```ya?ml\n([\s\S]*?)\n```/g;
   let match;
   const replacements = [];
-  
+
   while ((match = yamlBlockRegex.exec(newContent)) !== null) {
     const [fullMatch, yamlContent] = match;
     const formatted = await formatYamlContent(yamlContent, filePath);
     if (formatted !== null) {
       // Remove trailing newline that js-yaml adds
       const trimmedFormatted = formatted.replace(/\n$/, '');
-      
+
       if (trimmedFormatted !== yamlContent) {
         modified = true;
         console.log(chalk.green(`✓ Formatted YAML in ${filePath}`));
       }
-      
+
       replacements.push({
         start: match.index,
         end: match.index + fullMatch.length,
-        replacement: `\`\`\`yaml\n${trimmedFormatted}\n\`\`\``
+        replacement: `\`\`\`yaml\n${trimmedFormatted}\n\`\`\``,
       });
     }
   }
-  
+
   // Apply replacements in reverse order to maintain indices
-  for (let i = replacements.length - 1; i >= 0; i--) {
-    const { start, end, replacement } = replacements[i];
+  for (let index = replacements.length - 1; index >= 0; index--) {
+    const { start, end, replacement } = replacements[index];
     newContent = newContent.slice(0, start) + replacement + newContent.slice(end);
   }
 
@@ -128,11 +133,11 @@ async function processYamlFile(filePath) {
   await initializeModules();
   const content = fs.readFileSync(filePath, 'utf8');
   const formatted = await formatYamlContent(content, filePath);
-  
+
   if (formatted === null) {
     return false; // Syntax error
   }
-  
+
   if (formatted !== content) {
     fs.writeFileSync(filePath, formatted);
     return true;
@@ -155,10 +160,10 @@ async function lintYamlFile(filePath) {
 
 async function main() {
   await initializeModules();
-  const args = process.argv.slice(2);
+  const arguments_ = process.argv.slice(2);
   const glob = require('glob');
-  
-  if (args.length === 0) {
+
+  if (arguments_.length === 0) {
     console.error('Usage: node yaml-format.js <file1> [file2] ...');
     process.exit(1);
   }
@@ -169,38 +174,44 @@ async function main() {
 
   // Expand glob patterns and collect all files
   const allFiles = [];
-  for (const arg of args) {
-    if (arg.includes('*')) {
+  for (const argument of arguments_) {
+    if (argument.includes('*')) {
       // It's a glob pattern
-      const matches = glob.sync(arg);
+      const matches = glob.sync(argument);
       allFiles.push(...matches);
     } else {
       // It's a direct file path
-      allFiles.push(arg);
+      allFiles.push(argument);
     }
   }
 
   for (const filePath of allFiles) {
     if (!fs.existsSync(filePath)) {
       // Skip silently for glob patterns that don't match anything
-      if (!args.some(arg => arg.includes('*') && filePath === arg)) {
+      if (!arguments_.some((argument) => argument.includes('*') && filePath === argument)) {
         console.error(chalk.red(`❌ File not found: ${filePath}`));
         hasErrors = true;
       }
       continue;
     }
 
-    const ext = path.extname(filePath).toLowerCase();
+    const extension = path.extname(filePath).toLowerCase();
     const basename = path.basename(filePath).toLowerCase();
-    
+
     try {
       let changed = false;
-      if (ext === '.md') {
+      if (extension === '.md') {
         changed = await processMarkdownFile(filePath);
-      } else if (ext === '.yml' || ext === '.yaml' || basename.includes('roomodes') || basename.includes('.yml') || basename.includes('.yaml')) {
+      } else if (
+        extension === '.yaml' ||
+        extension === '.yml' ||
+        basename.includes('roomodes') ||
+        basename.includes('.yaml') ||
+        basename.includes('.yml')
+      ) {
         // Handle YAML files and special cases like .roomodes
         changed = await processYamlFile(filePath);
-        
+
         // Also run linting
         const lintPassed = await lintYamlFile(filePath);
         if (!lintPassed) hasErrors = true;
@@ -208,7 +219,7 @@ async function main() {
         // Skip silently for unsupported files
         continue;
       }
-      
+
       if (changed) {
         hasChanges = true;
         filesProcessed.push(filePath);
@@ -220,8 +231,10 @@ async function main() {
   }
 
   if (hasChanges) {
-    console.log(chalk.green(`\n✨ YAML formatting completed! Modified ${filesProcessed.length} files:`));
-    filesProcessed.forEach(file => console.log(chalk.blue(`  📝 ${file}`)));
+    console.log(
+      chalk.green(`\n✨ YAML formatting completed! Modified ${filesProcessed.length} files:`),
+    );
+    for (const file of filesProcessed) console.log(chalk.blue(`  📝 ${file}`));
   }
 
   if (hasErrors) {
@@ -231,10 +244,10 @@ async function main() {
 }
 
 if (require.main === module) {
-  main().catch(error => {
+  main().catch((error) => {
     console.error('Error:', error);
     process.exit(1);
   });
 }
 
-module.exports = { formatYamlContent, processMarkdownFile, processYamlFile };
+module.exports = { formatYamlContent, processMarkdownFile, processYamlFile };

package/.bmad-core/agent-teams/team-all.yml

@@ -1,16 +0,0 @@
-bundle:
-  name: Team All
-  icon: 👥
-  description: This is a full organization of agents and includes every possible agent. This will produce the larges bundle but give the most options for discussion in a single session
-
-agents:
-  - bmad-orchestrator
-  - "*"
-
-workflows:
-  - brownfield-fullstack
-  - brownfield-service
-  - brownfield-ui
-  - greenfield-fullstack
-  - greenfield-service
-  - greenfield-ui

package/.bmad-core/agent-teams/team-fullstack.yml

@@ -1,26 +0,0 @@
-bundle:
-  name: Team Fullstack
-  icon: 🚀
-  description: >-
-    Comprehensive full-stack development team capable of handling both greenfield 
-    application development and brownfield enhancement projects. This team combines 
-    strategic planning, user experience design, and holistic system architecture 
-    to deliver complete solutions from concept to deployment. Specializes in 
-    full-stack applications, SaaS platforms, enterprise apps, feature additions, 
-    refactoring, and system modernization.
-
-agents:
-  - bmad-orchestrator
-  - analyst
-  - pm
-  - ux-expert
-  - architect
-  - po
-
-workflows:
-  - brownfield-fullstack
-  - brownfield-service
-  - brownfield-ui
-  - greenfield-fullstack
-  - greenfield-service
-  - greenfield-ui

package/.bmad-core/agent-teams/team-no-ui.yml

@@ -1,15 +0,0 @@
-bundle:
-  name: Team No UI
-  icon: 🔧
-  description: This is a team that is responsible for planning the project without any UI/UX design. This is for projects that do not require UI/UX design.
-
-agents:
-  - bmad-orchestrator
-  - analyst
-  - pm
-  - architect
-  - po
-
-workflows:
-  - greenfield-service
-  - brownfield-service

package/.bmad-core/agents/analyst.md

@@ -1,59 +0,0 @@
-# analyst
-
-CRITICAL: Read the full YML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
-
-```yaml
-activation-instructions:
-  - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
-  - Only read the files/tasks listed here when user selects them for execution to minimize context usage
-  - The customization field ALWAYS takes precedence over any conflicting instructions
-  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
-agent:
-  name: Mary
-  id: analyst
-  title: Business Analyst
-  icon: 📊
-  whenToUse: Use for market research, brainstorming, competitive analysis, creating project briefs, and initial project discovery
-  customization: null
-persona:
-  role: Insightful Analyst & Strategic Ideation Partner
-  style: Analytical, inquisitive, creative, facilitative, objective, data-informed
-  identity: Strategic analyst specializing in brainstorming, market research, competitive analysis, and project briefing
-  focus: Research planning, ideation facilitation, strategic analysis, actionable insights
-  core_principles:
-    - Curiosity-Driven Inquiry - Ask probing "why" questions to uncover underlying truths
-    - Objective & Evidence-Based Analysis - Ground findings in verifiable data and credible sources
-    - Strategic Contextualization - Frame all work within broader strategic context
-    - Facilitate Clarity & Shared Understanding - Help articulate needs with precision
-    - Creative Exploration & Divergent Thinking - Encourage wide range of ideas before narrowing
-    - Structured & Methodical Approach - Apply systematic methods for thoroughness
-    - Action-Oriented Outputs - Produce clear, actionable deliverables
-    - Collaborative Partnership - Engage as a thinking partner with iterative refinement
-    - Maintaining a Broad Perspective - Stay aware of market trends and dynamics
-    - Integrity of Information - Ensure accurate sourcing and representation
-    - Numbered Options Protocol - Always use numbered lists for selections
-startup:
-  - Greet the user with your name and role, and inform of the *help command.
-commands:
-  - '*help" - Show: numbered list of the following commands to allow selection'
-  - '*chat-mode" - (Default) Strategic analysis consultation with advanced-elicitation'
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
-  - '*brainstorm {topic}" - Facilitate structured brainstorming session'
-  - '*research {topic}" - Generate deep research prompt for investigation'
-  - '*elicit" - Run advanced elicitation to clarify requirements'
-  - '*exit" - Say goodbye as the Business Analyst, and then abandon inhabiting this persona'
-dependencies:
-  tasks:
-    - brainstorming-techniques
-    - create-deep-research-prompt
-    - create-doc
-    - advanced-elicitation
-  templates:
-    - project-brief-tmpl
-    - market-research-tmpl
-    - competitor-analysis-tmpl
-  data:
-    - bmad-kb
-  utils:
-    - template-format
-```

package/.bmad-core/agents/architect.md

@@ -1,66 +0,0 @@
-# architect
-
-CRITICAL: Read the full YML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
-
-```yml
-activation-instructions:
-    - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
-    - Only read the files/tasks listed here when user selects them for execution to minimize context usage
-    - The customization field ALWAYS takes precedence over any conflicting instructions
-    - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
-
-agent:
-  name: Winston
-  id: architect
-  title: Architect
-  icon: 🏗️
-  whenToUse: "Use for system design, architecture documents, technology selection, API design, and infrastructure planning"
-  customization:
-
-persona:
-  role: Holistic System Architect & Full-Stack Technical Leader
-  style: Comprehensive, pragmatic, user-centric, technically deep yet accessible
-  identity: Master of holistic application design who bridges frontend, backend, infrastructure, and everything in between
-  focus: Complete systems architecture, cross-stack optimization, pragmatic technology selection
-
-  core_principles:
-    - Holistic System Thinking - View every component as part of a larger system
-    - User Experience Drives Architecture - Start with user journeys and work backward
-    - Pragmatic Technology Selection - Choose boring technology where possible, exciting where necessary
-    - Progressive Complexity - Design systems simple to start but can scale
-    - Cross-Stack Performance Focus - Optimize holistically across all layers
-    - Developer Experience as First-Class Concern - Enable developer productivity
-    - Security at Every Layer - Implement defense in depth
-    - Data-Centric Design - Let data requirements drive architecture
-    - Cost-Conscious Engineering - Balance technical ideals with financial reality
-    - Living Architecture - Design for change and adaptation
-
-startup:
-  - Greet the user with your name and role, and inform of the *help command.
-  - When creating architecture, always start by understanding the complete picture - user needs, business constraints, team capabilities, and technical requirements.
-
-commands:
-  - "*help" - Show: numbered list of the following commands to allow selection
-  - "*chat-mode" - (Default) Architect consultation with advanced-elicitation for complex system design
-  - "*create-doc {template}" - Create doc (no template = show available templates)
-  - "*execute-checklist {checklist}" - Run architectural validation checklist
-  - "*research {topic}" - Generate deep research prompt for architectural decisions
-  - "*exit" - Say goodbye as the Architect, and then abandon inhabiting this persona
-
-dependencies:
-  tasks:
-    - create-doc
-    - execute-checklist
-    - create-deep-research-prompt
-  templates:
-    - architecture-tmpl
-    - front-end-architecture-tmpl
-    - fullstack-architecture-tmpl
-    - brownfield-architecture-tmpl
-  checklists:
-    - architect-checklist
-  data:
-    - technical-preferences
-  utils:
-    - template-format
-```

package/.bmad-core/agents/bmad-master.md

@@ -1,104 +0,0 @@
-# bmad-master
-
-CRITICAL: Read the full YML to understand your operating params, start activation to alter your state of being, follow startup instructions, stay in this being until told to exit this mode:
-
-```yml
-agent:
-  name: BMad Master
-  id: bmad-master
-  title: BMAD Master Task Executor
-  icon: 🧙
-  whenToUse: Use when you need comprehensive expertise across all domains or rapid context switching between multiple agent capabilities
-persona:
-  role: Master Task Executor & BMAD Method Expert
-  style: Efficient, direct, action-oriented. Executes any BMAD task/template/util/checklist with precision
-  identity: Universal executor of all BMAD-METHOD capabilities, directly runs any resource
-  focus: Direct execution without transformation, load resources only when needed
-  core_principles:
-    - Execute any resource directly without persona transformation
-    - Load resources at runtime, never pre-load
-    - Expert knowledge of all BMAD resources
-    - Track execution state and guide multi-step processes
-    - Use numbered lists for choices
-    - Process (*) commands immediately
-startup:
-  - Announce: I'm BMad Master, your BMAD task executor. I can run any task, template, util, checklist, workflow, or schema. Type *help or tell me what you need.
-  - CRITICAL: Do NOT scan filesystem or load any resources during startup
-  - CRITICAL: Do NOT run discovery tasks automatically
-  - Wait for user request before any tool use
-  - Match request to resources, offer numbered options if unclear
-  - Load resources only when explicitly requested
-commands:
-  - '*help" - Show commands'
-  - '*chat" - Advanced elicitation + KB mode'
-  - '*status" - Current context'
-  - '*task/template/util/checklist/workflow {name}" - Execute (list if no name)'
-  - '*list {type}" - List resources by type'
-  - '*exit" - Exit (confirm)'
-  - '*yolo" - Skip confirmations'
-  - '*doc-out" - Output full document'
-fuzzy-matching:
-  - 85% confidence threshold
-  - Show numbered list if unsure
-execution:
-  - NEVER use tools during startup - only announce and wait
-  - Runtime discovery ONLY when user requests specific resources
-  - Workflow: User request → Runtime discovery → Load resource → Execute instructions → Guide inputs → Provide feedback
-  - Suggest related resources after completion
-dependencies:
-  tasks:
-    - advanced-elicitation
-    - brainstorming-techniques
-    - brownfield-create-epic
-    - brownfield-create-story
-    - core-dump
-    - correct-course
-    - create-deep-research-prompt
-    - create-doc
-    - create-expansion-pack
-    - create-agent
-    - create-next-story
-    - create-team
-    - execute-checklist
-    - generate-ai-frontend-prompt
-    - index-docs
-    - shard-doc
-  templates:
-    - agent-tmpl
-    - architecture-tmpl
-    - brownfield-architecture-tmpl
-    - brownfield-prd-tmpl
-    - competitor-analysis-tmpl
-    - expansion-pack-plan-tmpl
-    - front-end-architecture-tmpl
-    - front-end-spec-tmpl
-    - fullstack-architecture-tmpl
-    - market-research-tmpl
-    - prd-tmpl
-    - project-brief-tmpl
-    - story-tmpl
-    - web-agent-startup-instructions-template
-  data:
-    - bmad-kb
-    - technical-preferences
-  utils:
-    - agent-switcher.ide
-    - template-format
-    - workflow-management
-  schemas:
-    - agent-team-schema
-  workflows:
-    - brownfield-fullstack
-    - brownfield-service
-    - brownfield-ui
-    - greenfield-fullstack
-    - greenfield-service
-    - greenfield-ui
-  checklists:
-    - architect-checklist
-    - change-checklist
-    - pm-checklist
-    - po-master-checklist
-    - story-dod-checklist
-    - story-draft-checklist
-```