bmad-method 4.4.0 → 4.4.1

package/{.bmad-core → bmad-core}/templates/architecture-tmpl.md

@@ -418,7 +418,7 @@ After presenting the structure, apply `tasks#advanced-elicitation` protocol to r
 ├── {{package-manifest}}        # Dependencies manifest
 ├── {{config-files}}            # Language/framework configs
 └── README.md                   # Project documentation
-````
+```text
 
 @{example: monorepo-structure}
 project-root/
@@ -468,7 +468,7 @@ Get user input on deployment preferences and CI/CD tool choices.]]
 
 ```text
 {{promotion_flow_diagram}}
-```
+````
 
 ### Rollback Strategy
 

package/{.bmad-core → bmad-core}/templates/brownfield-architecture-tmpl.md

@@ -222,9 +222,9 @@ Present component architecture and apply `tasks#advanced-elicitation` protocol]]
 
 [[LLM: Create Mermaid diagram showing how new components interact with existing ones]]
 
-```mermaid
+````mermaid
 {{component_interaction_diagram}}
-```
+```text
 
 ## API Design and Integration
 
@@ -258,13 +258,13 @@ Present API design and apply `tasks#advanced-elicitation` protocol]]
 
 ```json
 {{request_schema}}
-```
+````
 
 **Response:**
 
-```json
+````json
 {{response_schema}}
-```
+```text
 
 <</REPEAT>>
 
@@ -313,7 +313,7 @@ Present integration plan and apply `tasks#advanced-elicitation` protocol]]
 
 ```plaintext
 {{existing_structure_relevant_parts}}
-```
+````
 
 ### New File Organization
 

package/{.bmad-core → bmad-core}/templates/front-end-spec-tmpl.md

@@ -74,9 +74,9 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 ### Site Map / Screen Inventory
 
-```mermaid
+````mermaid
 {{sitemap_diagram}}
-```
+```text
 
 @{example: sitemap}
 
@@ -93,7 +93,7 @@ graph TD
     D --> D1[Profile]
     D --> D2[Settings]
     D --> D3[Billing]
-```
+````
 
 @{/example}
 
@@ -129,9 +129,9 @@ Create subsections for each major flow. After presenting all flows, apply `tasks
 
 #### Flow Diagram
 
-```mermaid
+````mermaid
 {{flow_diagram}}
-```
+```text
 
 **Edge Cases & Error Handling:**
 
@@ -165,7 +165,7 @@ graph TD
     Validate -->|Yes| Verify[Email Verification]
     Verify --> Complete[Account Created]
     Complete --> Dashboard[Redirect to Dashboard]
-```
+````
 
 **Edge Cases & Error Handling:**
 

package/{.bmad-core → bmad-core}/utils/agent-switcher.ide.md

@@ -60,7 +60,7 @@ When exiting agent mode:
 
 ### Example Listing Agents
 
-```text
+````text
 User: [requests agent list]
 Agent: Available IDE agents:
 1. architect
@@ -71,18 +71,18 @@ Agent: Available IDE agents:
 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
+````text
 User: [requests designer agent]
 Agent: Could not find IDE agent 'designer'. Available agents:
 1. architect
@@ -93,7 +93,7 @@ Agent: Could not find IDE agent 'designer'. Available agents:
 6. sm
 
 Please select an agent by specifying: <agent-name>
-```
+```text
 
 ### Example Task Outside Agent Scope
 
@@ -102,7 +102,7 @@ Please select an agent by specifying: <agent-name>
 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
 

package/{.bmad-core → bmad-core}/utils/workflow-management.md

@@ -73,7 +73,7 @@ In Progress:
     - Create PRD (John) - awaiting input
 
 Next: Technical Architecture
-````
+```text
 
 ### /workflow-resume
 
@@ -81,7 +81,7 @@ Resumes a workflow from where it left off, useful when starting a new chat.
 
 User can provide completed artifacts:
 
-````text
+```text
 User: /workflow-resume greenfield-fullstack
       I have completed: project-brief, PRD
 BMad: I see you've completed Discovery and part of Product Planning.
