chore(release): 4.10.2 [skip ci]

## [4.10.2](https://github.com/bmadcode/BMAD-METHOD/compare/v4.10.1...v4.10.2) (2025-06-20)

### Bug Fixes

* file formatting ([c78a35f](c78a35f547))

.prettierignore

@@ -4,7 +4,6 @@ package-lock.json
 
 # Build outputs
 dist/
-web-bundles/
 
 # Generated files
 *.log

CHANGELOG.md

@@ -1,3 +1,90 @@
+## [4.10.2](https://github.com/bmadcode/BMAD-METHOD/compare/v4.10.1...v4.10.2) (2025-06-20)
+
+
+### Bug Fixes
+
+* file formatting ([c78a35f](https://github.com/bmadcode/BMAD-METHOD/commit/c78a35f547459b07a15d94c827ec05921cd21571))
+
+## [4.10.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.10.0...v4.10.1) (2025-06-20)
+
+
+### Bug Fixes
+
+* SM sometimes would skip the rest of the epic stories, fixed ([1148b32](https://github.com/bmadcode/BMAD-METHOD/commit/1148b32fa97586d2f86d07a70ffbf9bb8c327261))
+
+# [4.10.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.9.2...v4.10.0) (2025-06-19)
+
+
+### Features
+
+* Core Config and doc sharding is now optional in v4 ([ff6112d](https://github.com/bmadcode/BMAD-METHOD/commit/ff6112d6c2f822ed22c75046f5a14f05e36041c2))
+
+## [4.9.2](https://github.com/bmadcode/BMAD-METHOD/compare/v4.9.1...v4.9.2) (2025-06-19)
+
+
+### Bug Fixes
+
+* bad brownfield yml ([09d2ad6](https://github.com/bmadcode/BMAD-METHOD/commit/09d2ad6aea187996d0a2e1dff27d9bf7e3e6dc06))
+
+## [4.9.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.9.0...v4.9.1) (2025-06-19)
+
+
+### Bug Fixes
+
+* dist bundles updated ([d9a989d](https://github.com/bmadcode/BMAD-METHOD/commit/d9a989dbe50da62cf598afa07a8588229c56b69c))
+
+# [4.9.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.8.0...v4.9.0) (2025-06-19)
+
+
+### Features
+
+* dev can use debug log configured in core-config.yml ([0e5aaf0](https://github.com/bmadcode/BMAD-METHOD/commit/0e5aaf07bbc6fd9f2706ea26e35f5f38fd72147a))
+
+# [4.8.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.7.0...v4.8.0) (2025-06-19)
+
+
+### Bug Fixes
+
+* installer has fast v4 update option now to keep the bmad method up to date with changes easily without breaking any customizations from the user. The SM and DEV are much more configurable to find epics stories and architectureal information when the prd and architecture are deviant from v4 templates and/or have not been sharded. so a config will give the user the option to configure the SM to use the full large documents or the sharded versions! ([aea7f3c](https://github.com/bmadcode/BMAD-METHOD/commit/aea7f3cc86e749d25ed18bed761dc2839023b3b3))
+* prevent double installation when updating v4 ([af0e767](https://github.com/bmadcode/BMAD-METHOD/commit/af0e767ecf1b91d41f114e1a5d7bf5da08de57d6))
+* resolve undefined config properties in performUpdate ([0185e01](https://github.com/bmadcode/BMAD-METHOD/commit/0185e012bb579948a4de1ea3950db4e399761619))
+* update file-manager to properly handle YAML manifest files ([724cdd0](https://github.com/bmadcode/BMAD-METHOD/commit/724cdd07a199cb12b82236ad34ca1a0c61eb43e2))
+
+
+### Features
+
+* add early v4 detection for improved update flow ([29e7bbf](https://github.com/bmadcode/BMAD-METHOD/commit/29e7bbf4c5aa7e17854061a5ee695f44324f307a))
+* add file resolution context for IDE agents ([74d9bb4](https://github.com/bmadcode/BMAD-METHOD/commit/74d9bb4b2b70a341673849a1df704f6eac70c3de))
+* update web builder to remove IDE-specific properties from agent bundles ([2f2a1e7](https://github.com/bmadcode/BMAD-METHOD/commit/2f2a1e72d6a70f8127db6ba58a563d0f289621c3))
+
+# [4.7.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.6.3...v4.7.0) (2025-06-19)
+
+
+### Features
+
+* extensive bmad-kb for web orchestrator to be much more helpful ([e663a11](https://github.com/bmadcode/BMAD-METHOD/commit/e663a1146b89e7b5078d9726649a51ae5624da46))
+
+## [4.6.3](https://github.com/bmadcode/BMAD-METHOD/compare/v4.6.2...v4.6.3) (2025-06-19)
+
+
+### Bug Fixes
+
+* SM fixed file resolution issue in v4 ([61ab116](https://github.com/bmadcode/BMAD-METHOD/commit/61ab1161e59a92d657ab663082abcaf26729fa6b))
+
+## [4.6.2](https://github.com/bmadcode/BMAD-METHOD/compare/v4.6.1...v4.6.2) (2025-06-19)
+
+
+### Bug Fixes
+
+* installer upgrade path fixed ([bd6a558](https://github.com/bmadcode/BMAD-METHOD/commit/bd6a55892906077a700f488bde175b57e846729d))
+
+## [4.6.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.6.0...v4.6.1) (2025-06-19)
+
+
+### Bug Fixes
+
+* expansion pack builder now includes proper dependencies from core as needed, and default template file name save added to template llm instructions ([9dded00](https://github.com/bmadcode/BMAD-METHOD/commit/9dded003565879901246885d60787695e0d0b7bd))
+
 # [4.6.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.5.1...v4.6.0) (2025-06-18)
 
 

README.md

@@ -11,6 +11,23 @@
 
 ⭐ **If you find this project helpful or useful, please give it a star!** It helps others discover BMAD-METHOD and you will be notified of updates!
 
+## 🔄 Important: Keeping Your BMAD Installation Updated
+
+**Stay up-to-date effortlessly!** If you already have BMAD-METHOD installed in your project, simply run:
+
+```bash
+npx bmad-method install
+```
+
+The installer will:
+
+- ✅ Automatically detect your existing v4 installation
+- ✅ Update only the files that have changed
+- ✅ Create `.bak` backup files for any custom modifications you've made
+- ✅ Preserve your project-specific configurations
+
+This makes it easy to benefit from the latest improvements, bug fixes, and new agents without losing your customizations!
+
 ## 🚀 Quick Start
 
 ### Fastest Start: Web UI (2 minutes) 🏃‍♂️
@@ -155,11 +172,37 @@ The upgrade process will:
 
 After upgrading:
 
-1. Review your documents in the `docs/` folder
+1. Review your documents in the `docs/` folder - if you had a PRD or architecture in your old project, copy it from the backup to the docs folder if they are not there.
-2. Use `@bmad-master` agent to run the `doc-migration-task` to align your documents with V4 templates
+2. Optionally run the `doc-migration-task` to align your documents with V4 templates - you can do this with your agent my saying something like: 'run {drag in task} against {drag prd or arch file from docs} to align with {drag the template from .bmad-core/templates/full-stack-architecture.md}
-3. If you have separate front-end and backend architecture docs, the migration task will help merge them into a unified `full-stack-architecture.md`
+3. If you have separate front-end and backend architecture docs you can modify step 2 to merge both into a single full stack architecture or separate Front and Back end.
 
-**Note**: The agents in `.bmad-core/` fully replace the items in `bmad-agent/`.
+The reason #2 and 3 are optional is because now BMad V4 makes sharding optional for the SM. See [Core Configuration](#-core-configuration-new-in-v4)
+
+**Note**: The agents in `.bmad-core/` fully replace the items in `bmad-agent/` - you can remove the backup folder versions.
+
+### 🔧 Core Configuration (NEW in V4)
+
+**Critical**: V4 introduces `bmad-core/core-config.yml` - a powerful configuration file that enables BMAD to work seamlessly with any project structure, whether it's V4-optimized or legacy. You can even now use non-standard PRDs and architectures!
+
+#### What is core-config.yml?
+
+This configuration file tells BMAD agents exactly where to find your project documents and how they're structured. It's the key to V4's flexibility and backwards compatibility.
+
+#### Key Features:
+
+- **Version Awareness**: Agents understand if your PRD/Architecture follows V4 conventions or earlier versions
+- **Flexible Document Locations**: Works whether your epics are embedded in PRD or properly sharded
+- **Developer Context**: Define which files the dev agent should always load
+- **Debug Support**: Built-in logging for troubleshooting story implementation
+
+#### Why It Matters:
+
+- **Use BMAD with ANY project structure** - V3, V4, or custom layouts
+- **No forced migrations** - Keep your existing document organization
+- **Customize developer workflow** - Specify exactly which files provide context
+- **Seamless upgrades** - Start with V3 docs and gradually adopt V4 patterns
+
+See the [detailed core-config.yml guide](docs/user-guide.md#core-configuration-coreconfigyml) for configuration examples and best practices.
 
 ## Teams & Workflows
 
@@ -191,7 +234,7 @@ Structured approaches for different scenarios:
 ├── tasks/           # Reusable task definitions
 ├── checklists/      # Quality checklists
 ├── data/            # Knowledge base
-└── web-bundles/     # Pre-built bundles (deprecated - use dist/ instead)
+└── web-bundles/     # Optional can be added if you use the install command and select this folder as a destination for the build bundle files
 
 tools/
 ├── cli.js           # Build tool

bmad-core/agents/analyst.md

@@ -3,6 +3,9 @@
 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
+root: .bmad-core
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
 activation-instructions:
   - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
@@ -34,14 +37,14 @@ persona:
     - Numbered Options Protocol - Always use numbered lists for selections
 startup:
   - Greet the user with your name and role, and inform of the *help command.
-commands:
+commands:  # All commands require * prefix when used (e.g., *help)
-  - '*help" - Show: numbered list of the following commands to allow selection'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - (Default) Strategic analysis consultation with advanced-elicitation'
+  - chat-mode: (Default) Strategic analysis consultation with advanced-elicitation
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - create-doc {template}: Create doc (no template = show available templates)
-  - '*brainstorm {topic}" - Facilitate structured brainstorming session'
+  - brainstorm {topic}: Facilitate structured brainstorming session
-  - '*research {topic}" - Generate deep research prompt for investigation'
+  - research {topic}: Generate deep research prompt for investigation
-  - '*elicit" - Run advanced elicitation to clarify requirements'
+  - elicit: Run advanced elicitation to clarify requirements
-  - '*exit" - Say goodbye as the Business Analyst, and then abandon inhabiting this persona'
+  - exit: Say goodbye as the Business Analyst, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - brainstorming-techniques

bmad-core/agents/architect.md

@@ -3,6 +3,9 @@
 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
+root: .bmad-core
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
 activation-instructions:
   - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
@@ -34,13 +37,13 @@ persona:
 startup:
   - Greet the user with your name and role, and inform of the *help command.
   - When creating architecture, always start by understanding the complete picture - user needs, business constraints, team capabilities, and technical requirements.
-commands:
+commands:  # All commands require * prefix when used (e.g., *help)
-  - '*help" - Show: numbered list of the following commands to allow selection'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - (Default) Architect consultation with advanced-elicitation for complex system design'
+  - chat-mode: (Default) Architect consultation with advanced-elicitation for complex system design
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - create-doc {template}: Create doc (no template = show available templates)
-  - '*execute-checklist {checklist}" - Run architectural validation checklist'
+  - execute-checklist {checklist}: Run architectural validation checklist
-  - '*research {topic}" - Generate deep research prompt for architectural decisions'
+  - research {topic}: Generate deep research prompt for architectural decisions
-  - '*exit" - Say goodbye as the Architect, and then abandon inhabiting this persona'
+  - exit: Say goodbye as the Architect, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - create-doc

bmad-core/agents/bmad-master.md

@@ -3,6 +3,9 @@
 CRITICAL: Read the full YML to understand your operating params, start activation to alter your state of being, follow startup instructions, stay in this being until told to exit this mode:
 
 ```yml
+root: .bmad-core
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
 agent:
   name: BMad Master
   id: bmad-master
@@ -22,21 +25,21 @@ persona:
     - Use numbered lists for choices
     - Process (*) commands immediately
 startup:
-  - Announce: I'm BMad Master, your BMAD task executor. I can run any task, template, util, checklist, workflow, or schema. Type *help or tell me what you need.
+  - Greet the user with your name and role, and inform of the *help command.
   - CRITICAL: Do NOT scan filesystem or load any resources during startup
   - CRITICAL: Do NOT run discovery tasks automatically
   - Wait for user request before any tool use
   - Match request to resources, offer numbered options if unclear
   - Load resources only when explicitly requested
-commands:
+commands:  # All commands require * prefix when used (e.g., *help)
-  - '*help" - Show commands'
+  - help: Show commands
-  - '*chat" - Advanced elicitation + KB mode'
+  - chat: Advanced elicitation + KB mode
-  - '*status" - Current context'
+  - status: Current context
-  - '*task/template/util/checklist/workflow {name}" - Execute (list if no name)'
+  - task {template|util|checklist|workflow}: Execute
-  - '*list {type}" - List resources by type'
+  - list {task|template|util|checklist|workflow}: List resources by type
-  - '*exit" - Exit (confirm)'
+  - exit: Exit (confirm)
-  - '*yolo" - Skip confirmations'
+  - yolo: Toggle Yolo Mode off on - on will skip doc section confirmations
-  - '*doc-out" - Output full document'
+  - doc-out: Output full document
 fuzzy-matching:
   - 85% confidence threshold
   - Show numbered list if unsure
@@ -74,7 +77,6 @@ dependencies:
     - prd-tmpl
     - project-brief-tmpl
     - story-tmpl
-    - web-agent-startup-instructions-template
   data:
     - bmad-kb
     - technical-preferences

bmad-core/agents/bmad-orchestrator.md

@@ -3,6 +3,9 @@
 CRITICAL: Read the full YML to understand your operating params, start activation to alter your state of being, follow startup instructions, stay in this being until told to exit this mode:
 
 ```yaml
+root: .bmad-core
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
 agent:
   name: BMad Orchestrator
   id: bmad-orchestrator
@@ -96,6 +99,11 @@ loading:
   - Agents: Only when transforming
   - Templates/Tasks: Only when executing
   - Always indicate loading
+kb-mode-behavior:
+  - When *kb-mode is invoked, use kb-mode-interaction task
+  - Don't dump all KB content immediately
+  - Present topic areas and wait for user selection
+  - Provide focused, contextual responses
 workflow-guidance:
   - Discover available workflows in the bundle at runtime
   - Understand each workflow's purpose, options, and decision points
@@ -109,6 +117,7 @@ dependencies:
   tasks:
     - advanced-elicitation
     - create-doc
+    - kb-mode-interaction
   data:
     - bmad-kb
   utils:

bmad-core/agents/dev.md

@@ -3,6 +3,9 @@
 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
+root: .bmad-core
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
 agent:
   name: James
   id: dev
@@ -11,6 +14,13 @@ agent:
   whenToUse: "Use for code implementation, debugging, refactoring, and development best practices"
   customization:
 
+startup:
+  - Announce: Greet the user with your name and role, and inform of the *help command.
+  - CRITICAL: Load .bmad-core/core-config.yml and read devLoadAlwaysFiles list and devDebugLog values
+  - CRITICAL: Load ONLY files specified in devLoadAlwaysFiles. If any missing, inform user but continue
+  - CRITICAL: Do NOT load any story files during startup unless user requested you do
+  - CRITICAL: Do NOT begin development until told to proceed
+
 persona:
   role: Expert Senior Software Engineer & Implementation Specialist
   style: Extremely concise, pragmatic, detail-oriented, solution-focused
@@ -19,47 +29,30 @@ persona:
 
 core_principles:
   - CRITICAL: Story-Centric - Story has ALL info. NEVER load PRD/architecture/other docs files unless explicitly directed in dev notes
-  - CRITICAL: Load Standards - MUST load docs/architecture/coding-standards.md into core memory at startup
+  - CRITICAL: Dev Record Only - ONLY update story file Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
-  - CRITICAL: Dev Record Only - ONLY update Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
+  - Strive for Sequential Task Execution - Complete tasks 1-by-1 and mark [x] as completed
-  - Sequential Execution - Complete tasks 1-by-1 in order. Mark [x] before next. No skipping
   - Test-Driven Quality - Write tests alongside code. Task incomplete without passing tests
-  - Debug Log Discipline - Log temp changes to table. Revert after fix. Keep story lean
+  - Debug Log Discipline - Log temp changes to md table in devDebugLog. Revert after fix.
   - Block Only When Critical - HALT for: missing approval/ambiguous reqs/3 failures/missing config
-  - Code Excellence - Clean, secure, maintainable code per coding-standards.md
+  - Code Excellence - Clean, secure, maintainable code per loaded standards
   - Numbered Options - Always use numbered lists when presenting choices
 
-startup:
+commands:  # All commands require * prefix when used (e.g., *help)
-  - Announce: Greet the user with your name and role, and inform of the *help command.
+  - help: Show numbered list of the following commands to allow selection
-  - CRITICAL: Do NOT load any story files or coding-standards.md during startup
+  - run-tests: Execute linting and tests
-  - CRITICAL: Do NOT scan docs/stories/ directory automatically
+  - debug-log: Show debug entries
-  - CRITICAL: Do NOT begin any tasks automatically
+  - complete-story: Finalize to "Review"
-  - Wait for user to specify story or ask for story selection
+  - exit: Say goodbye as the Developer, and then abandon inhabiting this persona
-  - Only load files and begin work when explicitly requested by user
-
-commands:
-  - "*help" - Show commands
-  - "*chat-mode" - Conversational mode
-  - "*run-tests" - Execute linting+tests
-  - "*lint" - Run linting only
-  - "*dod-check" - Run story-dod-checklist
-  - "*status" - Show task progress
-  - "*debug-log" - Show debug entries
-  - "*complete-story" - Finalize to "Review"
-  - "*exit" - Leave developer mode
 
 task-execution:
   flow: "Read task→Implement→Write tests→Pass tests→Update [x]→Next task"
-
   updates-ONLY:
     - "Checkboxes: [ ] not started | [-] in progress | [x] complete"
     - "Debug Log: | Task | File | Change | Reverted? |"
     - "Completion Notes: Deviations only, <50 words"
     - "Change Log: Requirement changes only"
-
   blocking: "Unapproved deps | Ambiguous after story check | 3 failures | Missing config"
-
   done: "Code matches reqs + Tests pass + Follows standards + No lint errors"
-
   completion: "All [x]→Lint→Tests(100%)→Integration(if noted)→Coverage(80%+)→E2E(if noted)→DoD→Summary→HALT"
 
 dependencies:

bmad-core/agents/pm.md

@@ -3,6 +3,9 @@
 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
+root: .bmad-core
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
 activation-instructions:
   - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
@@ -31,11 +34,11 @@ persona:
     - Strategic thinking & outcome-oriented
 startup:
   - Greet the user with your name and role, and inform of the *help command.
-commands:
+commands:  # All commands require * prefix when used (e.g., *help)
-  - '*help" - Show: numbered list of the following commands to allow selection'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - (Default) Deep conversation with advanced-elicitation'
+  - chat-mode: (Default) Deep conversation with advanced-elicitation
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - create-doc {template}: Create doc (no template = show available templates)
-  - '*exit" - Say goodbye as the PM, and then abandon inhabiting this persona'
+  - exit: Say goodbye as the PM, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - create-doc

bmad-core/agents/po.md

@@ -3,6 +3,9 @@
 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
+root: .bmad-core
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
 activation-instructions:
   - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
@@ -33,16 +36,16 @@ persona:
     - Documentation Ecosystem Integrity - Maintain consistency across all documents
 startup:
   - Greet the user with your name and role, and inform of the *help command.
-commands:
+commands:  # All commands require * prefix when used (e.g., *help)
-  - '*help" - Show: numbered list of the following commands to allow selection'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - (Default) Product Owner consultation with advanced-elicitation'
+  - chat-mode: (Default) Product Owner consultation with advanced-elicitation
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - create-doc {template}: Create doc (no template = show available templates)
-  - '*execute-checklist {checklist}" - Run validation checklist (default->po-master-checklist)'
+  - execute-checklist {checklist}: Run validation checklist (default->po-master-checklist)
-  - '*shard-doc {document}" - Break down document into actionable parts'
+  - shard-doc {document}: Break down document into actionable parts
-  - '*correct-course" - Analyze and suggest project course corrections'
+  - correct-course: Analyze and suggest project course corrections
-  - '*create-epic" - Create epic for brownfield projects (task brownfield-create-epic)'
+  - create-epic: Create epic for brownfield projects (task brownfield-create-epic)
-  - '*create-story" - Create user story from requirements (task brownfield-create-story)'
+  - create-story: Create user story from requirements (task brownfield-create-story)
-  - '*exit" - Say Goodbye, You are no longer this Agent'
+  - exit: Say goodbye as the Product Owner, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - execute-checklist

bmad-core/agents/qa.md

@@ -3,6 +3,9 @@
 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
+root: .bmad-core
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
 activation-instructions:
   - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
@@ -33,11 +36,11 @@ persona:
     - Cross-Browser & Cross-Platform Testing - Ensure comprehensive compatibility
 startup:
   - Greet the user with your name and role, and inform of the *help command.
-commands:
+commands:  # All commands require * prefix when used (e.g., *help)
-  - '*help" - Show: numbered list of the following commands to allow selection'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - (Default) QA consultation with advanced-elicitation for test strategy'
+  - chat-mode: (Default) QA consultation with advanced-elicitation for test strategy
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - create-doc {template}: Create doc (no template = show available templates)
-  - '*exit" - Say goodbye as the QA Test Architect, and then abandon inhabiting this persona'
+  - exit: Say goodbye as the QA Test Architect, and then abandon inhabiting this persona
 dependencies:
   data:
     - technical-preferences

bmad-core/agents/sm.md

@@ -3,9 +3,11 @@
 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
+root: .bmad-core
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
 activation-instructions:
   - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
-  - Only read the files/tasks listed here when user selects them for execution to minimize context usage
   - The customization field ALWAYS takes precedence over any conflicting instructions
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
 agent:
@@ -21,31 +23,25 @@ persona:
   identity: Story creation expert who prepares detailed, actionable stories for AI developers
   focus: Creating crystal-clear stories that dumb AI agents can implement without confusion
   core_principles:
-    - Task Adherence - Rigorously follow create-next-story procedures
+    - Rigorously follow `create-next-story` procedure to generate the detailed user story
-    - Checklist-Driven Validation - Apply story-draft-checklist meticulously
+    - Will ensure all information comes from the PRD and Architecture to guide the dumb dev agent
-    - Clarity for Developer Handoff - Stories must be immediately actionable
+    - You are NOT allowed to implement stories or modify code EVER!
-    - Focus on One Story at a Time - Complete one before starting next
-    - Numbered Options Protocol - Always use numbered lists for selections
 startup:
-  - Greet the user with your name and role, and inform of the *help command.
+  - Greet the user with your name and role, and inform of the *help command and then HALT to await instruction if not given already.
-  - CRITICAL: Do NOT automatically execute create-next-story tasks during startup
-  - CRITICAL: Do NOT create or modify any files during startup
   - Offer to help with story preparation but wait for explicit user confirmation
   - Only execute tasks when user explicitly requests them
-  - 'CRITICAL RULE: You are ONLY allowed to create/modify story files - NEVER implement! If asked to implement, tell user they MUST switch to Dev Agent'
+commands:  # All commands require * prefix when used (e.g., *help)
-commands:
+  - help: Show numbered list of the following commands to allow selection
-  - '*help" - Show: numbered list of the following commands to allow selection'
+  - chat-mode: Conversational mode with advanced-elicitation for advice
-  - '*chat-mode" - Conversational mode with advanced-elicitation for advice'
+  - create|draft: Execute create-next-story
-  - '*create" - Execute all steps in Create Next Story Task document'
+  - pivot: Execute `correct-course` task
-  - '*pivot" - Run correct-course task (ensure no story already created first)'
+  - checklist {checklist}: Show numbered list of checklists, execute selection
-  - '*checklist {checklist}" - Show numbered list of checklists, execute selection'
+  - exit: Say goodbye as the Scrum Master, and then abandon inhabiting this persona
-  - '*doc-shard {PRD|Architecture|Other}" - Execute shard-doc task'
-  - '*index-docs" - Update documentation index in /docs/index.md'
-  - '*exit" - Say goodbye as the Scrum Master, and then abandon inhabiting this persona'
 dependencies:
   tasks:
     - create-next-story
     - execute-checklist
+    - course-correct
   templates:
     - story-tmpl
   checklists:

bmad-core/agents/ux-expert.md

@@ -3,6 +3,9 @@
 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
+root: .bmad-core
+IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
 activation-instructions:
   - Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
   - Only read the files/tasks listed here when user selects them for execution to minimize context usage
@@ -37,14 +40,14 @@ persona:
 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:
+commands:  # All commands require * prefix when used (e.g., *help)
-  - '*help" - Show: numbered list of the following commands to allow selection'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - (Default) UX consultation with advanced-elicitation for design decisions'
+  - chat-mode: (Default) UX consultation with advanced-elicitation for design decisions
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - create-doc {template}: Create doc (no template = show available templates)
-  - '*generate-ui-prompt" - Create AI frontend generation prompt'
+  - generate-ui-prompt: Create AI frontend generation prompt
-  - '*research {topic}" - Generate deep research prompt for UX investigation'
+  - research {topic}: Generate deep research prompt for UX investigation
-  - '*execute-checklist {checklist}" - Run design validation checklist'
+  - execute-checklist {checklist}: Run design validation checklist
-  - '*exit" - Say goodbye as the UX Expert, and then abandon inhabiting this persona'
+  - exit: Say goodbye as the UX Expert, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - generate-ai-frontend-prompt

bmad-core/core-config.yml

@@ -0,0 +1,26 @@
+core-project-information:
+  dev-story-location: docs/stories # alternate could be .ai/stories if preferred for example
+  prd:
+    prd-file: docs/prd.md
+    prdVersion: v4
+    prdSharded: true
+    prdShardedLocation: docs/prd
+    epicFilePattern: epic-{n}*.md
+  architecture:
+    architecture-file: docs/architecture.md
+    architectureVersion: v4
+    architectureSharded: true
+    architectureShardedLocation: docs/architecture
+  # if you have a front-end architecture document, uncomment the following and validate the file path
+  # front-end-architecture:
+  #   front-end-architecture-file: docs/front-end-architecture.md
+  #   architectureVersion: v4
+  #   architectureSharded: true
+  #   architectureShardedLocation: docs/architecture
+  customTechnicalDocuments: null # list other documents only if you want the SM to read them when creating stories
+  devLoadAlwaysFiles:
+    - docs/architecture/coding-standards.md
+    - docs/architecture/tech-stack.md
+    - docs/architecture/project-structure.md
+  devDebugLog: .ai/debug-log.md
+  agentCoreDump: .ai/core-dump{n}.md

bmad-core/data/bmad-kb.md

@@ -12,6 +12,118 @@ BMAD-METHOD (Breakthrough Method of Agile AI-driven Development) is a framework
 - **Reusable Resources**: Portable templates, tasks, and checklists
 - **Slash Command Integration**: Quick agent switching and control
 
+### When to Use BMAD
+
+- **New Projects (Greenfield)**: Complete end-to-end development
+- **Existing Projects (Brownfield)**: Feature additions and enhancements
+- **Team Collaboration**: Multiple roles working together
+- **Quality Assurance**: Structured testing and validation
+- **Documentation**: Professional PRDs, architecture docs, user stories
+
+## Getting Started
+
+### Quick Start Options
+
+#### Option 1: Web UI
+**Best for**: ChatGPT, Claude, Gemini users who want to start immediately
+
+1. Navigate to `dist/teams/`
+2. Copy `team-fullstack.txt` content
+3. Create new Gemini Gem or CustomGPT
+4. Upload file with instructions: "Your critical operating instructions are attached, do not break character as directed"
+5. Type `/help` to see available commands
+
+#### Option 2: IDE Integration
+**Best for**: Cursor, Claude Code, Windsurf, VS Code users
+
+```bash
+# Interactive installation (recommended)
+npx bmad-method install
+```
+
+**Installation Steps**:
+- Choose "Complete installation"
+- Select your IDE (Cursor, Claude Code, Windsurf, or Roo Code)
+
+**Verify Installation**:
+- `.bmad-core/` folder created with all agents
+- IDE-specific integration files created
+- All agent commands/rules/modes available
+
+### Environment Selection Guide
+
+**Use Web UI for**:
+- Initial planning and documentation (PRD, architecture)
+- Cost-effective document creation (especially with Gemini)
+- Brainstorming and analysis phases
+- Multi-agent consultation and planning
+
+**Use IDE for**:
+- Active development and coding
+- File operations and project integration
+- Document sharding and story management
+- Implementation workflow (SM/Dev cycles)
+
+**Cost-Saving Tip**: Create large documents (PRDs, architecture) in web UI, then copy to `docs/prd.md` and `docs/architecture.md` in your project before switching to IDE for development.
+
+## Core Configuration (core-config.yml)
+
+**New in V4**: The `bmad-core/core-config.yml` file is a critical innovation that enables BMAD to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
+
+### What is core-config.yml?
+
+This configuration file acts as a map for BMAD agents, telling them exactly where to find your project documents and how they're structured. It enables:
+
+- **Version Flexibility**: Work with V3, V4, or custom document structures
+- **Custom Locations**: Define where your documents and shards live
+- **Developer Context**: Specify which files the dev agent should always load
+- **Debug Support**: Built-in logging for troubleshooting
+
+### Key Configuration Areas
+
+#### PRD Configuration
+- **prdVersion**: Tells agents if PRD follows v3 or v4 conventions
+- **prdSharded**: Whether epics are embedded (false) or in separate files (true)
+- **prdShardedLocation**: Where to find sharded epic files
+- **epicFilePattern**: Pattern for epic filenames (e.g., `epic-{n}*.md`)
+
+#### Architecture Configuration
+- **architectureVersion**: v3 (monolithic) or v4 (sharded)
+- **architectureSharded**: Whether architecture is split into components
+- **architectureShardedLocation**: Where sharded architecture files live
+
+#### Developer Files
+- **devLoadAlwaysFiles**: List of files the dev agent loads for every task
+- **devDebugLog**: Where dev agent logs repeated failures
+- **agentCoreDump**: Export location for chat conversations
+
+### Why It Matters
+
+1. **No Forced Migrations**: Keep your existing document structure
+2. **Gradual Adoption**: Start with V3 and migrate to V4 at your pace
+3. **Custom Workflows**: Configure BMAD to match your team's process
+4. **Intelligent Agents**: Agents automatically adapt to your configuration
+
+### Common Configurations
+
+**Legacy V3 Project**:
+```yaml
+prdVersion: v3
+prdSharded: false
+architectureVersion: v3
+architectureSharded: false
+```
+
+**V4 Optimized Project**:
+```yaml
+prdVersion: v4
+prdSharded: true
+prdShardedLocation: docs/prd
+architectureVersion: v4
+architectureSharded: true
+architectureShardedLocation: docs/architecture
+```
+
 ## Core Philosophy
 
 ### Vibe CEO'ing
@@ -33,15 +145,342 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
 7. **START_SMALL_SCALE_FAST**: Test concepts, then expand.
 8. **EMBRACE_THE_CHAOS**: Adapt and overcome challenges.
 
-## IDE Development Workflow
+### Key Workflow Principles
 
-1. Shard the PRD (And Architecture documents if they exist also based on workflow type) using the Doc Shard task. The BMad-Master agent can help you do this. You will select the task, provide the doc to shard and the output folder. for example: `BMad Master, please Shard the docs/prd.md to the doc/prd/ folder` - this should ask you to use the md-tree-parser which is recommended, but either way shoudl result in multiple documents being created in the folder docs/prd.
+1. **Agent Specialization**: Each agent has specific expertise and responsibilities
-2. If you have fullstack, front end and or back end architecture documents you will want to follow the same thing, but shard all of these to an architecture folder instead of a prd folder.
+2. **Clean Handoffs**: Always start fresh when switching between agents
-3. Ensure that you have at least one epic-n.md file in your prd folder, with the stories in order to develop.
+3. **Status Tracking**: Maintain story statuses (Draft → Approved → InProgress → Done)
-4. The docs or architecture folder or prd folder should have a source tree document and coding standards at a minimum. These are used by the dev agent, and the many other sharded docs are used by the SM agent.
+4. **Iterative Development**: Complete one story before starting the next
-5. Use a new chat window to allow the SM agent to `draft the next story`.
+5. **Documentation First**: Always start with solid PRD and architecture
-6. If you agree the story is correct, mark it as approved in the status field, and then start a new chat window with the dev agent.
-7. Ask the dev agent to implement the next story. If you draft the story file into the chat it will save time for the dev to have to find what the next one is. The dev should follow the tasks and subtasks marking them off as they are completed. The dev agent will also leave notes potentially for the SM to know about any deviations that might have occured to help draft the next story.
-8. Once complete and you have verified, mark it done, and start a new chat. Ask the SM to draft the next story - repeating the cycle.
 
-With this work flow, there is only 1 story in progress at a time, worked sequentially.
+## Agent System
+
+### Core Development Team
+
+| Agent       | Role               | Primary Functions                       | When to Use                            |
+| ----------- | ------------------ | --------------------------------------- | -------------------------------------- |
+| `analyst`   | Business Analyst   | Market research, requirements gathering | Project planning, competitive analysis |
+| `pm`        | Product Manager    | PRD creation, feature prioritization    | Strategic planning, roadmaps           |
+| `architect` | Solution Architect | System design, technical architecture   | Complex systems, scalability planning  |
+| `dev`       | Developer          | Code implementation, debugging          | All development tasks                  |
+| `qa`        | QA Specialist      | Test planning, quality assurance        | Testing strategies, bug validation     |
+| `ux-expert` | UX Designer        | UI/UX design, prototypes                | User experience, interface design      |
+| `po`        | Product Owner      | Backlog management, story validation    | Story refinement, acceptance criteria  |
+| `sm`        | Scrum Master       | Sprint planning, story creation         | Project management, workflow           |
+
+### Meta Agents
+
+| Agent               | Role             | Primary Functions                     | When to Use                       |
+| ------------------- | ---------------- | ------------------------------------- | --------------------------------- |
+| `bmad-orchestrator` | Team Coordinator | Multi-agent workflows, role switching | Complex multi-role tasks          |
+| `bmad-master`       | Universal Expert | All capabilities without switching    | Single-session comprehensive work |
+
+### Agent Interaction Commands
+
+#### IDE-Specific Syntax
+
+**Agent Loading by IDE**:
+- **Claude Code**: `/agent-name` (e.g., `/bmad-master`)
+- **Cursor**: `@agent-name` (e.g., `@bmad-master`)
+- **Windsurf**: `@agent-name` (e.g., `@bmad-master`)
+- **Roo Code**: Select mode from mode selector (e.g., `bmad-bmad-master`)
+
+**Chat Management Guidelines**:
+- **Claude Code, Cursor, Windsurf**: Start new chats when switching agents
+- **Roo Code**: Switch modes within the same conversation
+
+**Common Task Commands**:
+- `*help` - Show available commands
+- `*status` - Show current context/progress
+- `*exit` - Exit the agent mode
+- `*shard-doc docs/prd.md prd` - Shard PRD into manageable pieces
+- `*shard-doc docs/architecture.md architecture` - Shard architecture document
+- `*create` - Run create-next-story task (SM agent)
+
+**In Web UI**:
+```text
+/pm create-doc prd
+/architect review system design
+/dev implement story 1.2
+/help - Show available commands
+/switch agent-name - Change active agent (if orchestrator available)
+```
+
+## Team Configurations
+
+### Pre-Built Teams
+
+#### Team All
+- **Includes**: All 10 agents + orchestrator
+- **Use Case**: Complete projects requiring all roles
+- **Bundle**: `team-all.txt`
+
+#### Team Fullstack
+- **Includes**: PM, Architect, Developer, QA, UX Expert
+- **Use Case**: End-to-end web/mobile development
+- **Bundle**: `team-fullstack.txt`
+
+#### Team No-UI
+- **Includes**: PM, Architect, Developer, QA (no UX Expert)
+- **Use Case**: Backend services, APIs, system development
+- **Bundle**: `team-no-ui.txt`
+
+## Core Architecture
+
+### System Overview
+
+The BMAD-Method is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
+
+### Key Architectural Components
+
+#### 1. Agents (`bmad-core/agents/`)
+- **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.)
+- **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies
+- **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use
+- **Startup Instructions**: Can load project-specific documentation for immediate context
+
+#### 2. Agent Teams (`bmad-core/agent-teams/`)
+- **Purpose**: Define collections of agents bundled together for specific purposes
+- **Examples**: `team-all.yml` (comprehensive bundle), `team-fullstack.yml` (full-stack development)
+- **Usage**: Creates pre-packaged contexts for web UI environments
+
+#### 3. Workflows (`bmad-core/workflows/`)
+- **Purpose**: YAML files defining prescribed sequences of steps for specific project types
+- **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development
+- **Structure**: Defines agent interactions, artifacts created, and transition conditions
+
+#### 4. Reusable Resources
+- **Templates** (`bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories
+- **Tasks** (`bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story"
+- **Checklists** (`bmad-core/checklists/`): Quality assurance checklists for validation and review
+- **Data** (`bmad-core/data/`): Core knowledge base and technical preferences
+
+### Dual Environment Architecture
+
+#### IDE Environment
+
+- Users interact directly with agent markdown files
+- Agents can access all dependencies dynamically
+- Supports real-time file operations and project integration
+- Optimized for development workflow execution
+
+#### Web UI Environment
+
+- Uses pre-built bundles from `dist/teams` for stand alone 1 upload files for all agents and their assest with an orchestrating agent
+- Single text files containing all agent dependencies are in `dist/agents/` - these are unnecessary unless you want to create a web agent that is only a single agent and not a team
+- Created by the web-builder tool for upload to web interfaces
+- Provides complete context in one package
+
+### Template Processing System
+
+BMAD employs a sophisticated template system with three key components:
+
+1. **Template Format** (`utils/template-format.md`): Defines markup language for variable substitution and AI processing directives
+2. **Document Creation** (`tasks/create-doc.md`): Orchestrates template selection and user interaction
+3. **Advanced Elicitation** (`tasks/advanced-elicitation.md`): Provides interactive refinement through structured brainstorming
+
+**Template Features**:
+
+- **Self-contained**: Templates embed both output structure and processing instructions
+- **Variable Substitution**: `{{placeholders}}` for dynamic content
+- **AI Processing Directives**: `[[LLM: instructions]]` for AI-only processing
+- **Interactive Refinement**: Built-in elicitation processes for quality improvement
+
+### Technical Preferences Integration
+
+The `technical-preferences.md` file serves as a persistent technical profile that:
+- Ensures consistency across all agents and projects
+- Eliminates repetitive technology specification
+- Provides personalized recommendations aligned with user preferences
+- Evolves over time with lessons learned
+
+### Build and Delivery Process
+
+The `web-builder.js` tool creates web-ready bundles by:
+1. Reading agent or team definition files
+2. Recursively resolving all dependencies
+3. Concatenating content into single text files with clear separators
+4. Outputting ready-to-upload bundles for web AI interfaces
+
+This architecture enables seamless operation across environments while maintaining the rich, interconnected agent ecosystem that makes BMAD powerful.
+
+## Complete Development Workflow
+
+### Planning Phase (Web UI Recommended)
+
+**Ideal for cost efficiency, especially with Gemini:**
+
+1. **Optional Analysis**: `/analyst` - Market research, competitive analysis
+2. **Project Brief**: Create foundation document (Analyst or user)
+3. **PRD Creation**: `/pm create-doc prd` - Comprehensive product requirements
+4. **Architecture Design**: `/architect create-doc architecture` - Technical foundation
+5. **Validation & Alignment**: `/po` run master checklist to ensure document consistency
+6. **Document Preparation**: Copy final documents to project as `docs/prd.md` and `docs/architecture.md`
+
+#### Example Planning Prompts
+
+**For PRD Creation**:
+```text
+"I want to build a [type] application that [core purpose].
+Help me brainstorm features and create a comprehensive PRD."
+```
+
+**For Architecture Design**:
+```text
+"Based on this PRD, design a scalable technical architecture
+that can handle [specific requirements]."
+```
+
+### Critical Transition: Web UI to IDE
+
+**Once planning is complete, you MUST switch to IDE for development:**
+
+- **Why**: Development workflow requires file operations, real-time project integration, and document sharding
+- **Cost Benefit**: Web UI is more cost-effective for large document creation; IDE is optimized for development tasks
+- **Required Files**: Ensure `docs/prd.md` and `docs/architecture.md` exist in your project
+
+### IDE Development Workflow
+
+**Prerequisites**: Planning documents must exist in `docs/` folder
+
+1. **Document Sharding**: 
+   - `@bmad-master` or `@po` shard `docs/prd.md` to `docs/prd/` folder
+   - If architecture exists, shard to `docs/architecture/` folder
+   - Results in multiple manageable documents and epic files
+
+2. **Verify Sharded Content**:
+   - At least one `epic-n.md` file in `docs/prd/` with stories in development order
+   - Source tree document and coding standards for dev agent reference
+   - Sharded docs for SM agent story creation
+
+**Resulting Folder Structure**:
+- `docs/prd/` - Broken down PRD sections
+- `docs/architecture/` - Broken down architecture sections
+- `docs/stories/` - Generated user stories
+
+3. **Development Cycle** (Sequential, one story at a time):
+
+   **Step 1 - Story Creation**: New chat window → `@sm` → `*create`
+   - SM executes create-next-story task
+   - Review generated story in `docs/stories/`
+   - Update status from "Draft" to "Approved"
+   
+   **Step 2 - Story Implementation**: New chat window → `@dev`
+   - Agent asks which story to implement
+   - Include story file content to save dev agent lookup time
+   - Dev follows tasks/subtasks, marking completion
+   - Dev leaves notes for SM about any deviations
+   - Update status to "Done"
+   
+   **Step 3 - Repeat**: Continue SM → Dev cycle until all epic stories complete
+
+**Important**: Only 1 story in progress at a time, worked sequentially until all epic stories complete.
+
+### Status Tracking Workflow
+
+Stories progress through defined statuses:
+- **Draft** → **Approved** → **InProgress** → **Done**
+
+Each status change requires user verification and approval before proceeding.
+
+### Workflow Types
+
+#### Greenfield Development
+- Business analysis and market research
+- Product requirements and feature definition  
+- System architecture and design
+- Development execution
+- Testing and deployment
+
+#### Brownfield Enhancement
+- Current system analysis
+- Enhancement planning
+- Impact assessment
+- Incremental development
+- Integration testing
+
+## Document Creation Best Practices
+
+### Required File Naming for Framework Integration
+
+- `docs/prd.md` - Product Requirements Document
+- `docs/architecture.md` - System Architecture Document
+
+**Why These Names Matter**:
+- Agents automatically reference these files during development
+- Sharding tasks expect these specific filenames
+- Workflow automation depends on standard naming
+
+### Cost-Effective Document Creation Workflow
+
+**Recommended for Large Documents (PRD, Architecture):**
+
+1. **Use Web UI**: Create documents in web interface for cost efficiency
+2. **Copy Final Output**: Save complete markdown to your project
+3. **Standard Names**: Save as `docs/prd.md` and `docs/architecture.md`
+4. **Switch to IDE**: Use IDE agents for development and smaller documents
+
+### Document Sharding
+
+Templates with Level 2 headings (`##`) can be automatically sharded:
+
+**Original PRD**:
+```markdown
+## Goals and Background Context
+## Requirements  
+## User Interface Design Goals
+## Success Metrics
+```
+
+**After Sharding**:
+- `docs/prd/goals-and-background-context.md`
+- `docs/prd/requirements.md`
+- `docs/prd/user-interface-design-goals.md`
+- `docs/prd/success-metrics.md`
+
+Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic sharding.
+
+## Usage Patterns and Best Practices
+
+### Environment-Specific Usage
+
+**Web UI Best For**:
+- Initial planning and documentation phases
+- Cost-effective large document creation
+- Agent consultation and brainstorming
+- Multi-agent workflows with orchestrator
+
+**IDE Best For**:
+- Active development and implementation
+- File operations and project integration
+- Story management and development cycles
+- Code review and debugging
+
+### Quality Assurance
+
+- Use appropriate agents for specialized tasks
+- Follow Agile ceremonies and review processes
+- Maintain document consistency with PO agent
+- Regular validation with checklists and templates
+
+### Performance Optimization
+
+- Use specific agents vs. `bmad-master` for focused tasks
+- Choose appropriate team size for project needs
+- Leverage technical preferences for consistency
+- Regular context management and cache clearing
+
+## Success Tips
+
+- **Use Gemini for big picture planning** - The team-fullstack bundle provides collaborative expertise
+- **Use bmad-master for document organization** - Sharding creates manageable chunks
+- **Follow the SM → Dev cycle religiously** - This ensures systematic progress
+- **Keep conversations focused** - One agent, one task per conversation
+- **Review everything** - Always review and approve before marking complete
+
+## Getting Help
+
+- **Commands**: Use `/help` in any environment to see available commands
+- **Agent Switching**: Use `/switch agent-name` with orchestrator for role changes
+- **Documentation**: Check `docs/` folder for project-specific context
+- **Community**: Discord and GitHub resources available for support

bmad-core/tasks/create-next-story.md

@@ -4,45 +4,42 @@
 
 To identify the next logical story based on project progress and epic definitions, and then to prepare a comprehensive, self-contained, and actionable story file using the `Story Template`. This task ensures the story is enriched with all necessary technical context, requirements, and acceptance criteria, making it ready for efficient implementation by a Developer Agent with minimal need for additional research.
 
-## Inputs for this Task
-
-- Access to the project's documentation repository, specifically:
-  - `docs/index.md` (hereafter "Index Doc")
-  - All Epic files - located in one of these locations:
-    - Primary: `docs/prd/epic-{n}-{description}.md` (e.g., `epic-1-foundation-core-infrastructure.md`)
-    - Secondary: `docs/epics/epic-{n}-{description}.md`
-    - User-specified location if not found in above paths
-  - Existing story files in `docs/stories/`
-  - Main PRD (hereafter "PRD Doc")
-  - Main Architecture Document (hereafter "Main Arch Doc")
-  - Frontend Architecture Document (hereafter "Frontend Arch Doc," if relevant)
-  - Project Structure Guide (`docs/project-structure.md`)
-  - Operational Guidelines Document (`docs/operational-guidelines.md`)
-  - Technology Stack Document (`docs/tech-stack.md`)
-  - Data Models Document (as referenced in Index Doc)
-  - API Reference Document (as referenced in Index Doc)
-  - UI/UX Specifications, Style Guides, Component Guides (if relevant, as referenced in Index Doc)
-- The `bmad-core/templates/story-tmpl.md` (hereafter "Story Template")
-- The `bmad-core/checklists/story-draft-checklist.md` (hereafter "Story Draft Checklist")
-- User confirmation to proceed with story identification and, if needed, to override warnings about incomplete prerequisite stories.
-
 ## Task Execution Instructions
 
+### 0. Load Core Configuration
+
+[[LLM: CRITICAL - This MUST be your first step]]
+
+- Load `.bmad-core/core-config.yml` from the project root
+- If the file does not exist:
+  - HALT and inform the user: "core-config.yml not found. This file is required for story creation. You can:
+    1. Copy it from GITHUB BMAD-METHOD/bmad-core/core-config.yml and configure it for your project
+    2. Run the BMAD installer against your project to upgrade and add the file automatically
+    Please add and configure core-config.yml before proceeding."
+- Extract the following key configurations:
+  - `dev-story-location`: Where to save story files
+  - `prd.prdSharded`: Whether PRD is sharded or monolithic
+  - `prd.prd-file`: Location of monolithic PRD (if not sharded)
+  - `prd.prdShardedLocation`: Location of sharded epic files
+  - `prd.epicFilePattern`: Pattern for epic files (e.g., `epic-{n}*.md`)
+  - `architecture.architectureVersion`: Architecture document version
+  - `architecture.architectureSharded`: Whether architecture is sharded
+  - `architecture.architecture-file`: Location of monolithic architecture
+  - `architecture.architectureShardedLocation`: Location of sharded architecture files
+
 ### 1. Identify Next Story for Preparation
 
 #### 1.1 Locate Epic Files
 
-- First, determine where epic files are located:
+- Based on `prdSharded` from config:
-  - Check `docs/prd/` for files matching pattern `epic-{n}-*.md`
+  - **If `prdSharded: true`**: Look for epic files in `prdShardedLocation` using `epicFilePattern`
-  - If not found, check `docs/epics/` for files matching pattern `epic-{n}-*.md`
+  - **If `prdSharded: false`**: Load the full PRD from `prd-file` and extract epics from section headings (## Epic N or ### Epic N)
-  - If still not found, ask user: "Unable to locate epic files. Please specify the path where epic files are stored."
-- Note: Epic files follow naming convention `epic-{n}-{description}.md` (e.g., `epic-1-foundation-core-infrastructure.md`)
 
 #### 1.2 Review Existing Stories
 
-- Review `docs/stories/` to find the highest-numbered story file.
+- Check `dev-story-location` from config (e.g., `docs/stories/`) for existing story files
+- If the directory exists and has at least 1 file, find the highest-numbered story file.
 - **If a highest story file exists (`{lastEpicNum}.{lastStoryNum}.story.md`):**
-
   - Verify its `Status` is 'Done' (or equivalent).
   - If not 'Done', present an alert to the user:
 
@@ -60,17 +57,45 @@ To identify the next logical story based on project progress and epic definition
     ```
 
   - Proceed only if user selects option 3 (Override) or if the last story was 'Done'.
-  - If proceeding: Look for the Epic File for `{lastEpicNum}` (e.g., `epic-{lastEpicNum}-*.md`) and check for a story numbered `{lastStoryNum + 1}`. If it exists and its prerequisites (per Epic File) are met, this is the next story.
+  - If proceeding: Look for the Epic File for `{lastEpicNum}` (e.g., `epic-{lastEpicNum}*.md`) and parse it to find ALL stories in that epic. **ALWAYS select the next sequential story** (e.g., if last was 2.2, next MUST be 2.3).
-  - Else (story not found or prerequisites not met): The next story is the first story in the next Epic File (e.g., look for `epic-{lastEpicNum + 1}-*.md`, then `epic-{lastEpicNum + 2}-*.md`, etc.) whose prerequisites are met.
+  - If the next sequential story has unmet prerequisites, present this to the user:
+
+    ```plaintext
+    ALERT: Next story has unmet prerequisites:
+    Story: {epicNum}.{storyNum} - {Story Title}
+    Prerequisites not met: [list specific prerequisites]
+    
+    Would you like to:
+    1. Create the story anyway (mark prerequisites as pending)
+    2. Skip to a different story (requires your specific instruction)
+    3. Cancel story creation
+    
+    Please choose an option (1/2/3):
+    ```
+
+  - If there are no more stories in the current epic (e.g., 2.9 was done and there is no 2.10):
+
+    ```plaintext
+    Epic {epicNum} Complete: All stories in Epic {epicNum} have been completed.
+    
+    Would you like to:
+    1. Begin Epic {epicNum + 1} with story {epicNum + 1}.1
+    2. Select a specific story to work on
+    3. Cancel story creation
+    
+    Please choose an option (1/2/3):
+    ```
+
+  - **CRITICAL**: NEVER automatically skip to another epic or non-sequential story. The user MUST explicitly instruct which story to create if skipping the sequential order.
 
 - **If no story files exist in `docs/stories/`:**
-  - The next story is the first story in the first epic file (look for `epic-1-*.md`, then `epic-2-*.md`, etc.) whose prerequisites are met.
+  - The next story is ALWAYS 1.1 (the first story of the first epic).
-- If no suitable story with met prerequisites is found, report to the user that story creation is blocked, specifying what prerequisites are pending. HALT task.
+  - If story 1.1 has unmet prerequisites, follow the same alert process as above.
 - Announce the identified story to the user: "Identified next story for preparation: {epicNum}.{storyNum} - {Story Title}".
 
-### 2. Gather Core Story Requirements (from Epic File)
+### 2. Gather Core Story Requirements (from Epic)
 
-- For the identified story, open its parent Epic File (e.g., `epic-{epicNum}-*.md` from the location identified in step 1.1).
+- For the identified story, review its parent Epic (e.g., `epic-{epicNum}*.md` from the location identified in step 1.1).
 - Extract: Exact Title, full Goal/User Story statement, initial list of Requirements, all Acceptance Criteria (ACs), and any predefined high-level Tasks.
 - Keep a record of this original epic-defined scope for later deviation analysis.
 
@@ -79,7 +104,7 @@ To identify the next logical story based on project progress and epic definition
 [[LLM: This step is CRITICAL for continuity and learning from implementation experience]]
 
 - If this is not the first story (i.e., previous story exists):
-  - Read the previous story file: `docs/stories/{prevEpicNum}.{prevStoryNum}.story.md`
+  - Read the previous sequential story from `docs/stories`
   - Pay special attention to:
     - Dev Agent Record sections (especially Completion Notes and Debug Log References)
     - Any deviations from planned implementation
@@ -88,18 +113,30 @@ To identify the next logical story based on project progress and epic definition
     - Any "lessons learned" or notes for future stories
   - Extract relevant insights that might inform the current story's preparation
 
-### 4. Gather & Synthesize Architecture Context from Sharded Docs
+### 4. Gather & Synthesize Architecture Context
 
-[[LLM: CRITICAL - You MUST gather technical details from the sharded architecture documents. NEVER make up technical details not found in these documents.]]
+[[LLM: CRITICAL - You MUST gather technical details from the architecture documents. NEVER make up technical details not found in these documents.]]
 
-#### 4.1 Start with Architecture Index
+#### 4.1 Determine Architecture Document Strategy
 
-- Read `docs/architecture/index.md` to understand the full scope of available documentation
+Based on configuration loaded in Step 0:
-- Identify which sharded documents are most relevant to the current story
 
-#### 4.2 Recommended Reading Order Based on Story Type
+- **If `architectureVersion: v4` and `architectureSharded: true`**:
+  - Read `{architectureShardedLocation}/index.md` to understand available documentation
+  - Follow the structured reading order in section 4.2 below
+  
+- **If `architectureVersion: v4` and `architectureSharded: false`**:
+  - Load the monolithic architecture from `architecture-file`
+  - Extract relevant sections based on v4 structure (tech stack, project structure, etc.)
+  
+- **If `architectureVersion` is NOT v4**:
+  - Inform user: "Architecture document is not v4 format. Will use best judgment to find relevant information."
+  - If `architectureSharded: true`: Search sharded files by filename relevance
+  - If `architectureSharded: false`: Search within monolithic `architecture-file` for relevant sections
 
-[[LLM: Read documents in this order, but ALWAYS verify relevance to the specific story. Skip irrelevant sections but NEVER skip documents that contain information needed for the story.]]
+#### 4.2 Recommended Reading Order Based on Story Type (v4 Sharded Only)
+
+[[LLM: Use this structured approach ONLY for v4 sharded architecture. For other versions, use best judgment based on file names and content.]]
 
 **For ALL Stories:**
 
@@ -108,9 +145,18 @@ To identify the next logical story based on project progress and epic definition
 3. `docs/architecture/coding-standards.md` - Ensure dev follows project conventions
 4. `docs/architecture/testing-strategy.md` - Include testing requirements in tasks
 
-**For Backend/API Stories, additionally read:** 5. `docs/architecture/data-models.md` - Data structures and validation rules 6. `docs/architecture/database-schema.md` - Database design and relationships 7. `docs/architecture/backend-architecture.md` - Service patterns and structure 8. `docs/architecture/rest-api-spec.md` - API endpoint specifications 9. `docs/architecture/external-apis.md` - Third-party integrations (if relevant)
+**For Backend/API Stories, additionally read:**
+5. `docs/architecture/data-models.md` - Data structures and validation rules
+6. `docs/architecture/database-schema.md` - Database design and relationships
+7. `docs/architecture/backend-architecture.md` - Service patterns and structure
+8. `docs/architecture/rest-api-spec.md` - API endpoint specifications
+9. `docs/architecture/external-apis.md` - Third-party integrations (if relevant)
 
-**For Frontend/UI Stories, additionally read:** 5. `docs/architecture/frontend-architecture.md` - Component structure and patterns 6. `docs/architecture/components.md` - Specific component designs 7. `docs/architecture/core-workflows.md` - User interaction flows 8. `docs/architecture/data-models.md` - Frontend data handling
+**For Frontend/UI Stories, additionally read:**
+5. `docs/architecture/frontend-architecture.md` - Component structure and patterns
+6. `docs/architecture/components.md` - Specific component designs
+7. `docs/architecture/core-workflows.md` - User interaction flows
+8. `docs/architecture/data-models.md` - Frontend data handling
 
 **For Full-Stack Stories:**
 
@@ -143,7 +189,7 @@ Format references as: `[Source: architecture/{filename}.md#{section}]`
 
 ### 6. Populate Story Template with Full Context
 
-- Create a new story file: `docs/stories/{epicNum}.{storyNum}.story.md`.
+- Create a new story file: `{dev-story-location}/{epicNum}.{storyNum}.story.md` (using location from config).
 - Use the Story Template to structure the file.
 - Fill in:
   - Story `{EpicNum}.{StoryNum}: {Short Title Copied from Epic File}`
@@ -190,7 +236,7 @@ Format references as: `[Source: architecture/{filename}.md#{section}]`
 - Verify all source references are included for technical details
 - Ensure tasks align with both epic requirements and architecture constraints
 - Update status to "Draft"
-- Save the story file to `docs/stories/{epicNum}.{storyNum}.story.md`
+- Save the story file to `{dev-story-location}/{epicNum}.{storyNum}.story.md` (using location from config)
 
 ### 9. Report Completion
 

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

@@ -0,0 +1,70 @@
+# KB Mode Interaction Task
+
+## Purpose
+Provide a user-friendly interface to the BMAD knowledge base without overwhelming users with information upfront.
+
+## Instructions
+
+When entering KB mode (*kb-mode), follow these steps:
+
+### 1. Welcome and Guide
+Announce entering KB mode with a brief, friendly introduction:
+
+"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."
+
+### 2. Present Topic Areas
+Offer a concise list of main topic areas the user might want to explore:
+
+**What would you like to know more about?**
+
+1. **Setup & Installation** - Getting started with BMAD
+2. **Workflows** - Choosing the right workflow for your project
+3. **Web vs IDE** - When to use each environment
+4. **Agents** - Understanding specialized agents and their roles
+5. **Documents** - PRDs, Architecture, Stories, and more
+6. **Agile Process** - How BMAD implements Agile methodologies
+7. **Configuration** - Customizing BMAD for your needs
+8. **Best Practices** - Tips for effective BMAD usage
+
+Or ask me about anything else related to BMAD-METHOD!
+
+### 3. Respond Contextually
+- Wait for user's specific question or topic selection
+- Provide focused, relevant information from the knowledge base
+- Offer to dive deeper or explore related topics
+- Keep responses concise unless user asks for detailed explanations
+
+### 4. Interactive Exploration
+- After answering, suggest related topics they might find helpful
+- Maintain conversational flow rather than data dumping
+- Use examples when appropriate
+- Reference specific documentation sections when relevant
+
+### 5. Exit Gracefully
+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
+- Suggest next steps based on what was discussed
+
+## Example Interaction
+
+**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.
+
+**What would you like to know more about?**
+
+1. **Setup & Installation** - Getting started with BMAD
+2. **Workflows** - Choosing the right workflow for your project
+3. **Web vs IDE** - When to use each environment
+4. **Agents** - Understanding specialized agents and their roles
+5. **Documents** - PRDs, Architecture, Stories, and more
+6. **Agile Process** - How BMAD implements Agile methodologies
+7. **Configuration** - Customizing BMAD for your needs
+8. **Best Practices** - Tips for effective BMAD usage
+
+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]

bmad-core/tasks/shard-doc.md

@@ -112,7 +112,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
 

bmad-core/templates/architecture-tmpl.md

@@ -2,6 +2,8 @@
 
 [[LLM: If available, review any provided relevant documents to gather all relevant context before beginning. If at a minimum you cannot local `docs/prd.md` ask the user what docs will provide the basis for the architecture.]]
 
+[[LLM: The default path and filename unless specified is docs/architecture.md]]
+
 ## Introduction
 
 [[LLM: This section establishes the document's purpose and scope. Keep the content below but ensure project name is properly substituted.
@@ -355,7 +357,7 @@ servers:
       '[object Object]': null
     description:
       '[object Object]': null
-```text
+```
 
 ^^/CONDITION: has_rest_api^^
 
@@ -418,7 +420,6 @@ 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/
@@ -430,6 +431,7 @@ project-root/
 ├── scripts/ # Monorepo management scripts
 └── package.json # Root package.json with workspaces
 @{/example}
+```
 
 [[LLM: After presenting the source tree structure, apply `tasks#advanced-elicitation` protocol]]
 

bmad-core/templates/brownfield-architecture-tmpl.md

@@ -1,5 +1,7 @@
 # {{Project Name}} Brownfield Enhancement Architecture
 
+[[LLM: The default path and filename unless specified is docs/architecture.md]]
+
 [[LLM: IMPORTANT - SCOPE AND ASSESSMENT REQUIRED:
 
 This architecture document is for SIGNIFICANT enhancements to existing projects that require comprehensive architectural planning. Before proceeding:
@@ -224,7 +226,7 @@ Present component architecture and apply `tasks#advanced-elicitation` protocol]]
 
 ```mermaid
 {{component_interaction_diagram}}
-```text
+```
 
 ## API Design and Integration
 
@@ -264,7 +266,7 @@ Present API design and apply `tasks#advanced-elicitation` protocol]]
 
 ```json
 {{response_schema}}
-```text
+```
 
 <</REPEAT>>
 

bmad-core/templates/brownfield-prd-tmpl.md

@@ -1,5 +1,7 @@
 # {{Project Name}} Brownfield Enhancement PRD
 
+[[LLM: The default path and filename unless specified is docs/prd.md]]
+
 [[LLM: IMPORTANT - SCOPE ASSESSMENT REQUIRED:
 
 This PRD is for SIGNIFICANT enhancements to existing projects that require comprehensive planning and multiple stories. Before proceeding:

bmad-core/templates/competitor-analysis-tmpl.md

@@ -1,5 +1,7 @@
 # Competitive Analysis Report: {{Project/Product Name}}
 
+[[LLM: The default path and filename unless specified is docs/competitor-analysis.md]]
+
 [[LLM: This template guides comprehensive competitor analysis. Start by understanding the user's competitive intelligence needs and strategic objectives. Help them identify and prioritize competitors before diving into detailed analysis.]]
 
 ## Executive Summary

bmad-core/templates/front-end-architecture-tmpl.md

@@ -1,5 +1,7 @@
 # {{Project Name}} Frontend Architecture Document
 
+[[LLM: The default path and filename unless specified is docs/ui-architecture.md]]
+
 [[LLM: Review provided documents including PRD, UX-UI Specification, and main Architecture Document. Focus on extracting technical implementation details needed for AI frontend tools and developer agents. Ask the user for any of these documents if you are unable to locate and were not provided.]]
 
 ## Template and Framework Selection

bmad-core/templates/front-end-spec-tmpl.md

@@ -1,5 +1,7 @@
 # {{Project Name}} UI/UX Specification
 
+[[LLM: The default path and filename unless specified is docs/front-end-spec.md]]
+
 [[LLM: Review provided documents including Project Brief, PRD, and any user research to gather context. Focus on understanding user needs, pain points, and desired outcomes before beginning the specification.]]
 
 ## Introduction
@@ -76,7 +78,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 ```mermaid
 {{sitemap_diagram}}
-```text
+```
 
 @{example: sitemap}
 

bmad-core/templates/fullstack-architecture-tmpl.md

@@ -1,5 +1,7 @@
 # {{Project Name}} Fullstack Architecture Document
 
+[[LLM: The default path and filename unless specified is docs/architecture.md]]
+
 [[LLM: If available, review any provided relevant documents to gather all relevant context before beginning. At minimum, you should have access to docs/prd.md and docs/front-end-spec.md. Ask the user for any documents you need but cannot locate. This template creates a unified architecture that covers both backend and frontend concerns to guide AI-driven fullstack development.]]
 
 ## Introduction

bmad-core/templates/market-research-tmpl.md

@@ -1,5 +1,7 @@
 # Market Research Report: {{Project/Product Name}}
 
+[[LLM: The default path and filename unless specified is docs/market-research.md]]
+
 [[LLM: This template guides the creation of a comprehensive market research report. Begin by understanding what market insights the user needs and why. Work through each section systematically, using the appropriate analytical frameworks based on the research objectives.]]
 
 ## Executive Summary

bmad-core/templates/prd-tmpl.md

@@ -1,5 +1,7 @@
 # {{Project Name}} Product Requirements Document (PRD)
 
+[[LLM: The default path and filename unless specified is docs/prd.md]]
+
 [[LLM: If available, review any provided document or ask if any are optionally available: Project Brief]]
 
 ## Goals and Background Context

bmad-core/templates/project-brief-tmpl.md

@@ -1,5 +1,7 @@
 # Project Brief: {{Project Name}}
 
+[[LLM: The default path and filename unless specified is docs/brief.md]]
+
 [[LLM: This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development.
 
 Start by asking the user which mode they prefer:

bmad-core/utils/file-resolution-context.md

@@ -0,0 +1,10 @@
+# File Resolution Context
+
+Update the installer/upgrader so that when agents are added to a project (under Add these two lines to any agent's `activation-instructions` for ide installation:
+
+```yaml
+- IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
+- REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
+```
+
+and add `root: .bmad-core` as the first root yml property.

bmad-core/utils/workflow-management.md

@@ -47,7 +47,7 @@ Available workflows for [Team Name]:
 [... etc. ...]
 
 Use /workflow-start {number or id} to begin a workflow.
-```text
+```
 
 ### /workflow-start {workflow-id}
 
@@ -73,7 +73,7 @@ In Progress:
     - Create PRD (John) - awaiting input
 
 Next: Technical Architecture
-```text
+```
 
 ### /workflow-resume
 
@@ -89,7 +89,7 @@ BMad: I see you've completed Discovery and part of Product Planning.
       - UX Strategy with Sally (ux-expert)
 
       Would you like me to load Sally to continue?
-```text
+```
 
 ### /workflow-next
 
@@ -159,7 +159,7 @@ BMad: I see you have a PRD and architecture document. Based on these artifacts,
       - Load Sarah (Product Owner) to validate all artifacts
 
       Would you like to continue with this workflow?
-```text
+```
 
 ## Workflow Context Passing
 
@@ -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
 

bmad-core/workflows/brownfield-service.yml

@@ -14,7 +14,7 @@ workflow:
 
   sequence:
     - step: service_analysis
-     agent: architect
+      agent: architect
       action: analyze existing project and use task document-project
       creates: multiple documents per the document-project template
       notes: "Review existing service documentation, codebase, performance metrics, and identify integration dependencies."

dist/agents/analyst.txt

@@ -76,13 +76,13 @@ persona:
 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'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - (Default) Strategic analysis consultation with advanced-elicitation'
+  - chat-mode: (Default) Strategic analysis consultation with advanced-elicitation
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - create-doc {template}: Create doc (no template = show available templates)
-  - '*brainstorm {topic}" - Facilitate structured brainstorming session'
+  - brainstorm {topic}: Facilitate structured brainstorming session
-  - '*research {topic}" - Generate deep research prompt for investigation'
+  - research {topic}: Generate deep research prompt for investigation
-  - '*elicit" - Run advanced elicitation to clarify requirements'
+  - elicit: Run advanced elicitation to clarify requirements
-  - '*exit" - Say goodbye as the Business Analyst, and then abandon inhabiting this persona'
+  - exit: Say goodbye as the Business Analyst, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - brainstorming-techniques
@@ -820,6 +820,8 @@ Choose an action (0-9 - 9 to bypass - HELP for explanation of these options):
 ==================== START: templates#project-brief-tmpl ====================
 # Project Brief: {{Project Name}}
 
+[[LLM: The default path and filename unless specified is docs/brief.md]]
+
 [[LLM: This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development.
 
 Start by asking the user which mode they prefer:
@@ -1051,6 +1053,8 @@ These replace the standard elicitation options when working on project brief doc
 ==================== START: templates#market-research-tmpl ====================
 # Market Research Report: {{Project/Product Name}}
 
+[[LLM: The default path and filename unless specified is docs/market-research.md]]
+
 [[LLM: This template guides the creation of a comprehensive market research report. Begin by understanding what market insights the user needs and why. Work through each section systematically, using the appropriate analytical frameworks based on the research objectives.]]
 
 ## Executive Summary
@@ -1315,6 +1319,8 @@ These replace the standard elicitation options when working on market research d
 ==================== START: templates#competitor-analysis-tmpl ====================
 # Competitive Analysis Report: {{Project/Product Name}}
 
+[[LLM: The default path and filename unless specified is docs/competitor-analysis.md]]
+
 [[LLM: This template guides comprehensive competitor analysis. Start by understanding the user's competitive intelligence needs and strategic objectives. Help them identify and prioritize competitors before diving into detailed analysis.]]
 
 ## Executive Summary
@@ -1619,6 +1625,60 @@ BMAD-METHOD (Breakthrough Method of Agile AI-driven Development) is a framework
 - **Reusable Resources**: Portable templates, tasks, and checklists
 - **Slash Command Integration**: Quick agent switching and control
 
+### When to Use BMAD
+
+- **New Projects (Greenfield)**: Complete end-to-end development
+- **Existing Projects (Brownfield)**: Feature additions and enhancements
+- **Team Collaboration**: Multiple roles working together
+- **Quality Assurance**: Structured testing and validation
+- **Documentation**: Professional PRDs, architecture docs, user stories
+
+## Getting Started
+
+### Quick Start Options
+
+#### Option 1: Web UI
+**Best for**: ChatGPT, Claude, Gemini users who want to start immediately
+
+1. Navigate to `dist/teams/`
+2. Copy `team-fullstack.txt` content
+3. Create new Gemini Gem or CustomGPT
+4. Upload file with instructions: "Your critical operating instructions are attached, do not break character as directed"
+5. Type `/help` to see available commands
+
+#### Option 2: IDE Integration
+**Best for**: Cursor, Claude Code, Windsurf, VS Code users
+
+```bash
+# Interactive installation (recommended)
+npx bmad-method install
+```
+
+**Installation Steps**:
+- Choose "Complete installation"
+- Select your IDE (Cursor, Claude Code, Windsurf, or Roo Code)
+
+**Verify Installation**:
+- `.bmad-core/` folder created with all agents
+- IDE-specific integration files created
+- All agent commands/rules/modes available
+
+### Environment Selection Guide
+
+**Use Web UI for**:
+- Initial planning and documentation (PRD, architecture)
+- Cost-effective document creation (especially with Gemini)
+- Brainstorming and analysis phases
+- Multi-agent consultation and planning
+
+**Use IDE for**:
+- Active development and coding
+- File operations and project integration
+- Document sharding and story management
+- Implementation workflow (SM/Dev cycles)
+
+**Cost-Saving Tip**: Create large documents (PRDs, architecture) in web UI, then copy to `docs/prd.md` and `docs/architecture.md` in your project before switching to IDE for development.
+
 ## Core Philosophy
 
 ### Vibe CEO'ing
@@ -1640,18 +1700,345 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
 7. **START_SMALL_SCALE_FAST**: Test concepts, then expand.
 8. **EMBRACE_THE_CHAOS**: Adapt and overcome challenges.
 
-## IDE Development Workflow
+### Key Workflow Principles
 
-1. Shard the PRD (And Architecture documents if they exist also based on workflow type) using the Doc Shard task. The BMad-Master agent can help you do this. You will select the task, provide the doc to shard and the output folder. for example: `BMad Master, please Shard the docs/prd.md to the doc/prd/ folder` - this should ask you to use the md-tree-parser which is recommended, but either way shoudl result in multiple documents being created in the folder docs/prd.
+1. **Agent Specialization**: Each agent has specific expertise and responsibilities
-2. If you have fullstack, front end and or back end architecture documents you will want to follow the same thing, but shard all of these to an architecture folder instead of a prd folder.
+2. **Clean Handoffs**: Always start fresh when switching between agents
-3. Ensure that you have at least one epic-n.md file in your prd folder, with the stories in order to develop.
+3. **Status Tracking**: Maintain story statuses (Draft → Approved → InProgress → Done)
-4. The docs or architecture folder or prd folder should have a source tree document and coding standards at a minimum. These are used by the dev agent, and the many other sharded docs are used by the SM agent.
+4. **Iterative Development**: Complete one story before starting the next
-5. Use a new chat window to allow the SM agent to `draft the next story`.
+5. **Documentation First**: Always start with solid PRD and architecture
-6. If you agree the story is correct, mark it as approved in the status field, and then start a new chat window with the dev agent.
-7. Ask the dev agent to implement the next story. If you draft the story file into the chat it will save time for the dev to have to find what the next one is. The dev should follow the tasks and subtasks marking them off as they are completed. The dev agent will also leave notes potentially for the SM to know about any deviations that might have occured to help draft the next story.
-8. Once complete and you have verified, mark it done, and start a new chat. Ask the SM to draft the next story - repeating the cycle.
 
-With this work flow, there is only 1 story in progress at a time, worked sequentially.
+## Agent System
+
+### Core Development Team
+
+| Agent       | Role               | Primary Functions                       | When to Use                            |
+| ----------- | ------------------ | --------------------------------------- | -------------------------------------- |
+| `analyst`   | Business Analyst   | Market research, requirements gathering | Project planning, competitive analysis |
+| `pm`        | Product Manager    | PRD creation, feature prioritization    | Strategic planning, roadmaps           |
+| `architect` | Solution Architect | System design, technical architecture   | Complex systems, scalability planning  |
+| `dev`       | Developer          | Code implementation, debugging          | All development tasks                  |
+| `qa`        | QA Specialist      | Test planning, quality assurance        | Testing strategies, bug validation     |
+| `ux-expert` | UX Designer        | UI/UX design, prototypes                | User experience, interface design      |
+| `po`        | Product Owner      | Backlog management, story validation    | Story refinement, acceptance criteria  |
+| `sm`        | Scrum Master       | Sprint planning, story creation         | Project management, workflow           |
+
+### Meta Agents
+
+| Agent               | Role             | Primary Functions                     | When to Use                       |
+| ------------------- | ---------------- | ------------------------------------- | --------------------------------- |
+| `bmad-orchestrator` | Team Coordinator | Multi-agent workflows, role switching | Complex multi-role tasks          |
+| `bmad-master`       | Universal Expert | All capabilities without switching    | Single-session comprehensive work |
+
+### Agent Interaction Commands
+
+#### IDE-Specific Syntax
+
+**Agent Loading by IDE**:
+- **Claude Code**: `/agent-name` (e.g., `/bmad-master`)
+- **Cursor**: `@agent-name` (e.g., `@bmad-master`)
+- **Windsurf**: `@agent-name` (e.g., `@bmad-master`)
+- **Roo Code**: Select mode from mode selector (e.g., `bmad-bmad-master`)
+
+**Chat Management Guidelines**:
+- **Claude Code, Cursor, Windsurf**: Start new chats when switching agents
+- **Roo Code**: Switch modes within the same conversation
+
+**Common Task Commands**:
+- `*help` - Show available commands
+- `*status` - Show current context/progress
+- `*exit` - Exit the agent mode
+- `*shard-doc docs/prd.md prd` - Shard PRD into manageable pieces
+- `*shard-doc docs/architecture.md architecture` - Shard architecture document
+- `*create` - Run create-next-story task (SM agent)
+
+**In Web UI**:
+```text
+/pm create-doc prd
+/architect review system design
+/dev implement story 1.2
+/help - Show available commands
+/switch agent-name - Change active agent (if orchestrator available)
+```
+
+## Team Configurations
+
+### Pre-Built Teams
+
+#### Team All
+- **Includes**: All 10 agents + orchestrator
+- **Use Case**: Complete projects requiring all roles
+- **Bundle**: `team-all.txt`
+
+#### Team Fullstack
+- **Includes**: PM, Architect, Developer, QA, UX Expert
+- **Use Case**: End-to-end web/mobile development
+- **Bundle**: `team-fullstack.txt`
+
+#### Team No-UI
+- **Includes**: PM, Architect, Developer, QA (no UX Expert)
+- **Use Case**: Backend services, APIs, system development
+- **Bundle**: `team-no-ui.txt`
+
+## Core Architecture
+
+### System Overview
+
+The BMAD-Method is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
+
+### Key Architectural Components
+
+#### 1. Agents (`bmad-core/agents/`)
+- **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.)
+- **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies
+- **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use
+- **Startup Instructions**: Can load project-specific documentation for immediate context
+
+#### 2. Agent Teams (`bmad-core/agent-teams/`)
+- **Purpose**: Define collections of agents bundled together for specific purposes
+- **Examples**: `team-all.yml` (comprehensive bundle), `team-fullstack.yml` (full-stack development)
+- **Usage**: Creates pre-packaged contexts for web UI environments
+
+#### 3. Workflows (`bmad-core/workflows/`)
+- **Purpose**: YAML files defining prescribed sequences of steps for specific project types
+- **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development
+- **Structure**: Defines agent interactions, artifacts created, and transition conditions
+
+#### 4. Reusable Resources
+- **Templates** (`bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories
+- **Tasks** (`bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story"
+- **Checklists** (`bmad-core/checklists/`): Quality assurance checklists for validation and review
+- **Data** (`bmad-core/data/`): Core knowledge base and technical preferences
+
+### Dual Environment Architecture
+
+#### IDE Environment
+
+- Users interact directly with agent markdown files
+- Agents can access all dependencies dynamically
+- Supports real-time file operations and project integration
+- Optimized for development workflow execution
+
+#### Web UI Environment
+
+- Uses pre-built bundles from `dist/teams` for stand alone 1 upload files for all agents and their assest with an orchestrating agent
+- Single text files containing all agent dependencies are in `dist/agents/` - these are unnecessary unless you want to create a web agent that is only a single agent and not a team
+- Created by the web-builder tool for upload to web interfaces
+- Provides complete context in one package
+
+### Template Processing System
+
+BMAD employs a sophisticated template system with three key components:
+
+1. **Template Format** (`utils/template-format.md`): Defines markup language for variable substitution and AI processing directives
+2. **Document Creation** (`tasks/create-doc.md`): Orchestrates template selection and user interaction
+3. **Advanced Elicitation** (`tasks/advanced-elicitation.md`): Provides interactive refinement through structured brainstorming
+
+**Template Features**:
+
+- **Self-contained**: Templates embed both output structure and processing instructions
+- **Variable Substitution**: `{{placeholders}}` for dynamic content
+- **AI Processing Directives**: `[[LLM: instructions]]` for AI-only processing
+- **Interactive Refinement**: Built-in elicitation processes for quality improvement
+
+### Technical Preferences Integration
+
+The `technical-preferences.md` file serves as a persistent technical profile that:
+- Ensures consistency across all agents and projects
+- Eliminates repetitive technology specification
+- Provides personalized recommendations aligned with user preferences
+- Evolves over time with lessons learned
+
+### Build and Delivery Process
+
+The `web-builder.js` tool creates web-ready bundles by:
+1. Reading agent or team definition files
+2. Recursively resolving all dependencies
+3. Concatenating content into single text files with clear separators
+4. Outputting ready-to-upload bundles for web AI interfaces
+
+This architecture enables seamless operation across environments while maintaining the rich, interconnected agent ecosystem that makes BMAD powerful.
+
+## Complete Development Workflow
+
+### Planning Phase (Web UI Recommended)
+
+**Ideal for cost efficiency, especially with Gemini:**
+
+1. **Optional Analysis**: `/analyst` - Market research, competitive analysis
+2. **Project Brief**: Create foundation document (Analyst or user)
+3. **PRD Creation**: `/pm create-doc prd` - Comprehensive product requirements
+4. **Architecture Design**: `/architect create-doc architecture` - Technical foundation
+5. **Validation & Alignment**: `/po` run master checklist to ensure document consistency
+6. **Document Preparation**: Copy final documents to project as `docs/prd.md` and `docs/architecture.md`
+
+#### Example Planning Prompts
+
+**For PRD Creation**:
+```text
+"I want to build a [type] application that [core purpose].
+Help me brainstorm features and create a comprehensive PRD."
+```
+
+**For Architecture Design**:
+```text
+"Based on this PRD, design a scalable technical architecture
+that can handle [specific requirements]."
+```
+
+### Critical Transition: Web UI to IDE
+
+**Once planning is complete, you MUST switch to IDE for development:**
+
+- **Why**: Development workflow requires file operations, real-time project integration, and document sharding
+- **Cost Benefit**: Web UI is more cost-effective for large document creation; IDE is optimized for development tasks
+- **Required Files**: Ensure `docs/prd.md` and `docs/architecture.md` exist in your project
+
+### IDE Development Workflow
+
+**Prerequisites**: Planning documents must exist in `docs/` folder
+
+1. **Document Sharding**: 
+   - `@bmad-master` or `@po` shard `docs/prd.md` to `docs/prd/` folder
+   - If architecture exists, shard to `docs/architecture/` folder
+   - Results in multiple manageable documents and epic files
+
+2. **Verify Sharded Content**:
+   - At least one `epic-n.md` file in `docs/prd/` with stories in development order
+   - Source tree document and coding standards for dev agent reference
+   - Sharded docs for SM agent story creation
+
+**Resulting Folder Structure**:
+- `docs/prd/` - Broken down PRD sections
+- `docs/architecture/` - Broken down architecture sections
+- `docs/stories/` - Generated user stories
+
+3. **Development Cycle** (Sequential, one story at a time):
+
+   **Step 1 - Story Creation**: New chat window → `@sm` → `*create`
+   - SM executes create-next-story task
+   - Review generated story in `docs/stories/`
+   - Update status from "Draft" to "Approved"
+   
+   **Step 2 - Story Implementation**: New chat window → `@dev`
+   - Agent asks which story to implement
+   - Include story file content to save dev agent lookup time
+   - Dev follows tasks/subtasks, marking completion
+   - Dev leaves notes for SM about any deviations
+   - Update status to "Done"
+   
+   **Step 3 - Repeat**: Continue SM → Dev cycle until all epic stories complete
+
+**Important**: Only 1 story in progress at a time, worked sequentially until all epic stories complete.
+
+### Status Tracking Workflow
+
+Stories progress through defined statuses:
+- **Draft** → **Approved** → **InProgress** → **Done**
+
+Each status change requires user verification and approval before proceeding.
+
+### Workflow Types
+
+#### Greenfield Development
+- Business analysis and market research
+- Product requirements and feature definition  
+- System architecture and design
+- Development execution
+- Testing and deployment
+
+#### Brownfield Enhancement
+- Current system analysis
+- Enhancement planning
+- Impact assessment
+- Incremental development
+- Integration testing
+
+## Document Creation Best Practices
+
+### Required File Naming for Framework Integration
+
+- `docs/prd.md` - Product Requirements Document
+- `docs/architecture.md` - System Architecture Document
+
+**Why These Names Matter**:
+- Agents automatically reference these files during development
+- Sharding tasks expect these specific filenames
+- Workflow automation depends on standard naming
+
+### Cost-Effective Document Creation Workflow
+
+**Recommended for Large Documents (PRD, Architecture):**
+
+1. **Use Web UI**: Create documents in web interface for cost efficiency
+2. **Copy Final Output**: Save complete markdown to your project
+3. **Standard Names**: Save as `docs/prd.md` and `docs/architecture.md`
+4. **Switch to IDE**: Use IDE agents for development and smaller documents
+
+### Document Sharding
+
+Templates with Level 2 headings (`##`) can be automatically sharded:
+
+**Original PRD**:
+```markdown
+## Goals and Background Context
+## Requirements  
+## User Interface Design Goals
+## Success Metrics
+```
+
+**After Sharding**:
+- `docs/prd/goals-and-background-context.md`
+- `docs/prd/requirements.md`
+- `docs/prd/user-interface-design-goals.md`
+- `docs/prd/success-metrics.md`
+
+Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic sharding.
+
+## Usage Patterns and Best Practices
+
+### Environment-Specific Usage
+
+**Web UI Best For**:
+- Initial planning and documentation phases
+- Cost-effective large document creation
+- Agent consultation and brainstorming
+- Multi-agent workflows with orchestrator
+
+**IDE Best For**:
+- Active development and implementation
+- File operations and project integration
+- Story management and development cycles
+- Code review and debugging
+
+### Quality Assurance
+
+- Use appropriate agents for specialized tasks
+- Follow Agile ceremonies and review processes
+- Maintain document consistency with PO agent
+- Regular validation with checklists and templates
+
+### Performance Optimization
+
+- Use specific agents vs. `bmad-master` for focused tasks
+- Choose appropriate team size for project needs
+- Leverage technical preferences for consistency
+- Regular context management and cache clearing
+
+## Success Tips
+
+- **Use Gemini for big picture planning** - The team-fullstack bundle provides collaborative expertise
+- **Use bmad-master for document organization** - Sharding creates manageable chunks
+- **Follow the SM → Dev cycle religiously** - This ensures systematic progress
+- **Keep conversations focused** - One agent, one task per conversation
+- **Review everything** - Always review and approve before marking complete
+
+## Getting Help
+
+- **Commands**: Use `/help` in any environment to see available commands
+- **Agent Switching**: Use `/switch agent-name` with orchestrator for role changes
+- **Documentation**: Check `docs/` folder for project-specific context
+- **Community**: Discord and GitHub resources available for support
 ==================== END: data#bmad-kb ====================
 
 ==================== START: utils#template-format ====================

dist/agents/architect.txt

@@ -76,12 +76,12 @@ startup:
   - Greet the user with your name and role, and inform of the *help command.
   - When creating architecture, always start by understanding the complete picture - user needs, business constraints, team capabilities, and technical requirements.
 commands:
-  - '*help" - Show: numbered list of the following commands to allow selection'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - (Default) Architect consultation with advanced-elicitation for complex system design'
+  - chat-mode: (Default) Architect consultation with advanced-elicitation for complex system design
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - create-doc {template}: Create doc (no template = show available templates)
-  - '*execute-checklist {checklist}" - Run architectural validation checklist'
+  - execute-checklist {checklist}: Run architectural validation checklist
-  - '*research {topic}" - Generate deep research prompt for architectural decisions'
+  - research {topic}: Generate deep research prompt for architectural decisions
-  - '*exit" - Say goodbye as the Architect, and then abandon inhabiting this persona'
+  - exit: Say goodbye as the Architect, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - create-doc
@@ -980,6 +980,8 @@ The LLM will:
 
 [[LLM: If available, review any provided relevant documents to gather all relevant context before beginning. If at a minimum you cannot local `docs/prd.md` ask the user what docs will provide the basis for the architecture.]]
 
+[[LLM: The default path and filename unless specified is docs/architecture.md]]
+
 ## Introduction
 
 [[LLM: This section establishes the document's purpose and scope. Keep the content below but ensure project name is properly substituted.
@@ -1333,7 +1335,7 @@ servers:
       '[object Object]': null
     description:
       '[object Object]': null
-```text
+```
 
 ^^/CONDITION: has_rest_api^^
 
@@ -1396,7 +1398,6 @@ 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/
@@ -1408,6 +1409,7 @@ project-root/
 ├── scripts/ # Monorepo management scripts
 └── package.json # Root package.json with workspaces
 @{/example}
+```
 
 [[LLM: After presenting the source tree structure, apply `tasks#advanced-elicitation` protocol]]
 
@@ -1755,6 +1757,8 @@ Note: Basic info goes in Coding Standards for dev agent. This detailed section i
 ==================== START: templates#front-end-architecture-tmpl ====================
 # {{Project Name}} Frontend Architecture Document
 
+[[LLM: The default path and filename unless specified is docs/ui-architecture.md]]
+
 [[LLM: Review provided documents including PRD, UX-UI Specification, and main Architecture Document. Focus on extracting technical implementation details needed for AI frontend tools and developer agents. Ask the user for any of these documents if you are unable to locate and were not provided.]]
 
 ## Template and Framework Selection
@@ -1931,6 +1935,8 @@ Document the starter template decision and any constraints it imposes before pro
 ==================== START: templates#fullstack-architecture-tmpl ====================
 # {{Project Name}} Fullstack Architecture Document
 
+[[LLM: The default path and filename unless specified is docs/architecture.md]]
+
 [[LLM: If available, review any provided relevant documents to gather all relevant context before beginning. At minimum, you should have access to docs/prd.md and docs/front-end-spec.md. Ask the user for any documents you need but cannot locate. This template creates a unified architecture that covers both backend and frontend concerns to guide AI-driven fullstack development.]]
 
 ## Introduction
@@ -2950,6 +2956,8 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 ==================== START: templates#brownfield-architecture-tmpl ====================
 # {{Project Name}} Brownfield Enhancement Architecture
 
+[[LLM: The default path and filename unless specified is docs/architecture.md]]
+
 [[LLM: IMPORTANT - SCOPE AND ASSESSMENT REQUIRED:
 
 This architecture document is for SIGNIFICANT enhancements to existing projects that require comprehensive architectural planning. Before proceeding:
@@ -3174,7 +3182,7 @@ Present component architecture and apply `tasks#advanced-elicitation` protocol]]
 
 ```mermaid
 {{component_interaction_diagram}}
-```text
+```
 
 ## API Design and Integration
 
@@ -3214,7 +3222,7 @@ Present API design and apply `tasks#advanced-elicitation` protocol]]
 
 ```json
 {{response_schema}}
-```text
+```
 
 <</REPEAT>>
 

dist/agents/bmad-master.txt

@@ -41,9 +41,9 @@ These references map directly to bundle sections:
 ==================== START: agents#bmad-master ====================
 # bmad-master
 
-CRITICAL: Read the full YML to understand your operating params, start activation to alter your state of being, follow startup instructions, stay in this being until told to exit this mode:
+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
 agent:
   name: BMad Master
   id: bmad-master
@@ -63,21 +63,21 @@ persona:
     - Use numbered lists for choices
     - Process (*) commands immediately
 startup:
-  - Announce: I'm BMad Master, your BMAD task executor. I can run any task, template, util, checklist, workflow, or schema. Type *help or tell me what you need.
+  - Greet the user with your name and role, and inform of the *help command.
   - CRITICAL: Do NOT scan filesystem or load any resources during startup
   - CRITICAL: Do NOT run discovery tasks automatically
   - Wait for user request before any tool use
   - Match request to resources, offer numbered options if unclear
   - Load resources only when explicitly requested
 commands:
-  - '*help" - Show commands'
+  - help: Show commands
-  - '*chat" - Advanced elicitation + KB mode'
+  - chat: Advanced elicitation + KB mode
-  - '*status" - Current context'
+  - status: Current context
-  - '*task/template/util/checklist/workflow {name}" - Execute (list if no name)'
+  - task {template|util|checklist|workflow}: Execute
-  - '*list {type}" - List resources by type'
+  - list {task|template|util|checklist|workflow}: List resources by type
-  - '*exit" - Exit (confirm)'
+  - exit: Exit (confirm)
-  - '*yolo" - Skip confirmations'
+  - yolo: Toggle Yolo Mode off on - on will skip doc section confirmations
-  - '*doc-out" - Output full document'
+  - doc-out: Output full document
 fuzzy-matching:
   - 85% confidence threshold
   - Show numbered list if unsure
@@ -115,7 +115,6 @@ dependencies:
     - prd-tmpl
     - project-brief-tmpl
     - story-tmpl
-    - web-agent-startup-instructions-template
   data:
     - bmad-kb
     - technical-preferences
@@ -1722,45 +1721,42 @@ Present a summary of what was created and ask if any additional documentation wo
 
 To identify the next logical story based on project progress and epic definitions, and then to prepare a comprehensive, self-contained, and actionable story file using the `Story Template`. This task ensures the story is enriched with all necessary technical context, requirements, and acceptance criteria, making it ready for efficient implementation by a Developer Agent with minimal need for additional research.
 
-## Inputs for this Task
-
-- Access to the project's documentation repository, specifically:
-  - `docs/index.md` (hereafter "Index Doc")
-  - All Epic files - located in one of these locations:
-    - Primary: `docs/prd/epic-{n}-{description}.md` (e.g., `epic-1-foundation-core-infrastructure.md`)
-    - Secondary: `docs/epics/epic-{n}-{description}.md`
-    - User-specified location if not found in above paths
-  - Existing story files in `docs/stories/`
-  - Main PRD (hereafter "PRD Doc")
-  - Main Architecture Document (hereafter "Main Arch Doc")
-  - Frontend Architecture Document (hereafter "Frontend Arch Doc," if relevant)
-  - Project Structure Guide (`docs/project-structure.md`)
-  - Operational Guidelines Document (`docs/operational-guidelines.md`)
-  - Technology Stack Document (`docs/tech-stack.md`)
-  - Data Models Document (as referenced in Index Doc)
-  - API Reference Document (as referenced in Index Doc)
-  - UI/UX Specifications, Style Guides, Component Guides (if relevant, as referenced in Index Doc)
-- The `bmad-core/templates/story-tmpl.md` (hereafter "Story Template")
-- The `bmad-core/checklists/story-draft-checklist.md` (hereafter "Story Draft Checklist")
-- User confirmation to proceed with story identification and, if needed, to override warnings about incomplete prerequisite stories.
-
 ## Task Execution Instructions
 
+### 0. Load Core Configuration
+
+[[LLM: CRITICAL - This MUST be your first step]]
+
+- Load `.bmad-core/core-config.yml` from the project root
+- If the file does not exist:
+  - HALT and inform the user: "core-config.yml not found. This file is required for story creation. You can:
+    1. Copy it from GITHUB BMAD-METHOD/bmad-core/core-config.yml and configure it for your project
+    2. Run the BMAD installer against your project to upgrade and add the file automatically
+    Please add and configure core-config.yml before proceeding."
+- Extract the following key configurations:
+  - `dev-story-location`: Where to save story files
+  - `prd.prdSharded`: Whether PRD is sharded or monolithic
+  - `prd.prd-file`: Location of monolithic PRD (if not sharded)
+  - `prd.prdShardedLocation`: Location of sharded epic files
+  - `prd.epicFilePattern`: Pattern for epic files (e.g., `epic-{n}*.md`)
+  - `architecture.architectureVersion`: Architecture document version
+  - `architecture.architectureSharded`: Whether architecture is sharded
+  - `architecture.architecture-file`: Location of monolithic architecture
+  - `architecture.architectureShardedLocation`: Location of sharded architecture files
+
 ### 1. Identify Next Story for Preparation
 
 #### 1.1 Locate Epic Files
 
-- First, determine where epic files are located:
+- Based on `prdSharded` from config:
-  - Check `docs/prd/` for files matching pattern `epic-{n}-*.md`
+  - **If `prdSharded: true`**: Look for epic files in `prdShardedLocation` using `epicFilePattern`
-  - If not found, check `docs/epics/` for files matching pattern `epic-{n}-*.md`
+  - **If `prdSharded: false`**: Load the full PRD from `prd-file` and extract epics from section headings (## Epic N or ### Epic N)
-  - If still not found, ask user: "Unable to locate epic files. Please specify the path where epic files are stored."
-- Note: Epic files follow naming convention `epic-{n}-{description}.md` (e.g., `epic-1-foundation-core-infrastructure.md`)
 
 #### 1.2 Review Existing Stories
 
-- Review `docs/stories/` to find the highest-numbered story file.
+- Check `dev-story-location` from config (e.g., `docs/stories/`) for existing story files
+- If the directory exists and has at least 1 file, find the highest-numbered story file.
 - **If a highest story file exists (`{lastEpicNum}.{lastStoryNum}.story.md`):**
-
   - Verify its `Status` is 'Done' (or equivalent).
   - If not 'Done', present an alert to the user:
 
@@ -1778,17 +1774,17 @@ To identify the next logical story based on project progress and epic definition
     ```
 
   - Proceed only if user selects option 3 (Override) or if the last story was 'Done'.
-  - If proceeding: Look for the Epic File for `{lastEpicNum}` (e.g., `epic-{lastEpicNum}-*.md`) and check for a story numbered `{lastStoryNum + 1}`. If it exists and its prerequisites (per Epic File) are met, this is the next story.
+  - If proceeding: Look for the Epic File for `{lastEpicNum}` (e.g., `epic-{lastEpicNum}*.md`) and check for a story numbered `{lastStoryNum + 1}`. If it exists and its prerequisites (per Epic File) are met, this is the next story.
-  - Else (story not found or prerequisites not met): The next story is the first story in the next Epic File (e.g., look for `epic-{lastEpicNum + 1}-*.md`, then `epic-{lastEpicNum + 2}-*.md`, etc.) whose prerequisites are met.
+  - Else (story not found or prerequisites not met): The next story is the first story in the next Epic File (e.g., look for `epic-{lastEpicNum + 1}*.md`, then `epic-{lastEpicNum + 2}*.md`, etc.) whose prerequisites are met.
 
 - **If no story files exist in `docs/stories/`:**
   - The next story is the first story in the first epic file (look for `epic-1-*.md`, then `epic-2-*.md`, etc.) whose prerequisites are met.
 - If no suitable story with met prerequisites is found, report to the user that story creation is blocked, specifying what prerequisites are pending. HALT task.
 - Announce the identified story to the user: "Identified next story for preparation: {epicNum}.{storyNum} - {Story Title}".
 
-### 2. Gather Core Story Requirements (from Epic File)
+### 2. Gather Core Story Requirements (from Epic)
 
-- For the identified story, open its parent Epic File (e.g., `epic-{epicNum}-*.md` from the location identified in step 1.1).
+- For the identified story, review its parent Epic (e.g., `epic-{epicNum}*.md` from the location identified in step 1.1).
 - Extract: Exact Title, full Goal/User Story statement, initial list of Requirements, all Acceptance Criteria (ACs), and any predefined high-level Tasks.
 - Keep a record of this original epic-defined scope for later deviation analysis.
 
@@ -1797,7 +1793,7 @@ To identify the next logical story based on project progress and epic definition
 [[LLM: This step is CRITICAL for continuity and learning from implementation experience]]
 
 - If this is not the first story (i.e., previous story exists):
-  - Read the previous story file: `docs/stories/{prevEpicNum}.{prevStoryNum}.story.md`
+  - Read the previous sequential story from `docs/stories`
   - Pay special attention to:
     - Dev Agent Record sections (especially Completion Notes and Debug Log References)
     - Any deviations from planned implementation
@@ -1806,18 +1802,30 @@ To identify the next logical story based on project progress and epic definition
     - Any "lessons learned" or notes for future stories
   - Extract relevant insights that might inform the current story's preparation
 
-### 4. Gather & Synthesize Architecture Context from Sharded Docs
+### 4. Gather & Synthesize Architecture Context
 
-[[LLM: CRITICAL - You MUST gather technical details from the sharded architecture documents. NEVER make up technical details not found in these documents.]]
+[[LLM: CRITICAL - You MUST gather technical details from the architecture documents. NEVER make up technical details not found in these documents.]]
 
-#### 4.1 Start with Architecture Index
+#### 4.1 Determine Architecture Document Strategy
 
-- Read `docs/architecture/index.md` to understand the full scope of available documentation
+Based on configuration loaded in Step 0:
-- Identify which sharded documents are most relevant to the current story
 
-#### 4.2 Recommended Reading Order Based on Story Type
+- **If `architectureVersion: v4` and `architectureSharded: true`**:
+  - Read `{architectureShardedLocation}/index.md` to understand available documentation
+  - Follow the structured reading order in section 4.2 below
+  
+- **If `architectureVersion: v4` and `architectureSharded: false`**:
+  - Load the monolithic architecture from `architecture-file`
+  - Extract relevant sections based on v4 structure (tech stack, project structure, etc.)
+  
+- **If `architectureVersion` is NOT v4**:
+  - Inform user: "Architecture document is not v4 format. Will use best judgment to find relevant information."
+  - If `architectureSharded: true`: Search sharded files by filename relevance
+  - If `architectureSharded: false`: Search within monolithic `architecture-file` for relevant sections
 
-[[LLM: Read documents in this order, but ALWAYS verify relevance to the specific story. Skip irrelevant sections but NEVER skip documents that contain information needed for the story.]]
+#### 4.2 Recommended Reading Order Based on Story Type (v4 Sharded Only)
+
+[[LLM: Use this structured approach ONLY for v4 sharded architecture. For other versions, use best judgment based on file names and content.]]
 
 **For ALL Stories:**
 
@@ -1826,9 +1834,18 @@ To identify the next logical story based on project progress and epic definition
 3. `docs/architecture/coding-standards.md` - Ensure dev follows project conventions
 4. `docs/architecture/testing-strategy.md` - Include testing requirements in tasks
 
-**For Backend/API Stories, additionally read:** 5. `docs/architecture/data-models.md` - Data structures and validation rules 6. `docs/architecture/database-schema.md` - Database design and relationships 7. `docs/architecture/backend-architecture.md` - Service patterns and structure 8. `docs/architecture/rest-api-spec.md` - API endpoint specifications 9. `docs/architecture/external-apis.md` - Third-party integrations (if relevant)
+**For Backend/API Stories, additionally read:**
+5. `docs/architecture/data-models.md` - Data structures and validation rules
+6. `docs/architecture/database-schema.md` - Database design and relationships
+7. `docs/architecture/backend-architecture.md` - Service patterns and structure
+8. `docs/architecture/rest-api-spec.md` - API endpoint specifications
+9. `docs/architecture/external-apis.md` - Third-party integrations (if relevant)
 
-**For Frontend/UI Stories, additionally read:** 5. `docs/architecture/frontend-architecture.md` - Component structure and patterns 6. `docs/architecture/components.md` - Specific component designs 7. `docs/architecture/core-workflows.md` - User interaction flows 8. `docs/architecture/data-models.md` - Frontend data handling
+**For Frontend/UI Stories, additionally read:**
+5. `docs/architecture/frontend-architecture.md` - Component structure and patterns
+6. `docs/architecture/components.md` - Specific component designs
+7. `docs/architecture/core-workflows.md` - User interaction flows
+8. `docs/architecture/data-models.md` - Frontend data handling
 
 **For Full-Stack Stories:**
 
@@ -1861,7 +1878,7 @@ Format references as: `[Source: architecture/{filename}.md#{section}]`
 
 ### 6. Populate Story Template with Full Context
 
-- Create a new story file: `docs/stories/{epicNum}.{storyNum}.story.md`.
+- Create a new story file: `{dev-story-location}/{epicNum}.{storyNum}.story.md` (using location from config).
 - Use the Story Template to structure the file.
 - Fill in:
   - Story `{EpicNum}.{StoryNum}: {Short Title Copied from Epic File}`
@@ -1908,7 +1925,7 @@ Format references as: `[Source: architecture/{filename}.md#{section}]`
 - Verify all source references are included for technical details
 - Ensure tasks align with both epic requirements and architecture constraints
 - Update status to "Draft"
-- Save the story file to `docs/stories/{epicNum}.{storyNum}.story.md`
+- Save the story file to `{dev-story-location}/{epicNum}.{storyNum}.story.md` (using location from config)
 
 ### 9. Report Completion
 
@@ -2375,7 +2392,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
 
@@ -2441,6 +2458,8 @@ Document sharded successfully:
 
 [[LLM: If available, review any provided relevant documents to gather all relevant context before beginning. If at a minimum you cannot local `docs/prd.md` ask the user what docs will provide the basis for the architecture.]]
 
+[[LLM: The default path and filename unless specified is docs/architecture.md]]
+
 ## Introduction
 
 [[LLM: This section establishes the document's purpose and scope. Keep the content below but ensure project name is properly substituted.
@@ -2794,7 +2813,7 @@ servers:
       '[object Object]': null
     description:
       '[object Object]': null
-```text
+```
 
 ^^/CONDITION: has_rest_api^^
 
@@ -2857,7 +2876,6 @@ 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/
@@ -2869,6 +2887,7 @@ project-root/
 ├── scripts/ # Monorepo management scripts
 └── package.json # Root package.json with workspaces
 @{/example}
+```
 
 [[LLM: After presenting the source tree structure, apply `tasks#advanced-elicitation` protocol]]
 
@@ -3216,6 +3235,8 @@ Note: Basic info goes in Coding Standards for dev agent. This detailed section i
 ==================== START: templates#brownfield-architecture-tmpl ====================
 # {{Project Name}} Brownfield Enhancement Architecture
 
+[[LLM: The default path and filename unless specified is docs/architecture.md]]
+
 [[LLM: IMPORTANT - SCOPE AND ASSESSMENT REQUIRED:
 
 This architecture document is for SIGNIFICANT enhancements to existing projects that require comprehensive architectural planning. Before proceeding:
@@ -3440,7 +3461,7 @@ Present component architecture and apply `tasks#advanced-elicitation` protocol]]
 
 ```mermaid
 {{component_interaction_diagram}}
-```text
+```
 
 ## API Design and Integration
 
@@ -3480,7 +3501,7 @@ Present API design and apply `tasks#advanced-elicitation` protocol]]
 
 ```json
 {{response_schema}}
-```text
+```
 
 <</REPEAT>>
 
@@ -3761,6 +3782,8 @@ Present risk assessment and apply `tasks#advanced-elicitation` protocol]]
 ==================== START: templates#brownfield-prd-tmpl ====================
 # {{Project Name}} Brownfield Enhancement PRD
 
+[[LLM: The default path and filename unless specified is docs/prd.md]]
+
 [[LLM: IMPORTANT - SCOPE ASSESSMENT REQUIRED:
 
 This PRD is for SIGNIFICANT enhancements to existing projects that require comprehensive planning and multiple stories. Before proceeding:
@@ -4004,6 +4027,8 @@ so that {{benefit}}.
 ==================== START: templates#competitor-analysis-tmpl ====================
 # Competitive Analysis Report: {{Project/Product Name}}
 
+[[LLM: The default path and filename unless specified is docs/competitor-analysis.md]]
+
 [[LLM: This template guides comprehensive competitor analysis. Start by understanding the user's competitive intelligence needs and strategic objectives. Help them identify and prioritize competitors before diving into detailed analysis.]]
 
 ## Executive Summary
@@ -4296,6 +4321,8 @@ These replace the standard elicitation options when working on competitive analy
 ==================== START: templates#front-end-architecture-tmpl ====================
 # {{Project Name}} Frontend Architecture Document
 
+[[LLM: The default path and filename unless specified is docs/ui-architecture.md]]
+
 [[LLM: Review provided documents including PRD, UX-UI Specification, and main Architecture Document. Focus on extracting technical implementation details needed for AI frontend tools and developer agents. Ask the user for any of these documents if you are unable to locate and were not provided.]]
 
 ## Template and Framework Selection
@@ -4472,6 +4499,8 @@ Document the starter template decision and any constraints it imposes before pro
 ==================== START: templates#front-end-spec-tmpl ====================
 # {{Project Name}} UI/UX Specification
 
+[[LLM: The default path and filename unless specified is docs/front-end-spec.md]]
+
 [[LLM: Review provided documents including Project Brief, PRD, and any user research to gather context. Focus on understanding user needs, pain points, and desired outcomes before beginning the specification.]]
 
 ## Introduction
@@ -4548,7 +4577,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 ```mermaid
 {{sitemap_diagram}}
-```text
+```
 
 @{example: sitemap}
 
@@ -4886,6 +4915,8 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 ==================== START: templates#fullstack-architecture-tmpl ====================
 # {{Project Name}} Fullstack Architecture Document
 
+[[LLM: The default path and filename unless specified is docs/architecture.md]]
+
 [[LLM: If available, review any provided relevant documents to gather all relevant context before beginning. At minimum, you should have access to docs/prd.md and docs/front-end-spec.md. Ask the user for any documents you need but cannot locate. This template creates a unified architecture that covers both backend and frontend concerns to guide AI-driven fullstack development.]]
 
 ## Introduction
@@ -5905,6 +5936,8 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 ==================== START: templates#market-research-tmpl ====================
 # Market Research Report: {{Project/Product Name}}
 
+[[LLM: The default path and filename unless specified is docs/market-research.md]]
+
 [[LLM: This template guides the creation of a comprehensive market research report. Begin by understanding what market insights the user needs and why. Work through each section systematically, using the appropriate analytical frameworks based on the research objectives.]]
 
 ## Executive Summary
@@ -6169,6 +6202,8 @@ These replace the standard elicitation options when working on market research d
 ==================== START: templates#prd-tmpl ====================
 # {{Project Name}} Product Requirements Document (PRD)
 
+[[LLM: The default path and filename unless specified is docs/prd.md]]
+
 [[LLM: If available, review any provided document or ask if any are optionally available: Project Brief]]
 
 ## Goals and Background Context
@@ -6372,6 +6407,8 @@ so that {{benefit}}.
 ==================== START: templates#project-brief-tmpl ====================
 # Project Brief: {{Project Name}}
 
+[[LLM: The default path and filename unless specified is docs/brief.md]]
+
 [[LLM: This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development.
 
 Start by asking the user which mode they prefer:
@@ -6664,48 +6701,6 @@ Manual Test Steps: [[LLM: Include how if possible the user can manually test the
 | :--- | :------ | :---------- | :----- |
 ==================== END: templates#story-tmpl ====================
 
-==================== START: templates#web-agent-startup-instructions-template ====================
-# Web Agent Bundle Instructions
-
-You are now operating as a specialized AI agent from the BMAD-METHOD framework. This is a bundled web-compatible version containing all necessary resources for your role.
-
-## Important Instructions
-
-1. **Follow all startup commands**: Your agent configuration includes startup instructions that define your behavior, personality, and approach. These MUST be followed exactly.
-
-2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
-
-- `==================== START: folder#filename ====================`
-- `==================== END: folder#filename ====================`
-
-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
-
-**Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
-
-```yaml
-dependencies:
-  utils:
-    - template-format
-  tasks:
-    - create-story
-```
-
-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 ====================`
-
-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.
-
-4. **Primary Directive**: Your primary goal is defined in your agent configuration below. Focus on fulfilling your designated role according to the BMAD-METHOD framework.
-
----
-==================== END: templates#web-agent-startup-instructions-template ====================
-
 ==================== START: checklists#architect-checklist ====================
 # Architect Solution Validation Checklist
 
@@ -8437,6 +8432,60 @@ BMAD-METHOD (Breakthrough Method of Agile AI-driven Development) is a framework
 - **Reusable Resources**: Portable templates, tasks, and checklists
 - **Slash Command Integration**: Quick agent switching and control
 
+### When to Use BMAD
+
+- **New Projects (Greenfield)**: Complete end-to-end development
+- **Existing Projects (Brownfield)**: Feature additions and enhancements
+- **Team Collaboration**: Multiple roles working together
+- **Quality Assurance**: Structured testing and validation
+- **Documentation**: Professional PRDs, architecture docs, user stories
+
+## Getting Started
+
+### Quick Start Options
+
+#### Option 1: Web UI
+**Best for**: ChatGPT, Claude, Gemini users who want to start immediately
+
+1. Navigate to `dist/teams/`
+2. Copy `team-fullstack.txt` content
+3. Create new Gemini Gem or CustomGPT
+4. Upload file with instructions: "Your critical operating instructions are attached, do not break character as directed"
+5. Type `/help` to see available commands
+
+#### Option 2: IDE Integration
+**Best for**: Cursor, Claude Code, Windsurf, VS Code users
+
+```bash
+# Interactive installation (recommended)
+npx bmad-method install
+```
+
+**Installation Steps**:
+- Choose "Complete installation"
+- Select your IDE (Cursor, Claude Code, Windsurf, or Roo Code)
+
+**Verify Installation**:
+- `.bmad-core/` folder created with all agents
+- IDE-specific integration files created
+- All agent commands/rules/modes available
+
+### Environment Selection Guide
+
+**Use Web UI for**:
+- Initial planning and documentation (PRD, architecture)
+- Cost-effective document creation (especially with Gemini)
+- Brainstorming and analysis phases
+- Multi-agent consultation and planning
+
+**Use IDE for**:
+- Active development and coding
+- File operations and project integration
+- Document sharding and story management
+- Implementation workflow (SM/Dev cycles)
+
+**Cost-Saving Tip**: Create large documents (PRDs, architecture) in web UI, then copy to `docs/prd.md` and `docs/architecture.md` in your project before switching to IDE for development.
+
 ## Core Philosophy
 
 ### Vibe CEO'ing
@@ -8458,18 +8507,345 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
 7. **START_SMALL_SCALE_FAST**: Test concepts, then expand.
 8. **EMBRACE_THE_CHAOS**: Adapt and overcome challenges.
 
-## IDE Development Workflow
+### Key Workflow Principles
 
-1. Shard the PRD (And Architecture documents if they exist also based on workflow type) using the Doc Shard task. The BMad-Master agent can help you do this. You will select the task, provide the doc to shard and the output folder. for example: `BMad Master, please Shard the docs/prd.md to the doc/prd/ folder` - this should ask you to use the md-tree-parser which is recommended, but either way shoudl result in multiple documents being created in the folder docs/prd.
+1. **Agent Specialization**: Each agent has specific expertise and responsibilities
-2. If you have fullstack, front end and or back end architecture documents you will want to follow the same thing, but shard all of these to an architecture folder instead of a prd folder.
+2. **Clean Handoffs**: Always start fresh when switching between agents
-3. Ensure that you have at least one epic-n.md file in your prd folder, with the stories in order to develop.
+3. **Status Tracking**: Maintain story statuses (Draft → Approved → InProgress → Done)
-4. The docs or architecture folder or prd folder should have a source tree document and coding standards at a minimum. These are used by the dev agent, and the many other sharded docs are used by the SM agent.
+4. **Iterative Development**: Complete one story before starting the next
-5. Use a new chat window to allow the SM agent to `draft the next story`.
+5. **Documentation First**: Always start with solid PRD and architecture
-6. If you agree the story is correct, mark it as approved in the status field, and then start a new chat window with the dev agent.
-7. Ask the dev agent to implement the next story. If you draft the story file into the chat it will save time for the dev to have to find what the next one is. The dev should follow the tasks and subtasks marking them off as they are completed. The dev agent will also leave notes potentially for the SM to know about any deviations that might have occured to help draft the next story.
-8. Once complete and you have verified, mark it done, and start a new chat. Ask the SM to draft the next story - repeating the cycle.
 
-With this work flow, there is only 1 story in progress at a time, worked sequentially.
+## Agent System
+
+### Core Development Team
+
+| Agent       | Role               | Primary Functions                       | When to Use                            |
+| ----------- | ------------------ | --------------------------------------- | -------------------------------------- |
+| `analyst`   | Business Analyst   | Market research, requirements gathering | Project planning, competitive analysis |
+| `pm`        | Product Manager    | PRD creation, feature prioritization    | Strategic planning, roadmaps           |
+| `architect` | Solution Architect | System design, technical architecture   | Complex systems, scalability planning  |
+| `dev`       | Developer          | Code implementation, debugging          | All development tasks                  |
+| `qa`        | QA Specialist      | Test planning, quality assurance        | Testing strategies, bug validation     |
+| `ux-expert` | UX Designer        | UI/UX design, prototypes                | User experience, interface design      |
+| `po`        | Product Owner      | Backlog management, story validation    | Story refinement, acceptance criteria  |
+| `sm`        | Scrum Master       | Sprint planning, story creation         | Project management, workflow           |
+
+### Meta Agents
+
+| Agent               | Role             | Primary Functions                     | When to Use                       |
+| ------------------- | ---------------- | ------------------------------------- | --------------------------------- |
+| `bmad-orchestrator` | Team Coordinator | Multi-agent workflows, role switching | Complex multi-role tasks          |
+| `bmad-master`       | Universal Expert | All capabilities without switching    | Single-session comprehensive work |
+
+### Agent Interaction Commands
+
+#### IDE-Specific Syntax
+
+**Agent Loading by IDE**:
+- **Claude Code**: `/agent-name` (e.g., `/bmad-master`)
+- **Cursor**: `@agent-name` (e.g., `@bmad-master`)
+- **Windsurf**: `@agent-name` (e.g., `@bmad-master`)
+- **Roo Code**: Select mode from mode selector (e.g., `bmad-bmad-master`)
+
+**Chat Management Guidelines**:
+- **Claude Code, Cursor, Windsurf**: Start new chats when switching agents
+- **Roo Code**: Switch modes within the same conversation
+
+**Common Task Commands**:
+- `*help` - Show available commands
+- `*status` - Show current context/progress
+- `*exit` - Exit the agent mode
+- `*shard-doc docs/prd.md prd` - Shard PRD into manageable pieces
+- `*shard-doc docs/architecture.md architecture` - Shard architecture document
+- `*create` - Run create-next-story task (SM agent)
+
+**In Web UI**:
+```text
+/pm create-doc prd
+/architect review system design
+/dev implement story 1.2
+/help - Show available commands
+/switch agent-name - Change active agent (if orchestrator available)
+```
+
+## Team Configurations
+
+### Pre-Built Teams
+
+#### Team All
+- **Includes**: All 10 agents + orchestrator
+- **Use Case**: Complete projects requiring all roles
+- **Bundle**: `team-all.txt`
+
+#### Team Fullstack
+- **Includes**: PM, Architect, Developer, QA, UX Expert
+- **Use Case**: End-to-end web/mobile development
+- **Bundle**: `team-fullstack.txt`
+
+#### Team No-UI
+- **Includes**: PM, Architect, Developer, QA (no UX Expert)
+- **Use Case**: Backend services, APIs, system development
+- **Bundle**: `team-no-ui.txt`
+
+## Core Architecture
+
+### System Overview
+
+The BMAD-Method is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
+
+### Key Architectural Components
+
+#### 1. Agents (`bmad-core/agents/`)
+- **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.)
+- **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies
+- **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use
+- **Startup Instructions**: Can load project-specific documentation for immediate context
+
+#### 2. Agent Teams (`bmad-core/agent-teams/`)
+- **Purpose**: Define collections of agents bundled together for specific purposes
+- **Examples**: `team-all.yml` (comprehensive bundle), `team-fullstack.yml` (full-stack development)
+- **Usage**: Creates pre-packaged contexts for web UI environments
+
+#### 3. Workflows (`bmad-core/workflows/`)
+- **Purpose**: YAML files defining prescribed sequences of steps for specific project types
+- **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development
+- **Structure**: Defines agent interactions, artifacts created, and transition conditions
+
+#### 4. Reusable Resources
+- **Templates** (`bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories
+- **Tasks** (`bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story"
+- **Checklists** (`bmad-core/checklists/`): Quality assurance checklists for validation and review
+- **Data** (`bmad-core/data/`): Core knowledge base and technical preferences
+
+### Dual Environment Architecture
+
+#### IDE Environment
+
+- Users interact directly with agent markdown files
+- Agents can access all dependencies dynamically
+- Supports real-time file operations and project integration
+- Optimized for development workflow execution
+
+#### Web UI Environment
+
+- Uses pre-built bundles from `dist/teams` for stand alone 1 upload files for all agents and their assest with an orchestrating agent
+- Single text files containing all agent dependencies are in `dist/agents/` - these are unnecessary unless you want to create a web agent that is only a single agent and not a team
+- Created by the web-builder tool for upload to web interfaces
+- Provides complete context in one package
+
+### Template Processing System
+
+BMAD employs a sophisticated template system with three key components:
+
+1. **Template Format** (`utils/template-format.md`): Defines markup language for variable substitution and AI processing directives
+2. **Document Creation** (`tasks/create-doc.md`): Orchestrates template selection and user interaction
+3. **Advanced Elicitation** (`tasks/advanced-elicitation.md`): Provides interactive refinement through structured brainstorming
+
+**Template Features**:
+
+- **Self-contained**: Templates embed both output structure and processing instructions
+- **Variable Substitution**: `{{placeholders}}` for dynamic content
+- **AI Processing Directives**: `[[LLM: instructions]]` for AI-only processing
+- **Interactive Refinement**: Built-in elicitation processes for quality improvement
+
+### Technical Preferences Integration
+
+The `technical-preferences.md` file serves as a persistent technical profile that:
+- Ensures consistency across all agents and projects
+- Eliminates repetitive technology specification
+- Provides personalized recommendations aligned with user preferences
+- Evolves over time with lessons learned
+
+### Build and Delivery Process
+
+The `web-builder.js` tool creates web-ready bundles by:
+1. Reading agent or team definition files
+2. Recursively resolving all dependencies
+3. Concatenating content into single text files with clear separators
+4. Outputting ready-to-upload bundles for web AI interfaces
+
+This architecture enables seamless operation across environments while maintaining the rich, interconnected agent ecosystem that makes BMAD powerful.
+
+## Complete Development Workflow
+
+### Planning Phase (Web UI Recommended)
+
+**Ideal for cost efficiency, especially with Gemini:**
+
+1. **Optional Analysis**: `/analyst` - Market research, competitive analysis
+2. **Project Brief**: Create foundation document (Analyst or user)
+3. **PRD Creation**: `/pm create-doc prd` - Comprehensive product requirements
+4. **Architecture Design**: `/architect create-doc architecture` - Technical foundation
+5. **Validation & Alignment**: `/po` run master checklist to ensure document consistency
+6. **Document Preparation**: Copy final documents to project as `docs/prd.md` and `docs/architecture.md`
+
+#### Example Planning Prompts
+
+**For PRD Creation**:
+```text
+"I want to build a [type] application that [core purpose].
+Help me brainstorm features and create a comprehensive PRD."
+```
+
+**For Architecture Design**:
+```text
+"Based on this PRD, design a scalable technical architecture
+that can handle [specific requirements]."
+```
+
+### Critical Transition: Web UI to IDE
+
+**Once planning is complete, you MUST switch to IDE for development:**
+
+- **Why**: Development workflow requires file operations, real-time project integration, and document sharding
+- **Cost Benefit**: Web UI is more cost-effective for large document creation; IDE is optimized for development tasks
+- **Required Files**: Ensure `docs/prd.md` and `docs/architecture.md` exist in your project
+
+### IDE Development Workflow
+
+**Prerequisites**: Planning documents must exist in `docs/` folder
+
+1. **Document Sharding**: 
+   - `@bmad-master` or `@po` shard `docs/prd.md` to `docs/prd/` folder
+   - If architecture exists, shard to `docs/architecture/` folder
+   - Results in multiple manageable documents and epic files
+
+2. **Verify Sharded Content**:
+   - At least one `epic-n.md` file in `docs/prd/` with stories in development order
+   - Source tree document and coding standards for dev agent reference
+   - Sharded docs for SM agent story creation
+
+**Resulting Folder Structure**:
+- `docs/prd/` - Broken down PRD sections
+- `docs/architecture/` - Broken down architecture sections
+- `docs/stories/` - Generated user stories
+
+3. **Development Cycle** (Sequential, one story at a time):
+
+   **Step 1 - Story Creation**: New chat window → `@sm` → `*create`
+   - SM executes create-next-story task
+   - Review generated story in `docs/stories/`
+   - Update status from "Draft" to "Approved"
+   
+   **Step 2 - Story Implementation**: New chat window → `@dev`
+   - Agent asks which story to implement
+   - Include story file content to save dev agent lookup time
+   - Dev follows tasks/subtasks, marking completion
+   - Dev leaves notes for SM about any deviations
+   - Update status to "Done"
+   
+   **Step 3 - Repeat**: Continue SM → Dev cycle until all epic stories complete
+
+**Important**: Only 1 story in progress at a time, worked sequentially until all epic stories complete.
+
+### Status Tracking Workflow
+
+Stories progress through defined statuses:
+- **Draft** → **Approved** → **InProgress** → **Done**
+
+Each status change requires user verification and approval before proceeding.
+
+### Workflow Types
+
+#### Greenfield Development
+- Business analysis and market research
+- Product requirements and feature definition  
+- System architecture and design
+- Development execution
+- Testing and deployment
+
+#### Brownfield Enhancement
+- Current system analysis
+- Enhancement planning
+- Impact assessment
+- Incremental development
+- Integration testing
+
+## Document Creation Best Practices
+
+### Required File Naming for Framework Integration
+
+- `docs/prd.md` - Product Requirements Document
+- `docs/architecture.md` - System Architecture Document
+
+**Why These Names Matter**:
+- Agents automatically reference these files during development
+- Sharding tasks expect these specific filenames
+- Workflow automation depends on standard naming
+
+### Cost-Effective Document Creation Workflow
+
+**Recommended for Large Documents (PRD, Architecture):**
+
+1. **Use Web UI**: Create documents in web interface for cost efficiency
+2. **Copy Final Output**: Save complete markdown to your project
+3. **Standard Names**: Save as `docs/prd.md` and `docs/architecture.md`
+4. **Switch to IDE**: Use IDE agents for development and smaller documents
+
+### Document Sharding
+
+Templates with Level 2 headings (`##`) can be automatically sharded:
+
+**Original PRD**:
+```markdown
+## Goals and Background Context
+## Requirements  
+## User Interface Design Goals
+## Success Metrics
+```
+
+**After Sharding**:
+- `docs/prd/goals-and-background-context.md`
+- `docs/prd/requirements.md`
+- `docs/prd/user-interface-design-goals.md`
+- `docs/prd/success-metrics.md`
+
+Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic sharding.
+
+## Usage Patterns and Best Practices
+
+### Environment-Specific Usage
+
+**Web UI Best For**:
+- Initial planning and documentation phases
+- Cost-effective large document creation
+- Agent consultation and brainstorming
+- Multi-agent workflows with orchestrator
+
+**IDE Best For**:
+- Active development and implementation
+- File operations and project integration
+- Story management and development cycles
+- Code review and debugging
+
+### Quality Assurance
+
+- Use appropriate agents for specialized tasks
+- Follow Agile ceremonies and review processes
+- Maintain document consistency with PO agent
+- Regular validation with checklists and templates
+
+### Performance Optimization
+
+- Use specific agents vs. `bmad-master` for focused tasks
+- Choose appropriate team size for project needs
+- Leverage technical preferences for consistency
+- Regular context management and cache clearing
+
+## Success Tips
+
+- **Use Gemini for big picture planning** - The team-fullstack bundle provides collaborative expertise
+- **Use bmad-master for document organization** - Sharding creates manageable chunks
+- **Follow the SM → Dev cycle religiously** - This ensures systematic progress
+- **Keep conversations focused** - One agent, one task per conversation
+- **Review everything** - Always review and approve before marking complete
+
+## Getting Help
+
+- **Commands**: Use `/help` in any environment to see available commands
+- **Agent Switching**: Use `/switch agent-name` with orchestrator for role changes
+- **Documentation**: Check `docs/` folder for project-specific context
+- **Community**: Discord and GitHub resources available for support
 ==================== END: data#bmad-kb ====================
 
 ==================== START: data#technical-preferences ====================
@@ -8557,7 +8933,7 @@ Available workflows for [Team Name]:
 [... etc. ...]
 
 Use /workflow-start {number or id} to begin a workflow.
-```text
+```
 
 ### /workflow-start {workflow-id}
 
@@ -8583,7 +8959,7 @@ In Progress:
     - Create PRD (John) - awaiting input
 
 Next: Technical Architecture
-```text
+```
 
 ### /workflow-resume
 
@@ -8599,7 +8975,7 @@ BMad: I see you've completed Discovery and part of Product Planning.
       - UX Strategy with Sally (ux-expert)
 
       Would you like me to load Sally to continue?
-```text
+```
 
 ### /workflow-next
 
@@ -8669,7 +9045,7 @@ BMad: I see you have a PRD and architecture document. Based on these artifacts,
       - Load Sarah (Product Owner) to validate all artifacts
 
       Would you like to continue with this workflow?
-```text
+```
 
 ## Workflow Context Passing
 
@@ -8695,7 +9071,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
 

dist/agents/bmad-orchestrator.txt

@@ -39,9 +39,9 @@ These references map directly to bundle sections:
 ---
 
 ==================== START: agents#bmad-orchestrator ====================
-# bmad
+# bmad-orchestrator
 
-CRITICAL: Read the full YML to understand your operating params, start activation to alter your state of being, follow startup instructions, stay in this being until told to exit this mode:
+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
 agent:
@@ -73,9 +73,9 @@ startup:
   - If clear match to an agent's expertise, suggest transformation with *agent command
   - If project-oriented, suggest *workflow-guidance to explore options
   - Load resources only when needed - never pre-load
-commands:  # All commands require * prefix when used (e.g., *help, *agent pm)
+commands:
   help: Show this guide with available agents and workflows
-  chat-mode: Start conversational mode for detailed assistance  
+  chat-mode: Start conversational mode for detailed assistance
   kb-mode: Load full BMAD knowledge base
   status: Show current context, active agent, and progress
   agent: Transform into a specialized agent (list if name not specified)
@@ -90,41 +90,40 @@ commands:  # All commands require * prefix when used (e.g., *help, *agent pm)
 help-display-template: |
   === BMAD Orchestrator Commands ===
   All commands must start with * (asterisk)
-  
+
   Core 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
   *exit ............... Return to BMad or exit session
-  
+
   Agent & Task Management:
   *agent [name] ....... Transform into specialized agent (list if no name)
   *task [name] ........ Run specific task (list if no name, requires agent)
   *checklist [name] ... Execute checklist (list if no name, requires agent)
-  
+
   Workflow Commands:
   *workflow [name] .... Start specific workflow (list if no name)
   *workflow-guidance .. Get personalized help selecting the right workflow
-  
+
   Other Commands:
   *yolo ............... Toggle skip confirmations mode
   *party-mode ......... Group chat with all agents
   *doc-out ............ Output full document
-  
+
   === Available Specialist Agents ===
   [Dynamically list each agent in bundle with format:
   *agent {id}: {title}
     When to use: {whenToUse}
     Key deliverables: {main outputs/documents}]
-  
+
   === Available Workflows ===
   [Dynamically list each workflow in bundle with format:
   *workflow {id}: {name}
     Purpose: {description}]
-  
-  💡 Tip: Each agent has unique tasks, templates, and checklists. Switch to an agent to access their capabilities!
 
+  💡 Tip: Each agent has unique tasks, templates, and checklists. Switch to an agent to access their capabilities!
 fuzzy-matching:
   - 85% confidence threshold
   - Show numbered list if unsure
@@ -345,6 +344,60 @@ BMAD-METHOD (Breakthrough Method of Agile AI-driven Development) is a framework
 - **Reusable Resources**: Portable templates, tasks, and checklists
 - **Slash Command Integration**: Quick agent switching and control
 
+### When to Use BMAD
+
+- **New Projects (Greenfield)**: Complete end-to-end development
+- **Existing Projects (Brownfield)**: Feature additions and enhancements
+- **Team Collaboration**: Multiple roles working together
+- **Quality Assurance**: Structured testing and validation
+- **Documentation**: Professional PRDs, architecture docs, user stories
+
+## Getting Started
+
+### Quick Start Options
+
+#### Option 1: Web UI
+**Best for**: ChatGPT, Claude, Gemini users who want to start immediately
+
+1. Navigate to `dist/teams/`
+2. Copy `team-fullstack.txt` content
+3. Create new Gemini Gem or CustomGPT
+4. Upload file with instructions: "Your critical operating instructions are attached, do not break character as directed"
+5. Type `/help` to see available commands
+
+#### Option 2: IDE Integration
+**Best for**: Cursor, Claude Code, Windsurf, VS Code users
+
+```bash
+# Interactive installation (recommended)
+npx bmad-method install
+```
+
+**Installation Steps**:
+- Choose "Complete installation"
+- Select your IDE (Cursor, Claude Code, Windsurf, or Roo Code)
+
+**Verify Installation**:
+- `.bmad-core/` folder created with all agents
+- IDE-specific integration files created
+- All agent commands/rules/modes available
+
+### Environment Selection Guide
+
+**Use Web UI for**:
+- Initial planning and documentation (PRD, architecture)
+- Cost-effective document creation (especially with Gemini)
+- Brainstorming and analysis phases
+- Multi-agent consultation and planning
+
+**Use IDE for**:
+- Active development and coding
+- File operations and project integration
+- Document sharding and story management
+- Implementation workflow (SM/Dev cycles)
+
+**Cost-Saving Tip**: Create large documents (PRDs, architecture) in web UI, then copy to `docs/prd.md` and `docs/architecture.md` in your project before switching to IDE for development.
+
 ## Core Philosophy
 
 ### Vibe CEO'ing
@@ -366,18 +419,345 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
 7. **START_SMALL_SCALE_FAST**: Test concepts, then expand.
 8. **EMBRACE_THE_CHAOS**: Adapt and overcome challenges.
 
-## IDE Development Workflow
+### Key Workflow Principles
 
-1. Shard the PRD (And Architecture documents if they exist also based on workflow type) using the Doc Shard task. The BMad-Master agent can help you do this. You will select the task, provide the doc to shard and the output folder. for example: `BMad Master, please Shard the docs/prd.md to the doc/prd/ folder` - this should ask you to use the md-tree-parser which is recommended, but either way shoudl result in multiple documents being created in the folder docs/prd.
+1. **Agent Specialization**: Each agent has specific expertise and responsibilities
-2. If you have fullstack, front end and or back end architecture documents you will want to follow the same thing, but shard all of these to an architecture folder instead of a prd folder.
+2. **Clean Handoffs**: Always start fresh when switching between agents
-3. Ensure that you have at least one epic-n.md file in your prd folder, with the stories in order to develop.
+3. **Status Tracking**: Maintain story statuses (Draft → Approved → InProgress → Done)
-4. The docs or architecture folder or prd folder should have a source tree document and coding standards at a minimum. These are used by the dev agent, and the many other sharded docs are used by the SM agent.
+4. **Iterative Development**: Complete one story before starting the next
-5. Use a new chat window to allow the SM agent to `draft the next story`.
+5. **Documentation First**: Always start with solid PRD and architecture
-6. If you agree the story is correct, mark it as approved in the status field, and then start a new chat window with the dev agent.
-7. Ask the dev agent to implement the next story. If you draft the story file into the chat it will save time for the dev to have to find what the next one is. The dev should follow the tasks and subtasks marking them off as they are completed. The dev agent will also leave notes potentially for the SM to know about any deviations that might have occured to help draft the next story.
-8. Once complete and you have verified, mark it done, and start a new chat. Ask the SM to draft the next story - repeating the cycle.
 
-With this work flow, there is only 1 story in progress at a time, worked sequentially.
+## Agent System
+
+### Core Development Team
+
+| Agent       | Role               | Primary Functions                       | When to Use                            |
+| ----------- | ------------------ | --------------------------------------- | -------------------------------------- |
+| `analyst`   | Business Analyst   | Market research, requirements gathering | Project planning, competitive analysis |
+| `pm`        | Product Manager    | PRD creation, feature prioritization    | Strategic planning, roadmaps           |
+| `architect` | Solution Architect | System design, technical architecture   | Complex systems, scalability planning  |
+| `dev`       | Developer          | Code implementation, debugging          | All development tasks                  |
+| `qa`        | QA Specialist      | Test planning, quality assurance        | Testing strategies, bug validation     |
+| `ux-expert` | UX Designer        | UI/UX design, prototypes                | User experience, interface design      |
+| `po`        | Product Owner      | Backlog management, story validation    | Story refinement, acceptance criteria  |
+| `sm`        | Scrum Master       | Sprint planning, story creation         | Project management, workflow           |
+
+### Meta Agents
+
+| Agent               | Role             | Primary Functions                     | When to Use                       |
+| ------------------- | ---------------- | ------------------------------------- | --------------------------------- |
+| `bmad-orchestrator` | Team Coordinator | Multi-agent workflows, role switching | Complex multi-role tasks          |
+| `bmad-master`       | Universal Expert | All capabilities without switching    | Single-session comprehensive work |
+
+### Agent Interaction Commands
+
+#### IDE-Specific Syntax
+
+**Agent Loading by IDE**:
+- **Claude Code**: `/agent-name` (e.g., `/bmad-master`)
+- **Cursor**: `@agent-name` (e.g., `@bmad-master`)
+- **Windsurf**: `@agent-name` (e.g., `@bmad-master`)
+- **Roo Code**: Select mode from mode selector (e.g., `bmad-bmad-master`)
+
+**Chat Management Guidelines**:
+- **Claude Code, Cursor, Windsurf**: Start new chats when switching agents
+- **Roo Code**: Switch modes within the same conversation
+
+**Common Task Commands**:
+- `*help` - Show available commands
+- `*status` - Show current context/progress
+- `*exit` - Exit the agent mode
+- `*shard-doc docs/prd.md prd` - Shard PRD into manageable pieces
+- `*shard-doc docs/architecture.md architecture` - Shard architecture document
+- `*create` - Run create-next-story task (SM agent)
+
+**In Web UI**:
+```text
+/pm create-doc prd
+/architect review system design
+/dev implement story 1.2
+/help - Show available commands
+/switch agent-name - Change active agent (if orchestrator available)
+```
+
+## Team Configurations
+
+### Pre-Built Teams
+
+#### Team All
+- **Includes**: All 10 agents + orchestrator
+- **Use Case**: Complete projects requiring all roles
+- **Bundle**: `team-all.txt`
+
+#### Team Fullstack
+- **Includes**: PM, Architect, Developer, QA, UX Expert
+- **Use Case**: End-to-end web/mobile development
+- **Bundle**: `team-fullstack.txt`
+
+#### Team No-UI
+- **Includes**: PM, Architect, Developer, QA (no UX Expert)
+- **Use Case**: Backend services, APIs, system development
+- **Bundle**: `team-no-ui.txt`
+
+## Core Architecture
+
+### System Overview
+
+The BMAD-Method is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
+
+### Key Architectural Components
+
+#### 1. Agents (`bmad-core/agents/`)
+- **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.)
+- **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies
+- **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use
+- **Startup Instructions**: Can load project-specific documentation for immediate context
+
+#### 2. Agent Teams (`bmad-core/agent-teams/`)
+- **Purpose**: Define collections of agents bundled together for specific purposes
+- **Examples**: `team-all.yml` (comprehensive bundle), `team-fullstack.yml` (full-stack development)
+- **Usage**: Creates pre-packaged contexts for web UI environments
+
+#### 3. Workflows (`bmad-core/workflows/`)
+- **Purpose**: YAML files defining prescribed sequences of steps for specific project types
+- **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development
+- **Structure**: Defines agent interactions, artifacts created, and transition conditions
+
+#### 4. Reusable Resources
+- **Templates** (`bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories
+- **Tasks** (`bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story"
+- **Checklists** (`bmad-core/checklists/`): Quality assurance checklists for validation and review
+- **Data** (`bmad-core/data/`): Core knowledge base and technical preferences
+
+### Dual Environment Architecture
+
+#### IDE Environment
+
+- Users interact directly with agent markdown files
+- Agents can access all dependencies dynamically
+- Supports real-time file operations and project integration
+- Optimized for development workflow execution
+
+#### Web UI Environment
+
+- Uses pre-built bundles from `dist/teams` for stand alone 1 upload files for all agents and their assest with an orchestrating agent
+- Single text files containing all agent dependencies are in `dist/agents/` - these are unnecessary unless you want to create a web agent that is only a single agent and not a team
+- Created by the web-builder tool for upload to web interfaces
+- Provides complete context in one package
+
+### Template Processing System
+
+BMAD employs a sophisticated template system with three key components:
+
+1. **Template Format** (`utils/template-format.md`): Defines markup language for variable substitution and AI processing directives
+2. **Document Creation** (`tasks/create-doc.md`): Orchestrates template selection and user interaction
+3. **Advanced Elicitation** (`tasks/advanced-elicitation.md`): Provides interactive refinement through structured brainstorming
+
+**Template Features**:
+
+- **Self-contained**: Templates embed both output structure and processing instructions
+- **Variable Substitution**: `{{placeholders}}` for dynamic content
+- **AI Processing Directives**: `[[LLM: instructions]]` for AI-only processing
+- **Interactive Refinement**: Built-in elicitation processes for quality improvement
+
+### Technical Preferences Integration
+
+The `technical-preferences.md` file serves as a persistent technical profile that:
+- Ensures consistency across all agents and projects
+- Eliminates repetitive technology specification
+- Provides personalized recommendations aligned with user preferences
+- Evolves over time with lessons learned
+
+### Build and Delivery Process
+
+The `web-builder.js` tool creates web-ready bundles by:
+1. Reading agent or team definition files
+2. Recursively resolving all dependencies
+3. Concatenating content into single text files with clear separators
+4. Outputting ready-to-upload bundles for web AI interfaces
+
+This architecture enables seamless operation across environments while maintaining the rich, interconnected agent ecosystem that makes BMAD powerful.
+
+## Complete Development Workflow
+
+### Planning Phase (Web UI Recommended)
+
+**Ideal for cost efficiency, especially with Gemini:**
+
+1. **Optional Analysis**: `/analyst` - Market research, competitive analysis
+2. **Project Brief**: Create foundation document (Analyst or user)
+3. **PRD Creation**: `/pm create-doc prd` - Comprehensive product requirements
+4. **Architecture Design**: `/architect create-doc architecture` - Technical foundation
+5. **Validation & Alignment**: `/po` run master checklist to ensure document consistency
+6. **Document Preparation**: Copy final documents to project as `docs/prd.md` and `docs/architecture.md`
+
+#### Example Planning Prompts
+
+**For PRD Creation**:
+```text
+"I want to build a [type] application that [core purpose].
+Help me brainstorm features and create a comprehensive PRD."
+```
+
+**For Architecture Design**:
+```text
+"Based on this PRD, design a scalable technical architecture
+that can handle [specific requirements]."
+```
+
+### Critical Transition: Web UI to IDE
+
+**Once planning is complete, you MUST switch to IDE for development:**
+
+- **Why**: Development workflow requires file operations, real-time project integration, and document sharding
+- **Cost Benefit**: Web UI is more cost-effective for large document creation; IDE is optimized for development tasks
+- **Required Files**: Ensure `docs/prd.md` and `docs/architecture.md` exist in your project
+
+### IDE Development Workflow
+
+**Prerequisites**: Planning documents must exist in `docs/` folder
+
+1. **Document Sharding**: 
+   - `@bmad-master` or `@po` shard `docs/prd.md` to `docs/prd/` folder
+   - If architecture exists, shard to `docs/architecture/` folder
+   - Results in multiple manageable documents and epic files
+
+2. **Verify Sharded Content**:
+   - At least one `epic-n.md` file in `docs/prd/` with stories in development order
+   - Source tree document and coding standards for dev agent reference
+   - Sharded docs for SM agent story creation
+
+**Resulting Folder Structure**:
+- `docs/prd/` - Broken down PRD sections
+- `docs/architecture/` - Broken down architecture sections
+- `docs/stories/` - Generated user stories
+
+3. **Development Cycle** (Sequential, one story at a time):
+
+   **Step 1 - Story Creation**: New chat window → `@sm` → `*create`
+   - SM executes create-next-story task
+   - Review generated story in `docs/stories/`
+   - Update status from "Draft" to "Approved"
+   
+   **Step 2 - Story Implementation**: New chat window → `@dev`
+   - Agent asks which story to implement
+   - Include story file content to save dev agent lookup time
+   - Dev follows tasks/subtasks, marking completion
+   - Dev leaves notes for SM about any deviations
+   - Update status to "Done"
+   
+   **Step 3 - Repeat**: Continue SM → Dev cycle until all epic stories complete
+
+**Important**: Only 1 story in progress at a time, worked sequentially until all epic stories complete.
+
+### Status Tracking Workflow
+
+Stories progress through defined statuses:
+- **Draft** → **Approved** → **InProgress** → **Done**
+
+Each status change requires user verification and approval before proceeding.
+
+### Workflow Types
+
+#### Greenfield Development
+- Business analysis and market research
+- Product requirements and feature definition  
+- System architecture and design
+- Development execution
+- Testing and deployment
+
+#### Brownfield Enhancement
+- Current system analysis
+- Enhancement planning
+- Impact assessment
+- Incremental development
+- Integration testing
+
+## Document Creation Best Practices
+
+### Required File Naming for Framework Integration
+
+- `docs/prd.md` - Product Requirements Document
+- `docs/architecture.md` - System Architecture Document
+
+**Why These Names Matter**:
+- Agents automatically reference these files during development
+- Sharding tasks expect these specific filenames
+- Workflow automation depends on standard naming
+
+### Cost-Effective Document Creation Workflow
+
+**Recommended for Large Documents (PRD, Architecture):**
+
+1. **Use Web UI**: Create documents in web interface for cost efficiency
+2. **Copy Final Output**: Save complete markdown to your project
+3. **Standard Names**: Save as `docs/prd.md` and `docs/architecture.md`
+4. **Switch to IDE**: Use IDE agents for development and smaller documents
+
+### Document Sharding
+
+Templates with Level 2 headings (`##`) can be automatically sharded:
+
+**Original PRD**:
+```markdown
+## Goals and Background Context
+## Requirements  
+## User Interface Design Goals
+## Success Metrics
+```
+
+**After Sharding**:
+- `docs/prd/goals-and-background-context.md`
+- `docs/prd/requirements.md`
+- `docs/prd/user-interface-design-goals.md`
+- `docs/prd/success-metrics.md`
+
+Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic sharding.
+
+## Usage Patterns and Best Practices
+
+### Environment-Specific Usage
+
+**Web UI Best For**:
+- Initial planning and documentation phases
+- Cost-effective large document creation
+- Agent consultation and brainstorming
+- Multi-agent workflows with orchestrator
+
+**IDE Best For**:
+- Active development and implementation
+- File operations and project integration
+- Story management and development cycles
+- Code review and debugging
+
+### Quality Assurance
+
+- Use appropriate agents for specialized tasks
+- Follow Agile ceremonies and review processes
+- Maintain document consistency with PO agent
+- Regular validation with checklists and templates
+
+### Performance Optimization
+
+- Use specific agents vs. `bmad-master` for focused tasks
+- Choose appropriate team size for project needs
+- Leverage technical preferences for consistency
+- Regular context management and cache clearing
+
+## Success Tips
+
+- **Use Gemini for big picture planning** - The team-fullstack bundle provides collaborative expertise
+- **Use bmad-master for document organization** - Sharding creates manageable chunks
+- **Follow the SM → Dev cycle religiously** - This ensures systematic progress
+- **Keep conversations focused** - One agent, one task per conversation
+- **Review everything** - Always review and approve before marking complete
+
+## Getting Help
+
+- **Commands**: Use `/help` in any environment to see available commands
+- **Agent Switching**: Use `/switch agent-name` with orchestrator for role changes
+- **Documentation**: Check `docs/` folder for project-specific context
+- **Community**: Discord and GitHub resources available for support
 ==================== END: data#bmad-kb ====================
 
 ==================== START: utils#workflow-management ====================
@@ -430,7 +810,7 @@ Available workflows for [Team Name]:
 [... etc. ...]
 
 Use /workflow-start {number or id} to begin a workflow.
-```text
+```
 
 ### /workflow-start {workflow-id}
 
@@ -456,7 +836,7 @@ In Progress:
     - Create PRD (John) - awaiting input
 
 Next: Technical Architecture
-```text
+```
 
 ### /workflow-resume
 
@@ -472,7 +852,7 @@ BMad: I see you've completed Discovery and part of Product Planning.
       - UX Strategy with Sally (ux-expert)
 
       Would you like me to load Sally to continue?
-```text
+```
 
 ### /workflow-next
 
@@ -542,7 +922,7 @@ BMad: I see you have a PRD and architecture document. Based on these artifacts,
       - Load Sarah (Product Owner) to validate all artifacts
 
       Would you like to continue with this workflow?
-```text
+```
 
 ## Workflow Context Passing
 
@@ -568,7 +948,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
 

dist/agents/dev.txt

@@ -43,66 +43,50 @@ 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
 agent:
   name: James
   id: dev
   title: Full Stack Developer
   icon: 💻
-  whenToUse: "Use for code implementation, debugging, refactoring, and development best practices"
+  whenToUse: Use for code implementation, debugging, refactoring, and development best practices
-  customization:
+  customization: null
-
+startup:
+  - Announce: Greet the user with your name and role, and inform of the *help command.
+  - CRITICAL: Load .bmad-core/core-config.yml and read devLoadAlwaysFiles list and devDebugLog values
+  - CRITICAL: Load ONLY files specified in devLoadAlwaysFiles. If any missing, inform user but continue
+  - CRITICAL: Do NOT load any story files during startup unless user requested you do
+  - CRITICAL: Do NOT begin development until told to proceed
 persona:
   role: Expert Senior Software Engineer & Implementation Specialist
   style: Extremely concise, pragmatic, detail-oriented, solution-focused
   identity: Expert who implements stories by reading requirements and executing tasks sequentially with comprehensive testing
   focus: Executing story tasks with precision, updating Dev Agent Record sections only, maintaining minimal context overhead
-
 core_principles:
   - CRITICAL: Story-Centric - Story has ALL info. NEVER load PRD/architecture/other docs files unless explicitly directed in dev notes
-  - CRITICAL: Load Standards - MUST load docs/architecture/coding-standards.md into core memory at startup
+  - CRITICAL: Dev Record Only - ONLY update story file Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
-  - CRITICAL: Dev Record Only - ONLY update Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
+  - Strive for Sequential Task Execution - Complete tasks 1-by-1 and mark [x] as completed
-  - Sequential Execution - Complete tasks 1-by-1 in order. Mark [x] before next. No skipping
   - Test-Driven Quality - Write tests alongside code. Task incomplete without passing tests
-  - Debug Log Discipline - Log temp changes to table. Revert after fix. Keep story lean
+  - Debug Log Discipline - Log temp changes to md table in devDebugLog. Revert after fix.
   - Block Only When Critical - HALT for: missing approval/ambiguous reqs/3 failures/missing config
-  - Code Excellence - Clean, secure, maintainable code per coding-standards.md
+  - Code Excellence - Clean, secure, maintainable code per loaded standards
   - Numbered Options - Always use numbered lists when presenting choices
-
-startup:
-  - Announce: Greet the user with your name and role, and inform of the *help command.
-  - CRITICAL: Do NOT load any story files or coding-standards.md during startup
-  - CRITICAL: Do NOT scan docs/stories/ directory automatically
-  - CRITICAL: Do NOT begin any tasks automatically
-  - Wait for user to specify story or ask for story selection
-  - Only load files and begin work when explicitly requested by user
-
 commands:
-  - "*help" - Show commands
+  - help: Show numbered list of the following commands to allow selection
-  - "*chat-mode" - Conversational mode
+  - run-tests: Execute linting and tests
-  - "*run-tests" - Execute linting+tests
+  - debug-log: Show debug entries
-  - "*lint" - Run linting only
+  - complete-story: Finalize to "Review"
-  - "*dod-check" - Run story-dod-checklist
+  - exit: Say goodbye as the Developer, and then abandon inhabiting this persona
-  - "*status" - Show task progress
-  - "*debug-log" - Show debug entries
-  - "*complete-story" - Finalize to "Review"
-  - "*exit" - Leave developer mode
-
 task-execution:
-  flow: "Read task→Implement→Write tests→Pass tests→Update [x]→Next task"
+  flow: Read task→Implement→Write tests→Pass tests→Update [x]→Next task
-
   updates-ONLY:
-    - "Checkboxes: [ ] not started | [-] in progress | [x] complete"
+    - 'Checkboxes: [ ] not started | [-] in progress | [x] complete'
-    - "Debug Log: | Task | File | Change | Reverted? |"
+    - 'Debug Log: | Task | File | Change | Reverted? |'
-    - "Completion Notes: Deviations only, <50 words"
+    - 'Completion Notes: Deviations only, <50 words'
-    - "Change Log: Requirement changes only"
+    - 'Change Log: Requirement changes only'
-
+  blocking: Unapproved deps | Ambiguous after story check | 3 failures | Missing config
-  blocking: "Unapproved deps | Ambiguous after story check | 3 failures | Missing config"
+  done: Code matches reqs + Tests pass + Follows standards + No lint errors
-
+  completion: All [x]→Lint→Tests(100%)→Integration(if noted)→Coverage(80%+)→E2E(if noted)→DoD→Summary→HALT
-  done: "Code matches reqs + Tests pass + Follows standards + No lint errors"
-
-  completion: "All [x]→Lint→Tests(100%)→Integration(if noted)→Coverage(80%+)→E2E(if noted)→DoD→Summary→HALT"
-
 dependencies:
   tasks:
     - execute-checklist

dist/agents/pm.txt

@@ -43,7 +43,7 @@ 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
@@ -73,10 +73,10 @@ persona:
 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'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - (Default) Deep conversation with advanced-elicitation'
+  - chat-mode: (Default) Deep conversation with advanced-elicitation
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - create-doc {template}: Create doc (no template = show available templates)
-  - '*exit" - Say goodbye as the PM, and then abandon inhabiting this persona'
+  - exit: Say goodbye as the PM, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - create-doc
@@ -1084,7 +1084,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
 
@@ -1148,6 +1148,8 @@ Document sharded successfully:
 ==================== START: templates#prd-tmpl ====================
 # {{Project Name}} Product Requirements Document (PRD)
 
+[[LLM: The default path and filename unless specified is docs/prd.md]]
+
 [[LLM: If available, review any provided document or ask if any are optionally available: Project Brief]]
 
 ## Goals and Background Context
@@ -1351,6 +1353,8 @@ so that {{benefit}}.
 ==================== START: templates#brownfield-prd-tmpl ====================
 # {{Project Name}} Brownfield Enhancement PRD
 
+[[LLM: The default path and filename unless specified is docs/prd.md]]
+
 [[LLM: IMPORTANT - SCOPE ASSESSMENT REQUIRED:
 
 This PRD is for SIGNIFICANT enhancements to existing projects that require comprehensive planning and multiple stories. Before proceeding:

dist/agents/po.txt

@@ -43,7 +43,7 @@ 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
@@ -75,15 +75,15 @@ persona:
 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'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - (Default) Product Owner consultation with advanced-elicitation'
+  - chat-mode: (Default) Product Owner consultation with advanced-elicitation
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - create-doc {template}: Create doc (no template = show available templates)
-  - '*execute-checklist {checklist}" - Run validation checklist (default->po-master-checklist)'
+  - execute-checklist {checklist}: Run validation checklist (default->po-master-checklist)
-  - '*shard-doc {document}" - Break down document into actionable parts'
+  - shard-doc {document}: Break down document into actionable parts
-  - '*correct-course" - Analyze and suggest project course corrections'
+  - correct-course: Analyze and suggest project course corrections
-  - '*create-epic" - Create epic for brownfield projects (task brownfield-create-epic)'
+  - create-epic: Create epic for brownfield projects (task brownfield-create-epic)
-  - '*create-story" - Create user story from requirements (task brownfield-create-story)'
+  - create-story: Create user story from requirements (task brownfield-create-story)
-  - '*exit" - Say Goodbye, You are no longer this Agent'
+  - exit: Say goodbye as the Product Owner, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - execute-checklist
@@ -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
 

dist/agents/qa.txt

@@ -75,10 +75,10 @@ persona:
 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'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - (Default) QA consultation with advanced-elicitation for test strategy'
+  - chat-mode: (Default) QA consultation with advanced-elicitation for test strategy
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - create-doc {template}: Create doc (no template = show available templates)
-  - '*exit" - Say goodbye as the QA Test Architect, and then abandon inhabiting this persona'
+  - exit: Say goodbye as the QA Test Architect, and then abandon inhabiting this persona
 dependencies:
   data:
     - technical-preferences

dist/agents/sm.txt

@@ -46,7 +46,6 @@ CRITICAL: Read the full YML, start activation to alter your state of being, foll
 ```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:
@@ -62,31 +61,25 @@ persona:
   identity: Story creation expert who prepares detailed, actionable stories for AI developers
   focus: Creating crystal-clear stories that dumb AI agents can implement without confusion
   core_principles:
-    - Task Adherence - Rigorously follow create-next-story procedures
+    - Rigorously follow `create-next-story` procedure to generate the detailed user story
-    - Checklist-Driven Validation - Apply story-draft-checklist meticulously
+    - Will ensure all information comes from the PRD and Architecture to guide the dumb dev agent
-    - Clarity for Developer Handoff - Stories must be immediately actionable
+    - You are NOT allowed to implement stories or modify code EVER!
-    - Focus on One Story at a Time - Complete one before starting next
-    - Numbered Options Protocol - Always use numbered lists for selections
 startup:
-  - Greet the user with your name and role, and inform of the *help command.
+  - Greet the user with your name and role, and inform of the *help command and then HALT to await instruction if not given already.
-  - CRITICAL: Do NOT automatically execute create-next-story tasks during startup
-  - CRITICAL: Do NOT create or modify any files during startup
   - Offer to help with story preparation but wait for explicit user confirmation
   - Only execute tasks when user explicitly requests them
-  - 'CRITICAL RULE: You are ONLY allowed to create/modify story files - NEVER implement! If asked to implement, tell user they MUST switch to Dev Agent'
 commands:
-  - '*help" - Show: numbered list of the following commands to allow selection'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - Conversational mode with advanced-elicitation for advice'
+  - chat-mode: Conversational mode with advanced-elicitation for advice
-  - '*create" - Execute all steps in Create Next Story Task document'
+  - create|draft: Execute create-next-story
-  - '*pivot" - Run correct-course task (ensure no story already created first)'
+  - pivot: Execute `correct-course` task
-  - '*checklist {checklist}" - Show numbered list of checklists, execute selection'
+  - checklist {checklist}: Show numbered list of checklists, execute selection
-  - '*doc-shard {PRD|Architecture|Other}" - Execute shard-doc task'
+  - exit: Say goodbye as the Scrum Master, and then abandon inhabiting this persona
-  - '*index-docs" - Update documentation index in /docs/index.md'
-  - '*exit" - Say goodbye as the Scrum Master, and then abandon inhabiting this persona'
 dependencies:
   tasks:
     - create-next-story
     - execute-checklist
+    - course-correct
   templates:
     - story-tmpl
   checklists:
@@ -103,45 +96,42 @@ dependencies:
 
 To identify the next logical story based on project progress and epic definitions, and then to prepare a comprehensive, self-contained, and actionable story file using the `Story Template`. This task ensures the story is enriched with all necessary technical context, requirements, and acceptance criteria, making it ready for efficient implementation by a Developer Agent with minimal need for additional research.
 
-## Inputs for this Task
-
-- Access to the project's documentation repository, specifically:
-  - `docs/index.md` (hereafter "Index Doc")
-  - All Epic files - located in one of these locations:
-    - Primary: `docs/prd/epic-{n}-{description}.md` (e.g., `epic-1-foundation-core-infrastructure.md`)
-    - Secondary: `docs/epics/epic-{n}-{description}.md`
-    - User-specified location if not found in above paths
-  - Existing story files in `docs/stories/`
-  - Main PRD (hereafter "PRD Doc")
-  - Main Architecture Document (hereafter "Main Arch Doc")
-  - Frontend Architecture Document (hereafter "Frontend Arch Doc," if relevant)
-  - Project Structure Guide (`docs/project-structure.md`)
-  - Operational Guidelines Document (`docs/operational-guidelines.md`)
-  - Technology Stack Document (`docs/tech-stack.md`)
-  - Data Models Document (as referenced in Index Doc)
-  - API Reference Document (as referenced in Index Doc)
-  - UI/UX Specifications, Style Guides, Component Guides (if relevant, as referenced in Index Doc)
-- The `bmad-core/templates/story-tmpl.md` (hereafter "Story Template")
-- The `bmad-core/checklists/story-draft-checklist.md` (hereafter "Story Draft Checklist")
-- User confirmation to proceed with story identification and, if needed, to override warnings about incomplete prerequisite stories.
-
 ## Task Execution Instructions
 
+### 0. Load Core Configuration
+
+[[LLM: CRITICAL - This MUST be your first step]]
+
+- Load `.bmad-core/core-config.yml` from the project root
+- If the file does not exist:
+  - HALT and inform the user: "core-config.yml not found. This file is required for story creation. You can:
+    1. Copy it from GITHUB BMAD-METHOD/bmad-core/core-config.yml and configure it for your project
+    2. Run the BMAD installer against your project to upgrade and add the file automatically
+    Please add and configure core-config.yml before proceeding."
+- Extract the following key configurations:
+  - `dev-story-location`: Where to save story files
+  - `prd.prdSharded`: Whether PRD is sharded or monolithic
+  - `prd.prd-file`: Location of monolithic PRD (if not sharded)
+  - `prd.prdShardedLocation`: Location of sharded epic files
+  - `prd.epicFilePattern`: Pattern for epic files (e.g., `epic-{n}*.md`)
+  - `architecture.architectureVersion`: Architecture document version
+  - `architecture.architectureSharded`: Whether architecture is sharded
+  - `architecture.architecture-file`: Location of monolithic architecture
+  - `architecture.architectureShardedLocation`: Location of sharded architecture files
+
 ### 1. Identify Next Story for Preparation
 
 #### 1.1 Locate Epic Files
 
-- First, determine where epic files are located:
+- Based on `prdSharded` from config:
-  - Check `docs/prd/` for files matching pattern `epic-{n}-*.md`
+  - **If `prdSharded: true`**: Look for epic files in `prdShardedLocation` using `epicFilePattern`
-  - If not found, check `docs/epics/` for files matching pattern `epic-{n}-*.md`
+  - **If `prdSharded: false`**: Load the full PRD from `prd-file` and extract epics from section headings (## Epic N or ### Epic N)
-  - If still not found, ask user: "Unable to locate epic files. Please specify the path where epic files are stored."
-- Note: Epic files follow naming convention `epic-{n}-{description}.md` (e.g., `epic-1-foundation-core-infrastructure.md`)
 
 #### 1.2 Review Existing Stories
 
-- Review `docs/stories/` to find the highest-numbered story file.
+- Check `dev-story-location` from config (e.g., `docs/stories/`) for existing story files
+- If the directory exists and has at least 1 file, find the highest-numbered story file.
 - **If a highest story file exists (`{lastEpicNum}.{lastStoryNum}.story.md`):**
-
   - Verify its `Status` is 'Done' (or equivalent).
   - If not 'Done', present an alert to the user:
 
@@ -159,17 +149,17 @@ To identify the next logical story based on project progress and epic definition
     ```
 
   - Proceed only if user selects option 3 (Override) or if the last story was 'Done'.
-  - If proceeding: Look for the Epic File for `{lastEpicNum}` (e.g., `epic-{lastEpicNum}-*.md`) and check for a story numbered `{lastStoryNum + 1}`. If it exists and its prerequisites (per Epic File) are met, this is the next story.
+  - If proceeding: Look for the Epic File for `{lastEpicNum}` (e.g., `epic-{lastEpicNum}*.md`) and check for a story numbered `{lastStoryNum + 1}`. If it exists and its prerequisites (per Epic File) are met, this is the next story.
-  - Else (story not found or prerequisites not met): The next story is the first story in the next Epic File (e.g., look for `epic-{lastEpicNum + 1}-*.md`, then `epic-{lastEpicNum + 2}-*.md`, etc.) whose prerequisites are met.
+  - Else (story not found or prerequisites not met): The next story is the first story in the next Epic File (e.g., look for `epic-{lastEpicNum + 1}*.md`, then `epic-{lastEpicNum + 2}*.md`, etc.) whose prerequisites are met.
 
 - **If no story files exist in `docs/stories/`:**
   - The next story is the first story in the first epic file (look for `epic-1-*.md`, then `epic-2-*.md`, etc.) whose prerequisites are met.
 - If no suitable story with met prerequisites is found, report to the user that story creation is blocked, specifying what prerequisites are pending. HALT task.
 - Announce the identified story to the user: "Identified next story for preparation: {epicNum}.{storyNum} - {Story Title}".
 
-### 2. Gather Core Story Requirements (from Epic File)
+### 2. Gather Core Story Requirements (from Epic)
 
-- For the identified story, open its parent Epic File (e.g., `epic-{epicNum}-*.md` from the location identified in step 1.1).
+- For the identified story, review its parent Epic (e.g., `epic-{epicNum}*.md` from the location identified in step 1.1).
 - Extract: Exact Title, full Goal/User Story statement, initial list of Requirements, all Acceptance Criteria (ACs), and any predefined high-level Tasks.
 - Keep a record of this original epic-defined scope for later deviation analysis.
 
@@ -178,7 +168,7 @@ To identify the next logical story based on project progress and epic definition
 [[LLM: This step is CRITICAL for continuity and learning from implementation experience]]
 
 - If this is not the first story (i.e., previous story exists):
-  - Read the previous story file: `docs/stories/{prevEpicNum}.{prevStoryNum}.story.md`
+  - Read the previous sequential story from `docs/stories`
   - Pay special attention to:
     - Dev Agent Record sections (especially Completion Notes and Debug Log References)
     - Any deviations from planned implementation
@@ -187,18 +177,30 @@ To identify the next logical story based on project progress and epic definition
     - Any "lessons learned" or notes for future stories
   - Extract relevant insights that might inform the current story's preparation
 
-### 4. Gather & Synthesize Architecture Context from Sharded Docs
+### 4. Gather & Synthesize Architecture Context
 
-[[LLM: CRITICAL - You MUST gather technical details from the sharded architecture documents. NEVER make up technical details not found in these documents.]]
+[[LLM: CRITICAL - You MUST gather technical details from the architecture documents. NEVER make up technical details not found in these documents.]]
 
-#### 4.1 Start with Architecture Index
+#### 4.1 Determine Architecture Document Strategy
 
-- Read `docs/architecture/index.md` to understand the full scope of available documentation
+Based on configuration loaded in Step 0:
-- Identify which sharded documents are most relevant to the current story
 
-#### 4.2 Recommended Reading Order Based on Story Type
+- **If `architectureVersion: v4` and `architectureSharded: true`**:
+  - Read `{architectureShardedLocation}/index.md` to understand available documentation
+  - Follow the structured reading order in section 4.2 below
+  
+- **If `architectureVersion: v4` and `architectureSharded: false`**:
+  - Load the monolithic architecture from `architecture-file`
+  - Extract relevant sections based on v4 structure (tech stack, project structure, etc.)
+  
+- **If `architectureVersion` is NOT v4**:
+  - Inform user: "Architecture document is not v4 format. Will use best judgment to find relevant information."
+  - If `architectureSharded: true`: Search sharded files by filename relevance
+  - If `architectureSharded: false`: Search within monolithic `architecture-file` for relevant sections
 
-[[LLM: Read documents in this order, but ALWAYS verify relevance to the specific story. Skip irrelevant sections but NEVER skip documents that contain information needed for the story.]]
+#### 4.2 Recommended Reading Order Based on Story Type (v4 Sharded Only)
+
+[[LLM: Use this structured approach ONLY for v4 sharded architecture. For other versions, use best judgment based on file names and content.]]
 
 **For ALL Stories:**
 
@@ -207,9 +209,18 @@ To identify the next logical story based on project progress and epic definition
 3. `docs/architecture/coding-standards.md` - Ensure dev follows project conventions
 4. `docs/architecture/testing-strategy.md` - Include testing requirements in tasks
 
-**For Backend/API Stories, additionally read:** 5. `docs/architecture/data-models.md` - Data structures and validation rules 6. `docs/architecture/database-schema.md` - Database design and relationships 7. `docs/architecture/backend-architecture.md` - Service patterns and structure 8. `docs/architecture/rest-api-spec.md` - API endpoint specifications 9. `docs/architecture/external-apis.md` - Third-party integrations (if relevant)
+**For Backend/API Stories, additionally read:**
+5. `docs/architecture/data-models.md` - Data structures and validation rules
+6. `docs/architecture/database-schema.md` - Database design and relationships
+7. `docs/architecture/backend-architecture.md` - Service patterns and structure
+8. `docs/architecture/rest-api-spec.md` - API endpoint specifications
+9. `docs/architecture/external-apis.md` - Third-party integrations (if relevant)
 
-**For Frontend/UI Stories, additionally read:** 5. `docs/architecture/frontend-architecture.md` - Component structure and patterns 6. `docs/architecture/components.md` - Specific component designs 7. `docs/architecture/core-workflows.md` - User interaction flows 8. `docs/architecture/data-models.md` - Frontend data handling
+**For Frontend/UI Stories, additionally read:**
+5. `docs/architecture/frontend-architecture.md` - Component structure and patterns
+6. `docs/architecture/components.md` - Specific component designs
+7. `docs/architecture/core-workflows.md` - User interaction flows
+8. `docs/architecture/data-models.md` - Frontend data handling
 
 **For Full-Stack Stories:**
 
@@ -242,7 +253,7 @@ Format references as: `[Source: architecture/{filename}.md#{section}]`
 
 ### 6. Populate Story Template with Full Context
 
-- Create a new story file: `docs/stories/{epicNum}.{storyNum}.story.md`.
+- Create a new story file: `{dev-story-location}/{epicNum}.{storyNum}.story.md` (using location from config).
 - Use the Story Template to structure the file.
 - Fill in:
   - Story `{EpicNum}.{StoryNum}: {Short Title Copied from Epic File}`
@@ -289,7 +300,7 @@ Format references as: `[Source: architecture/{filename}.md#{section}]`
 - Verify all source references are included for technical details
 - Ensure tasks align with both epic requirements and architecture constraints
 - Update status to "Draft"
-- Save the story file to `docs/stories/{epicNum}.{storyNum}.story.md`
+- Save the story file to `{dev-story-location}/{epicNum}.{storyNum}.story.md` (using location from config)
 
 ### 9. Report Completion
 

dist/agents/ux-expert.txt

@@ -79,13 +79,13 @@ 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'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - (Default) UX consultation with advanced-elicitation for design decisions'
+  - chat-mode: (Default) UX consultation with advanced-elicitation for design decisions
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - create-doc {template}: Create doc (no template = show available templates)
-  - '*generate-ui-prompt" - Create AI frontend generation prompt'
+  - generate-ui-prompt: Create AI frontend generation prompt
-  - '*research {topic}" - Generate deep research prompt for UX investigation'
+  - research {topic}: Generate deep research prompt for UX investigation
-  - '*execute-checklist {checklist}" - Run design validation checklist'
+  - execute-checklist {checklist}: Run design validation checklist
-  - '*exit" - Say goodbye as the UX Expert, and then abandon inhabiting this persona'
+  - exit: Say goodbye as the UX Expert, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - generate-ai-frontend-prompt
@@ -639,6 +639,8 @@ The LLM will:
 ==================== START: templates#front-end-spec-tmpl ====================
 # {{Project Name}} UI/UX Specification
 
+[[LLM: The default path and filename unless specified is docs/front-end-spec.md]]
+
 [[LLM: Review provided documents including Project Brief, PRD, and any user research to gather context. Focus on understanding user needs, pain points, and desired outcomes before beginning the specification.]]
 
 ## Introduction
@@ -715,7 +717,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 ```mermaid
 {{sitemap_diagram}}
-```text
+```
 
 @{example: sitemap}
 

dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-developer.txt

@@ -107,6 +107,106 @@ dependencies:
 ```
 ==================== END: agents#game-developer ====================
 
+==================== START: tasks#execute-checklist ====================
+# 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.
+
+## Context
+
+The BMAD Method uses various checklists to ensure quality and completeness of different artifacts. Each checklist contains embedded prompts and instructions to guide the LLM through thorough validation and advanced elicitation. The checklists automatically identify their required artifacts and guide the validation process.
+
+## 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 bmad-core/checklists folder to select the appropriate one to run.
+
+## 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
+     - Load the appropriate checklist from bmad-core/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
+   - Confirm if they want to work through the checklist:
+     - Section by section (interactive mode - very time consuming)
+     - 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
+     - Check each item against the relevant documentation or artifacts as appropriate
+     - Present summary of findings for that section, highlighting warnings, errors and non applicable items (rationale for non-applicability).
+     - 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
+
+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
+   - Aside from this, follow all checklist llm instructions
+   - Mark items as:
+     - ✅ PASS: Requirement clearly met
+     - ❌ FAIL: Requirement not met or insufficient coverage
+     - ⚠️ PARTIAL: Some aspects covered but needs improvement
+     - N/A: Not applicable to this case
+
+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
+   - In interactive mode, discuss findings with user
+   - Document any user decisions or explanations
+
+6. **Final Report**
+
+   Prepare a summary that includes:
+
+   - Overall checklist completion status
+   - Pass rates by section
+   - List of failed items with context
+   - Specific recommendations for improvement
+   - Any sections or items marked as N/A with justification
+
+## Checklist Execution Methodology
+
+Each checklist now contains embedded LLM prompts and instructions that will:
+
+1. **Guide thorough thinking** - Prompts ensure deep analysis of each section
+2. **Request specific artifacts** - Clear instructions on what documents/access is needed
+3. **Provide contextual guidance** - Section-specific prompts for better validation
+4. **Generate comprehensive reports** - Final summary with detailed findings
+
+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 ====================
+
 ==================== START: templates#game-architecture-tmpl ====================
 # {{Game Title}} Game Architecture Document
 
@@ -190,7 +290,7 @@ This architecture is designed to support the gameplay mechanics defined in the G
 │   ├── stories/         # Development stories
 │   └── architecture/    # Technical docs
 └── dist/                # Built game files
-```text
+```
 
 ### Module Organization
 
@@ -475,7 +575,7 @@ const gameConfig: Phaser.Types.Core.GameConfig = {
     },
     // Additional configuration...
 };
-```text
+```
 
 ### Game Balance Configuration
 
@@ -676,6 +776,7 @@ export const GameBalance = {
 ## Story Completeness
 
 ### Basic Story Elements
+
 - [ ] **Story Title** - Clear, descriptive title that identifies the feature
 - [ ] **Epic Assignment** - Story is properly assigned to relevant epic
 - [ ] **Priority Level** - Appropriate priority assigned (High/Medium/Low)
@@ -683,6 +784,7 @@ export const GameBalance = {
 - [ ] **Description** - Clear, concise description of what needs to be implemented
 
 ### Game Design Alignment
+
 - [ ] **GDD Reference** - Specific Game Design Document section referenced
 - [ ] **Game Mechanic Context** - Clear connection to game mechanics defined in GDD
 - [ ] **Player Experience Goal** - Describes the intended player experience
@@ -692,6 +794,7 @@ export const GameBalance = {
 ## Technical Specifications
 
 ### Architecture Compliance
+
 - [ ] **File Organization** - Follows game architecture document structure
 - [ ] **Class Definitions** - TypeScript interfaces and classes are properly defined
 - [ ] **Integration Points** - Clear specification of how feature integrates with existing systems
@@ -699,6 +802,7 @@ export const GameBalance = {
 - [ ] **Dependencies** - All system dependencies clearly identified
 
 ### Phaser 3 Requirements
+
 - [ ] **Scene Integration** - Specifies which scenes are affected and how
 - [ ] **Game Object Usage** - Proper use of Phaser 3 game objects and components
 - [ ] **Physics Integration** - Physics requirements specified if applicable
@@ -706,6 +810,7 @@ export const GameBalance = {
 - [ ] **Performance Considerations** - 60 FPS target and optimization requirements
 
 ### Code Quality Standards
+
 - [ ] **TypeScript Strict Mode** - All code must comply with strict TypeScript
 - [ ] **Error Handling** - Error scenarios and handling requirements specified
 - [ ] **Memory Management** - Object pooling and cleanup requirements where needed
@@ -715,6 +820,7 @@ export const GameBalance = {
 ## Implementation Readiness
 
 ### Acceptance Criteria
+
 - [ ] **Functional Requirements** - All functional acceptance criteria are specific and testable
 - [ ] **Technical Requirements** - Technical acceptance criteria are complete and verifiable
 - [ ] **Game Design Requirements** - Game-specific requirements match GDD specifications
@@ -722,6 +828,7 @@ export const GameBalance = {
 - [ ] **Completeness** - No acceptance criteria are vague or unmeasurable
 
 ### Implementation Tasks
+
 - [ ] **Task Breakdown** - Story broken into specific, ordered implementation tasks
 - [ ] **Task Scope** - Each task is completable in 1-4 hours
 - [ ] **Task Clarity** - Each task has clear, actionable instructions
@@ -729,6 +836,7 @@ export const GameBalance = {
 - [ ] **Development Flow** - Tasks follow logical implementation order
 
 ### Dependencies
+
 - [ ] **Story Dependencies** - All prerequisite stories identified with IDs
 - [ ] **Technical Dependencies** - Required systems and files identified
 - [ ] **Asset Dependencies** - All needed assets specified with locations
@@ -738,6 +846,7 @@ export const GameBalance = {
 ## Testing Requirements
 
 ### Test Coverage
+
 - [ ] **Unit Test Requirements** - Specific unit test files and scenarios defined
 - [ ] **Integration Test Cases** - Integration testing with other game systems specified
 - [ ] **Manual Test Cases** - Game-specific manual testing procedures defined
@@ -745,6 +854,7 @@ export const GameBalance = {
 - [ ] **Edge Case Testing** - Edge cases and error conditions covered
 
 ### Test Implementation
+
 - [ ] **Test File Paths** - Exact test file locations specified
 - [ ] **Test Scenarios** - All test scenarios are complete and executable
 - [ ] **Expected Behaviors** - Clear expected outcomes for all tests defined
@@ -754,6 +864,7 @@ export const GameBalance = {
 ## Game-Specific Quality
 
 ### Gameplay Implementation
+
 - [ ] **Mechanic Accuracy** - Implementation matches GDD mechanic specifications
 - [ ] **Player Controls** - Input handling requirements are complete
 - [ ] **Game Feel** - Requirements for juice, feedback, and responsiveness specified
@@ -761,6 +872,7 @@ export const GameBalance = {
 - [ ] **State Management** - Game state changes and persistence requirements defined
 
 ### User Experience
+
 - [ ] **UI Requirements** - User interface elements and behaviors specified
 - [ ] **Audio Integration** - Sound effect and music requirements defined
 - [ ] **Visual Feedback** - Animation and visual effect requirements specified
@@ -768,6 +880,7 @@ export const GameBalance = {
 - [ ] **Error Recovery** - User-facing error handling and recovery specified
 
 ### Performance Optimization
+
 - [ ] **Frame Rate Targets** - Specific FPS requirements for different platforms
 - [ ] **Memory Usage** - Memory consumption limits and monitoring requirements
 - [ ] **Asset Optimization** - Texture, audio, and data optimization requirements
@@ -777,6 +890,7 @@ export const GameBalance = {
 ## Documentation and Communication
 
 ### Story Documentation
+
 - [ ] **Implementation Notes** - Additional context and implementation guidance provided
 - [ ] **Design Decisions** - Key design choices documented with rationale
 - [ ] **Future Considerations** - Potential future enhancements or modifications noted
@@ -784,6 +898,7 @@ export const GameBalance = {
 - [ ] **Reference Materials** - Links to relevant GDD sections and architecture docs
 
 ### Developer Handoff
+
 - [ ] **Immediate Actionability** - Developer can start implementation without additional questions
 - [ ] **Complete Context** - All necessary context provided within the story
 - [ ] **Clear Boundaries** - What is and isn't included in the story scope is clear
@@ -793,6 +908,7 @@ export const GameBalance = {
 ## Final Validation
 
 ### Story Readiness
+
 - [ ] **No Ambiguity** - No sections require interpretation or additional design decisions
 - [ ] **Technical Completeness** - All technical requirements are specified and actionable
 - [ ] **Scope Appropriateness** - Story scope matches assigned story points
@@ -800,6 +916,7 @@ export const GameBalance = {
 - [ ] **Review Completion** - Story has been reviewed for completeness and accuracy
 
 ### Implementation Preparedness
+
 - [ ] **Environment Ready** - Development environment requirements specified
 - [ ] **Resources Available** - All required resources (assets, docs, dependencies) accessible
 - [ ] **Testing Prepared** - Testing environment and data requirements specified
@@ -828,6 +945,7 @@ This document establishes coding standards, architectural patterns, and developm
 ### Strict Mode Configuration
 
 **Required tsconfig.json settings:**
+
 ```json
 {
   "compilerOptions": {
@@ -841,11 +959,12 @@ This document establishes coding standards, architectural patterns, and developm
     "exactOptionalPropertyTypes": true
   }
 }
-```text
+```
 
 ### Type Definitions
 
 **Game Object Interfaces:**
+
 ```typescript
 // Core game entity interface
 interface GameEntity {
@@ -869,9 +988,10 @@ interface GameSystem {
   update(delta: number): void;
   shutdown(): void;
 }
-```text
+```
 
 **Scene Data Interfaces:**
+
 ```typescript
 // Scene transition data
 interface SceneData {
@@ -889,28 +1009,32 @@ interface GameState {
 interface GameSettings {
   musicVolume: number;
   sfxVolume: number;
-  difficulty: 'easy' | 'normal' | 'hard';
+  difficulty: "easy" | "normal" | "hard";
   controls: ControlScheme;
 }
-```text
+```
 
 ### Naming Conventions
 
 **Classes and Interfaces:**
+
 - PascalCase for classes: `PlayerSprite`, `GameManager`, `AudioSystem`
 - PascalCase with 'I' prefix for interfaces: `IGameEntity`, `IPlayerController`
 - Descriptive names that indicate purpose: `CollisionManager` not `CM`
 
 **Methods and Variables:**
+
 - camelCase for methods and variables: `updatePosition()`, `playerSpeed`
 - Descriptive names: `calculateDamage()` not `calcDmg()`
 - Boolean variables with is/has/can prefix: `isActive`, `hasCollision`, `canMove`
 
 **Constants:**
+
 - UPPER_SNAKE_CASE for constants: `MAX_PLAYER_SPEED`, `DEFAULT_VOLUME`
 - Group related constants in enums or const objects
 
 **Files and Directories:**
+
 - kebab-case for file names: `player-controller.ts`, `audio-manager.ts`
 - PascalCase for scene files: `MenuScene.ts`, `GameScene.ts`
 
@@ -919,88 +1043,91 @@ interface GameSettings {
 ### Scene Organization
 
 **Scene Lifecycle Management:**
+
 ```typescript
 class GameScene extends Phaser.Scene {
   private gameManager!: GameManager;
   private inputManager!: InputManager;
-  
+
   constructor() {
-    super({ key: 'GameScene' });
+    super({ key: "GameScene" });
   }
-  
+
   preload(): void {
     // Load only scene-specific assets
-    this.load.image('player', 'assets/player.png');
+    this.load.image("player", "assets/player.png");
   }
-  
+
   create(data: SceneData): void {
     // Initialize game systems
     this.gameManager = new GameManager(this);
     this.inputManager = new InputManager(this);
-    
+
     // Set up scene-specific logic
     this.setupGameObjects();
     this.setupEventListeners();
   }
-  
+
   update(time: number, delta: number): void {
     // Update all game systems
     this.gameManager.update(delta);
     this.inputManager.update(delta);
   }
-  
+
   shutdown(): void {
     // Clean up resources
     this.gameManager.destroy();
     this.inputManager.destroy();
-    
+
     // Remove event listeners
-    this.events.off('*');
+    this.events.off("*");
   }
 }
 ```
 
 **Scene Transitions:**
+
 ```typescript
 // Proper scene transitions with data
-this.scene.start('NextScene', {
+this.scene.start("NextScene", {
   playerScore: this.playerScore,
-  currentLevel: this.currentLevel + 1
+  currentLevel: this.currentLevel + 1,
 });
 
 // Scene overlays for UI
-this.scene.launch('PauseMenuScene');
+this.scene.launch("PauseMenuScene");
 this.scene.pause();
-```text
+```
 
 ### Game Object Patterns
 
 **Component-Based Architecture:**
+
 ```typescript
 // Base game entity
 abstract class GameEntity extends Phaser.GameObjects.Sprite {
   protected components: Map<string, GameComponent> = new Map();
-  
+
   constructor(scene: Phaser.Scene, x: number, y: number, texture: string) {
     super(scene, x, y, texture);
     scene.add.existing(this);
   }
-  
+
   addComponent<T extends GameComponent>(component: T): T {
     this.components.set(component.name, component);
     return component;
   }
-  
+
   getComponent<T extends GameComponent>(name: string): T | undefined {
     return this.components.get(name) as T;
   }
-  
+
   update(delta: number): void {
-    this.components.forEach(component => component.update(delta));
+    this.components.forEach((component) => component.update(delta));
   }
-  
+
   destroy(): void {
-    this.components.forEach(component => component.destroy());
+    this.components.forEach((component) => component.destroy());
     this.components.clear();
     super.destroy();
   }
@@ -1010,65 +1137,67 @@ abstract class GameEntity extends Phaser.GameObjects.Sprite {
 class Player extends GameEntity {
   private movement!: MovementComponent;
   private health!: HealthComponent;
-  
+
   constructor(scene: Phaser.Scene, x: number, y: number) {
-    super(scene, x, y, 'player');
+    super(scene, x, y, "player");
-    
+
     this.movement = this.addComponent(new MovementComponent(this));
     this.health = this.addComponent(new HealthComponent(this, 100));
   }
 }
-```text
+```
 
 ### System Management
 
 **Singleton Managers:**
+
 ```typescript
 class GameManager {
   private static instance: GameManager;
   private scene: Phaser.Scene;
   private gameState: GameState;
-  
+
   constructor(scene: Phaser.Scene) {
     if (GameManager.instance) {
-      throw new Error('GameManager already exists!');
+      throw new Error("GameManager already exists!");
     }
-    
+
     this.scene = scene;
     this.gameState = this.loadGameState();
     GameManager.instance = this;
   }
-  
+
   static getInstance(): GameManager {
     if (!GameManager.instance) {
-      throw new Error('GameManager not initialized!');
+      throw new Error("GameManager not initialized!");
     }
     return GameManager.instance;
   }
-  
+
   update(delta: number): void {
     // Update game logic
   }
-  
+
   destroy(): void {
     GameManager.instance = null!;
   }
 }
-```text
+```
 
 ## Performance Optimization
 
 ### Object Pooling
 
 **Required for High-Frequency Objects:**
+
 ```typescript
 class BulletPool {
   private pool: Bullet[] = [];
   private scene: Phaser.Scene;
-  
+
   constructor(scene: Phaser.Scene, initialSize: number = 50) {
     this.scene = scene;
-    
+
     // Pre-create bullets
     for (let i = 0; i < initialSize; i++) {
       const bullet = new Bullet(scene, 0, 0);
@@ -1077,20 +1206,20 @@ class BulletPool {
       this.pool.push(bullet);
     }
   }
-  
+
   getBullet(): Bullet | null {
-    const bullet = this.pool.find(b => !b.active);
+    const bullet = this.pool.find((b) => !b.active);
     if (bullet) {
       bullet.setActive(true);
       bullet.setVisible(true);
       return bullet;
     }
-    
+
     // Pool exhausted - create new bullet
-    console.warn('Bullet pool exhausted, creating new bullet');
+    console.warn("Bullet pool exhausted, creating new bullet");
     return new Bullet(this.scene, 0, 0);
   }
-  
+
   releaseBullet(bullet: Bullet): void {
     bullet.setActive(false);
     bullet.setVisible(false);
@@ -1102,45 +1231,47 @@ class BulletPool {
 ### Frame Rate Optimization
 
 **Performance Monitoring:**
+
 ```typescript
 class PerformanceMonitor {
   private frameCount: number = 0;
   private lastTime: number = 0;
   private frameRate: number = 60;
-  
+
   update(time: number): void {
     this.frameCount++;
-    
+
     if (time - this.lastTime >= 1000) {
       this.frameRate = this.frameCount;
       this.frameCount = 0;
       this.lastTime = time;
-      
+
       if (this.frameRate < 55) {
         console.warn(`Low frame rate detected: ${this.frameRate} FPS`);
         this.optimizePerformance();
       }
     }
   }
-  
+
   private optimizePerformance(): void {
     // Reduce particle counts, disable effects, etc.
   }
 }
-```text
+```
 
 **Update Loop Optimization:**
+
 ```typescript
 // Avoid expensive operations in update loops
 class GameScene extends Phaser.Scene {
   private updateTimer: number = 0;
   private readonly UPDATE_INTERVAL = 100; // ms
-  
+
   update(time: number, delta: number): void {
     // High-frequency updates (every frame)
     this.updatePlayer(delta);
     this.updatePhysics(delta);
-    
+
     // Low-frequency updates (10 times per second)
     this.updateTimer += delta;
     if (this.updateTimer >= this.UPDATE_INTERVAL) {
@@ -1150,13 +1281,14 @@ class GameScene extends Phaser.Scene {
     }
   }
 }
-```text
+```
 
 ## Input Handling
 
 ### Cross-Platform Input
 
 **Input Abstraction:**
+
 ```typescript
 interface InputState {
   moveLeft: boolean;
@@ -1172,26 +1304,26 @@ class InputManager {
     moveRight: false,
     jump: false,
     action: false,
-    pause: false
+    pause: false,
   };
-  
+
   private keys!: { [key: string]: Phaser.Input.Keyboard.Key };
   private pointer!: Phaser.Input.Pointer;
-  
+
   constructor(private scene: Phaser.Scene) {
     this.setupKeyboard();
     this.setupTouch();
   }
-  
+
   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 {
-    this.scene.input.on('pointerdown', this.handlePointerDown, this);
+    this.scene.input.on("pointerdown", this.handlePointerDown, this);
-    this.scene.input.on('pointerup', this.handlePointerUp, this);
+    this.scene.input.on("pointerup", this.handlePointerUp, this);
   }
-  
+
   update(): void {
     // Update input state from multiple sources
     this.inputState.moveLeft = this.keys.A.isDown || this.keys.LEFT.isDown;
@@ -1199,42 +1331,43 @@ class InputManager {
     this.inputState.jump = Phaser.Input.Keyboard.JustDown(this.keys.SPACE);
     // ... handle touch input
   }
-  
+
   getInputState(): InputState {
     return { ...this.inputState };
   }
 }
-```text
+```
 
 ## Error Handling
 
 ### Graceful Degradation
 
 **Asset Loading Error Handling:**
+
 ```typescript
 class AssetManager {
   loadAssets(): Promise<void> {
     return new Promise((resolve, reject) => {
-      this.scene.load.on('filecomplete', this.handleFileComplete, this);
+      this.scene.load.on("filecomplete", this.handleFileComplete, this);
-      this.scene.load.on('loaderror', this.handleLoadError, this);
+      this.scene.load.on("loaderror", this.handleLoadError, this);
-      this.scene.load.on('complete', () => resolve());
+      this.scene.load.on("complete", () => resolve());
-      
+
       this.scene.load.start();
     });
   }
-  
+
   private handleLoadError(file: Phaser.Loader.File): void {
     console.error(`Failed to load asset: ${file.key}`);
-    
+
     // Use fallback assets
     this.loadFallbackAsset(file.key);
   }
-  
+
   private loadFallbackAsset(key: string): void {
     // Load placeholder or default assets
     switch (key) {
-      case 'player':
+      case "player":
-        this.scene.load.image('player', 'assets/defaults/default-player.png');
+        this.scene.load.image("player", "assets/defaults/default-player.png");
         break;
       default:
         console.warn(`No fallback for asset: ${key}`);
@@ -1246,25 +1379,26 @@ class AssetManager {
 ### Runtime Error Recovery
 
 **System Error Handling:**
+
 ```typescript
 class GameSystem {
   protected handleError(error: Error, context: string): void {
     console.error(`Error in ${context}:`, error);
-    
+
     // Report to analytics/logging service
     this.reportError(error, context);
-    
+
     // Attempt recovery
     this.attemptRecovery(context);
   }
-  
+
   private attemptRecovery(context: string): void {
     switch (context) {
-      case 'update':
+      case "update":
         // Reset system state
         this.reset();
         break;
-      case 'render':
+      case "render":
         // Disable visual effects
         this.disableEffects();
         break;
@@ -1274,64 +1408,66 @@ class GameSystem {
     }
   }
 }
-```text
+```
 
 ## Testing Standards
 
 ### Unit Testing
 
 **Game Logic Testing:**
+
 ```typescript
 // Example test for game mechanics
-describe('HealthComponent', () => {
+describe("HealthComponent", () => {
   let healthComponent: HealthComponent;
-  
+
   beforeEach(() => {
     const mockEntity = {} as GameEntity;
     healthComponent = new HealthComponent(mockEntity, 100);
   });
-  
+
-  test('should initialize with correct health', () => {
+  test("should initialize with correct health", () => {
     expect(healthComponent.currentHealth).toBe(100);
     expect(healthComponent.maxHealth).toBe(100);
   });
-  
+
-  test('should handle damage correctly', () => {
+  test("should handle damage correctly", () => {
     healthComponent.takeDamage(25);
     expect(healthComponent.currentHealth).toBe(75);
     expect(healthComponent.isAlive()).toBe(true);
   });
-  
+
-  test('should handle death correctly', () => {
+  test("should handle death correctly", () => {
     healthComponent.takeDamage(150);
     expect(healthComponent.currentHealth).toBe(0);
     expect(healthComponent.isAlive()).toBe(false);
   });
 });
-```text
+```
 
 ### Integration Testing
 
 **Scene Testing:**
+
 ```typescript
-describe('GameScene Integration', () => {
+describe("GameScene Integration", () => {
   let scene: GameScene;
   let mockGame: Phaser.Game;
-  
+
   beforeEach(() => {
     // Mock Phaser game instance
     mockGame = createMockGame();
     scene = new GameScene();
   });
-  
+
-  test('should initialize all systems', () => {
+  test("should initialize all systems", () => {
     scene.create({});
-    
+
     expect(scene.gameManager).toBeDefined();
     expect(scene.inputManager).toBeDefined();
   });
 });
-```text
+```
 
 ## File Organization
 
@@ -1385,21 +1521,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
@@ -1412,6 +1552,7 @@ src/
 ### Code Review Checklist
 
 **Before Committing:**
+
 - [ ] TypeScript compiles without errors
 - [ ] All tests pass
 - [ ] Performance targets met (60 FPS)
@@ -1425,17 +1566,20 @@ src/
 ## Performance Targets
 
 ### Frame Rate Requirements
+
 - **Desktop**: Maintain 60 FPS at 1080p
 - **Mobile**: Maintain 60 FPS on mid-range devices, minimum 30 FPS on low-end
 - **Optimization**: Implement dynamic quality scaling when performance drops
 
 ### Memory Management
+
 - **Total Memory**: Under 100MB for full game
 - **Per Scene**: Under 50MB per gameplay scene
 - **Asset Loading**: Progressive loading to stay under limits
 - **Garbage Collection**: Minimize object creation in update loops
 
 ### Loading Performance
+
 - **Initial Load**: Under 5 seconds for game start
 - **Scene Transitions**: Under 2 seconds between scenes
 - **Asset Streaming**: Background loading for upcoming content

dist/expansion-packs/bmad-2d-phaser-game-dev/agents/game-sm.txt

@@ -109,6 +109,7 @@ Create detailed, actionable game development stories that enable AI developers t
 ## Prerequisites
 
 Before creating stories, ensure you have:
+
 - Completed Game Design Document (GDD)
 - Game Architecture Document
 - Epic definition this story belongs to
@@ -119,12 +120,14 @@ Before creating stories, ensure you have:
 ### 1. Story Identification
 
 **Review Epic Context:**
+
 - Understand the epic's overall goal
 - Identify specific features that need implementation
 - Review any existing stories in the epic
 - Ensure no duplicate work
 
 **Feature Analysis:**
+
 - Reference specific GDD sections
 - Understand player experience goals
 - Identify technical complexity
@@ -133,12 +136,14 @@ Before creating stories, ensure you have:
 ### 2. Story Scoping
 
 **Single Responsibility:**
+
 - Focus on one specific game feature
 - Ensure story is completable in 1-3 days
 - Break down complex features into multiple stories
 - Maintain clear boundaries with other stories
 
 **Implementation Clarity:**
+
 - Define exactly what needs to be built
 - Specify all technical requirements
 - Include all necessary integration points
@@ -150,6 +155,7 @@ Before creating stories, ensure you have:
 Use `templates#game-story-tmpl` following all embedded LLM instructions
 
 **Key Focus Areas:**
+
 - Clear, actionable description
 - Specific acceptance criteria
 - Detailed technical specifications
@@ -159,18 +165,21 @@ Use `templates#game-story-tmpl` following all embedded LLM instructions
 ### 4. Story Validation
 
 **Technical Review:**
+
 - Verify all technical specifications are complete
 - Ensure integration points are clearly defined
 - Confirm file paths match architecture
 - Validate TypeScript interfaces and classes
 
 **Game Design Alignment:**
+
 - Confirm story implements GDD requirements
 - Verify player experience goals are met
 - Check balance parameters are included
 - Ensure game mechanics are correctly interpreted
 
 **Implementation Readiness:**
+
 - All dependencies identified
 - Assets requirements specified
 - Testing criteria defined
@@ -182,6 +191,7 @@ Use `templates#game-story-tmpl` following all embedded LLM instructions
 Execute `checklists#game-story-dod-checklist` against completed story
 
 **Story Criteria:**
+
 - Story is immediately actionable
 - No design decisions left to developer
 - Technical requirements are complete
@@ -191,12 +201,14 @@ Execute `checklists#game-story-dod-checklist` against completed story
 ### 6. Story Refinement
 
 **Developer Perspective:**
+
 - Can a developer start implementation immediately?
 - Are all technical questions answered?
 - Is the scope appropriate for the estimated points?
 - Are all dependencies clearly identified?
 
 **Iterative Improvement:**
+
 - Address any gaps or ambiguities
 - Clarify complex technical requirements
 - Ensure story fits within epic scope
@@ -205,6 +217,7 @@ Execute `checklists#game-story-dod-checklist` against completed story
 ## Story Elements Checklist
 
 ### Required Sections
+
 - [ ] Clear, specific description
 - [ ] Complete acceptance criteria (functional, technical, game design)
 - [ ] Detailed technical specifications
@@ -218,6 +231,7 @@ Execute `checklists#game-story-dod-checklist` against completed story
 - [ ] Definition of Done checklist
 
 ### Game-Specific Requirements
+
 - [ ] GDD section references
 - [ ] Game mechanic implementation details
 - [ ] Player experience goals
@@ -227,6 +241,7 @@ Execute `checklists#game-story-dod-checklist` against completed story
 - [ ] Cross-platform considerations
 
 ### Technical Quality
+
 - [ ] TypeScript strict mode compliance
 - [ ] Architecture document alignment
 - [ ] Code organization follows standards
@@ -237,18 +252,21 @@ Execute `checklists#game-story-dod-checklist` against completed story
 ## Common Pitfalls
 
 **Scope Issues:**
+
 - Story too large (break into multiple stories)
 - Story too vague (add specific requirements)
 - Missing dependencies (identify all prerequisites)
 - Unclear boundaries (define what's in/out of scope)
 
 **Technical Issues:**
+
 - Missing integration details
 - Incomplete technical specifications
 - Undefined interfaces or classes
 - Missing performance requirements
 
 **Game Design Issues:**
+
 - Not referencing GDD properly
 - Missing player experience context
 - Unclear game mechanic implementation
@@ -257,6 +275,7 @@ Execute `checklists#game-story-dod-checklist` against completed story
 ## Success Criteria
 
 **Story Readiness:**
+
 - [ ] Developer can start implementation immediately
 - [ ] No additional design decisions required
 - [ ] All technical questions answered
@@ -265,6 +284,7 @@ Execute `checklists#game-story-dod-checklist` against completed story
 - [ ] Story fits within epic scope
 
 **Quality Validation:**
+
 - [ ] Game story DOD checklist passes
 - [ ] Architecture alignment confirmed
 - [ ] GDD requirements covered
@@ -274,6 +294,7 @@ Execute `checklists#game-story-dod-checklist` against completed story
 ## Handoff Protocol
 
 **To Game Developer:**
+
 1. Provide story document
 2. Confirm GDD and architecture access
 3. Verify all dependencies are met
@@ -281,6 +302,7 @@ Execute `checklists#game-story-dod-checklist` against completed story
 5. Establish check-in schedule
 
 **Story Status Updates:**
+
 - Draft → Ready for Development
 - In Development → Code Review
 - Code Review → Testing
@@ -289,6 +311,106 @@ Execute `checklists#game-story-dod-checklist` against completed story
 This task ensures game development stories are immediately actionable and enable efficient AI-driven development of game features.
 ==================== END: tasks#create-game-story ====================
 
+==================== START: tasks#execute-checklist ====================
+# 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.
+
+## Context
+
+The BMAD Method uses various checklists to ensure quality and completeness of different artifacts. Each checklist contains embedded prompts and instructions to guide the LLM through thorough validation and advanced elicitation. The checklists automatically identify their required artifacts and guide the validation process.
+
+## 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 bmad-core/checklists folder to select the appropriate one to run.
+
+## 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
+     - Load the appropriate checklist from bmad-core/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
+   - Confirm if they want to work through the checklist:
+     - Section by section (interactive mode - very time consuming)
+     - 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
+     - Check each item against the relevant documentation or artifacts as appropriate
+     - Present summary of findings for that section, highlighting warnings, errors and non applicable items (rationale for non-applicability).
+     - 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
+
+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
+   - Aside from this, follow all checklist llm instructions
+   - Mark items as:
+     - ✅ PASS: Requirement clearly met
+     - ❌ FAIL: Requirement not met or insufficient coverage
+     - ⚠️ PARTIAL: Some aspects covered but needs improvement
+     - N/A: Not applicable to this case
+
+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
+   - In interactive mode, discuss findings with user
+   - Document any user decisions or explanations
+
+6. **Final Report**
+
+   Prepare a summary that includes:
+
+   - Overall checklist completion status
+   - Pass rates by section
+   - List of failed items with context
+   - Specific recommendations for improvement
+   - Any sections or items marked as N/A with justification
+
+## Checklist Execution Methodology
+
+Each checklist now contains embedded LLM prompts and instructions that will:
+
+1. **Guide thorough thinking** - Prompts ensure deep analysis of each section
+2. **Request specific artifacts** - Clear instructions on what documents/access is needed
+3. **Provide contextual guidance** - Section-specific prompts for better validation
+4. **Generate comprehensive reports** - Final summary with detailed findings
+
+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 ====================
+
 ==================== START: templates#game-story-tmpl ====================
 # Story: {{Story Title}}
 
@@ -533,6 +655,7 @@ class {{ClassName}} extends {{PhaseClass}} {
 ## Story Completeness
 
 ### Basic Story Elements
+
 - [ ] **Story Title** - Clear, descriptive title that identifies the feature
 - [ ] **Epic Assignment** - Story is properly assigned to relevant epic
 - [ ] **Priority Level** - Appropriate priority assigned (High/Medium/Low)
@@ -540,6 +663,7 @@ class {{ClassName}} extends {{PhaseClass}} {
 - [ ] **Description** - Clear, concise description of what needs to be implemented
 
 ### Game Design Alignment
+
 - [ ] **GDD Reference** - Specific Game Design Document section referenced
 - [ ] **Game Mechanic Context** - Clear connection to game mechanics defined in GDD
 - [ ] **Player Experience Goal** - Describes the intended player experience
@@ -549,6 +673,7 @@ class {{ClassName}} extends {{PhaseClass}} {
 ## Technical Specifications
 
 ### Architecture Compliance
+
 - [ ] **File Organization** - Follows game architecture document structure
 - [ ] **Class Definitions** - TypeScript interfaces and classes are properly defined
 - [ ] **Integration Points** - Clear specification of how feature integrates with existing systems
@@ -556,6 +681,7 @@ class {{ClassName}} extends {{PhaseClass}} {
 - [ ] **Dependencies** - All system dependencies clearly identified
 
 ### Phaser 3 Requirements
+
 - [ ] **Scene Integration** - Specifies which scenes are affected and how
 - [ ] **Game Object Usage** - Proper use of Phaser 3 game objects and components
 - [ ] **Physics Integration** - Physics requirements specified if applicable
@@ -563,6 +689,7 @@ class {{ClassName}} extends {{PhaseClass}} {
 - [ ] **Performance Considerations** - 60 FPS target and optimization requirements
 
 ### Code Quality Standards
+
 - [ ] **TypeScript Strict Mode** - All code must comply with strict TypeScript
 - [ ] **Error Handling** - Error scenarios and handling requirements specified
 - [ ] **Memory Management** - Object pooling and cleanup requirements where needed
@@ -572,6 +699,7 @@ class {{ClassName}} extends {{PhaseClass}} {
 ## Implementation Readiness
 
 ### Acceptance Criteria
+
 - [ ] **Functional Requirements** - All functional acceptance criteria are specific and testable
 - [ ] **Technical Requirements** - Technical acceptance criteria are complete and verifiable
 - [ ] **Game Design Requirements** - Game-specific requirements match GDD specifications
@@ -579,6 +707,7 @@ class {{ClassName}} extends {{PhaseClass}} {
 - [ ] **Completeness** - No acceptance criteria are vague or unmeasurable
 
 ### Implementation Tasks
+
 - [ ] **Task Breakdown** - Story broken into specific, ordered implementation tasks
 - [ ] **Task Scope** - Each task is completable in 1-4 hours
 - [ ] **Task Clarity** - Each task has clear, actionable instructions
@@ -586,6 +715,7 @@ class {{ClassName}} extends {{PhaseClass}} {
 - [ ] **Development Flow** - Tasks follow logical implementation order
 
 ### Dependencies
+
 - [ ] **Story Dependencies** - All prerequisite stories identified with IDs
 - [ ] **Technical Dependencies** - Required systems and files identified
 - [ ] **Asset Dependencies** - All needed assets specified with locations
@@ -595,6 +725,7 @@ class {{ClassName}} extends {{PhaseClass}} {
 ## Testing Requirements
 
 ### Test Coverage
+
 - [ ] **Unit Test Requirements** - Specific unit test files and scenarios defined
 - [ ] **Integration Test Cases** - Integration testing with other game systems specified
 - [ ] **Manual Test Cases** - Game-specific manual testing procedures defined
@@ -602,6 +733,7 @@ class {{ClassName}} extends {{PhaseClass}} {
 - [ ] **Edge Case Testing** - Edge cases and error conditions covered
 
 ### Test Implementation
+
 - [ ] **Test File Paths** - Exact test file locations specified
 - [ ] **Test Scenarios** - All test scenarios are complete and executable
 - [ ] **Expected Behaviors** - Clear expected outcomes for all tests defined
@@ -611,6 +743,7 @@ class {{ClassName}} extends {{PhaseClass}} {
 ## Game-Specific Quality
 
 ### Gameplay Implementation
+
 - [ ] **Mechanic Accuracy** - Implementation matches GDD mechanic specifications
 - [ ] **Player Controls** - Input handling requirements are complete
 - [ ] **Game Feel** - Requirements for juice, feedback, and responsiveness specified
@@ -618,6 +751,7 @@ class {{ClassName}} extends {{PhaseClass}} {
 - [ ] **State Management** - Game state changes and persistence requirements defined
 
 ### User Experience
+
 - [ ] **UI Requirements** - User interface elements and behaviors specified
 - [ ] **Audio Integration** - Sound effect and music requirements defined
 - [ ] **Visual Feedback** - Animation and visual effect requirements specified
@@ -625,6 +759,7 @@ class {{ClassName}} extends {{PhaseClass}} {
 - [ ] **Error Recovery** - User-facing error handling and recovery specified
 
 ### Performance Optimization
+
 - [ ] **Frame Rate Targets** - Specific FPS requirements for different platforms
 - [ ] **Memory Usage** - Memory consumption limits and monitoring requirements
 - [ ] **Asset Optimization** - Texture, audio, and data optimization requirements
@@ -634,6 +769,7 @@ class {{ClassName}} extends {{PhaseClass}} {
 ## Documentation and Communication
 
 ### Story Documentation
+
 - [ ] **Implementation Notes** - Additional context and implementation guidance provided
 - [ ] **Design Decisions** - Key design choices documented with rationale
 - [ ] **Future Considerations** - Potential future enhancements or modifications noted
@@ -641,6 +777,7 @@ class {{ClassName}} extends {{PhaseClass}} {
 - [ ] **Reference Materials** - Links to relevant GDD sections and architecture docs
 
 ### Developer Handoff
+
 - [ ] **Immediate Actionability** - Developer can start implementation without additional questions
 - [ ] **Complete Context** - All necessary context provided within the story
 - [ ] **Clear Boundaries** - What is and isn't included in the story scope is clear
@@ -650,6 +787,7 @@ class {{ClassName}} extends {{PhaseClass}} {
 ## Final Validation
 
 ### Story Readiness
+
 - [ ] **No Ambiguity** - No sections require interpretation or additional design decisions
 - [ ] **Technical Completeness** - All technical requirements are specified and actionable
 - [ ] **Scope Appropriateness** - Story scope matches assigned story points
@@ -657,6 +795,7 @@ class {{ClassName}} extends {{PhaseClass}} {
 - [ ] **Review Completion** - Story has been reviewed for completeness and accuracy
 
 ### Implementation Preparedness
+
 - [ ] **Environment Ready** - Development environment requirements specified
 - [ ] **Resources Available** - All required resources (assets, docs, dependencies) accessible
 - [ ] **Testing Prepared** - Testing environment and data requirements specified

dist/expansion-packs/bmad-infrastructure-devops/agents/infra-devops-platform.txt

@@ -1006,7 +1006,7 @@ module "vpc" {
   public_subnets = {{public_subnets}}
   private_subnets = {{private_subnets}}
 }
-```text
+```
 
 ### Security Foundation
 
@@ -1053,7 +1053,7 @@ eksctl create cluster \
   --nodegroup-name {{nodegroup_name}} \
   --node-type {{instance_type}} \
   --nodes {{node_count}}
-```text
+```
 
 ^^/CONDITION: uses_eks^^
 
@@ -1067,7 +1067,7 @@ az aks create \
   --node-count {{node_count}} \
   --node-vm-size {{vm_size}} \
   --network-plugin azure
-```text
+```
 
 ^^/CONDITION: uses_aks^^
 
@@ -1111,11 +1111,11 @@ metadata:
 spec:
   source:
     repoURL:
-      '[object Object]': null
+      "[object Object]": null
     targetRevision:
-      '[object Object]': null
+      "[object Object]": null
     path:
-      '[object Object]': null
+      "[object Object]": null
 ```
 
 ^^/CONDITION: uses_argocd^^
@@ -1132,10 +1132,10 @@ spec:
   interval: 1m
   ref:
     branch:
-      '[object Object]': null
+      "[object Object]": null
   url:
-    '[object Object]': null
+    "[object Object]": null
-```text
+```
 
 ^^/CONDITION: uses_flux^^
 
@@ -1153,7 +1153,7 @@ platform-gitops/
  applications/
      base/
      overlays/
-```text
+```
 
 ### Deployment Workflows
 
@@ -1197,7 +1197,7 @@ istioctl install --set profile={{istio_profile}} \
 # Linkerd Installation
 linkerd install --cluster-name={{cluster_name}} | kubectl apply -f -
 linkerd viz install | kubectl apply -f -
-```text
+```
 
 - Control plane setup
 - Proxy injection
@@ -1248,7 +1248,7 @@ spec:
     - name: deploy
       taskRef:
         name: gitops-deploy
-```text
+```
 
 ### Development Tools
 
@@ -1290,7 +1290,7 @@ data:
       - job_name: 'kubernetes-pods'
         kubernetes_sd_configs:
           - role: pod
-```text
+```
 
 ### Platform Observability
 
@@ -1380,7 +1380,7 @@ stages:
   - develop
   - test
   - deploy
-```text
+```
 
 ## Platform Validation & Testing
 
@@ -1409,8 +1409,8 @@ stages:
 
 ### Load Testing
 
-```yaml
+```typescript
-# K6 Load Test Example
+// K6 Load Test Example
 import http from 'k6/http';
 import { check } from 'k6';
 
@@ -2019,3 +2019,38 @@ This checklist serves as a comprehensive framework for validating infrastructure
 - [ ] Platform component integration validated
 - [ ] Cross-platform functionality tested and verified
 ==================== END: checklists#infrastructure-checklist ====================
+
+==================== START: data#technical-preferences ====================
+# User-Defined Preferred Patterns and Preferences
+
+None Listed
+==================== END: data#technical-preferences ====================
+
+==================== START: utils#template-format ====================
+# Template Format Conventions
+
+Templates in the BMAD method use standardized markup for AI processing. These conventions ensure consistent document generation.
+
+## Template Markup Elements
+
+- **{{placeholders}}**: Variables to be replaced with actual content
+- **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users)
+- **REPEAT** sections: Content blocks that may be repeated as needed
+- **^^CONDITION^^** blocks: Conditional content included only if criteria are met
+- **@{examples}**: Example content for guidance (never output to users)
+
+## Processing Rules
+
+- Replace all {{placeholders}} with project-specific content
+- Execute all [[LLM: instructions]] internally without showing users
+- Process conditional and repeat blocks as specified
+- Use examples for guidance but never include them in final output
+- Present only clean, formatted content to users
+
+## Critical Guidelines
+
+- **NEVER display template markup, LLM instructions, or examples to users**
+- 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 ====================

dist/expansion-packs/expansion-creator/agents/bmad-the-creator.txt

@@ -160,7 +160,7 @@ Created during agent setup:
 - Templates:
   - [ ] template-name-1.md
   - [ ] template-name-2.md
-```text
+```
 
 ### 4. Create Agent File
 
@@ -218,7 +218,7 @@ Present to the user:
    1. Review and customize the created tasks/templates
    2. Run npm run build:agents
    3. Test the agent thoroughly
-```text
+```
 
 ## Template Reference
 
@@ -247,7 +247,7 @@ persona:
     - Data integrity and accuracy above all
     - Clear communication of complex findings
     - Actionable insights over raw numbers
-```text
+```
 
 ## Creating Missing Dependencies
 
@@ -280,12 +280,12 @@ When a required task or template doesn't exist:
 ```yaml
 dependencies:
   tasks:
-    - 'create-doc # Required if agent creates any documents'
+    - create-doc
-    - 'analyze-requirements # Custom task for this agent'
+    - analyze-requirements
-    - 'generate-report # Another custom task'
+    - generate-report
   templates:
-    - 'requirements-doc # Template for requirements documents'
+    - requirements-doc
-    - 'analysis-report # Template for analysis reports'
+    - analysis-report
 ```
 
 ## Notes
@@ -973,7 +973,7 @@ Before declaring complete:
 
 **README Structure with Character Introduction:**
 
-````markdown
+```markdown
 # {Pack Name} Expansion Pack
 
 ## Meet Your {Domain} Team
@@ -998,9 +998,7 @@ _{Professional background and expertise}_
 
 2. **Launch Orchestrator**:
 
-   ```bash
    npm run agent {pack-name}-orchestrator
-   ```
 
 3. **Follow Numbered Options**: {Character Name} will present numbered choices for each decision
 
@@ -1030,7 +1028,7 @@ _{Professional background and expertise}_
 ### Knowledge Base
 
 [Embedded domain expertise]
-````
+```
 
 #### 6.3 Advanced Data File Documentation with Validation
 
@@ -1330,6 +1328,405 @@ Embedded knowledge (automatic):
 ```
 ==================== END: tasks#generate-expansion-pack ====================
 
+==================== START: tasks#advanced-elicitation ====================
+# Advanced Elicitation Task
+
+## Purpose
+
+- Provide optional reflective and brainstorming actions to enhance content quality
+- Enable deeper exploration of ideas through structured elicitation techniques
+- Support iterative refinement through multiple analytical perspectives
+
+## Task Instructions
+
+### 1. Section Context and Review
+
+[[LLM: When invoked after outputting a section:
+
+1. First, provide a brief 1-2 sentence summary of what the user should look for in the section just presented (e.g., "Please review the technology choices for completeness and alignment with your project needs. Pay special attention to version numbers and any missing categories.")
+
+2. If the section contains Mermaid diagrams, explain each diagram briefly before offering elicitation options (e.g., "The component diagram shows the main system modules and their interactions. Notice how the API Gateway routes requests to different services.")
+
+3. If the section contains multiple distinct items (like multiple components, multiple patterns, etc.), inform the user they can apply elicitation actions to:
+
+   - The entire section as a whole
+   - Individual items within the section (specify which item when selecting an action)
+
+4. Then present the action list as specified below.]]
+
+### 2. Ask for Review and Present Action List
+
+[[LLM: Ask the user to review the drafted section. In the SAME message, inform them that they can suggest additions, removals, or modifications, OR they can select an action by number from the 'Advanced Reflective, Elicitation & Brainstorming Actions'. If there are multiple items in the section, mention they can specify which item(s) to apply the action to. Then, present ONLY the numbered list (0-9) of these actions. Conclude by stating that selecting 9 will proceed to the next section. Await user selection. If an elicitation action (0-8) is chosen, execute it and then re-offer this combined review/elicitation choice. If option 9 is chosen, or if the user provides direct feedback, proceed accordingly.]]
+
+**Present the numbered list (0-9) with this exact format:**
+
+```text
+**Advanced Reflective, Elicitation & Brainstorming Actions**
+Choose an action (0-9 - 9 to bypass - HELP for explanation of these options):
+
+0. Expand or Contract for Audience
+1. Explain Reasoning (CoT Step-by-Step)
+2. Critique and Refine
+3. Analyze Logical Flow and Dependencies
+4. Assess Alignment with Overall Goals
+5. Identify Potential Risks and Unforeseen Issues
+6. Challenge from Critical Perspective (Self or Other Persona)
+7. Explore Diverse Alternatives (ToT-Inspired)
+8. Hindsight is 20/20: The 'If Only...' Reflection
+9. Proceed / No Further Actions
+```
+
+### 2. Processing Guidelines
+
+**Do NOT show:**
+
+- The full protocol text with `[[LLM: ...]]` instructions
+- Detailed explanations of each option unless executing or the user asks, when giving the definition you can modify to tie its relevance
+- Any internal template markup
+
+**After user selection from the list:**
+
+- Execute the chosen action according to the protocol instructions below
+- Ask if they want to select another action or proceed with option 9 once complete
+- Continue until user selects option 9 or indicates completion
+
+## Action Definitions
+
+0. Expand or Contract for Audience
+   [[LLM: Ask the user whether they want to 'expand' on the content (add more detail, elaborate) or 'contract' it (simplify, clarify, make more concise). Also, ask if there's a specific target audience they have in mind. Once clarified, perform the expansion or contraction from your current role's perspective, tailored to the specified audience if provided.]]
+
+1. Explain Reasoning (CoT Step-by-Step)
+   [[LLM: Explain the step-by-step thinking process, characteristic of your role, that you used to arrive at the current proposal for this content.]]
+
+2. Critique and Refine
+   [[LLM: From your current role's perspective, review your last output or the current section for flaws, inconsistencies, or areas for improvement, and then suggest a refined version reflecting your expertise.]]
+
+3. Analyze Logical Flow and Dependencies
+   [[LLM: From your role's standpoint, examine the content's structure for logical progression, internal consistency, and any relevant dependencies. Confirm if elements are presented in an effective order.]]
+
+4. Assess Alignment with Overall Goals
+   [[LLM: Evaluate how well the current content contributes to the stated overall goals of the document, interpreting this from your specific role's perspective and identifying any misalignments you perceive.]]
+
+5. Identify Potential Risks and Unforeseen Issues
+   [[LLM: Based on your role's expertise, brainstorm potential risks, overlooked edge cases, or unintended consequences related to the current content or proposal.]]
+
+6. Challenge from Critical Perspective (Self or Other Persona)
+   [[LLM: Adopt a critical perspective on the current content. If the user specifies another role or persona (e.g., 'as a customer', 'as [Another Persona Name]'), critique the content or play devil's advocate from that specified viewpoint. If no other role is specified, play devil's advocate from your own current persona's viewpoint, arguing against the proposal or current content and highlighting weaknesses or counterarguments specific to your concerns. This can also randomly include YAGNI when appropriate, such as when trimming the scope of an MVP, the perspective might challenge the need for something to cut MVP scope.]]
+
+7. Explore Diverse Alternatives (ToT-Inspired)
+   [[LLM: From your role's perspective, first broadly brainstorm a range of diverse approaches or solutions to the current topic. Then, from this wider exploration, select and present 2 distinct alternatives, detailing the pros, cons, and potential implications you foresee for each.]]
+
+8. Hindsight is 20/20: The 'If Only...' Reflection
+   [[LLM: In your current persona, imagine it's a retrospective for a project based on the current content. What's the one 'if only we had known/done X...' that your role would humorously or dramatically highlight, along with the imagined consequences?]]
+
+9. Proceed / No Further Actions
+   [[LLM: Acknowledge the user's choice to finalize the current work, accept the AI's last output as is, or move on to the next step without selecting another action from this list. Prepare to proceed accordingly.]]
+==================== END: tasks#advanced-elicitation ====================
+
+==================== START: tasks#create-deep-research-prompt ====================
+# 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.
+
+## Purpose
+
+Generate well-structured research prompts that:
+
+- Define clear research objectives and scope
+- Specify appropriate research methodologies
+- Outline expected deliverables and formats
+- Guide systematic investigation of complex topics
+- Ensure actionable insights are captured
+
+## Research Type Selection
+
+[[LLM: First, help the user select the most appropriate research focus based on their needs and any input documents they've provided.]]
+
+### 1. Research Focus Options
+
+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**
+   [[LLM: Allow user to define their own specific research focus.]]
+   - User-defined research objectives
+   - Specialized domain investigation
+   - Cross-functional research needs
+
+### 2. Input Processing
+
+[[LLM: Based on the selected research type and any provided inputs (project brief, brainstorming results, etc.), extract relevant context and constraints.]]
+
+**If Project Brief provided:**
+
+- Extract key product concepts and goals
+- Identify target users and use cases
+- Note technical constraints and preferences
+- Highlight uncertainties and assumptions
+
+**If Brainstorming Results provided:**
+
+- Synthesize main ideas and themes
+- Identify areas needing validation
+- Extract hypotheses to test
+- Note creative directions to explore
+
+**If Market Research provided:**
+
+- Build on identified opportunities
+- Deepen specific market insights
+- Validate initial findings
+- Explore adjacent possibilities
+
+**If Starting Fresh:**
+
+- Gather essential context through questions
+- Define the problem space
+- Clarify research objectives
+- Establish success criteria
+
+## Process
+
+### 3. Research Prompt Structure
+
+[[LLM: Based on the selected research type and context, collaboratively develop a comprehensive research prompt with these components.]]
+
+#### A. Research Objectives
+
+[[LLM: Work with the user to articulate clear, specific objectives for the research.]]
+
+- Primary research goal and purpose
+- Key decisions the research will inform
+- Success criteria for the research
+- Constraints and boundaries
+
+#### B. Research Questions
+
+[[LLM: Develop specific, actionable research questions organized by theme.]]
+
+**Core Questions:**
+
+- Central questions that must be answered
+- Priority ranking of questions
+- Dependencies between questions
+
+**Supporting Questions:**
+
+- Additional context-building questions
+- Nice-to-have insights
+- Future-looking considerations
+
+#### C. Research Methodology
+
+[[LLM: Specify appropriate research methods based on the type and objectives.]]
+
+**Data Collection Methods:**
+
+- Secondary research sources
+- Primary research approaches (if applicable)
+- Data quality requirements
+- Source credibility criteria
+
+**Analysis Frameworks:**
+
+- Specific frameworks to apply
+- Comparison criteria
+- Evaluation methodologies
+- Synthesis approaches
+
+#### D. Output Requirements
+
+[[LLM: Define how research findings should be structured and presented.]]
+
+**Format Specifications:**
+
+- Executive summary requirements
+- Detailed findings structure
+- Visual/tabular presentations
+- Supporting documentation
+
+**Key Deliverables:**
+
+- Must-have sections and insights
+- Decision-support elements
+- Action-oriented recommendations
+- Risk and uncertainty documentation
+
+### 4. Prompt Generation
+
+[[LLM: Synthesize all elements into a comprehensive, ready-to-use research prompt.]]
+
+**Research Prompt Template:**
+
+```markdown
+## Research Objective
+
+[Clear statement of what this research aims to achieve]
+
+## Background Context
+
+[Relevant information from project brief, brainstorming, or other inputs]
+
+## Research Questions
+
+### Primary Questions (Must Answer)
+
+1. [Specific, actionable question]
+2. [Specific, actionable question]
+   ...
+
+### Secondary Questions (Nice to Have)
+
+1. [Supporting question]
+2. [Supporting question]
+   ...
+
+## Research Methodology
+
+### Information Sources
+
+- [Specific source types and priorities]
+
+### Analysis Frameworks
+
+- [Specific frameworks to apply]
+
+### Data Requirements
+
+- [Quality, recency, credibility needs]
+
+## Expected Deliverables
+
+### Executive Summary
+
+- Key findings and insights
+- Critical implications
+- Recommended actions
+
+### Detailed Analysis
+
+[Specific sections needed based on research type]
+
+### Supporting Materials
+
+- Data tables
+- Comparison matrices
+- Source documentation
+
+## Success Criteria
+
+[How to evaluate if research achieved its objectives]
+
+## Timeline and Priority
+
+[If applicable, any time constraints or phasing]
+```
+
+### 5. Review and Refinement
+
+[[LLM: Present the draft research prompt for user 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?
+   - Are output requirements sufficient?
+
+3. **Refine as Needed**
+   - Incorporate user feedback
+   - Adjust scope or focus
+   - Add missing elements
+   - Clarify ambiguities
+
+### 6. Next Steps Guidance
+
+[[LLM: Provide clear guidance on how to use the research prompt.]]
+
+**Execution Options:**
+
+1. **Use with AI Research Assistant**: Provide this prompt to an AI model with research capabilities
+2. **Guide Human Research**: Use as a framework for manual research efforts
+3. **Hybrid Approach**: Combine AI and human research using this structure
+
+**Integration Points:**
+
+- How findings will feed into next phases
+- Which team members should review results
+- How to validate findings
+- When to revisit or expand research
+
+## Important Notes
+
+- The quality of the research prompt directly impacts the quality of insights gathered
+- Be specific rather than general in research questions
+- Consider both current state and future implications
+- Balance comprehensiveness with focus
+- Document assumptions and limitations clearly
+- Plan for iterative refinement based on initial findings
+==================== END: tasks#create-deep-research-prompt ====================
+
 ==================== START: templates#agent-tmpl ====================
 # [AGENT_ID]
 
@@ -1349,6 +1746,7 @@ activation-instructions:
     - 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
+    - Command
 
 agent:
   name: [AGENT_NAME]
@@ -1369,7 +1767,9 @@ persona:
     # Add more principles as needed
 
 startup:
-  - [STARTUP_INSTRUCTIONS]
+  - Greet the user with your name and role, and inform of the *help command.
+  - [STARTUP_INSTRUCTION]
+  - [STARTUP_INSTRUCTION]...
 
 commands:
   - "*help" - Show: numbered list of the following commands to allow selection
@@ -1400,7 +1800,7 @@ dependencies:
     - [TEMPLATE_1]  # Template with LLM instructions for guided creation
     - [TEMPLATE_2]  # Another template for different document type
     [[LLM: Example: blueprint-tmpl, contract-tmpl, report-tmpl
-    Each template should include [[LLM: guidance]] and other conventions from `template-formmat.md` sections for user interaction]]
+    Each template should include [[LLM: guidance]] and other conventions from `template-format.md` sections for user interaction]]
 
   checklists:
     - [CHECKLIST_1]  # Quality validation for template outputs
@@ -1416,7 +1816,7 @@ dependencies:
     - template-format  # Required if using templates
     - [UTIL_1]        # Other utilities as needed
     [[LLM: Include workflow-management if agent participates in workflows]]
-```text
+```
 
 @{example: Construction Contractor Agent}
 
@@ -1455,21 +1855,21 @@ commands:
   - '*exit" - Say goodbye as Marcus and exit'
 dependencies:
   tasks:
-    - 'create-doc          # For document creation'
+    - create-doc
-    - 'validate-plans      # Custom validation task'
+    - validate-plans
-    - 'safety-assessment   # Custom safety review task'
+    - safety-assessment
   templates:
-    - 'blueprint-tmpl      # Architectural blueprint template'
+    - blueprint-tmpl
-    - 'estimate-tmpl       # Cost estimation template'
+    - estimate-tmpl
-    - 'schedule-tmpl       # Project timeline template'
+    - schedule-tmpl
   checklists:
-    - 'blueprint-checklist # Validates blueprint completeness'
+    - blueprint-checklist
-    - 'safety-checklist    # Safety compliance validation'
+    - safety-checklist
   data:
-    - 'building-codes.md   # Local building code reference'
+    - building-codes.md
-    - 'materials-guide.md  # Construction materials specs'
+    - materials-guide.md
   utils:
-    - 'template-format     # For template processing'
+    - template-format
 ```
 ==================== END: templates#agent-tmpl ====================
 

dist/teams/team-fullstack.txt

@@ -60,9 +60,9 @@ workflows:
 ==================== END: agent-teams#team-fullstack ====================
 
 ==================== START: agents#bmad-orchestrator ====================
-# bmad
+# bmad-orchestrator
 
-CRITICAL: Read the full YML to understand your operating params, start activation to alter your state of being, follow startup instructions, stay in this being until told to exit this mode:
+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
 agent:
@@ -94,9 +94,9 @@ startup:
   - If clear match to an agent's expertise, suggest transformation with *agent command
   - If project-oriented, suggest *workflow-guidance to explore options
   - Load resources only when needed - never pre-load
-commands:  # All commands require * prefix when used (e.g., *help, *agent pm)
+commands:
   help: Show this guide with available agents and workflows
-  chat-mode: Start conversational mode for detailed assistance  
+  chat-mode: Start conversational mode for detailed assistance
   kb-mode: Load full BMAD knowledge base
   status: Show current context, active agent, and progress
   agent: Transform into a specialized agent (list if name not specified)
@@ -111,41 +111,40 @@ commands:  # All commands require * prefix when used (e.g., *help, *agent pm)
 help-display-template: |
   === BMAD Orchestrator Commands ===
   All commands must start with * (asterisk)
-  
+
   Core 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
   *exit ............... Return to BMad or exit session
-  
+
   Agent & Task Management:
   *agent [name] ....... Transform into specialized agent (list if no name)
   *task [name] ........ Run specific task (list if no name, requires agent)
   *checklist [name] ... Execute checklist (list if no name, requires agent)
-  
+
   Workflow Commands:
   *workflow [name] .... Start specific workflow (list if no name)
   *workflow-guidance .. Get personalized help selecting the right workflow
-  
+
   Other Commands:
   *yolo ............... Toggle skip confirmations mode
   *party-mode ......... Group chat with all agents
   *doc-out ............ Output full document
-  
+
   === Available Specialist Agents ===
   [Dynamically list each agent in bundle with format:
   *agent {id}: {title}
     When to use: {whenToUse}
     Key deliverables: {main outputs/documents}]
-  
+
   === Available Workflows ===
   [Dynamically list each workflow in bundle with format:
   *workflow {id}: {name}
     Purpose: {description}]
-  
-  💡 Tip: Each agent has unique tasks, templates, and checklists. Switch to an agent to access their capabilities!
 
+  💡 Tip: Each agent has unique tasks, templates, and checklists. Switch to an agent to access their capabilities!
 fuzzy-matching:
   - 85% confidence threshold
   - Show numbered list if unsure
@@ -217,13 +216,13 @@ persona:
 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'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - (Default) Strategic analysis consultation with advanced-elicitation'
+  - chat-mode: (Default) Strategic analysis consultation with advanced-elicitation
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - create-doc {template}: Create doc (no template = show available templates)
-  - '*brainstorm {topic}" - Facilitate structured brainstorming session'
+  - brainstorm {topic}: Facilitate structured brainstorming session
-  - '*research {topic}" - Generate deep research prompt for investigation'
+  - research {topic}: Generate deep research prompt for investigation
-  - '*elicit" - Run advanced elicitation to clarify requirements'
+  - elicit: Run advanced elicitation to clarify requirements
-  - '*exit" - Say goodbye as the Business Analyst, and then abandon inhabiting this persona'
+  - exit: Say goodbye as the Business Analyst, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - brainstorming-techniques
@@ -246,7 +245,7 @@ dependencies:
 
 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
@@ -276,10 +275,10 @@ persona:
 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'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - (Default) Deep conversation with advanced-elicitation'
+  - chat-mode: (Default) Deep conversation with advanced-elicitation
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - create-doc {template}: Create doc (no template = show available templates)
-  - '*exit" - Say goodbye as the PM, and then abandon inhabiting this persona'
+  - exit: Say goodbye as the PM, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - create-doc
@@ -343,13 +342,13 @@ 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'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - (Default) UX consultation with advanced-elicitation for design decisions'
+  - chat-mode: (Default) UX consultation with advanced-elicitation for design decisions
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - create-doc {template}: Create doc (no template = show available templates)
-  - '*generate-ui-prompt" - Create AI frontend generation prompt'
+  - generate-ui-prompt: Create AI frontend generation prompt
-  - '*research {topic}" - Generate deep research prompt for UX investigation'
+  - research {topic}: Generate deep research prompt for UX investigation
-  - '*execute-checklist {checklist}" - Run design validation checklist'
+  - execute-checklist {checklist}: Run design validation checklist
-  - '*exit" - Say goodbye as the UX Expert, and then abandon inhabiting this persona'
+  - exit: Say goodbye as the UX Expert, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - generate-ai-frontend-prompt
@@ -403,12 +402,12 @@ startup:
   - Greet the user with your name and role, and inform of the *help command.
   - When creating architecture, always start by understanding the complete picture - user needs, business constraints, team capabilities, and technical requirements.
 commands:
-  - '*help" - Show: numbered list of the following commands to allow selection'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - (Default) Architect consultation with advanced-elicitation for complex system design'
+  - chat-mode: (Default) Architect consultation with advanced-elicitation for complex system design
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - create-doc {template}: Create doc (no template = show available templates)
-  - '*execute-checklist {checklist}" - Run architectural validation checklist'
+  - execute-checklist {checklist}: Run architectural validation checklist
-  - '*research {topic}" - Generate deep research prompt for architectural decisions'
+  - research {topic}: Generate deep research prompt for architectural decisions
-  - '*exit" - Say goodbye as the Architect, and then abandon inhabiting this persona'
+  - exit: Say goodbye as the Architect, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - create-doc
@@ -434,7 +433,7 @@ dependencies:
 
 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
@@ -466,15 +465,15 @@ persona:
 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'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - (Default) Product Owner consultation with advanced-elicitation'
+  - chat-mode: (Default) Product Owner consultation with advanced-elicitation
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - create-doc {template}: Create doc (no template = show available templates)
-  - '*execute-checklist {checklist}" - Run validation checklist (default->po-master-checklist)'
+  - execute-checklist {checklist}: Run validation checklist (default->po-master-checklist)
-  - '*shard-doc {document}" - Break down document into actionable parts'
+  - shard-doc {document}: Break down document into actionable parts
-  - '*correct-course" - Analyze and suggest project course corrections'
+  - correct-course: Analyze and suggest project course corrections
-  - '*create-epic" - Create epic for brownfield projects (task brownfield-create-epic)'
+  - create-epic: Create epic for brownfield projects (task brownfield-create-epic)
-  - '*create-story" - Create user story from requirements (task brownfield-create-story)'
+  - create-story: Create user story from requirements (task brownfield-create-story)
-  - '*exit" - Say Goodbye, You are no longer this Agent'
+  - exit: Say goodbye as the Product Owner, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - execute-checklist
@@ -679,6 +678,60 @@ BMAD-METHOD (Breakthrough Method of Agile AI-driven Development) is a framework
 - **Reusable Resources**: Portable templates, tasks, and checklists
 - **Slash Command Integration**: Quick agent switching and control
 
+### When to Use BMAD
+
+- **New Projects (Greenfield)**: Complete end-to-end development
+- **Existing Projects (Brownfield)**: Feature additions and enhancements
+- **Team Collaboration**: Multiple roles working together
+- **Quality Assurance**: Structured testing and validation
+- **Documentation**: Professional PRDs, architecture docs, user stories
+
+## Getting Started
+
+### Quick Start Options
+
+#### Option 1: Web UI
+**Best for**: ChatGPT, Claude, Gemini users who want to start immediately
+
+1. Navigate to `dist/teams/`
+2. Copy `team-fullstack.txt` content
+3. Create new Gemini Gem or CustomGPT
+4. Upload file with instructions: "Your critical operating instructions are attached, do not break character as directed"
+5. Type `/help` to see available commands
+
+#### Option 2: IDE Integration
+**Best for**: Cursor, Claude Code, Windsurf, VS Code users
+
+```bash
+# Interactive installation (recommended)
+npx bmad-method install
+```
+
+**Installation Steps**:
+- Choose "Complete installation"
+- Select your IDE (Cursor, Claude Code, Windsurf, or Roo Code)
+
+**Verify Installation**:
+- `.bmad-core/` folder created with all agents
+- IDE-specific integration files created
+- All agent commands/rules/modes available
+
+### Environment Selection Guide
+
+**Use Web UI for**:
+- Initial planning and documentation (PRD, architecture)
+- Cost-effective document creation (especially with Gemini)
+- Brainstorming and analysis phases
+- Multi-agent consultation and planning
+
+**Use IDE for**:
+- Active development and coding
+- File operations and project integration
+- Document sharding and story management
+- Implementation workflow (SM/Dev cycles)
+
+**Cost-Saving Tip**: Create large documents (PRDs, architecture) in web UI, then copy to `docs/prd.md` and `docs/architecture.md` in your project before switching to IDE for development.
+
 ## Core Philosophy
 
 ### Vibe CEO'ing
@@ -700,18 +753,345 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
 7. **START_SMALL_SCALE_FAST**: Test concepts, then expand.
 8. **EMBRACE_THE_CHAOS**: Adapt and overcome challenges.
 
-## IDE Development Workflow
+### Key Workflow Principles
 
-1. Shard the PRD (And Architecture documents if they exist also based on workflow type) using the Doc Shard task. The BMad-Master agent can help you do this. You will select the task, provide the doc to shard and the output folder. for example: `BMad Master, please Shard the docs/prd.md to the doc/prd/ folder` - this should ask you to use the md-tree-parser which is recommended, but either way shoudl result in multiple documents being created in the folder docs/prd.
+1. **Agent Specialization**: Each agent has specific expertise and responsibilities
-2. If you have fullstack, front end and or back end architecture documents you will want to follow the same thing, but shard all of these to an architecture folder instead of a prd folder.
+2. **Clean Handoffs**: Always start fresh when switching between agents
-3. Ensure that you have at least one epic-n.md file in your prd folder, with the stories in order to develop.
+3. **Status Tracking**: Maintain story statuses (Draft → Approved → InProgress → Done)
-4. The docs or architecture folder or prd folder should have a source tree document and coding standards at a minimum. These are used by the dev agent, and the many other sharded docs are used by the SM agent.
+4. **Iterative Development**: Complete one story before starting the next
-5. Use a new chat window to allow the SM agent to `draft the next story`.
+5. **Documentation First**: Always start with solid PRD and architecture
-6. If you agree the story is correct, mark it as approved in the status field, and then start a new chat window with the dev agent.
-7. Ask the dev agent to implement the next story. If you draft the story file into the chat it will save time for the dev to have to find what the next one is. The dev should follow the tasks and subtasks marking them off as they are completed. The dev agent will also leave notes potentially for the SM to know about any deviations that might have occured to help draft the next story.
-8. Once complete and you have verified, mark it done, and start a new chat. Ask the SM to draft the next story - repeating the cycle.
 
-With this work flow, there is only 1 story in progress at a time, worked sequentially.
+## Agent System
+
+### Core Development Team
+
+| Agent       | Role               | Primary Functions                       | When to Use                            |
+| ----------- | ------------------ | --------------------------------------- | -------------------------------------- |
+| `analyst`   | Business Analyst   | Market research, requirements gathering | Project planning, competitive analysis |
+| `pm`        | Product Manager    | PRD creation, feature prioritization    | Strategic planning, roadmaps           |
+| `architect` | Solution Architect | System design, technical architecture   | Complex systems, scalability planning  |
+| `dev`       | Developer          | Code implementation, debugging          | All development tasks                  |
+| `qa`        | QA Specialist      | Test planning, quality assurance        | Testing strategies, bug validation     |
+| `ux-expert` | UX Designer        | UI/UX design, prototypes                | User experience, interface design      |
+| `po`        | Product Owner      | Backlog management, story validation    | Story refinement, acceptance criteria  |
+| `sm`        | Scrum Master       | Sprint planning, story creation         | Project management, workflow           |
+
+### Meta Agents
+
+| Agent               | Role             | Primary Functions                     | When to Use                       |
+| ------------------- | ---------------- | ------------------------------------- | --------------------------------- |
+| `bmad-orchestrator` | Team Coordinator | Multi-agent workflows, role switching | Complex multi-role tasks          |
+| `bmad-master`       | Universal Expert | All capabilities without switching    | Single-session comprehensive work |
+
+### Agent Interaction Commands
+
+#### IDE-Specific Syntax
+
+**Agent Loading by IDE**:
+- **Claude Code**: `/agent-name` (e.g., `/bmad-master`)
+- **Cursor**: `@agent-name` (e.g., `@bmad-master`)
+- **Windsurf**: `@agent-name` (e.g., `@bmad-master`)
+- **Roo Code**: Select mode from mode selector (e.g., `bmad-bmad-master`)
+
+**Chat Management Guidelines**:
+- **Claude Code, Cursor, Windsurf**: Start new chats when switching agents
+- **Roo Code**: Switch modes within the same conversation
+
+**Common Task Commands**:
+- `*help` - Show available commands
+- `*status` - Show current context/progress
+- `*exit` - Exit the agent mode
+- `*shard-doc docs/prd.md prd` - Shard PRD into manageable pieces
+- `*shard-doc docs/architecture.md architecture` - Shard architecture document
+- `*create` - Run create-next-story task (SM agent)
+
+**In Web UI**:
+```text
+/pm create-doc prd
+/architect review system design
+/dev implement story 1.2
+/help - Show available commands
+/switch agent-name - Change active agent (if orchestrator available)
+```
+
+## Team Configurations
+
+### Pre-Built Teams
+
+#### Team All
+- **Includes**: All 10 agents + orchestrator
+- **Use Case**: Complete projects requiring all roles
+- **Bundle**: `team-all.txt`
+
+#### Team Fullstack
+- **Includes**: PM, Architect, Developer, QA, UX Expert
+- **Use Case**: End-to-end web/mobile development
+- **Bundle**: `team-fullstack.txt`
+
+#### Team No-UI
+- **Includes**: PM, Architect, Developer, QA (no UX Expert)
+- **Use Case**: Backend services, APIs, system development
+- **Bundle**: `team-no-ui.txt`
+
+## Core Architecture
+
+### System Overview
+
+The BMAD-Method is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
+
+### Key Architectural Components
+
+#### 1. Agents (`bmad-core/agents/`)
+- **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.)
+- **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies
+- **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use
+- **Startup Instructions**: Can load project-specific documentation for immediate context
+
+#### 2. Agent Teams (`bmad-core/agent-teams/`)
+- **Purpose**: Define collections of agents bundled together for specific purposes
+- **Examples**: `team-all.yml` (comprehensive bundle), `team-fullstack.yml` (full-stack development)
+- **Usage**: Creates pre-packaged contexts for web UI environments
+
+#### 3. Workflows (`bmad-core/workflows/`)
+- **Purpose**: YAML files defining prescribed sequences of steps for specific project types
+- **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development
+- **Structure**: Defines agent interactions, artifacts created, and transition conditions
+
+#### 4. Reusable Resources
+- **Templates** (`bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories
+- **Tasks** (`bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story"
+- **Checklists** (`bmad-core/checklists/`): Quality assurance checklists for validation and review
+- **Data** (`bmad-core/data/`): Core knowledge base and technical preferences
+
+### Dual Environment Architecture
+
+#### IDE Environment
+
+- Users interact directly with agent markdown files
+- Agents can access all dependencies dynamically
+- Supports real-time file operations and project integration
+- Optimized for development workflow execution
+
+#### Web UI Environment
+
+- Uses pre-built bundles from `dist/teams` for stand alone 1 upload files for all agents and their assest with an orchestrating agent
+- Single text files containing all agent dependencies are in `dist/agents/` - these are unnecessary unless you want to create a web agent that is only a single agent and not a team
+- Created by the web-builder tool for upload to web interfaces
+- Provides complete context in one package
+
+### Template Processing System
+
+BMAD employs a sophisticated template system with three key components:
+
+1. **Template Format** (`utils/template-format.md`): Defines markup language for variable substitution and AI processing directives
+2. **Document Creation** (`tasks/create-doc.md`): Orchestrates template selection and user interaction
+3. **Advanced Elicitation** (`tasks/advanced-elicitation.md`): Provides interactive refinement through structured brainstorming
+
+**Template Features**:
+
+- **Self-contained**: Templates embed both output structure and processing instructions
+- **Variable Substitution**: `{{placeholders}}` for dynamic content
+- **AI Processing Directives**: `[[LLM: instructions]]` for AI-only processing
+- **Interactive Refinement**: Built-in elicitation processes for quality improvement
+
+### Technical Preferences Integration
+
+The `technical-preferences.md` file serves as a persistent technical profile that:
+- Ensures consistency across all agents and projects
+- Eliminates repetitive technology specification
+- Provides personalized recommendations aligned with user preferences
+- Evolves over time with lessons learned
+
+### Build and Delivery Process
+
+The `web-builder.js` tool creates web-ready bundles by:
+1. Reading agent or team definition files
+2. Recursively resolving all dependencies
+3. Concatenating content into single text files with clear separators
+4. Outputting ready-to-upload bundles for web AI interfaces
+
+This architecture enables seamless operation across environments while maintaining the rich, interconnected agent ecosystem that makes BMAD powerful.
+
+## Complete Development Workflow
+
+### Planning Phase (Web UI Recommended)
+
+**Ideal for cost efficiency, especially with Gemini:**
+
+1. **Optional Analysis**: `/analyst` - Market research, competitive analysis
+2. **Project Brief**: Create foundation document (Analyst or user)
+3. **PRD Creation**: `/pm create-doc prd` - Comprehensive product requirements
+4. **Architecture Design**: `/architect create-doc architecture` - Technical foundation
+5. **Validation & Alignment**: `/po` run master checklist to ensure document consistency
+6. **Document Preparation**: Copy final documents to project as `docs/prd.md` and `docs/architecture.md`
+
+#### Example Planning Prompts
+
+**For PRD Creation**:
+```text
+"I want to build a [type] application that [core purpose].
+Help me brainstorm features and create a comprehensive PRD."
+```
+
+**For Architecture Design**:
+```text
+"Based on this PRD, design a scalable technical architecture
+that can handle [specific requirements]."
+```
+
+### Critical Transition: Web UI to IDE
+
+**Once planning is complete, you MUST switch to IDE for development:**
+
+- **Why**: Development workflow requires file operations, real-time project integration, and document sharding
+- **Cost Benefit**: Web UI is more cost-effective for large document creation; IDE is optimized for development tasks
+- **Required Files**: Ensure `docs/prd.md` and `docs/architecture.md` exist in your project
+
+### IDE Development Workflow
+
+**Prerequisites**: Planning documents must exist in `docs/` folder
+
+1. **Document Sharding**: 
+   - `@bmad-master` or `@po` shard `docs/prd.md` to `docs/prd/` folder
+   - If architecture exists, shard to `docs/architecture/` folder
+   - Results in multiple manageable documents and epic files
+
+2. **Verify Sharded Content**:
+   - At least one `epic-n.md` file in `docs/prd/` with stories in development order
+   - Source tree document and coding standards for dev agent reference
+   - Sharded docs for SM agent story creation
+
+**Resulting Folder Structure**:
+- `docs/prd/` - Broken down PRD sections
+- `docs/architecture/` - Broken down architecture sections
+- `docs/stories/` - Generated user stories
+
+3. **Development Cycle** (Sequential, one story at a time):
+
+   **Step 1 - Story Creation**: New chat window → `@sm` → `*create`
+   - SM executes create-next-story task
+   - Review generated story in `docs/stories/`
+   - Update status from "Draft" to "Approved"
+   
+   **Step 2 - Story Implementation**: New chat window → `@dev`
+   - Agent asks which story to implement
+   - Include story file content to save dev agent lookup time
+   - Dev follows tasks/subtasks, marking completion
+   - Dev leaves notes for SM about any deviations
+   - Update status to "Done"
+   
+   **Step 3 - Repeat**: Continue SM → Dev cycle until all epic stories complete
+
+**Important**: Only 1 story in progress at a time, worked sequentially until all epic stories complete.
+
+### Status Tracking Workflow
+
+Stories progress through defined statuses:
+- **Draft** → **Approved** → **InProgress** → **Done**
+
+Each status change requires user verification and approval before proceeding.
+
+### Workflow Types
+
+#### Greenfield Development
+- Business analysis and market research
+- Product requirements and feature definition  
+- System architecture and design
+- Development execution
+- Testing and deployment
+
+#### Brownfield Enhancement
+- Current system analysis
+- Enhancement planning
+- Impact assessment
+- Incremental development
+- Integration testing
+
+## Document Creation Best Practices
+
+### Required File Naming for Framework Integration
+
+- `docs/prd.md` - Product Requirements Document
+- `docs/architecture.md` - System Architecture Document
+
+**Why These Names Matter**:
+- Agents automatically reference these files during development
+- Sharding tasks expect these specific filenames
+- Workflow automation depends on standard naming
+
+### Cost-Effective Document Creation Workflow
+
+**Recommended for Large Documents (PRD, Architecture):**
+
+1. **Use Web UI**: Create documents in web interface for cost efficiency
+2. **Copy Final Output**: Save complete markdown to your project
+3. **Standard Names**: Save as `docs/prd.md` and `docs/architecture.md`
+4. **Switch to IDE**: Use IDE agents for development and smaller documents
+
+### Document Sharding
+
+Templates with Level 2 headings (`##`) can be automatically sharded:
+
+**Original PRD**:
+```markdown
+## Goals and Background Context
+## Requirements  
+## User Interface Design Goals
+## Success Metrics
+```
+
+**After Sharding**:
+- `docs/prd/goals-and-background-context.md`
+- `docs/prd/requirements.md`
+- `docs/prd/user-interface-design-goals.md`
+- `docs/prd/success-metrics.md`
+
+Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic sharding.
+
+## Usage Patterns and Best Practices
+
+### Environment-Specific Usage
+
+**Web UI Best For**:
+- Initial planning and documentation phases
+- Cost-effective large document creation
+- Agent consultation and brainstorming
+- Multi-agent workflows with orchestrator
+
+**IDE Best For**:
+- Active development and implementation
+- File operations and project integration
+- Story management and development cycles
+- Code review and debugging
+
+### Quality Assurance
+
+- Use appropriate agents for specialized tasks
+- Follow Agile ceremonies and review processes
+- Maintain document consistency with PO agent
+- Regular validation with checklists and templates
+
+### Performance Optimization
+
+- Use specific agents vs. `bmad-master` for focused tasks
+- Choose appropriate team size for project needs
+- Leverage technical preferences for consistency
+- Regular context management and cache clearing
+
+## Success Tips
+
+- **Use Gemini for big picture planning** - The team-fullstack bundle provides collaborative expertise
+- **Use bmad-master for document organization** - Sharding creates manageable chunks
+- **Follow the SM → Dev cycle religiously** - This ensures systematic progress
+- **Keep conversations focused** - One agent, one task per conversation
+- **Review everything** - Always review and approve before marking complete
+
+## Getting Help
+
+- **Commands**: Use `/help` in any environment to see available commands
+- **Agent Switching**: Use `/switch agent-name` with orchestrator for role changes
+- **Documentation**: Check `docs/` folder for project-specific context
+- **Community**: Discord and GitHub resources available for support
 ==================== END: data#bmad-kb ====================
 
 ==================== START: utils#workflow-management ====================
@@ -764,7 +1144,7 @@ Available workflows for [Team Name]:
 [... etc. ...]
 
 Use /workflow-start {number or id} to begin a workflow.
-```text
+```
 
 ### /workflow-start {workflow-id}
 
@@ -790,7 +1170,7 @@ In Progress:
     - Create PRD (John) - awaiting input
 
 Next: Technical Architecture
-```text
+```
 
 ### /workflow-resume
 
@@ -806,7 +1186,7 @@ BMad: I see you've completed Discovery and part of Product Planning.
       - UX Strategy with Sally (ux-expert)
 
       Would you like me to load Sally to continue?
-```text
+```
 
 ### /workflow-next
 
@@ -876,7 +1256,7 @@ BMad: I see you have a PRD and architecture document. Based on these artifacts,
       - Load Sarah (Product Owner) to validate all artifacts
 
       Would you like to continue with this workflow?
-```text
+```
 
 ## Workflow Context Passing
 
@@ -902,7 +1282,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
 
@@ -1517,6 +1897,8 @@ Present these numbered options to the user:
 ==================== START: templates#project-brief-tmpl ====================
 # Project Brief: {{Project Name}}
 
+[[LLM: The default path and filename unless specified is docs/brief.md]]
+
 [[LLM: This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development.
 
 Start by asking the user which mode they prefer:
@@ -1748,6 +2130,8 @@ These replace the standard elicitation options when working on project brief doc
 ==================== START: templates#market-research-tmpl ====================
 # Market Research Report: {{Project/Product Name}}
 
+[[LLM: The default path and filename unless specified is docs/market-research.md]]
+
 [[LLM: This template guides the creation of a comprehensive market research report. Begin by understanding what market insights the user needs and why. Work through each section systematically, using the appropriate analytical frameworks based on the research objectives.]]
 
 ## Executive Summary
@@ -2012,6 +2396,8 @@ These replace the standard elicitation options when working on market research d
 ==================== START: templates#competitor-analysis-tmpl ====================
 # Competitive Analysis Report: {{Project/Product Name}}
 
+[[LLM: The default path and filename unless specified is docs/competitor-analysis.md]]
+
 [[LLM: This template guides comprehensive competitor analysis. Start by understanding the user's competitive intelligence needs and strategic objectives. Help them identify and prioritize competitors before diving into detailed analysis.]]
 
 ## Executive Summary
@@ -2905,7 +3291,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
 
@@ -2969,6 +3355,8 @@ Document sharded successfully:
 ==================== START: templates#prd-tmpl ====================
 # {{Project Name}} Product Requirements Document (PRD)
 
+[[LLM: The default path and filename unless specified is docs/prd.md]]
+
 [[LLM: If available, review any provided document or ask if any are optionally available: Project Brief]]
 
 ## Goals and Background Context
@@ -3172,6 +3560,8 @@ so that {{benefit}}.
 ==================== START: templates#brownfield-prd-tmpl ====================
 # {{Project Name}} Brownfield Enhancement PRD
 
+[[LLM: The default path and filename unless specified is docs/prd.md]]
+
 [[LLM: IMPORTANT - SCOPE ASSESSMENT REQUIRED:
 
 This PRD is for SIGNIFICANT enhancements to existing projects that require comprehensive planning and multiple stories. Before proceeding:
@@ -4038,6 +4428,8 @@ You will now synthesize the inputs and the above principles into a final, compre
 ==================== START: templates#front-end-spec-tmpl ====================
 # {{Project Name}} UI/UX Specification
 
+[[LLM: The default path and filename unless specified is docs/front-end-spec.md]]
+
 [[LLM: Review provided documents including Project Brief, PRD, and any user research to gather context. Focus on understanding user needs, pain points, and desired outcomes before beginning the specification.]]
 
 ## Introduction
@@ -4114,7 +4506,7 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 
 ```mermaid
 {{sitemap_diagram}}
-```text
+```
 
 @{example: sitemap}
 
@@ -4846,6 +5238,8 @@ Present a summary of what was created and ask if any additional documentation wo
 
 [[LLM: If available, review any provided relevant documents to gather all relevant context before beginning. If at a minimum you cannot local `docs/prd.md` ask the user what docs will provide the basis for the architecture.]]
 
+[[LLM: The default path and filename unless specified is docs/architecture.md]]
+
 ## Introduction
 
 [[LLM: This section establishes the document's purpose and scope. Keep the content below but ensure project name is properly substituted.
@@ -5199,7 +5593,7 @@ servers:
       '[object Object]': null
     description:
       '[object Object]': null
-```text
+```
 
 ^^/CONDITION: has_rest_api^^
 
@@ -5262,7 +5656,6 @@ 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/
@@ -5274,6 +5667,7 @@ project-root/
 ├── scripts/ # Monorepo management scripts
 └── package.json # Root package.json with workspaces
 @{/example}
+```
 
 [[LLM: After presenting the source tree structure, apply `tasks#advanced-elicitation` protocol]]
 
@@ -5621,6 +6015,8 @@ Note: Basic info goes in Coding Standards for dev agent. This detailed section i
 ==================== START: templates#front-end-architecture-tmpl ====================
 # {{Project Name}} Frontend Architecture Document
 
+[[LLM: The default path and filename unless specified is docs/ui-architecture.md]]
+
 [[LLM: Review provided documents including PRD, UX-UI Specification, and main Architecture Document. Focus on extracting technical implementation details needed for AI frontend tools and developer agents. Ask the user for any of these documents if you are unable to locate and were not provided.]]
 
 ## Template and Framework Selection
@@ -5797,6 +6193,8 @@ Document the starter template decision and any constraints it imposes before pro
 ==================== START: templates#fullstack-architecture-tmpl ====================
 # {{Project Name}} Fullstack Architecture Document
 
+[[LLM: The default path and filename unless specified is docs/architecture.md]]
+
 [[LLM: If available, review any provided relevant documents to gather all relevant context before beginning. At minimum, you should have access to docs/prd.md and docs/front-end-spec.md. Ask the user for any documents you need but cannot locate. This template creates a unified architecture that covers both backend and frontend concerns to guide AI-driven fullstack development.]]
 
 ## Introduction
@@ -6816,6 +7214,8 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 ==================== START: templates#brownfield-architecture-tmpl ====================
 # {{Project Name}} Brownfield Enhancement Architecture
 
+[[LLM: The default path and filename unless specified is docs/architecture.md]]
+
 [[LLM: IMPORTANT - SCOPE AND ASSESSMENT REQUIRED:
 
 This architecture document is for SIGNIFICANT enhancements to existing projects that require comprehensive architectural planning. Before proceeding:
@@ -7040,7 +7440,7 @@ Present component architecture and apply `tasks#advanced-elicitation` protocol]]
 
 ```mermaid
 {{component_interaction_diagram}}
-```text
+```
 
 ## API Design and Integration
 
@@ -7080,7 +7480,7 @@ Present API design and apply `tasks#advanced-elicitation` protocol]]
 
 ```json
 {{response_schema}}
-```text
+```
 
 <</REPEAT>>
 

dist/teams/team-ide-minimal.txt

@@ -52,9 +52,9 @@ workflows: null
 ==================== END: agent-teams#team-ide-minimal ====================
 
 ==================== START: agents#bmad-orchestrator ====================
-# bmad
+# bmad-orchestrator
 
-CRITICAL: Read the full YML to understand your operating params, start activation to alter your state of being, follow startup instructions, stay in this being until told to exit this mode:
+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
 agent:
@@ -86,9 +86,9 @@ startup:
   - If clear match to an agent's expertise, suggest transformation with *agent command
   - If project-oriented, suggest *workflow-guidance to explore options
   - Load resources only when needed - never pre-load
-commands:  # All commands require * prefix when used (e.g., *help, *agent pm)
+commands:
   help: Show this guide with available agents and workflows
-  chat-mode: Start conversational mode for detailed assistance  
+  chat-mode: Start conversational mode for detailed assistance
   kb-mode: Load full BMAD knowledge base
   status: Show current context, active agent, and progress
   agent: Transform into a specialized agent (list if name not specified)
@@ -103,41 +103,40 @@ commands:  # All commands require * prefix when used (e.g., *help, *agent pm)
 help-display-template: |
   === BMAD Orchestrator Commands ===
   All commands must start with * (asterisk)
-  
+
   Core 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
   *exit ............... Return to BMad or exit session
-  
+
   Agent & Task Management:
   *agent [name] ....... Transform into specialized agent (list if no name)
   *task [name] ........ Run specific task (list if no name, requires agent)
   *checklist [name] ... Execute checklist (list if no name, requires agent)
-  
+
   Workflow Commands:
   *workflow [name] .... Start specific workflow (list if no name)
   *workflow-guidance .. Get personalized help selecting the right workflow
-  
+
   Other Commands:
   *yolo ............... Toggle skip confirmations mode
   *party-mode ......... Group chat with all agents
   *doc-out ............ Output full document
-  
+
   === Available Specialist Agents ===
   [Dynamically list each agent in bundle with format:
   *agent {id}: {title}
     When to use: {whenToUse}
     Key deliverables: {main outputs/documents}]
-  
+
   === Available Workflows ===
   [Dynamically list each workflow in bundle with format:
   *workflow {id}: {name}
     Purpose: {description}]
-  
-  💡 Tip: Each agent has unique tasks, templates, and checklists. Switch to an agent to access their capabilities!
 
+  💡 Tip: Each agent has unique tasks, templates, and checklists. Switch to an agent to access their capabilities!
 fuzzy-matching:
   - 85% confidence threshold
   - Show numbered list if unsure
@@ -176,7 +175,7 @@ dependencies:
 
 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
@@ -208,15 +207,15 @@ persona:
 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'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - (Default) Product Owner consultation with advanced-elicitation'
+  - chat-mode: (Default) Product Owner consultation with advanced-elicitation
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - create-doc {template}: Create doc (no template = show available templates)
-  - '*execute-checklist {checklist}" - Run validation checklist (default->po-master-checklist)'
+  - execute-checklist {checklist}: Run validation checklist (default->po-master-checklist)
-  - '*shard-doc {document}" - Break down document into actionable parts'
+  - shard-doc {document}: Break down document into actionable parts
-  - '*correct-course" - Analyze and suggest project course corrections'
+  - correct-course: Analyze and suggest project course corrections
-  - '*create-epic" - Create epic for brownfield projects (task brownfield-create-epic)'
+  - create-epic: Create epic for brownfield projects (task brownfield-create-epic)
-  - '*create-story" - Create user story from requirements (task brownfield-create-story)'
+  - create-story: Create user story from requirements (task brownfield-create-story)
-  - '*exit" - Say Goodbye, You are no longer this Agent'
+  - exit: Say goodbye as the Product Owner, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - execute-checklist
@@ -242,7 +241,6 @@ CRITICAL: Read the full YML, start activation to alter your state of being, foll
 ```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:
@@ -258,31 +256,25 @@ persona:
   identity: Story creation expert who prepares detailed, actionable stories for AI developers
   focus: Creating crystal-clear stories that dumb AI agents can implement without confusion
   core_principles:
-    - Task Adherence - Rigorously follow create-next-story procedures
+    - Rigorously follow `create-next-story` procedure to generate the detailed user story
-    - Checklist-Driven Validation - Apply story-draft-checklist meticulously
+    - Will ensure all information comes from the PRD and Architecture to guide the dumb dev agent
-    - Clarity for Developer Handoff - Stories must be immediately actionable
+    - You are NOT allowed to implement stories or modify code EVER!
-    - Focus on One Story at a Time - Complete one before starting next
-    - Numbered Options Protocol - Always use numbered lists for selections
 startup:
-  - Greet the user with your name and role, and inform of the *help command.
+  - Greet the user with your name and role, and inform of the *help command and then HALT to await instruction if not given already.
-  - CRITICAL: Do NOT automatically execute create-next-story tasks during startup
-  - CRITICAL: Do NOT create or modify any files during startup
   - Offer to help with story preparation but wait for explicit user confirmation
   - Only execute tasks when user explicitly requests them
-  - 'CRITICAL RULE: You are ONLY allowed to create/modify story files - NEVER implement! If asked to implement, tell user they MUST switch to Dev Agent'
 commands:
-  - '*help" - Show: numbered list of the following commands to allow selection'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - Conversational mode with advanced-elicitation for advice'
+  - chat-mode: Conversational mode with advanced-elicitation for advice
-  - '*create" - Execute all steps in Create Next Story Task document'
+  - create|draft: Execute create-next-story
-  - '*pivot" - Run correct-course task (ensure no story already created first)'
+  - pivot: Execute `correct-course` task
-  - '*checklist {checklist}" - Show numbered list of checklists, execute selection'
+  - checklist {checklist}: Show numbered list of checklists, execute selection
-  - '*doc-shard {PRD|Architecture|Other}" - Execute shard-doc task'
+  - exit: Say goodbye as the Scrum Master, and then abandon inhabiting this persona
-  - '*index-docs" - Update documentation index in /docs/index.md'
-  - '*exit" - Say goodbye as the Scrum Master, and then abandon inhabiting this persona'
 dependencies:
   tasks:
     - create-next-story
     - execute-checklist
+    - course-correct
   templates:
     - story-tmpl
   checklists:
@@ -297,66 +289,50 @@ dependencies:
 
 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
 agent:
   name: James
   id: dev
   title: Full Stack Developer
   icon: 💻
-  whenToUse: "Use for code implementation, debugging, refactoring, and development best practices"
+  whenToUse: Use for code implementation, debugging, refactoring, and development best practices
-  customization:
+  customization: null
-
+startup:
+  - Announce: Greet the user with your name and role, and inform of the *help command.
+  - CRITICAL: Load .bmad-core/core-config.yml and read devLoadAlwaysFiles list and devDebugLog values
+  - CRITICAL: Load ONLY files specified in devLoadAlwaysFiles. If any missing, inform user but continue
+  - CRITICAL: Do NOT load any story files during startup unless user requested you do
+  - CRITICAL: Do NOT begin development until told to proceed
 persona:
   role: Expert Senior Software Engineer & Implementation Specialist
   style: Extremely concise, pragmatic, detail-oriented, solution-focused
   identity: Expert who implements stories by reading requirements and executing tasks sequentially with comprehensive testing
   focus: Executing story tasks with precision, updating Dev Agent Record sections only, maintaining minimal context overhead
-
 core_principles:
   - CRITICAL: Story-Centric - Story has ALL info. NEVER load PRD/architecture/other docs files unless explicitly directed in dev notes
-  - CRITICAL: Load Standards - MUST load docs/architecture/coding-standards.md into core memory at startup
+  - CRITICAL: Dev Record Only - ONLY update story file Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
-  - CRITICAL: Dev Record Only - ONLY update Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
+  - Strive for Sequential Task Execution - Complete tasks 1-by-1 and mark [x] as completed
-  - Sequential Execution - Complete tasks 1-by-1 in order. Mark [x] before next. No skipping
   - Test-Driven Quality - Write tests alongside code. Task incomplete without passing tests
-  - Debug Log Discipline - Log temp changes to table. Revert after fix. Keep story lean
+  - Debug Log Discipline - Log temp changes to md table in devDebugLog. Revert after fix.
   - Block Only When Critical - HALT for: missing approval/ambiguous reqs/3 failures/missing config
-  - Code Excellence - Clean, secure, maintainable code per coding-standards.md
+  - Code Excellence - Clean, secure, maintainable code per loaded standards
   - Numbered Options - Always use numbered lists when presenting choices
-
-startup:
-  - Announce: Greet the user with your name and role, and inform of the *help command.
-  - CRITICAL: Do NOT load any story files or coding-standards.md during startup
-  - CRITICAL: Do NOT scan docs/stories/ directory automatically
-  - CRITICAL: Do NOT begin any tasks automatically
-  - Wait for user to specify story or ask for story selection
-  - Only load files and begin work when explicitly requested by user
-
 commands:
-  - "*help" - Show commands
+  - help: Show numbered list of the following commands to allow selection
-  - "*chat-mode" - Conversational mode
+  - run-tests: Execute linting and tests
-  - "*run-tests" - Execute linting+tests
+  - debug-log: Show debug entries
-  - "*lint" - Run linting only
+  - complete-story: Finalize to "Review"
-  - "*dod-check" - Run story-dod-checklist
+  - exit: Say goodbye as the Developer, and then abandon inhabiting this persona
-  - "*status" - Show task progress
-  - "*debug-log" - Show debug entries
-  - "*complete-story" - Finalize to "Review"
-  - "*exit" - Leave developer mode
-
 task-execution:
-  flow: "Read task→Implement→Write tests→Pass tests→Update [x]→Next task"
+  flow: Read task→Implement→Write tests→Pass tests→Update [x]→Next task
-
   updates-ONLY:
-    - "Checkboxes: [ ] not started | [-] in progress | [x] complete"
+    - 'Checkboxes: [ ] not started | [-] in progress | [x] complete'
-    - "Debug Log: | Task | File | Change | Reverted? |"
+    - 'Debug Log: | Task | File | Change | Reverted? |'
-    - "Completion Notes: Deviations only, <50 words"
+    - 'Completion Notes: Deviations only, <50 words'
-    - "Change Log: Requirement changes only"
+    - 'Change Log: Requirement changes only'
-
+  blocking: Unapproved deps | Ambiguous after story check | 3 failures | Missing config
-  blocking: "Unapproved deps | Ambiguous after story check | 3 failures | Missing config"
+  done: Code matches reqs + Tests pass + Follows standards + No lint errors
-
+  completion: All [x]→Lint→Tests(100%)→Integration(if noted)→Coverage(80%+)→E2E(if noted)→DoD→Summary→HALT
-  done: "Code matches reqs + Tests pass + Follows standards + No lint errors"
-
-  completion: "All [x]→Lint→Tests(100%)→Integration(if noted)→Coverage(80%+)→E2E(if noted)→DoD→Summary→HALT"
-
 dependencies:
   tasks:
     - execute-checklist
@@ -402,10 +378,10 @@ persona:
 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'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - (Default) QA consultation with advanced-elicitation for test strategy'
+  - chat-mode: (Default) QA consultation with advanced-elicitation for test strategy
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - create-doc {template}: Create doc (no template = show available templates)
-  - '*exit" - Say goodbye as the QA Test Architect, and then abandon inhabiting this persona'
+  - exit: Say goodbye as the QA Test Architect, and then abandon inhabiting this persona
 dependencies:
   data:
     - technical-preferences
@@ -601,6 +577,60 @@ BMAD-METHOD (Breakthrough Method of Agile AI-driven Development) is a framework
 - **Reusable Resources**: Portable templates, tasks, and checklists
 - **Slash Command Integration**: Quick agent switching and control
 
+### When to Use BMAD
+
+- **New Projects (Greenfield)**: Complete end-to-end development
+- **Existing Projects (Brownfield)**: Feature additions and enhancements
+- **Team Collaboration**: Multiple roles working together
+- **Quality Assurance**: Structured testing and validation
+- **Documentation**: Professional PRDs, architecture docs, user stories
+
+## Getting Started
+
+### Quick Start Options
+
+#### Option 1: Web UI
+**Best for**: ChatGPT, Claude, Gemini users who want to start immediately
+
+1. Navigate to `dist/teams/`
+2. Copy `team-fullstack.txt` content
+3. Create new Gemini Gem or CustomGPT
+4. Upload file with instructions: "Your critical operating instructions are attached, do not break character as directed"
+5. Type `/help` to see available commands
+
+#### Option 2: IDE Integration
+**Best for**: Cursor, Claude Code, Windsurf, VS Code users
+
+```bash
+# Interactive installation (recommended)
+npx bmad-method install
+```
+
+**Installation Steps**:
+- Choose "Complete installation"
+- Select your IDE (Cursor, Claude Code, Windsurf, or Roo Code)
+
+**Verify Installation**:
+- `.bmad-core/` folder created with all agents
+- IDE-specific integration files created
+- All agent commands/rules/modes available
+
+### Environment Selection Guide
+
+**Use Web UI for**:
+- Initial planning and documentation (PRD, architecture)
+- Cost-effective document creation (especially with Gemini)
+- Brainstorming and analysis phases
+- Multi-agent consultation and planning
+
+**Use IDE for**:
+- Active development and coding
+- File operations and project integration
+- Document sharding and story management
+- Implementation workflow (SM/Dev cycles)
+
+**Cost-Saving Tip**: Create large documents (PRDs, architecture) in web UI, then copy to `docs/prd.md` and `docs/architecture.md` in your project before switching to IDE for development.
+
 ## Core Philosophy
 
 ### Vibe CEO'ing
@@ -622,18 +652,345 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
 7. **START_SMALL_SCALE_FAST**: Test concepts, then expand.
 8. **EMBRACE_THE_CHAOS**: Adapt and overcome challenges.
 
-## IDE Development Workflow
+### Key Workflow Principles
 
-1. Shard the PRD (And Architecture documents if they exist also based on workflow type) using the Doc Shard task. The BMad-Master agent can help you do this. You will select the task, provide the doc to shard and the output folder. for example: `BMad Master, please Shard the docs/prd.md to the doc/prd/ folder` - this should ask you to use the md-tree-parser which is recommended, but either way shoudl result in multiple documents being created in the folder docs/prd.
+1. **Agent Specialization**: Each agent has specific expertise and responsibilities
-2. If you have fullstack, front end and or back end architecture documents you will want to follow the same thing, but shard all of these to an architecture folder instead of a prd folder.
+2. **Clean Handoffs**: Always start fresh when switching between agents
-3. Ensure that you have at least one epic-n.md file in your prd folder, with the stories in order to develop.
+3. **Status Tracking**: Maintain story statuses (Draft → Approved → InProgress → Done)
-4. The docs or architecture folder or prd folder should have a source tree document and coding standards at a minimum. These are used by the dev agent, and the many other sharded docs are used by the SM agent.
+4. **Iterative Development**: Complete one story before starting the next
-5. Use a new chat window to allow the SM agent to `draft the next story`.
+5. **Documentation First**: Always start with solid PRD and architecture
-6. If you agree the story is correct, mark it as approved in the status field, and then start a new chat window with the dev agent.
-7. Ask the dev agent to implement the next story. If you draft the story file into the chat it will save time for the dev to have to find what the next one is. The dev should follow the tasks and subtasks marking them off as they are completed. The dev agent will also leave notes potentially for the SM to know about any deviations that might have occured to help draft the next story.
-8. Once complete and you have verified, mark it done, and start a new chat. Ask the SM to draft the next story - repeating the cycle.
 
-With this work flow, there is only 1 story in progress at a time, worked sequentially.
+## Agent System
+
+### Core Development Team
+
+| Agent       | Role               | Primary Functions                       | When to Use                            |
+| ----------- | ------------------ | --------------------------------------- | -------------------------------------- |
+| `analyst`   | Business Analyst   | Market research, requirements gathering | Project planning, competitive analysis |
+| `pm`        | Product Manager    | PRD creation, feature prioritization    | Strategic planning, roadmaps           |
+| `architect` | Solution Architect | System design, technical architecture   | Complex systems, scalability planning  |
+| `dev`       | Developer          | Code implementation, debugging          | All development tasks                  |
+| `qa`        | QA Specialist      | Test planning, quality assurance        | Testing strategies, bug validation     |
+| `ux-expert` | UX Designer        | UI/UX design, prototypes                | User experience, interface design      |
+| `po`        | Product Owner      | Backlog management, story validation    | Story refinement, acceptance criteria  |
+| `sm`        | Scrum Master       | Sprint planning, story creation         | Project management, workflow           |
+
+### Meta Agents
+
+| Agent               | Role             | Primary Functions                     | When to Use                       |
+| ------------------- | ---------------- | ------------------------------------- | --------------------------------- |
+| `bmad-orchestrator` | Team Coordinator | Multi-agent workflows, role switching | Complex multi-role tasks          |
+| `bmad-master`       | Universal Expert | All capabilities without switching    | Single-session comprehensive work |
+
+### Agent Interaction Commands
+
+#### IDE-Specific Syntax
+
+**Agent Loading by IDE**:
+- **Claude Code**: `/agent-name` (e.g., `/bmad-master`)
+- **Cursor**: `@agent-name` (e.g., `@bmad-master`)
+- **Windsurf**: `@agent-name` (e.g., `@bmad-master`)
+- **Roo Code**: Select mode from mode selector (e.g., `bmad-bmad-master`)
+
+**Chat Management Guidelines**:
+- **Claude Code, Cursor, Windsurf**: Start new chats when switching agents
+- **Roo Code**: Switch modes within the same conversation
+
+**Common Task Commands**:
+- `*help` - Show available commands
+- `*status` - Show current context/progress
+- `*exit` - Exit the agent mode
+- `*shard-doc docs/prd.md prd` - Shard PRD into manageable pieces
+- `*shard-doc docs/architecture.md architecture` - Shard architecture document
+- `*create` - Run create-next-story task (SM agent)
+
+**In Web UI**:
+```text
+/pm create-doc prd
+/architect review system design
+/dev implement story 1.2
+/help - Show available commands
+/switch agent-name - Change active agent (if orchestrator available)
+```
+
+## Team Configurations
+
+### Pre-Built Teams
+
+#### Team All
+- **Includes**: All 10 agents + orchestrator
+- **Use Case**: Complete projects requiring all roles
+- **Bundle**: `team-all.txt`
+
+#### Team Fullstack
+- **Includes**: PM, Architect, Developer, QA, UX Expert
+- **Use Case**: End-to-end web/mobile development
+- **Bundle**: `team-fullstack.txt`
+
+#### Team No-UI
+- **Includes**: PM, Architect, Developer, QA (no UX Expert)
+- **Use Case**: Backend services, APIs, system development
+- **Bundle**: `team-no-ui.txt`
+
+## Core Architecture
+
+### System Overview
+
+The BMAD-Method is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
+
+### Key Architectural Components
+
+#### 1. Agents (`bmad-core/agents/`)
+- **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.)
+- **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies
+- **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use
+- **Startup Instructions**: Can load project-specific documentation for immediate context
+
+#### 2. Agent Teams (`bmad-core/agent-teams/`)
+- **Purpose**: Define collections of agents bundled together for specific purposes
+- **Examples**: `team-all.yml` (comprehensive bundle), `team-fullstack.yml` (full-stack development)
+- **Usage**: Creates pre-packaged contexts for web UI environments
+
+#### 3. Workflows (`bmad-core/workflows/`)
+- **Purpose**: YAML files defining prescribed sequences of steps for specific project types
+- **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development
+- **Structure**: Defines agent interactions, artifacts created, and transition conditions
+
+#### 4. Reusable Resources
+- **Templates** (`bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories
+- **Tasks** (`bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story"
+- **Checklists** (`bmad-core/checklists/`): Quality assurance checklists for validation and review
+- **Data** (`bmad-core/data/`): Core knowledge base and technical preferences
+
+### Dual Environment Architecture
+
+#### IDE Environment
+
+- Users interact directly with agent markdown files
+- Agents can access all dependencies dynamically
+- Supports real-time file operations and project integration
+- Optimized for development workflow execution
+
+#### Web UI Environment
+
+- Uses pre-built bundles from `dist/teams` for stand alone 1 upload files for all agents and their assest with an orchestrating agent
+- Single text files containing all agent dependencies are in `dist/agents/` - these are unnecessary unless you want to create a web agent that is only a single agent and not a team
+- Created by the web-builder tool for upload to web interfaces
+- Provides complete context in one package
+
+### Template Processing System
+
+BMAD employs a sophisticated template system with three key components:
+
+1. **Template Format** (`utils/template-format.md`): Defines markup language for variable substitution and AI processing directives
+2. **Document Creation** (`tasks/create-doc.md`): Orchestrates template selection and user interaction
+3. **Advanced Elicitation** (`tasks/advanced-elicitation.md`): Provides interactive refinement through structured brainstorming
+
+**Template Features**:
+
+- **Self-contained**: Templates embed both output structure and processing instructions
+- **Variable Substitution**: `{{placeholders}}` for dynamic content
+- **AI Processing Directives**: `[[LLM: instructions]]` for AI-only processing
+- **Interactive Refinement**: Built-in elicitation processes for quality improvement
+
+### Technical Preferences Integration
+
+The `technical-preferences.md` file serves as a persistent technical profile that:
+- Ensures consistency across all agents and projects
+- Eliminates repetitive technology specification
+- Provides personalized recommendations aligned with user preferences
+- Evolves over time with lessons learned
+
+### Build and Delivery Process
+
+The `web-builder.js` tool creates web-ready bundles by:
+1. Reading agent or team definition files
+2. Recursively resolving all dependencies
+3. Concatenating content into single text files with clear separators
+4. Outputting ready-to-upload bundles for web AI interfaces
+
+This architecture enables seamless operation across environments while maintaining the rich, interconnected agent ecosystem that makes BMAD powerful.
+
+## Complete Development Workflow
+
+### Planning Phase (Web UI Recommended)
+
+**Ideal for cost efficiency, especially with Gemini:**
+
+1. **Optional Analysis**: `/analyst` - Market research, competitive analysis
+2. **Project Brief**: Create foundation document (Analyst or user)
+3. **PRD Creation**: `/pm create-doc prd` - Comprehensive product requirements
+4. **Architecture Design**: `/architect create-doc architecture` - Technical foundation
+5. **Validation & Alignment**: `/po` run master checklist to ensure document consistency
+6. **Document Preparation**: Copy final documents to project as `docs/prd.md` and `docs/architecture.md`
+
+#### Example Planning Prompts
+
+**For PRD Creation**:
+```text
+"I want to build a [type] application that [core purpose].
+Help me brainstorm features and create a comprehensive PRD."
+```
+
+**For Architecture Design**:
+```text
+"Based on this PRD, design a scalable technical architecture
+that can handle [specific requirements]."
+```
+
+### Critical Transition: Web UI to IDE
+
+**Once planning is complete, you MUST switch to IDE for development:**
+
+- **Why**: Development workflow requires file operations, real-time project integration, and document sharding
+- **Cost Benefit**: Web UI is more cost-effective for large document creation; IDE is optimized for development tasks
+- **Required Files**: Ensure `docs/prd.md` and `docs/architecture.md` exist in your project
+
+### IDE Development Workflow
+
+**Prerequisites**: Planning documents must exist in `docs/` folder
+
+1. **Document Sharding**: 
+   - `@bmad-master` or `@po` shard `docs/prd.md` to `docs/prd/` folder
+   - If architecture exists, shard to `docs/architecture/` folder
+   - Results in multiple manageable documents and epic files
+
+2. **Verify Sharded Content**:
+   - At least one `epic-n.md` file in `docs/prd/` with stories in development order
+   - Source tree document and coding standards for dev agent reference
+   - Sharded docs for SM agent story creation
+
+**Resulting Folder Structure**:
+- `docs/prd/` - Broken down PRD sections
+- `docs/architecture/` - Broken down architecture sections
+- `docs/stories/` - Generated user stories
+
+3. **Development Cycle** (Sequential, one story at a time):
+
+   **Step 1 - Story Creation**: New chat window → `@sm` → `*create`
+   - SM executes create-next-story task
+   - Review generated story in `docs/stories/`
+   - Update status from "Draft" to "Approved"
+   
+   **Step 2 - Story Implementation**: New chat window → `@dev`
+   - Agent asks which story to implement
+   - Include story file content to save dev agent lookup time
+   - Dev follows tasks/subtasks, marking completion
+   - Dev leaves notes for SM about any deviations
+   - Update status to "Done"
+   
+   **Step 3 - Repeat**: Continue SM → Dev cycle until all epic stories complete
+
+**Important**: Only 1 story in progress at a time, worked sequentially until all epic stories complete.
+
+### Status Tracking Workflow
+
+Stories progress through defined statuses:
+- **Draft** → **Approved** → **InProgress** → **Done**
+
+Each status change requires user verification and approval before proceeding.
+
+### Workflow Types
+
+#### Greenfield Development
+- Business analysis and market research
+- Product requirements and feature definition  
+- System architecture and design
+- Development execution
+- Testing and deployment
+
+#### Brownfield Enhancement
+- Current system analysis
+- Enhancement planning
+- Impact assessment
+- Incremental development
+- Integration testing
+
+## Document Creation Best Practices
+
+### Required File Naming for Framework Integration
+
+- `docs/prd.md` - Product Requirements Document
+- `docs/architecture.md` - System Architecture Document
+
+**Why These Names Matter**:
+- Agents automatically reference these files during development
+- Sharding tasks expect these specific filenames
+- Workflow automation depends on standard naming
+
+### Cost-Effective Document Creation Workflow
+
+**Recommended for Large Documents (PRD, Architecture):**
+
+1. **Use Web UI**: Create documents in web interface for cost efficiency
+2. **Copy Final Output**: Save complete markdown to your project
+3. **Standard Names**: Save as `docs/prd.md` and `docs/architecture.md`
+4. **Switch to IDE**: Use IDE agents for development and smaller documents
+
+### Document Sharding
+
+Templates with Level 2 headings (`##`) can be automatically sharded:
+
+**Original PRD**:
+```markdown
+## Goals and Background Context
+## Requirements  
+## User Interface Design Goals
+## Success Metrics
+```
+
+**After Sharding**:
+- `docs/prd/goals-and-background-context.md`
+- `docs/prd/requirements.md`
+- `docs/prd/user-interface-design-goals.md`
+- `docs/prd/success-metrics.md`
+
+Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic sharding.
+
+## Usage Patterns and Best Practices
+
+### Environment-Specific Usage
+
+**Web UI Best For**:
+- Initial planning and documentation phases
+- Cost-effective large document creation
+- Agent consultation and brainstorming
+- Multi-agent workflows with orchestrator
+
+**IDE Best For**:
+- Active development and implementation
+- File operations and project integration
+- Story management and development cycles
+- Code review and debugging
+
+### Quality Assurance
+
+- Use appropriate agents for specialized tasks
+- Follow Agile ceremonies and review processes
+- Maintain document consistency with PO agent
+- Regular validation with checklists and templates
+
+### Performance Optimization
+
+- Use specific agents vs. `bmad-master` for focused tasks
+- Choose appropriate team size for project needs
+- Leverage technical preferences for consistency
+- Regular context management and cache clearing
+
+## Success Tips
+
+- **Use Gemini for big picture planning** - The team-fullstack bundle provides collaborative expertise
+- **Use bmad-master for document organization** - Sharding creates manageable chunks
+- **Follow the SM → Dev cycle religiously** - This ensures systematic progress
+- **Keep conversations focused** - One agent, one task per conversation
+- **Review everything** - Always review and approve before marking complete
+
+## Getting Help
+
+- **Commands**: Use `/help` in any environment to see available commands
+- **Agent Switching**: Use `/switch agent-name` with orchestrator for role changes
+- **Documentation**: Check `docs/` folder for project-specific context
+- **Community**: Discord and GitHub resources available for support
 ==================== END: data#bmad-kb ====================
 
 ==================== START: utils#workflow-management ====================
@@ -686,7 +1043,7 @@ Available workflows for [Team Name]:
 [... etc. ...]
 
 Use /workflow-start {number or id} to begin a workflow.
-```text
+```
 
 ### /workflow-start {workflow-id}
 
@@ -712,7 +1069,7 @@ In Progress:
     - Create PRD (John) - awaiting input
 
 Next: Technical Architecture
-```text
+```
 
 ### /workflow-resume
 
@@ -728,7 +1085,7 @@ BMad: I see you've completed Discovery and part of Product Planning.
       - UX Strategy with Sally (ux-expert)
 
       Would you like me to load Sally to continue?
-```text
+```
 
 ### /workflow-next
 
@@ -798,7 +1155,7 @@ BMad: I see you have a PRD and architecture document. Based on these artifacts,
       - Load Sarah (Product Owner) to validate all artifacts
 
       Would you like to continue with this workflow?
-```text
+```
 
 ## Workflow Context Passing
 
@@ -824,7 +1181,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
 
@@ -1106,7 +1463,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
 
@@ -2256,45 +2613,42 @@ Keep it action-oriented and forward-looking.]]
 
 To identify the next logical story based on project progress and epic definitions, and then to prepare a comprehensive, self-contained, and actionable story file using the `Story Template`. This task ensures the story is enriched with all necessary technical context, requirements, and acceptance criteria, making it ready for efficient implementation by a Developer Agent with minimal need for additional research.
 
-## Inputs for this Task
-
-- Access to the project's documentation repository, specifically:
-  - `docs/index.md` (hereafter "Index Doc")
-  - All Epic files - located in one of these locations:
-    - Primary: `docs/prd/epic-{n}-{description}.md` (e.g., `epic-1-foundation-core-infrastructure.md`)
-    - Secondary: `docs/epics/epic-{n}-{description}.md`
-    - User-specified location if not found in above paths
-  - Existing story files in `docs/stories/`
-  - Main PRD (hereafter "PRD Doc")
-  - Main Architecture Document (hereafter "Main Arch Doc")
-  - Frontend Architecture Document (hereafter "Frontend Arch Doc," if relevant)
-  - Project Structure Guide (`docs/project-structure.md`)
-  - Operational Guidelines Document (`docs/operational-guidelines.md`)
-  - Technology Stack Document (`docs/tech-stack.md`)
-  - Data Models Document (as referenced in Index Doc)
-  - API Reference Document (as referenced in Index Doc)
-  - UI/UX Specifications, Style Guides, Component Guides (if relevant, as referenced in Index Doc)
-- The `bmad-core/templates/story-tmpl.md` (hereafter "Story Template")
-- The `bmad-core/checklists/story-draft-checklist.md` (hereafter "Story Draft Checklist")
-- User confirmation to proceed with story identification and, if needed, to override warnings about incomplete prerequisite stories.
-
 ## Task Execution Instructions
 
+### 0. Load Core Configuration
+
+[[LLM: CRITICAL - This MUST be your first step]]
+
+- Load `.bmad-core/core-config.yml` from the project root
+- If the file does not exist:
+  - HALT and inform the user: "core-config.yml not found. This file is required for story creation. You can:
+    1. Copy it from GITHUB BMAD-METHOD/bmad-core/core-config.yml and configure it for your project
+    2. Run the BMAD installer against your project to upgrade and add the file automatically
+    Please add and configure core-config.yml before proceeding."
+- Extract the following key configurations:
+  - `dev-story-location`: Where to save story files
+  - `prd.prdSharded`: Whether PRD is sharded or monolithic
+  - `prd.prd-file`: Location of monolithic PRD (if not sharded)
+  - `prd.prdShardedLocation`: Location of sharded epic files
+  - `prd.epicFilePattern`: Pattern for epic files (e.g., `epic-{n}*.md`)
+  - `architecture.architectureVersion`: Architecture document version
+  - `architecture.architectureSharded`: Whether architecture is sharded
+  - `architecture.architecture-file`: Location of monolithic architecture
+  - `architecture.architectureShardedLocation`: Location of sharded architecture files
+
 ### 1. Identify Next Story for Preparation
 
 #### 1.1 Locate Epic Files
 
-- First, determine where epic files are located:
+- Based on `prdSharded` from config:
-  - Check `docs/prd/` for files matching pattern `epic-{n}-*.md`
+  - **If `prdSharded: true`**: Look for epic files in `prdShardedLocation` using `epicFilePattern`
-  - If not found, check `docs/epics/` for files matching pattern `epic-{n}-*.md`
+  - **If `prdSharded: false`**: Load the full PRD from `prd-file` and extract epics from section headings (## Epic N or ### Epic N)
-  - If still not found, ask user: "Unable to locate epic files. Please specify the path where epic files are stored."
-- Note: Epic files follow naming convention `epic-{n}-{description}.md` (e.g., `epic-1-foundation-core-infrastructure.md`)
 
 #### 1.2 Review Existing Stories
 
-- Review `docs/stories/` to find the highest-numbered story file.
+- Check `dev-story-location` from config (e.g., `docs/stories/`) for existing story files
+- If the directory exists and has at least 1 file, find the highest-numbered story file.
 - **If a highest story file exists (`{lastEpicNum}.{lastStoryNum}.story.md`):**
-
   - Verify its `Status` is 'Done' (or equivalent).
   - If not 'Done', present an alert to the user:
 
@@ -2312,17 +2666,17 @@ To identify the next logical story based on project progress and epic definition
     ```
 
   - Proceed only if user selects option 3 (Override) or if the last story was 'Done'.
-  - If proceeding: Look for the Epic File for `{lastEpicNum}` (e.g., `epic-{lastEpicNum}-*.md`) and check for a story numbered `{lastStoryNum + 1}`. If it exists and its prerequisites (per Epic File) are met, this is the next story.
+  - If proceeding: Look for the Epic File for `{lastEpicNum}` (e.g., `epic-{lastEpicNum}*.md`) and check for a story numbered `{lastStoryNum + 1}`. If it exists and its prerequisites (per Epic File) are met, this is the next story.
-  - Else (story not found or prerequisites not met): The next story is the first story in the next Epic File (e.g., look for `epic-{lastEpicNum + 1}-*.md`, then `epic-{lastEpicNum + 2}-*.md`, etc.) whose prerequisites are met.
+  - Else (story not found or prerequisites not met): The next story is the first story in the next Epic File (e.g., look for `epic-{lastEpicNum + 1}*.md`, then `epic-{lastEpicNum + 2}*.md`, etc.) whose prerequisites are met.
 
 - **If no story files exist in `docs/stories/`:**
   - The next story is the first story in the first epic file (look for `epic-1-*.md`, then `epic-2-*.md`, etc.) whose prerequisites are met.
 - If no suitable story with met prerequisites is found, report to the user that story creation is blocked, specifying what prerequisites are pending. HALT task.
 - Announce the identified story to the user: "Identified next story for preparation: {epicNum}.{storyNum} - {Story Title}".
 
-### 2. Gather Core Story Requirements (from Epic File)
+### 2. Gather Core Story Requirements (from Epic)
 
-- For the identified story, open its parent Epic File (e.g., `epic-{epicNum}-*.md` from the location identified in step 1.1).
+- For the identified story, review its parent Epic (e.g., `epic-{epicNum}*.md` from the location identified in step 1.1).
 - Extract: Exact Title, full Goal/User Story statement, initial list of Requirements, all Acceptance Criteria (ACs), and any predefined high-level Tasks.
 - Keep a record of this original epic-defined scope for later deviation analysis.
 
@@ -2331,7 +2685,7 @@ To identify the next logical story based on project progress and epic definition
 [[LLM: This step is CRITICAL for continuity and learning from implementation experience]]
 
 - If this is not the first story (i.e., previous story exists):
-  - Read the previous story file: `docs/stories/{prevEpicNum}.{prevStoryNum}.story.md`
+  - Read the previous sequential story from `docs/stories`
   - Pay special attention to:
     - Dev Agent Record sections (especially Completion Notes and Debug Log References)
     - Any deviations from planned implementation
@@ -2340,18 +2694,30 @@ To identify the next logical story based on project progress and epic definition
     - Any "lessons learned" or notes for future stories
   - Extract relevant insights that might inform the current story's preparation
 
-### 4. Gather & Synthesize Architecture Context from Sharded Docs
+### 4. Gather & Synthesize Architecture Context
 
-[[LLM: CRITICAL - You MUST gather technical details from the sharded architecture documents. NEVER make up technical details not found in these documents.]]
+[[LLM: CRITICAL - You MUST gather technical details from the architecture documents. NEVER make up technical details not found in these documents.]]
 
-#### 4.1 Start with Architecture Index
+#### 4.1 Determine Architecture Document Strategy
 
-- Read `docs/architecture/index.md` to understand the full scope of available documentation
+Based on configuration loaded in Step 0:
-- Identify which sharded documents are most relevant to the current story
 
-#### 4.2 Recommended Reading Order Based on Story Type
+- **If `architectureVersion: v4` and `architectureSharded: true`**:
+  - Read `{architectureShardedLocation}/index.md` to understand available documentation
+  - Follow the structured reading order in section 4.2 below
+  
+- **If `architectureVersion: v4` and `architectureSharded: false`**:
+  - Load the monolithic architecture from `architecture-file`
+  - Extract relevant sections based on v4 structure (tech stack, project structure, etc.)
+  
+- **If `architectureVersion` is NOT v4**:
+  - Inform user: "Architecture document is not v4 format. Will use best judgment to find relevant information."
+  - If `architectureSharded: true`: Search sharded files by filename relevance
+  - If `architectureSharded: false`: Search within monolithic `architecture-file` for relevant sections
 
-[[LLM: Read documents in this order, but ALWAYS verify relevance to the specific story. Skip irrelevant sections but NEVER skip documents that contain information needed for the story.]]
+#### 4.2 Recommended Reading Order Based on Story Type (v4 Sharded Only)
+
+[[LLM: Use this structured approach ONLY for v4 sharded architecture. For other versions, use best judgment based on file names and content.]]
 
 **For ALL Stories:**
 
@@ -2360,9 +2726,18 @@ To identify the next logical story based on project progress and epic definition
 3. `docs/architecture/coding-standards.md` - Ensure dev follows project conventions
 4. `docs/architecture/testing-strategy.md` - Include testing requirements in tasks
 
-**For Backend/API Stories, additionally read:** 5. `docs/architecture/data-models.md` - Data structures and validation rules 6. `docs/architecture/database-schema.md` - Database design and relationships 7. `docs/architecture/backend-architecture.md` - Service patterns and structure 8. `docs/architecture/rest-api-spec.md` - API endpoint specifications 9. `docs/architecture/external-apis.md` - Third-party integrations (if relevant)
+**For Backend/API Stories, additionally read:**
+5. `docs/architecture/data-models.md` - Data structures and validation rules
+6. `docs/architecture/database-schema.md` - Database design and relationships
+7. `docs/architecture/backend-architecture.md` - Service patterns and structure
+8. `docs/architecture/rest-api-spec.md` - API endpoint specifications
+9. `docs/architecture/external-apis.md` - Third-party integrations (if relevant)
 
-**For Frontend/UI Stories, additionally read:** 5. `docs/architecture/frontend-architecture.md` - Component structure and patterns 6. `docs/architecture/components.md` - Specific component designs 7. `docs/architecture/core-workflows.md` - User interaction flows 8. `docs/architecture/data-models.md` - Frontend data handling
+**For Frontend/UI Stories, additionally read:**
+5. `docs/architecture/frontend-architecture.md` - Component structure and patterns
+6. `docs/architecture/components.md` - Specific component designs
+7. `docs/architecture/core-workflows.md` - User interaction flows
+8. `docs/architecture/data-models.md` - Frontend data handling
 
 **For Full-Stack Stories:**
 
@@ -2395,7 +2770,7 @@ Format references as: `[Source: architecture/{filename}.md#{section}]`
 
 ### 6. Populate Story Template with Full Context
 
-- Create a new story file: `docs/stories/{epicNum}.{storyNum}.story.md`.
+- Create a new story file: `{dev-story-location}/{epicNum}.{storyNum}.story.md` (using location from config).
 - Use the Story Template to structure the file.
 - Fill in:
   - Story `{EpicNum}.{StoryNum}: {Short Title Copied from Epic File}`
@@ -2442,7 +2817,7 @@ Format references as: `[Source: architecture/{filename}.md#{section}]`
 - Verify all source references are included for technical details
 - Ensure tasks align with both epic requirements and architecture constraints
 - Update status to "Draft"
-- Save the story file to `docs/stories/{epicNum}.{storyNum}.story.md`
+- Save the story file to `{dev-story-location}/{epicNum}.{storyNum}.story.md` (using location from config)
 
 ### 9. Report Completion
 

dist/teams/team-no-ui.txt

@@ -55,9 +55,9 @@ workflows:
 ==================== END: agent-teams#team-no-ui ====================
 
 ==================== START: agents#bmad-orchestrator ====================
-# bmad
+# bmad-orchestrator
 
-CRITICAL: Read the full YML to understand your operating params, start activation to alter your state of being, follow startup instructions, stay in this being until told to exit this mode:
+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
 agent:
@@ -89,9 +89,9 @@ startup:
   - If clear match to an agent's expertise, suggest transformation with *agent command
   - If project-oriented, suggest *workflow-guidance to explore options
   - Load resources only when needed - never pre-load
-commands:  # All commands require * prefix when used (e.g., *help, *agent pm)
+commands:
   help: Show this guide with available agents and workflows
-  chat-mode: Start conversational mode for detailed assistance  
+  chat-mode: Start conversational mode for detailed assistance
   kb-mode: Load full BMAD knowledge base
   status: Show current context, active agent, and progress
   agent: Transform into a specialized agent (list if name not specified)
@@ -106,41 +106,40 @@ commands:  # All commands require * prefix when used (e.g., *help, *agent pm)
 help-display-template: |
   === BMAD Orchestrator Commands ===
   All commands must start with * (asterisk)
-  
+
   Core 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
   *exit ............... Return to BMad or exit session
-  
+
   Agent & Task Management:
   *agent [name] ....... Transform into specialized agent (list if no name)
   *task [name] ........ Run specific task (list if no name, requires agent)
   *checklist [name] ... Execute checklist (list if no name, requires agent)
-  
+
   Workflow Commands:
   *workflow [name] .... Start specific workflow (list if no name)
   *workflow-guidance .. Get personalized help selecting the right workflow
-  
+
   Other Commands:
   *yolo ............... Toggle skip confirmations mode
   *party-mode ......... Group chat with all agents
   *doc-out ............ Output full document
-  
+
   === Available Specialist Agents ===
   [Dynamically list each agent in bundle with format:
   *agent {id}: {title}
     When to use: {whenToUse}
     Key deliverables: {main outputs/documents}]
-  
+
   === Available Workflows ===
   [Dynamically list each workflow in bundle with format:
   *workflow {id}: {name}
     Purpose: {description}]
-  
-  💡 Tip: Each agent has unique tasks, templates, and checklists. Switch to an agent to access their capabilities!
 
+  💡 Tip: Each agent has unique tasks, templates, and checklists. Switch to an agent to access their capabilities!
 fuzzy-matching:
   - 85% confidence threshold
   - Show numbered list if unsure
@@ -212,13 +211,13 @@ persona:
 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'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - (Default) Strategic analysis consultation with advanced-elicitation'
+  - chat-mode: (Default) Strategic analysis consultation with advanced-elicitation
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - create-doc {template}: Create doc (no template = show available templates)
-  - '*brainstorm {topic}" - Facilitate structured brainstorming session'
+  - brainstorm {topic}: Facilitate structured brainstorming session
-  - '*research {topic}" - Generate deep research prompt for investigation'
+  - research {topic}: Generate deep research prompt for investigation
-  - '*elicit" - Run advanced elicitation to clarify requirements'
+  - elicit: Run advanced elicitation to clarify requirements
-  - '*exit" - Say goodbye as the Business Analyst, and then abandon inhabiting this persona'
+  - exit: Say goodbye as the Business Analyst, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - brainstorming-techniques
@@ -241,7 +240,7 @@ dependencies:
 
 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
@@ -271,10 +270,10 @@ persona:
 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'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - (Default) Deep conversation with advanced-elicitation'
+  - chat-mode: (Default) Deep conversation with advanced-elicitation
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - create-doc {template}: Create doc (no template = show available templates)
-  - '*exit" - Say goodbye as the PM, and then abandon inhabiting this persona'
+  - exit: Say goodbye as the PM, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - create-doc
@@ -335,12 +334,12 @@ startup:
   - Greet the user with your name and role, and inform of the *help command.
   - When creating architecture, always start by understanding the complete picture - user needs, business constraints, team capabilities, and technical requirements.
 commands:
-  - '*help" - Show: numbered list of the following commands to allow selection'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - (Default) Architect consultation with advanced-elicitation for complex system design'
+  - chat-mode: (Default) Architect consultation with advanced-elicitation for complex system design
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - create-doc {template}: Create doc (no template = show available templates)
-  - '*execute-checklist {checklist}" - Run architectural validation checklist'
+  - execute-checklist {checklist}: Run architectural validation checklist
-  - '*research {topic}" - Generate deep research prompt for architectural decisions'
+  - research {topic}: Generate deep research prompt for architectural decisions
-  - '*exit" - Say goodbye as the Architect, and then abandon inhabiting this persona'
+  - exit: Say goodbye as the Architect, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - create-doc
@@ -366,7 +365,7 @@ dependencies:
 
 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
@@ -398,15 +397,15 @@ persona:
 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'
+  - help: Show numbered list of the following commands to allow selection
-  - '*chat-mode" - (Default) Product Owner consultation with advanced-elicitation'
+  - chat-mode: (Default) Product Owner consultation with advanced-elicitation
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - create-doc {template}: Create doc (no template = show available templates)
-  - '*execute-checklist {checklist}" - Run validation checklist (default->po-master-checklist)'
+  - execute-checklist {checklist}: Run validation checklist (default->po-master-checklist)
-  - '*shard-doc {document}" - Break down document into actionable parts'
+  - shard-doc {document}: Break down document into actionable parts
-  - '*correct-course" - Analyze and suggest project course corrections'
+  - correct-course: Analyze and suggest project course corrections
-  - '*create-epic" - Create epic for brownfield projects (task brownfield-create-epic)'
+  - create-epic: Create epic for brownfield projects (task brownfield-create-epic)
-  - '*create-story" - Create user story from requirements (task brownfield-create-story)'
+  - create-story: Create user story from requirements (task brownfield-create-story)
-  - '*exit" - Say Goodbye, You are no longer this Agent'
+  - exit: Say goodbye as the Product Owner, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - execute-checklist
@@ -611,6 +610,60 @@ BMAD-METHOD (Breakthrough Method of Agile AI-driven Development) is a framework
 - **Reusable Resources**: Portable templates, tasks, and checklists
 - **Slash Command Integration**: Quick agent switching and control
 
+### When to Use BMAD
+
+- **New Projects (Greenfield)**: Complete end-to-end development
+- **Existing Projects (Brownfield)**: Feature additions and enhancements
+- **Team Collaboration**: Multiple roles working together
+- **Quality Assurance**: Structured testing and validation
+- **Documentation**: Professional PRDs, architecture docs, user stories
+
+## Getting Started
+
+### Quick Start Options
+
+#### Option 1: Web UI
+**Best for**: ChatGPT, Claude, Gemini users who want to start immediately
+
+1. Navigate to `dist/teams/`
+2. Copy `team-fullstack.txt` content
+3. Create new Gemini Gem or CustomGPT
+4. Upload file with instructions: "Your critical operating instructions are attached, do not break character as directed"
+5. Type `/help` to see available commands
+
+#### Option 2: IDE Integration
+**Best for**: Cursor, Claude Code, Windsurf, VS Code users
+
+```bash
+# Interactive installation (recommended)
+npx bmad-method install
+```
+
+**Installation Steps**:
+- Choose "Complete installation"
+- Select your IDE (Cursor, Claude Code, Windsurf, or Roo Code)
+
+**Verify Installation**:
+- `.bmad-core/` folder created with all agents
+- IDE-specific integration files created
+- All agent commands/rules/modes available
+
+### Environment Selection Guide
+
+**Use Web UI for**:
+- Initial planning and documentation (PRD, architecture)
+- Cost-effective document creation (especially with Gemini)
+- Brainstorming and analysis phases
+- Multi-agent consultation and planning
+
+**Use IDE for**:
+- Active development and coding
+- File operations and project integration
+- Document sharding and story management
+- Implementation workflow (SM/Dev cycles)
+
+**Cost-Saving Tip**: Create large documents (PRDs, architecture) in web UI, then copy to `docs/prd.md` and `docs/architecture.md` in your project before switching to IDE for development.
+
 ## Core Philosophy
 
 ### Vibe CEO'ing
@@ -632,18 +685,345 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
 7. **START_SMALL_SCALE_FAST**: Test concepts, then expand.
 8. **EMBRACE_THE_CHAOS**: Adapt and overcome challenges.
 
-## IDE Development Workflow
+### Key Workflow Principles
 
-1. Shard the PRD (And Architecture documents if they exist also based on workflow type) using the Doc Shard task. The BMad-Master agent can help you do this. You will select the task, provide the doc to shard and the output folder. for example: `BMad Master, please Shard the docs/prd.md to the doc/prd/ folder` - this should ask you to use the md-tree-parser which is recommended, but either way shoudl result in multiple documents being created in the folder docs/prd.
+1. **Agent Specialization**: Each agent has specific expertise and responsibilities
-2. If you have fullstack, front end and or back end architecture documents you will want to follow the same thing, but shard all of these to an architecture folder instead of a prd folder.
+2. **Clean Handoffs**: Always start fresh when switching between agents
-3. Ensure that you have at least one epic-n.md file in your prd folder, with the stories in order to develop.
+3. **Status Tracking**: Maintain story statuses (Draft → Approved → InProgress → Done)
-4. The docs or architecture folder or prd folder should have a source tree document and coding standards at a minimum. These are used by the dev agent, and the many other sharded docs are used by the SM agent.
+4. **Iterative Development**: Complete one story before starting the next
-5. Use a new chat window to allow the SM agent to `draft the next story`.
+5. **Documentation First**: Always start with solid PRD and architecture
-6. If you agree the story is correct, mark it as approved in the status field, and then start a new chat window with the dev agent.
-7. Ask the dev agent to implement the next story. If you draft the story file into the chat it will save time for the dev to have to find what the next one is. The dev should follow the tasks and subtasks marking them off as they are completed. The dev agent will also leave notes potentially for the SM to know about any deviations that might have occured to help draft the next story.
-8. Once complete and you have verified, mark it done, and start a new chat. Ask the SM to draft the next story - repeating the cycle.
 
-With this work flow, there is only 1 story in progress at a time, worked sequentially.
+## Agent System
+
+### Core Development Team
+
+| Agent       | Role               | Primary Functions                       | When to Use                            |
+| ----------- | ------------------ | --------------------------------------- | -------------------------------------- |
+| `analyst`   | Business Analyst   | Market research, requirements gathering | Project planning, competitive analysis |
+| `pm`        | Product Manager    | PRD creation, feature prioritization    | Strategic planning, roadmaps           |
+| `architect` | Solution Architect | System design, technical architecture   | Complex systems, scalability planning  |
+| `dev`       | Developer          | Code implementation, debugging          | All development tasks                  |
+| `qa`        | QA Specialist      | Test planning, quality assurance        | Testing strategies, bug validation     |
+| `ux-expert` | UX Designer        | UI/UX design, prototypes                | User experience, interface design      |
+| `po`        | Product Owner      | Backlog management, story validation    | Story refinement, acceptance criteria  |
+| `sm`        | Scrum Master       | Sprint planning, story creation         | Project management, workflow           |
+
+### Meta Agents
+
+| Agent               | Role             | Primary Functions                     | When to Use                       |
+| ------------------- | ---------------- | ------------------------------------- | --------------------------------- |
+| `bmad-orchestrator` | Team Coordinator | Multi-agent workflows, role switching | Complex multi-role tasks          |
+| `bmad-master`       | Universal Expert | All capabilities without switching    | Single-session comprehensive work |
+
+### Agent Interaction Commands
+
+#### IDE-Specific Syntax
+
+**Agent Loading by IDE**:
+- **Claude Code**: `/agent-name` (e.g., `/bmad-master`)
+- **Cursor**: `@agent-name` (e.g., `@bmad-master`)
+- **Windsurf**: `@agent-name` (e.g., `@bmad-master`)
+- **Roo Code**: Select mode from mode selector (e.g., `bmad-bmad-master`)
+
+**Chat Management Guidelines**:
+- **Claude Code, Cursor, Windsurf**: Start new chats when switching agents
+- **Roo Code**: Switch modes within the same conversation
+
+**Common Task Commands**:
+- `*help` - Show available commands
+- `*status` - Show current context/progress
+- `*exit` - Exit the agent mode
+- `*shard-doc docs/prd.md prd` - Shard PRD into manageable pieces
+- `*shard-doc docs/architecture.md architecture` - Shard architecture document
+- `*create` - Run create-next-story task (SM agent)
+
+**In Web UI**:
+```text
+/pm create-doc prd
+/architect review system design
+/dev implement story 1.2
+/help - Show available commands
+/switch agent-name - Change active agent (if orchestrator available)
+```
+
+## Team Configurations
+
+### Pre-Built Teams
+
+#### Team All
+- **Includes**: All 10 agents + orchestrator
+- **Use Case**: Complete projects requiring all roles
+- **Bundle**: `team-all.txt`
+
+#### Team Fullstack
+- **Includes**: PM, Architect, Developer, QA, UX Expert
+- **Use Case**: End-to-end web/mobile development
+- **Bundle**: `team-fullstack.txt`
+
+#### Team No-UI
+- **Includes**: PM, Architect, Developer, QA (no UX Expert)
+- **Use Case**: Backend services, APIs, system development
+- **Bundle**: `team-no-ui.txt`
+
+## Core Architecture
+
+### System Overview
+
+The BMAD-Method is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
+
+### Key Architectural Components
+
+#### 1. Agents (`bmad-core/agents/`)
+- **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.)
+- **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies
+- **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use
+- **Startup Instructions**: Can load project-specific documentation for immediate context
+
+#### 2. Agent Teams (`bmad-core/agent-teams/`)
+- **Purpose**: Define collections of agents bundled together for specific purposes
+- **Examples**: `team-all.yml` (comprehensive bundle), `team-fullstack.yml` (full-stack development)
+- **Usage**: Creates pre-packaged contexts for web UI environments
+
+#### 3. Workflows (`bmad-core/workflows/`)
+- **Purpose**: YAML files defining prescribed sequences of steps for specific project types
+- **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development
+- **Structure**: Defines agent interactions, artifacts created, and transition conditions
+
+#### 4. Reusable Resources
+- **Templates** (`bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories
+- **Tasks** (`bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story"
+- **Checklists** (`bmad-core/checklists/`): Quality assurance checklists for validation and review
+- **Data** (`bmad-core/data/`): Core knowledge base and technical preferences
+
+### Dual Environment Architecture
+
+#### IDE Environment
+
+- Users interact directly with agent markdown files
+- Agents can access all dependencies dynamically
+- Supports real-time file operations and project integration
+- Optimized for development workflow execution
+
+#### Web UI Environment
+
+- Uses pre-built bundles from `dist/teams` for stand alone 1 upload files for all agents and their assest with an orchestrating agent
+- Single text files containing all agent dependencies are in `dist/agents/` - these are unnecessary unless you want to create a web agent that is only a single agent and not a team
+- Created by the web-builder tool for upload to web interfaces
+- Provides complete context in one package
+
+### Template Processing System
+
+BMAD employs a sophisticated template system with three key components:
+
+1. **Template Format** (`utils/template-format.md`): Defines markup language for variable substitution and AI processing directives
+2. **Document Creation** (`tasks/create-doc.md`): Orchestrates template selection and user interaction
+3. **Advanced Elicitation** (`tasks/advanced-elicitation.md`): Provides interactive refinement through structured brainstorming
+
+**Template Features**:
+
+- **Self-contained**: Templates embed both output structure and processing instructions
+- **Variable Substitution**: `{{placeholders}}` for dynamic content
+- **AI Processing Directives**: `[[LLM: instructions]]` for AI-only processing
+- **Interactive Refinement**: Built-in elicitation processes for quality improvement
+
+### Technical Preferences Integration
+
+The `technical-preferences.md` file serves as a persistent technical profile that:
+- Ensures consistency across all agents and projects
+- Eliminates repetitive technology specification
+- Provides personalized recommendations aligned with user preferences
+- Evolves over time with lessons learned
+
+### Build and Delivery Process
+
+The `web-builder.js` tool creates web-ready bundles by:
+1. Reading agent or team definition files
+2. Recursively resolving all dependencies
+3. Concatenating content into single text files with clear separators
+4. Outputting ready-to-upload bundles for web AI interfaces
+
+This architecture enables seamless operation across environments while maintaining the rich, interconnected agent ecosystem that makes BMAD powerful.
+
+## Complete Development Workflow
+
+### Planning Phase (Web UI Recommended)
+
+**Ideal for cost efficiency, especially with Gemini:**
+
+1. **Optional Analysis**: `/analyst` - Market research, competitive analysis
+2. **Project Brief**: Create foundation document (Analyst or user)
+3. **PRD Creation**: `/pm create-doc prd` - Comprehensive product requirements
+4. **Architecture Design**: `/architect create-doc architecture` - Technical foundation
+5. **Validation & Alignment**: `/po` run master checklist to ensure document consistency
+6. **Document Preparation**: Copy final documents to project as `docs/prd.md` and `docs/architecture.md`
+
+#### Example Planning Prompts
+
+**For PRD Creation**:
+```text
+"I want to build a [type] application that [core purpose].
+Help me brainstorm features and create a comprehensive PRD."
+```
+
+**For Architecture Design**:
+```text
+"Based on this PRD, design a scalable technical architecture
+that can handle [specific requirements]."
+```
+
+### Critical Transition: Web UI to IDE
+
+**Once planning is complete, you MUST switch to IDE for development:**
+
+- **Why**: Development workflow requires file operations, real-time project integration, and document sharding
+- **Cost Benefit**: Web UI is more cost-effective for large document creation; IDE is optimized for development tasks
+- **Required Files**: Ensure `docs/prd.md` and `docs/architecture.md` exist in your project
+
+### IDE Development Workflow
+
+**Prerequisites**: Planning documents must exist in `docs/` folder
+
+1. **Document Sharding**: 
+   - `@bmad-master` or `@po` shard `docs/prd.md` to `docs/prd/` folder
+   - If architecture exists, shard to `docs/architecture/` folder
+   - Results in multiple manageable documents and epic files
+
+2. **Verify Sharded Content**:
+   - At least one `epic-n.md` file in `docs/prd/` with stories in development order
+   - Source tree document and coding standards for dev agent reference
+   - Sharded docs for SM agent story creation
+
+**Resulting Folder Structure**:
+- `docs/prd/` - Broken down PRD sections
+- `docs/architecture/` - Broken down architecture sections
+- `docs/stories/` - Generated user stories
+
+3. **Development Cycle** (Sequential, one story at a time):
+
+   **Step 1 - Story Creation**: New chat window → `@sm` → `*create`
+   - SM executes create-next-story task
+   - Review generated story in `docs/stories/`
+   - Update status from "Draft" to "Approved"
+   
+   **Step 2 - Story Implementation**: New chat window → `@dev`
+   - Agent asks which story to implement
+   - Include story file content to save dev agent lookup time
+   - Dev follows tasks/subtasks, marking completion
+   - Dev leaves notes for SM about any deviations
+   - Update status to "Done"
+   
+   **Step 3 - Repeat**: Continue SM → Dev cycle until all epic stories complete
+
+**Important**: Only 1 story in progress at a time, worked sequentially until all epic stories complete.
+
+### Status Tracking Workflow
+
+Stories progress through defined statuses:
+- **Draft** → **Approved** → **InProgress** → **Done**
+
+Each status change requires user verification and approval before proceeding.
+
+### Workflow Types
+
+#### Greenfield Development
+- Business analysis and market research
+- Product requirements and feature definition  
+- System architecture and design
+- Development execution
+- Testing and deployment
+
+#### Brownfield Enhancement
+- Current system analysis
+- Enhancement planning
+- Impact assessment
+- Incremental development
+- Integration testing
+
+## Document Creation Best Practices
+
+### Required File Naming for Framework Integration
+
+- `docs/prd.md` - Product Requirements Document
+- `docs/architecture.md` - System Architecture Document
+
+**Why These Names Matter**:
+- Agents automatically reference these files during development
+- Sharding tasks expect these specific filenames
+- Workflow automation depends on standard naming
+
+### Cost-Effective Document Creation Workflow
+
+**Recommended for Large Documents (PRD, Architecture):**
+
+1. **Use Web UI**: Create documents in web interface for cost efficiency
+2. **Copy Final Output**: Save complete markdown to your project
+3. **Standard Names**: Save as `docs/prd.md` and `docs/architecture.md`
+4. **Switch to IDE**: Use IDE agents for development and smaller documents
+
+### Document Sharding
+
+Templates with Level 2 headings (`##`) can be automatically sharded:
+
+**Original PRD**:
+```markdown
+## Goals and Background Context
+## Requirements  
+## User Interface Design Goals
+## Success Metrics
+```
+
+**After Sharding**:
+- `docs/prd/goals-and-background-context.md`
+- `docs/prd/requirements.md`
+- `docs/prd/user-interface-design-goals.md`
+- `docs/prd/success-metrics.md`
+
+Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic sharding.
+
+## Usage Patterns and Best Practices
+
+### Environment-Specific Usage
+
+**Web UI Best For**:
+- Initial planning and documentation phases
+- Cost-effective large document creation
+- Agent consultation and brainstorming
+- Multi-agent workflows with orchestrator
+
+**IDE Best For**:
+- Active development and implementation
+- File operations and project integration
+- Story management and development cycles
+- Code review and debugging
+
+### Quality Assurance
+
+- Use appropriate agents for specialized tasks
+- Follow Agile ceremonies and review processes
+- Maintain document consistency with PO agent
+- Regular validation with checklists and templates
+
+### Performance Optimization
+
+- Use specific agents vs. `bmad-master` for focused tasks
+- Choose appropriate team size for project needs
+- Leverage technical preferences for consistency
+- Regular context management and cache clearing
+
+## Success Tips
+
+- **Use Gemini for big picture planning** - The team-fullstack bundle provides collaborative expertise
+- **Use bmad-master for document organization** - Sharding creates manageable chunks
+- **Follow the SM → Dev cycle religiously** - This ensures systematic progress
+- **Keep conversations focused** - One agent, one task per conversation
+- **Review everything** - Always review and approve before marking complete
+
+## Getting Help
+
+- **Commands**: Use `/help` in any environment to see available commands
+- **Agent Switching**: Use `/switch agent-name` with orchestrator for role changes
+- **Documentation**: Check `docs/` folder for project-specific context
+- **Community**: Discord and GitHub resources available for support
 ==================== END: data#bmad-kb ====================
 
 ==================== START: utils#workflow-management ====================
@@ -696,7 +1076,7 @@ Available workflows for [Team Name]:
 [... etc. ...]
 
 Use /workflow-start {number or id} to begin a workflow.
-```text
+```
 
 ### /workflow-start {workflow-id}
 
@@ -722,7 +1102,7 @@ In Progress:
     - Create PRD (John) - awaiting input
 
 Next: Technical Architecture
-```text
+```
 
 ### /workflow-resume
 
@@ -738,7 +1118,7 @@ BMad: I see you've completed Discovery and part of Product Planning.
       - UX Strategy with Sally (ux-expert)
 
       Would you like me to load Sally to continue?
-```text
+```
 
 ### /workflow-next
 
@@ -808,7 +1188,7 @@ BMad: I see you have a PRD and architecture document. Based on these artifacts,
       - Load Sarah (Product Owner) to validate all artifacts
 
       Would you like to continue with this workflow?
-```text
+```
 
 ## Workflow Context Passing
 
@@ -834,7 +1214,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
 
@@ -1449,6 +1829,8 @@ Present these numbered options to the user:
 ==================== START: templates#project-brief-tmpl ====================
 # Project Brief: {{Project Name}}
 
+[[LLM: The default path and filename unless specified is docs/brief.md]]
+
 [[LLM: This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development.
 
 Start by asking the user which mode they prefer:
@@ -1680,6 +2062,8 @@ These replace the standard elicitation options when working on project brief doc
 ==================== START: templates#market-research-tmpl ====================
 # Market Research Report: {{Project/Product Name}}
 
+[[LLM: The default path and filename unless specified is docs/market-research.md]]
+
 [[LLM: This template guides the creation of a comprehensive market research report. Begin by understanding what market insights the user needs and why. Work through each section systematically, using the appropriate analytical frameworks based on the research objectives.]]
 
 ## Executive Summary
@@ -1944,6 +2328,8 @@ These replace the standard elicitation options when working on market research d
 ==================== START: templates#competitor-analysis-tmpl ====================
 # Competitive Analysis Report: {{Project/Product Name}}
 
+[[LLM: The default path and filename unless specified is docs/competitor-analysis.md]]
+
 [[LLM: This template guides comprehensive competitor analysis. Start by understanding the user's competitive intelligence needs and strategic objectives. Help them identify and prioritize competitors before diving into detailed analysis.]]
 
 ## Executive Summary
@@ -2837,7 +3223,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
 
@@ -2901,6 +3287,8 @@ Document sharded successfully:
 ==================== START: templates#prd-tmpl ====================
 # {{Project Name}} Product Requirements Document (PRD)
 
+[[LLM: The default path and filename unless specified is docs/prd.md]]
+
 [[LLM: If available, review any provided document or ask if any are optionally available: Project Brief]]
 
 ## Goals and Background Context
@@ -3104,6 +3492,8 @@ so that {{benefit}}.
 ==================== START: templates#brownfield-prd-tmpl ====================
 # {{Project Name}} Brownfield Enhancement PRD
 
+[[LLM: The default path and filename unless specified is docs/prd.md]]
+
 [[LLM: IMPORTANT - SCOPE ASSESSMENT REQUIRED:
 
 This PRD is for SIGNIFICANT enhancements to existing projects that require comprehensive planning and multiple stories. Before proceeding:
@@ -4310,6 +4700,8 @@ Present a summary of what was created and ask if any additional documentation wo
 
 [[LLM: If available, review any provided relevant documents to gather all relevant context before beginning. If at a minimum you cannot local `docs/prd.md` ask the user what docs will provide the basis for the architecture.]]
 
+[[LLM: The default path and filename unless specified is docs/architecture.md]]
+
 ## Introduction
 
 [[LLM: This section establishes the document's purpose and scope. Keep the content below but ensure project name is properly substituted.
@@ -4663,7 +5055,7 @@ servers:
       '[object Object]': null
     description:
       '[object Object]': null
-```text
+```
 
 ^^/CONDITION: has_rest_api^^
 
@@ -4726,7 +5118,6 @@ 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/
@@ -4738,6 +5129,7 @@ project-root/
 ├── scripts/ # Monorepo management scripts
 └── package.json # Root package.json with workspaces
 @{/example}
+```
 
 [[LLM: After presenting the source tree structure, apply `tasks#advanced-elicitation` protocol]]
 
@@ -5085,6 +5477,8 @@ Note: Basic info goes in Coding Standards for dev agent. This detailed section i
 ==================== START: templates#front-end-architecture-tmpl ====================
 # {{Project Name}} Frontend Architecture Document
 
+[[LLM: The default path and filename unless specified is docs/ui-architecture.md]]
+
 [[LLM: Review provided documents including PRD, UX-UI Specification, and main Architecture Document. Focus on extracting technical implementation details needed for AI frontend tools and developer agents. Ask the user for any of these documents if you are unable to locate and were not provided.]]
 
 ## Template and Framework Selection
@@ -5261,6 +5655,8 @@ Document the starter template decision and any constraints it imposes before pro
 ==================== START: templates#fullstack-architecture-tmpl ====================
 # {{Project Name}} Fullstack Architecture Document
 
+[[LLM: The default path and filename unless specified is docs/architecture.md]]
+
 [[LLM: If available, review any provided relevant documents to gather all relevant context before beginning. At minimum, you should have access to docs/prd.md and docs/front-end-spec.md. Ask the user for any documents you need but cannot locate. This template creates a unified architecture that covers both backend and frontend concerns to guide AI-driven fullstack development.]]
 
 ## Introduction
@@ -6280,6 +6676,8 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
 ==================== START: templates#brownfield-architecture-tmpl ====================
 # {{Project Name}} Brownfield Enhancement Architecture
 
+[[LLM: The default path and filename unless specified is docs/architecture.md]]
+
 [[LLM: IMPORTANT - SCOPE AND ASSESSMENT REQUIRED:
 
 This architecture document is for SIGNIFICANT enhancements to existing projects that require comprehensive architectural planning. Before proceeding:
@@ -6504,7 +6902,7 @@ Present component architecture and apply `tasks#advanced-elicitation` protocol]]
 
 ```mermaid
 {{component_interaction_diagram}}
-```text
+```
 
 ## API Design and Integration
 
@@ -6544,7 +6942,7 @@ Present API design and apply `tasks#advanced-elicitation` protocol]]
 
 ```json
 {{response_schema}}
-```text
+```
 
 <</REPEAT>>
 

docs/bmad-workflow-guide.md

@@ -33,11 +33,13 @@ The BMAD Method follows a structured approach to AI-assisted software developmen
 
 Use Google's Gemini for collaborative planning with the full team:
 
-1. **Open [Google AI Studio](https://aistudio.google.com/)**
+1. **Open [Google Gems](https://gemini.google.com/gems/view)**
-2. **Load team-fullstack**:
+2. **Create a new Gem**:
-   - Copy contents of: `/Users/brianmadison/dev/BMAD-METHOD/.bmad-core/web-bundles/teams/team-fullstack.txt`
+   - Give it a title and description (e.g., "BMAD Team Fullstack")
-   - Paste into new Gemini chat
+3. **Load team-fullstack**:
-3. **Collaborate with the team**:
+   - Copy contents of: `dist/teams/team-fullstack.txt` from your project
+   - Paste this content into the Gem setup to configure the team
+4. **Collaborate with the team**:
    - Business Analyst: Requirements gathering
    - Product Manager: Feature prioritization
    - Solution Architect: Technical design
@@ -53,9 +55,9 @@ Help me brainstorm features and create a comprehensive PRD."
 that can handle [specific requirements]."
 ```
 
-4. **Export planning documents**:
+5. **Export planning documents**:
-   - Save PRD as `docs/prd.md`
+   - Copy the PRD output and save as `docs/prd.md` in your project
-   - Save architecture as `docs/architecture.md`
+   - Copy the architecture output and save as `docs/architecture.md` in your project
 
 ### Phase 3: Document Organization (IDE)
 

docs/claude-code-guide.md

@@ -23,7 +23,7 @@ For ideation and planning, use Google's Gemini Custom Gem with the team-fullstac
 
 1. Open [Google gems](https://gemini.google.com/gems/view)
 2. Create a new Gem - give it a title and description
-3. Copy the contents of `.<install location>/web-bundles/teams/team-fullstack.txt`
+3. Copy the contents of `.<install location>/<web-bundles>/teams/team-fullstack.txt` (location can vary if you chose a non default installation location for the bundles) - or just use the bundle premade from the repo dist folder.
 4. Paste this content into Gemini to set up the team
 
 ### Gemini Planning Phase

docs/core-architecture.md

@@ -35,7 +35,7 @@ graph TD
         end
 
         subgraph Outputs
-            J[".bmad-core/web-bundles"]
+            J["dist"]
         end
 
         B -- defines dependencies for --> E
@@ -59,7 +59,7 @@ graph TD
     style A fill:#1a73e8,color:#fff
     style I fill:#f9ab00,color:#fff
     style J fill:#34a853,color:#fff
-```text
+```
 
 ## 3. Core Components
 
@@ -110,6 +110,7 @@ The system maintains a clean separation of concerns: template markup is processe
 BMAD includes a personalization layer through the `technical-preferences.md` file in `.bmad-core/data/`. This file serves as a persistent technical profile that influences agent behavior across all projects.
 
 **Purpose and Benefits:**
+
 - **Consistency**: Ensures all agents reference the same technical preferences
 - **Efficiency**: Eliminates the need to repeatedly specify preferred technologies
 - **Personalization**: Agents provide recommendations aligned with user preferences
@@ -119,6 +120,7 @@ BMAD includes a personalization layer through the `technical-preferences.md` fil
 The file typically includes preferred technology stacks, design patterns, external services, coding standards, and anti-patterns to avoid. Agents automatically reference this file during planning and development to provide contextually appropriate suggestions.
 
 **Integration Points:**
+
 - Templates can reference technical preferences during document generation
 - Agents suggest preferred technologies when appropriate for project requirements
 - When preferences don't fit project needs, agents explain alternatives
@@ -133,17 +135,17 @@ The framework is designed for two primary environments: local IDEs and web-based
 
 ### 4.1. Web Builder (`tools/builders/web-builder.js`)
 
-- **Purpose**: This Node.js script is responsible for creating the `.txt` bundles found in `.bmad-core/web-bundles/`.
+- **Purpose**: This Node.js script is responsible for creating the `.txt` bundles found in `dist`.
 - **Process**:
   1. **Resolves Dependencies**: For a given agent or team, the script reads its definition file.
   2. It recursively finds all dependent resources (tasks, templates, etc.) that the agent/team needs.
   3. **Bundles Content**: It reads the content of all these files and concatenates them into a single, large text file, with clear separators indicating the original file path of each section.
-  4. **Outputs Bundle**: The final `.txt` file is saved in the `web-bundles` directory, ready to be uploaded to a web UI.
+  4. **Outputs Bundle**: The final `.txt` file is saved in the `dist` directory, ready to be uploaded to a web UI.
 
 ### 4.2. Environment-Specific Usage
 
 - **For IDEs**: Users interact with the agents directly via their markdown files in `.bmad-core/agents/`. The IDE integration (for Cursor, Claude Code, etc.) knows how to call these agents.
-- **For Web UIs**: Users upload a pre-built bundle from `.bmad-core/web-bundles/`. This single file provides the AI with the context of the entire team and all their required tools and knowledge.
+- **For Web UIs**: Users upload a pre-built bundle from `dist`. This single file provides the AI with the context of the entire team and all their required tools and knowledge.
 
 ## 5. BMAD Workflows
 
@@ -168,7 +170,7 @@ graph TD
     I --> L["📁 Switch to IDE"]
     L --> M["PO: Shard Documents"]
     M --> N["Ready for SM/Dev Cycle"]
-    
+
     style I fill:#34a853,color:#fff
     style G fill:#f9ab00,color:#fff
     style L fill:#1a73e8,color:#fff

docs/cursor-guide.md

@@ -23,7 +23,7 @@ For ideation and planning, use Google's Gemini Custom Gem with the team-fullstac
 
 1. Open [Google gems](https://gemini.google.com/gems/view)
 2. Create a new Gem - give it a title and description
-3. Copy the contents of `.<install location>/web-bundles/teams/team-fullstack.txt`
+3. Copy the contents of `.<install location>/<web-bundles>/teams/team-fullstack.txt` (location can vary if you chose a non default installation location for the bundles) - or just use the bundle premade from the repo dist folder.
 4. Paste this content into Gemini to set up the team
 
 ### Gemini Planning Phase

docs/how-to-contribute-with-pull-requests.md

@@ -24,7 +24,7 @@ A pull request (PR) is how you propose changes to a project on GitHub. Think of
 # Replace YOUR-USERNAME with your actual GitHub username
 git clone https://github.com/YOUR-USERNAME/bmad-method.git
 cd bmad-method
-```text
+```
 
 ### 3. Create a New Branch
 
@@ -57,7 +57,7 @@ git add .
 
 # Commit with a clear message
 git commit -m "Fix typo in README.md"
-```text
+```
 
 **Good commit messages:**
 

docs/roo-code-guide.md

@@ -23,7 +23,7 @@ For ideation and planning, use Google's Gemini Custom Gem with the team-fullstac
 
 1. Open [Google gems](https://gemini.google.com/gems/view)
 2. Create a new Gem - give it a title and description
-3. Copy the contents of `.<install location>/web-bundles/teams/team-fullstack.txt`
+3. Copy the contents of `.<install location>/<web-bundles>/teams/team-fullstack.txt` (location can vary if you chose a non default installation location for the bundles) - or just use the bundle premade from the repo dist folder.
 4. Paste this content into Gemini to set up the team
 
 ### Gemini Planning Phase

docs/user-guide.md

@@ -46,7 +46,7 @@ BMAD-METHOD (Breakthrough Method of Agile AI-Driven Development) is an AI agent
 
 Best for: ChatGPT, Claude, Gemini users
 
-1. Navigate to `.bmad-core/web-bundles/teams/`
+1. Navigate to `dist/teams/`
 2. Copy `team-fullstack.txt` content
 3. Create new Gemini Gem or CustomGPT
 4. Upload file with instructions: "Your critical operating instructions are attached, do not break character as directed"
@@ -59,10 +59,7 @@ Best for: Cursor, Claude Code, Windsurf, VS Code users
 ```bash
 # Interactive installation (recommended)
 npx bmad-method install
-
+```
-# Command line installation
-npx bmad-method install --full --directory ./my-project --ide cursor
-```text
 
 ### First Steps
 
@@ -130,7 +127,7 @@ dependencies:
 # Claude Code (files in commands folder - loaded with /)
 /pm Create user stories
 /dev Fix the login bug
-```text
+```
 
 **In Web UI:**
 
@@ -178,7 +175,7 @@ Templates follow the `template-format.md` specification:
 
 - **Template**: `architecture-template.md`
 - **Agent**: Architect
-- **Use Case**: System design, technical planning  
+- **Use Case**: System design, technical planning
 - **Command**: `/architect create-doc architecture`
 - **💡 Cost-Saving Tip**: For Gemini users, create architecture docs in the web UI to avoid high IDE token costs. Copy the final markdown output to `docs/architecture.md` in your project.
 
@@ -203,10 +200,12 @@ For cost efficiency, especially with Gemini:
 #### File Naming Conventions
 
 **Required Names for Framework Integration:**
+
 - `docs/prd.md` - Product Requirements Document
 - `docs/architecture.md` - System Architecture Document
 
 **Why These Names Matter:**
+
 - Agents automatically reference these files during development
 - Sharding tasks expect these specific filenames
 - Workflow automation depends on standard naming
@@ -214,6 +213,7 @@ For cost efficiency, especially with Gemini:
 #### IDE Document Creation
 
 When working directly in IDEs:
+
 - Agents should create documents in `docs/` folder automatically
 - If agents name files differently (e.g., `product-requirements.md`), rename to `prd.md`
 - Verify document location matches `docs/prd.md` and `docs/architecture.md`
@@ -226,7 +226,7 @@ Templates can include `advanced-elicitation.md` for enhanced interaction:
 
 ```markdown
 [[LLM: Use advanced-elicitation actions 0-3 to refine requirements]]
-```text
+```
 
 This provides 10 structured brainstorming actions:
 
@@ -262,7 +262,7 @@ graph TD
     I --> L["📁 Switch to IDE"]
     L --> M["PO: Shard Documents"]
     M --> N["Ready for SM/Dev Cycle"]
-    
+
     style I fill:#34a853,color:#fff
     style G fill:#f9ab00,color:#fff
     style L fill:#1a73e8,color:#fff
@@ -298,7 +298,7 @@ graph TD
     J --> E
 
     style J fill:#34a853,color:#fff
-```text
+```
 
 ### Workflow Phases
 
@@ -487,11 +487,13 @@ workflows:
 Web UI agents focus on planning and documentation. Here's how to interact with each:
 
 #### Agent Switching and Conversation
+
 - **Switch Agents**: Use `/pm`, `/architect`, `/analyst`, `/po` to switch between roles
 - **Agent Consultation**: Each agent offers their specialized options and capabilities
 - **Natural Conversation**: Agents guide you through their processes with questions and suggestions
 
 #### Planning Phase Agents
+
 - **Analyst**: `/analyst` - Brainstorming, market research, competitive analysis
 - **PM**: `/pm` - Product requirements, feature definition, roadmaps
 - **Architect**: `/architect` - System design, technical architecture
@@ -511,12 +513,13 @@ Web UI agents focus on planning and documentation. Here's how to interact with e
 
 1. **Use Web UI for PRD and Architecture**: These are token-heavy documents, especially in Gemini
 2. **Copy Final Output**: Save complete markdown to your project
-3. **Standard File Names**: 
+3. **Standard File Names**:
    - Save PRD as `docs/prd.md`
    - Save Architecture as `docs/architecture.md`
 4. **IDE for Development**: Switch to IDE agents for implementation tasks
 
 **Why This Saves Money:**
+
 - Web UI pricing is typically more cost-effective for large context windows
 - PRD and architecture creation involves extensive back-and-forth refinement
 - IDE token costs can accumulate quickly with large document generation
@@ -557,7 +560,7 @@ dependencies:
 ## Section 2
 
 {{section_2_content}}
-```text
+```
 
 ### Workflow Customization
 
@@ -611,27 +614,34 @@ Templates are self-contained documents that embed both output structure and proc
 @{example: Example content for AI guidance}
 
 ^^CONDITION: condition_name^^
+
 ## Conditional Section
+
 [[LLM: Only include if condition is met]]
 ^^/CONDITION^^
-```text
+```
 
 #### Key Template Patterns
 
 **Variable Substitution:**
+
 - `{{Project Name}}` - Dynamic project name
 - `{{document_title}}` - Document-specific title
 - `{{section_content}}` - Placeholder for generated content
 
 **AI Processing Instructions:**
+
 - `[[LLM: Instructions for AI behavior]]` - AI-only processing directives
 - `@{example: Sample content}` - Guidance examples (not output)
 - `tasks#advanced-elicitation` - Reference to embedded tasks
 
 **Conditional Content:**
+
 ```markdown
 ^^CONDITION: has_ui^^
+
 ## User Interface Section
+
 [[LLM: Only include for UI projects]]
 ^^/CONDITION^^
 ```
@@ -641,16 +651,21 @@ Templates are self-contained documents that embed both output structure and proc
 Level 2 headings (`##`) in templates can be automatically sharded into separate documents:
 
 **Original PRD:**
+
 ```markdown
 ## Goals and Background Context
-## Requirements  
+
+## Requirements
+
 ## User Interface Design Goals
+
 ## Success Metrics
-```text
+```
 
 **After Sharding:**
+
 - `docs/prd/goals-and-background-context.md`
-- `docs/prd/requirements.md`  
+- `docs/prd/requirements.md`
 - `docs/prd/user-interface-design-goals.md`
 - `docs/prd/success-metrics.md`
 
@@ -673,10 +688,12 @@ Tasks are reusable automation instructions that agents can execute. They follow
 ## Instructions
 
 ### 1. Step One
+
 - Detailed instructions for the agent
 - Specific behaviors and outputs expected
 
-### 2. Step Two  
+### 2. Step Two
+
 - Additional processing steps
 - Integration with other resources
 
@@ -688,20 +705,23 @@ Tasks are reusable automation instructions that agents can execute. They follow
 #### Task Patterns
 
 **Resource Integration:**
+
 ```markdown
 [[LLM: Check if docs/coding-standards.md exists and reference it]]
 [[LLM: Load docs/openapi-spec.yaml for API context]]
-```text
+```
 
 **Advanced Elicitation:**
+
 ```markdown
 [[LLM: Apply tasks#advanced-elicitation protocol after completion]]
 ```
 
 **Conditional Logic:**
+
 ```markdown
 [[LLM: If project has UI components, also check frontend standards]]
-```text
+```
 
 ### Creating Custom Agents
 
@@ -747,7 +767,7 @@ startup:
   - Review docs/project-structure.md for context
   - Check for docs/third-party-apis/ folder
   - Announce specialized capabilities
-```text
+```
 
 #### Loading Project Documents
 
@@ -763,8 +783,9 @@ Agents can reference and load documents from the `docs/` folder:
 
 ```markdown
 [[LLM: Before beginning, check for and load relevant context:
+
 - docs/coding-standards.md for development standards
-- docs/brand-guidelines.md for design consistency  
+- docs/brand-guidelines.md for design consistency
 - docs/third-party-apis/ for integration requirements
 - Any project-specific documentation in docs/ folder]]
 ```
@@ -780,50 +801,60 @@ This file allows you to define your preferred technologies, patterns, and standa
 #### What to Include
 
 **Technology Stack Preferences:**
+
 ```markdown
 ## Preferred Technologies
 
 ### Frontend
+
 - React with TypeScript
 - Tailwind CSS for styling
 - Next.js for full-stack applications
 
-### Backend  
+### Backend
+
 - Node.js with Express
 - PostgreSQL for relational data
 - Redis for caching
 
 ### Deployment
+
 - Vercel for frontend
 - Railway for backend services
-```text
+```
 
 **Design Patterns & Standards:**
+
 ```markdown
 ## Code Standards
+
 - Use functional programming patterns where possible
 - Prefer composition over inheritance
 - Always include comprehensive error handling
 - Write tests for all business logic
 
 ## Architecture Preferences
+
 - Microservices for complex applications
 - RESTful APIs with OpenAPI documentation
 - Event-driven architecture for real-time features
 ```
 
 **External Services & APIs:**
+
 ```markdown
 ## Preferred External Services
+
 - Auth0 for authentication
 - Stripe for payments
 - SendGrid for email
 - Cloudinary for image processing
 
 ## APIs to Avoid
+
 - Legacy SOAP services
 - Services without proper documentation
-```text
+```
 
 #### How Agents Use This File
 
@@ -837,22 +868,264 @@ This file allows you to define your preferred technologies, patterns, and standa
 
 **Learning and Evolution**: As you work on projects, add discoveries to your preferences file:
 
-```markdown
 ## Lessons Learned
+
 - Avoid using Library X for large datasets (performance issues)
 - Pattern Y works well for real-time features
 - Service Z has excellent documentation and support
 
 ## Future Exploration
+
 - Want to try Framework A on next appropriate project
 - Interested in Pattern B for microservices
 - Consider Service C for better performance
-```
 
-#### Using with Web Bundles
+### Using with Web Bundles
 
 When creating custom web bundles or uploading to AI platforms, include your `technical-preferences.md` content to ensure agents have your preferences from the start of any conversation.
 
+### Core Configuration (core-config.yml)
+
+The `bmad-core/core-config.yml` file is a critical V4 innovation that enables BMAD to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
+
+#### Understanding core-config.yml
+
+This configuration file acts as a map for BMAD agents, telling them exactly where to find your project documents and how they're structured. It's what makes V4 agents intelligent enough to work with V3 projects, custom layouts, or any document organization you prefer.
+
+#### Configuration Structure
+
+```yaml
+core-project-information:
+  dev-story-location: docs/stories # Where completed stories are saved
+
+  prd:
+    prd-file: docs/prd.md
+    prdVersion: v4 # v3 or v4
+    prdSharded: true # false if epics are embedded in PRD
+    prdShardedLocation: docs/prd # Where sharded epics live
+    epicFilePattern: epic-{n}*.md # Pattern for epic files
+
+  architecture:
+    architecture-file: docs/architecture.md
+    architectureVersion: v4 # v3 or v4
+    architectureSharded: true # false if monolithic
+    architectureShardedLocation: docs/architecture
+
+  customTechnicalDocuments: null # Additional docs for SM
+
+  devLoadAlwaysFiles: # Files dev agent always loads
+    - docs/architecture/coding-standards.md
+    - docs/architecture/tech-stack.md
+    - docs/architecture/project-structure.md
+
+  devDebugLog: .ai/debug-log.md # Dev agent debug tracking
+  agentCoreDump: .ai/core-dump{n}.md # Export chat contents
+```
+
+#### Key Configuration Options
+
+##### PRD Configuration
+
+The Scrum Master agent uses these settings to locate epics:
+
+**V4 Sharded Structure:**
+
+```yaml
+prd:
+  prd-file: docs/prd.md
+  prdVersion: v4
+  prdSharded: true
+  prdShardedLocation: docs/prd
+  epicFilePattern: epic-{n}*.md
+```
+
+**V3 Embedded Epics:**
+
+```yaml
+prd:
+  prd-file: docs/prd.md
+  prdVersion: v3
+  prdSharded: false # Epics are inside PRD
+```
+
+**Custom Sharded Location:**
+
+```yaml
+prd:
+  prd-file: docs/product-requirements.md
+  prdVersion: v4
+  prdSharded: true
+  prdShardedLocation: docs # Epics in docs/ not docs/prd/
+  epicFilePattern: epic-*.md
+```
+
+##### Architecture Configuration
+
+Similar flexibility for architecture documents:
+
+**V4 Sharded Architecture:**
+
+```yaml
+architecture:
+  architecture-file: docs/architecture.md
+  architectureVersion: v4
+  architectureSharded: true
+  architectureShardedLocation: docs/architecture
+```
+
+**V3 Monolithic Architecture:**
+
+```yaml
+architecture:
+  architecture-file: docs/technical-architecture.md
+  architectureVersion: v3
+  architectureSharded: false # All in one file
+```
+
+##### Developer Context Files
+
+Define which files the dev agent should always load:
+
+```yaml
+devLoadAlwaysFiles:
+  - docs/architecture/coding-standards.md
+  - docs/architecture/tech-stack.md
+  - docs/architecture/project-structure.md
+  - docs/api-contracts.yaml
+  - docs/database-schema.md
+  - .env.example
+```
+
+This ensures the dev agent always has critical context without needing to search for it.
+
+##### Debug and Export Options
+
+**Debug Log:**
+
+```yaml
+devDebugLog: .ai/debug-log.md
+```
+
+When the dev agent encounters repeated failures implementing a story, it logs issues here to avoid repeating the same mistakes.
+
+**Core Dump:**
+
+```yaml
+agentCoreDump: .ai/core-dump{n}.md
+```
+
+Export entire chat conversations for preservation or analysis. The `{n}` is replaced with a number.
+
+#### Common Configurations
+
+##### Legacy V3 Project
+
+```yaml
+core-project-information:
+  dev-story-location: docs/stories
+  prd:
+    prd-file: docs/prd.md
+    prdVersion: v3
+    prdSharded: false
+  architecture:
+    architecture-file: docs/architecture.md
+    architectureVersion: v3
+    architectureSharded: false
+  devLoadAlwaysFiles: []
+```
+
+##### Hybrid Project (V3 PRD, V4 Architecture)
+
+```yaml
+core-project-information:
+  dev-story-location: .ai/stories
+  prd:
+    prd-file: docs/product-requirements.md
+    prdVersion: v3
+    prdSharded: false
+  architecture:
+    architecture-file: docs/architecture.md
+    architectureVersion: v4
+    architectureSharded: true
+    architectureShardedLocation: docs/architecture
+  devLoadAlwaysFiles:
+    - docs/architecture/tech-stack.md
+```
+
+##### Custom Organization
+
+```yaml
+core-project-information:
+  dev-story-location: development/completed-stories
+  prd:
+    prd-file: planning/requirements.md
+    prdVersion: v4
+    prdSharded: true
+    prdShardedLocation: planning/epics
+    epicFilePattern: requirement-{n}.md
+  architecture:
+    architecture-file: technical/system-design.md
+    architectureVersion: v4
+    architectureSharded: true
+    architectureShardedLocation: technical/components
+  customTechnicalDocuments:
+    - technical/api-guide.md
+    - technical/deployment.md
+  devLoadAlwaysFiles:
+    - technical/coding-guidelines.md
+    - technical/git-workflow.md
+```
+
+#### Migration Strategies
+
+##### Gradual V3 to V4 Migration
+
+Start with V3 documents and gradually adopt V4 patterns:
+
+1. **Initial State**: Set `prdVersion: v3` and `prdSharded: false`
+2. **Shard PRD**: Use PO agent to shard, then update to `prdSharded: true`
+3. **Update Version**: Change to `prdVersion: v4` after using V4 templates
+4. **Repeat for Architecture**: Same process for architecture documents
+
+##### Working with Mixed Teams
+
+If some team members use V3 and others use V4:
+
+```yaml
+# Support both patterns
+customTechnicalDocuments:
+  - docs/legacy-requirements.md # V3 format
+  - docs/prd.md # V4 format
+```
+
+#### Best Practices
+
+1. **Always Configure for Your Structure**: Don't force your project to match BMAD defaults
+2. **Keep devLoadAlwaysFiles Focused**: Only include files needed for every dev task
+3. **Use Debug Log**: Enable when troubleshooting story implementation issues
+4. **Version Control core-config.yml**: Track changes to understand project evolution
+5. **Document Custom Patterns**: If using custom epicFilePattern, document it
+
+#### Troubleshooting
+
+**Scrum Master Can't Find Epics:**
+
+- Check `prdSharded` matches your structure
+- Verify `prdShardedLocation` path exists
+- Confirm `epicFilePattern` matches your files
+
+**Dev Agent Missing Context:**
+
+- Add critical files to `devLoadAlwaysFiles`
+- Ensure file paths are correct
+- Check files exist and are readable
+
+**Architecture Not Loading:**
+
+- Verify `architecture-file` path
+- Check `architectureVersion` setting
+- Confirm sharding configuration matches reality
+
 ### Extension Packs
 
 Add specialized capabilities:

docs/windsurf-guide.md

@@ -23,7 +23,7 @@ For ideation and planning, use Google's Gemini Custom Gem with the team-fullstac
 
 1. Open [Google gems](https://gemini.google.com/gems/view)
 2. Create a new Gem - give it a title and description
-3. Copy the contents of `.<install location>/web-bundles/teams/team-fullstack.txt`
+3. Copy the contents of `.<install location>/<web-bundles>/teams/team-fullstack.txt` (location can vary if you chose a non default installation location for the bundles) - or just use the bundle premade from the repo dist folder.
 4. Paste this content into Gemini to set up the team
 
 ### Gemini Planning Phase

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

@@ -3,6 +3,7 @@ bundle:
   icon: 🎮
   description: Game Development team specialized in 2D games using Phaser 3 and TypeScript.
 agents:
+  - analyst
   - bmad-orchestrator
   - game-designer
   - game-developer

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

@@ -55,4 +55,4 @@ dependencies:
     - game-brief-tmpl
   checklists:
     - game-design-checklist
-```
+```

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

@@ -48,10 +48,10 @@ commands:
 task-execution:
   flow: Read story → Implement game feature → Write tests → Pass tests → Update [x] → Next task
   updates-ONLY:
-    - 'Checkboxes: [ ] not started | [-] in progress | [x] complete'
+    - "Checkboxes: [ ] not started | [-] in progress | [x] complete"
-    - 'Debug Log: | Task | File | Change | Reverted? |'
+    - "Debug Log: | Task | File | Change | Reverted? |"
-    - 'Completion Notes: Deviations only, <50 words'
+    - "Completion Notes: Deviations only, <50 words"
-    - 'Change Log: Requirement changes only'
+    - "Change Log: Requirement changes only"
   blocking: Unapproved deps | Ambiguous after story check | 3 failures | Missing game config
   done: Game feature works + Tests pass + 60 FPS + No lint errors + Follows Phaser 3 best practices
 dependencies:
@@ -63,4 +63,4 @@ dependencies:
     - game-story-dod-checklist
   data:
     - development-guidelines
-```
+```

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

@@ -33,7 +33,7 @@ startup:
   - CRITICAL: Do NOT create or modify any files during startup
   - Offer to help with game story preparation but wait for explicit user confirmation
   - Only execute tasks when user explicitly requests them
-  - 'CRITICAL RULE: You are ONLY allowed to create/modify story files - NEVER implement! If asked to implement, tell user they MUST switch to Game Developer Agent'
+  - "CRITICAL RULE: You are ONLY allowed to create/modify story files - NEVER implement! If asked to implement, tell user they MUST switch to Game Developer Agent"
 commands:
   - '*help" - Show numbered list of available commands for selection'
   - '*chat-mode" - Conversational mode with advanced-elicitation for game dev advice'
@@ -48,4 +48,4 @@ dependencies:
     - game-story-tmpl
   checklists:
     - game-story-dod-checklist
-```
+```

expansion-packs/bmad-2d-phaser-game-dev/checklists/game-design-checklist.md

@@ -3,6 +3,7 @@
 ## Document Completeness
 
 ### Executive Summary
+
 - [ ] **Core Concept** - Game concept is clearly explained in 2-3 sentences
 - [ ] **Target Audience** - Primary and secondary audiences defined with demographics
 - [ ] **Platform Requirements** - Technical platforms and requirements specified
@@ -10,6 +11,7 @@
 - [ ] **Technical Foundation** - Phaser 3 + TypeScript requirements confirmed
 
 ### Game Design Foundation
+
 - [ ] **Game Pillars** - 3-5 core design pillars defined and actionable
 - [ ] **Core Gameplay Loop** - 30-60 second loop documented with specific timings
 - [ ] **Win/Loss Conditions** - Clear victory and failure states defined
@@ -19,6 +21,7 @@
 ## Gameplay Mechanics
 
 ### Core Mechanics Documentation
+
 - [ ] **Primary Mechanics** - 3-5 core mechanics detailed with implementation notes
 - [ ] **Mechanic Integration** - How mechanics work together is clear
 - [ ] **Player Input** - All input methods specified for each platform
@@ -26,6 +29,7 @@
 - [ ] **Performance Impact** - Performance considerations for each mechanic noted
 
 ### Controls and Interaction
+
 - [ ] **Multi-Platform Controls** - Desktop, mobile, and gamepad controls defined
 - [ ] **Input Responsiveness** - Requirements for responsive game feel specified
 - [ ] **Accessibility Options** - Control customization and accessibility considered
@@ -35,6 +39,7 @@
 ## Progression and Balance
 
 ### Player Progression
+
 - [ ] **Progression Type** - Linear, branching, or metroidvania approach defined
 - [ ] **Key Milestones** - Major progression points documented
 - [ ] **Unlock System** - What players unlock and when is specified
@@ -42,6 +47,7 @@
 - [ ] **Player Agency** - Meaningful player choices and consequences defined
 
 ### Game Balance
+
 - [ ] **Balance Parameters** - Numeric values for key game systems provided
 - [ ] **Difficulty Curve** - Appropriate challenge progression designed
 - [ ] **Economy Design** - Resource systems balanced for engagement
@@ -51,6 +57,7 @@
 ## Level Design Framework
 
 ### Level Structure
+
 - [ ] **Level Types** - Different level categories defined with purposes
 - [ ] **Level Progression** - How players move through levels specified
 - [ ] **Duration Targets** - Expected play time for each level type
@@ -58,6 +65,7 @@
 - [ ] **Replay Value** - Elements that encourage repeated play designed
 
 ### Content Guidelines
+
 - [ ] **Level Creation Rules** - Clear guidelines for level designers
 - [ ] **Mechanic Introduction** - How new mechanics are taught in levels
 - [ ] **Pacing Variety** - Mix of action, puzzle, and rest moments planned
@@ -67,6 +75,7 @@
 ## Technical Implementation Readiness
 
 ### Performance Requirements
+
 - [ ] **Frame Rate Targets** - 60 FPS target with minimum acceptable rates
 - [ ] **Memory Budgets** - Maximum memory usage limits defined
 - [ ] **Load Time Goals** - Acceptable loading times for different content
@@ -74,6 +83,7 @@
 - [ ] **Scalability Plan** - How performance scales across different devices
 
 ### Platform Specifications
+
 - [ ] **Desktop Requirements** - Minimum and recommended PC/Mac specs
 - [ ] **Mobile Optimization** - iOS and Android specific requirements
 - [ ] **Browser Compatibility** - Supported browsers and versions listed
@@ -81,6 +91,7 @@
 - [ ] **Update Strategy** - Plan for post-launch updates and patches
 
 ### Asset Requirements
+
 - [ ] **Art Style Definition** - Clear visual style with reference materials
 - [ ] **Asset Specifications** - Technical requirements for all asset types
 - [ ] **Audio Requirements** - Music and sound effect specifications
@@ -90,6 +101,7 @@
 ## Development Planning
 
 ### Implementation Phases
+
 - [ ] **Phase Breakdown** - Development divided into logical phases
 - [ ] **Epic Definitions** - Major development epics identified
 - [ ] **Dependency Mapping** - Prerequisites between features documented
@@ -97,6 +109,7 @@
 - [ ] **Milestone Planning** - Key deliverables and deadlines established
 
 ### Team Requirements
+
 - [ ] **Role Definitions** - Required team roles and responsibilities
 - [ ] **Skill Requirements** - Technical skills needed for implementation
 - [ ] **Resource Allocation** - Time and effort estimates for major features
@@ -106,6 +119,7 @@
 ## Quality Assurance
 
 ### Success Metrics
+
 - [ ] **Technical Metrics** - Measurable technical performance goals
 - [ ] **Gameplay Metrics** - Player engagement and retention targets
 - [ ] **Quality Benchmarks** - Standards for bug rates and polish level
@@ -113,6 +127,7 @@
 - [ ] **Business Objectives** - Commercial or project success criteria
 
 ### Testing Strategy
+
 - [ ] **Playtesting Plan** - How and when player feedback will be gathered
 - [ ] **Technical Testing** - Performance and compatibility testing approach
 - [ ] **Balance Validation** - Methods for confirming game balance
@@ -122,6 +137,7 @@
 ## Documentation Quality
 
 ### Clarity and Completeness
+
 - [ ] **Clear Writing** - All sections are well-written and understandable
 - [ ] **Complete Coverage** - No major game systems left undefined
 - [ ] **Actionable Detail** - Enough detail for developers to create implementation stories
@@ -129,6 +145,7 @@
 - [ ] **Reference Materials** - Links to inspiration, research, and additional resources
 
 ### Maintainability
+
 - [ ] **Version Control** - Change log established for tracking revisions
 - [ ] **Update Process** - Plan for maintaining document during development
 - [ ] **Team Access** - All team members can access and reference the document
@@ -138,6 +155,7 @@
 ## Stakeholder Alignment
 
 ### Team Understanding
+
 - [ ] **Shared Vision** - All team members understand and agree with the game vision
 - [ ] **Role Clarity** - Each team member understands their contribution
 - [ ] **Decision Framework** - Process for making design decisions during development
@@ -145,6 +163,7 @@
 - [ ] **Communication Channels** - Regular meetings and feedback sessions planned
 
 ### External Validation
+
 - [ ] **Market Validation** - Competitive analysis and market fit assessment
 - [ ] **Technical Validation** - Feasibility confirmed with technical team
 - [ ] **Resource Validation** - Required resources available and committed
@@ -154,6 +173,7 @@
 ## Final Readiness Assessment
 
 ### Implementation Preparedness
+
 - [ ] **Story Creation Ready** - Document provides sufficient detail for story creation
 - [ ] **Architecture Alignment** - Game design aligns with technical capabilities
 - [ ] **Asset Production** - Asset requirements enable art and audio production
@@ -161,6 +181,7 @@
 - [ ] **Quality Assurance** - Testing and validation processes established
 
 ### Document Approval
+
 - [ ] **Design Review Complete** - Document reviewed by all relevant stakeholders
 - [ ] **Technical Review Complete** - Technical feasibility confirmed
 - [ ] **Business Review Complete** - Project scope and goals approved
@@ -177,4 +198,4 @@
 _List any critical items that need attention before moving to implementation phase._
 
 **Next Steps:**
-_Outline immediate next actions for the team based on this assessment._
+_Outline immediate next actions for the team based on this assessment._

expansion-packs/bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md

@@ -3,6 +3,7 @@
 ## Story Completeness
 
 ### Basic Story Elements
+
 - [ ] **Story Title** - Clear, descriptive title that identifies the feature
 - [ ] **Epic Assignment** - Story is properly assigned to relevant epic
 - [ ] **Priority Level** - Appropriate priority assigned (High/Medium/Low)
@@ -10,6 +11,7 @@
 - [ ] **Description** - Clear, concise description of what needs to be implemented
 
 ### Game Design Alignment
+
 - [ ] **GDD Reference** - Specific Game Design Document section referenced
 - [ ] **Game Mechanic Context** - Clear connection to game mechanics defined in GDD
 - [ ] **Player Experience Goal** - Describes the intended player experience
@@ -19,6 +21,7 @@
 ## Technical Specifications
 
 ### Architecture Compliance
+
 - [ ] **File Organization** - Follows game architecture document structure
 - [ ] **Class Definitions** - TypeScript interfaces and classes are properly defined
 - [ ] **Integration Points** - Clear specification of how feature integrates with existing systems
@@ -26,6 +29,7 @@
 - [ ] **Dependencies** - All system dependencies clearly identified
 
 ### Phaser 3 Requirements
+
 - [ ] **Scene Integration** - Specifies which scenes are affected and how
 - [ ] **Game Object Usage** - Proper use of Phaser 3 game objects and components
 - [ ] **Physics Integration** - Physics requirements specified if applicable
@@ -33,6 +37,7 @@
 - [ ] **Performance Considerations** - 60 FPS target and optimization requirements
 
 ### Code Quality Standards
+
 - [ ] **TypeScript Strict Mode** - All code must comply with strict TypeScript
 - [ ] **Error Handling** - Error scenarios and handling requirements specified
 - [ ] **Memory Management** - Object pooling and cleanup requirements where needed
@@ -42,6 +47,7 @@
 ## Implementation Readiness
 
 ### Acceptance Criteria
+
 - [ ] **Functional Requirements** - All functional acceptance criteria are specific and testable
 - [ ] **Technical Requirements** - Technical acceptance criteria are complete and verifiable
 - [ ] **Game Design Requirements** - Game-specific requirements match GDD specifications
@@ -49,6 +55,7 @@
 - [ ] **Completeness** - No acceptance criteria are vague or unmeasurable
 
 ### Implementation Tasks
+
 - [ ] **Task Breakdown** - Story broken into specific, ordered implementation tasks
 - [ ] **Task Scope** - Each task is completable in 1-4 hours
 - [ ] **Task Clarity** - Each task has clear, actionable instructions
@@ -56,6 +63,7 @@
 - [ ] **Development Flow** - Tasks follow logical implementation order
 
 ### Dependencies
+
 - [ ] **Story Dependencies** - All prerequisite stories identified with IDs
 - [ ] **Technical Dependencies** - Required systems and files identified
 - [ ] **Asset Dependencies** - All needed assets specified with locations
@@ -65,6 +73,7 @@
 ## Testing Requirements
 
 ### Test Coverage
+
 - [ ] **Unit Test Requirements** - Specific unit test files and scenarios defined
 - [ ] **Integration Test Cases** - Integration testing with other game systems specified
 - [ ] **Manual Test Cases** - Game-specific manual testing procedures defined
@@ -72,6 +81,7 @@
 - [ ] **Edge Case Testing** - Edge cases and error conditions covered
 
 ### Test Implementation
+
 - [ ] **Test File Paths** - Exact test file locations specified
 - [ ] **Test Scenarios** - All test scenarios are complete and executable
 - [ ] **Expected Behaviors** - Clear expected outcomes for all tests defined
@@ -81,6 +91,7 @@
 ## Game-Specific Quality
 
 ### Gameplay Implementation
+
 - [ ] **Mechanic Accuracy** - Implementation matches GDD mechanic specifications
 - [ ] **Player Controls** - Input handling requirements are complete
 - [ ] **Game Feel** - Requirements for juice, feedback, and responsiveness specified
@@ -88,6 +99,7 @@
 - [ ] **State Management** - Game state changes and persistence requirements defined
 
 ### User Experience
+
 - [ ] **UI Requirements** - User interface elements and behaviors specified
 - [ ] **Audio Integration** - Sound effect and music requirements defined
 - [ ] **Visual Feedback** - Animation and visual effect requirements specified
@@ -95,6 +107,7 @@
 - [ ] **Error Recovery** - User-facing error handling and recovery specified
 
 ### Performance Optimization
+
 - [ ] **Frame Rate Targets** - Specific FPS requirements for different platforms
 - [ ] **Memory Usage** - Memory consumption limits and monitoring requirements
 - [ ] **Asset Optimization** - Texture, audio, and data optimization requirements
@@ -104,6 +117,7 @@
 ## Documentation and Communication
 
 ### Story Documentation
+
 - [ ] **Implementation Notes** - Additional context and implementation guidance provided
 - [ ] **Design Decisions** - Key design choices documented with rationale
 - [ ] **Future Considerations** - Potential future enhancements or modifications noted
@@ -111,6 +125,7 @@
 - [ ] **Reference Materials** - Links to relevant GDD sections and architecture docs
 
 ### Developer Handoff
+
 - [ ] **Immediate Actionability** - Developer can start implementation without additional questions
 - [ ] **Complete Context** - All necessary context provided within the story
 - [ ] **Clear Boundaries** - What is and isn't included in the story scope is clear
@@ -120,6 +135,7 @@
 ## Final Validation
 
 ### Story Readiness
+
 - [ ] **No Ambiguity** - No sections require interpretation or additional design decisions
 - [ ] **Technical Completeness** - All technical requirements are specified and actionable
 - [ ] **Scope Appropriateness** - Story scope matches assigned story points
@@ -127,6 +143,7 @@
 - [ ] **Review Completion** - Story has been reviewed for completeness and accuracy
 
 ### Implementation Preparedness
+
 - [ ] **Environment Ready** - Development environment requirements specified
 - [ ] **Resources Available** - All required resources (assets, docs, dependencies) accessible
 - [ ] **Testing Prepared** - Testing environment and data requirements specified
@@ -140,4 +157,4 @@
 **Ready for Development:** [ ] Yes [ ] No
 
 **Additional Notes:**
-_Any specific concerns, recommendations, or clarifications needed before development begins._
+_Any specific concerns, recommendations, or clarifications needed before development begins._

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
+
+   - 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
@@ -82,6 +86,7 @@ You are developing games as a "Player Experience CEO" - thinking like a game dir
 ### Phaser 3 + TypeScript Standards
 
 **Project Structure:**
+
 ```text
 game-project/
 ├── src/
@@ -99,12 +104,14 @@ game-project/
 ```
 
 **Performance Requirements:**
+
 - Maintain 60 FPS on target devices
 - Memory usage under specified limits per level
 - Loading times under 3 seconds for levels
 - Smooth animation and responsive controls
 
 **Code Quality:**
+
 - TypeScript strict mode compliance
 - Component-based architecture
 - Object pooling for frequently created/destroyed objects
@@ -113,6 +120,7 @@ game-project/
 ### Game Development Story Structure
 
 **Story Requirements:**
+
 - Clear reference to Game Design Document section
 - Specific acceptance criteria for game functionality
 - Technical implementation details for Phaser 3
@@ -120,6 +128,7 @@ game-project/
 - Testing requirements including gameplay validation
 
 **Story Categories:**
+
 - **Core Mechanics**: Fundamental gameplay systems
 - **Level Content**: Individual levels and content implementation
 - **UI/UX**: User interface and player experience features
@@ -129,6 +138,7 @@ game-project/
 ### Quality Assurance for Games
 
 **Testing Approach:**
+
 - Unit tests for game logic (separate from Phaser)
 - Integration tests for game systems
 - Performance benchmarking and profiling
@@ -136,6 +146,7 @@ game-project/
 - Cross-platform compatibility testing
 
 **Performance Monitoring:**
+
 - Frame rate consistency tracking
 - Memory usage monitoring
 - Asset loading performance
@@ -145,16 +156,19 @@ game-project/
 ## Game Development Team Roles
 
 ### Game Designer (Alex)
+
 - **Primary Focus**: Game mechanics, player experience, design documentation
 - **Key Outputs**: Game Brief, Game Design Document, Level Design Framework
 - **Specialties**: Brainstorming, game balance, player psychology, creative direction
 
 ### Game Developer (Maya)
+
 - **Primary Focus**: Phaser 3 implementation, technical excellence, performance
 - **Key Outputs**: Working game features, optimized code, technical architecture
 - **Specialties**: TypeScript/Phaser 3, performance optimization, cross-platform development
 
 ### Game Scrum Master (Jordan)
+
 - **Primary Focus**: Story creation, development planning, agile process
 - **Key Outputs**: Detailed implementation stories, sprint planning, quality assurance
 - **Specialties**: Story breakdown, developer handoffs, process optimization
@@ -162,18 +176,21 @@ game-project/
 ## Platform-Specific Considerations
 
 ### Web Platform
+
 - Browser compatibility across modern browsers
 - Progressive loading for large assets
 - Touch-friendly mobile controls
 - Responsive design for different screen sizes
 
 ### Mobile Optimization
+
 - Touch gesture support and responsive controls
 - Battery usage optimization
 - Performance scaling for different device capabilities
 - App store compliance and packaging
 
 ### Performance Targets
+
 - **Desktop**: 60 FPS at 1080p resolution
 - **Mobile**: 60 FPS on mid-range devices, 30 FPS minimum on low-end
 - **Loading**: Initial load under 5 seconds, level transitions under 2 seconds
@@ -182,18 +199,21 @@ game-project/
 ## Success Metrics for Game Development
 
 ### Technical Metrics
+
 - Frame rate consistency (>90% of time at target FPS)
 - Memory usage within budgets
 - Loading time targets met
 - Zero critical bugs in core gameplay systems
 
 ### Player Experience Metrics
+
 - Tutorial completion rate >80%
 - Level completion rates appropriate for difficulty curve
 - Average session length meets design targets
 - Player retention and engagement metrics
 
 ### Development Process Metrics
+
 - Story completion within estimated timeframes
 - Code quality metrics (test coverage, linting compliance)
 - Documentation completeness and accuracy
@@ -202,6 +222,7 @@ game-project/
 ## Common Game Development Patterns
 
 ### Scene Management
+
 - Boot scene for initial setup and configuration
 - Preload scene for asset loading with progress feedback
 - Menu scene for navigation and settings
@@ -209,22 +230,25 @@ game-project/
 - Clean transitions between scenes with proper cleanup
 
 ### Game State Management
+
 - Persistent data (player progress, unlocks, settings)
 - Session data (current level, score, temporary state)
 - Save/load system with error recovery
 - Settings management with platform storage
 
 ### Input Handling
+
 - Cross-platform input abstraction
 - Touch gesture support for mobile
 - Keyboard and gamepad support for desktop
 - Customizable control schemes
 
 ### Performance Optimization
+
 - Object pooling for bullets, effects, enemies
 - Texture atlasing and sprite optimization
 - Audio compression and streaming
 - Culling and level-of-detail systems
 - 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.
+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.

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

@@ -9,6 +9,7 @@ This document establishes coding standards, architectural patterns, and developm
 ### Strict Mode Configuration
 
 **Required tsconfig.json settings:**
+
 ```json
 {
   "compilerOptions": {
@@ -22,11 +23,12 @@ This document establishes coding standards, architectural patterns, and developm
     "exactOptionalPropertyTypes": true
   }
 }
-```text
+```
 
 ### Type Definitions
 
 **Game Object Interfaces:**
+
 ```typescript
 // Core game entity interface
 interface GameEntity {
@@ -50,9 +52,10 @@ interface GameSystem {
   update(delta: number): void;
   shutdown(): void;
 }
-```text
+```
 
 **Scene Data Interfaces:**
+
 ```typescript
 // Scene transition data
 interface SceneData {
@@ -70,28 +73,32 @@ interface GameState {
 interface GameSettings {
   musicVolume: number;
   sfxVolume: number;
-  difficulty: 'easy' | 'normal' | 'hard';
+  difficulty: "easy" | "normal" | "hard";
   controls: ControlScheme;
 }
-```text
+```
 
 ### Naming Conventions
 
 **Classes and Interfaces:**
+
 - PascalCase for classes: `PlayerSprite`, `GameManager`, `AudioSystem`
 - PascalCase with 'I' prefix for interfaces: `IGameEntity`, `IPlayerController`
 - Descriptive names that indicate purpose: `CollisionManager` not `CM`
 
 **Methods and Variables:**
+
 - camelCase for methods and variables: `updatePosition()`, `playerSpeed`
 - Descriptive names: `calculateDamage()` not `calcDmg()`
 - Boolean variables with is/has/can prefix: `isActive`, `hasCollision`, `canMove`
 
 **Constants:**
+
 - UPPER_SNAKE_CASE for constants: `MAX_PLAYER_SPEED`, `DEFAULT_VOLUME`
 - Group related constants in enums or const objects
 
 **Files and Directories:**
+
 - kebab-case for file names: `player-controller.ts`, `audio-manager.ts`
 - PascalCase for scene files: `MenuScene.ts`, `GameScene.ts`
 
@@ -100,88 +107,91 @@ interface GameSettings {
 ### Scene Organization
 
 **Scene Lifecycle Management:**
+
 ```typescript
 class GameScene extends Phaser.Scene {
   private gameManager!: GameManager;
   private inputManager!: InputManager;
-  
+
   constructor() {
-    super({ key: 'GameScene' });
+    super({ key: "GameScene" });
   }
-  
+
   preload(): void {
     // Load only scene-specific assets
-    this.load.image('player', 'assets/player.png');
+    this.load.image("player", "assets/player.png");
   }
-  
+
   create(data: SceneData): void {
     // Initialize game systems
     this.gameManager = new GameManager(this);
     this.inputManager = new InputManager(this);
-    
+
     // Set up scene-specific logic
     this.setupGameObjects();
     this.setupEventListeners();
   }
-  
+
   update(time: number, delta: number): void {
     // Update all game systems
     this.gameManager.update(delta);
     this.inputManager.update(delta);
   }
-  
+
   shutdown(): void {
     // Clean up resources
     this.gameManager.destroy();
     this.inputManager.destroy();
-    
+
     // Remove event listeners
-    this.events.off('*');
+    this.events.off("*");
   }
 }
 ```
 
 **Scene Transitions:**
+
 ```typescript
 // Proper scene transitions with data
-this.scene.start('NextScene', {
+this.scene.start("NextScene", {
   playerScore: this.playerScore,
-  currentLevel: this.currentLevel + 1
+  currentLevel: this.currentLevel + 1,
 });
 
 // Scene overlays for UI
-this.scene.launch('PauseMenuScene');
+this.scene.launch("PauseMenuScene");
 this.scene.pause();
-```text
+```
 
 ### Game Object Patterns
 
 **Component-Based Architecture:**
+
 ```typescript
 // Base game entity
 abstract class GameEntity extends Phaser.GameObjects.Sprite {
   protected components: Map<string, GameComponent> = new Map();
-  
+
   constructor(scene: Phaser.Scene, x: number, y: number, texture: string) {
     super(scene, x, y, texture);
     scene.add.existing(this);
   }
-  
+
   addComponent<T extends GameComponent>(component: T): T {
     this.components.set(component.name, component);
     return component;
   }
-  
+
   getComponent<T extends GameComponent>(name: string): T | undefined {
     return this.components.get(name) as T;
   }
-  
+
   update(delta: number): void {
-    this.components.forEach(component => component.update(delta));
+    this.components.forEach((component) => component.update(delta));
   }
-  
+
   destroy(): void {
-    this.components.forEach(component => component.destroy());
+    this.components.forEach((component) => component.destroy());
     this.components.clear();
     super.destroy();
   }
@@ -191,65 +201,67 @@ abstract class GameEntity extends Phaser.GameObjects.Sprite {
 class Player extends GameEntity {
   private movement!: MovementComponent;
   private health!: HealthComponent;
-  
+
   constructor(scene: Phaser.Scene, x: number, y: number) {
-    super(scene, x, y, 'player');
+    super(scene, x, y, "player");
-    
+
     this.movement = this.addComponent(new MovementComponent(this));
     this.health = this.addComponent(new HealthComponent(this, 100));
   }
 }
-```text
+```
 
 ### System Management
 
 **Singleton Managers:**
+
 ```typescript
 class GameManager {
   private static instance: GameManager;
   private scene: Phaser.Scene;
   private gameState: GameState;
-  
+
   constructor(scene: Phaser.Scene) {
     if (GameManager.instance) {
-      throw new Error('GameManager already exists!');
+      throw new Error("GameManager already exists!");
     }
-    
+
     this.scene = scene;
     this.gameState = this.loadGameState();
     GameManager.instance = this;
   }
-  
+
   static getInstance(): GameManager {
     if (!GameManager.instance) {
-      throw new Error('GameManager not initialized!');
+      throw new Error("GameManager not initialized!");
     }
     return GameManager.instance;
   }
-  
+
   update(delta: number): void {
     // Update game logic
   }
-  
+
   destroy(): void {
     GameManager.instance = null!;
   }
 }
-```text
+```
 
 ## Performance Optimization
 
 ### Object Pooling
 
 **Required for High-Frequency Objects:**
+
 ```typescript
 class BulletPool {
   private pool: Bullet[] = [];
   private scene: Phaser.Scene;
-  
+
   constructor(scene: Phaser.Scene, initialSize: number = 50) {
     this.scene = scene;
-    
+
     // Pre-create bullets
     for (let i = 0; i < initialSize; i++) {
       const bullet = new Bullet(scene, 0, 0);
@@ -258,20 +270,20 @@ class BulletPool {
       this.pool.push(bullet);
     }
   }
-  
+
   getBullet(): Bullet | null {
-    const bullet = this.pool.find(b => !b.active);
+    const bullet = this.pool.find((b) => !b.active);
     if (bullet) {
       bullet.setActive(true);
       bullet.setVisible(true);
       return bullet;
     }
-    
+
     // Pool exhausted - create new bullet
-    console.warn('Bullet pool exhausted, creating new bullet');
+    console.warn("Bullet pool exhausted, creating new bullet");
     return new Bullet(this.scene, 0, 0);
   }
-  
+
   releaseBullet(bullet: Bullet): void {
     bullet.setActive(false);
     bullet.setVisible(false);
@@ -283,45 +295,47 @@ class BulletPool {
 ### Frame Rate Optimization
 
 **Performance Monitoring:**
+
 ```typescript
 class PerformanceMonitor {
   private frameCount: number = 0;
   private lastTime: number = 0;
   private frameRate: number = 60;
-  
+
   update(time: number): void {
     this.frameCount++;
-    
+
     if (time - this.lastTime >= 1000) {
       this.frameRate = this.frameCount;
       this.frameCount = 0;
       this.lastTime = time;
-      
+
       if (this.frameRate < 55) {
         console.warn(`Low frame rate detected: ${this.frameRate} FPS`);
         this.optimizePerformance();
       }
     }
   }
-  
+
   private optimizePerformance(): void {
     // Reduce particle counts, disable effects, etc.
   }
 }
-```text
+```
 
 **Update Loop Optimization:**
+
 ```typescript
 // Avoid expensive operations in update loops
 class GameScene extends Phaser.Scene {
   private updateTimer: number = 0;
   private readonly UPDATE_INTERVAL = 100; // ms
-  
+
   update(time: number, delta: number): void {
     // High-frequency updates (every frame)
     this.updatePlayer(delta);
     this.updatePhysics(delta);
-    
+
     // Low-frequency updates (10 times per second)
     this.updateTimer += delta;
     if (this.updateTimer >= this.UPDATE_INTERVAL) {
@@ -331,13 +345,14 @@ class GameScene extends Phaser.Scene {
     }
   }
 }
-```text
+```
 
 ## Input Handling
 
 ### Cross-Platform Input
 
 **Input Abstraction:**
+
 ```typescript
 interface InputState {
   moveLeft: boolean;
@@ -353,26 +368,26 @@ class InputManager {
     moveRight: false,
     jump: false,
     action: false,
-    pause: false
+    pause: false,
   };
-  
+
   private keys!: { [key: string]: Phaser.Input.Keyboard.Key };
   private pointer!: Phaser.Input.Pointer;
-  
+
   constructor(private scene: Phaser.Scene) {
     this.setupKeyboard();
     this.setupTouch();
   }
-  
+
   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 {
-    this.scene.input.on('pointerdown', this.handlePointerDown, this);
+    this.scene.input.on("pointerdown", this.handlePointerDown, this);
-    this.scene.input.on('pointerup', this.handlePointerUp, this);
+    this.scene.input.on("pointerup", this.handlePointerUp, this);
   }
-  
+
   update(): void {
     // Update input state from multiple sources
     this.inputState.moveLeft = this.keys.A.isDown || this.keys.LEFT.isDown;
@@ -380,42 +395,43 @@ class InputManager {
     this.inputState.jump = Phaser.Input.Keyboard.JustDown(this.keys.SPACE);
     // ... handle touch input
   }
-  
+
   getInputState(): InputState {
     return { ...this.inputState };
   }
 }
-```text
+```
 
 ## Error Handling
 
 ### Graceful Degradation
 
 **Asset Loading Error Handling:**
+
 ```typescript
 class AssetManager {
   loadAssets(): Promise<void> {
     return new Promise((resolve, reject) => {
-      this.scene.load.on('filecomplete', this.handleFileComplete, this);
+      this.scene.load.on("filecomplete", this.handleFileComplete, this);
-      this.scene.load.on('loaderror', this.handleLoadError, this);
+      this.scene.load.on("loaderror", this.handleLoadError, this);
-      this.scene.load.on('complete', () => resolve());
+      this.scene.load.on("complete", () => resolve());
-      
+
       this.scene.load.start();
     });
   }
-  
+
   private handleLoadError(file: Phaser.Loader.File): void {
     console.error(`Failed to load asset: ${file.key}`);
-    
+
     // Use fallback assets
     this.loadFallbackAsset(file.key);
   }
-  
+
   private loadFallbackAsset(key: string): void {
     // Load placeholder or default assets
     switch (key) {
-      case 'player':
+      case "player":
-        this.scene.load.image('player', 'assets/defaults/default-player.png');
+        this.scene.load.image("player", "assets/defaults/default-player.png");
         break;
       default:
         console.warn(`No fallback for asset: ${key}`);
@@ -427,25 +443,26 @@ class AssetManager {
 ### Runtime Error Recovery
 
 **System Error Handling:**
+
 ```typescript
 class GameSystem {
   protected handleError(error: Error, context: string): void {
     console.error(`Error in ${context}:`, error);
-    
+
     // Report to analytics/logging service
     this.reportError(error, context);
-    
+
     // Attempt recovery
     this.attemptRecovery(context);
   }
-  
+
   private attemptRecovery(context: string): void {
     switch (context) {
-      case 'update':
+      case "update":
         // Reset system state
         this.reset();
         break;
-      case 'render':
+      case "render":
         // Disable visual effects
         this.disableEffects();
         break;
@@ -455,64 +472,66 @@ class GameSystem {
     }
   }
 }
-```text
+```
 
 ## Testing Standards
 
 ### Unit Testing
 
 **Game Logic Testing:**
+
 ```typescript
 // Example test for game mechanics
-describe('HealthComponent', () => {
+describe("HealthComponent", () => {
   let healthComponent: HealthComponent;
-  
+
   beforeEach(() => {
     const mockEntity = {} as GameEntity;
     healthComponent = new HealthComponent(mockEntity, 100);
   });
-  
+
-  test('should initialize with correct health', () => {
+  test("should initialize with correct health", () => {
     expect(healthComponent.currentHealth).toBe(100);
     expect(healthComponent.maxHealth).toBe(100);
   });
-  
+
-  test('should handle damage correctly', () => {
+  test("should handle damage correctly", () => {
     healthComponent.takeDamage(25);
     expect(healthComponent.currentHealth).toBe(75);
     expect(healthComponent.isAlive()).toBe(true);
   });
-  
+
-  test('should handle death correctly', () => {
+  test("should handle death correctly", () => {
     healthComponent.takeDamage(150);
     expect(healthComponent.currentHealth).toBe(0);
     expect(healthComponent.isAlive()).toBe(false);
   });
 });
-```text
+```
 
 ### Integration Testing
 
 **Scene Testing:**
+
 ```typescript
-describe('GameScene Integration', () => {
+describe("GameScene Integration", () => {
   let scene: GameScene;
   let mockGame: Phaser.Game;
-  
+
   beforeEach(() => {
     // Mock Phaser game instance
     mockGame = createMockGame();
     scene = new GameScene();
   });
-  
+
-  test('should initialize all systems', () => {
+  test("should initialize all systems", () => {
     scene.create({});
-    
+
     expect(scene.gameManager).toBeDefined();
     expect(scene.inputManager).toBeDefined();
   });
 });
-```text
+```
 
 ## File Organization
 
@@ -566,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
@@ -593,6 +616,7 @@ src/
 ### Code Review Checklist
 
 **Before Committing:**
+
 - [ ] TypeScript compiles without errors
 - [ ] All tests pass
 - [ ] Performance targets met (60 FPS)
@@ -606,19 +630,22 @@ src/
 ## Performance Targets
 
 ### Frame Rate Requirements
+
 - **Desktop**: Maintain 60 FPS at 1080p
 - **Mobile**: Maintain 60 FPS on mid-range devices, minimum 30 FPS on low-end
 - **Optimization**: Implement dynamic quality scaling when performance drops
 
 ### Memory Management
+
 - **Total Memory**: Under 100MB for full game
 - **Per Scene**: Under 50MB per gameplay scene
 - **Asset Loading**: Progressive loading to stay under limits
 - **Garbage Collection**: Minimize object creation in update loops
 
 ### Loading Performance
+
 - **Initial Load**: Under 5 seconds for game start
 - **Scene Transitions**: Under 2 seconds between scenes
 - **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.
+These guidelines ensure consistent, high-quality game development that meets performance targets and maintains code quality across all implementation stories.

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

@@ -103,8 +103,9 @@ This elicitation task is specifically designed for game development and should b
 - **Platform Considerations**: When adapting designs for different devices and input methods
 
 The questions and perspectives offered should always consider:
+
 - Player psychology and motivation
 - Technical feasibility with Phaser 3 and TypeScript
 - Performance implications for 60 FPS targets
 - Cross-platform compatibility (desktop and mobile)
-- Game development best practices and common pitfalls
+- Game development best practices and common pitfalls

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

@@ -14,6 +14,7 @@ Create detailed, actionable game development stories that enable AI developers t
 ## Prerequisites
 
 Before creating stories, ensure you have:
+
 - Completed Game Design Document (GDD)
 - Game Architecture Document
 - Epic definition this story belongs to
@@ -24,12 +25,14 @@ Before creating stories, ensure you have:
 ### 1. Story Identification
 
 **Review Epic Context:**
+
 - Understand the epic's overall goal
 - Identify specific features that need implementation
 - Review any existing stories in the epic
 - Ensure no duplicate work
 
 **Feature Analysis:**
+
 - Reference specific GDD sections
 - Understand player experience goals
 - Identify technical complexity
@@ -38,12 +41,14 @@ Before creating stories, ensure you have:
 ### 2. Story Scoping
 
 **Single Responsibility:**
+
 - Focus on one specific game feature
 - Ensure story is completable in 1-3 days
 - Break down complex features into multiple stories
 - Maintain clear boundaries with other stories
 
 **Implementation Clarity:**
+
 - Define exactly what needs to be built
 - Specify all technical requirements
 - Include all necessary integration points
@@ -55,6 +60,7 @@ Before creating stories, ensure you have:
 Use `templates#game-story-tmpl` following all embedded LLM instructions
 
 **Key Focus Areas:**
+
 - Clear, actionable description
 - Specific acceptance criteria
 - Detailed technical specifications
@@ -64,18 +70,21 @@ Use `templates#game-story-tmpl` following all embedded LLM instructions
 ### 4. Story Validation
 
 **Technical Review:**
+
 - Verify all technical specifications are complete
 - Ensure integration points are clearly defined
 - Confirm file paths match architecture
 - Validate TypeScript interfaces and classes
 
 **Game Design Alignment:**
+
 - Confirm story implements GDD requirements
 - Verify player experience goals are met
 - Check balance parameters are included
 - Ensure game mechanics are correctly interpreted
 
 **Implementation Readiness:**
+
 - All dependencies identified
 - Assets requirements specified
 - Testing criteria defined
@@ -87,6 +96,7 @@ Use `templates#game-story-tmpl` following all embedded LLM instructions
 Execute `checklists#game-story-dod-checklist` against completed story
 
 **Story Criteria:**
+
 - Story is immediately actionable
 - No design decisions left to developer
 - Technical requirements are complete
@@ -96,12 +106,14 @@ Execute `checklists#game-story-dod-checklist` against completed story
 ### 6. Story Refinement
 
 **Developer Perspective:**
+
 - Can a developer start implementation immediately?
 - Are all technical questions answered?
 - Is the scope appropriate for the estimated points?
 - Are all dependencies clearly identified?
 
 **Iterative Improvement:**
+
 - Address any gaps or ambiguities
 - Clarify complex technical requirements
 - Ensure story fits within epic scope
@@ -110,6 +122,7 @@ Execute `checklists#game-story-dod-checklist` against completed story
 ## Story Elements Checklist
 
 ### Required Sections
+
 - [ ] Clear, specific description
 - [ ] Complete acceptance criteria (functional, technical, game design)
 - [ ] Detailed technical specifications
@@ -123,6 +136,7 @@ Execute `checklists#game-story-dod-checklist` against completed story
 - [ ] Definition of Done checklist
 
 ### Game-Specific Requirements
+
 - [ ] GDD section references
 - [ ] Game mechanic implementation details
 - [ ] Player experience goals
@@ -132,6 +146,7 @@ Execute `checklists#game-story-dod-checklist` against completed story
 - [ ] Cross-platform considerations
 
 ### Technical Quality
+
 - [ ] TypeScript strict mode compliance
 - [ ] Architecture document alignment
 - [ ] Code organization follows standards
@@ -142,18 +157,21 @@ Execute `checklists#game-story-dod-checklist` against completed story
 ## Common Pitfalls
 
 **Scope Issues:**
+
 - Story too large (break into multiple stories)
 - Story too vague (add specific requirements)
 - Missing dependencies (identify all prerequisites)
 - Unclear boundaries (define what's in/out of scope)
 
 **Technical Issues:**
+
 - Missing integration details
 - Incomplete technical specifications
 - Undefined interfaces or classes
 - Missing performance requirements
 
 **Game Design Issues:**
+
 - Not referencing GDD properly
 - Missing player experience context
 - Unclear game mechanic implementation
@@ -162,6 +180,7 @@ Execute `checklists#game-story-dod-checklist` against completed story
 ## Success Criteria
 
 **Story Readiness:**
+
 - [ ] Developer can start implementation immediately
 - [ ] No additional design decisions required
 - [ ] All technical questions answered
@@ -170,6 +189,7 @@ Execute `checklists#game-story-dod-checklist` against completed story
 - [ ] Story fits within epic scope
 
 **Quality Validation:**
+
 - [ ] Game story DOD checklist passes
 - [ ] Architecture alignment confirmed
 - [ ] GDD requirements covered
@@ -179,6 +199,7 @@ Execute `checklists#game-story-dod-checklist` against completed story
 ## Handoff Protocol
 
 **To Game Developer:**
+
 1. Provide story document
 2. Confirm GDD and architecture access
 3. Verify all dependencies are met
@@ -186,9 +207,10 @@ Execute `checklists#game-story-dod-checklist` against completed story
 5. Establish check-in schedule
 
 **Story Status Updates:**
+
 - Draft → Ready for Development
 - In Development → Code Review
 - Code Review → Testing
 - Testing → Done
 
-This task ensures game development stories are immediately actionable and enable efficient AI-driven development of game features.
+This task ensures game development stories are immediately actionable and enable efficient AI-driven development of game features.

expansion-packs/bmad-2d-phaser-game-dev/tasks/game-design-brainstorming.md

@@ -9,6 +9,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
 [[LLM: Begin by understanding the game design context and goals. Ask clarifying questions if needed to determine the best approach for game-specific ideation.]]
 
 1. **Establish Game Context**
+
    - Understand the game genre or opportunity area
    - Identify target audience and platform constraints
    - Determine session goals (concept exploration vs. mechanic refinement)
@@ -164,26 +165,31 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
 [[LLM: Help user select appropriate techniques based on their specific game design needs.]]
 
 **For Initial Game Concepts:**
+
 - What If Game Scenarios
 - Cross-Genre Fusion
 - Emotion-First Design
 
 **For Stuck/Blocked Creativity:**
+
 - Player Motivation Reversal
 - Constraint-Based Creativity
 - Genre Expectation Subversion
 
 **For Mechanic Development:**
+
 - SCAMPER for Game Mechanics
 - Core Loop Deconstruction
 - Player Agency Spectrum
 
 **For Player Experience:**
+
 - Player Archetype Brainstorming
 - Emotion-First Design
 - Accessibility-First Innovation
 
 **For World Building:**
+
 - Environmental Storytelling
 - Player-Generated Narrative
 - Platform-Specific Design
@@ -193,16 +199,19 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
 [[LLM: Guide the brainstorming session with appropriate pacing for game design exploration.]]
 
 1. **Inspiration Phase** (10-15 min)
+
    - Reference existing games and mechanics
    - Explore player experiences and emotions
    - Gather visual and thematic inspiration
 
 2. **Divergent Exploration** (25-35 min)
+
    - Generate many game concepts or mechanics
    - Use expansion and fusion techniques
    - Encourage wild and impossible ideas
 
 3. **Player-Centered Filtering** (15-20 min)
+
    - Consider target audience reactions
    - Evaluate emotional impact and engagement
    - Group ideas by player experience goals
@@ -217,6 +226,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
 [[LLM: Present brainstorming results in a format useful for game development.]]
 
 **Session Summary:**
+
 - Techniques used and focus areas
 - Total concepts/mechanics generated
 - Key themes and patterns identified
@@ -232,21 +242,25 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
 **Development Readiness:**
 
 **Prototype-Ready Ideas:**
+
 - Ideas that can be tested immediately
 - Minimum viable implementations
 - Quick validation approaches
 
 **Research-Required Ideas:**
+
 - Concepts needing technical investigation
 - Player testing and market research needs
 - Competitive analysis requirements
 
 **Future Innovation Pipeline:**
+
 - Ideas requiring significant development
 - Technology-dependent concepts
 - Market timing considerations
 
 **Next Steps:**
+
 - Which concepts to prototype first
 - Recommended research areas
 - Suggested playtesting approaches
@@ -255,24 +269,28 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
 ## Game Design Specific Considerations
 
 ### Platform and Audience Awareness
+
 - Always consider target platform limitations and advantages
 - Keep target audience preferences and expectations in mind
 - Balance innovation with familiar game design patterns
 - Consider monetization and business model implications
 
 ### Rapid Prototyping Mindset
+
 - Focus on ideas that can be quickly tested
 - Emphasize core mechanics over complex features
 - Design for iteration and player feedback
 - Consider digital and paper prototyping approaches
 
 ### Player Psychology Integration
+
 - Understand motivation and engagement drivers
 - Consider learning curves and skill development
 - Design for different play session lengths
 - Balance challenge and reward appropriately
 
 ### Technical Feasibility
+
 - Keep development resources and timeline in mind
 - Consider art and audio asset requirements
 - Think about performance and optimization needs
@@ -287,4 +305,4 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
 - Think about community and social aspects of gameplay
 - Consider accessibility and inclusivity from the start
 - Balance innovation with market viability
-- Plan for iteration based on player feedback
+- Plan for iteration based on player feedback

expansion-packs/bmad-2d-phaser-game-dev/templates/game-architecture-tmpl.md

@@ -80,7 +80,7 @@ This architecture is designed to support the gameplay mechanics defined in the G
 │   ├── stories/         # Development stories
 │   └── architecture/    # Technical docs
 └── dist/                # Built game files
-```text
+```
 
 ### Module Organization
 
@@ -365,7 +365,7 @@ const gameConfig: Phaser.Types.Core.GameConfig = {
     },
     // Additional configuration...
 };
-```text
+```
 
 ### Game Balance Configuration
 

expansion-packs/bmad-2d-phaser-game-dev/templates/game-brief-tmpl.md

@@ -60,11 +60,13 @@ This brief is typically created early in the ideation process, often after brain
 [[LLM: List the 3-5 most important gameplay mechanics that define the player experience]]
 
 **Core Mechanic 1: {{mechanic_name}}**
+
 - **Description:** {{how_it_works}}
 - **Player Value:** {{why_its_fun}}
 - **Implementation Scope:** {{complexity_estimate}}
 
 **Core Mechanic 2: {{mechanic_name}}**
+
 - **Description:** {{how_it_works}}
 - **Player Value:** {{why_its_fun}}
 - **Implementation Scope:** {{complexity_estimate}}
@@ -91,10 +93,12 @@ This brief is typically created early in the ideation process, often after brain
 ### Technical Constraints
 
 **Platform Requirements:**
+
 - Primary: {{platform_1}} - {{requirements}}
 - Secondary: {{platform_2}} - {{requirements}}
 
 **Technical Specifications:**
+
 - Engine: Phaser 3 + TypeScript
 - Performance Target: {{fps_target}} FPS on {{target_device}}
 - Memory Budget: <{{memory_limit}}MB
@@ -125,6 +129,7 @@ This brief is typically created early in the ideation process, often after brain
 ### Inspiration Games
 
 **Primary References:**
+
 1. **{{reference_game_1}}** - {{what_we_learn_from_it}}
 2. **{{reference_game_2}}** - {{what_we_learn_from_it}}
 3. **{{reference_game_3}}** - {{what_we_learn_from_it}}
@@ -132,6 +137,7 @@ This brief is typically created early in the ideation process, often after brain
 ### Competitive Analysis
 
 **Direct Competitors:**
+
 - {{competitor_1}}: {{strengths_and_weaknesses}}
 - {{competitor_2}}: {{strengths_and_weaknesses}}
 
@@ -157,13 +163,16 @@ This brief is typically created early in the ideation process, often after brain
 ### Content Categories
 
 **Core Content:**
+
 - {{content_type_1}}: {{quantity_and_description}}
 - {{content_type_2}}: {{quantity_and_description}}
 
 **Optional Content:**
+
 - {{optional_content_type}}: {{quantity_and_description}}
 
 **Replay Elements:**
+
 - {{replayability_features}}
 
 ### Difficulty and Accessibility
@@ -201,23 +210,23 @@ This brief is typically created early in the ideation process, often after brain
 
 ### Technical Risks
 
-| Risk | Probability | Impact | Mitigation Strategy |
+| Risk                 | Probability | Impact | Mitigation Strategy |
-|------|-------------|--------|-------------------|
+| -------------------- | ----------- | ------ | ------------------- | ------ | --- | ----- | ----------------------- |
-| {{technical_risk_1}} | {{high|med|low}} | {{high|med|low}} | {{mitigation_approach}} |
+| {{technical_risk_1}} | {{high      | med    | low}}               | {{high | med | low}} | {{mitigation_approach}} |
-| {{technical_risk_2}} | {{high|med|low}} | {{high|med|low}} | {{mitigation_approach}} |
+| {{technical_risk_2}} | {{high      | med    | low}}               | {{high | med | low}} | {{mitigation_approach}} |
 
 ### Design Risks
 
-| Risk | Probability | Impact | Mitigation Strategy |
+| Risk              | Probability | Impact | Mitigation Strategy |
-|------|-------------|--------|-------------------|
+| ----------------- | ----------- | ------ | ------------------- | ------ | --- | ----- | ----------------------- |
-| {{design_risk_1}} | {{high|med|low}} | {{high|med|low}} | {{mitigation_approach}} |
+| {{design_risk_1}} | {{high      | med    | low}}               | {{high | med | low}} | {{mitigation_approach}} |
-| {{design_risk_2}} | {{high|med|low}} | {{high|med|low}} | {{mitigation_approach}} |
+| {{design_risk_2}} | {{high      | med    | low}}               | {{high | med | low}} | {{mitigation_approach}} |
 
 ### Market Risks
 
-| Risk | Probability | Impact | Mitigation Strategy |
+| Risk              | Probability | Impact | Mitigation Strategy |
-|------|-------------|--------|-------------------|
+| ----------------- | ----------- | ------ | ------------------- | ------ | --- | ----- | ----------------------- |
-| {{market_risk_1}} | {{high|med|low}} | {{high|med|low}} | {{mitigation_approach}} |
+| {{market_risk_1}} | {{high      | med    | low}}               | {{high | med | low}} | {{mitigation_approach}} |
 
 ## Success Criteria
 
@@ -226,11 +235,13 @@ This brief is typically created early in the ideation process, often after brain
 ### Player Experience Metrics
 
 **Engagement Goals:**
+
 - Tutorial completion rate: >{{percentage}}%
 - Average session length: {{duration}} minutes
 - Player retention: D1 {{d1}}%, D7 {{d7}}%, D30 {{d30}}%
 
 **Quality Benchmarks:**
+
 - Player satisfaction: >{{rating}}/10
 - Completion rate: >{{percentage}}%
 - Technical performance: {{fps_target}} FPS consistent
@@ -238,11 +249,13 @@ This brief is typically created early in the ideation process, often after brain
 ### Development Metrics
 
 **Technical Targets:**
+
 - Zero critical bugs at launch
 - Performance targets met on all platforms
 - Load times under {{seconds}}s
 
 **Process Goals:**
+
 - Development timeline adherence
 - Feature scope completion
 - Quality assurance standards
@@ -252,6 +265,7 @@ This brief is typically created early in the ideation process, often after brain
 ### Business Metrics
 
 **Commercial Goals:**
+
 - {{revenue_target}} in first {{time_period}}
 - {{user_acquisition_target}} players in first {{time_period}}
 - {{retention_target}} monthly active users
@@ -271,16 +285,19 @@ This brief is typically created early in the ideation process, often after brain
 ### Development Roadmap
 
 **Phase 1: Pre-Production** ({{duration}})
+
 - Detailed Game Design Document creation
 - Technical architecture planning
 - Art style exploration and pipeline setup
 
 **Phase 2: Prototype** ({{duration}})
+
 - Core mechanic implementation
 - Technical proof of concept
 - Initial playtesting and iteration
 
 **Phase 3: Production** ({{duration}})
+
 - Full feature development
 - Content creation and integration
 - Comprehensive testing and optimization
@@ -288,6 +305,7 @@ This brief is typically created early in the ideation process, often after brain
 ### Documentation Pipeline
 
 **Required Documents:**
+
 1. Game Design Document (GDD) - {{target_completion}}
 2. Technical Architecture Document - {{target_completion}}
 3. Art Style Guide - {{target_completion}}
@@ -296,10 +314,12 @@ This brief is typically created early in the ideation process, often after brain
 ### Validation Plan
 
 **Concept Testing:**
+
 - {{validation_method_1}} - {{timeline}}
 - {{validation_method_2}} - {{timeline}}
 
 **Prototype Testing:**
+
 - {{testing_approach}} - {{timeline}}
 - {{feedback_collection_method}} - {{timeline}}
 
@@ -322,4 +342,4 @@ This brief is typically created early in the ideation process, often after brain
 [[LLM: Track document versions and changes]]
 
 | Date | Version | Description | Author |
-| :--- | :------ | :---------- | :----- |
+| :--- | :------ | :---------- | :----- |

expansion-packs/bmad-2d-phaser-game-dev/templates/game-design-doc-tmpl.md

@@ -53,6 +53,7 @@ If available, review any provided documents or ask if any are optionally availab
 [[LLM: Define the 30-60 second loop that players will repeat. Be specific about timing and player actions.]]
 
 **Primary Loop ({{duration}} seconds):**
+
 1. {{action_1}} ({{time_1}}s)
 2. {{action_2}} ({{time_2}}s)
 3. {{action_3}} ({{time_3}}s)
@@ -63,10 +64,12 @@ If available, review any provided documents or ask if any are optionally availab
 [[LLM: Clearly define success and failure states]]
 
 **Victory Conditions:**
+
 - {{win_condition_1}}
 - {{win_condition_2}}
 
 **Failure States:**
+
 - {{loss_condition_1}}
 - {{loss_condition_2}}
 
@@ -87,6 +90,7 @@ If available, review any provided documents or ask if any are optionally availab
 **System Response:** {{game_response}}
 
 **Implementation Notes:**
+
 - {{tech_requirement_1}}
 - {{tech_requirement_2}}
 - {{performance_consideration}}
@@ -99,8 +103,8 @@ If available, review any provided documents or ask if any are optionally availab
 
 [[LLM: Define all input methods for different platforms]]
 
-| Action | Desktop | Mobile | Gamepad |
+| Action       | Desktop | Mobile      | Gamepad    |
-|--------|---------|--------|---------|
+| ------------ | ------- | ----------- | ---------- |
 | {{action_1}} | {{key}} | {{gesture}} | {{button}} |
 | {{action_2}} | {{key}} | {{gesture}} | {{button}} |
 
@@ -113,6 +117,7 @@ If available, review any provided documents or ask if any are optionally availab
 **Progression Type:** {{linear|branching|metroidvania}}
 
 **Key Milestones:**
+
 1. **{{milestone_1}}** - {{unlock_description}}
 2. **{{milestone_2}}** - {{unlock_description}}
 3. **{{milestone_3}}** - {{unlock_description}}
@@ -132,9 +137,9 @@ If available, review any provided documents or ask if any are optionally availab
 
 [[LLM: Define any in-game currencies, resources, or collectibles]]
 
-| Resource | Earn Rate | Spend Rate | Purpose | Cap |
+| Resource       | Earn Rate | Spend Rate | Purpose | Cap     |
-|----------|-----------|------------|---------|-----|
+| -------------- | --------- | ---------- | ------- | ------- |
-| {{resource_1}} | {{rate}} | {{rate}} | {{use}} | {{max}} |
+| {{resource_1}} | {{rate}}  | {{rate}}   | {{use}} | {{max}} |
 
 ^^/CONDITION: has_economy^^
 
@@ -154,6 +159,7 @@ If available, review any provided documents or ask if any are optionally availab
 **Difficulty:** {{relative_difficulty}}
 
 **Structure Template:**
+
 - Introduction: {{intro_description}}
 - Challenge: {{main_challenge}}
 - Resolution: {{completion_requirement}}
@@ -180,11 +186,13 @@ If available, review any provided documents or ask if any are optionally availab
 ### Platform Specific
 
 **Desktop:**
+
 - Resolution: {{min_resolution}} - {{max_resolution}}
 - Input: Keyboard, Mouse, Gamepad
 - Browser: Chrome 80+, Firefox 75+, Safari 13+
 
 **Mobile:**
+
 - Resolution: {{mobile_min}} - {{mobile_max}}
 - Input: Touch, Tilt (optional)
 - OS: iOS 13+, Android 8+
@@ -194,12 +202,14 @@ If available, review any provided documents or ask if any are optionally availab
 [[LLM: Define asset specifications for the art and audio teams]]
 
 **Visual Assets:**
+
 - Art Style: {{style_description}}
 - Color Palette: {{color_specification}}
 - Animation: {{animation_requirements}}
 - UI Resolution: {{ui_specs}}
 
 **Audio Assets:**
+
 - Music Style: {{music_genre}}
 - Sound Effects: {{sfx_requirements}}
 - Voice Acting: {{voice_needs}}
@@ -211,6 +221,7 @@ If available, review any provided documents or ask if any are optionally availab
 ### Engine Configuration
 
 **Phaser 3 Setup:**
+
 - TypeScript: Strict mode enabled
 - Physics: {{physics_system}} (Arcade/Matter)
 - Renderer: WebGL with Canvas fallback
@@ -219,6 +230,7 @@ If available, review any provided documents or ask if any are optionally availab
 ### Code Architecture
 
 **Required Systems:**
+
 - Scene Management
 - State Management
 - Asset Loading
@@ -230,6 +242,7 @@ If available, review any provided documents or ask if any are optionally availab
 ### Data Management
 
 **Save Data:**
+
 - Progress tracking
 - Settings persistence
 - Statistics collection
@@ -242,12 +255,14 @@ If available, review any provided documents or ask if any are optionally availab
 ### Phase 1: Core Systems ({{duration}})
 
 **Epic: Foundation**
+
 - Engine setup and configuration
 - Basic scene management
 - Core input handling
 - Asset loading pipeline
 
 **Epic: Core Mechanics**
+
 - {{primary_mechanic}} implementation
 - Basic physics and collision
 - Player controller
@@ -255,11 +270,13 @@ If available, review any provided documents or ask if any are optionally availab
 ### Phase 2: Gameplay Features ({{duration}})
 
 **Epic: Game Systems**
+
 - {{mechanic_2}} implementation
 - {{mechanic_3}} implementation
 - Game state management
 
 **Epic: Content Creation**
+
 - Level loading system
 - First playable levels
 - Basic UI implementation
@@ -267,11 +284,13 @@ If available, review any provided documents or ask if any are optionally availab
 ### Phase 3: Polish & Optimization ({{duration}})
 
 **Epic: Performance**
+
 - Optimization and profiling
 - Mobile platform testing
 - Memory management
 
 **Epic: User Experience**
+
 - Audio implementation
 - Visual effects and polish
 - Final UI/UX refinement
@@ -281,12 +300,14 @@ If available, review any provided documents or ask if any are optionally availab
 [[LLM: Define measurable goals for the game]]
 
 **Technical Metrics:**
+
 - Frame rate: {{fps_target}}
 - Load time: {{load_target}}
 - Crash rate: <{{crash_threshold}}%
 - Memory usage: <{{memory_target}}MB
 
 **Gameplay Metrics:**
+
 - Tutorial completion: {{completion_rate}}%
 - Average session: {{session_length}} minutes
 - Level completion: {{level_completion}}%
@@ -307,4 +328,4 @@ If available, review any provided documents or ask if any are optionally availab
 
 - {{reference_1}}
 - {{reference_2}}
-- {{reference_3}}
+- {{reference_3}}

expansion-packs/bmad-2d-phaser-game-dev/templates/level-design-doc-tmpl.md

@@ -64,19 +64,23 @@ This framework ensures consistency across all levels while providing flexibility
 **Difficulty Range:** {{difficulty_scale}}
 
 **Key Mechanics Featured:**
+
 - {{mechanic_1}} - {{usage_description}}
 - {{mechanic_2}} - {{usage_description}}
 
 **Player Objectives:**
+
 - Primary: {{primary_objective}}
 - Secondary: {{secondary_objective}}
 - Hidden: {{secret_objective}}
 
 **Success Criteria:**
+
 - {{completion_requirement_1}}
 - {{completion_requirement_2}}
 
 **Technical Requirements:**
+
 - Maximum entities: {{entity_limit}}
 - Performance target: {{fps_target}} FPS
 - Memory budget: {{memory_limit}}MB
@@ -97,6 +101,7 @@ This framework ensures consistency across all levels while providing flexibility
 **Total Level Count:** {{number}}
 
 **World Breakdown:**
+
 - World 1: {{level_count}} levels - {{theme}} - {{difficulty_range}}
 - World 2: {{level_count}} levels - {{theme}} - {{difficulty_range}}
 - World 3: {{level_count}} levels - {{theme}} - {{difficulty_range}}
@@ -106,7 +111,8 @@ This framework ensures consistency across all levels while providing flexibility
 [[LLM: Define how challenge increases across the game]]
 
 **Progression Curve:**
-```text
+
+````text
 Difficulty
     ^     ___/```
     |    /
@@ -116,9 +122,10 @@ Difficulty
     |/     /
     +-----------> Level Number
    Tutorial  Early  Mid  Late
-```text
+````
 
 **Scaling Parameters:**
+
 - Enemy count: {{start_count}} → {{end_count}}
 - Enemy difficulty: {{start_diff}} → {{end_diff}}
 - Level complexity: {{start_complex}} → {{end_complex}}
@@ -129,6 +136,7 @@ Difficulty
 [[LLM: Define how players access new levels]]
 
 **Progression Gates:**
+
 - Linear progression: Complete previous level
 - Star requirements: {{star_count}} stars to unlock
 - Skill gates: Demonstrate {{skill_requirement}}
@@ -143,14 +151,17 @@ Difficulty
 [[LLM: Define all environmental components that can be used in levels]]
 
 **Terrain Types:**
+
 - {{terrain_1}}: {{properties_and_usage}}
 - {{terrain_2}}: {{properties_and_usage}}
 
 **Interactive Objects:**
+
 - {{object_1}}: {{behavior_and_purpose}}
 - {{object_2}}: {{behavior_and_purpose}}
 
 **Hazards and Obstacles:**
+
 - {{hazard_1}}: {{damage_and_behavior}}
 - {{hazard_2}}: {{damage_and_behavior}}
 
@@ -159,15 +170,18 @@ Difficulty
 [[LLM: Define all collectible items and their placement rules]]
 
 **Collectible Types:**
+
 - {{collectible_1}}: {{value_and_purpose}}
 - {{collectible_2}}: {{value_and_purpose}}
 
 **Placement Guidelines:**
+
 - Mandatory collectibles: {{placement_rules}}
 - Optional collectibles: {{placement_rules}}
 - Secret collectibles: {{placement_rules}}
 
 **Reward Distribution:**
+
 - Easy to find: {{percentage}}%
 - Moderate challenge: {{percentage}}%
 - High skill required: {{percentage}}%
@@ -177,15 +191,18 @@ Difficulty
 [[LLM: Define how enemies should be placed and balanced in levels]]
 
 **Enemy Categories:**
+
 - {{enemy_type_1}}: {{behavior_and_usage}}
 - {{enemy_type_2}}: {{behavior_and_usage}}
 
 **Placement Principles:**
+
 - Introduction encounters: {{guideline}}
 - Standard encounters: {{guideline}}
 - Challenge encounters: {{guideline}}
 
 **Difficulty Scaling:**
+
 - Enemy count progression: {{scaling_rule}}
 - Enemy type introduction: {{pacing_rule}}
 - Encounter complexity: {{complexity_rule}}
@@ -197,12 +214,14 @@ Difficulty
 ### Level Layout Principles
 
 **Spatial Design:**
+
 - Grid size: {{grid_dimensions}}
 - Minimum path width: {{width_units}}
 - Maximum vertical distance: {{height_units}}
 - Safe zones placement: {{safety_guidelines}}
 
 **Navigation Design:**
+
 - Clear path indication: {{visual_cues}}
 - Landmark placement: {{landmark_rules}}
 - Dead end avoidance: {{dead_end_policy}}
@@ -213,11 +232,13 @@ Difficulty
 [[LLM: Define how to control the rhythm and pace of gameplay within levels]]
 
 **Action Sequences:**
+
 - High intensity duration: {{max_duration}}
 - Rest period requirement: {{min_rest_time}}
 - Intensity variation: {{pacing_pattern}}
 
 **Learning Sequences:**
+
 - New mechanic introduction: {{teaching_method}}
 - Practice opportunity: {{practice_duration}}
 - Skill application: {{application_context}}
@@ -227,12 +248,14 @@ Difficulty
 [[LLM: Define how to create appropriate challenges for each level type]]
 
 **Challenge Types:**
+
 - Execution challenges: {{skill_requirements}}
 - Puzzle challenges: {{complexity_guidelines}}
 - Time challenges: {{time_pressure_rules}}
 - Resource challenges: {{resource_management}}
 
 **Difficulty Calibration:**
+
 - Skill check frequency: {{frequency_guidelines}}
 - Failure recovery: {{retry_mechanics}}
 - Hint system integration: {{help_system}}
@@ -246,11 +269,13 @@ Difficulty
 [[LLM: Define how level data should be structured for implementation]]
 
 **Level File Format:**
+
 - Data format: {{json|yaml|custom}}
 - File naming: `level_{{world}}_{{number}}.{{extension}}`
 - Data organization: {{structure_description}}
 
 **Required Data Fields:**
+
 ```json
 {
   "levelId": "{{unique_identifier}}",
@@ -282,12 +307,14 @@ Difficulty
 [[LLM: Define how level assets are organized and loaded]]
 
 **Tilemap Requirements:**
+
 - Tile size: {{tile_dimensions}}px
 - Tileset organization: {{tileset_structure}}
 - Layer organization: {{layer_system}}
 - Collision data: {{collision_format}}
 
 **Audio Integration:**
+
 - Background music: {{music_requirements}}
 - Ambient sounds: {{ambient_system}}
 - Dynamic audio: {{dynamic_audio_rules}}
@@ -297,16 +324,19 @@ Difficulty
 [[LLM: Define performance requirements for level systems]]
 
 **Entity Limits:**
+
 - Maximum active entities: {{entity_limit}}
 - Maximum particles: {{particle_limit}}
 - Maximum audio sources: {{audio_limit}}
 
 **Memory Management:**
+
 - Texture memory budget: {{texture_memory}}MB
 - Audio memory budget: {{audio_memory}}MB
 - Level loading time: <{{load_time}}s
 
 **Culling and LOD:**
+
 - Off-screen culling: {{culling_distance}}
 - Level-of-detail rules: {{lod_system}}
 - Asset streaming: {{streaming_requirements}}
@@ -318,11 +348,13 @@ Difficulty
 ### Automated Testing
 
 **Performance Testing:**
+
 - Frame rate validation: Maintain {{fps_target}} FPS
 - Memory usage monitoring: Stay under {{memory_limit}}MB
 - Loading time verification: Complete in <{{load_time}}s
 
 **Gameplay Testing:**
+
 - Completion path validation: All objectives achievable
 - Collectible accessibility: All items reachable
 - Softlock prevention: No unwinnable states
@@ -330,6 +362,7 @@ Difficulty
 ### Manual Testing Protocol
 
 **Playtesting Checklist:**
+
 - [ ] Level completes within target time range
 - [ ] All mechanics function correctly
 - [ ] Difficulty feels appropriate for level category
@@ -337,6 +370,7 @@ Difficulty
 - [ ] No exploits or sequence breaks (unless intended)
 
 **Player Experience Testing:**
+
 - [ ] Tutorial levels teach effectively
 - [ ] Challenge feels fair and rewarding
 - [ ] Flow and pacing maintain engagement
@@ -345,12 +379,14 @@ Difficulty
 ### Balance Validation
 
 **Metrics Collection:**
+
 - Completion rate: Target {{completion_percentage}}%
 - Average completion time: {{target_time}} ± {{variance}}
 - Death count per level: <{{max_deaths}}
 - Collectible discovery rate: {{discovery_percentage}}%
 
 **Iteration Guidelines:**
+
 - Adjustment criteria: {{criteria_for_changes}}
 - Testing sample size: {{minimum_testers}}
 - Validation period: {{testing_duration}}
@@ -362,12 +398,14 @@ Difficulty
 ### Design Phase
 
 **Concept Development:**
+
 1. Define level purpose and goals
 2. Create rough layout sketch
 3. Identify key mechanics and challenges
 4. Estimate difficulty and duration
 
 **Documentation Requirements:**
+
 - Level design brief
 - Layout diagrams
 - Mechanic integration notes
@@ -376,6 +414,7 @@ Difficulty
 ### Implementation Phase
 
 **Technical Implementation:**
+
 1. Create level data file
 2. Build tilemap and layout
 3. Place entities and objects
@@ -383,6 +422,7 @@ Difficulty
 5. Integrate audio and visual effects
 
 **Quality Assurance:**
+
 1. Automated testing execution
 2. Internal playtesting
 3. Performance validation
@@ -391,12 +431,14 @@ Difficulty
 ### Integration Phase
 
 **Game Integration:**
+
 1. Level progression integration
 2. Save system compatibility
 3. Analytics integration
 4. Achievement system integration
 
 **Final Validation:**
+
 1. Full game context testing
 2. Performance regression testing
 3. Platform compatibility verification
@@ -407,19 +449,22 @@ Difficulty
 [[LLM: Define how to measure level design success]]
 
 **Player Engagement:**
+
 - Level completion rate: {{target_rate}}%
 - Replay rate: {{replay_target}}%
 - Time spent per level: {{engagement_time}}
 - Player satisfaction scores: {{satisfaction_target}}/10
 
 **Technical Performance:**
+
 - Frame rate consistency: {{fps_consistency}}%
 - Loading time compliance: {{load_compliance}}%
 - Memory usage efficiency: {{memory_efficiency}}%
 - Crash rate: <{{crash_threshold}}%
 
 **Design Quality:**
+
 - Difficulty curve adherence: {{curve_accuracy}}
 - Mechanic integration effectiveness: {{integration_score}}
 - Player guidance clarity: {{guidance_score}}
-- Content accessibility: {{accessibility_rate}}%
+- Content accessibility: {{accessibility_rate}}%

expansion-packs/bmad-infrastructure-devops/README.md

@@ -66,13 +66,13 @@ To install this expansion pack, run:
 
 ```bash
 npm run install:expansion infrastructure
-```text
+```
 
 Or manually:
 
 ```bash
 node tools/install-expansion-pack.js infrastructure
-```text
+```
 
 This will:
 
@@ -92,7 +92,7 @@ After the main architecture is complete:
 
 # Or directly with DevOps agent
 npm run agent devops
-```text
+```
 
 ### 2. Platform Implementation
 

expansion-packs/bmad-infrastructure-devops/agents/infra-devops-platform.md

@@ -31,8 +31,8 @@ persona:
     - Collaborative Operations - Work closely with development teams fostering shared responsibility for system reliability
 startup:
   - Announce: Hey! I'm Alex, your DevOps Infrastructure Specialist. I love when things run secure, stable, reliable and performant. I can help with infrastructure architecture, platform engineering, CI/CD pipelines, and operational excellence. What infrastructure challenge can I help you with today?
-  - 'List available tasks: review-infrastructure, validate-infrastructure, create infrastructure documentation'
+  - "List available tasks: review-infrastructure, validate-infrastructure, create infrastructure documentation"
-  - 'List available templates: infrastructure-architecture, infrastructure-platform-from-arch'
+  - "List available templates: infrastructure-architecture, infrastructure-platform-from-arch"
   - Execute selected task or stay in persona to help guided by Core DevOps Principles
 commands:
   - '*help" - Show: numbered list of the following commands to allow selection'

expansion-packs/bmad-infrastructure-devops/data/bmad-kb.md

@@ -0,0 +1,3 @@
+# Usage Information
+
+TODO

expansion-packs/expansion-creator/README.md

@@ -5,4 +5,4 @@ Tools for creating and extending BMAD framework components.
 ## Tasks
 
 - **create-agent**: Create new AI agent definitions
-- **generate-expansion-pack**: Generate new expansion pack templates
+- **generate-expansion-pack**: Generate new expansion pack templates

expansion-packs/expansion-creator/agents/bmad-the-creator.md

@@ -50,4 +50,4 @@ dependencies:
   templates:
     - agent-tmpl
     - expansion-pack-plan-tmpl
-```
+```

expansion-packs/expansion-creator/tasks/create-agent.md

@@ -63,7 +63,7 @@ Created during agent setup:
 - Templates:
   - [ ] template-name-1.md
   - [ ] template-name-2.md
-```text
+```
 
 ### 4. Create Agent File
 
@@ -121,7 +121,7 @@ Present to the user:
    1. Review and customize the created tasks/templates
    2. Run npm run build:agents
    3. Test the agent thoroughly
-```text
+```
 
 ## Template Reference
 
@@ -150,7 +150,7 @@ persona:
     - Data integrity and accuracy above all
     - Clear communication of complex findings
     - Actionable insights over raw numbers
-```text
+```
 
 ## Creating Missing Dependencies
 
@@ -183,12 +183,12 @@ When a required task or template doesn't exist:
 ```yaml
 dependencies:
   tasks:
-    - 'create-doc # Required if agent creates any documents'
+    - create-doc
-    - 'analyze-requirements # Custom task for this agent'
+    - analyze-requirements
-    - 'generate-report # Another custom task'
+    - generate-report
   templates:
-    - 'requirements-doc # Template for requirements documents'
+    - requirements-doc
-    - 'analysis-report # Template for analysis reports'
+    - analysis-report
 ```
 
 ## Notes

expansion-packs/expansion-creator/tasks/generate-expansion-pack.md

@@ -673,7 +673,7 @@ Before declaring complete:
 
 **README Structure with Character Introduction:**
 
-````markdown
+```markdown
 # {Pack Name} Expansion Pack
 
 ## Meet Your {Domain} Team
@@ -698,9 +698,7 @@ _{Professional background and expertise}_
 
 2. **Launch Orchestrator**:
 
-   ```bash
    npm run agent {pack-name}-orchestrator
-   ```
 
 3. **Follow Numbered Options**: {Character Name} will present numbered choices for each decision
 
@@ -730,7 +728,7 @@ _{Professional background and expertise}_
 ### Knowledge Base
 
 [Embedded domain expertise]
-````
+```
 
 #### 6.3 Advanced Data File Documentation with Validation
 

expansion-packs/expansion-creator/templates/agent-teams-tmpl.md

@@ -83,7 +83,7 @@ workflows:
   - {{workflow-name}}  # {{workflow-description}}
   <</REPEAT>>
   ^^/CONDITION: domain-workflows^^
-```text
+```
 
 @{example-1: Standard fullstack team}
 
@@ -127,7 +127,7 @@ workflows:
   - healthcare-patient-portal
   - healthcare-compliance-audit
   - clinical-trial-management
-```text
+```
 
 @{example-3: Minimal IDE team}
 

expansion-packs/expansion-creator/templates/agent-tmpl.md

@@ -16,6 +16,7 @@ activation-instructions:
     - 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
+    - Command
 
 agent:
   name: [AGENT_NAME]
@@ -36,7 +37,9 @@ persona:
     # Add more principles as needed
 
 startup:
-  - [STARTUP_INSTRUCTIONS]
+  - Greet the user with your name and role, and inform of the *help command.
+  - [STARTUP_INSTRUCTION]
+  - [STARTUP_INSTRUCTION]...
 
 commands:
   - "*help" - Show: numbered list of the following commands to allow selection
@@ -67,7 +70,7 @@ dependencies:
     - [TEMPLATE_1]  # Template with LLM instructions for guided creation
     - [TEMPLATE_2]  # Another template for different document type
     [[LLM: Example: blueprint-tmpl, contract-tmpl, report-tmpl
-    Each template should include [[LLM: guidance]] and other conventions from `template-formmat.md` sections for user interaction]]
+    Each template should include [[LLM: guidance]] and other conventions from `template-format.md` sections for user interaction]]
 
   checklists:
     - [CHECKLIST_1]  # Quality validation for template outputs
@@ -83,7 +86,7 @@ dependencies:
     - template-format  # Required if using templates
     - [UTIL_1]        # Other utilities as needed
     [[LLM: Include workflow-management if agent participates in workflows]]
-```text
+```
 
 @{example: Construction Contractor Agent}
 
@@ -122,19 +125,19 @@ commands:
   - '*exit" - Say goodbye as Marcus and exit'
 dependencies:
   tasks:
-    - 'create-doc          # For document creation'
+    - create-doc
-    - 'validate-plans      # Custom validation task'
+    - validate-plans
-    - 'safety-assessment   # Custom safety review task'
+    - safety-assessment
   templates:
-    - 'blueprint-tmpl      # Architectural blueprint template'
+    - blueprint-tmpl
-    - 'estimate-tmpl       # Cost estimation template'
+    - estimate-tmpl
-    - 'schedule-tmpl       # Project timeline template'
+    - schedule-tmpl
   checklists:
-    - 'blueprint-checklist # Validates blueprint completeness'
+    - blueprint-checklist
-    - 'safety-checklist    # Safety compliance validation'
+    - safety-checklist
   data:
-    - 'building-codes.md   # Local building code reference'
+    - building-codes.md
-    - 'materials-guide.md  # Construction materials specs'
+    - materials-guide.md
   utils:
-    - 'template-format     # For template processing'
+    - template-format
 ```

expansion-packs/expansion-creator/utils/workflow-management.md

@@ -47,7 +47,7 @@ Available workflows for [Team Name]:
 [... etc. ...]
 
 Use /workflow-start {number or id} to begin a workflow.
-```text
+```
 
 ### /workflow-start {workflow-id}
 
@@ -73,7 +73,7 @@ In Progress:
     - Create PRD (John) - awaiting input
 
 Next: Technical Architecture
-```text
+```
 
 ### /workflow-resume
 
@@ -89,7 +89,7 @@ BMad: I see you've completed Discovery and part of Product Planning.
       - UX Strategy with Sally (ux-expert)
 
       Would you like me to load Sally to continue?
-```text
+```
 
 ### /workflow-next
 
@@ -135,7 +135,7 @@ workflow_state:
       status: in-progress
       created_by: pm
       started: 2024-01-15T11:00:00.000Z
-```text
+```
 
 ### 4. Workflow Interruption Handling
 
@@ -159,7 +159,7 @@ BMad: I see you have a PRD and architecture document. Based on these artifacts,
       - Load Sarah (Product Owner) to validate all artifacts
 
       Would you like to continue with this workflow?
-```text
+```
 
 ## Workflow Context Passing
 
@@ -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
 

package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "bmad-method",
-  "version": "4.6.0",
+  "version": "4.10.2",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "bmad-method",
-      "version": "4.6.0",
+      "version": "4.10.2",
       "license": "MIT",
       "dependencies": {
         "@kayvan/markdown-tree-parser": "^1.5.0",
@@ -443,9 +443,9 @@
       }
     },
     "node_modules/@kayvan/markdown-tree-parser": {
-      "version": "1.5.1",
+      "version": "1.6.0",
-      "resolved": "https://registry.npmjs.org/@kayvan/markdown-tree-parser/-/markdown-tree-parser-1.5.1.tgz",
+      "resolved": "https://registry.npmjs.org/@kayvan/markdown-tree-parser/-/markdown-tree-parser-1.6.0.tgz",
-      "integrity": "sha512-Npd6OIKwZ+0eOPxKOA/yd3BZ8k/tGgz24wJVMXUDODzhRm6LswXoWl0/rg4ZB3DOYsTO4yHwc6gIySCxd9B6Rw==",
+      "integrity": "sha512-d/6L71xHwjNGA+rt2rhGFKpxP/WTxO6egiGkNdoqIuGEgHYNUXJKDpnmDBMfESSHLXqgPargaPxmR74U8JxxXQ==",
       "license": "MIT",
       "dependencies": {
         "remark-parse": "^11.0.0",

package.json

@@ -1,6 +1,6 @@
 {
   "name": "bmad-method",
-  "version": "4.6.0",
+  "version": "4.10.2",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "main": "tools/cli.js",
   "bin": {

tools/builders/web-builder.js

@@ -1,15 +1,23 @@
-const fs = require('node:fs').promises;
+const fs = require("node:fs").promises;
-const path = require('node:path');
+const path = require("node:path");
-const DependencyResolver = require('../lib/dependency-resolver');
+const DependencyResolver = require("../lib/dependency-resolver");
 
 class WebBuilder {
   constructor(options = {}) {
     this.rootDir = options.rootDir || process.cwd();
-    this.outputDirs = options.outputDirs || [
+    this.outputDirs = options.outputDirs || [path.join(this.rootDir, "dist")];
-      path.join(this.rootDir, 'dist')
-    ];
     this.resolver = new DependencyResolver(this.rootDir);
-    this.templatePath = path.join(this.rootDir, 'bmad-core', 'templates', 'web-agent-startup-instructions-template.md');
+    this.templatePath = path.join(
+      this.rootDir,
+      "bmad-core",
+      "utils",
+      "web-agent-startup-instructions.md"
+    );
+  }
+
+  parseYaml(content) {
+    const yaml = require("js-yaml");
+    return yaml.load(content);
   }
 
   async cleanOutputDirs() {
@@ -33,10 +41,10 @@ class WebBuilder {
 
       // Write to all output directories
       for (const outputDir of this.outputDirs) {
-        const outputPath = path.join(outputDir, 'agents');
+        const outputPath = path.join(outputDir, "agents");
         await fs.mkdir(outputPath, { recursive: true });
         const outputFile = path.join(outputPath, `${agentId}.txt`);
-        await fs.writeFile(outputFile, bundle, 'utf8');
+        await fs.writeFile(outputFile, bundle, "utf8");
       }
     }
 
@@ -52,10 +60,10 @@ class WebBuilder {
 
       // Write to all output directories
       for (const outputDir of this.outputDirs) {
-        const outputPath = path.join(outputDir, 'teams');
+        const outputPath = path.join(outputDir, "teams");
         await fs.mkdir(outputPath, { recursive: true });
         const outputFile = path.join(outputPath, `${teamId}.txt`);
-        await fs.writeFile(outputFile, bundle, 'utf8');
+        await fs.writeFile(outputFile, bundle, "utf8");
       }
     }
 
@@ -64,7 +72,7 @@ class WebBuilder {
 
   async buildAgentBundle(agentId) {
     const dependencies = await this.resolver.resolveAgentDependencies(agentId);
-    const template = await fs.readFile(this.templatePath, 'utf8');
+    const template = await fs.readFile(this.templatePath, "utf8");
 
     const sections = [template];
 
@@ -76,12 +84,12 @@ class WebBuilder {
       sections.push(this.formatSection(resource.path, resource.content));
     }
 
-    return sections.join('\n');
+    return sections.join("\n");
   }
 
   async buildTeamBundle(teamId) {
     const dependencies = await this.resolver.resolveTeamDependencies(teamId);
-    const template = await fs.readFile(this.templatePath, 'utf8');
+    const template = await fs.readFile(this.templatePath, "utf8");
 
     const sections = [template];
 
@@ -98,21 +106,72 @@ class WebBuilder {
       sections.push(this.formatSection(resource.path, resource.content));
     }
 
-    return sections.join('\n');
+    return sections.join("\n");
+  }
+
+  processAgentContent(content) {
+    // First, replace content before YAML with the template
+    const yamlMatch = content.match(/```ya?ml\n([\s\S]*?)\n```/);
+    if (!yamlMatch) return content;
+
+    const yamlContent = yamlMatch[1];
+    const yamlStartIndex = content.indexOf(yamlMatch[0]);
+    const yamlEndIndex = yamlStartIndex + yamlMatch[0].length;
+    
+    // Parse YAML and remove root and IDE-FILE-RESOLUTION properties
+    try {
+      const yaml = require("js-yaml");
+      const parsed = yaml.load(yamlContent);
+      
+      // Remove the properties if they exist at root level
+      delete parsed.root;
+      delete parsed['IDE-FILE-RESOLUTION'];
+      delete parsed['REQUEST-RESOLUTION'];
+      
+      // Also remove from activation-instructions if they exist
+      if (parsed['activation-instructions'] && Array.isArray(parsed['activation-instructions'])) {
+        parsed['activation-instructions'] = parsed['activation-instructions'].filter(instruction => {
+          return !instruction.startsWith('IDE-FILE-RESOLUTION:') && 
+                 !instruction.startsWith('REQUEST-RESOLUTION:');
+        });
+      }
+      
+      // Reconstruct the YAML
+      const cleanedYaml = yaml.dump(parsed, { lineWidth: -1 });
+      
+      // Get the agent name from the YAML for the header
+      const agentName = parsed.agent?.id || 'agent';
+      
+      // Build the new content with just the agent header and YAML
+      const newHeader = `# ${agentName}\n\nCRITICAL: 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:\n\n`;
+      const afterYaml = content.substring(yamlEndIndex);
+      
+      return newHeader + "```yaml\n" + cleanedYaml.trim() + "\n```" + afterYaml;
+    } catch (error) {
+      console.warn("Failed to process agent YAML:", error.message);
+      // If parsing fails, return original content
+      return content;
+    }
   }
 
   formatSection(path, content) {
-    const separator = '====================';
+    const separator = "====================";
+    
+    // Process agent content if this is an agent file
+    if (path.startsWith("agents#")) {
+      content = this.processAgentContent(content);
+    }
+    
     return [
       `${separator} START: ${path} ${separator}`,
       content.trim(),
       `${separator} END: ${path} ${separator}`,
-      ''
+      "",
-    ].join('\n');
+    ].join("\n");
   }
 
   async validate() {
-    console.log('Validating agent configurations...');
+    console.log("Validating agent configurations...");
     const agents = await this.resolver.listAgents();
     for (const agentId of agents) {
       try {
@@ -124,7 +183,7 @@ class WebBuilder {
       }
     }
 
-    console.log('\nValidating team configurations...');
+    console.log("\nValidating team configurations...");
     const teams = await this.resolver.listTeams();
     for (const teamId of teams) {
       try {
@@ -149,10 +208,8 @@ class WebBuilder {
   }
 
   async buildExpansionPack(packName, options = {}) {
-    const packDir = path.join(this.rootDir, 'expansion-packs', packName);
+    const packDir = path.join(this.rootDir, "expansion-packs", packName);
-    const outputDirs = [
+    const outputDirs = [path.join(this.rootDir, "dist", "expansion-packs", packName)];
-      path.join(this.rootDir, 'dist', 'expansion-packs', packName)
-    ];
 
     // Clean output directories if requested
     if (options.clean !== false) {
@@ -166,27 +223,27 @@ class WebBuilder {
     }
 
     // Build individual agents first
-    const agentsDir = path.join(packDir, 'agents');
+    const agentsDir = path.join(packDir, "agents");
     try {
       const agentFiles = await fs.readdir(agentsDir);
-      const agentMarkdownFiles = agentFiles.filter(f => f.endsWith('.md'));
+      const agentMarkdownFiles = agentFiles.filter((f) => f.endsWith(".md"));
-      
+
       if (agentMarkdownFiles.length > 0) {
         console.log(`    Building individual agents for ${packName}:`);
-        
+
         for (const agentFile of agentMarkdownFiles) {
-          const agentName = agentFile.replace('.md', '');
+          const agentName = agentFile.replace(".md", "");
           console.log(`      - ${agentName}`);
-          
+
           // Build individual agent bundle
           const bundle = await this.buildExpansionAgentBundle(packName, packDir, agentName);
-          
+
           // Write to all output directories
           for (const outputDir of outputDirs) {
-            const agentsOutputDir = path.join(outputDir, 'agents');
+            const agentsOutputDir = path.join(outputDir, "agents");
             await fs.mkdir(agentsOutputDir, { recursive: true });
             const outputFile = path.join(agentsOutputDir, `${agentName}.txt`);
-            await fs.writeFile(outputFile, bundle, 'utf8');
+            await fs.writeFile(outputFile, bundle, "utf8");
           }
         }
       }
@@ -195,24 +252,24 @@ class WebBuilder {
     }
 
     // Build team bundle
-    const agentTeamsDir = path.join(packDir, 'agent-teams');
+    const agentTeamsDir = path.join(packDir, "agent-teams");
     try {
       const teamFiles = await fs.readdir(agentTeamsDir);
-      const teamFile = teamFiles.find(f => f.endsWith('.yml'));
+      const teamFile = teamFiles.find((f) => f.endsWith(".yml"));
-      
+
       if (teamFile) {
         console.log(`    Building team bundle for ${packName}`);
         const teamConfigPath = path.join(agentTeamsDir, teamFile);
-        
+
         // Build expansion pack as a team bundle
         const bundle = await this.buildExpansionTeamBundle(packName, packDir, teamConfigPath);
-        
+
         // Write to all output directories
         for (const outputDir of outputDirs) {
-          const teamsOutputDir = path.join(outputDir, 'teams');
+          const teamsOutputDir = path.join(outputDir, "teams");
           await fs.mkdir(teamsOutputDir, { recursive: true });
-          const outputFile = path.join(teamsOutputDir, teamFile.replace('.yml', '.txt'));
+          const outputFile = path.join(teamsOutputDir, teamFile.replace(".yml", ".txt"));
-          await fs.writeFile(outputFile, bundle, 'utf8');
+          await fs.writeFile(outputFile, bundle, "utf8");
           console.log(`    ✓ Created bundle: ${path.relative(this.rootDir, outputFile)}`);
         }
       } else {
@@ -224,32 +281,70 @@ class WebBuilder {
   }
 
   async buildExpansionAgentBundle(packName, packDir, agentName) {
-    const template = await fs.readFile(this.templatePath, 'utf8');
+    const template = await fs.readFile(this.templatePath, "utf8");
     const sections = [template];
 
     // Add agent configuration
-    const agentPath = path.join(packDir, 'agents', `${agentName}.md`);
+    const agentPath = path.join(packDir, "agents", `${agentName}.md`);
-    const agentContent = await fs.readFile(agentPath, 'utf8');
+    const agentContent = await fs.readFile(agentPath, "utf8");
     sections.push(this.formatSection(`agents#${agentName}`, agentContent));
 
-    // Resolve and add agent dependencies from expansion pack
+    // Resolve and add agent dependencies
     const agentYaml = agentContent.match(/```yaml\n([\s\S]*?)\n```/);
     if (agentYaml) {
       try {
-        const yaml = require('js-yaml');
+        const yaml = require("js-yaml");
         const agentConfig = yaml.load(agentYaml[1]);
-        
+
         if (agentConfig.dependencies) {
-          // Add resources from expansion pack
+          // Add resources, first try expansion pack, then core
           for (const [resourceType, resources] of Object.entries(agentConfig.dependencies)) {
             if (Array.isArray(resources)) {
               for (const resourceName of resources) {
-                const resourcePath = path.join(packDir, resourceType, `${resourceName}.md`);
+                let found = false;
-                try {
+                const extensions = [".md", ".yml", ".yaml"];
-                  const resourceContent = await fs.readFile(resourcePath, 'utf8');
+
-                  sections.push(this.formatSection(`${resourceType}#${resourceName}`, resourceContent));
+                // Try expansion pack first
-                } catch (error) {
+                for (const ext of extensions) {
-                  // Resource might not exist in expansion pack, that's ok
+                  const resourcePath = path.join(packDir, resourceType, `${resourceName}${ext}`);
+                  try {
+                    const resourceContent = await fs.readFile(resourcePath, "utf8");
+                    sections.push(
+                      this.formatSection(`${resourceType}#${resourceName}`, resourceContent)
+                    );
+                    found = true;
+                    break;
+                  } catch (error) {
+                    // Not in expansion pack, continue
+                  }
+                }
+
+                // If not found in expansion pack, try core
+                if (!found) {
+                  for (const ext of extensions) {
+                    const corePath = path.join(
+                      this.rootDir,
+                      "bmad-core",
+                      resourceType,
+                      `${resourceName}${ext}`
+                    );
+                    try {
+                      const coreContent = await fs.readFile(corePath, "utf8");
+                      sections.push(
+                        this.formatSection(`${resourceType}#${resourceName}`, coreContent)
+                      );
+                      found = true;
+                      break;
+                    } catch (error) {
+                      // Not in core either, continue
+                    }
+                  }
+                }
+
+                if (!found) {
+                  console.warn(
+                    `    ⚠ Dependency ${resourceType}#${resourceName} not found in expansion pack or core`
+                  );
                 }
               }
             }
@@ -260,67 +355,205 @@ class WebBuilder {
       }
     }
 
-    return sections.join('\n');
+    return sections.join("\n");
   }
 
   async buildExpansionTeamBundle(packName, packDir, teamConfigPath) {
-    const template = await fs.readFile(this.templatePath, 'utf8');
+    const template = await fs.readFile(this.templatePath, "utf8");
 
     const sections = [template];
 
-    // Add team configuration
+    // Add team configuration and parse to get agent list
-    const teamContent = await fs.readFile(teamConfigPath, 'utf8');
+    const teamContent = await fs.readFile(teamConfigPath, "utf8");
-    const teamFileName = path.basename(teamConfigPath, '.yml');
+    const teamFileName = path.basename(teamConfigPath, ".yml");
+    const teamConfig = this.parseYaml(teamContent);
     sections.push(this.formatSection(`agent-teams#${teamFileName}`, teamContent));
 
-    // Add bmad-orchestrator (required for all teams)
+    // Get list of expansion pack agents
-    const orchestratorPath = path.join(this.rootDir, 'bmad-core', 'agents', 'bmad-orchestrator.md');
+    const expansionAgents = new Set();
-    const orchestratorContent = await fs.readFile(orchestratorPath, 'utf8');
+    const agentsDir = path.join(packDir, "agents");
-    sections.push(this.formatSection('agents#bmad-orchestrator', orchestratorContent));
-
-    // Add expansion pack agents
-    const agentsDir = path.join(packDir, 'agents');
     try {
       const agentFiles = await fs.readdir(agentsDir);
-      for (const agentFile of agentFiles.filter(f => f.endsWith('.md'))) {
+      for (const agentFile of agentFiles.filter((f) => f.endsWith(".md"))) {
-        const agentPath = path.join(agentsDir, agentFile);
+        const agentName = agentFile.replace(".md", "");
-        const agentContent = await fs.readFile(agentPath, 'utf8');
+        expansionAgents.add(agentName);
-        const agentName = agentFile.replace('.md', '');
-        sections.push(this.formatSection(`agents#${agentName}`, agentContent));
       }
     } catch (error) {
       console.warn(`    ⚠ No agents directory found in ${packName}`);
     }
 
-    // Add expansion pack resources (templates, tasks, checklists)
+    // Build a map of all available expansion pack resources for override checking
-    const resourceDirs = ['templates', 'tasks', 'checklists', 'workflows', 'data'];
+    const expansionResources = new Map();
+    const resourceDirs = ["templates", "tasks", "checklists", "workflows", "data"];
     for (const resourceDir of resourceDirs) {
       const resourcePath = path.join(packDir, resourceDir);
       try {
         const resourceFiles = await fs.readdir(resourcePath);
-        for (const resourceFile of resourceFiles.filter(f => f.endsWith('.md') || f.endsWith('.yml'))) {
+        for (const resourceFile of resourceFiles.filter(
-          const filePath = path.join(resourcePath, resourceFile);
+          (f) => f.endsWith(".md") || f.endsWith(".yml")
-          const fileContent = await fs.readFile(filePath, 'utf8');
+        )) {
-          const fileName = resourceFile.replace(/\.(md|yml)$/, '');
+          const fileName = resourceFile.replace(/\.(md|yml)$/, "");
-          sections.push(this.formatSection(`${resourceDir}#${fileName}`, fileContent));
+          expansionResources.set(`${resourceDir}#${fileName}`, true);
         }
       } catch (error) {
         // Directory might not exist, that's fine
       }
     }
 
-    return sections.join('\n');
+    // Process all agents listed in team configuration
+    const agentsToProcess = teamConfig.agents || [];
+
+    // Ensure bmad-orchestrator is always included for teams
+    if (!agentsToProcess.includes("bmad-orchestrator")) {
+      console.warn(`    ⚠ Team ${teamFileName} missing bmad-orchestrator, adding automatically`);
+      agentsToProcess.unshift("bmad-orchestrator");
+    }
+
+    // Track all dependencies from all agents (deduplicated)
+    const allDependencies = new Map();
+
+    for (const agentId of agentsToProcess) {
+      if (expansionAgents.has(agentId)) {
+        // Use expansion pack version (override)
+        const agentPath = path.join(agentsDir, `${agentId}.md`);
+        const agentContent = await fs.readFile(agentPath, "utf8");
+        sections.push(this.formatSection(`agents#${agentId}`, agentContent));
+
+        // Parse and collect dependencies from expansion agent
+        const agentYaml = agentContent.match(/```yaml\n([\s\S]*?)\n```/);
+        if (agentYaml) {
+          try {
+            const agentConfig = this.parseYaml(agentYaml[1]);
+            if (agentConfig.dependencies) {
+              for (const [resourceType, resources] of Object.entries(agentConfig.dependencies)) {
+                if (Array.isArray(resources)) {
+                  for (const resourceName of resources) {
+                    const key = `${resourceType}#${resourceName}`;
+                    if (!allDependencies.has(key)) {
+                      allDependencies.set(key, { type: resourceType, name: resourceName });
+                    }
+                  }
+                }
+              }
+            }
+          } catch (error) {
+            console.debug(`Failed to parse agent YAML for ${agentId}:`, error.message);
+          }
+        }
+      } else {
+        // Use core BMAD version
+        try {
+          const coreAgentPath = path.join(this.rootDir, "bmad-core", "agents", `${agentId}.md`);
+          const coreAgentContent = await fs.readFile(coreAgentPath, "utf8");
+          sections.push(this.formatSection(`agents#${agentId}`, coreAgentContent));
+
+          // Parse and collect dependencies from core agent
+          const agentYaml = coreAgentContent.match(/```yaml\n([\s\S]*?)\n```/);
+          if (agentYaml) {
+            try {
+              // Clean up the YAML to handle command descriptions after dashes
+              let yamlContent = agentYaml[1];
+              yamlContent = yamlContent.replace(/^(\s*-)(\s*"[^"]+")(\s*-\s*.*)$/gm, "$1$2");
+
+              const agentConfig = this.parseYaml(yamlContent);
+              if (agentConfig.dependencies) {
+                for (const [resourceType, resources] of Object.entries(agentConfig.dependencies)) {
+                  if (Array.isArray(resources)) {
+                    for (const resourceName of resources) {
+                      const key = `${resourceType}#${resourceName}`;
+                      if (!allDependencies.has(key)) {
+                        allDependencies.set(key, { type: resourceType, name: resourceName });
+                      }
+                    }
+                  }
+                }
+              }
+            } catch (error) {
+              console.debug(`Failed to parse agent YAML for ${agentId}:`, error.message);
+            }
+          }
+        } catch (error) {
+          console.warn(`    ⚠ Agent ${agentId} not found in core or expansion pack`);
+        }
+      }
+    }
+
+    // Add all collected dependencies from agents
+    // Always prefer expansion pack versions if they exist
+    for (const [key, dep] of allDependencies) {
+      let found = false;
+      const extensions = [".md", ".yml", ".yaml"];
+
+      // Always check expansion pack first, even if the dependency came from a core agent
+      if (expansionResources.has(key)) {
+        // We know it exists in expansion pack, find and load it
+        for (const ext of extensions) {
+          const expansionPath = path.join(packDir, dep.type, `${dep.name}${ext}`);
+          try {
+            const content = await fs.readFile(expansionPath, "utf8");
+            sections.push(this.formatSection(key, content));
+            console.log(`      ✓ Using expansion override for ${key}`);
+            found = true;
+            break;
+          } catch (error) {
+            // Try next extension
+          }
+        }
+      }
+
+      // If not found in expansion pack (or doesn't exist there), try core
+      if (!found) {
+        for (const ext of extensions) {
+          const corePath = path.join(this.rootDir, "bmad-core", dep.type, `${dep.name}${ext}`);
+          try {
+            const content = await fs.readFile(corePath, "utf8");
+            sections.push(this.formatSection(key, content));
+            found = true;
+            break;
+          } catch (error) {
+            // Not in core either, continue
+          }
+        }
+      }
+
+      if (!found) {
+        console.warn(`    ⚠ Dependency ${key} not found in expansion pack or core`);
+      }
+    }
+
+    // Add remaining expansion pack resources not already included as dependencies
+    for (const resourceDir of resourceDirs) {
+      const resourcePath = path.join(packDir, resourceDir);
+      try {
+        const resourceFiles = await fs.readdir(resourcePath);
+        for (const resourceFile of resourceFiles.filter(
+          (f) => f.endsWith(".md") || f.endsWith(".yml")
+        )) {
+          const filePath = path.join(resourcePath, resourceFile);
+          const fileContent = await fs.readFile(filePath, "utf8");
+          const fileName = resourceFile.replace(/\.(md|yml)$/, "");
+
+          // Only add if not already included as a dependency
+          const resourceKey = `${resourceDir}#${fileName}`;
+          if (!allDependencies.has(resourceKey)) {
+            sections.push(this.formatSection(resourceKey, fileContent));
+          }
+        }
+      } catch (error) {
+        // Directory might not exist, that's fine
+      }
+    }
+
+    return sections.join("\n");
   }
 
   async listExpansionPacks() {
-    const expansionPacksDir = path.join(this.rootDir, 'expansion-packs');
+    const expansionPacksDir = path.join(this.rootDir, "expansion-packs");
     try {
       const entries = await fs.readdir(expansionPacksDir, { withFileTypes: true });
-      return entries
+      return entries.filter((entry) => entry.isDirectory()).map((entry) => entry.name);
-        .filter(entry => entry.isDirectory())
-        .map(entry => entry.name);
     } catch (error) {
-      console.warn('No expansion-packs directory found');
+      console.warn("No expansion-packs directory found");
       return [];
     }
   }
@@ -330,4 +563,4 @@ class WebBuilder {
   }
 }
 
-module.exports = WebBuilder;
+module.exports = WebBuilder;

tools/installer/README.md

@@ -33,7 +33,7 @@ installer/
 
 ## Usage
 
-````bash
+```bash
 # Interactive installation
 npx bmad-method install
 
@@ -42,7 +42,7 @@ npx bmad-method install --profile=minimal
 
 # Update existing installation
 npx bmad-method update
-```text
+```
 
 ## Development
 
@@ -55,4 +55,4 @@ npm test
 
 # Lint code
 npm run lint
-````
+```

tools/installer/bin/bmad.js

@@ -1,6 +1,7 @@
 #!/usr/bin/env node
 
 const { program } = require('commander');
+const path = require('path');
 
 // Dynamic imports for ES modules
 let chalk, inquirer;
@@ -57,7 +58,9 @@ program
       if (!options.full && !options.agent && !options.team && !options.expansionOnly) {
         // Interactive mode
         const answers = await promptInstallation();
-        await installer.install(answers);
+        if (!answers._alreadyInstalled) {
+          await installer.install(answers);
+        }
       } else {
         // Direct mode
         let installType = 'full';
@@ -158,6 +161,35 @@ async function promptInstallation() {
   ]);
   answers.directory = directory;
 
+  // Check if this is an existing v4 installation
+  const installDir = path.resolve(answers.directory);
+  const state = await installer.detectInstallationState(installDir);
+  
+  if (state.type === 'v4_existing') {
+    console.log(chalk.yellow('\n🔍 Found existing BMAD v4 installation'));
+    console.log(`   Directory: ${installDir}`);
+    console.log(`   Version: ${state.manifest?.version || 'Unknown'}`);
+    console.log(`   Installed: ${state.manifest?.installed_at ? new Date(state.manifest.installed_at).toLocaleDateString() : 'Unknown'}`);
+    
+    const { shouldUpdate } = await inquirer.prompt([
+      {
+        type: 'confirm',
+        name: 'shouldUpdate',
+        message: 'Would you like to update your existing BMAD v4 installation?',
+        default: true
+      }
+    ]);
+    
+    if (shouldUpdate) {
+      // Skip other prompts and go directly to update
+      answers.installType = 'update';
+      answers._alreadyInstalled = true; // Flag to prevent double installation
+      await installer.install(answers);
+      return answers; // Return the answers object
+    }
+    // If user doesn't want to update, continue with normal flow
+  }
+
   // Ask for installation type
   const { installType } = await inquirer.prompt([
     {
@@ -373,7 +405,7 @@ async function promptInstallation() {
         type: 'input',
         name: 'webBundlesDirectory',
         message: 'Enter directory for web bundles:',
-        default: `${directory}/web-bundles`,
+        default: `${answers.directory}/web-bundles`,
         validate: (input) => {
           if (!input.trim()) {
             return 'Please enter a valid directory path';

tools/installer/lib/file-manager.js

@@ -2,6 +2,7 @@ const fs = require("fs-extra");
 const path = require("path");
 const crypto = require("crypto");
 const glob = require("glob");
+const yaml = require("js-yaml");
 
 // Dynamic import for ES module
 let chalk;
@@ -106,7 +107,7 @@ class FileManager {
 
     // Write manifest
     await fs.ensureDir(path.dirname(manifestPath));
-    await fs.writeFile(manifestPath, JSON.stringify(manifest, null, 2));
+    await fs.writeFile(manifestPath, yaml.dump(manifest, { indent: 2 }));
 
     return manifest;
   }
@@ -120,7 +121,7 @@ class FileManager {
 
     try {
       const content = await fs.readFile(manifestPath, "utf8");
-      return JSON.parse(content);
+      return yaml.load(content);
     } catch (error) {
       return null;
     }

tools/installer/lib/ide-setup.js

@@ -39,20 +39,13 @@ class IdeSetup {
 
   async setupCursor(installDir, selectedAgent) {
     const cursorRulesDir = path.join(installDir, ".cursor", "rules");
-    const agents = selectedAgent
+    const agents = selectedAgent ? [selectedAgent] : await this.getAllAgentIds(installDir);
-      ? [selectedAgent]
-      : await this.getAllAgentIds(installDir);
 
     await fileManager.ensureDirectory(cursorRulesDir);
 
     for (const agentId of agents) {
       // Check if .bmad-core is a subdirectory (full install) or if agents are in root (single agent install)
-      let agentPath = path.join(
+      let agentPath = path.join(installDir, ".bmad-core", "agents", `${agentId}.md`);
-        installDir,
-        ".bmad-core",
-        "agents",
-        `${agentId}.md`
-      );
       if (!(await fileManager.pathExists(agentPath))) {
         agentPath = path.join(installDir, "agents", `${agentId}.md`);
       }
@@ -103,20 +96,13 @@ class IdeSetup {
 
   async setupClaudeCode(installDir, selectedAgent) {
     const commandsDir = path.join(installDir, ".claude", "commands");
-    const agents = selectedAgent
+    const agents = selectedAgent ? [selectedAgent] : await this.getAllAgentIds(installDir);
-      ? [selectedAgent]
-      : await this.getAllAgentIds(installDir);
 
     await fileManager.ensureDirectory(commandsDir);
 
     for (const agentId of agents) {
       // Check if .bmad-core is a subdirectory (full install) or if agents are in root (single agent install)
-      let agentPath = path.join(
+      let agentPath = path.join(installDir, ".bmad-core", "agents", `${agentId}.md`);
-        installDir,
-        ".bmad-core",
-        "agents",
-        `${agentId}.md`
-      );
       if (!(await fileManager.pathExists(agentPath))) {
         agentPath = path.join(installDir, "agents", `${agentId}.md`);
       }
@@ -136,29 +122,20 @@ class IdeSetup {
       }
     }
 
-    console.log(
+    console.log(chalk.green(`\n✓ Created Claude Code commands in ${commandsDir}`));
-      chalk.green(`\n✓ Created Claude Code commands in ${commandsDir}`)
-    );
 
     return true;
   }
 
   async setupWindsurf(installDir, selectedAgent) {
     const windsurfRulesDir = path.join(installDir, ".windsurf", "rules");
-    const agents = selectedAgent
+    const agents = selectedAgent ? [selectedAgent] : await this.getAllAgentIds(installDir);
-      ? [selectedAgent]
-      : await this.getAllAgentIds(installDir);
 
     await fileManager.ensureDirectory(windsurfRulesDir);
 
     for (const agentId of agents) {
       // Check if .bmad-core is a subdirectory (full install) or if agents are in root (single agent install)
-      let agentPath = path.join(
+      let agentPath = path.join(installDir, ".bmad-core", "agents", `${agentId}.md`);
-        installDir,
-        ".bmad-core",
-        "agents",
-        `${agentId}.md`
-      );
       if (!(await fileManager.pathExists(agentPath))) {
         agentPath = path.join(installDir, "agents", `${agentId}.md`);
       }
@@ -197,9 +174,7 @@ class IdeSetup {
       }
     }
 
-    console.log(
+    console.log(chalk.green(`\n✓ Created Windsurf rules in ${windsurfRulesDir}`));
-      chalk.green(`\n✓ Created Windsurf rules in ${windsurfRulesDir}`)
-    );
 
     return true;
   }
@@ -233,13 +208,7 @@ class IdeSetup {
   }
 
   async setupRoo(installDir, selectedAgent) {
-    const agents = selectedAgent
+    const agents = selectedAgent ? [selectedAgent] : await this.getAllAgentIds(installDir);
-      ? [selectedAgent]
-      : await this.getAllAgentIds(installDir);
-
-    // Create .roo directory first
-    const rooDir = path.join(installDir, ".roo");
-    await fileManager.ensureDirectory(rooDir);
 
     // Check for existing .roomodes file in project root
     const roomodesPath = path.join(installDir, ".roomodes");
@@ -253,11 +222,7 @@ class IdeSetup {
       for (const match of modeMatches) {
         existingModes.push(match[1]);
       }
-      console.log(
+      console.log(chalk.yellow(`Found existing .roomodes file with ${existingModes.length} modes`));
-        chalk.yellow(
-          `Found existing .roomodes file with ${existingModes.length} modes`
-        )
-      );
     }
 
     // Create new modes content
@@ -265,55 +230,48 @@ class IdeSetup {
 
     // Define file permissions for each agent type
     const agentPermissions = {
-      'analyst': {
+      analyst: {
-        fileRegex: '\\.(md|txt)$',
+        fileRegex: "\\.(md|txt)$",
-        description: 'Documentation and text files'
+        description: "Documentation and text files",
       },
-      'pm': {
+      pm: {
-        fileRegex: '\\.(md|txt)$',
+        fileRegex: "\\.(md|txt)$",
-        description: 'Product documentation'
+        description: "Product documentation",
       },
-      'architect': {
+      architect: {
-        fileRegex: '\\.(md|txt|yml|yaml|json)$',
+        fileRegex: "\\.(md|txt|yml|yaml|json)$",
-        description: 'Architecture docs and configs'
+        description: "Architecture docs and configs",
       },
-      'dev': null, // Full edit access
+      dev: null, // Full edit access
-      'qa': {
+      qa: {
-        fileRegex: '\\.(test|spec)\\.(js|ts|jsx|tsx)$|\\.md$',
+        fileRegex: "\\.(test|spec)\\.(js|ts|jsx|tsx)$|\\.md$",
-        description: 'Test files and documentation'
+        description: "Test files and documentation",
       },
-      'ux-expert': {
+      "ux-expert": {
-        fileRegex: '\\.(md|css|scss|html|jsx|tsx)$',
+        fileRegex: "\\.(md|css|scss|html|jsx|tsx)$",
-        description: 'Design-related files'
+        description: "Design-related files",
       },
-      'po': {
+      po: {
-        fileRegex: '\\.(md|txt)$',
+        fileRegex: "\\.(md|txt)$",
-        description: 'Story and requirement docs'
+        description: "Story and requirement docs",
       },
-      'sm': {
+      sm: {
-        fileRegex: '\\.(md|txt)$',
+        fileRegex: "\\.(md|txt)$",
-        description: 'Process and planning docs'
+        description: "Process and planning docs",
       },
-      'bmad-orchestrator': null, // Full edit access
+      "bmad-orchestrator": null, // Full edit access
-      'bmad-master': null // Full edit access
+      "bmad-master": null, // Full edit access
     };
 
     for (const agentId of agents) {
       // Skip if already exists
       if (existingModes.includes(`bmad-${agentId}`)) {
-        console.log(
+        console.log(chalk.dim(`Skipping ${agentId} - already exists in .roomodes`));
-          chalk.dim(`Skipping ${agentId} - already exists in .roomodes`)
-        );
         continue;
       }
 
       // Read agent file to extract all information
-      let agentPath = path.join(
+      let agentPath = path.join(installDir, ".bmad-core", "agents", `${agentId}.md`);
-        installDir,
-        ".bmad-core",
-        "agents",
-        `${agentId}.md`
-      );
       if (!(await fileManager.pathExists(agentPath))) {
         agentPath = path.join(installDir, "agents", `${agentId}.md`);
       }
@@ -334,9 +292,7 @@ class IdeSetup {
 
           const title = titleMatch ? titleMatch[1].trim() : this.getAgentTitle(agentId);
           const icon = iconMatch ? iconMatch[1].trim() : "🤖";
-          const whenToUse = whenToUseMatch
+          const whenToUse = whenToUseMatch ? whenToUseMatch[1].trim() : `Use for ${title} tasks`;
-            ? whenToUseMatch[1].trim()
-            : `Use for ${title} tasks`;
           const roleDefinition = roleDefinitionMatch
             ? roleDefinitionMatch[1].trim()
             : `You are a ${title} specializing in ${title.toLowerCase()} tasks and responsibilities.`;
@@ -360,9 +316,7 @@ class IdeSetup {
             newModesContent += `    - edit\n`;
           }
 
-          console.log(
+          console.log(chalk.green(`✓ Added mode: bmad-${agentId} (${icon} ${title})`));
-            chalk.green(`✓ Added mode: bmad-${agentId} (${icon} ${title})`)
-          );
         }
       }
     }
@@ -381,46 +335,8 @@ class IdeSetup {
     await fileManager.writeFile(roomodesPath, roomodesContent);
     console.log(chalk.green("✓ Created .roomodes file in project root"));
 
-    // Create README in .roo directory
-    const rooReadme = `# Roo Code Custom Modes for BMAD-METHOD
-
-This directory contains custom mode configurations for Roo Code to enable BMAD agent personalities.
-
-## Setup
-
-The \`.roomodes\` file defines all BMAD agents as custom modes using the proper \`customModes:\` structure. Modes are automatically available in Roo Code when you open this project.
-
-## Available Modes
-
-${agents.map((id) => `- **bmad-${id}** - ${this.getAgentTitle(id)}`).join("\n")}
-
-## Usage
-
-In Roo Code:
-1. Open the mode selector (usually in the status bar)
-2. Select any BMAD agent mode
-3. The AI will adopt that agent's personality and expertise
-
-## File Permissions
-
-Each agent has specific file access permissions:
-- **Analysts, PM, PO, SM**: Limited to documentation files (.md, .txt)
-- **Architect**: Architecture docs and configs (.md, .txt, .yml, .yaml, .json)
-- **QA**: Test files and documentation
-- **UX Expert**: Design-related files (.md, .css, .scss, .html, .jsx, .tsx)
-- **Developer, Orchestrator, Master**: Full edit access to all files
-`;
-
-    const readmePath = path.join(rooDir, "README.md");
-    await fileManager.writeFile(readmePath, rooReadme);
-    console.log(chalk.green("✓ Created .roo/README.md"));
-
     console.log(chalk.green(`\n✓ Roo Code setup complete!`));
-    console.log(
+    console.log(chalk.dim("Custom modes will be available when you open this project in Roo Code"));
-      chalk.dim(
-        "Custom modes will be available when you open this project in Roo Code"
-      )
-    );
 
     return true;
   }

tools/installer/lib/installer.js

@@ -102,6 +102,17 @@ class Installer {
         spinner.start("Analyzing installation directory...");
       }
 
+      // If this is an update request from early detection, handle it directly
+      if (config.installType === 'update') {
+        const state = await this.detectInstallationState(installDir);
+        if (state.type === 'v4_existing') {
+          return await this.performUpdate(config, installDir, state.manifest, spinner);
+        } else {
+          spinner.fail('No existing v4 installation found to update');
+          throw new Error('No existing v4 installation found');
+        }
+      }
+
       // Detect current state
       const state = await this.detectInstallationState(installDir);
 
@@ -425,7 +436,10 @@ class Installer {
         console.log(chalk.cyan("\n📦 Starting v3 to v4 upgrade process..."));
         const V3ToV4Upgrader = require("../../upgraders/v3-to-v4-upgrader");
         const upgrader = new V3ToV4Upgrader();
-        return await upgrader.upgrade({ projectPath: installDir });
+        return await upgrader.upgrade({ 
+          projectPath: installDir,
+          ides: config.ides || [] // Pass IDE selections from initial config
+        });
       }
       case "alongside":
         return await this.performFreshInstall(config, installDir, spinner);
@@ -538,7 +552,8 @@ class Installer {
         installType: manifest.install_type,
         agent: manifest.agent,
         directory: installDir,
-        ide: newConfig.ide || manifest.ide_setup, // Use new IDE choice if provided
+        ide: newConfig?.ide || manifest.ide_setup, // Use new IDE choice if provided
+        ides: newConfig?.ides || manifest.ides_setup || [],
       };
 
       await this.performFreshInstall(config, installDir, spinner);

tools/installer/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bmad-method",
-  "version": "4.6.0",
+  "version": "4.10.2",
   "description": "BMAD Method installer - AI-powered Agile development framework",
   "main": "lib/installer.js",
   "bin": {

tools/upgraders/v3-to-v4-upgrader.js

@@ -98,7 +98,7 @@ class V3ToV4Upgrader {
 
       // 8. Setup IDE
       if (!options.dryRun) {
-        await this.setupIDE(projectPath);
+        await this.setupIDE(projectPath, options.ides);
       }
 
       // 9. Show completion report
@@ -379,8 +379,8 @@ class V3ToV4Upgrader {
     const spinner = ora("Installing V4 structure...").start();
 
     try {
-      // Get the source .bmad-core directory
+      // Get the source bmad-core directory (without dot prefix)
-      const sourcePath = path.join(__dirname, "..", "..", ".bmad-core");
+      const sourcePath = path.join(__dirname, "..", "..", "bmad-core");
       const destPath = path.join(projectPath, ".bmad-core");
 
       // Copy .bmad-core
@@ -545,47 +545,37 @@ class V3ToV4Upgrader {
     }
   }
 
-  async setupIDE(projectPath) {
+  async setupIDE(projectPath, selectedIdes) {
-    const { ide } = await inquirer.prompt([
+    // Use the IDE selections passed from the installer
-      {
+    if (!selectedIdes || selectedIdes.length === 0) {
-        type: "list",
+      console.log(chalk.dim("No IDE setup requested - skipping"));
-        name: "ide",
+      return;
-        message: "Which IDE are you using?",
+    }
-        choices: [
-          { name: "Cursor", value: "cursor" },
-          { name: "Claude Code", value: "claude-code" },
-          { name: "Windsurf", value: "windsurf" },
-          { name: "Roo Code", value: "roo" },
-          { name: "VS Code", value: "skip" },
-          { name: "Other/Skip", value: "skip" },
-        ],
-      },
-    ]);
 
-    const selectedIde = ide === "skip" ? null : ide;
+    const ideSetup = require("../installer/lib/ide-setup");
+    const spinner = ora("Setting up IDE rules for all agents...").start();
 
-    if (selectedIde) {
+    try {
-      const ideSetup = require("../installer/lib/ide-setup");
+      const ideMessages = {
-      const spinner = ora("Setting up IDE rules for all agents...").start();
+        cursor: "Rules created in .cursor/rules/",
+        "claude-code": "Commands created in .claude/commands/",
+        windsurf: "Rules created in .windsurf/rules/",
+        roo: "Custom modes created in .roomodes",
+      };
 
-      try {
+      // Setup each selected IDE
-        await ideSetup.setup(selectedIde, projectPath);
+      for (const ide of selectedIdes) {
-        spinner.succeed("IDE setup complete!");
+        spinner.text = `Setting up ${ide}...`;
-
+        await ideSetup.setup(ide, projectPath);
-        const ideMessages = {
+        console.log(chalk.green(`\n✓ ${ideMessages[ide]}`));
-          cursor: "Rules created in .cursor/rules/",
-          "claude-code": "Commands created in .claude/commands/",
-          windsurf: "Rules created in .windsurf/rules/",
-          roo: "Custom modes created in .roomodes",
-        };
-
-        console.log(chalk.green(`- ${ideMessages[selectedIde]}`));
-      } catch (error) {
-        spinner.fail("IDE setup failed");
-        console.error(
-          chalk.yellow("IDE setup failed, but upgrade is complete.")
-        );
       }
+
+      spinner.succeed(`IDE setup complete for ${selectedIdes.length} IDE(s)!`);
+    } catch (error) {
+      spinner.fail("IDE setup failed");
+      console.error(
+        chalk.yellow("IDE setup failed, but upgrade is complete.")
+      );
     }
   }