bmad-method 4.44.1 → 4.44.3

package/dist/teams/team-no-ui.txt

@@ -437,7 +437,6 @@ dependencies:
 
 ==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
-
 # Advanced Elicitation Task
 
 ## Purpose
@@ -559,7 +558,6 @@ Choose a number (0-8) or 9 to proceed:
 
 ==================== START: .bmad-core/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
-
 # Create Document from Template (YAML Driven)
 
 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@@ -665,7 +663,6 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 
 ==================== START: .bmad-core/tasks/kb-mode-interaction.md ====================
 <!-- Powered by BMAD™ Core -->
-
 # KB Mode Interaction Task
 
 ## Purpose
@@ -745,7 +742,6 @@ Or ask me about anything else related to BMad-Method!
 
 ==================== START: .bmad-core/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
-
 # BMAD™ Knowledge Base
 
 ## Overview
@@ -848,7 +844,6 @@ npx bmad-method install
   - **Cline**: VS Code extension with AI features
   - **Roo Code**: Web-based IDE with agent support
   - **GitHub Copilot**: VS Code extension with AI peer programming assistant
-  - **Auggie CLI (Augment Code)**: AI-powered development environment
 
 **Note for VS Code Users**: BMAD-METHOD™ assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMad agents. The installer includes built-in support for Cline and Roo.
 
@@ -1557,7 +1552,6 @@ Use the **expansion-creator** pack to build your own:
 
 ==================== START: .bmad-core/data/elicitation-methods.md ====================
 <!-- Powered by BMAD™ Core -->
-
 # Elicitation Methods Data
 
 ## Core Reflective Methods
@@ -1716,7 +1710,6 @@ Use the **expansion-creator** pack to build your own:
 
 ==================== START: .bmad-core/utils/workflow-management.md ====================
 <!-- Powered by BMAD™ Core -->
-
 # Workflow Management
 
 Enables BMad orchestrator to manage and execute team workflows.
@@ -1790,7 +1783,6 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
 
 ==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
-
 # Create Deep Research Prompt Task
 
 This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@@ -2073,7 +2065,6 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
 
 ==================== START: .bmad-core/tasks/document-project.md ====================
 <!-- Powered by BMAD™ Core -->
-
 # Document an Existing Project
 
 ## Purpose
@@ -2420,11 +2411,10 @@ Apply the advanced elicitation task after major sections to refine based on user
 ==================== END: .bmad-core/tasks/document-project.md ====================
 
 ==================== START: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
-## <!-- Powered by BMAD™ Core -->
-
+<!-- Powered by BMAD™ Core -->
+---
 docOutputLocation: docs/brainstorming-session-results.md
 template: '.bmad-core/templates/brainstorming-output-tmpl.yaml'
-
 ---
 
 # Facilitate Brainstorming Session Task
@@ -3512,7 +3502,6 @@ sections:
 
 ==================== START: .bmad-core/data/brainstorming-techniques.md ====================
 <!-- Powered by BMAD™ Core -->
-
 # Brainstorming Techniques Data
 
 ## Creative Expansion
@@ -3553,7 +3542,6 @@ sections:
 
 ==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
 <!-- Powered by BMAD™ Core -->
-
 # Create Brownfield Epic Task
 
 ## Purpose
@@ -3718,7 +3706,6 @@ The epic creation is successful when:
 
 ==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
 <!-- Powered by BMAD™ Core -->
-
 # Create Brownfield Story Task
 
 ## Purpose
@@ -3870,7 +3857,6 @@ The story creation is successful when:
 
 ==================== START: .bmad-core/tasks/correct-course.md ====================
 <!-- Powered by BMAD™ Core -->
-
 # Correct Course Task
 
 ## Purpose
@@ -3945,7 +3931,6 @@ The story creation is successful when:
 
 ==================== START: .bmad-core/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
-
 # Checklist Validation Task
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@@ -4036,7 +4021,6 @@ The LLM will:
 
 ==================== START: .bmad-core/tasks/shard-doc.md ====================
 <!-- Powered by BMAD™ Core -->
-
 # Document Sharding Task
 
 ## Purpose
@@ -4716,7 +4700,6 @@ sections:
 
 ==================== START: .bmad-core/checklists/change-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
