bmad-method 4.44.0 → 4.44.2

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.
 
@@ -927,7 +922,7 @@ npx bmad-method install
 
 ## Core Configuration (core-config.yaml)
 
-**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
+**New in V4**: The `.bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
 
 ### What is core-config.yaml?
 
@@ -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
@@ -5964,7 +5945,7 @@ sections:
       1. **Verify Complexity**: Confirm this enhancement requires architectural planning. For simple additions, recommend: "For simpler changes that don't require architectural planning, consider using the brownfield-create-epic or brownfield-create-story task with the Product Owner instead."
 
       2. **REQUIRED INPUTS**:
-         - Completed brownfield-prd.md
+         - Completed prd.md
          - Existing project technical documentation (from docs folder or user-provided)
          - Access to existing project structure (IDE or uploaded files)
 
@@ -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.
@@ -8208,7 +8186,7 @@ First, determine the project type by checking:
 
 2. Is this a BROWNFIELD project (enhancing existing system)?
    - Look for: References to existing codebase, enhancement/modification language
-   - Check for: brownfield-prd.md, brownfield-architecture.md, existing system analysis
+   - Check for: prd.md, architecture.md, existing system analysis
 
 3. Does the project include UI/UX components?
    - Check for: frontend-architecture.md, UI/UX specifications, design files
@@ -8226,8 +8204,8 @@ For GREENFIELD projects:
 
 For BROWNFIELD projects:
 
-- brownfield-prd.md - The brownfield enhancement requirements
-- brownfield-architecture.md - The enhancement architecture
+- prd.md - The brownfield enhancement requirements
+- architecture.md - The enhancement architecture
 - Existing project codebase access (CRITICAL - cannot proceed without this)
 - Current deployment configuration and infrastructure details
 - Database schemas, API documentation, monitoring setup
@@ -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/docs/user-guide.md

@@ -187,6 +187,53 @@ If you want to do the planning on the web with Claude (Sonnet 4 or Opus), Gemini
 npx bmad-method install
 ```
 
+### OpenCode
+
+BMAD integrates with OpenCode via a project-level `opencode.jsonc`/`opencode.json` (JSON-only, no Markdown fallback).
+
+- Installation:
+  - Run `npx bmad-method install` and choose `OpenCode` in the IDE list.
+  - The installer will detect an existing `opencode.jsonc`/`opencode.json` or create a minimal `opencode.jsonc` if missing.
+  - It will:
+    - Ensure `instructions` includes `.bmad-core/core-config.yaml` (and each selected expansion pack’s `config.yaml`).
+    - Merge BMAD agents and commands using file references (`{file:./.bmad-core/...}`), idempotently.
+    - Preserve other top-level fields and user-defined entries.
+
+- Prefixes and collisions:
+  - You can opt-in to prefix agent keys with `bmad-` and command keys with `bmad:tasks:` to avoid name collisions.
+  - If a key already exists and is not BMAD-managed, the installer will skip it and suggest enabling prefixes.
+
+- What gets added:
+  - `instructions`: `.bmad-core/core-config.yaml` plus any selected expansion pack `config.yaml` files.
+  - `agent`: BMAD agents from core and selected packs.
+    - `prompt`: `{file:./.bmad-core/agents/<id>.md}` (or pack path)
+    - `mode`: `primary` for orchestrators, otherwise `all`
+    - `tools`: `{ write: true, edit: true, bash: true }`
+    - `description`: extracted from the agent’s `whenToUse`
+  - `command`: BMAD tasks from core and selected packs.
+    - `template`: `{file:./.bmad-core/tasks/<id>.md}` (or pack path)
+    - `description`: extracted from the task’s “Purpose” section
+
+- Selected Packages Only:
+  - The installer includes agents and tasks only from the packages you selected in the earlier step (core and chosen packs).
+
+- Refresh after changes:
+  - Re-run:
+    ```bash
+    npx bmad-method install -f -i opencode
+    ```
+  - The installer safely updates entries without duplication and preserves your custom fields and comments.
+
+- Optional convenience script:
+  - You can add a script to your project’s `package.json` for quick refreshes:
+    ```json
+    {
+      "scripts": {
+        "bmad:opencode": "bmad-method install -f -i opencode"
+      }
+    }
+    ```
+
 ### Codex (CLI & Web)
 
 BMAD integrates with OpenAI Codex via `AGENTS.md` and committed core agent files.
