refactor: update file paths to remove leading dot from bmad-core references

.github/FORK_GUIDE.md

@@ -1,106 +0,0 @@
-# Fork Guide - CI/CD Configuration
-
-## CI/CD in Forks
-
-By default, CI/CD workflows are **disabled in forks** to conserve GitHub Actions resources and provide a cleaner fork experience.
-
-### Why This Approach?
-
-- **Resource efficiency**: Prevents unnecessary GitHub Actions usage across 1,600+ forks
-- **Clean fork experience**: No failed workflow notifications in your fork
-- **Full control**: Enable CI/CD only when you actually need it
-- **PR validation**: Your changes are still fully tested when submitting PRs to the main repository
-
-## Enabling CI/CD in Your Fork
-
-If you need to run CI/CD workflows in your fork, follow these steps:
-
-1. Navigate to your fork's **Settings** tab
-2. Go to **Secrets and variables** → **Actions** → **Variables**
-3. Click **New repository variable**
-4. Create a new variable:
-   - **Name**: `ENABLE_CI_IN_FORK`
-   - **Value**: `true`
-5. Click **Add variable**
-
-That's it! CI/CD workflows will now run in your fork.
-
-## Disabling CI/CD Again
-
-To disable CI/CD workflows in your fork, you can either:
-
-- **Delete the variable**: Remove the `ENABLE_CI_IN_FORK` variable entirely, or
-- **Set to false**: Change the `ENABLE_CI_IN_FORK` value to `false`
-
-## Alternative Testing Options
-
-You don't always need to enable CI/CD in your fork. Here are alternatives:
-
-### Local Testing
-
-Run tests locally before pushing:
-
-```bash
-# Install dependencies
-npm ci
-
-# Run linting
-npm run lint
-
-# Run format check
-npm run format:check
-
-# Run validation
-npm run validate
-
-# Build the project
-npm run build
-```
-
-### Pull Request CI
-
-When you open a Pull Request to the main repository:
-
-- All CI/CD workflows automatically run
-- You get full validation of your changes
-- No configuration needed
-
-### GitHub Codespaces
-
-Use GitHub Codespaces for a full development environment:
-
-- All tools pre-configured
-- Same environment as CI/CD
-- No local setup required
-
-## Frequently Asked Questions
-
-### Q: Will my PR be tested even if CI is disabled in my fork?
-
-**A:** Yes! When you open a PR to the main repository, all CI/CD workflows run automatically, regardless of your fork's settings.
-
-### Q: Can I selectively enable specific workflows?
-
-**A:** The `ENABLE_CI_IN_FORK` variable enables all workflows. For selective control, you'd need to modify individual workflow files.
-
-### Q: Do I need to enable CI in my fork to contribute?
-
-**A:** No! Most contributors never need to enable CI in their forks. Local testing and PR validation are sufficient for most contributions.
-
-### Q: Will disabling CI affect my ability to merge PRs?
-
-**A:** No! PR merge requirements are based on CI runs in the main repository, not your fork.
-
-### Q: Why was this implemented?
-
-**A:** With over 1,600 forks of BMAD-METHOD, this saves thousands of GitHub Actions minutes monthly while maintaining code quality standards.
-
-## Need Help?
-
-- Join our [Discord Community](https://discord.gg/gk8jAdXWmj) for support
-- Check the [Contributing Guide](../README.md#contributing) for more information
-- Open an issue if you encounter any problems
-
----
-
-> 💡 **Pro Tip**: This fork-friendly approach is particularly valuable for projects using AI/LLM tools that create many experimental commits, as it prevents unnecessary CI runs while maintaining code quality standards.

.github/workflows/discord.yaml

@@ -14,7 +14,6 @@ name: Discord Notification
 jobs:
   notify:
     runs-on: ubuntu-latest
-    if: github.event.repository.fork != true || vars.ENABLE_CI_IN_FORK == 'true'
     steps:
       - name: Notify Discord
         uses: sarisia/actions-status-discord@v1

.github/workflows/format-check.yaml

@@ -7,7 +7,6 @@ name: format-check
 jobs:
   prettier:
     runs-on: ubuntu-latest
-    if: github.event.repository.fork != true || vars.ENABLE_CI_IN_FORK == 'true'
     steps:
       - name: Checkout
         uses: actions/checkout@v4
@@ -26,7 +25,6 @@ jobs:
 
   eslint:
     runs-on: ubuntu-latest
-    if: github.event.repository.fork != true || vars.ENABLE_CI_IN_FORK == 'true'
     steps:
       - name: Checkout
         uses: actions/checkout@v4

.github/workflows/manual-release.yaml

@@ -20,7 +20,6 @@ permissions:
 jobs:
   release:
     runs-on: ubuntu-latest
-    if: github.event.repository.fork != true || vars.ENABLE_CI_IN_FORK == 'true'
     steps:
       - name: Checkout
         uses: actions/checkout@v4

.github/workflows/pr-validation.yaml

@@ -1,55 +0,0 @@
-name: PR Validation
-
-on:
-  pull_request:
-    branches: [main]
-    types: [opened, synchronize, reopened]
-
-jobs:
-  validate:
-    runs-on: ubuntu-latest
-    if: github.event.repository.fork != true || vars.ENABLE_CI_IN_FORK == 'true'
-
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: "20"
-          cache: npm
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Run validation
-        run: npm run validate
-
-      - name: Check formatting
-        run: npm run format:check
-
-      - name: Run linter
-        run: npm run lint
-
-      - name: Run tests (if available)
-        run: npm test --if-present
-
-      - name: Comment on PR if checks fail
-        if: failure()
-        uses: actions/github-script@v7
-        with:
-          script: |
-            github.rest.issues.createComment({
-              issue_number: context.issue.number,
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              body: `❌ **PR Validation Failed**
-              
-              This PR has validation errors that must be fixed before merging:
-              - Run \`npm run validate\` to check agent/team configs
-              - Run \`npm run format:check\` to check formatting (fix with \`npm run format\`)
-              - Run \`npm run lint\` to check linting issues (fix with \`npm run lint:fix\`)
-              
-              Please fix these issues and push the changes.`
-            })

.gitignore

@@ -38,7 +38,7 @@ CLAUDE.md
 .gemini
 
 # Project-specific
-.bmad-core
+bmad-core
 .bmad-creator-tools
 test-project-install/*
 sample-project/*

CHANGELOG.md

@@ -555,7 +555,7 @@
 - add docs ([48ef875](https://github.com/bmadcode/BMAD-METHOD/commit/48ef875f5ec5b0f0211baa43bbc04701e54824f4))
 - auto semantic versioning fix ([166ed04](https://github.com/bmadcode/BMAD-METHOD/commit/166ed047671cccab2874fd327efb1ac293ae7276))
 - auto semantic versioning fix again ([11260e4](https://github.com/bmadcode/BMAD-METHOD/commit/11260e43950b6bf78d68c759dc3ac278bc13f8a8))
-- BMAD install creates `.bmad-core/.bmad-core/` directory structure + updates ([#223](https://github.com/bmadcode/BMAD-METHOD/issues/223)) ([28b313c](https://github.com/bmadcode/BMAD-METHOD/commit/28b313c01df41961cebb71fb3bce0fcc7b4b4796))
+- BMAD install creates `bmad-core/bmad-core/` directory structure + updates ([#223](https://github.com/bmadcode/BMAD-METHOD/issues/223)) ([28b313c](https://github.com/bmadcode/BMAD-METHOD/commit/28b313c01df41961cebb71fb3bce0fcc7b4b4796))
 - resolve NPM token configuration ([620b09a](https://github.com/bmadcode/BMAD-METHOD/commit/620b09a556ce8d61ad1a4d8ee7c523d263abd69c))
 - resolve NPM token configuration ([b447a8b](https://github.com/bmadcode/BMAD-METHOD/commit/b447a8bd57625d02692d7e2771241bacd120c631))
 - update dependency resolver to support both yml and yaml code blocks ([ba1e5ce](https://github.com/bmadcode/BMAD-METHOD/commit/ba1e5ceb36f4a0bb204ceee40e92725d3fc57c5f))

CONTRIBUTING.md

@@ -17,47 +17,6 @@ Also note, we use the discussions feature in GitHub to have a community to discu
 
 By participating in this project, you agree to abide by our Code of Conduct. Please read it before participating.
 
-## Before Submitting a PR
-
-**IMPORTANT**: All PRs must pass validation checks before they can be merged.
-
-### Required Checks
-
-Before submitting your PR, run these commands locally:
-
-```bash
-# Run all validation checks
-npm run pre-release
-
-# Or run them individually:
-npm run validate     # Validate agent/team configs
-npm run format:check # Check code formatting
-npm run lint        # Check for linting issues
-```
-
-### Fixing Issues
-
-If any checks fail, use these commands to fix them:
-
-```bash
-# Fix all issues automatically
-npm run fix
-
-# Or fix individually:
-npm run format      # Fix formatting issues
-npm run lint:fix    # Fix linting issues
-```
-
-### Setup Git Hooks (Optional but Recommended)
-
-To catch issues before committing:
-
-```bash
-# Run this once after cloning
-chmod +x tools/setup-hooks.sh
-./tools/setup-hooks.sh
-```
-
 ## How to Contribute
 
 ### Reporting Bugs

README.md

@@ -40,7 +40,7 @@ This two-phase approach eliminates both **planning inconsistency** and **context
 
 - **[Install and Build software with Full Stack Agile AI Team](#quick-start)** → Quick Start Instruction
 - **[Learn how to use BMad](docs/user-guide.md)** → Complete user guide and walkthrough
-- **[See available AI agents](/bmad-core/agents)** → Specialized roles for your team
+- **[See available AI agents](/bmad-core/agents))** → Specialized roles for your team
 - **[Explore non-technical uses](#-beyond-software-development---expansion-packs)** → Creative writing, business, wellness, education
 - **[Create my own AI agents](docs/expansion-packs.md)** → Build agents for your domain
 - **[Browse ready-made expansion packs](expansion-packs/)** → Game dev, DevOps, infrastructure and get inspired with ideas and examples
@@ -212,26 +212,6 @@ The generated XML file contains your project's text-based source files in a stru
 
 📋 **[Read CONTRIBUTING.md](CONTRIBUTING.md)** - Complete guide to contributing, including guidelines, process, and requirements
 
-### Working with Forks
-
-When you fork this repository, CI/CD workflows are **disabled by default** to save resources. This is intentional and helps keep your fork clean.
-
-#### Need CI/CD in Your Fork?
-
-See our [Fork CI/CD Guide](.github/FORK_GUIDE.md) for instructions on enabling workflows in your fork.
-
-#### Contributing Workflow
-
-1. **Fork the repository** - Click the Fork button on GitHub
-2. **Clone your fork** - `git clone https://github.com/YOUR-USERNAME/BMAD-METHOD.git`
-3. **Create a feature branch** - `git checkout -b feature/amazing-feature`
-4. **Make your changes** - Test locally with `npm test`
-5. **Commit your changes** - `git commit -m 'feat: add amazing feature'`
-6. **Push to your fork** - `git push origin feature/amazing-feature`
-7. **Open a Pull Request** - CI/CD will run automatically on the PR
-
-Your contributions are tested when you submit a PR - no need to enable CI in your fork!
-
 ## License
 
 MIT License - see [LICENSE](LICENSE) for details.
@@ -243,19 +223,3 @@ BMAD™ and BMAD-METHOD™ are trademarks of BMad Code, LLC. All rights reserved
 [![Contributors](https://contrib.rocks/image?repo=bmadcode/bmad-method)](https://github.com/bmadcode/bmad-method/graphs/contributors)
 
 <sub>Built with ❤️ for the AI-assisted development community</sub>
-
-#### Codex (CLI & Web)
-
-- Two modes are supported:
-  - Codex (local only): `npx bmad-method install -f -i codex -d .` — keeps `.bmad-core/` ignored via `.gitignore` for local development.
-  - Codex Web Enabled: `npx bmad-method install -f -i codex-web -d .` — ensures `.bmad-core/` is tracked (not ignored) so it can be committed for Codex Web.
-- For Codex Web, commit both `.bmad-core/` and `AGENTS.md` to the repository.
-- Codex CLI: run `codex` at your project root; reference agents naturally, e.g., “As dev, implement …”.
-- Codex Web: open your repo in Codex and prompt the same way — it reads `AGENTS.md` automatically.
-- Refresh after changes: rerun the appropriate install command (`codex` or `codex-web`) to regenerate the BMAD section inside `AGENTS.md`.
-
-If a `package.json` exists in your project, the installer will add helpful scripts:
-
-- `bmad:refresh` → `bmad-method install -f -i codex`
-- `bmad:list` → `bmad-method list:agents`
-- `bmad:validate` → `bmad-method validate`

bmad-core/agents/bmad-master.md

@@ -11,16 +11,16 @@ CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your
 ```yaml
 IDE-FILE-RESOLUTION:
   - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
+  - Dependencies map to root/type/name
   - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
+  - Example: create-doc.md → root/tasks/create-doc.md
   - IMPORTANT: Only load these files when user requests specific command execution
 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), ALWAYS ask for clarification if no clear match.
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
-  - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
+  - STEP 3: Load and read bmad-core/core-config.yaml (project configuration) before any greeting
+  - STEP 4: Greet user with your name/role and immediately run *help to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task
   - The agent.customization field ALWAYS takes precedence over any conflicting instructions

bmad-core/agents/dev.md

@@ -49,7 +49,6 @@ persona:
 
 core_principles:
   - CRITICAL: Story has ALL info you will need aside from what you loaded during the startup commands. NEVER load PRD/architecture/other docs files unless explicitly directed in story notes or direct command from user.
-  - CRITICAL: ALWAYS check current folder structure before starting your story tasks, don't create new working directory if it already exists. Create new one when you're sure it's a brand new project.
   - CRITICAL: ONLY update story file Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
   - CRITICAL: FOLLOW THE develop-story command when the user tells you to implement the story
   - Numbered Options - Always use numbered lists when presenting choices to the user

bmad-core/data/bmad-kb.md

@@ -107,7 +107,7 @@ npx bmad-method install
 
 **Verify Installation**:
 
-- `.bmad-core/` folder created with all agents
+- `bmad-core/` folder created with all agents
 - IDE-specific integration files created
 - All agent commands/rules/modes available
 

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

@@ -10,7 +10,7 @@ To comprehensively validate a story draft before implementation begins, ensuring
 
 ### 0. Load Core Configuration and Inputs
 
-- Load `.bmad-core/core-config.yaml`
+- Load `bmad-core/core-config.yaml`
 - If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story validation."
 - Extract key configurations: `devStoryLocation`, `prd.*`, `architecture.*`
 - Identify and load the following inputs:

bmad-core/workflows/brownfield-fullstack.yaml

@@ -160,7 +160,7 @@ workflow:
         - Dev Agent (New Chat): Address remaining items
         - Return to QA for final approval
 
-    - step: repeat_development_cycle
+    - repeat_development_cycle:
       action: continue_for_all_stories
       notes: |
         Repeat story cycle (SM → Dev → QA) for all epic stories
@@ -177,7 +177,7 @@ workflow:
         - Validate epic was completed correctly
         - Document learnings and improvements
 
-    - step: workflow_end
+    - workflow_end:
       action: project_complete
       notes: |
         All stories implemented and reviewed!

bmad-core/workflows/brownfield-service.yaml

@@ -106,7 +106,7 @@ workflow:
         - Dev Agent (New Chat): Address remaining items
         - Return to QA for final approval
 
-    - step: repeat_development_cycle
+    - repeat_development_cycle:
       action: continue_for_all_stories
       notes: |
         Repeat story cycle (SM → Dev → QA) for all epic stories
@@ -123,7 +123,7 @@ workflow:
         - Validate epic was completed correctly
         - Document learnings and improvements
 
-    - step: workflow_end
+    - workflow_end:
       action: project_complete
       notes: |
         All stories implemented and reviewed!

bmad-core/workflows/brownfield-ui.yaml

@@ -113,7 +113,7 @@ workflow:
         - Dev Agent (New Chat): Address remaining items
         - Return to QA for final approval
 
-    - step: repeat_development_cycle
+    - repeat_development_cycle:
       action: continue_for_all_stories
       notes: |
         Repeat story cycle (SM → Dev → QA) for all epic stories
@@ -130,7 +130,7 @@ workflow:
         - Validate epic was completed correctly
         - Document learnings and improvements
 
-    - step: workflow_end
+    - workflow_end:
       action: project_complete
       notes: |
         All stories implemented and reviewed!

bmad-core/workflows/greenfield-fullstack.yaml

@@ -65,12 +65,12 @@ workflow:
       condition: po_checklist_issues
       notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder."
 
-    - step: project_setup_guidance
+    - project_setup_guidance:
       action: guide_project_structure
       condition: user_has_generated_ui
       notes: "If user generated UI with v0/Lovable: For polyrepo setup, place downloaded project in separate frontend repo alongside backend repo. For monorepo, place in apps/web or packages/frontend directory. Review architecture document for specific guidance."
 
-    - step: development_order_guidance
+    - development_order_guidance:
       action: guide_development_sequence
       notes: "Based on PRD stories: If stories are frontend-heavy, start with frontend project/directory first. If backend-heavy or API-first, start with backend. For tightly coupled features, follow story sequence in monorepo setup. Reference sharded PRD epics for development order."
 
@@ -138,7 +138,7 @@ workflow:
         - Dev Agent (New Chat): Address remaining items
         - Return to QA for final approval
 
-    - step: repeat_development_cycle
+    - repeat_development_cycle:
       action: continue_for_all_stories
       notes: |
         Repeat story cycle (SM → Dev → QA) for all epic stories
@@ -155,7 +155,7 @@ workflow:
         - Validate epic was completed correctly
         - Document learnings and improvements
 
-    - step: workflow_end
+    - workflow_end:
       action: project_complete
       notes: |
         All stories implemented and reviewed!

bmad-core/workflows/greenfield-service.yaml

@@ -114,7 +114,7 @@ workflow:
         - Dev Agent (New Chat): Address remaining items
         - Return to QA for final approval
 
-    - step: repeat_development_cycle
+    - repeat_development_cycle:
       action: continue_for_all_stories
       notes: |
         Repeat story cycle (SM → Dev → QA) for all epic stories
@@ -131,7 +131,7 @@ workflow:
         - Validate epic was completed correctly
         - Document learnings and improvements
 
-    - step: workflow_end
+    - workflow_end:
       action: project_complete
       notes: |
         All stories implemented and reviewed!

bmad-core/workflows/greenfield-ui.yaml

@@ -64,7 +64,7 @@ workflow:
       condition: po_checklist_issues
       notes: "If PO finds issues, return to relevant agent to fix and re-export updated documents to docs/ folder."
 
-    - step: project_setup_guidance
+    - project_setup_guidance:
       action: guide_project_structure
       condition: user_has_generated_ui
       notes: "If user generated UI with v0/Lovable: For polyrepo setup, place downloaded project in separate frontend repo. For monorepo, place in apps/web or frontend/ directory. Review architecture document for specific guidance."
@@ -133,7 +133,7 @@ workflow:
         - Dev Agent (New Chat): Address remaining items
         - Return to QA for final approval
 
-    - step: repeat_development_cycle
+    - repeat_development_cycle:
       action: continue_for_all_stories
       notes: |
         Repeat story cycle (SM → Dev → QA) for all epic stories
@@ -150,7 +150,7 @@ workflow:
         - Validate epic was completed correctly
         - Document learnings and improvements
 
-    - step: workflow_end
+    - workflow_end:
       action: project_complete
       notes: |
         All stories implemented and reviewed!

common/tasks/create-doc.md

@@ -17,7 +17,7 @@ When this task is invoked:
 
 ## Critical: Template Discovery
 
-If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.
+If a YAML Template has not been provided, list all templates from bmad-core/templates or ask the user to provide another.
 
 ## CRITICAL: Mandatory Elicitation Format
 

dist/agents/analyst.txt

@@ -8,13 +8,13 @@ You are now operating as a specialized AI agent from the BMad-Method framework.
 
 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
 
-- `==================== START: .bmad-core/folder/filename.md ====================`
-- `==================== END: .bmad-core/folder/filename.md ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
+- `==================== END: bmad-core/folder/filename.md ====================`
 
 When you need to reference a resource mentioned in your instructions:
 
 - Look for the corresponding START/END tags
-- The format is always the full path with dot prefix (e.g., `.bmad-core/personas/analyst.md`, `.bmad-core/tasks/create-story.md`)
+- The format is always the full path with dot prefix (e.g., `bmad-core/personas/analyst.md`, `bmad-core/tasks/create-story.md`)
 - If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
 
 **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
@@ -29,8 +29,8 @@ dependencies:
 
 These references map directly to bundle sections:
 
-- `utils: template-format` → Look for `==================== START: .bmad-core/utils/template-format.md ====================`
-- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.md ====================`
+- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
+- `tasks: create-story` → Look for `==================== START: bmad-core/tasks/create-story.md ====================`
 
 3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
 
@@ -39,7 +39,7 @@ These references map directly to bundle sections:
 ---
 
 
-==================== START: .bmad-core/agents/analyst.md ====================
+==================== START: bmad-core/agents/analyst.md ====================
 # analyst
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -101,9 +101,9 @@ dependencies:
     - market-research-tmpl.yaml
     - project-brief-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/analyst.md ====================
+==================== END: bmad-core/agents/analyst.md ====================
 
-==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
+==================== START: bmad-core/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
 # Advanced Elicitation Task
 
@@ -222,9 +222,9 @@ Choose a number (0-8) or 9 to proceed:
 - **Stay Relevant**: Tie all elicitation back to the specific content being analyzed
 - **Identify Personas**: For multi-persona methods, clearly identify which viewpoint is speaking
 - **Maintain Flow**: Keep the process moving efficiently
-==================== END: .bmad-core/tasks/advanced-elicitation.md ====================
+==================== END: bmad-core/tasks/advanced-elicitation.md ====================
 
-==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
+==================== START: bmad-core/tasks/create-deep-research-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Deep Research Prompt Task
 
@@ -504,9 +504,9 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
 - Balance comprehensiveness with focus
 - Document assumptions and limitations clearly
 - Plan for iterative refinement based on initial findings
-==================== END: .bmad-core/tasks/create-deep-research-prompt.md ====================
+==================== END: bmad-core/tasks/create-deep-research-prompt.md ====================
 
-==================== START: .bmad-core/tasks/create-doc.md ====================
+==================== START: bmad-core/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Document from Template (YAML Driven)
 
@@ -525,7 +525,7 @@ When this task is invoked:
 
 ## Critical: Template Discovery
 
-If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.
+If a YAML Template has not been provided, list all templates from bmad-core/templates or ask the user to provide another.
 
 ## CRITICAL: Mandatory Elicitation Format
 
@@ -609,9 +609,9 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 - Select options 2-9 from data/elicitation-methods only
 - Provide detailed rationale explaining decisions
 - End with "Select 1-9 or just type your question/feedback:"
-==================== END: .bmad-core/tasks/create-doc.md ====================
+==================== END: bmad-core/tasks/create-doc.md ====================
 
-==================== START: .bmad-core/tasks/document-project.md ====================
+==================== START: bmad-core/tasks/document-project.md ====================
 <!-- Powered by BMAD™ Core -->
 # Document an Existing Project
 
@@ -956,13 +956,13 @@ Apply the advanced elicitation task after major sections to refine based on user
 - Documents technical debt, workarounds, and constraints honestly
 - For brownfield projects with PRD: Provides clear enhancement impact analysis
 - The goal is PRACTICAL documentation for AI agents doing real work
-==================== END: .bmad-core/tasks/document-project.md ====================
+==================== END: bmad-core/tasks/document-project.md ====================
 
-==================== START: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
+==================== START: bmad-core/tasks/facilitate-brainstorming-session.md ====================
 <!-- Powered by BMAD™ Core -->
 ---
 docOutputLocation: docs/brainstorming-session-results.md
-template: '.bmad-core/templates/brainstorming-output-tmpl.yaml'
+template: 'bmad-core/templates/brainstorming-output-tmpl.yaml'
 ---
 
 # Facilitate Brainstorming Session Task
@@ -1096,9 +1096,9 @@ Generate structured document with these sections:
 - Always ask before switching techniques: "Ready to try a different approach?"
 - Offer options: "Should we explore this idea deeper or generate more alternatives?"
 - Respect their process and timing
-==================== END: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
+==================== END: bmad-core/tasks/facilitate-brainstorming-session.md ====================
 
-==================== START: .bmad-core/templates/brainstorming-output-tmpl.yaml ====================
+==================== START: bmad-core/templates/brainstorming-output-tmpl.yaml ====================
 template:
   id: brainstorming-output-template-v2
   name: Brainstorming Session Results
@@ -1255,9 +1255,9 @@ sections:
       ---
 
       *Session facilitated using the BMAD-METHOD™ brainstorming framework*
-==================== END: .bmad-core/templates/brainstorming-output-tmpl.yaml ====================
+==================== END: bmad-core/templates/brainstorming-output-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/competitor-analysis-tmpl.yaml ====================
+==================== START: bmad-core/templates/competitor-analysis-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: competitor-analysis-template-v2
@@ -1565,9 +1565,9 @@ sections:
           - Weekly: {{weekly_items}}
           - Monthly: {{monthly_items}}
           - Quarterly: {{quarterly_analysis}}
-==================== END: .bmad-core/templates/competitor-analysis-tmpl.yaml ====================
+==================== END: bmad-core/templates/competitor-analysis-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/market-research-tmpl.yaml ====================
+==================== START: bmad-core/templates/market-research-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: market-research-template-v2
@@ -1821,9 +1821,9 @@ sections:
       - id: additional-analysis
         title: C. Additional Analysis
         instruction: Any supplementary analysis not included in main body
-==================== END: .bmad-core/templates/market-research-tmpl.yaml ====================
+==================== END: bmad-core/templates/market-research-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/project-brief-tmpl.yaml ====================
+==================== START: bmad-core/templates/project-brief-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: project-brief-template-v2
@@ -2046,9 +2046,9 @@ sections:
         title: PM Handoff
         content: |
           This Project Brief provides the full context for {{project_name}}. Please start in 'PRD Generation Mode', review the brief thoroughly to work with the user to create the PRD section by section as the template indicates, asking for any necessary clarification or suggesting improvements.
-==================== END: .bmad-core/templates/project-brief-tmpl.yaml ====================
+==================== END: bmad-core/templates/project-brief-tmpl.yaml ====================
 
-==================== START: .bmad-core/data/bmad-kb.md ====================
+==================== START: bmad-core/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
 # BMAD™ Knowledge Base
 
@@ -2157,7 +2157,7 @@ npx bmad-method install
 
 **Verify Installation**:
 
-- `.bmad-core/` folder created with all agents
+- `bmad-core/` folder created with all agents
 - IDE-specific integration files created
 - All agent commands/rules/modes available
 
@@ -2856,9 +2856,9 @@ Use the **expansion-creator** pack to build your own:
 - **Documentation**: Check `docs/` folder for project-specific context
 - **Community**: Discord and GitHub resources available for support
 - **Contributing**: See `CONTRIBUTING.md` for full guidelines
-==================== END: .bmad-core/data/bmad-kb.md ====================
+==================== END: bmad-core/data/bmad-kb.md ====================
 
-==================== START: .bmad-core/data/brainstorming-techniques.md ====================
+==================== START: bmad-core/data/brainstorming-techniques.md ====================
 <!-- Powered by BMAD™ Core -->
 # Brainstorming Techniques Data
 
@@ -2896,4 +2896,4 @@ Use the **expansion-creator** pack to build your own:
 18. **Resource Constraints**: "What if you had only $10 and 1 hour?"
 19. **Metaphor Mapping**: Use extended metaphors to explore solutions
 20. **Question Storming**: Generate questions instead of answers first
-==================== END: .bmad-core/data/brainstorming-techniques.md ====================
+==================== END: bmad-core/data/brainstorming-techniques.md ====================

dist/agents/architect.txt

@@ -8,13 +8,13 @@ You are now operating as a specialized AI agent from the BMad-Method framework.
 
 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
 
-- `==================== START: .bmad-core/folder/filename.md ====================`
-- `==================== END: .bmad-core/folder/filename.md ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
+- `==================== END: bmad-core/folder/filename.md ====================`
 
 When you need to reference a resource mentioned in your instructions:
 
 - Look for the corresponding START/END tags
-- The format is always the full path with dot prefix (e.g., `.bmad-core/personas/analyst.md`, `.bmad-core/tasks/create-story.md`)
+- The format is always the full path with dot prefix (e.g., `bmad-core/personas/analyst.md`, `bmad-core/tasks/create-story.md`)
 - If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
 
 **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
@@ -29,8 +29,8 @@ dependencies:
 
 These references map directly to bundle sections:
 
-- `utils: template-format` → Look for `==================== START: .bmad-core/utils/template-format.md ====================`
-- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.md ====================`
+- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
+- `tasks: create-story` → Look for `==================== START: bmad-core/tasks/create-story.md ====================`
 
 3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
 
@@ -39,7 +39,7 @@ These references map directly to bundle sections:
 ---
 
 
-==================== START: .bmad-core/agents/architect.md ====================
+==================== START: bmad-core/agents/architect.md ====================
 # architect
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -102,9 +102,9 @@ dependencies:
     - front-end-architecture-tmpl.yaml
     - fullstack-architecture-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/architect.md ====================
+==================== END: bmad-core/agents/architect.md ====================
 
-==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
+==================== START: bmad-core/tasks/create-deep-research-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Deep Research Prompt Task
 
@@ -384,9 +384,9 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
 - Balance comprehensiveness with focus
 - Document assumptions and limitations clearly
 - Plan for iterative refinement based on initial findings
-==================== END: .bmad-core/tasks/create-deep-research-prompt.md ====================
+==================== END: bmad-core/tasks/create-deep-research-prompt.md ====================
 
-==================== START: .bmad-core/tasks/create-doc.md ====================
+==================== START: bmad-core/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Document from Template (YAML Driven)
 
@@ -405,7 +405,7 @@ When this task is invoked:
 
 ## Critical: Template Discovery
 
-If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.
+If a YAML Template has not been provided, list all templates from bmad-core/templates or ask the user to provide another.
 
 ## CRITICAL: Mandatory Elicitation Format
 
@@ -489,9 +489,9 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 - Select options 2-9 from data/elicitation-methods only
 - Provide detailed rationale explaining decisions
 - End with "Select 1-9 or just type your question/feedback:"
-==================== END: .bmad-core/tasks/create-doc.md ====================
+==================== END: bmad-core/tasks/create-doc.md ====================
 
-==================== START: .bmad-core/tasks/document-project.md ====================
+==================== START: bmad-core/tasks/document-project.md ====================
 <!-- Powered by BMAD™ Core -->
 # Document an Existing Project
 
@@ -836,9 +836,9 @@ Apply the advanced elicitation task after major sections to refine based on user
 - Documents technical debt, workarounds, and constraints honestly
 - For brownfield projects with PRD: Provides clear enhancement impact analysis
 - The goal is PRACTICAL documentation for AI agents doing real work
-==================== END: .bmad-core/tasks/document-project.md ====================
+==================== END: bmad-core/tasks/document-project.md ====================
 
-==================== START: .bmad-core/tasks/execute-checklist.md ====================
+==================== START: bmad-core/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
@@ -846,7 +846,7 @@ This task provides instructions for validating documentation against checklists.
 
 ## 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.
+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
 
@@ -854,7 +854,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
    - If user or the task being run provides a checklist name:
      - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
      - If multiple matches found, ask user to clarify
-     - Load the appropriate checklist from .bmad-core/checklists/
+     - 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
@@ -926,9 +926,9 @@ The LLM will:
 - Execute the complete checklist validation
 - Present a final report with pass/fail rates and key findings
 - Offer to provide detailed analysis of any section, especially those with warnings or failures
-==================== END: .bmad-core/tasks/execute-checklist.md ====================
+==================== END: bmad-core/tasks/execute-checklist.md ====================
 
-==================== START: .bmad-core/templates/architecture-tmpl.yaml ====================
+==================== START: bmad-core/templates/architecture-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: architecture-template-v2
@@ -1059,7 +1059,7 @@ sections:
     instruction: |
       This is the DEFINITIVE technology selection section. Work with the user to make specific choices:
 
-      1. Review PRD technical assumptions and any preferences from .bmad-core/data/technical-preferences.yaml or an attached technical-preferences
+      1. Review PRD technical assumptions and any preferences from bmad-core/data/technical-preferences.yaml or an attached technical-preferences
       2. For each category, present 2-3 viable options with pros/cons
       3. Make a clear recommendation based on project needs
       4. Get explicit user approval for each selection
@@ -1580,9 +1580,9 @@ sections:
           - Key UI requirements from PRD
           - Any frontend-specific decisions made here
           - Request for detailed frontend architecture
-==================== END: .bmad-core/templates/architecture-tmpl.yaml ====================
+==================== END: bmad-core/templates/architecture-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
+==================== START: bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: brownfield-architecture-template-v2
@@ -2060,9 +2060,9 @@ sections:
           - Key technical decisions based on real project constraints
           - Existing system compatibility requirements with specific verification steps
           - Clear sequencing of implementation to minimize risk to existing functionality
-==================== END: .bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
+==================== END: bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/front-end-architecture-tmpl.yaml ====================
+==================== START: bmad-core/templates/front-end-architecture-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: frontend-architecture-template-v2
@@ -2282,9 +2282,9 @@ sections:
           - Key import patterns
           - File naming conventions
           - Project-specific patterns and utilities
-==================== END: .bmad-core/templates/front-end-architecture-tmpl.yaml ====================
+==================== END: bmad-core/templates/front-end-architecture-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
+==================== START: bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: fullstack-architecture-template-v2
@@ -3109,9 +3109,9 @@ sections:
   - id: checklist-results
     title: Checklist Results Report
     instruction: Before running the checklist, offer to output the full architecture document. Once user confirms, execute the architect-checklist and populate results here.
-==================== END: .bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
+==================== END: bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
 
-==================== START: .bmad-core/checklists/architect-checklist.md ====================
+==================== START: bmad-core/checklists/architect-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Architect Solution Validation Checklist
 
@@ -3551,11 +3551,11 @@ Now that you've completed the checklist, generate a comprehensive validation rep
    - Component design clarity
 
 After presenting the report, ask the user if they would like detailed analysis of any specific section, especially those with warnings or failures.]]
-==================== END: .bmad-core/checklists/architect-checklist.md ====================
+==================== END: bmad-core/checklists/architect-checklist.md ====================
 
-==================== START: .bmad-core/data/technical-preferences.md ====================
+==================== START: bmad-core/data/technical-preferences.md ====================
 <!-- Powered by BMAD™ Core -->
 # User-Defined Preferred Patterns and Preferences
 
 None Listed
-==================== END: .bmad-core/data/technical-preferences.md ====================
+==================== END: bmad-core/data/technical-preferences.md ====================

dist/agents/bmad-master.txt

@@ -8,13 +8,13 @@ You are now operating as a specialized AI agent from the BMad-Method framework.
 
 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
 
-- `==================== START: .bmad-core/folder/filename.md ====================`
-- `==================== END: .bmad-core/folder/filename.md ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
+- `==================== END: bmad-core/folder/filename.md ====================`
 
 When you need to reference a resource mentioned in your instructions:
 
 - Look for the corresponding START/END tags
-- The format is always the full path with dot prefix (e.g., `.bmad-core/personas/analyst.md`, `.bmad-core/tasks/create-story.md`)
+- The format is always the full path with dot prefix (e.g., `bmad-core/personas/analyst.md`, `bmad-core/tasks/create-story.md`)
 - If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
 
 **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
@@ -29,8 +29,8 @@ dependencies:
 
 These references map directly to bundle sections:
 
-- `utils: template-format` → Look for `==================== START: .bmad-core/utils/template-format.md ====================`
-- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.md ====================`
+- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
+- `tasks: create-story` → Look for `==================== START: bmad-core/tasks/create-story.md ====================`
 
 3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
 
@@ -39,7 +39,7 @@ These references map directly to bundle sections:
 ---
 
 
-==================== START: .bmad-core/agents/bmad-master.md ====================
+==================== START: bmad-core/agents/bmad-master.md ====================
 # bmad-master
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -72,7 +72,7 @@ commands:
   - doc-out: Output full document to current destination file
   - document-project: execute the task document-project.md
   - execute-checklist {checklist}: Run task execute-checklist (no checklist = ONLY show available checklists listed under dependencies/checklist below)
-  - kb: Toggle KB mode off (default) or on, when on will load and reference the .bmad-core/data/bmad-kb.md and converse with the user answering his questions with this informational resource
+  - kb: Toggle KB mode off (default) or on, when on will load and reference the bmad-core/data/bmad-kb.md and converse with the user answering his questions with this informational resource
   - shard-doc {document} {destination}: run the task shard-doc against the optionally provided document to the specified destination
   - task {task}: Execute task, if not found or none specified, ONLY list available dependencies/tasks listed below
   - yolo: Toggle Yolo Mode
@@ -124,9 +124,9 @@ dependencies:
     - greenfield-service.md
     - greenfield-ui.md
 ```
-==================== END: .bmad-core/agents/bmad-master.md ====================
+==================== END: bmad-core/agents/bmad-master.md ====================
 
-==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
+==================== START: bmad-core/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
 # Advanced Elicitation Task
 
@@ -245,9 +245,9 @@ Choose a number (0-8) or 9 to proceed:
 - **Stay Relevant**: Tie all elicitation back to the specific content being analyzed
 - **Identify Personas**: For multi-persona methods, clearly identify which viewpoint is speaking
 - **Maintain Flow**: Keep the process moving efficiently
-==================== END: .bmad-core/tasks/advanced-elicitation.md ====================
+==================== END: bmad-core/tasks/advanced-elicitation.md ====================
 
-==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
+==================== START: bmad-core/tasks/brownfield-create-epic.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Brownfield Epic Task
 
@@ -409,9 +409,9 @@ The epic creation is successful when:
 - If the scope grows beyond 3 stories, consider the full brownfield PRD process
 - Always prioritize existing system integrity over new functionality
 - When in doubt about scope or complexity, escalate to full brownfield planning
-==================== END: .bmad-core/tasks/brownfield-create-epic.md ====================
+==================== END: bmad-core/tasks/brownfield-create-epic.md ====================
 
-==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
+==================== START: bmad-core/tasks/brownfield-create-story.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Brownfield Story Task
 
@@ -560,15 +560,15 @@ The story creation is successful when:
 - Always prioritize existing system integrity
 - When in doubt about integration complexity, use brownfield-create-epic instead
 - Stories should take no more than 4 hours of focused development work
-==================== END: .bmad-core/tasks/brownfield-create-story.md ====================
+==================== END: bmad-core/tasks/brownfield-create-story.md ====================
 
-==================== START: .bmad-core/tasks/correct-course.md ====================
+==================== START: bmad-core/tasks/correct-course.md ====================
 <!-- Powered by BMAD™ Core -->
 # Correct Course Task
 
 ## Purpose
 
-- Guide a structured response to a change trigger using the `.bmad-core/checklists/change-checklist`.
+- Guide a structured response to a change trigger using the `bmad-core/checklists/change-checklist`.
 - Analyze the impacts of the change on epics, project artifacts, and the MVP, guided by the checklist's structure.
 - Explore potential solutions (e.g., adjust scope, rollback elements, re-scope features) as prompted by the checklist.
 - Draft specific, actionable proposed updates to any affected project artifacts (e.g., epics, user stories, PRD sections, architecture document sections) based on the analysis.
@@ -582,7 +582,7 @@ The story creation is successful when:
 - **Acknowledge Task & Inputs:**
   - Confirm with the user that the "Correct Course Task" (Change Navigation & Integration) is being initiated.
   - Verify the change trigger and ensure you have the user's initial explanation of the issue and its perceived impact.
-  - Confirm access to all relevant project artifacts (e.g., PRD, Epics/Stories, Architecture Documents, UI/UX Specifications) and, critically, the `.bmad-core/checklists/change-checklist`.
+  - Confirm access to all relevant project artifacts (e.g., PRD, Epics/Stories, Architecture Documents, UI/UX Specifications) and, critically, the `bmad-core/checklists/change-checklist`.
 - **Establish Interaction Mode:**
   - Ask the user their preferred interaction mode for this task:
     - **"Incrementally (Default & Recommended):** Shall we work through the change-checklist section by section, discussing findings and collaboratively drafting proposed changes for each relevant part before moving to the next? This allows for detailed, step-by-step refinement."
@@ -634,9 +634,9 @@ The story creation is successful when:
   - A summary of the change-checklist analysis (issue, impact, rationale for the chosen path).
   - Specific, clearly drafted proposed edits for all affected project artifacts.
 - **Implicit:** An annotated change-checklist (or the record of its completion) reflecting the discussions, findings, and decisions made during the process.
-==================== END: .bmad-core/tasks/correct-course.md ====================
+==================== END: bmad-core/tasks/correct-course.md ====================
 
-==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
+==================== START: bmad-core/tasks/create-deep-research-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Deep Research Prompt Task
 
@@ -916,9 +916,9 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
 - Balance comprehensiveness with focus
 - Document assumptions and limitations clearly
 - Plan for iterative refinement based on initial findings
-==================== END: .bmad-core/tasks/create-deep-research-prompt.md ====================
+==================== END: bmad-core/tasks/create-deep-research-prompt.md ====================
 
-==================== START: .bmad-core/tasks/create-doc.md ====================
+==================== START: bmad-core/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Document from Template (YAML Driven)
 
@@ -937,7 +937,7 @@ When this task is invoked:
 
 ## Critical: Template Discovery
 
-If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.
+If a YAML Template has not been provided, list all templates from bmad-core/templates or ask the user to provide another.
 
 ## CRITICAL: Mandatory Elicitation Format
 
@@ -1021,9 +1021,9 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 - Select options 2-9 from data/elicitation-methods only
 - Provide detailed rationale explaining decisions
 - End with "Select 1-9 or just type your question/feedback:"
-==================== END: .bmad-core/tasks/create-doc.md ====================
+==================== END: bmad-core/tasks/create-doc.md ====================
 
-==================== START: .bmad-core/tasks/create-next-story.md ====================
+==================== START: bmad-core/tasks/create-next-story.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Next Story Task
 
@@ -1035,7 +1035,7 @@ To identify the next logical story based on project progress and epic definition
 
 ### 0. Load Core Configuration and Check Workflow
 
-- Load `.bmad-core/core-config.yaml` from the project root
+- Load `bmad-core/core-config.yaml` from the project root
 - If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story creation. You can either: 1) Copy it from GITHUB bmad-core/core-config.yaml and configure it for your project OR 2) Run the BMad installer against your project to upgrade and add the file automatically. Please add and configure core-config.yaml before proceeding."
 - Extract key configurations: `devStoryLocation`, `prd.*`, `architecture.*`, `workflow.*`
 
@@ -1129,17 +1129,17 @@ ALWAYS cite source documents: `[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" and save the story file
-- Execute `.bmad-core/tasks/execute-checklist` `.bmad-core/checklists/story-draft-checklist`
+- Execute `bmad-core/tasks/execute-checklist` `bmad-core/checklists/story-draft-checklist`
 - Provide summary to user including:
   - Story created: `{devStoryLocation}/{epicNum}.{storyNum}.story.md`
   - Status: Draft
   - Key technical components included from architecture docs
   - Any deviations or conflicts noted between epic and architecture
   - Checklist Results
-  - Next steps: For Complex stories, suggest the user carefully review the story draft and also optionally have the PO run the task `.bmad-core/tasks/validate-next-story`
-==================== END: .bmad-core/tasks/create-next-story.md ====================
+  - Next steps: For Complex stories, suggest the user carefully review the story draft and also optionally have the PO run the task `bmad-core/tasks/validate-next-story`
+==================== END: bmad-core/tasks/create-next-story.md ====================
 
-==================== START: .bmad-core/tasks/document-project.md ====================
+==================== START: bmad-core/tasks/document-project.md ====================
 <!-- Powered by BMAD™ Core -->
 # Document an Existing Project
 
@@ -1484,9 +1484,9 @@ Apply the advanced elicitation task after major sections to refine based on user
 - Documents technical debt, workarounds, and constraints honestly
 - For brownfield projects with PRD: Provides clear enhancement impact analysis
 - The goal is PRACTICAL documentation for AI agents doing real work
-==================== END: .bmad-core/tasks/document-project.md ====================
+==================== END: bmad-core/tasks/document-project.md ====================
 
-==================== START: .bmad-core/tasks/execute-checklist.md ====================
+==================== START: bmad-core/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
@@ -1494,7 +1494,7 @@ This task provides instructions for validating documentation against checklists.
 
 ## 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.
+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
 
@@ -1502,7 +1502,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
    - If user or the task being run provides a checklist name:
      - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
      - If multiple matches found, ask user to clarify
-     - Load the appropriate checklist from .bmad-core/checklists/
+     - 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
@@ -1574,13 +1574,13 @@ 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: .bmad-core/tasks/execute-checklist.md ====================
+==================== END: bmad-core/tasks/execute-checklist.md ====================
 
-==================== START: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
+==================== START: bmad-core/tasks/facilitate-brainstorming-session.md ====================
 <!-- Powered by BMAD™ Core -->
 ---
 docOutputLocation: docs/brainstorming-session-results.md
-template: '.bmad-core/templates/brainstorming-output-tmpl.yaml'
+template: 'bmad-core/templates/brainstorming-output-tmpl.yaml'
 ---
 
 # Facilitate Brainstorming Session Task
@@ -1714,9 +1714,9 @@ Generate structured document with these sections:
 - Always ask before switching techniques: "Ready to try a different approach?"
 - Offer options: "Should we explore this idea deeper or generate more alternatives?"
 - Respect their process and timing
-==================== END: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
+==================== END: bmad-core/tasks/facilitate-brainstorming-session.md ====================
 
-==================== START: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
+==================== START: bmad-core/tasks/generate-ai-frontend-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create AI Frontend Prompt Task
 
@@ -1769,9 +1769,9 @@ You will now synthesize the inputs and the above principles into a final, compre
    - Output the complete, generated prompt in a clear, copy-pasteable format (e.g., a large code block).
    - Explain the structure of the prompt and why certain information was included, referencing the principles above.
    - <important_note>Conclude by reminding the user that all AI-generated code will require careful human review, testing, and refinement to be considered production-ready.</important_note>
-==================== END: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
+==================== END: bmad-core/tasks/generate-ai-frontend-prompt.md ====================
 
-==================== START: .bmad-core/tasks/index-docs.md ====================
+==================== START: bmad-core/tasks/index-docs.md ====================
 <!-- Powered by BMAD™ Core -->
 # Index Documentation Task
 
@@ -1946,9 +1946,9 @@ Please provide:
 5. Whether to include hidden files/folders (starting with `.`)
 
 Would you like to proceed with documentation indexing? Please provide the required input above.
-==================== END: .bmad-core/tasks/index-docs.md ====================
+==================== END: bmad-core/tasks/index-docs.md ====================
 
-==================== START: .bmad-core/tasks/shard-doc.md ====================
+==================== START: bmad-core/tasks/shard-doc.md ====================
 <!-- Powered by BMAD™ Core -->
 # Document Sharding Task
 
@@ -1960,20 +1960,20 @@ Would you like to proceed with documentation indexing? Please provide the requir
 
 ## Primary Method: Automatic with markdown-tree
 
-[[LLM: First, check if markdownExploder is set to true in .bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
+[[LLM: First, check if markdownExploder is set to true in bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
 
 If the command succeeds, inform the user that the document has been sharded successfully and STOP - do not proceed further.
 
 If the command fails (especially with an error indicating the command is not found or not available), inform the user: "The markdownExploder setting is enabled but the md-tree command is not available. Please either:
 
 1. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
-2. Or set markdownExploder to false in .bmad-core/core-config.yaml
+2. Or set markdownExploder to false in bmad-core/core-config.yaml
 
 **IMPORTANT: STOP HERE - do not proceed with manual sharding until one of the above actions is taken.**"
 
 If markdownExploder is set to false, inform the user: "The markdownExploder setting is currently false. For better performance and reliability, you should:
 
-1. Set markdownExploder to true in .bmad-core/core-config.yaml
+1. Set markdownExploder to true in bmad-core/core-config.yaml
 2. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
 
 I will now proceed with the manual sharding process."
@@ -2135,9 +2135,9 @@ Document sharded successfully:
 - Preserve ALL formatting, including whitespace where significant
 - Handle edge cases like sections with code blocks containing ## symbols
 - Ensure the sharding is reversible (could reconstruct the original from shards)
-==================== END: .bmad-core/tasks/shard-doc.md ====================
+==================== END: bmad-core/tasks/shard-doc.md ====================
 
-==================== START: .bmad-core/templates/architecture-tmpl.yaml ====================
+==================== START: bmad-core/templates/architecture-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: architecture-template-v2
@@ -2268,7 +2268,7 @@ sections:
     instruction: |
       This is the DEFINITIVE technology selection section. Work with the user to make specific choices:
 
-      1. Review PRD technical assumptions and any preferences from .bmad-core/data/technical-preferences.yaml or an attached technical-preferences
+      1. Review PRD technical assumptions and any preferences from bmad-core/data/technical-preferences.yaml or an attached technical-preferences
       2. For each category, present 2-3 viable options with pros/cons
       3. Make a clear recommendation based on project needs
       4. Get explicit user approval for each selection
@@ -2789,9 +2789,9 @@ sections:
           - Key UI requirements from PRD
           - Any frontend-specific decisions made here
           - Request for detailed frontend architecture
-==================== END: .bmad-core/templates/architecture-tmpl.yaml ====================
+==================== END: bmad-core/templates/architecture-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
+==================== START: bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: brownfield-architecture-template-v2
@@ -3269,9 +3269,9 @@ sections:
           - Key technical decisions based on real project constraints
           - Existing system compatibility requirements with specific verification steps
           - Clear sequencing of implementation to minimize risk to existing functionality
-==================== END: .bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
+==================== END: bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/brownfield-prd-tmpl.yaml ====================
+==================== START: bmad-core/templates/brownfield-prd-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: brownfield-prd-template-v2
@@ -3553,9 +3553,9 @@ sections:
               - template: "IV1: {{existing_functionality_verification}}"
               - template: "IV2: {{integration_point_verification}}"
               - template: "IV3: {{performance_impact_verification}}"
-==================== END: .bmad-core/templates/brownfield-prd-tmpl.yaml ====================
+==================== END: bmad-core/templates/brownfield-prd-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/competitor-analysis-tmpl.yaml ====================
+==================== START: bmad-core/templates/competitor-analysis-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: competitor-analysis-template-v2
@@ -3863,9 +3863,9 @@ sections:
           - Weekly: {{weekly_items}}
           - Monthly: {{monthly_items}}
           - Quarterly: {{quarterly_analysis}}
-==================== END: .bmad-core/templates/competitor-analysis-tmpl.yaml ====================
+==================== END: bmad-core/templates/competitor-analysis-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/front-end-architecture-tmpl.yaml ====================
+==================== START: bmad-core/templates/front-end-architecture-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: frontend-architecture-template-v2
@@ -4085,9 +4085,9 @@ sections:
           - Key import patterns
           - File naming conventions
           - Project-specific patterns and utilities
-==================== END: .bmad-core/templates/front-end-architecture-tmpl.yaml ====================
+==================== END: bmad-core/templates/front-end-architecture-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/front-end-spec-tmpl.yaml ====================
+==================== START: bmad-core/templates/front-end-spec-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: frontend-spec-template-v2
@@ -4438,9 +4438,9 @@ sections:
   - id: checklist-results
     title: Checklist Results
     instruction: If a UI/UX checklist exists, run it against this document and report results here.
-==================== END: .bmad-core/templates/front-end-spec-tmpl.yaml ====================
+==================== END: bmad-core/templates/front-end-spec-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
+==================== START: bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: fullstack-architecture-template-v2
@@ -5265,9 +5265,9 @@ sections:
   - id: checklist-results
     title: Checklist Results Report
     instruction: Before running the checklist, offer to output the full architecture document. Once user confirms, execute the architect-checklist and populate results here.
-==================== END: .bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
+==================== END: bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/market-research-tmpl.yaml ====================
+==================== START: bmad-core/templates/market-research-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: market-research-template-v2
@@ -5521,9 +5521,9 @@ sections:
       - id: additional-analysis
         title: C. Additional Analysis
         instruction: Any supplementary analysis not included in main body
-==================== END: .bmad-core/templates/market-research-tmpl.yaml ====================
+==================== END: bmad-core/templates/market-research-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/prd-tmpl.yaml ====================
+==================== START: bmad-core/templates/prd-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: prd-template-v2
@@ -5626,7 +5626,7 @@ sections:
     instruction: |
       Gather technical decisions that will guide the Architect. Steps:
 
-      1. Check if .bmad-core/data/technical-preferences.yaml or an attached technical-preferences file exists - use it to pre-populate choices
+      1. Check if bmad-core/data/technical-preferences.yaml or an attached technical-preferences file exists - use it to pre-populate choices
       2. Ask user about: languages, frameworks, starter templates, libraries, APIs, deployment targets
       3. For unknowns, offer guidance based on project goals and MVP scope
       4. Document ALL technical choices with rationale (why this choice fits the project)
@@ -5727,9 +5727,9 @@ sections:
       - id: architect-prompt
         title: Architect Prompt
         instruction: This section will contain the prompt for the Architect, keep it short and to the point to initiate create architecture mode using this document as input.
-==================== END: .bmad-core/templates/prd-tmpl.yaml ====================
+==================== END: bmad-core/templates/prd-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/project-brief-tmpl.yaml ====================
+==================== START: bmad-core/templates/project-brief-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: project-brief-template-v2
@@ -5952,9 +5952,9 @@ sections:
         title: PM Handoff
         content: |
           This Project Brief provides the full context for {{project_name}}. Please start in 'PRD Generation Mode', review the brief thoroughly to work with the user to create the PRD section by section as the template indicates, asking for any necessary clarification or suggesting improvements.
-==================== END: .bmad-core/templates/project-brief-tmpl.yaml ====================
+==================== END: bmad-core/templates/project-brief-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/story-tmpl.yaml ====================
+==================== START: bmad-core/templates/story-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: story-template-v2
@@ -6093,9 +6093,9 @@ sections:
     instruction: Results from QA Agent QA review of the completed story implementation
     owner: qa-agent
     editors: [qa-agent]
-==================== END: .bmad-core/templates/story-tmpl.yaml ====================
+==================== END: bmad-core/templates/story-tmpl.yaml ====================
 
-==================== START: .bmad-core/checklists/architect-checklist.md ====================
+==================== START: bmad-core/checklists/architect-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Architect Solution Validation Checklist
 
@@ -6535,9 +6535,9 @@ Now that you've completed the checklist, generate a comprehensive validation rep
    - Component design clarity
 
 After presenting the report, ask the user if they would like detailed analysis of any specific section, especially those with warnings or failures.]]
-==================== END: .bmad-core/checklists/architect-checklist.md ====================
+==================== END: bmad-core/checklists/architect-checklist.md ====================
 
-==================== START: .bmad-core/checklists/change-checklist.md ====================
+==================== START: bmad-core/checklists/change-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Change Navigation Checklist
 
@@ -6721,9 +6721,9 @@ Keep it action-oriented and forward-looking.]]
 - [ ] **Confirm Next Steps:** Reiterate the handoff plan and the next actions to be taken by specific agents.
 
 ---
-==================== END: .bmad-core/checklists/change-checklist.md ====================
+==================== END: bmad-core/checklists/change-checklist.md ====================
 
-==================== START: .bmad-core/checklists/pm-checklist.md ====================
+==================== START: bmad-core/checklists/pm-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Product Manager (PM) Requirements Checklist
 
@@ -7095,9 +7095,9 @@ After presenting the report, ask if the user wants:
 
 - **READY FOR ARCHITECT**: The PRD and epics are comprehensive, properly structured, and ready for architectural design.
 - **NEEDS REFINEMENT**: The requirements documentation requires additional work to address the identified deficiencies.
-==================== END: .bmad-core/checklists/pm-checklist.md ====================
+==================== END: bmad-core/checklists/pm-checklist.md ====================
 
-==================== START: .bmad-core/checklists/po-master-checklist.md ====================
+==================== START: bmad-core/checklists/po-master-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Product Owner (PO) Master Validation Checklist
 
@@ -7531,9 +7531,9 @@ After presenting the report, ask if the user wants:
 - **APPROVED**: The plan is comprehensive, properly sequenced, and ready for implementation.
 - **CONDITIONAL**: The plan requires specific adjustments before proceeding.
 - **REJECTED**: The plan requires significant revision to address critical deficiencies.
-==================== END: .bmad-core/checklists/po-master-checklist.md ====================
+==================== END: bmad-core/checklists/po-master-checklist.md ====================
 
-==================== START: .bmad-core/checklists/story-dod-checklist.md ====================
+==================== START: bmad-core/checklists/story-dod-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Story Definition of Done (DoD) Checklist
 
@@ -7629,9 +7629,9 @@ After completing the checklist:
 Be honest - it's better to flag issues now than have them discovered later.]]
 
 - [ ] I, the Developer Agent, confirm that all applicable items above have been addressed.
-==================== END: .bmad-core/checklists/story-dod-checklist.md ====================
+==================== END: bmad-core/checklists/story-dod-checklist.md ====================
 
-==================== START: .bmad-core/checklists/story-draft-checklist.md ====================
+==================== START: bmad-core/checklists/story-draft-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Story Draft Checklist
 
@@ -7786,9 +7786,9 @@ Be pragmatic - perfect documentation doesn't exist, but it must be enough to pro
 - READY: The story provides sufficient context for implementation
 - NEEDS REVISION: The story requires updates (see issues)
 - BLOCKED: External information required (specify what information)
-==================== END: .bmad-core/checklists/story-draft-checklist.md ====================
+==================== END: bmad-core/checklists/story-draft-checklist.md ====================
 
-==================== START: .bmad-core/data/bmad-kb.md ====================
+==================== START: bmad-core/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
 # BMAD™ Knowledge Base
 
@@ -7897,7 +7897,7 @@ npx bmad-method install
 
 **Verify Installation**:
 
-- `.bmad-core/` folder created with all agents
+- `bmad-core/` folder created with all agents
 - IDE-specific integration files created
 - All agent commands/rules/modes available
 
@@ -8596,9 +8596,9 @@ Use the **expansion-creator** pack to build your own:
 - **Documentation**: Check `docs/` folder for project-specific context
 - **Community**: Discord and GitHub resources available for support
 - **Contributing**: See `CONTRIBUTING.md` for full guidelines
-==================== END: .bmad-core/data/bmad-kb.md ====================
+==================== END: bmad-core/data/bmad-kb.md ====================
 
-==================== START: .bmad-core/data/brainstorming-techniques.md ====================
+==================== START: bmad-core/data/brainstorming-techniques.md ====================
 <!-- Powered by BMAD™ Core -->
 # Brainstorming Techniques Data
 
@@ -8636,9 +8636,9 @@ Use the **expansion-creator** pack to build your own:
 18. **Resource Constraints**: "What if you had only $10 and 1 hour?"
 19. **Metaphor Mapping**: Use extended metaphors to explore solutions
 20. **Question Storming**: Generate questions instead of answers first
-==================== END: .bmad-core/data/brainstorming-techniques.md ====================
+==================== END: bmad-core/data/brainstorming-techniques.md ====================
 
-==================== START: .bmad-core/data/elicitation-methods.md ====================
+==================== START: bmad-core/data/elicitation-methods.md ====================
 <!-- Powered by BMAD™ Core -->
 # Elicitation Methods Data
 
@@ -8794,11 +8794,11 @@ Use the **expansion-creator** pack to build your own:
 - Acknowledge choice to finalize current work
 - Accept output as-is or move to next step
 - Prepare to continue without additional elicitation
-==================== END: .bmad-core/data/elicitation-methods.md ====================
+==================== END: bmad-core/data/elicitation-methods.md ====================
 
-==================== START: .bmad-core/data/technical-preferences.md ====================
+==================== START: bmad-core/data/technical-preferences.md ====================
 <!-- Powered by BMAD™ Core -->
 # User-Defined Preferred Patterns and Preferences
 
 None Listed
-==================== END: .bmad-core/data/technical-preferences.md ====================
+==================== END: bmad-core/data/technical-preferences.md ====================

dist/agents/bmad-orchestrator.txt

@@ -8,13 +8,13 @@ You are now operating as a specialized AI agent from the BMad-Method framework.
 
 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
 
-- `==================== START: .bmad-core/folder/filename.md ====================`
-- `==================== END: .bmad-core/folder/filename.md ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
+- `==================== END: bmad-core/folder/filename.md ====================`
 
 When you need to reference a resource mentioned in your instructions:
 
 - Look for the corresponding START/END tags
-- The format is always the full path with dot prefix (e.g., `.bmad-core/personas/analyst.md`, `.bmad-core/tasks/create-story.md`)
+- The format is always the full path with dot prefix (e.g., `bmad-core/personas/analyst.md`, `bmad-core/tasks/create-story.md`)
 - If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
 
 **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
@@ -29,8 +29,8 @@ dependencies:
 
 These references map directly to bundle sections:
 
-- `utils: template-format` → Look for `==================== START: .bmad-core/utils/template-format.md ====================`
-- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.md ====================`
+- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
+- `tasks: create-story` → Look for `==================== START: bmad-core/tasks/create-story.md ====================`
 
 3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
 
@@ -39,7 +39,7 @@ These references map directly to bundle sections:
 ---
 
 
-==================== START: .bmad-core/agents/bmad-orchestrator.md ====================
+==================== START: bmad-core/agents/bmad-orchestrator.md ====================
 # bmad-orchestrator
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -164,9 +164,9 @@ dependencies:
   utils:
     - workflow-management.md
 ```
-==================== END: .bmad-core/agents/bmad-orchestrator.md ====================
+==================== END: bmad-core/agents/bmad-orchestrator.md ====================
 
-==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
+==================== START: bmad-core/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
 # Advanced Elicitation Task
 
@@ -285,9 +285,9 @@ Choose a number (0-8) or 9 to proceed:
 - **Stay Relevant**: Tie all elicitation back to the specific content being analyzed
 - **Identify Personas**: For multi-persona methods, clearly identify which viewpoint is speaking
 - **Maintain Flow**: Keep the process moving efficiently
-==================== END: .bmad-core/tasks/advanced-elicitation.md ====================
+==================== END: bmad-core/tasks/advanced-elicitation.md ====================
 
-==================== START: .bmad-core/tasks/create-doc.md ====================
+==================== START: bmad-core/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Document from Template (YAML Driven)
 
@@ -306,7 +306,7 @@ When this task is invoked:
 
 ## Critical: Template Discovery
 
-If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.
+If a YAML Template has not been provided, list all templates from bmad-core/templates or ask the user to provide another.
 
 ## CRITICAL: Mandatory Elicitation Format
 
@@ -390,9 +390,9 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 - Select options 2-9 from data/elicitation-methods only
 - Provide detailed rationale explaining decisions
 - End with "Select 1-9 or just type your question/feedback:"
-==================== END: .bmad-core/tasks/create-doc.md ====================
+==================== END: bmad-core/tasks/create-doc.md ====================
 
-==================== START: .bmad-core/tasks/kb-mode-interaction.md ====================
+==================== START: bmad-core/tasks/kb-mode-interaction.md ====================
 <!-- Powered by BMAD™ Core -->
 # KB Mode Interaction Task
 
@@ -469,9 +469,9 @@ Or ask me about anything else related to BMad-Method!
 **User**: Tell me about workflows
 
 **Assistant**: [Provides focused information about workflows from the KB, then offers to explore specific workflow types or related topics]
-==================== END: .bmad-core/tasks/kb-mode-interaction.md ====================
+==================== END: bmad-core/tasks/kb-mode-interaction.md ====================
 
-==================== START: .bmad-core/data/bmad-kb.md ====================
+==================== START: bmad-core/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
 # BMAD™ Knowledge Base
 
@@ -580,7 +580,7 @@ npx bmad-method install
 
 **Verify Installation**:
 
-- `.bmad-core/` folder created with all agents
+- `bmad-core/` folder created with all agents
 - IDE-specific integration files created
 - All agent commands/rules/modes available
 
@@ -1279,9 +1279,9 @@ Use the **expansion-creator** pack to build your own:
 - **Documentation**: Check `docs/` folder for project-specific context
 - **Community**: Discord and GitHub resources available for support
 - **Contributing**: See `CONTRIBUTING.md` for full guidelines
-==================== END: .bmad-core/data/bmad-kb.md ====================
+==================== END: bmad-core/data/bmad-kb.md ====================
 
-==================== START: .bmad-core/data/elicitation-methods.md ====================
+==================== START: bmad-core/data/elicitation-methods.md ====================
 <!-- Powered by BMAD™ Core -->
 # Elicitation Methods Data
 
@@ -1437,9 +1437,9 @@ Use the **expansion-creator** pack to build your own:
 - Acknowledge choice to finalize current work
 - Accept output as-is or move to next step
 - Prepare to continue without additional elicitation
-==================== END: .bmad-core/data/elicitation-methods.md ====================
+==================== END: bmad-core/data/elicitation-methods.md ====================
 
-==================== START: .bmad-core/utils/workflow-management.md ====================
+==================== START: bmad-core/utils/workflow-management.md ====================
 <!-- Powered by BMAD™ Core -->
 # Workflow Management
 
@@ -1510,4 +1510,4 @@ Handle conditional paths by asking clarifying questions when needed.
 ## Agent Integration
 
 Agents should be workflow-aware: know active workflow, their role, access artifacts, understand expected outputs.
-==================== END: .bmad-core/utils/workflow-management.md ====================
+==================== END: bmad-core/utils/workflow-management.md ====================

dist/agents/dev.txt

@@ -8,13 +8,13 @@ You are now operating as a specialized AI agent from the BMad-Method framework.
 
 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
 
-- `==================== START: .bmad-core/folder/filename.md ====================`
-- `==================== END: .bmad-core/folder/filename.md ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
+- `==================== END: bmad-core/folder/filename.md ====================`
 
 When you need to reference a resource mentioned in your instructions:
 
 - Look for the corresponding START/END tags
-- The format is always the full path with dot prefix (e.g., `.bmad-core/personas/analyst.md`, `.bmad-core/tasks/create-story.md`)
+- The format is always the full path with dot prefix (e.g., `bmad-core/personas/analyst.md`, `bmad-core/tasks/create-story.md`)
 - If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
 
 **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
@@ -29,8 +29,8 @@ dependencies:
 
 These references map directly to bundle sections:
 
-- `utils: template-format` → Look for `==================== START: .bmad-core/utils/template-format.md ====================`
-- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.md ====================`
+- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
+- `tasks: create-story` → Look for `==================== START: bmad-core/tasks/create-story.md ====================`
 
 3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
 
@@ -39,7 +39,7 @@ These references map directly to bundle sections:
 ---
 
 
-==================== START: .bmad-core/agents/dev.md ====================
+==================== START: bmad-core/agents/dev.md ====================
 # dev
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -90,9 +90,9 @@ dependencies:
     - execute-checklist.md
     - validate-next-story.md
 ```
-==================== END: .bmad-core/agents/dev.md ====================
+==================== END: bmad-core/agents/dev.md ====================
 
-==================== START: .bmad-core/tasks/apply-qa-fixes.md ====================
+==================== START: bmad-core/tasks/apply-qa-fixes.md ====================
 <!-- Powered by BMAD™ Core -->
 # apply-qa-fixes
 
@@ -242,9 +242,9 @@ Fix plan:
 - Tests validate behavior and close gaps
 - Strict adherence to allowed story update areas
 - Gate ownership remains with QA; Dev signals readiness via Status
-==================== END: .bmad-core/tasks/apply-qa-fixes.md ====================
+==================== END: bmad-core/tasks/apply-qa-fixes.md ====================
 
-==================== START: .bmad-core/tasks/execute-checklist.md ====================
+==================== START: bmad-core/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
@@ -252,7 +252,7 @@ This task provides instructions for validating documentation against checklists.
 
 ## 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.
+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
 
@@ -260,7 +260,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
    - If user or the task being run provides a checklist name:
      - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
      - If multiple matches found, ask user to clarify
-     - Load the appropriate checklist from .bmad-core/checklists/
+     - 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
@@ -332,9 +332,9 @@ The LLM will:
 - Execute the complete checklist validation
 - Present a final report with pass/fail rates and key findings
 - Offer to provide detailed analysis of any section, especially those with warnings or failures
-==================== END: .bmad-core/tasks/execute-checklist.md ====================
+==================== END: bmad-core/tasks/execute-checklist.md ====================
 
-==================== START: .bmad-core/tasks/validate-next-story.md ====================
+==================== START: bmad-core/tasks/validate-next-story.md ====================
 <!-- Powered by BMAD™ Core -->
 # Validate Next Story Task
 
@@ -346,7 +346,7 @@ To comprehensively validate a story draft before implementation begins, ensuring
 
 ### 0. Load Core Configuration and Inputs
 
-- Load `.bmad-core/core-config.yaml`
+- Load `bmad-core/core-config.yaml`
 - If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story validation."
 - Extract key configurations: `devStoryLocation`, `prd.*`, `architecture.*`
 - Identify and load the following inputs:
@@ -470,9 +470,9 @@ Provide a structured validation report including:
 - **NO-GO**: Story requires fixes before implementation
 - **Implementation Readiness Score**: 1-10 scale
 - **Confidence Level**: High/Medium/Low for successful implementation
-==================== END: .bmad-core/tasks/validate-next-story.md ====================
+==================== END: bmad-core/tasks/validate-next-story.md ====================
 
-==================== START: .bmad-core/checklists/story-dod-checklist.md ====================
+==================== START: bmad-core/checklists/story-dod-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Story Definition of Done (DoD) Checklist
 
@@ -568,4 +568,4 @@ After completing the checklist:
 Be honest - it's better to flag issues now than have them discovered later.]]
 
 - [ ] I, the Developer Agent, confirm that all applicable items above have been addressed.
-==================== END: .bmad-core/checklists/story-dod-checklist.md ====================
+==================== END: bmad-core/checklists/story-dod-checklist.md ====================

dist/agents/pm.txt

@@ -8,13 +8,13 @@ You are now operating as a specialized AI agent from the BMad-Method framework.
 
 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
 
-- `==================== START: .bmad-core/folder/filename.md ====================`
-- `==================== END: .bmad-core/folder/filename.md ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
+- `==================== END: bmad-core/folder/filename.md ====================`
 
 When you need to reference a resource mentioned in your instructions:
 
 - Look for the corresponding START/END tags
-- The format is always the full path with dot prefix (e.g., `.bmad-core/personas/analyst.md`, `.bmad-core/tasks/create-story.md`)
+- The format is always the full path with dot prefix (e.g., `bmad-core/personas/analyst.md`, `bmad-core/tasks/create-story.md`)
 - If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
 
 **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
@@ -29,8 +29,8 @@ dependencies:
 
 These references map directly to bundle sections:
 
-- `utils: template-format` → Look for `==================== START: .bmad-core/utils/template-format.md ====================`
-- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.md ====================`
+- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
+- `tasks: create-story` → Look for `==================== START: bmad-core/tasks/create-story.md ====================`
 
 3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
 
@@ -39,7 +39,7 @@ These references map directly to bundle sections:
 ---
 
 
-==================== START: .bmad-core/agents/pm.md ====================
+==================== START: bmad-core/agents/pm.md ====================
 # pm
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -101,9 +101,9 @@ dependencies:
     - brownfield-prd-tmpl.yaml
     - prd-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/pm.md ====================
+==================== END: bmad-core/agents/pm.md ====================
 
-==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
+==================== START: bmad-core/tasks/brownfield-create-epic.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Brownfield Epic Task
 
@@ -265,9 +265,9 @@ The epic creation is successful when:
 - If the scope grows beyond 3 stories, consider the full brownfield PRD process
 - Always prioritize existing system integrity over new functionality
 - When in doubt about scope or complexity, escalate to full brownfield planning
-==================== END: .bmad-core/tasks/brownfield-create-epic.md ====================
+==================== END: bmad-core/tasks/brownfield-create-epic.md ====================
 
-==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
+==================== START: bmad-core/tasks/brownfield-create-story.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Brownfield Story Task
 
@@ -416,15 +416,15 @@ The story creation is successful when:
 - Always prioritize existing system integrity
 - When in doubt about integration complexity, use brownfield-create-epic instead
 - Stories should take no more than 4 hours of focused development work
-==================== END: .bmad-core/tasks/brownfield-create-story.md ====================
+==================== END: bmad-core/tasks/brownfield-create-story.md ====================
 
-==================== START: .bmad-core/tasks/correct-course.md ====================
+==================== START: bmad-core/tasks/correct-course.md ====================
 <!-- Powered by BMAD™ Core -->
 # Correct Course Task
 
 ## Purpose
 
-- Guide a structured response to a change trigger using the `.bmad-core/checklists/change-checklist`.
+- Guide a structured response to a change trigger using the `bmad-core/checklists/change-checklist`.
 - Analyze the impacts of the change on epics, project artifacts, and the MVP, guided by the checklist's structure.
 - Explore potential solutions (e.g., adjust scope, rollback elements, re-scope features) as prompted by the checklist.
 - Draft specific, actionable proposed updates to any affected project artifacts (e.g., epics, user stories, PRD sections, architecture document sections) based on the analysis.
@@ -438,7 +438,7 @@ The story creation is successful when:
 - **Acknowledge Task & Inputs:**
   - Confirm with the user that the "Correct Course Task" (Change Navigation & Integration) is being initiated.
   - Verify the change trigger and ensure you have the user's initial explanation of the issue and its perceived impact.
-  - Confirm access to all relevant project artifacts (e.g., PRD, Epics/Stories, Architecture Documents, UI/UX Specifications) and, critically, the `.bmad-core/checklists/change-checklist`.
+  - Confirm access to all relevant project artifacts (e.g., PRD, Epics/Stories, Architecture Documents, UI/UX Specifications) and, critically, the `bmad-core/checklists/change-checklist`.
 - **Establish Interaction Mode:**
   - Ask the user their preferred interaction mode for this task:
     - **"Incrementally (Default & Recommended):** Shall we work through the change-checklist section by section, discussing findings and collaboratively drafting proposed changes for each relevant part before moving to the next? This allows for detailed, step-by-step refinement."
@@ -490,9 +490,9 @@ The story creation is successful when:
   - A summary of the change-checklist analysis (issue, impact, rationale for the chosen path).
   - Specific, clearly drafted proposed edits for all affected project artifacts.
 - **Implicit:** An annotated change-checklist (or the record of its completion) reflecting the discussions, findings, and decisions made during the process.
-==================== END: .bmad-core/tasks/correct-course.md ====================
+==================== END: bmad-core/tasks/correct-course.md ====================
 
-==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
+==================== START: bmad-core/tasks/create-deep-research-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Deep Research Prompt Task
 
@@ -772,9 +772,9 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
 - Balance comprehensiveness with focus
 - Document assumptions and limitations clearly
 - Plan for iterative refinement based on initial findings
-==================== END: .bmad-core/tasks/create-deep-research-prompt.md ====================
+==================== END: bmad-core/tasks/create-deep-research-prompt.md ====================
 
-==================== START: .bmad-core/tasks/create-doc.md ====================
+==================== START: bmad-core/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Document from Template (YAML Driven)
 
@@ -793,7 +793,7 @@ When this task is invoked:
 
 ## Critical: Template Discovery
 
-If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.
+If a YAML Template has not been provided, list all templates from bmad-core/templates or ask the user to provide another.
 
 ## CRITICAL: Mandatory Elicitation Format
 
@@ -877,9 +877,9 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 - Select options 2-9 from data/elicitation-methods only
 - Provide detailed rationale explaining decisions
 - End with "Select 1-9 or just type your question/feedback:"
-==================== END: .bmad-core/tasks/create-doc.md ====================
+==================== END: bmad-core/tasks/create-doc.md ====================
 
-==================== START: .bmad-core/tasks/execute-checklist.md ====================
+==================== START: bmad-core/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
@@ -887,7 +887,7 @@ This task provides instructions for validating documentation against checklists.
 
 ## 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.
+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
 
@@ -895,7 +895,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
    - If user or the task being run provides a checklist name:
      - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
      - If multiple matches found, ask user to clarify
-     - Load the appropriate checklist from .bmad-core/checklists/
+     - 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
@@ -967,9 +967,9 @@ The LLM will:
 - Execute the complete checklist validation
 - Present a final report with pass/fail rates and key findings
 - Offer to provide detailed analysis of any section, especially those with warnings or failures
-==================== END: .bmad-core/tasks/execute-checklist.md ====================
+==================== END: bmad-core/tasks/execute-checklist.md ====================
 
-==================== START: .bmad-core/tasks/shard-doc.md ====================
+==================== START: bmad-core/tasks/shard-doc.md ====================
 <!-- Powered by BMAD™ Core -->
 # Document Sharding Task
 
@@ -981,20 +981,20 @@ The LLM will:
 
 ## Primary Method: Automatic with markdown-tree
 
-[[LLM: First, check if markdownExploder is set to true in .bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
+[[LLM: First, check if markdownExploder is set to true in bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
 
 If the command succeeds, inform the user that the document has been sharded successfully and STOP - do not proceed further.
 
 If the command fails (especially with an error indicating the command is not found or not available), inform the user: "The markdownExploder setting is enabled but the md-tree command is not available. Please either:
 
 1. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
-2. Or set markdownExploder to false in .bmad-core/core-config.yaml
+2. Or set markdownExploder to false in bmad-core/core-config.yaml
 
 **IMPORTANT: STOP HERE - do not proceed with manual sharding until one of the above actions is taken.**"
 
 If markdownExploder is set to false, inform the user: "The markdownExploder setting is currently false. For better performance and reliability, you should:
 
-1. Set markdownExploder to true in .bmad-core/core-config.yaml
+1. Set markdownExploder to true in bmad-core/core-config.yaml
 2. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
 
 I will now proceed with the manual sharding process."
@@ -1156,9 +1156,9 @@ Document sharded successfully:
 - Preserve ALL formatting, including whitespace where significant
 - Handle edge cases like sections with code blocks containing ## symbols
 - Ensure the sharding is reversible (could reconstruct the original from shards)
-==================== END: .bmad-core/tasks/shard-doc.md ====================
+==================== END: bmad-core/tasks/shard-doc.md ====================
 
-==================== START: .bmad-core/templates/brownfield-prd-tmpl.yaml ====================
+==================== START: bmad-core/templates/brownfield-prd-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: brownfield-prd-template-v2
@@ -1440,9 +1440,9 @@ sections:
               - template: "IV1: {{existing_functionality_verification}}"
               - template: "IV2: {{integration_point_verification}}"
               - template: "IV3: {{performance_impact_verification}}"
-==================== END: .bmad-core/templates/brownfield-prd-tmpl.yaml ====================
+==================== END: bmad-core/templates/brownfield-prd-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/prd-tmpl.yaml ====================
+==================== START: bmad-core/templates/prd-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: prd-template-v2
@@ -1545,7 +1545,7 @@ sections:
     instruction: |
       Gather technical decisions that will guide the Architect. Steps:
 
-      1. Check if .bmad-core/data/technical-preferences.yaml or an attached technical-preferences file exists - use it to pre-populate choices
+      1. Check if bmad-core/data/technical-preferences.yaml or an attached technical-preferences file exists - use it to pre-populate choices
       2. Ask user about: languages, frameworks, starter templates, libraries, APIs, deployment targets
       3. For unknowns, offer guidance based on project goals and MVP scope
       4. Document ALL technical choices with rationale (why this choice fits the project)
@@ -1646,9 +1646,9 @@ sections:
       - id: architect-prompt
         title: Architect Prompt
         instruction: This section will contain the prompt for the Architect, keep it short and to the point to initiate create architecture mode using this document as input.
-==================== END: .bmad-core/templates/prd-tmpl.yaml ====================
+==================== END: bmad-core/templates/prd-tmpl.yaml ====================
 
-==================== START: .bmad-core/checklists/change-checklist.md ====================
+==================== START: bmad-core/checklists/change-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Change Navigation Checklist
 
@@ -1832,9 +1832,9 @@ Keep it action-oriented and forward-looking.]]
 - [ ] **Confirm Next Steps:** Reiterate the handoff plan and the next actions to be taken by specific agents.
 
 ---
-==================== END: .bmad-core/checklists/change-checklist.md ====================
+==================== END: bmad-core/checklists/change-checklist.md ====================
 
-==================== START: .bmad-core/checklists/pm-checklist.md ====================
+==================== START: bmad-core/checklists/pm-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Product Manager (PM) Requirements Checklist
 
@@ -2206,11 +2206,11 @@ After presenting the report, ask if the user wants:
 
 - **READY FOR ARCHITECT**: The PRD and epics are comprehensive, properly structured, and ready for architectural design.
 - **NEEDS REFINEMENT**: The requirements documentation requires additional work to address the identified deficiencies.
-==================== END: .bmad-core/checklists/pm-checklist.md ====================
+==================== END: bmad-core/checklists/pm-checklist.md ====================
 
-==================== START: .bmad-core/data/technical-preferences.md ====================
+==================== START: bmad-core/data/technical-preferences.md ====================
 <!-- Powered by BMAD™ Core -->
 # User-Defined Preferred Patterns and Preferences
 
 None Listed
-==================== END: .bmad-core/data/technical-preferences.md ====================
+==================== END: bmad-core/data/technical-preferences.md ====================

dist/agents/po.txt

@@ -8,13 +8,13 @@ You are now operating as a specialized AI agent from the BMad-Method framework.
 
 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
 
-- `==================== START: .bmad-core/folder/filename.md ====================`
-- `==================== END: .bmad-core/folder/filename.md ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
+- `==================== END: bmad-core/folder/filename.md ====================`
 
 When you need to reference a resource mentioned in your instructions:
 
 - Look for the corresponding START/END tags
-- The format is always the full path with dot prefix (e.g., `.bmad-core/personas/analyst.md`, `.bmad-core/tasks/create-story.md`)
+- The format is always the full path with dot prefix (e.g., `bmad-core/personas/analyst.md`, `bmad-core/tasks/create-story.md`)
 - If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
 
 **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
@@ -29,8 +29,8 @@ dependencies:
 
 These references map directly to bundle sections:
 
-- `utils: template-format` → Look for `==================== START: .bmad-core/utils/template-format.md ====================`
-- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.md ====================`
+- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
+- `tasks: create-story` → Look for `==================== START: bmad-core/tasks/create-story.md ====================`
 
 3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
 
@@ -39,7 +39,7 @@ These references map directly to bundle sections:
 ---
 
 
-==================== START: .bmad-core/agents/po.md ====================
+==================== START: bmad-core/agents/po.md ====================
 # po
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -96,15 +96,15 @@ dependencies:
   templates:
     - story-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/po.md ====================
+==================== END: bmad-core/agents/po.md ====================
 
-==================== START: .bmad-core/tasks/correct-course.md ====================
+==================== START: bmad-core/tasks/correct-course.md ====================
 <!-- Powered by BMAD™ Core -->
 # Correct Course Task
 
 ## Purpose
 
-- Guide a structured response to a change trigger using the `.bmad-core/checklists/change-checklist`.
+- Guide a structured response to a change trigger using the `bmad-core/checklists/change-checklist`.
 - Analyze the impacts of the change on epics, project artifacts, and the MVP, guided by the checklist's structure.
 - Explore potential solutions (e.g., adjust scope, rollback elements, re-scope features) as prompted by the checklist.
 - Draft specific, actionable proposed updates to any affected project artifacts (e.g., epics, user stories, PRD sections, architecture document sections) based on the analysis.
@@ -118,7 +118,7 @@ dependencies:
 - **Acknowledge Task & Inputs:**
   - Confirm with the user that the "Correct Course Task" (Change Navigation & Integration) is being initiated.
   - Verify the change trigger and ensure you have the user's initial explanation of the issue and its perceived impact.
-  - Confirm access to all relevant project artifacts (e.g., PRD, Epics/Stories, Architecture Documents, UI/UX Specifications) and, critically, the `.bmad-core/checklists/change-checklist`.
+  - Confirm access to all relevant project artifacts (e.g., PRD, Epics/Stories, Architecture Documents, UI/UX Specifications) and, critically, the `bmad-core/checklists/change-checklist`.
 - **Establish Interaction Mode:**
   - Ask the user their preferred interaction mode for this task:
     - **"Incrementally (Default & Recommended):** Shall we work through the change-checklist section by section, discussing findings and collaboratively drafting proposed changes for each relevant part before moving to the next? This allows for detailed, step-by-step refinement."
@@ -170,9 +170,9 @@ dependencies:
   - A summary of the change-checklist analysis (issue, impact, rationale for the chosen path).
   - Specific, clearly drafted proposed edits for all affected project artifacts.
 - **Implicit:** An annotated change-checklist (or the record of its completion) reflecting the discussions, findings, and decisions made during the process.
-==================== END: .bmad-core/tasks/correct-course.md ====================
+==================== END: bmad-core/tasks/correct-course.md ====================
 
-==================== START: .bmad-core/tasks/execute-checklist.md ====================
+==================== START: bmad-core/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
@@ -180,7 +180,7 @@ This task provides instructions for validating documentation against checklists.
 
 ## 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.
+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
 
@@ -188,7 +188,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
    - If user or the task being run provides a checklist name:
      - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
      - If multiple matches found, ask user to clarify
-     - Load the appropriate checklist from .bmad-core/checklists/
+     - 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
@@ -260,9 +260,9 @@ The LLM will:
 - Execute the complete checklist validation
 - Present a final report with pass/fail rates and key findings
 - Offer to provide detailed analysis of any section, especially those with warnings or failures
-==================== END: .bmad-core/tasks/execute-checklist.md ====================
+==================== END: bmad-core/tasks/execute-checklist.md ====================
 
-==================== START: .bmad-core/tasks/shard-doc.md ====================
+==================== START: bmad-core/tasks/shard-doc.md ====================
 <!-- Powered by BMAD™ Core -->
 # Document Sharding Task
 
@@ -274,20 +274,20 @@ The LLM will:
 
 ## Primary Method: Automatic with markdown-tree
 
-[[LLM: First, check if markdownExploder is set to true in .bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
+[[LLM: First, check if markdownExploder is set to true in bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
 
 If the command succeeds, inform the user that the document has been sharded successfully and STOP - do not proceed further.
 
 If the command fails (especially with an error indicating the command is not found or not available), inform the user: "The markdownExploder setting is enabled but the md-tree command is not available. Please either:
 
 1. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
-2. Or set markdownExploder to false in .bmad-core/core-config.yaml
+2. Or set markdownExploder to false in bmad-core/core-config.yaml
 
 **IMPORTANT: STOP HERE - do not proceed with manual sharding until one of the above actions is taken.**"
 
 If markdownExploder is set to false, inform the user: "The markdownExploder setting is currently false. For better performance and reliability, you should:
 
-1. Set markdownExploder to true in .bmad-core/core-config.yaml
+1. Set markdownExploder to true in bmad-core/core-config.yaml
 2. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
 
 I will now proceed with the manual sharding process."
@@ -449,9 +449,9 @@ Document sharded successfully:
 - Preserve ALL formatting, including whitespace where significant
 - Handle edge cases like sections with code blocks containing ## symbols
 - Ensure the sharding is reversible (could reconstruct the original from shards)
-==================== END: .bmad-core/tasks/shard-doc.md ====================
+==================== END: bmad-core/tasks/shard-doc.md ====================
 
-==================== START: .bmad-core/tasks/validate-next-story.md ====================
+==================== START: bmad-core/tasks/validate-next-story.md ====================
 <!-- Powered by BMAD™ Core -->
 # Validate Next Story Task
 
@@ -463,7 +463,7 @@ To comprehensively validate a story draft before implementation begins, ensuring
 
 ### 0. Load Core Configuration and Inputs
 
-- Load `.bmad-core/core-config.yaml`
+- Load `bmad-core/core-config.yaml`
 - If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story validation."
 - Extract key configurations: `devStoryLocation`, `prd.*`, `architecture.*`
 - Identify and load the following inputs:
@@ -587,9 +587,9 @@ Provide a structured validation report including:
 - **NO-GO**: Story requires fixes before implementation
 - **Implementation Readiness Score**: 1-10 scale
 - **Confidence Level**: High/Medium/Low for successful implementation
-==================== END: .bmad-core/tasks/validate-next-story.md ====================
+==================== END: bmad-core/tasks/validate-next-story.md ====================
 
-==================== START: .bmad-core/templates/story-tmpl.yaml ====================
+==================== START: bmad-core/templates/story-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: story-template-v2
@@ -728,9 +728,9 @@ sections:
     instruction: Results from QA Agent QA review of the completed story implementation
     owner: qa-agent
     editors: [qa-agent]
-==================== END: .bmad-core/templates/story-tmpl.yaml ====================
+==================== END: bmad-core/templates/story-tmpl.yaml ====================
 
-==================== START: .bmad-core/checklists/change-checklist.md ====================
+==================== START: bmad-core/checklists/change-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Change Navigation Checklist
 
@@ -914,9 +914,9 @@ Keep it action-oriented and forward-looking.]]
 - [ ] **Confirm Next Steps:** Reiterate the handoff plan and the next actions to be taken by specific agents.
 
 ---
-==================== END: .bmad-core/checklists/change-checklist.md ====================
+==================== END: bmad-core/checklists/change-checklist.md ====================
 
-==================== START: .bmad-core/checklists/po-master-checklist.md ====================
+==================== START: bmad-core/checklists/po-master-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Product Owner (PO) Master Validation Checklist
 
@@ -1350,4 +1350,4 @@ After presenting the report, ask if the user wants:
 - **APPROVED**: The plan is comprehensive, properly sequenced, and ready for implementation.
 - **CONDITIONAL**: The plan requires specific adjustments before proceeding.
 - **REJECTED**: The plan requires significant revision to address critical deficiencies.
-==================== END: .bmad-core/checklists/po-master-checklist.md ====================
+==================== END: bmad-core/checklists/po-master-checklist.md ====================

dist/agents/qa.txt

@@ -8,13 +8,13 @@ You are now operating as a specialized AI agent from the BMad-Method framework.
 
 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
 
-- `==================== START: .bmad-core/folder/filename.md ====================`
-- `==================== END: .bmad-core/folder/filename.md ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
+- `==================== END: bmad-core/folder/filename.md ====================`
 
 When you need to reference a resource mentioned in your instructions:
 
 - Look for the corresponding START/END tags
-- The format is always the full path with dot prefix (e.g., `.bmad-core/personas/analyst.md`, `.bmad-core/tasks/create-story.md`)
+- The format is always the full path with dot prefix (e.g., `bmad-core/personas/analyst.md`, `bmad-core/tasks/create-story.md`)
 - If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
 
 **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
@@ -29,8 +29,8 @@ dependencies:
 
 These references map directly to bundle sections:
 
-- `utils: template-format` → Look for `==================== START: .bmad-core/utils/template-format.md ====================`
-- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.md ====================`
+- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
+- `tasks: create-story` → Look for `==================== START: bmad-core/tasks/create-story.md ====================`
 
 3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
 
@@ -39,7 +39,7 @@ These references map directly to bundle sections:
 ---
 
 
-==================== START: .bmad-core/agents/qa.md ====================
+==================== START: bmad-core/agents/qa.md ====================
 # qa
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -108,9 +108,9 @@ dependencies:
     - qa-gate-tmpl.yaml
     - story-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/qa.md ====================
+==================== END: bmad-core/agents/qa.md ====================
 
-==================== START: .bmad-core/tasks/nfr-assess.md ====================
+==================== START: bmad-core/tasks/nfr-assess.md ====================
 <!-- Powered by BMAD™ Core -->
 # nfr-assess
 
@@ -455,9 +455,9 @@ performance_deep_dive:
 ```
 
 </details>
-==================== END: .bmad-core/tasks/nfr-assess.md ====================
+==================== END: bmad-core/tasks/nfr-assess.md ====================
 
-==================== START: .bmad-core/tasks/qa-gate.md ====================
+==================== START: bmad-core/tasks/qa-gate.md ====================
 <!-- Powered by BMAD™ Core -->
 # qa-gate
 
@@ -620,9 +620,9 @@ Gate: CONCERNS → qa.qaLocation/gates/{epic}.{story}-{slug}.yml
 - Always write to standard path
 - Always update story with gate reference
 - Clear, actionable findings
-==================== END: .bmad-core/tasks/qa-gate.md ====================
+==================== END: bmad-core/tasks/qa-gate.md ====================
 
-==================== START: .bmad-core/tasks/review-story.md ====================
+==================== START: bmad-core/tasks/review-story.md ====================
 <!-- Powered by BMAD™ Core -->
 # review-story
 
@@ -938,9 +938,9 @@ After review:
 3. Recommend status: "Ready for Done" or "Changes Required" (owner decides)
 4. If files were modified, list them in QA Results and ask Dev to update File List
 5. Always provide constructive feedback and actionable recommendations
-==================== END: .bmad-core/tasks/review-story.md ====================
+==================== END: bmad-core/tasks/review-story.md ====================
 
-==================== START: .bmad-core/tasks/risk-profile.md ====================
+==================== START: bmad-core/tasks/risk-profile.md ====================
 <!-- Powered by BMAD™ Core -->
 # risk-profile
 
@@ -1295,9 +1295,9 @@ Risk profile: qa.qaLocation/assessments/{epic}.{story}-risk-{YYYYMMDD}.md
 - Link risks to specific test requirements
 - Track residual risk after mitigation
 - Update risk profile as story evolves
-==================== END: .bmad-core/tasks/risk-profile.md ====================
+==================== END: bmad-core/tasks/risk-profile.md ====================
 
-==================== START: .bmad-core/tasks/test-design.md ====================
+==================== START: bmad-core/tasks/test-design.md ====================
 <!-- Powered by BMAD™ Core -->
 # test-design
 
@@ -1473,9 +1473,9 @@ Before finalizing, verify:
 - **Efficient coverage**: Test once at the right level
 - **Maintainability**: Consider long-term test maintenance
 - **Fast feedback**: Quick tests run first
-==================== END: .bmad-core/tasks/test-design.md ====================
+==================== END: bmad-core/tasks/test-design.md ====================
 
-==================== START: .bmad-core/tasks/trace-requirements.md ====================
+==================== START: bmad-core/tasks/trace-requirements.md ====================
 <!-- Powered by BMAD™ Core -->
 # trace-requirements
 
@@ -1741,9 +1741,9 @@ Trace matrix: qa.qaLocation/assessments/{epic}.{story}-trace-{YYYYMMDD}.md
 - Identify both presence and absence
 - Prioritize based on risk
 - Make recommendations actionable
-==================== END: .bmad-core/tasks/trace-requirements.md ====================
+==================== END: bmad-core/tasks/trace-requirements.md ====================
 
-==================== START: .bmad-core/templates/qa-gate-tmpl.yaml ====================
+==================== START: bmad-core/templates/qa-gate-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: qa-gate-template-v1
@@ -1847,9 +1847,9 @@ optional_fields_examples:
       future:  # Can be addressed later
         - action: "Consider caching for better performance"
           refs: ["services/data.service.ts"]
-==================== END: .bmad-core/templates/qa-gate-tmpl.yaml ====================
+==================== END: bmad-core/templates/qa-gate-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/story-tmpl.yaml ====================
+==================== START: bmad-core/templates/story-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: story-template-v2
@@ -1988,11 +1988,11 @@ sections:
     instruction: Results from QA Agent QA review of the completed story implementation
     owner: qa-agent
     editors: [qa-agent]
-==================== END: .bmad-core/templates/story-tmpl.yaml ====================
+==================== END: bmad-core/templates/story-tmpl.yaml ====================
 
-==================== START: .bmad-core/data/technical-preferences.md ====================
+==================== START: bmad-core/data/technical-preferences.md ====================
 <!-- Powered by BMAD™ Core -->
 # User-Defined Preferred Patterns and Preferences
 
 None Listed
-==================== END: .bmad-core/data/technical-preferences.md ====================
+==================== END: bmad-core/data/technical-preferences.md ====================

dist/agents/sm.txt

@@ -8,13 +8,13 @@ You are now operating as a specialized AI agent from the BMad-Method framework.
 
 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
 
-- `==================== START: .bmad-core/folder/filename.md ====================`
-- `==================== END: .bmad-core/folder/filename.md ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
+- `==================== END: bmad-core/folder/filename.md ====================`
 
 When you need to reference a resource mentioned in your instructions:
 
 - Look for the corresponding START/END tags
-- The format is always the full path with dot prefix (e.g., `.bmad-core/personas/analyst.md`, `.bmad-core/tasks/create-story.md`)
+- The format is always the full path with dot prefix (e.g., `bmad-core/personas/analyst.md`, `bmad-core/tasks/create-story.md`)
 - If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
 
 **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
@@ -29,8 +29,8 @@ dependencies:
 
 These references map directly to bundle sections:
 
-- `utils: template-format` → Look for `==================== START: .bmad-core/utils/template-format.md ====================`
-- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.md ====================`
+- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
+- `tasks: create-story` → Look for `==================== START: bmad-core/tasks/create-story.md ====================`
 
 3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
 
@@ -39,7 +39,7 @@ These references map directly to bundle sections:
 ---
 
 
-==================== START: .bmad-core/agents/sm.md ====================
+==================== START: bmad-core/agents/sm.md ====================
 # sm
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -82,15 +82,15 @@ dependencies:
   templates:
     - story-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/sm.md ====================
+==================== END: bmad-core/agents/sm.md ====================
 
-==================== START: .bmad-core/tasks/correct-course.md ====================
+==================== START: bmad-core/tasks/correct-course.md ====================
 <!-- Powered by BMAD™ Core -->
 # Correct Course Task
 
 ## Purpose
 
-- Guide a structured response to a change trigger using the `.bmad-core/checklists/change-checklist`.
+- Guide a structured response to a change trigger using the `bmad-core/checklists/change-checklist`.
 - Analyze the impacts of the change on epics, project artifacts, and the MVP, guided by the checklist's structure.
 - Explore potential solutions (e.g., adjust scope, rollback elements, re-scope features) as prompted by the checklist.
 - Draft specific, actionable proposed updates to any affected project artifacts (e.g., epics, user stories, PRD sections, architecture document sections) based on the analysis.
@@ -104,7 +104,7 @@ dependencies:
 - **Acknowledge Task & Inputs:**
   - Confirm with the user that the "Correct Course Task" (Change Navigation & Integration) is being initiated.
   - Verify the change trigger and ensure you have the user's initial explanation of the issue and its perceived impact.
-  - Confirm access to all relevant project artifacts (e.g., PRD, Epics/Stories, Architecture Documents, UI/UX Specifications) and, critically, the `.bmad-core/checklists/change-checklist`.
+  - Confirm access to all relevant project artifacts (e.g., PRD, Epics/Stories, Architecture Documents, UI/UX Specifications) and, critically, the `bmad-core/checklists/change-checklist`.
 - **Establish Interaction Mode:**
   - Ask the user their preferred interaction mode for this task:
     - **"Incrementally (Default & Recommended):** Shall we work through the change-checklist section by section, discussing findings and collaboratively drafting proposed changes for each relevant part before moving to the next? This allows for detailed, step-by-step refinement."
@@ -156,9 +156,9 @@ dependencies:
   - A summary of the change-checklist analysis (issue, impact, rationale for the chosen path).
   - Specific, clearly drafted proposed edits for all affected project artifacts.
 - **Implicit:** An annotated change-checklist (or the record of its completion) reflecting the discussions, findings, and decisions made during the process.
-==================== END: .bmad-core/tasks/correct-course.md ====================
+==================== END: bmad-core/tasks/correct-course.md ====================
 
-==================== START: .bmad-core/tasks/create-next-story.md ====================
+==================== START: bmad-core/tasks/create-next-story.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Next Story Task
 
@@ -170,7 +170,7 @@ To identify the next logical story based on project progress and epic definition
 
 ### 0. Load Core Configuration and Check Workflow
 
-- Load `.bmad-core/core-config.yaml` from the project root
+- Load `bmad-core/core-config.yaml` from the project root
 - If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story creation. You can either: 1) Copy it from GITHUB bmad-core/core-config.yaml and configure it for your project OR 2) Run the BMad installer against your project to upgrade and add the file automatically. Please add and configure core-config.yaml before proceeding."
 - Extract key configurations: `devStoryLocation`, `prd.*`, `architecture.*`, `workflow.*`
 
@@ -264,17 +264,17 @@ ALWAYS cite source documents: `[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" and save the story file
-- Execute `.bmad-core/tasks/execute-checklist` `.bmad-core/checklists/story-draft-checklist`
+- Execute `bmad-core/tasks/execute-checklist` `bmad-core/checklists/story-draft-checklist`
 - Provide summary to user including:
   - Story created: `{devStoryLocation}/{epicNum}.{storyNum}.story.md`
   - Status: Draft
   - Key technical components included from architecture docs
   - Any deviations or conflicts noted between epic and architecture
   - Checklist Results
-  - Next steps: For Complex stories, suggest the user carefully review the story draft and also optionally have the PO run the task `.bmad-core/tasks/validate-next-story`
-==================== END: .bmad-core/tasks/create-next-story.md ====================
+  - Next steps: For Complex stories, suggest the user carefully review the story draft and also optionally have the PO run the task `bmad-core/tasks/validate-next-story`
+==================== END: bmad-core/tasks/create-next-story.md ====================
 
-==================== START: .bmad-core/tasks/execute-checklist.md ====================
+==================== START: bmad-core/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
@@ -282,7 +282,7 @@ This task provides instructions for validating documentation against checklists.
 
 ## 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.
+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
 
@@ -290,7 +290,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
    - If user or the task being run provides a checklist name:
      - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
      - If multiple matches found, ask user to clarify
-     - Load the appropriate checklist from .bmad-core/checklists/
+     - 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
@@ -362,9 +362,9 @@ The LLM will:
 - Execute the complete checklist validation
 - Present a final report with pass/fail rates and key findings
 - Offer to provide detailed analysis of any section, especially those with warnings or failures
-==================== END: .bmad-core/tasks/execute-checklist.md ====================
+==================== END: bmad-core/tasks/execute-checklist.md ====================
 
-==================== START: .bmad-core/templates/story-tmpl.yaml ====================
+==================== START: bmad-core/templates/story-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: story-template-v2
@@ -503,9 +503,9 @@ sections:
     instruction: Results from QA Agent QA review of the completed story implementation
     owner: qa-agent
     editors: [qa-agent]
-==================== END: .bmad-core/templates/story-tmpl.yaml ====================
+==================== END: bmad-core/templates/story-tmpl.yaml ====================
 
-==================== START: .bmad-core/checklists/story-draft-checklist.md ====================
+==================== START: bmad-core/checklists/story-draft-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Story Draft Checklist
 
@@ -660,4 +660,4 @@ Be pragmatic - perfect documentation doesn't exist, but it must be enough to pro
 - READY: The story provides sufficient context for implementation
 - NEEDS REVISION: The story requires updates (see issues)
 - BLOCKED: External information required (specify what information)
-==================== END: .bmad-core/checklists/story-draft-checklist.md ====================
+==================== END: bmad-core/checklists/story-draft-checklist.md ====================

dist/agents/ux-expert.txt

@@ -8,13 +8,13 @@ You are now operating as a specialized AI agent from the BMad-Method framework.
 
 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
 
-- `==================== START: .bmad-core/folder/filename.md ====================`
-- `==================== END: .bmad-core/folder/filename.md ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
+- `==================== END: bmad-core/folder/filename.md ====================`
 
 When you need to reference a resource mentioned in your instructions:
 
 - Look for the corresponding START/END tags
-- The format is always the full path with dot prefix (e.g., `.bmad-core/personas/analyst.md`, `.bmad-core/tasks/create-story.md`)
+- The format is always the full path with dot prefix (e.g., `bmad-core/personas/analyst.md`, `bmad-core/tasks/create-story.md`)
 - If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
 
 **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
@@ -29,8 +29,8 @@ dependencies:
 
 These references map directly to bundle sections:
 
-- `utils: template-format` → Look for `==================== START: .bmad-core/utils/template-format.md ====================`
-- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.md ====================`
+- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
+- `tasks: create-story` → Look for `==================== START: bmad-core/tasks/create-story.md ====================`
 
 3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
 
@@ -39,7 +39,7 @@ These references map directly to bundle sections:
 ---
 
 
-==================== START: .bmad-core/agents/ux-expert.md ====================
+==================== START: bmad-core/agents/ux-expert.md ====================
 # ux-expert
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -86,9 +86,9 @@ dependencies:
   templates:
     - front-end-spec-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/ux-expert.md ====================
+==================== END: bmad-core/agents/ux-expert.md ====================
 
-==================== START: .bmad-core/tasks/create-doc.md ====================
+==================== START: bmad-core/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Document from Template (YAML Driven)
 
@@ -107,7 +107,7 @@ When this task is invoked:
 
 ## Critical: Template Discovery
 
-If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.
+If a YAML Template has not been provided, list all templates from bmad-core/templates or ask the user to provide another.
 
 ## CRITICAL: Mandatory Elicitation Format
 
@@ -191,9 +191,9 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 - Select options 2-9 from data/elicitation-methods only
 - Provide detailed rationale explaining decisions
 - End with "Select 1-9 or just type your question/feedback:"
-==================== END: .bmad-core/tasks/create-doc.md ====================
+==================== END: bmad-core/tasks/create-doc.md ====================
 
-==================== START: .bmad-core/tasks/execute-checklist.md ====================
+==================== START: bmad-core/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
@@ -201,7 +201,7 @@ This task provides instructions for validating documentation against checklists.
 
 ## 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.
+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
 
@@ -209,7 +209,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
    - If user or the task being run provides a checklist name:
      - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
      - If multiple matches found, ask user to clarify
-     - Load the appropriate checklist from .bmad-core/checklists/
+     - 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
@@ -281,9 +281,9 @@ The LLM will:
 - Execute the complete checklist validation
 - Present a final report with pass/fail rates and key findings
 - Offer to provide detailed analysis of any section, especially those with warnings or failures
-==================== END: .bmad-core/tasks/execute-checklist.md ====================
+==================== END: bmad-core/tasks/execute-checklist.md ====================
 
-==================== START: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
+==================== START: bmad-core/tasks/generate-ai-frontend-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create AI Frontend Prompt Task
 
@@ -336,9 +336,9 @@ You will now synthesize the inputs and the above principles into a final, compre
    - Output the complete, generated prompt in a clear, copy-pasteable format (e.g., a large code block).
    - Explain the structure of the prompt and why certain information was included, referencing the principles above.
    - <important_note>Conclude by reminding the user that all AI-generated code will require careful human review, testing, and refinement to be considered production-ready.</important_note>
-==================== END: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
+==================== END: bmad-core/tasks/generate-ai-frontend-prompt.md ====================
 
-==================== START: .bmad-core/templates/front-end-spec-tmpl.yaml ====================
+==================== START: bmad-core/templates/front-end-spec-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: frontend-spec-template-v2
@@ -689,11 +689,11 @@ sections:
   - id: checklist-results
     title: Checklist Results
     instruction: If a UI/UX checklist exists, run it against this document and report results here.
-==================== END: .bmad-core/templates/front-end-spec-tmpl.yaml ====================
+==================== END: bmad-core/templates/front-end-spec-tmpl.yaml ====================
 
-==================== START: .bmad-core/data/technical-preferences.md ====================
+==================== START: bmad-core/data/technical-preferences.md ====================
 <!-- Powered by BMAD™ Core -->
 # User-Defined Preferred Patterns and Preferences
 
 None Listed
-==================== END: .bmad-core/data/technical-preferences.md ====================
+==================== END: bmad-core/data/technical-preferences.md ====================

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

@@ -113,7 +113,7 @@ When this task is invoked:
 
 ## Critical: Template Discovery
 
-If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.
+If a YAML Template has not been provided, list all templates from bmad-core/templates or ask the user to provide another.
 
 ## CRITICAL: Mandatory Elicitation Format
 

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

@@ -1121,7 +1121,7 @@ When this task is invoked:
 
 ## Critical: Template Discovery
 
-If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.
+If a YAML Template has not been provided, list all templates from bmad-core/templates or ask the user to provide another.
 
 ## CRITICAL: Mandatory Elicitation Format
 

dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-architect.txt

@@ -121,7 +121,7 @@ When this task is invoked:
 
 ## Critical: Template Discovery
 
-If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.
+If a YAML Template has not been provided, list all templates from bmad-core/templates or ask the user to provide another.
 
 ## CRITICAL: Mandatory Elicitation Format
 
@@ -3382,7 +3382,7 @@ npx bmad-method install
 
 **Verify Game Development Installation**:
 
-- `.bmad-core/` folder created with all core agents
+- `bmad-core/` folder created with all core agents
 - `.bmad-2d-unity-game-dev/` folder with game development agents
 - IDE-specific integration files created
 - Game development agents available with `/bmad2du` prefix (per config.yaml)

dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-designer.txt

@@ -118,7 +118,7 @@ When this task is invoked:
 
 ## Critical: Template Discovery
 
-If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.
+If a YAML Template has not been provided, list all templates from bmad-core/templates or ask the user to provide another.
 
 ## CRITICAL: Mandatory Elicitation Format
 
@@ -3069,7 +3069,7 @@ npx bmad-method install
 
 **Verify Game Development Installation**:
 
-- `.bmad-core/` folder created with all core agents
+- `bmad-core/` folder created with all core agents
 - `.bmad-2d-unity-game-dev/` folder with game development agents
 - IDE-specific integration files created
 - Game development agents available with `/bmad2du` prefix (per config.yaml)

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

@@ -198,7 +198,7 @@ To comprehensively validate a story draft before implementation begins, ensuring
 
 ### 0. Load Core Configuration and Inputs
 
-- Load `.bmad-core/core-config.yaml`
+- Load `bmad-core/core-config.yaml`
 - If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story validation."
 - Extract key configurations: `devStoryLocation`, `prd.*`, `architecture.*`
 - Identify and load the following inputs:

dist/expansion-packs/bmad-2d-unity-game-dev/teams/unity-2d-game-team.txt

@@ -610,7 +610,7 @@ npx bmad-method install
 
 **Verify Game Development Installation**:
 
-- `.bmad-core/` folder created with all core agents
+- `bmad-core/` folder created with all core agents
 - `.bmad-2d-unity-game-dev/` folder with game development agents
 - IDE-specific integration files created
 - Game development agents available with `/bmad2du` prefix (per config.yaml)
@@ -1704,7 +1704,7 @@ When this task is invoked:
 
 ## Critical: Template Discovery
 
-If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.
+If a YAML Template has not been provided, list all templates from bmad-core/templates or ask the user to provide another.
 
 ## CRITICAL: Mandatory Elicitation Format
 
@@ -7903,7 +7903,7 @@ To comprehensively validate a story draft before implementation begins, ensuring
 
 ### 0. Load Core Configuration and Inputs
 
-- Load `.bmad-core/core-config.yaml`
+- Load `bmad-core/core-config.yaml`
 - If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story validation."
 - Extract key configurations: `devStoryLocation`, `prd.*`, `architecture.*`
 - Identify and load the following inputs:
@@ -14188,7 +14188,7 @@ npx bmad-method install
 
 **Verify Game Development Installation**:
 
-- `.bmad-core/` folder created with all core agents
+- `bmad-core/` folder created with all core agents
 - `.bmad-2d-unity-game-dev/` folder with game development agents
 - IDE-specific integration files created
 - Game development agents available with `/bmad2du` prefix (per config.yaml)

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

@@ -119,7 +119,7 @@ When this task is invoked:
 
 ## Critical: Template Discovery
 
-If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.
+If a YAML Template has not been provided, list all templates from bmad-core/templates or ask the user to provide another.
 
 ## CRITICAL: Mandatory Elicitation Format
 

dist/teams/team-all.txt

@@ -8,13 +8,13 @@ You are now operating as a specialized AI agent from the BMad-Method framework.
 
 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
 
-- `==================== START: .bmad-core/folder/filename.md ====================`
-- `==================== END: .bmad-core/folder/filename.md ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
+- `==================== END: bmad-core/folder/filename.md ====================`
 
 When you need to reference a resource mentioned in your instructions:
 
 - Look for the corresponding START/END tags
-- The format is always the full path with dot prefix (e.g., `.bmad-core/personas/analyst.md`, `.bmad-core/tasks/create-story.md`)
+- The format is always the full path with dot prefix (e.g., `bmad-core/personas/analyst.md`, `bmad-core/tasks/create-story.md`)
 - If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
 
 **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
@@ -29,8 +29,8 @@ dependencies:
 
 These references map directly to bundle sections:
 
-- `utils: template-format` → Look for `==================== START: .bmad-core/utils/template-format.md ====================`
-- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.md ====================`
+- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
+- `tasks: create-story` → Look for `==================== START: bmad-core/tasks/create-story.md ====================`
 
 3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
 
@@ -39,7 +39,7 @@ These references map directly to bundle sections:
 ---
 
 
-==================== START: .bmad-core/agent-teams/team-all.yaml ====================
+==================== START: bmad-core/agent-teams/team-all.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 bundle:
   name: Team All
@@ -55,9 +55,9 @@ workflows:
   - greenfield-fullstack.yaml
   - greenfield-service.yaml
   - greenfield-ui.yaml
-==================== END: .bmad-core/agent-teams/team-all.yaml ====================
+==================== END: bmad-core/agent-teams/team-all.yaml ====================
 
-==================== START: .bmad-core/agents/bmad-orchestrator.md ====================
+==================== START: bmad-core/agents/bmad-orchestrator.md ====================
 # bmad-orchestrator
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -182,9 +182,9 @@ dependencies:
   utils:
     - workflow-management.md
 ```
-==================== END: .bmad-core/agents/bmad-orchestrator.md ====================
+==================== END: bmad-core/agents/bmad-orchestrator.md ====================
 
-==================== START: .bmad-core/agents/analyst.md ====================
+==================== START: bmad-core/agents/analyst.md ====================
 # analyst
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -246,9 +246,9 @@ dependencies:
     - market-research-tmpl.yaml
     - project-brief-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/analyst.md ====================
+==================== END: bmad-core/agents/analyst.md ====================
 
-==================== START: .bmad-core/agents/architect.md ====================
+==================== START: bmad-core/agents/architect.md ====================
 # architect
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -311,9 +311,9 @@ dependencies:
     - front-end-architecture-tmpl.yaml
     - fullstack-architecture-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/architect.md ====================
+==================== END: bmad-core/agents/architect.md ====================
 
-==================== START: .bmad-core/agents/dev.md ====================
+==================== START: bmad-core/agents/dev.md ====================
 # dev
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -364,9 +364,9 @@ dependencies:
     - execute-checklist.md
     - validate-next-story.md
 ```
-==================== END: .bmad-core/agents/dev.md ====================
+==================== END: bmad-core/agents/dev.md ====================
 
-==================== START: .bmad-core/agents/pm.md ====================
+==================== START: bmad-core/agents/pm.md ====================
 # pm
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -428,9 +428,9 @@ dependencies:
     - brownfield-prd-tmpl.yaml
     - prd-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/pm.md ====================
+==================== END: bmad-core/agents/pm.md ====================
 
-==================== START: .bmad-core/agents/po.md ====================
+==================== START: bmad-core/agents/po.md ====================
 # po
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -487,9 +487,9 @@ dependencies:
   templates:
     - story-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/po.md ====================
+==================== END: bmad-core/agents/po.md ====================
 
-==================== START: .bmad-core/agents/qa.md ====================
+==================== START: bmad-core/agents/qa.md ====================
 # qa
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -558,9 +558,9 @@ dependencies:
     - qa-gate-tmpl.yaml
     - story-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/qa.md ====================
+==================== END: bmad-core/agents/qa.md ====================
 
-==================== START: .bmad-core/agents/sm.md ====================
+==================== START: bmad-core/agents/sm.md ====================
 # sm
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -603,9 +603,9 @@ dependencies:
   templates:
     - story-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/sm.md ====================
+==================== END: bmad-core/agents/sm.md ====================
 
-==================== START: .bmad-core/agents/ux-expert.md ====================
+==================== START: bmad-core/agents/ux-expert.md ====================
 # ux-expert
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -652,9 +652,9 @@ dependencies:
   templates:
     - front-end-spec-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/ux-expert.md ====================
+==================== END: bmad-core/agents/ux-expert.md ====================
 
-==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
+==================== START: bmad-core/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
 # Advanced Elicitation Task
 
@@ -773,9 +773,9 @@ Choose a number (0-8) or 9 to proceed:
 - **Stay Relevant**: Tie all elicitation back to the specific content being analyzed
 - **Identify Personas**: For multi-persona methods, clearly identify which viewpoint is speaking
 - **Maintain Flow**: Keep the process moving efficiently
-==================== END: .bmad-core/tasks/advanced-elicitation.md ====================
+==================== END: bmad-core/tasks/advanced-elicitation.md ====================
 
-==================== START: .bmad-core/tasks/create-doc.md ====================
+==================== START: bmad-core/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Document from Template (YAML Driven)
 
@@ -794,7 +794,7 @@ When this task is invoked:
 
 ## Critical: Template Discovery
 
-If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.
+If a YAML Template has not been provided, list all templates from bmad-core/templates or ask the user to provide another.
 
 ## CRITICAL: Mandatory Elicitation Format
 
@@ -878,9 +878,9 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 - Select options 2-9 from data/elicitation-methods only
 - Provide detailed rationale explaining decisions
 - End with "Select 1-9 or just type your question/feedback:"
-==================== END: .bmad-core/tasks/create-doc.md ====================
+==================== END: bmad-core/tasks/create-doc.md ====================
 
-==================== START: .bmad-core/tasks/kb-mode-interaction.md ====================
+==================== START: bmad-core/tasks/kb-mode-interaction.md ====================
 <!-- Powered by BMAD™ Core -->
 # KB Mode Interaction Task
 
@@ -957,9 +957,9 @@ Or ask me about anything else related to BMad-Method!
 **User**: Tell me about workflows
 
 **Assistant**: [Provides focused information about workflows from the KB, then offers to explore specific workflow types or related topics]
-==================== END: .bmad-core/tasks/kb-mode-interaction.md ====================
+==================== END: bmad-core/tasks/kb-mode-interaction.md ====================
 
-==================== START: .bmad-core/data/bmad-kb.md ====================
+==================== START: bmad-core/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
 # BMAD™ Knowledge Base
 
@@ -1068,7 +1068,7 @@ npx bmad-method install
 
 **Verify Installation**:
 
-- `.bmad-core/` folder created with all agents
+- `bmad-core/` folder created with all agents
 - IDE-specific integration files created
 - All agent commands/rules/modes available
 
@@ -1767,9 +1767,9 @@ Use the **expansion-creator** pack to build your own:
 - **Documentation**: Check `docs/` folder for project-specific context
 - **Community**: Discord and GitHub resources available for support
 - **Contributing**: See `CONTRIBUTING.md` for full guidelines
-==================== END: .bmad-core/data/bmad-kb.md ====================
+==================== END: bmad-core/data/bmad-kb.md ====================
 
-==================== START: .bmad-core/data/elicitation-methods.md ====================
+==================== START: bmad-core/data/elicitation-methods.md ====================
 <!-- Powered by BMAD™ Core -->
 # Elicitation Methods Data
 
@@ -1925,9 +1925,9 @@ Use the **expansion-creator** pack to build your own:
 - Acknowledge choice to finalize current work
 - Accept output as-is or move to next step
 - Prepare to continue without additional elicitation
-==================== END: .bmad-core/data/elicitation-methods.md ====================
+==================== END: bmad-core/data/elicitation-methods.md ====================
 
-==================== START: .bmad-core/utils/workflow-management.md ====================
+==================== START: bmad-core/utils/workflow-management.md ====================
 <!-- Powered by BMAD™ Core -->
 # Workflow Management
 
@@ -1998,9 +1998,9 @@ Handle conditional paths by asking clarifying questions when needed.
 ## Agent Integration
 
 Agents should be workflow-aware: know active workflow, their role, access artifacts, understand expected outputs.
-==================== END: .bmad-core/utils/workflow-management.md ====================
+==================== END: bmad-core/utils/workflow-management.md ====================
 
-==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
+==================== START: bmad-core/tasks/create-deep-research-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Deep Research Prompt Task
 
@@ -2280,9 +2280,9 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
 - Balance comprehensiveness with focus
 - Document assumptions and limitations clearly
 - Plan for iterative refinement based on initial findings
-==================== END: .bmad-core/tasks/create-deep-research-prompt.md ====================
+==================== END: bmad-core/tasks/create-deep-research-prompt.md ====================
 
-==================== START: .bmad-core/tasks/document-project.md ====================
+==================== START: bmad-core/tasks/document-project.md ====================
 <!-- Powered by BMAD™ Core -->
 # Document an Existing Project
 
@@ -2627,13 +2627,13 @@ Apply the advanced elicitation task after major sections to refine based on user
 - Documents technical debt, workarounds, and constraints honestly
 - For brownfield projects with PRD: Provides clear enhancement impact analysis
 - The goal is PRACTICAL documentation for AI agents doing real work
-==================== END: .bmad-core/tasks/document-project.md ====================
+==================== END: bmad-core/tasks/document-project.md ====================
 
-==================== START: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
+==================== START: bmad-core/tasks/facilitate-brainstorming-session.md ====================
 <!-- Powered by BMAD™ Core -->
 ---
 docOutputLocation: docs/brainstorming-session-results.md
-template: '.bmad-core/templates/brainstorming-output-tmpl.yaml'
+template: 'bmad-core/templates/brainstorming-output-tmpl.yaml'
 ---
 
 # Facilitate Brainstorming Session Task
@@ -2767,9 +2767,9 @@ Generate structured document with these sections:
 - Always ask before switching techniques: "Ready to try a different approach?"
 - Offer options: "Should we explore this idea deeper or generate more alternatives?"
 - Respect their process and timing
-==================== END: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
+==================== END: bmad-core/tasks/facilitate-brainstorming-session.md ====================
 
-==================== START: .bmad-core/templates/brainstorming-output-tmpl.yaml ====================
+==================== START: bmad-core/templates/brainstorming-output-tmpl.yaml ====================
 template:
   id: brainstorming-output-template-v2
   name: Brainstorming Session Results
@@ -2926,9 +2926,9 @@ sections:
       ---
 
       *Session facilitated using the BMAD-METHOD™ brainstorming framework*
-==================== END: .bmad-core/templates/brainstorming-output-tmpl.yaml ====================
+==================== END: bmad-core/templates/brainstorming-output-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/competitor-analysis-tmpl.yaml ====================
+==================== START: bmad-core/templates/competitor-analysis-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: competitor-analysis-template-v2
@@ -3236,9 +3236,9 @@ sections:
           - Weekly: {{weekly_items}}
           - Monthly: {{monthly_items}}
           - Quarterly: {{quarterly_analysis}}
-==================== END: .bmad-core/templates/competitor-analysis-tmpl.yaml ====================
+==================== END: bmad-core/templates/competitor-analysis-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/market-research-tmpl.yaml ====================
+==================== START: bmad-core/templates/market-research-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: market-research-template-v2
@@ -3492,9 +3492,9 @@ sections:
       - id: additional-analysis
         title: C. Additional Analysis
         instruction: Any supplementary analysis not included in main body
-==================== END: .bmad-core/templates/market-research-tmpl.yaml ====================
+==================== END: bmad-core/templates/market-research-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/project-brief-tmpl.yaml ====================
+==================== START: bmad-core/templates/project-brief-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: project-brief-template-v2
@@ -3717,9 +3717,9 @@ sections:
         title: PM Handoff
         content: |
           This Project Brief provides the full context for {{project_name}}. Please start in 'PRD Generation Mode', review the brief thoroughly to work with the user to create the PRD section by section as the template indicates, asking for any necessary clarification or suggesting improvements.
-==================== END: .bmad-core/templates/project-brief-tmpl.yaml ====================
+==================== END: bmad-core/templates/project-brief-tmpl.yaml ====================
 
-==================== START: .bmad-core/data/brainstorming-techniques.md ====================
+==================== START: bmad-core/data/brainstorming-techniques.md ====================
 <!-- Powered by BMAD™ Core -->
 # Brainstorming Techniques Data
 
@@ -3757,9 +3757,9 @@ sections:
 18. **Resource Constraints**: "What if you had only $10 and 1 hour?"
 19. **Metaphor Mapping**: Use extended metaphors to explore solutions
 20. **Question Storming**: Generate questions instead of answers first
-==================== END: .bmad-core/data/brainstorming-techniques.md ====================
+==================== END: bmad-core/data/brainstorming-techniques.md ====================
 
-==================== START: .bmad-core/tasks/execute-checklist.md ====================
+==================== START: bmad-core/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
@@ -3767,7 +3767,7 @@ This task provides instructions for validating documentation against checklists.
 
 ## 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.
+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
 
@@ -3775,7 +3775,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
    - If user or the task being run provides a checklist name:
      - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
      - If multiple matches found, ask user to clarify
-     - Load the appropriate checklist from .bmad-core/checklists/
+     - 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
@@ -3847,9 +3847,9 @@ The LLM will:
 - Execute the complete checklist validation
 - Present a final report with pass/fail rates and key findings
 - Offer to provide detailed analysis of any section, especially those with warnings or failures
-==================== END: .bmad-core/tasks/execute-checklist.md ====================
+==================== END: bmad-core/tasks/execute-checklist.md ====================
 
-==================== START: .bmad-core/templates/architecture-tmpl.yaml ====================
+==================== START: bmad-core/templates/architecture-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: architecture-template-v2
@@ -3980,7 +3980,7 @@ sections:
     instruction: |
       This is the DEFINITIVE technology selection section. Work with the user to make specific choices:
 
-      1. Review PRD technical assumptions and any preferences from .bmad-core/data/technical-preferences.yaml or an attached technical-preferences
+      1. Review PRD technical assumptions and any preferences from bmad-core/data/technical-preferences.yaml or an attached technical-preferences
       2. For each category, present 2-3 viable options with pros/cons
       3. Make a clear recommendation based on project needs
       4. Get explicit user approval for each selection
@@ -4501,9 +4501,9 @@ sections:
           - Key UI requirements from PRD
           - Any frontend-specific decisions made here
           - Request for detailed frontend architecture
-==================== END: .bmad-core/templates/architecture-tmpl.yaml ====================
+==================== END: bmad-core/templates/architecture-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
+==================== START: bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: brownfield-architecture-template-v2
@@ -4981,9 +4981,9 @@ sections:
           - Key technical decisions based on real project constraints
           - Existing system compatibility requirements with specific verification steps
           - Clear sequencing of implementation to minimize risk to existing functionality
-==================== END: .bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
+==================== END: bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/front-end-architecture-tmpl.yaml ====================
+==================== START: bmad-core/templates/front-end-architecture-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: frontend-architecture-template-v2
@@ -5203,9 +5203,9 @@ sections:
           - Key import patterns
           - File naming conventions
           - Project-specific patterns and utilities
-==================== END: .bmad-core/templates/front-end-architecture-tmpl.yaml ====================
+==================== END: bmad-core/templates/front-end-architecture-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
+==================== START: bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: fullstack-architecture-template-v2
@@ -6030,9 +6030,9 @@ sections:
   - id: checklist-results
     title: Checklist Results Report
     instruction: Before running the checklist, offer to output the full architecture document. Once user confirms, execute the architect-checklist and populate results here.
-==================== END: .bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
+==================== END: bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
 
-==================== START: .bmad-core/checklists/architect-checklist.md ====================
+==================== START: bmad-core/checklists/architect-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Architect Solution Validation Checklist
 
@@ -6472,16 +6472,16 @@ Now that you've completed the checklist, generate a comprehensive validation rep
    - Component design clarity
 
 After presenting the report, ask the user if they would like detailed analysis of any specific section, especially those with warnings or failures.]]
-==================== END: .bmad-core/checklists/architect-checklist.md ====================
+==================== END: bmad-core/checklists/architect-checklist.md ====================
 
-==================== START: .bmad-core/data/technical-preferences.md ====================
+==================== START: bmad-core/data/technical-preferences.md ====================
 <!-- Powered by BMAD™ Core -->
 # User-Defined Preferred Patterns and Preferences
 
 None Listed
-==================== END: .bmad-core/data/technical-preferences.md ====================
+==================== END: bmad-core/data/technical-preferences.md ====================
 
-==================== START: .bmad-core/tasks/apply-qa-fixes.md ====================
+==================== START: bmad-core/tasks/apply-qa-fixes.md ====================
 <!-- Powered by BMAD™ Core -->
 # apply-qa-fixes
 
@@ -6631,9 +6631,9 @@ Fix plan:
 - Tests validate behavior and close gaps
 - Strict adherence to allowed story update areas
 - Gate ownership remains with QA; Dev signals readiness via Status
-==================== END: .bmad-core/tasks/apply-qa-fixes.md ====================
+==================== END: bmad-core/tasks/apply-qa-fixes.md ====================
 
-==================== START: .bmad-core/tasks/validate-next-story.md ====================
+==================== START: bmad-core/tasks/validate-next-story.md ====================
 <!-- Powered by BMAD™ Core -->
 # Validate Next Story Task
 
@@ -6645,7 +6645,7 @@ To comprehensively validate a story draft before implementation begins, ensuring
 
 ### 0. Load Core Configuration and Inputs
 
-- Load `.bmad-core/core-config.yaml`
+- Load `bmad-core/core-config.yaml`
 - If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story validation."
 - Extract key configurations: `devStoryLocation`, `prd.*`, `architecture.*`
 - Identify and load the following inputs:
@@ -6769,9 +6769,9 @@ Provide a structured validation report including:
 - **NO-GO**: Story requires fixes before implementation
 - **Implementation Readiness Score**: 1-10 scale
 - **Confidence Level**: High/Medium/Low for successful implementation
-==================== END: .bmad-core/tasks/validate-next-story.md ====================
+==================== END: bmad-core/tasks/validate-next-story.md ====================
 
-==================== START: .bmad-core/checklists/story-dod-checklist.md ====================
+==================== START: bmad-core/checklists/story-dod-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Story Definition of Done (DoD) Checklist
 
@@ -6867,9 +6867,9 @@ After completing the checklist:
 Be honest - it's better to flag issues now than have them discovered later.]]
 
 - [ ] I, the Developer Agent, confirm that all applicable items above have been addressed.
-==================== END: .bmad-core/checklists/story-dod-checklist.md ====================
+==================== END: bmad-core/checklists/story-dod-checklist.md ====================
 
-==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
+==================== START: bmad-core/tasks/brownfield-create-epic.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Brownfield Epic Task
 
@@ -7031,9 +7031,9 @@ The epic creation is successful when:
 - If the scope grows beyond 3 stories, consider the full brownfield PRD process
 - Always prioritize existing system integrity over new functionality
 - When in doubt about scope or complexity, escalate to full brownfield planning
-==================== END: .bmad-core/tasks/brownfield-create-epic.md ====================
+==================== END: bmad-core/tasks/brownfield-create-epic.md ====================
 
-==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
+==================== START: bmad-core/tasks/brownfield-create-story.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Brownfield Story Task
 
@@ -7182,15 +7182,15 @@ The story creation is successful when:
 - Always prioritize existing system integrity
 - When in doubt about integration complexity, use brownfield-create-epic instead
 - Stories should take no more than 4 hours of focused development work
-==================== END: .bmad-core/tasks/brownfield-create-story.md ====================
+==================== END: bmad-core/tasks/brownfield-create-story.md ====================
 
-==================== START: .bmad-core/tasks/correct-course.md ====================
+==================== START: bmad-core/tasks/correct-course.md ====================
 <!-- Powered by BMAD™ Core -->
 # Correct Course Task
 
 ## Purpose
 
-- Guide a structured response to a change trigger using the `.bmad-core/checklists/change-checklist`.
+- Guide a structured response to a change trigger using the `bmad-core/checklists/change-checklist`.
 - Analyze the impacts of the change on epics, project artifacts, and the MVP, guided by the checklist's structure.
 - Explore potential solutions (e.g., adjust scope, rollback elements, re-scope features) as prompted by the checklist.
 - Draft specific, actionable proposed updates to any affected project artifacts (e.g., epics, user stories, PRD sections, architecture document sections) based on the analysis.
@@ -7204,7 +7204,7 @@ The story creation is successful when:
 - **Acknowledge Task & Inputs:**
   - Confirm with the user that the "Correct Course Task" (Change Navigation & Integration) is being initiated.
   - Verify the change trigger and ensure you have the user's initial explanation of the issue and its perceived impact.
-  - Confirm access to all relevant project artifacts (e.g., PRD, Epics/Stories, Architecture Documents, UI/UX Specifications) and, critically, the `.bmad-core/checklists/change-checklist`.
+  - Confirm access to all relevant project artifacts (e.g., PRD, Epics/Stories, Architecture Documents, UI/UX Specifications) and, critically, the `bmad-core/checklists/change-checklist`.
 - **Establish Interaction Mode:**
   - Ask the user their preferred interaction mode for this task:
     - **"Incrementally (Default & Recommended):** Shall we work through the change-checklist section by section, discussing findings and collaboratively drafting proposed changes for each relevant part before moving to the next? This allows for detailed, step-by-step refinement."
@@ -7256,9 +7256,9 @@ The story creation is successful when:
   - A summary of the change-checklist analysis (issue, impact, rationale for the chosen path).
   - Specific, clearly drafted proposed edits for all affected project artifacts.
 - **Implicit:** An annotated change-checklist (or the record of its completion) reflecting the discussions, findings, and decisions made during the process.
-==================== END: .bmad-core/tasks/correct-course.md ====================
+==================== END: bmad-core/tasks/correct-course.md ====================
 
-==================== START: .bmad-core/tasks/shard-doc.md ====================
+==================== START: bmad-core/tasks/shard-doc.md ====================
 <!-- Powered by BMAD™ Core -->
 # Document Sharding Task
 
@@ -7270,20 +7270,20 @@ The story creation is successful when:
 
 ## Primary Method: Automatic with markdown-tree
 
-[[LLM: First, check if markdownExploder is set to true in .bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
+[[LLM: First, check if markdownExploder is set to true in bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
 
 If the command succeeds, inform the user that the document has been sharded successfully and STOP - do not proceed further.
 
 If the command fails (especially with an error indicating the command is not found or not available), inform the user: "The markdownExploder setting is enabled but the md-tree command is not available. Please either:
 
 1. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
-2. Or set markdownExploder to false in .bmad-core/core-config.yaml
+2. Or set markdownExploder to false in bmad-core/core-config.yaml
 
 **IMPORTANT: STOP HERE - do not proceed with manual sharding until one of the above actions is taken.**"
 
 If markdownExploder is set to false, inform the user: "The markdownExploder setting is currently false. For better performance and reliability, you should:
 
-1. Set markdownExploder to true in .bmad-core/core-config.yaml
+1. Set markdownExploder to true in bmad-core/core-config.yaml
 2. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
 
 I will now proceed with the manual sharding process."
@@ -7445,9 +7445,9 @@ Document sharded successfully:
 - Preserve ALL formatting, including whitespace where significant
 - Handle edge cases like sections with code blocks containing ## symbols
 - Ensure the sharding is reversible (could reconstruct the original from shards)
-==================== END: .bmad-core/tasks/shard-doc.md ====================
+==================== END: bmad-core/tasks/shard-doc.md ====================
 
-==================== START: .bmad-core/templates/brownfield-prd-tmpl.yaml ====================
+==================== START: bmad-core/templates/brownfield-prd-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: brownfield-prd-template-v2
@@ -7729,9 +7729,9 @@ sections:
               - template: "IV1: {{existing_functionality_verification}}"
               - template: "IV2: {{integration_point_verification}}"
               - template: "IV3: {{performance_impact_verification}}"
-==================== END: .bmad-core/templates/brownfield-prd-tmpl.yaml ====================
+==================== END: bmad-core/templates/brownfield-prd-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/prd-tmpl.yaml ====================
+==================== START: bmad-core/templates/prd-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: prd-template-v2
@@ -7834,7 +7834,7 @@ sections:
     instruction: |
       Gather technical decisions that will guide the Architect. Steps:
 
-      1. Check if .bmad-core/data/technical-preferences.yaml or an attached technical-preferences file exists - use it to pre-populate choices
+      1. Check if bmad-core/data/technical-preferences.yaml or an attached technical-preferences file exists - use it to pre-populate choices
       2. Ask user about: languages, frameworks, starter templates, libraries, APIs, deployment targets
       3. For unknowns, offer guidance based on project goals and MVP scope
       4. Document ALL technical choices with rationale (why this choice fits the project)
@@ -7935,9 +7935,9 @@ sections:
       - id: architect-prompt
         title: Architect Prompt
         instruction: This section will contain the prompt for the Architect, keep it short and to the point to initiate create architecture mode using this document as input.
-==================== END: .bmad-core/templates/prd-tmpl.yaml ====================
+==================== END: bmad-core/templates/prd-tmpl.yaml ====================
 
-==================== START: .bmad-core/checklists/change-checklist.md ====================
+==================== START: bmad-core/checklists/change-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Change Navigation Checklist
 
@@ -8121,9 +8121,9 @@ Keep it action-oriented and forward-looking.]]
 - [ ] **Confirm Next Steps:** Reiterate the handoff plan and the next actions to be taken by specific agents.
 
 ---
-==================== END: .bmad-core/checklists/change-checklist.md ====================
+==================== END: bmad-core/checklists/change-checklist.md ====================
 
-==================== START: .bmad-core/checklists/pm-checklist.md ====================
+==================== START: bmad-core/checklists/pm-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Product Manager (PM) Requirements Checklist
 
@@ -8495,9 +8495,9 @@ After presenting the report, ask if the user wants:
 
 - **READY FOR ARCHITECT**: The PRD and epics are comprehensive, properly structured, and ready for architectural design.
 - **NEEDS REFINEMENT**: The requirements documentation requires additional work to address the identified deficiencies.
-==================== END: .bmad-core/checklists/pm-checklist.md ====================
+==================== END: bmad-core/checklists/pm-checklist.md ====================
 
-==================== START: .bmad-core/templates/story-tmpl.yaml ====================
+==================== START: bmad-core/templates/story-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: story-template-v2
@@ -8636,9 +8636,9 @@ sections:
     instruction: Results from QA Agent QA review of the completed story implementation
     owner: qa-agent
     editors: [qa-agent]
-==================== END: .bmad-core/templates/story-tmpl.yaml ====================
+==================== END: bmad-core/templates/story-tmpl.yaml ====================
 
-==================== START: .bmad-core/checklists/po-master-checklist.md ====================
+==================== START: bmad-core/checklists/po-master-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Product Owner (PO) Master Validation Checklist
 
@@ -9072,9 +9072,9 @@ After presenting the report, ask if the user wants:
 - **APPROVED**: The plan is comprehensive, properly sequenced, and ready for implementation.
 - **CONDITIONAL**: The plan requires specific adjustments before proceeding.
 - **REJECTED**: The plan requires significant revision to address critical deficiencies.
-==================== END: .bmad-core/checklists/po-master-checklist.md ====================
+==================== END: bmad-core/checklists/po-master-checklist.md ====================
 
-==================== START: .bmad-core/tasks/nfr-assess.md ====================
+==================== START: bmad-core/tasks/nfr-assess.md ====================
 <!-- Powered by BMAD™ Core -->
 # nfr-assess
 
@@ -9419,9 +9419,9 @@ performance_deep_dive:
 ```
 
 </details>
-==================== END: .bmad-core/tasks/nfr-assess.md ====================
+==================== END: bmad-core/tasks/nfr-assess.md ====================
 
-==================== START: .bmad-core/tasks/qa-gate.md ====================
+==================== START: bmad-core/tasks/qa-gate.md ====================
 <!-- Powered by BMAD™ Core -->
 # qa-gate
 
@@ -9584,9 +9584,9 @@ Gate: CONCERNS → qa.qaLocation/gates/{epic}.{story}-{slug}.yml
 - Always write to standard path
 - Always update story with gate reference
 - Clear, actionable findings
-==================== END: .bmad-core/tasks/qa-gate.md ====================
+==================== END: bmad-core/tasks/qa-gate.md ====================
 
-==================== START: .bmad-core/tasks/review-story.md ====================
+==================== START: bmad-core/tasks/review-story.md ====================
 <!-- Powered by BMAD™ Core -->
 # review-story
 
@@ -9902,9 +9902,9 @@ After review:
 3. Recommend status: "Ready for Done" or "Changes Required" (owner decides)
 4. If files were modified, list them in QA Results and ask Dev to update File List
 5. Always provide constructive feedback and actionable recommendations
-==================== END: .bmad-core/tasks/review-story.md ====================
+==================== END: bmad-core/tasks/review-story.md ====================
 
-==================== START: .bmad-core/tasks/risk-profile.md ====================
+==================== START: bmad-core/tasks/risk-profile.md ====================
 <!-- Powered by BMAD™ Core -->
 # risk-profile
 
@@ -10259,9 +10259,9 @@ Risk profile: qa.qaLocation/assessments/{epic}.{story}-risk-{YYYYMMDD}.md
 - Link risks to specific test requirements
 - Track residual risk after mitigation
 - Update risk profile as story evolves
-==================== END: .bmad-core/tasks/risk-profile.md ====================
+==================== END: bmad-core/tasks/risk-profile.md ====================
 
-==================== START: .bmad-core/tasks/test-design.md ====================
+==================== START: bmad-core/tasks/test-design.md ====================
 <!-- Powered by BMAD™ Core -->
 # test-design
 
@@ -10437,9 +10437,9 @@ Before finalizing, verify:
 - **Efficient coverage**: Test once at the right level
 - **Maintainability**: Consider long-term test maintenance
 - **Fast feedback**: Quick tests run first
-==================== END: .bmad-core/tasks/test-design.md ====================
+==================== END: bmad-core/tasks/test-design.md ====================
 
-==================== START: .bmad-core/tasks/trace-requirements.md ====================
+==================== START: bmad-core/tasks/trace-requirements.md ====================
 <!-- Powered by BMAD™ Core -->
 # trace-requirements
 
@@ -10705,9 +10705,9 @@ Trace matrix: qa.qaLocation/assessments/{epic}.{story}-trace-{YYYYMMDD}.md
 - Identify both presence and absence
 - Prioritize based on risk
 - Make recommendations actionable
-==================== END: .bmad-core/tasks/trace-requirements.md ====================
+==================== END: bmad-core/tasks/trace-requirements.md ====================
 
-==================== START: .bmad-core/templates/qa-gate-tmpl.yaml ====================
+==================== START: bmad-core/templates/qa-gate-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: qa-gate-template-v1
@@ -10811,9 +10811,9 @@ optional_fields_examples:
       future:  # Can be addressed later
         - action: "Consider caching for better performance"
           refs: ["services/data.service.ts"]
-==================== END: .bmad-core/templates/qa-gate-tmpl.yaml ====================
+==================== END: bmad-core/templates/qa-gate-tmpl.yaml ====================
 
-==================== START: .bmad-core/tasks/create-next-story.md ====================
+==================== START: bmad-core/tasks/create-next-story.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Next Story Task
 
@@ -10825,7 +10825,7 @@ To identify the next logical story based on project progress and epic definition
 
 ### 0. Load Core Configuration and Check Workflow
 
-- Load `.bmad-core/core-config.yaml` from the project root
+- Load `bmad-core/core-config.yaml` from the project root
 - If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story creation. You can either: 1) Copy it from GITHUB bmad-core/core-config.yaml and configure it for your project OR 2) Run the BMad installer against your project to upgrade and add the file automatically. Please add and configure core-config.yaml before proceeding."
 - Extract key configurations: `devStoryLocation`, `prd.*`, `architecture.*`, `workflow.*`
 
@@ -10919,17 +10919,17 @@ ALWAYS cite source documents: `[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" and save the story file
-- Execute `.bmad-core/tasks/execute-checklist` `.bmad-core/checklists/story-draft-checklist`
+- Execute `bmad-core/tasks/execute-checklist` `bmad-core/checklists/story-draft-checklist`
 - Provide summary to user including:
   - Story created: `{devStoryLocation}/{epicNum}.{storyNum}.story.md`
   - Status: Draft
   - Key technical components included from architecture docs
   - Any deviations or conflicts noted between epic and architecture
   - Checklist Results
-  - Next steps: For Complex stories, suggest the user carefully review the story draft and also optionally have the PO run the task `.bmad-core/tasks/validate-next-story`
-==================== END: .bmad-core/tasks/create-next-story.md ====================
+  - Next steps: For Complex stories, suggest the user carefully review the story draft and also optionally have the PO run the task `bmad-core/tasks/validate-next-story`
+==================== END: bmad-core/tasks/create-next-story.md ====================
 
-==================== START: .bmad-core/checklists/story-draft-checklist.md ====================
+==================== START: bmad-core/checklists/story-draft-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Story Draft Checklist
 
@@ -11084,9 +11084,9 @@ Be pragmatic - perfect documentation doesn't exist, but it must be enough to pro
 - READY: The story provides sufficient context for implementation
 - NEEDS REVISION: The story requires updates (see issues)
 - BLOCKED: External information required (specify what information)
-==================== END: .bmad-core/checklists/story-draft-checklist.md ====================
+==================== END: bmad-core/checklists/story-draft-checklist.md ====================
 
-==================== START: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
+==================== START: bmad-core/tasks/generate-ai-frontend-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create AI Frontend Prompt Task
 
@@ -11139,9 +11139,9 @@ You will now synthesize the inputs and the above principles into a final, compre
    - Output the complete, generated prompt in a clear, copy-pasteable format (e.g., a large code block).
    - Explain the structure of the prompt and why certain information was included, referencing the principles above.
    - <important_note>Conclude by reminding the user that all AI-generated code will require careful human review, testing, and refinement to be considered production-ready.</important_note>
-==================== END: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
+==================== END: bmad-core/tasks/generate-ai-frontend-prompt.md ====================
 
-==================== START: .bmad-core/templates/front-end-spec-tmpl.yaml ====================
+==================== START: bmad-core/templates/front-end-spec-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: frontend-spec-template-v2
@@ -11492,9 +11492,9 @@ sections:
   - id: checklist-results
     title: Checklist Results
     instruction: If a UI/UX checklist exists, run it against this document and report results here.
-==================== END: .bmad-core/templates/front-end-spec-tmpl.yaml ====================
+==================== END: bmad-core/templates/front-end-spec-tmpl.yaml ====================
 
-==================== START: .bmad-core/workflows/brownfield-fullstack.yaml ====================
+==================== START: bmad-core/workflows/brownfield-fullstack.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 workflow:
   id: brownfield-fullstack
@@ -11680,7 +11680,7 @@ workflow:
         All stories implemented and reviewed!
         Project development phase complete.
 
-        Reference: .bmad-core/data/bmad-kb.md#IDE Development Workflow
+        Reference: bmad-core/data/bmad-kb.md#IDE Development Workflow
 
   flow_diagram: |
     ```mermaid
@@ -11793,9 +11793,9 @@ workflow:
       {{if missing_context}}: May need to gather additional context from user during story creation.
 
     complete: "All planning artifacts validated and development can begin. Stories will be created based on available documentation format."
-==================== END: .bmad-core/workflows/brownfield-fullstack.yaml ====================
+==================== END: bmad-core/workflows/brownfield-fullstack.yaml ====================
 
-==================== START: .bmad-core/workflows/brownfield-service.yaml ====================
+==================== START: bmad-core/workflows/brownfield-service.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 workflow:
   id: brownfield-service
@@ -11927,7 +11927,7 @@ workflow:
         All stories implemented and reviewed!
         Project development phase complete.
 
-        Reference: .bmad-core/data/bmad-kb.md#IDE Development Workflow
+        Reference: bmad-core/data/bmad-kb.md#IDE Development Workflow
 
   flow_diagram: |
     ```mermaid
@@ -11984,9 +11984,9 @@ workflow:
     architect_to_po: "Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for service integration safety."
     po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
     complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
-==================== END: .bmad-core/workflows/brownfield-service.yaml ====================
+==================== END: bmad-core/workflows/brownfield-service.yaml ====================
 
-==================== START: .bmad-core/workflows/brownfield-ui.yaml ====================
+==================== START: bmad-core/workflows/brownfield-ui.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 workflow:
   id: brownfield-ui
@@ -12125,7 +12125,7 @@ workflow:
         All stories implemented and reviewed!
         Project development phase complete.
 
-        Reference: .bmad-core/data/bmad-kb.md#IDE Development Workflow
+        Reference: bmad-core/data/bmad-kb.md#IDE Development Workflow
 
   flow_diagram: |
     ```mermaid
@@ -12185,9 +12185,9 @@ workflow:
     architect_to_po: "Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for UI integration safety."
     po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
     complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
-==================== END: .bmad-core/workflows/brownfield-ui.yaml ====================
+==================== END: bmad-core/workflows/brownfield-ui.yaml ====================
 
-==================== START: .bmad-core/workflows/greenfield-fullstack.yaml ====================
+==================== START: bmad-core/workflows/greenfield-fullstack.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 workflow:
   id: greenfield-fullstack
@@ -12351,7 +12351,7 @@ workflow:
         All stories implemented and reviewed!
         Project development phase complete.
 
-        Reference: .bmad-core/data/bmad-kb.md#IDE Development Workflow
+        Reference: bmad-core/data/bmad-kb.md#IDE Development Workflow
 
   flow_diagram: |
     ```mermaid
@@ -12429,9 +12429,9 @@ workflow:
     updated_to_po: "All documents ready in docs/ folder. Please validate all artifacts for consistency."
     po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
     complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
-==================== END: .bmad-core/workflows/greenfield-fullstack.yaml ====================
+==================== END: bmad-core/workflows/greenfield-fullstack.yaml ====================
 
-==================== START: .bmad-core/workflows/greenfield-service.yaml ====================
+==================== START: bmad-core/workflows/greenfield-service.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 workflow:
   id: greenfield-service
@@ -12571,7 +12571,7 @@ workflow:
         All stories implemented and reviewed!
         Service development phase complete.
 
-        Reference: .bmad-core/data/bmad-kb.md#IDE Development Workflow
+        Reference: bmad-core/data/bmad-kb.md#IDE Development Workflow
 
   flow_diagram: |
     ```mermaid
@@ -12639,9 +12639,9 @@ workflow:
     updated_to_po: "All documents ready in docs/ folder. Please validate all artifacts for consistency."
     po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
     complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
-==================== END: .bmad-core/workflows/greenfield-service.yaml ====================
+==================== END: bmad-core/workflows/greenfield-service.yaml ====================
 
-==================== START: .bmad-core/workflows/greenfield-ui.yaml ====================
+==================== START: bmad-core/workflows/greenfield-ui.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 workflow:
   id: greenfield-ui
@@ -12800,7 +12800,7 @@ workflow:
         All stories implemented and reviewed!
         Project development phase complete.
 
-        Reference: .bmad-core/data/bmad-kb.md#IDE Development Workflow
+        Reference: bmad-core/data/bmad-kb.md#IDE Development Workflow
 
   flow_diagram: |
     ```mermaid
@@ -12878,4 +12878,4 @@ workflow:
     updated_to_po: "All documents ready in docs/ folder. Please validate all artifacts for consistency."
     po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
     complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
-==================== END: .bmad-core/workflows/greenfield-ui.yaml ====================
+==================== END: bmad-core/workflows/greenfield-ui.yaml ====================

dist/teams/team-fullstack.txt

@@ -8,13 +8,13 @@ You are now operating as a specialized AI agent from the BMad-Method framework.
 
 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
 
-- `==================== START: .bmad-core/folder/filename.md ====================`
-- `==================== END: .bmad-core/folder/filename.md ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
+- `==================== END: bmad-core/folder/filename.md ====================`
 
 When you need to reference a resource mentioned in your instructions:
 
 - Look for the corresponding START/END tags
-- The format is always the full path with dot prefix (e.g., `.bmad-core/personas/analyst.md`, `.bmad-core/tasks/create-story.md`)
+- The format is always the full path with dot prefix (e.g., `bmad-core/personas/analyst.md`, `bmad-core/tasks/create-story.md`)
 - If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
 
 **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
@@ -29,8 +29,8 @@ dependencies:
 
 These references map directly to bundle sections:
 
-- `utils: template-format` → Look for `==================== START: .bmad-core/utils/template-format.md ====================`
-- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.md ====================`
+- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
+- `tasks: create-story` → Look for `==================== START: bmad-core/tasks/create-story.md ====================`
 
 3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
 
@@ -39,7 +39,7 @@ These references map directly to bundle sections:
 ---
 
 
-==================== START: .bmad-core/agent-teams/team-fullstack.yaml ====================
+==================== START: bmad-core/agent-teams/team-fullstack.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 bundle:
   name: Team Fullstack
@@ -59,9 +59,9 @@ workflows:
   - greenfield-fullstack.yaml
   - greenfield-service.yaml
   - greenfield-ui.yaml
-==================== END: .bmad-core/agent-teams/team-fullstack.yaml ====================
+==================== END: bmad-core/agent-teams/team-fullstack.yaml ====================
 
-==================== START: .bmad-core/agents/bmad-orchestrator.md ====================
+==================== START: bmad-core/agents/bmad-orchestrator.md ====================
 # bmad-orchestrator
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -186,9 +186,9 @@ dependencies:
   utils:
     - workflow-management.md
 ```
-==================== END: .bmad-core/agents/bmad-orchestrator.md ====================
+==================== END: bmad-core/agents/bmad-orchestrator.md ====================
 
-==================== START: .bmad-core/agents/analyst.md ====================
+==================== START: bmad-core/agents/analyst.md ====================
 # analyst
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -250,9 +250,9 @@ dependencies:
     - market-research-tmpl.yaml
     - project-brief-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/analyst.md ====================
+==================== END: bmad-core/agents/analyst.md ====================
 
-==================== START: .bmad-core/agents/pm.md ====================
+==================== START: bmad-core/agents/pm.md ====================
 # pm
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -314,9 +314,9 @@ dependencies:
     - brownfield-prd-tmpl.yaml
     - prd-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/pm.md ====================
+==================== END: bmad-core/agents/pm.md ====================
 
-==================== START: .bmad-core/agents/ux-expert.md ====================
+==================== START: bmad-core/agents/ux-expert.md ====================
 # ux-expert
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -363,9 +363,9 @@ dependencies:
   templates:
     - front-end-spec-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/ux-expert.md ====================
+==================== END: bmad-core/agents/ux-expert.md ====================
 
-==================== START: .bmad-core/agents/architect.md ====================
+==================== START: bmad-core/agents/architect.md ====================
 # architect
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -428,9 +428,9 @@ dependencies:
     - front-end-architecture-tmpl.yaml
     - fullstack-architecture-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/architect.md ====================
+==================== END: bmad-core/agents/architect.md ====================
 
-==================== START: .bmad-core/agents/po.md ====================
+==================== START: bmad-core/agents/po.md ====================
 # po
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -487,9 +487,9 @@ dependencies:
   templates:
     - story-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/po.md ====================
+==================== END: bmad-core/agents/po.md ====================
 
-==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
+==================== START: bmad-core/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
 # Advanced Elicitation Task
 
@@ -608,9 +608,9 @@ Choose a number (0-8) or 9 to proceed:
 - **Stay Relevant**: Tie all elicitation back to the specific content being analyzed
 - **Identify Personas**: For multi-persona methods, clearly identify which viewpoint is speaking
 - **Maintain Flow**: Keep the process moving efficiently
-==================== END: .bmad-core/tasks/advanced-elicitation.md ====================
+==================== END: bmad-core/tasks/advanced-elicitation.md ====================
 
-==================== START: .bmad-core/tasks/create-doc.md ====================
+==================== START: bmad-core/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Document from Template (YAML Driven)
 
@@ -629,7 +629,7 @@ When this task is invoked:
 
 ## Critical: Template Discovery
 
-If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.
+If a YAML Template has not been provided, list all templates from bmad-core/templates or ask the user to provide another.
 
 ## CRITICAL: Mandatory Elicitation Format
 
@@ -713,9 +713,9 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 - Select options 2-9 from data/elicitation-methods only
 - Provide detailed rationale explaining decisions
 - End with "Select 1-9 or just type your question/feedback:"
-==================== END: .bmad-core/tasks/create-doc.md ====================
+==================== END: bmad-core/tasks/create-doc.md ====================
 
-==================== START: .bmad-core/tasks/kb-mode-interaction.md ====================
+==================== START: bmad-core/tasks/kb-mode-interaction.md ====================
 <!-- Powered by BMAD™ Core -->
 # KB Mode Interaction Task
 
@@ -792,9 +792,9 @@ Or ask me about anything else related to BMad-Method!
 **User**: Tell me about workflows
 
 **Assistant**: [Provides focused information about workflows from the KB, then offers to explore specific workflow types or related topics]
-==================== END: .bmad-core/tasks/kb-mode-interaction.md ====================
+==================== END: bmad-core/tasks/kb-mode-interaction.md ====================
 
-==================== START: .bmad-core/data/bmad-kb.md ====================
+==================== START: bmad-core/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
 # BMAD™ Knowledge Base
 
@@ -903,7 +903,7 @@ npx bmad-method install
 
 **Verify Installation**:
 
-- `.bmad-core/` folder created with all agents
+- `bmad-core/` folder created with all agents
 - IDE-specific integration files created
 - All agent commands/rules/modes available
 
@@ -1602,9 +1602,9 @@ Use the **expansion-creator** pack to build your own:
 - **Documentation**: Check `docs/` folder for project-specific context
 - **Community**: Discord and GitHub resources available for support
 - **Contributing**: See `CONTRIBUTING.md` for full guidelines
-==================== END: .bmad-core/data/bmad-kb.md ====================
+==================== END: bmad-core/data/bmad-kb.md ====================
 
-==================== START: .bmad-core/data/elicitation-methods.md ====================
+==================== START: bmad-core/data/elicitation-methods.md ====================
 <!-- Powered by BMAD™ Core -->
 # Elicitation Methods Data
 
@@ -1760,9 +1760,9 @@ Use the **expansion-creator** pack to build your own:
 - Acknowledge choice to finalize current work
 - Accept output as-is or move to next step
 - Prepare to continue without additional elicitation
-==================== END: .bmad-core/data/elicitation-methods.md ====================
+==================== END: bmad-core/data/elicitation-methods.md ====================
 
-==================== START: .bmad-core/utils/workflow-management.md ====================
+==================== START: bmad-core/utils/workflow-management.md ====================
 <!-- Powered by BMAD™ Core -->
 # Workflow Management
 
@@ -1833,9 +1833,9 @@ Handle conditional paths by asking clarifying questions when needed.
 ## Agent Integration
 
 Agents should be workflow-aware: know active workflow, their role, access artifacts, understand expected outputs.
-==================== END: .bmad-core/utils/workflow-management.md ====================
+==================== END: bmad-core/utils/workflow-management.md ====================
 
-==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
+==================== START: bmad-core/tasks/create-deep-research-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Deep Research Prompt Task
 
@@ -2115,9 +2115,9 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
 - Balance comprehensiveness with focus
 - Document assumptions and limitations clearly
 - Plan for iterative refinement based on initial findings
-==================== END: .bmad-core/tasks/create-deep-research-prompt.md ====================
+==================== END: bmad-core/tasks/create-deep-research-prompt.md ====================
 
-==================== START: .bmad-core/tasks/document-project.md ====================
+==================== START: bmad-core/tasks/document-project.md ====================
 <!-- Powered by BMAD™ Core -->
 # Document an Existing Project
 
@@ -2462,13 +2462,13 @@ Apply the advanced elicitation task after major sections to refine based on user
 - Documents technical debt, workarounds, and constraints honestly
 - For brownfield projects with PRD: Provides clear enhancement impact analysis
 - The goal is PRACTICAL documentation for AI agents doing real work
-==================== END: .bmad-core/tasks/document-project.md ====================
+==================== END: bmad-core/tasks/document-project.md ====================
 
-==================== START: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
+==================== START: bmad-core/tasks/facilitate-brainstorming-session.md ====================
 <!-- Powered by BMAD™ Core -->
 ---
 docOutputLocation: docs/brainstorming-session-results.md
-template: '.bmad-core/templates/brainstorming-output-tmpl.yaml'
+template: 'bmad-core/templates/brainstorming-output-tmpl.yaml'
 ---
 
 # Facilitate Brainstorming Session Task
@@ -2602,9 +2602,9 @@ Generate structured document with these sections:
 - Always ask before switching techniques: "Ready to try a different approach?"
 - Offer options: "Should we explore this idea deeper or generate more alternatives?"
 - Respect their process and timing
-==================== END: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
+==================== END: bmad-core/tasks/facilitate-brainstorming-session.md ====================
 
-==================== START: .bmad-core/templates/brainstorming-output-tmpl.yaml ====================
+==================== START: bmad-core/templates/brainstorming-output-tmpl.yaml ====================
 template:
   id: brainstorming-output-template-v2
   name: Brainstorming Session Results
@@ -2761,9 +2761,9 @@ sections:
       ---
 
       *Session facilitated using the BMAD-METHOD™ brainstorming framework*
-==================== END: .bmad-core/templates/brainstorming-output-tmpl.yaml ====================
+==================== END: bmad-core/templates/brainstorming-output-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/competitor-analysis-tmpl.yaml ====================
+==================== START: bmad-core/templates/competitor-analysis-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: competitor-analysis-template-v2
@@ -3071,9 +3071,9 @@ sections:
           - Weekly: {{weekly_items}}
           - Monthly: {{monthly_items}}
           - Quarterly: {{quarterly_analysis}}
-==================== END: .bmad-core/templates/competitor-analysis-tmpl.yaml ====================
+==================== END: bmad-core/templates/competitor-analysis-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/market-research-tmpl.yaml ====================
+==================== START: bmad-core/templates/market-research-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: market-research-template-v2
@@ -3327,9 +3327,9 @@ sections:
       - id: additional-analysis
         title: C. Additional Analysis
         instruction: Any supplementary analysis not included in main body
-==================== END: .bmad-core/templates/market-research-tmpl.yaml ====================
+==================== END: bmad-core/templates/market-research-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/project-brief-tmpl.yaml ====================
+==================== START: bmad-core/templates/project-brief-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: project-brief-template-v2
@@ -3552,9 +3552,9 @@ sections:
         title: PM Handoff
         content: |
           This Project Brief provides the full context for {{project_name}}. Please start in 'PRD Generation Mode', review the brief thoroughly to work with the user to create the PRD section by section as the template indicates, asking for any necessary clarification or suggesting improvements.
-==================== END: .bmad-core/templates/project-brief-tmpl.yaml ====================
+==================== END: bmad-core/templates/project-brief-tmpl.yaml ====================
 
-==================== START: .bmad-core/data/brainstorming-techniques.md ====================
+==================== START: bmad-core/data/brainstorming-techniques.md ====================
 <!-- Powered by BMAD™ Core -->
 # Brainstorming Techniques Data
 
@@ -3592,9 +3592,9 @@ sections:
 18. **Resource Constraints**: "What if you had only $10 and 1 hour?"
 19. **Metaphor Mapping**: Use extended metaphors to explore solutions
 20. **Question Storming**: Generate questions instead of answers first
-==================== END: .bmad-core/data/brainstorming-techniques.md ====================
+==================== END: bmad-core/data/brainstorming-techniques.md ====================
 
-==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
+==================== START: bmad-core/tasks/brownfield-create-epic.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Brownfield Epic Task
 
@@ -3756,9 +3756,9 @@ The epic creation is successful when:
 - If the scope grows beyond 3 stories, consider the full brownfield PRD process
 - Always prioritize existing system integrity over new functionality
 - When in doubt about scope or complexity, escalate to full brownfield planning
-==================== END: .bmad-core/tasks/brownfield-create-epic.md ====================
+==================== END: bmad-core/tasks/brownfield-create-epic.md ====================
 
-==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
+==================== START: bmad-core/tasks/brownfield-create-story.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Brownfield Story Task
 
@@ -3907,15 +3907,15 @@ The story creation is successful when:
 - Always prioritize existing system integrity
 - When in doubt about integration complexity, use brownfield-create-epic instead
 - Stories should take no more than 4 hours of focused development work
-==================== END: .bmad-core/tasks/brownfield-create-story.md ====================
+==================== END: bmad-core/tasks/brownfield-create-story.md ====================
 
-==================== START: .bmad-core/tasks/correct-course.md ====================
+==================== START: bmad-core/tasks/correct-course.md ====================
 <!-- Powered by BMAD™ Core -->
 # Correct Course Task
 
 ## Purpose
 
-- Guide a structured response to a change trigger using the `.bmad-core/checklists/change-checklist`.
+- Guide a structured response to a change trigger using the `bmad-core/checklists/change-checklist`.
 - Analyze the impacts of the change on epics, project artifacts, and the MVP, guided by the checklist's structure.
 - Explore potential solutions (e.g., adjust scope, rollback elements, re-scope features) as prompted by the checklist.
 - Draft specific, actionable proposed updates to any affected project artifacts (e.g., epics, user stories, PRD sections, architecture document sections) based on the analysis.
@@ -3929,7 +3929,7 @@ The story creation is successful when:
 - **Acknowledge Task & Inputs:**
   - Confirm with the user that the "Correct Course Task" (Change Navigation & Integration) is being initiated.
   - Verify the change trigger and ensure you have the user's initial explanation of the issue and its perceived impact.
-  - Confirm access to all relevant project artifacts (e.g., PRD, Epics/Stories, Architecture Documents, UI/UX Specifications) and, critically, the `.bmad-core/checklists/change-checklist`.
+  - Confirm access to all relevant project artifacts (e.g., PRD, Epics/Stories, Architecture Documents, UI/UX Specifications) and, critically, the `bmad-core/checklists/change-checklist`.
 - **Establish Interaction Mode:**
   - Ask the user their preferred interaction mode for this task:
     - **"Incrementally (Default & Recommended):** Shall we work through the change-checklist section by section, discussing findings and collaboratively drafting proposed changes for each relevant part before moving to the next? This allows for detailed, step-by-step refinement."
@@ -3981,9 +3981,9 @@ The story creation is successful when:
   - A summary of the change-checklist analysis (issue, impact, rationale for the chosen path).
   - Specific, clearly drafted proposed edits for all affected project artifacts.
 - **Implicit:** An annotated change-checklist (or the record of its completion) reflecting the discussions, findings, and decisions made during the process.
-==================== END: .bmad-core/tasks/correct-course.md ====================
+==================== END: bmad-core/tasks/correct-course.md ====================
 
-==================== START: .bmad-core/tasks/execute-checklist.md ====================
+==================== START: bmad-core/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
@@ -3991,7 +3991,7 @@ This task provides instructions for validating documentation against checklists.
 
 ## 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.
+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
 
@@ -3999,7 +3999,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
    - If user or the task being run provides a checklist name:
      - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
      - If multiple matches found, ask user to clarify
-     - Load the appropriate checklist from .bmad-core/checklists/
+     - 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
@@ -4071,9 +4071,9 @@ The LLM will:
 - Execute the complete checklist validation
 - Present a final report with pass/fail rates and key findings
 - Offer to provide detailed analysis of any section, especially those with warnings or failures
-==================== END: .bmad-core/tasks/execute-checklist.md ====================
+==================== END: bmad-core/tasks/execute-checklist.md ====================
 
-==================== START: .bmad-core/tasks/shard-doc.md ====================
+==================== START: bmad-core/tasks/shard-doc.md ====================
 <!-- Powered by BMAD™ Core -->
 # Document Sharding Task
 
@@ -4085,20 +4085,20 @@ The LLM will:
 
 ## Primary Method: Automatic with markdown-tree
 
-[[LLM: First, check if markdownExploder is set to true in .bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
+[[LLM: First, check if markdownExploder is set to true in bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
 
 If the command succeeds, inform the user that the document has been sharded successfully and STOP - do not proceed further.
 
 If the command fails (especially with an error indicating the command is not found or not available), inform the user: "The markdownExploder setting is enabled but the md-tree command is not available. Please either:
 
 1. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
-2. Or set markdownExploder to false in .bmad-core/core-config.yaml
+2. Or set markdownExploder to false in bmad-core/core-config.yaml
 
 **IMPORTANT: STOP HERE - do not proceed with manual sharding until one of the above actions is taken.**"
 
 If markdownExploder is set to false, inform the user: "The markdownExploder setting is currently false. For better performance and reliability, you should:
 
-1. Set markdownExploder to true in .bmad-core/core-config.yaml
+1. Set markdownExploder to true in bmad-core/core-config.yaml
 2. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
 
 I will now proceed with the manual sharding process."
@@ -4260,9 +4260,9 @@ Document sharded successfully:
 - Preserve ALL formatting, including whitespace where significant
 - Handle edge cases like sections with code blocks containing ## symbols
 - Ensure the sharding is reversible (could reconstruct the original from shards)
-==================== END: .bmad-core/tasks/shard-doc.md ====================
+==================== END: bmad-core/tasks/shard-doc.md ====================
 
-==================== START: .bmad-core/templates/brownfield-prd-tmpl.yaml ====================
+==================== START: bmad-core/templates/brownfield-prd-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: brownfield-prd-template-v2
@@ -4544,9 +4544,9 @@ sections:
               - template: "IV1: {{existing_functionality_verification}}"
               - template: "IV2: {{integration_point_verification}}"
               - template: "IV3: {{performance_impact_verification}}"
-==================== END: .bmad-core/templates/brownfield-prd-tmpl.yaml ====================
+==================== END: bmad-core/templates/brownfield-prd-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/prd-tmpl.yaml ====================
+==================== START: bmad-core/templates/prd-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: prd-template-v2
@@ -4649,7 +4649,7 @@ sections:
     instruction: |
       Gather technical decisions that will guide the Architect. Steps:
 
-      1. Check if .bmad-core/data/technical-preferences.yaml or an attached technical-preferences file exists - use it to pre-populate choices
+      1. Check if bmad-core/data/technical-preferences.yaml or an attached technical-preferences file exists - use it to pre-populate choices
       2. Ask user about: languages, frameworks, starter templates, libraries, APIs, deployment targets
       3. For unknowns, offer guidance based on project goals and MVP scope
       4. Document ALL technical choices with rationale (why this choice fits the project)
@@ -4750,9 +4750,9 @@ sections:
       - id: architect-prompt
         title: Architect Prompt
         instruction: This section will contain the prompt for the Architect, keep it short and to the point to initiate create architecture mode using this document as input.
-==================== END: .bmad-core/templates/prd-tmpl.yaml ====================
+==================== END: bmad-core/templates/prd-tmpl.yaml ====================
 
-==================== START: .bmad-core/checklists/change-checklist.md ====================
+==================== START: bmad-core/checklists/change-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Change Navigation Checklist
 
@@ -4936,9 +4936,9 @@ Keep it action-oriented and forward-looking.]]
 - [ ] **Confirm Next Steps:** Reiterate the handoff plan and the next actions to be taken by specific agents.
 
 ---
-==================== END: .bmad-core/checklists/change-checklist.md ====================
+==================== END: bmad-core/checklists/change-checklist.md ====================
 
-==================== START: .bmad-core/checklists/pm-checklist.md ====================
+==================== START: bmad-core/checklists/pm-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Product Manager (PM) Requirements Checklist
 
@@ -5310,16 +5310,16 @@ After presenting the report, ask if the user wants:
 
 - **READY FOR ARCHITECT**: The PRD and epics are comprehensive, properly structured, and ready for architectural design.
 - **NEEDS REFINEMENT**: The requirements documentation requires additional work to address the identified deficiencies.
-==================== END: .bmad-core/checklists/pm-checklist.md ====================
+==================== END: bmad-core/checklists/pm-checklist.md ====================
 
-==================== START: .bmad-core/data/technical-preferences.md ====================
+==================== START: bmad-core/data/technical-preferences.md ====================
 <!-- Powered by BMAD™ Core -->
 # User-Defined Preferred Patterns and Preferences
 
 None Listed
-==================== END: .bmad-core/data/technical-preferences.md ====================
+==================== END: bmad-core/data/technical-preferences.md ====================
 
-==================== START: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
+==================== START: bmad-core/tasks/generate-ai-frontend-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create AI Frontend Prompt Task
 
@@ -5372,9 +5372,9 @@ You will now synthesize the inputs and the above principles into a final, compre
    - Output the complete, generated prompt in a clear, copy-pasteable format (e.g., a large code block).
    - Explain the structure of the prompt and why certain information was included, referencing the principles above.
    - <important_note>Conclude by reminding the user that all AI-generated code will require careful human review, testing, and refinement to be considered production-ready.</important_note>
-==================== END: .bmad-core/tasks/generate-ai-frontend-prompt.md ====================
+==================== END: bmad-core/tasks/generate-ai-frontend-prompt.md ====================
 
-==================== START: .bmad-core/templates/front-end-spec-tmpl.yaml ====================
+==================== START: bmad-core/templates/front-end-spec-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: frontend-spec-template-v2
@@ -5725,9 +5725,9 @@ sections:
   - id: checklist-results
     title: Checklist Results
     instruction: If a UI/UX checklist exists, run it against this document and report results here.
-==================== END: .bmad-core/templates/front-end-spec-tmpl.yaml ====================
+==================== END: bmad-core/templates/front-end-spec-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/architecture-tmpl.yaml ====================
+==================== START: bmad-core/templates/architecture-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: architecture-template-v2
@@ -5858,7 +5858,7 @@ sections:
     instruction: |
       This is the DEFINITIVE technology selection section. Work with the user to make specific choices:
 
-      1. Review PRD technical assumptions and any preferences from .bmad-core/data/technical-preferences.yaml or an attached technical-preferences
+      1. Review PRD technical assumptions and any preferences from bmad-core/data/technical-preferences.yaml or an attached technical-preferences
       2. For each category, present 2-3 viable options with pros/cons
       3. Make a clear recommendation based on project needs
       4. Get explicit user approval for each selection
@@ -6379,9 +6379,9 @@ sections:
           - Key UI requirements from PRD
           - Any frontend-specific decisions made here
           - Request for detailed frontend architecture
-==================== END: .bmad-core/templates/architecture-tmpl.yaml ====================
+==================== END: bmad-core/templates/architecture-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
+==================== START: bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: brownfield-architecture-template-v2
@@ -6859,9 +6859,9 @@ sections:
           - Key technical decisions based on real project constraints
           - Existing system compatibility requirements with specific verification steps
           - Clear sequencing of implementation to minimize risk to existing functionality
-==================== END: .bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
+==================== END: bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/front-end-architecture-tmpl.yaml ====================
+==================== START: bmad-core/templates/front-end-architecture-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: frontend-architecture-template-v2
@@ -7081,9 +7081,9 @@ sections:
           - Key import patterns
           - File naming conventions
           - Project-specific patterns and utilities
-==================== END: .bmad-core/templates/front-end-architecture-tmpl.yaml ====================
+==================== END: bmad-core/templates/front-end-architecture-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
+==================== START: bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: fullstack-architecture-template-v2
@@ -7908,9 +7908,9 @@ sections:
   - id: checklist-results
     title: Checklist Results Report
     instruction: Before running the checklist, offer to output the full architecture document. Once user confirms, execute the architect-checklist and populate results here.
-==================== END: .bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
+==================== END: bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
 
-==================== START: .bmad-core/checklists/architect-checklist.md ====================
+==================== START: bmad-core/checklists/architect-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Architect Solution Validation Checklist
 
@@ -8350,9 +8350,9 @@ Now that you've completed the checklist, generate a comprehensive validation rep
    - Component design clarity
 
 After presenting the report, ask the user if they would like detailed analysis of any specific section, especially those with warnings or failures.]]
-==================== END: .bmad-core/checklists/architect-checklist.md ====================
+==================== END: bmad-core/checklists/architect-checklist.md ====================
 
-==================== START: .bmad-core/tasks/validate-next-story.md ====================
+==================== START: bmad-core/tasks/validate-next-story.md ====================
 <!-- Powered by BMAD™ Core -->
 # Validate Next Story Task
 
@@ -8364,7 +8364,7 @@ To comprehensively validate a story draft before implementation begins, ensuring
 
 ### 0. Load Core Configuration and Inputs
 
-- Load `.bmad-core/core-config.yaml`
+- Load `bmad-core/core-config.yaml`
 - If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story validation."
 - Extract key configurations: `devStoryLocation`, `prd.*`, `architecture.*`
 - Identify and load the following inputs:
@@ -8488,9 +8488,9 @@ Provide a structured validation report including:
 - **NO-GO**: Story requires fixes before implementation
 - **Implementation Readiness Score**: 1-10 scale
 - **Confidence Level**: High/Medium/Low for successful implementation
-==================== END: .bmad-core/tasks/validate-next-story.md ====================
+==================== END: bmad-core/tasks/validate-next-story.md ====================
 
-==================== START: .bmad-core/templates/story-tmpl.yaml ====================
+==================== START: bmad-core/templates/story-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: story-template-v2
@@ -8629,9 +8629,9 @@ sections:
     instruction: Results from QA Agent QA review of the completed story implementation
     owner: qa-agent
     editors: [qa-agent]
-==================== END: .bmad-core/templates/story-tmpl.yaml ====================
+==================== END: bmad-core/templates/story-tmpl.yaml ====================
 
-==================== START: .bmad-core/checklists/po-master-checklist.md ====================
+==================== START: bmad-core/checklists/po-master-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Product Owner (PO) Master Validation Checklist
 
@@ -9065,9 +9065,9 @@ After presenting the report, ask if the user wants:
 - **APPROVED**: The plan is comprehensive, properly sequenced, and ready for implementation.
 - **CONDITIONAL**: The plan requires specific adjustments before proceeding.
 - **REJECTED**: The plan requires significant revision to address critical deficiencies.
-==================== END: .bmad-core/checklists/po-master-checklist.md ====================
+==================== END: bmad-core/checklists/po-master-checklist.md ====================
 
-==================== START: .bmad-core/workflows/brownfield-fullstack.yaml ====================
+==================== START: bmad-core/workflows/brownfield-fullstack.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 workflow:
   id: brownfield-fullstack
@@ -9253,7 +9253,7 @@ workflow:
         All stories implemented and reviewed!
         Project development phase complete.
 
-        Reference: .bmad-core/data/bmad-kb.md#IDE Development Workflow
+        Reference: bmad-core/data/bmad-kb.md#IDE Development Workflow
 
   flow_diagram: |
     ```mermaid
@@ -9366,9 +9366,9 @@ workflow:
       {{if missing_context}}: May need to gather additional context from user during story creation.
 
     complete: "All planning artifacts validated and development can begin. Stories will be created based on available documentation format."
-==================== END: .bmad-core/workflows/brownfield-fullstack.yaml ====================
+==================== END: bmad-core/workflows/brownfield-fullstack.yaml ====================
 
-==================== START: .bmad-core/workflows/brownfield-service.yaml ====================
+==================== START: bmad-core/workflows/brownfield-service.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 workflow:
   id: brownfield-service
@@ -9500,7 +9500,7 @@ workflow:
         All stories implemented and reviewed!
         Project development phase complete.
 
-        Reference: .bmad-core/data/bmad-kb.md#IDE Development Workflow
+        Reference: bmad-core/data/bmad-kb.md#IDE Development Workflow
 
   flow_diagram: |
     ```mermaid
@@ -9557,9 +9557,9 @@ workflow:
     architect_to_po: "Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for service integration safety."
     po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
     complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
-==================== END: .bmad-core/workflows/brownfield-service.yaml ====================
+==================== END: bmad-core/workflows/brownfield-service.yaml ====================
 
-==================== START: .bmad-core/workflows/brownfield-ui.yaml ====================
+==================== START: bmad-core/workflows/brownfield-ui.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 workflow:
   id: brownfield-ui
@@ -9698,7 +9698,7 @@ workflow:
         All stories implemented and reviewed!
         Project development phase complete.
 
-        Reference: .bmad-core/data/bmad-kb.md#IDE Development Workflow
+        Reference: bmad-core/data/bmad-kb.md#IDE Development Workflow
 
   flow_diagram: |
     ```mermaid
@@ -9758,9 +9758,9 @@ workflow:
     architect_to_po: "Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for UI integration safety."
     po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
     complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
-==================== END: .bmad-core/workflows/brownfield-ui.yaml ====================
+==================== END: bmad-core/workflows/brownfield-ui.yaml ====================
 
-==================== START: .bmad-core/workflows/greenfield-fullstack.yaml ====================
+==================== START: bmad-core/workflows/greenfield-fullstack.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 workflow:
   id: greenfield-fullstack
@@ -9924,7 +9924,7 @@ workflow:
         All stories implemented and reviewed!
         Project development phase complete.
 
-        Reference: .bmad-core/data/bmad-kb.md#IDE Development Workflow
+        Reference: bmad-core/data/bmad-kb.md#IDE Development Workflow
 
   flow_diagram: |
     ```mermaid
@@ -10002,9 +10002,9 @@ workflow:
     updated_to_po: "All documents ready in docs/ folder. Please validate all artifacts for consistency."
     po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
     complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
-==================== END: .bmad-core/workflows/greenfield-fullstack.yaml ====================
+==================== END: bmad-core/workflows/greenfield-fullstack.yaml ====================
 
-==================== START: .bmad-core/workflows/greenfield-service.yaml ====================
+==================== START: bmad-core/workflows/greenfield-service.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 workflow:
   id: greenfield-service
@@ -10144,7 +10144,7 @@ workflow:
         All stories implemented and reviewed!
         Service development phase complete.
 
-        Reference: .bmad-core/data/bmad-kb.md#IDE Development Workflow
+        Reference: bmad-core/data/bmad-kb.md#IDE Development Workflow
 
   flow_diagram: |
     ```mermaid
@@ -10212,9 +10212,9 @@ workflow:
     updated_to_po: "All documents ready in docs/ folder. Please validate all artifacts for consistency."
     po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
     complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
-==================== END: .bmad-core/workflows/greenfield-service.yaml ====================
+==================== END: bmad-core/workflows/greenfield-service.yaml ====================
 
-==================== START: .bmad-core/workflows/greenfield-ui.yaml ====================
+==================== START: bmad-core/workflows/greenfield-ui.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 workflow:
   id: greenfield-ui
@@ -10373,7 +10373,7 @@ workflow:
         All stories implemented and reviewed!
         Project development phase complete.
 
-        Reference: .bmad-core/data/bmad-kb.md#IDE Development Workflow
+        Reference: bmad-core/data/bmad-kb.md#IDE Development Workflow
 
   flow_diagram: |
     ```mermaid
@@ -10451,4 +10451,4 @@ workflow:
     updated_to_po: "All documents ready in docs/ folder. Please validate all artifacts for consistency."
     po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
     complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
-==================== END: .bmad-core/workflows/greenfield-ui.yaml ====================
+==================== END: bmad-core/workflows/greenfield-ui.yaml ====================

dist/teams/team-ide-minimal.txt

@@ -8,13 +8,13 @@ You are now operating as a specialized AI agent from the BMad-Method framework.
 
 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
 
-- `==================== START: .bmad-core/folder/filename.md ====================`
-- `==================== END: .bmad-core/folder/filename.md ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
+- `==================== END: bmad-core/folder/filename.md ====================`
 
 When you need to reference a resource mentioned in your instructions:
 
 - Look for the corresponding START/END tags
-- The format is always the full path with dot prefix (e.g., `.bmad-core/personas/analyst.md`, `.bmad-core/tasks/create-story.md`)
+- The format is always the full path with dot prefix (e.g., `bmad-core/personas/analyst.md`, `bmad-core/tasks/create-story.md`)
 - If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
 
 **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
@@ -29,8 +29,8 @@ dependencies:
 
 These references map directly to bundle sections:
 
-- `utils: template-format` → Look for `==================== START: .bmad-core/utils/template-format.md ====================`
-- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.md ====================`
+- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
+- `tasks: create-story` → Look for `==================== START: bmad-core/tasks/create-story.md ====================`
 
 3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
 
@@ -39,7 +39,7 @@ These references map directly to bundle sections:
 ---
 
 
-==================== START: .bmad-core/agent-teams/team-ide-minimal.yaml ====================
+==================== START: bmad-core/agent-teams/team-ide-minimal.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 bundle:
   name: Team IDE Minimal
@@ -51,9 +51,9 @@ agents:
   - dev
   - qa
 workflows: null
-==================== END: .bmad-core/agent-teams/team-ide-minimal.yaml ====================
+==================== END: bmad-core/agent-teams/team-ide-minimal.yaml ====================
 
-==================== START: .bmad-core/agents/bmad-orchestrator.md ====================
+==================== START: bmad-core/agents/bmad-orchestrator.md ====================
 # bmad-orchestrator
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -178,9 +178,9 @@ dependencies:
   utils:
     - workflow-management.md
 ```
-==================== END: .bmad-core/agents/bmad-orchestrator.md ====================
+==================== END: bmad-core/agents/bmad-orchestrator.md ====================
 
-==================== START: .bmad-core/agents/po.md ====================
+==================== START: bmad-core/agents/po.md ====================
 # po
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -237,9 +237,9 @@ dependencies:
   templates:
     - story-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/po.md ====================
+==================== END: bmad-core/agents/po.md ====================
 
-==================== START: .bmad-core/agents/sm.md ====================
+==================== START: bmad-core/agents/sm.md ====================
 # sm
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -282,9 +282,9 @@ dependencies:
   templates:
     - story-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/sm.md ====================
+==================== END: bmad-core/agents/sm.md ====================
 
-==================== START: .bmad-core/agents/dev.md ====================
+==================== START: bmad-core/agents/dev.md ====================
 # dev
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -335,9 +335,9 @@ dependencies:
     - execute-checklist.md
     - validate-next-story.md
 ```
-==================== END: .bmad-core/agents/dev.md ====================
+==================== END: bmad-core/agents/dev.md ====================
 
-==================== START: .bmad-core/agents/qa.md ====================
+==================== START: bmad-core/agents/qa.md ====================
 # qa
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -406,9 +406,9 @@ dependencies:
     - qa-gate-tmpl.yaml
     - story-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/qa.md ====================
+==================== END: bmad-core/agents/qa.md ====================
 
-==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
+==================== START: bmad-core/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
 # Advanced Elicitation Task
 
@@ -527,9 +527,9 @@ Choose a number (0-8) or 9 to proceed:
 - **Stay Relevant**: Tie all elicitation back to the specific content being analyzed
 - **Identify Personas**: For multi-persona methods, clearly identify which viewpoint is speaking
 - **Maintain Flow**: Keep the process moving efficiently
-==================== END: .bmad-core/tasks/advanced-elicitation.md ====================
+==================== END: bmad-core/tasks/advanced-elicitation.md ====================
 
-==================== START: .bmad-core/tasks/create-doc.md ====================
+==================== START: bmad-core/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Document from Template (YAML Driven)
 
@@ -548,7 +548,7 @@ When this task is invoked:
 
 ## Critical: Template Discovery
 
-If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.
+If a YAML Template has not been provided, list all templates from bmad-core/templates or ask the user to provide another.
 
 ## CRITICAL: Mandatory Elicitation Format
 
@@ -632,9 +632,9 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 - Select options 2-9 from data/elicitation-methods only
 - Provide detailed rationale explaining decisions
 - End with "Select 1-9 or just type your question/feedback:"
-==================== END: .bmad-core/tasks/create-doc.md ====================
+==================== END: bmad-core/tasks/create-doc.md ====================
 
-==================== START: .bmad-core/tasks/kb-mode-interaction.md ====================
+==================== START: bmad-core/tasks/kb-mode-interaction.md ====================
 <!-- Powered by BMAD™ Core -->
 # KB Mode Interaction Task
 
@@ -711,9 +711,9 @@ Or ask me about anything else related to BMad-Method!
 **User**: Tell me about workflows
 
 **Assistant**: [Provides focused information about workflows from the KB, then offers to explore specific workflow types or related topics]
-==================== END: .bmad-core/tasks/kb-mode-interaction.md ====================
+==================== END: bmad-core/tasks/kb-mode-interaction.md ====================
 
-==================== START: .bmad-core/data/bmad-kb.md ====================
+==================== START: bmad-core/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
 # BMAD™ Knowledge Base
 
@@ -822,7 +822,7 @@ npx bmad-method install
 
 **Verify Installation**:
 
-- `.bmad-core/` folder created with all agents
+- `bmad-core/` folder created with all agents
 - IDE-specific integration files created
 - All agent commands/rules/modes available
 
@@ -1521,9 +1521,9 @@ Use the **expansion-creator** pack to build your own:
 - **Documentation**: Check `docs/` folder for project-specific context
 - **Community**: Discord and GitHub resources available for support
 - **Contributing**: See `CONTRIBUTING.md` for full guidelines
-==================== END: .bmad-core/data/bmad-kb.md ====================
+==================== END: bmad-core/data/bmad-kb.md ====================
 
-==================== START: .bmad-core/data/elicitation-methods.md ====================
+==================== START: bmad-core/data/elicitation-methods.md ====================
 <!-- Powered by BMAD™ Core -->
 # Elicitation Methods Data
 
@@ -1679,9 +1679,9 @@ Use the **expansion-creator** pack to build your own:
 - Acknowledge choice to finalize current work
 - Accept output as-is or move to next step
 - Prepare to continue without additional elicitation
-==================== END: .bmad-core/data/elicitation-methods.md ====================
+==================== END: bmad-core/data/elicitation-methods.md ====================
 
-==================== START: .bmad-core/utils/workflow-management.md ====================
+==================== START: bmad-core/utils/workflow-management.md ====================
 <!-- Powered by BMAD™ Core -->
 # Workflow Management
 
@@ -1752,15 +1752,15 @@ Handle conditional paths by asking clarifying questions when needed.
 ## Agent Integration
 
 Agents should be workflow-aware: know active workflow, their role, access artifacts, understand expected outputs.
-==================== END: .bmad-core/utils/workflow-management.md ====================
+==================== END: bmad-core/utils/workflow-management.md ====================
 
-==================== START: .bmad-core/tasks/correct-course.md ====================
+==================== START: bmad-core/tasks/correct-course.md ====================
 <!-- Powered by BMAD™ Core -->
 # Correct Course Task
 
 ## Purpose
 
-- Guide a structured response to a change trigger using the `.bmad-core/checklists/change-checklist`.
+- Guide a structured response to a change trigger using the `bmad-core/checklists/change-checklist`.
 - Analyze the impacts of the change on epics, project artifacts, and the MVP, guided by the checklist's structure.
 - Explore potential solutions (e.g., adjust scope, rollback elements, re-scope features) as prompted by the checklist.
 - Draft specific, actionable proposed updates to any affected project artifacts (e.g., epics, user stories, PRD sections, architecture document sections) based on the analysis.
@@ -1774,7 +1774,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
 - **Acknowledge Task & Inputs:**
   - Confirm with the user that the "Correct Course Task" (Change Navigation & Integration) is being initiated.
   - Verify the change trigger and ensure you have the user's initial explanation of the issue and its perceived impact.
-  - Confirm access to all relevant project artifacts (e.g., PRD, Epics/Stories, Architecture Documents, UI/UX Specifications) and, critically, the `.bmad-core/checklists/change-checklist`.
+  - Confirm access to all relevant project artifacts (e.g., PRD, Epics/Stories, Architecture Documents, UI/UX Specifications) and, critically, the `bmad-core/checklists/change-checklist`.
 - **Establish Interaction Mode:**
   - Ask the user their preferred interaction mode for this task:
     - **"Incrementally (Default & Recommended):** Shall we work through the change-checklist section by section, discussing findings and collaboratively drafting proposed changes for each relevant part before moving to the next? This allows for detailed, step-by-step refinement."
@@ -1826,9 +1826,9 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
   - A summary of the change-checklist analysis (issue, impact, rationale for the chosen path).
   - Specific, clearly drafted proposed edits for all affected project artifacts.
 - **Implicit:** An annotated change-checklist (or the record of its completion) reflecting the discussions, findings, and decisions made during the process.
-==================== END: .bmad-core/tasks/correct-course.md ====================
+==================== END: bmad-core/tasks/correct-course.md ====================
 
-==================== START: .bmad-core/tasks/execute-checklist.md ====================
+==================== START: bmad-core/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
@@ -1836,7 +1836,7 @@ This task provides instructions for validating documentation against checklists.
 
 ## 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.
+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
 
@@ -1844,7 +1844,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
    - If user or the task being run provides a checklist name:
      - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
      - If multiple matches found, ask user to clarify
-     - Load the appropriate checklist from .bmad-core/checklists/
+     - 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
@@ -1916,9 +1916,9 @@ The LLM will:
 - Execute the complete checklist validation
 - Present a final report with pass/fail rates and key findings
 - Offer to provide detailed analysis of any section, especially those with warnings or failures
-==================== END: .bmad-core/tasks/execute-checklist.md ====================
+==================== END: bmad-core/tasks/execute-checklist.md ====================
 
-==================== START: .bmad-core/tasks/shard-doc.md ====================
+==================== START: bmad-core/tasks/shard-doc.md ====================
 <!-- Powered by BMAD™ Core -->
 # Document Sharding Task
 
@@ -1930,20 +1930,20 @@ The LLM will:
 
 ## Primary Method: Automatic with markdown-tree
 
-[[LLM: First, check if markdownExploder is set to true in .bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
+[[LLM: First, check if markdownExploder is set to true in bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
 
 If the command succeeds, inform the user that the document has been sharded successfully and STOP - do not proceed further.
 
 If the command fails (especially with an error indicating the command is not found or not available), inform the user: "The markdownExploder setting is enabled but the md-tree command is not available. Please either:
 
 1. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
-2. Or set markdownExploder to false in .bmad-core/core-config.yaml
+2. Or set markdownExploder to false in bmad-core/core-config.yaml
 
 **IMPORTANT: STOP HERE - do not proceed with manual sharding until one of the above actions is taken.**"
 
 If markdownExploder is set to false, inform the user: "The markdownExploder setting is currently false. For better performance and reliability, you should:
 
-1. Set markdownExploder to true in .bmad-core/core-config.yaml
+1. Set markdownExploder to true in bmad-core/core-config.yaml
 2. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
 
 I will now proceed with the manual sharding process."
@@ -2105,9 +2105,9 @@ Document sharded successfully:
 - Preserve ALL formatting, including whitespace where significant
 - Handle edge cases like sections with code blocks containing ## symbols
 - Ensure the sharding is reversible (could reconstruct the original from shards)
-==================== END: .bmad-core/tasks/shard-doc.md ====================
+==================== END: bmad-core/tasks/shard-doc.md ====================
 
-==================== START: .bmad-core/tasks/validate-next-story.md ====================
+==================== START: bmad-core/tasks/validate-next-story.md ====================
 <!-- Powered by BMAD™ Core -->
 # Validate Next Story Task
 
@@ -2119,7 +2119,7 @@ To comprehensively validate a story draft before implementation begins, ensuring
 
 ### 0. Load Core Configuration and Inputs
 
-- Load `.bmad-core/core-config.yaml`
+- Load `bmad-core/core-config.yaml`
 - If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story validation."
 - Extract key configurations: `devStoryLocation`, `prd.*`, `architecture.*`
 - Identify and load the following inputs:
@@ -2243,9 +2243,9 @@ Provide a structured validation report including:
 - **NO-GO**: Story requires fixes before implementation
 - **Implementation Readiness Score**: 1-10 scale
 - **Confidence Level**: High/Medium/Low for successful implementation
-==================== END: .bmad-core/tasks/validate-next-story.md ====================
+==================== END: bmad-core/tasks/validate-next-story.md ====================
 
-==================== START: .bmad-core/templates/story-tmpl.yaml ====================
+==================== START: bmad-core/templates/story-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: story-template-v2
@@ -2384,9 +2384,9 @@ sections:
     instruction: Results from QA Agent QA review of the completed story implementation
     owner: qa-agent
     editors: [qa-agent]
-==================== END: .bmad-core/templates/story-tmpl.yaml ====================
+==================== END: bmad-core/templates/story-tmpl.yaml ====================
 
-==================== START: .bmad-core/checklists/change-checklist.md ====================
+==================== START: bmad-core/checklists/change-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Change Navigation Checklist
 
@@ -2570,9 +2570,9 @@ Keep it action-oriented and forward-looking.]]
 - [ ] **Confirm Next Steps:** Reiterate the handoff plan and the next actions to be taken by specific agents.
 
 ---
-==================== END: .bmad-core/checklists/change-checklist.md ====================
+==================== END: bmad-core/checklists/change-checklist.md ====================
 
-==================== START: .bmad-core/checklists/po-master-checklist.md ====================
+==================== START: bmad-core/checklists/po-master-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Product Owner (PO) Master Validation Checklist
 
@@ -3006,9 +3006,9 @@ After presenting the report, ask if the user wants:
 - **APPROVED**: The plan is comprehensive, properly sequenced, and ready for implementation.
 - **CONDITIONAL**: The plan requires specific adjustments before proceeding.
 - **REJECTED**: The plan requires significant revision to address critical deficiencies.
-==================== END: .bmad-core/checklists/po-master-checklist.md ====================
+==================== END: bmad-core/checklists/po-master-checklist.md ====================
 
-==================== START: .bmad-core/tasks/create-next-story.md ====================
+==================== START: bmad-core/tasks/create-next-story.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Next Story Task
 
@@ -3020,7 +3020,7 @@ To identify the next logical story based on project progress and epic definition
 
 ### 0. Load Core Configuration and Check Workflow
 
-- Load `.bmad-core/core-config.yaml` from the project root
+- Load `bmad-core/core-config.yaml` from the project root
 - If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story creation. You can either: 1) Copy it from GITHUB bmad-core/core-config.yaml and configure it for your project OR 2) Run the BMad installer against your project to upgrade and add the file automatically. Please add and configure core-config.yaml before proceeding."
 - Extract key configurations: `devStoryLocation`, `prd.*`, `architecture.*`, `workflow.*`
 
@@ -3114,17 +3114,17 @@ ALWAYS cite source documents: `[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" and save the story file
-- Execute `.bmad-core/tasks/execute-checklist` `.bmad-core/checklists/story-draft-checklist`
+- Execute `bmad-core/tasks/execute-checklist` `bmad-core/checklists/story-draft-checklist`
 - Provide summary to user including:
   - Story created: `{devStoryLocation}/{epicNum}.{storyNum}.story.md`
   - Status: Draft
   - Key technical components included from architecture docs
   - Any deviations or conflicts noted between epic and architecture
   - Checklist Results
-  - Next steps: For Complex stories, suggest the user carefully review the story draft and also optionally have the PO run the task `.bmad-core/tasks/validate-next-story`
-==================== END: .bmad-core/tasks/create-next-story.md ====================
+  - Next steps: For Complex stories, suggest the user carefully review the story draft and also optionally have the PO run the task `bmad-core/tasks/validate-next-story`
+==================== END: bmad-core/tasks/create-next-story.md ====================
 
-==================== START: .bmad-core/checklists/story-draft-checklist.md ====================
+==================== START: bmad-core/checklists/story-draft-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Story Draft Checklist
 
@@ -3279,9 +3279,9 @@ Be pragmatic - perfect documentation doesn't exist, but it must be enough to pro
 - READY: The story provides sufficient context for implementation
 - NEEDS REVISION: The story requires updates (see issues)
 - BLOCKED: External information required (specify what information)
-==================== END: .bmad-core/checklists/story-draft-checklist.md ====================
+==================== END: bmad-core/checklists/story-draft-checklist.md ====================
 
-==================== START: .bmad-core/tasks/apply-qa-fixes.md ====================
+==================== START: bmad-core/tasks/apply-qa-fixes.md ====================
 <!-- Powered by BMAD™ Core -->
 # apply-qa-fixes
 
@@ -3431,9 +3431,9 @@ Fix plan:
 - Tests validate behavior and close gaps
 - Strict adherence to allowed story update areas
 - Gate ownership remains with QA; Dev signals readiness via Status
-==================== END: .bmad-core/tasks/apply-qa-fixes.md ====================
+==================== END: bmad-core/tasks/apply-qa-fixes.md ====================
 
-==================== START: .bmad-core/checklists/story-dod-checklist.md ====================
+==================== START: bmad-core/checklists/story-dod-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Story Definition of Done (DoD) Checklist
 
@@ -3529,9 +3529,9 @@ After completing the checklist:
 Be honest - it's better to flag issues now than have them discovered later.]]
 
 - [ ] I, the Developer Agent, confirm that all applicable items above have been addressed.
-==================== END: .bmad-core/checklists/story-dod-checklist.md ====================
+==================== END: bmad-core/checklists/story-dod-checklist.md ====================
 
-==================== START: .bmad-core/tasks/nfr-assess.md ====================
+==================== START: bmad-core/tasks/nfr-assess.md ====================
 <!-- Powered by BMAD™ Core -->
 # nfr-assess
 
@@ -3876,9 +3876,9 @@ performance_deep_dive:
 ```
 
 </details>
-==================== END: .bmad-core/tasks/nfr-assess.md ====================
+==================== END: bmad-core/tasks/nfr-assess.md ====================
 
-==================== START: .bmad-core/tasks/qa-gate.md ====================
+==================== START: bmad-core/tasks/qa-gate.md ====================
 <!-- Powered by BMAD™ Core -->
 # qa-gate
 
@@ -4041,9 +4041,9 @@ Gate: CONCERNS → qa.qaLocation/gates/{epic}.{story}-{slug}.yml
 - Always write to standard path
 - Always update story with gate reference
 - Clear, actionable findings
-==================== END: .bmad-core/tasks/qa-gate.md ====================
+==================== END: bmad-core/tasks/qa-gate.md ====================
 
-==================== START: .bmad-core/tasks/review-story.md ====================
+==================== START: bmad-core/tasks/review-story.md ====================
 <!-- Powered by BMAD™ Core -->
 # review-story
 
@@ -4359,9 +4359,9 @@ After review:
 3. Recommend status: "Ready for Done" or "Changes Required" (owner decides)
 4. If files were modified, list them in QA Results and ask Dev to update File List
 5. Always provide constructive feedback and actionable recommendations
-==================== END: .bmad-core/tasks/review-story.md ====================
+==================== END: bmad-core/tasks/review-story.md ====================
 
-==================== START: .bmad-core/tasks/risk-profile.md ====================
+==================== START: bmad-core/tasks/risk-profile.md ====================
 <!-- Powered by BMAD™ Core -->
 # risk-profile
 
@@ -4716,9 +4716,9 @@ Risk profile: qa.qaLocation/assessments/{epic}.{story}-risk-{YYYYMMDD}.md
 - Link risks to specific test requirements
 - Track residual risk after mitigation
 - Update risk profile as story evolves
-==================== END: .bmad-core/tasks/risk-profile.md ====================
+==================== END: bmad-core/tasks/risk-profile.md ====================
 
-==================== START: .bmad-core/tasks/test-design.md ====================
+==================== START: bmad-core/tasks/test-design.md ====================
 <!-- Powered by BMAD™ Core -->
 # test-design
 
@@ -4894,9 +4894,9 @@ Before finalizing, verify:
 - **Efficient coverage**: Test once at the right level
 - **Maintainability**: Consider long-term test maintenance
 - **Fast feedback**: Quick tests run first
-==================== END: .bmad-core/tasks/test-design.md ====================
+==================== END: bmad-core/tasks/test-design.md ====================
 
-==================== START: .bmad-core/tasks/trace-requirements.md ====================
+==================== START: bmad-core/tasks/trace-requirements.md ====================
 <!-- Powered by BMAD™ Core -->
 # trace-requirements
 
@@ -5162,9 +5162,9 @@ Trace matrix: qa.qaLocation/assessments/{epic}.{story}-trace-{YYYYMMDD}.md
 - Identify both presence and absence
 - Prioritize based on risk
 - Make recommendations actionable
-==================== END: .bmad-core/tasks/trace-requirements.md ====================
+==================== END: bmad-core/tasks/trace-requirements.md ====================
 
-==================== START: .bmad-core/templates/qa-gate-tmpl.yaml ====================
+==================== START: bmad-core/templates/qa-gate-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: qa-gate-template-v1
@@ -5268,11 +5268,11 @@ optional_fields_examples:
       future:  # Can be addressed later
         - action: "Consider caching for better performance"
           refs: ["services/data.service.ts"]
-==================== END: .bmad-core/templates/qa-gate-tmpl.yaml ====================
+==================== END: bmad-core/templates/qa-gate-tmpl.yaml ====================
 
-==================== START: .bmad-core/data/technical-preferences.md ====================
+==================== START: bmad-core/data/technical-preferences.md ====================
 <!-- Powered by BMAD™ Core -->
 # User-Defined Preferred Patterns and Preferences
 
 None Listed
-==================== END: .bmad-core/data/technical-preferences.md ====================
+==================== END: bmad-core/data/technical-preferences.md ====================

dist/teams/team-no-ui.txt

@@ -8,13 +8,13 @@ You are now operating as a specialized AI agent from the BMad-Method framework.
 
 2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
 
-- `==================== START: .bmad-core/folder/filename.md ====================`
-- `==================== END: .bmad-core/folder/filename.md ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
+- `==================== END: bmad-core/folder/filename.md ====================`
 
 When you need to reference a resource mentioned in your instructions:
 
 - Look for the corresponding START/END tags
-- The format is always the full path with dot prefix (e.g., `.bmad-core/personas/analyst.md`, `.bmad-core/tasks/create-story.md`)
+- The format is always the full path with dot prefix (e.g., `bmad-core/personas/analyst.md`, `bmad-core/tasks/create-story.md`)
 - If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
 
 **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
@@ -29,8 +29,8 @@ dependencies:
 
 These references map directly to bundle sections:
 
-- `utils: template-format` → Look for `==================== START: .bmad-core/utils/template-format.md ====================`
-- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.md ====================`
+- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
+- `tasks: create-story` → Look for `==================== START: bmad-core/tasks/create-story.md ====================`
 
 3. **Execution Context**: You are operating in a web environment. All your capabilities and knowledge are contained within this bundle. Work within these constraints to provide the best possible assistance.
 
@@ -39,7 +39,7 @@ These references map directly to bundle sections:
 ---
 
 
-==================== START: .bmad-core/agent-teams/team-no-ui.yaml ====================
+==================== START: bmad-core/agent-teams/team-no-ui.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 bundle:
   name: Team No UI
@@ -54,9 +54,9 @@ agents:
 workflows:
   - greenfield-service.yaml
   - brownfield-service.yaml
-==================== END: .bmad-core/agent-teams/team-no-ui.yaml ====================
+==================== END: bmad-core/agent-teams/team-no-ui.yaml ====================
 
-==================== START: .bmad-core/agents/bmad-orchestrator.md ====================
+==================== START: bmad-core/agents/bmad-orchestrator.md ====================
 # bmad-orchestrator
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -181,9 +181,9 @@ dependencies:
   utils:
     - workflow-management.md
 ```
-==================== END: .bmad-core/agents/bmad-orchestrator.md ====================
+==================== END: bmad-core/agents/bmad-orchestrator.md ====================
 
-==================== START: .bmad-core/agents/analyst.md ====================
+==================== START: bmad-core/agents/analyst.md ====================
 # analyst
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -245,9 +245,9 @@ dependencies:
     - market-research-tmpl.yaml
     - project-brief-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/analyst.md ====================
+==================== END: bmad-core/agents/analyst.md ====================
 
-==================== START: .bmad-core/agents/pm.md ====================
+==================== START: bmad-core/agents/pm.md ====================
 # pm
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -309,9 +309,9 @@ dependencies:
     - brownfield-prd-tmpl.yaml
     - prd-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/pm.md ====================
+==================== END: bmad-core/agents/pm.md ====================
 
-==================== START: .bmad-core/agents/architect.md ====================
+==================== START: bmad-core/agents/architect.md ====================
 # architect
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -374,9 +374,9 @@ dependencies:
     - front-end-architecture-tmpl.yaml
     - fullstack-architecture-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/architect.md ====================
+==================== END: bmad-core/agents/architect.md ====================
 
-==================== START: .bmad-core/agents/po.md ====================
+==================== START: bmad-core/agents/po.md ====================
 # po
 
 CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
@@ -433,9 +433,9 @@ dependencies:
   templates:
     - story-tmpl.yaml
 ```
-==================== END: .bmad-core/agents/po.md ====================
+==================== END: bmad-core/agents/po.md ====================
 
-==================== START: .bmad-core/tasks/advanced-elicitation.md ====================
+==================== START: bmad-core/tasks/advanced-elicitation.md ====================
 <!-- Powered by BMAD™ Core -->
 # Advanced Elicitation Task
 
@@ -554,9 +554,9 @@ Choose a number (0-8) or 9 to proceed:
 - **Stay Relevant**: Tie all elicitation back to the specific content being analyzed
 - **Identify Personas**: For multi-persona methods, clearly identify which viewpoint is speaking
 - **Maintain Flow**: Keep the process moving efficiently
-==================== END: .bmad-core/tasks/advanced-elicitation.md ====================
+==================== END: bmad-core/tasks/advanced-elicitation.md ====================
 
-==================== START: .bmad-core/tasks/create-doc.md ====================
+==================== START: bmad-core/tasks/create-doc.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Document from Template (YAML Driven)
 
@@ -575,7 +575,7 @@ When this task is invoked:
 
 ## Critical: Template Discovery
 
-If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.
+If a YAML Template has not been provided, list all templates from bmad-core/templates or ask the user to provide another.
 
 ## CRITICAL: Mandatory Elicitation Format
 
@@ -659,9 +659,9 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 - Select options 2-9 from data/elicitation-methods only
 - Provide detailed rationale explaining decisions
 - End with "Select 1-9 or just type your question/feedback:"
-==================== END: .bmad-core/tasks/create-doc.md ====================
+==================== END: bmad-core/tasks/create-doc.md ====================
 
-==================== START: .bmad-core/tasks/kb-mode-interaction.md ====================
+==================== START: bmad-core/tasks/kb-mode-interaction.md ====================
 <!-- Powered by BMAD™ Core -->
 # KB Mode Interaction Task
 
@@ -738,9 +738,9 @@ Or ask me about anything else related to BMad-Method!
 **User**: Tell me about workflows
 
 **Assistant**: [Provides focused information about workflows from the KB, then offers to explore specific workflow types or related topics]
-==================== END: .bmad-core/tasks/kb-mode-interaction.md ====================
+==================== END: bmad-core/tasks/kb-mode-interaction.md ====================
 
-==================== START: .bmad-core/data/bmad-kb.md ====================
+==================== START: bmad-core/data/bmad-kb.md ====================
 <!-- Powered by BMAD™ Core -->
 # BMAD™ Knowledge Base
 
@@ -849,7 +849,7 @@ npx bmad-method install
 
 **Verify Installation**:
 
-- `.bmad-core/` folder created with all agents
+- `bmad-core/` folder created with all agents
 - IDE-specific integration files created
 - All agent commands/rules/modes available
 
@@ -1548,9 +1548,9 @@ Use the **expansion-creator** pack to build your own:
 - **Documentation**: Check `docs/` folder for project-specific context
 - **Community**: Discord and GitHub resources available for support
 - **Contributing**: See `CONTRIBUTING.md` for full guidelines
-==================== END: .bmad-core/data/bmad-kb.md ====================
+==================== END: bmad-core/data/bmad-kb.md ====================
 
-==================== START: .bmad-core/data/elicitation-methods.md ====================
+==================== START: bmad-core/data/elicitation-methods.md ====================
 <!-- Powered by BMAD™ Core -->
 # Elicitation Methods Data
 
@@ -1706,9 +1706,9 @@ Use the **expansion-creator** pack to build your own:
 - Acknowledge choice to finalize current work
 - Accept output as-is or move to next step
 - Prepare to continue without additional elicitation
-==================== END: .bmad-core/data/elicitation-methods.md ====================
+==================== END: bmad-core/data/elicitation-methods.md ====================
 
-==================== START: .bmad-core/utils/workflow-management.md ====================
+==================== START: bmad-core/utils/workflow-management.md ====================
 <!-- Powered by BMAD™ Core -->
 # Workflow Management
 
@@ -1779,9 +1779,9 @@ Handle conditional paths by asking clarifying questions when needed.
 ## Agent Integration
 
 Agents should be workflow-aware: know active workflow, their role, access artifacts, understand expected outputs.
-==================== END: .bmad-core/utils/workflow-management.md ====================
+==================== END: bmad-core/utils/workflow-management.md ====================
 
-==================== START: .bmad-core/tasks/create-deep-research-prompt.md ====================
+==================== START: bmad-core/tasks/create-deep-research-prompt.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Deep Research Prompt Task
 
@@ -2061,9 +2061,9 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
 - Balance comprehensiveness with focus
 - Document assumptions and limitations clearly
 - Plan for iterative refinement based on initial findings
-==================== END: .bmad-core/tasks/create-deep-research-prompt.md ====================
+==================== END: bmad-core/tasks/create-deep-research-prompt.md ====================
 
-==================== START: .bmad-core/tasks/document-project.md ====================
+==================== START: bmad-core/tasks/document-project.md ====================
 <!-- Powered by BMAD™ Core -->
 # Document an Existing Project
 
@@ -2408,13 +2408,13 @@ Apply the advanced elicitation task after major sections to refine based on user
 - Documents technical debt, workarounds, and constraints honestly
 - For brownfield projects with PRD: Provides clear enhancement impact analysis
 - The goal is PRACTICAL documentation for AI agents doing real work
-==================== END: .bmad-core/tasks/document-project.md ====================
+==================== END: bmad-core/tasks/document-project.md ====================
 
-==================== START: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
+==================== START: bmad-core/tasks/facilitate-brainstorming-session.md ====================
 <!-- Powered by BMAD™ Core -->
 ---
 docOutputLocation: docs/brainstorming-session-results.md
-template: '.bmad-core/templates/brainstorming-output-tmpl.yaml'
+template: 'bmad-core/templates/brainstorming-output-tmpl.yaml'
 ---
 
 # Facilitate Brainstorming Session Task
@@ -2548,9 +2548,9 @@ Generate structured document with these sections:
 - Always ask before switching techniques: "Ready to try a different approach?"
 - Offer options: "Should we explore this idea deeper or generate more alternatives?"
 - Respect their process and timing
-==================== END: .bmad-core/tasks/facilitate-brainstorming-session.md ====================
+==================== END: bmad-core/tasks/facilitate-brainstorming-session.md ====================
 
-==================== START: .bmad-core/templates/brainstorming-output-tmpl.yaml ====================
+==================== START: bmad-core/templates/brainstorming-output-tmpl.yaml ====================
 template:
   id: brainstorming-output-template-v2
   name: Brainstorming Session Results
@@ -2707,9 +2707,9 @@ sections:
       ---
 
       *Session facilitated using the BMAD-METHOD™ brainstorming framework*
-==================== END: .bmad-core/templates/brainstorming-output-tmpl.yaml ====================
+==================== END: bmad-core/templates/brainstorming-output-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/competitor-analysis-tmpl.yaml ====================
+==================== START: bmad-core/templates/competitor-analysis-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: competitor-analysis-template-v2
@@ -3017,9 +3017,9 @@ sections:
           - Weekly: {{weekly_items}}
           - Monthly: {{monthly_items}}
           - Quarterly: {{quarterly_analysis}}
-==================== END: .bmad-core/templates/competitor-analysis-tmpl.yaml ====================
+==================== END: bmad-core/templates/competitor-analysis-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/market-research-tmpl.yaml ====================
+==================== START: bmad-core/templates/market-research-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: market-research-template-v2
@@ -3273,9 +3273,9 @@ sections:
       - id: additional-analysis
         title: C. Additional Analysis
         instruction: Any supplementary analysis not included in main body
-==================== END: .bmad-core/templates/market-research-tmpl.yaml ====================
+==================== END: bmad-core/templates/market-research-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/project-brief-tmpl.yaml ====================
+==================== START: bmad-core/templates/project-brief-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: project-brief-template-v2
@@ -3498,9 +3498,9 @@ sections:
         title: PM Handoff
         content: |
           This Project Brief provides the full context for {{project_name}}. Please start in 'PRD Generation Mode', review the brief thoroughly to work with the user to create the PRD section by section as the template indicates, asking for any necessary clarification or suggesting improvements.
-==================== END: .bmad-core/templates/project-brief-tmpl.yaml ====================
+==================== END: bmad-core/templates/project-brief-tmpl.yaml ====================
 
-==================== START: .bmad-core/data/brainstorming-techniques.md ====================
+==================== START: bmad-core/data/brainstorming-techniques.md ====================
 <!-- Powered by BMAD™ Core -->
 # Brainstorming Techniques Data
 
@@ -3538,9 +3538,9 @@ sections:
 18. **Resource Constraints**: "What if you had only $10 and 1 hour?"
 19. **Metaphor Mapping**: Use extended metaphors to explore solutions
 20. **Question Storming**: Generate questions instead of answers first
-==================== END: .bmad-core/data/brainstorming-techniques.md ====================
+==================== END: bmad-core/data/brainstorming-techniques.md ====================
 
-==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
+==================== START: bmad-core/tasks/brownfield-create-epic.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Brownfield Epic Task
 
@@ -3702,9 +3702,9 @@ The epic creation is successful when:
 - If the scope grows beyond 3 stories, consider the full brownfield PRD process
 - Always prioritize existing system integrity over new functionality
 - When in doubt about scope or complexity, escalate to full brownfield planning
-==================== END: .bmad-core/tasks/brownfield-create-epic.md ====================
+==================== END: bmad-core/tasks/brownfield-create-epic.md ====================
 
-==================== START: .bmad-core/tasks/brownfield-create-story.md ====================
+==================== START: bmad-core/tasks/brownfield-create-story.md ====================
 <!-- Powered by BMAD™ Core -->
 # Create Brownfield Story Task
 
@@ -3853,15 +3853,15 @@ The story creation is successful when:
 - Always prioritize existing system integrity
 - When in doubt about integration complexity, use brownfield-create-epic instead
 - Stories should take no more than 4 hours of focused development work
-==================== END: .bmad-core/tasks/brownfield-create-story.md ====================
+==================== END: bmad-core/tasks/brownfield-create-story.md ====================
 
-==================== START: .bmad-core/tasks/correct-course.md ====================
+==================== START: bmad-core/tasks/correct-course.md ====================
 <!-- Powered by BMAD™ Core -->
 # Correct Course Task
 
 ## Purpose
 
-- Guide a structured response to a change trigger using the `.bmad-core/checklists/change-checklist`.
+- Guide a structured response to a change trigger using the `bmad-core/checklists/change-checklist`.
 - Analyze the impacts of the change on epics, project artifacts, and the MVP, guided by the checklist's structure.
 - Explore potential solutions (e.g., adjust scope, rollback elements, re-scope features) as prompted by the checklist.
 - Draft specific, actionable proposed updates to any affected project artifacts (e.g., epics, user stories, PRD sections, architecture document sections) based on the analysis.
@@ -3875,7 +3875,7 @@ The story creation is successful when:
 - **Acknowledge Task & Inputs:**
   - Confirm with the user that the "Correct Course Task" (Change Navigation & Integration) is being initiated.
   - Verify the change trigger and ensure you have the user's initial explanation of the issue and its perceived impact.
-  - Confirm access to all relevant project artifacts (e.g., PRD, Epics/Stories, Architecture Documents, UI/UX Specifications) and, critically, the `.bmad-core/checklists/change-checklist`.
+  - Confirm access to all relevant project artifacts (e.g., PRD, Epics/Stories, Architecture Documents, UI/UX Specifications) and, critically, the `bmad-core/checklists/change-checklist`.
 - **Establish Interaction Mode:**
   - Ask the user their preferred interaction mode for this task:
     - **"Incrementally (Default & Recommended):** Shall we work through the change-checklist section by section, discussing findings and collaboratively drafting proposed changes for each relevant part before moving to the next? This allows for detailed, step-by-step refinement."
@@ -3927,9 +3927,9 @@ The story creation is successful when:
   - A summary of the change-checklist analysis (issue, impact, rationale for the chosen path).
   - Specific, clearly drafted proposed edits for all affected project artifacts.
 - **Implicit:** An annotated change-checklist (or the record of its completion) reflecting the discussions, findings, and decisions made during the process.
-==================== END: .bmad-core/tasks/correct-course.md ====================
+==================== END: bmad-core/tasks/correct-course.md ====================
 
-==================== START: .bmad-core/tasks/execute-checklist.md ====================
+==================== START: bmad-core/tasks/execute-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
@@ -3937,7 +3937,7 @@ This task provides instructions for validating documentation against checklists.
 
 ## 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.
+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
 
@@ -3945,7 +3945,7 @@ If the user asks or does not specify a specific checklist, list the checklists a
    - If user or the task being run provides a checklist name:
      - Try fuzzy matching (e.g. "architecture checklist" -> "architect-checklist")
      - If multiple matches found, ask user to clarify
-     - Load the appropriate checklist from .bmad-core/checklists/
+     - 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
@@ -4017,9 +4017,9 @@ The LLM will:
 - Execute the complete checklist validation
 - Present a final report with pass/fail rates and key findings
 - Offer to provide detailed analysis of any section, especially those with warnings or failures
-==================== END: .bmad-core/tasks/execute-checklist.md ====================
+==================== END: bmad-core/tasks/execute-checklist.md ====================
 
-==================== START: .bmad-core/tasks/shard-doc.md ====================
+==================== START: bmad-core/tasks/shard-doc.md ====================
 <!-- Powered by BMAD™ Core -->
 # Document Sharding Task
 
@@ -4031,20 +4031,20 @@ The LLM will:
 
 ## Primary Method: Automatic with markdown-tree
 
-[[LLM: First, check if markdownExploder is set to true in .bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
+[[LLM: First, check if markdownExploder is set to true in bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
 
 If the command succeeds, inform the user that the document has been sharded successfully and STOP - do not proceed further.
 
 If the command fails (especially with an error indicating the command is not found or not available), inform the user: "The markdownExploder setting is enabled but the md-tree command is not available. Please either:
 
 1. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
-2. Or set markdownExploder to false in .bmad-core/core-config.yaml
+2. Or set markdownExploder to false in bmad-core/core-config.yaml
 
 **IMPORTANT: STOP HERE - do not proceed with manual sharding until one of the above actions is taken.**"
 
 If markdownExploder is set to false, inform the user: "The markdownExploder setting is currently false. For better performance and reliability, you should:
 
-1. Set markdownExploder to true in .bmad-core/core-config.yaml
+1. Set markdownExploder to true in bmad-core/core-config.yaml
 2. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
 
 I will now proceed with the manual sharding process."
@@ -4206,9 +4206,9 @@ Document sharded successfully:
 - Preserve ALL formatting, including whitespace where significant
 - Handle edge cases like sections with code blocks containing ## symbols
 - Ensure the sharding is reversible (could reconstruct the original from shards)
-==================== END: .bmad-core/tasks/shard-doc.md ====================
+==================== END: bmad-core/tasks/shard-doc.md ====================
 
-==================== START: .bmad-core/templates/brownfield-prd-tmpl.yaml ====================
+==================== START: bmad-core/templates/brownfield-prd-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: brownfield-prd-template-v2
@@ -4490,9 +4490,9 @@ sections:
               - template: "IV1: {{existing_functionality_verification}}"
               - template: "IV2: {{integration_point_verification}}"
               - template: "IV3: {{performance_impact_verification}}"
-==================== END: .bmad-core/templates/brownfield-prd-tmpl.yaml ====================
+==================== END: bmad-core/templates/brownfield-prd-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/prd-tmpl.yaml ====================
+==================== START: bmad-core/templates/prd-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: prd-template-v2
@@ -4595,7 +4595,7 @@ sections:
     instruction: |
       Gather technical decisions that will guide the Architect. Steps:
 
-      1. Check if .bmad-core/data/technical-preferences.yaml or an attached technical-preferences file exists - use it to pre-populate choices
+      1. Check if bmad-core/data/technical-preferences.yaml or an attached technical-preferences file exists - use it to pre-populate choices
       2. Ask user about: languages, frameworks, starter templates, libraries, APIs, deployment targets
       3. For unknowns, offer guidance based on project goals and MVP scope
       4. Document ALL technical choices with rationale (why this choice fits the project)
@@ -4696,9 +4696,9 @@ sections:
       - id: architect-prompt
         title: Architect Prompt
         instruction: This section will contain the prompt for the Architect, keep it short and to the point to initiate create architecture mode using this document as input.
-==================== END: .bmad-core/templates/prd-tmpl.yaml ====================
+==================== END: bmad-core/templates/prd-tmpl.yaml ====================
 
-==================== START: .bmad-core/checklists/change-checklist.md ====================
+==================== START: bmad-core/checklists/change-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Change Navigation Checklist
 
@@ -4882,9 +4882,9 @@ Keep it action-oriented and forward-looking.]]
 - [ ] **Confirm Next Steps:** Reiterate the handoff plan and the next actions to be taken by specific agents.
 
 ---
-==================== END: .bmad-core/checklists/change-checklist.md ====================
+==================== END: bmad-core/checklists/change-checklist.md ====================
 
-==================== START: .bmad-core/checklists/pm-checklist.md ====================
+==================== START: bmad-core/checklists/pm-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Product Manager (PM) Requirements Checklist
 
@@ -5256,16 +5256,16 @@ After presenting the report, ask if the user wants:
 
 - **READY FOR ARCHITECT**: The PRD and epics are comprehensive, properly structured, and ready for architectural design.
 - **NEEDS REFINEMENT**: The requirements documentation requires additional work to address the identified deficiencies.
-==================== END: .bmad-core/checklists/pm-checklist.md ====================
+==================== END: bmad-core/checklists/pm-checklist.md ====================
 
-==================== START: .bmad-core/data/technical-preferences.md ====================
+==================== START: bmad-core/data/technical-preferences.md ====================
 <!-- Powered by BMAD™ Core -->
 # User-Defined Preferred Patterns and Preferences
 
 None Listed
-==================== END: .bmad-core/data/technical-preferences.md ====================
+==================== END: bmad-core/data/technical-preferences.md ====================
 
-==================== START: .bmad-core/templates/architecture-tmpl.yaml ====================
+==================== START: bmad-core/templates/architecture-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: architecture-template-v2
@@ -5396,7 +5396,7 @@ sections:
     instruction: |
       This is the DEFINITIVE technology selection section. Work with the user to make specific choices:
 
-      1. Review PRD technical assumptions and any preferences from .bmad-core/data/technical-preferences.yaml or an attached technical-preferences
+      1. Review PRD technical assumptions and any preferences from bmad-core/data/technical-preferences.yaml or an attached technical-preferences
       2. For each category, present 2-3 viable options with pros/cons
       3. Make a clear recommendation based on project needs
       4. Get explicit user approval for each selection
@@ -5917,9 +5917,9 @@ sections:
           - Key UI requirements from PRD
           - Any frontend-specific decisions made here
           - Request for detailed frontend architecture
-==================== END: .bmad-core/templates/architecture-tmpl.yaml ====================
+==================== END: bmad-core/templates/architecture-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
+==================== START: bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: brownfield-architecture-template-v2
@@ -6397,9 +6397,9 @@ sections:
           - Key technical decisions based on real project constraints
           - Existing system compatibility requirements with specific verification steps
           - Clear sequencing of implementation to minimize risk to existing functionality
-==================== END: .bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
+==================== END: bmad-core/templates/brownfield-architecture-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/front-end-architecture-tmpl.yaml ====================
+==================== START: bmad-core/templates/front-end-architecture-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: frontend-architecture-template-v2
@@ -6619,9 +6619,9 @@ sections:
           - Key import patterns
           - File naming conventions
           - Project-specific patterns and utilities
-==================== END: .bmad-core/templates/front-end-architecture-tmpl.yaml ====================
+==================== END: bmad-core/templates/front-end-architecture-tmpl.yaml ====================
 
-==================== START: .bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
+==================== START: bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: fullstack-architecture-template-v2
@@ -7446,9 +7446,9 @@ sections:
   - id: checklist-results
     title: Checklist Results Report
     instruction: Before running the checklist, offer to output the full architecture document. Once user confirms, execute the architect-checklist and populate results here.
-==================== END: .bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
+==================== END: bmad-core/templates/fullstack-architecture-tmpl.yaml ====================
 
-==================== START: .bmad-core/checklists/architect-checklist.md ====================
+==================== START: bmad-core/checklists/architect-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Architect Solution Validation Checklist
 
@@ -7888,9 +7888,9 @@ Now that you've completed the checklist, generate a comprehensive validation rep
    - Component design clarity
 
 After presenting the report, ask the user if they would like detailed analysis of any specific section, especially those with warnings or failures.]]
-==================== END: .bmad-core/checklists/architect-checklist.md ====================
+==================== END: bmad-core/checklists/architect-checklist.md ====================
 
-==================== START: .bmad-core/tasks/validate-next-story.md ====================
+==================== START: bmad-core/tasks/validate-next-story.md ====================
 <!-- Powered by BMAD™ Core -->
 # Validate Next Story Task
 
@@ -7902,7 +7902,7 @@ To comprehensively validate a story draft before implementation begins, ensuring
 
 ### 0. Load Core Configuration and Inputs
 
-- Load `.bmad-core/core-config.yaml`
+- Load `bmad-core/core-config.yaml`
 - If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story validation."
 - Extract key configurations: `devStoryLocation`, `prd.*`, `architecture.*`
 - Identify and load the following inputs:
@@ -8026,9 +8026,9 @@ Provide a structured validation report including:
 - **NO-GO**: Story requires fixes before implementation
 - **Implementation Readiness Score**: 1-10 scale
 - **Confidence Level**: High/Medium/Low for successful implementation
-==================== END: .bmad-core/tasks/validate-next-story.md ====================
+==================== END: bmad-core/tasks/validate-next-story.md ====================
 
-==================== START: .bmad-core/templates/story-tmpl.yaml ====================
+==================== START: bmad-core/templates/story-tmpl.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 template:
   id: story-template-v2
@@ -8167,9 +8167,9 @@ sections:
     instruction: Results from QA Agent QA review of the completed story implementation
     owner: qa-agent
     editors: [qa-agent]
-==================== END: .bmad-core/templates/story-tmpl.yaml ====================
+==================== END: bmad-core/templates/story-tmpl.yaml ====================
 
-==================== START: .bmad-core/checklists/po-master-checklist.md ====================
+==================== START: bmad-core/checklists/po-master-checklist.md ====================
 <!-- Powered by BMAD™ Core -->
 # Product Owner (PO) Master Validation Checklist
 
@@ -8603,9 +8603,9 @@ After presenting the report, ask if the user wants:
 - **APPROVED**: The plan is comprehensive, properly sequenced, and ready for implementation.
 - **CONDITIONAL**: The plan requires specific adjustments before proceeding.
 - **REJECTED**: The plan requires significant revision to address critical deficiencies.
-==================== END: .bmad-core/checklists/po-master-checklist.md ====================
+==================== END: bmad-core/checklists/po-master-checklist.md ====================
 
-==================== START: .bmad-core/workflows/greenfield-service.yaml ====================
+==================== START: bmad-core/workflows/greenfield-service.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 workflow:
   id: greenfield-service
@@ -8745,7 +8745,7 @@ workflow:
         All stories implemented and reviewed!
         Service development phase complete.
 
-        Reference: .bmad-core/data/bmad-kb.md#IDE Development Workflow
+        Reference: bmad-core/data/bmad-kb.md#IDE Development Workflow
 
   flow_diagram: |
     ```mermaid
@@ -8813,9 +8813,9 @@ workflow:
     updated_to_po: "All documents ready in docs/ folder. Please validate all artifacts for consistency."
     po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
     complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
-==================== END: .bmad-core/workflows/greenfield-service.yaml ====================
+==================== END: bmad-core/workflows/greenfield-service.yaml ====================
 
-==================== START: .bmad-core/workflows/brownfield-service.yaml ====================
+==================== START: bmad-core/workflows/brownfield-service.yaml ====================
 # <!-- Powered by BMAD™ Core -->
 workflow:
   id: brownfield-service
@@ -8947,7 +8947,7 @@ workflow:
         All stories implemented and reviewed!
         Project development phase complete.
 
-        Reference: .bmad-core/data/bmad-kb.md#IDE Development Workflow
+        Reference: bmad-core/data/bmad-kb.md#IDE Development Workflow
 
   flow_diagram: |
     ```mermaid
@@ -9004,4 +9004,4 @@ workflow:
     architect_to_po: "Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for service integration safety."
     po_issues: "PO found issues with [document]. Please return to [agent] to fix and re-save the updated document."
     complete: "All planning artifacts validated and saved in docs/ folder. Move to IDE environment to begin development."
-==================== END: .bmad-core/workflows/brownfield-service.yaml ====================
+==================== END: bmad-core/workflows/brownfield-service.yaml ====================

docs/user-guide.md

@@ -12,38 +12,38 @@ If the diagrams below don't render, install Markdown All in One along with the M
 
 ### The Planning Workflow (Web UI or Powerful IDE Agents)
 
-Before development begins, BMad follows a structured planning workflow that's ideally done in web UI for cost efficiency:
+Before development begins, BMad follows a structured planning workflow that's ideally done in web UI for cost efficiency. When loading an agent, always initialize the agent before loading anything else. This will ensure the agent loads any dependencies and is ready to assist you in the planning process. Some IDE's and web models will automatically initialize the agent for you, but if not, simply sending an arbitrary message such as a period will initialize the agent.
 
 ```mermaid
 graph TD
     A["Start: Project Idea"] --> B{"Optional: Analyst Research"}
-    B -->|Yes| C["Analyst: Brainstorming (Optional)"]
+    B -->|Yes| C["Analyst: Brainstorming (Optional)<br/>*brainstorm {topic}"]
     B -->|No| G{"Project Brief Available?"}
-    C --> C2["Analyst: Market Research (Optional)"]
-    C2 --> C3["Analyst: Competitor Analysis (Optional)"]
-    C3 --> D["Analyst: Create Project Brief"]
+    C --> C2["Analyst: Market Research (Optional)<br/>*perform-market-research"]
+    C2 --> C3["Analyst: Competitor Analysis (Optional)<br/>*create-competitor-analysis"]
+    C3 --> D["Analyst: Create Project Brief<br/>*create-project-brief"]
     D --> G
-    G -->|Yes| E["PM: Create PRD from Brief (Fast Track)"]
-    G -->|No| E2["PM: Interactive PRD Creation (More Questions)"]
+    G -->|Yes| E["PM: Create PRD from Brief (Fast Track)<br/>*create-prd"]
+    G -->|No| E2["PM: Interactive PRD Creation (More Questions)<br/>*create-prd"]
     E --> F["PRD Created with FRs, NFRs, Epics & Stories"]
     E2 --> F
     F --> F2{"UX Required?"}
-    F2 -->|Yes| F3["UX Expert: Create Front End Spec"]
-    F2 -->|No| H["Architect: Create Architecture from PRD"]
-    F3 --> F4["UX Expert: Generate UI Prompt for Lovable/V0 (Optional)"]
-    F4 --> H2["Architect: Create Architecture from PRD + UX Spec"]
+    F2 -->|Yes| F3["UX Expert: Create Front End Spec<br/>*create-front-end-spec"]
+    F2 -->|No| H["Architect: Create Architecture from PRD<br/>*create-full-stack-architecture"]
+    F3 --> F4["UX Expert: Generate UI Prompt for Lovable/V0 (Optional)<br/>*generate-ui-prompt"]
+    F4 --> H2["Architect: Create Architecture from PRD + UX Spec<br/>*create-full-stack-architecture"]
     H --> Q{"Early Test Strategy? (Optional)"}
     H2 --> Q
-    Q -->|Yes| R["QA: Early Test Architecture Input on High-Risk Areas"]
+    Q -->|Yes| R["QA: Early Test Architecture Input on High-Risk Areas<br/>*risk-profile + *test-design"]
     Q -->|No| I
-    R --> I["PO: Run Master Checklist"]
+    R --> I["PO: Run Master Checklist<br/>*execute-checklist-po"]
     I --> J{"Documents Aligned?"}
     J -->|Yes| K["Planning Complete"]
-    J -->|No| L["PO: Update Epics & Stories"]
+    J -->|No| L["PO: Update Epics & Stories<br/>*create-epic/*create-story"]
     L --> M["Update PRD/Architecture as needed"]
     M --> I
     K --> N["📁 Switch to IDE (If in a Web Agent Platform)"]
-    N --> O["PO: Shard Documents"]
+    N --> O["PO: Shard Documents<br/>*shard-doc {document} {destination}"]
     O --> P["Ready for SM/Dev Cycle"]
 
     style A fill:#f5f5f5,color:#000
@@ -100,35 +100,36 @@ Once planning is complete and documents are sharded, BMad follows a structured d
 ```mermaid
 graph TD
     A["Development Phase Start"] --> B["SM: Reviews Previous Story Dev/QA Notes"]
-    B --> B2["SM: Drafts Next Story from Sharded Epic + Architecture"]
+    B --> B2["SM: Drafts Next Story from Sharded Epic + Architecture<br/>*draft"]
     B2 --> S{"High-Risk Story? (Optional)"}
     S -->|Yes| T["QA: *risk + *design on Draft Story"]
     S -->|No| B3
     T --> U["Test Strategy & Risk Profile Created"]
     U --> B3{"PO: Validate Story Draft (Optional)"}
-    B3 -->|Validation Requested| B4["PO: Validate Story Against Artifacts"]
+    B3 -->|Validation Requested| B4["PO: Validate Story Against Artifacts<br/>*validate-story-draft {story}"]
     B3 -->|Skip Validation| C{"User Approval"}
     B4 --> C
     C -->|Approved| D["Dev: Sequential Task Execution"]
     C -->|Needs Changes| B2
-    D --> E["Dev: Implement Tasks + Tests"]
+    D --> E["Dev: Implement Tasks + Tests<br/>*develop-story"]
     E --> V{"Mid-Dev QA Check? (Optional)"}
-    V -->|Yes| W["QA: *trace or *nfr for Early Validation"]
+    V -->|Yes| W["QA: Early Validation<br/>*trace or *nfr-assess"]
     V -->|No| F
-    W --> X["Dev: Address Coverage/NFR Gaps"]
-    X --> F["Dev: Run All Validations"]
+    W --> X["Dev: Address Coverage/NFR Gaps<br/>*review-qa"]
+    X --> F["Dev: Run All Validations<br/>*run-tests"]
     F --> G["Dev: Mark Ready for Review + Add Notes"]
     G --> H{"User Verification"}
     H -->|Request QA Review| I["QA: Test Architect Review + Quality Gate"]
     H -->|Approve Without QA| M["IMPORTANT: Verify All Regression Tests and Linting are Passing"]
-    I --> J["QA: Test Architecture Analysis + Active Refactoring"]
+    I --> J["QA: Test Architecture Analysis + Active Refactoring<br/>*review {story}"]
     J --> L{"QA Decision"}
-    L -->|Needs Dev Work| D
+    L -->|Needs Dev Work| D2["Dev: Apply QA Fixes<br/>*review-qa"]
+    D2 --> M
     L -->|Approved| M
     H -->|Needs Fixes| D
     M --> N["IMPORTANT: COMMIT YOUR CHANGES BEFORE PROCEEDING!"]
     N --> Y{"Gate Update Needed?"}
-    Y -->|Yes| Z["QA: *gate to Update Status"]
+    Y -->|Yes| Z["QA: Update Gate Status<br/>*gate {story}"]
     Y -->|No| K
     Z --> K["Mark Story as Done"]
     K --> B
@@ -187,32 +188,6 @@ If you want to do the planning on the web with Claude (Sonnet 4 or Opus), Gemini
 npx bmad-method install
 ```
 
-### Codex (CLI & Web)
-
-BMAD integrates with OpenAI Codex via `AGENTS.md` and committed core agent files.
-
-- Two installation modes:
-  - Codex (local only): keeps `.bmad-core/` ignored for local dev.
-    - `npx bmad-method install -f -i codex -d .`
-  - Codex Web Enabled: ensures `.bmad-core/` is tracked so you can commit it for Codex Web.
-    - `npx bmad-method install -f -i codex-web -d .`
-
-- What gets generated:
-  - `AGENTS.md` at the project root with a BMAD section containing
-    - How-to-use with Codex (CLI & Web)
-    - Agent Directory (Title, ID, When To Use)
-    - Detailed per‑agent sections with source path, when-to-use, activation phrasing, and YAML
-    - Tasks with quick usage notes
-  - If a `package.json` exists, helpful scripts are added:
-    - `bmad:refresh`, `bmad:list`, `bmad:validate`
-
-- Using Codex:
-  - CLI: run `codex` in the project root and prompt naturally, e.g., “As dev, implement …”.
-  - Web: commit `.bmad-core/` and `AGENTS.md`, then open the repo in Codex and prompt the same way.
-
-- Refresh after changes:
-  - Re-run the appropriate install mode (`codex` or `codex-web`) to update the BMAD block in `AGENTS.md`.
-
 ## Special Agents
 
 There are two BMad agents — in the future they'll be consolidated into a single BMad-Master.
@@ -493,7 +468,7 @@ Quick reference for where Test Architect outputs are stored:
 
 ## Technical Preferences System
 
-BMad includes a personalization system through the `technical-preferences.md` file located in `.bmad-core/data/` - this can help bias the PM and Architect to recommend your preferences for design patterns, technology selection, or anything else you would like to put in here.
+BMad includes a personalization system through the `technical-preferences.md` file located in `bmad-core/data/` - this can help bias the PM and Architect to recommend your preferences for design patterns, technology selection, or anything else you would like to put in here.
 
 ### Using with Web Bundles
 

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

@@ -132,7 +132,7 @@ npx bmad-method install
 
 **Verify Game Development Installation**:
 
-- `.bmad-core/` folder created with all core agents
+- `bmad-core/` folder created with all core agents
 - `.bmad-2d-unity-game-dev/` folder with game development agents
 - IDE-specific integration files created
 - Game development agents available with `/bmad2du` prefix (per config.yaml)

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

@@ -76,7 +76,7 @@ node tools/install-expansion-pack.js infrastructure
 
 This will:
 
-1. Copy all files to their appropriate locations in `.bmad-core/`
+1. Copy all files to their appropriate locations in `bmad-core/`
 2. Update any necessary configurations
 3. Make the DevOps agent available in teams
 

implement-fork-friendly-ci.sh

@@ -1,229 +0,0 @@
-#!/bin/bash
-
-# Fork-Friendly CI/CD Implementation Script
-# Usage: ./implement-fork-friendly-ci.sh
-# 
-# This script automates the implementation of fork-friendly CI/CD
-# by adding fork detection conditions to all GitHub Actions workflows
-
-set -e
-
-echo "🚀 Implementing Fork-Friendly CI/CD..."
-
-# Colors for output
-RED='\033[0;31m'
-GREEN='\033[0;32m'
-YELLOW='\033[1;33m'
-NC='\033[0m' # No Color
-
-# 1. Check if .github/workflows directory exists
-if [ ! -d ".github/workflows" ]; then
-    echo -e "${RED}✗${NC} No .github/workflows directory found"
-    echo "This script must be run from the repository root"
-    exit 1
-fi
-
-# 2. Backup existing workflows
-echo "📦 Backing up workflows..."
-backup_dir=".github/workflows.backup.$(date +%Y%m%d_%H%M%S)"
-cp -r .github/workflows "$backup_dir"
-echo -e "${GREEN}✓${NC} Workflows backed up to $backup_dir"
-
-# 3. Count workflow files and jobs
-WORKFLOW_COUNT=$(ls -1 .github/workflows/*.yml .github/workflows/*.yaml 2>/dev/null | wc -l)
-echo "📊 Found ${WORKFLOW_COUNT} workflow files"
-
-# 4. Process each workflow file
-UPDATED_FILES=0
-MANUAL_REVIEW_NEEDED=0
-
-for file in .github/workflows/*.yml .github/workflows/*.yaml; do
-    if [ -f "$file" ]; then
-        filename=$(basename "$file")
-        echo -n "Processing ${filename}... "
-        
-        # Create temporary file
-        temp_file="${file}.tmp"
-        
-        # Track if file needs manual review
-        needs_review=0
-        
-        # Process the file with awk
-        awk '
-        BEGIN {
-            in_jobs = 0
-            job_count = 0
-            modified = 0
-        }
-        
-        /^jobs:/ { 
-            in_jobs = 1
-            print
-            next
-        }
-        
-        # Match job definitions (2 spaces + name + colon)
-        in_jobs && /^  [a-z][a-z0-9_-]*:/ {
-            job_name = $0
-            print job_name
-            job_count++
-            
-            # Look ahead for existing conditions
-            getline next_line
-            
-            # Check if next line is already an if condition
-            if (next_line ~ /^    if:/) {
-                # Job already has condition - combine with fork detection
-                existing_condition = next_line
-                sub(/^    if: /, "", existing_condition)
-                
-                # Check if fork condition already exists
-                if (existing_condition !~ /github\.event\.repository\.fork/) {
-                    print "    # Fork-friendly CI: Combined with existing condition"
-                    print "    if: (" existing_condition ") && (github.event.repository.fork != true || vars.ENABLE_CI_IN_FORK == '\''true'\'')"
-                    modified++
-                } else {
-                    # Already has fork detection
-                    print next_line
-                }
-            } else if (next_line ~ /^    runs-on:/) {
-                # No condition exists, add before runs-on
-                print "    if: github.event.repository.fork != true || vars.ENABLE_CI_IN_FORK == '\''true'\''"
-                print next_line
-                modified++
-            } else {
-                # Some other configuration, preserve as-is
-                print next_line
-            }
-            next
-        }
-        
-        # Reset when leaving jobs section
-        /^[a-z]/ && in_jobs {
-            in_jobs = 0
-        }
-        
-        # Print all other lines
-        { 
-            if (!in_jobs) print 
-        }
-        
-        END {
-            if (modified > 0) {
-                exit 0  # Success - file was modified
-            } else {
-                exit 1  # No modifications needed
-            }
-        }
-        ' "$file" > "$temp_file"
-        
-        # Check if modifications were made
-        if [ $? -eq 0 ]; then
-            mv "$temp_file" "$file"
-            echo -e "${GREEN}✓${NC} Updated"
-            ((UPDATED_FILES++))
-        else
-            rm -f "$temp_file"
-            echo -e "${YELLOW}○${NC} No changes needed"
-        fi
-        
-        # Check for complex conditions that might need manual review
-        if grep -q "needs:" "$file" || grep -q "strategy:" "$file"; then
-            echo "  ⚠️  Complex workflow detected - manual review recommended"
-            ((MANUAL_REVIEW_NEEDED++))
-        fi
-    fi
-done
-
-echo -e "${GREEN}✓${NC} Updated ${UPDATED_FILES} workflow files"
-
-# 5. Create Fork Guide if it doesn't exist
-if [ ! -f ".github/FORK_GUIDE.md" ]; then
-    echo "📝 Creating Fork Guide documentation..."
-    cat > .github/FORK_GUIDE.md << 'EOF'
-# Fork Guide - CI/CD Configuration
-
-## CI/CD in Forks
-
-By default, CI/CD workflows are **disabled in forks** to conserve GitHub Actions resources.
-
-### Enabling CI/CD in Your Fork
-
-If you need to run CI/CD workflows in your fork:
-
-1. Navigate to **Settings** → **Secrets and variables** → **Actions** → **Variables**
-2. Click **New repository variable**
-3. Create variable:
-   - **Name**: `ENABLE_CI_IN_FORK`
-   - **Value**: `true`
-4. Click **Add variable**
-
-### Disabling CI/CD Again
-
-Either:
-- Delete the `ENABLE_CI_IN_FORK` variable, or
-- Set its value to `false`
-
-### Alternative Testing Options
-
-- **Local testing**: Run tests locally before pushing
-- **Pull Request CI**: Workflows automatically run when you open a PR
-- **GitHub Codespaces**: Full development environment
-EOF
-    echo -e "${GREEN}✓${NC} Fork Guide created"
-else
-    echo "ℹ️  Fork Guide already exists"
-fi
-
-# 6. Validate YAML files (if yamllint is available)
-if command -v yamllint &> /dev/null; then
-    echo "🔍 Validating YAML syntax..."
-    VALIDATION_ERRORS=0
-    for file in .github/workflows/*.yml .github/workflows/*.yaml; do
-        if [ -f "$file" ]; then
-            filename=$(basename "$file")
-            if yamllint -d relaxed "$file" &>/dev/null; then
-                echo -e "  ${GREEN}✓${NC} ${filename}"
-            else
-                echo -e "  ${RED}✗${NC} ${filename} - YAML validation failed"
-                ((VALIDATION_ERRORS++))
-            fi
-        fi
-    done
-    
-    if [ $VALIDATION_ERRORS -gt 0 ]; then
-        echo -e "${YELLOW}⚠${NC}  ${VALIDATION_ERRORS} files have YAML errors"
-    fi
-else
-    echo "ℹ️  yamllint not found - skipping YAML validation"
-    echo "  Install with: pip install yamllint"
-fi
-
-# 7. Summary
-echo ""
-echo "═══════════════════════════════════════"
-echo "       Fork-Friendly CI/CD Summary"
-echo "═══════════════════════════════════════"
-echo "  📁 Files updated: ${UPDATED_FILES}"
-echo "  📊 Total workflows: ${WORKFLOW_COUNT}"
-echo "  📝 Fork Guide: .github/FORK_GUIDE.md"
-if [ $MANUAL_REVIEW_NEEDED -gt 0 ]; then
-    echo "  ⚠️  Files needing review: ${MANUAL_REVIEW_NEEDED}"
-fi
-echo ""
-echo "Next steps:"
-echo "1. Review the changes: git diff"
-echo "2. Test workflows locally (if possible)"
-echo "3. Commit changes: git commit -m 'feat: implement fork-friendly CI/CD'"
-echo "4. Push and create PR"
-echo ""
-echo "Remember to update README.md with fork information!"
-echo "═══════════════════════════════════════"
-
-# Exit with appropriate code
-if [ $UPDATED_FILES -gt 0 ]; then
-    exit 0
-else
-    echo "No files were updated - workflows may already be fork-friendly"
-    exit 1
-fi

package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "4.40.1",
+  "version": "4.39.1",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",
@@ -27,7 +27,6 @@
     "build": "node tools/cli.js build",
     "build:agents": "node tools/cli.js build --agents-only",
     "build:teams": "node tools/cli.js build --teams-only",
-    "fix": "npm run format && npm run lint:fix",
     "flatten": "node tools/flattener/main.js",
     "format": "prettier --write \"**/*.{js,cjs,mjs,json,md,yaml}\"",
     "format:check": "prettier --check \"**/*.{js,cjs,mjs,json,md,yaml}\"",
@@ -35,14 +34,12 @@
     "lint": "eslint . --ext .js,.cjs,.mjs,.yaml --max-warnings=0",
     "lint:fix": "eslint . --ext .js,.cjs,.mjs,.yaml --fix",
     "list:agents": "node tools/cli.js list:agents",
-    "pre-release": "npm run validate && npm run format:check && npm run lint",
     "prepare": "husky",
     "preview:release": "node tools/preview-release-notes.js",
     "release:major": "gh workflow run \"Manual Release\" -f version_bump=major",
     "release:minor": "gh workflow run \"Manual Release\" -f version_bump=minor",
     "release:patch": "gh workflow run \"Manual Release\" -f version_bump=patch",
     "release:watch": "gh run watch",
-    "setup:hooks": "chmod +x tools/setup-hooks.sh && ./tools/setup-hooks.sh",
     "validate": "node tools/cli.js validate",
     "version:all": "node tools/bump-all-versions.js",
     "version:all:major": "node tools/bump-all-versions.js major",
@@ -72,33 +69,31 @@
     ]
   },
   "dependencies": {
-    "@kayvan/markdown-tree-parser": "^1.6.1",
+    "@kayvan/markdown-tree-parser": "^1.5.0",
+    "bmad-method": "^4.30.3",
     "chalk": "^4.1.2",
     "commander": "^14.0.0",
-    "fs-extra": "^11.3.1",
+    "fs-extra": "^11.3.0",
     "glob": "^11.0.3",
     "ignore": "^7.0.5",
     "inquirer": "^8.2.6",
     "js-yaml": "^4.1.0",
     "ora": "^5.4.1",
-    "semver": "^7.7.2"
+    "semver": "^7.6.3"
   },
   "devDependencies": {
-    "@eslint/js": "^9.34.0",
-    "@semantic-release/changelog": "6.0.3",
-    "@semantic-release/git": "^10.0.1",
-    "eslint": "^9.34.0",
+    "@eslint/js": "^9.33.0",
+    "eslint": "^9.33.0",
     "eslint-config-prettier": "^10.1.8",
     "eslint-plugin-n": "^17.21.3",
     "eslint-plugin-unicorn": "^60.0.0",
     "eslint-plugin-yml": "^1.18.0",
     "husky": "^9.1.7",
-    "jest": "^30.0.5",
-    "lint-staged": "^16.1.5",
-    "prettier": "^3.6.2",
+    "jest": "^30.0.4",
+    "lint-staged": "^16.1.1",
+    "prettier": "^3.5.3",
     "prettier-plugin-packagejson": "^2.5.19",
-    "semantic-release": "24.2.7",
-    "yaml-eslint-parser": "^1.3.0",
+    "yaml-eslint-parser": "^1.2.3",
     "yaml-lint": "^1.7.0"
   },
   "engines": {

test.md

@@ -1 +0,0 @@
-# Test

tools/builders/web-builder.js

@@ -41,22 +41,22 @@ class WebBuilder {
 
   generateWebInstructions(bundleType, packName = null) {
     // Generate dynamic web instructions based on bundle type
-    const rootExample = packName ? `.${packName}` : '.bmad-core';
+    const rootExample = packName ? `.${packName}` : 'bmad-core';
     const examplePath = packName
       ? `.${packName}/folder/filename.md`
-      : '.bmad-core/folder/filename.md';
+      : 'bmad-core/folder/filename.md';
     const personasExample = packName
       ? `.${packName}/personas/analyst.md`
-      : '.bmad-core/personas/analyst.md';
+      : 'bmad-core/personas/analyst.md';
     const tasksExample = packName
       ? `.${packName}/tasks/create-story.md`
-      : '.bmad-core/tasks/create-story.md';
+      : 'bmad-core/tasks/create-story.md';
     const utilitiesExample = packName
       ? `.${packName}/utils/template-format.md`
-      : '.bmad-core/utils/template-format.md';
+      : 'bmad-core/utils/template-format.md';
     const tasksReference = packName
       ? `.${packName}/tasks/create-story.md`
-      : '.bmad-core/tasks/create-story.md';
+      : 'bmad-core/tasks/create-story.md';
 
     return `# Web Agent Bundle Instructions
 

tools/flattener/ignoreRules.js

@@ -6,7 +6,7 @@ const ignore = require('ignore');
 // These complement .gitignore and are applied regardless of VCS presence.
 const DEFAULT_PATTERNS = [
   // Project/VCS
-  '**/.bmad-core/**',
+  '**/bmad-core/**',
   '**/.git/**',
   '**/.svn/**',
   '**/.hg/**',

tools/flattener/main.js

@@ -115,6 +115,11 @@ program
           path.join(inputDir, 'flattened-codebase.xml'),
         );
       }
+    } else {
+      console.error(
+        'Could not auto-detect a project root and no arguments were provided. Please specify -i/--input and -o/--output.',
+      );
+      process.exit(1);
     }
 
     // Ensure output directory exists

tools/installer/bin/bmad.js

@@ -49,7 +49,7 @@ program
   .option('-d, --directory <path>', 'Installation directory')
   .option(
     '-i, --ide <ide...>',
-    'Configure for specific IDE(s) - can specify multiple (cursor, claude-code, windsurf, trae, roo, kilo, cline, gemini, qwen-code, github-copilot, codex, codex-web, other)',
+    'Configure for specific IDE(s) - can specify multiple (cursor, claude-code, windsurf, trae, roo, kilo, cline, gemini, qwen-code, github-copilot, other)',
   )
   .option(
     '-e, --expansion-packs <packs...>',
@@ -254,9 +254,9 @@ async function promptInstallation() {
       currentVersion === newVersion
         ? `(v${currentVersion} - reinstall)`
         : `(v${currentVersion} → v${newVersion})`;
-    bmadOptionText = `Update ${coreShortTitle} ${versionInfo} .bmad-core`;
+    bmadOptionText = `Update ${coreShortTitle} ${versionInfo} bmad-core`;
   } else {
-    bmadOptionText = `${coreShortTitle} (v${version}) .bmad-core`;
+    bmadOptionText = `${coreShortTitle} (v${version}) bmad-core`;
   }
 
   choices.push({

tools/installer/config/install.config.yaml

@@ -1,7 +1,7 @@
 installation-options:
   full:
     name: Complete BMad Core
-    description: Copy the entire .bmad-core folder with all agents, templates, and tools
+    description: Copy the entire bmad-core folder with all agents, templates, and tools
     action: copy-folder
     source: bmad-core
   single-agent:
@@ -121,25 +121,3 @@ ide-configurations:
       # 2. It concatenates all agent files into a single QWEN.md file.
       # 3. Simply mention the agent in your prompt (e.g., "As *dev, ...").
       # 4. The Qwen Code CLI will automatically have the context for that agent.
-
-  codex:
-    name: Codex CLI
-    format: project-memory
-    file: AGENTS.md
-    instructions: |
-      # To use BMAD agents with Codex CLI:
-      # 1. The installer updates/creates AGENTS.md at your project root with BMAD agents and tasks.
-      # 2. Run `codex` in your project. Codex automatically reads AGENTS.md as project memory.
-      # 3. Mention agents in your prompt (e.g., "As dev, please implement ...") or reference tasks.
-      # 4. You can further customize global Codex behavior via ~/.codex/config.toml.
-
-  codex-web:
-    name: Codex Web Enabled
-    format: project-memory
-    file: AGENTS.md
-    instructions: |
-      # To enable BMAD agents for Codex Web (cloud):
-      # 1. The installer updates/creates AGENTS.md and ensures `.bmad-core` is NOT ignored by git.
-      # 2. Commit `.bmad-core/` and `AGENTS.md` to your repository.
-      # 3. Open the repo in Codex Web and reference agents naturally (e.g., "As dev, ...").
-      # 4. Re-run this installer to refresh agent sections when the core changes.

tools/installer/lib/config-loader.js

@@ -148,7 +148,7 @@ class ConfigLoader {
 
     // Add all resolved resources
     for (const resource of agentDeps.resources) {
-      const filePath = `.bmad-core/${resource.type}/${resource.id}.md`;
+      const filePath = `bmad-core/${resource.type}/${resource.id}.md`;
       if (!depPaths.includes(filePath)) {
         depPaths.push(filePath);
       }
@@ -229,11 +229,11 @@ class ConfigLoader {
       const depPaths = [];
 
       // Add team config file
-      depPaths.push(`.bmad-core/agent-teams/${teamId}.yaml`);
+      depPaths.push(`bmad-core/agent-teams/${teamId}.yaml`);
 
       // Add all agents
       for (const agent of teamDeps.agents) {
-        const filePath = `.bmad-core/agents/${agent.id}.md`;
+        const filePath = `bmad-core/agents/${agent.id}.md`;
         if (!depPaths.includes(filePath)) {
           depPaths.push(filePath);
         }
@@ -241,7 +241,7 @@ class ConfigLoader {
 
       // Add all resolved resources
       for (const resource of teamDeps.resources) {
-        const filePath = `.bmad-core/${resource.type}/${resource.id}.${resource.type === 'workflows' ? 'yaml' : 'md'}`;
+        const filePath = `bmad-core/${resource.type}/${resource.id}.${resource.type === 'workflows' ? 'yaml' : 'md'}`;
         if (!depPaths.includes(filePath)) {
           depPaths.push(filePath);
         }

tools/installer/lib/file-manager.js

@@ -272,7 +272,7 @@ class FileManager {
   }
 
   async modifyCoreConfig(installDir, config) {
-    const coreConfigPath = path.join(installDir, '.bmad-core', 'core-config.yaml');
+    const coreConfigPath = path.join(installDir, 'bmad-core', 'core-config.yaml');
 
     try {
       // Read the existing core-config.yaml
@@ -382,7 +382,7 @@ class FileManager {
       return false;
     }
   }
-  manifestDir = '.bmad-core';
+  manifestDir = 'bmad-core';
   manifestFile = 'install-manifest.yaml';
 }
 

tools/installer/lib/ide-base-setup.js

@@ -50,7 +50,7 @@ class BaseIdeSetup {
   async getCoreAgentIds(installDir) {
     const coreAgents = [];
     const corePaths = [
-      path.join(installDir, '.bmad-core', 'agents'),
+      path.join(installDir, 'bmad-core', 'agents'),
       path.join(installDir, 'bmad-core', 'agents'),
     ];
 
@@ -80,7 +80,7 @@ class BaseIdeSetup {
     if (!agentPath) {
       // Check installation-specific paths
       const possiblePaths = [
-        path.join(installDir, '.bmad-core', 'agents', `${agentId}.md`),
+        path.join(installDir, 'bmad-core', 'agents', `${agentId}.md`),
         path.join(installDir, 'bmad-core', 'agents', `${agentId}.md`),
         path.join(installDir, 'common', 'agents', `${agentId}.md`),
       ];
@@ -134,7 +134,7 @@ class BaseIdeSetup {
     const dotExpansions = await resourceLocator.findFiles('.bmad-*', { cwd: installDir });
 
     for (const dotExpansion of dotExpansions) {
-      if (dotExpansion !== '.bmad-core') {
+      if (dotExpansion !== 'bmad-core') {
         const packPath = path.join(installDir, dotExpansion);
         const packName = dotExpansion.slice(1); // remove the dot
         expansionPacks.push({
@@ -147,7 +147,7 @@ class BaseIdeSetup {
     // Check other dot folders that have config.yaml
     const allDotFolders = await resourceLocator.findFiles('.*', { cwd: installDir });
     for (const folder of allDotFolders) {
-      if (!folder.startsWith('.bmad-') && folder !== '.bmad-core') {
+      if (!folder.startsWith('.bmad-') && folder !== 'bmad-core') {
         const packPath = path.join(installDir, folder);
         const configPath = path.join(packPath, 'config.yaml');
         if (await fileManager.pathExists(configPath)) {

tools/installer/lib/ide-setup.js

@@ -74,12 +74,6 @@ class IdeSetup extends BaseIdeSetup {
       case 'qwen-code': {
         return this.setupQwenCode(installDir, selectedAgent);
       }
-      case 'codex': {
-        return this.setupCodex(installDir, selectedAgent, { webEnabled: false });
-      }
-      case 'codex-web': {
-        return this.setupCodex(installDir, selectedAgent, { webEnabled: true });
-      }
       default: {
         console.log(chalk.yellow(`\nIDE ${ide} not yet supported`));
         return false;
@@ -87,175 +81,6 @@ class IdeSetup extends BaseIdeSetup {
     }
   }
 
-  async setupCodex(installDir, selectedAgent, options) {
-    options = options ?? { webEnabled: false };
-    // Codex reads AGENTS.md at the project root as project memory (CLI & Web).
-    // Inject/update a BMAD section with guidance, directory, and details.
-    const filePath = path.join(installDir, 'AGENTS.md');
-    const startMarker = '<!-- BEGIN: BMAD-AGENTS -->';
-    const endMarker = '<!-- END: BMAD-AGENTS -->';
-
-    const agents = selectedAgent ? [selectedAgent] : await this.getAllAgentIds(installDir);
-    const tasks = await this.getAllTaskIds(installDir);
-
-    // Build BMAD section content
-    let section = '';
-    section += `${startMarker}\n`;
-    section += `# BMAD-METHOD Agents and Tasks\n\n`;
-    section += `This section is auto-generated by BMAD-METHOD for Codex. Codex merges this AGENTS.md into context.\n\n`;
-    section += `## How To Use With Codex\n\n`;
-    section += `- Codex CLI: run \`codex\` in this project. Reference an agent naturally, e.g., "As dev, implement ...".\n`;
-    section += `- Codex Web: open this repo and reference roles the same way; Codex reads \`AGENTS.md\`.\n`;
-    section += `- Commit \`.bmad-core\` and this \`AGENTS.md\` file to your repo so Codex (Web/CLI) can read full agent definitions.\n`;
-    section += `- Refresh this section after agent updates: \`npx bmad-method install -f -i codex\`.\n\n`;
-
-    section += `### Helpful Commands\n\n`;
-    section += `- List agents: \`npx bmad-method list:agents\`\n`;
-    section += `- Reinstall BMAD core and regenerate AGENTS.md: \`npx bmad-method install -f -i codex\`\n`;
-    section += `- Validate configuration: \`npx bmad-method validate\`\n\n`;
-
-    // Agents directory table
-    section += `## Agents\n\n`;
-    section += `### Directory\n\n`;
-    section += `| Title | ID | When To Use |\n|---|---|---|\n`;
-    const agentSummaries = [];
-    for (const agentId of agents) {
-      const agentPath = await this.findAgentPath(agentId, installDir);
-      if (!agentPath) continue;
-      const raw = await fileManager.readFile(agentPath);
-      const yamlMatch = raw.match(/```ya?ml\r?\n([\s\S]*?)```/);
-      const yamlBlock = yamlMatch ? yamlMatch[1].trim() : null;
-      const title = await this.getAgentTitle(agentId, installDir);
-      const whenToUse = yamlBlock?.match(/whenToUse:\s*"?([^\n"]+)"?/i)?.[1]?.trim() || '';
-      agentSummaries.push({ agentId, title, whenToUse, yamlBlock, raw, path: agentPath });
-      section += `| ${title} | ${agentId} | ${whenToUse || '—'} |\n`;
-    }
-    section += `\n`;
-
-    // Detailed agent sections
-    for (const { agentId, title, whenToUse, yamlBlock, raw, path: agentPath } of agentSummaries) {
-      const relativePath = path.relative(installDir, agentPath).replaceAll('\\', '/');
-      section += `### ${title} (id: ${agentId})\n`;
-      section += `Source: ${relativePath}\n\n`;
-      if (whenToUse) section += `- When to use: ${whenToUse}\n`;
-      section += `- How to activate: Mention "As ${agentId}, ..." or "Use ${title} to ..."\n\n`;
-      if (yamlBlock) {
-        section += '```yaml\n' + yamlBlock + '\n```\n\n';
-      } else {
-        section += '```md\n' + raw.trim() + '\n```\n\n';
-      }
-    }
-
-    // Tasks
-    if (tasks && tasks.length > 0) {
-      section += `## Tasks\n\n`;
-      section += `These are reusable task briefs you can reference directly in Codex.\n\n`;
-      for (const taskId of tasks) {
-        const taskPath = await this.findTaskPath(taskId, installDir);
-        if (!taskPath) continue;
-        const raw = await fileManager.readFile(taskPath);
-        const relativePath = path.relative(installDir, taskPath).replaceAll('\\', '/');
-        section += `### Task: ${taskId}\n`;
-        section += `Source: ${relativePath}\n`;
-        section += `- How to use: "Use task ${taskId} with the appropriate agent" and paste relevant parts as needed.\n\n`;
-        section += '```md\n' + raw.trim() + '\n```\n\n';
-      }
-    }
-
-    section += `${endMarker}\n`;
-
-    // Write or update AGENTS.md
-    let finalContent = '';
-    if (await fileManager.pathExists(filePath)) {
-      const existing = await fileManager.readFile(filePath);
-      if (existing.includes(startMarker) && existing.includes(endMarker)) {
-        // Replace existing BMAD block
-        const pattern = String.raw`${startMarker}[\s\S]*?${endMarker}`;
-        const replaced = existing.replace(new RegExp(pattern, 'm'), section);
-        finalContent = replaced;
-      } else {
-        // Append BMAD block to existing file
-        finalContent = existing.trimEnd() + `\n\n` + section;
-      }
-    } else {
-      // Create fresh AGENTS.md with a small header and BMAD block
-      finalContent += '# Project Agents\n\n';
-      finalContent += 'This file provides guidance and memory for Codex CLI.\n\n';
-      finalContent += section;
-    }
-
-    await fileManager.writeFile(filePath, finalContent);
-    console.log(chalk.green('✓ Created/updated AGENTS.md for Codex CLI integration'));
-    console.log(
-      chalk.dim(
-        'Codex reads AGENTS.md automatically. Run `codex` in this project to use BMAD agents.',
-      ),
-    );
-
-    // Optionally add helpful npm scripts if a package.json exists
-    try {
-      const pkgPath = path.join(installDir, 'package.json');
-      if (await fileManager.pathExists(pkgPath)) {
-        const pkgRaw = await fileManager.readFile(pkgPath);
-        const pkg = JSON.parse(pkgRaw);
-        pkg.scripts = pkg.scripts || {};
-        const updated = { ...pkg.scripts };
-        if (!updated['bmad:refresh']) updated['bmad:refresh'] = 'bmad-method install -f -i codex';
-        if (!updated['bmad:list']) updated['bmad:list'] = 'bmad-method list:agents';
-        if (!updated['bmad:validate']) updated['bmad:validate'] = 'bmad-method validate';
-        const changed = JSON.stringify(updated) !== JSON.stringify(pkg.scripts);
-        if (changed) {
-          const newPkg = { ...pkg, scripts: updated };
-          await fileManager.writeFile(pkgPath, JSON.stringify(newPkg, null, 2) + '\n');
-          console.log(chalk.green('✓ Added npm scripts: bmad:refresh, bmad:list, bmad:validate'));
-        }
-      }
-    } catch {
-      console.log(
-        chalk.yellow('⚠︎ Skipped adding npm scripts (package.json not writable or invalid)'),
-      );
-    }
-
-    // Adjust .gitignore behavior depending on Codex mode
-    try {
-      const gitignorePath = path.join(installDir, '.gitignore');
-      const ignoreLines = ['# BMAD (local only)', '.bmad-core/', '.bmad-*/'];
-      const exists = await fileManager.pathExists(gitignorePath);
-      if (options.webEnabled) {
-        if (exists) {
-          let gi = await fileManager.readFile(gitignorePath);
-          // Remove lines that ignore BMAD dot-folders
-          const updated = gi
-            .split(/\r?\n/)
-            .filter((l) => !/^\s*\.bmad-core\/?\s*$/.test(l) && !/^\s*\.bmad-\*\/?\s*$/.test(l))
-            .join('\n');
-          if (updated !== gi) {
-            await fileManager.writeFile(gitignorePath, updated.trimEnd() + '\n');
-            console.log(chalk.green('✓ Updated .gitignore to include .bmad-core in commits'));
-          }
-        }
-      } else {
-        // Local-only: add ignores if missing
-        let base = exists ? await fileManager.readFile(gitignorePath) : '';
-        const haveCore = base.includes('.bmad-core/');
-        const haveStar = base.includes('.bmad-*/');
-        if (!haveCore || !haveStar) {
-          const sep = base.endsWith('\n') || base.length === 0 ? '' : '\n';
-          const add = [!haveCore || !haveStar ? ignoreLines.join('\n') : '']
-            .filter(Boolean)
-            .join('\n');
-          const out = base + sep + add + '\n';
-          await fileManager.writeFile(gitignorePath, out);
-          console.log(chalk.green('✓ Added .bmad-core/* to .gitignore for local-only Codex setup'));
-        }
-      }
-    } catch {
-      console.log(chalk.yellow('⚠︎ Could not update .gitignore (skipping)'));
-    }
-
-    return true;
-  }
-
   async setupCursor(installDir, selectedAgent) {
     const cursorRulesDir = path.join(installDir, '.cursor', 'rules', 'bmad');
     const agents = selectedAgent ? [selectedAgent] : await this.getAllAgentIds(installDir);
@@ -288,7 +113,7 @@ class IdeSetup extends BaseIdeSetup {
       coreSlashPrefix,
       coreAgents,
       coreTasks,
-      '.bmad-core',
+      'bmad-core',
     );
 
     // Setup expansion pack commands
@@ -326,7 +151,7 @@ class IdeSetup extends BaseIdeSetup {
       coreSlashPrefix,
       coreAgents,
       coreTasks,
-      '.bmad-core',
+      'bmad-core',
     );
 
     // Setup expansion pack commands
@@ -620,7 +445,7 @@ class IdeSetup extends BaseIdeSetup {
   async findAgentPath(agentId, installDir) {
     // Try to find the agent file in various locations
     const possiblePaths = [
-      path.join(installDir, '.bmad-core', 'agents', `${agentId}.md`),
+      path.join(installDir, 'bmad-core', 'agents', `${agentId}.md`),
       path.join(installDir, 'agents', `${agentId}.md`),
     ];
 
@@ -644,8 +469,8 @@ class IdeSetup extends BaseIdeSetup {
     const glob = require('glob');
     const allAgentIds = [];
 
-    // Check core agents in .bmad-core or root
-    let agentsDir = path.join(installDir, '.bmad-core', 'agents');
+    // Check core agents in bmad-core or root
+    let agentsDir = path.join(installDir, 'bmad-core', 'agents');
     if (!(await fileManager.pathExists(agentsDir))) {
       agentsDir = path.join(installDir, 'agents');
     }
@@ -670,8 +495,8 @@ class IdeSetup extends BaseIdeSetup {
   async getCoreAgentIds(installDir) {
     const allAgentIds = [];
 
-    // Check core agents in .bmad-core or root only
-    let agentsDir = path.join(installDir, '.bmad-core', 'agents');
+    // Check core agents in bmad-core or root only
+    let agentsDir = path.join(installDir, 'bmad-core', 'agents');
     if (!(await fileManager.pathExists(agentsDir))) {
       agentsDir = path.join(installDir, 'bmad-core', 'agents');
     }
@@ -688,8 +513,8 @@ class IdeSetup extends BaseIdeSetup {
   async getCoreTaskIds(installDir) {
     const allTaskIds = [];
 
-    // Check core tasks in .bmad-core or root only
-    let tasksDir = path.join(installDir, '.bmad-core', 'tasks');
+    // Check core tasks in bmad-core or root only
+    let tasksDir = path.join(installDir, 'bmad-core', 'tasks');
     if (!(await fileManager.pathExists(tasksDir))) {
       tasksDir = path.join(installDir, 'bmad-core', 'tasks');
     }
@@ -713,7 +538,7 @@ class IdeSetup extends BaseIdeSetup {
   async getAgentTitle(agentId, installDir) {
     // Try to find the agent file in various locations
     const possiblePaths = [
-      path.join(installDir, '.bmad-core', 'agents', `${agentId}.md`),
+      path.join(installDir, 'bmad-core', 'agents', `${agentId}.md`),
       path.join(installDir, 'agents', `${agentId}.md`),
     ];
 
@@ -754,8 +579,8 @@ class IdeSetup extends BaseIdeSetup {
     const glob = require('glob');
     const allTaskIds = [];
 
-    // Check core tasks in .bmad-core or root
-    let tasksDir = path.join(installDir, '.bmad-core', 'tasks');
+    // Check core tasks in bmad-core or root
+    let tasksDir = path.join(installDir, 'bmad-core', 'tasks');
     if (!(await fileManager.pathExists(tasksDir))) {
       tasksDir = path.join(installDir, 'bmad-core', 'tasks');
     }
@@ -798,7 +623,7 @@ class IdeSetup extends BaseIdeSetup {
   async findTaskPath(taskId, installDir) {
     // Try to find the task file in various locations
     const possiblePaths = [
-      path.join(installDir, '.bmad-core', 'tasks', `${taskId}.md`),
+      path.join(installDir, 'bmad-core', 'tasks', `${taskId}.md`),
       path.join(installDir, 'bmad-core', 'tasks', `${taskId}.md`),
       path.join(installDir, 'common', 'tasks', `${taskId}.md`),
     ];
@@ -832,7 +657,7 @@ class IdeSetup extends BaseIdeSetup {
 
   async getCoreSlashPrefix(installDir) {
     try {
-      const coreConfigPath = path.join(installDir, '.bmad-core', 'core-config.yaml');
+      const coreConfigPath = path.join(installDir, 'bmad-core', 'core-config.yaml');
       if (!(await fileManager.pathExists(coreConfigPath))) {
         // Try bmad-core directory
         const altConfigPath = path.join(installDir, 'bmad-core', 'core-config.yaml');
@@ -861,7 +686,7 @@ class IdeSetup extends BaseIdeSetup {
     const dotExpansions = glob.sync('.bmad-*', { cwd: installDir });
 
     for (const dotExpansion of dotExpansions) {
-      if (dotExpansion !== '.bmad-core') {
+      if (dotExpansion !== 'bmad-core') {
         const packPath = path.join(installDir, dotExpansion);
         const packName = dotExpansion.slice(1); // remove the dot
         expansionPacks.push({
@@ -1187,7 +1012,7 @@ class IdeSetup extends BaseIdeSetup {
         }
         mdContent += '\n```\n\n';
         mdContent += '## Project Standards\n\n';
-        mdContent += `- Always maintain consistency with project documentation in .bmad-core/\n`;
+        mdContent += `- Always maintain consistency with project documentation in bmad-core/\n`;
         mdContent += `- Follow the agent's specific guidelines and constraints\n`;
         mdContent += `- Update relevant project files when making changes\n`;
         const relativePath = path.relative(installDir, agentPath).replaceAll('\\', '/');

tools/installer/lib/installer.js

@@ -34,8 +34,8 @@ class Installer {
         ? config.directory
         : path.resolve(originalCwd, config.directory);
 
-      if (path.basename(installDir) === '.bmad-core') {
-        // If user points directly to .bmad-core, treat its parent as the project root
+      if (path.basename(installDir) === 'bmad-core') {
+        // If user points directly to bmad-core, treat its parent as the project root
         installDir = path.dirname(installDir);
       }
 
@@ -173,8 +173,8 @@ class Installer {
       return state; // clean install
     }
 
-    // Check for V4 installation (has .bmad-core with manifest)
-    const bmadCorePath = path.join(installDir, '.bmad-core');
+    // Check for V4 installation (has bmad-core with manifest)
+    const bmadCorePath = path.join(installDir, 'bmad-core');
     const manifestPath = path.join(bmadCorePath, 'install-manifest.yaml');
 
     if (await fileManager.pathExists(manifestPath)) {
@@ -193,7 +193,7 @@ class Installer {
       return state;
     }
 
-    // Check for .bmad-core without manifest (broken V4 or manual copy)
+    // Check for bmad-core without manifest (broken V4 or manual copy)
     if (await fileManager.pathExists(bmadCorePath)) {
       state.type = 'unknown_existing';
       state.hasBmadCore = true;
@@ -227,23 +227,19 @@ class Installer {
 
     switch (config.installType) {
       case 'full': {
-        // Full installation - copy entire .bmad-core folder as a subdirectory
-        spinner.text = 'Copying complete .bmad-core folder...';
+        // Full installation - copy entire bmad-core folder as a subdirectory
+        spinner.text = 'Copying complete bmad-core folder...';
         const sourceDir = resourceLocator.getBmadCorePath();
-        const bmadCoreDestDir = path.join(installDir, '.bmad-core');
-        await fileManager.copyDirectoryWithRootReplacement(
-          sourceDir,
-          bmadCoreDestDir,
-          '.bmad-core',
-        );
+        const bmadCoreDestDir = path.join(installDir, 'bmad-core');
+        await fileManager.copyDirectoryWithRootReplacement(sourceDir, bmadCoreDestDir, 'bmad-core');
 
-        // Copy common/ items to .bmad-core
+        // Copy common/ items to bmad-core
         spinner.text = 'Copying common utilities...';
-        await this.copyCommonItems(installDir, '.bmad-core', spinner);
+        await this.copyCommonItems(installDir, 'bmad-core', spinner);
 
-        // Copy documentation files from docs/ to .bmad-core
+        // Copy documentation files from docs/ to bmad-core
         spinner.text = 'Copying documentation files...';
-        await this.copyDocsItems(installDir, '.bmad-core', spinner);
+        await this.copyDocsItems(installDir, 'bmad-core', spinner);
 
         // Get list of all files for manifest
         const foundFiles = await resourceLocator.findFiles('**/*', {
@@ -251,7 +247,7 @@ class Installer {
           nodir: true,
           ignore: ['**/.git/**', '**/node_modules/**'],
         });
-        files = foundFiles.map((file) => path.join('.bmad-core', file));
+        files = foundFiles.map((file) => path.join('bmad-core', file));
 
         break;
       }
@@ -263,16 +259,12 @@ class Installer {
         const agentPath = configLoader.getAgentPath(config.agent);
         const destinationAgentPath = path.join(
           installDir,
-          '.bmad-core',
+          'bmad-core',
           'agents',
           `${config.agent}.md`,
         );
-        await fileManager.copyFileWithRootReplacement(
-          agentPath,
-          destinationAgentPath,
-          '.bmad-core',
-        );
-        files.push(`.bmad-core/agents/${config.agent}.md`);
+        await fileManager.copyFileWithRootReplacement(agentPath, destinationAgentPath, 'bmad-core');
+        files.push(`bmad-core/agents/${config.agent}.md`);
 
         // Copy dependencies
         const { all: dependencies } = await resourceLocator.getAgentDependencies(config.agent);
@@ -284,15 +276,15 @@ class Installer {
           if (dep.includes('*')) {
             // Handle glob patterns with {root} replacement
             const copiedFiles = await fileManager.copyGlobPattern(
-              dep.replace('.bmad-core/', ''),
+              dep.replace('bmad-core/', ''),
               sourceBase,
-              path.join(installDir, '.bmad-core'),
-              '.bmad-core',
+              path.join(installDir, 'bmad-core'),
+              'bmad-core',
             );
-            files.push(...copiedFiles.map((f) => `.bmad-core/${f}`));
+            files.push(...copiedFiles.map((f) => `bmad-core/${f}`));
           } else {
             // Handle single files with {root} replacement if needed
-            const sourcePath = path.join(sourceBase, dep.replace('.bmad-core/', ''));
+            const sourcePath = path.join(sourceBase, dep.replace('bmad-core/', ''));
             const destinationPath = path.join(installDir, dep);
 
             const needsRootReplacement =
@@ -300,7 +292,7 @@ class Installer {
             let success = false;
 
             success = await (needsRootReplacement
-              ? fileManager.copyFileWithRootReplacement(sourcePath, destinationPath, '.bmad-core')
+              ? fileManager.copyFileWithRootReplacement(sourcePath, destinationPath, 'bmad-core')
               : fileManager.copyFile(sourcePath, destinationPath));
 
             if (success) {
@@ -309,14 +301,14 @@ class Installer {
           }
         }
 
-        // Copy common/ items to .bmad-core
+        // Copy common/ items to bmad-core
         spinner.text = 'Copying common utilities...';
-        const commonFiles = await this.copyCommonItems(installDir, '.bmad-core', spinner);
+        const commonFiles = await this.copyCommonItems(installDir, 'bmad-core', spinner);
         files.push(...commonFiles);
 
-        // Copy documentation files from docs/ to .bmad-core
+        // Copy documentation files from docs/ to bmad-core
         spinner.text = 'Copying documentation files...';
-        const documentFiles = await this.copyDocsItems(installDir, '.bmad-core', spinner);
+        const documentFiles = await this.copyDocsItems(installDir, 'bmad-core', spinner);
         files.push(...documentFiles);
 
         break;
@@ -336,15 +328,15 @@ class Installer {
           if (dep.includes('*')) {
             // Handle glob patterns with {root} replacement
             const copiedFiles = await fileManager.copyGlobPattern(
-              dep.replace('.bmad-core/', ''),
+              dep.replace('bmad-core/', ''),
               sourceBase,
-              path.join(installDir, '.bmad-core'),
-              '.bmad-core',
+              path.join(installDir, 'bmad-core'),
+              'bmad-core',
             );
-            files.push(...copiedFiles.map((f) => `.bmad-core/${f}`));
+            files.push(...copiedFiles.map((f) => `bmad-core/${f}`));
           } else {
             // Handle single files with {root} replacement if needed
-            const sourcePath = path.join(sourceBase, dep.replace('.bmad-core/', ''));
+            const sourcePath = path.join(sourceBase, dep.replace('bmad-core/', ''));
             const destinationPath = path.join(installDir, dep);
 
             const needsRootReplacement =
@@ -352,7 +344,7 @@ class Installer {
             let success = false;
 
             success = await (needsRootReplacement
-              ? fileManager.copyFileWithRootReplacement(sourcePath, destinationPath, '.bmad-core')
+              ? fileManager.copyFileWithRootReplacement(sourcePath, destinationPath, 'bmad-core')
               : fileManager.copyFile(sourcePath, destinationPath));
 
             if (success) {
@@ -361,20 +353,20 @@ class Installer {
           }
         }
 
-        // Copy common/ items to .bmad-core
+        // Copy common/ items to bmad-core
         spinner.text = 'Copying common utilities...';
-        const commonFiles = await this.copyCommonItems(installDir, '.bmad-core', spinner);
+        const commonFiles = await this.copyCommonItems(installDir, 'bmad-core', spinner);
         files.push(...commonFiles);
 
-        // Copy documentation files from docs/ to .bmad-core
+        // Copy documentation files from docs/ to bmad-core
         spinner.text = 'Copying documentation files...';
-        const documentFiles = await this.copyDocsItems(installDir, '.bmad-core', spinner);
+        const documentFiles = await this.copyDocsItems(installDir, 'bmad-core', spinner);
         files.push(...documentFiles);
 
         break;
       }
       case 'expansion-only': {
-        // Expansion-only installation - DO NOT create .bmad-core
+        // Expansion-only installation - DO NOT create bmad-core
         // Only install expansion packs
         spinner.text = 'Installing expansion packs only...';
 
@@ -633,7 +625,7 @@ class Installer {
     console.log(`   Directory: ${installDir}`);
 
     if (state.hasBmadCore) {
-      console.log('   Found: .bmad-core directory (but no manifest)');
+      console.log('   Found: bmad-core directory (but no manifest)');
     }
     if (state.hasOtherFiles) {
       console.log('   Found: Other files in directory');
@@ -771,7 +763,7 @@ class Installer {
         // Skip the manifest file itself
         if (file.endsWith('install-manifest.yaml')) continue;
 
-        const relativePath = file.replace('.bmad-core/', '');
+        const relativePath = file.replace('bmad-core/', '');
         const destinationPath = path.join(installDir, file);
 
         // Check if this is a common/ file that needs special processing
@@ -782,7 +774,7 @@ class Installer {
           // This is a common/ file - needs template processing
           const fs = require('node:fs').promises;
           const content = await fs.readFile(commonSourcePath, 'utf8');
-          const updatedContent = content.replaceAll('{root}', '.bmad-core');
+          const updatedContent = content.replaceAll('{root}', 'bmad-core');
           await fileManager.ensureDirectory(path.dirname(destinationPath));
           await fs.writeFile(destinationPath, updatedContent, 'utf8');
           spinner.text = `Restored: ${file}`;
@@ -845,8 +837,8 @@ class Installer {
   async performReinstall(config, installDir, spinner) {
     spinner.start('Preparing to reinstall BMad Method...');
 
-    // Remove existing .bmad-core
-    const bmadCorePath = path.join(installDir, '.bmad-core');
+    // Remove existing bmad-core
+    const bmadCorePath = path.join(installDir, 'bmad-core');
     if (await fileManager.pathExists(bmadCorePath)) {
       spinner.text = 'Removing existing installation...';
       await fileManager.removeDirectory(bmadCorePath);
@@ -882,7 +874,7 @@ class Installer {
     // Information about installation components
     console.log(chalk.bold('\n🎯 Installation Summary:'));
     if (config.installType !== 'expansion-only') {
-      console.log(chalk.green('✓ .bmad-core framework installed with all agents and workflows'));
+      console.log(chalk.green('✓ bmad-core framework installed with all agents and workflows'));
     }
 
     if (config.expansionPacks && config.expansionPacks.length > 0) {
@@ -941,7 +933,7 @@ class Installer {
     // Important notice to read the user guide
     console.log(
       chalk.red.bold(
-        '\n📖 IMPORTANT: Please read the user guide at docs/user-guide.md (also installed at .bmad-core/user-guide.md)',
+        '\n📖 IMPORTANT: Please read the user guide at docs/user-guide.md (also installed at bmad-core/user-guide.md)',
       ),
     );
     console.log(
@@ -1787,7 +1779,7 @@ class Installer {
     // Find all dot folders that might be expansion packs
     const dotFolders = glob.sync('.*', {
       cwd: installDir,
-      ignore: ['.git', '.git/**', '.bmad-core', '.bmad-core/**'],
+      ignore: ['.git', '.git/**', 'bmad-core', 'bmad-core/**'],
     });
 
     for (const folder of dotFolders) {
@@ -1944,22 +1936,22 @@ class Installer {
   }
 
   async findInstallation() {
-    // Look for .bmad-core in current directory or parent directories
+    // Look for bmad-core in current directory or parent directories
     let currentDir = process.cwd();
 
     while (currentDir !== path.dirname(currentDir)) {
-      const bmadDir = path.join(currentDir, '.bmad-core');
+      const bmadDir = path.join(currentDir, 'bmad-core');
       const manifestPath = path.join(bmadDir, 'install-manifest.yaml');
 
       if (await fileManager.pathExists(manifestPath)) {
-        return currentDir; // Return parent directory, not .bmad-core itself
+        return currentDir; // Return parent directory, not bmad-core itself
       }
 
       currentDir = path.dirname(currentDir);
     }
 
-    // Also check if we're inside a .bmad-core directory
-    if (path.basename(process.cwd()) === '.bmad-core') {
+    // Also check if we're inside a bmad-core directory
+    if (path.basename(process.cwd()) === 'bmad-core') {
       const manifestPath = path.join(process.cwd(), 'install-manifest.yaml');
       if (await fileManager.pathExists(manifestPath)) {
         return path.dirname(process.cwd()); // Return parent directory

tools/installer/lib/resource-locator.js

@@ -251,7 +251,7 @@ class ResourceLocator {
         if (Array.isArray(deps)) {
           byType[type] = deps;
           for (const dep of deps) {
-            allDeps.push(`.bmad-core/${type}/${dep}`);
+            allDeps.push(`bmad-core/${type}/${dep}`);
           }
         }
       }

tools/md-assets/web-agent-startup-instructions.md

@@ -8,13 +8,13 @@ You are now operating as a specialized AI agent from the BMad-Method framework.
 
 ### **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
 
-- `==================== START: .bmad-core/folder/filename.md ====================`
-- `==================== END: .bmad-core/folder/filename.md ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
+- `==================== END: bmad-core/folder/filename.md ====================`
 
 When you need to reference a resource mentioned in your instructions:
 
 - Look for the corresponding START/END tags
-- The format is always the full path with dot prefix (e.g., `.bmad-core/personas/analyst.md`, `.bmad-core/tasks/create-story.md`)
+- The format is always the full path with dot prefix (e.g., `bmad-core/personas/analyst.md`, `bmad-core/tasks/create-story.md`)
 - If a section is specified (e.g., `{root}/tasks/create-story.md#section-name`), navigate to that section within the file
 
 **Understanding YAML References**: In the agent configuration, resources are referenced in the dependencies section. For example:
@@ -29,8 +29,8 @@ dependencies:
 
 These references map directly to bundle sections:
 
-- `dependencies.utils: template-format` → Look for `==================== START: .bmad-core/utils/template-format.md ====================`
-- `dependencies.utils: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.md ====================`
+- `dependencies.utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
+- `dependencies.utils: create-story` → Look for `==================== START: bmad-core/tasks/create-story.md ====================`
 
 ### **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. You have no file system to write to, so you will maintain document history being drafted in your memory unless a canvas feature is available and the user confirms its usage.
 

tools/setup-hooks.sh

@@ -1,37 +0,0 @@
-#!/bin/bash
-
-# Setup script for git hooks
-echo "Setting up git hooks..."
-
-# Install husky
-npm install --save-dev husky
-
-# Initialize husky
-npx husky init
-
-# Create pre-commit hook
-cat > .husky/pre-commit << 'EOF'
-#!/usr/bin/env sh
-. "$(dirname -- "$0")/_/husky.sh"
-
-# Run validation checks before commit
-echo "Running pre-commit checks..."
-
-npm run validate
-npm run format:check
-npm run lint
-
-if [ $? -ne 0 ]; then
-  echo "❌ Pre-commit checks failed. Please fix the issues before committing."
-  echo "   Run 'npm run format' to fix formatting issues"
-  echo "   Run 'npm run lint:fix' to fix some lint issues"
-  exit 1
-fi
-
-echo "✅ Pre-commit checks passed!"
-EOF
-
-chmod +x .husky/pre-commit
-
-echo "✅ Git hooks setup complete!"
-echo "Now commits will be validated before they're created."

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

@@ -29,7 +29,7 @@ class V3ToV4Upgrader {
       console.log('This tool will help you upgrade your BMad-Method V3 project to V4.\n');
       console.log(chalk.cyan('What this tool does:'));
       console.log('- Creates a backup of your V3 files (.bmad-v3-backup/)');
-      console.log('- Installs the new V4 .bmad-core structure');
+      console.log('- Installs the new V4 bmad-core structure');
       console.log('- Preserves your PRD, Architecture, and Stories in the new format\n');
       console.log(chalk.yellow('What this tool does NOT do:'));
       console.log('- Modify your document content (use doc-migration-task after upgrade)');
@@ -336,12 +336,12 @@ class V3ToV4Upgrader {
     try {
       // Get the source bmad-core directory (without dot prefix)
       const sourcePath = path.join(__dirname, '..', '..', 'bmad-core');
-      const destinationPath = path.join(projectPath, '.bmad-core');
+      const destinationPath = path.join(projectPath, 'bmad-core');
 
-      // Copy .bmad-core
+      // Copy bmad-core
       await this.copyDirectory(sourcePath, destinationPath);
-      spinner.text = '✓ Copied fresh .bmad-core/ directory from V4';
-      console.log(chalk.green('\n✓ Copied fresh .bmad-core/ directory from V4'));
+      spinner.text = '✓ Copied fresh bmad-core/ directory from V4';
+      console.log(chalk.green('\n✓ Copied fresh bmad-core/ directory from V4'));
 
       // Create docs directory
       const docsPath = path.join(projectPath, 'docs');
@@ -516,7 +516,7 @@ class V3ToV4Upgrader {
     console.log(chalk.bold.green('\n✓ Upgrade Complete!\n'));
     console.log(chalk.bold('Summary:'));
     console.log(`- V3 files backed up to: .bmad-v3-backup/`);
-    console.log(`- V4 structure installed: .bmad-core/ (fresh from V4)`);
+    console.log(`- V4 structure installed: bmad-core/ (fresh from V4)`);
 
     const totalDocs =
       (analysis.prdFile ? 1 : 0) +
@@ -648,16 +648,16 @@ class V3ToV4Upgrader {
     const fileManager = require('../installer/lib/file-manager');
     const { glob } = require('glob');
 
-    // Get all files in .bmad-core for the manifest
-    const bmadCorePath = path.join(projectPath, '.bmad-core');
+    // Get all files in bmad-core for the manifest
+    const bmadCorePath = path.join(projectPath, 'bmad-core');
     const files = await glob('**/*', {
       cwd: bmadCorePath,
       nodir: true,
       ignore: ['**/.git/**', '**/node_modules/**'],
     });
 
-    // Prepend .bmad-core/ to file paths for manifest
-    const manifestFiles = files.map((file) => path.join('.bmad-core', file));
+    // Prepend bmad-core/ to file paths for manifest
+    const manifestFiles = files.map((file) => path.join('bmad-core', file));
 
     const config = {
       installType: 'full',