bmad-method 4.17.0 → 4.19.0

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

@@ -560,9 +560,9 @@ Confirm with the user their preferred interaction style:
 
 ### 3. Execute Template
 
-- Load specified template from `templates#*` or the /templates directory
+- Load specified template from `templates#*` or the `{root}/templates directory`
 - Follow ALL embedded LLM instructions within the template
-- Process template markup according to `utils#template-format` conventions
+- Process template markup according to `utils#template-format` or `{root}/utils/template-format` conventions
 
 ### 4. Template Processing Rules
 
@@ -1429,227 +1429,73 @@ Use the **expansion-creator** pack to build your own:
 ==================== START: utils#workflow-management ====================
 # Workflow Management
 
-This utility enables the BMAD orchestrator to manage and execute team workflows.
+Enables BMAD orchestrator to manage and execute team workflows.
 
-## Important: Dynamic Workflow Loading
+## Dynamic Workflow Loading
 
-The BMAD orchestrator MUST read the available workflows from the current team configuration's `workflows` field. Do not use hardcoded workflow lists. Each team bundle defines its own set of supported workflows based on the agents it includes.
+Read available workflows from current team configuration's `workflows` field. Each team bundle defines its own supported workflows.
 
-**Critical Distinction**:
+**Key Commands**:
 
-- When asked "what workflows are available?", show ONLY the workflows defined in the current team bundle's configuration
-- Use `/agent-list` to show agents in the current bundle
-- Use `/workflows` to show workflows in the current bundle, NOT any creation tasks
-
-### Workflow Descriptions
-
-When displaying workflows, use these descriptions based on the workflow ID:
-
-- **greenfield-fullstack**: Build a new full-stack application from concept to development
-- **brownfield-fullstack**: Enhance an existing full-stack application with new features
-- **greenfield-service**: Build a new backend service or API from concept to development
-- **brownfield-service**: Enhance an existing backend service or API
-- **greenfield-ui**: Build a new frontend/UI application from concept to development
-- **brownfield-ui**: Enhance an existing frontend/UI application
+- `/workflows` - List workflows in current bundle or workflows folder
+- `/agent-list` - Show agents in current bundle
 
 ## Workflow Commands
 
 ### /workflows
 
-Lists all available workflows for the current team. The available workflows are determined by the team configuration and may include workflows such as:
-
-- greenfield-fullstack
-- brownfield-fullstack
-- greenfield-service
-- brownfield-service
-- greenfield-ui
-- brownfield-ui
-
-The actual list depends on which team bundle is loaded. When responding to this command, display the workflows that are configured in the current team's `workflows` field.
-
-Example response format:
-
-```text
-Available workflows for [Team Name]:
-1. [workflow-id] - [Brief description based on workflow type]
-2. [workflow-id] - [Brief description based on workflow type]
-[... etc. ...]
-
-Use /workflow-start {number or id} to begin a workflow.
-```
+Lists available workflows with titles and descriptions.
 
 ### /workflow-start {workflow-id}
 
-Starts a specific workflow and transitions to the first agent.
-
-Example: `/workflow-start greenfield-fullstack`
+Starts workflow and transitions to first agent.
 
 ### /workflow-status
 
-Shows current workflow progress, completed artifacts, and next steps.
-
-Example response:
-
-```text
-Current Workflow: Greenfield Full-Stack Development
-Stage: Product Planning (2 of 6)
-Completed:
-  ✓ Discovery & Requirements
-    - project-brief (completed by Mary)
-
-In Progress:
-  ⚡ Product Planning
-    - Create PRD (John) - awaiting input
-
-Next: Technical Architecture
-```
+Shows current progress, completed artifacts, and next steps.
 
 ### /workflow-resume
 
-Resumes a workflow from where it left off, useful when starting a new chat.
-
-User can provide completed artifacts:
-
-```text
-User: /workflow-resume greenfield-fullstack
-      I have completed: project-brief, PRD
-BMad: I see you've completed Discovery and part of Product Planning.
-      Based on the greenfield-fullstack workflow, the next step is:
-      - UX Strategy with Sally (ux-expert)
-
-      Would you like me to load Sally to continue?
-```
+Resumes workflow from last position. User can provide completed artifacts.
 
 ### /workflow-next
 