-
 # Change Navigation Checklist
 
 **Purpose:** To systematically guide the selected Agent and user through the analysis and planning required when a significant change (pivot, tech issue, missing requirement, failed story) is identified during the BMad workflow.
@@ -4903,7 +4886,6 @@ Keep it action-oriented and forward-looking.]]
 
 ==================== START: .bmad-core/checklists/pm-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
-
 # Product Manager (PM) Requirements Checklist
 
 This checklist serves as a comprehensive framework to ensure the Product Requirements Document (PRD) and Epic definitions are complete, well-structured, and appropriately scoped for MVP development. The PM should systematically work through each item during the product definition process.
@@ -5278,7 +5260,6 @@ After presenting the report, ask if the user wants:
 
 ==================== START: .bmad-core/data/technical-preferences.md ====================
 <!-- Powered by BMAD™ Core -->
-
 # User-Defined Preferred Patterns and Preferences
 
 None Listed
@@ -6050,8 +6031,8 @@ sections:
           - **UI/UX Consistency:** {{ui_compatibility}}
           - **Performance Impact:** {{performance_constraints}}
 
-  - id: tech-stack
-    title: Tech Stack
+  - id: tech-stack-alignment
+    title: Tech Stack Alignment
     instruction: |
       Ensure new components align with existing technology choices:
 
@@ -6213,8 +6194,8 @@ sections:
 
           **Error Handling:** {{error_handling_strategy}}
 
-  - id: source-tree
-    title: Source Tree
+  - id: source-tree-integration
+    title: Source Tree Integration
     instruction: |
       Define how new code will integrate with existing project structure:
 
@@ -6283,7 +6264,7 @@ sections:
           **Monitoring:** {{monitoring_approach}}
 
   - id: coding-standards
-    title: Coding Standards
+    title: Coding Standards and Conventions
     instruction: |
       Ensure new code follows existing project conventions:
 
@@ -7469,7 +7450,6 @@ sections:
 
 ==================== START: .bmad-core/checklists/architect-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
-
 # Architect Solution Validation Checklist
 
 This checklist serves as a comprehensive framework for the Architect to validate the technical design and architecture before development execution. The Architect should systematically work through each item, ensuring the architecture is robust, scalable, secure, and aligned with the product requirements.
@@ -7912,7 +7892,6 @@ After presenting the report, ask the user if they would like detailed analysis o
 
 ==================== START: .bmad-core/tasks/validate-next-story.md ====================
 <!-- Powered by BMAD™ Core -->
-
 # Validate Next Story Task
 
 ## Purpose
@@ -7934,7 +7913,7 @@ To comprehensively validate a story draft before implementation begins, ensuring
 
 ### 1. Template Completeness Validation
 
