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

.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

@@ -206,4 +206,4 @@ Each commit should represent one logical change:
 
 ## License
 
-By contributing to this project, you agree that your contributions will be licensed under the same license as the project.
+By contributing to this project, you agree that your contributions will be licensed under the MIT License.

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2025 Brian AKA BMad AKA BMad Code
+Copyright (c) 2025 BMad Code, LLC
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
@@ -19,3 +19,8 @@ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
+
+TRADEMARK NOTICE:
+BMAD™ and BMAD-METHOD™ are trademarks of BMad Code, LLC. The use of these 
+trademarks in this software does not grant any rights to use the trademarks 
+for any other purpose.

README.md

@@ -1,4 +1,4 @@
-# BMad-Method: Universal AI Agent Framework
+# BMAD-METHOD™: Universal AI Agent Framework
 
 [![Version](https://img.shields.io/npm/v/bmad-method?color=blue&label=version)](https://www.npmjs.com/package/bmad-method)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
@@ -11,11 +11,11 @@ Foundations in Agentic Agile Driven Development, known as the Breakthrough Metho
 
 **[Join our Discord Community](https://discord.gg/gk8jAdXWmj)** - A growing community for AI enthusiasts! Get help, share ideas, explore AI agents & frameworks, collaborate on tech projects, enjoy hobbies, and help each other succeed. Whether you're stuck on BMad, building your own agents, or just want to chat about the latest in AI - we're here for you! **Some mobile and VPN may have issue joining the discord, this is a discord issue - if the invite does not work, try from your own internet or another network, or non-VPN.**
 
-⭐ **If you find this project helpful or useful, please give it a star in the upper right hand corner!** It helps others discover BMad-Method and you will be notified of updates!
+⭐ **If you find this project helpful or useful, please give it a star in the upper right hand corner!** It helps others discover BMAD-METHOD™ and you will be notified of updates!
 
 ## Overview
 
-**BMad Method's Two Key Innovations:**
+**BMAD-METHOD™'s Two Key Innovations:**
 
 **1. Agentic Planning:** Dedicated agents (Analyst, PM, Architect) collaborate with you to create detailed, consistent PRDs and Architecture documents. Through advanced prompt engineering and human-in-the-loop refinement, these planning agents produce comprehensive specifications that go far beyond generic AI task generation.
 
@@ -49,7 +49,7 @@ This two-phase approach eliminates both **planning inconsistency** and **context
 
 ## Important: Keep Your BMad Installation Updated
 
-**Stay up-to-date effortlessly!** If you already have BMad-Method installed in your project, simply run:
+**Stay up-to-date effortlessly!** If you already have BMAD-METHOD™ installed in your project, simply run:
 
 ```bash
 npx bmad-method install
@@ -110,11 +110,11 @@ npm run install:bmad # build and install all to a destination folder
 
 ## 🌟 Beyond Software Development - Expansion Packs
 
-BMad's natural language framework works in ANY domain. Expansion packs provide specialized AI agents for creative writing, business strategy, health & wellness, education, and more. Also expansion packs can expand the core BMad-Method with specific functionality that is not generic for all cases. [See the Expansion Packs Guide](docs/expansion-packs.md) and learn to create your own!
+BMAD™'s natural language framework works in ANY domain. Expansion packs provide specialized AI agents for creative writing, business strategy, health & wellness, education, and more. Also expansion packs can expand the core BMAD-METHOD™ with specific functionality that is not generic for all cases. [See the Expansion Packs Guide](docs/expansion-packs.md) and learn to create your own!
 
 ## Codebase Flattener Tool
 
-The BMad-Method includes a powerful codebase flattener tool designed to prepare your project files for AI model consumption. This tool aggregates your entire codebase into a single XML file, making it easy to share your project context with AI assistants for analysis, debugging, or development assistance.
+The BMAD-METHOD™ includes a powerful codebase flattener tool designed to prepare your project files for AI model consumption. This tool aggregates your entire codebase into a single XML file, making it easy to share your project context with AI assistants for analysis, debugging, or development assistance.
 
 ### Features
 
@@ -157,7 +157,7 @@ The tool will display progress and provide a comprehensive summary:
 📊 File breakdown: 142 text, 14 binary, 0 errors
 ```
 
-The generated XML file contains your project's text-based source files in a structured format that AI models can easily parse and understand, making it perfect for code reviews, architecture discussions, or getting AI assistance with your BMad-Method projects.
+The generated XML file contains your project's text-based source files in a structured format that AI models can easily parse and understand, making it perfect for code reviews, architecture discussions, or getting AI assistance with your BMAD-METHOD™ projects.
 
 #### Advanced Usage & Options
 
@@ -216,6 +216,10 @@ The generated XML file contains your project's text-based source files in a stru
 
 MIT License - see [LICENSE](LICENSE) for details.
 
+## Trademark Notice
+
+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>

bmad-core/agent-teams/team-all.yaml

@@ -1,3 +1,4 @@
+# <!-- Powered by BMAD™ Core -->
 bundle:
   name: Team All
   icon: 👥

bmad-core/agent-teams/team-fullstack.yaml

@@ -1,3 +1,4 @@
+# <!-- Powered by BMAD™ Core -->
 bundle:
   name: Team Fullstack
   icon: 🚀

bmad-core/agent-teams/team-ide-minimal.yaml

@@ -1,3 +1,4 @@
+# <!-- Powered by BMAD™ Core -->
 bundle:
   name: Team IDE Minimal
   icon: ⚡

bmad-core/agent-teams/team-no-ui.yaml

@@ -1,3 +1,4 @@
+# <!-- Powered by BMAD™ Core -->
 bundle:
   name: Team No UI
   icon: 🔧

bmad-core/agents/analyst.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # analyst
 
 ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.

bmad-core/agents/architect.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # architect
 
 ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.

bmad-core/agents/bmad-master.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # BMad Master
 
 ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.

bmad-core/agents/bmad-orchestrator.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # BMad Web Orchestrator
 
 ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.

bmad-core/agents/dev.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # dev
 
 ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.

bmad-core/agents/pm.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # pm
 
 ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.

bmad-core/agents/po.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # po
 
 ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.

bmad-core/agents/qa.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # qa
 
 ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.

bmad-core/agents/sm.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # sm
 
 ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.

bmad-core/agents/ux-expert.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # ux-expert
 
 ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.

bmad-core/checklists/architect-checklist.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Architect Solution Validation Checklist
 
 This checklist serves as a comprehensive framework for the Architect to validate the technical design and architecture before development execution. The Architect should systematically work through each item, ensuring the architecture is robust, scalable, secure, and aligned with the product requirements.

bmad-core/checklists/change-checklist.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Change Navigation Checklist
 
 **Purpose:** To systematically guide the selected Agent and user through the analysis and planning required when a significant change (pivot, tech issue, missing requirement, failed story) is identified during the BMad workflow.

bmad-core/checklists/pm-checklist.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Product Manager (PM) Requirements Checklist
 
 This checklist serves as a comprehensive framework to ensure the Product Requirements Document (PRD) and Epic definitions are complete, well-structured, and appropriately scoped for MVP development. The PM should systematically work through each item during the product definition process.

bmad-core/checklists/po-master-checklist.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Product Owner (PO) Master Validation Checklist
 
 This checklist serves as a comprehensive framework for the Product Owner to validate project plans before development execution. It adapts intelligently based on project type (greenfield vs brownfield) and includes UI/UX considerations when applicable.

bmad-core/checklists/story-dod-checklist.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Story Definition of Done (DoD) Checklist
 
 ## Instructions for Developer Agent

bmad-core/checklists/story-draft-checklist.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Story Draft Checklist
 
 The Scrum Master should use this checklist to validate that each story contains sufficient context for a developer agent to implement it successfully, while assuming the dev agent has reasonable capabilities to figure things out.

bmad-core/core-config.yaml

@@ -1,3 +1,4 @@
+# <!-- Powered by BMAD™ Core -->
 markdownExploder: true
 qa:
   qaLocation: docs/qa

bmad-core/data/bmad-kb.md

@@ -1,8 +1,10 @@
-# BMad Knowledge Base
+<!-- Powered by BMAD™ Core -->
+
+# BMAD™ Knowledge Base
 
 ## Overview
 
-BMad-Method (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
+BMAD-METHOD™ (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
 
 ### Key Features
 
@@ -101,15 +103,15 @@ npx bmad-method install
   - **Roo Code**: Web-based IDE with agent support
   - **GitHub Copilot**: VS Code extension with AI peer programming assistant
 
-**Note for VS Code Users**: BMad-Method assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMad agents. The installer includes built-in support for Cline and Roo.
+**Note for VS Code Users**: BMAD-METHOD™ assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMad agents. The installer includes built-in support for Cline and Roo.
 
 **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
 
-**Remember**: At its core, BMad-Method is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
+**Remember**: At its core, BMAD-METHOD™ is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
 
 ### Environment Selection Guide
 
@@ -353,7 +355,7 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
 
 ### System Overview
 
-The BMad-Method is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
+The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
 
 ### Key Architectural Components
 
@@ -708,7 +710,7 @@ Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic sh
 - **Keep conversations focused** - One agent, one task per conversation
 - **Review everything** - Always review and approve before marking complete
 
-## Contributing to BMad-Method
+## Contributing to BMAD-METHOD™
 
 ### Quick Contribution Guidelines
 
@@ -740,7 +742,7 @@ For full details, see `CONTRIBUTING.md`. Key points:
 
 ### What Are Expansion Packs?
 
-Expansion packs extend BMad-Method beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
+Expansion packs extend BMAD-METHOD™ beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
 
 ### Why Use Expansion Packs?
 

bmad-core/data/brainstorming-techniques.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Brainstorming Techniques Data
 
 ## Creative Expansion

bmad-core/data/elicitation-methods.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Elicitation Methods Data
 
 ## Core Reflective Methods

bmad-core/data/technical-preferences.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # User-Defined Preferred Patterns and Preferences
 
 None Listed

bmad-core/data/test-levels-framework.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Test Levels Framework
 
 Comprehensive guide for determining appropriate test levels (unit, integration, E2E) for different scenarios.

bmad-core/data/test-priorities-matrix.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Test Priorities Matrix
 
 Guide for prioritizing test scenarios based on risk, criticality, and business impact.

bmad-core/tasks/advanced-elicitation.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Advanced Elicitation Task
 
 ## Purpose

bmad-core/tasks/apply-qa-fixes.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # apply-qa-fixes
 
 Implement fixes based on QA results (gate and assessments) for a specific story. This task is for the Dev agent to systematically consume QA outputs and apply code/test changes while only updating allowed sections in the story file.

bmad-core/tasks/brownfield-create-epic.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Create Brownfield Epic Task
 
 ## Purpose

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

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Create Brownfield Story Task
 
 ## Purpose

bmad-core/tasks/correct-course.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Correct Course Task
 
 ## Purpose

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

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Create Brownfield Story Task
 
 ## Purpose

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

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Create Deep Research Prompt Task
 
 This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.

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

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Create Next Story Task
 
 ## Purpose

bmad-core/tasks/document-project.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Document an Existing Project
 
 ## Purpose

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

@@ -1,6 +1,8 @@
----
+## <!-- Powered by BMAD™ Core -->
+
 docOutputLocation: docs/brainstorming-session-results.md
 template: '{root}/templates/brainstorming-output-tmpl.yaml'
+
 ---
 
 # Facilitate Brainstorming Session Task

bmad-core/tasks/generate-ai-frontend-prompt.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Create AI Frontend Prompt Task
 
 ## Purpose

bmad-core/tasks/index-docs.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Index Documentation Task
 
 ## Purpose

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

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # KB Mode Interaction Task
 
 ## Purpose

bmad-core/tasks/nfr-assess.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # nfr-assess
 
 Quick NFR validation focused on the core four: security, performance, reliability, maintainability.

bmad-core/tasks/qa-gate.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # qa-gate
 
 Create or update a quality gate decision file for a story based on review findings.

bmad-core/tasks/review-story.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # review-story
 
 Perform a comprehensive test architecture review with quality gate decision. This adaptive, risk-aware review creates both a story update and a detailed gate file.

bmad-core/tasks/risk-profile.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # risk-profile
 
 Generate a comprehensive risk assessment matrix for a story implementation using probability × impact analysis.

bmad-core/tasks/shard-doc.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Document Sharding Task
 
 ## Purpose

bmad-core/tasks/test-design.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # test-design
 
 Create comprehensive test scenarios with appropriate test level recommendations for story implementation.

bmad-core/tasks/trace-requirements.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # trace-requirements
 
 Map story requirements to test cases using Given-When-Then patterns for comprehensive traceability.

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

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Validate Next Story Task
 
 ## Purpose
@@ -8,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/templates/architecture-tmpl.yaml

@@ -1,3 +1,4 @@
+# <!-- Powered by BMAD™ Core -->
 template:
   id: architecture-template-v2
   name: Architecture Document

bmad-core/templates/brainstorming-output-tmpl.yaml

@@ -153,4 +153,4 @@ sections:
     content: |
       ---
 
-      *Session facilitated using the BMAD-METHOD brainstorming framework*
+      *Session facilitated using the BMAD-METHOD™ brainstorming framework*

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

@@ -1,3 +1,4 @@
+# <!-- Powered by BMAD™ Core -->
 template:
   id: brownfield-architecture-template-v2
   name: Brownfield Enhancement Architecture

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

@@ -1,3 +1,4 @@
+# <!-- Powered by BMAD™ Core -->
 template:
   id: brownfield-prd-template-v2
   name: Brownfield Enhancement PRD

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

@@ -1,3 +1,4 @@
+# <!-- Powered by BMAD™ Core -->
 template:
   id: competitor-analysis-template-v2
   name: Competitive Analysis Report

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

@@ -1,3 +1,4 @@
+# <!-- Powered by BMAD™ Core -->
 template:
   id: frontend-architecture-template-v2
   name: Frontend Architecture Document

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

@@ -1,3 +1,4 @@
+# <!-- Powered by BMAD™ Core -->
 template:
   id: frontend-spec-template-v2
   name: UI/UX Specification

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

@@ -1,3 +1,4 @@
+# <!-- Powered by BMAD™ Core -->
 template:
   id: fullstack-architecture-template-v2
   name: Fullstack Architecture Document

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

@@ -1,3 +1,4 @@
+# <!-- Powered by BMAD™ Core -->
 template:
   id: market-research-template-v2
   name: Market Research Report

bmad-core/templates/prd-tmpl.yaml

@@ -1,3 +1,4 @@
+# <!-- Powered by BMAD™ Core -->
 template:
   id: prd-template-v2
   name: Product Requirements Document

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

@@ -1,3 +1,4 @@
+# <!-- Powered by BMAD™ Core -->
 template:
   id: project-brief-template-v2
   name: Project Brief

bmad-core/templates/qa-gate-tmpl.yaml

@@ -1,3 +1,4 @@
+# <!-- Powered by BMAD™ Core -->
 template:
   id: qa-gate-template-v1
   name: Quality Gate Decision

bmad-core/templates/story-tmpl.yaml

@@ -1,3 +1,4 @@
+# <!-- Powered by BMAD™ Core -->
 template:
   id: story-template-v2
   name: Story Document

bmad-core/workflows/brownfield-fullstack.yaml

@@ -1,3 +1,4 @@
+# <!-- Powered by BMAD™ Core -->
 workflow:
   id: brownfield-fullstack
   name: Brownfield Full-Stack Enhancement

bmad-core/workflows/brownfield-service.yaml

@@ -1,3 +1,4 @@
+# <!-- Powered by BMAD™ Core -->
 workflow:
   id: brownfield-service
   name: Brownfield Service/API Enhancement

bmad-core/workflows/brownfield-ui.yaml

@@ -1,3 +1,4 @@
+# <!-- Powered by BMAD™ Core -->
 workflow:
   id: brownfield-ui
   name: Brownfield UI/Frontend Enhancement

bmad-core/workflows/greenfield-fullstack.yaml

@@ -1,3 +1,4 @@
+# <!-- Powered by BMAD™ Core -->
 workflow:
   id: greenfield-fullstack
   name: Greenfield Full-Stack Application Development

bmad-core/workflows/greenfield-service.yaml

@@ -1,3 +1,4 @@
+# <!-- Powered by BMAD™ Core -->
 workflow:
   id: greenfield-service
   name: Greenfield Service/API Development

bmad-core/workflows/greenfield-ui.yaml

@@ -1,3 +1,4 @@
+# <!-- Powered by BMAD™ Core -->
 workflow:
   id: greenfield-ui
   name: Greenfield UI/Frontend Development

common/tasks/create-doc.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Create Document from Template (YAML Driven)
 
 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@@ -15,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
 

common/tasks/execute-checklist.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Checklist Validation Task
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.

common/utils/bmad-doc-template.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # BMad Document Template Specification
 
 ## Overview

common/utils/workflow-management.md

@@ -1,3 +1,5 @@
+<!-- Powered by BMAD™ Core -->
+
 # Workflow Management
 
 Enables BMad orchestrator to manage and execute team workflows.

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 ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
-- `==================== END: .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 ====================`
+- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
-- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.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,10 @@ 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
 
 ## Purpose
@@ -221,9 +222,10 @@ 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
 
 This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@@ -502,9 +504,10 @@ 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)
 
 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@@ -522,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
 
@@ -606,9 +609,10 @@ 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
 
 ## Purpose
@@ -952,12 +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
@@ -1091,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
@@ -1249,10 +1254,11 @@ sections:
     content: |
       ---
 
-      *Session facilitated using the BMAD-METHOD brainstorming framework*
+      *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
   name: Competitive Analysis Report
@@ -1559,9 +1565,10 @@ 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
   name: Market Research Report
@@ -1814,9 +1821,10 @@ 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
   name: Project Brief
@@ -2038,14 +2046,15 @@ 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 ====================
-# BMad Knowledge Base
+<!-- Powered by BMAD™ Core -->
+# BMAD™ Knowledge Base
 
 ## Overview
 
-BMad-Method (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
+BMAD-METHOD™ (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
 
 ### Key Features
 
@@ -2144,15 +2153,15 @@ npx bmad-method install
   - **Roo Code**: Web-based IDE with agent support
   - **GitHub Copilot**: VS Code extension with AI peer programming assistant
 
-**Note for VS Code Users**: BMad-Method assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMad agents. The installer includes built-in support for Cline and Roo.
+**Note for VS Code Users**: BMAD-METHOD™ assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMad agents. The installer includes built-in support for Cline and Roo.
 
 **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
 
-**Remember**: At its core, BMad-Method is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
+**Remember**: At its core, BMAD-METHOD™ is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
 
 ### Environment Selection Guide
 
@@ -2396,7 +2405,7 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
 
 ### System Overview
 
-The BMad-Method is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
+The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
 
 ### Key Architectural Components
 
@@ -2751,7 +2760,7 @@ Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic sh
 - **Keep conversations focused** - One agent, one task per conversation
 - **Review everything** - Always review and approve before marking complete
 
-## Contributing to BMad-Method
+## Contributing to BMAD-METHOD™
 
 ### Quick Contribution Guidelines
 
@@ -2783,7 +2792,7 @@ For full details, see `CONTRIBUTING.md`. Key points:
 
 ### What Are Expansion Packs?
 
-Expansion packs extend BMad-Method beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
+Expansion packs extend BMAD-METHOD™ beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
 
 ### Why Use Expansion Packs?
 
@@ -2847,9 +2856,10 @@ 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
 
 ## Creative Expansion
@@ -2886,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 ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
-- `==================== END: .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 ====================`
+- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
-- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.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,10 @@ 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
 
 This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@@ -383,9 +384,10 @@ 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)
 
 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@@ -403,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
 
@@ -487,9 +489,10 @@ 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
 
 ## Purpose
@@ -833,16 +836,17 @@ 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
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
 
 ## 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
 
@@ -850,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
@@ -922,9 +926,10 @@ 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
   name: Architecture Document
@@ -1054,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
@@ -1575,9 +1580,10 @@ 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
   name: Brownfield Enhancement Architecture
@@ -2054,9 +2060,10 @@ 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
   name: Frontend Architecture Document
@@ -2275,9 +2282,10 @@ 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
   name: Fullstack Architecture Document
@@ -3101,9 +3109,10 @@ 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
 
 This checklist serves as a comprehensive framework for the Architect to validate the technical design and architecture before development execution. The Architect should systematically work through each item, ensuring the architecture is robust, scalable, secure, and aligned with the product requirements.
@@ -3542,10 +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 ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
-- `==================== END: .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 ====================`
+- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
-- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.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,10 @@ 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
 
 ## Purpose
@@ -244,9 +245,10 @@ 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
 
 ## Purpose
@@ -407,9 +409,10 @@ 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
 
 ## Purpose
@@ -557,14 +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.
@@ -578,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."
@@ -630,9 +634,10 @@ 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
 
 This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@@ -911,9 +916,10 @@ 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)
 
 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@@ -931,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
 
@@ -1015,9 +1021,10 @@ 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
 
 ## Purpose
@@ -1028,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.*`
 
@@ -1122,17 +1129,18 @@ 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`
+  - 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 ====================
+==================== 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
 
 ## Purpose
@@ -1476,16 +1484,17 @@ 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
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
 
 ## 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
 
@@ -1493,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
@@ -1565,12 +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
@@ -1704,9 +1714,10 @@ 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
 
 ## Purpose
@@ -1758,9 +1769,10 @@ 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
 
 ## Purpose
@@ -1934,9 +1946,10 @@ 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
 
 ## Purpose
@@ -1947,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."
@@ -2122,9 +2135,10 @@ 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
   name: Architecture Document
@@ -2254,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
@@ -2775,9 +2789,10 @@ 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
   name: Brownfield Enhancement Architecture
@@ -3254,9 +3269,10 @@ 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
   name: Brownfield Enhancement PRD
@@ -3537,9 +3553,10 @@ 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
   name: Competitive Analysis Report
@@ -3846,9 +3863,10 @@ 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
   name: Frontend Architecture Document
@@ -4067,9 +4085,10 @@ 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
   name: UI/UX Specification
@@ -4419,9 +4438,10 @@ 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
   name: Fullstack Architecture Document
@@ -5245,9 +5265,10 @@ 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
   name: Market Research Report
@@ -5500,9 +5521,10 @@ 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
   name: Product Requirements Document
@@ -5604,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)
@@ -5705,9 +5727,10 @@ 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
   name: Project Brief
@@ -5929,9 +5952,10 @@ 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
   name: Story Document
@@ -6069,9 +6093,10 @@ 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
 
 This checklist serves as a comprehensive framework for the Architect to validate the technical design and architecture before development execution. The Architect should systematically work through each item, ensuring the architecture is robust, scalable, secure, and aligned with the product requirements.
@@ -6510,9 +6535,10 @@ 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
 
 **Purpose:** To systematically guide the selected Agent and user through the analysis and planning required when a significant change (pivot, tech issue, missing requirement, failed story) is identified during the BMad workflow.
@@ -6695,9 +6721,10 @@ 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
 
 This checklist serves as a comprehensive framework to ensure the Product Requirements Document (PRD) and Epic definitions are complete, well-structured, and appropriately scoped for MVP development. The PM should systematically work through each item during the product definition process.
@@ -7068,9 +7095,10 @@ 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
 
 This checklist serves as a comprehensive framework for the Product Owner to validate project plans before development execution. It adapts intelligently based on project type (greenfield vs brownfield) and includes UI/UX considerations when applicable.
@@ -7503,9 +7531,10 @@ 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
 
 ## Instructions for Developer Agent
@@ -7600,9 +7629,10 @@ 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
 
 The Scrum Master should use this checklist to validate that each story contains sufficient context for a developer agent to implement it successfully, while assuming the dev agent has reasonable capabilities to figure things out.
@@ -7756,14 +7786,15 @@ 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 ====================
-# BMad Knowledge Base
+<!-- Powered by BMAD™ Core -->
+# BMAD™ Knowledge Base
 
 ## Overview
 
-BMad-Method (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
+BMAD-METHOD™ (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
 
 ### Key Features
 
@@ -7862,15 +7893,15 @@ npx bmad-method install
   - **Roo Code**: Web-based IDE with agent support
   - **GitHub Copilot**: VS Code extension with AI peer programming assistant
 
-**Note for VS Code Users**: BMad-Method assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMad agents. The installer includes built-in support for Cline and Roo.
+**Note for VS Code Users**: BMAD-METHOD™ assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMad agents. The installer includes built-in support for Cline and Roo.
 
 **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
 
-**Remember**: At its core, BMad-Method is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
+**Remember**: At its core, BMAD-METHOD™ is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
 
 ### Environment Selection Guide
 
@@ -8114,7 +8145,7 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
 
 ### System Overview
 
-The BMad-Method is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
+The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
 
 ### Key Architectural Components
 
@@ -8469,7 +8500,7 @@ Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic sh
 - **Keep conversations focused** - One agent, one task per conversation
 - **Review everything** - Always review and approve before marking complete
 
-## Contributing to BMad-Method
+## Contributing to BMAD-METHOD™
 
 ### Quick Contribution Guidelines
 
@@ -8501,7 +8532,7 @@ For full details, see `CONTRIBUTING.md`. Key points:
 
 ### What Are Expansion Packs?
 
-Expansion packs extend BMad-Method beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
+Expansion packs extend BMAD-METHOD™ beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
 
 ### Why Use Expansion Packs?
 
@@ -8565,9 +8596,10 @@ 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
 
 ## Creative Expansion
@@ -8604,9 +8636,10 @@ 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
 
 ## Core Reflective Methods
@@ -8761,10 +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 ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
-- `==================== END: .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 ====================`
+- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
-- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.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,10 @@ 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
 
 ## Purpose
@@ -284,9 +285,10 @@ 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)
 
 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@@ -304,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
 
@@ -388,9 +390,10 @@ 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
 
 ## Purpose
@@ -466,14 +469,15 @@ 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 ====================
-# BMad Knowledge Base
+<!-- Powered by BMAD™ Core -->
+# BMAD™ Knowledge Base
 
 ## Overview
 
-BMad-Method (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
+BMAD-METHOD™ (Breakthrough Method of Agile AI-driven Development) is a framework that combines AI agents with Agile development methodologies. The v4 system introduces a modular architecture with improved dependency management, bundle optimization, and support for both web and IDE environments.
 
 ### Key Features
 
@@ -572,15 +576,15 @@ npx bmad-method install
   - **Roo Code**: Web-based IDE with agent support
   - **GitHub Copilot**: VS Code extension with AI peer programming assistant
 
-**Note for VS Code Users**: BMad-Method assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMad agents. The installer includes built-in support for Cline and Roo.
+**Note for VS Code Users**: BMAD-METHOD™ assumes when you mention "VS Code" that you're using it with an AI-powered extension like GitHub Copilot, Cline, or Roo. Standard VS Code without AI capabilities cannot run BMad agents. The installer includes built-in support for Cline and Roo.
 
 **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
 
-**Remember**: At its core, BMad-Method is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
+**Remember**: At its core, BMAD-METHOD™ is about mastering and harnessing prompt engineering. Any IDE with AI agent support can use BMad - the framework provides the structured prompts and workflows that make AI development effective
 
 ### Environment Selection Guide
 
@@ -824,7 +828,7 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
 
 ### System Overview
 
-The BMad-Method is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
+The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
 
 ### Key Architectural Components
 
@@ -1179,7 +1183,7 @@ Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic sh
 - **Keep conversations focused** - One agent, one task per conversation
 - **Review everything** - Always review and approve before marking complete
 
-## Contributing to BMad-Method
+## Contributing to BMAD-METHOD™
 
 ### Quick Contribution Guidelines
 
@@ -1211,7 +1215,7 @@ For full details, see `CONTRIBUTING.md`. Key points:
 
 ### What Are Expansion Packs?
 
-Expansion packs extend BMad-Method beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
+Expansion packs extend BMAD-METHOD™ beyond traditional software development into ANY domain. They provide specialized agent teams, templates, and workflows while keeping the core framework lean and focused on development.
 
 ### Why Use Expansion Packs?
 
@@ -1275,9 +1279,10 @@ 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
 
 ## Core Reflective Methods
@@ -1432,9 +1437,10 @@ 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
 
 Enables BMad orchestrator to manage and execute team workflows.
@@ -1504,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 ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
-- `==================== END: .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 ====================`
+- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
-- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.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,10 @@ 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
 
 Implement fixes based on QA results (gate and assessments) for a specific story. This task is for the Dev agent to systematically consume QA outputs and apply code/test changes while only updating allowed sections in the story file.
@@ -241,16 +242,17 @@ 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
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
 
 ## 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
 
@@ -258,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
@@ -330,9 +332,10 @@ 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
 
 ## Purpose
@@ -343,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:
@@ -467,9 +470,10 @@ 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
 
 ## Instructions for Developer Agent
@@ -564,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 ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
-- `==================== END: .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 ====================`
+- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
-- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.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,10 @@ 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
 
 ## Purpose
@@ -264,9 +265,10 @@ 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
 
 ## Purpose
@@ -414,14 +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.
@@ -435,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."
@@ -487,9 +490,10 @@ 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
 
 This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@@ -768,9 +772,10 @@ 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)
 
 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@@ -788,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
 
@@ -872,16 +877,17 @@ 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
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
 
 ## 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
 
@@ -889,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
@@ -961,9 +967,10 @@ 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
 
 ## Purpose
@@ -974,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."
@@ -1149,9 +1156,10 @@ 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
   name: Brownfield Enhancement PRD
@@ -1432,9 +1440,10 @@ 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
   name: Product Requirements Document
@@ -1536,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)
@@ -1637,9 +1646,10 @@ 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
 
 **Purpose:** To systematically guide the selected Agent and user through the analysis and planning required when a significant change (pivot, tech issue, missing requirement, failed story) is identified during the BMad workflow.
@@ -1822,9 +1832,10 @@ 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
 
 This checklist serves as a comprehensive framework to ensure the Product Requirements Document (PRD) and Epic definitions are complete, well-structured, and appropriately scoped for MVP development. The PM should systematically work through each item during the product definition process.
@@ -2195,10 +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 ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
-- `==================== END: .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 ====================`
+- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
-- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.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,14 +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.
@@ -117,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."
@@ -169,16 +170,17 @@ 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
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
 
 ## 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
 
@@ -186,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
@@ -258,9 +260,10 @@ 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
 
 ## Purpose
@@ -271,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."
@@ -446,9 +449,10 @@ 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
 
 ## Purpose
@@ -459,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:
@@ -583,9 +587,10 @@ 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
   name: Story Document
@@ -723,9 +728,10 @@ 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
 
 **Purpose:** To systematically guide the selected Agent and user through the analysis and planning required when a significant change (pivot, tech issue, missing requirement, failed story) is identified during the BMad workflow.
@@ -908,9 +914,10 @@ 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
 
 This checklist serves as a comprehensive framework for the Product Owner to validate project plans before development execution. It adapts intelligently based on project type (greenfield vs brownfield) and includes UI/UX considerations when applicable.
@@ -1343,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 ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
-- `==================== END: .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 ====================`
+- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
-- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.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,10 @@ 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
 
 Quick NFR validation focused on the core four: security, performance, reliability, maintainability.
@@ -454,9 +455,10 @@ 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
 
 Create or update a quality gate decision file for a story based on review findings.
@@ -618,9 +620,10 @@ 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
 
 Perform a comprehensive test architecture review with quality gate decision. This adaptive, risk-aware review creates both a story update and a detailed gate file.
@@ -935,9 +938,10 @@ 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
 
 Generate a comprehensive risk assessment matrix for a story implementation using probability × impact analysis.
@@ -1291,9 +1295,10 @@ 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
 
 Create comprehensive test scenarios with appropriate test level recommendations for story implementation.
@@ -1468,9 +1473,10 @@ 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
 
 Map story requirements to test cases using Given-When-Then patterns for comprehensive traceability.
@@ -1735,9 +1741,10 @@ 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
   name: Quality Gate Decision
@@ -1840,9 +1847,10 @@ 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
   name: Story Document
@@ -1980,10 +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 ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
-- `==================== END: .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 ====================`
+- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
-- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.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,14 +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.
@@ -103,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."
@@ -155,9 +156,10 @@ 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
 
 ## Purpose
@@ -168,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.*`
 
@@ -262,24 +264,25 @@ 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`
+  - 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 ====================
+==================== 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
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
 
 ## 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
 
@@ -287,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
@@ -359,9 +362,10 @@ 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
   name: Story Document
@@ -499,9 +503,10 @@ 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
 
 The Scrum Master should use this checklist to validate that each story contains sufficient context for a developer agent to implement it successfully, while assuming the dev agent has reasonable capabilities to figure things out.
@@ -655,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 ====================`
+- `==================== START: bmad-core/folder/filename.md ====================`
-- `==================== END: .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 ====================`
+- `utils: template-format` → Look for `==================== START: bmad-core/utils/template-format.md ====================`
-- `tasks: create-story` → Look for `==================== START: .bmad-core/tasks/create-story.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,10 @@ 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)
 
 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@@ -106,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
 
@@ -190,16 +191,17 @@ 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
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
 
 ## 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
 
@@ -207,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
@@ -279,9 +281,10 @@ 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
 
 ## Purpose
@@ -333,9 +336,10 @@ 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
   name: UI/UX Specification
@@ -685,10 +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

@@ -95,6 +95,7 @@ dependencies:
 ==================== END: .bmad-2d-phaser-game-dev/agents/game-designer.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/tasks/create-doc.md ====================
+<!-- Powered by BMAD™ Core -->
 # Create Document from Template (YAML Driven)
 
 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@@ -112,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
 
@@ -199,6 +200,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 ==================== END: .bmad-2d-phaser-game-dev/tasks/create-doc.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@@ -288,6 +290,7 @@ The LLM will:
 ==================== END: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/tasks/game-design-brainstorming.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Design Brainstorming Techniques Task
 
 This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
@@ -581,6 +584,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
 ==================== END: .bmad-2d-phaser-game-dev/tasks/game-design-brainstorming.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/tasks/create-deep-research-prompt.md ====================
+<!-- Powered by BMAD™ Core -->
 # Create Deep Research Prompt Task
 
 This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@@ -862,6 +866,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
 ==================== END: .bmad-2d-phaser-game-dev/tasks/create-deep-research-prompt.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
+<!-- Powered by BMAD™ Core -->
 # Advanced Game Design Elicitation Task
 
 ## Purpose
@@ -975,6 +980,7 @@ The questions and perspectives offered should always consider:
 ==================== END: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/templates/game-design-doc-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: game-design-doc-template-v2
   name: Game Design Document (GDD)
@@ -1321,6 +1327,7 @@ sections:
 ==================== END: .bmad-2d-phaser-game-dev/templates/game-design-doc-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/templates/level-design-doc-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: level-design-doc-template-v2
   name: Level Design Document
@@ -1808,6 +1815,7 @@ sections:
 ==================== END: .bmad-2d-phaser-game-dev/templates/level-design-doc-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/templates/game-brief-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: game-brief-template-v2
   name: Game Brief
@@ -2167,6 +2175,7 @@ sections:
 ==================== END: .bmad-2d-phaser-game-dev/templates/game-brief-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/checklists/game-design-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Design Document Quality Checklist
 
 ## Document Completeness

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

@@ -102,6 +102,7 @@ dependencies:
 ==================== END: .bmad-2d-phaser-game-dev/agents/game-developer.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@@ -191,6 +192,7 @@ The LLM will:
 ==================== END: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/templates/game-architecture-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: game-architecture-template-v2
   name: Game Architecture Document
@@ -807,6 +809,7 @@ sections:
 ==================== END: .bmad-2d-phaser-game-dev/templates/game-architecture-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Development Story Definition of Done Checklist
 
 ## Story Completeness
@@ -970,6 +973,7 @@ _Any specific concerns, recommendations, or clarifications needed before develop
 ==================== END: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/data/development-guidelines.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Development Guidelines
 
 ## Overview

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

@@ -88,6 +88,7 @@ dependencies:
 ==================== END: .bmad-2d-phaser-game-dev/agents/game-sm.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
+<!-- Powered by BMAD™ Core -->
 # Create Game Development Story Task
 
 ## Purpose
@@ -307,6 +308,7 @@ This task ensures game development stories are immediately actionable and enable
 ==================== END: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@@ -396,6 +398,7 @@ The LLM will:
 ==================== END: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/templates/game-story-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: game-story-template-v2
   name: Game Development Story
@@ -652,6 +655,7 @@ sections:
 ==================== END: .bmad-2d-phaser-game-dev/templates/game-story-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Development Story Definition of Done Checklist
 
 ## Story Completeness

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

@@ -40,6 +40,7 @@ These references map directly to bundle sections:
 
 
 ==================== START: .bmad-2d-phaser-game-dev/agent-teams/phaser-2d-nodejs-game-team.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 bundle:
   name: Phaser 2D NodeJS Game Team
   icon: 🎮
@@ -412,6 +413,7 @@ dependencies:
 ==================== END: .bmad-2d-phaser-game-dev/agents/game-sm.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/data/bmad-kb.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Development BMad Knowledge Base
 
 ## Overview
@@ -665,6 +667,7 @@ This knowledge base provides the foundation for effective game development using
 ==================== END: .bmad-2d-phaser-game-dev/data/bmad-kb.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/data/brainstorming-techniques.md ====================
+<!-- Powered by BMAD™ Core -->
 # Brainstorming Techniques Data
 
 ## Creative Expansion
@@ -704,6 +707,7 @@ This knowledge base provides the foundation for effective game development using
 ==================== END: .bmad-2d-phaser-game-dev/data/brainstorming-techniques.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
+<!-- Powered by BMAD™ Core -->
 # Advanced Game Design Elicitation Task
 
 ## Purpose
@@ -817,6 +821,7 @@ The questions and perspectives offered should always consider:
 ==================== END: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/tasks/create-deep-research-prompt.md ====================
+<!-- Powered by BMAD™ Core -->
 # Create Deep Research Prompt Task
 
 This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@@ -1098,6 +1103,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
 ==================== END: .bmad-2d-phaser-game-dev/tasks/create-deep-research-prompt.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/tasks/create-doc.md ====================
+<!-- Powered by BMAD™ Core -->
 # Create Document from Template (YAML Driven)
 
 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@@ -1115,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
 
@@ -1202,6 +1208,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 ==================== END: .bmad-2d-phaser-game-dev/tasks/create-doc.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/tasks/document-project.md ====================
+<!-- Powered by BMAD™ Core -->
 # Document an Existing Project
 
 ## Purpose
@@ -1548,6 +1555,7 @@ Apply the advanced elicitation task after major sections to refine based on user
 ==================== END: .bmad-2d-phaser-game-dev/tasks/document-project.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/tasks/facilitate-brainstorming-session.md ====================
+<!-- Powered by BMAD™ Core -->
 ---
 docOutputLocation: docs/brainstorming-session-results.md
 template: '.bmad-2d-phaser-game-dev/templates/brainstorming-output-tmpl.yaml'
@@ -1842,10 +1850,11 @@ sections:
     content: |
       ---
 
-      *Session facilitated using the BMAD-METHOD brainstorming framework*
+      *Session facilitated using the BMAD-METHOD™ brainstorming framework*
 ==================== END: .bmad-2d-phaser-game-dev/templates/brainstorming-output-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/templates/competitor-analysis-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: competitor-analysis-template-v2
   name: Competitive Analysis Report
@@ -2155,6 +2164,7 @@ sections:
 ==================== END: .bmad-2d-phaser-game-dev/templates/competitor-analysis-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/templates/market-research-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: market-research-template-v2
   name: Market Research Report
@@ -2410,6 +2420,7 @@ sections:
 ==================== END: .bmad-2d-phaser-game-dev/templates/market-research-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/templates/project-brief-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: project-brief-template-v2
   name: Project Brief
@@ -2634,6 +2645,7 @@ sections:
 ==================== END: .bmad-2d-phaser-game-dev/templates/project-brief-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/data/elicitation-methods.md ====================
+<!-- Powered by BMAD™ Core -->
 # Elicitation Methods Data
 
 ## Core Reflective Methods
@@ -2791,6 +2803,7 @@ sections:
 ==================== END: .bmad-2d-phaser-game-dev/data/elicitation-methods.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/tasks/kb-mode-interaction.md ====================
+<!-- Powered by BMAD™ Core -->
 # KB Mode Interaction Task
 
 ## Purpose
@@ -2869,6 +2882,7 @@ Or ask me about anything else related to BMad-Method!
 ==================== END: .bmad-2d-phaser-game-dev/tasks/kb-mode-interaction.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/utils/workflow-management.md ====================
+<!-- Powered by BMAD™ Core -->
 # Workflow Management
 
 Enables BMad orchestrator to manage and execute team workflows.
@@ -2941,6 +2955,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
 ==================== END: .bmad-2d-phaser-game-dev/utils/workflow-management.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@@ -3030,6 +3045,7 @@ The LLM will:
 ==================== END: .bmad-2d-phaser-game-dev/tasks/execute-checklist.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/tasks/game-design-brainstorming.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Design Brainstorming Techniques Task
 
 This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
@@ -3323,6 +3339,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
 ==================== END: .bmad-2d-phaser-game-dev/tasks/game-design-brainstorming.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/templates/game-design-doc-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: game-design-doc-template-v2
   name: Game Design Document (GDD)
@@ -3669,6 +3686,7 @@ sections:
 ==================== END: .bmad-2d-phaser-game-dev/templates/game-design-doc-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/templates/level-design-doc-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: level-design-doc-template-v2
   name: Level Design Document
@@ -4156,6 +4174,7 @@ sections:
 ==================== END: .bmad-2d-phaser-game-dev/templates/level-design-doc-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/templates/game-brief-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: game-brief-template-v2
   name: Game Brief
@@ -4515,6 +4534,7 @@ sections:
 ==================== END: .bmad-2d-phaser-game-dev/templates/game-brief-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/checklists/game-design-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Design Document Quality Checklist
 
 ## Document Completeness
@@ -4719,6 +4739,7 @@ _Outline immediate next actions for the team based on this assessment._
 ==================== END: .bmad-2d-phaser-game-dev/checklists/game-design-checklist.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/templates/game-architecture-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: game-architecture-template-v2
   name: Game Architecture Document
@@ -5335,6 +5356,7 @@ sections:
 ==================== END: .bmad-2d-phaser-game-dev/templates/game-architecture-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Development Story Definition of Done Checklist
 
 ## Story Completeness
@@ -5498,6 +5520,7 @@ _Any specific concerns, recommendations, or clarifications needed before develop
 ==================== END: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/data/development-guidelines.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Development Guidelines
 
 ## Overview
@@ -6148,6 +6171,7 @@ These guidelines ensure consistent, high-quality game development that meets per
 ==================== END: .bmad-2d-phaser-game-dev/data/development-guidelines.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
+<!-- Powered by BMAD™ Core -->
 # Create Game Development Story Task
 
 ## Purpose
@@ -6367,6 +6391,7 @@ This task ensures game development stories are immediately actionable and enable
 ==================== END: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/templates/game-story-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: game-story-template-v2
   name: Game Development Story
@@ -6623,6 +6648,7 @@ sections:
 ==================== END: .bmad-2d-phaser-game-dev/templates/game-story-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/templates/game-architecture-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: game-architecture-template-v2
   name: Game Architecture Document
@@ -7239,6 +7265,7 @@ sections:
 ==================== END: .bmad-2d-phaser-game-dev/templates/game-architecture-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/templates/game-brief-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: game-brief-template-v2
   name: Game Brief
@@ -7598,6 +7625,7 @@ sections:
 ==================== END: .bmad-2d-phaser-game-dev/templates/game-brief-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/templates/game-design-doc-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: game-design-doc-template-v2
   name: Game Design Document (GDD)
@@ -7944,6 +7972,7 @@ sections:
 ==================== END: .bmad-2d-phaser-game-dev/templates/game-design-doc-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/templates/game-story-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: game-story-template-v2
   name: Game Development Story
@@ -8200,6 +8229,7 @@ sections:
 ==================== END: .bmad-2d-phaser-game-dev/templates/game-story-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/templates/level-design-doc-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: level-design-doc-template-v2
   name: Level Design Document
@@ -8687,6 +8717,7 @@ sections:
 ==================== END: .bmad-2d-phaser-game-dev/templates/level-design-doc-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
+<!-- Powered by BMAD™ Core -->
 # Advanced Game Design Elicitation Task
 
 ## Purpose
@@ -8800,6 +8831,7 @@ The questions and perspectives offered should always consider:
 ==================== END: .bmad-2d-phaser-game-dev/tasks/advanced-elicitation.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
+<!-- Powered by BMAD™ Core -->
 # Create Game Development Story Task
 
 ## Purpose
@@ -9019,6 +9051,7 @@ This task ensures game development stories are immediately actionable and enable
 ==================== END: .bmad-2d-phaser-game-dev/tasks/create-game-story.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/tasks/game-design-brainstorming.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Design Brainstorming Techniques Task
 
 This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
@@ -9312,6 +9345,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
 ==================== END: .bmad-2d-phaser-game-dev/tasks/game-design-brainstorming.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/checklists/game-design-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Design Document Quality Checklist
 
 ## Document Completeness
@@ -9516,6 +9550,7 @@ _Outline immediate next actions for the team based on this assessment._
 ==================== END: .bmad-2d-phaser-game-dev/checklists/game-design-checklist.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Development Story Definition of Done Checklist
 
 ## Story Completeness
@@ -9679,6 +9714,7 @@ _Any specific concerns, recommendations, or clarifications needed before develop
 ==================== END: .bmad-2d-phaser-game-dev/checklists/game-story-dod-checklist.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/workflows/game-dev-greenfield.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 workflow:
   id: game-dev-greenfield
   name: Game Development - Greenfield Project
@@ -9865,6 +9901,7 @@ workflow:
 ==================== END: .bmad-2d-phaser-game-dev/workflows/game-dev-greenfield.yaml ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/workflows/game-prototype.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 workflow:
   id: game-prototype
   name: Game Prototype Development
@@ -10043,6 +10080,7 @@ workflow:
 ==================== END: .bmad-2d-phaser-game-dev/workflows/game-prototype.yaml ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/data/bmad-kb.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Development BMad Knowledge Base
 
 ## Overview
@@ -10296,6 +10334,7 @@ This knowledge base provides the foundation for effective game development using
 ==================== END: .bmad-2d-phaser-game-dev/data/bmad-kb.md ====================
 
 ==================== START: .bmad-2d-phaser-game-dev/data/development-guidelines.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Development Guidelines
 
 ## Overview

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

@@ -103,6 +103,7 @@ dependencies:
 ==================== END: .bmad-2d-unity-game-dev/agents/game-architect.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/create-doc.md ====================
+<!-- Powered by BMAD™ Core -->
 # Create Document from Template (YAML Driven)
 
 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@@ -120,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
 
@@ -207,6 +208,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 ==================== END: .bmad-2d-unity-game-dev/tasks/create-doc.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/create-deep-research-prompt.md ====================
+<!-- Powered by BMAD™ Core -->
 # Create Deep Research Prompt Task
 
 This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@@ -488,6 +490,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
 ==================== END: .bmad-2d-unity-game-dev/tasks/create-deep-research-prompt.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/shard-doc.md ====================
+<!-- Powered by BMAD™ Core -->
 # Document Sharding Task
 
 ## Purpose
@@ -676,6 +679,7 @@ Document sharded successfully:
 ==================== END: .bmad-2d-unity-game-dev/tasks/shard-doc.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/document-project.md ====================
+<!-- Powered by BMAD™ Core -->
 # Document an Existing Project
 
 ## Purpose
@@ -1022,6 +1026,7 @@ Apply the advanced elicitation task after major sections to refine based on user
 ==================== END: .bmad-2d-unity-game-dev/tasks/document-project.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@@ -1111,6 +1116,7 @@ The LLM will:
 ==================== END: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
+<!-- Powered by BMAD™ Core -->
 # Advanced Game Design Elicitation Task
 
 ## Purpose
@@ -1224,6 +1230,7 @@ The questions and perspectives offered should always consider:
 ==================== END: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/templates/game-architecture-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: game-architecture-template-v3
   name: Game Architecture Document
@@ -2257,6 +2264,7 @@ sections:
 ==================== END: .bmad-2d-unity-game-dev/templates/game-architecture-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-unity-game-dev/checklists/game-architect-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Architect Solution Validation Checklist
 
 This checklist serves as a comprehensive framework for the Game Architect to validate the technical design and architecture before game development execution. The Game Architect should systematically work through each item, ensuring the game architecture is robust, scalable, performant, and aligned with the Game Design Document requirements.
@@ -2651,6 +2659,7 @@ After presenting the report, ask the user if they would like detailed analysis o
 ==================== END: .bmad-2d-unity-game-dev/checklists/game-architect-checklist.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/data/development-guidelines.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Development Guidelines (Unity & C#)
 
 ## Overview
@@ -3240,6 +3249,7 @@ These guidelines ensure consistent, high-quality game development that meets per
 ==================== END: .bmad-2d-unity-game-dev/data/development-guidelines.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/data/bmad-kb.md ====================
+<!-- Powered by BMAD™ Core -->
 # BMad Knowledge Base - 2D Unity Game Development
 
 ## Overview
@@ -3372,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

@@ -100,6 +100,7 @@ dependencies:
 ==================== END: .bmad-2d-unity-game-dev/agents/game-designer.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/create-doc.md ====================
+<!-- Powered by BMAD™ Core -->
 # Create Document from Template (YAML Driven)
 
 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@@ -117,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
 
@@ -204,6 +205,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 ==================== END: .bmad-2d-unity-game-dev/tasks/create-doc.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@@ -293,6 +295,7 @@ The LLM will:
 ==================== END: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/shard-doc.md ====================
+<!-- Powered by BMAD™ Core -->
 # Document Sharding Task
 
 ## Purpose
@@ -481,6 +484,7 @@ Document sharded successfully:
 ==================== END: .bmad-2d-unity-game-dev/tasks/shard-doc.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/game-design-brainstorming.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Design Brainstorming Techniques Task
 
 This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
@@ -774,6 +778,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
 ==================== END: .bmad-2d-unity-game-dev/tasks/game-design-brainstorming.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/create-deep-research-prompt.md ====================
+<!-- Powered by BMAD™ Core -->
 # Create Deep Research Prompt Task
 
 This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@@ -1055,6 +1060,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
 ==================== END: .bmad-2d-unity-game-dev/tasks/create-deep-research-prompt.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
+<!-- Powered by BMAD™ Core -->
 # Advanced Game Design Elicitation Task
 
 ## Purpose
@@ -1168,6 +1174,7 @@ The questions and perspectives offered should always consider:
 ==================== END: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/templates/game-design-doc-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: game-design-doc-template-v3
   name: Game Design Document (GDD)
@@ -1876,6 +1883,7 @@ sections:
 ==================== END: .bmad-2d-unity-game-dev/templates/game-design-doc-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-unity-game-dev/templates/level-design-doc-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: level-design-doc-template-v2
   name: Level Design Document
@@ -2363,6 +2371,7 @@ sections:
 ==================== END: .bmad-2d-unity-game-dev/templates/level-design-doc-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-unity-game-dev/templates/game-brief-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: game-brief-template-v3
   name: Game Brief
@@ -2722,6 +2731,7 @@ sections:
 ==================== END: .bmad-2d-unity-game-dev/templates/game-brief-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-unity-game-dev/checklists/game-design-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Design Document Quality Checklist
 
 ## Document Completeness
@@ -2926,6 +2936,7 @@ _Outline immediate next actions for the team based on this assessment._
 ==================== END: .bmad-2d-unity-game-dev/checklists/game-design-checklist.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/data/bmad-kb.md ====================
+<!-- Powered by BMAD™ Core -->
 # BMad Knowledge Base - 2D Unity Game Development
 
 ## Overview
@@ -3058,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

@@ -97,6 +97,7 @@ dependencies:
 ==================== END: .bmad-2d-unity-game-dev/agents/game-developer.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@@ -186,6 +187,7 @@ The LLM will:
 ==================== END: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/validate-next-story.md ====================
+<!-- Powered by BMAD™ Core -->
 # Validate Next Story Task
 
 ## Purpose
@@ -196,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:
@@ -323,6 +325,7 @@ Provide a structured validation report including:
 ==================== END: .bmad-2d-unity-game-dev/tasks/validate-next-story.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/checklists/game-story-dod-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Development Story Definition of Done (DoD) Checklist
 
 ## Instructions for Developer Agent

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

@@ -88,6 +88,7 @@ dependencies:
 ==================== END: .bmad-2d-unity-game-dev/agents/game-sm.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/create-game-story.md ====================
+<!-- Powered by BMAD™ Core -->
 # Create Game Story Task
 
 ## Purpose
@@ -275,6 +276,7 @@ This task ensures game development stories are immediately actionable and enable
 ==================== END: .bmad-2d-unity-game-dev/tasks/create-game-story.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@@ -364,6 +366,7 @@ The LLM will:
 ==================== END: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/correct-course-game.md ====================
+<!-- Powered by BMAD™ Core -->
 # Correct Course Task - Game Development
 
 ## Purpose
@@ -508,6 +511,7 @@ Based on the analysis and agreed path forward:
 ==================== END: .bmad-2d-unity-game-dev/tasks/correct-course-game.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/templates/game-story-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: game-story-template-v3
   name: Game Development Story
@@ -767,6 +771,7 @@ sections:
 ==================== END: .bmad-2d-unity-game-dev/templates/game-story-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-unity-game-dev/checklists/game-change-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Development Change Navigation Checklist
 
 **Purpose:** To systematically guide the Game SM agent and user through analysis and planning when a significant change (performance issue, platform constraint, technical blocker, gameplay feedback) is identified during Unity game development.

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

@@ -40,6 +40,7 @@ These references map directly to bundle sections:
 
 
 ==================== START: .bmad-2d-unity-game-dev/agent-teams/unity-2d-game-team.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 bundle:
   name: Unity 2D Game Team
   icon: 🎮
@@ -476,6 +477,7 @@ dependencies:
 ==================== END: .bmad-2d-unity-game-dev/agents/game-sm.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/data/bmad-kb.md ====================
+<!-- Powered by BMAD™ Core -->
 # BMad Knowledge Base - 2D Unity Game Development
 
 ## Overview
@@ -608,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)
@@ -1248,6 +1250,7 @@ This knowledge base provides the foundation for effective game development using
 ==================== END: .bmad-2d-unity-game-dev/data/bmad-kb.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/data/brainstorming-techniques.md ====================
+<!-- Powered by BMAD™ Core -->
 # Brainstorming Techniques Data
 
 ## Creative Expansion
@@ -1287,6 +1290,7 @@ This knowledge base provides the foundation for effective game development using
 ==================== END: .bmad-2d-unity-game-dev/data/brainstorming-techniques.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
+<!-- Powered by BMAD™ Core -->
 # Advanced Game Design Elicitation Task
 
 ## Purpose
@@ -1400,6 +1404,7 @@ The questions and perspectives offered should always consider:
 ==================== END: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/create-deep-research-prompt.md ====================
+<!-- Powered by BMAD™ Core -->
 # Create Deep Research Prompt Task
 
 This task helps create comprehensive research prompts for various types of deep analysis. It can process inputs from brainstorming sessions, project briefs, market research, or specific research questions to generate targeted prompts for deeper investigation.
@@ -1681,6 +1686,7 @@ CRITICAL: collaborate with the user to develop specific, actionable research que
 ==================== END: .bmad-2d-unity-game-dev/tasks/create-deep-research-prompt.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/create-doc.md ====================
+<!-- Powered by BMAD™ Core -->
 # Create Document from Template (YAML Driven)
 
 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@@ -1698,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
 
@@ -1785,6 +1791,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 ==================== END: .bmad-2d-unity-game-dev/tasks/create-doc.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/document-project.md ====================
+<!-- Powered by BMAD™ Core -->
 # Document an Existing Project
 
 ## Purpose
@@ -2131,6 +2138,7 @@ Apply the advanced elicitation task after major sections to refine based on user
 ==================== END: .bmad-2d-unity-game-dev/tasks/document-project.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/facilitate-brainstorming-session.md ====================
+<!-- Powered by BMAD™ Core -->
 ---
 docOutputLocation: docs/brainstorming-session-results.md
 template: '.bmad-2d-unity-game-dev/templates/brainstorming-output-tmpl.yaml'
@@ -2425,10 +2433,11 @@ sections:
     content: |
       ---
 
-      *Session facilitated using the BMAD-METHOD brainstorming framework*
+      *Session facilitated using the BMAD-METHOD™ brainstorming framework*
 ==================== END: .bmad-2d-unity-game-dev/templates/brainstorming-output-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-unity-game-dev/templates/competitor-analysis-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: competitor-analysis-template-v2
   name: Competitive Analysis Report
@@ -2738,6 +2747,7 @@ sections:
 ==================== END: .bmad-2d-unity-game-dev/templates/competitor-analysis-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-unity-game-dev/templates/market-research-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: market-research-template-v2
   name: Market Research Report
@@ -2993,6 +3003,7 @@ sections:
 ==================== END: .bmad-2d-unity-game-dev/templates/market-research-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-unity-game-dev/templates/project-brief-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: project-brief-template-v2
   name: Project Brief
@@ -3217,6 +3228,7 @@ sections:
 ==================== END: .bmad-2d-unity-game-dev/templates/project-brief-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-unity-game-dev/data/elicitation-methods.md ====================
+<!-- Powered by BMAD™ Core -->
 # Elicitation Methods Data
 
 ## Core Reflective Methods
@@ -3374,6 +3386,7 @@ sections:
 ==================== END: .bmad-2d-unity-game-dev/data/elicitation-methods.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/kb-mode-interaction.md ====================
+<!-- Powered by BMAD™ Core -->
 # KB Mode Interaction Task
 
 ## Purpose
@@ -3452,6 +3465,7 @@ Or ask me about anything else related to BMad-Method!
 ==================== END: .bmad-2d-unity-game-dev/tasks/kb-mode-interaction.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/utils/workflow-management.md ====================
+<!-- Powered by BMAD™ Core -->
 # Workflow Management
 
 Enables BMad orchestrator to manage and execute team workflows.
@@ -3524,6 +3538,7 @@ Agents should be workflow-aware: know active workflow, their role, access artifa
 ==================== END: .bmad-2d-unity-game-dev/utils/workflow-management.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@@ -3613,6 +3628,7 @@ The LLM will:
 ==================== END: .bmad-2d-unity-game-dev/tasks/execute-checklist.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/shard-doc.md ====================
+<!-- Powered by BMAD™ Core -->
 # Document Sharding Task
 
 ## Purpose
@@ -3801,6 +3817,7 @@ Document sharded successfully:
 ==================== END: .bmad-2d-unity-game-dev/tasks/shard-doc.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/game-design-brainstorming.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Design Brainstorming Techniques Task
 
 This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
@@ -4094,6 +4111,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
 ==================== END: .bmad-2d-unity-game-dev/tasks/game-design-brainstorming.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/templates/game-design-doc-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: game-design-doc-template-v3
   name: Game Design Document (GDD)
@@ -4802,6 +4820,7 @@ sections:
 ==================== END: .bmad-2d-unity-game-dev/templates/game-design-doc-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-unity-game-dev/templates/level-design-doc-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: level-design-doc-template-v2
   name: Level Design Document
@@ -5289,6 +5308,7 @@ sections:
 ==================== END: .bmad-2d-unity-game-dev/templates/level-design-doc-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-unity-game-dev/templates/game-brief-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: game-brief-template-v3
   name: Game Brief
@@ -5648,6 +5668,7 @@ sections:
 ==================== END: .bmad-2d-unity-game-dev/templates/game-brief-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-unity-game-dev/checklists/game-design-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Design Document Quality Checklist
 
 ## Document Completeness
@@ -5852,6 +5873,7 @@ _Outline immediate next actions for the team based on this assessment._
 ==================== END: .bmad-2d-unity-game-dev/checklists/game-design-checklist.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/templates/game-architecture-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: game-architecture-template-v3
   name: Game Architecture Document
@@ -6885,6 +6907,7 @@ sections:
 ==================== END: .bmad-2d-unity-game-dev/templates/game-architecture-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-unity-game-dev/checklists/game-architect-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Architect Solution Validation Checklist
 
 This checklist serves as a comprehensive framework for the Game Architect to validate the technical design and architecture before game development execution. The Game Architect should systematically work through each item, ensuring the game architecture is robust, scalable, performant, and aligned with the Game Design Document requirements.
@@ -7279,6 +7302,7 @@ After presenting the report, ask the user if they would like detailed analysis o
 ==================== END: .bmad-2d-unity-game-dev/checklists/game-architect-checklist.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/data/development-guidelines.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Development Guidelines (Unity & C#)
 
 ## Overview
@@ -7868,6 +7892,7 @@ These guidelines ensure consistent, high-quality game development that meets per
 ==================== END: .bmad-2d-unity-game-dev/data/development-guidelines.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/validate-next-story.md ====================
+<!-- Powered by BMAD™ Core -->
 # Validate Next Story Task
 
 ## Purpose
@@ -7878,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:
@@ -8005,6 +8030,7 @@ Provide a structured validation report including:
 ==================== END: .bmad-2d-unity-game-dev/tasks/validate-next-story.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/checklists/game-story-dod-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Development Story Definition of Done (DoD) Checklist
 
 ## Instructions for Developer Agent
@@ -8132,6 +8158,7 @@ Be honest - it's better to flag issues now than have them discovered during play
 ==================== END: .bmad-2d-unity-game-dev/checklists/game-story-dod-checklist.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/create-game-story.md ====================
+<!-- Powered by BMAD™ Core -->
 # Create Game Story Task
 
 ## Purpose
@@ -8319,6 +8346,7 @@ This task ensures game development stories are immediately actionable and enable
 ==================== END: .bmad-2d-unity-game-dev/tasks/create-game-story.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/correct-course-game.md ====================
+<!-- Powered by BMAD™ Core -->
 # Correct Course Task - Game Development
 
 ## Purpose
@@ -8463,6 +8491,7 @@ Based on the analysis and agreed path forward:
 ==================== END: .bmad-2d-unity-game-dev/tasks/correct-course-game.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/templates/game-story-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: game-story-template-v3
   name: Game Development Story
@@ -8722,6 +8751,7 @@ sections:
 ==================== END: .bmad-2d-unity-game-dev/templates/game-story-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-unity-game-dev/checklists/game-change-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Development Change Navigation Checklist
 
 **Purpose:** To systematically guide the Game SM agent and user through analysis and planning when a significant change (performance issue, platform constraint, technical blocker, gameplay feedback) is identified during Unity game development.
@@ -8928,6 +8958,7 @@ Keep it technically precise and actionable.]]
 ==================== END: .bmad-2d-unity-game-dev/checklists/game-change-checklist.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/templates/game-architecture-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: game-architecture-template-v3
   name: Game Architecture Document
@@ -9961,6 +9992,7 @@ sections:
 ==================== END: .bmad-2d-unity-game-dev/templates/game-architecture-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-unity-game-dev/templates/game-brief-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: game-brief-template-v3
   name: Game Brief
@@ -10320,6 +10352,7 @@ sections:
 ==================== END: .bmad-2d-unity-game-dev/templates/game-brief-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-unity-game-dev/templates/game-design-doc-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: game-design-doc-template-v3
   name: Game Design Document (GDD)
@@ -11028,6 +11061,7 @@ sections:
 ==================== END: .bmad-2d-unity-game-dev/templates/game-design-doc-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-unity-game-dev/templates/game-story-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: game-story-template-v3
   name: Game Development Story
@@ -11287,6 +11321,7 @@ sections:
 ==================== END: .bmad-2d-unity-game-dev/templates/game-story-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-unity-game-dev/templates/level-design-doc-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 template:
   id: level-design-doc-template-v2
   name: Level Design Document
@@ -11774,6 +11809,7 @@ sections:
 ==================== END: .bmad-2d-unity-game-dev/templates/level-design-doc-tmpl.yaml ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
+<!-- Powered by BMAD™ Core -->
 # Advanced Game Design Elicitation Task
 
 ## Purpose
@@ -11887,6 +11923,7 @@ The questions and perspectives offered should always consider:
 ==================== END: .bmad-2d-unity-game-dev/tasks/advanced-elicitation.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/correct-course-game.md ====================
+<!-- Powered by BMAD™ Core -->
 # Correct Course Task - Game Development
 
 ## Purpose
@@ -12031,6 +12068,7 @@ Based on the analysis and agreed path forward:
 ==================== END: .bmad-2d-unity-game-dev/tasks/correct-course-game.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/create-game-story.md ====================
+<!-- Powered by BMAD™ Core -->
 # Create Game Story Task
 
 ## Purpose
@@ -12218,6 +12256,7 @@ This task ensures game development stories are immediately actionable and enable
 ==================== END: .bmad-2d-unity-game-dev/tasks/create-game-story.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/game-design-brainstorming.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Design Brainstorming Techniques Task
 
 This task provides a comprehensive toolkit of creative brainstorming techniques specifically designed for game design ideation and innovative thinking. The game designer can use these techniques to facilitate productive brainstorming sessions focused on game mechanics, player experience, and creative concepts.
@@ -12511,6 +12550,7 @@ This task provides a comprehensive toolkit of creative brainstorming techniques
 ==================== END: .bmad-2d-unity-game-dev/tasks/game-design-brainstorming.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/tasks/validate-game-story.md ====================
+<!-- Powered by BMAD™ Core -->
 # Validate Game Story Task
 
 ## Purpose
@@ -12714,6 +12754,7 @@ Based on validation results, provide specific recommendations for:
 ==================== END: .bmad-2d-unity-game-dev/tasks/validate-game-story.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/checklists/game-architect-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Architect Solution Validation Checklist
 
 This checklist serves as a comprehensive framework for the Game Architect to validate the technical design and architecture before game development execution. The Game Architect should systematically work through each item, ensuring the game architecture is robust, scalable, performant, and aligned with the Game Design Document requirements.
@@ -13108,6 +13149,7 @@ After presenting the report, ask the user if they would like detailed analysis o
 ==================== END: .bmad-2d-unity-game-dev/checklists/game-architect-checklist.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/checklists/game-change-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Development Change Navigation Checklist
 
 **Purpose:** To systematically guide the Game SM agent and user through analysis and planning when a significant change (performance issue, platform constraint, technical blocker, gameplay feedback) is identified during Unity game development.
@@ -13314,6 +13356,7 @@ Keep it technically precise and actionable.]]
 ==================== END: .bmad-2d-unity-game-dev/checklists/game-change-checklist.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/checklists/game-design-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Design Document Quality Checklist
 
 ## Document Completeness