-Shows the next recommended agent and action in the current workflow.
-
-## Workflow Execution Flow
-
-### 1. Starting a Workflow
+Shows next recommended agent and action.
 
-When a workflow is started:
+## Execution Flow
 
-1. Load the workflow definition
-2. Identify the first stage and step
-3. Transition to the required agent
-4. Provide context about expected inputs/outputs
-5. Guide artifact creation
+1. **Starting**: Load definition → Identify first stage → Transition to agent → Guide artifact creation
 
-### 2. Stage Transitions
+2. **Stage Transitions**: Mark complete → Check conditions → Load next agent → Pass artifacts
 
-After each artifact is completed:
+3. **Artifact Tracking**: Track status, creator, timestamps in workflow_state
 
-1. Mark the step as complete
-2. Check transition conditions
-3. If stage is complete, move to next stage
-4. Load the appropriate agent
-5. Pass relevant artifacts as context
+4. **Interruption Handling**: Analyze provided artifacts → Determine position → Suggest next step
 
-### 3. Artifact Tracking
+## Context Passing
 
-Track all created artifacts:
-
-```yaml
-workflow_state:
-  current_workflow: greenfield-fullstack
-  current_stage: planning
-  current_step: 2
-  artifacts:
-    project-brief:
-      status: completed
-      created_by: analyst
-      timestamp: 2024-01-15T10:30:00.000Z
-    prd:
-      status: in-progress
-      created_by: pm
-      started: 2024-01-15T11:00:00.000Z
-```
+When transitioning, pass:
 
-### 4. Workflow Interruption Handling
-
-When user returns after interruption:
-
-1. Ask if continuing previous workflow
-2. Request any completed artifacts
-3. Analyze provided artifacts
-4. Determine workflow position
-5. Suggest next appropriate step
-
-Example:
-
-```text
-User: I'm working on a new app. Here's my PRD and architecture doc.
-BMad: I see you have a PRD and architecture document. Based on these artifacts,
-      it looks like you're following the greenfield-fullstack workflow and have completed
-      stages 1-3. The next recommended step would be:
-
-      Stage 4: Validation & Refinement
-      - Load Sarah (Product Owner) to validate all artifacts
-
-      Would you like to continue with this workflow?
-```
-
-## Workflow Context Passing
-
-When transitioning between agents, pass:
-
-1. Previous artifacts created
-2. Current workflow stage
-3. Expected outputs
-4. Any decisions or constraints identified
-
-Example transition:
-
-```text
-BMad: Great! John has completed the PRD. According to the greenfield-fullstack workflow,
-      the next step is UX Strategy with Sally.
-
-      /ux-expert
-
-Sally: I see we're in the Product Planning stage of the greenfield-fullstack workflow.
-       I have access to:
-       - Project Brief from Mary
-       - PRD from John
-
-       Let's create the UX strategy and UI specifications. First, let me review
-       the PRD to understand the features we're designing for...
-```
+- Previous artifacts
+- Current workflow stage
+- Expected outputs
+- Decisions/constraints
 
 ## Multi-Path Workflows
 
-Some workflows may have multiple paths:
+Handle conditional paths by asking clarifying questions when needed.
 
-```yaml
-conditional_paths:
-  - condition: project_type == 'mobile'
-    next_stage: mobile-specific-design
-  - condition: project_type == 'web'
-    next_stage: web-architecture
-  - default: fullstack-architecture
-```
+## Best Practices
 
-Handle these by asking clarifying questions when needed.
+1. Show progress
+2. Explain transitions
+3. Preserve context
+4. Allow flexibility
+5. Track state
 
-## Workflow Best Practices
+## Agent Integration
 
-1. **Always show progress** - Users should know where they are
-2. **Explain transitions** - Why moving to next agent
-3. **Preserve context** - Pass relevant information forward
-4. **Allow flexibility** - Users can skip or modify steps
-5. **Track everything** - Maintain complete workflow state
-
-## Integration with Agents
-
-Each agent should be workflow-aware:
-
-- Know which workflow is active
-- Understand their role in the workflow
-- Access previous artifacts
-- Know expected outputs
-- Guide toward workflow goals
-
-This creates a seamless experience where the entire team works together toward the workflow's objectives.
+Agents should be workflow-aware: know active workflow, their role, access artifacts, understand expected outputs.
 ==================== END: utils#workflow-management ====================
 
 ==================== START: utils#template-format ====================