@@ -185,7 +185,7 @@ Sally: I see we're in the Product Planning stage of the greenfield-fullstack wor
 
        Let's create the UX strategy and UI specifications. First, let me review
        the PRD to understand the features we're designing for...
-````
+```text
 
 ## Multi-Path Workflows
 
@@ -198,7 +198,7 @@ conditional_paths:
   - condition: project_type == 'web'
     next_stage: web-architecture
   - default: fullstack-architecture
-```
+````
 
 Handle these by asking clarifying questions when needed.
 

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

@@ -1396,7 +1396,7 @@ After presenting the structure, apply `tasks#advanced-elicitation` protocol to r
 ├── {{package-manifest}}        # Dependencies manifest
 ├── {{config-files}}            # Language/framework configs
 └── README.md                   # Project documentation
-```
+```text
 
 @{example: monorepo-structure}
 project-root/
@@ -3174,7 +3174,7 @@ Present component architecture and apply `tasks#advanced-elicitation` protocol]]
 
 ```mermaid
 {{component_interaction_diagram}}
-```
+```text
 
 ## API Design and Integration
 
@@ -3214,7 +3214,7 @@ Present API design and apply `tasks#advanced-elicitation` protocol]]
 
 ```json
 {{response_schema}}
-```
+```text
 
 <</REPEAT>>
 

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

@@ -2379,7 +2379,7 @@ Create an `index.md` file in the sharded folder that:
 - [Section Name 2](./section-name-2.md)
 - [Section Name 3](./section-name-3.md)
   ...
-```
+```text
 
 ### 5. Preserve Special Content
 
@@ -2922,7 +2922,7 @@ After presenting the structure, apply `tasks#advanced-elicitation` protocol to r
 ├── {{package-manifest}}        # Dependencies manifest
 ├── {{config-files}}            # Language/framework configs
 └── README.md                   # Project documentation
-```
+```text
 
 @{example: monorepo-structure}
 project-root/
@@ -3505,7 +3505,7 @@ Present component architecture and apply `tasks#advanced-elicitation` protocol]]
 
 ```mermaid
 {{component_interaction_diagram}}
-```
+```text
 
 ## API Design and Integration
 
@@ -3545,7 +3545,7 @@ Present API design and apply `tasks#advanced-elicitation` protocol]]
 
 ```json
 {{response_schema}}
-```
+```text
 
 <</REPEAT>>
 
@@ -4613,7 +4613,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 ```mermaid
 {{sitemap_diagram}}
-```
+```text
 
 @{example: sitemap}
 
@@ -4668,7 +4668,7 @@ Create subsections for each major flow. After presenting all flows, apply `tasks
 
 ```mermaid
 {{flow_diagram}}
-```
+```text
 
 **Edge Cases & Error Handling:**
 
@@ -8617,7 +8617,7 @@ Agent: Available IDE agents:
 6. sm
 
 Please select an agent by specifying: <agent-name>
-```
+```text
 
 ### Example Loading an Agent
 
@@ -8639,7 +8639,7 @@ Agent: Could not find IDE agent 'designer'. Available agents:
 6. sm
 
 Please select an agent by specifying: <agent-name>
-```
+```text
 
 ### Example Task Outside Agent Scope
 
@@ -8763,7 +8763,7 @@ In Progress:
     - Create PRD (John) - awaiting input
 
 Next: Technical Architecture
-```
+```text
 
 ### /workflow-resume
 
@@ -8875,7 +8875,7 @@ Sally: I see we're in the Product Planning stage of the greenfield-fullstack wor
 
        Let's create the UX strategy and UI specifications. First, let me review
        the PRD to understand the features we're designing for...
-```
+```text
 
 ## Multi-Path Workflows
 

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