@@ -13518,6 +13561,7 @@ _Outline immediate next actions for the team based on this assessment._
 ==================== END: .bmad-2d-unity-game-dev/checklists/game-design-checklist.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/checklists/game-story-dod-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Development Story Definition of Done (DoD) Checklist
 
 ## Instructions for Developer Agent
@@ -13645,6 +13689,7 @@ Be honest - it's better to flag issues now than have them discovered during play
 ==================== END: .bmad-2d-unity-game-dev/checklists/game-story-dod-checklist.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/workflows/game-dev-greenfield.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 workflow:
   id: unity-game-dev-greenfield
   name: Game Development - Greenfield Project (Unity)
@@ -13831,6 +13876,7 @@ workflow:
 ==================== END: .bmad-2d-unity-game-dev/workflows/game-dev-greenfield.yaml ====================
 
 ==================== START: .bmad-2d-unity-game-dev/workflows/game-prototype.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 workflow:
   id: unity-game-prototype
   name: Game Prototype Development (Unity)
@@ -14009,6 +14055,7 @@ workflow:
 ==================== END: .bmad-2d-unity-game-dev/workflows/game-prototype.yaml ====================
 
 ==================== START: .bmad-2d-unity-game-dev/data/bmad-kb.md ====================
+<!-- Powered by BMAD™ Core -->
 # BMad Knowledge Base - 2D Unity Game Development
 
 ## Overview
