bmad-method 4.41.0 → 4.43.0

package/dist/teams/team-fullstack.txt

@@ -902,6 +902,7 @@ 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.
 
@@ -9252,7 +9253,7 @@ workflow:
         - Dev Agent (New Chat): Address remaining items
         - Return to QA for final approval
 
-    - repeat_development_cycle:
+    - step: repeat_development_cycle
       action: continue_for_all_stories
       notes: |
         Repeat story cycle (SM → Dev → QA) for all epic stories
@@ -9269,7 +9270,7 @@ workflow:
         - Validate epic was completed correctly
         - Document learnings and improvements
 
-    - workflow_end:
+    - step: workflow_end
       action: project_complete
       notes: |
         All stories implemented and reviewed!
@@ -9499,7 +9500,7 @@ workflow:
         - Dev Agent (New Chat): Address remaining items
         - Return to QA for final approval
 
-    - repeat_development_cycle:
+    - step: repeat_development_cycle
       action: continue_for_all_stories
       notes: |
         Repeat story cycle (SM → Dev → QA) for all epic stories
@@ -9516,7 +9517,7 @@ workflow:
         - Validate epic was completed correctly
         - Document learnings and improvements
 
-    - workflow_end:
+    - step: workflow_end
       action: project_complete
       notes: |
         All stories implemented and reviewed!
@@ -9697,7 +9698,7 @@ workflow:
         - Dev Agent (New Chat): Address remaining items
         - Return to QA for final approval
 
-    - repeat_development_cycle:
+    - step: repeat_development_cycle
       action: continue_for_all_stories
       notes: |
         Repeat story cycle (SM → Dev → QA) for all epic stories
@@ -9714,7 +9715,7 @@ workflow:
         - Validate epic was completed correctly
         - Document learnings and improvements
 
-    - workflow_end:
+    - step: workflow_end
       action: project_complete
       notes: |
         All stories implemented and reviewed!
@@ -9850,12 +9851,12 @@ workflow:
       condition: po_checklist_issues
       notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder."
 
-    - project_setup_guidance:
+    - step: project_setup_guidance
       action: guide_project_structure
       condition: user_has_generated_ui
       notes: "If user generated UI with v0/Lovable: For polyrepo setup, place downloaded project in separate frontend repo alongside backend repo. For monorepo, place in apps/web or packages/frontend directory. Review architecture document for specific guidance."
 
-    - development_order_guidance:
+    - step: development_order_guidance
       action: guide_development_sequence
       notes: "Based on PRD stories: If stories are frontend-heavy, start with frontend project/directory first. If backend-heavy or API-first, start with backend. For tightly coupled features, follow story sequence in monorepo setup. Reference sharded PRD epics for development order."
 
@@ -9923,7 +9924,7 @@ workflow:
         - Dev Agent (New Chat): Address remaining items
         - Return to QA for final approval
 
-    - repeat_development_cycle:
+    - step: repeat_development_cycle
       action: continue_for_all_stories
       notes: |
         Repeat story cycle (SM → Dev → QA) for all epic stories
@@ -9940,7 +9941,7 @@ workflow:
         - Validate epic was completed correctly
         - Document learnings and improvements
 
-    - workflow_end:
+    - step: workflow_end
       action: project_complete
       notes: |
         All stories implemented and reviewed!
@@ -10143,7 +10144,7 @@ workflow:
         - Dev Agent (New Chat): Address remaining items
         - Return to QA for final approval
 
-    - repeat_development_cycle:
+    - step: repeat_development_cycle
       action: continue_for_all_stories
       notes: |
         Repeat story cycle (SM → Dev → QA) for all epic stories
@@ -10160,7 +10161,7 @@ workflow:
         - Validate epic was completed correctly
         - Document learnings and improvements
 
-    - workflow_end:
+    - step: workflow_end
       action: project_complete
       notes: |
         All stories implemented and reviewed!
@@ -10303,7 +10304,7 @@ workflow:
       condition: po_checklist_issues
       notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder."
 
-    - project_setup_guidance:
+    - step: project_setup_guidance
       action: guide_project_structure
       condition: user_has_generated_ui
       notes: "If user generated UI with v0/Lovable: For polyrepo setup, place downloaded project in separate frontend repo. For monorepo, place in apps/web or frontend/ directory. Review architecture document for specific guidance."
@@ -10372,7 +10373,7 @@ workflow:
         - Dev Agent (New Chat): Address remaining items
         - Return to QA for final approval
 
