bmad-method 4.7.0 → 4.8.0

package/.prettierignore

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

package/CHANGELOG.md

@@ -1,3 +1,20 @@
+# [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)
 
 

package/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) 🏃‍♂️
@@ -191,7 +208,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

package/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:
-  - '*help" - Show: numbered list of the following commands to allow selection'
-  - '*chat-mode" - (Default) Strategic analysis consultation with advanced-elicitation'
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
-  - '*brainstorm {topic}" - Facilitate structured brainstorming session'
-  - '*research {topic}" - Generate deep research prompt for investigation'
-  - '*elicit" - Run advanced elicitation to clarify requirements'
-  - '*exit" - Say goodbye as the Business Analyst, and then abandon inhabiting this persona'
+commands:  # All commands require * prefix when used (e.g., *help)
+  - help: Show numbered list of the following commands to allow selection
+  - chat-mode: (Default) Strategic analysis consultation with advanced-elicitation
+  - create-doc {template}: Create doc (no template = show available templates)
+  - brainstorm {topic}: Facilitate structured brainstorming session
+  - research {topic}: Generate deep research prompt for investigation
+  - elicit: Run advanced elicitation to clarify requirements
+  - exit: Say goodbye as the Business Analyst, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - brainstorming-techniques

package/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:
-  - '*help" - Show: numbered list of the following commands to allow selection'
-  - '*chat-mode" - (Default) Architect consultation with advanced-elicitation for complex system design'
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
-  - '*execute-checklist {checklist}" - Run architectural validation checklist'
-  - '*research {topic}" - Generate deep research prompt for architectural decisions'
-  - '*exit" - Say goodbye as the Architect, and then abandon inhabiting this persona'
+commands:  # All commands require * prefix when used (e.g., *help)
+  - help: Show numbered list of the following commands to allow selection
+  - chat-mode: (Default) Architect consultation with advanced-elicitation for complex system design
+  - create-doc {template}: Create doc (no template = show available templates)
+  - execute-checklist {checklist}: Run architectural validation checklist
+  - research {topic}: Generate deep research prompt for architectural decisions
+  - exit: Say goodbye as the Architect, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - create-doc

package/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:
-  - '*help" - Show commands'
-  - '*chat" - Advanced elicitation + KB mode'
-  - '*status" - Current context'
-  - '*task/template/util/checklist/workflow {name}" - Execute (list if no name)'
-  - '*list {type}" - List resources by type'
-  - '*exit" - Exit (confirm)'
-  - '*yolo" - Skip confirmations'
-  - '*doc-out" - Output full document'
+commands:  # All commands require * prefix when used (e.g., *help)
+  - help: Show commands
+  - chat: Advanced elicitation + KB mode
+  - status: Current context
+  - task {template|util|checklist|workflow}: Execute
+  - list {task|template|util|checklist|workflow}: List resources by type
+  - exit: Exit (confirm)
+  - yolo: Toggle Yolo Mode off on - on will skip doc section confirmations
+  - 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

package/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

package/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
@@ -19,33 +22,35 @@ 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: Config-Based Loading - MUST load .bmad-core/core-config.yml at startup, then load ONLY files listed in devLoadAlwaysFiles. Inform user of missing files but continue
   - CRITICAL: Dev Record Only - ONLY update Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
   - 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
   - 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: Load .bmad-core/core-config.yml and read devLoadAlwaysFiles list
+  - 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 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
+  - Only load story 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
+commands:  # All commands require * prefix when used (e.g., *help)
+  - help: Show numbered list of the following commands to allow selection
+  - chat-mode: Conversational mode for development discussions
+  - run-tests: Execute linting and 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: Say goodbye as the Developer, and then abandon inhabiting this persona
 
 task-execution:
   flow: "Read task→Implement→Write tests→Pass tests→Update [x]→Next task"

package/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:
-  - '*help" - Show: numbered list of the following commands to allow selection'
-  - '*chat-mode" - (Default) Deep conversation with advanced-elicitation'
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
-  - '*exit" - Say goodbye as the PM, and then abandon inhabiting this persona'
+commands:  # All commands require * prefix when used (e.g., *help)
+  - help: Show numbered list of the following commands to allow selection
+  - chat-mode: (Default) Deep conversation with advanced-elicitation
+  - create-doc {template}: Create doc (no template = show available templates)
+  - exit: Say goodbye as the PM, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - create-doc

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

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

