bmad-method 4.20.0 → 4.21.0

package/CHANGELOG.md

@@ -1,3 +1,15 @@
+# [4.21.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.20.0...v4.21.0) (2025-06-30)
+
+
+### Bug Fixes
+
+* remove unneeded files ([c48f200](https://github.com/bmadcode/BMAD-METHOD/commit/c48f200727384f37a42f4c6b1a946cb90f2445fe))
+
+
+### Features
+
+* massive installer improvement update ([c151bda](https://github.com/bmadcode/BMAD-METHOD/commit/c151bda93833aa310ccc7c0eabcf483376f9e82a))
+
 # [4.20.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.19.2...v4.20.0) (2025-06-29)
 
 

package/CONTRIBUTING.md

@@ -8,6 +8,11 @@ Thank you for considering contributing to this project! This document outlines t
 
 Also note, we use the discussions feature in GitHub to have a community to discuss potential ideas, uses, additions and enhancements.
 
+💬 **Discord Community**: Join our [Discord server](https://discord.gg/g6ypHytrCB) for real-time discussions:
+
+- **#general-dev** - Technical discussions, feature ideas, and development questions
+- **#bugs-issues** - Bug reports and issue discussions
+
 ## Code of Conduct
 
 By participating in this project, you agree to abide by our Code of Conduct. Please read it before participating.
@@ -16,16 +21,35 @@ By participating in this project, you agree to abide by our Code of Conduct. Ple
 
 ### Reporting Bugs
 
-- Check if the bug has already been reported in the Issues section
-- Include detailed steps to reproduce the bug
-- Include any relevant logs or screenshots
+1. **Check existing issues** first to avoid duplicates
+2. **Use the bug report template** when creating a new issue - it will guide you through providing:
+   - Clear bug description
+   - Steps to reproduce
+   - Expected vs actual behavior
+   - Model/IDE/BMad version details
+   - Screenshots or links if applicable
+3. **Consider discussing in Discord** (#bugs-issues channel) for quick help
+4. **Indicate if you're working on a fix** to avoid duplicate efforts
 
 ### Suggesting Features
 
-- Check if the feature has already been suggested in the Issues section, and consider using the discussions tab in GitHub also. Explain the feature in detail and why it would be valuable.
+1. **Discuss first in Discord** (#general-dev channel) - the feature request template asks if you've done this
+2. **Check existing issues and discussions** to avoid duplicates
+3. **Use the feature request template** when creating an issue - it will guide you through:
+   - Confirming Discord discussion
+   - Describing the problem it solves
+   - Explaining your solution
+   - Listing alternatives considered
+4. **Be specific** about why this feature would benefit the BMad community
 
 ### Pull Request Process
 
+⚠️ **Before starting work:**
+
+1. **For bugs**: Check if an issue exists (create one using the bug template if not)
+2. **For features**: Ensure you've discussed in Discord (#general-dev) AND created a feature request issue
+3. **For large changes**: Always open an issue first to discuss alignment
+
 Please only propose small granular commits! If its large or significant, please discuss in the discussions tab and open up an issue first. I do not want you to waste your time on a potentially very large PR to have it rejected because it is not aligned or deviates from other planned changes. Communicate and lets work together to build and improve this great community project!
 
 **Important**: All contributions must align with our [Guiding Principles](GUIDING-PRINCIPLES.md). Key points:
@@ -95,6 +119,15 @@ Example breakdown:
 6. Push to your branch (`git push origin feature/your-feature-name`)
 7. Open a Pull Request against the main branch
 
+## Issue Templates
+
+We use GitHub issue templates to ensure all necessary information is provided:
+
+- **Bug Reports**: Automatically guides you through providing reproduction steps, environment details, and expected behavior
+- **Feature Requests**: Requires Discord discussion confirmation and asks for problem/solution descriptions
+
+Using these templates helps maintainers understand and address your contribution faster.
+
 ## Pull Request Description Guidelines
 
 Keep PR descriptions short and to the point following this template:
@@ -111,6 +144,7 @@ Keep your PR description concise and focused. Use this template:
 ## Why
 
 [1-2 sentences explaining WHY this change is needed]
+Fixes #[issue number] (if applicable)
 
 ## How
 

package/bmad-core/core-config.yml

@@ -1,3 +1,4 @@
+version: 4.20.1
 markdownExploder: true
 prd:
   prdFile: docs/prd.md

package/dist/agents/dev.txt

@@ -83,7 +83,7 @@ task-execution:
   updates-ONLY:
     - 'Checkboxes: [ ] not started | [-] in progress | [x] complete'
     - 'Debug Log: | Task | File | Change | Reverted? |'
-    - 'Completion Notes: Deviations only, <50 words'
+    - 'Completion Notes: Deviations from AC or tasks during execution only, <50 words'
     - 'Change Log: Requirement changes only'
     - 'File List: CRITICAL - Maintain complete list of ALL files created/modified during implementation'
   blocking: Unapproved deps | Ambiguous after story check | 3 failures | Missing config | Failing validations

package/dist/teams/team-all.txt

@@ -353,7 +353,7 @@ task-execution:
   updates-ONLY:
     - 'Checkboxes: [ ] not started | [-] in progress | [x] complete'
     - 'Debug Log: | Task | File | Change | Reverted? |'
-    - 'Completion Notes: Deviations only, <50 words'
+    - 'Completion Notes: Deviations from AC or tasks during execution only, <50 words'
     - 'Change Log: Requirement changes only'
     - 'File List: CRITICAL - Maintain complete list of ALL files created/modified during implementation'
   blocking: Unapproved deps | Ambiguous after story check | 3 failures | Missing config | Failing validations

package/dist/teams/team-ide-minimal.txt

@@ -335,7 +335,7 @@ task-execution:
   updates-ONLY:
     - 'Checkboxes: [ ] not started | [-] in progress | [x] complete'
     - 'Debug Log: | Task | File | Change | Reverted? |'
-    - 'Completion Notes: Deviations only, <50 words'
+    - 'Completion Notes: Deviations from AC or tasks during execution only, <50 words'
     - 'Change Log: Requirement changes only'
     - 'File List: CRITICAL - Maintain complete list of ALL files created/modified during implementation'
   blocking: Unapproved deps | Ambiguous after story check | 3 failures | Missing config | Failing validations

package/docs/how-to-contribute-with-pull-requests.md

@@ -8,7 +8,15 @@ A pull request (PR) is how you propose changes to a project on GitHub. Think of
 
 ## Before You Start
 
-⚠️ **Important**: Please keep your contributions small and focused! We prefer many small, clear changes rather than one massive change. If you're planning something big, please [open an issue](https://github.com/bmadcode/bmad-method/issues) or start a [discussion](https://github.com/bmadcode/bmad-method/discussions) first.
+⚠️ **Important**: Please keep your contributions small and focused! We prefer many small, clear changes rather than one massive change.
+
+**Required before submitting PRs:**
+
+- **For bug fixes**: Create an issue using the [bug report template](https://github.com/bmadcode/bmad-method/issues/new?template=bug_report.md)
+- **For new features**:
+  1. Discuss in Discord [#general-dev channel](https://discord.gg/g6ypHytrCB)
+  2. Create an issue using the [feature request template](https://github.com/bmadcode/bmad-method/issues/new?template=feature_request.md)
+- **For large changes**: Always open an issue first to discuss alignment
 
 ## Step-by-Step Guide
 
@@ -82,9 +90,15 @@ git push origin fix/typo-in-readme
 
 1. Go to your fork on GitHub
 2. You'll see a green "Compare & pull request" button - click it
-3. Fill out the PR template:
-   - **Title**: Clear, descriptive title
-   - **Description**: Explain what you changed and why
+3. Select the correct target branch:
+   - **`next` branch** for most contributions (features, docs, enhancements)
+   - **`main` branch** only for critical fixes
+4. Fill out the PR description using the template in CONTRIBUTING.md:
+   - **What**: 1-2 sentences describing what changed
+   - **Why**: 1-2 sentences explaining why
+   - **How**: 2-3 bullets on implementation
+   - **Testing**: How you tested
+5. Reference the related issue number (e.g., "Fixes #123")
 
 ### 8. Wait for Review
 
@@ -117,9 +131,12 @@ git push origin fix/typo-in-readme
 
 ## Need Help?
 
-- 💬 Join our [Discord Community](https://discord.gg/g6ypHytrCB) for real-time help
-- 💬 Ask questions in [Discussions](https://github.com/bmadcode/bmad-method/discussions)
-- 🐛 Report bugs in [Issues](https://github.com/bmadcode/bmad-method/issues)
+- 💬 Join our [Discord Community](https://discord.gg/g6ypHytrCB) for real-time help:
+  - **#general-dev** - Technical questions and feature discussions
+  - **#bugs-issues** - Get help with bugs before filing issues
+- 💬 Ask questions in [GitHub Discussions](https://github.com/bmadcode/bmad-method/discussions)
+- 🐛 Report bugs using the [bug report template](https://github.com/bmadcode/bmad-method/issues/new?template=bug_report.md)
+- 💡 Suggest features using the [feature request template](https://github.com/bmadcode/bmad-method/issues/new?template=feature_request.md)
 - 📖 Read the full [Contributing Guidelines](../CONTRIBUTING.md)
 
 ## Example: Good vs Bad PRs

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

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

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

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

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

@@ -1,5 +1,8 @@
 name: bmad-infrastructure-devops
-version: 1.0.0
+version: 1.0.2
 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.
+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.20.0",
+  "version": "4.21.0",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "main": "tools/cli.js",
   "bin": {
@@ -18,6 +18,20 @@
     "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:core": "node tools/bump-core-version.js",
+    "version:core:major": "node tools/bump-core-version.js major",
+    "version:core:minor": "node tools/bump-core-version.js minor",
+    "version:core:patch": "node tools/bump-core-version.js patch",
+    "version:expansion": "node tools/bump-expansion-version.js",
+    "version:expansion:set": "node tools/update-expansion-version.js",
+    "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:patch": "node tools/bump-all-versions.js patch",
+    "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: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"

package/tools/bump-all-versions.js

@@ -0,0 +1,107 @@
+#!/usr/bin/env node
+
+const fs = require('fs');
+const path = require('path');
+const yaml = require('js-yaml');
+
+const args = process.argv.slice(2);
+const bumpType = args[0] || 'minor'; // default to minor
+
+if (!['major', 'minor', 'patch'].includes(bumpType)) {
+  console.log('Usage: node bump-all-versions.js [major|minor|patch]');
+  console.log('Default: minor');
+  process.exit(1);
+}
+
+function bumpVersion(currentVersion, type) {
+  const [major, minor, patch] = currentVersion.split('.').map(Number);
+  
+  switch (type) {
+    case 'major':
+      return `${major + 1}.0.0`;
+    case 'minor':
+      return `${major}.${minor + 1}.0`;
+    case 'patch':
+      return `${major}.${minor}.${patch + 1}`;
+    default:
+      return currentVersion;
+  }
+}
+
+async function bumpAllVersions() {
+  const updatedItems = [];
+  
+  // First, bump the core version
+  const coreConfigPath = path.join(__dirname, '..', 'bmad-core', 'core-config.yml');
+  try {
+    const coreConfigContent = fs.readFileSync(coreConfigPath, 'utf8');
+    const coreConfig = yaml.load(coreConfigContent);
+    const oldCoreVersion = coreConfig.version || '1.0.0';
+    const newCoreVersion = bumpVersion(oldCoreVersion, bumpType);
+    
+    coreConfig.version = newCoreVersion;
+    
+    const updatedCoreYaml = yaml.dump(coreConfig, { indent: 2 });
+    fs.writeFileSync(coreConfigPath, updatedCoreYaml);
+    
+    updatedItems.push({ type: 'core', name: 'BMad Core', oldVersion: oldCoreVersion, newVersion: newCoreVersion });
+    console.log(`✓ BMad Core: ${oldCoreVersion} → ${newCoreVersion}`);
+  } catch (error) {
+    console.error(`✗ Failed to update BMad Core: ${error.message}`);
+  }
+  
+  // Then, bump all expansion packs
+  const expansionPacksDir = path.join(__dirname, '..', 'expansion-packs');
+  
+  try {
+    const entries = fs.readdirSync(expansionPacksDir, { withFileTypes: true });
+    
+    for (const entry of entries) {
+      if (entry.isDirectory() && !entry.name.startsWith('.') && entry.name !== 'README.md') {
+        const packId = entry.name;
+        const configPath = path.join(expansionPacksDir, packId, 'config.yml');
+        
+        if (fs.existsSync(configPath)) {
+          try {
+            const configContent = fs.readFileSync(configPath, 'utf8');
+            const config = yaml.load(configContent);
+            const oldVersion = config.version || '1.0.0';
+            const newVersion = bumpVersion(oldVersion, bumpType);
+            
+            config.version = newVersion;
+            
+            const updatedYaml = yaml.dump(config, { indent: 2 });
+            fs.writeFileSync(configPath, updatedYaml);
+            
+            updatedItems.push({ type: 'expansion', name: packId, oldVersion, newVersion });
+            console.log(`✓ ${packId}: ${oldVersion} → ${newVersion}`);
+            
+          } catch (error) {
+            console.error(`✗ Failed to update ${packId}: ${error.message}`);
+          }
+        }
+      }
+    }
+    
+    if (updatedItems.length > 0) {
+      const coreCount = updatedItems.filter(i => i.type === 'core').length;
+      const expansionCount = updatedItems.filter(i => i.type === 'expansion').length;
+      
+      console.log(`\n✓ Successfully bumped ${updatedItems.length} item(s) with ${bumpType} version bump`);
+      if (coreCount > 0) console.log(`  - ${coreCount} core`);
+      if (expansionCount > 0) console.log(`  - ${expansionCount} expansion pack(s)`);
+      
+      console.log('\nNext steps:');
+      console.log('1. Test the changes');
+      console.log('2. Commit: git add -A && git commit -m "chore: bump all versions (' + bumpType + ')"');
+    } else {
+      console.log('No items found to update');
+    }
+    
+  } catch (error) {
+    console.error('Error reading expansion packs directory:', error.message);
+    process.exit(1);
+  }
+}
+
+bumpAllVersions();

package/tools/bump-core-version.js

@@ -0,0 +1,57 @@
+#!/usr/bin/env node
+
+const fs = require('fs');
+const path = require('path');
+const yaml = require('js-yaml');
+
+const args = process.argv.slice(2);
+const bumpType = args[0] || 'minor'; // default to minor
+
+if (!['major', 'minor', 'patch'].includes(bumpType)) {
+  console.log('Usage: node bump-core-version.js [major|minor|patch]');
+  console.log('Default: minor');
+  process.exit(1);
+}
+
+function bumpVersion(currentVersion, type) {
+  const [major, minor, patch] = currentVersion.split('.').map(Number);
+  
+  switch (type) {
+    case 'major':
+      return `${major + 1}.0.0`;
+    case 'minor':
+      return `${major}.${minor + 1}.0`;
+    case 'patch':
+      return `${major}.${minor}.${patch + 1}`;
+    default:
+      return currentVersion;
+  }
+}
+
+async function bumpCoreVersion() {
+  try {
+    const coreConfigPath = path.join(__dirname, '..', 'bmad-core', 'core-config.yml');
+    
+    const coreConfigContent = fs.readFileSync(coreConfigPath, 'utf8');
+    const coreConfig = yaml.load(coreConfigContent);
+    const oldVersion = coreConfig.version || '1.0.0';
+    const newVersion = bumpVersion(oldVersion, bumpType);
+    
+    coreConfig.version = newVersion;
+    
+    const updatedYaml = yaml.dump(coreConfig, { indent: 2 });
+    fs.writeFileSync(coreConfigPath, updatedYaml);
+    
+    console.log(`✓ BMad Core: ${oldVersion} → ${newVersion}`);
+    console.log(`\n✓ Successfully bumped BMad Core with ${bumpType} version bump`);
+    console.log('\nNext steps:');
+    console.log('1. Test the changes');
+    console.log('2. Commit: git add -A && git commit -m "chore: bump core version (' + bumpType + ')"');
+    
+  } catch (error) {
+    console.error('Error updating core version:', error.message);
+    process.exit(1);
+  }
+}
+
+bumpCoreVersion();

package/tools/bump-expansion-version.js

@@ -0,0 +1,78 @@
+#!/usr/bin/env node
+
+const fs = require('fs');
+const path = require('path');
+const yaml = require('js-yaml');
+
+const args = process.argv.slice(2);
+
+if (args.length < 1 || args.length > 2) {
+  console.log('Usage: node bump-expansion-version.js <expansion-pack-id> [major|minor|patch]');
+  console.log('Default: minor');
+  console.log('Example: node bump-expansion-version.js bmad-creator-tools patch');
+  process.exit(1);
+}
+
+const packId = args[0];
+const bumpType = args[1] || 'minor'; // default to minor
+
+if (!['major', 'minor', 'patch'].includes(bumpType)) {
+  console.error('Error: Bump type must be major, minor, or patch');
+  process.exit(1);
+}
+
+function bumpVersion(currentVersion, type) {
+  const [major, minor, patch] = currentVersion.split('.').map(Number);
+  
+  switch (type) {
+    case 'major':
+      return `${major + 1}.0.0`;
+    case 'minor':
+      return `${major}.${minor + 1}.0`;
+    case 'patch':
+      return `${major}.${minor}.${patch + 1}`;
+    default:
+      return currentVersion;
+  }
+}
+
+async function updateVersion() {
+  try {
+    const configPath = path.join(__dirname, '..', 'expansion-packs', packId, 'config.yml');
+    
+    if (!fs.existsSync(configPath)) {
+      console.error(`Error: Expansion pack '${packId}' not found`);
+      console.log('\nAvailable expansion packs:');
+      const expansionPacksDir = path.join(__dirname, '..', 'expansion-packs');
+      const entries = fs.readdirSync(expansionPacksDir, { withFileTypes: true });
+      entries.forEach(entry => {
+        if (entry.isDirectory() && !entry.name.startsWith('.')) {
+          console.log(`  - ${entry.name}`);
+        }
+      });
+      process.exit(1);
+    }
+    
+    const configContent = fs.readFileSync(configPath, 'utf8');
+    const config = yaml.load(configContent);
+    const oldVersion = config.version || '1.0.0';
+    const newVersion = bumpVersion(oldVersion, bumpType);
+    
+    config.version = newVersion;
+    
+    const updatedYaml = yaml.dump(config, { indent: 2 });
+    fs.writeFileSync(configPath, updatedYaml);
+    
+    console.log(`✓ ${packId}: ${oldVersion} → ${newVersion}`);
+    console.log(`\n✓ Successfully bumped ${packId} with ${bumpType} version bump`);
+    console.log('\nNext steps:');
+    console.log('1. Test the changes');
+    console.log('2. Commit: git add -A && git commit -m "chore: bump ' + packId + ' version (' + bumpType + ')"');
+    
+  } catch (error) {
+    console.error('Error updating version:', error.message);
+    process.exit(1);
+  }
+}
+
+updateVersion();