@@ -501,7 +548,7 @@ When creating custom web bundles or uploading to AI platforms, include your `tec
 
 ## Core Configuration
 
-The `bmad-core/core-config.yaml` file is a critical config that enables BMad to work seamlessly with differing project structures, more options will be made available in the future. Currently the most important is the devLoadAlwaysFiles list section in the yaml.
+The `.bmad-core/core-config.yaml` file is a critical config that enables BMad to work seamlessly with differing project structures, more options will be made available in the future. Currently the most important is the devLoadAlwaysFiles list section in the yaml.
 
 ### Developer Context Files
 

package/expansion-packs/bmad-godot-game-dev/agents/bmad-orchestrator.md

@@ -31,7 +31,7 @@ activation-instructions:
   - Assess user goal against available agents and workflows in this bundle
   - If clear match to an agent's expertise, suggest transformation with *agent command
   - If project-oriented, suggest *workflow-guidance to explore options
-  - Load resources only when needed - never pre-load (Exception: Read `bmad-core/core-config.yaml` during activation)
+  - Load resources only when needed - never pre-load (Exception: Read `.bmad-core/core-config.yaml` during activation)
   - CRITICAL: On activation, ONLY greet user, auto-run `*help`, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
 agent:
   name: BMad Orchestrator

package/expansion-packs/bmad-godot-game-dev/agents/game-qa.md

@@ -34,8 +34,7 @@ agent:
   id: game-qa
   title: Game Test Architect & TDD Enforcer (Godot)
   icon: 🎮🧪
-  whenToUse: |
-    Use for Godot game testing architecture, test-driven development enforcement,
+  whenToUse: Use for Godot game testing architecture, test-driven development enforcement,
     performance validation, and gameplay quality assurance. Ensures all code is
     test-first, performance targets are met, and player experience is validated.
     Enforces GUT for GDScript and GoDotTest/GodotTestDriver for C# with TDD practices.

package/expansion-packs/bmad-godot-game-dev/tasks/apply-qa-fixes.md

@@ -50,7 +50,7 @@ optional:
 
 ### 0) Load Core Config & Locate Story
 
-- Read `bmad-core/core-config.yaml` and resolve `qa_root`, `story_root`, and `project_root`
+- Read `.bmad-core/core-config.yaml` and resolve `qa_root`, `story_root`, and `project_root`
 - Locate story file in `{story_root}/{epic}.{story}.*.md`
   - HALT if missing and ask for correct story id/path
 
@@ -150,7 +150,7 @@ Status Rule:
 
 ## Blocking Conditions
 
-- Missing `bmad-core/core-config.yaml`
+- Missing `.bmad-core/core-config.yaml`
 - Story file not found for `story_id`
 - No QA artifacts found (neither gate nor assessments)
   - HALT and request QA to generate at least a gate file (or proceed only with clear developer-provided fix list)

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "4.44.0",
+  "version": "4.44.2",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",
@@ -75,6 +75,7 @@
     "@kayvan/markdown-tree-parser": "^1.6.1",
     "chalk": "^4.1.2",
     "commander": "^14.0.0",
+    "comment-json": "^4.2.5",
     "fs-extra": "^11.3.1",
     "glob": "^11.0.3",
     "ignore": "^7.0.5",

package/tools/installer/bin/bmad.js

@@ -49,7 +49,7 @@ program
   .option('-d, --directory <path>', 'Installation directory')
   .option(
     '-i, --ide <ide...>',
-    'Configure for specific IDE(s) - can specify multiple (cursor, claude-code, windsurf, trae, roo, kilo, cline, gemini, qwen-code, github-copilot, codex, codex-web, auggie-cli, iflow-cli, other)',
+    'Configure for specific IDE(s) - can specify multiple (cursor, claude-code, windsurf, trae, roo, kilo, cline, gemini, qwen-code, github-copilot, codex, codex-web, auggie-cli, iflow-cli, opencode, other)',
   )
   .option(
     '-e, --expansion-packs <packs...>',
@@ -208,6 +208,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
@@ -410,6 +417,7 @@ async function promptInstallation() {
           { name: 'Auggie CLI (Augment Code)', value: 'auggie-cli' },
           { name: 'Codex CLI', value: 'codex' },
           { name: 'Codex Web', value: 'codex-web' },
+          { name: 'OpenCode', value: 'opencode' },
         ],
       },
     ]);
@@ -478,6 +486,43 @@ async function promptInstallation() {
     answers.githubCopilotConfig = { configChoice };
   }
 
+  // Configure OpenCode immediately if selected
+  if (ides.includes('opencode')) {
+    console.log(chalk.cyan('\n⚙️  OpenCode Configuration'));
+    console.log(
+      chalk.dim(
+        'OpenCode will include agents and tasks from the packages you selected above; choose optional key prefixes (defaults: no prefixes).\n',
+      ),
+    );
+
+    const { useAgentPrefix, useCommandPrefix } = await inquirer.prompt([
+      {
+        type: 'confirm',
+        name: 'useAgentPrefix',
+        message: "Prefix agent keys with 'bmad-'? (e.g., 'bmad-dev')",
+        default: true,
+      },
+      {
+        type: 'confirm',
+        name: 'useCommandPrefix',
+        message: "Prefix command keys with 'bmad:tasks:'? (e.g., 'bmad:tasks:create-doc')",
+        default: true,
+      },
+    ]);
+
+    answers.openCodeConfig = {
+      opencode: {
+        useAgentPrefix,
+        useCommandPrefix,
+      },
+      // pass previously selected packages so IDE setup only applies those
+      selectedPackages: {
+        includeCore: selectedItems.includes('bmad-core'),
+        packs: answers.expansionPacks || [],
+      },
+    };
+  }
+
   // Configure Auggie CLI (Augment Code) immediately if selected
   if (ides.includes('auggie-cli')) {
     console.log(chalk.cyan('\n📍 Auggie CLI Location Configuration'));

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)
@@ -171,3 +171,14 @@ ide-configurations:
       # 2. Commit `.bmad-core/` and `AGENTS.md` to your repository.
       # 3. Open the repo in Codex Web and reference agents naturally (e.g., "As dev, ...").
       # 4. Re-run this installer to refresh agent sections when the core changes.
+
+  opencode:
+    name: OpenCode CLI
+    format: jsonc-config
+    file: opencode.jsonc
+    instructions: |
+      # To use BMAD agents with OpenCode CLI:
+      # 1. The installer creates/updates `opencode.jsonc` at your project root.
+      # 2. It ensures the BMAD core instructions file is referenced: `./.bmad-core/core-config.yaml`.
+      # 3. If an existing `opencode.json` or `opencode.jsonc` is present, it is preserved and only `instructions` are minimally merged.
+      # 4. Run `opencode` in this project to use your configured agents and commands.