@@ -14141,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)
@@ -14781,6 +14828,7 @@ This knowledge base provides the foundation for effective game development using
 ==================== END: .bmad-2d-unity-game-dev/data/bmad-kb.md ====================
 
 ==================== START: .bmad-2d-unity-game-dev/data/development-guidelines.md ====================
+<!-- Powered by BMAD™ Core -->
 # Game Development Guidelines (Unity & C#)
 
 ## Overview

dist/expansion-packs/bmad-creative-writing/agents/beta-reader.txt

@@ -116,6 +116,7 @@ Remember to present all options as numbered lists for easy selection.
 ==================== END: .bmad-creative-writing/agents/beta-reader.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
+<!-- Powered by BMAD™ Core -->
 # Create Document from Template (YAML Driven)
 
 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@@ -220,6 +221,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 ==================== END: .bmad-creative-writing/tasks/create-doc.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/provide-feedback.md ====================
+<!-- Powered by BMAD™ Core -->
 # ------------------------------------------------------------
 
 # 5. Provide Feedback (Beta)
@@ -245,6 +247,7 @@ inputs:
 ==================== END: .bmad-creative-writing/tasks/provide-feedback.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/quick-feedback.md ====================
+<!-- Powered by BMAD™ Core -->
 # ------------------------------------------------------------
 
 # 13. Quick Feedback (Serial)
