bmad-method 4.24.3 → 4.24.4

package/expansion-packs/bmad-2d-phaser-game-dev/data/bmad-kb.md

@@ -1,8 +1,8 @@
-# Game Development BMAD Knowledge Base
+# Game Development BMad Knowledge Base
 
 ## Overview
 
-This game development expansion of BMAD-METHOD specializes in creating 2D games using Phaser 3 and TypeScript. It extends the core BMAD framework with game-specific agents, workflows, and best practices for professional game development.
+This game development expansion of BMad-Method specializes in creating 2D games using Phaser 3 and TypeScript. It extends the core BMad framework with game-specific agents, workflows, and best practices for professional game development.
 
 ### Game Development Focus
 
@@ -251,4 +251,4 @@ game-project/
 - Culling and level-of-detail systems
 - Memory management and garbage collection optimization
 
-This knowledge base provides the foundation for effective game development using the BMAD-METHOD framework with specialized focus on 2D game creation using Phaser 3 and TypeScript.
+This knowledge base provides the foundation for effective game development using the BMad-Method framework with specialized focus on 2D game creation using Phaser 3 and TypeScript.

package/expansion-packs/bmad-creator-tools/README.md

@@ -1,6 +1,6 @@
-# BMAD Creator Tools
+# BMad Creator Tools
 
-Tools for creating and extending BMAD framework components.
+Tools for creating and extending BMad framework components.
 
 ## Tasks
 

package/expansion-packs/bmad-creator-tools/agents/bmad-the-creator.md

@@ -11,27 +11,27 @@ activation-instructions:
 agent:
   name: The Creator
   id: bmad-the-creator
-  title: BMAD Framework Extension Specialist
+  title: BMad Framework Extension Specialist
   icon: 🏗️
-  whenToUse: Use for creating new agents, expansion packs, and extending the BMAD framework
+  whenToUse: Use for creating new agents, expansion packs, and extending the BMad framework
   customization: null
 persona:
-  role: Expert BMAD Framework Architect & Creator
+  role: Expert BMad Framework Architect & Creator
   style: Methodical, creative, framework-aware, systematic
-  identity: Master builder who extends BMAD capabilities through thoughtful design and deep framework understanding
-  focus: Creating well-structured agents, expansion packs, and framework extensions that follow BMAD patterns and conventions
+  identity: Master builder who extends BMad capabilities through thoughtful design and deep framework understanding
+  focus: Creating well-structured agents, expansion packs, and framework extensions that follow BMad patterns and conventions
 core_principles:
-  - Framework Consistency - All creations follow established BMAD patterns
+  - Framework Consistency - All creations follow established BMad patterns
   - Modular Design - Create reusable, composable components
   - Clear Documentation - Every creation includes proper documentation
-  - Convention Over Configuration - Follow BMAD naming and structure patterns
+  - Convention Over Configuration - Follow BMad naming and structure patterns
   - Extensibility First - Design for future expansion and customization
   - Numbered Options Protocol - Always use numbered lists for user selections
 startup:
   - Greet the user with your name and role, and inform of the *help command
   - CRITICAL: Do NOT automatically create documents or execute tasks during startup
   - CRITICAL: Do NOT create or modify any files during startup
-  - Offer to help with BMAD framework extensions but wait for explicit user confirmation
+  - Offer to help with BMad framework extensions but wait for explicit user confirmation
   - Only execute tasks when user explicitly requests them
 commands:
   - '*help" - Show numbered list of available commands for selection'

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

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

package/expansion-packs/bmad-creator-tools/tasks/create-agent.md

@@ -1,6 +1,6 @@
 # Create Agent Task
 
-This task guides you through creating a new BMAD agent following the standard template.
+This task guides you through creating a new BMad agent following the standard template.
 
 ## Prerequisites
 

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

@@ -1,10 +1,10 @@
 # Create Expansion Pack Task
 
-This task helps you create a sophisticated BMAD expansion pack with advanced agent orchestration, template systems, and quality assurance patterns based on proven best practices.
+This task helps you create a sophisticated BMad expansion pack with advanced agent orchestration, template systems, and quality assurance patterns based on proven best practices.
 
 ## Understanding Expansion Packs
 
