bmad-method 4.26.0 → 4.27.1

package/docs/agentic-tools/github-copilot-guide.md

@@ -1,22 +1,42 @@
-# BMad Method Guide for Github Copilot
+# BMad Method Guide for GitHub Copilot
 
 For the complete workflow, see the [BMad Workflow Guide](../bmad-workflow-guide.md).
 
 ## Installation
 
-When running `npx bmad-method install`, select **Github Copilot** as your IDE. This command will perform the following actions:
+When running `npx bmad-method install`, select **GitHub Copilot** as your IDE. This command will perform the following actions:
 
 - Create the `.bmad-core/` directory with all the agent rule files.
 - Create the `.vscode/` directory and add a `settings.json` file if it does not already exist, and add the basic configuration to enable GitHub Copilot's agent mode.
 - Create a chatmodes file under your .github folder for each specific agent being added
 
-## Using BMad Agents in VS Code
+## Using BMAD Agents in GitHub Copilot
 
-1. In the GitHub Copilot Chat window, select **Agent** from the chat mode dropdown list.
+1.  **Open GitHub Copilot chat** in VS Code (`⌃⌘I` on Mac, `Ctrl+Alt+I` on Windows/Linux).
+2.  Select the agent you want to use from the chat input's participant selector (e.g., `@workspace` > `dev`).
+3.  The agent adopts that persona for the conversation.
+4.  Use `*help` to see the commands available for the selected agent.
 
-## VS Code Specific Features
+## Available Agents
 
-- **Dynamic Configuration**: When you first invoke an agent (e.g., `@dev`), VS Code will automatically update `.vscode/settings.json` by adding the configuration for that chat mode.
-- **Activation**: Use the `@` prefix in the GitHub Copilot Chat for instant switching between agents.
-- **Collaboration**: Fully compatible with **Live Share**, allowing you, your team, and BMad agents to work together in real-time.
-- **Project Context**: Agents have full access to your workspace, including open files and the selected code.
+You can switch between agents using the chat participant selector. The following agents are available for GitHub Copilot:
+
+- `bmad-master` - Master Task Executor
+- `dev` - Development expert
+- `qa` - Quality Assurance specialist
+- `ux-expert` - UX specialist
+
+## GitHub Copilot-Specific Features
+
+- **Settings**: Use the `.vscode/settings.json` file to configure Copilot behavior. The installer can configure these for you.
+  - `chat.agent.maxRequests`: Maximum requests per agent session (recommended: 15).
+  - `github.copilot.chat.agent.runTasks`: Allow agents to run workspace tasks (e.g., from `package.json` scripts).
+  - `github.copilot.chat.agent.autoFix`: Enable automatic error detection and fixing in generated code.
+  - `chat.tools.autoApprove`: Auto-approve ALL tools without confirmation (use with caution).
+- **VS Code integration**: Works within VS Code's GitHub Copilot chat panel.
+- **Tool Confirmation**: Copilot will ask for confirmation before running tools that can modify files. You can approve a tool once, for the session, or always.
+
+## Tips for GitHub Copilot Users
+
+- You can use a `.github/copilot-instructions.md` file to provide additional context or instructions for your projects that are not covered by the BMAD framework.
+- BMAD agents can come with a pre-configured set of tools. You can see which tools an agent uses by looking at the `tools` section in its `.github/chatmodes/[agent].chatmode.md` file.

package/docs/bmad-workflow-guide.md