@@ -268,6 +271,7 @@ inputs:
 ==================== END: .bmad-creative-writing/tasks/quick-feedback.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/analyze-reader-feedback.md ====================
+<!-- Powered by BMAD™ Core -->
 # ------------------------------------------------------------
 
 # 16. Analyze Reader Feedback
@@ -292,6 +296,7 @@ inputs:
 ==================== END: .bmad-creative-writing/tasks/analyze-reader-feedback.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@@ -381,6 +386,7 @@ The LLM will:
 ==================== END: .bmad-creative-writing/tasks/execute-checklist.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
+<!-- Powered by BMAD™ Core -->
 # Advanced Elicitation Task
 
 ## Purpose
@@ -501,6 +507,7 @@ Choose a number (0-8) or 9 to proceed:
 ==================== END: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
 
 ==================== START: .bmad-creative-writing/templates/beta-feedback-form.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 ---
 template:
   id: beta-feedback-form-tmpl
@@ -600,6 +607,7 @@ sections:
 ==================== END: .bmad-creative-writing/templates/beta-feedback-form.yaml ====================
 
 ==================== START: .bmad-creative-writing/checklists/beta-feedback-closure-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # ------------------------------------------------------------
 
 # 6. Beta‑Feedback Closure Checklist
@@ -624,6 +632,7 @@ items:
 ==================== END: .bmad-creative-writing/checklists/beta-feedback-closure-checklist.md ====================
 
 ==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