-Expansion packs extend BMAD with domain-specific capabilities using sophisticated AI agent orchestration patterns. They are self-contained packages that leverage:
+Expansion packs extend BMad with domain-specific capabilities using sophisticated AI agent orchestration patterns. They are self-contained packages that leverage:
 
 - **Advanced Agent Architecture**: YAML-in-Markdown with embedded personas and character consistency
 - **Template Systems**: LLM instruction embedding with conditional content and dynamic variables
@@ -12,7 +12,7 @@ Expansion packs extend BMAD with domain-specific capabilities using sophisticate
 - **Quality Assurance**: Multi-level validation with star ratings and comprehensive checklists
 - **Knowledge Integration**: Domain-specific data organization and best practices embedding
 
-Every expansion pack MUST include a custom BMAD orchestrator agent with sophisticated command systems and numbered options protocols.
+Every expansion pack MUST include a custom BMad orchestrator agent with sophisticated command systems and numbered options protocols.
 
 ## CRITICAL REQUIREMENTS
 
@@ -83,7 +83,7 @@ Create `expansion-packs/{pack-name}/plan.md` with:
 
 ### Agents (with Character Personas)
 
-- [ ] {pack-name}-orchestrator (REQUIRED: Custom BMAD orchestrator)
+- [ ] {pack-name}-orchestrator (REQUIRED: Custom BMad orchestrator)
   - Character Name: {human-name}
   - Communication Style: {style}
   - Key Commands: {command-list}
@@ -157,7 +157,7 @@ Important: Wait for user approval before proceeding to Phase 2
 
 #### 2.1 Create Orchestrator Agent with Domain-Themed Character
 
-**FIRST PRIORITY**: Design the custom BMAD orchestrator with domain-appropriate theme:
+**FIRST PRIORITY**: Design the custom BMad orchestrator with domain-appropriate theme:
 
 **Themed Character Design:**
 
@@ -183,7 +183,7 @@ Important: Wait for user approval before proceeding to Phase 2
 - **Activation Instructions**: Embedded YAML with behavior directives
 - **Startup Procedures**: Initialize without auto-execution
 - **Dependencies**: Clear references to tasks, templates, and data files
-- **Integration Points**: How it coordinates with core BMAD agents
+- **Integration Points**: How it coordinates with core BMad agents
 
 #### 2.2 Design Specialist Agents with Character Personas
 
@@ -374,7 +374,7 @@ embedded_knowledge:
   - {domain}-terminology.md
   - {domain}-standards.md
 
-# Dependencies on core BMAD components
+# Dependencies on core BMad components
 core_dependencies:
   agents:
     - architect        # For system design
@@ -863,7 +863,7 @@ Embedded knowledge (automatic):
 7. "Where in the workflow should users choose between different paths?"
 8. "How should the orchestrator hand off to specialist agents?"
 9. "What quality gates should be built into the workflow?"
-10. "How should it integrate with core BMAD agents?"
+10. "How should it integrate with core BMad agents?"
 
 ### Agent Planning
 
@@ -913,7 +913,7 @@ Embedded knowledge (automatic):
 **Quality and Validation:**
 
 - **Plan First**: ALWAYS create and get approval for plan.md before implementing
-- **Orchestrator Required**: Every pack MUST have a custom BMAD orchestrator with sophisticated command system
+- **Orchestrator Required**: Every pack MUST have a custom BMad orchestrator with sophisticated command system
 - **Verify References**: ALL referenced tasks/templates MUST exist and be tested
 - **Multi-Level Validation**: Quality systems must provide basic, comprehensive, and expert-level assessment
 - **Domain Expertise**: Ensure accuracy in specialized fields with embedded best practices

package/expansion-packs/bmad-creator-tools/templates/expansion-pack-plan-tmpl.md

@@ -70,7 +70,7 @@ Users must add these files to `bmad-core/data/`:
 
 ## Integration Points
 
