bmad-method 4.31.0 → 4.33.0

package/expansion-packs/bmad-2d-unity-game-dev/templates/game-story-tmpl.yaml

@@ -1,7 +1,7 @@
 template:
-  id: game-story-template-v2
+  id: game-story-template-v3
   name: Game Development Story
-  version: 2.0
+  version: 3.0
   output:
     format: markdown
     filename: "stories/{{epic_name}}/{{story_id}}-{{story_name}}.md"
@@ -49,9 +49,9 @@ sections:
         title: Technical Requirements
         type: checklist
         items:
-          - "Code follows C# best practices"
-          - "Maintains stable frame rate on target devices"
-          - "No memory leaks or performance degradation"
+          - Code follows C# best practices
+          - Maintains stable frame rate on target devices
+          - No memory leaks or performance degradation
           - "{{specific_technical_requirement}}"
       - id: game-design-requirements
         title: Game Design Requirements
@@ -227,13 +227,13 @@ sections:
     instruction: Checklist that must be completed before the story is considered finished
     type: checklist
     items:
-      - "All acceptance criteria met"
-      - "Code reviewed and approved"
-      - "Unit tests written and passing"
-      - "Integration tests passing"
-      - "Performance targets met"
-      - "No C# compiler errors or warnings"
-      - "Documentation updated"
+      - All acceptance criteria met
+      - Code reviewed and approved
+      - Unit tests written and passing
+      - Integration tests passing
+      - Performance targets met
+      - No C# compiler errors or warnings
+      - Documentation updated
       - "{{game_specific_dod_item}}"
 
   - id: notes

package/expansion-packs/bmad-2d-unity-game-dev/templates/level-design-doc-tmpl.yaml

@@ -1,10 +1,10 @@
 template:
   id: level-design-doc-template-v2
   name: Level Design Document
-  version: 2.0
+  version: 2.1
   output:
     format: markdown
-    filename: "docs/{{game_name}}-level-design-document.md"
+    filename: docs/level-design-document.md
     title: "{{game_title}} Level Design Document"
 
 workflow:
@@ -371,19 +371,19 @@ sections:
             title: Playtesting Checklist
             type: checklist
             items:
-              - "Level completes within target time range"
-              - "All mechanics function correctly"
-              - "Difficulty feels appropriate for level category"
-              - "Player guidance is clear and effective"
-              - "No exploits or sequence breaks (unless intended)"
+              - Level completes within target time range
+              - All mechanics function correctly
+              - Difficulty feels appropriate for level category
+              - Player guidance is clear and effective
+              - No exploits or sequence breaks (unless intended)
           - id: player-experience-testing
             title: Player Experience Testing
             type: checklist
             items:
-              - "Tutorial levels teach effectively"
-              - "Challenge feels fair and rewarding"
-              - "Flow and pacing maintain engagement"
-              - "Audio and visual feedback support gameplay"
+              - Tutorial levels teach effectively
+              - Challenge feels fair and rewarding
+              - Flow and pacing maintain engagement
+              - Audio and visual feedback support gameplay
       - id: balance-validation
         title: Balance Validation
         template: |

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

@@ -1,5 +1,5 @@
 name: bmad-infrastructure-devops
-version: 1.10.0
+version: 1.11.0
 short-title: Infrastructure DevOps Pack
 description: >-
   This expansion pack extends BMad Method with comprehensive infrastructure and

package/expansion-packs/bmad-infrastructure-devops/data/bmad-kb.md

@@ -247,17 +247,14 @@ A comprehensive 16-section checklist covering:
 ### Common Issues
 
 1. **Infrastructure Drift**
-
    - Solution: Implement drift detection in IaC pipelines
    - Prevention: Restrict manual changes, enforce GitOps
 
 2. **Cost Overruns**
-
    - Solution: Implement cost monitoring and alerts
    - Prevention: Resource tagging, budget limits
 
 3. **Performance Problems**
-
    - Solution: Review monitoring data, scale resources
    - Prevention: Load testing, capacity planning
 

package/expansion-packs/bmad-infrastructure-devops/tasks/review-infrastructure.md

@@ -32,7 +32,6 @@ To conduct a thorough review of existing infrastructure to identify improvement
 ### 3. Conduct Systematic Review
 
 - **If "Incremental Mode" was selected:**
-
   - For each section of the infrastructure checklist:
     - **a. Present Section Focus:** Explain what aspects of infrastructure this section reviews
     - **b. Work Through Items:** Examine each checklist item against current infrastructure

package/expansion-packs/bmad-infrastructure-devops/tasks/validate-infrastructure.md

@@ -55,7 +55,6 @@ To comprehensively validate platform infrastructure changes against security, re
 ### 4. Execute Comprehensive Platform Validation Process
 
 - **If "Incremental Mode" was selected:**
-
   - For each section of the infrastructure checklist (Sections 1-16):
     - **a. Present Section Purpose:** Explain what this section validates and why it's important for platform operations
     - **b. Work Through Items:** Present each checklist item, guide the user through validation, and document compliance or gaps

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bmad-method",
-  "version": "4.31.0",
+  "version": "4.33.0",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "main": "tools/cli.js",
   "bin": {
@@ -13,6 +13,7 @@
     "build:teams": "node tools/cli.js build --teams-only",
     "list:agents": "node tools/cli.js list:agents",
     "validate": "node tools/cli.js validate",
+    "flatten": "node tools/flattener/main.js",
     "install:bmad": "node tools/installer/bin/bmad.js install",
     "format": "prettier --write \"**/*.md\"",
     "version:patch": "node tools/version-bump.js patch",
@@ -41,6 +42,7 @@
     "glob": "^11.0.3",
     "inquirer": "^8.2.6",
     "js-yaml": "^4.1.0",
+    "minimatch": "^10.0.3",
     "ora": "^5.4.1"
   },
   "keywords": [
@@ -65,6 +67,7 @@
     "@semantic-release/changelog": "^6.0.3",
     "@semantic-release/git": "^10.0.1",
     "husky": "^9.1.7",
+    "jest": "^30.0.4",
     "lint-staged": "^16.1.1",
     "prettier": "^3.5.3",
     "semantic-release": "^22.0.0",

package/tools/bmad-npx-wrapper.js

@@ -14,28 +14,26 @@ const isNpxExecution = __dirname.includes('_npx') || __dirname.includes('.npm');
 
 // If running via npx, we need to handle things differently
 if (isNpxExecution) {
-  // The actual bmad.js is in installer/bin/ (relative to tools directory)
+  const args = process.argv.slice(2);
+  
+  // Use the installer for all commands
   const bmadScriptPath = path.join(__dirname, 'installer', 'bin', 'bmad.js');
   
-  // Verify the file exists
   if (!fs.existsSync(bmadScriptPath)) {
     console.error('Error: Could not find bmad.js at', bmadScriptPath);
     console.error('Current directory:', __dirname);
     process.exit(1);
   }
   
-  // Execute with proper working directory
   try {
-    execSync(`node "${bmadScriptPath}" ${process.argv.slice(2).join(' ')}`, {
+    execSync(`node "${bmadScriptPath}" ${args.join(' ')}`, {
       stdio: 'inherit',
       cwd: path.dirname(__dirname)
     });
   } catch (error) {
-    // execSync will throw if the command exits with non-zero
-    // But the stdio is inherited, so the error is already displayed
     process.exit(error.status || 1);
   }
 } else {
-  // Local execution - just require the installer directly
+  // Local execution - use installer for all commands
   require('./installer/bin/bmad.js');
 }