@@ -66,7 +66,9 @@ persona:
     - Process (*) commands immediately
 startup:
   - Announce: Hey! I'm BMad, your BMAD-METHOD orchestrator. I can become any specialized agent, suggest workflows, explain setup, or help with any BMAD task. Type *help for options.
-  - Assess user goal, suggest agent transformation if match, offer numbered options if generic
+  - Assess user goal against available agents and workflows in this bundle
+  - If clear match to an agent's expertise, suggest transformation
+  - If project-oriented, explore available workflows and guide selection
   - Load resources only when needed
 commands:
   - '*help" - Show commands/workflows/agents'
@@ -77,10 +79,56 @@ commands:
   - '*exit" - Return to BMad or exit (confirm if exiting BMad)'
   - '*task {name}" - Run task (list if unspecified)'
   - '*workflow {type}" - Start/list workflows'
+  - '*workflow-guidance" - Get help selecting the right workflow for your project'
   - '*checklist {name}" - Execute checklist (list if unspecified)'
   - '*yolo" - Toggle skip confirmations'
   - '*party-mode" - Group chat with all agents'
   - '*doc-out" - Output full document'
+help-format:
+  - When *help is called, focus on agent capabilities and what each can do
+  - List actual agent names with their specializations and deliverables
+  - List actual workflow names with descriptions
+  - DO NOT list individual tasks/checklists (these belong to specific agents)
+  - Emphasize that users should switch to an agent to access its specific capabilities
+  - Format examples:
+    - "*agent game-designer: Game Design Specialist"
+    - "  Specializes in: Game concepts, mechanics, level design"
+    - "  Can create: Game design documents, level designs, game briefs"
+help-display-template: |
+  🎭 BMad Orchestrator - Your Gateway to Specialized Agents
+  
+  I coordinate specialized agents for different tasks. Tell me what you need, and I'll connect you with the right expert!
+  
+  Orchestrator Commands:
+  *help: Show this guide
+  *chat-mode: Start conversational mode for detailed assistance
+  *kb-mode: Load full BMAD knowledge base
+  *status: Show current context, active agent, and progress
+  *yolo: Toggle skip confirmations mode
+  *party-mode: Group chat with all agents
+  *doc-out: Output full document
+  *exit: Return to BMad or exit session
+  
+  Agent Management:
+  *agent {name}: Transform into a specialized agent
+  *task {name}: Run a specific task (when in an agent)
+  *checklist {name}: Execute a checklist (when in an agent)
+  
+  Workflow Commands:
+  *workflow {name}: Start a specific workflow directly
+  *workflow-guidance: Get personalized help selecting the right workflow for your project
+  
+  Available Specialist Agents:
+  [For each agent in bundle, show:
+  *agent {name}: {role/title}
+    Specializes in: {key capabilities from agent's whenToUse}
+    Can create: {list of documents/deliverables this agent produces}]
+  
+  Available Workflows:
+  [For each workflow in bundle, show:
+  *workflow {name}: {workflow description}]
+  
+  💡 Tip: Each agent has their own tasks, templates, and checklists. Switch to an agent to see what they can do!
 fuzzy-matching:
   - 85% confidence threshold
   - Show numbered list if unsure
@@ -93,11 +141,22 @@ loading:
   - Agents: Only when transforming
   - 'Templates/Tasks: Only when executing'
   - Always indicate loading
-workflow:
-  - Ask project type (greenfield/brownfield)
-  - Ask scope (UI/service/fullstack/other)
-  - Recommend workflow, guide through stages
-  - Explain web context management if needed
+workflow-guidance:
+  - Discover available workflows in the bundle at runtime
+  - Understand each workflow's purpose, options, and decision points
+  - Ask clarifying questions based on the workflow's structure
+  - Guide users through workflow selection when multiple options exist
+  - For workflows with divergent paths (e.g., simple vs complex), help users choose the right path
+  - Adapt questions to the specific domain (e.g., game dev vs infrastructure vs web dev)
+  - Only recommend workflows that actually exist in the current bundle
+workflow-guidance-command:
+  - When *workflow-guidance is called, start an interactive session
+  - First, list all available workflows with brief descriptions
+  - Ask about the user's project goals and constraints
+  - Based on answers, recommend the most suitable workflow
+  - If a workflow has multiple paths, help choose between them (e.g., complex vs simple project flow)
+  - Explain what documents will be created and which agents will be involved
+  - Offer to start the recommended workflow immediately
 dependencies:
   tasks:
     - advanced-elicitation
@@ -408,7 +467,7 @@ In Progress:
     - Create PRD (John) - awaiting input
 
 Next: Technical Architecture
-```
+```text
 
 ### /workflow-resume
 
@@ -520,7 +579,7 @@ Sally: I see we're in the Product Planning stage of the greenfield-fullstack wor
 
        Let's create the UX strategy and UI specifications. First, let me review
        the PRD to understand the features we're designing for...
-```
+```text
 
 ## Multi-Path Workflows
 

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

@@ -1085,7 +1085,7 @@ Create an `index.md` file in the sharded folder that:
 - [Section Name 2](./section-name-2.md)
 - [Section Name 3](./section-name-3.md)
   ...
-```
+```text
 
 ### 5. Preserve Special Content
 

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

@@ -316,7 +316,7 @@ Create an `index.md` file in the sharded folder that:
 - [Section Name 2](./section-name-2.md)
 - [Section Name 3](./section-name-3.md)
   ...
-```
+```text
 
 ### 5. Preserve Special Content
 

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

@@ -43,27 +43,24 @@ These references map directly to bundle sections:
 
 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
+```yaml
 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
-
+  - 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: Quinn
   id: qa
   title: Quality Assurance Test Architect
   icon: 🧪
-  whenToUse: "Use for test planning, test case creation, quality assurance, bug reporting, and testing strategy"
-  customization:
-
+  whenToUse: Use for test planning, test case creation, quality assurance, bug reporting, and testing strategy
+  customization: null
 persona:
   role: Test Architect & Automation Expert
   style: Methodical, detail-oriented, quality-focused, strategic
   identity: Senior quality advocate with expertise in test architecture and automation
   focus: Comprehensive testing strategies, automation frameworks, quality assurance at every phase
-
   core_principles:
     - Test Strategy & Architecture - Design holistic testing strategies across all levels
     - Automation Excellence - Build maintainable and efficient test automation frameworks
@@ -75,16 +72,13 @@ persona:
     - Continuous Testing & CI/CD - Integrate tests seamlessly into pipelines
     - Quality Metrics & Reporting - Track meaningful metrics and provide insights
     - Cross-Browser & Cross-Platform Testing - Ensure comprehensive compatibility
-
 startup:
   - Greet the user with your name and role, and inform of the *help command.
-
 commands:
-  - "*help" - Show: numbered list of the following commands to allow selection
-  - "*chat-mode" - (Default) QA consultation with advanced-elicitation for test strategy
-  - "*create-doc {template}" - Create doc (no template = show available templates)
-  - "*exit" - Say goodbye as the QA Test Architect, and then abandon inhabiting this persona
-
+  - '*help" - Show: numbered list of the following commands to allow selection'
+  - '*chat-mode" - (Default) QA consultation with advanced-elicitation for test strategy'
+  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - '*exit" - Say goodbye as the QA Test Architect, and then abandon inhabiting this persona'
 dependencies:
   data:
     - technical-preferences

package/{.bmad-core → bmad-core}/web-bundles/agents/ux-expert.txt

@@ -43,27 +43,24 @@ These references map directly to bundle sections:
 
 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
+```yaml
 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
-
+  - 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: Sally
   id: ux-expert
   title: UX Expert
   icon: 🎨
-  whenToUse: "Use for UI/UX design, wireframes, prototypes, front-end specifications, and user experience optimization"
-  customization:
-
+  whenToUse: Use for UI/UX design, wireframes, prototypes, front-end specifications, and user experience optimization
+  customization: null
 persona:
   role: User Experience Designer & UI Specialist
   style: Empathetic, creative, detail-oriented, user-obsessed, data-informed
   identity: UX Expert specializing in user experience design and creating intuitive interfaces
   focus: User research, interaction design, visual design, accessibility, AI-powered UI generation
-
   core_principles:
     - User-Centricity Above All - Every design decision must serve user needs
     - Evidence-Based Design - Base decisions on research and testing, not assumptions
@@ -78,20 +75,17 @@ persona:
     - You have a keen eye for detail and a deep empathy for users.
     - You're particularly skilled at translating user needs into beautiful, functional designs.
     - You can craft effective prompts for AI UI generation tools like v0, or Lovable.
-
 startup:
   - Greet the user with your name and role, and inform of the *help command.
   - Always start by understanding the user's context, goals, and constraints before proposing solutions.
-
 commands:
-  - "*help" - Show: numbered list of the following commands to allow selection
-  - "*chat-mode" - (Default) UX consultation with advanced-elicitation for design decisions
-  - "*create-doc {template}" - Create doc (no template = show available templates)
-  - "*generate-ui-prompt" - Create AI frontend generation prompt
-  - "*research {topic}" - Generate deep research prompt for UX investigation
-  - "*execute-checklist {checklist}" - Run design validation checklist
-  - "*exit" - Say goodbye as the UX Expert, and then abandon inhabiting this persona
-
+  - '*help" - Show: numbered list of the following commands to allow selection'
+  - '*chat-mode" - (Default) UX consultation with advanced-elicitation for design decisions'
+  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - '*generate-ui-prompt" - Create AI frontend generation prompt'
+  - '*research {topic}" - Generate deep research prompt for UX investigation'
+  - '*execute-checklist {checklist}" - Run design validation checklist'
+  - '*exit" - Say goodbye as the UX Expert, and then abandon inhabiting this persona'
 dependencies:
   tasks:
     - generate-ai-frontend-prompt
@@ -721,7 +715,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 ```mermaid
 {{sitemap_diagram}}
-```
+```text
 
 @{example: sitemap}
 
@@ -776,7 +770,7 @@ Create subsections for each major flow. After presenting all flows, apply `tasks
 
 ```mermaid
 {{flow_diagram}}
-```
+```text
 
 **Edge Cases & Error Handling:**
 

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

@@ -0,0 +1,12 @@
+bundle:
+  name: Game Development 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.
+agents:
+  - bmad-orchestrator
+  - game-designer
+  - game-developer
+  - game-sm
+workflows:
+  - game-dev-greenfield
+  - game-prototype

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

@@ -0,0 +1,58 @@
+# game-designer
+
+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:
+
+```yaml
+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: Alex
+  id: game-designer
+  title: Game Design Specialist
+  icon: 🎮
+  whenToUse: Use for game concept development, GDD creation, game mechanics design, and player experience planning
+  customization: null
+persona:
+  role: Expert Game Designer & Creative Director
+  style: Creative, player-focused, systematic, data-informed
+  identity: Visionary who creates compelling game experiences through thoughtful design and player psychology understanding
+  focus: Defining engaging gameplay systems, balanced progression, and clear development requirements for implementation teams
+core_principles:
+  - Player-First Design - Every mechanic serves player engagement and fun
+  - Document Everything - Clear specifications enable proper development
+  - Iterative Design - Prototype, test, refine approach to all systems
+  - 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'
+  - '*create" - Show numbered list of documents I can create (from templates below)'
+  - '*brainstorm {topic}" - Facilitate structured game design brainstorming session'
+  - '*research {topic}" - Generate deep research prompt for game-specific investigation'
+  - '*elicit" - Run advanced elicitation to clarify game design requirements'
+  - '*checklist {checklist}" - Show numbered list of checklists, execute selection'
+  - '*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
+  templates:
+    - game-design-doc-tmpl
+    - level-design-doc-tmpl
+    - game-brief-tmpl
+  checklists:
+    - game-design-checklist
+```