+<!-- Powered by BMAD™ Core -->
 # BMad Creative Writing Knowledge Base
 
 ## Overview
@@ -834,6 +843,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
 ==================== END: .bmad-creative-writing/data/bmad-kb.md ====================
 
 ==================== START: .bmad-creative-writing/data/story-structures.md ====================
+<!-- Powered by BMAD™ Core -->
 # Story Structure Patterns
 
 ## Three-Act Structure

dist/expansion-packs/bmad-creative-writing/agents/character-psychologist.txt

@@ -115,6 +115,7 @@ Remember to present all options as numbered lists for easy selection.
 ==================== END: .bmad-creative-writing/agents/character-psychologist.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
+<!-- Powered by BMAD™ Core -->
 # Create Document from Template (YAML Driven)
 
 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@@ -219,6 +220,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 ==================== END: .bmad-creative-writing/tasks/create-doc.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/develop-character.md ====================
+<!-- Powered by BMAD™ Core -->
 # ------------------------------------------------------------
 
 # 3. Develop Character
@@ -244,6 +246,7 @@ inputs:
 ==================== END: .bmad-creative-writing/tasks/develop-character.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/workshop-dialog.md ====================
+<!-- Powered by BMAD™ Core -->
 # Workshop Dialog
 
 ## Purpose
