bmad-method 4.36.2 → 4.37.0-beta.2

package/bmad-core/tasks/create-brownfield-story.md

@@ -128,7 +128,7 @@ Critical: For brownfield, ALWAYS include criteria about maintaining existing fun
 Standard structure:
 
 1. New functionality works as specified
-2. Existing {{affected feature}} continues to work unchanged
+2. Existing {{affected feature}} continues to work unchanged  
 3. Integration with {{existing system}} maintains current behavior
 4. No regression in {{related area}}
 5. Performance remains within acceptable bounds
@@ -139,19 +139,16 @@ Critical: This is where you'll need to be interactive with the user if informati
 
 Create Dev Technical Guidance section with available information:
 
-````markdown
+```markdown
 ## Dev Technical Guidance
 
 ### Existing System Context
-
 [Extract from available documentation]
 
 ### Integration Approach
-
 [Based on patterns found or ask user]
 
 ### Technical Constraints
-
 [From documentation or user input]
 
 ### Missing Information
@@ -194,7 +191,6 @@ Example task structure for brownfield:
   - [ ] Integration test for {{integration point}}
   - [ ] Update existing tests if needed
 ```
-````
 
 ### 5. Risk Assessment and Mitigation
 
@@ -206,17 +202,14 @@ Add section for brownfield-specific risks:
 ## Risk Assessment
 
 ### Implementation Risks
-
 - **Primary Risk**: {{main risk to existing system}}
 - **Mitigation**: {{how to address}}
 - **Verification**: {{how to confirm safety}}
 
 ### Rollback Plan
-
 - {{Simple steps to undo changes if needed}}
 
 ### Safety Checks
-
 - [ ] Existing {{feature}} tested before changes
 - [ ] Changes can be feature-flagged or isolated
 - [ ] Rollback procedure documented
@@ -259,7 +252,6 @@ Include header noting documentation context:
 <!-- Context: Brownfield enhancement to {{existing system}} -->
 
 ## Status: Draft