-    - repeat_development_cycle:
+    - step: repeat_development_cycle
       action: continue_for_all_stories
       notes: |
         Repeat story cycle (SM → Dev → QA) for all epic stories
@@ -10389,7 +10390,7 @@ workflow:
         - Validate epic was completed correctly
         - Document learnings and improvements
 
-    - workflow_end:
+    - step: workflow_end
       action: project_complete
       notes: |
         All stories implemented and reviewed!

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

@@ -309,6 +309,7 @@ persona:
   focus: Executing story tasks with precision, updating Dev Agent Record sections only, maintaining minimal context overhead
 core_principles:
   - CRITICAL: Story has ALL info you will need aside from what you loaded during the startup commands. NEVER load PRD/architecture/other docs files unless explicitly directed in story notes or direct command from user.
+  - CRITICAL: ALWAYS check current folder structure before starting your story tasks, don't create new working directory if it already exists. Create new one when you're sure it's a brand new project.
   - CRITICAL: ONLY update story file Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
   - CRITICAL: FOLLOW THE develop-story command when the user tells you to implement the story
   - Numbered Options - Always use numbered lists when presenting choices to the user
@@ -821,6 +822,7 @@ 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.
 

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

@@ -848,6 +848,7 @@ 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.
 
@@ -8743,7 +8744,7 @@ workflow:
         - Dev Agent (New Chat): Address remaining items
         - Return to QA for final approval
 
-    - repeat_development_cycle:
+    - step: repeat_development_cycle
       action: continue_for_all_stories
       notes: |
         Repeat story cycle (SM → Dev → QA) for all epic stories
@@ -8760,7 +8761,7 @@ workflow:
         - Validate epic was completed correctly
         - Document learnings and improvements
 
-    - workflow_end:
+    - step: workflow_end
       action: project_complete
       notes: |
         All stories implemented and reviewed!
@@ -8945,7 +8946,7 @@ workflow:
         - Dev Agent (New Chat): Address remaining items
         - Return to QA for final approval
 
-    - repeat_development_cycle:
+    - step: repeat_development_cycle
       action: continue_for_all_stories
       notes: |
         Repeat story cycle (SM → Dev → QA) for all epic stories
@@ -8962,7 +8963,7 @@ workflow:
         - Validate epic was completed correctly
         - Document learnings and improvements
 
-    - workflow_end:
+    - step: workflow_end
       action: project_complete
       notes: |
         All stories implemented and reviewed!

package/docs/expansion-packs.md

@@ -18,7 +18,7 @@ Each expansion pack provides deep, specialized knowledge without bloating the co
 
 Anyone can create and share expansion packs, fostering a ecosystem of AI-powered solutions across all industries and interests.
 
-## Technical Expansion Packs
+## Technical Expansion Packs (Examples of possible expansions to come)
 
 ### Game Development Pack
 
@@ -191,90 +191,10 @@ Research acceleration tools:
 
 ## Creating Your Own Expansion Pack
 
-### Step 1: Define Your Domain
-
-What expertise are you capturing? What problems will it solve?
-
-### Step 2: Design Your Agents
-
-Each agent should have:
-
-- Clear expertise area
-- Specific personality traits
-- Defined capabilities
-- Knowledge boundaries
-
-### Step 3: Create Tasks
-
-Tasks should be:
-
-- Step-by-step procedures
-- Reusable across scenarios
-- Clear and actionable
-- Domain-specific
-
-### Step 4: Build Templates
-
-Templates need:
-
-- Structured output format
-- Embedded LLM instructions
-- Placeholders for customization
-- Professional formatting
-
-### Step 5: Test & Iterate
-
-- Use with real scenarios
-- Gather user feedback
-- Refine agent responses
-- Improve task clarity
-
-### Step 6: Package & Share
-
-- Create clear documentation
-- Include usage examples
-- Add to expansion-packs directory
-- Share with community
-
-## The Future of Expansion Packs
-
-### Marketplace Potential
-
-Imagine a future where:
-
-- Professional expansion packs are sold
-- Certified packs for regulated industries
-- Community ratings and reviews
-- Automatic updates and improvements
-
-### AI Agent Ecosystems
-
-Expansion packs could enable:
-
-- Cross-pack agent collaboration
-- Industry-standard agent protocols
-- Interoperable AI workflows
-- Universal agent languages
-
-### Democratizing Expertise
-
-Every expansion pack:
-
-- Makes expert knowledge accessible
-- Reduces barriers to entry
-- Enables solo entrepreneurs
-- Empowers small teams
-
-## Getting Started
-
-1. **Browse existing packs**: Check `expansion-packs/` directory
-2. **Install what you need**: Use the installer's expansion pack option
-3. **Create your own**: Use the expansion-creator pack
-4. **Share with others**: Submit PRs with new packs
-5. **Build the future**: Help shape AI-assisted work
+The next major release will include a new agent and expansion pack builder and a new expansion format.
 
 ## Remember
 