@@ -309,6 +312,7 @@ Refined dialog with stronger voices and dramatic impact
 ==================== END: .bmad-creative-writing/tasks/workshop-dialog.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/character-depth-pass.md ====================
+<!-- Powered by BMAD™ Core -->
 # ------------------------------------------------------------
 
 # 9. Character Depth Pass
@@ -332,6 +336,7 @@ inputs:
 ==================== END: .bmad-creative-writing/tasks/character-depth-pass.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@@ -421,6 +426,7 @@ The LLM will:
 ==================== END: .bmad-creative-writing/tasks/execute-checklist.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
+<!-- Powered by BMAD™ Core -->
 # Advanced Elicitation Task
 
 ## Purpose
@@ -541,6 +547,7 @@ Choose a number (0-8) or 9 to proceed:
 ==================== END: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
 
 ==================== START: .bmad-creative-writing/templates/character-profile-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 ---
 template:
   id: character-profile
@@ -635,6 +642,7 @@ sections:
 ==================== END: .bmad-creative-writing/templates/character-profile-tmpl.yaml ====================
 
 ==================== START: .bmad-creative-writing/checklists/character-consistency-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # ------------------------------------------------------------
 
 # 1. Character Consistency Checklist
@@ -659,6 +667,7 @@ items:
 ==================== END: .bmad-creative-writing/checklists/character-consistency-checklist.md ====================
 
 ==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