-- Load `.bmad-core/templates/story-tmpl.yaml` and extract all section headings from the template
+- Load `bmad-core/templates/story-tmpl.md` and extract all section headings from the template
 - **Missing sections check**: Compare story sections against template sections to verify all required sections are present
 - **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`)
 - **Agent section verification**: Confirm all sections from template exist for future agent use
@@ -8192,7 +8171,6 @@ sections:
 
 ==================== START: .bmad-core/checklists/po-master-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
-
 # Product Owner (PO) Master Validation Checklist
 
 This checklist serves as a comprehensive framework for the Product Owner to validate project plans before development execution. It adapts intelligently based on project type (greenfield vs brownfield) and includes UI/UX considerations when applicable.
@@ -8744,7 +8722,7 @@ workflow:
         - Dev Agent (New Chat): Address remaining items
         - Return to QA for final approval
 
-    - step: repeat_development_cycle
+    - repeat_development_cycle:
       action: continue_for_all_stories
       notes: |
         Repeat story cycle (SM → Dev → QA) for all epic stories
@@ -8761,7 +8739,7 @@ workflow:
         - Validate epic was completed correctly
         - Document learnings and improvements
 
-    - step: workflow_end
+    - workflow_end:
       action: project_complete
       notes: |
         All stories implemented and reviewed!
@@ -8946,7 +8924,7 @@ workflow:
         - Dev Agent (New Chat): Address remaining items
         - Return to QA for final approval
 
-    - step: repeat_development_cycle
+    - repeat_development_cycle:
       action: continue_for_all_stories
       notes: |
         Repeat story cycle (SM → Dev → QA) for all epic stories
@@ -8963,7 +8941,7 @@ workflow:
         - Validate epic was completed correctly
         - Document learnings and improvements
 
-    - step: workflow_end
+    - workflow_end:
       action: project_complete
       notes: |
         All stories implemented and reviewed!

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "4.44.1",
+  "version": "4.44.3",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",

package/tools/installer/bin/bmad.js

@@ -15,7 +15,8 @@ let installer;
 let packageName;
 try {
   // Try installer context first (when run from tools/installer/)
-  version = require('../package.json').version;
+  // Always read version from root package.json to avoid hardcoded versions
+  version = require('../../../package.json').version;
   packageName = require('../package.json').name;
   installer = require('../lib/installer');
 } catch (error) {
@@ -208,6 +209,13 @@ async function promptInstallation() {
   console.log(chalk.bold.magenta('🚀 Universal AI Agent Framework for Any Domain'));
   console.log(chalk.bold.blue(`✨ Installer v${version}\n`));
 
+  // Deprecation notice for v4
+  console.log(chalk.yellow.bold('⚠️  You are installing BMad v4 (stable but frozen)'));
+  console.log(chalk.yellow('   v4 receives critical patches only - no new features\n'));
+  console.log(chalk.cyan('💡 Want the latest features? Try BMad v6 Alpha:'));
+  console.log(chalk.white('   npx bmad-method@alpha install'));
+  console.log(chalk.dim('   (Alpha is stable enough for testing)\n'));
+
   const answers = {};
 
   // Ask for installation directory first

package/tools/installer/config/install.config.yaml

@@ -121,15 +121,15 @@ ide-configurations:
 
   qwen-code:
     name: Qwen Code
-    rule-dir: .qwen/bmad-method/
-    format: single-file
-    command-suffix: .md
+    rule-dir: .qwen/commands/BMad/
+    format: multi-file
+    command-suffix: .toml
     instructions: |
       # To use BMad agents with Qwen Code:
-      # 1. The installer creates a .qwen/bmad-method/ directory in your project.
-      # 2. It concatenates all agent files into a single QWEN.md file.
-      # 3. Simply mention the agent in your prompt (e.g., "As *dev, ...").
-      # 4. The Qwen Code CLI will automatically have the context for that agent.
+      # 1. The installer creates a `BMad` folder in `.qwen/commands`.
+      # 2. This adds custom commands for each agent and task.
+      # 3. Type /BMad:agents:<agent-name> (e.g., "/BMad:agents:dev", "/BMad:agents:pm") or /BMad:tasks:<task-name> (e.g., "/BMad:tasks:create-doc").
+      # 4. The agent will adopt that persona for the conversation or perform the task.
 
   auggie-cli:
     name: Auggie CLI (Augment Code)

package/tools/installer/lib/ide-setup.js

@@ -2056,94 +2056,86 @@ CRITICAL: You are to execute the BMad Task defined below.
   }
 
   async setupQwenCode(installDir, selectedAgent) {
-    const qwenDir = path.join(installDir, '.qwen');
-    const bmadMethodDir = path.join(qwenDir, 'bmad-method');
-    await fileManager.ensureDirectory(bmadMethodDir);
+    const ideConfig = await configLoader.getIdeConfiguration('qwen-code');
+    const bmadCommandsDir = path.join(installDir, ideConfig['rule-dir']);
 
-    // Update logic for existing settings.json
-    const settingsPath = path.join(qwenDir, 'settings.json');
-    if (await fileManager.pathExists(settingsPath)) {
-      try {
-        const settingsContent = await fileManager.readFile(settingsPath);
-        const settings = JSON.parse(settingsContent);
-        let updated = false;
-
-        // Handle contextFileName property
-        if (settings.contextFileName && Array.isArray(settings.contextFileName)) {
-          const originalLength = settings.contextFileName.length;
-          settings.contextFileName = settings.contextFileName.filter(
-            (fileName) => !fileName.startsWith('agents/'),
-          );
-          if (settings.contextFileName.length !== originalLength) {
-            updated = true;
-          }
-        }
+    const agentCommandsDir = path.join(bmadCommandsDir, 'agents');
+    const taskCommandsDir = path.join(bmadCommandsDir, 'tasks');
+    await fileManager.ensureDirectory(agentCommandsDir);
+    await fileManager.ensureDirectory(taskCommandsDir);
 
-        if (updated) {
-          await fileManager.writeFile(settingsPath, JSON.stringify(settings, null, 2));
-          console.log(chalk.green('✓ Updated .qwen/settings.json - removed agent file references'));
-        }
-      } catch (error) {
-        console.warn(chalk.yellow('Could not update .qwen/settings.json'), error);
+    // Process Agents
+    const agents = selectedAgent ? [selectedAgent] : await this.getAllAgentIds(installDir);
+    for (const agentId of agents) {
+      const agentPath = await this.findAgentPath(agentId, installDir);
+      if (!agentPath) {
+        console.log(chalk.yellow(`✗ Agent file not found for ${agentId}, skipping.`));
+        continue;
       }
-    }
 
-    // Remove old agents directory
-    const agentsDir = path.join(qwenDir, 'agents');
-    if (await fileManager.pathExists(agentsDir)) {
-      await fileManager.removeDirectory(agentsDir);
-      console.log(chalk.green('✓ Removed old .qwen/agents directory'));
-    }
+      const agentTitle = await this.getAgentTitle(agentId, installDir);
+      const commandPath = path.join(agentCommandsDir, `${agentId}.toml`);
 
-    // Get all available agents
-    const agents = selectedAgent ? [selectedAgent] : await this.getAllAgentIds(installDir);
-    let concatenatedContent = '';
+      // Get relative path from installDir to agent file for @{file} reference
+      const relativeAgentPath = path.relative(installDir, agentPath).replaceAll('\\', '/');
 
-    for (const agentId of agents) {
-      // Find the source agent file
-      const agentPath = await this.findAgentPath(agentId, installDir);
+      // Read the agent content
+      const agentContent = await fileManager.readFile(agentPath);
 
-      if (agentPath) {
-        const agentContent = await fileManager.readFile(agentPath);
+      const tomlContent = `description = " Activates the ${agentTitle} agent from the BMad Method."
+prompt = """
+CRITICAL: You are now the BMad '${agentTitle}' agent. Adopt its persona, follow its instructions, and use its capabilities. 
 
-        // Create properly formatted agent rule content (similar to gemini)
-        let agentRuleContent = `# ${agentId.toUpperCase()} Agent Rule\n\n`;
-        agentRuleContent += `This rule is triggered when the user types \`*${agentId}\` and activates the ${await this.getAgentTitle(
-          agentId,
-          installDir,
-        )} agent persona.\n\n`;
-        agentRuleContent += '## Agent Activation\n\n';
-        agentRuleContent +=
-          'CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:\n\n';
-        agentRuleContent += '```yaml\n';
-        // Extract just the YAML content from the agent file
-        const yamlContent = extractYamlFromAgent(agentContent);
-        if (yamlContent) {
-          agentRuleContent += yamlContent;
-        } else {
-          // If no YAML found, include the whole content minus the header
-          agentRuleContent += agentContent.replace(/^#.*$/m, '').trim();
-        }
-        agentRuleContent += '\n```\n\n';
-        agentRuleContent += '## File Reference\n\n';
-        const relativePath = path.relative(installDir, agentPath).replaceAll('\\', '/');
-        agentRuleContent += `The complete agent definition is available in [${relativePath}](${relativePath}).\n\n`;
-        agentRuleContent += '## Usage\n\n';
-        agentRuleContent += `When the user types \`*${agentId}\`, activate this ${await this.getAgentTitle(
-          agentId,
-          installDir,
-        )} persona and follow all instructions defined in the YAML configuration above.\n`;
+READ THIS BEFORE ANSWERING AS THE PERSONA!
+
+${agentContent}
+"""`;
 
-        // Add to concatenated content with separator
-        concatenatedContent += agentRuleContent + '\n\n---\n\n';
-        console.log(chalk.green(`✓ Added context for *${agentId}`));
+      await fileManager.writeFile(commandPath, tomlContent);
+      console.log(chalk.green(`✓ Created agent command: /bmad:agents:${agentId}`));
+    }
+
+    // Process Tasks
+    const tasks = await this.getAllTaskIds(installDir);
+    for (const taskId of tasks) {
+      const taskPath = await this.findTaskPath(taskId, installDir);
+      if (!taskPath) {
+        console.log(chalk.yellow(`✗ Task file not found for ${taskId}, skipping.`));
+        continue;
       }
+
+      const taskTitle = taskId
+        .split('-')
+        .map((word) => word.charAt(0).toUpperCase() + word.slice(1))
+        .join(' ');
+      const commandPath = path.join(taskCommandsDir, `${taskId}.toml`);
+
+      // Get relative path from installDir to task file for @{file} reference
+      const relativeTaskPath = path.relative(installDir, taskPath).replaceAll('\\', '/');
+
+      // Read the task content
+      const taskContent = await fileManager.readFile(taskPath);
+
+      const tomlContent = `description = " Executes the BMad Task: ${taskTitle}"
+prompt = """
+CRITICAL: You are to execute the BMad Task defined below.
+
+READ THIS BEFORE EXECUTING THE TASK AS THE INSTRUCTIONS SPECIFIED!
+
+${taskContent}
+"""`;
+
+      await fileManager.writeFile(commandPath, tomlContent);
+      console.log(chalk.green(`✓ Created task command: /bmad:tasks:${taskId}`));
     }
 
-    // Write the concatenated content to QWEN.md
-    const qwenMdPath = path.join(bmadMethodDir, 'QWEN.md');
-    await fileManager.writeFile(qwenMdPath, concatenatedContent);
-    console.log(chalk.green(`\n✓ Created QWEN.md in ${bmadMethodDir}`));
+    console.log(
+      chalk.green(`
+✓ Created Qwen Code extension in ${bmadCommandsDir}`),
+    );
+    console.log(
+      chalk.dim('You can now use commands like /bmad:agents:dev or /bmad:tasks:create-doc.'),
+    );
 
     return true;
   }

package/tools/installer/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bmad-method",
-  "version": "4.44.1",
+  "version": "4.44.2",
   "description": "BMad Method installer - AI-powered Agile development framework",
   "keywords": [
     "bmad",

package/release_notes.md

@@ -1,54 +0,0 @@
-## 🚀 What's New in v4.44.1
-
-### ✨ New Features
-- feat: implement fork-friendly CI/CD with opt-in mechanism (#476)
-- feat(installer): add Codex CLI + Codex Web modes, generate AGENTS.md, inject npm scripts, and docs (#529)
-- feat: add PR validation workflow and contribution checks
-- feat: Add Auggie CLI (Augment Code) Integration (#520)
-- feat: enhance file exclusion capabilities with .bmad-flattenignore support (#531)
-- feat: add iflow cli support to bmad installer.  (#510)
-- feat(opencode): add JSON-only integration and compact AGENTS.md generator (#570)
-
-### 🐛 Bug Fixes
-- fix: update installer version display to show 4.39.0
-- fix: prettier fixes
-- fix: previous merge set wrong default install location
-- fix: documentation and trademark updates
-- fix: remove incorrect else branch causing flatten command regression (#452)
-- fix: correct dependency path format in bmad-master agent (#495)
-- fix: Codex options missing from the IDE selection menu (#535)
-- Fixed: "glob" is not defined (#504)
-- fix: Template file extension in validation next story steps (#523)
-- fix: update .gitignore to correct cursor file entry (#485)
-- fix: update workflow file extensions from .md to .yaml in bmad-master.md (#562)
-- fix: Changed title to coding standards section of brownfield architecture template (#564)
-- fix: BMAD Brownfield Document Naming Inconsistency Bug (#627)
-
-### 📦 Other Changes
-- patch: move script to tools folder
-- typo in README.md (#515)
-- Update dev.md (#491)
-- test: trigger PR validation (#533)
-- docs: remove misplaced Codex section from README
-- Expansion pack doc correction
-- added gemini cli custom commands! (#549)
-- Update ide-setup.js - add missing glob require (#514)
-- Godot Game Dev expansion pack for BMAD (#532)
-- documentation updates
-- remove errant command from readme
-- version up
-
-### 🔧 Maintenance
-- chore: bump to 4.39.1 to fix installer version display
-- chore: update project dependencies and development tooling (#508)
-- chore: bump version to 4.42.0 for release
-- chore: sync version to 4.42.1 after release
-
-
-## 📦 Installation
-
-```bash
-npx bmad-method install
-```
-
-**Full Changelog**: https://github.com/bmadcode/BMAD-METHOD/compare/v4.39.0...v4.44.1