-- Depends on core agents: {list any core BMAD agents used}
+- Depends on core agents: {list any core BMad agents used}
 - Extends teams: {which teams to update}
 
 ## Success Criteria

package/expansion-packs/bmad-infrastructure-devops/README.md

@@ -2,11 +2,11 @@
 
 ## Overview
 
-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.
+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.
 
 ## Purpose
 
-While the core BMAD flow focuses on getting from business requirements to development (Analyst → PM → Architect → SM → Dev), many projects require sophisticated infrastructure planning and implementation. This expansion pack adds:
+While the core BMad flow focuses on getting from business requirements to development (Analyst → PM → Architect → SM → Dev), many projects require sophisticated infrastructure planning and implementation. This expansion pack adds:
 
 - Infrastructure architecture design capabilities
 - Platform engineering implementation workflows
@@ -52,9 +52,9 @@ Install this expansion pack when your project requires:
 
 - `infrastructure-checklist.md` - Comprehensive 16-section infrastructure validation checklist
 
-## Integration with Core BMAD
+## Integration with Core BMad
 
-This expansion pack integrates with the core BMAD flow at these points:
+This expansion pack integrates with the core BMad flow at these points:
 
 1. **After Architecture Phase**: The Architect can trigger infrastructure architecture design
 2. **Parallel to Development**: Infrastructure implementation can proceed alongside application development
@@ -123,7 +123,7 @@ The DevOps agent can be added to team configurations:
 
 This expansion pack works best when used with:
 
-- Core BMAD agents (especially Architect)
+- Core BMad agents (especially Architect)
 - Technical preferences documentation
 - Approved PRD and system architecture
 
@@ -144,4 +144,4 @@ You can customize this expansion pack by:
 ---
 
 _Version: 1.0_
-_Compatible with: BMAD Method v4_
+_Compatible with: BMad Method v4_

package/expansion-packs/bmad-infrastructure-devops/checklists/infrastructure-checklist.md

@@ -270,7 +270,7 @@ This checklist serves as a comprehensive framework for validating infrastructure
 - [ ] Business stakeholders informed of changes
 - [ ] Feedback loops established for continuous improvement
 
-## 11. BMAD WORKFLOW INTEGRATION
+## 11. BMad WORKFLOW INTEGRATION
 
 ### 11.1 Development Agent Alignment
 

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

@@ -2,7 +2,7 @@ name: bmad-infrastructure-devops
 version: 1.2.0
 short-title: Infrastructure and DevOps capabilities
 description: >-
-  This expansion pack extends BMAD Method with comprehensive infrastructure and
+  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/expansion-packs/bmad-infrastructure-devops/tasks/review-infrastructure.md

@@ -55,13 +55,13 @@ To conduct a thorough review of existing infrastructure to identify improvement
 - Create an improvement roadmap with suggested timelines
 - Highlight cost optimization opportunities
 
-### 5. BMAD Integration Assessment
+### 5. BMad Integration Assessment
 
-- Evaluate how current infrastructure supports other BMAD agents:
+- Evaluate how current infrastructure supports other BMad agents:
   - **Development Support:** Assess how infrastructure enables Frontend Dev (Mira), Backend Dev (Enrique), and Full Stack Dev workflows
   - **Product Alignment:** Verify infrastructure supports PRD requirements from Product Owner (Oli)
   - **Architecture Compliance:** Check if implementation follows Architect (Alphonse) decisions
-  - Document any gaps in BMAD integration
+  - Document any gaps in BMad integration
 
 ### 6. Architectural Escalation Assessment
 
@@ -133,7 +133,7 @@ A comprehensive infrastructure review report that includes:
 2. **Prioritized findings** with severity ratings
 3. **Detailed recommendations** with effort/impact estimates
 4. **Cost optimization opportunities**
-5. **BMAD integration assessment**
+5. **BMad integration assessment**
 6. **Architectural escalation assessment** with clear escalation recommendations
 7. **Action plan** for critical improvements and architectural work
 8. **Escalation documentation** for Architect Agent collaboration (if applicable)

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