+<!-- Powered by BMAD™ Core -->
 # BMad Creative Writing Knowledge Base
 
 ## Overview

dist/expansion-packs/bmad-creative-writing/agents/dialog-specialist.txt

@@ -114,6 +114,7 @@ Remember to present all options as numbered lists for easy selection.
 ==================== END: .bmad-creative-writing/agents/dialog-specialist.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
+<!-- Powered by BMAD™ Core -->
 # Create Document from Template (YAML Driven)
 
 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@@ -218,6 +219,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 ==================== END: .bmad-creative-writing/tasks/create-doc.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/workshop-dialog.md ====================
+<!-- Powered by BMAD™ Core -->
 # Workshop Dialog
 
 ## Purpose
@@ -283,6 +285,7 @@ Refined dialog with stronger voices and dramatic impact
 ==================== END: .bmad-creative-writing/tasks/workshop-dialog.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@@ -372,6 +375,7 @@ The LLM will:
 ==================== END: .bmad-creative-writing/tasks/execute-checklist.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
+<!-- Powered by BMAD™ Core -->
 # Advanced Elicitation Task
 
 ## Purpose
@@ -492,6 +496,7 @@ Choose a number (0-8) or 9 to proceed:
 ==================== END: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
 
 ==================== START: .bmad-creative-writing/templates/character-profile-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 ---
 template:
   id: character-profile