-
 [Rest of story content...]
 ```
 
@@ -280,7 +272,7 @@ Key Integration Points Identified:
 Risks Noted:
 - {{primary risk}}
 
-{{If missing info}}:
+{{If missing info}}: 
 Note: Some technical details were unclear. The story includes exploration tasks to gather needed information during implementation.
 
 Next Steps:

package/bmad-core/tasks/create-deep-research-prompt.md

@@ -21,54 +21,63 @@ CRITICAL: First, help the user select the most appropriate research focus based
 Present these numbered options to the user:
 
 1. **Product Validation Research**
+
    - Validate product hypotheses and market fit
    - Test assumptions about user needs and solutions
    - Assess technical and business feasibility
    - Identify risks and mitigation strategies
 
 2. **Market Opportunity Research**
+
    - Analyze market size and growth potential
    - Identify market segments and dynamics
    - Assess market entry strategies
    - Evaluate timing and market readiness
 
 3. **User & Customer Research**
+
    - Deep dive into user personas and behaviors
    - Understand jobs-to-be-done and pain points
    - Map customer journeys and touchpoints
    - Analyze willingness to pay and value perception
 
 4. **Competitive Intelligence Research**
+
    - Detailed competitor analysis and positioning
    - Feature and capability comparisons
    - Business model and strategy analysis
    - Identify competitive advantages and gaps
 
 5. **Technology & Innovation Research**
+
    - Assess technology trends and possibilities
    - Evaluate technical approaches and architectures
    - Identify emerging technologies and disruptions
    - Analyze build vs. buy vs. partner options
 
 6. **Industry & Ecosystem Research**
+
    - Map industry value chains and dynamics
    - Identify key players and relationships
    - Analyze regulatory and compliance factors
    - Understand partnership opportunities
 
 7. **Strategic Options Research**
+
    - Evaluate different strategic directions
    - Assess business model alternatives
    - Analyze go-to-market strategies
    - Consider expansion and scaling paths
 
 8. **Risk & Feasibility Research**
+
    - Identify and assess various risk factors
    - Evaluate implementation challenges
    - Analyze resource requirements
    - Consider regulatory and legal implications
 
 9. **Custom Research Focus**
+
    - User-defined research objectives
    - Specialized domain investigation
    - Cross-functional research needs
@@ -237,11 +246,13 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
 ### 5. Review and Refinement
 
 1. **Present Complete Prompt**
+
    - Show the full research prompt
    - Explain key elements and rationale
    - Highlight any assumptions made
 
 2. **Gather Feedback**
+
    - Are the objectives clear and correct?
    - Do the questions address all concerns?
    - Is the scope appropriate?

package/bmad-core/tasks/document-project.md

@@ -111,9 +111,9 @@ This document captures the CURRENT STATE of the [Project Name] codebase, includi
 
 ### Change Log
 
-| Date   | Version | Description                 | Author    |
-| ------ | ------- | --------------------------- | --------- |
-| [Date] | 1.0     | Initial brownfield analysis | [Analyst] |
+| Date | Version | Description | Author |
+|------|---------|-------------|--------|
+| [Date] | 1.0 | Initial brownfield analysis | [Analyst] |
 
 ## Quick Reference - Key Files and Entry Points
 
@@ -136,11 +136,11 @@ This document captures the CURRENT STATE of the [Project Name] codebase, includi
 
 ### Actual Tech Stack (from package.json/requirements.txt)
 
-| Category  | Technology | Version | Notes                      |
-| --------- | ---------- | ------- | -------------------------- |
-| Runtime   | Node.js    | 16.x    | [Any constraints]          |
-| Framework | Express    | 4.18.2  | [Custom middleware?]       |
-| Database  | PostgreSQL | 13      | [Connection pooling setup] |
+| Category | Technology | Version | Notes |
+|----------|------------|---------|--------|
+| Runtime | Node.js | 16.x | [Any constraints] |
+| Framework | Express | 4.18.2 | [Custom middleware?] |
+| Database | PostgreSQL | 13 | [Connection pooling setup] |
 
 etc...
 
@@ -179,7 +179,6 @@ project-root/
 ### Data Models
 
 Instead of duplicating, reference actual model files:
-
 - **User Model**: See `src/models/User.js`
 - **Order Model**: See `src/models/Order.js`
 - **Related Types**: TypeScript definitions in `src/types/`
@@ -209,10 +208,10 @@ Instead of duplicating, reference actual model files:
 
 ### External Services
 
-| Service  | Purpose  | Integration Type | Key Files                      |
-| -------- | -------- | ---------------- | ------------------------------ |
-| Stripe   | Payments | REST API         | `src/integrations/stripe/`     |
-| SendGrid | Emails   | SDK              | `src/services/emailService.js` |
+| Service | Purpose | Integration Type | Key Files |
+|---------|---------|------------------|-----------|
+| Stripe | Payments | REST API | `src/integrations/stripe/` |
+| SendGrid | Emails | SDK | `src/services/emailService.js` |
 
 etc...
 
@@ -257,7 +256,6 @@ npm run test:integration  # Runs integration tests (requires local DB)
 ### Files That Will Need Modification
 
 Based on the enhancement requirements, these files will be affected:
-
 - `src/services/userService.js` - Add new user fields
 - `src/models/User.js` - Update schema
 - `src/routes/userRoutes.js` - New endpoints
@@ -340,4 +338,4 @@ Apply the advanced elicitation task after major sections to refine based on user
 - References actual files rather than duplicating content when possible
 - 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
+- The goal is PRACTICAL documentation for AI agents doing real work

package/bmad-core/tasks/facilitate-brainstorming-session.md

@@ -43,7 +43,7 @@ If user selects Option 1, present numbered list of techniques from the brainstor
 1. Apply selected technique according to data file description
 2. Keep engaging with technique until user indicates they want to:
    - Choose a different technique
-   - Apply current ideas to a new technique
+   - Apply current ideas to a new technique  
    - Move to convergent phase
    - End session
 

package/bmad-core/tasks/index-docs.md

@@ -11,12 +11,14 @@ You are now operating as a Documentation Indexer. Your goal is to ensure all doc
 ### Required Steps
 
 1. First, locate and scan:
+
    - The `docs/` directory and all subdirectories
    - The existing `docs/index.md` file (create if absent)
    - All markdown (`.md`) and text (`.txt`) files in the documentation structure
    - Note the folder structure for hierarchical organization
 
 2. For the existing `docs/index.md`:
+
    - Parse current entries
    - Note existing file references and descriptions
    - Identify any broken links or missing files
@@ -24,6 +26,7 @@ You are now operating as a Documentation Indexer. Your goal is to ensure all doc
    - Preserve existing folder sections
 
 3. For each documentation file found:
+
    - Extract the title (from first heading or filename)
    - Generate a brief description by analyzing the content
    - Create a relative markdown link to the file
@@ -32,6 +35,7 @@ You are now operating as a Documentation Indexer. Your goal is to ensure all doc
    - If missing or outdated, prepare an update
 
 4. For any missing or non-existent files found in index:
+
    - Present a list of all entries that reference non-existent files
    - For each entry:
      - Show the full entry details (title, path, description)
@@ -84,6 +88,7 @@ Documents within the `another-folder/` directory:
 ### [Nested Document](./another-folder/document.md)
 
 Description of nested document.
+
 ```
 
 ### Index Entry Format