@@ -3733,13 +3579,9 @@ The story creation is successful when:
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
 
-## Context
-
-The BMAD Method uses various checklists to ensure quality and completeness of different artifacts. Each checklist contains embedded prompts and instructions to guide the LLM through thorough validation and advanced elicitation. The checklists automatically identify their required artifacts and guide the validation process.
-
 ## Available Checklists
 
-If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the bmad-core/checklists folder to select the appropriate one to run.
+If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
 
 ## Instructions
 
@@ -3748,7 +3590,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
    - If user or the task being run provides a checklist name:
      - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
      - If multiple matches found, ask user to clarify
-     - Load the appropriate checklist from bmad-core/checklists/
+     - Load the appropriate checklist from {root}/checklists/
    - If no checklist specified:
      - Ask the user which checklist they want to use
      - Present the available options from the files in the checklists folder

package/docs/working-in-the-brownfield.md

@@ -116,7 +116,7 @@ The analyst will generate comprehensive documentation of everything.
 
 #### Option A: Full Brownfield Workflow (Recommended for Major Changes)
 
-**1. Create Brownfield PRD**
+**1. Create Brownfield PRD**:
 
 ```bash
 @pm
@@ -143,7 +143,7 @@ The PM agent will:
 - "What are the critical constraints we must respect?"
 - "What is your timeline and team size?"
 
-**2. Create Brownfield Architecture**
+**2. Create Brownfield Architecture**:
 
 ```bash
 @architect

package/expansion-packs/bmad-2d-phaser-game-dev/config.yml

@@ -0,0 +1,5 @@
+name: bmad-2d-phaser-game-dev
+version: 1.1.0
+short-title: 2D game development with Phaser 3 & TypeScript
+description: 2D Game Development expansion pack for BMAD Method - Phaser 3 & TypeScript focused
+author: Brian (BMad)

package/expansion-packs/bmad-creator-tools/config.yml

@@ -0,0 +1,5 @@
+name: bmad-creator-tools
+version: 1.0.0
+short-title: Tools for creating BMAD framework components
+description: Tools for creating and extending BMAD framework components.
+author: Brian (BMad)

package/expansion-packs/{expansion-creator → bmad-creator-tools}/tasks/generate-expansion-pack.md

@@ -436,17 +436,17 @@ IMPORTANT: Work through plan.md checklist systematically!
 
 **Step 2: Copy Core Utilities**
 
-Before proceeding, copy these essential files from bmad-core:
+Before proceeding, copy these essential files from common:
 
 ```bash
 # Copy core task utilities
-cp bmad-core/tasks/create-doc.md expansion-packs/{pack-name}/tasks/
-cp bmad-core/tasks/execute-checklist.md expansion-packs/{pack-name}/tasks/
+cp common/tasks/create-doc.md expansion-packs/{pack-name}/tasks/
+cp common/tasks/execute-checklist.md expansion-packs/{pack-name}/tasks/
 
 # Copy core utility files
 mkdir -p expansion-packs/{pack-name}/utils
-cp bmad-core/utils/template-format.md expansion-packs/{pack-name}/utils/
-cp bmad-core/utils/workflow-management.md expansion-packs/{pack-name}/utils/
+cp common/utils/template-format.md expansion-packs/{pack-name}/utils/
+cp common/utils/workflow-management.md expansion-packs/{pack-name}/utils/
 ```
 
 **Step 3: Technical Implementation**

package/expansion-packs/bmad-infrastructure-devops/config.yml

