bmad-method 4.37.0 → 4.39.1

package/expansion-packs/bmad-infrastructure-devops/templates/infrastructure-architecture-tmpl.yaml

@@ -27,18 +27,18 @@ sections:
   - id: initial-setup
     instruction: |
       Initial Setup
-      
+
       1. Replace {{project_name}} with the actual project name throughout the document
       2. Gather and review required inputs:
          - Product Requirements Document (PRD) - Required for business needs and scale requirements
          - Main System Architecture - Required for infrastructure dependencies
          - Technical Preferences/Tech Stack Document - Required for technology choices
          - PRD Technical Assumptions - Required for cross-referencing repository and service architecture
-      
+
       If any required documents are missing, ask user: "I need the following documents to create a comprehensive infrastructure architecture: [list missing]. Would you like to proceed with available information or provide the missing documents first?"
-      
+
       3. <critical_rule>Cross-reference with PRD Technical Assumptions to ensure infrastructure decisions align with repository and service architecture decisions made in the system architecture.</critical_rule>
-      
+
       Output file location: `docs/infrastructure-architecture.md`
 
   - id: infrastructure-overview
@@ -67,7 +67,7 @@ sections:
       - Repository Structure
       - State Management
       - Dependency Management
-      
+
       <critical_rule>All infrastructure must be defined as code. No manual resource creation in production environments.</critical_rule>
 
   - id: environment-configuration
@@ -103,7 +103,7 @@ sections:
     title: Network Architecture
     instruction: |
       Design network topology considering security zones, traffic patterns, and compliance requirements. Reference main architecture for service communication patterns.
-      
+
       Create Mermaid diagram showing:
       - VPC/Network structure
       - Security zones and boundaries
@@ -166,7 +166,7 @@ sections:
     title: Data Resources
     instruction: |
       Design data infrastructure based on data architecture from main system design. Consider data volumes, access patterns, compliance, and recovery requirements.
-      
+
       Create data flow diagram showing:
       - Database topology
       - Replication patterns
@@ -187,7 +187,7 @@ sections:
       - Data Encryption
       - Compliance Controls
       - Security Scanning & Monitoring
-      
+
       <critical_rule>Apply principle of least privilege for all access controls. Document all security exceptions with business justification.</critical_rule>
 
   - id: shared-responsibility
@@ -223,7 +223,7 @@ sections:
     title: CI/CD Pipeline
     instruction: |
       Design deployment pipeline that balances speed with safety. Include progressive deployment strategies and automated quality gates.
-      
+
       Create pipeline diagram showing:
       - Build stages
       - Test gates
@@ -254,7 +254,7 @@ sections:
       - Recovery Procedures
       - RTO & RPO Targets
       - DR Testing Approach
-      
+
       <critical_rule>DR procedures must be tested at least quarterly. Document test results and improvement actions.</critical_rule>
 
   - id: cost-optimization
@@ -296,15 +296,15 @@ sections:
     title: DevOps/Platform Feasibility Review
     instruction: |
       CRITICAL STEP - Present architectural blueprint summary to DevOps/Platform Engineering Agent for feasibility review. Request specific feedback on:
-      
+
       - **Operational Complexity:** Are the proposed patterns implementable with current tooling and expertise?
       - **Resource Constraints:** Do infrastructure requirements align with available resources and budgets?
       - **Security Implementation:** Are security patterns achievable with current security toolchain?
       - **Operational Overhead:** Will the proposed architecture create excessive operational burden?
       - **Technology Constraints:** Are selected technologies compatible with existing infrastructure?
-      
+
       Document all feasibility feedback and concerns raised. Iterate on architectural decisions based on operational constraints and feedback.
-      
+
       <critical_rule>Address all critical feasibility concerns before proceeding to final architecture documentation. If critical blockers identified, revise architecture before continuing.</critical_rule>
     sections:
       - id: feasibility-results
@@ -322,7 +322,7 @@ sections:
         title: Validation Framework
         content: |
           This infrastructure architecture will be validated using the comprehensive `infrastructure-checklist.md`, with particular focus on Section 12: Architecture Documentation Validation. The checklist ensures:
