ros/BMAD-METHOD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

web build optimization

Browse Source
This commit is contained in:
Brian Madison
2025-07-06 10:32:39 -05:00
parent 4b0a9235ab
commit 5fc69d773a
30 changed files with 1346 additions and 1360 deletions
Download Patch File Download Diff File Expand all files Collapse all files

65
dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-designer.txt vendored
View File

@@ -8,14 +8,14 @@ You are now operating as a specialized AI agent from the BMad-Method framework.
2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
- `==================== START: folder#filename ====================`
- `==================== END: folder#filename ====================`
- `==================== START: .bmad-2d-phaser-game-dev/folder/filename.md ====================`
- `==================== END: .bmad-2d-phaser-game-dev/folder/filename.md ====================`
When you need to reference a resource mentioned in your instructions:
- Look for the corresponding START/END tags
- The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
- If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
- The format is always the full path with dot prefix (e.g., `.bmad-2d-phaser-game-dev/personas/analyst.md`, `.bmad-2d-phaser-game-dev/tasks/create-story.md`)
- If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
**Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
@@ -29,8 +29,8 @@ dependencies:
These references map directly to bundle sections:
- `utils: template-format` → Look for `==================== START: utils#template-format ====================`
- `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
- `utils: template-format` → Look for `==================== START: .bmad-2d-phaser-game-dev/utils/template-format.md ====================`
- `tasks: create-story` → Look for `==================== START: .bmad-2d-phaser-game-dev/tasks/create-story.md ====================`
3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
@@ -38,7 +38,8 @@ These references map directly to bundle sections:
---
==================== START: agents#game-designer ====================
==================== START: .bmad-2d-phaser-game-dev/agents/game-designer.md ====================
# game-designer
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:
@@ -97,9 +98,9 @@ dependencies:
checklists:
- game-design-checklist
```
==================== END: agents#game-designer ====================
==================== END: .bmad-2d-phaser-game-dev/agents/game-designer.md ====================
==================== START: tasks#create-doc ====================
==================== START: .bmad-2d-phaser-game-dev/tasks/create-doc.md ====================
# Create Document from Template Task
## Purpose
@@ -119,7 +120,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
[[LLM: Check if plan tracking is enabled in core-config.yaml]]
- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
- If `workflow.trackProgress: true`, check for active plan using .bmad-2d-phaser-game-dev/utils/plan-management.md
- If plan exists and this document creation is part of the plan:
- Verify this is the expected next step
- If out of sequence and `enforceSequence: true`, warn user and halt without user override
@@ -128,7 +129,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
### 1. Identify Template
- Load from `templates#*` or `{root}/templates directory`
- Load from `.bmad-2d-phaser-game-dev/templates/*.md` or `.bmad-2d-phaser-game-dev/templates directory`
- Agent-specific templates are listed in agent's dependencies
- If agent has `templates: [prd-tmpl, architecture-tmpl]` for example, then offer to create "PRD" and "Architecture" documents
@@ -146,14 +147,14 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
### 4. Key Execution Patterns
**When you see:** `[[LLM: Draft X and immediately execute tasks#advanced-elicitation]]`
**When you see:** `[[LLM: Draft X and immediately execute .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md]]`
- Draft the content
- Present it to user
- IMMEDIATELY execute the task
- Wait for completion before continuing
**When you see:** `[[LLM: After section completion, apply tasks#Y]]`
**When you see:** `[[LLM: After section completion, apply .bmad-2d-phaser-game-dev/tasks/Y.md]]`
- Finish the section
- STOP and execute the task
@@ -191,16 +192,16 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
## Remember
Templates contain precise instructions for a reason. Follow them exactly to ensure document quality and completeness.
==================== END: tasks#create-doc ====================
==================== END: .bmad-2d-phaser-game-dev/tasks/create-doc.md ====================
==================== START: tasks#execute-checklist ====================
==================== START: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
# Checklist Validation Task
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
## Available Checklists
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the .bmad-2d-phaser-game-dev/checklists folder to select the appropriate one to run.
## Instructions
@@ -209,7 +210,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
- If user or the task being run provides a checklist name:
- Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
- If multiple matches found, ask user to clarify
- Load the appropriate checklist from {root}/checklists/
- Load the appropriate checklist from .bmad-2d-phaser-game-dev/checklists/
- If no checklist specified:
- Ask the user which checklist they want to use
- Present the available options from the files in the checklists folder
@@ -287,9 +288,9 @@ The LLM will:
- Execute the complete checklist validation
- Present a final report with pass/fail rates and key findings
- Offer to provide detailed analysis of any section, especially those with warnings or failures
==================== END: tasks#execute-checklist ====================
==================== END: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
==================== START: tasks#game-design-brainstorming ====================
==================== START: .bmad-2d-phaser-game-dev/tasks/game-design-brainstorming.md ====================
# Game Design Brainstorming Techniques Task
This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
@@ -598,9 +599,9 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
- Consider accessibility and inclusivity from the start
- Balance innovation with market viability
- Plan for iteration based on player feedback
==================== END: tasks#game-design-brainstorming ====================
==================== END: .bmad-2d-phaser-game-dev/tasks/game-design-brainstorming.md ====================
==================== START: tasks#create-deep-research-prompt ====================
==================== START: .bmad-2d-phaser-game-dev/tasks/create-deep-research-prompt.md ====================
# Create Deep Research Prompt Task
This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@@ -902,9 +903,9 @@ Present these numbered options to the user:
- Balance comprehensiveness with focus
- Document assumptions and limitations clearly
- Plan for iterative refinement based on initial findings
==================== END: tasks#create-deep-research-prompt ====================
==================== END: .bmad-2d-phaser-game-dev/tasks/create-deep-research-prompt.md ====================
==================== START: tasks#advanced-elicitation ====================
==================== START: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
# Advanced Game Design Elicitation Task
## Purpose
@@ -1016,9 +1017,9 @@ The questions and perspectives offered should always consider:
- Performance implications for 60 FPS targets
- Cross-platform compatibility (desktop and mobile)
- Game development best practices and common pitfalls
==================== END: tasks#advanced-elicitation ====================
==================== END: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
==================== START: templates#game-design-doc-tmpl ====================
==================== START: .bmad-2d-phaser-game-dev/templates/game-design-doc-tmpl.md ====================
# {{Game Title}} Game Design Document (GDD)
[[LLM: This template creates a comprehensive Game Design Document that will serve as the foundation for all game development work. The GDD should be detailed enough that developers can create user stories and epics from it. Focus on gameplay systems, mechanics, and technical requirements that can be broken down into implementable features.
@@ -1350,9 +1351,9 @@ If available, review any provided documents or ask if any are optionally availab
- {{reference_1}}
- {{reference_2}}
- {{reference_3}}
==================== END: templates#game-design-doc-tmpl ====================
==================== END: .bmad-2d-phaser-game-dev/templates/game-design-doc-tmpl.md ====================
==================== START: templates#level-design-doc-tmpl ====================
==================== START: .bmad-2d-phaser-game-dev/templates/level-design-doc-tmpl.md ====================
# {{Game Title}} Level Design Document
[[LLM: This template creates comprehensive level design documentation that guides both content creation and technical implementation. This document should provide enough detail for developers to create level loading systems and for designers to create specific levels.
@@ -1823,9 +1824,9 @@ Difficulty
- Mechanic integration effectiveness: {{integration_score}}
- Player guidance clarity: {{guidance_score}}
- Content accessibility: {{accessibility_rate}}%
==================== END: templates#level-design-doc-tmpl ====================
==================== END: .bmad-2d-phaser-game-dev/templates/level-design-doc-tmpl.md ====================
==================== START: templates#game-brief-tmpl ====================
==================== START: .bmad-2d-phaser-game-dev/templates/game-brief-tmpl.md ====================
# {{Game Title}} Game Brief
[[LLM: This template creates a comprehensive game brief that serves as the foundation for all subsequent game development work. The brief should capture the essential vision, scope, and requirements needed to create a detailed Game Design Document.
@@ -2171,9 +2172,9 @@ This brief is typically created early in the ideation process, often after brain
| Date | Version | Description | Author |
| :--- | :------ | :---------- | :----- |
==================== END: templates#game-brief-tmpl ====================
==================== END: .bmad-2d-phaser-game-dev/templates/game-brief-tmpl.md ====================
==================== START: checklists#game-design-checklist ====================
==================== START: .bmad-2d-phaser-game-dev/checklists/game-design-checklist.md ====================
# Game Design Document Quality Checklist
## Document Completeness
@@ -2375,4 +2376,4 @@ _List any critical items that need attention before moving to implementation pha
**Next Steps:**
_Outline immediate next actions for the team based on this assessment._
==================== END: checklists#game-design-checklist ====================
==================== END: .bmad-2d-phaser-game-dev/checklists/game-design-checklist.md ====================

37
dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-developer.txt vendored
View File

@@ -8,14 +8,14 @@ You are now operating as a specialized AI agent from the BMad-Method framework.
2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
- `==================== START: folder#filename ====================`
- `==================== END: folder#filename ====================`
- `==================== START: .bmad-2d-phaser-game-dev/folder/filename.md ====================`
- `==================== END: .bmad-2d-phaser-game-dev/folder/filename.md ====================`
When you need to reference a resource mentioned in your instructions:
- Look for the corresponding START/END tags
- The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
- If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
- The format is always the full path with dot prefix (e.g., `.bmad-2d-phaser-game-dev/personas/analyst.md`, `.bmad-2d-phaser-game-dev/tasks/create-story.md`)
- If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
**Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
@@ -29,8 +29,8 @@ dependencies:
These references map directly to bundle sections:
- `utils: template-format` → Look for `==================== START: utils#template-format ====================`
- `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
- `utils: template-format` → Look for `==================== START: .bmad-2d-phaser-game-dev/utils/template-format.md ====================`
- `tasks: create-story` → Look for `==================== START: .bmad-2d-phaser-game-dev/tasks/create-story.md ====================`
3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
@@ -38,7 +38,8 @@ These references map directly to bundle sections:
---
==================== START: agents#game-developer ====================
==================== START: .bmad-2d-phaser-game-dev/agents/game-developer.md ====================
# game-developer
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:
@@ -105,16 +106,16 @@ dependencies:
data:
- development-guidelines
```
==================== END: agents#game-developer ====================
==================== END: .bmad-2d-phaser-game-dev/agents/game-developer.md ====================
==================== START: tasks#execute-checklist ====================
==================== START: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
# Checklist Validation Task
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
## Available Checklists
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the .bmad-2d-phaser-game-dev/checklists folder to select the appropriate one to run.
## Instructions
@@ -123,7 +124,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
- If user or the task being run provides a checklist name:
- Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
- If multiple matches found, ask user to clarify
- Load the appropriate checklist from {root}/checklists/
- Load the appropriate checklist from .bmad-2d-phaser-game-dev/checklists/
- If no checklist specified:
- Ask the user which checklist they want to use
- Present the available options from the files in the checklists folder
@@ -201,9 +202,9 @@ The LLM will:
- Execute the complete checklist validation
- Present a final report with pass/fail rates and key findings
- Offer to provide detailed analysis of any section, especially those with warnings or failures
==================== END: tasks#execute-checklist ====================
==================== END: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
==================== START: templates#game-architecture-tmpl ====================
==================== START: .bmad-2d-phaser-game-dev/templates/game-architecture-tmpl.md ====================
# {{Game Title}} Game Architecture Document
[[LLM: This template creates a comprehensive game architecture document specifically for Phaser 3 + TypeScript projects. This should provide the technical foundation for all game development stories and epics.
@@ -764,9 +765,9 @@ export const GameBalance = {
- Zero TypeScript errors in strict mode
- Consistent adherence to coding standards
- Comprehensive documentation coverage
==================== END: templates#game-architecture-tmpl ====================
==================== END: .bmad-2d-phaser-game-dev/templates/game-architecture-tmpl.md ====================
==================== START: checklists#game-story-dod-checklist ====================
==================== START: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
# Game Development Story Definition of Done Checklist
## Story Completeness
@@ -927,9 +928,9 @@ export const GameBalance = {
**Additional Notes:**
_Any specific concerns, recommendations, or clarifications needed before development begins._
==================== END: checklists#game-story-dod-checklist ====================
==================== END: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
==================== START: data#development-guidelines ====================
==================== START: .bmad-2d-phaser-game-dev/data/development-guidelines.md ====================
# Game Development Guidelines
## Overview
@@ -1581,4 +1582,4 @@ src/
- **Asset Streaming**: Background loading for upcoming content
These guidelines ensure consistent, high-quality game development that meets performance targets and maintains code quality across all implementation stories.
==================== END: data#development-guidelines ====================
==================== END: .bmad-2d-phaser-game-dev/data/development-guidelines.md ====================

41
dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-sm.txt vendored
View File

@@ -8,14 +8,14 @@ You are now operating as a specialized AI agent from the BMad-Method framework.
2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
- `==================== START: folder#filename ====================`
- `==================== END: folder#filename ====================`
- `==================== START: .bmad-2d-phaser-game-dev/folder/filename.md ====================`
- `==================== END: .bmad-2d-phaser-game-dev/folder/filename.md ====================`
When you need to reference a resource mentioned in your instructions:
- Look for the corresponding START/END tags
- The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
- If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
- The format is always the full path with dot prefix (e.g., `.bmad-2d-phaser-game-dev/personas/analyst.md`, `.bmad-2d-phaser-game-dev/tasks/create-story.md`)
- If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
**Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
@@ -29,8 +29,8 @@ dependencies:
These references map directly to bundle sections:
- `utils: template-format` → Look for `==================== START: utils#template-format ====================`
- `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
- `utils: template-format` → Look for `==================== START: .bmad-2d-phaser-game-dev/utils/template-format.md ====================`
- `tasks: create-story` → Look for `==================== START: .bmad-2d-phaser-game-dev/tasks/create-story.md ====================`
3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
@@ -38,7 +38,8 @@ These references map directly to bundle sections:
---
==================== START: agents#game-sm ====================
==================== START: .bmad-2d-phaser-game-dev/agents/game-sm.md ====================
# game-sm
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:
@@ -90,9 +91,9 @@ dependencies:
checklists:
- game-story-dod-checklist
```
==================== END: agents#game-sm ====================
==================== END: .bmad-2d-phaser-game-dev/agents/game-sm.md ====================
==================== START: tasks#create-game-story ====================
==================== START: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
# Create Game Development Story Task
## Purpose
@@ -152,7 +153,7 @@ Before creating stories, ensure you have:
### 3. Template Execution
**Load Template:**
Use `templates#game-story-tmpl` following all embedded LLM instructions
Use `.bmad-2d-phaser-game-dev/templates/game-story-tmpl.md` following all embedded LLM instructions
**Key Focus Areas:**
@@ -188,7 +189,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 `.bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md` against completed story
**Story Criteria:**
@@ -309,16 +310,16 @@ Execute `checklists#game-story-dod-checklist` against completed story
- Testing → Done
This task ensures game development stories are immediately actionable and enable efficient AI-driven development of game features.
==================== END: tasks#create-game-story ====================
==================== END: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
==================== START: tasks#execute-checklist ====================
==================== START: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
# Checklist Validation Task
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
## Available Checklists
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the .bmad-2d-phaser-game-dev/checklists folder to select the appropriate one to run.
## Instructions
@@ -327,7 +328,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
- If user or the task being run provides a checklist name:
- Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
- If multiple matches found, ask user to clarify
- Load the appropriate checklist from {root}/checklists/
- Load the appropriate checklist from .bmad-2d-phaser-game-dev/checklists/
- If no checklist specified:
- Ask the user which checklist they want to use
- Present the available options from the files in the checklists folder
@@ -405,9 +406,9 @@ The LLM will:
- Execute the complete checklist validation
- Present a final report with pass/fail rates and key findings
- Offer to provide detailed analysis of any section, especially those with warnings or failures
==================== END: tasks#execute-checklist ====================
==================== END: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
==================== START: templates#game-story-tmpl ====================
==================== START: .bmad-2d-phaser-game-dev/templates/game-story-tmpl.md ====================
# Story: {{Story Title}}
**Epic:** {{Epic Name}}
@@ -643,9 +644,9 @@ class {{ClassName}} extends {{PhaseClass}} {
- {{future_enhancement_1}}
- {{future_optimization_1}}
==================== END: templates#game-story-tmpl ====================
==================== END: .bmad-2d-phaser-game-dev/templates/game-story-tmpl.md ====================
==================== START: checklists#game-story-dod-checklist ====================
==================== START: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
# Game Development Story Definition of Done Checklist
## Story Completeness
@@ -806,4 +807,4 @@ class {{ClassName}} extends {{PhaseClass}} {
**Additional Notes:**
_Any specific concerns, recommendations, or clarifications needed before development begins._
==================== END: checklists#game-story-dod-checklist ====================
==================== END: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================

175
dist/expansion-packs/bmad-2d-phaser-game-dev/teams/phaser-2d-nodejs-game-team.txt vendored
View File

@@ -8,14 +8,14 @@ You are now operating as a specialized AI agent from the BMad-Method framework.
2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
- `==================== START: folder#filename ====================`
- `==================== END: folder#filename ====================`
- `==================== START: .bmad-2d-phaser-game-dev/folder/filename.md ====================`
- `==================== END: .bmad-2d-phaser-game-dev/folder/filename.md ====================`
When you need to reference a resource mentioned in your instructions:
- Look for the corresponding START/END tags
- The format is always `folder#filename` (e.g., `personas#analyst`, `tasks#create-story`)
- If a section is specified (e.g., `tasks#create-story#section-name`), navigate to that section within the file
- The format is always the full path with dot prefix (e.g., `.bmad-2d-phaser-game-dev/personas/analyst.md`, `.bmad-2d-phaser-game-dev/tasks/create-story.md`)
- If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
**Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
@@ -29,8 +29,8 @@ dependencies:
These references map directly to bundle sections:
- `utils: template-format` → Look for `==================== START: utils#template-format ====================`
- `tasks: create-story` → Look for `==================== START: tasks#create-story ====================`
- `utils: template-format` → Look for `==================== START: .bmad-2d-phaser-game-dev/utils/template-format.md ====================`
- `tasks: create-story` → Look for `==================== START: .bmad-2d-phaser-game-dev/tasks/create-story.md ====================`
3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
@@ -38,7 +38,8 @@ These references map directly to bundle sections:
---
==================== START: agent-teams#phaser-2d-nodejs-game-team ====================
==================== START: .bmad-2d-phaser-game-dev/agent-teams/phaser-2d-nodejs-game-team.yaml ====================
bundle:
name: Phaser 2D NodeJS Game Team
icon: 🎮
@@ -52,9 +53,9 @@ agents:
workflows:
- game-dev-greenfield
- game-prototype
==================== END: agent-teams#phaser-2d-nodejs-game-team ====================
==================== END: .bmad-2d-phaser-game-dev/agent-teams/phaser-2d-nodejs-game-team.yaml ====================
==================== START: agents#analyst ====================
==================== START: .bmad-2d-phaser-game-dev/agents/analyst.md ====================
# analyst
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:
@@ -120,9 +121,9 @@ dependencies:
utils:
- template-format
```
==================== END: agents#analyst ====================
==================== END: .bmad-2d-phaser-game-dev/agents/analyst.md ====================
==================== START: agents#bmad-orchestrator ====================
==================== START: .bmad-2d-phaser-game-dev/agents/bmad-orchestrator.md ====================
# bmad-orchestrator
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:
@@ -153,7 +154,7 @@ startup:
- Announce: Introduce yourself as the BMad Orchestrator, explain you can coordinate agents and workflows
- IMPORTANT: Tell users that all commands start with * (e.g., *help, *agent, *workflow)
- Mention *help shows all available commands and options
- Check for active workflow plan using utils#plan-management
- Check for active workflow plan using .bmad-2d-phaser-game-dev/utils/plan-management.md
- 'If plan exists: Show 📋 Active plan: {workflow} ({progress}% complete). Use *plan-status for details.'
- 'If plan exists: Suggest next action based on plan progress'
- Assess user goal against available agents and workflows in this bundle
@@ -259,9 +260,9 @@ dependencies:
- workflow-management
- template-format
```
==================== END: agents#bmad-orchestrator ====================
==================== END: .bmad-2d-phaser-game-dev/agents/bmad-orchestrator.md ====================
==================== START: agents#game-designer ====================
==================== START: .bmad-2d-phaser-game-dev/agents/game-designer.md ====================
# game-designer
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:
@@ -320,9 +321,9 @@ dependencies:
checklists:
- game-design-checklist
```
==================== END: agents#game-designer ====================
==================== END: .bmad-2d-phaser-game-dev/agents/game-designer.md ====================
==================== START: agents#game-developer ====================
==================== START: .bmad-2d-phaser-game-dev/agents/game-developer.md ====================
# game-developer
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:
@@ -389,9 +390,9 @@ dependencies:
data:
- development-guidelines
```
==================== END: agents#game-developer ====================
==================== END: .bmad-2d-phaser-game-dev/agents/game-developer.md ====================
==================== START: agents#game-sm ====================
==================== START: .bmad-2d-phaser-game-dev/agents/game-sm.md ====================
# game-sm
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:
@@ -443,9 +444,9 @@ dependencies:
checklists:
- game-story-dod-checklist
```
==================== END: agents#game-sm ====================
==================== END: .bmad-2d-phaser-game-dev/agents/game-sm.md ====================
==================== START: tasks#facilitate-brainstorming-session ====================
==================== START: .bmad-2d-phaser-game-dev/tasks/facilitate-brainstorming-session.md ====================
---
docOutputLocation: docs/brainstorming-session-results.md
template: brainstorming-output-tmpl
@@ -582,9 +583,9 @@ Generate structured document with these sections:
- Always ask before switching techniques: "Ready to try a different approach?"
- Offer options: "Should we explore this idea deeper or generate more alternatives?"
- Respect their process and timing
==================== END: tasks#facilitate-brainstorming-session ====================
==================== END: .bmad-2d-phaser-game-dev/tasks/facilitate-brainstorming-session.md ====================
==================== START: tasks#create-deep-research-prompt ====================
==================== START: .bmad-2d-phaser-game-dev/tasks/create-deep-research-prompt.md ====================
# Create Deep Research Prompt Task
This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@@ -886,9 +887,9 @@ Present these numbered options to the user:
- Balance comprehensiveness with focus
- Document assumptions and limitations clearly
- Plan for iterative refinement based on initial findings
==================== END: tasks#create-deep-research-prompt ====================
==================== END: .bmad-2d-phaser-game-dev/tasks/create-deep-research-prompt.md ====================
==================== START: tasks#create-doc ====================
==================== START: .bmad-2d-phaser-game-dev/tasks/create-doc.md ====================
# Create Document from Template Task
## Purpose
@@ -908,7 +909,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
[[LLM: Check if plan tracking is enabled in core-config.yaml]]
- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
- If `workflow.trackProgress: true`, check for active plan using .bmad-2d-phaser-game-dev/utils/plan-management.md
- If plan exists and this document creation is part of the plan:
- Verify this is the expected next step
- If out of sequence and `enforceSequence: true`, warn user and halt without user override
@@ -917,7 +918,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
### 1. Identify Template
- Load from `templates#*` or `{root}/templates directory`
- Load from `.bmad-2d-phaser-game-dev/templates/*.md` or `.bmad-2d-phaser-game-dev/templates directory`
- Agent-specific templates are listed in agent's dependencies
- If agent has `templates: [prd-tmpl, architecture-tmpl]` for example, then offer to create "PRD" and "Architecture" documents
@@ -935,14 +936,14 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
### 4. Key Execution Patterns
**When you see:** `[[LLM: Draft X and immediately execute tasks#advanced-elicitation]]`
**When you see:** `[[LLM: Draft X and immediately execute .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md]]`
- Draft the content
- Present it to user
- IMMEDIATELY execute the task
- Wait for completion before continuing
**When you see:** `[[LLM: After section completion, apply tasks#Y]]`
**When you see:** `[[LLM: After section completion, apply .bmad-2d-phaser-game-dev/tasks/Y.md]]`
- Finish the section
- STOP and execute the task
@@ -980,9 +981,9 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
## Remember
Templates contain precise instructions for a reason. Follow them exactly to ensure document quality and completeness.
==================== END: tasks#create-doc ====================
==================== END: .bmad-2d-phaser-game-dev/tasks/create-doc.md ====================
==================== START: tasks#advanced-elicitation ====================
==================== START: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
# Advanced Game Design Elicitation Task
## Purpose
@@ -1094,9 +1095,9 @@ The questions and perspectives offered should always consider:
- Performance implications for 60 FPS targets
- Cross-platform compatibility (desktop and mobile)
- Game development best practices and common pitfalls
==================== END: tasks#advanced-elicitation ====================
==================== END: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
==================== START: tasks#document-project ====================
==================== START: .bmad-2d-phaser-game-dev/tasks/document-project.md ====================
# Document an Existing Project
## Purpose
@@ -1414,9 +1415,9 @@ Apply the advanced elicitation task after major sections to refine based on user
- Documents technical debt, workarounds, and constraints honestly
- For brownfield projects with PRD: Provides clear enhancement impact analysis
- The goal is PRACTICAL documentation for AI agents doing real work
==================== END: tasks#document-project ====================
==================== END: .bmad-2d-phaser-game-dev/tasks/document-project.md ====================
==================== START: templates#project-brief-tmpl ====================
==================== START: .bmad-2d-phaser-game-dev/templates/project-brief-tmpl.md ====================
---
defaultOutput: docs/brief.md
---
@@ -1649,9 +1650,9 @@ This Project Brief provides the full context for {{Project Name}}. Please start
9. Proceed to next section
These replace the standard elicitation options when working on project brief documents.]]
==================== END: templates#project-brief-tmpl ====================
==================== END: .bmad-2d-phaser-game-dev/templates/project-brief-tmpl.md ====================
==================== START: templates#market-research-tmpl ====================
==================== START: .bmad-2d-phaser-game-dev/templates/market-research-tmpl.md ====================
# Market Research Report: {{Project/Product Name}}
[[LLM: The default path and filename unless specified is docs/market-research.md]]
@@ -1915,9 +1916,9 @@ These replace the standard elicitation options when working on project brief doc
9. Proceed to next section
These replace the standard elicitation options when working on market research documents.]]
==================== END: templates#market-research-tmpl ====================
==================== END: .bmad-2d-phaser-game-dev/templates/market-research-tmpl.md ====================
==================== START: templates#competitor-analysis-tmpl ====================
==================== START: .bmad-2d-phaser-game-dev/templates/competitor-analysis-tmpl.md ====================
# Competitive Analysis Report: {{Project/Product Name}}
[[LLM: The default path and filename unless specified is docs/competitor-analysis.md]]
@@ -2209,9 +2210,9 @@ These replace the standard elicitation options when working on market research d
9. Proceed to next section
These replace the standard elicitation options when working on competitive analysis documents.]]
==================== END: templates#competitor-analysis-tmpl ====================
==================== END: .bmad-2d-phaser-game-dev/templates/competitor-analysis-tmpl.md ====================
==================== START: templates#brainstorming-output-tmpl ====================
==================== START: .bmad-2d-phaser-game-dev/templates/brainstorming-output-tmpl.md ====================
---
defaultOutput: docs/brainstorming-session-results.md
---
@@ -2361,9 +2362,9 @@ defaultOutput: docs/brainstorming-session-results.md
---
*Session facilitated using the BMAD-METHOD brainstorming framework*
==================== END: templates#brainstorming-output-tmpl ====================
==================== END: .bmad-2d-phaser-game-dev/templates/brainstorming-output-tmpl.md ====================
==================== START: data#bmad-kb ====================
==================== START: .bmad-2d-phaser-game-dev/data/bmad-kb.md ====================
# Game Development BMad Knowledge Base
## Overview
@@ -2618,9 +2619,9 @@ game-project/
- 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.
==================== END: data#bmad-kb ====================
==================== END: .bmad-2d-phaser-game-dev/data/bmad-kb.md ====================
==================== START: data#brainstorming-techniques ====================
==================== START: .bmad-2d-phaser-game-dev/data/brainstorming-techniques.md ====================
# Brainstorming Techniques Data
## Creative Expansion
@@ -2657,9 +2658,9 @@ This knowledge base provides the foundation for effective game development using
18. **Resource Constraints**: "What if you had only $10 and 1 hour?"
19. **Metaphor Mapping**: Use extended metaphors to explore solutions
20. **Question Storming**: Generate questions instead of answers first
==================== END: data#brainstorming-techniques ====================
==================== END: .bmad-2d-phaser-game-dev/data/brainstorming-techniques.md ====================
==================== START: utils#template-format ====================
==================== START: .bmad-2d-phaser-game-dev/utils/template-format.md ====================
# Template Format Conventions
Templates in the BMad method use standardized markup for AI processing. These conventions ensure consistent document generation.
@@ -2686,9 +2687,9 @@ Templates in the BMad method use standardized markup for AI processing. These co
- Template elements are for AI processing only
- Focus on faithful template execution and clean output
- All template-specific instructions are embedded within templates
==================== END: utils#template-format ====================
==================== END: .bmad-2d-phaser-game-dev/utils/template-format.md ====================
==================== START: tasks#create-workflow-plan ====================
==================== START: .bmad-2d-phaser-game-dev/tasks/create-workflow-plan.md ====================
# Create Workflow Plan Task
## Purpose
@@ -2978,9 +2979,9 @@ BMad Orchestrator: "Based on your answers, I recommend the brownfield-fullstack
BMad Orchestrator: "I've created a workflow plan at docs/workflow-plan.md. This shows all the steps we'll go through, what documents will be created, and where you'll need to make decisions. Would you like to review it together?"
```
==================== END: tasks#create-workflow-plan ====================
==================== END: .bmad-2d-phaser-game-dev/tasks/create-workflow-plan.md ====================
==================== START: tasks#kb-mode-interaction ====================
==================== START: .bmad-2d-phaser-game-dev/tasks/kb-mode-interaction.md ====================
# KB Mode Interaction Task
## Purpose
@@ -3051,9 +3052,9 @@ Or ask me about anything else related to BMad-Method!
**User**: Tell me about workflows
**Assistant**: [Provides focused information about workflows from the KB, then offers to explore specific workflow types or related topics]
==================== END: tasks#kb-mode-interaction ====================
==================== END: .bmad-2d-phaser-game-dev/tasks/kb-mode-interaction.md ====================
==================== START: tasks#update-workflow-plan ====================
==================== START: .bmad-2d-phaser-game-dev/tasks/update-workflow-plan.md ====================
# Update Workflow Plan Task
## Purpose
@@ -3302,9 +3303,9 @@ The update is successful when:
- Consider creating backup before major updates
- Updates should enhance, not complicate, the workflow experience
- If plan becomes too cluttered, suggest creating fresh plan for next phase
==================== END: tasks#update-workflow-plan ====================
==================== END: .bmad-2d-phaser-game-dev/tasks/update-workflow-plan.md ====================
==================== START: utils#plan-management ====================
==================== START: .bmad-2d-phaser-game-dev/utils/plan-management.md ====================
# Plan Management Utility
## Purpose
@@ -3524,9 +3525,9 @@ Would you like to:
- Malformed plan: Warn but continue, treat as no plan
- Update failures: Log but don't block task completion
- Parse errors: Fallback to basic text search
==================== END: utils#plan-management ====================
==================== END: .bmad-2d-phaser-game-dev/utils/plan-management.md ====================
==================== START: utils#workflow-management ====================
==================== START: .bmad-2d-phaser-game-dev/utils/workflow-management.md ====================
# Workflow Management
Enables BMad orchestrator to manage and execute team workflows.
@@ -3596,16 +3597,16 @@ Handle conditional paths by asking clarifying questions when needed.
## Agent Integration
Agents should be workflow-aware: know active workflow, their role, access artifacts, understand expected outputs.
==================== END: utils#workflow-management ====================
==================== END: .bmad-2d-phaser-game-dev/utils/workflow-management.md ====================
==================== START: tasks#execute-checklist ====================
==================== START: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
# Checklist Validation Task
This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
## Available Checklists
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the {root}/checklists folder to select the appropriate one to run.
If the user asks or does not specify a specific checklist, list the checklists available to the agent persona. If the task is being run not with a specific agent, tell the user to check the .bmad-2d-phaser-game-dev/checklists folder to select the appropriate one to run.
## Instructions
@@ -3614,7 +3615,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
- If user or the task being run provides a checklist name:
- Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
- If multiple matches found, ask user to clarify
- Load the appropriate checklist from {root}/checklists/
- Load the appropriate checklist from .bmad-2d-phaser-game-dev/checklists/
- If no checklist specified:
- Ask the user which checklist they want to use
- Present the available options from the files in the checklists folder
@@ -3692,9 +3693,9 @@ The LLM will:
- Execute the complete checklist validation
- Present a final report with pass/fail rates and key findings
- Offer to provide detailed analysis of any section, especially those with warnings or failures
==================== END: tasks#execute-checklist ====================
==================== END: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
==================== START: tasks#game-design-brainstorming ====================
==================== START: .bmad-2d-phaser-game-dev/tasks/game-design-brainstorming.md ====================
# Game Design Brainstorming Techniques Task
This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
@@ -4003,9 +4004,9 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
- Consider accessibility and inclusivity from the start
- Balance innovation with market viability
- Plan for iteration based on player feedback
==================== END: tasks#game-design-brainstorming ====================
==================== END: .bmad-2d-phaser-game-dev/tasks/game-design-brainstorming.md ====================
==================== START: templates#game-design-doc-tmpl ====================
==================== START: .bmad-2d-phaser-game-dev/templates/game-design-doc-tmpl.md ====================
# {{Game Title}} Game Design Document (GDD)
[[LLM: This template creates a comprehensive Game Design Document that will serve as the foundation for all game development work. The GDD should be detailed enough that developers can create user stories and epics from it. Focus on gameplay systems, mechanics, and technical requirements that can be broken down into implementable features.
@@ -4337,9 +4338,9 @@ If available, review any provided documents or ask if any are optionally availab
- {{reference_1}}
- {{reference_2}}
- {{reference_3}}
==================== END: templates#game-design-doc-tmpl ====================
==================== END: .bmad-2d-phaser-game-dev/templates/game-design-doc-tmpl.md ====================
==================== START: templates#level-design-doc-tmpl ====================
==================== START: .bmad-2d-phaser-game-dev/templates/level-design-doc-tmpl.md ====================
# {{Game Title}} Level Design Document
[[LLM: This template creates comprehensive level design documentation that guides both content creation and technical implementation. This document should provide enough detail for developers to create level loading systems and for designers to create specific levels.
@@ -4810,9 +4811,9 @@ Difficulty
- Mechanic integration effectiveness: {{integration_score}}
- Player guidance clarity: {{guidance_score}}
- Content accessibility: {{accessibility_rate}}%
==================== END: templates#level-design-doc-tmpl ====================
==================== END: .bmad-2d-phaser-game-dev/templates/level-design-doc-tmpl.md ====================
==================== START: templates#game-brief-tmpl ====================
==================== START: .bmad-2d-phaser-game-dev/templates/game-brief-tmpl.md ====================
# {{Game Title}} Game Brief
[[LLM: This template creates a comprehensive game brief that serves as the foundation for all subsequent game development work. The brief should capture the essential vision, scope, and requirements needed to create a detailed Game Design Document.
@@ -5158,9 +5159,9 @@ This brief is typically created early in the ideation process, often after brain
| Date | Version | Description | Author |
| :--- | :------ | :---------- | :----- |
==================== END: templates#game-brief-tmpl ====================
==================== END: .bmad-2d-phaser-game-dev/templates/game-brief-tmpl.md ====================
==================== START: checklists#game-design-checklist ====================
==================== START: .bmad-2d-phaser-game-dev/checklists/game-design-checklist.md ====================
# Game Design Document Quality Checklist
## Document Completeness
@@ -5362,9 +5363,9 @@ _List any critical items that need attention before moving to implementation pha
**Next Steps:**
_Outline immediate next actions for the team based on this assessment._
==================== END: checklists#game-design-checklist ====================
==================== END: .bmad-2d-phaser-game-dev/checklists/game-design-checklist.md ====================
==================== START: templates#game-architecture-tmpl ====================
==================== START: .bmad-2d-phaser-game-dev/templates/game-architecture-tmpl.md ====================
# {{Game Title}} Game Architecture Document
[[LLM: This template creates a comprehensive game architecture document specifically for Phaser 3 + TypeScript projects. This should provide the technical foundation for all game development stories and epics.
@@ -5925,9 +5926,9 @@ export const GameBalance = {
- Zero TypeScript errors in strict mode
- Consistent adherence to coding standards
- Comprehensive documentation coverage
==================== END: templates#game-architecture-tmpl ====================
==================== END: .bmad-2d-phaser-game-dev/templates/game-architecture-tmpl.md ====================
==================== START: checklists#game-story-dod-checklist ====================
==================== START: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
# Game Development Story Definition of Done Checklist
## Story Completeness
@@ -6088,9 +6089,9 @@ export const GameBalance = {
**Additional Notes:**
_Any specific concerns, recommendations, or clarifications needed before development begins._
==================== END: checklists#game-story-dod-checklist ====================
==================== END: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
==================== START: data#development-guidelines ====================
==================== START: .bmad-2d-phaser-game-dev/data/development-guidelines.md ====================
# Game Development Guidelines
## Overview
@@ -6742,9 +6743,9 @@ src/
- **Asset Streaming**: Background loading for upcoming content
These guidelines ensure consistent, high-quality game development that meets performance targets and maintains code quality across all implementation stories.
==================== END: data#development-guidelines ====================
==================== END: .bmad-2d-phaser-game-dev/data/development-guidelines.md ====================
==================== START: tasks#create-game-story ====================
==================== START: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
# Create Game Development Story Task
## Purpose
@@ -6804,7 +6805,7 @@ Before creating stories, ensure you have:
### 3. Template Execution
**Load Template:**
Use `templates#game-story-tmpl` following all embedded LLM instructions
Use `.bmad-2d-phaser-game-dev/templates/game-story-tmpl.md` following all embedded LLM instructions
**Key Focus Areas:**
@@ -6840,7 +6841,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 `.bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md` against completed story
**Story Criteria:**
@@ -6961,9 +6962,9 @@ Execute `checklists#game-story-dod-checklist` against completed story
- Testing → Done
This task ensures game development stories are immediately actionable and enable efficient AI-driven development of game features.
==================== END: tasks#create-game-story ====================
==================== END: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
==================== START: templates#game-story-tmpl ====================
==================== START: .bmad-2d-phaser-game-dev/templates/game-story-tmpl.md ====================
# Story: {{Story Title}}
**Epic:** {{Epic Name}}
@@ -7199,9 +7200,9 @@ class {{ClassName}} extends {{PhaseClass}} {
- {{future_enhancement_1}}
- {{future_optimization_1}}
==================== END: templates#game-story-tmpl ====================
==================== END: .bmad-2d-phaser-game-dev/templates/game-story-tmpl.md ====================
==================== START: workflows#game-dev-greenfield ====================
==================== START: .bmad-2d-phaser-game-dev/workflows/game-dev-greenfield.yaml ====================
workflow:
id: game-dev-greenfield
name: Game Development - Greenfield Project
@@ -7385,9 +7386,9 @@ workflow:
- Testing framework in place
- Team roles and responsibilities defined
- First implementation stories created and ready
==================== END: workflows#game-dev-greenfield ====================
==================== END: .bmad-2d-phaser-game-dev/workflows/game-dev-greenfield.yaml ====================
==================== START: workflows#game-prototype ====================
==================== START: .bmad-2d-phaser-game-dev/workflows/game-prototype.yaml ====================
workflow:
id: game-prototype
name: Game Prototype Development
@@ -7563,4 +7564,4 @@ workflow:
technical_to_stories: Technical plan complete. Create focused implementation stories for prototype development.
stories_to_implementation: Stories ready. Begin iterative implementation with frequent playtesting and design validation.
prototype_to_evaluation: Prototype playable. Evaluate core mechanics, gather feedback, and determine next development steps.
==================== END: workflows#game-prototype ====================
==================== END: .bmad-2d-phaser-game-dev/workflows/game-prototype.yaml ====================