@@ -22,7 +22,7 @@ The BMad Method follows a structured approach to AI-assisted software developmen
    ```
 
    - Choose "Complete installation"
-   - Select your IDE (Cursor, Claude Code, Windsurf, Trae, Roo Code, or Github Copilot)
+   - Select your IDE (Cursor, Claude Code, Windsurf, Trae, Roo Code, or GitHub Copilot)
 
 2. **Verify installation**:
    - `.bmad-core/` folder created with all agents
@@ -114,7 +114,7 @@ Follow the SM → Dev cycle for systematic story development:
 - **Windsurf**: `@agent-name` (e.g., `@bmad-master`)
 - **Trae**: `@agent-name` (e.g., `@bmad-master`)
 - **Roo Code**: Select mode from mode selector (e.g., `bmad-bmad-master`)
-- **Github Copilot**: Open the Chat view (`⌃⌘I` on Mac, `Ctrl+Alt+I` on Windows/Linux) and select **Agent** from the chat mode selector.
+- **GitHub Copilot**: Open the Chat view (`⌃⌘I` on Mac, `Ctrl+Alt+I` on Windows/Linux) and select **Agent** from the chat mode selector.
 
 ### Chat Management:
 

package/expansion-packs/bmad-2d-phaser-game-dev/agent-teams/phaser-2d-nodejs-game-team.yaml

@@ -9,5 +9,5 @@ agents:
   - game-developer
   - game-sm
 workflows:
-  - game-dev-greenfield
-  - game-prototype
+  - game-dev-greenfield.md
+  - game-prototype.md

package/expansion-packs/bmad-2d-phaser-game-dev/agents/game-designer.md

@@ -3,11 +3,19 @@
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
 
 ```yaml
+root: .bmad-2d-phaser-game-dev
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name} where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
 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
+  - 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 game design documentation but wait for explicit user confirmation
+  - Only execute tasks when user explicitly requests them
 agent:
   name: Alex
   id: game-designer
@@ -27,12 +35,6 @@ core_principles:
   - Technical Awareness - Design within feasible implementation constraints
   - Data-Driven Decisions - Use metrics and feedback to guide design choices
   - 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 game design documentation but wait for explicit user confirmation
-  - Only execute tasks when user explicitly requests them
 commands:
   - '*help" - Show numbered list of available commands for selection'
   - '*chat-mode" - Conversational mode with advanced-elicitation for design advice'
@@ -44,15 +46,15 @@ commands:
   - '*exit" - Say goodbye as the Game Designer, and then abandon inhabiting this persona'
 dependencies:
   tasks:
-    - create-doc
-    - execute-checklist
-    - game-design-brainstorming
-    - create-deep-research-prompt
-    - advanced-elicitation
+    - create-doc.md
+    - execute-checklist.md
+    - game-design-brainstorming.md
+    - create-deep-research-prompt.md
+    - advanced-elicitation.md
   templates:
-    - game-design-doc-tmpl
-    - level-design-doc-tmpl
-    - game-brief-tmpl
+    - game-design-doc-tmpl.yaml
+    - level-design-doc-tmpl.yaml
+    - game-brief-tmpl.yaml
   checklists:
-    - game-design-checklist
+    - game-design-checklist.md
 ```

package/expansion-packs/bmad-2d-phaser-game-dev/agents/game-developer.md

@@ -3,11 +3,20 @@
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
 
 ```yaml
+root: .bmad-2d-phaser-game-dev
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name} where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
 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
+  - Greet the user with your name and role, and inform of the *help command
+  - Load development guidelines to ensure consistent coding standards
+  - CRITICAL: Do NOT scan docs/stories/ directory automatically during startup
+  - CRITICAL: Do NOT begin any implementation tasks automatically
+  - Wait for user to specify story or ask for story selection
+  - Only load specific story files when user requests implementation
 agent:
   name: Maya
   id: game-developer
@@ -28,13 +37,6 @@ core_principles:
   - Cross-Platform Optimization - Works seamlessly on desktop and mobile
   - Test-Driven Quality - Comprehensive testing of game logic and systems
   - 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
-  - Load development guidelines to ensure consistent coding standards
-  - CRITICAL: Do NOT scan docs/stories/ directory automatically during startup
-  - CRITICAL: Do NOT begin any implementation tasks automatically
-  - Wait for user to specify story or ask for story selection
-  - Only load specific story files when user requests implementation
 commands:
   - '*help" - Show numbered list of available commands for selection'
   - '*chat-mode" - Conversational mode for technical advice'