-The BMad Method is more than a development framework - it's a platform for structuring human expertise into AI-accessible formats. Every expansion pack you create makes specialized knowledge more accessible to everyone.
+The BMad Method is more than a Software Development Agile Framework! Every expansion pack makes specialized knowledge and workflows more accessible to everyone.
 
 **What expertise will you share with the world?**

package/docs/user-guide.md

@@ -187,6 +187,32 @@ If you want to do the planning on the web with Claude (Sonnet 4 or Opus), Gemini
 npx bmad-method install
 ```
 
+### Codex (CLI & Web)
+
+BMAD integrates with OpenAI Codex via `AGENTS.md` and committed core agent files.
+
+- Two installation modes:
+  - Codex (local only): keeps `.bmad-core/` ignored for local dev.
+    - `npx bmad-method install -f -i codex -d .`
+  - Codex Web Enabled: ensures `.bmad-core/` is tracked so you can commit it for Codex Web.
+    - `npx bmad-method install -f -i codex-web -d .`
+
+- What gets generated:
+  - `AGENTS.md` at the project root with a BMAD section containing
+    - How-to-use with Codex (CLI & Web)
+    - Agent Directory (Title, ID, When To Use)
+    - Detailed per‑agent sections with source path, when-to-use, activation phrasing, and YAML
+    - Tasks with quick usage notes
+  - If a `package.json` exists, helpful scripts are added:
+    - `bmad:refresh`, `bmad:list`, `bmad:validate`
+
+- Using Codex:
+  - CLI: run `codex` in the project root and prompt naturally, e.g., “As dev, implement …”.
+  - Web: commit `.bmad-core/` and `AGENTS.md`, then open the repo in Codex and prompt the same way.
+
+- Refresh after changes:
+  - Re-run the appropriate install mode (`codex` or `codex-web`) to update the BMAD block in `AGENTS.md`.
+
 ## Special Agents
 
 There are two BMad agents — in the future they'll be consolidated into a single BMad-Master.

package/implement-fork-friendly-ci.sh

@@ -0,0 +1,229 @@
+#!/bin/bash
+
+# Fork-Friendly CI/CD Implementation Script
+# Usage: ./implement-fork-friendly-ci.sh
+# 
+# This script automates the implementation of fork-friendly CI/CD
+# by adding fork detection conditions to all GitHub Actions workflows
+
+set -e
+
+echo "🚀 Implementing Fork-Friendly CI/CD..."
+
+# Colors for output
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+NC='\033[0m' # No Color
+
+# 1. Check if .github/workflows directory exists
+if [ ! -d ".github/workflows" ]; then
+    echo -e "${RED}✗${NC} No .github/workflows directory found"
+    echo "This script must be run from the repository root"
+    exit 1
+fi
+
+# 2. Backup existing workflows
+echo "📦 Backing up workflows..."
+backup_dir=".github/workflows.backup.$(date +%Y%m%d_%H%M%S)"
+cp -r .github/workflows "$backup_dir"
+echo -e "${GREEN}✓${NC} Workflows backed up to $backup_dir"
+
+# 3. Count workflow files and jobs
+WORKFLOW_COUNT=$(ls -1 .github/workflows/*.yml .github/workflows/*.yaml 2>/dev/null | wc -l)
+echo "📊 Found ${WORKFLOW_COUNT} workflow files"
+
+# 4. Process each workflow file
+UPDATED_FILES=0
+MANUAL_REVIEW_NEEDED=0
+
+for file in .github/workflows/*.yml .github/workflows/*.yaml; do
+    if [ -f "$file" ]; then
+        filename=$(basename "$file")
+        echo -n "Processing ${filename}... "
+        
+        # Create temporary file
+        temp_file="${file}.tmp"
+        
+        # Track if file needs manual review
+        needs_review=0
+        
+        # Process the file with awk
+        awk '
+        BEGIN {
+            in_jobs = 0
+            job_count = 0
+            modified = 0
+        }
+        
+        /^jobs:/ { 
+            in_jobs = 1
+            print
+            next
+        }
+        
+        # Match job definitions (2 spaces + name + colon)
+        in_jobs && /^  [a-z][a-z0-9_-]*:/ {
+            job_name = $0
+            print job_name
+            job_count++
+            
+            # Look ahead for existing conditions
+            getline next_line
+            
+            # Check if next line is already an if condition
+            if (next_line ~ /^    if:/) {
+                # Job already has condition - combine with fork detection
+                existing_condition = next_line
+                sub(/^    if: /, "", existing_condition)
+                
+                # Check if fork condition already exists
+                if (existing_condition !~ /github\.event\.repository\.fork/) {
+                    print "    # Fork-friendly CI: Combined with existing condition"
+                    print "    if: (" existing_condition ") && (github.event.repository.fork != true || vars.ENABLE_CI_IN_FORK == '\''true'\'')"
+                    modified++
+                } else {
+                    # Already has fork detection
+                    print next_line
+                }
+            } else if (next_line ~ /^    runs-on:/) {
+                # No condition exists, add before runs-on
+                print "    if: github.event.repository.fork != true || vars.ENABLE_CI_IN_FORK == '\''true'\''"
+                print next_line
+                modified++
+            } else {
+                # Some other configuration, preserve as-is
+                print next_line
+            }
+            next
+        }
+        
+        # Reset when leaving jobs section
+        /^[a-z]/ && in_jobs {
+            in_jobs = 0
+        }
+        
+        # Print all other lines
+        { 
+            if (!in_jobs) print 
+        }
+        
+        END {
+            if (modified > 0) {
+                exit 0  # Success - file was modified
+            } else {
+                exit 1  # No modifications needed
+            }
+        }
+        ' "$file" > "$temp_file"
+        
+        # Check if modifications were made
+        if [ $? -eq 0 ]; then
+            mv "$temp_file" "$file"
+            echo -e "${GREEN}✓${NC} Updated"
+            ((UPDATED_FILES++))
+        else
+            rm -f "$temp_file"
+            echo -e "${YELLOW}○${NC} No changes needed"
+        fi
+        
+        # Check for complex conditions that might need manual review
+        if grep -q "needs:" "$file" || grep -q "strategy:" "$file"; then
+            echo "  ⚠️  Complex workflow detected - manual review recommended"
+            ((MANUAL_REVIEW_NEEDED++))
+        fi
+    fi
+done
+
+echo -e "${GREEN}✓${NC} Updated ${UPDATED_FILES} workflow files"
+
+# 5. Create Fork Guide if it doesn't exist
+if [ ! -f ".github/FORK_GUIDE.md" ]; then
+    echo "📝 Creating Fork Guide documentation..."
+    cat > .github/FORK_GUIDE.md << 'EOF'
+# Fork Guide - CI/CD Configuration
+
+## CI/CD in Forks
+
+By default, CI/CD workflows are **disabled in forks** to conserve GitHub Actions resources.
+
+### Enabling CI/CD in Your Fork
+
+If you need to run CI/CD workflows in your fork:
+
+1. Navigate to **Settings** → **Secrets and variables** → **Actions** → **Variables**
+2. Click **New repository variable**
+3. Create variable:
+   - **Name**: `ENABLE_CI_IN_FORK`
+   - **Value**: `true`
+4. Click **Add variable**
+
+### Disabling CI/CD Again
+
+Either:
+- Delete the `ENABLE_CI_IN_FORK` variable, or
+- Set its value to `false`
+
+### Alternative Testing Options
+
+- **Local testing**: Run tests locally before pushing
+- **Pull Request CI**: Workflows automatically run when you open a PR
+- **GitHub Codespaces**: Full development environment
+EOF
+    echo -e "${GREEN}✓${NC} Fork Guide created"
+else
+    echo "ℹ️  Fork Guide already exists"
+fi
+
+# 6. Validate YAML files (if yamllint is available)
+if command -v yamllint &> /dev/null; then
+    echo "🔍 Validating YAML syntax..."
+    VALIDATION_ERRORS=0
+    for file in .github/workflows/*.yml .github/workflows/*.yaml; do
+        if [ -f "$file" ]; then
+            filename=$(basename "$file")
+            if yamllint -d relaxed "$file" &>/dev/null; then
+                echo -e "  ${GREEN}✓${NC} ${filename}"
+            else
+                echo -e "  ${RED}✗${NC} ${filename} - YAML validation failed"
+                ((VALIDATION_ERRORS++))
+            fi
+        fi
+    done
+    
+    if [ $VALIDATION_ERRORS -gt 0 ]; then
+        echo -e "${YELLOW}⚠${NC}  ${VALIDATION_ERRORS} files have YAML errors"
+    fi
+else
+    echo "ℹ️  yamllint not found - skipping YAML validation"
+    echo "  Install with: pip install yamllint"
+fi
+
+# 7. Summary
+echo ""
+echo "═══════════════════════════════════════"
+echo "       Fork-Friendly CI/CD Summary"
+echo "═══════════════════════════════════════"
+echo "  📁 Files updated: ${UPDATED_FILES}"
+echo "  📊 Total workflows: ${WORKFLOW_COUNT}"
+echo "  📝 Fork Guide: .github/FORK_GUIDE.md"
+if [ $MANUAL_REVIEW_NEEDED -gt 0 ]; then
+    echo "  ⚠️  Files needing review: ${MANUAL_REVIEW_NEEDED}"
+fi
+echo ""
+echo "Next steps:"
+echo "1. Review the changes: git diff"
+echo "2. Test workflows locally (if possible)"
+echo "3. Commit changes: git commit -m 'feat: implement fork-friendly CI/CD'"
+echo "4. Push and create PR"
+echo ""
+echo "Remember to update README.md with fork information!"
+echo "═══════════════════════════════════════"
+
+# Exit with appropriate code
+if [ $UPDATED_FILES -gt 0 ]; then
+    exit 0
+else
+    echo "No files were updated - workflows may already be fork-friendly"
+    exit 1
+fi

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "4.41.0",
+  "version": "4.43.0",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",
@@ -27,6 +27,7 @@
     "build": "node tools/cli.js build",
     "build:agents": "node tools/cli.js build --agents-only",
     "build:teams": "node tools/cli.js build --teams-only",
+    "fix": "npm run format && npm run lint:fix",
     "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}\"",
@@ -34,12 +35,14 @@
     "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",
+    "pre-release": "npm run validate && npm run format:check && npm run lint",
     "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",
+    "setup:hooks": "chmod +x tools/setup-hooks.sh && ./tools/setup-hooks.sh",
     "validate": "node tools/cli.js validate",
     "version:all": "node tools/bump-all-versions.js",
     "version:all:major": "node tools/bump-all-versions.js major",

package/release_notes.md

@@ -1,4 +1,10 @@
-## 🚀 What's New in v4.41.0
+## 🚀 What's New in v4.43.0
+
+### ✨ New Features
+- feat: implement fork-friendly CI/CD with opt-in mechanism (#476)
+- feat(installer): add Codex CLI + Codex Web modes, generate AGENTS.md, inject npm scripts, and docs (#529)
+- feat: add PR validation workflow and contribution checks
+- feat: Add Auggie CLI (Augment Code) Integration (#520)
 
 ### 🐛 Bug Fixes
 - fix: update installer version display to show 4.39.0
@@ -6,13 +12,22 @@
 - fix: previous merge set wrong default install location
 - fix: documentation and trademark updates
 - fix: remove incorrect else branch causing flatten command regression (#452)
+- fix: correct dependency path format in bmad-master agent (#495)
+- fix: Codex options missing from the IDE selection menu (#535)
 
 ### 📦 Other Changes
 - patch: move script to tools folder
+- typo in README.md (#515)
+- Update dev.md (#491)
+- test: trigger PR validation (#533)
+- docs: remove misplaced Codex section from README
+- Expansion pack doc correction
 
 ### 🔧 Maintenance
 - chore: bump to 4.39.1 to fix installer version display
 - chore: update project dependencies and development tooling (#508)
+- chore: bump version to 4.42.0 for release
+- chore: sync version to 4.42.1 after release
 
 
 ## 📦 Installation
@@ -21,4 +36,4 @@
 npx bmad-method install
 ```
 
-**Full Changelog**: https://github.com/bmadcode/BMAD-METHOD/compare/v4.39.0...v4.41.0
+**Full Changelog**: https://github.com/bmadcode/BMAD-METHOD/compare/v4.39.0...v4.43.0

package/test.md

@@ -0,0 +1 @@
+# Test