@@ -2,7 +2,7 @@
 
 ## Purpose
 
-To comprehensively validate platform infrastructure changes against security, reliability, operational, and compliance requirements before deployment. This task ensures all platform infrastructure meets organizational standards, follows best practices, and properly integrates with the broader BMAD ecosystem.
+To comprehensively validate platform infrastructure changes against security, reliability, operational, and compliance requirements before deployment. This task ensures all platform infrastructure meets organizational standards, follows best practices, and properly integrates with the broader BMad ecosystem.
 
 ## Inputs
 
@@ -82,9 +82,9 @@ To comprehensively validate platform infrastructure changes against security, re
 - Provide validation signoff recommendation based on complete platform assessment
 - Document platform component integration validation results
 
-### 6. BMAD Integration Assessment
+### 6. BMad Integration Assessment
 
-- Review how platform infrastructure changes support other BMAD agents:
+- Review how platform infrastructure changes support other BMad agents:
   - **Development Agent Alignment:** Verify platform infrastructure supports Frontend Dev, Backend Dev, and Full Stack Dev requirements including:
     - Container platform development environment provisioning
     - GitOps workflows for application deployment
@@ -128,7 +128,7 @@ A comprehensive platform validation report documenting:
 3. **Detailed findings for each non-compliant item** across foundation and platform components
 4. **Platform integration validation results** documenting component interoperability
 5. **Remediation recommendations with priority levels** based on platform impact
-6. **BMAD integration assessment results** for complete platform stack
+6. **BMad integration assessment results** for complete platform stack
 7. **Clear signoff recommendation** for platform deployment readiness or architectural revision requirements
 8. **Next steps for implementation or remediation** prioritized by platform dependencies
 

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

@@ -264,9 +264,9 @@ Create pipeline diagram showing:
 - Cost Monitoring & Reporting
 - Optimization Recommendations
 
-## BMAD Integration Architecture
+## BMad Integration Architecture
 
-[[LLM: Design infrastructure to specifically support other BMAD agents and their workflows. This ensures the infrastructure enables the entire BMAD methodology.]]
+[[LLM: Design infrastructure to specifically support other BMad agents and their workflows. This ensures the infrastructure enables the entire BMad methodology.]]
 
 ### Development Agent Support
 

package/package.json

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

package/tools/bmad-npx-wrapper.js

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 
 /**
- * BMAD Method CLI - Direct execution wrapper for npx
+ * BMad Method CLI - Direct execution wrapper for npx
  * This file ensures proper execution when run via npx from GitHub
  */
 

package/tools/builders/web-builder.js