-          
+
           - Completeness of architecture documentation
           - Consistency with broader system architecture
           - Appropriate level of detail for different stakeholders
@@ -332,12 +332,12 @@ sections:
         title: Validation Process
         content: |
           The architecture documentation validation should be performed:
-          
+
           - After initial architecture development
           - After significant architecture changes
           - Before major implementation phases
           - During periodic architecture reviews
-          
+
           The Platform Engineer should use the infrastructure checklist to systematically validate all aspects of this architecture document.
 
   - id: implementation-handoff
@@ -348,7 +348,7 @@ sections:
         title: Architecture Decision Records (ADRs)
         content: |
           Create ADRs for key infrastructure decisions:
-          
+
           - Cloud provider selection rationale
           - Container orchestration platform choice
           - Networking architecture decisions
@@ -358,7 +358,7 @@ sections:
         title: Implementation Validation Criteria
         content: |
           Define specific criteria for validating correct implementation:
-          
+
           - Infrastructure as Code quality gates
           - Security compliance checkpoints
           - Performance benchmarks
@@ -418,7 +418,7 @@ sections:
     instruction: Final Review - Ensure all sections are complete and consistent. Verify feasibility review was conducted and all concerns addressed. Apply final validation against infrastructure checklist.
     content: |
       ---
-      
+
       _Document Version: 1.0_
       _Last Updated: {{current_date}}_
-      _Next Review: {{review_date}}_
+      _Next Review: {{review_date}}_

package/expansion-packs/bmad-infrastructure-devops/templates/infrastructure-platform-from-arch-tmpl.yaml

@@ -28,7 +28,7 @@ sections:
   - id: initial-setup
     instruction: |
       Initial Setup
-      
+
       1. Replace {{project_name}} with the actual project name throughout the document
       2. Gather and review required inputs:
          - **Infrastructure Architecture Document** (Primary input - REQUIRED)
@@ -37,10 +37,10 @@ sections:
          - Technology Stack Document
          - Infrastructure Checklist
          - NOTE: If Infrastructure Architecture Document is missing, HALT and request: "I need the Infrastructure Architecture Document to proceed with platform implementation. This document defines the infrastructure design that we'll be implementing."
-      
+
       3. Validate that the infrastructure architecture has been reviewed and approved
       4. <critical_rule>All platform implementation must align with the approved infrastructure architecture. Any deviations require architect approval.</critical_rule>
-      
+
       Output file location: `docs/platform-infrastructure/platform-implementation.md`
 
   - id: executive-summary