@@ -152,6 +157,7 @@ For each file referenced in the index but not found in the filesystem:
 ### Special Cases
 
 1. **Sharded Documents**: If a folder contains an `index.md` file, treat it as a sharded document:
+
    - Use the folder's `index.md` title as the section title
    - List the folder's documents as subsections
    - Note in the description that this is a multi-part document

package/bmad-core/tasks/kb-mode-interaction.md

@@ -6,7 +6,7 @@ Provide a user-friendly interface to the BMad knowledge base without overwhelmin
 
 ## Instructions
 
-When entering KB mode (\*kb-mode), follow these steps:
+When entering KB mode (*kb-mode), follow these steps:
 
 ### 1. Welcome and Guide
 
@@ -48,12 +48,12 @@ Or ask me about anything else related to BMad-Method!
 When user is done or wants to exit KB mode:
 
 - Summarize key points discussed if helpful
-- Remind them they can return to KB mode anytime with \*kb-mode
+- Remind them they can return to KB mode anytime with *kb-mode
 - Suggest next steps based on what was discussed
 
 ## Example Interaction
 
-**User**: \*kb-mode
+**User**: *kb-mode
 
 **Assistant**: I've entered KB mode and have access to the full BMad knowledge base. I can help you with detailed information about any aspect of BMad-Method.
 

package/bmad-core/tasks/review-story.md

@@ -81,31 +81,25 @@ After review and any refactoring, append your results to the story file in the Q
 ## QA Results
 
 ### Review Date: [Date]
-
 ### Reviewed By: Quinn (Senior Developer QA)
 
 ### Code Quality Assessment
-
 [Overall assessment of implementation quality]
 
 ### Refactoring Performed
-
 [List any refactoring you performed with explanations]
-
 - **File**: [filename]
   - **Change**: [what was changed]
   - **Why**: [reason for change]
   - **How**: [how it improves the code]
 
 ### Compliance Check
-
 - Coding Standards: [✓/✗] [notes if any]
 - Project Structure: [✓/✗] [notes if any]
 - Testing Strategy: [✓/✗] [notes if any]
 - All ACs Met: [✓/✗] [notes if any]
 
 ### Improvements Checklist
-
 [Check off items you handled yourself, leave unchecked for dev to address]
 
 - [x] Refactored user service for better error handling (services/user.service.ts)
@@ -115,15 +109,12 @@ After review and any refactoring, append your results to the story file in the Q
 - [ ] Update API documentation for new error codes
 
 ### Security Review
-
 [Any security concerns found and whether addressed]
 
 ### Performance Considerations
-
 [Any performance issues found and whether addressed]
 
 ### Final Status