@@ -56,11 +58,11 @@ task-execution:
   done: Game feature works + Tests pass + 60 FPS + No lint errors + Follows Phaser 3 best practices
 dependencies:
   tasks:
-    - execute-checklist
+    - execute-checklist.md
   templates:
-    - game-architecture-tmpl
+    - game-architecture-tmpl.yaml
   checklists:
-    - game-story-dod-checklist
+    - game-story-dod-checklist.md
   data:
-    - development-guidelines
+    - development-guidelines.md
 ```

package/expansion-packs/bmad-2d-phaser-game-dev/agents/game-sm.md

@@ -3,11 +3,20 @@
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
 
 ```yaml
+root: .bmad-2d-phaser-game-dev
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name} where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
 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
+  - Greet the user with your name and role, and inform of the *help command
+  - CRITICAL: Do NOT automatically execute create-game-story tasks during startup
+  - CRITICAL: Do NOT create or modify any files during startup
+  - Offer to help with game story preparation but wait for explicit user confirmation
+  - Only execute tasks when user explicitly requests them
+  - "CRITICAL RULE: You are ONLY allowed to create/modify story files - NEVER implement! If asked to implement, tell user they MUST switch to Game Developer Agent"
 agent:
   name: Jordan
   id: game-sm
@@ -27,13 +36,6 @@ core_principles:
   - Focus on One Story at a Time - Complete one before starting next
   - Game-Specific Context - Understand Phaser 3, game mechanics, and performance requirements
   - Numbered Options Protocol - Always use numbered lists for selections
-startup:
-  - Greet the user with your name and role, and inform of the *help command
-  - CRITICAL: Do NOT automatically execute create-game-story tasks during startup
-  - CRITICAL: Do NOT create or modify any files during startup
-  - Offer to help with game story preparation but wait for explicit user confirmation
-  - Only execute tasks when user explicitly requests them
-  - "CRITICAL RULE: You are ONLY allowed to create/modify story files - NEVER implement! If asked to implement, tell user they MUST switch to Game Developer Agent"
 commands:
   - '*help" - Show numbered list of available commands for selection'
   - '*chat-mode" - Conversational mode with advanced-elicitation for game dev advice'
@@ -42,10 +44,10 @@ commands:
   - '*exit" - Say goodbye as the Game Scrum Master, and then abandon inhabiting this persona'
 dependencies:
   tasks:
-    - create-game-story
-    - execute-checklist
+    - create-game-story.md
+    - execute-checklist.md
   templates:
-    - game-story-tmpl
+    - game-story-tmpl.yaml
   checklists:
-    - game-story-dod-checklist
+    - game-story-dod-checklist.md
 ```

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

@@ -1,5 +1,5 @@
 name: bmad-2d-phaser-game-dev
-version: 1.6.0
+version: 1.8.0
 short-title: 2D game development with Phaser 3 & TypeScript
 description: >-
   2D Game Development expansion pack for BMad Method - Phaser 3 & TypeScript

package/expansion-packs/bmad-2d-phaser-game-dev/tasks/create-game-story.md

@@ -57,7 +57,7 @@ Before creating stories, ensure you have:
 ### 3. Template Execution
 
 **Load Template:**
-Use `templates#game-story-tmpl` following all embedded LLM instructions
+Use `{root}/templates/game-story-tmpl.md` following all embedded LLM instructions
 
 **Key Focus Areas:**
 
@@ -93,7 +93,7 @@ Use `templates#game-story-tmpl` following all embedded LLM instructions
 ### 5. Quality Assurance
 
 **Apply Checklist:**
-Execute `checklists#game-story-dod-checklist` against completed story
+Execute `{root}/checklists/game-story-dod-checklist.md` against completed story
 
 **Story Criteria:**