@@ -113,7 +113,7 @@ sections:
           # Example Terraform for VPC setup
           module "vpc" {
             source = "./modules/vpc"
-          
+
             cidr_block = "{{vpc_cidr}}"
             availability_zones = {{availability_zones}}
             public_subnets = {{public_subnets}}
@@ -508,7 +508,7 @@ sections:
           // K6 Load Test Example
           import http from 'k6/http';
           import { check } from 'k6';
-          
+
           export let options = {
             stages: [
               { duration: '5m', target: {{target_users}} },
@@ -622,8 +622,8 @@ sections:
     instruction: Final Review - Ensure all platform layers are properly implemented, integrated, and documented. Verify that the implementation fully supports the BMAD methodology and all agent workflows. Confirm successful validation against the infrastructure checklist.
     content: |
       ---
-      
+
       _Platform Version: 1.0_
       _Implementation Date: {{implementation_date}}_
       _Next Review: {{review_date}}_
-      _Approved by: {{architect_name}} (Architect), {{devops_name}} (DevOps/Platform Engineer)_
+      _Approved by: {{architect_name}} (Architect), {{devops_name}} (DevOps/Platform Engineer)_

package/package.json

@@ -1,7 +1,23 @@
 {
+  "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "4.37.0",
+  "version": "4.39.1",
   "description": "Breakthrough Method of Agile AI-driven Development",
+  "keywords": [
+    "agile",
+    "ai",
+    "orchestrator",
+    "development",
+    "methodology",
+    "agents",
+    "bmad"
+  ],
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/bmadcode/BMAD-METHOD.git"
+  },
+  "license": "MIT",
+  "author": "Brian (BMad) Madison",
   "main": "tools/cli.js",
   "bin": {
     "bmad": "tools/bmad-npx-wrapper.js",
@@ -11,27 +27,46 @@
     "build": "node tools/cli.js build",
     "build:agents": "node tools/cli.js build --agents-only",
     "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",
+    "format": "prettier --write \"**/*.{js,cjs,mjs,json,md,yaml}\"",
+    "format:check": "prettier --check \"**/*.{js,cjs,mjs,json,md,yaml}\"",
     "install:bmad": "node tools/installer/bin/bmad.js install",
-    "format": "prettier --write \"**/*.md\"",
-    "version:patch": "node tools/version-bump.js patch",
-    "version:minor": "node tools/version-bump.js minor",
-    "version:major": "node tools/version-bump.js major",
-    "version:expansion": "node tools/bump-expansion-version.js",
-    "version:expansion:set": "node tools/update-expansion-version.js",
+    "lint": "eslint . --ext .js,.cjs,.mjs,.yaml --max-warnings=0",
+    "lint:fix": "eslint . --ext .js,.cjs,.mjs,.yaml --fix",
+    "list:agents": "node tools/cli.js list:agents",
+    "prepare": "husky",
+    "preview:release": "node tools/preview-release-notes.js",
+    "release:major": "gh workflow run \"Manual Release\" -f version_bump=major",
+    "release:minor": "gh workflow run \"Manual Release\" -f version_bump=minor",
+    "release:patch": "gh workflow run \"Manual Release\" -f version_bump=patch",
+    "release:watch": "gh run watch",
+    "validate": "node tools/cli.js validate",
     "version:all": "node tools/bump-all-versions.js",
-    "version:all:minor": "node tools/bump-all-versions.js minor",
     "version:all:major": "node tools/bump-all-versions.js major",
+    "version:all:minor": "node tools/bump-all-versions.js minor",
     "version:all:patch": "node tools/bump-all-versions.js patch",
+    "version:expansion": "node tools/bump-expansion-version.js",
     "version:expansion:all": "node tools/bump-all-versions.js",
-    "version:expansion:all:minor": "node tools/bump-all-versions.js minor",
     "version:expansion:all:major": "node tools/bump-all-versions.js major",
+    "version:expansion:all:minor": "node tools/bump-all-versions.js minor",
     "version:expansion:all:patch": "node tools/bump-all-versions.js patch",
-    "release": "semantic-release",
-    "release:test": "semantic-release --dry-run --no-ci || echo 'Config test complete - authentication errors are expected locally'",
-    "prepare": "husky"
+    "version:expansion:set": "node tools/update-expansion-version.js",
+    "version:major": "node tools/version-bump.js major",
+    "version:minor": "node tools/version-bump.js minor",
+    "version:patch": "node tools/version-bump.js patch"
+  },
+  "lint-staged": {
+    "**/*.{js,cjs,mjs}": [
+      "eslint --fix --max-warnings=0",
+      "prettier --write"
+    ],
+    "**/*.yaml": [
+      "eslint --fix",
+      "prettier --write"
+    ],
+    "**/*.{json,md}": [
+      "prettier --write"
+    ]
   },
   "dependencies": {
     "@kayvan/markdown-tree-parser": "^1.5.0",
@@ -46,37 +81,25 @@
     "ora": "^5.4.1",
     "semver": "^7.6.3"
   },
-  "keywords": [
-    "agile",
-    "ai",
-    "orchestrator",
-    "development",
-    "methodology",
-    "agents",
-    "bmad"
-  ],
-  "author": "Brian (BMad) Madison",
-  "license": "MIT",
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/bmadcode/BMAD-METHOD.git"
-  },
-  "engines": {
-    "node": ">=20.0.0"
-  },
   "devDependencies": {
-    "@semantic-release/changelog": "^6.0.3",
-    "@semantic-release/git": "^10.0.1",
+    "@eslint/js": "^9.33.0",
+    "eslint": "^9.33.0",
+    "eslint-config-prettier": "^10.1.8",
+    "eslint-plugin-n": "^17.21.3",
+    "eslint-plugin-unicorn": "^60.0.0",
+    "eslint-plugin-yml": "^1.18.0",
     "husky": "^9.1.7",
     "jest": "^30.0.4",
     "lint-staged": "^16.1.1",
     "prettier": "^3.5.3",
-    "semantic-release": "^22.0.0",
+    "prettier-plugin-packagejson": "^2.5.19",
+    "yaml-eslint-parser": "^1.2.3",
     "yaml-lint": "^1.7.0"
   },
-  "lint-staged": {
-    "**/*.md": [
-      "prettier --write"
-    ]
+  "engines": {
+    "node": ">=20.10.0"
+  },
+  "publishConfig": {
+    "access": "public"
   }
 }

package/prettier.config.mjs

@@ -0,0 +1,32 @@
+export default {
+  $schema: 'https://json.schemastore.org/prettierrc',
+  printWidth: 100,
+  tabWidth: 2,
+  useTabs: false,
+  semi: true,
+  singleQuote: true,
+  trailingComma: 'all',
+  bracketSpacing: true,
+  arrowParens: 'always',
+  endOfLine: 'lf',
+  proseWrap: 'preserve',
+  overrides: [
+    {
+      files: ['*.md'],
+      options: { proseWrap: 'preserve' },
+    },
+    {
+      files: ['*.yaml'],
+      options: { singleQuote: false },
+    },
+    {
+      files: ['*.json', '*.jsonc'],
+      options: { singleQuote: false },
+    },
+    {
+      files: ['*.cjs'],
+      options: { parser: 'babel' },
+    },
+  ],
+  plugins: ['prettier-plugin-packagejson'],
+};

package/sync-version.sh

@@ -0,0 +1,23 @@
+#!/bin/bash
+
+# Sync local version with published npm version
+# Run this after a release if the version bump commit didn't sync automatically
+
+echo "🔄 Syncing local version with npm..."
+
+# Get the latest published version
+VERSION=$(npm view bmad-method@latest version)
+echo "📦 Latest published version: $VERSION"
+
+# Update package.json
+npm version $VERSION --no-git-tag-version
+
+# Update installer package.json
+sed -i '' 's/"version": ".*"/"version": "'$VERSION'"/' tools/installer/package.json
+
+# Commit and push
+git add package.json tools/installer/package.json
+git commit -m "sync: update to published version $VERSION"
+git push
+
+echo "✅ Synced to version $VERSION"

package/tools/bmad-npx-wrapper.js

@@ -5,30 +5,30 @@
  * This file ensures proper execution when run via npx from GitHub
  */
 
-const { execSync } = require('child_process');
-const path = require('path');
-const fs = require('fs');
+const { execSync } = require('node:child_process');
+const path = require('node:path');
+const fs = require('node:fs');
 
 // Check if we're running in an npx temporary directory
 const isNpxExecution = __dirname.includes('_npx') || __dirname.includes('.npm');
 
 // If running via npx, we need to handle things differently
 if (isNpxExecution) {
-  const args = process.argv.slice(2);
-  
+  const arguments_ = process.argv.slice(2);
+
   // Use the installer for all commands
   const bmadScriptPath = path.join(__dirname, 'installer', 'bin', 'bmad.js');
-  
+
   if (!fs.existsSync(bmadScriptPath)) {
     console.error('Error: Could not find bmad.js at', bmadScriptPath);
     console.error('Current directory:', __dirname);
     process.exit(1);
   }
-  
+
   try {
-    execSync(`node "${bmadScriptPath}" ${args.join(' ')}`, {
+    execSync(`node "${bmadScriptPath}" ${arguments_.join(' ')}`, {
       stdio: 'inherit',
-      cwd: path.dirname(__dirname)
+      cwd: path.dirname(__dirname),
     });
   } catch (error) {
     process.exit(error.status || 1);
@@ -36,4 +36,4 @@ if (isNpxExecution) {
 } else {
   // Local execution - use installer for all commands
   require('./installer/bin/bmad.js');
-}
+}