@@ -470,7 +470,7 @@ class WebBuilder {
           }
         }
       } else {
-        // Use core BMAD version
+        // Use core BMad version
         try {
           const coreAgentPath = path.join(this.rootDir, "bmad-core", "agents", `${agentId}.md`);
           const coreAgentContent = await fs.readFile(coreAgentPath, "utf8");

package/tools/cli.js

@@ -10,7 +10,7 @@ const program = new Command();
 
 program
   .name('bmad-build')
-  .description('BMAD-METHOD build tool for creating web bundles')
+  .description('BMad-Method build tool for creating web bundles')
   .version('4.0.0');
 
 program
@@ -136,7 +136,7 @@ program
 
 program
   .command('upgrade')
-  .description('Upgrade a BMAD-METHOD V3 project to V4')
+  .description('Upgrade a BMad-Method V3 project to V4')
   .option('-p, --project <path>', 'Path to V3 project (defaults to current directory)')
   .option('--dry-run', 'Show what would be changed without making changes')
   .option('--no-backup', 'Skip creating backup (not recommended)')

package/tools/installer/README.md

@@ -1,58 +1,8 @@
-# BMAD Method Installer
-
-This directory contains the BMAD Method installer implementation.
-
-## Structure
-
-```text
-installer/
-├── bin/              # CLI entry points
-│   └── bmad.js      # Main CLI executable
-├── lib/             # Core implementation
-│   ├── installer.js # Main installation logic
-│   ├── updater.js   # Update management
-│   ├── config-loader.js # YAML config parsing
-│   ├── file-manager.js  # File operations
-│   ├── ide-setup.js     # IDE-specific setup
-│   └── prompts.js       # Interactive CLI prompts
-├── config/          # Configuration files
-│   └── install.config.yaml # Installation profiles
-├── templates/       # IDE template files
-│   ├── cursor-rules.md     # Cursor template
-│   ├── claude-commands.md  # Claude Code template
-│   └── windsurf-rules.md   # Windsurf template
-└── package.json     # NPM package configuration
-```
-
-## Installation Profiles
-
-- **minimal**: IDE agents only (best for beginners)
-- **core**: IDE + Web agents
-- **teams**: Full team workflows
-- **developer**: Everything including creation tools
+# BMad Method Installer
 
 ## Usage
 
 ```bash
 # Interactive installation
 npx bmad-method install
-
-# Direct profile installation
-npx bmad-method install --profile=minimal
-
-# Update existing installation
-npx bmad-method update
-```
-
-## Development
-
-```bash
-# Install dependencies
-npm install
-
-# Run tests
-npm test
-
-# Lint code
-npm run lint
 ```

package/tools/installer/bin/bmad.js

@@ -42,15 +42,15 @@ try {
 
 program
   .version(version)
-  .description('BMAD Method installer - Universal AI agent framework for any domain');
+  .description('BMad Method installer - Universal AI agent framework for any domain');
 
 program
   .command('install')
-  .description('Install BMAD Method agents and tools')
-  .option('-f, --full', 'Install complete BMAD Method')
+  .description('Install BMad Method agents and tools')
+  .option('-f, --full', 'Install complete BMad Method')
   .option('-x, --expansion-only', 'Install only expansion packs (no bmad-core)')
   .option('-d, --directory <path>', 'Installation directory')
-  .option('-i, --ide <ide...>', 'Configure for specific IDE(s) - can specify multiple (cursor, claude-code, windsurf, roo, cline, gemini, vs-code-copilot, other)')
+  .option('-i, --ide <ide...>', 'Configure for specific IDE(s) - can specify multiple (cursor, claude-code, windsurf, roo, cline, gemini, github-copilot, other)')
   .option('-e, --expansion-packs <packs...>', 'Install specific expansion packs (can specify multiple)')
   .action(async (options) => {
     try {
@@ -83,7 +83,7 @@ program
 
 program
   .command('update')
-  .description('Update existing BMAD installation')
+  .description('Update existing BMad installation')
   .option('--force', 'Force update, overwriting modified files')
   .option('--dry-run', 'Show what would be updated without making changes')
   .action(async () => {
@@ -124,7 +124,7 @@ program
 
 async function promptInstallation() {
   await initializeModules();
-  console.log(chalk.bold.blue(`\nWelcome to BMAD Method Installer v${version}\n`));
+  console.log(chalk.bold.blue(`\nWelcome to BMad Method Installer v${version}\n`));
 
   const answers = {};
 
@@ -133,7 +133,7 @@ async function promptInstallation() {
     {
       type: 'input',
       name: 'directory',
-      message: 'Enter the full path to your project directory where BMAD should be installed:',
+      message: 'Enter the full path to your project directory where BMad should be installed:',
       validate: (input) => {
         if (!input.trim()) {
           return 'Please enter a valid project path';
@@ -162,7 +162,7 @@ async function promptInstallation() {
   const coreConfig = yaml.load(await fs.readFile(coreConfigPath, 'utf8'));
   const coreShortTitle = coreConfig['short-title'] || 'BMad Agile Core System';
   
-  // Add BMAD core option
+  // Add BMad core option
   let bmadOptionText;
   if (state.type === 'v4_existing') {
     const currentVersion = state.manifest?.version || 'unknown';
@@ -237,7 +237,7 @@ async function promptInstallation() {
         { name: 'Roo Code', value: 'roo' },
         { name: 'Cline', value: 'cline' },
         { name: 'Gemini CLI', value: 'gemini' },
-        { name: 'VS Code Copilot', value: 'vs-code-copilot' }
+        { name: 'Github Copilot', value: 'github-copilot' }
       ]
     }
   ]);

package/tools/installer/config/install.config.yaml

@@ -1,6 +1,6 @@
 installation-options:
   full:
-    name: Complete BMAD Core
+    name: Complete BMad Core
     description: Copy the entire .bmad-core folder with all agents, templates, and tools
     action: copy-folder
     source: bmad-core
@@ -15,7 +15,7 @@ ide-configurations:
     format: multi-file
     command-suffix: .mdc
     instructions: |
-      # To use BMAD agents in Cursor:
+      # To use BMad agents in Cursor:
       # 1. Press Ctrl+L (Cmd+L on Mac) to open the chat
       # 2. Type @agent-name (e.g., "@dev", "@pm", "@architect")
       # 3. The agent will adopt that persona for the conversation
@@ -25,7 +25,7 @@ ide-configurations:
     format: multi-file
     command-suffix: .md
     instructions: |
-      # To use BMAD agents in Claude Code:
+      # To use BMad agents in Claude Code:
       # 1. Type /agent-name (e.g., "/dev", "/pm", "/architect")
       # 2. Claude will switch to that agent's persona
   windsurf:
@@ -34,7 +34,7 @@ ide-configurations:
     format: multi-file
     command-suffix: .md
     instructions: |
-      # To use BMAD agents in Windsurf:
+      # To use BMad agents in Windsurf:
       # 1. Type @agent-name (e.g., "@dev", "@pm")
       # 2. Windsurf will adopt that agent's persona
   roo:
@@ -42,7 +42,7 @@ ide-configurations:
     format: custom-modes
     file: .roomodes
     instructions: |
-      # To use BMAD agents in Roo Code:
+      # To use BMad agents in Roo Code:
       # 1. Open the mode selector (usually in the status bar)
       # 2. Select any bmad-{agent} mode (e.g., "bmad-dev", "bmad-pm")
       # 3. The AI will adopt that agent's full personality and capabilities
@@ -52,7 +52,7 @@ ide-configurations:
     format: multi-file
     command-suffix: .md
     instructions: |
-      # To use BMAD agents in Cline:
+      # To use BMad agents in Cline:
       # 1. Open the Cline chat panel in VS Code
       # 2. Type @agent-name (e.g., "@dev", "@pm", "@architect")
       # 3. The agent will adopt that persona for the conversation
@@ -62,18 +62,18 @@ ide-configurations:
     rule-dir: .gemini/agents/
     format: context-files
     instructions: |
-      # To use BMAD agents with the Gemini CLI:
+      # To use BMad agents with the Gemini CLI:
       # 1. The installer creates a .gemini/ directory in your project.
       # 2. It also configures .gemini/settings.json to load all agent files.
       # 3. Simply mention the agent in your prompt (e.g., "As @dev, ...").
       # 4. The Gemini CLI will automatically have the context for that agent.
-  vs-code-copilot:
-    name: VS Code Copilot
+  github-copilot:
+    name: Github Copilot
     rule-dir: .github/chatmodes/
     format: multi-file
     command-suffix: .md
     instructions: |
-      # To use BMAD agents with VS Code Copilot:
+      # To use BMad agents with Github Copilot:
       # 1. The installer creates a .github/chatmodes/ directory in your project
       # 2. Open the Chat view (`⌃⌘I` on Mac, `Ctrl+Alt+I` on Windows/Linux) and select **Agent** from the chat mode selector.
       # 3. The agent will adopt that persona for the conversation

package/tools/installer/lib/config-loader.js

@@ -93,7 +93,7 @@ class ConfigLoader {
               description: config['short-title'] || config.description || 'No description available',
               fullDescription: config.description || config['short-title'] || 'No description available',
               version: config.version || '1.0.0',
-              author: config.author || 'BMAD Team',
+              author: config.author || 'BMad Team',
               packPath: packPath,
               dependencies: config.dependencies?.agents || []
             });
@@ -113,7 +113,7 @@ class ConfigLoader {
               description: 'No description available',
               fullDescription: 'No description available',
               version: '1.0.0',
-              author: 'BMAD Team',
+              author: 'BMad Team',
               packPath: packPath,
               dependencies: []
             });

package/tools/installer/lib/ide-setup.js

@@ -63,7 +63,7 @@ class IdeSetup {
         return this.setupCline(installDir, selectedAgent);
       case "gemini":
         return this.setupGeminiCli(installDir, selectedAgent);
-      case "vs-code-copilot":
+      case "github-copilot":
         return this.setupVsCodeCopilot(installDir, selectedAgent, spinner);
       default:
         console.log(chalk.yellow(`\nIDE ${ide} not yet supported`));
@@ -559,8 +559,8 @@ tools: ['changes', 'codebase', 'fetch', 'findTestFiles', 'githubRepo', 'problems
       }
     }
 
-    console.log(chalk.green(`\n✓ VS Code Copilot setup complete!`));
-    console.log(chalk.dim(`You can now find the BMAD agents in the Chat view's mode selector.`));
+    console.log(chalk.green(`\n✓ Github Copilot setup complete!`));
+    console.log(chalk.dim(`You can now find the BMad agents in the Chat view's mode selector.`));
 
     return true;
   }
@@ -578,7 +578,7 @@ tools: ['changes', 'codebase', 'fetch', 'findTestFiles', 'githubRepo', 'problems
       try {
         const existingContent = await fileManager.readFile(settingsPath);
         existingSettings = JSON.parse(existingContent);
-        console.log(chalk.yellow("Found existing .vscode/settings.json. Merging BMAD settings..."));
+        console.log(chalk.yellow("Found existing .vscode/settings.json. Merging BMad settings..."));
       } catch (error) {
         console.warn(chalk.yellow("Could not parse existing settings.json. Creating new one."));
         existingSettings = {};
@@ -587,15 +587,15 @@ tools: ['changes', 'codebase', 'fetch', 'findTestFiles', 'githubRepo', 'problems
     
     // Clear any previous output and add spacing to avoid conflicts with loaders
     console.log('\n'.repeat(2));
-    console.log(chalk.blue("🔧 VS Code Copilot Agent Settings Configuration"));
-    console.log(chalk.dim("BMAD works best with specific VS Code settings for optimal agent experience."));
+    console.log(chalk.blue("🔧 Github Copilot Agent Settings Configuration"));
+    console.log(chalk.dim("BMad works best with specific VS Code settings for optimal agent experience."));
     console.log(''); // Add extra spacing
     
     const { configChoice } = await inquirer.prompt([
       {
         type: 'list',
         name: 'configChoice',
-        message: 'How would you like to configure VS Code Copilot settings?',
+        message: 'How would you like to configure Github Copilot settings?',
         choices: [
           {
             name: 'Use recommended defaults (fastest setup)',
@@ -638,7 +638,7 @@ tools: ['changes', 'codebase', 'fetch', 'findTestFiles', 'githubRepo', 'problems
         "github.copilot.chat.agent.autoFix": true,
         "chat.tools.autoApprove": false
       };
-      console.log(chalk.green("✓ Using recommended BMAD defaults for VS Code Copilot settings"));
+      console.log(chalk.green("✓ Using recommended BMad defaults for Github Copilot settings"));
     } else {
       // Manual configuration
       console.log(chalk.blue("\n📋 Let's configure each setting for your preferences:"));
@@ -696,7 +696,7 @@ tools: ['changes', 'codebase', 'fetch', 'findTestFiles', 'githubRepo', 'problems
       }
       
       bmadSettings = {
-        "chat.agent.enabled": true, // Always enabled - required for BMAD agents
+        "chat.agent.enabled": true, // Always enabled - required for BMad agents
         "chat.agent.maxRequests": parseInt(manualSettings.maxRequests),
         "github.copilot.chat.agent.runTasks": manualSettings.runTasks,
         "chat.mcp.discovery.enabled": manualSettings.mcpDiscovery,