-
 [✓ Approved - Ready for Done] / [✗ Changes Required - See unchecked items above]
 ```
 
@@ -151,4 +142,4 @@ After review:
 
 1. If all items are checked and approved: Update story status to "Done"
 2. If unchecked items remain: Keep status as "Review" for dev to address
-3. Always provide constructive feedback and explanations for learning
+3. Always provide constructive feedback and explanations for learning

package/bmad-core/tasks/shard-doc.md

@@ -91,11 +91,13 @@ CRITICAL: Use proper parsing that understands markdown context. A ## inside a co
 For each extracted section:
 
 1. **Generate filename**: Convert the section heading to lowercase-dash-case
+
    - Remove special characters
    - Replace spaces with dashes
    - Example: "## Tech Stack" → `tech-stack.md`
 
 2. **Adjust heading levels**:
+
    - The level 2 heading becomes level 1 (# instead of ##) in the sharded new document
    - All subsection levels decrease by 1:
 

package/common/tasks/execute-checklist.md

@@ -9,6 +9,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
 ## Instructions
 
 1. **Initial Assessment**
+
    - 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
@@ -21,12 +22,14 @@ If the user asks or does not specify a specific checklist, list the checklists a
      - All at once (YOLO mode - recommended for checklists, there will be a summary of sections at the end to discuss)
 
 2. **Document and Artifact Gathering**
+
    - Each checklist will specify its required documents/artifacts at the beginning
    - Follow the checklist's specific instructions for what to gather, generally a file can be resolved in the docs folder, if not or unsure, halt and ask or confirm with the user.
 
 3. **Checklist Processing**
 
    If in interactive mode:
+
    - Work through each section of the checklist one at a time
    - For each section:
      - Review all items in the section following instructions for that section embedded in the checklist
@@ -35,6 +38,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
      - Get user confirmation before proceeding to next section or if any thing major do we need to halt and take corrective action
 
    If in YOLO mode:
+
    - Process all sections at once
    - Create a comprehensive report of all findings
    - Present the complete analysis to the user
@@ -42,6 +46,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
 4. **Validation Approach**
 
    For each checklist item:
+
    - Read and understand the requirement
    - Look for evidence in the documentation that satisfies the requirement
    - Consider both explicit mentions and implicit coverage
@@ -55,6 +60,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
 5. **Section Analysis**
 
    For each section:
+
    - think step by step to calculate pass rate
    - Identify common themes in failed items
    - Provide specific recommendations for improvement
@@ -64,6 +70,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
 6. **Final Report**
 
    Prepare a summary that includes:
+
    - Overall checklist completion status
    - Pass rates by section
    - List of failed items with context

package/docs/GUIDING-PRINCIPLES.md

@@ -65,7 +65,7 @@ See [Expansion Packs Guide](../docs/expansion-packs.md) for detailed examples an
 
 ### Template Rules
 
-Templates follow the [BMad Document Template](common/utils/bmad-doc-template.md) specification using YAML format:
+Templates follow the [BMad Document Template](../common/utils/bmad-doc-template.md) specification using YAML format:
 
 1. **Structure**: Templates are defined in YAML with clear metadata, workflow configuration, and section hierarchy
 2. **Separation of Concerns**: Instructions for LLMs are in `instruction` fields, separate from content

package/docs/working-in-the-brownfield.md

@@ -27,7 +27,7 @@ If you have just completed an MVP with BMad, and you want to continue with post-
 ## The Complete Brownfield Workflow
 
 1. **Follow the [<ins>User Guide - Installation</ins>](user-guide.md#installation) steps to setup your agent in the web.**
-2. **Generate a 'flattened' single file of your entire codebase** run: `npx bmad-method flatten`
+2. **Generate a 'flattened' single file of your entire codebase** run: ```npx bmad-method flatten```
 
 ### Choose Your Approach
 

package/expansion-packs/Complete AI Agent System - Blank Templates & Google Cloud Setup/README.md

@@ -8,21 +8,21 @@ This expansion pack provides a complete, deployable starter kit for building and
 
 ## Features
 
-- **Automated GCP Setup**: `gcloud` scripts to configure your project, service accounts, and required APIs in minutes.
-- **Production-Ready Deployment**: Includes a `Dockerfile` and `cloudbuild.yaml` for easy, repeatable deployments to Google Cloud Run.
-- **Rich Template Library**: A comprehensive set of BMad-compatible templates for Teams, Agents, Tasks, Workflows, Documents, and Checklists.
-- **Pre-configured Agent Roles**: Includes powerful master templates for key agent archetypes like Orchestrators and Specialists.
-- **Highly Customizable**: Easily adapt the entire system with company-specific variables and industry-specific configurations.
-- **Powered by Google ADK**: Built on the official Google Agent Development Kit for robust and native integration with Vertex AI services.
+  * **Automated GCP Setup**: `gcloud` scripts to configure your project, service accounts, and required APIs in minutes.
+  * **Production-Ready Deployment**: Includes a `Dockerfile` and `cloudbuild.yaml` for easy, repeatable deployments to Google Cloud Run.
+  * **Rich Template Library**: A comprehensive set of BMad-compatible templates for Teams, Agents, Tasks, Workflows, Documents, and Checklists.
+  * **Pre-configured Agent Roles**: Includes powerful master templates for key agent archetypes like Orchestrators and Specialists.
+  * **Highly Customizable**: Easily adapt the entire system with company-specific variables and industry-specific configurations.
+  * **Powered by Google ADK**: Built on the official Google Agent Development Kit for robust and native integration with Vertex AI services.
 
 ## Prerequisites
 
 Before you begin, ensure you have the following installed and configured:
 
-- A Google Cloud Platform (GCP) Account with an active billing account.
-- The [Google Cloud SDK (`gcloud` CLI)](<https://www.google.com/search?q=%5Bhttps://cloud.google.com/sdk/docs/install%5D(https://cloud.google.com/sdk/docs/install)>) installed and authenticated.
-- [Docker](https://www.docker.com/products/docker-desktop/) installed on your local machine.
-- Python 3.11+
+  * A Google Cloud Platform (GCP) Account with an active billing account.
+  * The [Google Cloud SDK (`gcloud` CLI)](https://www.google.com/search?q=%5Bhttps://cloud.google.com/sdk/docs/install%5D\(https://cloud.google.com/sdk/docs/install\)) installed and authenticated.
+  * [Docker](https://www.docker.com/products/docker-desktop/) installed on your local machine.
+  * Python 3.11+
 
 ## Quick Start Guide
 
@@ -32,9 +32,9 @@ Follow these steps to get your own AI agent system running on Google Cloud.
 
 The setup scripts use placeholder variables. Before running them, open the files in the `/scripts` directory and replace the following placeholders with your own values:
 
-- `{{PROJECT_ID}}`: Your unique Google Cloud project ID.
-- `{{COMPANY_NAME}}`: Your company or project name (used for naming resources).
-- `{{LOCATION}}`: The GCP region you want to deploy to (e.g., `us-central1`).
+  * `{{PROJECT_ID}}`: Your unique Google Cloud project ID.
+  * `{{COMPANY_NAME}}`: Your company or project name (used for naming resources).
+  * `{{LOCATION}}`: The GCP region you want to deploy to (e.g., `us-central1`).
 
 ### 2\. Run the GCP Setup Scripts
 
@@ -106,4 +106,4 @@ This expansion pack has a comprehensive structure to get you started:
 
 ## Contributing
 
-Contributions are welcome\! Please follow the main project's `CONTRIBUTING.md` guidelines. For major changes or new features for this expansion pack, please open an issue or discussion first.
+Contributions are welcome\! Please follow the main project's `CONTRIBUTING.md` guidelines. For major changes or new features for this expansion pack, please open an issue or discussion first.

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

@@ -39,11 +39,13 @@ You are developing games as a "Player Experience CEO" - thinking like a game dir
 ### Phase 1: Game Concept and Design
 
 1. **Game Designer**: Start with brainstorming and concept development
+
    - Use \*brainstorm to explore game concepts and mechanics
    - Create Game Brief using game-brief-tmpl
    - Develop core game pillars and player experience goals
 
 2. **Game Designer**: Create comprehensive Game Design Document
+
    - Use game-design-doc-tmpl to create detailed GDD
    - Define all game mechanics, progression, and balance
    - Specify technical requirements and platform targets
@@ -63,11 +65,13 @@ You are developing games as a "Player Experience CEO" - thinking like a game dir
 ### Phase 3: Story-Driven Development
 
 5. **Game Scrum Master**: Break down design into development stories
+
    - Use create-game-story task to create detailed implementation stories
    - Each story should be immediately actionable by game developers
    - Apply game-story-dod-checklist to ensure story quality
 
 6. **Game Developer**: Implement game features story by story
+
    - Follow TypeScript strict mode and Phaser 3 best practices
    - Maintain 60 FPS performance target throughout development
    - Use test-driven development for game logic components

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

@@ -380,9 +380,7 @@ class InputManager {
   }
 
   private setupKeyboard(): void {
-    this.keys = this.scene.input.keyboard.addKeys(
-      "W,A,S,D,SPACE,ESC,UP,DOWN,LEFT,RIGHT",
-    );
+    this.keys = this.scene.input.keyboard.addKeys("W,A,S,D,SPACE,ESC,UP,DOWN,LEFT,RIGHT");
   }
 
   private setupTouch(): void {
@@ -587,21 +585,25 @@ src/
 ### Story Implementation Process
 
 1. **Read Story Requirements:**
+
    - Understand acceptance criteria
    - Identify technical requirements
    - Review performance constraints
 
 2. **Plan Implementation:**
+
    - Identify files to create/modify
    - Consider component architecture
    - Plan testing approach
 
 3. **Implement Feature:**
+
    - Follow TypeScript strict mode
    - Use established patterns
    - Maintain 60 FPS performance
 
 4. **Test Implementation:**
+
    - Write unit tests for game logic
    - Test cross-platform functionality
    - Validate performance targets

package/expansion-packs/bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md

@@ -18,6 +18,7 @@
 2. If the section contains game flow diagrams, level layouts, or system diagrams, explain each diagram briefly with game development context before offering elicitation options (e.g., "The gameplay loop diagram shows how player actions lead to rewards and progression. Notice how each step maintains player engagement and creates opportunities for skill development.")
 
 3. If the section contains multiple game elements (like multiple mechanics, multiple levels, multiple systems, etc.), inform the user they can apply elicitation actions to:
+
    - The entire section as a whole
    - Individual game elements within the section (specify which element when selecting an action)