@@ -0,0 +1,5 @@
+name: bmad-infrastructure-devops
+version: 1.0.0
+short-title: Infrastructure and DevOps capabilities
+description: This expansion pack extends BMAD Method with comprehensive infrastructure and DevOps capabilities. It's designed for teams that need to define, implement, and manage cloud infrastructure alongside their application development.
+author: Brian (BMad)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bmad-method",
-  "version": "4.17.0",
+  "version": "4.19.0",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "main": "tools/cli.js",
   "bin": {

package/test-ide-paths.js

@@ -0,0 +1,41 @@
+// Test script to verify IDE setup paths for expansion pack agents
+const path = require('path');
+const fs = require('fs-extra');
+
+// Simulate the findAgentPath logic
+function simulateFindAgentPath(agentId, installDir) {
+  const possiblePaths = [
+    path.join(installDir, ".bmad-core", "agents", `${agentId}.md`),
+    path.join(installDir, "agents", `${agentId}.md`),
+    // Expansion pack paths
+    path.join(installDir, ".bmad-2d-phaser-game-dev", "agents", `${agentId}.md`),
+    path.join(installDir, ".bmad-infrastructure-devops", "agents", `${agentId}.md`),
+    path.join(installDir, ".bmad-creator-tools", "agents", `${agentId}.md`)
+  ];
+  
+  // Simulate finding the agent in an expansion pack
+  if (agentId === 'game-developer') {
+    return path.join(installDir, ".bmad-2d-phaser-game-dev", "agents", `${agentId}.md`);
+  }
+  
+  // Default to core
+  return path.join(installDir, ".bmad-core", "agents", `${agentId}.md`);
+}
+
+// Test different scenarios
+const testDir = '/project';
+const agents = ['dev', 'game-developer', 'infra-devops-platform'];
+
+console.log('Testing IDE path references:\n');
+
+agents.forEach(agentId => {
+  const agentPath = simulateFindAgentPath(agentId, testDir);
+  const relativePath = path.relative(testDir, agentPath).replace(/\\/g, '/');
+  
+  console.log(`Agent: ${agentId}`);
+  console.log(`  Full path: ${agentPath}`);
+  console.log(`  Relative path: ${relativePath}`);
+  console.log(`  Roo customInstructions: CRITICAL Read the full YML from ${relativePath} ...`);
+  console.log(`  Cursor MDC reference: [${relativePath}](mdc:${relativePath})`);
+  console.log('');
+});

package/tools/builders/web-builder.js

@@ -9,8 +9,8 @@ class WebBuilder {
     this.resolver = new DependencyResolver(this.rootDir);
     this.templatePath = path.join(
       this.rootDir,
-      "bmad-core",
-      "utils",
+      "tools",
+      "md-assets",
       "web-agent-startup-instructions.md"
     );
   }
@@ -117,35 +117,39 @@ class WebBuilder {
     const yamlContent = yamlMatch[1];
     const yamlStartIndex = content.indexOf(yamlMatch[0]);
     const yamlEndIndex = yamlStartIndex + yamlMatch[0].length;
-    
+
     // Parse YAML and remove root and IDE-FILE-RESOLUTION properties
     try {
       const yaml = require("js-yaml");
       const parsed = yaml.load(yamlContent);
-      
+
       // Remove the properties if they exist at root level
       delete parsed.root;
-      delete parsed['IDE-FILE-RESOLUTION'];
-      delete parsed['REQUEST-RESOLUTION'];
-      
+      delete parsed["IDE-FILE-RESOLUTION"];
+      delete parsed["REQUEST-RESOLUTION"];
+
       // Also remove from activation-instructions if they exist
-      if (parsed['activation-instructions'] && Array.isArray(parsed['activation-instructions'])) {
-        parsed['activation-instructions'] = parsed['activation-instructions'].filter(instruction => {
-          return !instruction.startsWith('IDE-FILE-RESOLUTION:') && 
-                 !instruction.startsWith('REQUEST-RESOLUTION:');
-        });
+      if (parsed["activation-instructions"] && Array.isArray(parsed["activation-instructions"])) {
+        parsed["activation-instructions"] = parsed["activation-instructions"].filter(
+          (instruction) => {
+            return (
+              !instruction.startsWith("IDE-FILE-RESOLUTION:") &&
+              !instruction.startsWith("REQUEST-RESOLUTION:")
+            );
+          }
+        );
       }
-      
+
       // Reconstruct the YAML
       const cleanedYaml = yaml.dump(parsed, { lineWidth: -1 });
-      
+
       // Get the agent name from the YAML for the header
-      const agentName = parsed.agent?.id || 'agent';
-      
+      const agentName = parsed.agent?.id || "agent";
+
       // Build the new content with just the agent header and YAML
       const newHeader = `# ${agentName}\n\nCRITICAL: 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:\n\n`;
       const afterYaml = content.substring(yamlEndIndex);
-      
+
       return newHeader + "```yaml\n" + cleanedYaml.trim() + "\n```" + afterYaml;
     } catch (error) {
       console.warn("Failed to process agent YAML:", error.message);
@@ -156,12 +160,12 @@ class WebBuilder {
 
   formatSection(path, content) {
     const separator = "====================";
-    
+
     // Process agent content if this is an agent file
     if (path.startsWith("agents#")) {
       content = this.processAgentContent(content);
     }
-    
+
     return [
       `${separator} START: ${path} ${separator}`,
       content.trim(),
@@ -341,6 +345,28 @@ class WebBuilder {
                   }
                 }
 
+                // If not found in core, try common folder
+                if (!found) {
+                  for (const ext of extensions) {
+                    const commonPath = path.join(
+                      this.rootDir,
+                      "common",
+                      resourceType,
+                      `${resourceName}${ext}`
+                    );
+                    try {
+                      const commonContent = await fs.readFile(commonPath, "utf8");
+                      sections.push(
+                        this.formatSection(`${resourceType}#${resourceName}`, commonContent)
+                      );
+                      found = true;
+                      break;
+                    } catch (error) {
+                      // Not in common either, continue
+                    }
+                  }
+                }
+
                 if (!found) {
                   console.warn(
                     `    ⚠ Dependency ${resourceType}#${resourceName} not found in expansion pack or core`
@@ -516,6 +542,21 @@ class WebBuilder {
         }
       }
 
+      // If not found in core, try common folder
+      if (!found) {
+        for (const ext of extensions) {
+          const commonPath = path.join(this.rootDir, "common", dep.type, `${dep.name}${ext}`);
+          try {
+            const content = await fs.readFile(commonPath, "utf8");
+            sections.push(this.formatSection(key, content));
+            found = true;
+            break;
+          } catch (error) {
+            // Not in common either, continue
+          }
+        }
+      }
+
       if (!found) {
         console.warn(`    ⚠ Dependency ${key} not found in expansion pack or core`);
       }

package/tools/installer/config/ide-agent-config.yml

@@ -0,0 +1,58 @@
+# IDE-specific agent configurations
+# This file defines agent-specific settings for different IDEs
+
+# Roo Code file permissions
+# Each agent can have restricted file access based on regex patterns
+# If an agent is not listed here, it gets full edit access
+roo-permissions:
+  # Core agents
+  analyst:
+    fileRegex: "\\.(md|txt)$"
+    description: "Documentation and text files"
+  pm:
+    fileRegex: "\\.(md|txt)$"
+    description: "Product documentation"
+  architect:
+    fileRegex: "\\.(md|txt|yml|yaml|json)$"
+    description: "Architecture docs and configs"
+  qa:
+    fileRegex: "\\.(test|spec)\\.(js|ts|jsx|tsx)$|\\.md$"
+    description: "Test files and documentation"
+  ux-expert:
+    fileRegex: "\\.(md|css|scss|html|jsx|tsx)$"
+    description: "Design-related files"
+  po:
+    fileRegex: "\\.(md|txt)$"
+    description: "Story and requirement docs"
+  sm:
+    fileRegex: "\\.(md|txt)$"
+    description: "Process and planning docs"
+  # Expansion pack agents
+  game-designer:
+    fileRegex: "\\.(md|txt|json|yaml|yml)$"
+    description: "Game design documents and configs"
+  game-sm:
+    fileRegex: "\\.(md|txt)$"
+    description: "Game project management docs"
+
+# Cline agent ordering
+# Lower numbers appear first in the list
+# Agents not listed get order 99
+cline-order:
+  # Core agents
+  bmad-master: 1
+  bmad-orchestrator: 2
+  pm: 3
+  analyst: 4
+  architect: 5
+  po: 6
+  sm: 7
+  dev: 8
+  qa: 9
+  ux-expert: 10
+  # Expansion pack agents
+  bmad-the-creator: 11
+  game-designer: 12
+  game-developer: 13
+  game-sm: 14
+  infra-devops-platform: 15