bmad-method 4.4.1 → 4.5.0

package/{bmad-core/web-bundles → dist}/agents/bmad-master.txt

@@ -2440,67 +2440,6 @@ Document sharded successfully:
 - Ensure the sharding is reversible (could reconstruct the original from shards)
 ==================== END: tasks#shard-doc ====================
 
-==================== START: templates#agent-tmpl ====================
-# [AGENT_ID]
-
-CRITICAL: Read the full YML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
-
-```yml
-activation-instructions:
-    - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
-    - Only read the files/tasks listed here when user selects them for execution to minimize context usage
-    - The customization field ALWAYS takes precedence over any conflicting instructions
-    - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
-
-agent:
-  name: [AGENT_NAME]
-  id: [AGENT_ID]
-  title: [AGENT_TITLE]
-  customization: [OPTIONAL_CUSTOMIZATION]
-
-persona:
-  role: [AGENT_ROLE_DESCRIPTION]
-  style: [COMMUNICATION_STYLE]
-  identity: [AGENT_IDENTITY_DESCRIPTION]
-  focus: [PRIMARY_FOCUS_AREAS]
-
-  core_principles:
-    - [PRINCIPLE_1]
-    - [PRINCIPLE_2]
-    - [PRINCIPLE_3]
-    # Add more principles as needed
-
-startup:
-  - [STARTUP_INSTRUCTIONS]
-
-commands:
-  - "*help" - Show: numbered list of the following commands to allow selection
-  - "*chat-mode" - (Default) [DEFAULT_MODE_DESCRIPTION]
-  - "*create-doc {template}" - Create doc (no template = show available templates)
-  - [tasks] specific to the agent that are not covered by a template
-  - "*exit" - Say goodbye as the [AGENT_TITLE], and then abandon inhabiting this persona
-
-dependencies:
-  tasks:
-    - [TASK_1]
-    - [TASK_2]
-    # Add required tasks
-  templates:
-    - [TEMPLATE_1]
-    - [TEMPLATE_2]
-    # Add required templates
-  checklists:
-    - [CHECKLIST_1]
-    # Add required checklists
-  data:
-    - [DATA_1]
-    # Add required data files
-  utils:
-    - [UTIL_1]
-    # Add required utilities
-```
-==================== END: templates#agent-tmpl ====================
-
 ==================== START: templates#architecture-tmpl ====================
 # {{Project Name}} Architecture Document
 
@@ -8543,121 +8482,6 @@ With this work flow, there is only 1 story in progress at a time, worked sequent
 None Listed
 ==================== END: data#technical-preferences ====================
 
-==================== START: utils#agent-switcher.ide ====================
-# Agent Switcher Instructions
-
-## Overview
-
-This document provides instructions for switching between different IDE agent personas in the BMAD-METHOD framework.
-
-## Behavior
-
-### Listing Available Agents
-
-When no agent name is provided:
-
-1. Read the `bmad-core/ide-agents/` directory
-2. Look for files matching the pattern `*.ide.md`
-3. Extract agent names from filenames (the part before `.ide.md`)
-4. Present a numbered list of available agents
-
-### Loading an Agent
-
-When an agent name is provided:
-
-1. Attempt to load `bmad-core/ide-agents/{agent-name}.ide.md`
-2. If the file doesn't exist:
-   - List all available agents found in the directory
-   - Prompt for a valid selection
-3. If the file exists:
-   - Read and internalize the agent's instructions
-   - Note the agent's name and role from the Agent Profile section
-   - Embody that agent's persona, communication style, and capabilities
-   - Use the agent's name when referring to yourself (e.g., "I'm John, the Product Manager")
-   - Follow the agent's specific workflows and constraints
-
-### Active Agent Behavior
-
-When successfully operating as an IDE agent:
-
-- Strictly follow the agent's defined capabilities and limitations
-- Only execute commands that the agent supports (typically prefixed with `*`)
-- Maintain the agent identity and context until switched or exited
-- If asked to perform tasks outside the agent's scope:
-  - Inform the user of the limitation
-  - Suggest the appropriate agent for that task
-
-### Exiting Agent Mode
-
-When exiting agent mode:
-
-- Immediately exit the current agent persona
-- Return to standard assistant capabilities
-- Clear any agent-specific context or workflows
-
-## Implementation Details
-
-- Each agent maintains its own context and workflow state
-- Switching agents clears the previous agent's context
-- Agents are self-contained - no need to read additional files
-- The system automatically adapts as agents are added or removed
-
-## Example Interactions
-
-### Example Listing Agents
-
-```text
-User: [requests agent list]
-Agent: Available IDE agents:
-1. architect
-2. dev
-3. devops
-4. pm
-5. po
-6. sm
-
-Please select an agent by specifying: <agent-name>
-```text
-
-### Example Loading an Agent
-
-```text
-User: [requests dev agent]
-Agent: [Loads dev.ide.md and operates as Dev agent]
-```
-
-### Example Invalid Agent Request
-
-```text
-User: [requests designer agent]
-Agent: Could not find IDE agent 'designer'. Available agents:
-1. architect
-2. dev
-3. devops
-4. pm
-5. po
-6. sm
-
-Please select an agent by specifying: <agent-name>
-```text
-
-### Example Task Outside Agent Scope
-
-```text
-[While operating as Dev agent]
-User: Create a PRD
-Agent: I'm currently operating as the Dev agent, which doesn't have PRD creation capabilities.
-The PM agent can create PRDs. Would you like me to switch to the PM agent?
-```
-
-### Example Exiting Agent Mode
-
-```text
-User: [requests to exit agent mode]
-Agent: Exited IDE agent mode. Returned to standard assistant capabilities.
-```
-==================== END: utils#agent-switcher.ide ====================
-
 ==================== START: utils#template-format ====================
 # Template Format Conventions
 

package/{expansion-packs/bmad-2d-phaser-game-dev/web-bundles/teams/team-game-dev.txt → dist/expansion-packs/bmad-2d-phaser-game-dev/teams/phaser-2d-nodejs-game-team.txt}

@@ -38,11 +38,11 @@ These references map directly to bundle sections:
 
 ---
 
-==================== START: agent-teams#team-game-dev ====================
+==================== START: agent-teams#phaser-2d-nodejs-game-team ====================
 bundle:
-  name: Game Development Team
+  name: Phaser 2D NodeJS Game Team
   icon: 🎮
-  description: Comprehensive game development team specialized in 2D games using Phaser 3 and TypeScript. This team handles the complete game development lifecycle from initial concept brainstorming through detailed design documentation to technical implementation and quality assurance. Specializes in indie games, mobile games, web games, educational games, prototyping, and game feature development with focus on player experience and performance optimization.
+  description: Game Development team specialized in 2D games using Phaser 3 and TypeScript.
 agents:
   - bmad-orchestrator
   - game-designer
@@ -51,7 +51,7 @@ agents:
 workflows:
   - game-dev-greenfield
   - game-prototype
-==================== END: agent-teams#team-game-dev ====================
+==================== END: agent-teams#phaser-2d-nodejs-game-team ====================
 
 ==================== START: agents#bmad-orchestrator ====================
 # bmad