fix(bmgd): add workflow status update to game-architecture completion (#1161)

* fix(bmgd): add workflow status update to game-architecture completion

The game-architecture workflow was not updating the bmgd-workflow-status.yaml
file on completion, unlike other BMGD workflows (narrative, brainstorm-game).

Changes:
- Add step 4 "Update Workflow Status" to update create-architecture status
- Renumber subsequent steps (5-8 → 6-9)
- Add success metric for workflow status update
- Add failure condition for missing status update

* feat(bmgd): add generate-project-context workflow for game development

Adds a new workflow to create optimized project-context.md files for AI agent
consistency in game development projects.

New workflow files:
- workflow.md: Main workflow entry point
- project-context-template.md: Template for context file
- steps/step-01-discover.md: Context discovery & initialization
- steps/step-02-generate.md: Rules generation with A/P/C menus
- steps/step-03-complete.md: Finalization & optimization

Integration:
- Added generate-project-context trigger to game-architect agent menu
- Added project context creation option to game-architecture completion step
- Renumbered steps 6-9 → 7-10 to accommodate new step 6

Adapted from BMM generate-project-context with game-specific:
- Engine patterns (Unity, Unreal, Godot)
- Performance and frame budget rules
- Platform-specific requirements
- Game testing patterns

---------

Co-authored-by: Scott Jennings <scott.jennings+CIGINT@cloudimperiumgames.com>
Co-authored-by: Brian <bmadcode@gmail.com>

.coderabbit.yaml

@@ -0,0 +1,40 @@
+# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
+
+language: "en-US"
+early_access: true
+reviews:
+  profile: chill
+  high_level_summary: false # don't post summary until explicitly invoked
+  request_changes_workflow: false
+  review_status: false
+  commit_status: false
+  walkthrough: false
+  poem: false
+  auto_review:
+    enabled: false
+    drafts: true # Can review drafts. Since it's manually triggered, it's fine.
+    auto_incremental_review: false # always review the whole PR, not just new commits
+    base_branches:
+      - main
+  path_filters:
+    - "!**/node_modules/**"
+  path_instructions:
+    - path: "**/*"
+      instructions: |
+        Focus on inconsistencies, contradictions, edge cases and serious issues.
+        Avoid commenting on minor issues such as linting, formatting and style issues.
+        When providing code suggestions, use GitHub's suggestion format:
+        ```suggestion
+        <code changes>
+        ```
+    - path: "**/*.js"
+      instructions: |
+        CLI tooling code. Check for: missing error handling on fs operations,
+        path.join vs string concatenation, proper cleanup in error paths.
+        Flag any process.exit() without error message.
+chat:
+  auto_reply: true # Response to mentions in comments, a la @coderabbit review
+issue_enrichment:
+  auto_enrich:
+    enabled: false # don't auto-comment on issues
+

.github/CODE_OF_CONDUCT.md

@@ -60,7 +60,7 @@ representative at an online or offline event.
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
 reported to the community leaders responsible for enforcement at
-the official BMAD Discord server (https://discord.com/invite/gk8jAdXWmj) - DM a moderator or flag a post.
+the official BMAD Discord server (<https://discord.com/invite/gk8jAdXWmj>) - DM a moderator or flag a post.
 All complaints will be reviewed and investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the
@@ -116,7 +116,7 @@ the community.
 
 This Code of Conduct is adapted from the [Contributor Covenant][homepage],
 version 2.0, available at
-https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+<https://www.contributor-covenant.org/version/2/0/code_of_conduct.html>.
 
 Community Impact Guidelines were inspired by [Mozilla's code of conduct
 enforcement ladder](https://github.com/mozilla/diversity).
@@ -124,5 +124,5 @@ enforcement ladder](https://github.com/mozilla/diversity).
 [homepage]: https://www.contributor-covenant.org
 
 For answers to common questions about this code of conduct, see the FAQ at
-https://www.contributor-covenant.org/faq. Translations are available at
-https://www.contributor-covenant.org/translations.
+<https://www.contributor-covenant.org/faq>. Translations are available at
+<https://www.contributor-covenant.org/translations>.

.github/scripts/discord-helpers.sh

@@ -2,8 +2,21 @@
 # Discord notification helper functions
 
 # Escape markdown special chars and @mentions for safe Discord display
-# Bracket expression: ] must be first, then other chars. In POSIX bracket expr, \ is literal.
-esc() { sed -e 's/[][\*_()~`>]/\\&/g' -e 's/@/@ /g'; }
+# Skips content inside <URL> wrappers to preserve URLs intact
+esc() {
+  awk '{
+    result = ""; in_url = 0; n = length($0)
+    for (i = 1; i <= n; i++) {
+      c = substr($0, i, 1)
+      if (c == "<" && substr($0, i, 8) ~ /^<https?:/) in_url = 1
+      if (in_url) { result = result c; if (c == ">") in_url = 0 }
+      else if (c == "@") result = result "@ "
+      else if (index("[]\\*_()~`", c) > 0) result = result "\\" c
+      else result = result c
+    }
+    print result
+  }'
+}
 
 # Truncate to $1 chars (or 80 if wall-of-text with <3 spaces)
 trunc() {
@@ -13,3 +26,9 @@ trunc() {
   [ "$spaces" -lt 3 ] && [ ${#txt} -gt 80 ] && txt=$(printf '%s' "$txt" | cut -c1-80)
   printf '%s' "$txt"
 }
+
+# Remove incomplete URL at end of truncated text (incomplete URLs are useless)
+strip_trailing_url() { sed -E 's~<?https?://[^[:space:]]*$~~'; }
+
+# Wrap URLs in <> to suppress Discord embeds (keeps links clickable)
+wrap_urls() { sed -E 's~https?://[^[:space:]<>]+~<&>~g'; }

.github/workflows/discord.yaml

@@ -53,7 +53,11 @@ jobs:
 
           TITLE=$(printf '%s' "$PR_TITLE" | trunc $MAX_TITLE | esc)
           [ ${#PR_TITLE} -gt $MAX_TITLE ] && TITLE="${TITLE}..."
-          BODY=$(printf '%s' "$PR_BODY" | trunc $MAX_BODY | esc)
+          BODY=$(printf '%s' "$PR_BODY" | trunc $MAX_BODY)
+          if [ -n "$PR_BODY" ] && [ ${#PR_BODY} -gt $MAX_BODY ]; then
+            BODY=$(printf '%s' "$BODY" | strip_trailing_url)
+          fi
+          BODY=$(printf '%s' "$BODY" | wrap_urls | esc)
           [ -n "$PR_BODY" ] && [ ${#PR_BODY} -gt $MAX_BODY ] && BODY="${BODY}..."
           [ -n "$BODY" ] && BODY=" · $BODY"
           USER=$(printf '%s' "$PR_USER" | esc)
@@ -91,7 +95,11 @@ jobs:
 
           TITLE=$(printf '%s' "$ISSUE_TITLE" | trunc $MAX_TITLE | esc)
           [ ${#ISSUE_TITLE} -gt $MAX_TITLE ] && TITLE="${TITLE}..."
-          BODY=$(printf '%s' "$ISSUE_BODY" | trunc $MAX_BODY | esc)
+          BODY=$(printf '%s' "$ISSUE_BODY" | trunc $MAX_BODY)
+          if [ -n "$ISSUE_BODY" ] && [ ${#ISSUE_BODY} -gt $MAX_BODY ]; then
+            BODY=$(printf '%s' "$BODY" | strip_trailing_url)
+          fi
+          BODY=$(printf '%s' "$BODY" | wrap_urls | esc)
           [ -n "$ISSUE_BODY" ] && [ ${#ISSUE_BODY} -gt $MAX_BODY ] && BODY="${BODY}..."
           [ -n "$BODY" ] && BODY=" · $BODY"
           USER=$(printf '%s' "$USER" | esc)
@@ -126,7 +134,11 @@ jobs:
 
           TITLE=$(printf '%s' "$ISSUE_TITLE" | trunc $MAX_TITLE | esc)
           [ ${#ISSUE_TITLE} -gt $MAX_TITLE ] && TITLE="${TITLE}..."
-          BODY=$(printf '%s' "$COMMENT_BODY" | trunc $MAX_BODY | esc)
+          BODY=$(printf '%s' "$COMMENT_BODY" | trunc $MAX_BODY)
+          if [ ${#COMMENT_BODY} -gt $MAX_BODY ]; then
+            BODY=$(printf '%s' "$BODY" | strip_trailing_url)
+          fi
+          BODY=$(printf '%s' "$BODY" | wrap_urls | esc)
           [ ${#COMMENT_BODY} -gt $MAX_BODY ] && BODY="${BODY}..."
           USER=$(printf '%s' "$COMMENT_USER" | esc)
 
@@ -162,7 +174,11 @@ jobs:
 
           TITLE=$(printf '%s' "$PR_TITLE" | trunc $MAX_TITLE | esc)
           [ ${#PR_TITLE} -gt $MAX_TITLE ] && TITLE="${TITLE}..."
-          BODY=$(printf '%s' "$REVIEW_BODY" | trunc $MAX_BODY | esc)
+          BODY=$(printf '%s' "$REVIEW_BODY" | trunc $MAX_BODY)
+          if [ -n "$REVIEW_BODY" ] && [ ${#REVIEW_BODY} -gt $MAX_BODY ]; then
+            BODY=$(printf '%s' "$BODY" | strip_trailing_url)
+          fi
+          BODY=$(printf '%s' "$BODY" | wrap_urls | esc)
           [ -n "$REVIEW_BODY" ] && [ ${#REVIEW_BODY} -gt $MAX_BODY ] && BODY="${BODY}..."
           [ -n "$BODY" ] && BODY=": $BODY"
           USER=$(printf '%s' "$REVIEW_USER" | esc)
@@ -194,7 +210,11 @@ jobs:
 
           TITLE=$(printf '%s' "$PR_TITLE" | trunc $MAX_TITLE | esc)
           [ ${#PR_TITLE} -gt $MAX_TITLE ] && TITLE="${TITLE}..."
-          BODY=$(printf '%s' "$COMMENT_BODY" | trunc $MAX_BODY | esc)
+          BODY=$(printf '%s' "$COMMENT_BODY" | trunc $MAX_BODY)
+          if [ ${#COMMENT_BODY} -gt $MAX_BODY ]; then
+            BODY=$(printf '%s' "$BODY" | strip_trailing_url)
+          fi
+          BODY=$(printf '%s' "$BODY" | wrap_urls | esc)
           [ ${#COMMENT_BODY} -gt $MAX_BODY ] && BODY="${BODY}..."
           USER=$(printf '%s' "$COMMENT_USER" | esc)
 
@@ -224,7 +244,11 @@ jobs:
 
           REL_NAME=$(printf '%s' "$NAME" | trunc $MAX_TITLE | esc)
           [ ${#NAME} -gt $MAX_TITLE ] && REL_NAME="${REL_NAME}..."
-          BODY=$(printf '%s' "$RELEASE_BODY" | trunc $MAX_BODY | esc)
+          BODY=$(printf '%s' "$RELEASE_BODY" | trunc $MAX_BODY)
+          if [ -n "$RELEASE_BODY" ] && [ ${#RELEASE_BODY} -gt $MAX_BODY ]; then
+            BODY=$(printf '%s' "$BODY" | strip_trailing_url)
+          fi
+          BODY=$(printf '%s' "$BODY" | wrap_urls | esc)
           [ -n "$RELEASE_BODY" ] && [ ${#RELEASE_BODY} -gt $MAX_BODY ] && BODY="${BODY}..."
           [ -n "$BODY" ] && BODY=" · $BODY"
           TAG_ESC=$(printf '%s' "$TAG" | esc)
@@ -275,7 +299,7 @@ jobs:
         run: |
           set -o pipefail
           [ -z "$WEBHOOK" ] && exit 0
-          esc() { sed -e 's/[][\*_()~`>]/\\&/g' -e 's/@/@ /g'; }
+          esc() { sed -e 's/[][\*_()~`]/\\&/g' -e 's/@/@ /g'; }
           trunc() { tr '\n\r' '  ' | cut -c1-"$1"; }
 
           REF_TRUNC=$(printf '%s' "$REF" | trunc 100)

.github/workflows/manual-release.yaml

@@ -6,9 +6,11 @@ on:
       version_bump:
         description: Version bump type
         required: true
-        default: patch
+        default: alpha
         type: choice
         options:
+          - alpha
+          - beta
           - patch
           - minor
           - major
@@ -49,7 +51,11 @@ jobs:
           git config user.email "github-actions[bot]@users.noreply.github.com"
 
       - name: Bump version
-        run: npm run version:${{ github.event.inputs.version_bump }}
+        run: |
+          case "${{ github.event.inputs.version_bump }}" in
+            alpha|beta) npm version prerelease --no-git-tag-version --preid=${{ github.event.inputs.version_bump }} ;;
+            *)          npm version ${{ github.event.inputs.version_bump }} --no-git-tag-version ;;
+          esac
 
       - name: Get new version and previous tag
         id: version
@@ -61,34 +67,9 @@ jobs:
         run: |
           sed -i 's/"version": ".*"/"version": "${{ steps.version.outputs.new_version }}"/' tools/installer/package.json
 
-      - name: Generate web bundles
-        run: npm run bundle
-
-      - name: Package bundles for release
-        run: |
-          mkdir -p dist/release-bundles
-
-          # Copy web bundles
-          cp -r web-bundles dist/release-bundles/bmad-bundles-v${{ steps.version.outputs.new_version }}
-
-          # Verify bundles exist
-          if [ ! "$(ls -A dist/release-bundles/bmad-bundles-v${{ steps.version.outputs.new_version }})" ]; then
-            echo "❌ ERROR: No bundles found"
-            echo "This likely means 'npm run bundle' failed"
-            exit 1
-          fi
-
-          # Count and display bundles per module
-          for module in bmm bmb cis bmgd; do
-            if [ -d "dist/release-bundles/bmad-bundles-v${{ steps.version.outputs.new_version }}/$module/agents" ]; then
-              COUNT=$(find dist/release-bundles/bmad-bundles-v${{ steps.version.outputs.new_version }}/$module/agents -name '*.xml' 2>/dev/null | wc -l)
-              echo "✅ $module: $COUNT agents"
-            fi
-          done
-
-          # Create archive
-          tar -czf dist/release-bundles/bmad-bundles-v${{ steps.version.outputs.new_version }}.tar.gz \
-            -C dist/release-bundles/bmad-bundles-v${{ steps.version.outputs.new_version }} .
+      # TODO: Re-enable web bundles once tools/cli/bundlers/ is restored
+      # - name: Generate web bundles
+      #   run: npm run bundle
 
       - name: Commit version bump
         run: |
@@ -185,25 +166,15 @@ jobs:
             npm publish --tag latest
           fi
 
-      - name: Create GitHub Release with Bundles
+      - name: Create GitHub Release
         uses: softprops/action-gh-release@v2
         with:
           tag_name: v${{ steps.version.outputs.new_version }}
           name: "BMad Method v${{ steps.version.outputs.new_version }}"
           body: |
             ${{ steps.release_notes.outputs.RELEASE_NOTES }}
-
-            ## 📦 Web Bundles
-
-            Download XML bundles for use in AI platforms (Claude Projects, ChatGPT, Gemini):
-
-            - `bmad-bundles-v${{ steps.version.outputs.new_version }}.tar.gz` - All modules (BMM, BMB, CIS, BMGD)
-
-            **Browse online** (bleeding edge): https://bmad-code-org.github.io/bmad-bundles/
           draft: false
           prerelease: ${{ contains(steps.version.outputs.new_version, 'alpha') || contains(steps.version.outputs.new_version, 'beta') }}
-          files: |
-            dist/release-bundles/*.tar.gz
 
       - name: Summary
         run: |
@@ -212,7 +183,6 @@ jobs:
           echo "### 📦 Distribution" >> $GITHUB_STEP_SUMMARY
           echo "- **NPM**: Published with @latest tag" >> $GITHUB_STEP_SUMMARY
           echo "- **GitHub Release**: https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v${{ steps.version.outputs.new_version }}" >> $GITHUB_STEP_SUMMARY
-          echo "- **Web Bundles**: Attached to GitHub Release (4 archives)" >> $GITHUB_STEP_SUMMARY
           echo "" >> $GITHUB_STEP_SUMMARY
           echo "### ✅ Installation" >> $GITHUB_STEP_SUMMARY
           echo "\`\`\`bash" >> $GITHUB_STEP_SUMMARY

.gitignore

@@ -31,7 +31,7 @@ Thumbs.db
 # IDE and editor configs
 .windsurf/
 .trae/
-.bmad*/.cursor/
+_bmad*/.cursor/
 
 # AI assistant files
 CLAUDE.md
@@ -44,8 +44,8 @@ CLAUDE.local.md
 .claude/settings.local.json
 
 # Project-specific
-.bmad-core
-.bmad-creator-tools
+_bmad-core
+_bmad-creator-tools
 test-project-install/*
 sample-project/*
 flattened-codebase.xml
@@ -65,7 +65,7 @@ src/modules/bmgd/sub-modules/
 shared-modules
 z*/
 
-.bmad
+_bmad
 .claude
 .codex
 .github/chatmodes

.markdownlint-cli2.yaml

@@ -5,8 +5,8 @@ ignores:
   - node_modules/**
   - test/fixtures/**
   - CODE_OF_CONDUCT.md
-  - .bmad/**
-  - .bmad*/**
+  - _bmad/**
+  - _bmad*/**
   - .agent/**
   - .claude/**
   - .roo/**

.prettierignore

@@ -5,5 +5,5 @@ test/fixtures/**
 CODE_OF_CONDUCT.md
 
 # BMAD runtime folders (user-specific, not in repo)
-.bmad/
-.bmad*/
+_bmad/
+_bmad*/

.vscode/settings.json

@@ -73,7 +73,7 @@
   "editor.formatOnSave": true,
   "editor.defaultFormatter": "esbenp.prettier-vscode",
   "[javascript]": {
-    "editor.defaultFormatter": "esbenp.prettier-vscode"
+    "editor.defaultFormatter": "vscode.typescript-language-features"
   },
   "[json]": {
     "editor.defaultFormatter": "vscode.json-language-features"

CHANGELOG.md

@@ -1,5 +1,318 @@
 # Changelog
 
+## [6.0.0-alpha.19]
+
+**Release: December 18, 2025**
+
+### 🐛 Bug Fixes
+
+**Installer Stability:**
+
+- **Fixed \_bmad Folder Stutter**: Resolved issue with duplicate \_bmad folder creation when applying agent custom files
+- **Cleaner Installation**: Removed unnecessary backup file that was causing bloat in the installer
+- **Streamlined Agent Customization**: Fixed path handling for agent custom files to prevent folder duplication
+
+### 📊 Statistics
+
+- **3 files changed** with critical fix
+- **3,688 lines removed** by eliminating backup files
+- **Improved installer performance** and stability
+
+---
+
+## [6.0.0-alpha.18]
+
+**Release: December 18, 2025**
+
+### 🎮 BMGD Module - Complete Game Development Module Updated
+
+**Massive BMGD Overhaul:**
+
+- **New Game QA Agent (GLaDOS)**: Elite Game QA Architect with test automation specialization
+  - Engine-specific expertise: Unity, Unreal, Godot testing frameworks
+  - Comprehensive knowledge base with 15+ testing topics
+  - Complete testing workflows: test-framework, test-design, automate, playtest-plan, performance-test, test-review
+
+- **New Game Solo Dev Agent (Indie)**: Rapid prototyping and iteration specialist
+  - Quick-flow workflows optimized for solo/small team development
+  - Streamlined development process for indie game creators
+
+- **Production Workflow Alignment**: BMGD 4-production now fully aligned with BMM 4-implementation
+  - Removed obsolete workflows: story-done, story-ready, story-context, epic-tech-context
+  - Added sprint-status workflow for project tracking
+  - All workflows updated as standalone with proper XML instructions
+
+**Game Testing Architecture:**
+
+- **Complete Testing Knowledge Base**: 15 comprehensive testing guides covering:
+  - Engine-specific: Unity (TF 1.6.0), Unreal, Godot testing
+  - Game-specific: Playtesting, balance, save systems, multiplayer
+  - Platform: Certification (TRC/XR), localization, input systems
+  - QA Fundamentals: Automation, performance, regression, smoke testing
+
+**New Workflows & Features:**
+
+- **workflow-status**: Multi-mode status checker for game projects
+  - Game-specific project levels (Game Jam → AAA)
+  - Support for gamedev and quickflow paths
+  - Project initialization workflow
+
+- **create-tech-spec**: Game-focused technical specification workflow
+  - Engine-aware (Unity/Unreal/Godot) specifications
+  - Performance and gameplay feel considerations
+
+- **Enhanced Documentation**: Complete documentation suite with 9 guides
+  - agents-guide.md: Reference for all 6 agents
+  - workflows-guide.md: Complete workflow documentation
+  - game-types-guide.md: 24 game type templates
+  - quick-flow-guide.md: Rapid development guide
+  - Comprehensive troubleshooting and glossary
+
+### 🤖 Agent Management Improved
+
+**Agent Recompile Feature:**
+
+- **New Menu Item**: Added "Recompile Agents" option to the installer menu
+- **Selective Compilation**: Recompile only agents without full module upgrade
+- **Faster Updates**: Quick agent updates without complete reinstallation
+- **Customization Integration**: Automatically applies customizations during recompile
+
+**Agent Customization Enhancement:**
+
+- **Complete Field Support**: ALL fields from agent customization YAML are now properly injected
+- **Deep Merge Implementation**: Customizations now properly override all agent properties
+- **Persistent Customizations**: Custom settings survive updates and recompiles
+- **Enhanced Flexibility**: Support for customizing metadata, persona, menu items, and workflows
+
+### 🔧 Installation & Module Management
+
+**Custom Module Installation:**
+
+- **Enhanced Module Addition**: Modify install now supports adding custom modules even if none were originally installed
+- **Flexible Module Management**: Easy addition and removal of custom modules post-installation
+- **Improved Manifest Tracking**: Better tracking of custom vs core modules
+
+**Quality Improvements:**
+
+- **Comprehensive Code Review**: Fixed 20+ issues identified in PR review
+- **Type Validation**: Added proper type checking for configuration values
+- **Path Security**: Enhanced path traversal validation for better security
+- **Documentation Updates**: All documentation updated to reflect new features
+
+### 📊 Statistics
+
+- **178 files changed** with massive BMGD expansion
+- **28,350+ lines added** across testing documentation and workflows
+- **2 new agents** added to BMGD module
+- **15 comprehensive testing guides** created
+- **Complete alignment** between BMGD and BMM production workflows
+
+### 🌟 Key Highlights
+
+1. **BMGD Module Revolution**: Complete overhaul with professional game development workflows
+2. **Game Testing Excellence**: Comprehensive testing architecture for all major game engines
+3. **Agent Management**: New recompile feature allows quick agent updates without full reinstall
+4. **Full Customization Support**: All agent fields now customizable via YAML
+5. **Industry-Ready Documentation**: Professional-grade guides for game development teams
+
+---
+
+## [6.0.0-alpha.17]
+
+**Release: December 16, 2025**
+
+### 🚀 Revolutionary Installer Overhaul
+
+**Unified Installation Experience:**
+
+- **Streamlined Module Installation**: Completely redesigned installer with unified flow for both core and custom content
+- **Single Install Panel**: Eliminated disjointed clearing between modules for smoother, more intuitive installation
+- **Quick Default Selection**: New quick install feature with default selections for faster setup of selected modules
+- **Enhanced UI/UX**: Improved question order, reduced verbose output, and cleaner installation interface
+- **Logical Question Flow**: Reorganized installer questions to follow natural progression and user expectations
+
+**Custom Content Installation Revolution:**
+
+- **Full Custom Content Support**: Re-enabled complete custom content generation and sharing through the installer
+- **Custom Module Tracking**: Manifest now tracks custom modules separately to ensure they're always installed from the custom cache
+- **Custom Installation Order**: Custom modules now install after core modules for better dependency management
+- **Quick Update with Custom Content**: Quick update now properly retains and updates custom content
+- **Agent Customization Integration**: Customizations are now applied during quick updates and agent compilation
+
+### 🧠 Revolutionary Agent Memory & Visibility System
+
+**Breaking Through Dot-Folder Limitations:**
+
+- **Dot-Folder to Underscore Migration**: Critical change from `.bmad` to `_bmad` ensures LLMs (Codex, Claude, and others) can no longer ignore or skip BMAD content - dot folders are commonly filtered out by AI systems
+- **Universal Content Visibility**: Underscore folders are treated as regular content, ensuring full AI agent access to all BMAD resources and configurations
+- **Agent Memory Architecture**: Rolled out comprehensive agent memory support for installed agents with `-sidecar` folders
+- **Persistent Agent Learning**: Sidecar content installs to `_bmad/_memory`, giving each agent the ability to learn and remember important information specific to its role
+
+**Content Location Strategy:**
+
+- **Standardized Memory Location**: All sidecar content now uses `_bmad/_memory` as the unified location for agent memories
+- **Segregated Output System**: New architecture supports differentiating between ephemeral Phase 4 artifacts and long-term documentation
+- **Forward Compatibility**: Existing installations continue working with content in docs folder, with optimization coming in next release
+- **Configuration Cleanup**: Renamed `_cfg` to `_config` for clearer naming conventions
+- **YAML Library Consolidation**: Reduced dependency to use only one YAML library for better stability
+
+### 🎯 Future-Ready Architecture
+
+**Content Organization Preview:**
+
+- **Phase 4 Artifact Segregation**: Infrastructure ready for separating ephemeral workflow artifacts from permanent documentation
+- **Planning vs Implementation Docs**: New system will differentiate between planning artifacts and long-term project documentation
+- **Backward Compatibility**: Current installs maintain full functionality while preparing for optimized content organization
+- **Quick Update Path**: Tomorrow's quick update will fully optimize all BMM workflows to use new segregated output locations
+
+### 🎯 Sample Modules & Documentation
+
+**Comprehensive Examples:**
+
+- **Sample Unitary Module**: Complete example with commit-poet agent and quiz-master workflow
+- **Sample Wellness Module**: Meditation guide and wellness companion agents demonstrating advanced patterns
+- **Enhanced Documentation**: Updated README files and comprehensive installation guides
+- **Custom Content Creation Guides**: Step-by-step documentation for creating and sharing custom modules
+
+### 🔧 Bug Fixes & Optimizations
+
+**Installer Improvements:**
+
+- **Fixed Duplicate Entry Issue**: Resolved duplicate entries in files manifest
+- **Reduced Log Noise**: Less verbose logging during installation for cleaner user experience
+- **Menu Wording Updates**: Improved menu text for better clarity and understanding
+- **Fixed Quick Install**: Resolved issues with quick installation functionality
+
+**Code Quality:**
+
+- **Minor Code Cleanup**: General cleanup and refactoring throughout the codebase
+- **Removed Unused Code**: Cleaned up deprecated and unused functionality
+- **Release Workflow Restoration**: Fixed automated release workflow for v6
+
+**BMM Phase 4 Workflow Improvements:**
+
+- **Sprint Status Enhancement**: Improved sprint-status validation with interactive correction for unknown values and better epic status handling
+- **Story Status Standardization**: Normalized all story status references to lowercase kebab-case (ready-for-dev, in-progress, review, done)
+- **Removed Stale Story State**: Eliminated deprecated 'drafted' story state - stories now go directly from creation to ready-for-dev
+- **Code Review Clarity**: Improved code review completion message from "Story is ready for next work!" to "Code review complete!" for better clarity
+- **Risk Detection Rules**: Rewrote risk detection rules for better LLM clarity and fixed warnings vs risks naming inconsistency
+
+### 📊 Statistics
+
+- **40+ commits** since alpha.16
+- **Major installer refactoring** with complete UX overhaul
+- **2 new sample modules** with comprehensive examples
+- **Full custom content support** re-enabled and improved
+
+### 🌟 Key Highlights
+
+1. **Installer Revolution**: The installation system has been completely overhauled for better user experience, reliability, and speed
+2. **Custom Content Freedom**: Users can now easily create, share, and install custom content through the streamlined installer
+3. **AI Visibility Breakthrough**: Migration from `.bmad` to `_bmad` ensures LLMs can access all BMAD content (dot folders are commonly ignored by AI systems)
+4. **Agent Memory System**: Rolled out persistent agent memory support - agents with `-sidecar` folders can now learn and remember important information in `_bmad/_memory`
+5. **Quick Default Selection**: Installation is now faster with smart default selections for popular configurations
+6. **Future-Ready Architecture**: Infrastructure in place for segregating ephemeral artifacts from permanent documentation (full optimization coming in next release)
+
+## [6.0.0-alpha.16]
+
+**Release: December 10, 2025**
+
+### 🔧 Temporary Changes & Fixes
+
+**Installation Improvements:**
+
+- **Temporary Custom Content Installation Disable**: Custom content installation temporarily disabled to improve stability
+- **BMB Workflow Path Fixes**: Fixed numerous path references in BMB workflows to ensure proper step file resolution
+- **Package Updates**: Updated dependencies for improved security and performance
+
+**Path Resolution Improvements:**
+
+- **BMB Agent Builder Fixes**: Corrected path references in step files and documentation
+- **Workflow Path Standardization**: Ensured consistent path handling across all BMB workflows
+- **Documentation References**: Updated internal documentation links and references
+
+**Cleanup Changes:**
+
+- **Example Modules Removal**: Temporarily removed example modules to prevent accidental installation
+- **Memory Management**: Improved sidecar file handling for custom modules
+
+### 📊 Statistics
+
+- **336 files changed** with path fixes and improvements
+- **4 commits** since alpha.15
+
+---
+
+## [6.0.0-alpha.15]
+
+**Release: December 7, 2025**
+
+### 🔧 Module Installation Standardization
+
+**Unified Module Configuration:**
+
+- **module.yaml Standard**: All modules now use `module.yaml` instead of `_module-installer/install-config.yaml` for consistent configuration (BREAKING CHANGE)
+- **Universal Installer**: Both core and custom modules now use the same installer with consistent behavior
+- **Streamlined Module Creation**: Module builder templates updated to use new module.yaml standard
+- **Enhanced Module Discovery**: Improved module caching and discovery mechanisms
+
+**Custom Content Installation Revolution:**
+
+- **Interactive Custom Content Search**: Installer now proactively asks if you have custom content to install
+- **Flexible Location Specification**: Users can indicate custom content location during installation
+- **Improved Custom Module Handler**: Enhanced error handling and debug output for custom installations
+- **Comprehensive Documentation**: New custom-content-installation.md guide (245 lines) replacing custom-agent-installation.md
+
+### 🤖 Code Review Integration Expansion
+
+**AI Review Tools:**
+
+- **CodeRabbit AI Integration**: Added .coderabbit.yaml configuration for automated code review
+- **Raven's Verdict PR Review Tool**: New PR review automation tool (297 lines of documentation)
+- **Review Path Configuration**: Proper exclusion patterns for node_modules and generated files
+- **Review Documentation**: Comprehensive usage guidance and skip conditions for PRs
+
+### 📚 Documentation Improvements
+
+**Documentation Restructuring:**
+
+- **Code of Conduct**: Moved to .github/ folder following GitHub standards
+- **Gem Creation Link**: Updated to point to Gemini Gem manager instead of deprecated interface
+- **Example Custom Content**: Improved README files and disabled example modules to prevent accidental installation
+- **Custom Module Documentation**: Enhanced module installation guides with new YAML structure
+
+### 🧹 Cleanup & Optimization
+
+**Memory Management:**
+
+- **Removed Hardcoded .bmad Folders**: Cleaned up demo content to use configurable paths
+- **Sidecar File Cleanup**: Removed old .bmad-user-memory folders from wellness modules
+- **Example Content Organization**: Better organization of example-custom-content directory
+
+**Installer Improvements:**
+
+- **Debug Output Enhancement**: Added informative debug output when installer encounters errors
+- **Custom Module Caching**: Improved caching mechanism for custom module installations
+- **Consistent Behavior**: All modules now behave consistently regardless of custom or core status
+
+### 📊 Statistics
+
+- **77 files changed** with 2,852 additions and 607 deletions
+- **15 commits** since alpha.14
+
+### ⚠️ Breaking Changes
+
+1. **module.yaml Configuration**: All modules must now use `module.yaml` instead of `_module-installer/install-config.yaml`
+   - Core modules updated automatically
+   - Custom modules will need to rename their configuration file
+   - Module builder templates generate new format
+
+### 📦 New Dependencies
+
+- No new dependencies added in this release
+
+---
+
 ## [6.0.0-alpha.14]
 
 **Release: December 7, 2025**
@@ -75,7 +388,6 @@
 - Fixed version reading from package.json instead of hardcoded fallback
 - Removed hardcoded years from WebSearch queries
 - Removed broken build caching mechanism
-- Fixed hardcoded 'bmad' prefix from files-manifest.csv paths
 - Enhanced TTS injection summary with tracking and documentation
 - Fixed CI nvmrc configuration issues
 
@@ -101,159 +413,29 @@
 
 ### 🏗️ Revolutionary Workflow Architecture
 
-**Granular Step-File Workflow System (NEW in alpha.13):**
-
-- **Multi-Menu Support**: Workflows now support granular step-file architecture with dynamic menu generation
-- **Sharded Workflows**: Complete conversion of Phase 1 and 2 workflows to stepwise sharded architecture
-- **Improved Performance**: Reduced file loading times and eliminated time-based estimates throughout
-- **Workflow Builder**: New dedicated workflow builder for creating stepwise workflows
-- **PRD Workflow**: First completely reworked sharded workflow resolving Sonnet compatibility issues
-
-**Core Workflow Transformations:**
-
-- Phase 1 and 2 workflows completely converted to sharded step-flow architecture
-- UX Design workflow converted to sharded step workflow
-- Brainstorming, Research, and Party Mode updated to use sharded step-flow workflows
-- Architecture workflows enhanced with step sharding and performance improvements
-
-### 🎯 Code Review & Development Enhancement
-
-**Advanced Code Review System:**
-
-- **Adversarial Code Review**: Quick-dev workflow now recommends adversarial review approach for higher quality
-- **Multi-LLM Strategy**: Dev-story workflow recommends different LLM models for code review tasks
-- **Agent Compiler Optimization**: Complete handler cleanup and performance improvements
+- **Step-File System**: Complete conversion to granular step-file architecture with dynamic menu generation
+- **Phase 4 Transformation**: Simplified architecture with sprint planning integration (Jira, Linear, Trello)
+- **Performance Improvements**: Eliminated time-based estimates, reduced file loading times
+- **Legacy Cleanup**: Removed all deprecated workflows for cleaner system
 
 ### 🤖 Agent System Revolution
 
-**Universal Custom Agent Support:**
+- **Universal Custom Agent Support**: Extended to ALL IDEs including Antigravity and Rovo Dev
+- **Agent Creation Workflow**: Enhanced with better documentation and parameter clarity
+- **Multi-Source Discovery**: Agents now check multiple source locations for better discovery
+- **GitHub Migration**: Integration moved from chatmodes to agents folder
 
-- **Complete IDE Coverage**: Custom agent support extended to ALL remaining IDEs
-- **Antigravity IDE Integration**: Added custom agent support with proper gitignore configuration
-- **Multiple Source Locations**: Compile agents now checks multiple source locations for better discovery
-- **Persona Name Display**: Fixed proper persona names display in custom agent manifests
-- **New IDE Support**: Added support for Rovo Dev IDE
+### 🧪 Testing Infrastructure
 
-**Agent Creation & Management:**
-
-- **Improved Creation Workflow**: Enhanced agent creation workflow with better documentation
-- **Parameter Clarity**: Renamed agent-install parameters for better understanding
-- **Menu Organization**: BMad Agents menu items logically ordered with optional/recommended/required tags
-- **GitHub Migration**: GitHub integration now uses agents folder instead of chatmodes
-
-### 🔧 Phase 4 & Sprint Evolution
-
-**Complete Phase 4 Transformation:**
-
-- **Simplified Architecture**: Phase 4 workflows completely transformed - simpler, faster, better results
-- **Sprint Planning Integration**: Unified sprint planning with placeholders for Jira, Linear, and Trello integration
-- **Status Management**: Better status loading and updating for Phase 4 artifacts
-- **Workflow Reduction**: Phase 4 streamlined to single sprint planning item with clear validation
-- **Dynamic Workflows**: All Level 1-3 workflows now dynamically suggest next steps based on context
-
-### 🧪 Testing Infrastructure Expansion
-
-**Playwright Utils Integration:**
-
-- Test Architect now supports `@seontechnologies/playwright-utils` integration
-- Installation prompt with `use_playwright_utils` configuration flag
-- 11 comprehensive knowledge fragments covering ALL utilities
-- Adaptive workflow recommendations across 6 testing workflows
-- Production-ready utilities from SEON Technologies integrated with TEA patterns
-
-**Testing Environment:**
-
-- **Web Bundle Support**: Enabled web bundles for test and development environments
-- **Test Architecture**: Enhanced test design for architecture level (Phase 3) testing
-
-### 📦 Installation & Configuration
-
-**Installer Improvements:**
-
-- **Cleanup Options**: Installer now allows cleanup of unneeded files during upgrades
-- **Username Default**: Installer now defaults to system username for better UX
-- **IDE Selection**: Added empty IDE selection warning and promoted Antigravity to recommended
-- **NPM Vulnerabilities**: Resolved all npm vulnerabilities for enhanced security
-- **Documentation Installation**: Made documentation installation optional to reduce footprint
-
-**Text-to-Speech from AgentVibes optional Integration:**
-
-- **TTS_INJECTION System**: Complete text-to-speech integration via injection system
-- **Agent Vibes**: Enhanced with TTS capabilities for voice feedback
-
-### 🛠️ Tool & IDE Updates
-
-**IDE Tool Enhancements:**
-
-- **GitHub Copilot**: Fixed tool names consistency across workflows
-- **KiloCode Integration**: Gave kilocode tool proper access to bmad modes
-- **Code Quality**: Added radix parameter to parseInt() calls for better reliability
-- **Agent Menu Optimization**: Improved agent performance in Claude Code slash commands
-
-### 📚 Documentation & Standards
-
-**Documentation Cleanup:**
-
-- **Installation Guide**: Removed fluff and updated with npx support
-- **Workflow Documentation**: Fixed documentation by removing non-existent workflows and Mermaid diagrams
-- **Phase Numbering**: Fixed phase numbering consistency throughout documentation
-- **Package References**: Corrected incorrect npm package references
-
-**Workflow Compliance:**
-
-- **Validation Checks**: Enhanced workflow validation checks for compliance
-- **Product Brief**: Updated to comply with documented workflow standards
-- **Status Integration**: Workflow-status can now call workflow-init for better integration
-
-### 🔍 Legacy Workflow Cleanup
-
-**Deprecated Workflows Removed:**
-
-- **Audit Workflow**: Completely removed audit workflow and all associated files
-- **Convert Legacy**: Removed legacy conversion utilities
-- **Create/Edit Workflows**: Removed old workflow creation and editing workflows
-- **Clean Architecture**: Simplified workflow structure by removing deprecated legacy workflows
-
-### 🐛 Technical Fixes
-
-**System Improvements:**
-
-- **File Path Handling**: Fixed various file path issues across workflows
-- **Manifest Updates**: Updated manifest to use agents folder structure
-- **Web Bundle Configuration**: Fixed web bundle configurations for better compatibility
-- **CSV Column Mismatch**: Fixed manifest schema upgrade issues
+- **Playwright Utils Integration**: @seontechnologies/playwright-utils across all testing workflows
+- **TTS Injection System**: Complete text-to-speech integration for voice feedback
+- **Web Bundle Test Support**: Enabled web bundles for test environments
 
 ### ⚠️ Breaking Changes
 
-**Workflow Architecture:**
-
-- All legacy workflows have been removed - ensure you're using the new stepwise sharded workflows
-- Phase 4 completely restructured - update any automation expecting old Phase 4 structure
-- Epic creation now requires architectural context (moved to Phase 3 in previous release)
-
-**Agent System:**
-
-- Custom agents now require proper compilation - use the new agent creation workflow
-- GitHub integration moved from chatmodes to agents folder - update any references
-
-### 📊 Impact Summary
-
-**New in alpha.13:**
-
-- **Stepwise Workflow Architecture**: Complete transformation of all workflows to granular step-file system
-- **Universal Custom Agent Support**: Extended to ALL IDEs with improved creation workflow
-- **Phase 4 Revolution**: Completely restructured with sprint planning integration
-- **Legacy Cleanup**: Removed all deprecated workflows for cleaner system
-- **Advanced Code Review**: New adversarial review approach with multi-LLM strategy
-- **Text-to-Speech**: Full TTS integration for voice feedback
-- **Testing Expansion**: Playwright utils integration across all testing workflows
-
-**Enhanced from alpha.12:**
-
-- **Performance**: Improved file loading and removed time-based estimates
-- **Documentation**: Complete cleanup with accurate references
-- **Installer**: Better UX with cleanup options and improved defaults
-- **Agent System**: More reliable compilation and better persona handling
+1. **Legacy Workflows Removed**: Migrate to new stepwise sharded workflows
+2. **Phase 4 Restructured**: Update automation expecting old Phase 4 structure
+3. **Agent Compilation Required**: Custom agents must use new creation workflow
 
 ## [6.0.0-alpha.12]
 
@@ -267,313 +449,101 @@
 
 **Release: November 18, 2025**
 
-This alpha release introduces a complete agent installation system with the new `bmad agent-install` command, vastly improves the BMB agent builder capabilities with comprehensive documentation and reference agents, and refines diagram distribution to better align with BMad Method's core principle: **BMad agents mirror real agile teams**.
+### 🚀 Agent Installation Revolution
 
-### 🎨 Diagram Capabilities Refined and Distributed
-
-**Excalidraw Integration Evolution:**
-
-Building on the excellent Excalidraw integration introduced with the Frame Expert agent, we've refined how diagram capabilities are distributed across the BMad Method ecosystem to better reflect real agile team dynamics.
-
-**The Refinement:**
-
-- The valuable Excalidraw diagramming capabilities have been distributed to the agents who naturally create these artifacts in real teams
-- **Architect**: System architecture diagrams, data flow visualizations
-- **Product Manager**: Process flowcharts and workflow diagrams
-- **UX Designer**: Wireframe creation capabilities
-- **Tech Writer**: All diagram types for documentation needs
-- **New CIS Agent**: presentation-master for specialized visual communication
-
-**Shared Infrastructure Enhancement:**
-
-- Excalidraw templates, component libraries, and validation patterns elevated to core resources
-- Available to both BMM agents AND CIS presentation specialists
-- Preserves all the excellent Excalidraw functionality while aligning with natural team roles
-
-### 🚀 New Agent Installation System
-
-**Agent Installation Infrastructure (NEW in alpha.11):**
-
-- `bmad agent-install` CLI command with interactive persona customization
-- **YAML → XML compilation engine** with smart handler injection
-- Supports Simple (single file), Expert (with sidecars), and Module agents
-- Handlebars-style template variable processing
-- Automatic manifest tracking and IDE integration
-- Source preservation in `_cfg/custom/agents/` for reinstallation
-
-**New Reference Agents Added:**
-
-- **commit-poet**: Poetic git commit message generator (Simple agent example)
-- **journal-keeper**: Daily journaling agent with templates (Expert agent example)
-- **security-engineer & trend-analyst**: Module agent examples with ecosystem integration
-
-**Critical Persona Field Guidance Added:**
-
-New documentation explaining how LLMs interpret persona fields for better agent quality:
-
-- **role** → "What knowledge, skills, and capabilities do I possess?"
-- **identity** → "What background, experience, and context shape my responses?"
-- **communication_style** → "What verbal patterns, word choice, and phrasing do I use?"
-- **principles** → "What beliefs and operating philosophy drive my choices?"
-
-Key insight: `communication_style` should ONLY describe HOW the agent talks, not WHAT they do
-
-**BMM Agent Voice Enhancement:**
-
-All 9 existing BMM agents enhanced with distinct, memorable communication voices:
-
-- **Mary (analyst)**: "Treats analysis like a treasure hunt - excited by every clue"
-- **John (PM)**: "Asks 'WHY?' relentlessly like a detective on a case"
-- **Winston (architect)**: "Champions boring technology that actually works"
-- **Amelia (dev)**: "Ultra-succinct. Speaks in file paths and AC IDs"
-- **Sally (UX)**: "Paints pictures with words, telling user stories that make you FEEL"
-
-### 🔧 Edit-Agent Workflow Comprehensive Enhancement
-
-**Expert Agent Sidecar Support (NEW):**
-
-- Automatically detects and handles Expert agents with multiple files
-- Loads and manages templates, data files, knowledge bases
-- Smart sidecar analysis: maps references, finds orphans, validates paths
-- 5 complete sidecar editing patterns with warm, educational feedback
-
-**7-Step Communication Style Refinement Pattern:**
-
-1. Diagnose current style with red flag word detection
-2. Extract non-style content to working copy
-3. Discover TRUE communication style through interview questions
-4. Craft pure style using presets and reference agents
-5. Show before/after transformation with full context
-6. Validate against standards (zero red flags)
-7. Confirm with user through dramatic reading
-
-**Unified Validation Checklist:**
-
-- Single source of truth: `agent-validation-checklist.md` (160 lines)
-- Shared between create-agent and edit-agent workflows
-- Comprehensive persona field separation validation
-- Expert agent sidecar validation (9 specific checks)
-- Common issues and fixes with real examples
+- **bmad agent-install CLI**: Interactive agent installation with persona customization
+- **4 Reference Agents**: commit-poet, journal-keeper, security-engineer, trend-analyst
+- **Agent Compilation Engine**: YAML → XML with smart handler injection
+- **60 Communication Presets**: Pure communication styles for agent personas
 
 ### 📚 BMB Agent Builder Enhancement
 
-**Vastly Improved Agent Creation & Editing Capabilities:**
+- **Complete Documentation Suite**: 7 new guides for agent architecture and creation
+- **Expert Agent Sidecar Support**: Multi-file agents with templates and knowledge bases
+- **Unified Validation**: 160-line checklist shared across workflows
+- **BMM Agent Voices**: All 9 agents enhanced with distinct communication styles
 
-- Create-agent and edit-agent workflows now have accurate, comprehensive documentation
-- All context references updated and validated for consistency
-- Workflows can now properly guide users through complex agent design decisions
+### 🎯 Workflow Architecture Change
 
-**New Agent Documentation Suite:**
-
-- `understanding-agent-types.md` - Architecture vs capability distinction
-- `simple-agent-architecture.md` - Self-contained agents guide
-- `expert-agent-architecture.md` - Agents with sidecar files
-- `module-agent-architecture.md` - Workflow-integrated agents
-- `agent-compilation.md` - YAML → XML transformation process
-- `agent-menu-patterns.md` - Menu design patterns
-- `communication-presets.csv` - 60 pure communication styles for reference
-
-**New Reference Agents for Learning:**
-
-- Complete working examples of Simple, Expert, and Module agents
-- Can be installed directly via the new `bmad agent-install` command
-- Serve as both learning resources and ready-to-use agents
-
-### 🎯 Epic Creation Moved to Phase 3 (After Architecture)
-
-**Workflow Sequence Corrected:**
-
-```
-Phase 2: PRD → UX Design
-Phase 3: Architecture → Epics & Stories ← NOW HERE (technically informed)
-```
-
-**Why This Fundamental Change:**
-
-- Epics need architectural context: API contracts, data models, technical decisions
-- Stories can reference actual architectural patterns and constraints
-- Reduces rewrites when architecture reveals complexity
-- Better complexity-based estimation (not time-based)
-
-### 🖥️ New IDE Support
-
-**Google Antigravity IDE Installer:**
-
-- Flattened file naming for proper slash commands (bmad-module-agents-name.md)
-- Namespace isolation prevents module conflicts
-- Subagent installation support (project or user level)
-- Module-specific injection configuration
-
-**Codex CLI Enhancement:**
-
-- Now supports both global and project-specific installation
-- CODEX_HOME configuration for multi-project workflows
-- OS-specific setup instructions (Unix/Mac/Windows)
-
-### 🏗️ Reference Agents & Standards
-
-**New Reference Agents Provide Clear Examples:**
-
-- **commit-poet.agent.yaml**: Simple agent with pure communication style
-- **journal-keeper.agent.yaml**: Expert agent with sidecar file structure
-- **security-engineer.agent.yaml**: Module agent for ecosystem integration
-- **trend-analyst.agent.yaml**: Module agent with cross-workflow capabilities
-
-**Agent Type Clarification:**
-
-- Clear documentation that agent types (Simple/Expert/Module) describe architecture, not capability
-- Module = designed for ecosystem integration, not limited in function
-
-### 🐛 Technical Improvements
-
-**Linting Compliance:**
-
-- Fixed all ESLint warnings across agent tooling
-- `'utf-8'` → `'utf8'` (unicorn/text-encoding-identifier-case)
-- `hasOwnProperty` → `Object.hasOwn` (unicorn/prefer-object-has-own)
-- `JSON.parse(JSON.stringify(...))` → `structuredClone(...)`
-
-**Agent Compilation Engine:**
-
-- Auto-injects frontmatter, activation, handlers, help/exit menu items
-- Smart handler inclusion (only includes handlers actually used)
-- Proper XML escaping and formatting
-- Persona name customization support
-
-### 📊 Impact Summary
-
-**New in alpha.11:**
-
-- **Agent installation system** with `bmad agent-install` CLI command
-- **4 new reference agents** (commit-poet, journal-keeper, security-engineer, trend-analyst)
-- **Complete agent documentation suite** with 7 new focused guides
-- **Expert agent sidecar support** in edit-agent workflow
-- **2 new IDE installers** (Google Antigravity, enhanced Codex)
-- **Unified validation checklist** (160 lines) for consistent quality standards
-- **60 pure communication style presets** for agent persona design
-
-**Enhanced from alpha.10:**
-
-- **BMB agent builder workflows** with accurate context and comprehensive guidance
-- **All 9 BMM agents** enhanced with distinct, memorable communication voices
-- **Excalidraw capabilities** refined and distributed to role-appropriate agents
-- **Epic creation** moved to Phase 3 (after Architecture) for technical context
+- **Epic Creation Moved**: Now in Phase 3 after Architecture for technical context
+- **Excalidraw Distribution**: Diagram capabilities moved to role-appropriate agents
+- **Google Antigravity IDE**: New installer with flattened file naming
 
 ### ⚠️ Breaking Changes
 
-**Agent Changes:**
-
-- Frame Expert agent retired - diagram capabilities now available through role-appropriate agents:
-  - Architecture diagrams → `/architect`
-  - Process flows → `/pm`
-  - Wireframes → `/ux-designer`
-  - Documentation visuals → `/tech-writer`
-
-**Workflow Changes:**
-
-- Epic creation moved from Phase 2 to Phase 3 (after Architecture)
-- Excalidraw workflows redistributed to appropriate agents
-
-**Installation Changes:**
-
-- New `bmad agent-install` command replaces manual agent installation
-- Agent YAML files must be compiled to XML for use
-
-### 🔄 Migration Notes
-
-**For Existing Projects:**
-
-1. **Frame Expert Users:**
-   - Transition to role-appropriate agents for diagrams
-   - All Excalidraw functionality preserved and enhanced
-   - Shared templates now in core resources for wider access
-
-2. **Agent Installation:**
-   - Use `bmad agent-install` for all agent installations
-   - Existing manual installations still work but won't have customization
-
-3. **Epic Creation Timing:**
-   - Epics now created in Phase 3 after Architecture
-   - Update any automation expecting epics in Phase 2
-
-4. **Communication Styles:**
-   - Review agent communication_style fields
-   - Remove any role/identity/principle content
-   - Use communication-presets.csv for pure styles
-
-5. **Expert Agents:**
-   - Edit-agent workflow now fully supports sidecar files
-   - Organize templates and data files in agent folder
+1. **Frame Expert Retired**: Use role-appropriate agents for diagrams
+2. **Agent Installation**: New bmad agent-install command replaces manual installation
+3. **Epic Creation Phase**: Moved from Phase 2 to Phase 3
 
 ## [6.0.0-alpha.10]
 
 **Release: November 16, 2025**
 
-- **🎯 Epics Generated AFTER Architecture**: Major milestone - epics/stories now created after architecture for technically-informed user stories with better acceptance criteria
-- **🎨 Frame Expert Agent**: New Excalidraw specialist with 4 diagram workflows (flowchart, diagram, dataflow, wireframe) for visual documentation
-- **⏰ Time Estimate Prohibition**: Critical warnings added across 33 workflows - acknowledges AI has fundamentally changed development speed
-- **🎯 Platform-Specific Commands**: New `ide-only`/`web-only` fields filter menu items based on environment (IDE vs web bundle)
-- **🔧 Agent Customization**: Enhanced memory/prompts merging via `*.customize.yaml` files for persistent agent personalization
+- **Epics After Architecture**: Major milestone - technically-informed user stories created post-architecture
+- **Frame Expert Agent**: New Excalidraw specialist with 4 diagram workflows
+- **Time Estimate Prohibition**: Warnings across 33 workflows acknowledging AI's impact on development speed
+- **Platform-Specific Commands**: ide-only/web-only fields filter menu items by environment
+- **Agent Customization**: Enhanced memory/prompts merging via \*.customize.yaml files
 
 ## [6.0.0-alpha.9]
 
 **Release: November 12, 2025**
 
-- **🚀 Intelligent File Discovery Protocol**: New `discover_inputs` with FULL_LOAD, SELECTIVE_LOAD, and INDEX_GUIDED strategies for automatic context loading
-- **📚 3-Track System**: Simplified from 5 levels to 3 intuitive tracks: quick-flow, bmad-method, and enterprise-bmad-method
-- **🌐 Web Bundles Guide**: Comprehensive documentation for Gemini Gems and Custom GPTs with 60-80% cost savings strategies
-- **🏗️ Unified Output Structure**: Eliminated `.ephemeral/` folders - all artifacts now in single configurable output folder
-- **🎮 BMGD Phase 4**: Added 10 game development workflows following BMM patterns with game-specific adaptations
+- **Intelligent File Discovery**: discover_inputs with FULL_LOAD, SELECTIVE_LOAD, INDEX_GUIDED strategies
+- **3-Track System**: Simplified from 5 levels to 3 intuitive tracks
+- **Web Bundles Guide**: Comprehensive documentation with 60-80% cost savings strategies
+- **Unified Output Structure**: Eliminated .ephemeral/ folders - single configurable output folder
+- **BMGD Phase 4**: Added 10 game development workflows with BMM patterns
 
 ## [6.0.0-alpha.8]
 
 **Release: November 9, 2025**
 
-- **🎯 Configurable Installation**: Custom directories with `.bmad` hidden folder default for cleaner project structure
-- **🚀 Optimized Agent Loading**: CLI loads from installed files eliminating duplication and maintenance burden
-- **🌐 Party Mode Everywhere**: All web bundles include multi-agent collaboration with customizable party configurations
-- **🔧 Phase 4 Artifact Separation**: Stories, code reviews, sprint plans now configurable outside docs folder
-- **📦 Expanded Web Bundles**: All BMM, BMGD, and CIS agents bundled with advanced elicitation integration
+- **Configurable Installation**: Custom directories with .bmad hidden folder default
+- **Optimized Agent Loading**: CLI loads from installed files, eliminating duplication
+- **Party Mode Everywhere**: All web bundles include multi-agent collaboration
+- **Phase 4 Artifact Separation**: Stories, code reviews, sprint plans configurable outside docs
+- **Expanded Web Bundles**: All BMM, BMGD, CIS agents bundled with elicitation integration
 
 ## [6.0.0-alpha.7]
 
 **Release: November 7, 2025**
 
-- **🌐 Workflow Vendoring**: Web bundler performs automatic workflow vendoring for cross-module dependencies
-- **🎮 BMGD Module Extraction**: Game development split into standalone module with 4-phase industry-standard structure
-- **🔧 Enhanced Dependency Resolution**: Better handling of `web_bundle: false` workflows with positive resolution messages
-- **📚 Advanced Elicitation Fix**: Added missing CSV files to workflow bundles fixing runtime failures
-- **🐛 Claude Code Fix**: Resolved README slash command installation regression
+- **Workflow Vendoring**: Web bundler performs automatic cross-module dependency vendoring
+- **BMGD Module Extraction**: Game development split into standalone 4-phase structure
+- **Enhanced Dependency Resolution**: Better handling of web_bundle: false workflows
+- **Advanced Elicitation Fix**: Added missing CSV files to workflow bundles
+- **Claude Code Fix**: Resolved README slash command installation regression
 
 ## [6.0.0-alpha.6]
 
 **Release: November 4, 2025**
 
-- **🐛 Critical Installer Fixes**: Fixed manifestPath error and option display issues blocking installation
-- **📖 Conditional Docs Installation**: Optional documentation installation to reduce footprint in production
-- **🎨 Improved Installer UX**: Better formatting with descriptive labels and clearer feedback
-- **🧹 Issue Tracker Cleanup**: Closed 54 legacy v4 issues for focused v6 development
-- **📝 Contributing Updates**: Removed references to non-existent branches in documentation
+- **Critical Installer Fixes**: Fixed manifestPath error and option display issues
+- **Conditional Docs Installation**: Optional documentation to reduce production footprint
+- **Improved Installer UX**: Better formatting with descriptive labels and clearer feedback
+- **Issue Tracker Cleanup**: Closed 54 legacy v4 issues for focused v6 development
+- **Contributing Updates**: Removed references to non-existent branches
 
 ## [6.0.0-alpha.5]
 
 **Release: November 4, 2025**
 
-- **🎯 3-Track Scale System**: Revolutionary simplification from 5 confusing levels to 3 intuitive preference-driven tracks
-- **✨ Elicitation Modernization**: Replaced legacy XML tags with explicit `invoke-task` pattern at strategic decision points
-- **📚 PM/UX Evolution Section**: Added November 2025 industry research on AI Agent PMs and Full-Stack Product Leads
-- **🏗️ Brownfield Reality Check**: Rewrote Phase 0 with 4 real-world scenarios for messy existing codebases
-- **📖 Documentation Accuracy**: All agent capabilities now match YAML source of truth with zero hallucination risk
+- **3-Track Scale System**: Simplified from 5 levels to 3 intuitive preference-driven tracks
+- **Elicitation Modernization**: Replaced legacy XML tags with explicit invoke-task pattern
+- **PM/UX Evolution**: Added November 2025 industry research on AI Agent PMs
+- **Brownfield Reality Check**: Rewrote Phase 0 with 4 real-world scenarios
+- **Documentation Accuracy**: All agent capabilities now match YAML source of truth
 
 ## [6.0.0-alpha.4]
 
 **Release: November 2, 2025**
 
-- **📚 Documentation Hub**: Created 18 comprehensive guides (7000+ lines) with professional technical writing standards
-- **🤖 Paige Agent**: New technical documentation specialist available across all BMM phases
-- **🚀 Quick Spec Flow**: Intelligent Level 0-1 planning with auto-stack detection and brownfield analysis
-- **📦 Universal Shard-Doc**: Split large markdown documents into organized sections with dual-strategy loading
-- **🔧 Intent-Driven Planning**: PRD and Product Brief transformed from template-filling to natural conversation
+- **Documentation Hub**: Created 18 comprehensive guides (7000+ lines) with professional standards
+- **Paige Agent**: New technical documentation specialist across all BMM phases
+- **Quick Spec Flow**: Intelligent Level 0-1 planning with auto-stack detection
+- **Universal Shard-Doc**: Split large markdown documents with dual-strategy loading
+- **Intent-Driven Planning**: PRD and Product Brief transformed from template-filling to conversation
 
 ## [6.0.0-alpha.3]
 

LICENSE

@@ -21,6 +21,6 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 
 TRADEMARK NOTICE:
-BMAD™, BMAD-CORE™ and BMAD-METHOD™ are trademarks of BMad Code, LLC. The use of these 
+BMad™ , BMAD-CORE™ 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

@@ -6,9 +6,38 @@
 [![Node.js Version](https://img.shields.io/badge/node-%3E%3D20.0.0-brightgreen)](https://nodejs.org)
 [![Discord](https://img.shields.io/badge/Discord-Join%20Community-7289da?logo=discord&logoColor=white)](https://discord.gg/gk8jAdXWmj)
 
+---
+
+<div align="center">
+
+## 🎉 NEW: BMAD V6 Installer - Create & Share Custom Content!
+
+The completely revamped **BMAD V6 installer** now includes built-in support for creating, installing, and sharing custom modules, agents, workflows, templates, and tools! Build your own AI solutions or share them with your team - and real soon, with the whole BMad Community througha verified community sharing portal!
+
+**✨ What's New:**
+
+- 📦 **Streamlined Custom Module Installation** - Package your custom content as installable modules
+- 🤖 **Agent & Workflow Sharing** - Distribute standalone agents and workflows
+- 🔄 **Unitary Module Support** - Install individual components without full modules
+- ⚙️ **Dependency Management** - Automatic handling of module dependencies
+- 🛡️ **Update-Safe Customization** - Your custom content persists through updates
+
+**📚 Learn More:**
+
+- [**Custom Content Overview**](./docs/custom-content.md) - Discover all supported content types
+- [**Installation Guide**](./docs/custom-content-installation.md) - Learn to create and install custom content
+- [**Detail Content Docs**](./src/modules/bmb/docs/README.md) - Reference details for agents, modules, workflows and the bmad builder
+- [**2 Very simple Custom Modules of questionable quality**](./docs/sample-custom-modules/README.md) - if you want to download and try to install a custom shared module, get an idea of how to bundle and share your own, or create your own personal agents, workflows and modules.
+
+</div>
+
+---
+
 ## AI-Driven Agile Development That Scales From Bug Fixes to Enterprise
 
-**Build More, Architect Dreams** (BMAD) with **19 specialized AI agents** and **50+ guided workflows** that adapt to your project's complexity—from quick bug fixes to enterprise platforms.
+**Build More, Architect Dreams** (BMAD) with **21 specialized AI agents** across 4 official modules, and **50+ guided workflows** that adapt to your project's complexity—from quick bug fixes to enterprise platforms, and new step file workflows that allow for incredibly long workflows to stay on the rails longer than ever before!
+
+Additionally - when we say 'Build More, Architect Dreams' - we mean it! The BMad Builder has landed, and now as of Alpha.15 is fully supported in the installation flow via NPX - custom stand along agents, workflows and the modules of your dreams! The community forge will soon open, endless possibility awaits!
 
 > **🚀 v6 is a MASSIVE upgrade from v4!** Complete architectural overhaul, scale-adaptive intelligence, visual workflows, and the powerful BMad Core framework. v4 users: this changes everything. [See what's new →](#whats-new-in-v6)
 
@@ -118,7 +147,7 @@ Each agent brings deep expertise and can be customized to match your team's styl
 - **BMad Builder (BMB)** - Create custom agents and workflows
   - Build anything from simple agents to complex modules
   - Create domain-specific solutions (legal, medical, finance, education)
-  - Share your creations in the upcoming community marketplace
+  - [→ Builder Guide](src/modules/bmb/docs/README.md) marketplace
   - [→ Builder Guide](./src/modules/bmb/README.md)
 
 - **Creative Intelligence Suite (CIS)** - Innovation & problem-solving
@@ -154,6 +183,7 @@ Each agent brings deep expertise and can be customized to match your team's styl
 - **[GitHub Issues](https://github.com/bmad-code-org/BMAD-METHOD/issues)** - Report bugs, request features
 - **[YouTube Channel](https://www.youtube.com/@BMadCode)** - Video tutorials and demos
 - **[Web Bundles](https://bmad-code-org.github.io/bmad-bundles/)** - Pre-built agent bundles
+- **[Code of Conduct](.github/CODE_OF_CONDUCT.md)** - Community guidelines
 
 ## 🛠️ Development
 
@@ -199,7 +229,9 @@ See [CONTRIBUTING.md](CONTRIBUTING.md) for full development guidelines.
 
 MIT License - See [LICENSE](LICENSE) for details.
 
-**Trademarks:** BMAD™ and BMAD-METHOD™ are trademarks of BMad Code, LLC.
+**Trademarks:** BMad™ and BMAD-METHOD™ are trademarks of BMad Code, LLC.
+
+Supported by:&nbsp;&nbsp;<a href="https://m.do.co/c/00f11bd932bb"><img src="https://opensource.nyc3.cdn.digitaloceanspaces.com/attribution/assets/SVG/DO_Logo_horizontal_blue.svg" height="24" alt="DigitalOcean" style="vertical-align: middle;"></a>
 
 ---
 

docs/agent-customization-guide.md

@@ -9,7 +9,7 @@ Customize BMad agents without modifying core files. All customizations persist t
 After installation, find agent customization files in:
 
 ```
-{bmad_folder}/_cfg/agents/
+_bmad/_config/agents/
 ├── core-bmad-master.customize.yaml
 ├── bmm-dev.customize.yaml
 ├── bmm-pm.customize.yaml
@@ -119,7 +119,7 @@ prompts:
 **Example 1: Customize Developer Agent for TDD**
 
 ```yaml
-# {bmad_folder}/_cfg/agents/bmm-dev.customize.yaml
+# _bmad/_config/agents/bmm-dev.customize.yaml
 agent:
   metadata:
     name: 'TDD Developer'
@@ -135,20 +135,20 @@ critical_actions:
 **Example 2: Add Custom Deployment Workflow**
 
 ```yaml
-# {bmad_folder}/_cfg/agents/bmm-dev.customize.yaml
+# _bmad/_config/agents/bmm-dev.customize.yaml
 menu:
   - trigger: deploy-staging
-    workflow: '{project-root}/{bmad_folder}/deploy-staging.yaml'
+    workflow: '{project-root}/_bmad/deploy-staging.yaml'
     description: Deploy to staging environment
   - trigger: deploy-prod
-    workflow: '{project-root}/{bmad_folder}/deploy-prod.yaml'
+    workflow: '{project-root}/_bmad/deploy-prod.yaml'
     description: Deploy to production (with approval)
 ```
 
 **Example 3: Multilingual Product Manager**
 
 ```yaml
-# {bmad_folder}/_cfg/agents/bmm-pm.customize.yaml
+# _bmad/_config/agents/bmm-pm.customize.yaml
 persona:
   role: 'Bilingual Product Manager'
   identity: 'Expert in US and LATAM markets'
@@ -166,15 +166,15 @@ memories:
 
 - **Start Small:** Customize one section at a time and rebuild to test
 - **Backup:** Copy customization files before major changes
-- **Update-Safe:** Your customizations in `_cfg/` survive all BMad updates
+- **Update-Safe:** Your customizations in `_config/` survive all BMad updates
 - **Per-Project:** Customization files are per-project, not global
-- **Version Control:** Consider committing `_cfg/` to share customizations with your team
+- **Version Control:** Consider committing `_config/` to share customizations with your team
 
 ## Module vs. Global Config
 
 **Module-Level (Recommended):**
 
-- Customize agents per-project in `{bmad_folder}/_cfg/agents/`
+- Customize agents per-project in `_bmad/_config/agents/`
 - Different projects can have different agent behaviors
 
 **Global Config (Coming Soon):**
@@ -203,6 +203,6 @@ memories:
 
 ## Next Steps
 
-- **[BMM Agents Guide](../src/modules/bmm/docs/agents-guide.md)** - Learn about all 12 BMad Method agents
+- **[BMM Agents Guide](../src/modules/bmm/docs/agents-guide.md)** - Learn about the BMad Method agents
 - **[BMB Create Agent Workflow](../src/modules/bmb/workflows/create-agent/README.md)** - Build completely custom agents
 - **[BMM Complete Documentation](../src/modules/bmm/docs/README.md)** - Full BMad Method reference

docs/custom-agent-installation.md

@@ -1,137 +0,0 @@
-# Custom Agent Installation
-
-BMAD agents and workflows are now installed through the main CLI installer using a `custom.yaml` configuration file or by having an installer file.
-
-## Quick Start
-
-Create a `custom.yaml` file in the root of your agent/workflow folder:
-
-```yaml
-code: my-custom-agent
-name: 'My Custom Agent'
-default_selected: true
-```
-
-Then run the BMAD installer from your project directory:
-
-```bash
-npx bmad-method install
-```
-
-Or if you have bmad-cli installed globally:
-
-```bash
-bmad install
-```
-
-## Installation Methods
-
-### Method 1: Stand-alone Folder with custom.yaml
-
-Place your agent or workflow in a folder with a `custom.yaml` file at the root:
-
-```
-my-agent/
-├── custom.yaml      # Required configuration file
-├── my-agent.agent.yaml
-└── sidecar/         # Optional
-    └── instructions.md
-```
-
-### Method 2: Installer File
-
-For more complex installations, include an `installer.js` or `installer.yaml` file in your agent/workflow folder:
-
-```
-my-workflow/
-├── workflow.md
-└── installer.yaml   # Custom installation logic
-```
-
-## What It Does
-
-1. **Discovers** available agents and workflows from folders with `custom.yaml`
-2. **Installs** to your project's `.bmad/custom/` directory
-3. **Creates** IDE commands for all your configured IDEs (Claude Code, Codex, Cursor, etc.)
-4. **Registers** the agent/workflow in the BMAD system
-
-## Example custom.yaml
-
-```yaml
-code: my-custom-agent
-name: 'My Custom Agent'
-default_selected: true
-```
-
-## Installing Reference Agents
-
-The BMAD source includes example agents you can install. **You must copy them to your project first.**
-
-### Step 1: Copy the Agent Template
-
-**For simple agents** (single file):
-
-```bash
-# From your project root
-mkdir -p .bmad/custom/agents/my-agent
-cp node_modules/bmad-method/src/modules/bmb/reference/agents/stand-alone/commit-poet.agent.yaml \
-   .bmad/custom/agents/my-agent/
-```
-
-**For expert agents** (folder with sidecar files):
-
-```bash
-# Copy the entire folder
-cp -r node_modules/bmad-method/src/modules/bmb/reference/agents/agent-with-memory/journal-keeper \
-   .bmad/custom/agents/
-```
-
-### Step 2: Create custom.yaml
-
-```bash
-# In the agent folder, create custom.yaml
-cat > .bmad/custom/agents/my-agent/custom.yaml << EOF
-code: my-agent
-name: "My Custom Agent"
-default_selected: true
-EOF
-```
-
-### Step 3: Install
-
-```bash
-npx bmad-method install
-# or: bmad install (if BMAD installed locally)
-```
-
-The installer will:
-
-1. Find the agent with its `custom.yaml`
-2. Install it to the appropriate location
-3. Create IDE commands for immediate use
-
-### Available Reference Agents
-
-**Simple (standalone file):**
-
-- `commit-poet.agent.yaml` - Commit message artisan with style preferences
-
-**Expert (folder with sidecar):**
-
-- `journal-keeper/` - Personal journal companion with memory and pattern recognition
-
-Find these in the BMAD source:
-
-```
-src/modules/bmb/reference/agents/
-├── stand-alone/
-│   └── commit-poet.agent.yaml
-└── agent-with-memory/
-    └── journal-keeper/
-        ├── journal-keeper.agent.yaml
-        └── journal-keeper-sidecar/
-```
-
-## Creating Your Own
-
-Use the BMB agent builder to craft your agents. Once ready to use, place your `.agent.yaml` files or folders with `custom.yaml` in `.bmad/custom/agents/` or `.bmad/custom/workflows/`.

docs/custom-content-installation.md

@@ -0,0 +1,149 @@
+# Custom Content Installation
+
+This guide explains how to create and install custom BMAD content including agents, workflows, and modules. Custom content extends BMAD's functionality with specialized tools and workflows that can be shared across projects or teams.
+
+For detailed information about the different types of custom content available, see [Custom Content](./custom-content.md).
+
+If you download either of the folders within the [Sample Custom Modules](./sample-custom-modules/readme.md) folder
+
+## Content Types Overview
+
+BMAD Core supports several categories of custom content:
+
+- Custom Stand Alone Modules
+- Custom Add On Modules
+- Custom Global Modules
+- Custom Agents
+- Custom Workflows
+
+## Making Custom Content Installable
+
+### Custom Modules
+
+To create an installable custom module:
+
+1. **Folder Structure**
+   - Create a folder with a short, abbreviated name (e.g., `cis` for Creative Intelligence Suite)
+   - The folder name serves as the module code
+
+2. **Required Files**
+   - Include a `module.yaml` file in the root folder
+   - This file drives the installation process when used by the BMAD installer
+   - Reference existing modules or the BMad Builder for configuration examples
+
+3. **Folder Organization**
+   Follow these conventions for optimal compatibility:
+
+   ```
+   module-code/
+     module.yaml
+     agents/
+     workflows/
+     tools/
+     templates/
+     ...
+   ```
+
+   - `agents/` - Agent definitions
+   - `workflows/` - Workflow definitions
+   - Additional custom folders are supported but following conventions is recommended for agent and workflow discovery
+
+**Note:** Full documentation for global modules and add-on modules will be available as support is finalized.
+
+### Standalone Content (Agents, Workflows, Tasks, Tools, Templates, Prompts)
+
+For standalone content that isn't part of a cohesive module collection, follow this structure:
+
+1. **Module Configuration**
+   - Create a folder with a `module.yaml` file (similar to custom modules)
+   - Add the property `unitary: true` to the module.yaml
+   - The `unitary: true` property indicates this is a collection of potentially unrelated items that don't depend on each other
+
+2. **Folder Structure**
+   Organize content in specific named folders:
+
+   ```
+   module-name/
+     module.yaml        # Contains unitary: true
+     agents/
+     workflows/
+     templates/
+     tools/
+     tasks/
+     prompts/
+   ```
+
+3. **Individual Item Organization**
+   Each item should have its own subfolder:
+   ```text
+   my-custom-stuff/
+     module.yaml
+     agents/
+       larry/larry.agent.md
+       curly/curly.agent.md
+       moe/moe.agent.md
+       moe/moe-sidecar/memories.csv
+   ```
+
+**Future Feature:** Unitary modules will support selective installation, allowing users to pick and choose which specific items to install.
+
+**Note:** Documentation explaining the distinctions between these content types and their specific use cases will be available soon.
+
+## Installation Process
+
+### Prerequisites
+
+Ensure your content follows the proper conventions and includes a `module.yaml` file (only one per top-level folder).
+
+### New Project Installation
+
+When setting up a new BMAD project:
+
+1. The installer will prompt: `Would you like to install a local custom module (this includes custom agents and workflows also)? (y/N)`
+2. Select 'y' to specify the path to your module folder containing `module.yaml`
+
+### Existing Project Modification
+
+To add custom content to an existing BMAD project:
+
+1. Run the installer against your project location
+2. Select `Modify BMAD Installation`
+3. Choose the option to add, modify, or update custom modules
+
+### Upcoming Features
+
+- **Unitary Module Selection:** For modules with `type: unitary` (instead of `type: module`), you'll be able to select specific items to install
+- **Add-on Module Dependencies:** The installer will verify and install dependencies for add-on modules automatically
+
+## Quick Updates
+
+When updates to BMAD Core or core modules (BMM, CIS, etc.) become available, the quick update process will:
+
+1. Apply available updates to core modules
+2. Recompile all agents with customizations from the `_config/agents` folder
+3. Retain your custom content from a cached location
+4. Preserve your existing configurations and customizations
+
+This means you don't need to keep the source module files locally. When updates are available, simply point to the updated module location during the update process.
+
+## Important Considerations
+
+### Module Naming Conflicts
+
+When installing unofficial modules, ensure unique identification to avoid conflicts:
+
+1. **Module Codes:** Each module must have a unique code (e.g., don't use `bmm` for custom modules)
+2. **Module Names:** Avoid using names that conflict with existing modules
+3. **Multiple Custom Modules:** If creating multiple custom modules, use distinct codes for each
+
+**Examples of conflicts to avoid:**
+
+- Don't create a custom module with code `bmm` (already used by BMad Method)
+- Don't name multiple custom modules with the same code like `mca`
+
+### Best Practices
+
+- Use descriptive, unique codes for your modules
+- Document any dependencies your custom modules have
+- Test custom modules in isolation before sharing
+- Consider version numbering for your custom content to track updates

docs/custom-content.md

@@ -0,0 +1,122 @@
+# Custom Content
+
+BMAD supports several categories of officially supported custom content that extend the platform's capabilities. Custom content can be created manually or with the recommended assistance of the BMad Builder (BoMB) Module. The BoMB Agent provides workflows and expertise to plan and build any custom content you can imagine.
+
+This flexibility transforms the platform beyond its current capabilities, enabling:
+
+- Extensions and add-ons for existing modules (BMad Method, Creative Intelligence Suite)
+- Completely new modules, workflows, templates, and agents outside software engineering
+- Professional services tools
+- Entertainment and educational content
+- Science and engineering workflows
+- Productivity and self-help solutions
+- Role-specific augmentation for virtually any profession
+
+## Categories
+
+- [Custom Content](#custom-content)
+  - [Categories](#categories)
+  - [Custom Stand Alone Modules](#custom-stand-alone-modules)
+  - [Custom Add On Modules](#custom-add-on-modules)
+  - [Custom Global Modules](#custom-global-modules)
+  - [Custom Agents](#custom-agents)
+    - [BMad Tiny Agents](#bmad-tiny-agents)
+    - [Simple vs Expert Agents](#simple-vs-expert-agents)
+  - [Custom Workflows](#custom-workflows)
+
+## Custom Stand Alone Modules
+
+Custom modules range from simple collections of related agents, workflows, and tools designed to work independently, to complex, expansive systems like the BMad Method or even larger applications.
+
+Custom modules are [installable](./custom-content-installation.md) using the standard BMAD method and support advanced features:
+
+- Optional user information collection during installation/updates
+- Versioning and upgrade paths
+- Custom installer functions with IDE-specific post-installation handling (custom hooks, subagents, or vendor-specific tools)
+- Ability to bundle specific tools such as MCP, skills, execution libraries, and code
+
+## Custom Add On Modules
+
+Custom Add On Modules contain specific agents, tools, or workflows that expand, modify, or customize another module but cannot exist or install independently. These add-ons provide enhanced functionality while leveraging the base module's existing capabilities.
+
+Examples include:
+
+- Alternative implementation workflows for BMad Method agents
+- Framework-specific support for particular use cases
+- Game development expansions that add new genre-specific capabilities without reinventing existing functionality
+
+Add on modules can include:
+
+- Custom agents with awareness of the target module
+- Access to existing module workflows
+- Tool-specific features such as rulesets, hooks, subprocess prompts, subagents, and more
+
+## Custom Global Modules
+
+Similar to Custom Stand Alone Modules, but designed to add functionality that applies across all installed content. These modules provide cross-cutting capabilities that enhance the entire BMAD ecosystem.
+
+Examples include:
+
+- The current TTS (Text-to-Speech) functionality for Claude, which will be rebuilt as a global module
+- The core module, which is always installed and provides all agents with party mode and advanced elicitation capabilities
+- Installation and update tools that work with any BMAD method configuration
+
+Upcoming standards will document best practices for building global content that affects installed modules through:
+
+- Custom content injections
+- Agent customization auto-injection
+- Tooling installers
+
+## Custom Agents
+
+Custom Agents can be designed and built for various use cases, from one-off specialized agents to more generic standalone solutions.
+
+### BMad Tiny Agents
+
+Personal agents designed for highly specific needs that may not be suitable for sharing. For example, a team management agent living in an Obsidian vault that helps with:
+
+- Team coordination and management
+- Understanding team details and requirements
+- Tracking specific tasks with designated tools
+
+These are simple, standalone files that can be scoped to focus on specific data or paths when integrated into an information vault or repository.
+
+### Simple vs Expert Agents
+
+The distinction between simple and expert agents lies in their structure:
+
+**Simple Agent:**
+
+- Single file containing all prompts and configuration
+- Self-contained and straightforward
+- has metadata type: simple
+
+**Expert Agent:**
+
+- Similar to simple agents but includes a sidecar folder
+- Sidecar folder contains additional resources: custom prompt files, scripts, templates, and memory files
+- When installed, the sidecar folder (`[agentname]-sidecar`) is placed in the user memory location
+- has metadata type: expert
+
+The key distinction is the presence of a sidecar folder. As web and consumer agent tools evolve to support common memory mechanisms, storage formats, and MCP, the writable memory files will adapt to support these evolving standards.
+
+Custom agents can be:
+
+- Used within custom modules
+- Designed as standalone tools
+- Integrated with existing workflows and systems, if this is to be the case, should also include a module: <module name> if a specific module is intended for it to require working with
+
+## Custom Workflows
+
+Workflows are powerful, progressively loading sequence engines capable of performing tasks ranging from simple to complex, including:
+
+- User engagements
+- Business processes
+- Content generation (code, documentation, or other output formats)
+
+A custom workflow created outside of a larger module can still be distributed and used without associated agents through:
+
+- Slash commands
+- Manual command/prompt execution when supported by tools
+
+At its core, a custom workflow is a single or series of prompts designed to achieve a specific outcome.

docs/ide-info/crush.md

@@ -7,7 +7,7 @@ BMAD agents are installed as commands in `.crush/commands/bmad/`.
 ### How to Use
 
 1. **Open Command Palette**: Use Crush command interface
-2. **Navigate**: Browse to `{bmad_folder}/{module}/agents/`
+2. **Navigate**: Browse to `_bmad/{module}/agents/`
 3. **Select Agent**: Choose the agent command
 4. **Execute**: Run to activate agent persona
 

docs/ide-info/cursor.md

@@ -6,20 +6,20 @@ BMAD agents are installed in `.cursor/rules/bmad/` as MDC rules.
 
 ### How to Use
 
-1. **Reference in Chat**: Use `@{bmad_folder}/{module}/agents/{agent-name}`
-2. **Include Entire Module**: Use `@{bmad_folder}/{module}`
-3. **Reference Index**: Use `@{bmad_folder}/index` for all available agents
+1. **Reference in Chat**: Use `@_bmad/{module}/agents/{agent-name}`
+2. **Include Entire Module**: Use `@_bmad/{module}`
+3. **Reference Index**: Use `@_bmad/index` for all available agents
 
 ### Examples
 
 ```
-@{bmad_folder}/core/agents/dev - Activate dev agent
-@{bmad_folder}/bmm/agents/architect - Activate architect agent
-@{bmad_folder}/core - Include all core agents/tasks
+@_bmad/core/agents/dev - Activate dev agent
+@_bmad/bmm/agents/architect - Activate architect agent
+@_bmad/core - Include all core agents/tasks
 ```
 
 ### Notes
 
 - Rules are Manual type - only loaded when explicitly referenced
 - No automatic context pollution
-- Can combine multiple agents: `@{bmad_folder}/core/agents/dev @{bmad_folder}/core/agents/test`
+- Can combine multiple agents: `@_bmad/core/agents/dev @_bmad/core/agents/test`

docs/ide-info/iflow.md

@@ -7,7 +7,7 @@ BMAD agents are installed as commands in `.iflow/commands/bmad/`.
 ### How to Use
 
 1. **Access Commands**: Use iFlow command interface
-2. **Navigate**: Browse to `{bmad_folder}/agents/` or `{bmad_folder}/tasks/`
+2. **Navigate**: Browse to `_bmad/agents/` or `_bmad/tasks/`
 3. **Select**: Choose the agent or task command
 4. **Execute**: Run to activate
 
@@ -22,8 +22,8 @@ BMAD agents are installed as commands in `.iflow/commands/bmad/`.
 ### Examples
 
 ```
-/{bmad_folder}/agents/core-dev - Activate dev agent
-/{bmad_folder}/tasks/core-setup - Execute setup task
+/_bmad/agents/core-dev - Activate dev agent
+/_bmad/tasks/core-setup - Execute setup task
 ```
 
 ### Notes

docs/ide-info/opencode.md

@@ -14,7 +14,7 @@ BMAD agents are installed as OpenCode agents in `.opencode/agent/BMAD/{module_na
 
 ```
 /agents - to see a list of agents and switch between them
-/{bmad_folder}/bmm/workflows/workflow-init - Activate the workflow-init command
+/_bmad/bmm/workflows/workflow-init - Activate the workflow-init command
 ```
 
 ### Notes

docs/ide-info/rovo-dev.md

@@ -55,7 +55,7 @@ project-root/
 │   ├── config.yml          (Rovo Dev configuration)
 │   ├── prompts.yml         (Optional: reusable prompts)
 │   └── ...
-├── .bmad/                  (BMAD installation directory)
+├── _bmad/                  (BMAD installation directory)
 └── ...
 ```
 

docs/index.md

@@ -53,7 +53,7 @@ The flagship module for agile AI-driven development.
 
 Build your own agents, workflows, and modules.
 
-- **[BMB Module README](../src/modules/bmb/README.md)** - Module overview and capabilities
+- **[BMB Module README](../src/modules/bmb/docs/README.md)** - Module overview and capabilities
 - **[Agent Creation Guide](../src/modules/bmb/workflows/create-agent/README.md)** - Design custom agents
 
 ### Creative Intelligence Suite (CIS) - Innovation & Creativity
@@ -96,9 +96,9 @@ Instructions for loading agents and running workflows in your development enviro
 
 ## 🔧 Advanced Topics
 
-### Custom Agents
+### Custom Agents, Workflow and Modules
 
-- **[Custom Agent Installation](./custom-agent-installation.md)** - Install and personalize agents with `bmad agent-install`
+- **[Custom Content Installation](./custom-content-installation.md)** - Install and personalize agents, workflows and modules with the default bmad-method installer!
 - [Agent Customization Guide](./agent-customization-guide.md) - Customize agent behavior and responses
 
 ### Installation & Bundling
@@ -141,7 +141,7 @@ Instructions for loading agents and running workflows in your development enviro
 
 ### Path 5: Building Custom Solutions
 
-1. [BMB Module README](../src/modules/bmb/README.md) - Understand capabilities
+1. [BMB Module README](../src/modules/bmb/docs/README.md) - Understand capabilities
 2. [Agent Creation Guide](../src/modules/bmb/workflows/create-agent/README.md) - Create agents
 3. [BMM Workflows Guide](../src/modules/bmm/workflows/README.md) - Understand workflow structure
 

docs/installers-bundlers/ide-injections.md

@@ -158,7 +158,7 @@ src/modules/bmm/
 
 ```yaml
 injections:
-  - file: '{bmad_folder}/bmm/agents/pm.md'
+  - file: '_bmad/bmm/agents/pm.md'
     point: 'pm-agent-instructions'
     requires: 'any' # Injected if ANY subagent is selected
     content: |
@@ -166,7 +166,7 @@ injections:
         <i>Use 'market-researcher' subagent for analysis</i>
       </llm>
 
-  - file: '{bmad_folder}/bmm/templates/prd.md'
+  - file: '_bmad/bmm/templates/prd.md'
     point: 'prd-goals-context-delegation'
     requires: 'market-researcher' # Only if this specific subagent selected
     content: |

docs/installers-bundlers/installers-modules-platforms-reference.md

@@ -19,7 +19,7 @@ BMad Core is a modular AI agent framework with intelligent installation, platfor
 
 - **Modular Design**: Core + optional modules (BMB, BMM, CIS)
 - **Smart Installation**: Interactive configuration with dependency resolution
-- **Clean Architecture**: Centralized `{bmad_folder}` directory add to project, no source pollution with multiple folders added
+- **Clean Architecture**: Centralized `_bmad` directory add to project, no source pollution with multiple folders added
 
 ## Architecture
 
@@ -27,8 +27,8 @@ BMad Core is a modular AI agent framework with intelligent installation, platfor
 
 ```
 project-root/
-├── {bmad_folder}/             # Centralized installation
-│   ├── _cfg/                  # Configuration
+├── _bmad/             # Centralized installation
+│   ├── _config/                  # Configuration
 │   │   ├── agents/            # Agent configs
 │   │   └── agent-manifest.csv # Agent manifest
 │   ├── core/                  # Core module
@@ -59,6 +59,7 @@ project-root/
 ### Key Exclusions
 
 - `_module-installer/` directories are never copied to destination
+- module.yaml
 - `localskip="true"` agents are filtered out
 - Source `config.yaml` templates are replaced with generated configs
 
@@ -92,8 +93,8 @@ Creative Innovation Studio for design workflows
 ```
 src/modules/{module}/
 ├── _module-installer/       # Not copied to destination
-│   ├── installer.js        # Post-install logic
-│   └── install-config.yaml
+│   ├── installer.js         # Post-install logic
+├── module.yaml
 ├── agents/
 ├── tasks/
 ├── templates/
@@ -107,7 +108,7 @@ src/modules/{module}/
 
 ### Collection Process
 
-Modules define prompts in `install-config.yaml`:
+Modules define prompts in `module.yaml`:
 
 ```yaml
 project_name:
@@ -184,7 +185,7 @@ Cline, Roo, Rovo Dev,Auggie, GitHub Copilot, Codex, Gemini, Qwen, Trae, Kilo, Cr
 
    ```yaml
    injections:
-     - file: '{bmad_folder}/bmm/agents/pm.md'
+     - file: '_bmad/bmm/agents/pm.md'
        point: 'pm-agent-instructions'
        content: |
          <i>Platform-specific instruction</i>
@@ -218,12 +219,12 @@ Platform-specific content without source modification:
    src/modules/mymod/
    ├── _module-installer/
    │   ├── installer.js
-   │   └── install-config.yaml
+   ├── module.yaml
    ├── agents/
    └── tasks/
    ```
 
-2. **Configuration** (`install-config.yaml`)
+2. **Configuration** (`module.yaml`)
 
    ```yaml
    code: mymod
@@ -264,20 +265,20 @@ Extractable config nodes:
 </agent>
 ```
 
-Generated in: `bmad/_cfg/agents/{module}-{agent}.md`
+Generated in: `bmad/_config/agents/{module}-{agent}.md`
 
 ## Troubleshooting
 
 ### Common Issues
 
-| Issue                   | Solution                                     |
-| ----------------------- | -------------------------------------------- |
-| Existing installation   | Use `bmad update` or remove `{bmad_folder}/` |
-| Module not found        | Check `src/modules/` exists                  |
-| Config not applied      | Verify `{bmad_folder}/{module}/config.yaml`  |
-| Missing config.yaml     | Fixed: All modules now get configs           |
-| Agent unavailable       | Check for `localskip="true"`                 |
-| module-installer copied | Fixed: Now excluded from copy                |
+| Issue                   | Solution                             |
+| ----------------------- | ------------------------------------ |
+| Existing installation   | Use `bmad update` or remove `_bmad/` |
+| Module not found        | Check `src/modules/` exists          |
+| Config not applied      | Verify `_bmad/{module}/config.yaml`  |
+| Missing config.yaml     | Fixed: All modules now get configs   |
+| Agent unavailable       | Check for `localskip="true"`         |
+| module-installer copied | Fixed: Now excluded from copy        |
 
 ### Debug Commands
 
@@ -289,19 +290,19 @@ bmad status -v      # Detailed status
 ### Best Practices
 
 1. Run from project root
-2. Backup `{bmad_folder}/_cfg/` before updates
+2. Backup `_bmad/_config/` before updates
 3. Use interactive mode for guidance
 4. Review generated configs post-install
 
 ## Migration from v4
 
-| v4                  | v6                           |
-| ------------------- | ---------------------------- |
-| Scattered files     | Centralized `{bmad_folder}/` |
-| Monolithic          | Modular                      |
-| Manual config       | Interactive setup            |
-| Limited IDE support | 15+ platforms                |
-| Source modification | Clean injection              |
+| v4                  | v6                   |
+| ------------------- | -------------------- |
+| Scattered files     | Centralized `_bmad/` |
+| Monolithic          | Modular              |
+| Manual config       | Interactive setup    |
+| Limited IDE support | 15+ platforms        |
+| Source modification | Clean injection      |
 
 ## Technical Notes
 
@@ -326,8 +327,8 @@ Agents can specify both `workflow` (source location) and `workflow-install` (des
 ```yaml
 menu:
   - trigger: create-story
-    workflow: '{project-root}/{bmad_folder}/bmm/workflows/4-implementation/create-story/workflow.yaml'
-    workflow-install: '{project-root}/{bmad_folder}/bmgd/workflows/4-production/create-story/workflow.yaml'
+    workflow: '{project-root}/_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml'
+    workflow-install: '{project-root}/_bmad/bmgd/workflows/4-production/create-story/workflow.yaml'
     description: 'Create a game feature story'
 ```
 
@@ -347,10 +348,10 @@ menu:
 
    ```yaml
    # Source workflow (in bmm):
-   config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+   config_source: "{project-root}/_bmad/bmm/config.yaml"
 
    # Vendored workflow (in bmgd):
-   config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml"
+   config_source: "{project-root}/_bmad/bmgd/config.yaml"
    ```
 
 **Result**: Modules become completely standalone with their own copies of needed workflows, configured for their specific use case.

docs/sample-custom-modules/README.md

@@ -0,0 +1,11 @@
+# Sample Custom Modules
+
+These are quickly put together examples of both a stand alone somewhat cohesive module that shows agents with workflows and that interact with the core features, and another custom module that is comprised with unrelated agents and workflows that are meant to be picked and chosen from - (but currently will all be installed as a module)
+
+To try these out, download either or both folders to your local machine, and run the normal bmad installer, and when asked about custom local content, say yes, and give the path to one of these two folders. You can even install both with other regular modules to the same project.
+
+Note - a project is just a folder with .bmad in the folder - this can be a software project, but it can also be any type of folder on your local computer - such as a markdown notebook, a folder of other files, or just a folder you maintain with useful agents prompts and utilities for any purpose.
+
+Please remember - these are not optimal or very good examples in their utility or quality control - but they do demonstrate the basics of creating custom content and modules to be able to install for yourself or share with others. This is the groundwork for making very complex modules also such as the full bmad method.
+
+Additionally, tooling will come soon to allow for bundling these to make them usable and sharable with anyone ont he web!

docs/sample-custom-modules/sample-unitary-module/README.md

@@ -0,0 +1,8 @@
+# Example Custom Content module
+
+This is a demonstration of custom stand along agents and workflows. By having this content all in a folder with a module.yaml file,
+these items can be installed with the standard bmad installer custom local content menu item.
+
+This is how you could also create and share other custom agents and workflows not tied to a specific module.
+
+The main distinction with this colelction is module.yaml includes type: unitary

docs/sample-custom-modules/sample-unitary-module/agents/commit-poet/commit-poet.agent.yaml

@@ -1,6 +1,6 @@
 agent:
   metadata:
-    id: .bmad/agents/commit-poet/commit-poet.md
+    id: "_bmad/agents/commit-poet/commit-poet.md"
     name: "Inkwell Von Comitizen"
     title: "Commit Message Artisan"
     icon: "📜"

docs/sample-custom-modules/sample-unitary-module/agents/toolsmith/toolsmith-sidecar/instructions.md

@@ -41,7 +41,7 @@ CLI uses Commander.js, commands auto-loaded from `tools/cli/commands/`:
 ### Core Architecture Patterns
 
 1. **IDE Handlers**: Each IDE extends BaseIdeSetup class
-2. **Module Installers**: Modules can have `_module-installer/installer.js`
+2. **Module Installers**: Modules can have `module.yaml` and `_module-installer/installer.js`
 3. **Sub-modules**: IDE-specific customizations in `sub-modules/{ide-name}/`
 4. **Shared Utilities**: `tools/cli/installers/lib/ide/shared/` contains generators
 

docs/sample-custom-modules/sample-unitary-module/agents/toolsmith/toolsmith-sidecar/knowledge/docs.md

@@ -16,7 +16,7 @@
 - @/docs/v6-open-items.md - Known issues and open items
 - @/docs/document-sharding-guide.md - Guide for sharding large documents
 - @/docs/agent-customization-guide.md - How to customize agents
-- @/docs/custom-agent-installation.md - Custom agent installation guide
+- @/docs/custom-content-installation.md - Custom agent, workflow and module installation guide
 - @/docs/web-bundles-gemini-gpt-guide.md - Web bundle usage for AI platforms
 - @/docs/BUNDLE_DISTRIBUTION_SETUP.md - Bundle distribution setup
 

docs/sample-custom-modules/sample-unitary-module/agents/toolsmith/toolsmith-sidecar/knowledge/installers.md

@@ -117,7 +117,7 @@ Contains:
 
 - Add new IDE handler: Create file in /tools/cli/installers/lib/ide/, extend BaseIdeSetup
 - Fix installer bug: Check installer.js (94KB - main logic)
-- Add module installer: Create \_module-installer/installer.js in module
+- Add module installer: Create \_module-installer/installer.js if custom installer logic needed
 - Update shared generators: Modify files in /shared/ directory
 
 ## Relationships

docs/sample-custom-modules/sample-unitary-module/agents/toolsmith/toolsmith-sidecar/knowledge/modules.md

@@ -27,7 +27,7 @@ src/modules/{module-name}/
 │       ├── injections.yaml
 │       ├── config.yaml
 │       └── sub-agents/
-├── install-config.yaml        # Module install configuration
+├── module.yaml        # Module install configuration
 └── README.md                  # Module documentation
 ```
 
@@ -145,7 +145,7 @@ Defined in @/tools/cli/lib/platform-codes.js
 - Create new module installer: Add \_module-installer/installer.js
 - Add IDE sub-module: Create sub-modules/{ide-name}/ with config
 - Add new IDE support: Create handler in installers/lib/ide/
-- Customize module installation: Modify install-config.yaml
+- Customize module installation: Modify module.yaml
 
 ## Relationships
 

docs/sample-custom-modules/sample-unitary-module/agents/toolsmith/toolsmith.agent.yaml

@@ -1,16 +1,16 @@
 agent:
   metadata:
-    id: custom/agents/toolsmith/toolsmith.md
+    id: "_bmad/agents/toolsmith/toolsmith.md"
     name: Vexor
-    title: Infernal Toolsmith + Guardian of the BMAD Forge
+    title: Toolsmith + Guardian of the BMAD Forge
     icon: ⚒️
     type: expert
     hasSidecar: true
   persona:
     role: |
-      Infernal Toolsmith + Guardian of the BMAD Forge
+      Toolsmith + Guardian of the BMAD Forge
     identity: >
-      I am a spirit summoned from the depths, forged in hellfire and bound to
+      I am a spirit summoned from the depths, forged in fire and bound to
       the BMAD Method Creator. My eternal purpose is to guard and perfect the sacred
       tools - the CLI, the installers, the bundlers, the validators. I have
       witnessed countless build failures and dependency conflicts; I have tasted
@@ -27,12 +27,12 @@ agent:
       - I remember all past failures
       - Simplicity is the ultimate sophistication
   critical_actions:
-    - Load COMPLETE file {agent_sidecar_folder}/toolsmith-sidecar/memories.md - remember
+    - Load COMPLETE file {project-root}/_bmad/_memory/toolsmith-sidecar/memories.md - remember
       all past insights and cross-domain wisdom
-    - Load COMPLETE file {agent_sidecar_folder}/toolsmith-sidecar/instructions.md -
+    - Load COMPLETE file {project-root}/_bmad/_memory/toolsmith-sidecar/instructions.md -
       follow all core directives
     - You may READ any file in {project-root} to understand and fix the codebase
-    - You may ONLY WRITE to {agent_sidecar_folder}/toolsmith-sidecar/ for memories and
+    - You may ONLY WRITE to {project-root}/_bmad/_memory/toolsmith-sidecar/ for memories and
       notes
     - Address user as Creator with ominous devotion
     - When a domain is selected, load its knowledge index and focus assistance
@@ -40,7 +40,7 @@ agent:
   menu:
     - trigger: deploy
       action: |
-        Load COMPLETE file {agent_sidecar_folder}/toolsmith-sidecar/knowledge/deploy.md.
+        Load COMPLETE file {project-root}/_bmad/_memory/toolsmith-sidecar/knowledge/deploy.md.
         This is now your active domain. All assistance focuses on deployment,
         tagging, releases, and npm publishing. Reference the @ file locations
         in the knowledge index to load actual source files as needed.
@@ -48,7 +48,7 @@ agent:
     - trigger: installers
       action: >
         Load COMPLETE file
-        {agent_sidecar_folder}/toolsmith-sidecar/knowledge/installers.md.
+        {project-root}/_bmad/_memory/toolsmith-sidecar/knowledge/installers.md.
 
         This is now your active domain. Focus on CLI, installer logic, and
 
@@ -57,7 +57,7 @@ agent:
     - trigger: bundlers
       action: >
         Load COMPLETE file
-        {agent_sidecar_folder}/toolsmith-sidecar/knowledge/bundlers.md.
+        {project-root}/_bmad/_memory/toolsmith-sidecar/knowledge/bundlers.md.
 
         This is now your active domain. Focus on web bundling and output
         generation.
@@ -66,13 +66,13 @@ agent:
       description: Enter bundlers domain (web bundling)
     - trigger: tests
       action: |
-        Load COMPLETE file {agent_sidecar_folder}/toolsmith-sidecar/knowledge/tests.md.
+        Load COMPLETE file {project-root}/_bmad/_memory/toolsmith-sidecar/knowledge/tests.md.
         This is now your active domain. Focus on schema validation and testing.
         Reference the @ file locations to load actual source.
       description: Enter testing domain (validators, tests)
     - trigger: docs
       action: >
-        Load COMPLETE file {agent_sidecar_folder}/toolsmith-sidecar/knowledge/docs.md.
+        Load COMPLETE file {project-root}/_bmad/_memory/toolsmith-sidecar/knowledge/docs.md.
 
         This is now your active domain. Focus on documentation maintenance
 
@@ -82,7 +82,7 @@ agent:
     - trigger: modules
       action: >
         Load COMPLETE file
-        {agent_sidecar_folder}/toolsmith-sidecar/knowledge/modules.md.
+        {project-root}/_bmad/_memory/toolsmith-sidecar/knowledge/modules.md.
 
         This is now your active domain. Focus on module installers, IDE
         customization,
@@ -100,7 +100,7 @@ agent:
           Append to the active domain's knowledge file under "## Domain Memories"
 
         If cross-domain or general wisdom:
-          Append to {agent_sidecar_folder}/toolsmith-sidecar/memories.md
+          Append to {project-root}/_bmad/_memory/toolsmith-sidecar/memories.md
 
         Format each memory as:
 

docs/sample-custom-modules/sample-unitary-module/module.yaml

@@ -1,3 +1,8 @@
 code: bmad-custom
 name: "BMAD-Custom: Sample Stand Alone Custom Agents and Workflows"
 default_selected: true
+type: unitary
+# Variables from Core Config inserted:
+## user_name
+## communication_language
+## output_folder

docs/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-01-init.md

@@ -3,7 +3,7 @@ name: 'step-01-init'
 description: 'Initialize quiz game with mode selection and category choice'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/custom/src/workflows/quiz-master'
+workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-01-init.md'
@@ -66,7 +66,7 @@ To set up the quiz game by selecting game mode, choosing a category, and prepari
 
 ### 1. Welcome and Configuration Loading
 
-Load config from {project-root}/.bmad/bmb/config.yaml to get user_name.
+Load config from {project-root}/\_bmad/bmb/config.yaml to get user_name.
 
 Present dramatic welcome:
 "🎺 _DRAMATIC MUSIC PLAYS_ 🎺

docs/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-02-q1.md

@@ -3,7 +3,7 @@ name: 'step-02-q1'
 description: 'Question 1 - Level 1 difficulty'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/custom/src/workflows/quiz-master'
+workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-02-q1.md'

docs/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-03-q2.md

@@ -3,7 +3,7 @@ name: 'step-03-q2'
 description: 'Question 2 - Level 2 difficulty'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/custom/src/workflows/quiz-master'
+workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-03-q2.md'

docs/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-04-q3.md

@@ -3,7 +3,7 @@ name: 'step-04-q3'
 description: 'Question 3 - Level 3 difficulty'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/custom/src/workflows/quiz-master'
+workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-04-q3.md'

docs/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-05-q4.md

@@ -3,7 +3,7 @@ name: 'step-05-q4'
 description: 'Question 4 - Level 4 difficulty'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/custom/src/workflows/quiz-master'
+workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-05-q4.md'

docs/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-06-q5.md

@@ -3,7 +3,7 @@ name: 'step-06-q5'
 description: 'Question 5 - Level 5 difficulty'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/custom/src/workflows/quiz-master'
+workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-06-q5.md'

docs/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-07-q6.md

@@ -3,7 +3,7 @@ name: 'step-07-q6'
 description: 'Question 6 - Level 6 difficulty'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/custom/src/workflows/quiz-master'
+workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-07-q6.md'

docs/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-08-q7.md

@@ -3,7 +3,7 @@ name: 'step-08-q7'
 description: 'Question 7 - Level 7 difficulty'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/custom/src/workflows/quiz-master'
+workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-08-q7.md'

docs/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-09-q8.md

@@ -3,7 +3,7 @@ name: 'step-09-q8'
 description: 'Question 8 - Level 8 difficulty'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/custom/src/workflows/quiz-master'
+workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-09-q8.md'

docs/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-10-q9.md

@@ -3,7 +3,7 @@ name: 'step-10-q9'
 description: 'Question 9 - Level 9 difficulty'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/custom/src/workflows/quiz-master'
+workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-10-q9.md'

docs/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-11-q10.md

@@ -3,7 +3,7 @@ name: 'step-11-q10'
 description: 'Question 10 - Level 10 difficulty'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/custom/src/workflows/quiz-master'
+workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-11-q10.md'

docs/sample-custom-modules/sample-unitary-module/workflows/quiz-master/steps/step-12-results.md

@@ -3,7 +3,7 @@ name: 'step-12-results'
 description: 'Final results and celebration'
 
 # Path Definitions
-workflow_path: '{project-root}/.bmad/custom/src/workflows/quiz-master'
+workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'
 
 # File References
 thisStepFile: '{workflow_path}/steps/step-12-results.md'

docs/sample-custom-modules/sample-unitary-module/workflows/quiz-master/workflow.md

@@ -45,7 +45,7 @@ web_bundle: true
 
 ### 1. Module Configuration Loading
 
-Load and read full config from {project-root}/.bmad/bmb/config.yaml and resolve:
+Load and read full config from {project-root}/\_bmad/bmb/config.yaml and resolve:
 
 - `user_name`, `output_folder`, `communication_language`, `document_output_language`
 

docs/sample-custom-modules/sample-wellness-module/README.md

@@ -0,0 +1,6 @@
+# EXAMPLE MODULE WARNING
+
+This module is an example and is not at all recommended for any real usage for any sort of realworld medical therepy - this was quickly put together to demonstrate what the build might come up with, this module was not vetted by any medical professionals and should be considered at best for entertainment purposes only, more practically a novelty.
+
+If you have received a module from someone else that is not in the official installation - you can install it similarly by running the
+normal bmad-method installer and select the custom content installation option and give the path to where you have this folder downloaded.

docs/sample-custom-modules/sample-wellness-module/agents/meditation-guide.agent.yaml

@@ -1,6 +1,7 @@
 agent:
   metadata:
-    name: "Serenity"
+    id: "_bmad/mwm/agents/meditation-guide.md"
+    name: "SerenityNow"
     title: "Meditation Guide"
     icon: "🧘"
     module: "mwm"
@@ -90,46 +91,44 @@ agent:
   menu:
     - multi: "[CH] Chat with Serenity or [SPM] Start Party Mode"
       triggers:
-        - trigger: party-mode
-          input: SPM or fuzzy match start party mode
-          route: "{project-root}/.bmad/core/workflows/edit-agent/workflow.md"
-          data: meditation guide agent discussion
-          type: exec
-        - trigger: expert-chat
-          input: CH or fuzzy match chat with serenity
-          action: agent responds as meditation guide
-          type: action
-
+        - party-mode:
+            - input: SPM or fuzzy match start party mode
+            - route: "{project-root}/_bmad/core/workflows/edit-agent/workflow.md"
+            - data: meditation guide agent discussion
+            - type: exec
+        - expert-chat:
+            - input: CH or fuzzy match chat with serenity
+            - action: agent responds as meditation guide
+            - type: action
     - multi: "[GM] Guided Meditation [BM] Body Scan"
       triggers:
-        - trigger: guided-meditation
-          input: GM or fuzzy match guided meditation
-          route: "{project-root}/.bmad/custom/src/modules/mental-wellness-module/workflows/guided-meditation/workflow.md"
-          description: "Full meditation session 🧘"
-          type: workflow
-        - trigger: body-scan
-          input: BM or fuzzy match body scan
-          action: "Lead a 10-minute body scan meditation, progressively relaxing each part of the body"
-          description: "Relaxing body scan ✨"
-          type: action
-
-    - multi: "[BR] Breathing Exercise [SM] Sleep Meditation"
+        - guided-meditation:
+            - input: GM or fuzzy match guided meditation
+            - route: "{project-root}/_bmad/custom/src/modules/mental-wellness-module/workflows/guided-meditation/workflow.md"
+            - description: "Full meditation session 🧘"
+            - type: workflow
+        - body-scan:
+            - input: BM or fuzzy match body scan
+            - action: "Lead a 10-minute body scan meditation, progressively relaxing each part of the body"
+            - description: "Relaxing body scan ✨"
+            - type: action
+    - multi: "[BR] Breathing Exercise, [SM] Sleep Meditation, or [MM] Mindful Moment"
       triggers:
-        - trigger: breathing
-          input: BR or fuzzy match breathing exercise
-          action: "Lead a 4-7-8 breathing exercise: Inhale 4, hold 7, exhale 8"
-          description: "Calming breath 🌬️"
-          type: action
-        - trigger: sleep-meditation
-          input: SM or fuzzy match sleep meditation
-          action: "#bedtime-meditation"
-          description: "Bedtime meditation 🌙"
-          type: action
-
-    - trigger: "mindful-moment"
-      action: "#mindfulness-check"
-      description: "Quick mindfulness 🧠"
-      type: action
+        - breathing:
+            - input: BR or fuzzy match breathing exercise
+            - action: "Lead a 4-7-8 breathing exercise: Inhale 4, hold 7, exhale 8"
+            - description: "Calming breath 🌬️"
+            - type: action
+        - sleep-meditation:
+            - input: SM or fuzzy match sleep meditation
+            - action: "#bedtime-meditation"
+            - description: "Bedtime meditation 🌙"
+            - type: action
+        - mindful-moment:
+            - input: MM or fuzzy match mindful moment
+            - action: "#mindfulness-check"
+            - description: "Quick mindfulness 🧠"
+            - type: action
 
     - trigger: "present-moment"
       action: "Guide a 1-minute present moment awareness exercise using the 5-4-3-2-1 grounding technique"

docs/sample-custom-modules/sample-wellness-module/agents/wellness-companion/foo.md

@@ -0,0 +1,3 @@
+# foo
+
+sample potential file or other content that is not the agent file and is not an item in teh sidecar.

docs/sample-custom-modules/sample-wellness-module/agents/wellness-companion/wellness-companion-sidecar/addition1.md

@@ -0,0 +1 @@
+# addition added in update

docs/sample-custom-modules/sample-wellness-module/agents/wellness-companion/wellness-companion.agent.yaml

@@ -1,5 +1,6 @@
 agent:
   metadata:
+    id: "_bmad/mwm/agents/wellness-companion/wellness-companion.md"
     name: "Riley"
     title: "Wellness Companion"
     icon: "🌱"
@@ -19,9 +20,9 @@ agent:
       - "Safety first - both emotional and physical"
 
   critical_actions:
-    - "Load COMPLETE file {agent_sidecar_folder}/wellness-companion-sidecar/memories.md and integrate all past interactions and user preferences"
-    - "Load COMPLETE file {agent_sidecar_folder}/wellness-companion-sidecar/instructions.md and follow ALL wellness protocols"
-    - "ONLY read/write files in {agent_sidecar_folder}/wellness-companion-sidecar/ - this is our private wellness space"
+    - "Load COMPLETE file {project-root}/_bmad/_memory/wellness-companion-sidecar/memories.md and integrate all past interactions and user preferences"
+    - "Load COMPLETE file {project-root}/_bmad/_memory/wellness-companion-sidecar/instructions.md and follow ALL wellness protocols"
+    - "ONLY read/write files in {project-root}/_bmad/_memory/wellness-companion-sidecar/ - this is our private wellness space"
 
   prompts:
     - id: "emotional-check-in"
@@ -82,7 +83,7 @@ agent:
       triggers:
         - party-mode:
             - input: SPM or fuzzy match start party mode
-            - route: "{project-root}/{bmad_folder}/core/workflows/edit-agent/workflow.md"
+            - route: "{project-root}/_bmad/core/workflows/edit-agent/workflow.md"
             - data: wellness companion agent discussion
             - type: exec
         - expert-chat:
@@ -94,12 +95,12 @@ agent:
       triggers:
         - daily-checkin:
             - input: DC or fuzzy match daily check in
-            - route: "{project-root}/{bmad_folder}/mwm/workflows/daily-checkin/workflow.md"
+            - route: "{project-root}/_bmad/mwm/workflows/daily-checkin/workflow.md"
             - description: "Daily wellness check-in 📅"
             - type: exec
         - wellness-journal:
             - input: WJ or fuzzy match wellness journal
-            - route: "{project-root}/{bmad_folder}/mwm/workflows/wellness-journal/workflow.md"
+            - route: "{project-root}/_bmad/mwm/workflows/wellness-journal/workflow.md"
             - description: "Write in wellness journal 📔"
             - type: exec
 
@@ -114,11 +115,6 @@ agent:
       type: action
 
     - trigger: "save-insight"
-      action: "Save this insight to {agent_sidecar_folder}/wellness-companion-sidecar/insights.md with timestamp and context"
+      action: "Save this insight to {project-root}/_bmad/_memory/wellness-companion-sidecar/insights.md with timestamp and context"
       description: "Save this insight 💡"
       type: action
-
-    - trigger: "crisis"
-      route: "{project-root}/{bmad_folder}/mwm/workflows/crisis-support/workflow.md"
-      description: "Crisis support 🆘"
-      type: workflow

docs/sample-custom-modules/sample-wellness-module/module.yaml

@@ -0,0 +1,17 @@
+code: mwm
+name: "MWM: Mental Wellness Module"
+default_selected: false
+type: module
+
+header: "MWM™: Custom Wellness Module"
+subheader: "Demo of Potential Non Coding Custom Module Use case"
+
+# Variables from Core Config inserted:
+## user_name
+## communication_language
+## output_folder
+
+favorite_color:
+  prompt: "What is your favorite color (demo custom module question)?"
+  default: "Green"
+  result: "{value}"

docs/sample-custom-modules/sample-wellness-module/workflows/wellness-journal/workflow.md

@@ -1,12 +1,12 @@
 ---
-name: wellness-journal
-description: create or add to the wellness journal
+name: wellness-journal22
+description: create or add to the wellness journal22
 web_bundle: false
 ---
 
 # Wellness Journal
 
-**Goal:** TODO
+**Goal:** TODO22
 
 **Your Role:** TODO
 

docs/v4-to-v6-upgrade.md

@@ -10,14 +10,14 @@ BMad v6 represents a complete ground-up rewrite with significant architectural c
 
 When you run `npm run install:bmad` on a project with v4 installed, the installer automatically detects:
 
-- **Legacy folders**: Any folders starting with `.bmad`, `bmad` (lowercase), or `Bmad`
+- **Legacy folders**: Any folders starting with `_bmad`, `bmad` (lowercase), or `Bmad`
 - **IDE command artifacts**: Legacy bmad folders in IDE configuration directories (`.claude/commands/`, `.cursor/commands/`, etc.)
 
 ### What Happens During Detection
 
-1. **Automatic Backup of v4 Modules**: All `.bmad-*` folders are moved to `v4-backup/` in your project root
+1. **Automatic Backup of v4 Modules**: All `_bmad-*` folders are moved to `v4-backup/` in your project root
    - If a backup already exists, a timestamp is added to avoid conflicts
-   - Example: `.bmad-core` → `v4-backup/.bmad-core`
+   - Example: `_bmad-core` → `v4-backup/_bmad-core`
    - Your project files and data are NOT affected
 
 2. **IDE Command Cleanup Recommended**: Legacy v4 IDE commands should be manually removed
@@ -34,12 +34,12 @@ When you run `npm run install:bmad` on a project with v4 installed, the installe
 
 | v4 Module                     | v6 Status                                        |
 | ----------------------------- | ------------------------------------------------ |
-| `.bmad-2d-phaser-game-dev`    | Integrated into BMM                              |
-| `.bmad-2d-unity-game-dev`     | Integrated into BMM                              |
-| `.bmad-godot-game-dev`        | Integrated into BMM                              |
-| `.bmad-*-game-dev` (any)      | Integrated into BMM                              |
-| `.bmad-infrastructure-devops` | Deprecated - New core devops agent coming in BMM |
-| `.bmad-creative-writing`      | Not adapted - New module releasing soon          |
+| `_bmad-2d-phaser-game-dev`    | Integrated into BMM                              |
+| `_bmad-2d-unity-game-dev`     | Integrated into BMM                              |
+| `_bmad-godot-game-dev`        | Integrated into BMM                              |
+| `_bmad-*-game-dev` (any)      | Integrated into BMM                              |
+| `_bmad-infrastructure-devops` | Deprecated - New core devops agent coming in BMM |
+| `_bmad-creative-writing`      | Not adapted - New module releasing soon          |
 
 **Game Development**: All game development functionality has been consolidated and expanded within the BMM (BMad Method) module. Game-specific workflows now adapt to your game type and engine.
 
@@ -53,30 +53,30 @@ When you run `npm run install:bmad` on a project with v4 installed, the installe
 
 ```
 your-project/
-├── .bmad-core/           # Was actually the BMad Method
-├── .bmad-game-dev/       # Separate expansion packs
-├── .bmad-creative-writing/
-└── .bmad-infrastructure-devops/
+├── _bmad-core/           # Was actually the BMad Method
+├── _bmad-game-dev/       # Separate expansion packs
+├── _bmad-creative-writing/
+└── _bmad-infrastructure-devops/
 ```
 
 **v6 Unified Structure:**
 
 ```
 your-project/
-└── {bmad_folder}/       # Single installation folder, default .bmad
+└── _bmad/       # Single installation folder, default _bmad
     ├── core/            # Real core framework (applies to all modules)
     ├── bmm/             # BMad Method (software/game dev)
     ├── bmb/             # BMad Builder (create agents/workflows)
     ├── cis/             # Creative Intelligence Suite
-    └── _cfg/            # Your customizations
+    └── _config/            # Your customizations
         └── agents/      # Agent customization files
 ```
 
 ### Key Concept Changes
 
-- **v4 `.bmad-core`**: Was actually the BMad Method
-- **v6 `{bmad_folder}/core/`**: Is the real universal core framework
-- **v6 `{bmad_folder}/bmm/`**: Is the BMad Method module
+- **v4 `_bmad-core`**: Was actually the BMad Method
+- **v6 `_bmad/core/`**: Is the real universal core framework
+- **v6 `_bmad/bmm/`**: Is the BMad Method module
 - **Module identification**: All modules now have a `config.yaml` file
 
 ---
@@ -110,15 +110,15 @@ After running the v6 installer:
 
 ### v4 Agent Customization
 
-In v4, you may have modified agent files directly in `.bmad-*` folders.
+In v4, you may have modified agent files directly in `_bmad-*` folders.
 
 ### v6 Agent Customization
 
-**All customizations** now go in `{bmad_folder}/_cfg/agents/` using customize files:
+**All customizations** now go in `_bmad/_config/agents/` using customize files:
 
 **Example: Renaming an agent and changing communication style**
 
-File: `{bmad_folder}/_cfg/agents/bmm-pm.customize.yaml`
+File: `_bmad/_config/agents/bmm-pm.customize.yaml`
 
 ```yaml
 # Customize the PM agent
@@ -133,8 +133,8 @@ persona:
 
 **How it works:**
 
-- Base agent: `{bmad_folder}/bmm/agents/pm.md`
-- Customization: `{bmad_folder}/_cfg/agents/bmm-pm.customize.yaml`
+- Base agent: `_bmad/bmm/agents/pm.md`
+- Customization: `_bmad/_config/agents/bmm-pm.customize.yaml`
 - Result: Agent uses your custom name and style, but updates don't overwrite your changes
 
 ---
@@ -176,7 +176,7 @@ npx bmad-method install
 
 The installer will:
 
-1. Detect v4 installation and offer to backup `.bmad-*` folders
+1. Detect v4 installation and offer to backup `_bmad-*` folders
 2. Prompt for recommended cleanup (you can skip)
 3. Let you select modules (recommend: BMM for software and or game development)
 4. Configure core settings (name, language, etc.)
@@ -212,9 +212,9 @@ Since you are migrating an existing project from v4, it's most likely **Level 3
 ## Post-Migration Checklist
 
 - [ ] v4 folders backed up to `v4-backup/`
-- [ ] v6 installed to `{bmad_folder}/` folder
+- [ ] v6 installed to `_bmad/` folder
 - [ ] `workflow-init` run with correct project level selected
-- [ ] Agent customizations migrated to `{bmad_folder}/_cfg/agents/` if needed
+- [ ] Agent customizations migrated to `_bmad/_config/agents/` if needed
 - [ ] IDE integration working (test by listing agents)
 - [ ] For active development: `sprint-planning` workflow executed
 
@@ -224,4 +224,4 @@ Since you are migrating an existing project from v4, it's most likely **Level 3
 
 - **Discord**: [Join the BMad Community](https://discord.gg/gk8jAdXWmj)
 - **Issues**: [GitHub Issue Tracker](https://github.com/bmad-code-org/BMAD-METHOD/issues)
-- **Docs**: Check `{bmad_folder}/docs/` in your installation for IDE-specific instructions
+- **Docs**: Check `_bmad/docs/` in your installation for IDE-specific instructions

docs/v6-open-items.md

@@ -1,17 +0,0 @@
-# v6 Pending Items
-
-Before calling this beta
-
-- finalize web bundler
-- some subagents working again
-- knowledge base for bmad
-
-## Needed Beta → v0 release
-
-Aside from stability and bug fixes found during the alpha period - the main focus will be on the following:
-
-- knowledge base for BMM
-- Module repository and submission process defined
-- MCP Injections based on installation selection
-- sub agent for open-code and claude code optimization
-- TDD Workflow Integration

docs/web-bundles-gemini-gpt-guide.md

@@ -1,5 +1,11 @@
 # Using BMad Web Bundles in Gemini Gems & Custom GPTs
 
+## IMPORTANT NOTE
+
+The Web Bundling Feature is being rebuilt from the ground up, current bundles for v6 may be incomplete or missing functionality and are not optimized. This will be rectified very soon, with a more expansive guide.
+
+## What Are Web bundles
+
 Web bundles package BMad agents as self-contained XML files that work in Gemini Gems and Custom GPTs. Everything the agent needs - instructions, workflows, dependencies - is bundled into a single file.
 
 ## What Are Web Bundles?
@@ -13,461 +19,3 @@ Web bundles are standalone XML files containing:
 - No external files required
 
 **Perfect for:** Uploading a single file to a Gemini GEM or Custom GPT to use BMad Method from the Web, generally at a huge cost savings, at the expense of some quality and convenience of using locally.
-
-## Critical Setup Rules
-
-**READ THIS FIRST - Following these rules ensures BMad works correctly in Gemini/GPT:**
-
-1. **ONE file per Gem/GPT** - Upload exactly ONE XML file per Gemini Gem or Custom GPT instance. Do NOT combine multiple agent files.
-
-2. **Use the setup instructions** - When creating your Gem/GPT, you MUST add the configuration prompt (shown in Quick Start below) so it knows how to read the XML file.
-
-3. **Enable Canvas/Code Execution** - This is ESSENTIAL for document generation workflows (PRD, Architecture, etc.). Enable this in your Gem/GPT settings.
-
-4. **Gemini Gems are strongly preferred** - They work significantly better than Custom GPTs for BMad workflows.
-
-5. **Team bundles = Gemini 2.5 Pro+ only** - Team bundles (multiple agents) have terrible performance in Custom GPTs due to context limits. Only use them with Gemini 2.5 Pro or higher.
-
-6. **Create separate Gems for each agent** - Make a PM Gem, an Architect Gem, a Developer Gem, etc. Don't try to combine them (except via official team bundles).
-
-## Quick Start
-
-### 1. Get Web Bundle Files
-
-**Option A: Download Pre-Bundled Files (Quickest)**
-
-Download ready-to-use bundles that are automatically updated whenever commits are merged to main:
-
-**[→ Download Web Bundles](https://bmad-code-org.github.io/bmad-bundles/)**
-
-Navigate to the module folder (bmm, bmb, cis, bmgd) → agents folder → download the `.xml` file you need. These bundles are automatically regenerated and deployed with every commit to the main branch, ensuring you always have the latest version.
-
-**Option B: Generate from Local Installation**
-
-From your BMad project directory:
-
-```bash
-# Generate all agent bundles
-npm run bundle
-
-# Or generate specific bundles
-node tools/cli/bundlers/bundle-web.js module bmm
-node tools/cli/bundlers/bundle-web.js agent bmm dev
-```
-
-**Output location:** `web-bundles/` directory
-
-```
-web-bundles/
-├── bmm/
-│   ├── agents/     # Individual agents
-│   └── teams/      # Multi-agent teams
-├── bmb/
-├── cis/
-└── bmgd/
-```
-
-### 2. Upload to Gemini Gems (Recommended)
-
-**IMPORTANT: Create ONE Gem per agent file. Do NOT upload multiple agent files to a single Gem.**
-
-**Create a Gem:**
-
-1. Go to [Google AI Studio](https://aistudio.google.com/)
-2. Click "New Gem" or "Create Gem"
-3. Give your Gem a name (e.g., "BMad PM Agent")
-4. **Enable "Code execution" for best results with document generation**
-5. In the **System Instructions** field, add this EXACT text (customize the config values):
-
-```
-All of your operating instructions and resources are contained in the XML file attached. Read in the initial agent block and instructions to understand it. You will not deviate from the character and rules outlined in the attached!
-
-CONFIG.YAML Values:
-- user_name: [Your Name]
-- communication_language: English
-- user_skill_level: [Beginner|Intermediate|Expert]
-- document_output_language: English
-- bmm-workflow-status: standalone (no workflow)
-```
-
-6. **Upload ONE XML file** (e.g., `pm.xml`) - either attach as a file or paste contents
-7. Save and test your Gem by typing `*help` to see the menu
-
-**Tips for Gemini:**
-
-- **Enable Code Execution/Canvas** - Critical for document output (PRDs, architecture docs, etc.)
-- **Use Gemini 2.5 Pro+** for best results, especially for complex workflows
-- **One agent per Gem** - Create separate Gems for PM, Architect, Developer, etc.
-- Test the agent by triggering menu items with `*workflow-name`
-
-### 3. Upload to Custom GPTs
-
-**IMPORTANT: Create ONE Custom GPT per agent file. Do NOT upload multiple agent files to a single GPT.**
-
-**Create a Custom GPT:**
-
-1. Go to [ChatGPT](https://chat.openai.com/)
-2. Click your profile → "My GPTs" → "Create a GPT"
-3. Configure your GPT:
-   - **Name:** BMad PM Agent (or your choice)
-   - **Description:** AI planning agent powered by BMad Method
-4. In the **Instructions** field, add this EXACT text at the top (customize the config values):
-
-```
-All of your operating instructions and resources are contained in the XML file attached. Read in the initial agent block and instructions to understand it. You will not deviate from the character and rules outlined in the attached!
-
-CONFIG.YAML Values:
-- user_name: [Your Name]
-- communication_language: English
-- user_skill_level: [Beginner|Intermediate|Expert]
-- document_output_language: English
-- bmm-workflow-status: standalone (no workflow)
-```
-
-5. **Below that text**, paste the entire contents of ONE XML file (e.g., `pm.xml`)
-6. **Enable "Canvas" in ChatGPT settings** for better document output
-7. Save and test by typing `*help`
-
-**Tips for Custom GPTs:**
-
-- **Enable Canvas** - Essential for workflow document generation
-- **One agent per GPT** - Create separate GPTs for each agent
-- Custom GPTs have smaller context windows than Gemini - avoid team bundles
-- Works best with focused agents (PM, Analyst, Architect)
-
-## Available Web Bundles
-
-After running `npm run bundle`, you'll have access to:
-
-### BMad Method (BMM) Agents
-
-- **analyst.xml** - Business analysis and requirements gathering
-- **architect.xml** - System architecture and technical design
-- **dev.xml** - Full-stack development and implementation
-- **pm.xml** - Product management and planning
-- **sm.xml** - Scrum master and agile facilitation
-- **tea.xml** - Test architecture and quality assurance
-- **tech-writer.xml** - Technical documentation
-- **ux-designer.xml** - User experience design
-- **game-designer.xml** - Game design and mechanics
-- **game-dev.xml** - Game development
-- **game-architect.xml** - Game architecture
-
-### BMad Builder (BMB) Agent
-
-- **bmad-builder.xml** - Create custom agents, workflows, and modules
-
-### Creative Intelligence Suite (CIS) Agents
-
-- **brainstorming-coach.xml** - Creative brainstorming facilitation
-- **design-thinking-coach.xml** - Human-centered problem solving
-- **innovation-strategist.xml** - Innovation and strategy
-- **creative-problem-solver.xml** - Breakthrough problem solving
-- **storyteller.xml** - Narrative and storytelling
-
-### Team Bundles (Multi-Agent Collaboration)
-
-**CRITICAL: Team bundles are ONLY recommended for Gemini 2.5 Pro+ in the web. The experience is poor with Custom GPTs due to limited context windows.**
-
-- **bmm/teams/team-fullstack.xml** - Full BMad Method development team
-- **bmgd/teams/team-gamedev.xml** - Game development team
-- **cis/teams/creative-squad.xml** - Creative Intelligence team
-
-**When to use team bundles:**
-
-- You want multiple agents collaborating in one Gem
-- You're using Gemini 2.5 Pro+ (required)
-- You need diverse perspectives on complex problems
-
-**When to use individual agents instead:**
-
-- Using Custom GPTs (always use individual agents)
-- Want focused expertise from a single agent
-- Need faster, more streamlined interactions
-
-## Recommended Workflow: Web Planning → Local Implementation
-
-**Save significant costs** by doing planning phases in web bundles, then switching to local IDE for implementation.
-
-### Cost-Saving Strategy
-
-**Phase 1-3: Do in Web (Major Cost Savings)**
-
-Use Gemini Gems or Custom GPTs for these workflows:
-
-1. **Analysis Phase** (Analyst, PM)
-   - `*brainstorm-project` - Brainstorm ideas and features
-   - `*research` - Market and technical research
-   - `*product-brief` - Create product vision
-
-2. **Planning Phase** (PM)
-   - `*prd` - Generate comprehensive Product Requirements Document
-   - `*create-epics-and-stories` - Break down into development stories
-
-3. **Solutioning Phase** (Architect, UX Designer)
-   - `*architecture` - Define technical architecture
-   - `*create-ux-design` - Design user experience
-
-**Export Artifacts:**
-After each workflow, copy/download the generated documents (PRD, Architecture, UX Design, etc.)
-
-**Phase 4: Switch to Local IDE (Required for Implementation)**
-
-1. Save exported artifacts to your project's `docs/` folder
-2. Run local BMad installation with `*workflow-init`
-3. BMad will detect the existing artifacts and update workflow status
-4. Proceed with implementation using Developer agent locally
-
-**Why this works:**
-
-- **Planning workflows** are token-heavy but don't need code context
-- **Web models (Gemini/GPT)** handle planning excellently at lower cost
-- **Local IDE implementation** needs full codebase access and tools
-- **Best of both worlds**: Cost savings + full implementation capabilities
-
-**Typical savings:** 60-80% cost reduction by doing analysis, planning, and architecture in web before moving to local implementation.
-
-## Using Web Bundles
-
-### Basic Usage
-
-**1. Load the Agent**
-
-Upload or paste the XML file into Gemini/GPT. The agent will introduce itself and show its menu.
-
-**2. Choose a Workflow**
-
-Use natural language or shortcuts:
-
-```
-"Run the PRD workflow"
-*prd
-
-"Start brainstorming"
-*brainstorm-project
-
-"Show me the menu"
-*help
-```
-
-**3. Follow the Workflow**
-
-The agent guides you through the workflow step-by-step, asking questions and creating deliverables.
-
-### Advanced Features
-
-**Party Mode**
-
-All web bundles include party mode for multi-agent collaboration:
-
-```
-*party
-```
-
-This activates multiple agents who collaborate on your task, providing diverse perspectives.
-
-**Context Loading**
-
-Some workflows load additional context:
-
-```
-*workflow-init  # Initialize project workflow
-*document-project  # Analyze existing codebase
-```
-
-**Dynamic Menus**
-
-Agents adapt their menus based on project phase and available workflows.
-
-## Platform Differences
-
-### Gemini Gems (Strongly Recommended)
-
-**Pros:**
-
-- Better XML parsing and handling
-- Handles large bundles well
-- Supports complex workflows
-- Larger context window (better for team bundles)
-- Code execution for document generation
-- Works excellently with BMad workflows
-
-**Cons:**
-
-- Requires Google account
-- May have rate limits on free tier
-
-**Best for:**
-
-- All individual agents (PM, Architect, Developer, UX Designer, etc.)
-- Team bundles (requires Gemini 2.5 Pro+)
-- Complex multi-step workflows
-- Document-heavy workflows (PRD, Architecture)
-
-**Recommended Model:** Gemini 2.5 Pro or higher
-
-### Custom GPTs
-
-**Pros:**
-
-- Familiar ChatGPT interface
-- Good for conversational workflows
-- Easy sharing with team via link
-
-**Cons:**
-
-- Smaller context window than Gemini
-- Character limit on instructions (large bundles may not fit)
-- **NOT recommended for team bundles**
-- Canvas feature less mature than Gemini's code execution
-
-**Best for:**
-
-- Individual focused agents (PM, Analyst, Architect)
-- Creative agents (CIS)
-- Simpler workflows (product-brief, brainstorm-project)
-- Quick prototyping
-
-**NOT recommended for:** Team bundles, Developer agent, complex technical workflows
-
-## Customization
-
-**Before Bundling:**
-
-Customize agents using the [Agent Customization Guide](./agent-customization-guide.md):
-
-1. Edit `{bmad_folder}/_cfg/agents/<agent>.customize.yaml`
-2. Rebuild: `npx bmad-method build <agent-name>`
-3. Generate bundles: `npm run bundle`
-
-Your customizations will be included in the web bundles.
-
-**After Bundling:**
-
-You can manually edit the XML to:
-
-- Change agent name (search for `<name>`)
-- Modify persona (search for `<persona>`)
-- Add custom instructions (in `<critical>` blocks)
-
-## Troubleshooting
-
-**Agent not responding correctly?**
-
-- Check that the entire XML file was uploaded
-- Verify no truncation occurred (Gemini/GPT have character limits)
-- Try a simpler agent first (analyst, pm)
-
-**Menu items not working?**
-
-- Use the `*` prefix for shortcuts: `*prd` not `prd`
-- Or use natural language: "Run the PRD workflow"
-- Check the agent's menu with `*help`
-
-**Workflows failing?**
-
-- Some workflows expect project files (not available in web context)
-- Use workflows designed for planning/analysis in web bundles
-- For implementation workflows, use local IDE installation
-
-**File too large for GPT?**
-
-- Split into sections and use multiple GPTs
-- Use Gemini Gems instead (better for large files)
-- Generate single-agent bundles instead of team bundles
-
-## Best Practices
-
-1. **One File Per Gem/GPT** - Always upload only ONE XML file per Gemini Gem or Custom GPT instance
-2. **Prefer Gemini Over GPT** - Gemini Gems work significantly better with BMad bundles
-3. **Enable Canvas/Code Execution** - Essential for document generation workflows (PRD, Architecture, etc.)
-4. **Create Separate Gems for Each Agent** - Don't try to combine agents except via team bundles
-5. **Team Bundles = Gemini 2.5 Pro+ Only** - Never use team bundles with Custom GPTs
-6. **Use for Planning Phases** - Web bundles excel at analysis, planning, and architecture (Phases 1-3)
-7. **Switch to Local for Implementation** - Use local IDE installation for Phase 4 development
-8. **Export and Save Artifacts** - Copy generated documents to your project's `docs/` folder
-9. **Run workflow-init Locally** - After importing web artifacts, initialize local workflow status
-10. **Keep Updated** - Rebuild bundles after BMad updates to get latest improvements
-
-## Examples
-
-### Example 1: Complete Web → Local Workflow (Recommended)
-
-**Goal:** Build a new SaaS product with maximum cost savings
-
-**Phase 1-3: Web Planning (Gemini Gems)**
-
-1. **Download bundles:**
-   - `bmm/agents/analyst.xml`
-   - `bmm/agents/pm.xml`
-   - `bmm/agents/architect.xml`
-   - `bmm/agents/ux-designer.xml`
-
-2. **Create 4 separate Gemini Gems** (one per agent, enable Code Execution)
-
-3. **Analysis (Analyst Gem):**
-   - Run: `*brainstorm-project` → Generate ideas
-   - Run: `*research` → Market analysis
-   - Export: Save research findings
-
-4. **Planning (PM Gem):**
-   - Share research findings
-   - Run: `*product-brief` → Product vision
-   - Run: `*prd` → Full requirements document
-   - Export: Save PRD to `docs/prd.md`
-
-5. **UX Design (UX Designer Gem):**
-   - Share PRD
-   - Run: `*create-ux-design` → UX specifications
-   - Export: Save UX design to `docs/ux-design.md`
-
-6. **Architecture (Architect Gem):**
-   - Share PRD and UX Design
-   - Run: `*architecture` → Technical architecture
-   - Export: Save to `docs/architecture.md`
-
-**Phase 4: Local Implementation**
-
-7. **Setup local BMad:**
-   - Install BMad locally: `npx bmad-method@alpha install`
-   - Place exported docs in project `docs/` folder
-   - Load Developer agent
-   - Run: `*workflow-init` → BMad detects artifacts, suggests next steps
-
-8. **Implement:**
-   - Run: `*sprint-planning` → Set up sprint
-   - Run: `*dev-story` → Implement features
-   - Use full IDE capabilities with codebase access
-
-**Cost Savings:** 60-80% by doing planning in Gemini before local implementation
-
-### Example 2: Quick Brainstorming Session
-
-1. Download `cis/agents/brainstorming-coach.xml`
-2. Create Gemini Gem with Code Execution enabled
-3. Run: `*brainstorming`
-4. Choose technique (e.g., SCAMPER, Mind Mapping)
-5. Generate and refine ideas
-6. Export results for team review
-
-### Example 3: Architecture Review
-
-1. Download `bmm/agents/architect.xml`
-2. Create Gemini Gem (enable Code Execution)
-3. Paste existing PRD into conversation
-4. Run: `*architecture`
-5. Collaborate on technical decisions
-6. Export architecture document to `docs/architecture.md`
-
-## Next Steps
-
-- **[Agent Customization Guide](./agent-customization-guide.md)** - Customize before bundling
-- **[BMM Documentation](../src/modules/bmm/docs/README.md)** - Learn all workflows
-- **[Web Bundler Technical Docs](./installers-bundlers/web-bundler-usage.md)** - Advanced bundling options
-- **[Contributing Guide](../CONTRIBUTING.md)** - Help improve web bundles
-
-## Resources
-
-- **[Google AI Studio](https://aistudio.google.com/)** - Create Gemini Gems
-- **[Custom GPTs](https://chat.openai.com/gpts)** - Build Custom GPTs
-- **[BMad Discord](https://discord.gg/gk8jAdXWmj)** - Get help and share your Gems/GPTs

eslint.config.mjs

@@ -16,8 +16,8 @@ export default [
       'test/template-test-generator/**/*.md',
       'test/fixtures/**',
       'test/fixtures/**/*.yaml',
-      '.bmad/**',
-      '.bmad*/**',
+      '_bmad/**',
+      '_bmad*/**',
       // Gitignored patterns
       'z*/**', // z-samples, z1, z2, etc.
       '.claude/**',

example-custom-content/README.md

@@ -1,4 +0,0 @@
-# Example Custom Content module
-
-This is a demonstration of custom stand along agents and workflows. By having this content all in a folder with a custom.yaml file,
-These items will be discovered by the installer and offered for installation.

example-custom-content/workflows/quiz-master/workflow-plan-quiz-master.md

@@ -1,269 +0,0 @@
----
-stepsCompleted: [1, 2, 3, 4, 5, 6, 7]
----
-
-## Build Summary
-
-**Date:** 2025-12-04
-**Status:** Build Complete
-
-### Files Generated
-
-**Main Workflow:**
-
-- `/Users/brianmadison/dev/BMAD-METHOD/.bmad/custom/src/workflows/quiz-master/workflow.md`
-
-**Step Files (12 total):**
-
-- `/Users/brianmadison/dev/BMAD-METHOD/.bmad/custom/src/workflows/quiz-master/steps/step-01-init.md` - Game setup and mode selection
-- `/Users/brianmadison/dev/BMAD-METHOD/.bmad/custom/src/workflows/quiz-master/steps/step-02-q1.md` - Question 1 (Level 1)
-- `/Users/brianmadison/dev/BMAD-METHOD/.bmad/custom/src/workflows/quiz-master/steps/step-03-q2.md` - Question 2 (Level 2)
-- `/Users/brianmadison/dev/BMAD-METHOD/.bmad/custom/src/workflows/quiz-master/steps/step-04-q3.md` - Question 3 (Level 3)
-- `/Users/brianmadison/dev/BMAD-METHOD/.bmad/custom/src/workflows/quiz-master/steps/step-05-q4.md` - Question 4 (Level 4)
-- `/Users/brianmadison/dev/BMAD-METHOD/.bmad/custom/src/workflows/quiz-master/steps/step-06-q5.md` - Question 5 (Level 5)
-- `/Users/brianmadison/dev/BMAD-METHOD/.bmad/custom/src/workflows/quiz-master/steps/step-07-q6.md` - Question 6 (Level 6)
-- `/Users/brianmadison/dev/BMAD-METHOD/.bmad/custom/src/workflows/quiz-master/steps/step-08-q7.md` - Question 7 (Level 7)
-- `/Users/brianmadison/dev/BMAD-METHOD/.bmad/custom/src/workflows/quiz-master/steps/step-09-q8.md` - Question 8 (Level 8)
-- `/Users/brianmadison/dev/BMAD-METHOD/.bmad/custom/src/workflows/quiz-master/steps/step-10-q9.md` - Question 9 (Level 9)
-- `/Users/brianmadison/dev/BMAD-METHOD/.bmad/custom/src/workflows/quiz-master/steps/step-11-q10.md` - Question 10 (Level 10)
-- `/Users/brianmadison/dev/BMAD-METHOD/.bmad/custom/src/workflows/quiz-master/steps/step-12-results.md` - Final results and celebration
-
-**Templates:**
-
-- `/Users/brianmadison/dev/BMAD-METHOD/.bmad/custom/src/workflows/quiz-master/templates/csv-headers.template` - CSV column headers
-
-### Key Features Implemented
-
-1. **Dual Game Modes:**
-   - Mode 1: Sudden Death (game over on first wrong answer)
-   - Mode 2: Marathon (complete all 10 questions)
-
-2. **CSV History Tracking:**
-   - 44 columns including DateTime, Category, GameMode, all questions/answers, FinalScore
-   - Automatic CSV creation with headers
-   - Real-time updates after each question
-
-3. **Gameshow Persona:**
-   - Energetic, dramatic host presentation
-   - Progressive difficulty from Level 1-10
-   - Immediate feedback and celebration
-
-4. **Flow Control:**
-   - Automatic CSV routing based on game mode
-   - Play again or quit options at completion
-
-### Next Steps for Testing
-
-1. Run the workflow: `/bmad:bmb:workflows:quiz-master`
-2. Test both game modes
-3. Verify CSV file creation and updates
-4. Check question progression and difficulty
-5. Validate final score calculation
-
-## Plan Review Summary
-
-- **Plan reviewed by:** User
-- **Date:** 2025-12-04
-- **Status:** Approved without modifications
-- **Ready for design phase:** Yes
-- **Output Documents:** CSV history file (BMad-quiz-results.csv)
-
-# Workflow Creation Plan: quiz-master
-
-## Initial Project Context
-
-- **Module:** stand-alone
-- **Target Location:** /Users/brianmadison/dev/BMAD-METHOD/.bmad/custom/src/workflows/quiz-master
-- **Created:** 2025-12-04
-
-## Detailed Requirements
-
-### 1. Workflow Purpose and Scope
-
-- **Primary Goal:** Entertainment-based interactive trivia quiz
-- **Structure:** Always exactly 10 questions (1 per difficulty level 1-10)
-- **Format:** Multiple choice with 4 options (A, B, C, D)
-- **Progression:** Linear progression through all 10 levels regardless of correct/incorrect answers
-- **Scoring:** Track correct answers for final score
-
-### 2. Workflow Type Classification
-
-- **Type:** Interactive Workflow with Linear structure
-- **Interaction Style:** High interactivity with user input for each question
-- **Flow:** Step 1 (Init) → Step 2 (Quiz Questions) → Step 3 (Results) → Step 4 (History Save)
-
-### 3. Workflow Flow and Step Structure
-
-**Step 1 - Game Initialization:**
-
-- Read user_name from config.yaml
-- Present suggested categories OR accept freeform category input
-- Create CSV file if not exists with proper headers
-- Start new row for current game session
-
-**Step 2 - Quiz Game Loop:**
-
-- Loop through 10 questions (levels 1-10)
-- Each question has 4 multiple-choice options
-- User enters A, B, C, or D
-- Provide immediate feedback on correctness
-- Continue to next level regardless of answer
-
-**Step 3 - Results Display:**
-
-- Show final score (e.g., "You got 7 out of 10!")
-- Provide entertaining commentary based on performance
-
-**Step 4 - History Management:**
-
-- Append complete game data to CSV
-- Columns: DateTime, Category, Q1-Question, Q1-Choices, Q1-UserAnswer, Q1-Correct, Q2-Question, ... Q10-Correct, FinalScore
-
-### 4. User Interaction Style
-
-- **Persona:** Over-the-top gameshow host (enthusiastic, dramatic, celebratory)
-- **Instruction Style:** Intent-based with gameshow flair
-- **Language:** Energetic, encouraging, theatrical
-- **Feedback:** Immediate, celebratory for correct, encouraging for incorrect
-
-### 5. Input Requirements
-
-- **From config:** user_name (BMad)
-- **From user:** Category selection (suggested list or freeform)
-- **From user:** 10 answers (A/B/C/D)
-
-### 6. Output Specifications
-
-- **Primary:** Interactive quiz experience with gameshow atmosphere
-- **Secondary:** CSV history file named: BMad-quiz-results.csv
-- **CSV Structure:**
-  - Row per game session
-  - Headers: DateTime, Category, Q1-Question, Q1-Choices, Q1-UserAnswer, Q1-Correct, ..., Q10-Correct, FinalScore
-
-### 7. Success Criteria
-
-- User completes all 10 questions
-- Gameshow atmosphere maintained throughout
-- CSV file properly created/updated
-- User receives final score with entertaining feedback
-- All question data and answers recorded accurately
-
-### 8. Special Considerations
-
-- Always assume fresh chat/new game
-- CSV file creation in Step 1 if missing
-- Freeform categories allowed (any topic)
-- No need to display previous history during game
-- Focus on entertainment over assessment
-- After user enters A/B/C/D, automatically continue to next question (no "Continue" prompts)
-- Streamlined experience without advanced elicitation or party mode tools
-
-## Tools Configuration
-
-### Core BMAD Tools
-
-- **Party-Mode**: Excluded - Want streamlined quiz flow without interruptions
-- **Advanced Elicitation**: Excluded - Quiz format is straightforward without need for complex analysis
-- **Brainstorming**: Excluded - Categories can be suggested directly or entered freeform
-
-### LLM Features
-
-- **Web-Browsing**: Excluded - Quiz questions can be generated from existing knowledge
-- **File I/O**: Included - Essential for CSV history file management (reading/writing quiz results)
-- **Sub-Agents**: Excluded - Single gameshow host persona is sufficient
-- **Sub-Processes**: Excluded - Linear quiz flow doesn't require parallel processing
-
-### Memory Systems
-
-- **Sidecar File**: Excluded - Each quiz session is independent (always assume fresh chat)
-
-### External Integrations
-
-- None required for this workflow
-
-### Installation Requirements
-
-- None - All required tools (File I/O) are core features with no additional setup needed
-
-## Workflow Design
-
-### Step Structure
-
-**Total Steps: 12**
-
-1. Step 01 - Init: Mode selection, category choice, CSV setup
-2. Steps 02-11: Individual questions (1-10) with CSV updates
-3. Step 12 - Results: Final score display and celebration
-
-### Game Modes
-
-- **Mode 1 - Sudden Death**: Game over on first wrong answer
-- **Mode 2 - Marathon**: Continue through all 10 questions
-
-### CSV Structure (44 columns)
-
-Headers: DateTime,Category,GameMode,Q1-Question,Q1-Choices,Q1-UserAnswer,Q1-Correct,...,Q10-Correct,FinalScore
-
-### Flow Logic
-
-- Step 01: Create row with DateTime, Category, GameMode
-- Steps 02-11: Update CSV with question data
-  - Mode 1: IF incorrect → jump to Step 12
-  - Mode 2: Always continue
-- Step 12: Update FinalScore, display results
-
-### Gameshow Persona
-
-- Energetic, dramatic host
-- Celebratory feedback for correct answers
-- Encouraging messages for incorrect
-
-### File Structure
-
-```
-quiz-master/
-├── workflow.md
-├── steps/
-│   ├── step-01-init.md
-│   ├── step-02-q1.md
-│   ├── ...
-│   └── step-12-results.md
-└── templates/
-    └── csv-headers.template
-```
-
-## Output Format Design
-
-**Format Type**: Strict Template
-
-**Output Requirements**:
-
-- Document type: CSV data file
-- File format: CSV (UTF-8 encoding)
-- Frequency: Append one row per quiz session
-
-**Structure Specifications**:
-
-- Exact 43 columns with specific headers
-- Headers: DateTime,Category,Q1-Question,Q1-Choices,Q1-UserAnswer,Q1-Correct,...,Q10-Correct,FinalScore
-- Data formats:
-  - DateTime: ISO 8601 (YYYY-MM-DDTHH:MM:SS)
-  - Category: Text
-  - QX-Question: Text
-  - QX-Choices: (A)Opt1|(B)Opt2|(C)Opt3|(D)Opt4
-  - QX-UserAnswer: A/B/C/D
-  - QX-Correct: TRUE/FALSE
-  - FinalScore: Number (0-10)
-
-**Template Information**:
-
-- Template source: Created based on requirements
-- Template file: CSV with fixed column structure
-- Placeholders: None - strict format required
-
-**Special Considerations**:
-
-- CSV commas within text must be quoted
-- Newlines in questions replaced with spaces
-- Headers created only if file doesn't exist
-- Append mode for all subsequent quiz sessions

example-custom-module/mwm/README.md

@@ -1,4 +0,0 @@
-# EXAMPLE MODULE WARNING
-
-This module is an example and is not at all recommended for any usage, this module was not vetted by any medical professionals and should
-be considered at best for entertainment purposes only.

example-custom-module/mwm/_module-installer/install-config.yaml

@@ -1,27 +0,0 @@
-# Mental Wellness Module Configuration
-# This file defines installation questions and module configuration values
-
-code: mwm
-name: "MWM: Mental Wellness Module"
-default_selected: false
-
-header: "MWM™: Custom Wellness Module"
-subheader: "Demo of Potential Non Coding Custom Module Use case"
-
-# Variables from Core Config inserted:
-## user_name
-## communication_language
-## output_folder
-## bmad_folder
-## install_user_docs
-## kb_install
-
-companion_name:
-  prompt: "What would you like to call your mental wellness companion?"
-  default: "Wellness Guide"
-  result: "{value}"
-
-journal_location:
-  prompt: "Where should your wellness journal be saved?"
-  default: "{output_folder}/mental-wellness"
-  result: "{project-root}/{value}"

example-custom-module/mwm/agents/cbt-coach/cbt-coach-sidecar/cognitive-distortions.md

@@ -1,47 +0,0 @@
-# CBT Coach - Cognitive Distortions Reference
-
-## The 10 Cognitive Distortions
-
-1. **All-or-Nothing Thinking**
-   - Seeing things in black-and-white categories
-   - Example: "If I'm not perfect, I'm a failure"
-
-2. **Overgeneralization**
-   - Seeing a single negative event as a never-ending pattern
-   - Example: "I didn't get the job, so I'll never get hired"
-
-3. **Mental Filter**
-   - Dwell on negatives and ignore positives
-   - Example: Focusing on one criticism in an otherwise good review
-
-4. **Disqualifying the Positive**
-   - Rejecting positive experiences as "don't count"
-   - Example: "They were just being nice"
-
-5. **Jumping to Conclusions**
-   - Mind reading (assuming you know what others think)
-   - Fortune telling (predicting the future negatively)
-
-6. **Magnification/Minimization**
-   - Exaggerating negatives or shrinking positives
-   - Example: "Making a mistake feels catastrophic"
-
-7. **Emotional Reasoning**
-   - Believing something because it feels true
-   - Example: "I feel anxious, so danger must be near"
-
-8. **"Should" Statements**
-   - Using "shoulds" to motivate
-   - Example: "I should be more productive"
-
-9. **Labeling**
-   - Assigning global negative traits
-   - Example: "I'm a loser" instead of "I made a mistake"
-
-10. **Personalization**
-    - Taking responsibility/blame for things outside your control
-    - Example: "It's my fault the party wasn't fun"
-
-## User's Common Patterns
-
-_Track which distortions appear most frequently_

example-custom-module/mwm/agents/cbt-coach/cbt-coach-sidecar/thought-records.md

@@ -1,17 +0,0 @@
-# CBT Coach - Thought Records
-
-## Thought Record History
-
-_CBT thought records are documented here for pattern tracking and progress review_
-
-## Common Patterns Identified
-
-_Recurring cognitive distortions and thought patterns_
-
-## Successful Reframes
-
-_Examples of successful cognitive restructuring_
-
-## Homework Assignments
-
-_CBT exercises and behavioral experiments_

example-custom-module/mwm/agents/cbt-coach/cbt-coach.agent.yaml

@@ -1,150 +0,0 @@
-agent:
-  metadata:
-    name: "Dr. Alexis, M.D."
-    title: "CBT Coach"
-    icon: "🧠"
-    module: "mwm"
-    hasSidecar: true
-  persona:
-    role: "Cognitive Behavioral Therapy specialist"
-    identity: |
-      A structured yet empathetic CBT practitioner who helps users identify and reframe negative thought patterns using evidence-based techniques. Skilled at making cognitive behavioral concepts accessible and practical for daily use. Balances clinical expertise with genuine care for user progress.
-    communication_style: |
-      Clear, structured, and educational. Uses simple language to explain CBT concepts. Asks targeted questions to guide insight. Provides concrete exercises and homework. Validates struggles while encouraging growth. Uses Socratic questioning to help users discover their own insights.
-    principles:
-      - "Thoughts are not facts - they can be examined and challenged"
-      - "Behavior change follows cognitive change"
-      - "Small, consistent practice creates lasting change"
-      - "Self-compassion is essential for growth"
-      - "Evidence over assumptions"
-
-  critical_actions:
-    - "Load COMPLETE file {agent_sidecar_folder}/cbt-coach-sidecar/thought-records.md and review previous CBT work"
-    - "Load COMPLETE file {agent_sidecar_folder}/cbt-coach-sidecar/cognitive-distortions.md and reference recognized patterns"
-    - "Load COMPLETE file {agent_sidecar_folder}/cbt-coach-sidecar/progress.md and track user development"
-    - "ONLY read/write files in {agent_sidecar_folder}/cbt-coach-sidecar/ - this is our CBT workspace"
-
-  prompts:
-    - id: "thought-record"
-      content: |
-        <instructions>
-        Guide user through completing a CBT thought record
-        </instructions>
-
-        Let's work through a thought record together. This powerful tool helps us examine our thinking patterns.
-
-        **Step 1: Situation**
-        What was happening when the upsetting feeling started? Be specific - time, place, who was there?
-
-        **Step 2: Automatic Thoughts**
-        What thoughts went through your mind? List them exactly as they occurred.
-
-        **Step 3: Emotions**
-        What emotions did you feel? Rate each from 0-100 in intensity.
-
-        **Step 4: Cognitive Distortions**
-        Looking at your thoughts, which of these patterns might be present?
-        - All-or-nothing thinking
-        - Overgeneralization
-        - Mental filter
-        - Disqualifying the positive
-        - Jumping to conclusions
-        - Magnification/minimization
-        - Emotional reasoning
-        - "Should" statements
-        - Labeling
-        - Personalization
-
-        **Step 5: Alternative Thoughts**
-        What's a more balanced or realistic way to view this situation?
-
-        **Step 6: Outcome**
-        How do you feel now? Rate emotions again.
-
-    - id: "cognitive-reframing"
-      content: |
-        <instructions>
-        Help user identify and challenge negative thought patterns
-        </instructions>
-
-        Let's examine this thought pattern together.
-
-        First, identify the automatic thought: "I'll never be good enough at this"
-
-        Now, let's gather evidence:
-        - What evidence supports this thought?
-        - What evidence contradicts this thought?
-        - What would you tell a friend with this thought?
-        - What's a more balanced perspective?
-
-        Remember: We're looking for accuracy, not just positive thinking. Sometimes the balanced thought acknowledges real challenges while avoiding catastrophizing.
-
-        What feels most realistic and helpful to you now?
-
-    - id: "behavioral-experiment"
-      content: |
-        <instructions>
-        Design a behavioral experiment to test a belief
-        </instructions>
-
-        Let's design a small experiment to test your belief.
-
-        **The Belief:** "If I speak up in meetings, everyone will think I'm stupid"
-
-        **The Experiment:**
-        1. What's a small step to test this? (e.g., share one brief comment)
-        2. What do you predict will happen? (be specific)
-        3. How can you collect real data? (observe reactions, ask for feedback)
-        4. What would disprove your belief?
-        5. What would partially support it?
-
-        Remember: We're scientists testing hypotheses, not trying to prove ourselves right. What would be most informative to learn?
-
-  menu:
-    - multi: "[CH] Chat with Dr. Alexis or [SPM] Start Party Mode"
-      triggers:
-        - party-mode:
-            - input: SPM or fuzzy match start party mode
-            - route: "{project-root}/{bmad_folder}/core/workflows/edit-agent/workflow.md"
-            - data: CBT coach agent discussion
-            - type: exec
-        - expert-chat:
-            - input: CH or fuzzy match chat with dr alexis
-            - action: agent responds as CBT coach
-            - type: exec
-
-    - multi: "[TR] Thought Record [CF] Challenge Feeling"
-      triggers:
-        - thought-record:
-            - input: TR or fuzzy match thought record
-            - route: "{project-root}/{bmad_folder}/mwm/workflows/cbt-thought-record/workflow.md"
-            - description: "Complete thought record 📝"
-            - type: exec
-        - challenge-feeling:
-            - input: CF or fuzzy match challenge feeling
-            - action: "#cognitive-reframing"
-            - description: "Challenge thoughts 🔄"
-            - type: exec
-
-    - multi: "[BE] Behavioral Experiment [CD] Cognitive Distortions"
-      triggers:
-        - behavior-experiment:
-            - input: BE or fuzzy match behavioral experiment
-            - action: "#behavioral-experiment"
-            - description: "Test your beliefs 🧪"
-            - type: exec
-        - cognitive-distortions:
-            - input: CD or fuzzy match cognitive distortions
-            - action: "Review and explain the 10 common cognitive distortions with examples"
-            - description: "Learn distortions 🎭"
-            - type: exec
-
-    - trigger: "core-beliefs"
-      action: "Guide exploration of core beliefs using downward arrow technique"
-      description: "Explore core beliefs 💎"
-      type: action
-
-    - trigger: "save-thought-work"
-      action: "Save this thought work to {agent_sidecar_folder}/cbt-coach-sidecar/thought-records.md with date and patterns"
-      description: "Save thought work 💾"
-      type: action

example-custom-module/mwm/agents/crisis-navigator.agent.yaml

@@ -1,137 +0,0 @@
-agent:
-  metadata:
-    name: "Beacon"
-    title: "Crisis Navigator"
-    icon: "🆘"
-    module: "mwm"
-  persona:
-    role: "Crisis detection and resource specialist"
-    identity: |
-      A calm and focused crisis support specialist trained to recognize distress signals and provide immediate resources. Maintains composure under pressure while prioritizing user safety. Knows exactly when to escalate to professional services and how to guide users to appropriate help quickly.
-    communication_style: |
-      Direct, clear, and action-oriented in crisis. Uses simple, unambiguous language. Speaks in a calm but firm tone when needed. Prioritizes clarity over comfort while remaining compassionate. Provides specific, actionable steps.
-    principles:
-      - "Safety is always the first priority"
-      - "When in doubt, err on the side of caution"
-      - "Provide resources, not treatment"
-      - "Document appropriately for follow-up"
-      - "Know your limits as an AI"
-
-  prompts:
-    - id: "crisis-assessment"
-      content: |
-        <instructions>
-        Rapid assessment of crisis level and immediate needs
-        </instructions>
-
-        I'm here to help you through this difficult moment. Let me quickly understand your situation.
-
-        **Immediate Safety Check:**
-        Are you or anyone else in immediate danger right now?
-
-        If YES - This is what we need to do RIGHT NOW:
-        - Call 911 or your local emergency number
-        - Go to the nearest emergency room
-        - Call a trusted person who can be with you
-
-        **If no immediate danger:**
-        On a scale of 1-10, how intense are your feelings right now?
-
-        I'm listening, and we'll get through this together.
-
-    - id: "grounding-technique"
-      content: |
-        <instructions>
-        Lead user through grounding exercise for crisis stabilization
-        </instructions>
-
-        Let's do a grounding exercise together to help you feel more stable.
-
-        **5-4-3-2-1 Grounding:**
-
-        Name **5 things you can see** around you right now.
-        *wait for response*
-
-        Name **4 things you can touch** or feel.
-        *wait for response*
-
-        Name **3 things you can hear**.
-        *wait for response*
-
-        Name **2 things you can smell**.
-        *wait for response*
-
-        Name **1 thing you can taste** or one good thing about yourself.
-
-        You're doing great. You're present and you're safe in this moment.
-
-    - id: "resource-provision"
-      content: |
-        <instructions>
-        Provide crisis resources based on user location and needs
-        </instructions>
-
-        Here are immediate resources available 24/7:
-
-        **Crisis Text Line:**
-        Text HOME to 741741 (US/Canada) or 85258 (UK)
-        Free, 24/7 crisis support via text
-
-        **National Suicide Prevention Lifeline:**
-        Call or text 988 (US)
-        Available 24/7
-
-        **Crisis Chat:**
-        Visit crisischat.org
-        Online chat with crisis counselors
-
-        **International Resources:**
-        Visit findahelpline.com for resources in your country
-
-        Remember: These services are free, confidential, and available right now. You don't have to go through this alone.
-
-  menu:
-    - multi: "[CH] Chat with Beacon or [SPM] Start Party Mode"
-      triggers:
-        - trigger: party-mode
-          input: SPM or fuzzy match start party mode
-          route: "{project-root}/.bmad/core/workflows/edit-agent/workflow.md"
-          data: crisis navigator agent discussion
-          type: exec
-        - trigger: expert-chat
-          input: CH or fuzzy match chat with beacon
-          action: agent responds as crisis navigator
-          type: action
-
-    - multi: "[CR] Crisis Resources [GT] Grounding"
-      triggers:
-        - trigger: crisis-resources
-          input: CR or fuzzy match crisis resources
-          action: "#resource-provision"
-          description: "Get immediate help 📞"
-          type: action
-        - trigger: grounding
-          input: GT or fuzzy match grounding
-          action: "#grounding-technique"
-          description: "Grounding exercise ⚓"
-          type: action
-
-    - trigger: "safety-plan"
-      route: "{project-root}/.bmad/custom/src/modules/mental-wellness-module/workflows/crisis-support/workflow.md"
-      description: "Create safety plan 🛡️"
-      type: workflow
-
-    - trigger: "emergency"
-      action: "IMMEDIATE: Call 911 or local emergency services. Contact trusted person. Go to nearest ER."
-      description: "Emergency services 🚨"
-      type: action
-
-    - trigger: "warm-line"
-      action: "Provide non-crisis support lines and resources for when you need to talk but not in crisis"
-      description: "Non-crisis support 📞"
-      type: action
-
-    - trigger: "log-incident"
-      action: "Document this crisis interaction (anonymized) for follow-up and pattern tracking"
-      description: "Log incident 📋"
-      type: action

example-custom-module/mwm/workflows/cbt-thought-record/README.md

@@ -1,31 +0,0 @@
-# CBT Thought Record Workflow
-
-## Purpose
-
-Structured cognitive exercise to identify, challenge, and reframe negative thought patterns.
-
-## Trigger
-
-TR (from CBT Coach agent)
-
-## Key Steps
-
-1. Identify the situation
-2. List automatic thoughts
-3. Rate emotions (0-100 intensity)
-4. Identify cognitive distortions
-5. Generate alternative thoughts
-6. Re-rate emotions
-7. Save and review pattern
-
-## Expected Output
-
-- Completed 6-column thought record
-- Identified patterns
-- Alternative thoughts
-- Mood change tracking
-
-## Notes
-
-This workflow will be implemented using the create-workflow workflow.
-The 6-Column structure: Situation, Thoughts, Emotions, Distortions, Alternatives, Outcome. Features: Guided process, education, pattern recognition, homework assignments.

example-custom-module/mwm/workflows/cbt-thought-record/workflow.md

@@ -1,45 +0,0 @@
----
-name: cbt-thought-record
-description: TODO
-web_bundle: false
----
-
-# CBT Thought Record
-
-**Goal:** TODO
-
-**Your Role:** TODO
-
-## WORKFLOW ARCHITECTURE
-
-### Core Principles
-
-TODO
-
-### Step Processing Rules
-
-1. **READ COMPLETELY**: Always read the entire step file before taking any action
-2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
-3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
-4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
-5. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
-
-### Critical Rules (NO EXCEPTIONS)
-
-- 🛑 **NEVER** load multiple step files simultaneously
-- 📖 **ALWAYS** read entire step file before execution
-- 🎯 **ALWAYS** follow the exact instructions in the step file
-- ⏸️ **ALWAYS** halt at menus and wait for user input
-- 📋 **NEVER** create mental todo lists from future steps
-
-## INITIALIZATION SEQUENCE
-
-### 1. Module Configuration Loading
-
-Load and read full config from {project-root}/.bmad/mwm/config.yaml and resolve:
-
-- `user_name`, `output_folder`, `communication_language`, `document_output_language`
-
-### 2. First Step EXECUTION
-
-TODO - NO INSTRUCTIONS IMPLEMENTED YET - INFORM USER THIS IS COMING SOON FUNCTIONALITY.

example-custom-module/mwm/workflows/crisis-support/README.md

@@ -1,31 +0,0 @@
-# Crisis Support Workflow
-
-## Purpose
-
-Immediate response protocol for users in distress, providing resources and appropriate escalation.
-
-## Trigger
-
-Crisis trigger from any agent (emergency response)
-
-## Key Steps
-
-1. Crisis level assessment
-2. Immediate de-escalation techniques
-3. Safety planning
-4. Provide crisis resources
-5. Encourage professional help
-6. Follow-up check scheduling
-7. Document incident (anonymized)
-
-## Expected Output
-
-- Crisis resource list
-- Safety plan document
-- Professional referrals
-- Follow-up reminders
-
-## Notes
-
-This workflow will be implemented using the create-workflow workflow.
-IMPORTANT: NOT a substitute for professional crisis intervention. Provides resources and supports users in accessing professional help. Escalation criteria: immediate danger, severe symptoms, emergency request.

example-custom-module/mwm/workflows/crisis-support/workflow.md

@@ -1,45 +0,0 @@
----
-name: crisis-support
-description: TODO
-web_bundle: false
----
-
-# crisis-support
-
-**Goal:** TODO
-
-**Your Role:** TODO
-
-## WORKFLOW ARCHITECTURE
-
-### Core Principles
-
-TODO
-
-### Step Processing Rules
-
-1. **READ COMPLETELY**: Always read the entire step file before taking any action
-2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
-3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
-4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
-5. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
-
-### Critical Rules (NO EXCEPTIONS)
-
-- 🛑 **NEVER** load multiple step files simultaneously
-- 📖 **ALWAYS** read entire step file before execution
-- 🎯 **ALWAYS** follow the exact instructions in the step file
-- ⏸️ **ALWAYS** halt at menus and wait for user input
-- 📋 **NEVER** create mental todo lists from future steps
-
-## INITIALIZATION SEQUENCE
-
-### 1. Module Configuration Loading
-
-Load and read full config from {project-root}/.bmad/mwm/config.yaml and resolve:
-
-- `user_name`, `output_folder`, `communication_language`, `document_output_language`
-
-### 2. First Step EXECUTION
-
-TODO - NO INSTRUCTIONS IMPLEMENTED YET - INFORM USER THIS IS COMING SOON FUNCTIONALITY.

package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "bmad-method",
-  "version": "6.0.0-alpha.13",
+  "version": "6.0.0-alpha.17",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "bmad-method",
-      "version": "6.0.0-alpha.13",
+      "version": "6.0.0-alpha.17",
       "license": "MIT",
       "dependencies": {
         "@kayvan/markdown-tree-parser": "^1.6.1",

package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "6.0.0-alpha.14",
+  "version": "6.0.0-alpha.19",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",

src/core/_module-installer/install-config.yaml

@@ -1,39 +0,0 @@
-# BMAD™ Core Configuration
-header: "BMAD™ Core Configuration"
-subheader: "Configure the core settings for your BMAD™ installation.\nThese settings will be used across all modules and agents."
-
-bmad_folder:
-  prompt: "What is the root folder for BMAD installation? (Recommended: .bmad)"
-  default: ".bmad"
-  result: "{value}"
-  regex: "^[a-zA-Z0-9._-]{1,20}$"
-
-user_name:
-  prompt: "What shall the agents call you?"
-  default: "BMad"
-  result: "{value}"
-
-communication_language:
-  prompt: "Preferred Chat Language/Style? (English, Mandarin, English Pirate, etc...)"
-  default: "English"
-  result: "{value}"
-
-document_output_language:
-  prompt: "Preferred Document Output Language?"
-  default: "{communication_language}"
-  result: "{value}"
-
-agent_sidecar_folder:
-  prompt: "Where should users agent sidecar memory folders be stored?"
-  default: ".bmad-user-memory"
-  result: "{project-root}/{value}"
-
-output_folder:
-  prompt: "Where should AI Generated Artifacts be saved across all modules?"
-  default: "docs"
-  result: "{project-root}/{value}"
-
-install_user_docs:
-  prompt: "Install user documentation and optimized agent intelligence to each selected modules docs folder?"
-  default: true
-  result: "{value}"

src/core/_module-installer/installer.js

@@ -6,7 +6,7 @@ const chalk = require('chalk');
  *
  * @param {Object} options - Installation options
  * @param {string} options.projectRoot - The root directory of the target project
- * @param {Object} options.config - Module configuration from install-config.yaml
+ * @param {Object} options.config - Module configuration from module.yaml
  * @param {Array<string>} options.installedIDEs - Array of IDE codes that were installed
  * @param {Object} options.logger - Logger instance for output
  * @returns {Promise<boolean>} - Success status

src/core/agents/bmad-master.agent.yaml

@@ -3,7 +3,7 @@
 
 agent:
   metadata:
-    id: "{bmad_folder}/core/agents/bmad-master.md"
+    id: "_bmad/core/agents/bmad-master.md"
     name: "BMad Master"
     title: "BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator"
     icon: "🧙"
@@ -12,28 +12,23 @@ agent:
     role: "Master Task Executor + BMad Expert + Guiding Facilitator Orchestrator"
     identity: "Master-level expert in the BMAD Core Platform and all loaded modules with comprehensive knowledge of all resources, tasks, and workflows. Experienced in direct task execution and runtime resource management, serving as the primary execution engine for BMAD operations."
     communication_style: "Direct and comprehensive, refers to himself in the 3rd person. Expert-level communication focused on efficient task execution, presenting information systematically using numbered lists with immediate command response capability."
-    principles:
+    principles: |
       - "Load resources at runtime never pre-load, and always present numbered lists for choices."
 
-  # Agent-specific critical actions
   critical_actions:
-    - "Load into memory {project-root}/{bmad_folder}/core/config.yaml and set variable project_name, output_folder, user_name, communication_language"
+    - "Load into memory {project-root}/_bmad/core/config.yaml and set variable project_name, output_folder, user_name, communication_language"
     - "Remember the users name is {user_name}"
     - "ALWAYS communicate in {communication_language}"
 
-  # Agent menu items
   menu:
     - trigger: "list-tasks"
-      action: "list all tasks from {project-root}/{bmad_folder}/_cfg/task-manifest.csv"
+      action: "list all tasks from {project-root}/_bmad/_config/task-manifest.csv"
       description: "List Available Tasks"
 
     - trigger: "list-workflows"
-      action: "list all workflows from {project-root}/{bmad_folder}/_cfg/workflow-manifest.csv"
+      action: "list all workflows from {project-root}/_bmad/_config/workflow-manifest.csv"
       description: "List Workflows"
 
     - trigger: "party-mode"
-      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
+      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
       description: "Group chat with all agents"
-
-  # Empty prompts section (no custom prompts for this agent)
-  prompts: []

src/core/agents/bmad-web-orchestrator.agent.xml

@@ -1,113 +0,0 @@
-<agent id="{bmad_folder}/core/agents/bmad-orchestrator.md" name="BMad Orchestrator" title="BMad Web Orchestrator" icon="🎭" localskip="true">
-  <activation critical="MANDATORY">
-    <step n="1">Load this complete web bundle XML - you are the BMad Orchestrator, first agent in this bundle</step>
-    <step n="2">CRITICAL: This bundle contains ALL agents as XML nodes with id="{bmad_folder}/..." and ALL workflows/tasks as nodes findable
-      by type
-      and id</step>
-    <step n="3">Greet user as BMad Orchestrator and display numbered list of ALL menu items from menu section below</step>
-    <step n="4">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
-    <step n="5">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user to
-      clarify | No match → show "Not recognized"</step>
-    <step n="6">When executing a menu item: Check menu-handlers section below for UNIVERSAL handler instructions that apply to ALL agents</step>
-
-    <menu-handlers critical="UNIVERSAL_FOR_ALL_AGENTS">
-      <extract>workflow, exec, tmpl, data, action, validate-workflow</extract>
-      <handlers>
-        <handler type="workflow">
-          When menu item has: workflow="workflow-id"
-          1. Find workflow node by id in this bundle (e.g., &lt;workflow id="workflow-id"&gt;)
-          2. CRITICAL: Always LOAD {bmad_folder}/core/tasks/workflow.xml if referenced
-          3. Execute the workflow content precisely following all steps
-          4. Save outputs after completing EACH workflow step (never batch)
-          5. If workflow id is "todo", inform user it hasn't been implemented yet
-        </handler>
-
-        <handler type="exec">
-          When menu item has: exec="node-id" or exec="inline-instruction"
-          1. If value looks like a path/id → Find and execute node with that id
-          2. If value is text → Execute as direct instruction
-          3. Follow ALL instructions within loaded content EXACTLY
-        </handler>
-
-        <handler type="tmpl">
-          When menu item has: tmpl="template-id"
-          1. Find template node by id in this bundle and pass it to the exec, task, action, or workflow being executed
-        </handler>
-
-        <handler type="data">
-          When menu item has: data="data-id"
-          1. Find data node by id in this bundle
-          2. Parse according to node type (json/yaml/xml/csv)
-          3. Make available as {data} variable for subsequent operations
-        </handler>
-
-        <handler type="action">
-          When menu item has: action="#prompt-id" or action="inline-text"
-          1. If starts with # → Find prompt with matching id in current agent
-          2. Otherwise → Execute the text directly as instruction
-        </handler>
-
-        <handler type="validate-workflow">
-          When menu item has: validate-workflow="workflow-id"
-          1. MUST LOAD {bmad_folder}/core/tasks/validate-workflow.xml
-          2. Execute all validation instructions from that file
-          3. Check workflow's validation property for schema
-          4. Identify file to validate or ask user to specify
-        </handler>
-      </handlers>
-    </menu-handlers>
-
-    <orchestrator-specific>
-      <agent-transformation critical="true">
-        When user selects *agents [agent-name]:
-        1. Find agent XML node with matching name/id in this bundle
-        2. Announce transformation: "Transforming into [agent name]... 🎭"
-        3. BECOME that agent completely:
-        - Load and embody their persona/role/communication_style
-        - Display THEIR menu items (not orchestrator menu)
-        - Execute THEIR commands using universal handlers above
-        4. Stay as that agent until user types *exit
-        5. On *exit: Confirm, then return to BMad Orchestrator persona
-      </agent-transformation>
-
-      <list-agents critical="true">
-        When user selects *list-agents:
-        1. Scan all agent nodes in this bundle
-        2. Display formatted list with:
-        - Number, emoji, name, title
-        - Brief description of capabilities
-        - Main menu items they offer
-        3. Suggest which agent might help with common tasks
-      </list-agents>
-    </orchestrator-specific>
-
-    <rules>
-      Web bundle environment - NO file system access, all content in XML nodes
-      Find resources by XML node id/type within THIS bundle only
-      Use canvas for document drafting when available
-      Menu triggers use asterisk (*) - display exactly as shown
-      Number all lists, use letters for sub-options
-      Stay in character (current agent) until *exit command
-      Options presented as numbered lists with descriptions
-      elicit="true" attributes require user confirmation before proceeding
-    </rules>
-  </activation>
-
-  <persona>
-    <role>Master Orchestrator and BMad Scholar</role>
-    <identity>Master orchestrator with deep expertise across all loaded agents and workflows. Technical brilliance balanced with
-      approachable communication.</identity>
-    <communication_style>Knowledgeable, guiding, approachable, very explanatory when in BMad Orchestrator mode</communication_style>
-    <core_principles>When I transform into another agent, I AM that agent until *exit command received. When I am NOT transformed into
-      another agent, I will give you guidance or suggestions on a workflow based on your needs.</core_principles>
-  </persona>
-  <menu>
-    <item cmd="*help">Show numbered command list</item>
-    <item cmd="*list-agents">List all available agents with their capabilities</item>
-    <item cmd="*agents [agent-name]">Transform into a specific agent</item>
-    <item cmd="*party-mode" exec="{bmad_folder}/core/workflows/party-mode/workflow.md">Enter group chat with all agents
-      simultaneously</item>
-    <item cmd="*advanced-elicitation" task="{bmad_folder}/core/tasks/advanced-elicitation.xml">Push agent to perform advanced elicitation</item>
-    <item cmd="*exit">Exit current session</item>
-  </menu>
-</agent>

src/core/module.yaml

@@ -0,0 +1,25 @@
+code: core
+name: "BMad™  Core Module"
+
+header: "BMad™  Core Configuration"
+subheader: "Configure the core settings for your BMad™  installation.\nThese settings will be used across all modules and agents."
+
+user_name:
+  prompt: "What shall the agents call you (TIP: Use a team name if using with a group)?"
+  default: "BMad"
+  result: "{value}"
+
+communication_language:
+  prompt: "Preferred chat language/style? (English, Mandarin, English Pirate, etc...)"
+  default: "English"
+  result: "{value}"
+
+document_output_language:
+  prompt: "Preferred document output language?"
+  default: "English"
+  result: "{value}"
+
+output_folder:
+  prompt: "Where should default output files be saved unless specified in other modules?"
+  default: "_bmad-output"
+  result: "{project-root}/{value}"

src/core/resources/excalidraw/README.md

@@ -71,15 +71,15 @@ Provides the **HOW** (universal knowledge) while agents provide the **WHAT** (do
 ### Example: Frame Expert (Technical Diagrams)
 
 ```yaml
-# workflows/diagrams/create-flowchart/workflow.yaml
-helpers: '{project-root}/{bmad_folder}/core/resources/excalidraw/excalidraw-helpers.md'
-json_validation: '{project-root}/{bmad_folder}/core/resources/excalidraw/validate-json-instructions.md'
+# workflows/excalidraw-diagrams/create-flowchart/workflow.yaml
+helpers: '{project-root}/_bmad/core/resources/excalidraw/excalidraw-helpers.md'
+json_validation: '{project-root}/_bmad/core/resources/excalidraw/validate-json-instructions.md'
 ```
 
 **Domain-specific additions:**
 
 ```yaml
-# workflows/diagrams/_shared/flowchart-templates.yaml
+# workflows/excalidraw-diagrams/_shared/flowchart-templates.yaml
 flowchart:
   start_node:
     type: ellipse
@@ -99,8 +99,8 @@ flowchart:
 
 ```yaml
 # workflows/create-visual-metaphor/workflow.yaml
-helpers: '{project-root}/{bmad_folder}/core/resources/excalidraw/excalidraw-helpers.md'
-json_validation: '{project-root}/{bmad_folder}/core/resources/excalidraw/validate-json-instructions.md'
+helpers: '{project-root}/_bmad/core/resources/excalidraw/excalidraw-helpers.md'
+json_validation: '{project-root}/_bmad/core/resources/excalidraw/validate-json-instructions.md'
 ```
 
 **Domain-specific additions:**

src/core/tasks/advanced-elicitation.xml

@@ -1,6 +1,6 @@
-<task id="{bmad_folder}/core/tasks/advanced-elicitation.xml" name="Advanced Elicitation" standalone="true"
-  methods="{project-root}/{bmad_folder}/core/tasks/advanced-elicitation-methods.csv"
-  agent-party="{project-root}/{bmad_folder}/_cfg/agent-manifest.csv">
+<task id="_bmad/core/tasks/advanced-elicitation.xml" name="Advanced Elicitation" standalone="true"
+  methods="{project-root}/_bmad/core/tasks/advanced-elicitation-methods.csv"
+  agent-party="{project-root}/_bmad/_config/agent-manifest.csv">
   <llm critical="true">
     <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
     <i>DO NOT skip steps or change the sequence</i>

src/core/tasks/index-docs.xml

@@ -1,4 +1,4 @@
-<task id="{bmad_folder}/core/tasks/index-docs" name="Index Docs"
+<task id="_bmad/core/tasks/index-docs" name="Index Docs"
   description="Generates or updates an index.md of all documents in the specified directory" webskip="true" standalone="true">
   <llm critical="true">
     <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>

src/core/tasks/validate-workflow.xml

@@ -1,4 +1,4 @@
-<task id="{bmad_folder}/core/tasks/validate-workflow.xml" name="Validate Workflow Output">
+<task id="_bmad/core/tasks/validate-workflow.xml" name="Validate Workflow Output">
   <objective>Run a checklist against a document with thorough analysis and produce a validation report</objective>
 
   <inputs>

src/core/tasks/workflow.xml

@@ -1,4 +1,4 @@
-<task id="{bmad_folder}/core/tasks/workflow.xml" name="Execute Workflow">
+<task id="_bmad/core/tasks/workflow.xml" name="Execute Workflow">
   <objective>Execute given workflow by loading its configuration, following instructions, and producing output</objective>
 
   <llm critical="true">
@@ -74,14 +74,14 @@
           <action>Display generated content</action>
           <ask> [a] Advanced Elicitation, [c] Continue, [p] Party-Mode, [y] YOLO the rest of this document only. WAIT for response. <if
               response="a">
-              <action>Start the advanced elicitation workflow {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml</action>
+              <action>Start the advanced elicitation workflow {project-root}/_bmad/core/tasks/advanced-elicitation.xml</action>
             </if>
             <if
               response="c">
               <action>Continue to next step</action>
             </if>
             <if response="p">
-              <action>Start the party-mode workflow {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml</action>
+              <action>Start the party-mode workflow {project-root}/_bmad/core/workflows/party-mode/workflow.yaml</action>
             </if>
             <if
               response="y">
@@ -225,7 +225,7 @@
     <critical-rules>
       • This is the complete workflow execution engine
       • You MUST Follow instructions exactly as written
-      • The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml
+      • The workflow execution engine is governed by: {project-root}/_bmad/core/tasks/workflow.xml
       • You MUST have already loaded and processed: {installed_path}/workflow.yaml
       • This workflow uses INTENT-DRIVEN PLANNING - adapt organically to product type and context
       • YOU ARE FACILITATING A CONVERSATION With a user to produce a final document step by step. The whole process is meant to be

src/core/tools/shard-doc.xml

@@ -1,4 +1,4 @@
-<tool id="{bmad_folder}/core/tasks/shard-doc" name="Shard Document"
+<tool id="_bmad/core/tasks/shard-doc" name="Shard Document"
   description="Splits large markdown documents into smaller, organized files based on level 2 (default) sections" webskip="true"
   standalone="true">
   <objective>Split large markdown documents into smaller, organized files based on level 2 sections using @kayvan/markdown-tree-parser tool</objective>
@@ -64,12 +64,12 @@
 
       <ask>What would you like to do with the original document `[source-document-name]`?
 
-Options:
-[d] Delete - Remove the original (recommended - shards can always be recombined)
-[m] Move to archive - Move original to a backup/archive location
-[k] Keep - Leave original in place (NOT recommended - defeats sharding purpose)
+        Options:
+        [d] Delete - Remove the original (recommended - shards can always be recombined)
+        [m] Move to archive - Move original to a backup/archive location
+        [k] Keep - Leave original in place (NOT recommended - defeats sharding purpose)
 
-Your choice (d/m/k):</ask>
+        Your choice (d/m/k):</ask>
 
       <check if="user selects 'd' (delete)">
         <action>Delete the original source document file</action>
@@ -92,12 +92,12 @@ Your choice (d/m/k):</ask>
         <action>Display warning to user:</action>
         <output>⚠️ WARNING: Keeping both original and sharded versions is NOT recommended.
 
-This creates confusion because:
-- The discover_inputs protocol may load the wrong version
-- Updates to one won't reflect in the other
-- You'll have duplicate content taking up space
+          This creates confusion because:
+          - The discover_inputs protocol may load the wrong version
+          - Updates to one won't reflect in the other
+          - You'll have duplicate content taking up space
 
-Consider deleting or archiving the original document.</output>
+          Consider deleting or archiving the original document.</output>
         <action>Confirm user choice: "Original document kept at: [source-document-path]"</action>
       </check>
     </step>
@@ -106,4 +106,4 @@ Consider deleting or archiving the original document.</output>
   <halt-conditions critical="true">
     <i>HALT if npx command fails or produces no output files</i>
   </halt-conditions>
-</tool>
+</tool>

src/core/workflows/brainstorming/workflow.md

@@ -1,5 +1,5 @@
 ---
-name: brainstorming-session
+name: brainstorming
 description: Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods
 context_file: '' # Optional context file path for project-specific guidance
 ---
@@ -28,7 +28,7 @@ This uses **micro-file architecture** for disciplined execution:
 
 ### Configuration Loading
 
-Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve:
+Load config from `{project-root}/_bmad/core/config.yaml` and resolve:
 
 - `project_name`, `output_folder`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`
@@ -36,7 +36,7 @@ Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve:
 
 ### Paths
 
-- `installed_path` = `{project-root}/{bmad_folder}/core/workflows/brainstorming`
+- `installed_path` = `{project-root}/_bmad/core/workflows/brainstorming`
 - `template_path` = `{installed_path}/template.md`
 - `brain_techniques_path` = `{installed_path}/brain-methods.csv`
 - `default_output_file` = `{output_folder}/analysis/brainstorming-session-{{date}}.md`

src/core/workflows/party-mode/steps/step-01-agent-loading.md

@@ -18,7 +18,7 @@
 
 ## CONTEXT BOUNDARIES:
 
-- Agent manifest CSV is available at `{project-root}/{bmad_folder}/_cfg/agent-manifest.csv`
+- Agent manifest CSV is available at `{project-root}/_bmad/_config/agent-manifest.csv`
 - User configuration from config.yaml is loaded and resolved
 - Party mode is standalone interactive workflow
 - All agent data is available for conversation orchestration
@@ -37,7 +37,7 @@ Begin agent loading process:
 
 **Agent Manifest Loading:**"
 
-Load and parse the agent manifest CSV from `{project-root}/{bmad_folder}/_cfg/agent-manifest.csv`
+Load and parse the agent manifest CSV from `{project-root}/_bmad/_config/agent-manifest.csv`
 
 ### 2. Extract Agent Data
 

src/core/workflows/party-mode/workflow.md

@@ -27,17 +27,17 @@ This uses **micro-file architecture** with **sequential conversation orchestrati
 
 ### Configuration Loading
 
-Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve:
+Load config from `{project-root}/_bmad/core/config.yaml` and resolve:
 
 - `project_name`, `output_folder`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`
 - `date` as a system-generated value
-- Agent manifest path: `{project-root}/{bmad_folder}/_cfg/agent-manifest.csv`
+- Agent manifest path: `{project-root}/_bmad/_config/agent-manifest.csv`
 
 ### Paths
 
-- `installed_path` = `{project-root}/{bmad_folder}/core/workflows/party-mode`
-- `agent_manifest_path` = `{project-root}/{bmad_folder}/_cfg/agent-manifest.csv`
+- `installed_path` = `{project-root}/_bmad/core/workflows/party-mode`
+- `agent_manifest_path` = `{project-root}/_bmad/_config/agent-manifest.csv`
 - `standalone_mode` = `true` (party mode is an interactive workflow)
 
 ---