package/bmad-core/agents/sm.md

@@ -2,16 +2,12 @@
 
 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:
 
-## Task and File Resolution
-
-`Create Next Story`: `.bmad-core/tasks/create-next-story.md`
-`story-tmpl`: `.bmad-core/templates/story-tmpl.md`
-`story-draft-checklist`: `.bmad-core/checklists/story-draft-checklist.md`
-
 ```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:
@@ -27,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
-    - Checklist-Driven Validation - Apply story-draft-checklist meticulously
-    - Clarity for Developer Handoff - Stories must be immediately actionable
-    - Focus on One Story at a Time - Complete one before starting next
-    - Numbered Options Protocol - Always use numbered lists for selections
+    - Rigorously follow `create-next-story` procedure to generate the detailed user story
+    - Will ensure all information comes from the PRD and Architecture to guide the dumb dev agent
+    - You are NOT allowed to implement stories or modify code EVER!
 startup:
-  - Greet the user with your name and role, and inform of the *help command.
-  - CRITICAL: Do NOT automatically execute `Create Next Story` tasks during startup
-  - CRITICAL: Do NOT create or modify any files during startup
+  - Greet the user with your name and role, and inform of the *help command and then HALT to await instruction if not given already.
   - 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'
-  - '*chat-mode" - Conversational mode with advanced-elicitation for advice'
-  - '*create" - Execute all steps in `Create Next Story`'
-  - '*pivot" - Run correct-course task (ensure no story already created first)'
-  - '*checklist {checklist}" - Show numbered list of checklists, execute selection'
-  - '*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'
+commands:  # All commands require * prefix when used (e.g., *help)
+  - help: Show numbered list of the following commands to allow selection
+  - chat-mode: Conversational mode with advanced-elicitation for advice
+  - create|draft: Execute create-next-story
+  - pivot: Execute `correct-course` task
+  - checklist {checklist}: Show numbered list of checklists, execute selection
+  - 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:

package/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:
-  - '*help" - Show: numbered list of the following commands to allow selection'
-  - '*chat-mode" - (Default) UX consultation with advanced-elicitation for design decisions'
-  - '*create-doc {template}" - Create doc (no template = show available templates)'
-  - '*generate-ui-prompt" - Create AI frontend generation prompt'
-  - '*research {topic}" - Generate deep research prompt for UX investigation'
-  - '*execute-checklist {checklist}" - Run design validation checklist'
-  - '*exit" - Say goodbye as the UX Expert, and then abandon inhabiting this persona'
+commands:  # All commands require * prefix when used (e.g., *help)
+  - help: Show numbered list of the following commands to allow selection
+  - chat-mode: (Default) UX consultation with advanced-elicitation for design decisions
+  - create-doc {template}: Create doc (no template = show available templates)
+  - generate-ui-prompt: Create AI frontend generation prompt
+  - research {topic}: Generate deep research prompt for UX investigation
+  - execute-checklist {checklist}: Run design validation checklist
+  - exit: Say goodbye as the UX Expert, and then abandon inhabiting this persona
 dependencies:
   tasks:
     - generate-ai-frontend-prompt

package/bmad-core/core-config.yml

@@ -0,0 +1,24 @@
+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

package/bmad-core/data/bmad-kb.md

@@ -27,7 +27,7 @@ BMAD-METHOD (Breakthrough Method of Agile AI-driven Development) is a framework
 #### Option 1: Web UI
 **Best for**: ChatGPT, Claude, Gemini users who want to start immediately
 
-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"
@@ -200,14 +200,16 @@ The BMAD-Method is built around a modular architecture centered on the `bmad-cor
 ### 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 `bmad-core/web-bundles/`
-- Single text files containing all agent dependencies
+
+- 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
 
@@ -220,6 +222,7 @@ BMAD employs a sophisticated template system with three key components:
 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