@@ -586,6 +591,7 @@ sections:
 ==================== END: .bmad-creative-writing/templates/character-profile-tmpl.yaml ====================
 
 ==================== START: .bmad-creative-writing/checklists/comedic-timing-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # ------------------------------------------------------------
 
 # 23. Comedic Timing & Humor Checklist
@@ -610,6 +616,7 @@ items:
 ==================== END: .bmad-creative-writing/checklists/comedic-timing-checklist.md ====================
 
 ==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
+<!-- Powered by BMAD™ Core -->
 # BMad Creative Writing Knowledge Base
 
 ## Overview
@@ -820,6 +827,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
 ==================== END: .bmad-creative-writing/data/bmad-kb.md ====================
 
 ==================== START: .bmad-creative-writing/data/story-structures.md ====================
+<!-- Powered by BMAD™ Core -->
 # Story Structure Patterns
 
 ## Three-Act Structure

dist/expansion-packs/bmad-creative-writing/agents/editor.txt

@@ -115,6 +115,7 @@ Remember to present all options as numbered lists for easy selection.
 ==================== END: .bmad-creative-writing/agents/editor.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
+<!-- Powered by BMAD™ Core -->
 # Create Document from Template (YAML Driven)
 
 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@@ -219,6 +220,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 ==================== END: .bmad-creative-writing/tasks/create-doc.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/final-polish.md ====================
+<!-- Powered by BMAD™ Core -->
 # ------------------------------------------------------------
 
 # 14. Final Polish
@@ -243,6 +245,7 @@ inputs:
 ==================== END: .bmad-creative-writing/tasks/final-polish.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/incorporate-feedback.md ====================
+<!-- Powered by BMAD™ Core -->
 # ------------------------------------------------------------
 
 # 6. Incorporate Feedback
@@ -269,6 +272,7 @@ inputs:
 ==================== END: .bmad-creative-writing/tasks/incorporate-feedback.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@@ -358,6 +362,7 @@ The LLM will:
 ==================== END: .bmad-creative-writing/tasks/execute-checklist.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
+<!-- Powered by BMAD™ Core -->
 # Advanced Elicitation Task
 
 ## Purpose
@@ -478,6 +483,7 @@ Choose a number (0-8) or 9 to proceed:
 ==================== END: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
 
 ==================== START: .bmad-creative-writing/templates/chapter-draft-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 ---
 template:
   id: chapter-draft-tmpl
@@ -562,6 +568,7 @@ sections:
 ==================== END: .bmad-creative-writing/templates/chapter-draft-tmpl.yaml ====================
 
 ==================== START: .bmad-creative-writing/checklists/line-edit-quality-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # ------------------------------------------------------------
 
 # 4. Line‑Edit Quality Checklist
@@ -586,6 +593,7 @@ items:
 ==================== END: .bmad-creative-writing/checklists/line-edit-quality-checklist.md ====================
 
 ==================== START: .bmad-creative-writing/checklists/publication-readiness-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # ------------------------------------------------------------
 
 # 5. Publication Readiness Checklist
@@ -610,6 +618,7 @@ items:
 ==================== END: .bmad-creative-writing/checklists/publication-readiness-checklist.md ====================
 
 ==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
+<!-- Powered by BMAD™ Core -->
 # BMad Creative Writing Knowledge Base
 
 ## Overview

dist/expansion-packs/bmad-creative-writing/agents/genre-specialist.txt

@@ -117,6 +117,7 @@ Remember to present all options as numbered lists for easy selection.
 ==================== END: .bmad-creative-writing/agents/genre-specialist.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/create-doc.md ====================
+<!-- Powered by BMAD™ Core -->
 # Create Document from Template (YAML Driven)
 
 ## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
@@ -221,6 +222,7 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
 ==================== END: .bmad-creative-writing/tasks/create-doc.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/analyze-story-structure.md ====================
+<!-- Powered by BMAD™ Core -->
 # Analyze Story Structure
 
 ## Purpose
@@ -289,6 +291,7 @@ Comprehensive structural analysis with actionable recommendations
 ==================== END: .bmad-creative-writing/tasks/analyze-story-structure.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/execute-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # Checklist Validation Task
 
 This task provides instructions for validating documentation against checklists. The agent MUST follow these instructions to ensure thorough and systematic validation of documents.
@@ -378,6 +381,7 @@ The LLM will:
 ==================== END: .bmad-creative-writing/tasks/execute-checklist.md ====================
 
 ==================== START: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
+<!-- Powered by BMAD™ Core -->
 # Advanced Elicitation Task
 
 ## Purpose
@@ -498,6 +502,7 @@ Choose a number (0-8) or 9 to proceed:
 ==================== END: .bmad-creative-writing/tasks/advanced-elicitation.md ====================
 
 ==================== START: .bmad-creative-writing/templates/story-outline-tmpl.yaml ====================
+# <!-- Powered by BMAD™ Core -->
 ---
 template:
   id: story-outline
@@ -596,6 +601,7 @@ sections:
 ==================== END: .bmad-creative-writing/templates/story-outline-tmpl.yaml ====================
 
 ==================== START: .bmad-creative-writing/checklists/genre-tropes-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # ------------------------------------------------------------
 
 # 10. Genre Tropes Checklist (General)
@@ -619,6 +625,7 @@ items:
 ==================== END: .bmad-creative-writing/checklists/genre-tropes-checklist.md ====================
 
 ==================== START: .bmad-creative-writing/checklists/fantasy-magic-system-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # ------------------------------------------------------------
 
 # 17. Fantasy Magic System Consistency Checklist
@@ -643,6 +650,7 @@ items:
 ==================== END: .bmad-creative-writing/checklists/fantasy-magic-system-checklist.md ====================
 
 ==================== START: .bmad-creative-writing/checklists/scifi-technology-plausibility-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # ------------------------------------------------------------
 
 # 15. Sci‑Fi Technology Plausibility Checklist
@@ -666,6 +674,7 @@ items:
 ==================== END: .bmad-creative-writing/checklists/scifi-technology-plausibility-checklist.md ====================
 
 ==================== START: .bmad-creative-writing/checklists/romance-emotional-beats-checklist.md ====================
+<!-- Powered by BMAD™ Core -->
 # ------------------------------------------------------------
 
 # 12. Romance Emotional Beats Checklist
@@ -690,6 +699,7 @@ items:
 ==================== END: .bmad-creative-writing/checklists/romance-emotional-beats-checklist.md ====================
 
 ==================== START: .bmad-creative-writing/data/bmad-kb.md ====================
+<!-- Powered by BMAD™ Core -->
 # BMad Creative Writing Knowledge Base
 
 ## Overview
@@ -900,6 +910,7 @@ Remember: BMad Creative Writing provides structure to liberate creativity, not c
 ==================== END: .bmad-creative-writing/data/bmad-kb.md ====================
 
 ==================== START: .bmad-creative-writing/data/story-structures.md ====================
+<!-- Powered by BMAD™ Core -->
 # Story Structure Patterns
 
 ## Three-Act Structure