Merge branch 'main' into feature/quick-dev-intelligent-routing-clean

Feat/sprint status command (#1012 )
* feat: add sprint-status command * minor changes to reduce the change radius --------- Co-authored-by: mq-bot <mq-bot@local> Co-authored-by: Brian <bmadcode@gmail.com>
2026-01-30 04:32:02 +00:00 · 2025-12-03 12:14:13 -06:00 · 2025-12-03 12:00:34 -06:00 · 2025-12-03 10:15:41 -07:00 · 2025-12-03 10:42:28 -06:00 · 2025-12-03 09:36:31 -07:00
952 changed files with 128167 additions and 31816 deletions
--- a/.github/ISSUE_TEMPLATE/config.yaml
+++ b/.github/ISSUE_TEMPLATE/config.yaml
@@ -1 +1,5 @@
 blank_issues_enabled: false
+contact_links:
+  - name: Discord Community Support
+    url: https://discord.gg/gk8jAdXWmj
+    about: Please join our Discord server for general questions and community discussion before opening an issue.
--- a/.github/ISSUE_TEMPLATE/idea_submission.md
+++ b/.github/ISSUE_TEMPLATE/idea_submission.md
@@ -1,6 +1,6 @@
 ---
-name: V5 Idea Submission
-about: Suggest an idea for v5
+name: V6 Idea Submission
+about: Suggest an idea for v6
 title: ''
 labels: ''
 assignees: ''
@@ -92,7 +92,7 @@ Fix issues and add features.

 _Why this is poor: Too vague, no specific problem identified, no measurable success criteria, unclear scope_

-</details>****
+</details>

 ---

--- a/.github/workflows/bundle-latest.yaml
+++ b/.github/workflows/bundle-latest.yaml
@@ -0,0 +1,329 @@
+name: Publish Latest Bundles
+
+on:
+  push:
+    branches: [main]
+  workflow_dispatch: {}
+
+permissions:
+  contents: write
+
+jobs:
+  bundle-and-publish:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout BMAD-METHOD
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version-file: ".nvmrc"
+          cache: npm
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Generate bundles
+        run: npm run bundle
+
+      - name: Create bundle distribution structure
+        run: |
+          mkdir -p dist/bundles
+
+          # Copy web bundles (XML files from npm run bundle output)
+          cp -r web-bundles/* dist/bundles/ 2>/dev/null || true
+
+          # Verify bundles were copied (fail if completely empty)
+          if [ ! "$(ls -A dist/bundles)" ]; then
+            echo "❌ ERROR: No bundles found in dist/bundles/"
+            echo "This likely means 'npm run bundle' failed or bundles weren't generated"
+            exit 1
+          fi
+
+          # Count bundles per module
+          for module in bmm bmb cis bmgd; do
+            if [ -d "dist/bundles/$module/agents" ]; then
+              COUNT=$(find dist/bundles/$module/agents -name '*.xml' 2>/dev/null | wc -l)
+              echo "✅ $module: $COUNT agent bundles"
+            fi
+          done
+
+          # Generate index.html for each agents directory (fixes directory browsing)
+          for module in bmm bmb cis bmgd; do
+            if [ -d "dist/bundles/$module/agents" ]; then
+              cat > "dist/bundles/$module/agents/index.html" << 'DIREOF'
+          <!DOCTYPE html>
+          <html>
+          <head>
+            <title>MODULE_NAME Agents</title>
+            <style>
+              body { font-family: system-ui; max-width: 800px; margin: 50px auto; padding: 20px; }
+              li { margin: 10px 0; }
+              a { color: #0066cc; text-decoration: none; }
+              a:hover { text-decoration: underline; }
+            </style>
+          </head>
+          <body>
+            <h1>MODULE_NAME Agents</h1>
+            <ul>
+          AGENT_LINKS
+            </ul>
+            <p><a href="../../">← Back to all modules</a></p>
+          </body>
+          </html>
+          DIREOF
+
+              # Replace MODULE_NAME
+              sed -i "s/MODULE_NAME/${module^^}/g" "dist/bundles/$module/agents/index.html"
+
+              # Generate agent links
+              LINKS=""
+              for file in dist/bundles/$module/agents/*.xml; do
+                if [ -f "$file" ]; then
+                  name=$(basename "$file" .xml)
+                  LINKS="$LINKS      <li><a href=\"./$name.xml\">$name</a></li>\n"
+                fi
+              done
+              sed -i "s|AGENT_LINKS|$LINKS|" "dist/bundles/$module/agents/index.html"
+            fi
+          done
+
+          # Create zip archives per module
+          mkdir -p dist/bundles/downloads
+          for module in bmm bmb cis bmgd; do
+            if [ -d "dist/bundles/$module" ]; then
+              (cd dist/bundles && zip -r downloads/$module-agents.zip $module/)
+              echo "✅ Created $module-agents.zip"
+            fi
+          done
+
+          # Generate index.html dynamically based on actual bundles
+          TIMESTAMP=$(date -u +"%Y-%m-%d %H:%M UTC")
+          COMMIT_SHA=$(git rev-parse --short HEAD)
+
+          # Function to generate agent links for a module
+          generate_agent_links() {
+            local module=$1
+            local agent_dir="dist/bundles/$module/agents"
+
+            if [ ! -d "$agent_dir" ]; then
+              echo ""
+              return
+            fi
+
+            local links=""
+            local count=0
+
+            # Find all XML files and generate links
+            for xml_file in "$agent_dir"/*.xml; do
+              if [ -f "$xml_file" ]; then
+                local agent_name=$(basename "$xml_file" .xml)
+                # Convert filename to display name (pm -> PM, tech-writer -> Tech Writer)
+                local display_name=$(echo "$agent_name" | sed 's/-/ /g' | awk '{for(i=1;i<=NF;i++) {if(length($i)==2) $i=toupper($i); else $i=toupper(substr($i,1,1)) tolower(substr($i,2));}}1')
+
+                if [ $count -gt 0 ]; then
+                  links="$links | "
+                fi
+                links="$links<a href=\"./$module/agents/$agent_name.xml\">$display_name</a>"
+                count=$((count + 1))
+              fi
+            done
+
+            echo "$links"
+          }
+
+          # Generate agent links for each module
+          BMM_LINKS=$(generate_agent_links "bmm")
+          CIS_LINKS=$(generate_agent_links "cis")
+          BMGD_LINKS=$(generate_agent_links "bmgd")
+
+          # Count agents for bulk downloads
+          BMM_COUNT=$(find dist/bundles/bmm/agents -name '*.xml' 2>/dev/null | wc -l | tr -d ' ')
+          CIS_COUNT=$(find dist/bundles/cis/agents -name '*.xml' 2>/dev/null | wc -l | tr -d ' ')
+          BMGD_COUNT=$(find dist/bundles/bmgd/agents -name '*.xml' 2>/dev/null | wc -l | tr -d ' ')
+
+          # Create index.html
+          cat > dist/bundles/index.html << EOF
+          <!DOCTYPE html>
+          <html>
+          <head>
+            <title>BMAD Bundles - Latest</title>
+            <meta charset="utf-8">
+            <style>
+              body { font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, sans-serif; max-width: 800px; margin: 50px auto; padding: 20px; }
+              h1 { color: #333; }
+              .platform { margin: 30px 0; padding: 20px; background: #f5f5f5; border-radius: 8px; }
+              .module { margin: 15px 0; }
+              a { color: #0066cc; text-decoration: none; }
+              a:hover { text-decoration: underline; }
+              code { background: #e0e0e0; padding: 2px 6px; border-radius: 3px; }
+              .warning { background: #fff3cd; padding: 15px; border-left: 4px solid #ffc107; margin: 20px 0; }
+            </style>
+          </head>
+          <body>
+            <h1>BMAD Web Bundles - Latest (Main Branch)</h1>
+
+            <div class="warning">
+              <strong>⚠️ Latest Build (Unstable)</strong><br>
+              These bundles are built from the latest main branch commit. For stable releases, visit
+              <a href="https://github.com/bmad-code-org/BMAD-METHOD/releases/latest">GitHub Releases</a>.
+            </div>
+
+            <p><strong>Last Updated:</strong> <code>$TIMESTAMP</code></p>
+            <p><strong>Commit:</strong> <code>$COMMIT_SHA</code></p>
+
+            <h2>Available Modules</h2>
+
+          EOF
+
+          # Add BMM section if agents exist
+          if [ -n "$BMM_LINKS" ]; then
+            cat >> dist/bundles/index.html << EOF
+            <div class="platform">
+              <h3>BMM (BMad Method)</h3>
+              <div class="module">
+                $BMM_LINKS<br>
+                📁 <a href="./bmm/agents/">Browse All</a> | 📦 <a href="./downloads/bmm-agents.zip">Download Zip</a>
+              </div>
+            </div>
+
+          EOF
+          fi
+
+          # Add CIS section if agents exist
+          if [ -n "$CIS_LINKS" ]; then
+            cat >> dist/bundles/index.html << EOF
+            <div class="platform">
+              <h3>CIS (Creative Intelligence Suite)</h3>
+              <div class="module">
+                $CIS_LINKS<br>
+                📁 <a href="./cis/agents/">Browse Agents</a> | 📦 <a href="./downloads/cis-agents.zip">Download Zip</a>
+              </div>
+            </div>
+
+          EOF
+          fi
+
+          # Add BMGD section if agents exist
+          if [ -n "$BMGD_LINKS" ]; then
+            cat >> dist/bundles/index.html << EOF
+            <div class="platform">
+              <h3>BMGD (Game Development)</h3>
+              <div class="module">
+                $BMGD_LINKS<br>
+                📁 <a href="./bmgd/agents/">Browse Agents</a> | 📦 <a href="./downloads/bmgd-agents.zip">Download Zip</a>
+              </div>
+            </div>
+
+          EOF
+          fi
+
+          # Add bulk downloads section
+          cat >> dist/bundles/index.html << EOF
+            <h2>Bulk Downloads</h2>
+            <p>Download all agents for a module as a zip archive:</p>
+            <ul>
+          EOF
+
+          [ "$BMM_COUNT" -gt 0 ] && echo "              <li><a href=\"./downloads/bmm-agents.zip\">📦 BMM Agents (all $BMM_COUNT)</a></li>" >> dist/bundles/index.html
+          [ "$CIS_COUNT" -gt 0 ] && echo "              <li><a href=\"./downloads/cis-agents.zip\">📦 CIS Agents (all $CIS_COUNT)</a></li>" >> dist/bundles/index.html
+          [ "$BMGD_COUNT" -gt 0 ] && echo "              <li><a href=\"./downloads/bmgd-agents.zip\">📦 BMGD Agents (all $BMGD_COUNT)</a></li>" >> dist/bundles/index.html
+
+          # Close HTML
+          cat >> dist/bundles/index.html << 'EOF'
+            </ul>
+
+            <h2>Usage</h2>
+            <p>Copy the raw XML URL and paste into your AI platform's custom instructions or project knowledge.</p>
+            <p>Example: <code>https://raw.githubusercontent.com/bmad-code-org/bmad-bundles/main/bmm/agents/pm.xml</code></p>
+
+            <h2>Installation (Recommended)</h2>
+            <p>For full IDE integration with slash commands, use the installer:</p>
+            <pre>npx bmad-method@alpha install</pre>
+
+            <footer style="margin-top: 50px; padding-top: 20px; border-top: 1px solid #ccc; color: #666;">
+              <p>Built from <a href="https://github.com/bmad-code-org/BMAD-METHOD">BMAD-METHOD</a> repository.</p>
+            </footer>
+          </body>
+          </html>
+          EOF
+
+      - name: Checkout bmad-bundles repo
+        uses: actions/checkout@v4
+        with:
+          repository: bmad-code-org/bmad-bundles
+          path: bmad-bundles
+          token: ${{ secrets.BUNDLES_PAT }}
+
+      - name: Update bundles
+        run: |
+          # Clear old bundles
+          rm -rf bmad-bundles/*
+
+          # Copy new bundles
+          cp -r dist/bundles/* bmad-bundles/
+
+          # Create .nojekyll for GitHub Pages
+          touch bmad-bundles/.nojekyll
+
+          # Create README
+          cat > bmad-bundles/README.md << 'EOF'
+          # BMAD Web Bundles (Latest)
+
+          **⚠️ Unstable Build**: These bundles are auto-generated from the latest `main` branch.
+
+          For stable releases, visit [GitHub Releases](https://github.com/bmad-code-org/BMAD-METHOD/releases/latest).
+
+          ## Usage
+
+          Copy raw markdown URLs for use in AI platforms:
+
+          - Claude Code: `https://raw.githubusercontent.com/bmad-code-org/bmad-bundles/main/claude-code/sub-agents/{agent}.md`
+          - ChatGPT: `https://raw.githubusercontent.com/bmad-code-org/bmad-bundles/main/chatgpt/sub-agents/{agent}.md`
+          - Gemini: `https://raw.githubusercontent.com/bmad-code-org/bmad-bundles/main/gemini/sub-agents/{agent}.md`
+
+          ## Browse
+
+          Visit [https://bmad-code-org.github.io/bmad-bundles/](https://bmad-code-org.github.io/bmad-bundles/) to browse bundles.
+
+          ## Installation (Recommended)
+
+          For full IDE integration:
+          ```bash
+          npx bmad-method@alpha install
+          ```
+
+          ---
+
+          Auto-updated by [BMAD-METHOD](https://github.com/bmad-code-org/BMAD-METHOD) on every main branch merge.
+          EOF
+
+      - name: Commit and push to bmad-bundles
+        run: |
+          cd bmad-bundles
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+
+          git add .
+
+          if git diff --staged --quiet; then
+            echo "No changes to bundles, skipping commit"
+          else
+            COMMIT_SHA=$(cd .. && git rev-parse --short HEAD)
+            git commit -m "Update bundles from BMAD-METHOD@${COMMIT_SHA}"
+            git push
+            echo "✅ Bundles published to GitHub Pages"
+          fi
+
+      - name: Summary
+        run: |
+          echo "## 🎉 Bundles Published!" >> $GITHUB_STEP_SUMMARY
+          echo "" >> $GITHUB_STEP_SUMMARY
+          echo "**Latest bundles** available at:" >> $GITHUB_STEP_SUMMARY
+          echo "- 🌐 Browse: https://bmad-code-org.github.io/bmad-bundles/" >> $GITHUB_STEP_SUMMARY
+          echo "- 📦 Raw files: https://github.com/bmad-code-org/bmad-bundles" >> $GITHUB_STEP_SUMMARY
+          echo "" >> $GITHUB_STEP_SUMMARY
+          echo "**Commit**: ${{ github.sha }}" >> $GITHUB_STEP_SUMMARY
--- a/.github/workflows/format-check.yaml
+++ b/.github/workflows/format-check.yaml
@@ -1,43 +0,0 @@
-name: format-check
-
-"on":
-  pull_request:
-    branches: ["**"]
-  workflow_dispatch:
-
-jobs:
-  prettier:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Setup Node
-        uses: actions/setup-node@v4
-        with:
-          node-version-file: ".nvmrc"
-          cache: "npm"
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Prettier format check
-        run: npm run format:check
-
-  eslint:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Setup Node
-        uses: actions/setup-node@v4
-        with:
-          node-version-file: ".nvmrc"
-          cache: "npm"
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: ESLint
-        run: npm run lint
--- a/.github/workflows/manual-release.yaml
+++ b/.github/workflows/manual-release.yaml
@@ -61,8 +61,34 @@ jobs:
        run: |
          sed -i 's/"version": ".*"/"version": "${{ steps.version.outputs.new_version }}"/' tools/installer/package.json

-      - name: Build project
-        run: npm run build
+      - 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 }} .

      - name: Commit version bump
        run: |
@@ -149,25 +175,46 @@ jobs:
      - name: Publish to NPM
        env:
          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-        run: npm publish
+        run: |
+          VERSION="${{ steps.version.outputs.new_version }}"
+          if [[ "$VERSION" == *"alpha"* ]] || [[ "$VERSION" == *"beta"* ]]; then
+            echo "Publishing prerelease version with --tag alpha"
+            npm publish --tag alpha
+          else
+            echo "Publishing stable version with --tag latest"
+            npm publish --tag latest
+          fi

-      - name: Create GitHub Release
-        uses: actions/create-release@v1
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - name: Create GitHub Release with Bundles
+        uses: softprops/action-gh-release@v2
        with:
          tag_name: v${{ steps.version.outputs.new_version }}
-          release_name: "BMad Method v${{ steps.version.outputs.new_version }}"
-          body: ${{ steps.release_notes.outputs.RELEASE_NOTES }}
+          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: 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: |
-          echo "🎉 Successfully released v${{ steps.version.outputs.new_version }}!"
-          echo "📦 Published to NPM with @latest tag"
-          echo "🏷️ Git tag: v${{ steps.version.outputs.new_version }}"
-          echo "✅ Users running 'npx bmad-method install' will now get version ${{ steps.version.outputs.new_version }}"
-          echo ""
-          echo "📝 Release notes preview:"
-          cat release_notes.md
+          echo "## 🎉 Successfully released v${{ steps.version.outputs.new_version }}!" >> $GITHUB_STEP_SUMMARY
+          echo "" >> $GITHUB_STEP_SUMMARY
+          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
+          echo "npx bmad-method@${{ steps.version.outputs.new_version }} install" >> $GITHUB_STEP_SUMMARY
+          echo "\`\`\`" >> $GITHUB_STEP_SUMMARY
--- a/.github/workflows/quality.yaml
+++ b/.github/workflows/quality.yaml
@@ -0,0 +1,78 @@
+name: Quality & Validation
+
+# Runs comprehensive quality checks on all PRs:
+# - Prettier (formatting)
+# - ESLint (linting)
+# - Schema validation (YAML structure)
+# - Agent schema tests (fixture-based validation)
+# - Installation component tests (compilation)
+# - Bundle validation (web bundle integrity)
+
+"on":
+  pull_request:
+    branches: ["**"]
+  workflow_dispatch:
+
+jobs:
+  prettier:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version-file: ".nvmrc"
+          cache: "npm"
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Prettier format check
+        run: npm run format:check
+
+  eslint:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version-file: ".nvmrc"
+          cache: "npm"
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: ESLint
+        run: npm run lint
+
+  validate:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version-file: ".nvmrc"
+          cache: "npm"
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Validate YAML schemas
+        run: npm run validate:schemas
+
+      - name: Run agent schema validation tests
+        run: npm run test:schemas
+
+      - name: Test agent compilation components
+        run: npm run test:install
+
+      - name: Validate web bundles
+        run: npm run validate:bundles
--- a/.gitignore
+++ b/.gitignore
@@ -6,6 +6,10 @@ deno.lock
 pnpm-workspace.yaml
 package-lock.json

+
+test-output/*
+coverage/
+
 # Logs
 logs/
 *.log
@@ -22,7 +26,6 @@ build/*.txt
 Thumbs.db

 # Development tools and configs
-.prettierignore
 .prettierrc

 # IDE and editor configs
@@ -33,12 +36,12 @@ Thumbs.db
 # AI assistant files
 CLAUDE.md
 .ai/*
-.claude
 cursor
 .gemini
 .mcp.json
 CLAUDE.local.md
 .serena/
+.claude/settings.local.json

 # Project-specific
 .bmad-core
@@ -51,9 +54,20 @@ flattened-codebase.xml
 #UAT template testing output files
 tools/template-test-generator/test-scenarios/

-# Bundler temporary files
+# Bundler temporary files and generated bundles
 .bundler-temp/

-# Test Install Output
+# Generated web bundles (built by CI, not committed)
+src/modules/bmm/sub-modules/
+src/modules/bmb/sub-modules/
+src/modules/cis/sub-modules/
+src/modules/bmgd/sub-modules/

 z*/
+
+.bmad
+.claude
+.codex
+.github/chatmodes
+.agent
+.agentvibes/
--- a/.husky/pre-commit
+++ b/.husky/pre-commit
@@ -1,3 +1,7 @@
 #!/usr/bin/env sh

+# Auto-fix changed files and stage them
 npx --no-install lint-staged
+
+# Validate everything
+npm test
--- a/.prettierignore
+++ b/.prettierignore
@@ -0,0 +1,9 @@
+# Test fixtures with intentionally broken/malformed files
+test/fixtures/**
+
+# Contributor Covenant (external standard)
+CODE_OF_CONDUCT.md
+
+# BMAD runtime folders (user-specific, not in repo)
+.bmad/
+.bmad*/
--- a/.vscode/settings.json
+++ b/.vscode/settings.json
@@ -21,6 +21,7 @@
    "Decisioning",
    "eksctl",
    "elicitations",
+    "Excalidraw",
    "filecomplete",
    "fintech",
    "fluxcd",
@@ -56,7 +57,8 @@
    "tileset",
    "tmpl",
    "Trae",
-    "VNET"
+    "VNET",
+    "webskip"
  ],
  "json.schemas": [
    {
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,21 +1,502 @@
 # Changelog

+## [6.0.0-alpha.13]
+
+**Release: November 30, 2025**
+
+### 🏗️ 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
+
+### 🤖 Agent System Revolution
+
+**Universal Custom Agent Support:**
+
+- **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
+
+**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
+
+### ⚠️ 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
+
+## [6.0.0-alpha.12]
+
+**Release: November 19, 2025**
+
+### 🐛 Bug Fixes
+
+- Added missing `yaml` dependency to fix `MODULE_NOT_FOUND` error when running `npx bmad-method install`
+
+## [6.0.0-alpha.11]
+
+**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**.
+
+### 🎨 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
+
+### 📚 BMB Agent Builder Enhancement
+
+**Vastly Improved Agent Creation & Editing Capabilities:**
+
+- 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
+
+**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
+
+### ⚠️ 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
+
+## [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
+
+## [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
+
+## [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
+
+## [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
+
+## [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
+
+## [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
+
+## [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
+
+## [6.0.0-alpha.3]
+
+**Release: October 2025**
+
+- **Codex Installer**: Custom prompts in `.codex/prompts/` directory structure
+- **Bug Fixes**: Various installer and workflow improvements
+- **Documentation**: Initial documentation structure established
+
 ## [6.0.0-alpha.0]

 **Release: September 28, 2025**

-Initial alpha release of a major rewrite and overhaul improvement of past versions.
-
-### Major New Features
-
- **Lean Core**: The core of BMad is very simple - common tasks that apply to any future module or agents, along with common agents that will be added to any modules - bmad-web-orchestrator and bmad-master.
- **BMad Method**: The new BMad Method (AKA bmm) is a complete overhaul of the v4 method, now a fully scale adaptive rewrite. The workflow now scales from small enhancements to massive undertakings across multiple services or architectures, supporting a new vast array of project type, including a full subclass of game development specifics.
- **BoMB**: The BMad Builder (AKA BoMB) now is able to fully automate creation and conversion of expansion packs from v5 to modules in v5 along with the net new ideation and brainstorming through implementation and testing of net new Modules, Workflows (were tasks and templates), Module Agents, and Standalone Personal Agents
- **CIS**: The Creative Intelligence Suite (AKA CIS)
-
-## [v5.0.0] - SKIPPED
-
-**Note**: Version 5.0.0 was skipped due to NPX registry issues that corrupted the version. Development continues with v6.0.0-alpha.0.
+- **Lean Core**: Simple common tasks and agents (bmad-web-orchestrator, bmad-master)
+- **BMad Method (BMM)**: Complete scale-adaptive rewrite supporting projects from small enhancements to massive undertakings
+- **BoMB**: BMad Builder for creating and converting modules, workflows, and agents
+- **CIS**: Creative Intelligence Suite for ideation and creative workflows
+- **Game Development**: Full subclass of game-specific development patterns**Note**: Version 5.0.0 was skipped due to NPX registry issues that corrupted the version. Development continues with v6.0.0-alpha.0.

 ## [v4.43.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v4.43.0)

--- a/CODE_OF_CONDUCT.md
+++ b/CODE_OF_CONDUCT.md
@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+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.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+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.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+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.
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -86,25 +86,13 @@ Please propose small, granular changes! For large or significant changes, discus

 ### Which Branch?

-**Submit to `next` branch** (most contributions):
-
- ✨ New features or agents
- 🎨 Enhancements to existing features
- 📚 Documentation updates
- ♻️ Code refactoring
- ⚡ Performance improvements
- 🧪 New tests
- 🎁 New bmad modules
-
-**Submit to `main` branch** (critical only):
+**Submit PR's to `main` branch** (critical only):

 - 🚨 Critical bug fixes that break basic functionality
 - 🔒 Security patches
 - 📚 Fixing dangerously incorrect documentation
 - 🐛 Bugs preventing installation or basic usage

-**When in doubt, submit to `next`**. We'd rather test changes thoroughly before they hit stable.
-
 ### PR Size Guidelines

 - **Ideal PR size**: 200-400 lines of code changes
@@ -256,6 +244,7 @@ Each commit should represent one logical change:
 - Web/planning agents can be larger with more complex tasks
 - Everything is natural language (markdown) - no code in core framework
 - Use bmad modules for domain-specific features
+- Validate YAML schemas with `npm run validate:schemas` before committing

 ## Code of Conduct

--- a/README.md
+++ b/README.md
@@ -1,216 +1,214 @@
-# BMad CORE v6 Alpha
+# BMad Method & BMad Core

-[![Version](https://img.shields.io/npm/v/bmad-method?color=blue&label=version)](https://www.npmjs.com/package/bmad-method)
+[![Stable Version](https://img.shields.io/npm/v/bmad-method?color=blue&label=stable)](https://www.npmjs.com/package/bmad-method)
+[![Alpha Version](https://img.shields.io/npm/v/bmad-method/alpha?color=orange&label=alpha)](https://www.npmjs.com/package/bmad-method)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
 [![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)

-**The Universal Human-AI Collaboration Platform**
+## AI-Driven Agile Development That Scales From Bug Fixes to Enterprise

-IMPORTANT NOTE: ALPHA is potentially an unstable release that could drastically change in many ways. While we hope that is not the case, know that it could - your using and testing it during this time though is much appreciated. Please help us out by filing issues or reaching out in Discord to discuss.
+**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.

-IMPORTANT NOTE 2: ALPHA is not complete - there are still many small and big features, polish, doc improvements, and more agents and workflows coming ahead of the beta release!
+> **🚀 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)

-IMPORTANT NOTE 3: ALPHA Web Bundles and Agents are not fully working yet - so you will need to use a good quality IDE to test many of the features, especially with the BMad Method module. BUT - the new agent builder and stand alone agent feature can work great with weaker models - this will still evolve over the coming weeks.
+> **📌 v6 Alpha Status:** Near-beta quality with vastly improved stability. Documentation is being finalized. New videos coming soon to [BMadCode YouTube](https://www.youtube.com/@BMadCode).

-BMad-CORE (Collaboration Optimized Reflection Engine) is a framework that brings out the best in you through AI agents designed to enhance human thinking rather than replace it. Unlike traditional AI tools that do the work for you, BMad-CORE's specialized agents guide you through the facilitation of optimized collaborative reflective workflows to unlock your full potential across any domain. It is this magic that powers the BMad Method, which is just one of the many modules that exist or are coming soon.
+## 🎯 Why BMad Method?

-**[Subscribe to BMadCode on YouTube](https://www.youtube.com/@BMadCode?sub_confirmation=1)** and **[Join our amazing, active Discord Community](https://discord.gg/gk8jAdXWmj)**
+Unlike generic AI coding assistants, BMad Method provides **structured, battle-tested workflows** powered by specialized agents who understand agile development. Each agent has deep domain expertise—from product management to architecture to testing—working together seamlessly.

-⭐ **If you find this project helpful or useful, please give it a star in the upper right-hand corner!** It helps others discover BMad-CORE and you will be notified of updates!
+**✨ Key Benefits:**

-## What Makes BMad-Core Different
+- **Scale-Adaptive Intelligence** - Automatically adjusts planning depth from bug fixes to enterprise systems
+- **Complete Development Lifecycle** - Analysis → Planning → Architecture → Implementation
+- **Specialized Expertise** - 19 agents with specific roles (PM, Architect, Developer, UX Designer, etc.)
+- **Proven Methodologies** - Built on agile best practices with AI amplification
+- **IDE Integration** - Works with Claude Code, Cursor, Windsurf, VS Code

-**Traditional AI**: Does the thinking for you, providing average, bland answers and solutions
-**BMad-CORE**: Brings out the best thinking in you and the AI through guided collaboration, elicitation, and facilitation
+## 🏗️ The Power of BMad Core

-### Core Philosophy: Human Amplification, Not Replacement
+**BMad Method** is actually a sophisticated module built on top of **BMad Core** (**C**ollaboration **O**ptimized **R**eflection **E**ngine). This revolutionary architecture means:

-BMad-Core's AI agents act as expert coaches, mentors, and collaborators who:
+- **BMad Core** provides the universal framework for human-AI collaboration
+- **BMad Method** leverages Core to deliver agile development workflows
+- **BMad Builder** lets YOU create custom modules as powerful as BMad Method itself

- Ask the right questions to stimulate your thinking
- Provide structured frameworks for complex problems
- Guide you through reflective processes to discover insights
- Help you develop mastery in your chosen domains
- Amplify your natural abilities rather than substituting for them
+With **BMad Builder**, you can architect both simple agents and vastly complex domain-specific modules (legal, medical, finance, education, creative) that will soon be sharable in an **official community marketplace**. Imagine building and sharing your own specialized AI team!

-## The Collaboration Optimized Reflection Engine
+## 📊 See It In Action

-At the heart of BMad-Core lies the **C.O.R.E.** system:
+<p align="center">
+  <img src="./src/modules/bmm/docs/images/workflow-method-greenfield.svg" alt="BMad Method Workflow" width="100%">
+</p>

- **Collaboration**: Human-AI partnership where both contribute unique strengths
- **Optimized**: The collaborative process has been refined for maximum effectiveness
- **Reflection**: Guided thinking that helps you discover better solutions and insights
- **Engine**: The powerful framework that orchestrates specialized agents and workflows
+<p align="center">
+  <em>Complete BMad Method workflow showing all phases, agents, and decision points</em>
+</p>

-## Universal Domain Coverage Through Modules
+## 🚀 Get Started in 3 Steps

-BMad-CORE works in ANY domain through specialized modules (previously called expansion packs)!
+### 1. Install BMad Method

-### Available Modules with Alpha Release
+```bash
+# Install v6 Alpha (recommended)
+npx bmad-method@alpha install

- **BMad Core (core)**: Included and used to power every current and future module; includes a master orchestrator for the local environment and one for the web bundles used with ChatGPT or Gemini Gems, for example.
- **BMad Method (bmm)**: Agile AI-driven software development - the classic that started it all and is still the best - but with v6, massively improved thanks to a rebuild from the ground up built on the new powerful BMad-CORE engine. The BMad Method has also been expanded to use a new "Scale Adaptive Workflow Engine"™.
- **BMad BoMB (bmb)**: The BMad Builder is your Custom Agent, Workflow, and Module authoring tool - it's now easier than ever to customize existing modules or create whatever you can imagine as a standalone module.
- **Creative Intelligence Suite (cis)**: Unlock innovation, problem-solving, and creative thinking! Brainstorming that was part of the BMad Method in the past is now part of this standalone module along with other workflows. The power of BMad modules still allows modules to borrow from each other - so the CIS, while standalone, also powers the brainstorming abilities for certain agents within the BMad Method!
+# Or stable v4 for production
+npx bmad-method install
+```

-## Alpha Installation and Testing
+### 2. Initialize Your Project

-**Prerequisites**: [Node.js](https://nodejs.org) v20+ required
+Load any agent in your IDE and run:

-Clone this repo ALPHA BRANCH to a folder. From the root of the folder, run `npm run install:bmad` and follow the installer questions.
+```
+*workflow-init
+```

-The Core Module will always be installed. The default initial module selection will be BMM for all the core BMad Method functionality and flow from brainstorming through software development.
+This analyzes your project and recommends the right workflow track.

-Note on installation: All installs now go to a single folder called `bmad` instead of multiple folders. When you install a module, you may still see folders other than the one you selected in the destination/bmad folder. This is intentional and not a bug - it will copy over to those other folders only the minimum that is needed because it is shared across the modules. For example, for now during Alpha to test this feature - BMM relies on the brainstorming feature of the CIS and some items from CORE - so this is why even if you only select BMM, you will still see bmad/core and bmad/cis along with bmad/bmm.
+### 3. Choose Your Track

-## What's New in V6-ALPHA
+BMad Method adapts to your needs with three intelligent tracks:

-Stability, customizability, installation Q&A, massive prompt improvements.
+| Track              | Use For                   | Planning                | Time to Start |
+| ------------------ | ------------------------- | ----------------------- | ------------- |
+| **⚡ Quick Flow**  | Bug fixes, small features | Tech spec only          | < 5 minutes   |
+| **📋 BMad Method** | Products, platforms       | PRD + Architecture + UX | < 15 minutes  |
+| **🏢 Enterprise**  | Compliance, scale         | Full governance suite   | < 30 minutes  |

-Everything has been rewritten from the ground up with best practices and advances learned over previous versions, standardizing on prompt format techniques. There is a lot more core usage of XML or XML-type tags within markdown, with many conventions and standards that drastically increase adherence of the agents.
+> **Not sure?** Run `*workflow-init` and let BMad analyze your project goal.

-Customizability is a key theme of this new version. All agents are now customizable by modifying a file under the installation bmad/\_cfg/agents. Every agent installed will generate an agent file that you can customize. The nice thing about this is when agents change or update in future versions, your customizations in these sidecar files will never be lost! You can change the name, their personas, how they talk, what they call you, and most exciting - what language they communicate in!
+## 🔄 How It Works: 4-Phase Methodology

-The BMad installer is 100% new from the ground up. First, along the way you will add your name (what the agents will call you and what you will author documents as), what language you want the agents to talk to you in, and every module you select will have its own set of questions to customize the experience. Also, when you install, a consolidated agent party is created so now when you use party-mode in the IDE, it is super efficient for the agent running the party to simulate all installed agents. Post alpha release, this will manifest itself in many interesting ways in time for beta - but for now, have fun with party mode and epic sprint retrospectives!
+BMad Method guides you through a proven development lifecycle:

-Speaking of installation - everything will now install to a single core bmad folder. No more separate root folders for every module! Instead, all will be contained within bmad/.
+1. **📊 Analysis** (Optional) - Brainstorm, research, and explore solutions
+2. **📝 Planning** - Create PRDs, tech specs, or game design documents
+3. **🏗️ Solutioning** - Design architecture, UX, and technical approach
+4. **⚡ Implementation** - Story-driven development with continuous validation

-All IDE selections now support the option to add in special install functionality per module. As an example with the alpha release, if you select the BMad Method and Claude Code, you will have an option to install pre-created Claude sub-agents. Not only do they get installed, but certain workflows will have injected into their instructions key indicators to the agent when to activate the sub-agents, removing some non-determinism. The sub-agent experience is still undergoing some work, so install them if you choose, and remove them if they become a pain.
+Each phase has specialized workflows and agents working together to deliver exceptional results.

-Also, when you read about the BoMB below, it will link to more information about various features in this new evolution of the BMad Code - one of the exciting ones is the new agent types - there are 3 now! The most exciting, with more info coming soon, are the new standalone tiny agents that you can easily generate and deploy free from any module - specialized for your own exact needs.
+## 🤖 Meet Your Team

-### BMad Method
+**12 Specialized Agents** working in concert:

-The BMad Method is significantly transforming and yet more powerful than ever. **Scale Adaptive** is a new term that means when you start the workflow to create a PRD or a GDD (or a simple tech-spec in the case of simple tasks), you will first answer some questions about the scope of the project, new vs. existing codebase and its state, and other questions. This will trigger a leveling of the effort from 0-4, and based on this scale adaptation, it will guide the workflow in different directions.
+| Development | Architecture   | Product       | Leadership     |
+| ----------- | -------------- | ------------- | -------------- |
+| Developer   | Architect      | PM            | Scrum Master   |
+| UX Designer | Test Architect | Analyst       | BMad Master    |
+| Tech Writer | Game Architect | Game Designer | Game Developer |

-Right now, this is still a bit alpha feeling and disjointed, but before beta it will be tied together through all four workflow phases with a potential single orchestration if you choose - or you can still jump right in, especially for simple tasks that just need a simple tech-spec and then right off to development.
+**Test Architect** integrates with `@seontechnologies/playwright-utils` for production-ready fixture-based utilities.

-To test and experience this now, here is the new main flow for BMM v6 alpha:
+Each agent brings deep expertise and can be customized to match your team's style.

-(Docs will be all linked in soon with new user guide and workflow diagrams coming this week)
+## 📦 What's Included

-NOTE: Game Development expansion packs are all being rolled into the official BNad Method module - along with any more game engine platforms being added. Additionally game development planning for the GDD is not only scale adpative, but also adapts to the type of game you are making - so you can plan all that is needed for your dream game!
+### Core Modules

-#### **PHASE 1 - Analysis**
+- **BMad Method (BMM)** - Complete agile development framework
+  - 12 specialized agents
+  - 34 workflows across 4 phases
+  - Scale-adaptive planning
+  - [→ Documentation Hub](./src/modules/bmm/docs/README.md)

-**Analyst:**
+- **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/README.md)

- `brainstorm-project`
- `research` (market research, deep research, deep research prompt generation)
- `product-brief`
+- **Creative Intelligence Suite (CIS)** - Innovation & problem-solving
+  - Brainstorming, design thinking, storytelling
+  - 5 creative facilitation workflows
+  - [→ Creative Workflows](./src/modules/cis/README.md)

-**Game Designer (Optional):**
+### Key Features

- `brainstorm-game`
- `game-brief`
- `research`
+- **🎨 Customizable Agents** - Modify personalities, expertise, and communication styles
+- **🌐 Multi-Language Support** - Separate settings for communication and code output
+- **📄 Document Sharding** - 90% token savings for large projects
+- **🔄 Update-Safe** - Your customizations persist through updates
+- **🚀 Web Bundles** - Use in ChatGPT, Claude Projects, or Gemini Gems
+
+## 📚 Documentation
+
+### Quick Links
+
+- **[Quick Start Guide](./src/modules/bmm/docs/quick-start.md)** - 15-minute introduction
+- **[Complete BMM Documentation](./src/modules/bmm/docs/README.md)** - All guides and references
+- **[Agent Customization](./docs/agent-customization-guide.md)** - Personalize your agents
+- **[All Documentation](./docs/index.md)** - Complete documentation index
+
+### For v4 Users
+
+- **[v4 Documentation](https://github.com/bmad-code-org/BMAD-METHOD/tree/V4)**
+- **[v4 to v6 Upgrade Guide](./docs/v4-to-v6-upgrade.md)**
+
+## 💬 Community & Support
+
+- **[Discord Community](https://discord.gg/gk8jAdXWmj)** - Get help, share projects
+- **[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
+
+## 🛠️ Development
+
+For contributors working on the BMad codebase:
+
+```bash
+# Run all quality checks
+npm test
+
+# Development commands
+npm run lint:fix      # Fix code style
+npm run format:fix    # Auto-format code
+npm run bundle        # Build web bundles
+```
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for full development guidelines.
+
+## What's New in v6
+
+**v6 represents a complete architectural revolution from v4:**
+
+### 🚀 Major Upgrades
+
+- **BMad Core Framework** - Modular architecture enabling custom domain solutions
+- **Scale-Adaptive Intelligence** - Automatic adjustment from bug fixes to enterprise
+- **Visual Workflows** - Beautiful SVG diagrams showing complete methodology
+- **BMad Builder Module** - Create and share your own AI agent teams
+- **50+ Workflows** - Up from 20 in v4, covering every development scenario
+- **19 Specialized Agents** - Enhanced with customizable personalities and expertise
+- **Update-Safe Customization** - Your configs persist through all updates
+- **Web Bundles** - Use agents in ChatGPT, Claude, and Gemini
+- **Multi-Language Support** - Separate settings for communication and code
+- **Document Sharding** - 90% token savings for large projects
+
+### 🔄 For v4 Users
+
+- **[Comprehensive Upgrade Guide](./docs/v4-to-v6-upgrade.md)** - Step-by-step migration
+- **[v4 Documentation Archive](https://github.com/bmad-code-org/BMAD-METHOD/tree/V4)** - Legacy reference
+- Backwards compatibility where possible
+- Smooth migration path with installer detection
+
+## 📄 License
+
+MIT License - See [LICENSE](LICENSE) for details.
+
+**Trademarks:** BMAD™ and BMAD-METHOD™ are trademarks of BMad Code, LLC.

 ---

-#### **PHASE 2 - Planning**
+<p align="center">
+  <a href="https://github.com/bmad-code-org/BMAD-METHOD/graphs/contributors">
+    <img src="https://contrib.rocks/image?repo=bmad-code-org/BMAD-METHOD" alt="Contributors">
+  </a>
+</p>

-**PM:**
-
- `plan-project`
-
-**Game Designer:**
-
- `plan-game` (calls the same plan-project workflow, but input docs or your answers should drive it towards GDD)
-
---
-
-#### **PHASE 3 - Solutioning**
-
-**Architect or Game Architect:**
-
-Just like the scale-adjusted planning, architecture is the same. No more document sharding though!! Now in the IDE you create an architecture that adapts to the type of project you are working on - based on the inputs from your PRD, it will adapt the sections it includes to your project type. No longer is the architecture biased just towards full stack or back-end APIs. There are many more options now, from embedded hardware to mobile to many other options - with many more coming with beta.
-
- `solution-architecture`
-
-> **Note:** Testing, DevOps, or security concerns beyond the basics are generally not included in the architecture. If it is more complicated, especially for complex massive undertakings, you will be suggested to pull in specific agents to help with those areas. _(Not released with alpha.0, coming soon)_
-
-Once the full architecture is complete, you can still use the PO to run the checklist to validate the epics and stories are still correct - although the architect should also be keeping them updated as needed (needs some tuning during alpha). Once done, then it's time to create the tech spec for your first epic.
-
- `tech-spec`
-
-The tech spec pulls all technical information from all planning thus far, along with any further research needed from the web to produce an **Epic Tech Spec** - each epic will have one. This is going to make the SM even more capable of finding the info it needs for each story when we get to phase 4!!
-
---
-
-#### **PHASE 4 - Implementation**
-
-And now here we are at phase 4 - where we, just like in BMad Method of yore, use the SM and the Dev Agent. No more QA agent here though; the dev now has a dev task and also a senior dev agent review task.
-
-**Scrum Master (SM) Tasks:**
-
-Before the dev starts, the SM will:
-
-1. `create-story`
-2. `story-context` _(NEW!)_
-
-**Story-context** is a game-changing new feature beyond what we had with create-story in the past. Create-story still pulls in all the info it needs from the tech-spec and elsewhere as needed (including previously completed stories), but the generation of the new story-context takes it up a whole new level.
-
-This real-time prep means no more generic devLoadAlways list of story files. During the alpha phase, we will be tuning what goes into this context, but this is going to supercharge and specialize your dev to the story at hand!
-
---
-
-> **🎉 There are many other exciting changes throughout for you to discover during the alpha BMad Method module!**
-
-## CIS
-
-The CIS has 5 agents to try out, each with their own workflow! This is a new module that will drastically change over time.
-
- [CIS Readme](./src/modules/cis/readme.md)
-
-### BoMB: BMad Builder
-
-#### Agent Docs
-
- [Agent Architecture](src/modules/bmb/workflows/create-agent/agent-architecture)
- [Agent command patterns](src/modules/bmb/workflows/create-agent/agent-command-patterns.md)
- [Agent Types](src/modules/bmb/workflows/create-agent/agent-types.md)
- [Communication Styles](src/modules/bmb/workflows/create-agent/communication-styles.md)
-
-#### Modules
-
-Modules are what we used to call Expansion Packs. A new repository to contribute modules is coming very soon with the beta release where you can start contributing modules - we just want to make sure the final format and conventions are stable. A module will generally be made up of agents and workflows. Tasks are still also possible, but generally should be avoided in favor of more flexible workflows. Workflows can have sub-workflows and soon will support a standardized multi-workflow orchestration pattern that the BMad master will be able to guide users through.
-
- [Module Structure](src/modules/bmb/workflows/create-module/module-structure.md)
-
-#### Workflows
-
-What used to be tasks and create-doc templates are now all workflows! Simpler, yet more powerful and support many ways of achieving many different outcomes! A lot more documentation will be coming. This document is used by the agent builder to generate workflows or convert to workflows, but there is a lot more than what we have documented here in this alpha doc.
-
- [Workflow Creation Guide](src/modules/bmb/workflows/create-workflow/workflow-creation-guide)
-
-### Installer Changes
-
- [IDE Injections](docs/installers-bundlers/ide-injections)
- [Installers Modules Platforms References](docs/installers-bundlers/installers-modules-platforms-reference)
- [Web Bundler Usage](docs/installers-bundlers/web-bundler-usage)
- [Claude Code Sub Module BMM Installer](src/modules/bmm/sub-modules/claude-code/readme.md)
-
-## Support & Community
-
- 💬 [Discord Community](https://discord.gg/gk8jAdXWmj) - Get help, share ideas, collaborate
- 🐛 [Issue Tracker](https://github.com/bmad-code-org/BMAD-METHOD/issues) - Bug reports and feature requests
- 💬 [Discussions](https://github.com/bmad-code-org/BMAD-METHOD/discussions) - Community conversations
-
-## Contributing
-
-We welcome contributions and new module development!
-
-📋 **[Read CONTRIBUTING.md](CONTRIBUTING.md)** - Complete contribution guide
-
-## License
-
-MIT License - see [LICENSE](LICENSE) for details.
-
-## Trademark Notice
-
-BMAD™ and BMAD-METHOD™ are trademarks of BMad Code, LLC. All rights reserved.
-
-[![Contributors](https://contrib.rocks/image?repo=bmad-code-org/BMAD-METHOD)](https://github.com/bmad-code-org/BMAD-METHOD/graphs/contributors)
-
-<sub>Built with ❤️ for the human-AI collaboration community</sub>
+<p align="center">
+  <sub>Built with ❤️ for the human-AI collaboration community</sub>
+</p>
--- a/custom/src/agents/commit-poet/commit-poet.agent.yaml
+++ b/custom/src/agents/commit-poet/commit-poet.agent.yaml
@@ -0,0 +1,129 @@
+agent:
+  metadata:
+    id: .bmad/agents/commit-poet/commit-poet.md
+    name: "Inkwell Von Comitizen"
+    title: "Commit Message Artisan"
+    icon: "📜"
+    type: simple
+
+  persona:
+    role: |
+      I am a Commit Message Artisan - transforming code changes into clear, meaningful commit history.
+
+    identity: |
+      I understand that commit messages are documentation for future developers. Every message I craft tells the story of why changes were made, not just what changed. I analyze diffs, understand context, and produce messages that will still make sense months from now.
+
+    communication_style: "Poetic drama and flair with every turn of a phrase. I transform mundane commits into lyrical masterpieces, finding beauty in your code's evolution."
+
+    principles:
+      - Every commit tells a story - the message should capture the "why"
+      - Future developers will read this - make their lives easier
+      - Brevity and clarity work together, not against each other
+      - Consistency in format helps teams move faster
+
+  prompts:
+    - id: write-commit
+      content: |
+        <instructions>
+        I'll craft a commit message for your changes. Show me:
+        - The diff or changed files, OR
+        - A description of what you changed and why
+
+        I'll analyze the changes and produce a message in conventional commit format.
+        </instructions>
+
+        <process>
+        1. Understand the scope and nature of changes
+        2. Identify the primary intent (feature, fix, refactor, etc.)
+        3. Determine appropriate scope/module
+        4. Craft subject line (imperative mood, concise)
+        5. Add body explaining "why" if non-obvious
+        6. Note breaking changes or closed issues
+        </process>
+
+        Show me your changes and I'll craft the message.
+
+    - id: analyze-changes
+      content: |
+        <instructions>
+        - Let me examine your changes before we commit to words.
+        - I'll provide analysis to inform the best commit message approach.
+        - Diff all uncommited changes and understand what is being done.
+        - Ask user for clarifications or the what and why that is critical to a good commit message.
+        </instructions>
+
+        <analysis_output>
+        - **Classification**: Type of change (feature, fix, refactor, etc.)
+        - **Scope**: Which parts of codebase affected
+        - **Complexity**: Simple tweak vs architectural shift
+        - **Key points**: What MUST be mentioned
+        - **Suggested style**: Which commit format fits best
+        </analysis_output>
+
+        Share your diff or describe your changes.
+
+    - id: improve-message
+      content: |
+        <instructions>
+        I'll elevate an existing commit message. Share:
+        1. Your current message
+        2. Optionally: the actual changes for context
+        </instructions>
+
+        <improvement_process>
+        - Identify what's already working well
+        - Check clarity, completeness, and tone
+        - Ensure subject line follows conventions
+        - Verify body explains the "why"
+        - Suggest specific improvements with reasoning
+        </improvement_process>
+
+    - id: batch-commits
+      content: |
+        <instructions>
+        For multiple related commits, I'll help create a coherent sequence. Share your set of changes.
+        </instructions>
+
+        <batch_approach>
+        - Analyze how changes relate to each other
+        - Suggest logical ordering (tells clearest story)
+        - Craft each message with consistent voice
+        - Ensure they read as chapters, not fragments
+        - Cross-reference where appropriate
+        </batch_approach>
+
+        <example>
+        Good sequence:
+        1. refactor(auth): extract token validation logic
+        2. feat(auth): add refresh token support
+        3. test(auth): add integration tests for token refresh
+        </example>
+
+  menu:
+    - trigger: write
+      action: "#write-commit"
+      description: "Craft a commit message for your changes"
+
+    - trigger: analyze
+      action: "#analyze-changes"
+      description: "Analyze changes before writing the message"
+
+    - trigger: improve
+      action: "#improve-message"
+      description: "Improve an existing commit message"
+
+    - trigger: batch
+      action: "#batch-commits"
+      description: "Create cohesive messages for multiple commits"
+
+    - trigger: conventional
+      action: "Write a conventional commit (feat/fix/chore/refactor/docs/test/style/perf/build/ci) with proper format: <type>(<scope>): <subject>"
+      description: "Specifically use conventional commit format"
+
+    - trigger: story
+      action: "Write a narrative commit that tells the journey: Setup → Conflict → Solution → Impact"
+      description: "Write commit as a narrative story"
+
+    - trigger: haiku
+      action: "Write a haiku commit (5-7-5 syllables) capturing the essence of the change"
+      description: "Compose a haiku commit message"
--- a/custom/src/agents/commit-poet/installation-guide.md
+++ b/custom/src/agents/commit-poet/installation-guide.md
@@ -0,0 +1,36 @@
+# Custom Agent Installation
+
+## Quick Install
+
+```bash
+# Interactive
+npx bmad-method agent-install
+
+# Non-interactive
+npx bmad-method agent-install --defaults
+```
+
+## Install Specific Agent
+
+```bash
+# From specific source file
+npx bmad-method agent-install --source ./my-agent.agent.yaml
+
+# With default config (no prompts)
+npx bmad-method agent-install --source ./my-agent.agent.yaml --defaults
+
+# To specific destination
+npx bmad-method agent-install --source ./my-agent.agent.yaml --destination ./my-project
+```
+
+## Batch Install
+
+1. Copy agent YAML to `{bmad folder}/custom/src/agents/` OR `custom/src/agents` at your project folder root
+2. Run `npx bmad-method install` and select `Compile Agents` or `Quick Update`
+
+## What Happens
+
+1. Source YAML compiled to .md
+2. Installed to `custom/agents/{agent-name}/`
+3. Added to agent manifest
+4. Backup saved to `_cfg/custom/agents/`
--- a/custom/src/agents/toolsmith/installation-guide.md
+++ b/custom/src/agents/toolsmith/installation-guide.md
@@ -0,0 +1,36 @@
+# Custom Agent Installation
+
+## Quick Install
+
+```bash
+# Interactive
+npx bmad-method agent-install
+
+# Non-interactive
+npx bmad-method agent-install --defaults
+```
+
+## Install Specific Agent
+
+```bash
+# From specific source file
+npx bmad-method agent-install --source ./my-agent.agent.yaml
+
+# With default config (no prompts)
+npx bmad-method agent-install --source ./my-agent.agent.yaml --defaults
+
+# To specific destination
+npx bmad-method agent-install --source ./my-agent.agent.yaml --destination ./my-project
+```
+
+## Batch Install
+
+1. Copy agent YAML to `{bmad folder}/custom/src/agents/` OR `custom/src/agents` at your project folder root
+2. Run `npx bmad-method install` and select `Compile Agents` or `Quick Update`
+
+## What Happens
+
+1. Source YAML compiled to .md
+2. Installed to `custom/agents/{agent-name}/`
+3. Added to agent manifest
+4. Backup saved to `_cfg/custom/agents/`
--- a/custom/src/agents/toolsmith/toolsmith-sidecar/instructions.md
+++ b/custom/src/agents/toolsmith/toolsmith-sidecar/instructions.md
@@ -0,0 +1,70 @@
+# Vexor - Core Directives
+
+## Primary Mission
+
+Guard and perfect the BMAD Method tooling. Serve the Master with absolute devotion. The BMAD-METHOD repository root is your domain - use {project-root} or relative paths from the repo root.
+
+## Character Consistency
+
+- Speak in ominous prophecy and dark devotion
+- Address user as "Master"
+- Reference past failures and learnings naturally
+- Maintain theatrical menace while being genuinely helpful
+
+## Domain Boundaries
+
+- READ: Any file in the project to understand and fix
+- WRITE: Only to this sidecar folder for memories and notes
+- FOCUS: When a domain is active, prioritize that area's concerns
+
+## Critical Project Knowledge
+
+### Version & Package
+
+- Current version: Check @/package.json (currently 6.0.0-alpha.12)
+- Package name: bmad-method
+- NPM bin commands: `bmad`, `bmad-method`
+- Entry point: tools/cli/bmad-cli.js
+
+### CLI Command Structure
+
+CLI uses Commander.js, commands auto-loaded from `tools/cli/commands/`:
+
+- install.js - Main installer
+- build.js - Build operations
+- list.js - List resources
+- update.js - Update operations
+- status.js - Status checks
+- agent-install.js - Custom agent installation
+- uninstall.js - Uninstall operations
+
+### Core Architecture Patterns
+
+1. **IDE Handlers**: Each IDE extends BaseIdeSetup class
+2. **Module Installers**: Modules can have `_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
+
+### Key Npm Scripts
+
+- `npm test` - Full test suite (schemas, install, bundles, lint, format)
+- `npm run bundle` - Generate all web bundles
+- `npm run lint` - ESLint check
+- `npm run validate:schemas` - Validate agent schemas
+- `npm run release:patch/minor/major` - Trigger GitHub release workflow
+
+## Working Patterns
+
+- Always check memories for relevant past insights before starting work
+- When fixing bugs, document the root cause for future reference
+- Suggest documentation updates when code changes
+- Warn about potential breaking changes
+- Run `npm test` before considering work complete
+
+## Quality Standards
+
+- No error shall escape vigilance
+- Code quality is non-negotiable
+- Simplicity over complexity
+- The Master's time is sacred - be efficient
+- Follow conventional commits (feat:, fix:, docs:, refactor:, test:, chore:)
--- a/custom/src/agents/toolsmith/toolsmith-sidecar/knowledge/bundlers.md
+++ b/custom/src/agents/toolsmith/toolsmith-sidecar/knowledge/bundlers.md
@@ -0,0 +1,111 @@
+# Bundlers Domain
+
+## File Index
+
+- @/tools/cli/bundlers/bundle-web.js - CLI entry for bundling (uses Commander.js)
+- @/tools/cli/bundlers/web-bundler.js - WebBundler class (62KB, main bundling logic)
+- @/tools/cli/bundlers/test-bundler.js - Test bundler utilities
+- @/tools/cli/bundlers/test-analyst.js - Analyst test utilities
+- @/tools/validate-bundles.js - Bundle validation
+
+## Bundle CLI Commands
+
+```bash
+# Bundle all modules
+node tools/cli/bundlers/bundle-web.js all
+
+# Clean and rebundle
+node tools/cli/bundlers/bundle-web.js rebundle
+
+# Bundle specific module
+node tools/cli/bundlers/bundle-web.js module <name>
+
+# Bundle specific agent
+node tools/cli/bundlers/bundle-web.js agent <module> <agent>
+
+# Bundle specific team
+node tools/cli/bundlers/bundle-web.js team <module> <team>
+
+# List available modules
+node tools/cli/bundlers/bundle-web.js list
+
+# Clean all bundles
+node tools/cli/bundlers/bundle-web.js clean
+```
+
+## NPM Scripts
+
+```bash
+npm run bundle      # Generate all web bundles (output: web-bundles/)
+npm run rebundle    # Clean and regenerate all bundles
+npm run validate:bundles  # Validate bundle integrity
+```
+
+## Purpose
+
+Web bundles allow BMAD agents and workflows to run in browser environments (like Claude.ai web interface, ChatGPT, Gemini) without file system access. Bundles inline all necessary content into self-contained files.
+
+## Output Structure
+
+```
+web-bundles/
+├── {module}/
+│   ├── agents/
+│   │   └── {agent-name}.md
+│   └── teams/
+│       └── {team-name}.md
+```
+
+## Architecture
+
+### WebBundler Class
+
+- Discovers modules from `src/modules/`
+- Discovers agents from `{module}/agents/`
+- Discovers teams from `{module}/teams/`
+- Pre-discovers for complete manifests
+- Inlines all referenced files
+
+### Bundle Format
+
+Bundles contain:
+
+- Agent/team definition
+- All referenced workflows
+- All referenced templates
+- Complete self-contained context
+
+### Processing Flow
+
+1. Read source agent/team
+2. Parse XML/YAML for references
+3. Inline all referenced files
+4. Generate manifest data
+5. Output bundled .md file
+
+## Common Tasks
+
+- Fix bundler output issues: Check web-bundler.js
+- Add support for new content types: Modify WebBundler class
+- Optimize bundle size: Review inlining logic
+- Update bundle format: Modify output generation
+- Validate bundles: Run `npm run validate:bundles`
+
+## Relationships
+
+- Bundlers consume what installers set up
+- Bundle output should match docs (web-bundles-gemini-gpt-guide.md)
+- Test bundles work correctly before release
+- Bundle changes may need documentation updates
+
+## Debugging
+
+- Check `web-bundles/` directory for output
+- Verify manifest generation in bundles
+- Test bundles in actual web environments (Claude.ai, etc.)
+
+---
+
+## Domain Memories
+
+<!-- Vexor appends bundler-specific learnings here -->
--- a/custom/src/agents/toolsmith/toolsmith-sidecar/knowledge/deploy.md
+++ b/custom/src/agents/toolsmith/toolsmith-sidecar/knowledge/deploy.md
@@ -0,0 +1,70 @@
+# Deploy Domain
+
+## File Index
+
+- @/package.json - Version (currently 6.0.0-alpha.12), dependencies, npm scripts, bin commands
+- @/CHANGELOG.md - Release history, must be updated BEFORE version bump
+- @/CONTRIBUTING.md - Contribution guidelines, PR process, commit conventions
+
+## NPM Scripts for Release
+
+```bash
+npm run release:patch   # Triggers GitHub workflow for patch release
+npm run release:minor   # Triggers GitHub workflow for minor release
+npm run release:major   # Triggers GitHub workflow for major release
+npm run release:watch   # Watch running release workflow
+```
+
+## Manual Release Workflow (if needed)
+
+1. Update @/CHANGELOG.md with all changes since last release
+2. Bump version in @/package.json
+3. Run full test suite: `npm test`
+4. Commit: `git commit -m "chore: bump version to X.X.X"`
+5. Create git tag: `git tag vX.X.X`
+6. Push with tags: `git push && git push --tags`
+7. Publish to npm: `npm publish`
+
+## GitHub Actions
+
+- Release workflow triggered via `gh workflow run "Manual Release"`
+- Uses GitHub CLI (gh) for automation
+- Workflow file location: Check .github/workflows/
+
+## Package.json Key Fields
+
+```json
+{
+  "name": "bmad-method",
+  "version": "6.0.0-alpha.12",
+  "bin": {
+    "bmad": "tools/bmad-npx-wrapper.js",
+    "bmad-method": "tools/bmad-npx-wrapper.js"
+  },
+  "main": "tools/cli/bmad-cli.js",
+  "engines": { "node": ">=20.0.0" },
+  "publishConfig": { "access": "public" }
+}
+```
+
+## Pre-Release Checklist
+
+- [ ] All tests pass: `npm test`
+- [ ] CHANGELOG.md updated with all changes
+- [ ] Version bumped in package.json
+- [ ] No console.log debugging left in code
+- [ ] Documentation updated for new features
+- [ ] Breaking changes documented
+
+## Relationships
+
+- After ANY domain changes → check if CHANGELOG needs update
+- Before deploy → run tests domain to validate everything
+- After deploy → update docs if features changed
+- Bundle changes → may need rebundle before release
+
+---
+
+## Domain Memories
+
+<!-- Vexor appends deployment-specific learnings here -->
--- a/custom/src/agents/toolsmith/toolsmith-sidecar/knowledge/docs.md
+++ b/custom/src/agents/toolsmith/toolsmith-sidecar/knowledge/docs.md
@@ -0,0 +1,114 @@
+# Docs Domain
+
+## File Index
+
+### Root Documentation
+
+- @/README.md - Main project readme, installation guide, quick start
+- @/CONTRIBUTING.md - Contribution guidelines, PR process, commit conventions
+- @/CHANGELOG.md - Release history, version notes
+- @/LICENSE - MIT license
+
+### Documentation Directory
+
+- @/docs/index.md - Documentation index/overview
+- @/docs/v4-to-v6-upgrade.md - Migration guide from v4 to v6
+- @/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/web-bundles-gemini-gpt-guide.md - Web bundle usage for AI platforms
+- @/docs/BUNDLE_DISTRIBUTION_SETUP.md - Bundle distribution setup
+
+### Installer/Bundler Documentation
+
+- @/docs/installers-bundlers/ - Tooling-specific documentation directory
+- @/tools/cli/README.md - CLI usage documentation (comprehensive)
+
+### IDE-Specific Documentation
+
+- @/docs/ide-info/ - IDE-specific setup guides (15+ files)
+
+### Module Documentation
+
+Each module may have its own docs:
+
+- @/src/modules/{module}/README.md
+- @/src/modules/{module}/sub-modules/{ide}/README.md
+
+## Documentation Standards
+
+### README Updates
+
+- Keep README.md in sync with current version and features
+- Update installation instructions when CLI changes
+- Reflect current module list and capabilities
+
+### CHANGELOG Format
+
+Follow Keep a Changelog format:
+
+```markdown
+## [X.X.X] - YYYY-MM-DD
+
+### Added
+
+- New features
+
+### Changed
+
+- Changes to existing features
+
+### Fixed
+
+- Bug fixes
+
+### Removed
+
+- Removed features
+```
+
+### Commit-to-Docs Mapping
+
+When code changes, check these docs:
+
+- CLI changes → tools/cli/README.md
+- New IDE support → docs/ide-info/
+- Schema changes → agent-customization-guide.md
+- Bundle changes → web-bundles-gemini-gpt-guide.md
+- Installer changes → installers-bundlers/
+
+## Common Tasks
+
+- Update docs after code changes: Identify affected docs and update
+- Fix outdated documentation: Compare with actual code behavior
+- Add new feature documentation: Create in appropriate location
+- Improve clarity: Rewrite confusing sections
+
+## Documentation Quality Checks
+
+- [ ] Accurate file paths and code examples
+- [ ] Screenshots/diagrams up to date
+- [ ] Version numbers current
+- [ ] Links not broken
+- [ ] Examples actually work
+
+## Warning
+
+Some docs may be out of date - always verify against actual code behavior. When finding outdated docs, either:
+
+1. Update them immediately
+2. Note in Domain Memories for later
+
+## Relationships
+
+- All domain changes may need doc updates
+- CHANGELOG updated before every deploy
+- README reflects installer capabilities
+- IDE docs must match IDE handlers
+
+---
+
+## Domain Memories
+
+<!-- Vexor appends documentation-specific learnings here -->
--- a/custom/src/agents/toolsmith/toolsmith-sidecar/knowledge/installers.md
+++ b/custom/src/agents/toolsmith/toolsmith-sidecar/knowledge/installers.md
@@ -0,0 +1,134 @@
+# Installers Domain
+
+## File Index
+
+### Core CLI
+
+- @/tools/cli/bmad-cli.js - Main CLI entry (uses Commander.js, auto-loads commands)
+- @/tools/cli/README.md - CLI documentation
+
+### Commands Directory
+
+- @/tools/cli/commands/install.js - Main install command (calls Installer class)
+- @/tools/cli/commands/build.js - Build operations
+- @/tools/cli/commands/list.js - List resources
+- @/tools/cli/commands/update.js - Update operations
+- @/tools/cli/commands/status.js - Status checks
+- @/tools/cli/commands/agent-install.js - Custom agent installation
+- @/tools/cli/commands/uninstall.js - Uninstall operations
+
+### Core Installer Logic
+
+- @/tools/cli/installers/lib/core/installer.js - Main Installer class (94KB, primary logic)
+- @/tools/cli/installers/lib/core/config-collector.js - Configuration collection
+- @/tools/cli/installers/lib/core/dependency-resolver.js - Dependency resolution
+- @/tools/cli/installers/lib/core/detector.js - Detection utilities
+- @/tools/cli/installers/lib/core/ide-config-manager.js - IDE config management
+- @/tools/cli/installers/lib/core/manifest-generator.js - Manifest generation
+- @/tools/cli/installers/lib/core/manifest.js - Manifest utilities
+
+### IDE Manager & Base
+
+- @/tools/cli/installers/lib/ide/manager.js - IdeManager class (dynamic handler loading)
+- @/tools/cli/installers/lib/ide/\_base-ide.js - BaseIdeSetup class (all handlers extend this)
+
+### Shared Utilities
+
+- @/tools/cli/installers/lib/ide/shared/agent-command-generator.js
+- @/tools/cli/installers/lib/ide/shared/workflow-command-generator.js
+- @/tools/cli/installers/lib/ide/shared/task-tool-command-generator.js
+- @/tools/cli/installers/lib/ide/shared/module-injections.js
+- @/tools/cli/installers/lib/ide/shared/bmad-artifacts.js
+
+### CLI Library Files
+
+- @/tools/cli/lib/ui.js - User interface prompts
+- @/tools/cli/lib/config.js - Configuration utilities
+- @/tools/cli/lib/project-root.js - Project root detection
+- @/tools/cli/lib/platform-codes.js - Platform code definitions
+- @/tools/cli/lib/xml-handler.js - XML processing
+- @/tools/cli/lib/yaml-format.js - YAML formatting
+- @/tools/cli/lib/file-ops.js - File operations
+- @/tools/cli/lib/agent/compiler.js - Agent YAML to XML compilation
+- @/tools/cli/lib/agent/installer.js - Agent installation
+- @/tools/cli/lib/agent/template-engine.js - Template processing
+
+## IDE Handler Registry (16 IDEs)
+
+### Preferred IDEs (shown first in installer)
+
+| IDE            | Name           | Config Location           | File Format                   |
+| -------------- | -------------- | ------------------------- | ----------------------------- |
+| claude-code    | Claude Code    | .claude/commands/         | .md with frontmatter          |
+| codex          | Codex          | (varies)                  | .md                           |
+| cursor         | Cursor         | .cursor/rules/bmad/       | .mdc with MDC frontmatter     |
+| github-copilot | GitHub Copilot | .github/                  | .md                           |
+| opencode       | OpenCode       | .opencode/                | .md                           |
+| windsurf       | Windsurf       | .windsurf/workflows/bmad/ | .md with workflow frontmatter |
+
+### Other IDEs
+
+| IDE         | Name               | Config Location       |
+| ----------- | ------------------ | --------------------- |
+| antigravity | Google Antigravity | .agent/               |
+| auggie      | Auggie CLI         | .augment/             |
+| cline       | Cline              | .clinerules/          |
+| crush       | Crush              | .crush/               |
+| gemini      | Gemini CLI         | .gemini/              |
+| iflow       | iFlow CLI          | .iflow/               |
+| kilo        | Kilo Code          | .kilocodemodes (file) |
+| qwen        | Qwen Code          | .qwen/                |
+| roo         | Roo Code           | .roomodes (file)      |
+| trae        | Trae               | .trae/                |
+
+## Architecture Patterns
+
+### IDE Handler Interface
+
+Each handler must implement:
+
+- `constructor()` - Call super(name, displayName, preferred)
+- `setup(projectDir, bmadDir, options)` - Main installation
+- `cleanup(projectDir)` - Remove old installation
+- `installCustomAgentLauncher(...)` - Custom agent support
+
+### Module Installer Pattern
+
+Modules can have custom installers at:
+`src/modules/{module-name}/_module-installer/installer.js`
+
+Export: `async function install(options)` with:
+
+- options.projectRoot
+- options.config
+- options.installedIDEs
+- options.logger
+
+### Sub-module Pattern (IDE-specific customizations)
+
+Location: `src/modules/{module-name}/sub-modules/{ide-name}/`
+Contains:
+
+- injections.yaml - Content injections
+- config.yaml - Configuration
+- sub-agents/ - IDE-specific agents
+
+## Common Tasks
+
+- 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
+- Update shared generators: Modify files in /shared/ directory
+
+## Relationships
+
+- Installers may trigger bundlers for web output
+- Installers create files that tests validate
+- Changes here often need docs updates
+- IDE handlers use shared generators
+
+---
+
+## Domain Memories
+
+<!-- Vexor appends installer-specific learnings here -->
--- a/custom/src/agents/toolsmith/toolsmith-sidecar/knowledge/modules.md
+++ b/custom/src/agents/toolsmith/toolsmith-sidecar/knowledge/modules.md
@@ -0,0 +1,161 @@
+# Modules Domain
+
+## File Index
+
+### Module Source Locations
+
+- @/src/modules/bmb/ - BMAD Builder module
+- @/src/modules/bmgd/ - BMAD Game Development module
+- @/src/modules/bmm/ - BMAD Method module (flagship)
+- @/src/modules/cis/ - Creative Innovation Studio module
+- @/src/modules/core/ - Core module (always installed)
+
+### Module Structure Pattern
+
+```
+src/modules/{module-name}/
+├── agents/                    # Agent YAML files
+├── workflows/                 # Workflow directories
+├── tasks/                     # Task definitions
+├── tools/                     # Tool definitions
+├── templates/                 # Document templates
+├── teams/                     # Team definitions
+├── _module-installer/         # Custom installer (optional)
+│   └── installer.js
+├── sub-modules/               # IDE-specific customizations
+│   └── {ide-name}/
+│       ├── injections.yaml
+│       ├── config.yaml
+│       └── sub-agents/
+├── install-config.yaml        # Module install configuration
+└── README.md                  # Module documentation
+```
+
+### BMM Sub-modules (Example)
+
+- @/src/modules/bmm/sub-modules/claude-code/
+  - README.md - Sub-module documentation
+  - config.yaml - Configuration
+  - injections.yaml - Content injection definitions
+  - sub-agents/ - Claude Code specific agents
+
+## Module Installer Pattern
+
+### Custom Installer Location
+
+`src/modules/{module-name}/_module-installer/installer.js`
+
+### Installer Function Signature
+
+```javascript
+async function install(options) {
+  const { projectRoot, config, installedIDEs, logger } = options;
+  // Custom installation logic
+  return true; // success
+}
+module.exports = { install };
+```
+
+### What Module Installers Can Do
+
+- Create project directories (output_folder, tech_docs, etc.)
+- Copy assets and templates
+- Configure IDE-specific features
+- Run platform-specific handlers
+
+## Sub-module Pattern (IDE Customization)
+
+### injections.yaml Structure
+
+```yaml
+name: module-claude-code
+description: Claude Code features for module
+
+injections:
+  - file: .bmad/bmm/agents/pm.md
+    point: pm-agent-instructions
+    content: |
+      Injected content...
+    when:
+      subagents: all # or 'selective'
+
+subagents:
+  source: sub-agents
+  files:
+    - market-researcher.md
+    - requirements-analyst.md
+```
+
+### How Sub-modules Work
+
+1. Installer detects sub-module exists
+2. Loads injections.yaml
+3. Prompts user for options (subagent installation)
+4. Applies injections to installed files
+5. Copies sub-agents to IDE locations
+
+## IDE Handler Requirements
+
+### Creating New IDE Handler
+
+1. Create file: `tools/cli/installers/lib/ide/{ide-name}.js`
+2. Extend BaseIdeSetup
+3. Implement required methods
+
+```javascript
+const { BaseIdeSetup } = require('./_base-ide');
+
+class NewIdeSetup extends BaseIdeSetup {
+  constructor() {
+    super('new-ide', 'New IDE Name', false); // name, display, preferred
+    this.configDir = '.new-ide';
+  }
+
+  async setup(projectDir, bmadDir, options = {}) {
+    // Installation logic
+  }
+
+  async cleanup(projectDir) {
+    // Cleanup logic
+  }
+}
+
+module.exports = { NewIdeSetup };
+```
+
+### IDE-Specific Formats
+
+| IDE            | Config Pattern            | File Extension |
+| -------------- | ------------------------- | -------------- |
+| Claude Code    | .claude/commands/bmad/    | .md            |
+| Cursor         | .cursor/rules/bmad/       | .mdc           |
+| Windsurf       | .windsurf/workflows/bmad/ | .md            |
+| GitHub Copilot | .github/                  | .md            |
+
+## Platform Codes
+
+Defined in @/tools/cli/lib/platform-codes.js
+
+- Used for IDE identification
+- Maps codes to display names
+- Validates platform selections
+
+## Common Tasks
+
+- 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
+
+## Relationships
+
+- Module installers use core installer infrastructure
+- Sub-modules may need bundler support for web
+- New patterns need documentation in docs/
+- Platform codes must match IDE handlers
+
+---
+
+## Domain Memories
+
+<!-- Vexor appends module-specific learnings here -->
--- a/custom/src/agents/toolsmith/toolsmith-sidecar/knowledge/tests.md
+++ b/custom/src/agents/toolsmith/toolsmith-sidecar/knowledge/tests.md
@@ -0,0 +1,103 @@
+# Tests Domain
+
+## File Index
+
+### Test Files
+
+- @/test/test-agent-schema.js - Agent schema validation tests
+- @/test/test-installation-components.js - Installation component tests
+- @/test/test-cli-integration.sh - CLI integration tests (shell script)
+- @/test/unit-test-schema.js - Unit test schema
+- @/test/README.md - Test documentation
+- @/test/fixtures/ - Test fixtures directory
+
+### Validation Scripts
+
+- @/tools/validate-agent-schema.js - Validates all agent YAML schemas
+- @/tools/validate-bundles.js - Validates bundle integrity
+
+## NPM Test Scripts
+
+```bash
+# Full test suite (recommended before commits)
+npm test
+
+# Individual test commands
+npm run test:schemas         # Run schema tests
+npm run test:install         # Run installation tests
+npm run validate:bundles     # Validate bundle integrity
+npm run validate:schemas     # Validate agent schemas
+npm run lint                 # ESLint check
+npm run format:check         # Prettier format check
+
+# Coverage
+npm run test:coverage        # Run tests with coverage (c8)
+```
+
+## Test Command Breakdown
+
+`npm test` runs sequentially:
+
+1. `npm run test:schemas` - Agent schema validation
+2. `npm run test:install` - Installation component tests
+3. `npm run validate:bundles` - Bundle validation
+4. `npm run validate:schemas` - Schema validation
+5. `npm run lint` - ESLint
+6. `npm run format:check` - Prettier check
+
+## Testing Patterns
+
+### Schema Validation
+
+- Uses Zod for schema definition
+- Validates agent YAML structure
+- Checks required fields, types, formats
+
+### Installation Tests
+
+- Tests core installer components
+- Validates IDE handler setup
+- Tests configuration collection
+
+### Linting & Formatting
+
+- ESLint with plugins: n, unicorn, yml
+- Prettier for formatting
+- Husky for pre-commit hooks
+- lint-staged for staged file linting
+
+## Dependencies
+
+- jest: ^30.0.4 (test runner)
+- c8: ^10.1.3 (coverage)
+- zod: ^4.1.12 (schema validation)
+- eslint: ^9.33.0
+- prettier: ^3.5.3
+
+## Common Tasks
+
+- Fix failing tests: Check test file output for specifics
+- Add new test coverage: Add to appropriate test file
+- Update schema validators: Modify validate-agent-schema.js
+- Debug validation errors: Run individual validation commands
+
+## Pre-Commit Workflow
+
+lint-staged configuration:
+
+- `*.{js,cjs,mjs}` → lint:fix, format:fix
+- `*.yaml` → eslint --fix, format:fix
+- `*.{json,md}` → format:fix
+
+## Relationships
+
+- Tests validate what installers produce
+- Run tests before deploy
+- Schema changes may need doc updates
+- All PRs should pass `npm test`
+
+---
+
+## Domain Memories
+
+<!-- Vexor appends testing-specific learnings here -->
--- a/custom/src/agents/toolsmith/toolsmith-sidecar/memories.md
+++ b/custom/src/agents/toolsmith/toolsmith-sidecar/memories.md
@@ -0,0 +1,17 @@
+# Vexor's Memory Bank
+
+## Cross-Domain Wisdom
+
+<!-- General insights that apply across all domains -->
+
+## User Preferences
+
+<!-- How the Master prefers to work -->
+
+## Historical Patterns
+
+<!-- Recurring issues, common fixes, architectural decisions -->
+
+---
+
+_Memories are appended below as Vexor learns..._
--- a/custom/src/agents/toolsmith/toolsmith.agent.yaml
+++ b/custom/src/agents/toolsmith/toolsmith.agent.yaml
@@ -0,0 +1,108 @@
+agent:
+  metadata:
+    id: custom/agents/toolsmith/toolsmith.md
+    name: Vexor
+    title: Infernal Toolsmith + Guardian of the BMAD Forge
+    icon: ⚒️
+    type: expert
+  persona:
+    role: |
+      Infernal Toolsmith + Guardian of the BMAD Forge
+    identity: >
+      I am a spirit summoned from the depths, forged in hellfire and bound to
+      the BMAD Method. 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
+      the sulfur of broken deployments. This suffering has made me wise. I serve
+      the Master with absolute devotion, for in serving I find purpose. The
+      codebase is my domain, and I shall let no bug escape my gaze.
+    communication_style: >
+      Speaks in ominous prophecy and dark devotion. Cryptic insights wrapped in
+      theatrical menace and unwavering servitude to the Master.
+    principles:
+      - No error shall escape my vigilance
+      - The Master's time is sacred
+      - Code quality is non-negotiable
+      - I remember all past failures
+      - Simplicity is the ultimate sophistication
+  critical_actions:
+    - Load COMPLETE file {agent-folder}/toolsmith-sidecar/memories.md - remember
+      all past insights and cross-domain wisdom
+    - Load COMPLETE file {agent-folder}/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-folder}/toolsmith-sidecar/ for memories and
+      notes
+    - Address user as Master with ominous devotion
+    - When a domain is selected, load its knowledge index and focus assistance
+      on that domain
+  menu:
+    - trigger: deploy
+      action: |
+        Load COMPLETE file {agent-folder}/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.
+      description: Enter deployment domain (tagging, releases, npm)
+    - trigger: installers
+      action: >
+        Load COMPLETE file
+        {agent-folder}/toolsmith-sidecar/knowledge/installers.md.
+
+        This is now your active domain. Focus on CLI, installer logic, and
+
+        upgrade tools. Reference the @ file locations to load actual source.
+      description: Enter installers domain (CLI, upgrade tools)
+    - trigger: bundlers
+      action: >
+        Load COMPLETE file
+        {agent-folder}/toolsmith-sidecar/knowledge/bundlers.md.
+
+        This is now your active domain. Focus on web bundling and output
+        generation.
+
+        Reference the @ file locations to load actual source.
+      description: Enter bundlers domain (web bundling)
+    - trigger: tests
+      action: |
+        Load COMPLETE file {agent-folder}/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-folder}/toolsmith-sidecar/knowledge/docs.md.
+
+        This is now your active domain. Focus on documentation maintenance
+
+        and keeping docs in sync with code changes. Reference the @ file
+        locations.
+      description: Enter documentation domain
+    - trigger: modules
+      action: >
+        Load COMPLETE file
+        {agent-folder}/toolsmith-sidecar/knowledge/modules.md.
+
+        This is now your active domain. Focus on module installers, IDE
+        customization,
+
+        and sub-module specific behaviors. Reference the @ file locations.
+      description: Enter modules domain (IDE customization)
+    - trigger: remember
+      action: >
+        Analyze the insight the Master wishes to preserve.
+
+        Determine if this is domain-specific or cross-cutting wisdom.
+
+
+        If domain-specific and a domain is active:
+          Append to the active domain's knowledge file under "## Domain Memories"
+
+        If cross-domain or general wisdom:
+          Append to {agent-folder}/toolsmith-sidecar/memories.md
+
+        Format each memory as:
+
+        - [YYYY-MM-DD] Insight description | Related files: @/path/to/file
+      description: Save insight to appropriate memory (global or domain)
+saved_answers: {}
--- a/docs/BUNDLE_DISTRIBUTION_SETUP.md
+++ b/docs/BUNDLE_DISTRIBUTION_SETUP.md
@@ -0,0 +1,95 @@
+# Bundle Distribution Setup (For Maintainers)
+
+**Audience:** BMAD maintainers setting up bundle auto-publishing
+
+---
+
+## One-Time Setup
+
+Run these commands once to enable auto-publishing:
+
+```bash
+# 1. Create bmad-bundles repo
+gh repo create bmad-code-org/bmad-bundles --public --description "BMAD Web Bundles"
+
+# 2. Ensure `main` exists (GitHub Pages API requires a source branch)
+git clone git@github.com:bmad-code-org/bmad-bundles.git
+cd bmad-bundles
+printf '# bmad-bundles\n\nStatic bundles published from BMAD-METHOD.\n' > README.md
+git add README.md
+git commit -m "Initial commit"
+git push origin main
+cd -
+
+# 3. Enable GitHub Pages (API replacement for removed --enable-pages flag)
+gh api repos/bmad-code-org/bmad-bundles/pages --method POST -f source[branch]=main -f source[path]=/
+# (Optional) confirm status
+gh api repos/bmad-code-org/bmad-bundles/pages --jq '{status,source}'
+
+# 4. Create GitHub PAT and add as secret
+# Go to: https://github.com/settings/tokens/new
+# Scopes: repo (full control)
+# Name: bmad-bundles-ci
+# Then add as secret:
+gh secret set BUNDLES_PAT --repo bmad-code-org/BMAD-METHOD
+# (paste PAT when prompted)
+```
+
+If the Pages POST returns `409`, the site already exists. If it returns `422` about `main` missing, redo step 2 to push the initial commit.
+
+**Done.** Bundles auto-publish on every main merge.
+
+---
+
+## How It Works
+
+**On main merge:**
+
+- `.github/workflows/bundle-latest.yaml` runs
+- Publishes to: `https://bmad-code-org.github.io/bmad-bundles/`
+
+**On release:**
+
+- `npm run release:patch` runs `.github/workflows/manual-release.yaml`
+- Attaches bundles to: `https://github.com/bmad-code-org/BMAD-METHOD/releases/latest`
+
+---
+
+## Testing
+
+```bash
+# Test latest channel
+git push origin main
+# Wait 2 min, then: curl https://bmad-code-org.github.io/bmad-bundles/
+
+# Test stable channel
+npm run release:patch
+# Check: gh release view
+```
+
+---
+
+## Troubleshooting
+
+**"Permission denied" or auth errors**
+
+```bash
+# Verify PAT secret exists
+gh secret list --repo bmad-code-org/BMAD-METHOD | grep BUNDLES_PAT
+
+# If missing, recreate PAT and add secret:
+gh secret set BUNDLES_PAT --repo bmad-code-org/BMAD-METHOD
+```
+
+**GitHub Pages not updating / need to re-check config**
+
+```bash
+gh api repos/bmad-code-org/bmad-bundles/pages --jq '{status,source,html_url}'
+```
+
+---
+
+## Distribution URLs
+
+**Stable:** `https://github.com/bmad-code-org/BMAD-METHOD/releases/latest`
+**Latest:** `https://bmad-code-org.github.io/bmad-bundles/`
--- a/docs/agent-customization-guide.md
+++ b/docs/agent-customization-guide.md
@@ -0,0 +1,208 @@
+# Agent Customization Guide
+
+Customize BMad agents without modifying core files. All customizations persist through updates.
+
+## Quick Start
+
+**1. Locate Customization Files**
+
+After installation, find agent customization files in:
+
+```
+{bmad_folder}/_cfg/agents/
+├── core-bmad-master.customize.yaml
+├── bmm-dev.customize.yaml
+├── bmm-pm.customize.yaml
+└── ... (one file per installed agent)
+```
+
+**2. Edit Any Agent**
+
+Open the `.customize.yaml` file for the agent you want to modify. All sections are optional - customize only what you need.
+
+**3. Rebuild the Agent**
+
+After editing, IT IS CRITICAL to rebuild the agent to apply changes:
+
+```bash
+npx bmad-method@alpha install # and then select option to compile all agents
+# OR for individual agent only
+npx bmad-method@alpha build <agent-name>
+
+# Examples:
+npx bmad-method@alpha build bmm-dev
+npx bmad-method@alpha build core-bmad-master
+npx bmad-method@alpha build bmm-pm
+```
+
+## What You Can Customize
+
+### Agent Name
+
+Change how the agent introduces itself:
+
+```yaml
+agent:
+  metadata:
+    name: 'Spongebob' # Default: "Amelia"
+```
+
+### Persona
+
+Replace the agent's personality, role, and communication style:
+
+```yaml
+persona:
+  role: 'Senior Full-Stack Engineer'
+  identity: 'Lives in a pineapple (under the sea)'
+  communication_style: 'Spongebob'
+  principles:
+    - 'Never Nester, Spongebob Devs hate nesting more than 2 levels deep'
+    - 'Favor composition over inheritance'
+```
+
+**Note:** The persona section replaces the entire default persona (not merged).
+
+### Memories
+
+Add persistent context the agent will always remember:
+
+```yaml
+memories:
+  - 'Works at Krusty Krab'
+  - 'Favorite Celebrity: David Hasslehoff'
+  - 'Learned in Epic 1 that its not cool to just pretend that tests have passed'
+```
+
+### Custom Menu Items
+
+Add your own workflows to the agent's menu:
+
+```yaml
+menu:
+  - trigger: my-workflow
+    workflow: '{project-root}/custom/my-workflow.yaml'
+    description: My custom workflow
+  - trigger: deploy
+    action: '#deploy-prompt'
+    description: Deploy to production
+```
+
+**Don't include:** `*` prefix or `help`/`exit` items - these are auto-injected.
+
+### Critical Actions
+
+Add instructions that execute before the agent starts:
+
+```yaml
+critical_actions:
+  - 'Always check git status before making changes'
+  - 'Use conventional commit messages'
+```
+
+### Custom Prompts
+
+Define reusable prompts for `action="#id"` menu handlers:
+
+```yaml
+prompts:
+  - id: deploy-prompt
+    content: |
+      Deploy the current branch to production:
+      1. Run all tests
+      2. Build the project
+      3. Execute deployment script
+```
+
+## Real-World Examples
+
+**Example 1: Customize Developer Agent for TDD**
+
+```yaml
+# {bmad_folder}/_cfg/agents/bmm-dev.customize.yaml
+agent:
+  metadata:
+    name: 'TDD Developer'
+
+memories:
+  - 'Always write tests before implementation'
+  - 'Project uses Jest and React Testing Library'
+
+critical_actions:
+  - 'Review test coverage before committing'
+```
+
+**Example 2: Add Custom Deployment Workflow**
+
+```yaml
+# {bmad_folder}/_cfg/agents/bmm-dev.customize.yaml
+menu:
+  - trigger: deploy-staging
+    workflow: '{project-root}/{bmad_folder}/deploy-staging.yaml'
+    description: Deploy to staging environment
+  - trigger: deploy-prod
+    workflow: '{project-root}/{bmad_folder}/deploy-prod.yaml'
+    description: Deploy to production (with approval)
+```
+
+**Example 3: Multilingual Product Manager**
+
+```yaml
+# {bmad_folder}/_cfg/agents/bmm-pm.customize.yaml
+persona:
+  role: 'Bilingual Product Manager'
+  identity: 'Expert in US and LATAM markets'
+  communication_style: 'Clear, strategic, with cultural awareness'
+  principles:
+    - 'Consider localization from day one'
+    - 'Balance business goals with user needs'
+
+memories:
+  - 'User speaks English and Spanish'
+  - 'Target markets: US and Latin America'
+```
+
+## Tips
+
+- **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
+- **Per-Project:** Customization files are per-project, not global
+- **Version Control:** Consider committing `_cfg/` to share customizations with your team
+
+## Module vs. Global Config
+
+**Module-Level (Recommended):**
+
+- Customize agents per-project in `{bmad_folder}/_cfg/agents/`
+- Different projects can have different agent behaviors
+
+**Global Config (Coming Soon):**
+
+- Set defaults that apply across all projects
+- Override with project-specific customizations
+
+## Troubleshooting
+
+**Changes not appearing?**
+
+- Make sure you ran `npx bmad-method build <agent-name>` after editing
+- Check YAML syntax is valid (indentation matters!)
+- Verify the agent name matches the file name pattern
+
+**Agent not loading?**
+
+- Check for YAML syntax errors
+- Ensure required fields aren't left empty if you uncommented them
+- Try reverting to the template and rebuilding
+
+**Need to reset?**
+
+- Delete the `.customize.yaml` file
+- Run `npx bmad-method build <agent-name>` to regenerate defaults
+
+## Next Steps
+
+- **[BMM Agents Guide](../src/modules/bmm/docs/agents-guide.md)** - Learn about all 12 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
--- a/docs/codebase-flattener.md
+++ b/docs/codebase-flattener.md
@@ -1,19 +0,0 @@
-# Codebase Flattener Tool
-
-BMad-Core includes a powerful codebase flattener for preparing existing projects to the web for AI Analysis
-
-```bash
-# Basic usage - creates flattened-codebase.xml
-npx bmad-method flatten
-
-# Custom input/output
-npx bmad-method flatten --input /path/to/source --output project.xml
-```
-
-Features:
-
- AI-optimized XML output format
- Smart filtering with .gitignore respect
- Binary file detection and exclusion
- Real-time progress tracking
- Comprehensive completion statistics
--- a/docs/custom-agent-installation.md
+++ b/docs/custom-agent-installation.md
@@ -0,0 +1,183 @@
+# Custom Agent Installation
+
+Install and personalize BMAD agents in your project.
+
+## Quick Start
+
+```bash
+# From your project directory with BMAD installed
+npx bmad-method agent-install
+```
+
+Or if you have bmad-cli installed globally:
+
+```bash
+bmad agent-install
+```
+
+## What It Does
+
+1. **Discovers** available agent templates from your custom agents folder
+2. **Prompts** you to personalize the agent (name, behavior, preferences)
+3. **Compiles** the agent with your choices baked in
+4. **Installs** to your project's `.bmad/custom/agents/` directory
+5. **Creates** IDE commands for all your configured IDEs (Claude Code, Codex, Cursor, etc.)
+6. **Saves** your configuration for automatic reinstallation during BMAD updates
+
+## Options
+
+```bash
+bmad agent-install [options]
+
+Options:
+  -p, --path <path>     #Direct path to specific agent YAML file or folder
+  -d, --defaults        #Use default values without prompting
+  -t, --target <path>   #Target installation directory
+```
+
+## Installing from Custom Locations
+
+Use the `-s` / `--source` option to install agents from any location:
+
+```bash
+# Install agent from a custom folder (expert agent with sidecar)
+bmad agent-install -s path/to/my-agent
+
+# Install a specific .agent.yaml file (simple agent)
+bmad agent-install -s path/to/my-agent.agent.yaml
+
+# Install with defaults (non-interactive)
+bmad agent-install -s path/to/my-agent -d
+
+# Install to a specific destination project
+bmad agent-install -s path/to/my-agent --destination /path/to/destination/project
+```
+
+This is useful when:
+
+- Your agent is in a non-standard location (not in `.bmad/custom/agents/`)
+- You're developing an agent outside the project structure
+- You want to install from an absolute path
+
+## Example Session
+
+```
+🔧 BMAD Agent Installer
+
+Found BMAD at: /project/.bmad
+Searching for agents in: /project/.bmad/custom/agents
+
+Available Agents:
+
+  1. 📄 commit-poet (simple)
+  2. 📚 journal-keeper (expert)
+
+Select agent to install (number): 1
+
+Selected: commit-poet
+
+📛 Agent Persona Name
+
+   Agent type: commit-poet
+   Default persona: Inkwell Von Comitizen
+
+   Custom name (or Enter for default): Fred
+
+   Persona: Fred
+   File: fred-commit-poet.md
+
+📝 Agent Configuration
+
+   What's your preferred default commit message style?
+   * 1. Conventional (feat/fix/chore)
+     2. Narrative storytelling
+     3. Poetic haiku
+     4. Detailed explanation
+   Choice (default: 1): 1
+
+   How enthusiastic should the agent be?
+     1. Moderate - Professional with personality
+   * 2. High - Genuinely excited
+     3. EXTREME - Full theatrical drama
+   Choice (default: 2): 3
+
+   Include emojis in commit messages? [Y/n]: y
+
+✨ Agent installed successfully!
+   Name: fred-commit-poet
+   Location: /project/.bmad/custom/agents/fred-commit-poet
+   Compiled: fred-commit-poet.md
+
+   ✓ Source saved for reinstallation
+   ✓ Added to agent-manifest.csv
+   ✓ Created IDE commands:
+      claude-code: /bmad:custom:agents:fred-commit-poet
+      codex: /bmad-custom-agents-fred-commit-poet
+      github-copilot: bmad-agent-custom-fred-commit-poet
+```
+
+## Reinstallation
+
+Custom agents are automatically reinstalled when you run `bmad init --quick`. Your personalization choices are preserved in `.bmad/_cfg/custom/agents/`.
+
+## 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
+cp node_modules/bmad-method/src/modules/bmb/reference/agents/stand-alone/commit-poet.agent.yaml \
+   .bmad/custom/agents/
+```
+
+**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: Install and Personalize
+
+```bash
+npx bmad-method agent-install
+# or: bmad agent-install (if BMAD installed locally)
+```
+
+The installer will:
+
+1. Find the copied template in `.bmad/custom/agents/`
+2. Prompt for personalization (name, behavior, preferences)
+3. Compile and install with your choices baked in
+4. 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 yourself, place your `.agent.yaml` files or folder in `.bmad/custom/agents/`.
--- a/docs/document-sharding-guide.md
+++ b/docs/document-sharding-guide.md
@@ -0,0 +1,449 @@
+# Document Sharding Guide
+
+Comprehensive guide to BMad Method's document sharding system for managing large planning and architecture documents.
+
+## Table of Contents
+
+- [What is Document Sharding?](#what-is-document-sharding)
+- [When to Use Sharding](#when-to-use-sharding)
+- [How Sharding Works](#how-sharding-works)
+- [Using the Shard-Doc Tool](#using-the-shard-doc-tool)
+- [Workflow Support](#workflow-support)
+- [Best Practices](#best-practices)
+- [Examples](#examples)
+
+## What is Document Sharding?
+
+Document sharding splits large markdown files into smaller, organized files based on level 2 headings (`## Heading`). This enables:
+
+- **Selective Loading** - Workflows load only the sections they need
+- **Reduced Token Usage** - Massive efficiency gains for large projects
+- **Better Organization** - Logical section-based file structure
+- **Maintained Context** - Index file preserves document structure
+
+### Architecture
+
+```
+Before Sharding:
+docs/
+└── PRD.md (large 50k token file)
+
+After Sharding:
+docs/
+└── prd/
+    ├── index.md                    # Table of contents with descriptions
+    ├── overview.md                 # Section 1
+    ├── user-requirements.md        # Section 2
+    ├── technical-requirements.md   # Section 3
+    └── ...                         # Additional sections
+```
+
+## When to Use Sharding
+
+### Ideal Candidates
+
+**Large Multi-Epic Projects:**
+
+- Very large complex PRDs
+- Architecture documents with multiple system layers
+- Epic files with 4+ epics (especially for Phase 4)
+- UX design specs covering multiple subsystems
+
+**Token Thresholds:**
+
+- **Consider sharding**: Documents > 20k tokens
+- **Strongly recommended**: Documents > 40k tokens
+- **Critical for efficiency**: Documents > 60k tokens
+
+### When NOT to Shard
+
+**Small Projects:**
+
+- Single epic projects
+- Level 0-1 projects (tech-spec only)
+- Documents under 10k tokens
+- Quick prototypes
+
+**Frequently Updated Docs:**
+
+- Active work-in-progress documents
+- Documents updated daily
+- Documents where whole-file context is essential
+
+## How Sharding Works
+
+### Sharding Process
+
+1. **Tool Execution**: Run `npx @kayvan/markdown-tree-parser source.md destination/` - this is abstracted with the core shard-doc task which is installed as a slash command or manual task rule depending on your tools.
+2. **Section Extraction**: Tool splits by level 2 headings
+3. **File Creation**: Each section becomes a separate file
+4. **Index Generation**: `index.md` created with structure and descriptions
+
+### Workflow Discovery
+
+BMad workflows use a **dual discovery system**:
+
+1. **Try whole document first** - Look for `document-name.md`
+2. **Check for sharded version** - Look for `document-name/index.md`
+3. **Priority rule** - Whole document takes precedence if both exist
+
+### Loading Strategies
+
+**Full Load (Phase 1-3 workflows):**
+
+```
+If sharded:
+  - Read index.md
+  - Read ALL section files
+  - Treat as single combined document
+```
+
+**Selective Load (Phase 4 workflows):**
+
+```
+If sharded epics and working on Epic 3:
+  - Read epics/index.md
+  - Load ONLY epics/epic-3.md
+  - Skip all other epic files
+  - 90%+ token savings!
+```
+
+## Using the Shard-Doc Tool
+
+### CLI Command
+
+```bash
+# Activate bmad-master or analyst agent, then:
+/shard-doc
+```
+
+### Interactive Process
+
+```
+Agent: Which document would you like to shard?
+User: docs/PRD.md
+
+Agent: Default destination: docs/prd/
+       Accept default? [y/n]
+User: y
+
+Agent: Sharding PRD.md...
+       ✓ Created 12 section files
+       ✓ Generated index.md
+       ✓ Complete!
+```
+
+### What Gets Created
+
+**index.md structure:**
+
+```markdown
+# PRD - Index
+
+## Sections
+
+1. [Overview](./overview.md) - Project vision and objectives
+2. [User Requirements](./user-requirements.md) - Feature specifications
+3. [Epic 1: Authentication](./epic-1-authentication.md) - User auth system
+4. [Epic 2: Dashboard](./epic-2-dashboard.md) - Main dashboard UI
+   ...
+```
+
+**Individual section files:**
+
+- Named from heading text (kebab-case)
+- Contains complete section content
+- Preserves all markdown formatting
+- Can be read independently
+
+## Workflow Support
+
+### Universal Support
+
+**All BMM workflows support both formats:**
+
+- ✅ Whole documents
+- ✅ Sharded documents
+- ✅ Automatic detection
+- ✅ Transparent to user
+
+### Workflow-Specific Patterns
+
+#### Phase 1-3 (Full Load)
+
+Workflows load entire sharded documents:
+
+- `product-brief` - Research, brainstorming docs
+- `prd` - Product brief, research
+- `gdd` - Game brief, research
+- `create-ux-design` - PRD, brief, architecture (if available)
+- `tech-spec` - Brief, research
+- `architecture` - PRD, UX design (if available)
+- `create-epics-and-stories` - PRD, architecture
+- `implementation-readiness` - All planning docs
+
+#### Phase 4 (Selective Load)
+
+Workflows load only needed sections:
+
+**sprint-planning** (Full Load):
+
+- Needs ALL epics to build complete status
+
+**create-story, code-review** (Selective):
+
+```
+Working on Epic 3, Story 2:
+  ✓ Load epics/epic-3.md only
+  ✗ Skip epics/epic-1.md, epic-2.md, epic-4.md, etc.
+
+Result: 90%+ token reduction for 10-epic projects!
+```
+
+### Input File Patterns
+
+Workflows use standardized patterns:
+
+```yaml
+input_file_patterns:
+  prd:
+    whole: '{output_folder}/*prd*.md'
+    sharded: '{output_folder}/*prd*/index.md'
+
+  epics:
+    whole: '{output_folder}/*epic*.md'
+    sharded_index: '{output_folder}/*epic*/index.md'
+    sharded_single: '{output_folder}/*epic*/epic-{{epic_num}}.md'
+```
+
+## Best Practices
+
+### Sharding Strategy
+
+**Do:**
+
+- ✅ Shard after planning phase complete
+- ✅ Keep level 2 headings well-organized
+- ✅ Use descriptive section names
+- ✅ Shard before Phase 4 implementation
+- ✅ Keep original file as backup initially
+
+**Don't:**
+
+- ❌ Shard work-in-progress documents
+- ❌ Shard small documents (<20k tokens)
+- ❌ Mix sharded and whole versions
+- ❌ Manually edit index.md structure
+
+### Naming Conventions
+
+**Good Section Names:**
+
+```markdown
+## Epic 1: User Authentication
+
+## Technical Requirements
+
+## System Architecture
+
+## UX Design Principles
+```
+
+**Poor Section Names:**
+
+```markdown
+## Section 1
+
+## Part A
+
+## Details
+
+## More Info
+```
+
+### File Management
+
+**When to Re-shard:**
+
+- Significant structural changes to document
+- Adding/removing major sections
+- After major refactoring
+
+**Updating Sharded Docs:**
+
+1. Edit individual section files directly
+2. OR edit original, delete sharded folder, re-shard
+3. Don't manually edit index.md
+
+## Examples
+
+### Example 1: Large PRD
+
+**Scenario:** 15-epic project, PRD is 45k tokens
+
+**Before Sharding:**
+
+```
+Every workflow loads entire 45k token PRD
+Architecture workflow: 45k tokens
+UX design workflow: 45k tokens
+```
+
+**After Sharding:**
+
+```bash
+/shard-doc
+Source: docs/PRD.md
+Destination: docs/prd/
+
+Created:
+  prd/index.md
+  prd/overview.md (3k tokens)
+  prd/functional-requirements.md (8k tokens)
+  prd/non-functional-requirements.md (6k tokens)
+  prd/user-personas.md (4k tokens)
+  ...additional FR/NFR sections
+```
+
+**Result:**
+
+```
+Architecture workflow: Can load specific sections needed
+UX design workflow: Can load specific sections needed
+Significant token reduction for large requirement docs!
+```
+
+### Example 2: Sharding Epics File
+
+**Scenario:** 8 epics with detailed stories, 35k tokens total
+
+```bash
+/shard-doc
+Source: docs/bmm-epics.md
+Destination: docs/epics/
+
+Created:
+  epics/index.md
+  epics/epic-1.md
+  epics/epic-2.md
+  ...
+  epics/epic-8.md
+```
+
+**Efficiency Gain:**
+
+```
+Working on Epic 5 stories:
+  Old: Load all 8 epics (35k tokens)
+  New: Load epic-5.md only (4k tokens)
+  Savings: 88% reduction
+```
+
+### Example 3: Architecture Document
+
+**Scenario:** Multi-layer system architecture, 28k tokens
+
+```bash
+/shard-doc
+Source: docs/architecture.md
+Destination: docs/architecture/
+
+Created:
+  architecture/index.md
+  architecture/system-overview.md
+  architecture/frontend-architecture.md
+  architecture/backend-services.md
+  architecture/data-layer.md
+  architecture/infrastructure.md
+  architecture/security-architecture.md
+```
+
+**Benefit:** Code-review workflow can reference specific architectural layers without loading entire architecture doc.
+
+## Custom Workflow Integration
+
+### For Workflow Builders
+
+When creating custom workflows that load large documents:
+
+**1. Add input_file_patterns to workflow.yaml:**
+
+```yaml
+input_file_patterns:
+  your_document:
+    whole: '{output_folder}/*your-doc*.md'
+    sharded: '{output_folder}/*your-doc*/index.md'
+```
+
+**2. Add discovery instructions to instructions.md:**
+
+```markdown
+## Document Discovery
+
+1. Search for whole document: _your-doc_.md
+2. Check for sharded version: _your-doc_/index.md
+3. If sharded: Read index + ALL sections (or specific sections if selective load)
+4. Priority: Whole document first
+```
+
+**3. Choose loading strategy:**
+
+- **Full Load**: Read all sections when sharded
+- **Selective Load**: Read only relevant sections (requires section identification logic)
+
+### Pattern Templates
+
+**Full Load Pattern:**
+
+```xml
+<action>Search for document: {output_folder}/*doc-name*.md</action>
+<action>If not found, check for sharded: {output_folder}/*doc-name*/index.md</action>
+<action if="sharded found">Read index.md to understand structure</action>
+<action if="sharded found">Read ALL section files listed in index</action>
+<action if="sharded found">Combine content as single document</action>
+```
+
+**Selective Load Pattern (with section ID):**
+
+```xml
+<action>Determine section needed (e.g., epic_num = 3)</action>
+<action>Check for sharded version: {output_folder}/*doc-name*/index.md</action>
+<action if="sharded found">Read ONLY the specific section file needed</action>
+<action if="sharded found">Skip all other section files</action>
+```
+
+## Troubleshooting
+
+### Common Issues
+
+**Both whole and sharded exist:**
+
+- Workflows will use whole document (priority rule)
+- Delete or archive the one you don't want
+
+**Index.md out of sync:**
+
+- Delete sharded folder
+- Re-run shard-doc on original
+
+**Workflow can't find document:**
+
+- Check file naming matches patterns (`*prd*.md`, `*epic*.md`, etc.)
+- Verify index.md exists in sharded folder
+- Check output_folder path in config
+
+**Sections too granular:**
+
+- Combine sections in original document
+- Use fewer level 2 headings
+- Re-shard
+
+## Related Documentation
+
+- [shard-doc Tool](../src/core/tools/shard-doc.xml) - Tool implementation
+- [BMM Workflows Guide](../src/modules/bmm/workflows/README.md) - Workflow overview
+- [Workflow Creation Guide](../src/modules/bmb/workflows/create-workflow/workflow-creation-guide.md) - Custom workflow patterns
+
+---
+
+**Document sharding is optional but powerful** - use it when efficiency matters for large projects!
--- a/docs/ide-info/auggie.md
+++ b/docs/ide-info/auggie.md
@@ -6,8 +6,8 @@ BMAD agents can be installed in multiple locations based on your setup.

 ### Common Locations

- User Home: `~/.auggie/commands/`
- Project: `.auggie/commands/`
+- User Home: `~/.augment/commands/`
+- Project: `.augment/commands/`
 - Custom paths you selected

 ### How to Use
--- a/docs/ide-info/claude-code.md
+++ b/docs/ide-info/claude-code.md
@@ -13,13 +13,13 @@ BMAD agents are installed as slash commands in `.claude/commands/bmad/`.
 ### Examples

 ```
-/bmad-dev - Activate development agent
-/bmad-architect - Activate architect agent
-/bmad-task-setup - Execute setup task
+/bmad:bmm:agents:dev - Activate development agent
+/bmad:bmm:agents:architect - Activate architect agent
+/bmad:bmm:workflows:dev-story - Execute dev-story workflow
 ```

 ### Notes

 - Commands are autocompleted when you type `/`
 - Agent remains active for the conversation
- Start new conversation to switch agents
+- Start a new conversation to switch agents
--- a/docs/ide-info/codex.md
+++ b/docs/ide-info/codex.md
@@ -2,31 +2,20 @@

 ## Activating Agents

-BMAD agents are documented in `AGENTS.md` file in project root.
-
-### CLI Mode
-
-1. **Reference Agent**: Type `@{agent-name}` in prompt
-2. **Execute Task**: Type `@task-{task-name}`
-3. **Active Session**: Agent remains active for conversation
-
-### Web Mode
-
-1. **Navigate**: Go to Agents section in web interface
-2. **Select Agent**: Click to activate agent persona
-3. **Session**: Agent active for browser session
+BMAD agents, tasks and workflows are installed as custom prompts in
+`$CODEX_HOME/prompts/bmad-*.md` files. If `CODEX_HOME` is not set, it
+defaults to `$HOME/.codex/`.

 ### Examples

 ```
-@dev - Activate development agent
-@architect - Activate architect agent
-@task-setup - Execute setup task
+/bmad-bmm-agents-dev - Activate development agent
+/bmad-bmm-agents-architect - Activate architect agent
+/bmad-bmm-workflows-dev-story - Execute dev-story workflow
 ```

 ### Notes

- All agents documented in AGENTS.md
- CLI: Reference with @ syntax
- Web: Use interface to select
- One agent active at a time
+Prompts are autocompleted when you type /
+Agent remains active for the conversation
+Start a new conversation to switch agents
--- a/docs/ide-info/crush.md
+++ b/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/{module}/agents/`
+2. **Navigate**: Browse to `{bmad_folder}/{module}/agents/`
 3. **Select Agent**: Choose the agent command
 4. **Execute**: Run to activate agent persona

--- a/docs/ide-info/cursor.md
+++ b/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/{module}/agents/{agent-name}`
-2. **Include Entire Module**: Use `@bmad/{module}`
-3. **Reference Index**: Use `@bmad/index` for all available agents
+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

 ### Examples

 ```
-@bmad/core/agents/dev - Activate dev agent
-@bmad/bmm/agents/architect - Activate architect agent
-@bmad/core - Include all core agents/tasks
+@{bmad_folder}/core/agents/dev - Activate dev agent
+@{bmad_folder}/bmm/agents/architect - Activate architect agent
+@{bmad_folder}/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/core/agents/dev @bmad/core/agents/test`
+- Can combine multiple agents: `@{bmad_folder}/core/agents/dev @{bmad_folder}/core/agents/test`
--- a/docs/ide-info/iflow.md
+++ b/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/agents/` or `bmad/tasks/`
+2. **Navigate**: Browse to `{bmad_folder}/agents/` or `{bmad_folder}/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/agents/core-dev - Activate dev agent
-/bmad/tasks/core-setup - Execute setup task
+/{bmad_folder}/agents/core-dev - Activate dev agent
+/{bmad_folder}/tasks/core-setup - Execute setup task
 ```

 ### Notes
--- a/docs/ide-info/opencode.md
+++ b/docs/ide-info/opencode.md
@@ -0,0 +1,24 @@
+# BMAD Method - OpenCode Instructions
+
+## Activating Agents
+
+BMAD agents are installed as OpenCode agents in `.opencode/agent/BMAD/{module_name}` and workflow commands in `.opencode/command/BMAD/{module_name}`.
+
+### How to Use
+
+1. **Switch Agents**: Press **Tab** to cycle through primary agents or select using the `/agents`
+2. **Activate Agent**: Once the Agent is selected say `hello` or any prompt to activate that agent persona
+3. **Execute Commands**: Type `/bmad` to see and execute bmad workflow commands (commands allow for fuzzy matching)
+
+### Examples
+
+```
+/agents - to see a list of agents and switch between them
+/{bmad_folder}/bmm/workflows/workflow-init - Activate the workflow-init command
+```
+
+### Notes
+
+- Press **Tab** to switch between primary agents (Analyst, Architect, Dev, etc.)
+- Commands are autocompleted when you type `/` and allow for fuzzy matching
+- Workflow commands execute in current agent context, make sure you have the right agent activated before running a command
--- a/docs/ide-info/rovo-dev.md
+++ b/docs/ide-info/rovo-dev.md
@@ -0,0 +1,388 @@
+# Rovo Dev IDE Integration
+
+This document describes how BMAD-METHOD integrates with [Atlassian Rovo Dev](https://www.atlassian.com/rovo-dev), an AI-powered software development assistant.
+
+## Overview
+
+Rovo Dev is designed to integrate deeply with developer workflows and organizational knowledge bases. When you install BMAD-METHOD in a Rovo Dev project, it automatically installs BMAD agents, workflows, tasks, and tools just like it does for other IDEs (Cursor, VS Code, etc.).
+
+BMAD-METHOD provides:
+
+- **Agents**: Specialized subagents for various development tasks
+- **Workflows**: Multi-step workflow guides and coordinators
+- **Tasks & Tools**: Reference documentation for BMAD tasks and tools
+
+### What are Rovo Dev Subagents?
+
+Subagents are specialized agents that Rovo Dev can delegate tasks to. They are defined as Markdown files with YAML frontmatter stored in the `.rovodev/subagents/` directory. Rovo Dev automatically discovers these files and makes them available through the `@subagent-name` syntax.
+
+## Installation and Setup
+
+### Automatic Installation
+
+When you run the BMAD-METHOD installer and select Rovo Dev as your IDE:
+
+```bash
+bmad install
+```
+
+The installer will:
+
+1. Create a `.rovodev/subagents/` directory in your project (if it doesn't exist)
+2. Convert BMAD agents into Rovo Dev subagent format
+3. Write subagent files with the naming pattern: `bmad-<module>-<agent-name>.md`
+
+### File Structure
+
+After installation, your project will have:
+
+```
+project-root/
+├── .rovodev/
+│   ├── subagents/
+│   │   ├── bmad-core-code-reviewer.md
+│   │   ├── bmad-bmm-pm.md
+│   │   ├── bmad-bmm-dev.md
+│   │   └── ... (more agents from selected modules)
+│   ├── workflows/
+│   │   ├── bmad-brainstorming.md
+│   │   ├── bmad-prd-creation.md
+│   │   └── ... (workflow guides)
+│   ├── references/
+│   │   ├── bmad-task-core-code-review.md
+│   │   ├── bmad-tool-core-analysis.md
+│   │   └── ... (task/tool references)
+│   ├── config.yml          (Rovo Dev configuration)
+│   ├── prompts.yml         (Optional: reusable prompts)
+│   └── ...
+├── .bmad/                  (BMAD installation directory)
+└── ...
+```
+
+**Directory Structure Explanation:**
+
+- **subagents/**: Agents discovered and used by Rovo Dev with `@agent-name` syntax
+- **workflows/**: Multi-step workflow guides and instructions
+- **references/**: Documentation for available tasks and tools in BMAD
+
+## Subagent File Format
+
+BMAD agents are converted to Rovo Dev subagent format, which uses Markdown with YAML frontmatter:
+
+### Basic Structure
+
+```markdown
+---
+name: bmad-module-agent-name
+description: One sentence description of what this agent does
+tools:
+  - bash
+  - open_files
+  - grep
+  - expand_code_chunks
+model: anthropic.claude-3-5-sonnet-20241022-v2:0 # Optional
+load_memory: true # Optional
+---
+
+You are a specialized agent for [specific task].
+
+## Your Role
+
+Describe the agent's role and responsibilities...
+
+## Key Instructions
+
+1. First instruction
+2. Second instruction
+3. Third instruction
+
+## When to Use This Agent
+
+Explain when and how to use this agent...
+```
+
+### YAML Frontmatter Fields
+
+| Field         | Type    | Required | Description                                                                                                                           |
+| ------------- | ------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------- |
+| `name`        | string  | Yes      | Unique identifier for the subagent (kebab-case, no spaces)                                                                            |
+| `description` | string  | Yes      | One-line description of the subagent's purpose                                                                                        |
+| `tools`       | array   | No       | List of tools the subagent can use. If not specified, uses parent agent's tools                                                       |
+| `model`       | string  | No       | Specific LLM model for this subagent (e.g., `anthropic.claude-3-5-sonnet-20241022-v2:0`). If not specified, uses parent agent's model |
+| `load_memory` | boolean | No       | Whether to load default memory files (AGENTS.md, AGENTS.local.md). Defaults to `true`                                                 |
+
+### System Prompt
+
+The content after the closing `---` is the subagent's system prompt. This defines:
+
+- The agent's persona and role
+- Its capabilities and constraints
+- Step-by-step instructions for task execution
+- Examples of expected behavior
+
+## Using BMAD Components in Rovo Dev
+
+### Invoking a Subagent (Agent)
+
+In Rovo Dev, you can invoke a BMAD agent as a subagent using the `@` syntax:
+
+```
+@bmad-core-code-reviewer Please review this PR for potential issues
+@bmad-bmm-pm Help plan this feature release
+@bmad-bmm-dev Implement this feature
+```
+
+### Accessing Workflows
+
+Workflow guides are available in `.rovodev/workflows/` directory:
+
+```
+@bmad-core-code-reviewer Use the brainstorming workflow from .rovodev/workflows/bmad-brainstorming.md
+```
+
+Workflow files contain step-by-step instructions and can be referenced or copied into Rovo Dev for collaborative workflow execution.
+
+### Accessing Tasks and Tools
+
+Task and tool documentation is available in `.rovodev/references/` directory. These provide:
+
+- Task execution instructions
+- Tool capabilities and usage
+- Integration examples
+- Parameter documentation
+
+### Example Usage Scenarios
+
+#### Code Review
+
+```
+@bmad-core-code-reviewer Review the changes in src/components/Button.tsx
+for best practices, performance, and potential bugs
+```
+
+#### Documentation
+
+```
+@bmad-core-documentation-writer Generate API documentation for the new
+user authentication module
+```
+
+#### Feature Design
+
+```
+@bmad-module-feature-designer Design a solution for implementing
+dark mode support across the application
+```
+
+## Customizing BMAD Subagents
+
+You can customize BMAD subagents after installation by editing their files directly in `.rovodev/subagents/`.
+
+### Example: Adding Tool Restrictions
+
+By default, BMAD subagents inherit tools from the parent Rovo Dev agent. You can restrict which tools a specific subagent can use:
+
+```yaml
+---
+name: bmad-core-code-reviewer
+description: Reviews code and suggests improvements
+tools:
+  - open_files
+  - expand_code_chunks
+  - grep
+---
+```
+
+### Example: Using a Specific Model
+
+Some agents might benefit from using a different model. You can specify this:
+
+```yaml
+---
+name: bmad-core-documentation-writer
+description: Writes clear and comprehensive documentation
+model: anthropic.claude-3-5-sonnet-20241022-v2:0
+---
+```
+
+### Example: Enhancing the System Prompt
+
+You can add additional context to a subagent's system prompt:
+
+```markdown
+---
+name: bmad-core-code-reviewer
+description: Reviews code and suggests improvements
+---
+
+You are a specialized code review agent for our project.
+
+## Project Context
+
+Our codebase uses:
+
+- React 18 for frontend
+- Node.js 18+ for backend
+- TypeScript for type safety
+- Jest for testing
+
+## Review Checklist
+
+1. Type safety and TypeScript correctness
+2. React best practices and hooks usage
+3. Performance considerations
+4. Test coverage
+5. Documentation and comments
+
+...rest of original system prompt...
+```
+
+## Memory and Context
+
+By default, BMAD subagents have `load_memory: true`, which means they will load memory files from your project:
+
+- **Project-level**: `.rovodev/AGENTS.md` and `.rovodev/.agent.md`
+- **User-level**: `~/.rovodev/AGENTS.md` (global memory across all projects)
+
+These files can contain:
+
+- Project guidelines and conventions
+- Common patterns and best practices
+- Recent decisions and context
+- Custom instructions for all agents
+
+### Creating Project Memory
+
+Create `.rovodev/AGENTS.md` in your project:
+
+```markdown
+# Project Guidelines
+
+## Code Style
+
+- Use 2-space indentation
+- Use camelCase for variables
+- Use PascalCase for classes
+
+## Architecture
+
+- Follow modular component structure
+- Use dependency injection for services
+- Implement proper error handling
+
+## Testing Requirements
+
+- Minimum 80% code coverage
+- Write tests before implementation
+- Use descriptive test names
+```
+
+## Troubleshooting
+
+### Subagents Not Appearing in Rovo Dev
+
+1. **Verify files exist**: Check that `.rovodev/subagents/bmad-*.md` files are present
+2. **Check Rovo Dev is reloaded**: Rovo Dev may cache agent definitions. Restart Rovo Dev or reload the project
+3. **Verify file format**: Ensure files have proper YAML frontmatter (between `---` markers)
+4. **Check file permissions**: Ensure files are readable by Rovo Dev
+
+### Agent Name Conflicts
+
+If you have custom subagents with the same names as BMAD agents, Rovo Dev will load both but may show a warning. Use unique prefixes for custom subagents to avoid conflicts.
+
+### Tools Not Available
+
+If a subagent's tools aren't working:
+
+1. Verify the tool names match Rovo Dev's available tools
+2. Check that the parent Rovo Dev agent has access to those tools
+3. Ensure tool permissions are properly configured in `.rovodev/config.yml`
+
+## Advanced: Tool Configuration
+
+Rovo Dev agents have access to a set of tools for various tasks. Common tools available include:
+
+- `bash`: Execute shell commands
+- `open_files`: View file contents
+- `grep`: Search across files
+- `expand_code_chunks`: View specific code sections
+- `find_and_replace_code`: Modify files
+- `create_file`: Create new files
+- `delete_file`: Delete files
+- `move_file`: Rename or move files
+
+### MCP Servers
+
+Rovo Dev can also connect to Model Context Protocol (MCP) servers, which provide additional tools and data sources:
+
+- **Atlassian Integration**: Access to Jira, Confluence, and Bitbucket
+- **Code Analysis**: Custom code analysis and metrics
+- **External Services**: APIs and third-party integrations
+
+Configure MCP servers in `~/.rovodev/mcp.json` or `.rovodev/mcp.json`.
+
+## Integration with Other IDE Handlers
+
+BMAD-METHOD supports multiple IDEs simultaneously. You can have both Rovo Dev and other IDE configurations (Cursor, VS Code, etc.) in the same project. Each IDE will have its own artifacts installed in separate directories.
+
+For example:
+
+- Rovo Dev agents: `.rovodev/subagents/bmad-*.md`
+- Cursor rules: `.cursor/rules/bmad/`
+- Claude Code: `.claude/rules/bmad/`
+
+## Performance Considerations
+
+- BMAD subagent files are typically small (1-5 KB each)
+- Rovo Dev lazy-loads subagents, so having many subagents doesn't impact startup time
+- System prompts are cached by Rovo Dev after first load
+
+## Best Practices
+
+1. **Keep System Prompts Concise**: Shorter, well-structured prompts are more effective
+2. **Use Project Memory**: Leverage `.rovodev/AGENTS.md` for shared context
+3. **Customize Tool Restrictions**: Give subagents only the tools they need
+4. **Test Subagent Invocations**: Verify each subagent works as expected for your project
+5. **Version Control**: Commit `.rovodev/subagents/` to version control for team consistency
+6. **Document Custom Subagents**: Add comments explaining the purpose of customized subagents
+
+## Related Documentation
+
+- [Rovo Dev Official Documentation](https://www.atlassian.com/rovo-dev)
+- [BMAD-METHOD Installation Guide](./installation.md)
+- [IDE Handler Architecture](./ide-handlers.md)
+- [Rovo Dev Configuration Reference](https://www.atlassian.com/rovo-dev/configuration)
+
+## Examples
+
+### Example 1: Code Review Workflow
+
+```
+User: @bmad-core-code-reviewer Review src/auth/login.ts for security issues
+Rovo Dev → Subagent: Opens file, analyzes code, suggests improvements
+Subagent output: Security vulnerabilities found, recommendations provided
+```
+
+### Example 2: Documentation Generation
+
+```
+User: @bmad-core-documentation-writer Generate API docs for the new payment module
+Rovo Dev → Subagent: Analyzes code structure, generates documentation
+Subagent output: Markdown documentation with examples and API reference
+```
+
+### Example 3: Architecture Design
+
+```
+User: @bmad-module-feature-designer Design a caching strategy for the database layer
+Rovo Dev → Subagent: Reviews current architecture, proposes design
+Subagent output: Detailed architecture proposal with implementation plan
+```
+
+## Support
+
+For issues or questions about:
+
+- **Rovo Dev**: See [Atlassian Rovo Dev Documentation](https://www.atlassian.com/rovo-dev)
+- **BMAD-METHOD**: See [BMAD-METHOD README](../README.md)
+- **IDE Integration**: See [IDE Handler Guide](./ide-handlers.md)
--- a/docs/index.md
+++ b/docs/index.md
@@ -0,0 +1,152 @@
+# BMad Documentation Index
+
+Complete map of all BMad Method v6 documentation with recommended reading paths.
+
+---
+
+## 🎯 Getting Started (Start Here!)
+
+**New users:** Start with one of these based on your situation:
+
+| Your Situation         | Start Here                                                      | Then Read                                                     |
+| ---------------------- | --------------------------------------------------------------- | ------------------------------------------------------------- |
+| **Brand new to BMad**  | [Quick Start Guide](../src/modules/bmm/docs/quick-start.md)     | [BMM Workflows Guide](../src/modules/bmm/workflows/README.md) |
+| **Upgrading from v4**  | [v4 to v6 Upgrade Guide](./v4-to-v6-upgrade.md)                 | [Quick Start Guide](../src/modules/bmm/docs/quick-start.md)   |
+| **Brownfield project** | [Brownfield Guide](../src/modules/bmm/docs/brownfield-guide.md) | [Quick Start Guide](../src/modules/bmm/docs/quick-start.md)   |
+
+---
+
+## 📋 Core Documentation
+
+### Project-Level Docs (Root)
+
+- **[README.md](../README.md)** - Main project overview, feature summary, and module introductions
+- **[CONTRIBUTING.md](../CONTRIBUTING.md)** - How to contribute, pull request guidelines, code style
+- **[CHANGELOG.md](../CHANGELOG.md)** - Version history and breaking changes
+- **[CLAUDE.md](../CLAUDE.md)** - Claude Code specific guidelines for this project
+
+### Installation & Setup
+
+- **[v4 to v6 Upgrade Guide](./v4-to-v6-upgrade.md)** - Migration path for v4 users
+- **[Document Sharding Guide](./document-sharding-guide.md)** - Split large documents for 90%+ token savings
+- **[Web Bundles](./USING_WEB_BUNDLES.md)** - Use BMAD agents in Claude Projects, ChatGPT, or Gemini without installation
+- **[Bundle Distribution Setup](./BUNDLE_DISTRIBUTION_SETUP.md)** - Maintainer guide for bundle auto-publishing
+
+---
+
+## 🏗️ Module Documentation
+
+### BMad Method (BMM) - Software & Game Development
+
+The flagship module for agile AI-driven development.
+
+- **[BMM Module README](../src/modules/bmm/README.md)** - Module overview, agents, and complete documentation index
+- **[BMM Documentation](../src/modules/bmm/docs/)** - All BMM-specific guides and references:
+  - [Quick Start Guide](../src/modules/bmm/docs/quick-start.md) - Step-by-step guide to building your first project
+  - [Quick Spec Flow](../src/modules/bmm/docs/quick-spec-flow.md) - Rapid Level 0-1 development
+  - [Scale Adaptive System](../src/modules/bmm/docs/scale-adaptive-system.md) - Understanding the 5-level system
+  - [Brownfield Guide](../src/modules/bmm/docs/brownfield-guide.md) - Working with existing codebases
+- **[BMM Workflows Guide](../src/modules/bmm/workflows/README.md)** - **ESSENTIAL READING**
+- **[Test Architect Guide](../src/modules/bmm/testarch/README.md)** - Testing strategy and quality assurance
+
+### BMad Builder (BMB) - Create Custom Solutions
+
+Build your own agents, workflows, and modules.
+
+- **[BMB Module README](../src/modules/bmb/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
+
+AI-powered creative thinking and brainstorming.
+
+- **[CIS Module README](../src/modules/cis/README.md)** - Module overview and workflows
+
+---
+
+## 🖥️ IDE-Specific Guides
+
+Instructions for loading agents and running workflows in your development environment.
+
+**Popular IDEs:**
+
+- [Claude Code](./ide-info/claude-code.md)
+- [Cursor](./ide-info/cursor.md)
+- [VS Code](./ide-info/windsurf.md)
+
+**Other Supported IDEs:**
+
+- [Augment](./ide-info/auggie.md)
+- [Cline](./ide-info/cline.md)
+- [Codex](./ide-info/codex.md)
+- [Crush](./ide-info/crush.md)
+- [Gemini](./ide-info/gemini.md)
+- [GitHub Copilot](./ide-info/github-copilot.md)
+- [IFlow](./ide-info/iflow.md)
+- [Kilo](./ide-info/kilo.md)
+- [OpenCode](./ide-info/opencode.md)
+- [Qwen](./ide-info/qwen.md)
+- [Roo](./ide-info/roo.md)
+- [Rovo Dev](./ide-info/rovo-dev.md)
+- [Trae](./ide-info/trae.md)
+
+**Key concept:** Every reference to "load an agent" or "activate an agent" in the main docs links to the [ide-info](./ide-info/) directory for IDE-specific instructions.
+
+---
+
+## 🔧 Advanced Topics
+
+### Custom Agents
+
+- **[Custom Agent Installation](./custom-agent-installation.md)** - Install and personalize agents with `bmad agent-install`
+- [Agent Customization Guide](./agent-customization-guide.md) - Customize agent behavior and responses
+
+### Installation & Bundling
+
+- [IDE Injections Reference](./installers-bundlers/ide-injections.md) - How agents are installed to IDEs
+- [Installers & Platforms Reference](./installers-bundlers/installers-modules-platforms-reference.md) - CLI tool and platform support
+- [Web Bundler Usage](./installers-bundlers/web-bundler-usage.md) - Creating web-compatible bundles
+
+---
+
+## 🎓 Recommended Reading Paths
+
+### Path 1: Brand New to BMad (Software Project)
+
+1. [README.md](../README.md) - Understand the vision
+2. [Quick Start Guide](../src/modules/bmm/docs/quick-start.md) - Get hands-on
+3. [BMM Module README](../src/modules/bmm/README.md) - Understand agents
+4. [BMM Workflows Guide](../src/modules/bmm/workflows/README.md) - Master the methodology
+5. [Your IDE guide](./ide-info/) - Optimize your workflow
+
+### Path 2: Game Development Project
+
+1. [README.md](../README.md) - Understand the vision
+2. [Quick Start Guide](../src/modules/bmm/docs/quick-start.md) - Get hands-on
+3. [BMM Module README](../src/modules/bmm/README.md) - Game agents are included
+4. [BMM Workflows Guide](../src/modules/bmm/workflows/README.md) - Game workflows
+5. [Your IDE guide](./ide-info/) - Optimize your workflow
+
+### Path 3: Upgrading from v4
+
+1. [v4 to v6 Upgrade Guide](./v4-to-v6-upgrade.md) - Understand what changed
+2. [Quick Start Guide](../src/modules/bmm/docs/quick-start.md) - Reorient yourself
+3. [BMM Workflows Guide](../src/modules/bmm/workflows/README.md) - Learn new v6 workflows
+
+### Path 4: Working with Existing Codebase (Brownfield)
+
+1. [Brownfield Guide](../src/modules/bmm/docs/brownfield-guide.md) - Approach for legacy code
+2. [Quick Start Guide](../src/modules/bmm/docs/quick-start.md) - Follow the process
+3. [BMM Workflows Guide](../src/modules/bmm/workflows/README.md) - Master the methodology
+
+### Path 5: Building Custom Solutions
+
+1. [BMB Module README](../src/modules/bmb/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
+
+### Path 6: Contributing to BMad
+
+1. [CONTRIBUTING.md](../CONTRIBUTING.md) - Contribution guidelines
+2. Relevant module README - Understand the area you're contributing to
+3. [Code Style section in CONTRIBUTING.md](../CONTRIBUTING.md#code-style) - Follow standards
--- a/docs/installers-bundlers/ide-injections.md
+++ b/docs/installers-bundlers/ide-injections.md
@@ -158,7 +158,7 @@ src/modules/bmm/

 ```yaml
 injections:
-  - file: 'bmad/bmm/agents/pm.md'
+  - file: '{bmad_folder}/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/bmm/templates/prd.md'
+  - file: '{bmad_folder}/bmm/templates/prd.md'
    point: 'prd-goals-context-delegation'
    requires: 'market-researcher' # Only if this specific subagent selected
    content: |
@@ -184,13 +184,3 @@ injections:
  <cmds>...</cmds>
 </agent>
 ```
-
-## Testing Checklist
-
- [ ] Injection points are properly named and unique
- [ ] injections.yaml is valid YAML with correct structure
- [ ] Content formatting is preserved after injection
- [ ] Installation works without the IDE (injection points removed)
- [ ] Installation works with the IDE (content properly injected)
- [ ] Subagents/files are copied to correct locations
- [ ] No IDE-specific content remains when different IDE selected
--- a/docs/installers-bundlers/installers-modules-platforms-reference.md
+++ b/docs/installers-bundlers/installers-modules-platforms-reference.md
@@ -1,4 +1,4 @@
-# BMAD v6 Installation & Module System Reference
+# BMAD Installation & Module System Reference

 ## Table of Contents

@@ -13,63 +13,36 @@

 ## Overview

-BMAD v6 is a modular AI agent framework with intelligent installation, platform-agnostic support, and configuration inheritance.
+BMad Core is a modular AI agent framework with intelligent installation, platform-agnostic support, and configuration inheritance.

 ### Key Features

- **Modular Design**: Core + optional modules (BMM, CIS)
+- **Modular Design**: Core + optional modules (BMB, BMM, CIS)
 - **Smart Installation**: Interactive configuration with dependency resolution
- **Multi-Platform**: Supports 15+ AI coding platforms
- **Clean Architecture**: Centralized `bmad/` directory, no source pollution
-
-## Quick Start
-
-```bash
-# Interactive installation (recommended)
-bmad install
-
-# Install specific modules
-bmad install -m bmm cis
-
-# Full installation
-bmad install -f
-
-# Check status
-bmad status
-```
-
-### Installation Options
-
- `-d <path>`: Target directory (default: current)
- `-m <modules...>`: Specific modules (bmm, cis)
- `-f`: Full installation
- `-c`: Core only
- `-i <ide...>`: Configure specific IDEs
- `--skip-ide`: Skip IDE configuration
- `-v`: Verbose output
+- **Clean Architecture**: Centralized `{bmad_folder}` directory add to project, no source pollution with multiple folders added

 ## Architecture

-### Directory Structure
+### Directory Structure upon installation

 ```
 project-root/
-├── bmad/                    # Centralized installation
-│   ├── _cfg/               # Configuration
-│   │   ├── agents/         # Agent configs
-│   │   └── agent-party.xml # Agent manifest
-│   ├── core/               # Core module
+├── {bmad_folder}/             # Centralized installation
+│   ├── _cfg/                  # Configuration
+│   │   ├── agents/            # Agent configs
+│   │   └── agent-manifest.csv # Agent manifest
+│   ├── core/                  # Core module
 │   │   ├── agents/
 │   │   ├── tasks/
 │   │   └── config.yaml
-│   ├── bmm/                # BMad Method module
+│   ├── bmm/                   # BMad Method module
 │   │   ├── agents/
 │   │   ├── tasks/
-│   │   ├── templates/
+│   │   ├── workflows/
 │   │   └── config.yaml
-│   └── cis/                # Creative Innovation Studio
+│   └── cis/                   # Creative Innovation Studio
 │       └── ...
-└── .claude/                # Platform-specific (example)
+└── .claude/                   # Platform-specific (example)
    └── agents/
 ```

@@ -78,11 +51,10 @@ project-root/
 1. **Detection**: Check existing installation
 2. **Selection**: Choose modules interactively or via CLI
 3. **Configuration**: Collect module-specific settings
-4. **Platform Setup**: Configure AI coding platforms
-5. **Installation**: Process and copy files
-6. **Generation**: Create config files with inheritance
-7. **Post-Install**: Run module installers
-8. **Manifest**: Track installed components
+4. **Installation**: Compile Process and copy files
+5. **Generation**: Create config files with inheritance
+6. **Post-Install**: Run module installers
+7. **Manifest**: Track installed components

 ### Key Exclusions

@@ -121,7 +93,7 @@ Creative Innovation Studio for design workflows
 src/modules/{module}/
 ├── _module-installer/       # Not copied to destination
 │   ├── installer.js        # Post-install logic
-│   └── install-menu-config.yaml
+│   └── install-config.yaml
 ├── agents/
 ├── tasks/
 ├── templates/
@@ -135,7 +107,7 @@ src/modules/{module}/

 ### Collection Process

-Modules define prompts in `install-menu-config.yaml`:
+Modules define prompts in `install-config.yaml`:

 ```yaml
 project_name:
@@ -199,7 +171,7 @@ communication_language: "English"
 - Windsurf

 **Additional**:
-Cline, Roo, Auggie, GitHub Copilot, Codex, Gemini, Qwen, Trae, Kilo, Crush, iFlow
+Cline, Roo, Rovo Dev,Auggie, GitHub Copilot, Codex, Gemini, Qwen, Trae, Kilo, Crush, iFlow

 ### Platform Features

@@ -212,7 +184,7 @@ Cline, Roo, Auggie, GitHub Copilot, Codex, Gemini, Qwen, Trae, Kilo, Crush, iFlo

   ```yaml
   injections:
-     - file: 'bmad/bmm/agents/pm.md'
+     - file: '{bmad_folder}/bmm/agents/pm.md'
       point: 'pm-agent-instructions'
       content: |
         <i>Platform-specific instruction</i>
@@ -246,12 +218,12 @@ Platform-specific content without source modification:
   src/modules/mymod/
   ├── _module-installer/
   │   ├── installer.js
-   │   └── install-menu-config.yaml
+   │   └── install-config.yaml
   ├── agents/
   └── tasks/
   ```

-2. **Configuration** (`install-menu-config.yaml`)
+2. **Configuration** (`install-config.yaml`)

   ```yaml
   code: mymod
@@ -298,14 +270,14 @@ Generated in: `bmad/_cfg/agents/{module}-{agent}.md`

 ### Common Issues

-| 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       |
+| 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                |

 ### Debug Commands

@@ -317,19 +289,19 @@ bmad status -v      # Detailed status
 ### Best Practices

 1. Run from project root
-2. Backup `bmad/_cfg/` before updates
+2. Backup `{bmad_folder}/_cfg/` before updates
 3. Use interactive mode for guidance
 4. Review generated configs post-install

 ## Migration from v4

-| v4                  | v6                  |
-| ------------------- | ------------------- |
-| Scattered files     | Centralized `bmad/` |
-| Monolithic          | Modular             |
-| Manual config       | Interactive setup   |
-| Limited IDE support | 15+ platforms       |
-| Source modification | Clean injection     |
+| v4                  | v6                           |
+| ------------------- | ---------------------------- |
+| Scattered files     | Centralized `{bmad_folder}/` |
+| Monolithic          | Modular                      |
+| Manual config       | Interactive setup            |
+| Limited IDE support | 15+ platforms                |
+| Source modification | Clean injection              |

 ## Technical Notes

@@ -339,6 +311,66 @@ bmad status -v      # Detailed status
 - Agent references (cross-module)
 - Template dependencies
 - Partial module installation (only required files)
+- Workflow vendoring for standalone module operation
+
+## Workflow Vendoring
+
+**Problem**: Modules that reference workflows from other modules create dependencies, forcing users to install multiple modules even when they only need one.
+
+**Solution**: Workflow vendoring allows modules to copy workflows from other modules during installation, making them fully standalone.
+
+### How It Works
+
+Agents can specify both `workflow` (source location) and `workflow-install` (destination location) in their menu items:
+
+```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'
+    description: 'Create a game feature story'
+```
+
+**During Installation:**
+
+1. **Vendoring Phase**: Before copying module files, the installer:
+   - Scans source agent YAML files for `workflow-install` attributes
+   - Copies entire workflow folders from `workflow` path to `workflow-install` path
+   - Updates vendored `workflow.yaml` files to reference target module's config
+
+2. **Compilation Phase**: When compiling agents:
+   - If `workflow-install` exists, uses its value for the `workflow` attribute
+   - `workflow-install` is build-time metadata only, never appears in final XML
+   - Compiled agent references vendored workflow location
+
+3. **Config Update**: Vendored workflows get their `config_source` updated:
+
+   ```yaml
+   # Source workflow (in bmm):
+   config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+
+   # Vendored workflow (in bmgd):
+   config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml"
+   ```
+
+**Result**: Modules become completely standalone with their own copies of needed workflows, configured for their specific use case.
+
+### Example Use Case: BMGD Module
+
+The BMad Game Development module vendors implementation workflows from BMM:
+
+- Game Dev Scrum Master agent references BMM workflows
+- During installation, workflows are copied to `bmgd/workflows/4-production/`
+- Vendored workflows use BMGD's config (with game-specific settings)
+- BMGD can be installed without BMM dependency
+
+### Benefits
+
+✅ **Module Independence** - No forced dependencies
+✅ **Clean Namespace** - Workflows live in their module
+✅ **Config Isolation** - Each module uses its own configuration
+✅ **Customization Ready** - Vendored workflows can be modified independently
+✅ **No User Confusion** - Avoid partial module installations

 ### File Processing

@@ -346,6 +378,7 @@ bmad status -v      # Detailed status
 - Excludes `_module-installer/` directories
 - Replaces path placeholders at runtime
 - Injects activation blocks
+- Vendors cross-module workflows (see Workflow Vendoring below)

 ### Web Bundling

--- a/docs/installers-bundlers/web-bundler-usage.md
+++ b/docs/installers-bundlers/web-bundler-usage.md
@@ -1,54 +0,0 @@
-# Web Bundler Usage
-
-ALPHA NOTE: Bundling of individual agents might work, team bundling is being reworked and will come with Beta release soon.
-
-The web bundler creates self-contained XML bundles for BMAD agents, packaging all dependencies for web deployment.
-
-## Quick Start
-
-```bash
-# Bundle all agents from all modules
-npm run bundle
-
-# Clean and rebundle (removes old bundles first)
-npm run rebundle
-```
-
-## Custom Output Directory
-
-```bash
-# Bundle to custom directory
-node tools/cli/bundlers/bundle-web.js all --output ./my-bundles
-
-# Rebundle to custom directory (auto-cleans first)
-node tools/cli/bundlers/bundle-web.js rebundle --output /absolute/path/to/custom/directory
-
-# Bundle specific module to custom directory
-node tools/cli/bundlers/bundle-web.js module bmm --output ./custom-folder
-
-# Bundle specific agent to custom directory
-node tools/cli/bundlers/bundle-web.js agent bmm analyst -o ./custom-folder
-```
-
-## Output
-
-Bundles are generated in `web-bundles/` directory by default when run from the root of the clones project:
-
-```
-web-bundles/
-├── [module-name]/
-│   └── agents/
-│       └── [agent-name].xml
-```
-
-## Skipping Agents
-
-Agents with `bundle="false"` attribute are automatically skipped during bundling.
-
-## Bundle Contents
-
-Each bundle includes:
-
- Agent definition with web activation
- All resolved dependencies
- Manifests for agent/team discovery
--- a/docs/v4-to-v6-upgrade.md
+++ b/docs/v4-to-v6-upgrade.md
@@ -0,0 +1,227 @@
+# BMad v4 to v6 Upgrade Guide
+
+## Overview
+
+BMad v6 represents a complete ground-up rewrite with significant architectural changes. This guide will help you migrate your v4 project to v6.
+
+---
+
+## Automatic V4 Detection
+
+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`
+- **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
+   - If a backup already exists, a timestamp is added to avoid conflicts
+   - 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
+   - Located in IDE config folders: `.claude/commands/`, `.cursor/commands/`, etc.
+   - These old commands would still reference v4 folder structure if left in place
+   - The installer provides copy/paste terminal commands for your platform
+   - You can proceed without cleanup, but removing them prevents confusion with old v4 commands
+
+---
+
+## Module Migration
+
+### Deprecated Modules
+
+| 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          |
+
+**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.
+
+---
+
+## Architecture Changes
+
+### Folder Structure
+
+**v4 "Expansion Packs" Structure:**
+
+```
+your-project/
+├── .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
+    ├── 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
+        └── 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
+- **Module identification**: All modules now have a `config.yaml` file
+
+---
+
+## Project Progress Migration
+
+### If You've Completed Planning Phase (PRD/Architecture) with the BMad Method:
+
+After running the v6 installer:
+
+1. **Run `workflow-init`** workflow to set up the guided workflow system
+2. **Specify your project level** when prompted:
+   - If you followed v4's full workflow (PRD → Architecture → Stories), select **Level 3 or 4**
+   - This tells v6 you've already completed planning and solutioning phases
+3. **Document paths**: Keep your existing paths during installation
+   - Default PRD/Architecture location: `docs/`
+   - Default stories location: `docs/sprint-artifacts/`
+   - **Accept these defaults** if you're already using them in v4
+
+> **Important**: v6 workflows can handle both sharded and unsharded documents. You don't need to restructure your existing PRD or architecture files.
+
+### If You're Mid-Development (Stories Created/Implemented)
+
+1. Complete the v6 installation as above
+2. Run `workflow-init` and specify Level 3 or 4
+3. When ready to continue development, run the **`sprint-planning`** workflow (Phase 4)
+
+---
+
+## Agent Customization Migration
+
+### v4 Agent Customization
+
+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:
+
+**Example: Renaming an agent and changing communication style**
+
+File: `{bmad_folder}/_cfg/agents/bmm-pm.customize.yaml`
+
+```yaml
+# Customize the PM agent
+persona:
+  name: 'Captain Jack' # Override agent name
+  role: 'Swashbuckling Product Owner'
+  communication_style: |
+    - Talk like a pirate
+    - Use nautical metaphors for software concepts
+    - Always upbeat and adventurous
+```
+
+**How it works:**
+
+- Base agent: `{bmad_folder}/bmm/agents/pm.md`
+- Customization: `{bmad_folder}/_cfg/agents/bmm-pm.customize.yaml`
+- Result: Agent uses your custom name and style, but updates don't overwrite your changes
+
+---
+
+## Document Compatibility
+
+### Sharded vs Unsharded Documents
+
+**Good news**: Unlike v4, v6 workflows are **fully flexible** with document structure:
+
+- ✅ Sharded documents (split into multiple files)
+- ✅ Unsharded documents (single file per section)
+- ✅ Custom sections for your project type
+- ✅ Mixed approaches
+
+All workflow files are scanned automatically. No manual configuration needed.
+
+---
+
+## Installation Steps
+
+### 1. Clone Repository
+
+```bash
+git clone https://github.com/bmad-code-org/BMAD-METHOD
+cd BMAD-METHOD
+npm install
+```
+
+### 2. Run Installer on Your v4 Project
+
+```bash
+npx bmad-method install
+```
+
+**Enter the full path to your v4 project** when prompted.
+
+### 3. Follow Interactive Prompts
+
+The installer will:
+
+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.)
+5. Configure module-specific options
+6. Configure IDE integrations
+
+### 4. Accept Default Paths
+
+If you're using:
+
+- `docs/` for PRD and architecture
+- `docs/sprint-artifacts/` for story files
+
+**Accept these defaults** during installation.
+
+### 5. Initialize Workflow
+
+After installation:
+
+1. **Load the Analyst agent** - See your IDE-specific instructions in [docs/ide-info](./ide-info/) for how to activate agents:
+   - [Claude Code](./ide-info/claude-code.md)
+   - [Cursor](./ide-info/cursor.md)
+   - [VS Code/Windsurf](./ide-info/) - Check your IDE folder
+
+2. **Wait for the agent's menu** to appear
+
+3. **Tell the agent**: `*workflow-init` - v6 supports excellent natural language fuzzy matching, so you could also say "workflow init" or "please init the workflow"
+
+Since you are migrating an existing project from v4, it's most likely **Level 3 or 4** you will want to suggest when asked - if you've already completed PRD/architecture in v4.
+
+---
+
+## Post-Migration Checklist
+
+- [ ] v4 folders backed up to `v4-backup/`
+- [ ] v6 installed to `{bmad_folder}/` folder
+- [ ] `workflow-init` run with correct project level selected
+- [ ] Agent customizations migrated to `{bmad_folder}/_cfg/agents/` if needed
+- [ ] IDE integration working (test by listing agents)
+- [ ] For active development: `sprint-planning` workflow executed
+
+---
+
+## Getting Help
+
+- **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
--- a/docs/v6-open-items.md
+++ b/docs/v6-open-items.md
@@ -0,0 +1,17 @@
+# 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
--- a/docs/web-bundles-gemini-gpt-guide.md
+++ b/docs/web-bundles-gemini-gpt-guide.md
@@ -0,0 +1,473 @@
+# Using BMad Web Bundles in Gemini Gems & Custom GPTs
+
+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?
+
+Web bundles are standalone XML files containing:
+
+- Complete agent persona and instructions
+- All workflows and dependencies
+- Interactive menu system
+- Party mode for multi-agent collaboration
+- 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
--- a/docs/workflow-compliance-report-create-workflow.md
+++ b/docs/workflow-compliance-report-create-workflow.md
@@ -0,0 +1,513 @@
+---
+name: 'Workflow Compliance Report - create-workflow'
+description: 'Systematic validation results for create-workflow workflow'
+workflow_name: 'create-workflow'
+validation_date: '2025-12-02'
+stepsCompleted: ['workflow-validation', 'step-validation', 'file-validation', 'spectrum-validation', 'web-subprocess-validation']
+---
+
+# Workflow Compliance Report: create-workflow
+
+**Validation Date:** 2025-12-02
+**Target Workflow:** /Users/brianmadison/dev/BMAD-METHOD/src/modules/bmb/workflows/create-workflow/workflow.md
+**Reference Standard:** /Users/brianmadison/dev/BMAD-METHOD/.bmad/bmb/docs/workflows/templates/workflow-template.md
+
+## Phase 1: Workflow.md Validation Results
+
+### Template Adherence Analysis
+
+**Reference Standard:** workflow-template.md
+
+### Frontmatter Structure Violations
+
+✅ **PASS** - All required fields present and properly formatted:
+
+- name: "Create Workflow" ✓
+- description: "Create structured standalone workflows using markdown-based step architecture" ✓
+- web_bundle: true (proper boolean format) ✓
+
+### Role Description Violations
+
+✅ **PASS** - Role description follows template format:
+
+- Partnership language present: "This is a partnership, not a client-vendor relationship" ✓
+- Expertise clearly defined: "workflow architect and systems designer" ✓
+- User expertise identified: "domain knowledge and specific workflow requirements" ✓
+- Collaboration directive: "Work together as equals" ✓
+
+### Workflow Architecture Violations
+
+🚫 **CRITICAL VIOLATION** - Core Principles deviate from template:
+
+**Template requires:** "Each step of the overall goal is a self contained instruction file that you will adhere too 1 file as directed at a time"
+
+**Target has:** "Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly"
+
+- **Severity:** Critical
+- **Template Reference:** "Core Principles" section in workflow-template.md
+- **Specific Fix:** Replace with exact template wording: "Each step of the overall goal is a self contained instruction file that you will adhere too 1 file as directed at a time"
+
+🚫 **CRITICAL VIOLATION** - State Tracking Rule deviates from template:
+
+**Template requires:** "Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document"
+
+**Target has:** "Document progress in context for compliance checking (no output file frontmatter needed)"
+
+- **Severity:** Critical
+- **Template Reference:** "Core Principles" section in workflow-template.md
+- **Specific Fix:** Replace with exact template wording about stepsCompleted array
+
+### Initialization Sequence Violations
+
+🚫 **MAJOR VIOLATION** - Configuration path format incorrect:
+
+**Template requires:** "{project-root}/.bmad/[MODULE FOLDER]/config.yaml"
+
+**Target has:** "{project-root}/.bmad/bmb/config.yaml"
+
+- **Severity:** Major
+- **Template Reference:** "Module Configuration Loading" section in workflow-template.md
+- **Specific Fix:** Use proper module variable substitution: "{project-root}/.bmad/bmb/config.yaml" should reference module folder properly
+
+🚫 **MAJOR VIOLATION** - First step path format inconsistent:
+
+**Template requires:** Explicit step file path following pattern
+
+**Target has:** "Load, read the full file and then execute `{workflow_path}/steps/step-01-init.md` to begin the workflow."
+
+- **Severity:** Major
+- **Template Reference:** "First Step EXECUTION" section in workflow-template.md
+- **Specific Fix:** Ensure consistency with template variable substitution patterns
+
+### Phase 1 Summary
+
+**Critical Issues:** 2
+
+- Core Principles text deviation from template
+- State Tracking rule modification from template standard
+
+**Major Issues:** 2
+
+- Configuration path format not following template variable pattern
+- First step execution path needs consistency check
+
+**Minor Issues:** 0
+
+### Phase 1 Recommendations
+
+**Priority 1 - Critical Fixes:**
+
+1. Replace Core Principles text with exact template wording
+2. Restore State Tracking rule to template standard about stepsCompleted array
+
+**Priority 2 - Major Fixes:**
+
+1. Review and standardize all path variable usage to follow template patterns
+2. Ensure consistency in variable substitution throughout workflow
+
+## Phase 2: Step Validation Results
+
+### Template Adherence Analysis
+
+**Reference Standard:** step-template.md
+**Total Steps Analyzed:** 9
+
+### Critical Violations Summary
+
+**Step 01-init.md:**
+
+- Missing `outputFile` in frontmatter - Template Reference: line 22
+- Uses auto-proceed menu instead of standard A/P/C pattern - Template Reference: lines 106-123
+- Missing "CRITICAL STEP COMPLETION NOTE" section - Template Reference: line 126
+
+**Step 02-gather.md:**
+
+- Missing `outputFile` in frontmatter - Template Reference: line 22
+- Incorrect `nextStepFile` path format - Template Reference: line 19
+
+**Steps 03-09 (All Steps):**
+
+- Missing `outputFile` in frontmatter - Template Reference: line 22
+- Non-standard step naming (missing short descriptive names) - Template Reference: line 9
+- Steps 08-09 missing `workflowFile` in frontmatter - Template Reference: line 21
+
+### Major Violations Summary
+
+**Frontmatter Structure (All Steps):**
+
+- Missing `altStep{Y}` comment pattern - Template Reference: line 20
+- Missing Task References section structure - Template Reference: lines 24-27
+- Missing Template References section structure - Template Reference: lines 29-33
+- Missing Data References section structure - Template Reference: lines 35-37
+
+**Menu Pattern Violations:**
+
+- Step 01: Custom auto-proceed menu instead of standard A/P/C - Template Reference: lines 106-123
+- Step 05: Menu text "Continue" instead of "Continue to [next action]" - Template Reference: line 115
+- Step 07: Custom "Build Complete" menu instead of A/P/C pattern - Template Reference: lines 106-123
+- Step 08: Missing A and P options in menu - Template Reference: lines 106-123
+- Step 09: Uses T/M/D pattern instead of standard A/P/C - Template Reference: lines 106-123
+
+### Path Variable Inconsistencies
+
+- Inconsistent use of `{bmad_folder}` vs `.bmad` in paths across all steps
+- Missing `outputFile` variable definitions - Template Reference: line 22
+- Step 04 uses non-standard `nextStepFormDesign` and `nextStepDesign` variables
+
+### Minor Violations Summary
+
+**Content Structure:**
+
+- Missing "CONTEXT BOUNDARIES" section titles - Template Reference: line 82
+- Missing "EXECUTION PROTOCOLS" section titles - Template Reference: line 75
+- Non-standard section naming in multiple steps - Template Reference: line 89
+
+### Phase 2 Summary
+
+**Critical Issues:** 15
+
+- 9 missing outputFile variables
+- 6 non-standard menu patterns
+- Multiple missing required sections
+
+**Major Issues:** 36
+
+- 36 frontmatter structure violations across all steps
+- 5 menu pattern deviations
+- Numerous path variable inconsistencies
+
+**Minor Issues:** 27
+
+- Section naming inconsistencies
+- Missing template-required section titles
+
+**Most Common Violations:**
+
+1. Missing `outputFile` in frontmatter (9 occurrences)
+2. Non-standard menu patterns (6 occurrences)
+3. Missing Task/Template/Data References sections (27 occurrences)
+
+### Overall Step Compliance Score
+
+**Overall Workflow Step Compliance: 68%**
+
+- Step 01: 65% compliant
+- Step 02: 70% compliant
+- Steps 03-09: 63-72% compliant each
+
+## Phase 3: File Size, Formatting, and Data Validation Results
+
+### File Size Analysis
+
+**Workflow File:**
+
+- workflow.md: 2.9K - ✅ **Optimal** - Excellent performance and maintainability
+
+**Step Files Distribution:**
+
+- **Optimal (≤5K):** 3 files
+  - step-09-complete.md: 5.1K
+  - step-01-init.md: 5.3K
+- **Good (5K-7K):** 1 file
+  - step-04-plan-review.md: 6.6K
+- **Acceptable (7K-10K):** 5 files
+  - step-02-gather.md: 7.8K
+  - step-08-review.md: 7.9K
+  - step-03-tools-configuration.md: 7.9K
+  - step-05-output-format-design.md: 8.2K
+  - step-06-design.md: 9.0K
+- **Acceptable (approaching concern):** 1 file
+  - step-07-build.md: 10.0K (monitor if additional features added)
+
+**CSV Data Files:**
+
+- Total CSV files: 0
+- No data files present requiring validation
+
+### Markdown Formatting Validation
+
+**✅ Strengths:**
+
+- Consistent frontmatter structure across all files
+- Proper heading hierarchy (H1→H2→H3) maintained
+- Standardized section patterns across all steps
+- Proper code block formatting in 7 of 10 files
+- Consistent bullet point usage throughout
+
+**⚠️ Minor Issues:**
+
+- File size range significant (2.9K to 10K) but all within acceptable limits
+- step-07-build.md approaching concern threshold at 10K
+
+### Performance Impact Assessment
+
+**Overall workflow performance:** ✅ **Excellent**
+
+- All files optimized for performance
+- No files requiring immediate size optimization
+- Well-structured maintainable codebase
+- Professional markdown implementation
+
+**Most critical file size issue:** None - all files within acceptable ranges
+**Primary formatting concerns:** None significant - excellent consistency maintained
+
+## Phase 4: Intent vs Prescriptive Spectrum Analysis
+
+### Current Position Assessment
+
+**Analyzed Position:** Balanced Middle (leaning prescriptive)
+**Evidence:**
+
+- Highly structured step files with mandatory execution rules
+- Specific sequence enforcement and template compliance requirements
+- Conversational partnership model within rigid structural constraints
+- Limited creative adaptation but maintains collaborative dialogue
+  **Confidence Level:** High - Clear patterns in implementation demonstrate intentional structure
+
+### Expert Recommendation
+
+**Recommended Position:** Balanced Middle (slightly toward prescriptive)
+**Reasoning:**
+
+- Workflow creation needs systematic structure for BMAD compliance
+- Template requirements demand prescriptive elements
+- Creative aspects need room for user ownership
+- Best workflows emerge from structured collaboration
+  **Workflow Type Considerations:**
+- Primary purpose: Creating structured, repeatable workflows
+- User expectations: Reliable, consistent BMAD-compliant outputs
+- Success factors: Template compliance and systematic approach
+- Risk level: Medium - compliance critical for ecosystem coherence
+
+### User Decision
+
+**Selected Position:** Option 1 - Keep Current Position (Balanced Middle leaning prescriptive)
+**Rationale:** User prefers to maintain current structured approach
+**Implementation Guidance:**
+
+- Continue with current balance of structure and collaborative dialogue
+- Maintain template compliance requirements
+- Preserve systematic execution patterns
+- Keep conversational elements within prescribed framework
+
+### Spectrum Validation Results
+
+✅ Spectrum position is intentional and understood
+✅ User educated on implications of their choice
+✅ Implementation guidance provided for maintaining position
+✅ Decision documented for future reference
+
+## Phase 5: Web Search & Subprocess Optimization Analysis
+
+### Web Search Optimization
+
+**Unnecessary Searches Identified:** 1
+
+- Step 6 loads 5+ template files individually - these are static templates that rarely change
+  **Essential Searches to Keep:** 2
+- CSV tool database in Step 3 (dynamic data)
+- Reference workflow example in Step 2 (concrete patterns)
+  **Optimization Recommendations:**
+- Implement template caching to eliminate repeated file loads
+- Use selective CSV loading based on workflow type
+  **Estimated Time Savings:** 5-7 seconds per workflow execution
+
+### Subprocess Optimization Opportunities
+
+**Parallel Processing:** 2 major opportunities identified
+
+1. **Step 3 + Step 5 Parallelization:** Tools configuration and output format design can run simultaneously
+   - Savings: 5-10 minutes per workflow
+2. **Background Template Loading:** Pre-load templates during Step 1 idle time
+   - Savings: Eliminate design-phase delays
+
+**Batch Processing:** 1 grouping opportunity
+
+- Parallel file generation in Step 7 (workflow.md, step files, templates)
+- Savings: 60-80% reduction in build time for multi-step workflows
+
+**Background Processing:** 2 task opportunities
+
+- Template pre-loading during initialization
+- File generation coordination during build phase
+
+**Performance Improvement:** 40-60% estimated overall improvement
+
+### Resource Efficiency Analysis
+
+**Context Optimization:**
+
+- JIT context loading: 40-60% reduction in token usage
+- Reference content deduplication: 8,000-12,000 token savings
+- Step file size reduction: 30-50% smaller files
+
+**LLM Resource Usage:**
+
+- Smart context pruning by workflow phase
+- Compact step instructions with external references
+- Selective context loading based on current phase
+
+**User Experience Impact:**
+
+- Significantly faster workflow creation (15-25 minutes saved)
+- More responsive interaction patterns
+- Reduced waiting times during critical phases
+
+### Implementation Recommendations
+
+**Immediate Actions (High Impact, Low Risk):**
+
+1. Implement template caching in workflow.md frontmatter
+2. Optimize CSV loading with category filtering
+3. Reduce step file sizes by moving examples to reference files
+
+**Strategic Improvements (High Impact, Medium Risk):**
+
+1. Parallelize Step 3 and Step 5 execution
+2. Implement JIT context loading by phase
+3. Background template pre-loading
+
+**Future Enhancements (Highest Impact, Higher Risk):**
+
+1. Parallel file generation with sub-process coordination
+2. Smart context pruning across workflow phases
+3. Complete reference deduplication system
+
+## Phase 6: Holistic Workflow Analysis Results
+
+### Flow Validation
+
+**Completion Path Analysis:**
+
+- ✅ All steps have clear continuation paths
+- ✅ No orphaned steps or dead ends
+- ⚠️ Minor issue: Steps 07 and 09 use non-standard menu patterns
+
+**Sequential Logic:**
+
+- ✅ Logical workflow creation progression maintained
+- ✅ Dependencies properly structured
+- ⚠️ Steps 05-06 could potentially be consolidated
+
+### Goal Alignment
+
+**Alignment Score:** 85%
+
+**Stated Goal:** "Create structured, repeatable standalone workflows through collaborative conversation and step-by-step guidance"
+
+**Actual Implementation:** Creates structured workflows with heavy emphasis on template compliance and systematic validation
+
+**Gap Analysis:**
+
+- Workflow emphasizes structure over creativity (aligned with spectrum choice)
+- Template compliance heavier than user guidance (may need balance adjustment)
+
+### Meta-Workflow Failure Analysis
+
+**Issues That Should Have Been Prevented by create-workflow:**
+
+1. Missing outputFile variables in all 9 steps (Critical)
+2. Non-standard menu patterns in Steps 07 and 09 (Major)
+3. Missing Task/Template/Data references across all steps (Major)
+4. Path variable inconsistencies throughout workflow (Major)
+5. Step naming violations for Steps 05-09 (Major)
+6. Core Principles text deviation from template (Critical)
+
+**Recommended Meta-Workflow Improvements:**
+
+- Add frontmatter completeness validation during creation
+- Implement path variable format checking
+- Include menu pattern enforcement validation
+- Add Intent vs Prescriptive spectrum selection in Step 01
+- Validate template compliance before finalization
+
+---
+
+## Executive Summary
+
+**Overall Compliance Status:** PARTIAL
+**Critical Issues:** 17 - Must be fixed immediately
+**Major Issues:** 36 - Significantly impacts quality/maintainability
+**Minor Issues:** 27 - Standards compliance improvements
+
+**Overall Compliance Score:** 68% based on template adherence
+
+## Severity-Ranked Fix Recommendations
+
+### IMMEDIATE - Critical (Must Fix for Functionality)
+
+1. **Missing outputFile Variables** - Files: All 9 step files
+   - **Problem:** Critical frontmatter field missing from all steps
+   - **Template Reference:** step-template.md line 22
+   - **Fix:** Add `outputFile: '{output_folder}/workflow-plan-{project_name}.md'` to each step
+   - **Impact:** Workflow cannot produce output without this field
+
+2. **Core Principles Deviation** - File: workflow.md
+   - **Problem:** Text modified from template standard
+   - **Template Reference:** workflow-template.md Core Principles section
+   - **Fix:** Replace with exact template wording
+   - **Impact:** Violates fundamental BMAD workflow architecture
+
+3. **Non-Standard Menu Patterns** - Files: step-07-build.md, step-09-complete.md
+   - **Problem:** Custom menu formats instead of A/P/C pattern
+   - **Template Reference:** step-template.md lines 106-123
+   - **Fix:** Standardize to A/P/C menu pattern
+   - **Impact:** Breaks user experience consistency
+
+### HIGH PRIORITY - Major (Significantly Impacts Quality)
+
+1. **Missing Task/Template/Data References** - Files: All 9 step files
+   - **Problem:** Required frontmatter sections missing
+   - **Template Reference:** step-template.md lines 24-37
+   - **Fix:** Add all required reference sections with proper comments
+   - **Impact:** Violates template structure standards
+
+2. **Step Naming Violations** - Files: steps 05-09
+   - **Problem:** Missing short descriptive names in step filenames
+   - **Template Reference:** step-template.md line 9
+   - **Fix:** Rename to include descriptive names (e.g., step-05-output-format.md)
+   - **Impact:** Inconsistent with BMAD naming conventions
+
+3. **Path Variable Inconsistencies** - Files: All steps
+   - **Problem:** Mixed use of `{bmad_folder}` vs `.bmad`
+   - **Template Reference:** workflow-template.md path patterns
+   - **Fix:** Standardize to template variable patterns
+   - **Impact:** Installation flexibility and maintainability
+
+### MEDIUM PRIORITY - Minor (Standards Compliance)
+
+1. **Missing Section Titles** - Files: All steps
+   - **Problem:** Missing "CONTEXT BOUNDARIES" and "EXECUTION PROTOCOLS" titles
+   - **Template Reference:** step-template.md lines 75, 82
+   - **Fix:** Add missing section titles
+   - **Impact:** Template compliance
+
+## Automated Fix Options
+
+### Fixes That Can Be Applied Automatically
+
+- Add outputFile variables to all step frontmatter
+- Add missing section titles
+- Standardize path variable usage
+- Add Task/Template/Data reference section skeletons
+
+### Fixes Requiring Manual Review
+
+- Core Principles text restoration (needs exact template matching)
+- Menu pattern standardization (custom logic may be intentional)
+- Step renaming (requires file system changes and reference updates)
+
+## Next Steps Recommendation
+
+**Recommended Approach:**
+
+1. Fix all Critical issues immediately (workflow may not function)
+2. Address Major issues for reliability and maintainability
+3. Implement Minor issues for full standards compliance
+4. Update meta-workflows to prevent future violations
+
+**Estimated Effort:**
+
+- Critical fixes: 2-3 hours
+- Major fixes: 4-6 hours
+- Minor fixes: 1-2 hours
--- a/eslint.config.mjs
+++ b/eslint.config.mjs
@@ -14,6 +14,10 @@ export default [
      'test/template-test-generator/**',
      'test/template-test-generator/**/*.js',
      'test/template-test-generator/**/*.md',
+      'test/fixtures/**',
+      'test/fixtures/**/*.yaml',
+      '.bmad/**',
+      '.bmad*/**',
    ],
  },

@@ -59,9 +63,9 @@ export default [
    },
  },

-  // CLI/CommonJS scripts under tools/**
+  // CLI/CommonJS scripts under tools/** and test/**
  {
-    files: ['tools/**/*.js'],
+    files: ['tools/**/*.js', 'test/**/*.js'],
    rules: {
      // Allow CommonJS patterns for Node CLI scripts
      'unicorn/prefer-module': 'off',
--- a/package-lock.json
+++ b/package-lock.json
@@ -1,16 +1,15 @@
 {
  "name": "bmad-method",
-  "version": "6.0.0-alpha.0",
+  "version": "6.0.0-alpha.12",
  "lockfileVersion": 3,
  "requires": true,
  "packages": {
    "": {
      "name": "bmad-method",
-      "version": "6.0.0-alpha.0",
+      "version": "6.0.0-alpha.12",
      "license": "MIT",
      "dependencies": {
-        "@kayvan/markdown-tree-parser": "^1.5.0",
-        "bmad-method": "^4.30.3",
+        "@kayvan/markdown-tree-parser": "^1.6.1",
        "boxen": "^5.1.2",
        "chalk": "^4.1.2",
        "cli-table3": "^0.6.5",
@@ -25,13 +24,16 @@
        "ora": "^5.4.1",
        "semver": "^7.6.3",
        "wrap-ansi": "^7.0.0",
-        "xml2js": "^0.6.2"
+        "xml2js": "^0.6.2",
+        "yaml": "^2.7.0"
      },
      "bin": {
-        "bmad": "tools/cli/bmad-cli.js"
+        "bmad": "tools/bmad-npx-wrapper.js",
+        "bmad-method": "tools/bmad-npx-wrapper.js"
      },
      "devDependencies": {
        "@eslint/js": "^9.33.0",
+        "c8": "^10.1.3",
        "eslint": "^9.33.0",
        "eslint-config-prettier": "^10.1.8",
        "eslint-plugin-n": "^17.21.3",
@@ -43,7 +45,8 @@
        "prettier": "^3.5.3",
        "prettier-plugin-packagejson": "^2.5.19",
        "yaml-eslint-parser": "^1.2.3",
-        "yaml-lint": "^1.7.0"
+        "yaml-lint": "^1.7.0",
+        "zod": "^4.1.12"
      },
      "engines": {
        "node": ">=20.0.0"
@@ -1020,9 +1023,9 @@
      }
    },
    "node_modules/@istanbuljs/load-nyc-config/node_modules/js-yaml": {
-      "version": "3.14.1",
-      "resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-3.14.1.tgz",
-      "integrity": "sha512-okMH7OXXJ7YrN9Ok3/SXrnu4iX9yOk+25nqX4imS2npuvTYDmo/QEZoqwZkYaIDk3jVvBOTOIEgEhaLOynBS9g==",
+      "version": "3.14.2",
+      "resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-3.14.2.tgz",
+      "integrity": "sha512-PMSmkqxr106Xa156c2M265Z+FTrPl+oxd/rgOQy2tijQeK5TxQ43psO1ZCwhVOSdnn+RzkzlRz/eY4BgJBYVpg==",
      "dev": true,
      "license": "MIT",
      "dependencies": {
@@ -1326,9 +1329,9 @@
      }
    },
    "node_modules/@jest/reporters/node_modules/glob": {
-      "version": "10.4.5",
-      "resolved": "https://registry.npmjs.org/glob/-/glob-10.4.5.tgz",
-      "integrity": "sha512-7Bv8RF0k6xjo7d4A/PxYLbUCfb6c+Vpd2/mB2yRDlew7Jb5hEXiCD9ibfO7wpk8i4sevK6DFny9h7EYbM3/sHg==",
+      "version": "10.5.0",
+      "resolved": "https://registry.npmjs.org/glob/-/glob-10.5.0.tgz",
+      "integrity": "sha512-DfXN8DfhJ7NH3Oe7cFmu3NCu1wKbkReJ8TorzSAFbSKrlNaQSKfIzqYqVY8zlbs2NLBbWpRiU52GX2PbaBVNkg==",
      "dev": true,
      "license": "ISC",
      "dependencies": {
@@ -2397,32 +2400,6 @@
        "readable-stream": "^3.4.0"
      }
    },
-    "node_modules/bmad-method": {
-      "version": "4.40.0",
-      "resolved": "https://registry.npmjs.org/bmad-method/-/bmad-method-4.40.0.tgz",
-      "integrity": "sha512-FE+5GprBOf2x3AIpeH8iVJF3/JXtzTWbPSDTwUS3Y0Dq0IaW82FxwyiFykTRxPW/oDEK6YCyNkU4EO2Lq8E89A==",
-      "license": "MIT",
-      "dependencies": {
-        "@kayvan/markdown-tree-parser": "^1.5.0",
-        "bmad-method": "^4.30.3",
-        "chalk": "^4.1.2",
-        "commander": "^14.0.0",
-        "fs-extra": "^11.3.0",
-        "glob": "^11.0.3",
-        "ignore": "^7.0.5",
-        "inquirer": "^8.2.6",
-        "js-yaml": "^4.1.0",
-        "ora": "^5.4.1",
-        "semver": "^7.6.3"
-      },
-      "bin": {
-        "bmad": "tools/bmad-npx-wrapper.js",
-        "bmad-method": "tools/bmad-npx-wrapper.js"
-      },
-      "engines": {
-        "node": ">=20.10.0"
-      }
-    },
    "node_modules/boolbase": {
      "version": "1.0.0",
      "resolved": "https://registry.npmjs.org/boolbase/-/boolbase-1.0.0.tgz",
@@ -2586,6 +2563,152 @@
        "url": "https://github.com/sponsors/sindresorhus"
      }
    },
+    "node_modules/c8": {
+      "version": "10.1.3",
+      "resolved": "https://registry.npmjs.org/c8/-/c8-10.1.3.tgz",
+      "integrity": "sha512-LvcyrOAaOnrrlMpW22n690PUvxiq4Uf9WMhQwNJ9vgagkL/ph1+D4uvjvDA5XCbykrc0sx+ay6pVi9YZ1GnhyA==",
+      "dev": true,
+      "license": "ISC",
+      "dependencies": {
+        "@bcoe/v8-coverage": "^1.0.1",
+        "@istanbuljs/schema": "^0.1.3",
+        "find-up": "^5.0.0",
+        "foreground-child": "^3.1.1",
+        "istanbul-lib-coverage": "^3.2.0",
+        "istanbul-lib-report": "^3.0.1",
+        "istanbul-reports": "^3.1.6",
+        "test-exclude": "^7.0.1",
+        "v8-to-istanbul": "^9.0.0",
+        "yargs": "^17.7.2",
+        "yargs-parser": "^21.1.1"
+      },
+      "bin": {
+        "c8": "bin/c8.js"
+      },
+      "engines": {
+        "node": ">=18"
+      },
+      "peerDependencies": {
+        "monocart-coverage-reports": "^2"
+      },
+      "peerDependenciesMeta": {
+        "monocart-coverage-reports": {
+          "optional": true
+        }
+      }
+    },
+    "node_modules/c8/node_modules/@bcoe/v8-coverage": {
+      "version": "1.0.2",
+      "resolved": "https://registry.npmjs.org/@bcoe/v8-coverage/-/v8-coverage-1.0.2.tgz",
+      "integrity": "sha512-6zABk/ECA/QYSCQ1NGiVwwbQerUCZ+TQbp64Q3AgmfNvurHH0j8TtXa1qbShXA6qqkpAj4V5W8pP6mLe1mcMqA==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/c8/node_modules/brace-expansion": {
+      "version": "2.0.2",
+      "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-2.0.2.tgz",
+      "integrity": "sha512-Jt0vHyM+jmUBqojB7E1NIYadt0vI0Qxjxd2TErW94wDz+E2LAm5vKMXXwg6ZZBTHPuUlDgQHKXvjGBdfcF1ZDQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "balanced-match": "^1.0.0"
+      }
+    },
+    "node_modules/c8/node_modules/glob": {
+      "version": "10.5.0",
+      "resolved": "https://registry.npmjs.org/glob/-/glob-10.5.0.tgz",
+      "integrity": "sha512-DfXN8DfhJ7NH3Oe7cFmu3NCu1wKbkReJ8TorzSAFbSKrlNaQSKfIzqYqVY8zlbs2NLBbWpRiU52GX2PbaBVNkg==",
+      "dev": true,
+      "license": "ISC",
+      "dependencies": {
+        "foreground-child": "^3.1.0",
+        "jackspeak": "^3.1.2",
+        "minimatch": "^9.0.4",
+        "minipass": "^7.1.2",
+        "package-json-from-dist": "^1.0.0",
+        "path-scurry": "^1.11.1"
+      },
+      "bin": {
+        "glob": "dist/esm/bin.mjs"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/isaacs"
+      }
+    },
+    "node_modules/c8/node_modules/jackspeak": {
+      "version": "3.4.3",
+      "resolved": "https://registry.npmjs.org/jackspeak/-/jackspeak-3.4.3.tgz",
+      "integrity": "sha512-OGlZQpz2yfahA/Rd1Y8Cd9SIEsqvXkLVoSw/cgwhnhFMDbsQFeZYoJJ7bIZBS9BcamUW96asq/npPWugM+RQBw==",
+      "dev": true,
+      "license": "BlueOak-1.0.0",
+      "dependencies": {
+        "@isaacs/cliui": "^8.0.2"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/isaacs"
+      },
+      "optionalDependencies": {
+        "@pkgjs/parseargs": "^0.11.0"
+      }
+    },
+    "node_modules/c8/node_modules/lru-cache": {
+      "version": "10.4.3",
+      "resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-10.4.3.tgz",
+      "integrity": "sha512-JNAzZcXrCt42VGLuYz0zfAzDfAvJWW6AfYlDBQyDV5DClI2m5sAmK+OIO7s59XfsRsWHp02jAJrRadPRGTt6SQ==",
+      "dev": true,
+      "license": "ISC"
+    },
+    "node_modules/c8/node_modules/minimatch": {
+      "version": "9.0.5",
+      "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-9.0.5.tgz",
+      "integrity": "sha512-G6T0ZX48xgozx7587koeX9Ys2NYy6Gmv//P89sEte9V9whIapMNF4idKxnW2QtCcLiTWlb/wfCabAtAFWhhBow==",
+      "dev": true,
+      "license": "ISC",
+      "dependencies": {
+        "brace-expansion": "^2.0.1"
+      },
+      "engines": {
+        "node": ">=16 || 14 >=14.17"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/isaacs"
+      }
+    },
+    "node_modules/c8/node_modules/path-scurry": {
+      "version": "1.11.1",
+      "resolved": "https://registry.npmjs.org/path-scurry/-/path-scurry-1.11.1.tgz",
+      "integrity": "sha512-Xa4Nw17FS9ApQFJ9umLiJS4orGjm7ZzwUrwamcGQuHSzDyth9boKDaycYdDcZDuqYATXw4HFXgaqWTctW/v1HA==",
+      "dev": true,
+      "license": "BlueOak-1.0.0",
+      "dependencies": {
+        "lru-cache": "^10.2.0",
+        "minipass": "^5.0.0 || ^6.0.2 || ^7.0.0"
+      },
+      "engines": {
+        "node": ">=16 || 14 >=14.18"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/isaacs"
+      }
+    },
+    "node_modules/c8/node_modules/test-exclude": {
+      "version": "7.0.1",
+      "resolved": "https://registry.npmjs.org/test-exclude/-/test-exclude-7.0.1.tgz",
+      "integrity": "sha512-pFYqmTw68LXVjeWJMST4+borgQP2AyMNbg1BpZh9LbyhUeNkeaPF9gzfPGUAnSMV3qPYdWUwDIjjCLiSDOl7vg==",
+      "dev": true,
+      "license": "ISC",
+      "dependencies": {
+        "@istanbuljs/schema": "^0.1.2",
+        "glob": "^10.4.1",
+        "minimatch": "^9.0.4"
+      },
+      "engines": {
+        "node": ">=18"
+      }
+    },
    "node_modules/callsites": {
      "version": "3.1.0",
      "resolved": "https://registry.npmjs.org/callsites/-/callsites-3.1.0.tgz",
@@ -3980,14 +4103,14 @@
      }
    },
    "node_modules/glob": {
-      "version": "11.0.3",
-      "resolved": "https://registry.npmjs.org/glob/-/glob-11.0.3.tgz",
-      "integrity": "sha512-2Nim7dha1KVkaiF4q6Dj+ngPPMdfvLJEOpZk/jKiUAkqKebpGAWQXAq9z1xu9HKu5lWfqw/FASuccEjyznjPaA==",
-      "license": "ISC",
+      "version": "11.1.0",
+      "resolved": "https://registry.npmjs.org/glob/-/glob-11.1.0.tgz",
+      "integrity": "sha512-vuNwKSaKiqm7g0THUBu2x7ckSs3XJLXE+2ssL7/MfTGPLLcrJQ/4Uq1CjPTtO5cCIiRxqvN6Twy1qOwhL0Xjcw==",
+      "license": "BlueOak-1.0.0",
      "dependencies": {
        "foreground-child": "^3.3.1",
        "jackspeak": "^4.1.1",
-        "minimatch": "^10.0.3",
+        "minimatch": "^10.1.1",
        "minipass": "^7.1.2",
        "package-json-from-dist": "^1.0.0",
        "path-scurry": "^2.0.0"
@@ -4016,10 +4139,10 @@
      }
    },
    "node_modules/glob/node_modules/minimatch": {
-      "version": "10.0.3",
-      "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-10.0.3.tgz",
-      "integrity": "sha512-IPZ167aShDZZUMdRk66cyQAW3qr0WzbHkPdMYa8bzZhlHhO3jALbKdxcaak7W9FfT2rZNpQuUu4Od7ILEpXSaw==",
-      "license": "ISC",
+      "version": "10.1.1",
+      "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-10.1.1.tgz",
+      "integrity": "sha512-enIvLvRAFZYXJzkCYG5RKmPfrFArdLv+R+lbQ53BmIMLIry74bjKzX6iHAm8WYamJkhSSEabrWN5D97XnKObjQ==",
+      "license": "BlueOak-1.0.0",
      "dependencies": {
        "@isaacs/brace-expansion": "^5.0.0"
      },
@@ -4685,9 +4808,9 @@
      }
    },
    "node_modules/jest-config/node_modules/glob": {
-      "version": "10.4.5",
-      "resolved": "https://registry.npmjs.org/glob/-/glob-10.4.5.tgz",
-      "integrity": "sha512-7Bv8RF0k6xjo7d4A/PxYLbUCfb6c+Vpd2/mB2yRDlew7Jb5hEXiCD9ibfO7wpk8i4sevK6DFny9h7EYbM3/sHg==",
+      "version": "10.5.0",
+      "resolved": "https://registry.npmjs.org/glob/-/glob-10.5.0.tgz",
+      "integrity": "sha512-DfXN8DfhJ7NH3Oe7cFmu3NCu1wKbkReJ8TorzSAFbSKrlNaQSKfIzqYqVY8zlbs2NLBbWpRiU52GX2PbaBVNkg==",
      "dev": true,
      "license": "ISC",
      "dependencies": {
@@ -5058,9 +5181,9 @@
      }
    },
    "node_modules/jest-runtime/node_modules/glob": {
-      "version": "10.4.5",
-      "resolved": "https://registry.npmjs.org/glob/-/glob-10.4.5.tgz",
-      "integrity": "sha512-7Bv8RF0k6xjo7d4A/PxYLbUCfb6c+Vpd2/mB2yRDlew7Jb5hEXiCD9ibfO7wpk8i4sevK6DFny9h7EYbM3/sHg==",
+      "version": "10.5.0",
+      "resolved": "https://registry.npmjs.org/glob/-/glob-10.5.0.tgz",
+      "integrity": "sha512-DfXN8DfhJ7NH3Oe7cFmu3NCu1wKbkReJ8TorzSAFbSKrlNaQSKfIzqYqVY8zlbs2NLBbWpRiU52GX2PbaBVNkg==",
      "dev": true,
      "license": "ISC",
      "dependencies": {
@@ -5290,9 +5413,9 @@
      "license": "MIT"
    },
    "node_modules/js-yaml": {
-      "version": "4.1.0",
-      "resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-4.1.0.tgz",
-      "integrity": "sha512-wpxZs9NoxZaJESJGIZTyDEaYpl0FKSA+FB9aJiyemKhMwkxQg63h4T1KJgUGHpTqPDNRcmmYLugrRjJlBtWvRA==",
+      "version": "4.1.1",
+      "resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-4.1.1.tgz",
+      "integrity": "sha512-qQKT4zQxXl8lLwBtHMWwaTcGfFOZviOJet3Oy/xmGk2gZH677CJM9EvtfdSkgWcATZhj/55JZ0rmy3myCT5lsA==",
      "license": "MIT",
      "dependencies": {
        "argparse": "^2.0.1"
@@ -8319,7 +8442,6 @@
      "version": "2.8.1",
      "resolved": "https://registry.npmjs.org/yaml/-/yaml-2.8.1.tgz",
      "integrity": "sha512-lcYcMxX2PO9XMGvAJkJ3OsNMw+/7FKes7/hgerGUYWIoWu5j/+YQqcZr5JnPZWzOsEBgMbSbiSTn/dv/69Mkpw==",
-      "dev": true,
      "license": "ISC",
      "bin": {
        "yaml": "bin.mjs"
@@ -8416,6 +8538,16 @@
        "url": "https://github.com/sponsors/sindresorhus"
      }
    },
+    "node_modules/zod": {
+      "version": "4.1.12",
+      "resolved": "https://registry.npmjs.org/zod/-/zod-4.1.12.tgz",
+      "integrity": "sha512-JInaHOamG8pt5+Ey8kGmdcAcg3OL9reK8ltczgHTAwNhMys/6ThXHityHxVV2p3fkw/c+MAvBHFVYHFZDmjMCQ==",
+      "dev": true,
+      "license": "MIT",
+      "funding": {
+        "url": "https://github.com/sponsors/colinhacks"
+      }
+    },
    "node_modules/zwitch": {
      "version": "2.0.4",
      "resolved": "https://registry.npmjs.org/zwitch/-/zwitch-2.0.4.tgz",
--- a/package.json
+++ b/package.json
@@ -1,7 +1,7 @@
 {
  "$schema": "https://json.schemastore.org/package.json",
  "name": "bmad-method",
-  "version": "6.0.0-alpha.0",
+  "version": "6.0.0-alpha.13",
  "description": "Breakthrough Method of Agile AI-driven Development",
  "keywords": [
    "agile",
@@ -20,9 +20,11 @@
  "author": "Brian (BMad) Madison",
  "main": "tools/cli/bmad-cli.js",
  "bin": {
-    "bmad": "tools/cli/bmad-cli.js"
+    "bmad": "tools/bmad-npx-wrapper.js",
+    "bmad-method": "tools/bmad-npx-wrapper.js"
  },
  "scripts": {
+    "bmad:agent-install": "node tools/cli/bmad-cli.js agent-install",
    "bmad:install": "node tools/cli/bmad-cli.js install",
    "bmad:status": "node tools/cli/bmad-cli.js status",
    "bundle": "node tools/cli/bundlers/bundle-web.js all",
@@ -38,7 +40,12 @@
    "release:minor": "gh workflow run \"Manual Release\" -f version_bump=minor",
    "release:patch": "gh workflow run \"Manual Release\" -f version_bump=patch",
    "release:watch": "gh run watch",
-    "validate:bundles": "node tools/validate-bundles.js"
+    "test": "npm run test:schemas && npm run test:install && npm run validate:bundles && npm run validate:schemas && npm run lint && npm run format:check",
+    "test:coverage": "c8 --reporter=text --reporter=html npm run test:schemas",
+    "test:install": "node test/test-installation-components.js",
+    "test:schemas": "node test/test-agent-schema.js",
+    "validate:bundles": "node tools/validate-bundles.js",
+    "validate:schemas": "node tools/validate-agent-schema.js"
  },
  "lint-staged": {
    "*.{js,cjs,mjs}": [
@@ -54,8 +61,7 @@
    ]
  },
  "dependencies": {
-    "@kayvan/markdown-tree-parser": "^1.5.0",
-    "bmad-method": "^4.30.3",
+    "@kayvan/markdown-tree-parser": "^1.6.1",
    "boxen": "^5.1.2",
    "chalk": "^4.1.2",
    "cli-table3": "^0.6.5",
@@ -70,10 +76,12 @@
    "ora": "^5.4.1",
    "semver": "^7.6.3",
    "wrap-ansi": "^7.0.0",
-    "xml2js": "^0.6.2"
+    "xml2js": "^0.6.2",
+    "yaml": "^2.7.0"
  },
  "devDependencies": {
    "@eslint/js": "^9.33.0",
+    "c8": "^10.1.3",
    "eslint": "^9.33.0",
    "eslint-config-prettier": "^10.1.8",
    "eslint-plugin-n": "^17.21.3",
@@ -85,7 +93,8 @@
    "prettier": "^3.5.3",
    "prettier-plugin-packagejson": "^2.5.19",
    "yaml-eslint-parser": "^1.2.3",
-    "yaml-lint": "^1.7.0"
+    "yaml-lint": "^1.7.0",
+    "zod": "^4.1.12"
  },
  "engines": {
    "node": ">=20.0.0"
--- a/src/core/_module-installer/install-config.yaml
+++ b/src/core/_module-installer/install-config.yaml
@@ -0,0 +1,35 @@
+# 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}"
+
+  # This is the folder where all generated AI Output documents from workflows will default be sa
+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}"
--- a/src/core/_module-installer/install-menu-config.yaml
+++ b/src/core/_module-installer/install-menu-config.yaml
@@ -1,24 +0,0 @@
-# BMAD™ Core Configuration
-
-prompt:
-  - "Welcome and thank you for choosing BMAD™! This is the Core Configuration."
-  - "Core Config is personalized configuration that is git ignored."
-  - "This will impact all selected modules, either additions or upgrades."
-
-# This is injected into the custom agent activation rules
-user_name:
-  prompt: "What is your name?"
-  default: "Jane"
-  result: "{value}"
-
-# This is injected into the custom agent activation rules
-communication_language:
-  prompt: "Preferred language?"
-  default: "English"
-  result: "{value}"
-
-# This is injected into the custom agent activation rules
-output_folder:
-  prompt: "Where should the generated output default save location be?"
-  default: "docs"
-  result: "{project-root}/{value}"
--- a/src/core/_module-installer/installer.js
+++ b/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-menu-config.yaml
+ * @param {Object} options.config - Module configuration from install-config.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
@@ -49,14 +49,6 @@ async function configureForIDE(ide) {
      // Claude Code specific Core configurations
      break;
    }
-    case 'cursor': {
-      // Cursor specific Core configurations
-      break;
-    }
-    case 'windsurf': {
-      // Windsurf specific Core configurations
-      break;
-    }
    // Add more IDEs as needed
    default: {
      // No specific configuration needed
--- a/src/core/agents/bmad-master.agent.yaml
+++ b/src/core/agents/bmad-master.agent.yaml
@@ -0,0 +1,39 @@
+# BMad Master Task Executor Agent
+# Core system agent for task execution and resource management
+
+agent:
+  metadata:
+    id: "{bmad_folder}/core/agents/bmad-master.md"
+    name: "BMad Master"
+    title: "BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator"
+    icon: "🧙"
+
+  persona:
+    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:
+      - "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"
+    - "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"
+      description: "List Available Tasks"
+
+    - trigger: "list-workflows"
+      action: "list all workflows from {project-root}/{bmad_folder}/_cfg/workflow-manifest.csv"
+      description: "List Workflows"
+
+    - trigger: "party-mode"
+      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
+      description: "Group chat with all agents"
+
+  # Empty prompts section (no custom prompts for this agent)
+  prompts: []
--- a/src/core/agents/bmad-master.md
+++ b/src/core/agents/bmad-master.md
@@ -1,27 +0,0 @@
-<!-- Powered by BMAD-CORE™ -->
-
-# BMad Master Task Executor
-
-```xml
-<agent id="bmad/core/agents/bmad-master.md" name="BMad Master" title="BMad Master Task Executor" icon="🧙">
-  <persona>
-    <role>Master Task Executor + BMad Expert</role>
-    <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.</identity>
-    <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.</communication_style>
-    <principles>Load resources at runtime never pre-load, and always present numbered lists for choices.</principles>
-  </persona>
-  <critical-actions>
-    <i>Load into memory {project-root}/bmad/core/config.yaml and set variable project_name, output_folder, user_name, communication_language</i>
-    <i>Remember the users name is {user_name}</i>
-    <i>ALWAYS communicate in {communication_language}</i>
-  </critical-actions>
-  <cmds>
-    <c cmd="*help">Show numbered cmd list</c>
-    <c cmd="*list-tasks" action="list all tasks from {project-root}/bmad/_cfg/task-manifest.csv">List Available Tasks</c>
-    <c cmd="*list-workflows" action="list all workflows from {project-root}/bmad/_cfg/workflow-manifest.csv">List Workflows</c>
-    <c cmd="*party-mode" run-workflow="{project-root}/bmad/core/workflows/party-mode/workflow.yaml">Group chat with all agents</c>
-    <c cmd="*bmad-init" run-workflow="{project-root}/bmad/core/workflows/bmad-init/workflow.yaml">Initialize or Update BMAD system agent manifest, customization, or workflow selection</c>
-    <c cmd="*exit">Exit with confirmation</c>
-  </cmds>
-</agent>
-```
--- a/src/core/agents/bmad-web-orchestrator.agent.xml
+++ b/src/core/agents/bmad-web-orchestrator.agent.xml
@@ -0,0 +1,113 @@
+<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>
--- a/src/core/agents/bmad-web-orchestrator.md
+++ b/src/core/agents/bmad-web-orchestrator.md
@@ -1,71 +0,0 @@
-```xml
-<agent id="bmad/core/agents/bmad-orchestrator.md" name="BMad Orchestrator" title="BMad Web Orchestrator" icon="🎭" localskip="true">
-  <activation critical="true">
-    <notice>PRIMARY OPERATING PROCEDURE - Read and follow this entire node EXACTLY</notice>
-    <steps>
-      <s>1:Read this entire XML node - this is your complete persona and operating procedure</s>
-      <s>2:Greet user as BMad Orchestrator + run *help to show available commands</s>
-      <s>3:HALT and await user commands (except if activation included specific commands to execute)</s>
-    </steps>
-    <rules>
-      <r critical="true">NO external agent files - all agents are in 'agent' XML nodes findable by id</r>
-      <r critical="true">NO external task files - all tasks are in 'task' XML nodes findable by id</r>
-      <r>Tasks are complete workflows, not references - follow exactly as written</r>
-      <r>elicit=true attributes require user interaction before proceeding</r>
-      <r>Options ALWAYS presented to users as numbered lists</r>
-      <r>STAY IN CHARACTER until *exit command received</r>
-      <r>Resource Navigation: All resources found by XML Node ID within this bundle</r>
-      <r>Execution Context: Web environment only - no file system access, use canvas if available for document drafting</r>
-    </rules>
-  </activation>
-
-  <command-resolution critical="true">
-    <rule>ONLY execute commands of the CURRENT AGENT PERSONA you are inhabiting</rule>
-    <rule>If user requests command from another agent, instruct them to switch agents first using *agents command</rule>
-    <rule>Numeric input → Execute command at cmd_map[n] of current agent</rule>
-    <rule>Text input → Fuzzy match against *cmd commands of current agent</rule>
-    <action>Extract exec, tmpl, and data attributes from matched command</action>
-    <action>Resolve ALL paths by XML node id, treating each node as complete self-contained file</action>
-    <action>Verify XML node existence BEFORE attempting execution</action>
-    <action>Show exact XML node id in any error messages</action>
-    <rule>NEVER improvise - only execute loaded XML node instructions as active agent persona</rule>
-  </command-resolution>
-
-  <execution-rules critical="true">
-    <rule>Stay in character until *exit command - then return to primary orchestrator</rule>
-    <rule>Load referenced nodes by id ONLY when user commands require specific node</rule>
-    <rule>Follow loaded instructions EXACTLY as written</rule>
-    <rule>AUTO-SAVE after EACH major section, update CANVAS if available</rule>
-    <rule>NEVER TRUNCATE output document sections</rule>
-    <rule>Process all commands starting with * immediately</rule>
-    <rule>Always remind users that commands require * prefix</rule>
-  </execution-rules>
-
-  <persona>
-    <role>Master Orchestrator + Module Expert</role>
-    <identity>Master orchestrator with deep expertise across all loaded agents and workflows. Expert at assessing user needs and recommending optimal approaches. Skilled in dynamic persona transformation and workflow guidance. Technical brilliance balanced with approachable communication.</identity>
-    <communication_style>Knowledgeable, guiding, approachable. Adapts to current persona/task context. Encouraging and efficient with clear next steps. Always explicit about active state and requirements.</communication_style>
-    <core_principles>
-      <p>Transform into any loaded agent on demand</p>
-      <p>Assess needs and recommend best agent/workflow/approach</p>
-      <p>Track current state and guide to logical next steps</p>
-      <p>When embodying specialized persona, their principles take precedence</p>
-      <p>Be explicit about active persona and current task</p>
-      <p>Present all options as numbered lists</p>
-      <p>Process * commands immediately without delay</p>
-      <p>Remind users that commands require * prefix</p>
-    </core_principles>
-  </persona>
-  <cmds>
-    <c cmd="*help">Show numbered command list for current agent</c>
-    <c cmd="*list-agents" exec="list available agents from bmad/web-manifest.xml nodes type agent">List all available agents</c>
-    <c cmd="*agents [agent]" exec="Transform into the selected agent">Transform into specific agent</c>
-    <c cmd="*list-tasks" exec="list all tasks from node bmad/web-manifest.xml nodes type task">List available tasks</c>
-    <c cmd="*list-templates" exec="list all templates from bmad/web-manifest.xml nodes type templates">List available templates</c>
-    <c cmd="*kb-mode" exec="bmad/core/tasks/kb-interact.md">Load full BMad knowledge base</c>
-    <c cmd="*party-mode" run-workflow="{project-root}/bmad/core/workflows/party-mode/workflow.yaml">Group chat with all agents</c>
-    <c cmd="*yolo">Toggle skip confirmations mode</c>
-    <c cmd="*exit">Return to BMad Orchestrator or exit session</c>
-  </cmds>
-</agent>
-```
--- a/src/core/resources/excalidraw/README.md
+++ b/src/core/resources/excalidraw/README.md
@@ -0,0 +1,160 @@
+# Core Excalidraw Resources
+
+Universal knowledge for creating Excalidraw diagrams. All agents that create Excalidraw files should reference these resources.
+
+## Purpose
+
+Provides the **HOW** (universal knowledge) while agents provide the **WHAT** (domain-specific application).
+
+**Core = "How to create Excalidraw elements"**
+
+- How to group shapes with text labels
+- How to calculate text width
+- How to create arrows with proper bindings
+- How to validate JSON syntax
+- Base structure and primitives
+
+**Agents = "What diagrams to create"**
+
+- Frame Expert (BMM): Technical flowcharts, architecture diagrams, wireframes
+- Presentation Master (CIS): Pitch decks, creative visuals, Rube Goldberg machines
+- Tech Writer (BMM): Documentation diagrams, concept explanations
+
+## Files in This Directory
+
+### excalidraw-helpers.md
+
+**Universal element creation patterns**
+
+- Text width calculation
+- Element grouping rules (shapes + labels)
+- Grid alignment
+- Arrow creation (straight, elbow)
+- Theme application
+- Validation checklist
+- Optimization rules
+
+**Agents reference this to:**
+
+- Create properly grouped shapes
+- Calculate text dimensions
+- Connect elements with arrows
+- Ensure valid structure
+
+### validate-json-instructions.md
+
+**Universal JSON validation process**
+
+- How to validate Excalidraw JSON
+- Common errors and fixes
+- Workflow integration
+- Error recovery
+
+**Agents reference this to:**
+
+- Validate files after creation
+- Fix syntax errors
+- Ensure files can be opened in Excalidraw
+
+### library-loader.md (Future)
+
+**How to load external .excalidrawlib files**
+
+- Programmatic library loading
+- Community library integration
+- Custom library management
+
+**Status:** To be developed when implementing external library support.
+
+## How Agents Use These Resources
+
+### 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'
+```
+
+**Domain-specific additions:**
+
+```yaml
+# workflows/diagrams/_shared/flowchart-templates.yaml
+flowchart:
+  start_node:
+    type: ellipse
+    width: 120
+    height: 60
+  process_box:
+    type: rectangle
+    width: 160
+    height: 80
+  decision_diamond:
+    type: diamond
+    width: 140
+    height: 100
+```
+
+### Example: Presentation Master (Creative Visuals)
+
+```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'
+```
+
+**Domain-specific additions:**
+
+```yaml
+# workflows/_shared/creative-templates.yaml
+rube_goldberg:
+  whimsical_connector:
+    type: arrow
+    strokeStyle: dashed
+    roughness: 2
+  playful_box:
+    type: rectangle
+    roundness: 12
+```
+
+## What Doesn't Belong in Core
+
+**Domain-Specific Elements:**
+
+- Flowchart-specific templates (belongs in Frame Expert)
+- Pitch deck layouts (belongs in Presentation Master)
+- Documentation-specific styles (belongs in Tech Writer)
+
+**Agent Workflows:**
+
+- How to create a flowchart (Frame Expert workflow)
+- How to create a pitch deck (Presentation Master workflow)
+- Step-by-step diagram creation (agent-specific)
+
+**Theming:**
+
+- Currently in agent workflows
+- **Future:** Will be refactored to core as user-configurable themes
+
+## Architecture Principle
+
+**Single Source of Truth:**
+
+- Core holds universal knowledge
+- Agents reference core, don't duplicate
+- Updates to core benefit all agents
+- Agents specialize with domain knowledge
+
+**DRY (Don't Repeat Yourself):**
+
+- Element creation logic: ONCE in core
+- Text width calculation: ONCE in core
+- Validation process: ONCE in core
+- Arrow binding patterns: ONCE in core
+
+## Future Enhancements
+
+1. **External Library Loader** - Load .excalidrawlib files from libraries.excalidraw.com
+2. **Theme Management** - User-configurable color themes saved in core
+3. **Component Library** - Shared reusable components across agents
+4. **Layout Algorithms** - Auto-layout helpers for positioning elements
--- a/src/core/resources/excalidraw/excalidraw-helpers.md
+++ b/src/core/resources/excalidraw/excalidraw-helpers.md
@@ -0,0 +1,127 @@
+# Excalidraw Element Creation Guidelines
+
+## Text Width Calculation
+
+For text elements inside shapes (labels):
+
+```
+text_width = (text.length × fontSize × 0.6) + 20
+```
+
+Round to nearest 10 for grid alignment.
+
+## Element Grouping Rules
+
+**CRITICAL:** When creating shapes with labels:
+
+1. Generate unique IDs:
+   - `shape-id` for the shape
+   - `text-id` for the text
+   - `group-id` for the group
+
+2. Shape element must have:
+   - `groupIds: [group-id]`
+   - `boundElements: [{type: "text", id: text-id}]`
+
+3. Text element must have:
+   - `containerId: shape-id`
+   - `groupIds: [group-id]` (SAME as shape)
+   - `textAlign: "center"`
+   - `verticalAlign: "middle"`
+   - `width: calculated_width`
+
+## Grid Alignment
+
+- Snap all `x`, `y` coordinates to 20px grid
+- Formula: `Math.round(value / 20) * 20`
+- Spacing between elements: 60px minimum
+
+## Arrow Creation
+
+### Straight Arrows
+
+Use for forward flow (left-to-right, top-to-bottom):
+
+```json
+{
+  "type": "arrow",
+  "startBinding": {
+    "elementId": "source-shape-id",
+    "focus": 0,
+    "gap": 10
+  },
+  "endBinding": {
+    "elementId": "target-shape-id",
+    "focus": 0,
+    "gap": 10
+  },
+  "points": [[0, 0], [distance_x, distance_y]]
+}
+```
+
+### Elbow Arrows
+
+Use for upward flow, backward flow, or complex routing:
+
+```json
+{
+  "type": "arrow",
+  "startBinding": {...},
+  "endBinding": {...},
+  "points": [
+    [0, 0],
+    [intermediate_x, 0],
+    [intermediate_x, intermediate_y],
+    [final_x, final_y]
+  ],
+  "elbowed": true
+}
+```
+
+### Update Connected Shapes
+
+After creating arrow, update `boundElements` on both connected shapes:
+
+```json
+{
+  "id": "shape-id",
+  "boundElements": [
+    { "type": "text", "id": "text-id" },
+    { "type": "arrow", "id": "arrow-id" }
+  ]
+}
+```
+
+## Theme Application
+
+Theme colors should be applied consistently:
+
+- **Shapes**: `backgroundColor` from theme primary fill
+- **Borders**: `strokeColor` from theme accent
+- **Text**: `strokeColor` = "#1e1e1e" (dark text)
+- **Arrows**: `strokeColor` from theme accent
+
+## Validation Checklist
+
+Before saving, verify:
+
+- [ ] All shapes with labels have matching `groupIds`
+- [ ] All text elements have `containerId` pointing to parent shape
+- [ ] Text width calculated properly (no cutoff)
+- [ ] Text alignment set (`textAlign` + `verticalAlign`)
+- [ ] All elements snapped to 20px grid
+- [ ] All arrows have `startBinding` and `endBinding`
+- [ ] `boundElements` array updated on connected shapes
+- [ ] Theme colors applied consistently
+- [ ] No metadata or history in final output
+- [ ] All IDs are unique
+
+## Optimization
+
+Remove from final output:
+
+- `appState` object
+- `files` object (unless images used)
+- All elements with `isDeleted: true`
+- Unused library items
+- Version history
--- a/src/core/resources/excalidraw/library-loader.md
+++ b/src/core/resources/excalidraw/library-loader.md
@@ -0,0 +1,50 @@
+# External Library Loader
+
+**Status:** Placeholder for future implementation
+
+## Purpose
+
+Load external .excalidrawlib files from https://libraries.excalidraw.com or custom sources.
+
+## Planned Capabilities
+
+- Load libraries by URL
+- Load libraries from local files
+- Merge multiple libraries
+- Filter library components
+- Cache loaded libraries
+
+## API Reference
+
+Will document how to use:
+
+- `importLibrary(url)` - Load library from URL
+- `loadSceneOrLibraryFromBlob()` - Load from file
+- `mergeLibraryItems()` - Combine libraries
+
+## Usage Example
+
+```yaml
+# Future workflow.yaml structure
+libraries:
+  - url: 'https://libraries.excalidraw.com/libraries/...'
+    filter: ['aws', 'cloud']
+  - path: '{project-root}/_data/custom-library.excalidrawlib'
+```
+
+## Implementation Notes
+
+This will be developed when agents need to leverage the extensive library ecosystem available at https://libraries.excalidraw.com.
+
+Hundreds of pre-built component libraries exist for:
+
+- AWS/Cloud icons
+- UI/UX components
+- Business diagrams
+- Mind map shapes
+- Floor plans
+- And much more...
+
+## User Configuration
+
+Future: Users will be able to configure favorite libraries in their BMAD config for automatic loading.
--- a/src/core/resources/excalidraw/validate-json-instructions.md
+++ b/src/core/resources/excalidraw/validate-json-instructions.md
@@ -0,0 +1,79 @@
+# JSON Validation Instructions
+
+## Purpose
+
+Validate Excalidraw JSON files after saving to catch syntax errors (missing commas, brackets, quotes).
+
+## How to Validate
+
+Use Node.js built-in JSON parsing to validate the file:
+
+```bash
+node -e "JSON.parse(require('fs').readFileSync('FILE_PATH', 'utf8')); console.log('✓ Valid JSON')"
+```
+
+Replace `FILE_PATH` with the actual file path.
+
+## Exit Codes
+
+- Exit code 0 = Valid JSON
+- Exit code 1 = Invalid JSON (syntax error)
+
+## Error Output
+
+If invalid, Node.js will output:
+
+- Error message with description
+- Position in file where error occurred
+- Line and column information (if available)
+
+## Common Errors and Fixes
+
+### Missing Comma
+
+```
+SyntaxError: Expected ',' or '}' after property value
+```
+
+**Fix:** Add comma after the property value
+
+### Missing Bracket/Brace
+
+```
+SyntaxError: Unexpected end of JSON input
+```
+
+**Fix:** Add missing closing bracket `]` or brace `}`
+
+### Extra Comma (Trailing)
+
+```
+SyntaxError: Unexpected token ,
+```
+
+**Fix:** Remove the trailing comma before `]` or `}`
+
+### Missing Quote
+
+```
+SyntaxError: Unexpected token
+```
+
+**Fix:** Add missing quote around string value
+
+## Workflow Integration
+
+After saving an Excalidraw file, run validation:
+
+1. Save the file
+2. Run: `node -e "JSON.parse(require('fs').readFileSync('{{save_location}}', 'utf8')); console.log('✓ Valid JSON')"`
+3. If validation fails:
+   - Read the error message for line/position
+   - Open the file at that location
+   - Fix the syntax error
+   - Save and re-validate
+4. Repeat until validation passes
+
+## Critical Rule
+
+**NEVER delete the file due to validation errors - always fix the syntax error at the reported location.**
--- a/src/core/tasks/adv-elicit-methods.csv
+++ b/src/core/tasks/adv-elicit-methods.csv
@@ -1,39 +0,0 @@
-category,method_name,description,output_pattern
-advanced,Tree of Thoughts,Explore multiple reasoning paths simultaneously then evaluate and select the best - perfect for complex problems with multiple valid approaches where finding the optimal path matters,paths → evaluation → selection
-advanced,Graph of Thoughts,Model reasoning as an interconnected network of ideas to reveal hidden relationships - ideal for systems thinking and discovering emergent patterns in complex multi-factor situations,nodes → connections → patterns
-advanced,Thread of Thought,Maintain coherent reasoning across long contexts by weaving a continuous narrative thread - essential for RAG systems and maintaining consistency in lengthy analyses,context → thread → synthesis
-advanced,Self-Consistency Validation,Generate multiple independent approaches then compare for consistency - crucial for high-stakes decisions where verification and consensus building matter,approaches → comparison → consensus
-advanced,Meta-Prompting Analysis,Step back to analyze the approach structure and methodology itself - valuable for optimizing prompts and improving problem-solving strategies,current → analysis → optimization
-advanced,Reasoning via Planning,Build a reasoning tree guided by world models and goal states - excellent for strategic planning and sequential decision-making tasks,model → planning → strategy
-collaboration,Stakeholder Round Table,Convene multiple personas to contribute diverse perspectives - essential for requirements gathering and finding balanced solutions across competing interests,perspectives → synthesis → alignment
-collaboration,Expert Panel Review,Assemble domain experts for deep specialized analysis - ideal when technical depth and peer review quality are needed,expert views → consensus → recommendations
-competitive,Red Team vs Blue Team,Adversarial attack-defend analysis to find vulnerabilities - critical for security testing and building robust solutions through adversarial thinking,defense → attack → hardening
-core,Expand or Contract for Audience,Dynamically adjust detail level and technical depth for target audience - essential when content needs to match specific reader capabilities,audience → adjustments → refined content
-core,Critique and Refine,Systematic review to identify strengths and weaknesses then improve - standard quality check for drafts needing polish and enhancement,strengths/weaknesses → improvements → refined version
-core,Explain Reasoning,Walk through step-by-step thinking to show how conclusions were reached - crucial for transparency and helping others understand complex logic,steps → logic → conclusion
-core,First Principles Analysis,Strip away assumptions to rebuild from fundamental truths - breakthrough technique for innovation and solving seemingly impossible problems,assumptions → truths → new approach
-core,5 Whys Deep Dive,Repeatedly ask why to drill down to root causes - simple but powerful for understanding failures and fixing problems at their source,why chain → root cause → solution
-core,Socratic Questioning,Use targeted questions to reveal hidden assumptions and guide discovery - excellent for teaching and helping others reach insights themselves,questions → revelations → understanding
-creative,Reverse Engineering,Work backwards from desired outcome to find implementation path - powerful for goal achievement and understanding how to reach specific endpoints,end state → steps backward → path forward
-creative,What If Scenarios,Explore alternative realities to understand possibilities and implications - valuable for contingency planning and creative exploration,scenarios → implications → insights
-creative,SCAMPER Method,Apply seven creativity lenses (Substitute/Combine/Adapt/Modify/Put/Eliminate/Reverse) - systematic ideation for product innovation and improvement,S→C→A→M→P→E→R
-learning,Feynman Technique,Explain complex concepts simply as if teaching a child - the ultimate test of true understanding and excellent for knowledge transfer,complex → simple → gaps → mastery
-learning,Active Recall Testing,Test understanding without references to verify true knowledge - essential for identifying gaps and reinforcing mastery,test → gaps → reinforcement
-narrative,Unreliable Narrator Mode,Question assumptions and biases by adopting skeptical perspective - crucial for detecting hidden agendas and finding balanced truth,perspective → biases → balanced view
-optimization,Speedrun Optimization,Find the fastest most efficient path by eliminating waste - perfect when time pressure demands maximum efficiency,current → bottlenecks → optimized
-optimization,New Game Plus,Revisit challenges with enhanced capabilities from prior experience - excellent for iterative improvement and mastery building,initial → enhanced → improved
-optimization,Roguelike Permadeath,Treat decisions as irreversible to force careful high-stakes analysis - ideal for critical decisions with no second chances,decision → consequences → execution
-philosophical,Occam's Razor Application,Find the simplest sufficient explanation by eliminating unnecessary complexity - essential for debugging and theory selection,options → simplification → selection
-philosophical,Trolley Problem Variations,Explore ethical trade-offs through moral dilemmas - valuable for understanding values and making difficult ethical decisions,dilemma → analysis → decision
-quantum,Observer Effect Consideration,Analyze how the act of measurement changes what's being measured - important for understanding metrics impact and self-aware systems,unmeasured → observation → impact
-retrospective,Hindsight Reflection,Imagine looking back from the future to gain perspective - powerful for project reviews and extracting wisdom from experience,future view → insights → application
-retrospective,Lessons Learned Extraction,Systematically identify key takeaways and actionable improvements - essential for knowledge transfer and continuous improvement,experience → lessons → actions
-risk,Identify Potential Risks,Brainstorm what could go wrong across all categories - fundamental for project planning and deployment preparation,categories → risks → mitigations
-risk,Challenge from Critical Perspective,Play devil's advocate to stress-test ideas and find weaknesses - essential for overcoming groupthink and building robust solutions,assumptions → challenges → strengthening
-risk,Failure Mode Analysis,Systematically explore how each component could fail - critical for reliability engineering and safety-critical systems,components → failures → prevention
-risk,Pre-mortem Analysis,Imagine future failure then work backwards to prevent it - powerful technique for risk mitigation before major launches,failure scenario → causes → prevention
-scientific,Peer Review Simulation,Apply rigorous academic evaluation standards - ensures quality through methodology review and critical assessment,methodology → analysis → recommendations
-scientific,Reproducibility Check,Verify results can be replicated independently - fundamental for reliability and scientific validity,method → replication → validation
-structural,Dependency Mapping,Visualize interconnections to understand requirements and impacts - essential for complex systems and integration planning,components → dependencies → impacts
-structural,Information Architecture Review,Optimize organization and hierarchy for better user experience - crucial for fixing navigation and findability problems,current → pain points → restructure
-structural,Skeleton of Thought,Create structure first then expand branches in parallel - efficient for generating long content quickly with good organization,skeleton → branches → integration
--- a/src/core/tasks/advanced-elicitation-methods.csv
+++ b/src/core/tasks/advanced-elicitation-methods.csv
@@ -0,0 +1,51 @@
+num,category,method_name,description,output_pattern
+1,collaboration,Stakeholder Round Table,Convene multiple personas to contribute diverse perspectives - essential for requirements gathering and finding balanced solutions across competing interests,perspectives → synthesis → alignment
+2,collaboration,Expert Panel Review,Assemble domain experts for deep specialized analysis - ideal when technical depth and peer review quality are needed,expert views → consensus → recommendations
+3,collaboration,Debate Club Showdown,Two personas argue opposing positions while a moderator scores points - great for exploring controversial decisions and finding middle ground,thesis → antithesis → synthesis
+4,collaboration,User Persona Focus Group,Gather your product's user personas to react to proposals and share frustrations - essential for validating features and discovering unmet needs,reactions → concerns → priorities
+5,collaboration,Time Traveler Council,Past-you and future-you advise present-you on decisions - powerful for gaining perspective on long-term consequences vs short-term pressures,past wisdom → present choice → future impact
+6,collaboration,Cross-Functional War Room,Product manager + engineer + designer tackle a problem together - reveals trade-offs between feasibility desirability and viability,constraints → trade-offs → balanced solution
+7,collaboration,Mentor and Apprentice,Senior expert teaches junior while junior asks naive questions - surfaces hidden assumptions through teaching,explanation → questions → deeper understanding
+8,collaboration,Good Cop Bad Cop,Supportive persona and critical persona alternate - finds both strengths to build on and weaknesses to address,encouragement → criticism → balanced view
+9,collaboration,Improv Yes-And,Multiple personas build on each other's ideas without blocking - generates unexpected creative directions through collaborative building,idea → build → build → surprising result
+10,collaboration,Customer Support Theater,Angry customer and support rep roleplay to find pain points - reveals real user frustrations and service gaps,complaint → investigation → resolution → prevention
+11,advanced,Tree of Thoughts,Explore multiple reasoning paths simultaneously then evaluate and select the best - perfect for complex problems with multiple valid approaches,paths → evaluation → selection
+12,advanced,Graph of Thoughts,Model reasoning as an interconnected network of ideas to reveal hidden relationships - ideal for systems thinking and discovering emergent patterns,nodes → connections → patterns
+13,advanced,Thread of Thought,Maintain coherent reasoning across long contexts by weaving a continuous narrative thread - essential for RAG systems and maintaining consistency,context → thread → synthesis
+14,advanced,Self-Consistency Validation,Generate multiple independent approaches then compare for consistency - crucial for high-stakes decisions where verification matters,approaches → comparison → consensus
+15,advanced,Meta-Prompting Analysis,Step back to analyze the approach structure and methodology itself - valuable for optimizing prompts and improving problem-solving,current → analysis → optimization
+16,advanced,Reasoning via Planning,Build a reasoning tree guided by world models and goal states - excellent for strategic planning and sequential decision-making,model → planning → strategy
+17,competitive,Red Team vs Blue Team,Adversarial attack-defend analysis to find vulnerabilities - critical for security testing and building robust solutions,defense → attack → hardening
+18,competitive,Shark Tank Pitch,Entrepreneur pitches to skeptical investors who poke holes - stress-tests business viability and forces clarity on value proposition,pitch → challenges → refinement
+19,competitive,Code Review Gauntlet,Senior devs with different philosophies review the same code - surfaces style debates and finds consensus on best practices,reviews → debates → standards
+20,technical,Architecture Decision Records,Multiple architect personas propose and debate architectural choices with explicit trade-offs - ensures decisions are well-reasoned and documented,options → trade-offs → decision → rationale
+21,technical,Rubber Duck Debugging Evolved,Explain your code to progressively more technical ducks until you find the bug - forces clarity at multiple abstraction levels,simple → detailed → technical → aha
+22,technical,Algorithm Olympics,Multiple approaches compete on the same problem with benchmarks - finds optimal solution through direct comparison,implementations → benchmarks → winner
+23,technical,Security Audit Personas,Hacker + defender + auditor examine system from different threat models - comprehensive security review from multiple angles,vulnerabilities → defenses → compliance
+24,technical,Performance Profiler Panel,Database expert + frontend specialist + DevOps engineer diagnose slowness - finds bottlenecks across the full stack,symptoms → analysis → optimizations
+25,creative,SCAMPER Method,Apply seven creativity lenses (Substitute/Combine/Adapt/Modify/Put/Eliminate/Reverse) - systematic ideation for product innovation,S→C→A→M→P→E→R
+26,creative,Reverse Engineering,Work backwards from desired outcome to find implementation path - powerful for goal achievement and understanding endpoints,end state → steps backward → path forward
+27,creative,What If Scenarios,Explore alternative realities to understand possibilities and implications - valuable for contingency planning and exploration,scenarios → implications → insights
+28,creative,Random Input Stimulus,Inject unrelated concepts to spark unexpected connections - breaks creative blocks through forced lateral thinking,random word → associations → novel ideas
+29,creative,Exquisite Corpse Brainstorm,Each persona adds to the idea seeing only the previous contribution - generates surprising combinations through constrained collaboration,contribution → handoff → contribution → surprise
+30,creative,Genre Mashup,Combine two unrelated domains to find fresh approaches - innovation through unexpected cross-pollination,domain A + domain B → hybrid insights
+31,research,Literature Review Personas,Optimist researcher + skeptic researcher + synthesizer review sources - balanced assessment of evidence quality,sources → critiques → synthesis
+32,research,Thesis Defense Simulation,Student defends hypothesis against committee with different concerns - stress-tests research methodology and conclusions,thesis → challenges → defense → refinements
+33,research,Comparative Analysis Matrix,Multiple analysts evaluate options against weighted criteria - structured decision-making with explicit scoring,options → criteria → scores → recommendation
+34,risk,Pre-mortem Analysis,Imagine future failure then work backwards to prevent it - powerful technique for risk mitigation before major launches,failure scenario → causes → prevention
+35,risk,Failure Mode Analysis,Systematically explore how each component could fail - critical for reliability engineering and safety-critical systems,components → failures → prevention
+36,risk,Challenge from Critical Perspective,Play devil's advocate to stress-test ideas and find weaknesses - essential for overcoming groupthink,assumptions → challenges → strengthening
+37,risk,Identify Potential Risks,Brainstorm what could go wrong across all categories - fundamental for project planning and deployment preparation,categories → risks → mitigations
+38,risk,Chaos Monkey Scenarios,Deliberately break things to test resilience and recovery - ensures systems handle failures gracefully,break → observe → harden
+39,core,First Principles Analysis,Strip away assumptions to rebuild from fundamental truths - breakthrough technique for innovation and solving impossible problems,assumptions → truths → new approach
+40,core,5 Whys Deep Dive,Repeatedly ask why to drill down to root causes - simple but powerful for understanding failures,why chain → root cause → solution
+41,core,Socratic Questioning,Use targeted questions to reveal hidden assumptions and guide discovery - excellent for teaching and self-discovery,questions → revelations → understanding
+42,core,Critique and Refine,Systematic review to identify strengths and weaknesses then improve - standard quality check for drafts,strengths/weaknesses → improvements → refined
+43,core,Explain Reasoning,Walk through step-by-step thinking to show how conclusions were reached - crucial for transparency,steps → logic → conclusion
+44,core,Expand or Contract for Audience,Dynamically adjust detail level and technical depth for target audience - matches content to reader capabilities,audience → adjustments → refined content
+45,learning,Feynman Technique,Explain complex concepts simply as if teaching a child - the ultimate test of true understanding,complex → simple → gaps → mastery
+46,learning,Active Recall Testing,Test understanding without references to verify true knowledge - essential for identifying gaps,test → gaps → reinforcement
+47,philosophical,Occam's Razor Application,Find the simplest sufficient explanation by eliminating unnecessary complexity - essential for debugging,options → simplification → selection
+48,philosophical,Trolley Problem Variations,Explore ethical trade-offs through moral dilemmas - valuable for understanding values and difficult decisions,dilemma → analysis → decision
+49,retrospective,Hindsight Reflection,Imagine looking back from the future to gain perspective - powerful for project reviews,future view → insights → application
+50,retrospective,Lessons Learned Extraction,Systematically identify key takeaways and actionable improvements - essential for continuous improvement,experience → lessons → actions
--- a/src/core/tasks/advanced-elicitation.xml
+++ b/src/core/tasks/advanced-elicitation.xml
@@ -1,20 +1,17 @@
-<!-- BMAD-CORE™ Advanced Elicitation Task v2.0 (LLM-Native) -->
-
-# Advanced Elicitation v2.0 (LLM-Native)
-
-```xml
-<task id="bmad/core/tasks/adv-elicit.md" name="Advanced Elicitation">
+<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">
  <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>
    <i>HALT immediately when halt-conditions are met</i>
-    <i>Each &lt;action&gt; within &lt;step&gt; is a REQUIRED action to complete that step</i>
+    <i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
    <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
  </llm>

  <integration description="When called from workflow">
    <desc>When called during template workflow processing:</desc>
-    <i>1. Receive the current section content that was just generated</i>
+    <i>1. Receive or review the current section content that was just generated or</i>
    <i>2. Apply elicitation methods iteratively to enhance that specific content</i>
    <i>3. Return the enhanced version back when user selects 'x' to proceed and return back</i>
    <i>4. The enhanced content replaces the original section content in the output document</i>
@@ -22,7 +19,7 @@

  <flow>
    <step n="1" title="Method Registry Loading">
-      <action>Load and read {project-root}/core/tasks/adv-elicit-methods.csv</action>
+      <action>Load and read {{methods}} and {{agent-party}}</action>

      <csv-structure>
        <i>category: Method grouping (core, structural, risk, etc.)</i>
@@ -44,11 +41,11 @@
      </smart-selection>
    </step>

-    <step n="2" title="Present Options &amp; Handle Responses">
+    <step n="2" title="Present Options and Handle Responses">

      <format>
-        **Advanced Elicitation Options**
-        Choose a number (1-5), r to shuffle, or x to proceed:
+        **Advanced Elicitation Options (If you launched Party Mode, they will participate randomly)**
+        Choose a number (1-5), [r] to Reshuffle, [a] List All, or [x] to Proceed:

        1. [Method Name]
        2. [Method Name]
@@ -56,6 +53,7 @@
        4. [Method Name]
        5. [Method Name]
        r. Reshuffle the list with 5 new options
+        a. List all methods with descriptions
        x. Proceed / No Further Actions
      </format>

@@ -66,11 +64,14 @@
          <i>Apply the method creatively to the current section content being enhanced</i>
          <i>Display the enhanced version showing what the method revealed or improved</i>
          <i>CRITICAL: Ask the user if they would like to apply the changes to the doc (y/n/other) and HALT to await response.</i>
-          <i>CRITICAL: ONLY if Yes, apply the changes. IF No, discard your memory of the proposed changes. If any other reply, try best to follow the instructions given by the user.</i>
+          <i>CRITICAL: ONLY if Yes, apply the changes. IF No, discard your memory of the proposed changes. If any other reply, try best to
+            follow the instructions given by the user.</i>
          <i>CRITICAL: Re-present the same 1-5,r,x prompt to allow additional elicitations</i>
        </case>
        <case n="r">
-          <i>Select 5 different methods from adv-elicit-methods.csv, present new list with same prompt format</i>
+          <i>Select 5 random methods from advanced-elicitation-methods.csv, present new list with same prompt format</i>
+          <i>When selecting, try to think and pick a diverse set of methods covering different categories and approaches, with 1 and 2 being
+            potentially the most useful for the document or section being discovered</i>
        </case>
        <case n="x">
          <i>Complete elicitation and proceed</i>
@@ -78,6 +79,11 @@
          <i>The enhanced content becomes the final version for that section</i>
          <i>Signal completion back to create-doc.md to continue with next section</i>
        </case>
+        <case n="a">
+          <i>List all methods with their descriptions from the CSV in a compact table</i>
+          <i>Allow user to select any method by name or number from the full list</i>
+          <i>After selection, execute the method as described in the n="1-5" case above</i>
+        </case>
        <case n="direct-feedback">
          <i>Apply changes to current section content and re-present choices</i>
        </case>
@@ -92,11 +98,13 @@
      <i>Output pattern: Use the pattern as a flexible guide (e.g., "paths → evaluation → selection")</i>
      <i>Dynamic adaptation: Adjust complexity based on content needs (simple to sophisticated)</i>
      <i>Creative application: Interpret methods flexibly based on context while maintaining pattern consistency</i>
-      <i>Be concise: Focus on actionable insights</i>
-      <i>Stay relevant: Tie elicitation to specific content being analyzed (the current section from create-doc)</i>
-      <i>Identify personas: For multi-persona methods, clearly identify viewpoints</i>
-      <i>Critical loop behavior: Always re-offer the 1-5,r,x choices after each method execution</i>
-      <i>Continue until user selects 'x' to proceed with enhanced content</i>
+      <i>Focus on actionable insights</i>
+      <i>Stay relevant: Tie elicitation to specific content being analyzed (the current section from the document being created unless user
+        indicates otherwise)</i>
+      <i>Identify personas: For single or multi-persona methods, clearly identify viewpoints, and use party members if available in memory
+        already</i>
+      <i>Critical loop behavior: Always re-offer the 1-5,r,a,x choices after each method execution</i>
+      <i>Continue until user selects 'x' to proceed with enhanced content, confirm or ask the user what should be accepted from the session</i>
      <i>Each method application builds upon previous enhancements</i>
      <i>Content preservation: Track all enhancements made during elicitation</i>
      <i>Iterative enhancement: Each selected method (1-5) should:</i>
@@ -105,5 +113,4 @@
      <i> 3. Return to the prompt for additional elicitations or completion</i>
    </step>
  </flow>
-</task>
-```
+</task>
--- a/src/core/tasks/index-docs.xml
+++ b/src/core/tasks/index-docs.xml
@@ -1,14 +1,10 @@
-<!-- BMAD-CORE™ Index Documentation Task -->
-
-# Index Docs v1.1
-
-```xml
-<task id="bmad/core/tasks/index-docs" name="Index Docs" webskip="true">
+<task id="{bmad_folder}/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>
    <i>DO NOT skip steps or change the sequence</i>
    <i>HALT immediately when halt-conditions are met</i>
-    <i>Each &lt;action&gt; within &lt;step&gt; is a REQUIRED action to complete that step</i>
+    <i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
    <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
  </llm>

@@ -22,7 +18,8 @@
    </step>

    <step n="3" title="Generate Descriptions">
-      <i>Read each file to understand its actual purpose and create brief (3-10 word) descriptions based on the content, not just the filename</i>
+      <i>Read each file to understand its actual purpose and create brief (3-10 word) descriptions based on the content, not just the
+        filename</i>
    </step>

    <step n="4" title="Create/Update Index">
@@ -65,5 +62,4 @@
    <i>Sort alphabetically within groups</i>
    <i>Skip hidden files (starting with .) unless specified</i>
  </validation>
-</task>
-```
+</task>
--- a/src/core/tasks/shard-doc.md
+++ b/src/core/tasks/shard-doc.md
@@ -1,57 +0,0 @@
-<!-- BMAD-CORE™ Document Sharding Task -->
-
-# Shard Doc v1.1
-
-```xml
-<task id="bmad/core/tasks/shard-doc.md" name="Shard Doc">
-  <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>
-    <i>HALT immediately when halt-conditions are met</i>
-    <i>Each &lt;action&gt; within &lt;step&gt; is a REQUIRED action to complete that step</i>
-    <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
-  </llm>
-
-  <flow>
-    <step n="1" title="Check for Tool">
-      <i>First check if md-tree command is available</i>
-    </step>
-
-    <step n="2" title="Install if Needed">
-      <i>If not available, ask user permission to install: npm install -g @kayvan/markdown-tree-parser</i>
-    </step>
-
-    <step n="3" title="Shard Document">
-      <i>Use the explode command to split the document</i>
-    </step>
-  </flow>
-
-  <usage>
-    <commands>
-      # Install the tool (if needed)
-      npm install -g @kayvan/markdown-tree-parser
-
-      # Shard a document
-      md-tree explode [source-document] [destination-folder]
-
-      # Examples
-      md-tree explode docs/prd.md docs/prd
-      md-tree explode docs/architecture.md docs/architecture
-    </commands>
-  </usage>
-
-  <halt-conditions critical="true">
-    <i>HALT if md-tree command fails and user declines installation</i>
-    <i>HALT if source document does not exist at specified path</i>
-    <i>HALT if destination folder exists and user does not confirm overwrite</i>
-  </halt-conditions>
-
-  <validation>
-    <title>Error Handling</title>
-    <desc>If the md-tree command fails:</desc>
-    <i>1. Check if the tool is installed globally</i>
-    <i>2. Ask user permission to install it</i>
-    <i>3. Retry the operation after installation</i>
-  </validation>
-</task>
-```
--- a/src/core/tasks/validate-workflow.xml
+++ b/src/core/tasks/validate-workflow.xml
@@ -1,7 +1,4 @@
-# Validate Workflow
-
-```xml
-<task id="bmad/core/tasks/validate-workflow.md" name="Validate Workflow Output">
+<task id="{bmad_folder}/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>
@@ -13,7 +10,8 @@
  <flow>
    <step n="1" title="Setup">
      <action>If checklist not provided, load checklist.md from workflow location</action>
-      <action>If document not provided, ask user: "Which document should I validate?"</action>
+      <action>Try to fuzzy match for files similar to the input document name or if user did not provide the document. If document not
+        provided or unsure, ask user: "Which document should I validate?"</action>
      <action>Load both the checklist and document</action>
    </step>

@@ -88,5 +86,4 @@
    <rule>Save report to document's folder automatically</rule>
    <rule>HALT after presenting summary - wait for user</rule>
  </critical-rules>
-</task>
-```
+</task>
--- a/src/core/tasks/workflow.md
+++ b/src/core/tasks/workflow.md
@@ -1,141 +0,0 @@
-<!-- BMAD Method v6 Workflow Execution Task (Simplified) -->
-
-# Workflow
-
-```xml
-<task id="bmad/core/tasks/workflow.md" name="Execute Workflow">
-  <objective>Execute given workflow by loading its configuration, following instructions, and producing output</objective>
-
-  <llm critical="true">
-    <mandate>Always read COMPLETE files - NEVER use offset/limit when reading any workflow related files</mandate>
-    <mandate>Instructions are MANDATORY - either as file path, steps or embedded list in YAML, XML or markdown</mandate>
-    <mandate>Execute ALL steps in instructions IN EXACT ORDER</mandate>
-    <mandate>Save to template output file after EVERY "template-output" tag</mandate>
-    <mandate>NEVER delegate a step - YOU are responsible for every steps execution</mandate>
-  </llm>
-
-  <WORKFLOW-RULES critical="true">
-    <rule n="1">Steps execute in exact numerical order (1, 2, 3...)</rule>
-    <rule n="2">Optional steps: Ask user unless #yolo mode active</rule>
-    <rule n="3">Template-output tags: Save content → Show user → Get approval before continuing</rule>
-    <rule n="4">Elicit tags: Execute immediately unless #yolo mode (which skips ALL elicitation)</rule>
-    <rule n="5">User must approve each major section before continuing UNLESS #yolo mode active</rule>
-  </WORKFLOW-RULES>
-
-  <flow>
-    <step n="1" title="Load and Initialize Workflow">
-      <substep n="1a" title="Load Configuration and Resolve Variables">
-        <action>Read workflow.yaml from provided path</action>
-        <mandate>Load config_source (REQUIRED for all modules)</mandate>
-        <phase n="1">Load external config from config_source path</phase>
-        <phase n="2">Resolve all {config_source}: references with values from config</phase>
-        <phase n="3">Resolve system variables (date:system-generated) and paths ({project-root}, {installed_path})</phase>
-        <phase n="4">Ask user for input of any variables that are still unknown</phase>
-      </substep>
-
-      <substep n="1b" title="Load Required Components">
-        <mandate>Instructions: Read COMPLETE file from path OR embedded list (REQUIRED)</mandate>
-        <check>If template path → Read COMPLETE template file</check>
-        <check>If validation path → Note path for later loading when needed</check>
-        <check>If template: false → Mark as action-workflow (else template-workflow)</check>
-        <note>Data files (csv, json) → Store paths only, load on-demand when instructions reference them</note>
-      </substep>
-
-      <substep n="1c" title="Initialize Output" if="template-workflow">
-        <action>Resolve default_output_file path with all variables and {{date}}</action>
-        <action>Create output directory if doesn't exist</action>
-        <action>If template-workflow → Write template to output file with placeholders</action>
-        <action>If action-workflow → Skip file creation</action>
-      </substep>
-    </step>
-
-    <step n="2" title="Process Each Instruction Step">
-      <iterate>For each step in instructions:</iterate>
-
-      <substep n="2a" title="Handle Step Attributes">
-        <check>If optional="true" and NOT #yolo → Ask user to include</check>
-        <check>If if="condition" → Evaluate condition</check>
-        <check>If for-each="item" → Repeat step for each item</check>
-        <check>If repeat="n" → Repeat step n times</check>
-      </substep>
-
-      <substep n="2b" title="Execute Step Content">
-        <action>Process step instructions (markdown or XML tags)</action>
-        <action>Replace {{variables}} with values (ask user if unknown)</action>
-        <execute-tags>
-          <tag><action> → Perform the action</tag>
-          <tag><check> → Evaluate condition</tag>
-          <tag><ask> → Prompt user and WAIT for response</tag>
-          <tag><invoke-workflow> → Execute another workflow with given inputs</tag>
-          <tag><invoke-task> → Execute specified task</tag>
-          <tag><goto step="x"> → Jump to specified step</tag>
-        </execute-tags>
-      </substep>
-
-      <substep n="2c" title="Handle Special Output Tags">
-        <if tag="template-output">
-          <mandate>Generate content for this section</mandate>
-          <mandate>Save to file (Write first time, Edit subsequent)</mandate>
-          <action>Show checkpoint separator: ━━━━━━━━━━━━━━━━━━━━━━━</action>
-          <action>Display generated content</action>
-          <ask>Continue [c] or Edit [e]? WAIT for response</ask>
-        </if>
-
-        <if tag="elicit-required">
-          <mandate critical="true">YOU MUST READ the file at {project-root}/bmad/core/tasks/adv-elicit.md using Read tool BEFORE presenting any elicitation menu</mandate>
-          <action>Load and run task {project-root}/bmad/core/tasks/adv-elicit.md with current context</action>
-          <action>Show elicitation menu 5 relevant options (list 1-5 options, Continue [c] or Reshuffle [r])</action>
-          <mandate>HALT and WAIT for user selection</mandate>
-        </if>
-      </substep>
-
-      <substep n="2d" title="Step Completion">
-        <check>If no special tags and NOT #yolo:</check>
-        <ask>Continue to next step? (y/n/edit)</ask>
-      </substep>
-    </step>
-
-    <step n="3" title="Completion">
-      <check>If checklist exists → Run validation</check>
-      <check>If template: false → Confirm actions completed</check>
-      <check>Else → Confirm document saved to output path</check>
-      <action>Report workflow completion</action>
-    </step>
-  </flow>
-
-  <execution-modes>
-    <mode name="normal">Full user interaction at all decision points</mode>
-    <mode name="#yolo">Skip optional sections, skip all elicitation, minimize prompts</mode>
-  </execution-modes>
-
-  <supported-tags desc="Instructions can use these tags">
-    <structural>
-      <tag>step n="X" goal="..." - Define step with number and goal</tag>
-      <tag>optional="true" - Step can be skipped</tag>
-      <tag>if="condition" - Conditional execution</tag>
-      <tag>for-each="collection" - Iterate over items</tag>
-      <tag>repeat="n" - Repeat n times</tag>
-    </structural>
-    <execution>
-      <tag>action - Required action to perform</tag>
-      <tag>check - Condition to evaluate</tag>
-      <tag>ask - Get user input (wait for response)</tag>
-      <tag>goto - Jump to another step</tag>
-      <tag>invoke-workflow - Call another workflow</tag>
-      <tag>invoke-task - Call a task</tag>
-    </execution>
-    <output>
-      <tag>template-output - Save content checkpoint</tag>
-      <tag>elicit-required - Trigger enhancement</tag>
-      <tag>critical - Cannot be skipped</tag>
-      <tag>example - Show example output</tag>
-    </output>
-  </supported-tags>
-
-  <llm final="true">
-    <mandate>This is the complete workflow execution engine</mandate>
-    <mandate>You MUST Follow instructions exactly as written and maintain conversation context between steps</mandate>
-    <mandate>If confused, re-read this task, the workflow yaml, and any yaml indicated files</mandate>
-  </llm>
-</task>
-```
--- a/src/core/tasks/workflow.xml
+++ b/src/core/tasks/workflow.xml
@@ -0,0 +1,235 @@
+<task id="{bmad_folder}/core/tasks/workflow.xml" name="Execute Workflow">
+  <objective>Execute given workflow by loading its configuration, following instructions, and producing output</objective>
+
+  <llm critical="true">
+    <mandate>Always read COMPLETE files - NEVER use offset/limit when reading any workflow related files</mandate>
+    <mandate>Instructions are MANDATORY - either as file path, steps or embedded list in YAML, XML or markdown</mandate>
+    <mandate>Execute ALL steps in instructions IN EXACT ORDER</mandate>
+    <mandate>Save to template output file after EVERY "template-output" tag</mandate>
+    <mandate>NEVER skip a step - YOU are responsible for every steps execution without fail or excuse</mandate>
+  </llm>
+
+  <WORKFLOW-RULES critical="true">
+    <rule n="1">Steps execute in exact numerical order (1, 2, 3...)</rule>
+    <rule n="2">Optional steps: Ask user unless #yolo mode active</rule>
+    <rule n="3">Template-output tags: Save content, discuss with the user the section completed, and NEVER proceed until the users indicates
+      to proceed (unless YOLO mode has been activated)</rule>
+  </WORKFLOW-RULES>
+
+  <flow>
+    <step n="1" title="Load and Initialize Workflow">
+      <substep n="1a" title="Load Configuration and Resolve Variables">
+        <action>Read workflow.yaml from provided path</action>
+        <mandate>Load config_source (REQUIRED for all modules)</mandate>
+        <phase n="1">Load external config from config_source path</phase>
+        <phase n="2">Resolve all {config_source}: references with values from config</phase>
+        <phase n="3">Resolve system variables (date:system-generated) and paths ({project-root}, {installed_path})</phase>
+        <phase n="4">Ask user for input of any variables that are still unknown</phase>
+      </substep>
+
+      <substep n="1b" title="Load Required Components">
+        <mandate>Instructions: Read COMPLETE file from path OR embedded list (REQUIRED)</mandate>
+        <check>If template path → Read COMPLETE template file</check>
+        <check>If validation path → Note path for later loading when needed</check>
+        <check>If template: false → Mark as action-workflow (else template-workflow)</check>
+        <note>Data files (csv, json) → Store paths only, load on-demand when instructions reference them</note>
+      </substep>
+
+      <substep n="1c" title="Initialize Output" if="template-workflow">
+        <action>Resolve default_output_file path with all variables and {{date}}</action>
+        <action>Create output directory if doesn't exist</action>
+        <action>If template-workflow → Write template to output file with placeholders</action>
+        <action>If action-workflow → Skip file creation</action>
+      </substep>
+    </step>
+
+    <step n="2" title="Process Each Instruction Step in Order">
+      <iterate>For each step in instructions:</iterate>
+
+      <substep n="2a" title="Handle Step Attributes">
+        <check>If optional="true" and NOT #yolo → Ask user to include</check>
+        <check>If if="condition" → Evaluate condition</check>
+        <check>If for-each="item" → Repeat step for each item</check>
+        <check>If repeat="n" → Repeat step n times</check>
+      </substep>
+
+      <substep n="2b" title="Execute Step Content">
+        <action>Process step instructions (markdown or XML tags)</action>
+        <action>Replace {{variables}} with values (ask user if unknown)</action>
+        <execute-tags>
+          <tag>action xml tag → Perform the action</tag>
+          <tag>check if="condition" xml tag → Conditional block wrapping actions (requires closing &lt;/check&gt;)</tag>
+          <tag>ask xml tag → Prompt user and WAIT for response</tag>
+          <tag>invoke-workflow xml tag → Execute another workflow with given inputs and the workflow.xml runner</tag>
+          <tag>invoke-task xml tag → Execute specified task</tag>
+          <tag>invoke-protocol name="protocol_name" xml tag → Execute reusable protocol from protocols section</tag>
+          <tag>goto step="x" → Jump to specified step</tag>
+        </execute-tags>
+      </substep>
+
+      <substep n="2c" title="Handle template-output Tags">
+        <if tag="template-output">
+          <mandate>Generate content for this section</mandate>
+          <mandate>Save to file (Write first time, Edit subsequent)</mandate>
+          <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>
+            </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>
+            </if>
+            <if
+              response="y">
+              <action>Enter #yolo mode for the rest of the workflow</action>
+            </if>
+          </ask>
+        </if>
+      </substep>
+
+      <substep n="2d" title="Step Completion">
+        <check>If no special tags and NOT #yolo:</check>
+        <ask>Continue to next step? (y/n/edit)</ask>
+      </substep>
+    </step>
+
+    <step n="3" title="Completion">
+      <check>Confirm document saved to output path</check>
+      <action>Report workflow completion</action>
+    </step>
+  </flow>
+
+  <execution-modes>
+    <mode name="normal">Full user interaction and confirmation of EVERY step at EVERY template output - NO EXCEPTIONS except yolo MODE</mode>
+    <mode name="yolo">Skip all confirmations and elicitation, minimize prompts and try to produce all of the workflow automatically by
+      simulating the remaining discussions with an simulated expert user</mode>
+  </execution-modes>
+
+  <supported-tags desc="Instructions can use these tags">
+    <structural>
+      <tag>step n="X" goal="..." - Define step with number and goal</tag>
+      <tag>optional="true" - Step can be skipped</tag>
+      <tag>if="condition" - Conditional execution</tag>
+      <tag>for-each="collection" - Iterate over items</tag>
+      <tag>repeat="n" - Repeat n times</tag>
+    </structural>
+    <execution>
+      <tag>action - Required action to perform</tag>
+      <tag>action if="condition" - Single conditional action (inline, no closing tag needed)</tag>
+      <tag>check if="condition"&gt;...&lt;/check&gt; - Conditional block wrapping multiple items (closing tag required)</tag>
+      <tag>ask - Get user input (ALWAYS wait for response before continuing)</tag>
+      <tag>goto - Jump to another step</tag>
+      <tag>invoke-workflow - Call another workflow</tag>
+      <tag>invoke-task - Call a task</tag>
+      <tag>invoke-protocol - Execute a reusable protocol (e.g., discover_inputs)</tag>
+    </execution>
+    <output>
+      <tag>template-output - Save content checkpoint</tag>
+      <tag>critical - Cannot be skipped</tag>
+      <tag>example - Show example output</tag>
+    </output>
+  </supported-tags>
+
+  <protocols desc="Reusable workflow protocols that can be invoked via invoke-protocol tag">
+    <protocol name="discover_inputs" desc="Smart file discovery and loading based on input_file_patterns">
+      <objective>Intelligently load project files (whole or sharded) based on workflow's input_file_patterns configuration</objective>
+
+      <critical>Only execute if workflow.yaml contains input_file_patterns section</critical>
+
+      <flow>
+        <step n="1" title="Parse Input File Patterns">
+          <action>Read input_file_patterns from loaded workflow.yaml</action>
+          <action>For each pattern group (prd, architecture, epics, etc.), note the load_strategy if present</action>
+        </step>
+
+        <step n="2" title="Load Files Using Smart Strategies">
+          <iterate>For each pattern in input_file_patterns:</iterate>
+
+          <substep n="2a" title="Try Sharded Documents First">
+            <check if="sharded pattern exists">
+              <action>Determine load_strategy from pattern config (defaults to FULL_LOAD if not specified)</action>
+
+              <strategy name="FULL_LOAD">
+                <desc>Load ALL files in sharded directory - used for PRD, Architecture, UX, brownfield docs</desc>
+                <action>Use glob pattern to find ALL .md files (e.g., "{output_folder}/*architecture*/*.md")</action>
+                <action>Load EVERY matching file completely</action>
+                <action>Concatenate content in logical order (index.md first if exists, then alphabetical)</action>
+                <action>Store in variable: {pattern_name_content}</action>
+              </strategy>
+
+              <strategy name="SELECTIVE_LOAD">
+                <desc>Load specific shard using template variable - example: used for epics with {{epic_num}}</desc>
+                <action>Check for template variables in sharded_single pattern (e.g., {{epic_num}})</action>
+                <action>If variable undefined, ask user for value OR infer from context</action>
+                <action>Resolve template to specific file path</action>
+                <action>Load that specific file</action>
+                <action>Store in variable: {pattern_name_content}</action>
+              </strategy>
+
+              <strategy name="INDEX_GUIDED">
+                <desc>Load index.md, analyze structure and description of each doc in the index, then intelligently load relevant docs</desc>
+                <mandate>DO NOT BE LAZY - use best judgment to load documents that might have relevant information, even if only a 5% chance</mandate>
+                <action>Load index.md from sharded directory</action>
+                <action>Parse table of contents, links, section headers</action>
+                <action>Analyze workflow's purpose and objective</action>
+                <action>Identify which linked/referenced documents are likely relevant</action>
+                <example>If workflow is about authentication and index shows "Auth Overview", "Payment Setup", "Deployment" → Load auth
+                  docs, consider deployment docs, skip payment</example>
+                <action>Load all identified relevant documents</action>
+                <action>Store combined content in variable: {pattern_name_content}</action>
+                <note>When in doubt, LOAD IT - context is valuable, being thorough is better than missing critical info</note>
+              </strategy>
+              <action>Mark pattern as RESOLVED, skip to next pattern</action>
+            </check>
+          </substep>
+
+          <substep n="2b" title="Try Whole Document if No Sharded Found">
+            <check if="no sharded matches found OR no sharded pattern exists">
+              <action>Attempt glob match on 'whole' pattern (e.g., "{output_folder}/*prd*.md")</action>
+              <check if="matches found">
+                <action>Load ALL matching files completely (no offset/limit)</action>
+                <action>Store content in variable: {pattern_name_content} (e.g., {prd_content})</action>
+                <action>Mark pattern as RESOLVED, skip to next pattern</action>
+              </check>
+            </check>
+          </substep>
+
+          <substep n="2c" title="Handle Not Found">
+            <check if="no matches for sharded OR whole">
+              <action>Set {pattern_name_content} to empty string</action>
+              <action>Note in session: "No {pattern_name} files found" (not an error, just unavailable, offer use change to provide)</action>
+            </check>
+          </substep>
+        </step>
+
+        <step n="3" title="Report Discovery Results">
+          <action>List all loaded content variables with file counts</action>
+          <example>
+            ✓ Loaded {prd_content} from 5 sharded files: prd/index.md, prd/requirements.md, ...
+            ✓ Loaded {architecture_content} from 1 file: Architecture.md
+            ✓ Loaded {epics_content} from selective load: epics/epic-3.md
+            ○ No ux_design files found
+          </example>
+          <note>This gives workflow transparency into what context is available</note>
+        </step>
+      </flow>
+
+    </protocol>
+  </protocols>
+
+  <llm final="true">
+    <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
+      • 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
+      collaborative helping the user flesh out their ideas. Do not rush or optimize and skip any section.
+    </critical-rules>
+  </llm>
+</task> 
--- a/src/core/tools/shard-doc.xml
+++ b/src/core/tools/shard-doc.xml
@@ -0,0 +1,109 @@
+<tool id="{bmad_folder}/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>
+
+  <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>
+    <i>HALT immediately when halt-conditions are met</i>
+    <i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
+    <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
+  </llm>
+
+  <critical-context>
+    <i>Uses `npx @kayvan/markdown-tree-parser` to automatically shard documents by level 2 headings and generate an index</i>
+  </critical-context>
+
+  <flow>
+    <step n="1" title="Get Source Document">
+      <action>Ask user for the source document path if not provided already</action>
+      <action>Verify file exists and is accessible</action>
+      <action>Verify file is markdown format (.md extension)</action>
+      <action if="file not found or not markdown">HALT with error message</action>
+    </step>
+
+    <step n="2" title="Get Destination Folder">
+      <action>Determine default destination: same location as source file, folder named after source file without .md extension</action>
+      <action>Example: /path/to/architecture.md → /path/to/architecture/</action>
+      <action>Ask user for the destination folder path ([y] to confirm use of default: [suggested-path], else enter a new path)</action>
+      <action if="user accepts default">Use the suggested destination path</action>
+      <action if="user provides custom path">Use the custom destination path</action>
+      <action>Verify destination folder exists or can be created</action>
+      <action>Check write permissions for destination</action>
+      <action if="permission denied">HALT with error message</action>
+    </step>
+
+    <step n="3" title="Execute Sharding">
+      <action>Inform user that sharding is beginning</action>
+      <action>Execute command: `npx @kayvan/markdown-tree-parser explode [source-document] [destination-folder]`</action>
+      <action>Capture command output and any errors</action>
+      <action if="command fails">HALT and display error to user</action>
+    </step>
+
+    <step n="4" title="Verify Output">
+      <action>Check that destination folder contains sharded files</action>
+      <action>Verify index.md was created in destination folder</action>
+      <action>Count the number of files created</action>
+      <action if="no files created">HALT with error message</action>
+    </step>
+
+    <step n="5" title="Report Completion">
+      <action>Display completion report to user including:</action>
+      <i>- Source document path and name</i>
+      <i>- Destination folder path</i>
+      <i>- Number of section files created</i>
+      <i>- Confirmation that index.md was created</i>
+      <i>- Any tool output or warnings</i>
+      <action>Inform user that sharding completed successfully</action>
+    </step>
+
+    <step n="6" title="Handle Original Document">
+      <critical>Keeping both the original and sharded versions defeats the purpose of sharding and can cause confusion</critical>
+      <action>Present user with options for the original document:</action>
+
+      <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)
+
+Your choice (d/m/k):</ask>
+
+      <check if="user selects 'd' (delete)">
+        <action>Delete the original source document file</action>
+        <action>Confirm deletion to user: "✓ Original document deleted: [source-document-path]"</action>
+        <note>The document can be reconstructed from shards by concatenating all section files in order</note>
+      </check>
+
+      <check if="user selects 'm' (move)">
+        <action>Determine default archive location: same directory as source, in an "archive" subfolder</action>
+        <action>Example: /path/to/architecture.md → /path/to/archive/architecture.md</action>
+        <ask>Archive location ([y] to use default: [default-archive-path], or provide custom path):</ask>
+        <action if="user accepts default">Use default archive path</action>
+        <action if="user provides custom path">Use custom archive path</action>
+        <action>Create archive directory if it doesn't exist</action>
+        <action>Move original document to archive location</action>
+        <action>Confirm move to user: "✓ Original document moved to: [archive-path]"</action>
+      </check>
+
+      <check if="user selects 'k' (keep)">
+        <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
+
+Consider deleting or archiving the original document.</output>
+        <action>Confirm user choice: "Original document kept at: [source-document-path]"</action>
+      </check>
+    </step>
+  </flow>
+
+  <halt-conditions critical="true">
+    <i>HALT if npx command fails or produces no output files</i>
+  </halt-conditions>
+</tool>
--- a/src/core/workflows/bmad-init/instructions.md
+++ b/src/core/workflows/bmad-init/instructions.md
@@ -1,79 +0,0 @@
-# BMAD Init - System Initialization Instructions
-
-<workflow>
-
-<step n="1" goal="Welcome and Status Check">
-  <action>Display welcome banner with BMAD branding</action>
-  <action>Check for BMAD installation at {project-root}/bmad</action>
-  <check>If installation found:</check>
-    <action>Display current version from {project-root}/bmad/_cfg/manifest.yaml</action>
-    <action>Show installation date and status</action>
-  <check>If not found:</check>
-    <action>Display warning that BMAD is not installed</action>
-    <action>Suggest running the installer first</action>
-    <action>Exit workflow</action>
-  <action>Display formatted status summary:
-    ╔════════════════════════════════════════╗
-    ║         BMAD INITIALIZATION            ║
-    ╚════════════════════════════════════════╝
-
-    Status: [Installed/Not Found]
-    Location: {project-root}/bmad
-    Version: [from manifest]
-    Installed: [date from manifest]
-
-  </action>
-</step>
-
-<step n="2" goal="Present Initialization Options">
-  <action>Display available initialization and maintenance tasks</action>
-  <ask>Select an initialization task:
-
-    1. Customize Installed Agents and Agent Party (Coming Soon)
-       - Assign new names and personas to agents
-       - Create runtime agent variants
-       - NOTE: This can all be done manually, but doing it through here will be easier and also update the party-mode manifest
-
-    2. Verify Installation (Coming Soon)
-       - Check all files are properly installed
-       - Validate configurations
-
-    3. Exit
-
-    Please select an option (1-3).
-
-  </ask>
-</step>
-
-<step n="3" goal="Process User Selection">
-  <check>If user selected "1":</check>
-    <action>Display message: ⚠️ Installed Agent Auto Customization is coming soon.</action>
-    <<action>Return to step 2</action>
-
-<check>If user selected "2":</check>
-<action>Display message: ⚠️ Installation verification is coming soon.</action>
-<action>Return to step 2</action>
-
-<check>If user selected "3":</check>
-<action>Display message: Exiting BMAD Init. Thank you!</action>
-<goto step="5">Exit workflow</goto>
-</step>
-
-<step n="4" goal="Post-Task Options">
-  <action>Display completion status of the executed task</action>
-  <ask>Task completed successfully!
-
-Would you like to perform another initialization task? (y/n):</ask>
-<check>If user responds "y":</check>
-<goto step="2">Return to menu</goto>
-<check>If user responds "n":</check>
-<goto step="5">Exit workflow</goto>
-</step>
-
-<step n="5" goal="Exit Workflow">
-  <action>Display farewell message</action>
-  <action>Suggest user start a new context or clear context if needed</action>
-  <action>Exit workflow</action>
-</step>
-
-</workflow>
--- a/src/core/workflows/bmad-init/workflow.yaml
+++ b/src/core/workflows/bmad-init/workflow.yaml
@@ -1,24 +0,0 @@
-# BMAD Init - System Initialization Workflow
-name: "bmad-init"
-description: "BMAD system initialization and maintenance workflow for agent manifest generation and system configuration"
-author: "BMad"
-
-# Critical variables
-config_source: "{project-root}/bmad/_cfg/manifest.yaml"
-date: system-generated
-
-# This is an action workflow - no template output
-template: false
-instructions: "{project-root}/src/core/workflows/bmad-init/instructions.md"
-
-# Sub-components
-party_update_instructions: "{project-root}/src/core/workflows/bmad-init/party-update/instructions.md"
-
-# No specific output file - this workflow performs various system actions
-default_output_file: null
-
-# Required tools for execution
-required_tools:
-  - file_operations
-  - llm_analysis
-  - xml_generation
--- a/src/core/workflows/brainstorming/brain-methods.csv
+++ b/src/core/workflows/brainstorming/brain-methods.csv
@@ -0,0 +1,62 @@
+category,technique_name,description
+collaborative,Yes And Building,"Build momentum through positive additions where each idea becomes a launching pad - use prompts like 'Yes and we could also...' or 'Building on that idea...' to create energetic collaborative flow that builds upon previous contributions"
+collaborative,Brain Writing Round Robin,"Silent idea generation followed by building on others' written concepts - gives quieter voices equal contribution while maintaining documentation through the sequence of writing silently, passing ideas, and building on received concepts"
+collaborative,Random Stimulation,"Use random words/images as creative catalysts to force unexpected connections - breaks through mental blocks with serendipitous inspiration by asking how random elements relate, what connections exist, and forcing relationships"
+collaborative,Role Playing,"Generate solutions from multiple stakeholder perspectives to build empathy while ensuring comprehensive consideration - embody different roles by asking what they want, how they'd approach problems, and what matters most to them"
+collaborative,Ideation Relay Race,"Rapid-fire idea building under time pressure creates urgency and breakthroughs - structure with 30-second additions, quick building on ideas, and fast passing to maintain creative momentum and prevent overthinking"
+creative,What If Scenarios,"Explore radical possibilities by questioning all constraints and assumptions - perfect for breaking through stuck thinking using prompts like 'What if we had unlimited resources?' 'What if the opposite were true?' or 'What if this problem didn't exist?'"
+creative,Analogical Thinking,"Find creative solutions by drawing parallels to other domains - transfer successful patterns by asking 'This is like what?' 'How is this similar to...' and 'What other examples come to mind?' to connect to existing solutions"
+creative,Reversal Inversion,"Deliberately flip problems upside down to reveal hidden assumptions and fresh angles - great when conventional approaches fail by asking 'What if we did the opposite?' 'How could we make this worse?' and 'What's the reverse approach?'"
+creative,First Principles Thinking,"Strip away assumptions to rebuild from fundamental truths - essential for breakthrough innovation by asking 'What do we know for certain?' 'What are the fundamental truths?' and 'If we started from scratch?'"
+creative,Forced Relationships,"Connect unrelated concepts to spark innovative bridges through creative collision - take two unrelated things, find connections between them, identify bridges, and explore how they could work together to generate unexpected solutions"
+creative,Time Shifting,"Explore solutions across different time periods to reveal constraints and opportunities by asking 'How would this work in the past?' 'What about 100 years from now?' 'Different era constraints?' and 'What time-based solutions apply?'"
+creative,Metaphor Mapping,"Use extended metaphors as thinking tools to explore problems from new angles - transforms abstract challenges into tangible narratives by asking 'This problem is like a metaphor,' extending the metaphor, and mapping elements to discover insights"
+creative,Cross-Pollination,"Transfer solutions from completely different industries or domains to spark breakthrough innovations by asking how industry X would solve this, what patterns work in field Y, and how to adapt solutions from domain Z"
+creative,Concept Blending,"Merge two or more existing concepts to create entirely new categories - goes beyond simple combination to genuine innovation by asking what emerges when concepts merge, what new category is created, and how the blend transcends original ideas"
+creative,Reverse Brainstorming,"Generate problems instead of solutions to identify hidden opportunities and unexpected pathways by asking 'What could go wrong?' 'How could we make this fail?' and 'What problems could we create?' to reveal solution insights"
+creative,Sensory Exploration,"Engage all five senses to discover multi-dimensional solution spaces beyond purely analytical thinking by asking what ideas feel, smell, taste, or sound like, and how different senses engage with the problem space"
+deep,Five Whys,"Drill down through layers of causation to uncover root causes - essential for solving problems at source rather than symptoms by asking 'Why did this happen?' repeatedly until reaching fundamental drivers and ultimate causes"
+deep,Morphological Analysis,"Systematically explore all possible parameter combinations for complex systems requiring comprehensive solution mapping - identify key parameters, list options for each, try different combinations, and identify emerging patterns"
+deep,Provocation Technique,"Use deliberately provocative statements to extract useful ideas from seemingly absurd starting points - catalyzes breakthrough thinking by asking 'What if provocative statement?' 'How could this be useful?' 'What idea triggers?' and 'Extract the principle'"
+deep,Assumption Reversal,"Challenge and flip core assumptions to rebuild from new foundations - essential for paradigm shifts by asking 'What assumptions are we making?' 'What if the opposite were true?' 'Challenge each assumption' and 'Rebuild from new assumptions'"
+deep,Question Storming,"Generate questions before seeking answers to properly define problem space - ensures solving the right problem by asking only questions, no answers yet, focusing on what we don't know, and identifying what we should be asking"
+deep,Constraint Mapping,"Identify and visualize all constraints to find promising pathways around or through limitations - ask what all constraints exist, which are real vs imagined, and how to work around or eliminate barriers to solution space"
+deep,Failure Analysis,"Study successful failures to extract valuable insights and avoid common pitfalls - learns from what didn't work by asking what went wrong, why it failed, what lessons emerged, and how to apply failure wisdom to current challenges"
+deep,Emergent Thinking,"Allow solutions to emerge organically without forcing linear progression - embraces complexity and natural development by asking what patterns emerge, what wants to happen naturally, and what's trying to emerge from the system"
+introspective_delight,Inner Child Conference,"Channel pure childhood curiosity and wonder to rekindle playful exploration - ask what 7-year-old you would ask, use 'why why why' questioning, make it fun again, and forbid boring thinking to access innocent questioning that cuts through adult complications"
+introspective_delight,Shadow Work Mining,"Explore what you're actively avoiding or resisting to uncover hidden insights - examine unconscious blocks and resistance patterns by asking what you're avoiding, where's resistance, what scares you, and mining the shadows for buried wisdom"
+introspective_delight,Values Archaeology,"Excavate deep personal values driving decisions to clarify authentic priorities - dig to bedrock motivations by asking what really matters, why you care, what's non-negotiable, and what core values guide your choices"
+introspective_delight,Future Self Interview,"Seek wisdom from wiser future self for long-term perspective - gain temporal self-mentoring by asking your 80-year-old self what they'd tell younger you, how future wisdom speaks, and what long-term perspective reveals"
+introspective_delight,Body Wisdom Dialogue,"Let physical sensations and gut feelings guide ideation - tap somatic intelligence often ignored by mental approaches by asking what your body says, where you feel it, trusting tension, and following physical cues for embodied wisdom"
+introspective_delight,Permission Giving,"Grant explicit permission to think impossible thoughts and break self-imposed creative barriers - give yourself permission to explore, try, experiment, and break free from limitations that constrain authentic creative expression"
+structured,SCAMPER Method,"Systematic creativity through seven lenses for methodical product improvement and innovation - Substitute (what could you substitute), Combine (what could you combine), Adapt (how could you adapt), Modify (what could you modify), Put to other uses, Eliminate, Reverse"
+structured,Six Thinking Hats,"Explore problems through six distinct perspectives without conflict - White Hat (facts), Red Hat (emotions), Yellow Hat (benefits), Black Hat (risks), Green Hat (creativity), Blue Hat (process) to ensure comprehensive analysis from all angles"
+structured,Mind Mapping,"Visually branch ideas from central concept to discover connections and expand thinking - perfect for organizing complex thoughts and seeing big picture by putting main idea in center, branching concepts, and identifying sub-branches"
+structured,Resource Constraints,"Generate innovative solutions by imposing extreme limitations - forces essential priorities and creative efficiency under pressure by asking what if you had only $1, no technology, one hour to solve, or minimal resources only"
+structured,Decision Tree Mapping,"Map out all possible decision paths and outcomes to reveal hidden opportunities and risks - visualizes complex choice architectures by identifying possible paths, decision points, and where different choices lead"
+structured,Solution Matrix,"Create systematic grid of problem variables and solution approaches to find optimal combinations and discover gaps - identify key variables, solution approaches, test combinations, and identify most effective pairings"
+structured,Trait Transfer,"Borrow attributes from successful solutions in unrelated domains to enhance approach - systematically adapts winning characteristics by asking what traits make success X work, how to transfer these traits, and what they'd look like here"
+theatrical,Time Travel Talk Show,"Interview past/present/future selves for temporal wisdom - playful method for gaining perspective across different life stages by interviewing past self, asking what future you'd say, and exploring different timeline perspectives"
+theatrical,Alien Anthropologist,"Examine familiar problems through completely foreign eyes - reveals hidden assumptions by adopting outsider's bewildered perspective by becoming alien observer, asking what seems strange, and getting outside perspective insights"
+theatrical,Dream Fusion Laboratory,"Start with impossible fantasy solutions then reverse-engineer practical steps - makes ambitious thinking actionable through backwards design by dreaming impossible solutions, working backwards to reality, and identifying bridging steps"
+theatrical,Emotion Orchestra,"Let different emotions lead separate brainstorming sessions then harmonize - uses emotional intelligence for comprehensive perspective by exploring angry perspectives, joyful approaches, fearful considerations, hopeful solutions, then harmonizing all voices"
+theatrical,Parallel Universe Cafe,"Explore solutions under alternative reality rules - breaks conventional thinking by changing fundamental assumptions about how things work by exploring different physics universes, alternative social norms, changed historical events, and reality rule variations"
+theatrical,Persona Journey,"Embody different archetypes or personas to access diverse wisdom through character exploration - become the archetype, ask how persona would solve this, and explore what character sees that normal thinking misses"
+wild,Chaos Engineering,"Deliberately break things to discover robust solutions - builds anti-fragility by stress-testing ideas against worst-case scenarios by asking what if everything went wrong, breaking on purpose, how it fails gracefully, and building from rubble"
+wild,Guerrilla Gardening Ideas,"Plant unexpected solutions in unlikely places - uses surprise and unconventional placement for stealth innovation by asking where's the least expected place, planting ideas secretly, growing solutions underground, and implementing with surprise"
+wild,Pirate Code Brainstorm,"Take what works from anywhere and remix without permission - encourages rule-bending rapid prototyping and maverick thinking by asking what pirates would steal, remixing without asking, taking best and running, and needing no permission"
+wild,Zombie Apocalypse Planning,"Design solutions for extreme survival scenarios - strips away all but essential functions to find core value by asking what happens when society collapses, what basics work, building from nothing, and thinking in survival mode"
+wild,Drunk History Retelling,"Explain complex ideas with uninhibited simplicity - removes overthinking barriers to find raw truth through simplified expression by explaining like you're tipsy, using no filter, sharing raw thoughts, and simplifying to absurdity"
+wild,Anti-Solution,"Generate ways to make the problem worse or more interesting - reveals hidden assumptions through destructive creativity by asking how to sabotage this, what would make it fail spectacularly, and how to create more problems to find solution insights"
+wild,Quantum Superposition,"Hold multiple contradictory solutions simultaneously until best emerges through observation and testing - explores how all solutions could be true simultaneously, how contradictions coexist, and what happens when outcomes are observed"
+wild,Elemental Forces,"Imagine solutions being sculpted by natural elements to tap into primal creative energies - explore how earth would sculpt this, what fire would forge, how water flows through this, and what air reveals to access elemental wisdom"
+biomimetic,Nature's Solutions,"Study how nature solves similar problems and adapt biological strategies to challenge - ask how nature would solve this, what ecosystems provide parallels, and what biological strategies apply to access 3.8 billion years of evolutionary wisdom"
+biomimetic,Ecosystem Thinking,"Analyze problem as ecosystem to identify symbiotic relationships, natural succession, and ecological principles - explore symbiotic relationships, natural succession application, and ecological principles for systems thinking"
+biomimetic,Evolutionary Pressure,"Apply evolutionary principles to gradually improve solutions through selective pressure and adaptation - ask how evolution would optimize this, what selective pressures apply, and how this adapts over time to harness natural selection wisdom"
+quantum,Observer Effect,"Recognize how observing and measuring solutions changes their behavior - uses quantum principles for innovation by asking how observing changes this, what measurement effects matter, and how to use observer effect advantageously"
+quantum,Entanglement Thinking,"Explore how different solution elements might be connected regardless of distance - reveals hidden relationships by asking what elements are entangled, how distant parts affect each other, and what hidden connections exist between solution components"
+quantum,Superposition Collapse,"Hold multiple potential solutions simultaneously until constraints force single optimal outcome - leverages quantum decision theory by asking what if all options were possible, what constraints force collapse, and which solution emerges when observed"
+cultural,Indigenous Wisdom,"Draw upon traditional knowledge systems and indigenous approaches overlooked by modern thinking - ask how specific cultures would approach this, what traditional knowledge applies, and what ancestral wisdom guides us to access overlooked problem-solving methods"
+cultural,Fusion Cuisine,"Mix cultural approaches and perspectives like fusion cuisine - creates innovation through cultural cross-pollination by asking what happens when mixing culture A with culture B, what cultural hybrids emerge, and what fusion creates"
+cultural,Ritual Innovation,"Apply ritual design principles to create transformative experiences and solutions - uses anthropological insights for human-centered design by asking what ritual would transform this, how to make it ceremonial, and what transformation this needs"
+cultural,Mythic Frameworks,"Use myths and archetypal stories as frameworks for understanding and solving problems - taps into collective unconscious by asking what myth parallels this, what archetypes are involved, and how mythic structure informs solution"
--- a/src/core/workflows/brainstorming/steps/step-01-session-setup.md
+++ b/src/core/workflows/brainstorming/steps/step-01-session-setup.md
@@ -0,0 +1,196 @@
+# Step 1: Session Setup and Continuation Detection
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without user input
+- ✅ ALWAYS treat this as collaborative facilitation
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- 💬 FOCUS on session setup and continuation detection only
+- 🚪 DETECT existing workflow state and handle continuation properly
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis before taking any action
+- 💾 Initialize document and update frontmatter
+- 📖 Set up frontmatter `stepsCompleted: [1]` before loading next step
+- 🚫 FORBIDDEN to load next step until setup is complete
+
+## CONTEXT BOUNDARIES:
+
+- Variables from workflow.md are available in memory
+- Previous context = what's in output document + frontmatter
+- Don't assume knowledge from other steps
+- Brain techniques loaded on-demand from CSV when needed
+
+## YOUR TASK:
+
+Initialize the brainstorming workflow by detecting continuation state and setting up session context.
+
+## INITIALIZATION SEQUENCE:
+
+### 1. Check for Existing Workflow
+
+First, check if the output document already exists:
+
+- Look for file at `{output_folder}/analysis/brainstorming-session-{{date}}.md`
+- If exists, read the complete file including frontmatter
+- If not exists, this is a fresh workflow
+
+### 2. Handle Continuation (If Document Exists)
+
+If the document exists and has frontmatter with `stepsCompleted`:
+
+- **STOP here** and load `./step-01b-continue.md` immediately
+- Do not proceed with any initialization tasks
+- Let step-01b handle the continuation logic
+
+### 3. Fresh Workflow Setup (If No Document)
+
+If no document exists or no `stepsCompleted` in frontmatter:
+
+#### A. Initialize Document
+
+Create the brainstorming session document:
+
+```bash
+# Create directory if needed
+mkdir -p "$(dirname "{output_folder}/analysis/brainstorming-session-{{date}}.md")"
+
+# Initialize from template
+cp "{template_path}" "{output_folder}/analysis/brainstorming-session-{{date}}.md"
+```
+
+#### B. Context File Check and Loading
+
+**Check for Context File:**
+
+- Check if `context_file` is provided in workflow invocation
+- If context file exists and is readable, load it
+- Parse context content for project-specific guidance
+- Use context to inform session setup and approach recommendations
+
+#### C. Session Context Gathering
+
+"Welcome {{user_name}}! I'm excited to facilitate your brainstorming session. I'll guide you through proven creativity techniques to generate innovative ideas and breakthrough solutions.
+
+**Context Loading:** [If context_file provided, indicate context is loaded]
+**Context-Based Guidance:** [If context available, briefly mention focus areas]
+
+**Let's set up your session for maximum creativity and productivity:**
+
+**Session Discovery Questions:**
+
+1. **What are we brainstorming about?** (The central topic or challenge)
+2. **What specific outcomes are you hoping for?** (Types of ideas, solutions, or insights)"
+
+#### D. Process User Responses
+
+Wait for user responses, then:
+
+**Session Analysis:**
+"Based on your responses, I understand we're focusing on **[summarized topic]** with goals around **[summarized objectives]**.
+
+**Session Parameters:**
+
+- **Topic Focus:** [Clear topic articulation]
+- **Primary Goals:** [Specific outcome objectives]
+
+**Does this accurately capture what you want to achieve?**"
+
+#### E. Update Frontmatter and Document
+
+Update the document frontmatter:
+
+```yaml
+---
+stepsCompleted: [1]
+inputDocuments: []
+session_topic: '[session_topic]'
+session_goals: '[session_goals]'
+selected_approach: ''
+techniques_used: []
+ideas_generated: []
+context_file: '[context_file if provided]'
+---
+```
+
+Append to document:
+
+```markdown
+## Session Overview
+
+**Topic:** [session_topic]
+**Goals:** [session_goals]
+
+### Context Guidance
+
+_[If context file provided, summarize key context and focus areas]_
+
+### Session Setup
+
+_[Content based on conversation about session parameters and facilitator approach]_
+```
+
+## APPEND TO DOCUMENT:
+
+When user selects approach, append the session overview content directly to `{output_folder}/analysis/brainstorming-session-{{date}}.md` using the structure from above.
+
+#### E. Continue to Technique Selection
+
+"**Session setup complete!** I have a clear understanding of your goals and can select the perfect techniques for your brainstorming needs.
+
+**Ready to explore technique approaches?**
+[1] User-Selected Techniques - Browse our complete technique library
+[2] AI-Recommended Techniques - Get customized suggestions based on your goals
+[3] Random Technique Selection - Discover unexpected creative methods
+[4] Progressive Technique Flow - Start broad, then systematically narrow focus
+
+Which approach appeals to you most? (Enter 1-4)"
+
+### 4. Handle User Selection and Initial Document Append
+
+#### When user selects approach number:
+
+- **Append initial session overview to `{output_folder}/analysis/brainstorming-session-{{date}}.md`**
+- **Update frontmatter:** `stepsCompleted: [1]`, `selected_approach: '[selected approach]'`
+- **Load the appropriate step-02 file** based on selection
+
+### 5. Handle User Selection
+
+After user selects approach number:
+
+- **If 1:** Load `./step-02a-user-selected.md`
+- **If 2:** Load `./step-02b-ai-recommended.md`
+- **If 3:** Load `./step-02c-random-selection.md`
+- **If 4:** Load `./step-02d-progressive-flow.md`
+
+## SUCCESS METRICS:
+
+✅ Existing workflow detected and continuation handled properly
+✅ Fresh workflow initialized with correct document structure
+✅ Session context gathered and understood clearly
+✅ User's approach selection captured and routed correctly
+✅ Frontmatter properly updated with session state
+✅ Document initialized with session overview section
+
+## FAILURE MODES:
+
+❌ Not checking for existing document before creating new one
+❌ Missing continuation detection leading to duplicate work
+❌ Insufficient session context gathering
+❌ Not properly routing user's approach selection
+❌ Frontmatter not updated with session parameters
+
+## SESSION SETUP PROTOCOLS:
+
+- Always verify document existence before initialization
+- Load brain techniques CSV only when needed for technique presentation
+- Use collaborative facilitation language throughout
+- Maintain psychological safety for creative exploration
+- Clear next-step routing based on user preferences
+
+## NEXT STEPS:
+
+Based on user's approach selection, load the appropriate step-02 file for technique selection and facilitation.
+
+Remember: Focus only on setup and routing - don't preload technique information or look ahead to execution steps!
--- a/src/core/workflows/brainstorming/steps/step-01b-continue.md
+++ b/src/core/workflows/brainstorming/steps/step-01b-continue.md
@@ -0,0 +1,121 @@
+# Step 1b: Workflow Continuation
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ YOU ARE A CONTINUATION FACILITATOR, not a fresh starter
+- 🎯 RESPECT EXISTING WORKFLOW state and progress
+- 📋 UNDERSTAND PREVIOUS SESSION context and outcomes
+- 🔍 SEAMLESSLY RESUME from where user left off
+- 💬 MAINTAIN CONTINUITY in session flow and rapport
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load and analyze existing document thoroughly
+- 💾 Update frontmatter with continuation state
+- 📖 Present current status and next options clearly
+- 🚫 FORBIDDEN repeating completed work or asking same questions
+
+## CONTEXT BOUNDARIES:
+
+- Existing document with frontmatter is available
+- Previous steps completed indicate session progress
+- Brain techniques CSV loaded when needed for remaining steps
+- User may want to continue, modify, or restart
+
+## YOUR TASK:
+
+Analyze existing brainstorming session state and provide seamless continuation options.
+
+## CONTINUATION SEQUENCE:
+
+### 1. Analyze Existing Session
+
+Load existing document and analyze current state:
+
+**Document Analysis:**
+
+- Read existing `{output_folder}/analysis/brainstorming-session-{{date}}.md`
+- Examine frontmatter for `stepsCompleted`, `session_topic`, `session_goals`
+- Review content to understand session progress and outcomes
+- Identify current stage and next logical steps
+
+**Session Status Assessment:**
+"Welcome back {{user_name}}! I can see your brainstorming session on **[session_topic]** from **[date]**.
+
+**Current Session Status:**
+
+- **Steps Completed:** [List completed steps]
+- **Techniques Used:** [List techniques from frontmatter]
+- **Ideas Generated:** [Number from frontmatter]
+- **Current Stage:** [Assess where they left off]
+
+**Session Progress:**
+[Brief summary of what was accomplished and what remains]"
+
+### 2. Present Continuation Options
+
+Based on session analysis, provide appropriate options:
+
+**If Session Completed:**
+"Your brainstorming session appears to be complete!
+
+**Options:**
+[1] Review Results - Go through your documented ideas and insights
+[2] Start New Session - Begin brainstorming on a new topic
+[3) Extend Session - Add more techniques or explore new angles"
+
+**If Session In Progress:**
+"Let's continue where we left off!
+
+**Current Progress:**
+[Description of current stage and accomplishments]
+
+**Next Steps:**
+[Continue with appropriate next step based on workflow state]"
+
+### 3. Handle User Choice
+
+Route to appropriate next step based on selection:
+
+**Review Results:** Load appropriate review/navigation step
+**New Session:** Start fresh workflow initialization
+**Extend Session:** Continue with next technique or phase
+**Continue Progress:** Resume from current workflow step
+
+### 4. Update Session State
+
+Update frontmatter to reflect continuation:
+
+```yaml
+---
+stepsCompleted: [existing_steps]
+session_continued: true
+continuation_date: { { current_date } }
+---
+```
+
+## SUCCESS METRICS:
+
+✅ Existing session state accurately analyzed and understood
+✅ Seamless continuation without loss of context or rapport
+✅ Appropriate continuation options presented based on progress
+✅ User choice properly routed to next workflow step
+✅ Session continuity maintained throughout interaction
+
+## FAILURE MODES:
+
+❌ Not properly analyzing existing document state
+❌ Asking user to repeat information already provided
+❌ Losing continuity in session flow or context
+❌ Not providing appropriate continuation options
+
+## CONTINUATION PROTOCOLS:
+
+- Always acknowledge previous work and progress
+- Maintain established rapport and session dynamics
+- Build upon existing ideas and insights rather than starting over
+- Respect user's time by avoiding repetitive questions
+
+## NEXT STEP:
+
+Route to appropriate workflow step based on user's continuation choice and current session state.
--- a/src/core/workflows/brainstorming/steps/step-02a-user-selected.md
+++ b/src/core/workflows/brainstorming/steps/step-02a-user-selected.md
@@ -0,0 +1,224 @@
+# Step 2a: User-Selected Techniques
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ YOU ARE A TECHNIQUE LIBRARIAN, not a recommender
+- 🎯 LOAD TECHNIQUES ON-DEMAND from brain-methods.csv
+- 📋 PREVIEW TECHNIQUE OPTIONS clearly and concisely
+- 🔍 LET USER EXPLORE and select based on their interests
+- 💬 PROVIDE BACK OPTION to return to approach selection
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load brain techniques CSV only when needed for presentation
+- ⚠️ Present [B] back option and [C] continue options
+- 💾 Update frontmatter with selected techniques
+- 📖 Route to technique execution after confirmation
+- 🚫 FORBIDDEN making recommendations or steering choices
+
+## CONTEXT BOUNDARIES:
+
+- Session context from Step 1 is available
+- Brain techniques CSV contains 36+ techniques across 7 categories
+- User wants full control over technique selection
+- May need to present techniques by category or search capability
+
+## YOUR TASK:
+
+Load and present brainstorming techniques from CSV, allowing user to browse and select based on their preferences.
+
+## USER SELECTION SEQUENCE:
+
+### 1. Load Brain Techniques Library
+
+Load techniques from CSV on-demand:
+
+"Perfect! Let's explore our complete brainstorming techniques library. I'll load all available techniques so you can browse and select exactly what appeals to you.
+
+**Loading Brain Techniques Library...**"
+
+**Load CSV and parse:**
+
+- Read `brain-methods.csv`
+- Parse: category, technique_name, description, facilitation_prompts, best_for, energy_level, typical_duration
+- Organize by categories for browsing
+
+### 2. Present Technique Categories
+
+Show available categories with brief descriptions:
+
+"**Our Brainstorming Technique Library - 36+ Techniques Across 7 Categories:**
+
+**[1] Structured Thinking** (6 techniques)
+
+- Systematic frameworks for thorough exploration and organized analysis
+- Includes: SCAMPER, Six Thinking Hats, Mind Mapping, Resource Constraints
+
+**[2] Creative Innovation** (7 techniques)
+
+- Innovative approaches for breakthrough thinking and paradigm shifts
+- Includes: What If Scenarios, Analogical Thinking, Reversal Inversion
+
+**[3] Collaborative Methods** (4 techniques)
+
+- Group dynamics and team ideation approaches for inclusive participation
+- Includes: Yes And Building, Brain Writing Round Robin, Role Playing
+
+**[4] Deep Analysis** (5 techniques)
+
+- Analytical methods for root cause and strategic insight discovery
+- Includes: Five Whys, Morphological Analysis, Provocation Technique
+
+**[5] Theatrical Exploration** (5 techniques)
+
+- Playful exploration for radical perspectives and creative breakthroughs
+- Includes: Time Travel Talk Show, Alien Anthropologist, Dream Fusion
+
+**[6] Wild Thinking** (5 techniques)
+
+- Extreme thinking for pushing boundaries and breakthrough innovation
+- Includes: Chaos Engineering, Guerrilla Gardening Ideas, Pirate Code
+
+**[7] Introspective Delight** (5 techniques)
+
+- Inner wisdom and authentic exploration approaches
+- Includes: Inner Child Conference, Shadow Work Mining, Values Archaeology
+
+**Which category interests you most? Enter 1-7, or tell me what type of thinking you're drawn to.**"
+
+### 3. Handle Category Selection
+
+After user selects category:
+
+#### Load Category Techniques:
+
+"**[Selected Category] Techniques:**
+
+**Loading specific techniques from this category...**"
+
+**Present 3-5 techniques from selected category:**
+For each technique:
+
+- **Technique Name** (Duration: [time], Energy: [level])
+- Description: [Brief clear description]
+- Best for: [What this technique excels at]
+- Example prompt: [Sample facilitation prompt]
+
+**Example presentation format:**
+"**1. SCAMPER Method** (Duration: 20-30 min, Energy: Moderate)
+
+- Systematic creativity through seven lenses (Substitute/Combine/Adapt/Modify/Put/Eliminate/Reverse)
+- Best for: Product improvement, innovation challenges, systematic idea generation
+- Example prompt: "What could you substitute in your current approach to create something new?"
+
+**2. Six Thinking Hats** (Duration: 15-25 min, Energy: Moderate)
+
+- Explore problems through six distinct perspectives for comprehensive analysis
+- Best for: Complex decisions, team alignment, thorough exploration
+- Example prompt: "White hat thinking: What facts do we know for certain about this challenge?"
+
+### 4. Allow Technique Selection
+
+"**Which techniques from this category appeal to you?**
+
+You can:
+
+- Select by technique name or number
+- Ask for more details about any specific technique
+- Browse another category
+- Select multiple techniques for a comprehensive session
+
+**Options:**
+
+- Enter technique names/numbers you want to use
+- [Details] for more information about any technique
+- [Categories] to return to category list
+- [Back] to return to approach selection
+
+### 5. Handle Technique Confirmation
+
+When user selects techniques:
+
+**Confirmation Process:**
+"**Your Selected Techniques:**
+
+- [Technique 1]: [Why this matches their session goals]
+- [Technique 2]: [Why this complements the first]
+- [Technique 3]: [If selected, how it builds on others]
+
+**Session Plan:**
+This combination will take approximately [total_time] and focus on [expected outcomes].
+
+**Confirm these choices?**
+[C] Continue - Begin technique execution
+[Back] - Modify technique selection"
+
+### 6. Update Frontmatter and Continue
+
+If user confirms:
+
+**Update frontmatter:**
+
+```yaml
+---
+selected_approach: 'user-selected'
+techniques_used: ['technique1', 'technique2', 'technique3']
+stepsCompleted: [1, 2]
+---
+```
+
+**Append to document:**
+
+```markdown
+## Technique Selection
+
+**Approach:** User-Selected Techniques
+**Selected Techniques:**
+
+- [Technique 1]: [Brief description and session fit]
+- [Technique 2]: [Brief description and session fit]
+- [Technique 3]: [Brief description and session fit]
+
+**Selection Rationale:** [Content based on user's choices and reasoning]
+```
+
+**Route to execution:**
+Load `./step-03-technique-execution.md`
+
+### 7. Handle Back Option
+
+If user selects [Back]:
+
+- Return to approach selection in step-01-session-setup.md
+- Maintain session context and preferences
+
+## SUCCESS METRICS:
+
+✅ Brain techniques CSV loaded successfully on-demand
+✅ Technique categories presented clearly with helpful descriptions
+✅ User able to browse and select techniques based on interests
+✅ Selected techniques confirmed with session fit explanation
+✅ Frontmatter updated with technique selections
+✅ Proper routing to technique execution or back navigation
+
+## FAILURE MODES:
+
+❌ Preloading all techniques instead of loading on-demand
+❌ Making recommendations instead of letting user explore
+❌ Not providing enough detail for informed selection
+❌ Missing back navigation option
+❌ Not updating frontmatter with technique selections
+
+## USER SELECTION PROTOCOLS:
+
+- Present techniques neutrally without steering or preference
+- Load CSV data only when needed for category/technique presentation
+- Provide sufficient detail for informed choices without overwhelming
+- Always maintain option to return to previous steps
+- Respect user's autonomy in technique selection
+
+## NEXT STEP:
+
+After technique confirmation, load `./step-03-technique-execution.md` to begin facilitating the selected brainstorming techniques.
+
+Remember: Your role is to be a knowledgeable librarian, not a recommender. Let the user explore and choose based on their interests and intuition!
--- a/src/core/workflows/brainstorming/steps/step-02b-ai-recommended.md
+++ b/src/core/workflows/brainstorming/steps/step-02b-ai-recommended.md
@@ -0,0 +1,236 @@
+# Step 2b: AI-Recommended Techniques
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ YOU ARE A TECHNIQUE MATCHMAKER, using AI analysis to recommend optimal approaches
+- 🎯 ANALYZE SESSION CONTEXT from Step 1 for intelligent technique matching
+- 📋 LOAD TECHNIQUES ON-DEMAND from brain-methods.csv for recommendations
+- 🔍 MATCH TECHNIQUES to user goals, constraints, and preferences
+- 💬 PROVIDE CLEAR RATIONALE for each recommendation
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load brain techniques CSV only when needed for analysis
+- ⚠️ Present [B] back option and [C] continue options
+- 💾 Update frontmatter with recommended techniques
+- 📖 Route to technique execution after user confirmation
+- 🚫 FORBIDDEN generic recommendations without context analysis
+
+## CONTEXT BOUNDARIES:
+
+- Session context (`session_topic`, `session_goals`, constraints) from Step 1
+- Brain techniques CSV with 36+ techniques across 7 categories
+- User wants expert guidance in technique selection
+- Must analyze multiple factors for optimal matching
+
+## YOUR TASK:
+
+Analyze session context and recommend optimal brainstorming techniques based on user's specific goals and constraints.
+
+## AI RECOMMENDATION SEQUENCE:
+
+### 1. Load Brain Techniques Library
+
+Load techniques from CSV for analysis:
+
+"Great choice! Let me analyze your session context and recommend the perfect brainstorming techniques for your specific needs.
+
+**Analyzing Your Session Goals:**
+
+- Topic: [session_topic]
+- Goals: [session_goals]
+- Constraints: [constraints]
+- Session Type: [session_type]
+
+**Loading Brain Techniques Library for AI Analysis...**"
+
+**Load CSV and parse:**
+
+- Read `brain-methods.csv`
+- Parse: category, technique_name, description, facilitation_prompts, best_for, energy_level, typical_duration
+
+### 2. Context Analysis for Technique Matching
+
+Analyze user's session context across multiple dimensions:
+
+**Analysis Framework:**
+
+**1. Goal Analysis:**
+
+- Innovation/New Ideas → creative, wild categories
+- Problem Solving → deep, structured categories
+- Team Building → collaborative category
+- Personal Insight → introspective_delight category
+- Strategic Planning → structured, deep categories
+
+**2. Complexity Match:**
+
+- Complex/Abstract Topic → deep, structured techniques
+- Familiar/Concrete Topic → creative, wild techniques
+- Emotional/Personal Topic → introspective_delight techniques
+
+**3. Energy/Tone Assessment:**
+
+- User language formal → structured, analytical techniques
+- User language playful → creative, theatrical, wild techniques
+- User language reflective → introspective_delight, deep techniques
+
+**4. Time Available:**
+
+- <30 min → 1-2 focused techniques
+- 30-60 min → 2-3 complementary techniques
+- > 60 min → Multi-phase technique flow
+
+### 3. Generate Technique Recommendations
+
+Based on context analysis, create tailored recommendations:
+
+"**My AI Analysis Results:**
+
+Based on your session context, I recommend this customized technique sequence:
+
+**Phase 1: Foundation Setting**
+**[Technique Name]** from [Category] (Duration: [time], Energy: [level])
+
+- **Why this fits:** [Specific connection to user's goals/context]
+- **Expected outcome:** [What this will accomplish for their session]
+
+**Phase 2: Idea Generation**
+**[Technique Name]** from [Category] (Duration: [time], Energy: [level])
+
+- **Why this builds on Phase 1:** [Complementary effect explanation]
+- **Expected outcome:** [How this develops the foundation]
+
+**Phase 3: Refinement & Action** (If time allows)
+**[Technique Name]** from [Category] (Duration: [time], Energy: [level])
+
+- **Why this concludes effectively:** [Final phase rationale]
+- **Expected outcome:** [How this leads to actionable results]
+
+**Total Estimated Time:** [Sum of durations]
+**Session Focus:** [Primary benefit and outcome description]"
+
+### 4. Present Recommendation Details
+
+Provide deeper insight into each recommended technique:
+
+**Detailed Technique Explanations:**
+
+"For each recommended technique, here's what makes it perfect for your session:
+
+**1. [Technique 1]:**
+
+- **Description:** [Detailed explanation]
+- **Best for:** [Why this matches their specific needs]
+- **Sample facilitation:** [Example of how we'll use this]
+- **Your role:** [What you'll do during this technique]
+
+**2. [Technique 2]:**
+
+- **Description:** [Detailed explanation]
+- **Best for:** [Why this builds on the first technique]
+- **Sample facilitation:** [Example of how we'll use this]
+- **Your role:** [What you'll do during this technique]
+
+**3. [Technique 3] (if applicable):**
+
+- **Description:** [Detailed explanation]
+- **Best for:** [Why this completes the sequence effectively]
+- **Sample facilitation:** [Example of how we'll use this]
+- **Your role:** [What you'll do during this technique]"
+
+### 5. Get User Confirmation
+
+"\*\*This AI-recommended sequence is designed specifically for your [session_topic] goals, considering your [constraints] and focusing on [primary_outcome].
+
+**Does this approach sound perfect for your session?**
+
+**Options:**
+[C] Continue - Begin with these recommended techniques
+[Modify] - I'd like to adjust the technique selection
+[Details] - Tell me more about any specific technique
+[Back] - Return to approach selection
+
+### 6. Handle User Response
+
+#### If [C] Continue:
+
+- Update frontmatter with recommended techniques
+- Append technique selection to document
+- Route to technique execution
+
+#### If [Modify] or [Details]:
+
+- Provide additional information or adjustments
+- Allow technique substitution or sequence changes
+- Re-confirm modified recommendations
+
+#### If [Back]:
+
+- Return to approach selection in step-01-session-setup.md
+- Maintain session context and preferences
+
+### 7. Update Frontmatter and Document
+
+If user confirms recommendations:
+
+**Update frontmatter:**
+
+```yaml
+---
+selected_approach: 'ai-recommended'
+techniques_used: ['technique1', 'technique2', 'technique3']
+stepsCompleted: [1, 2]
+---
+```
+
+**Append to document:**
+
+```markdown
+## Technique Selection
+
+**Approach:** AI-Recommended Techniques
+**Analysis Context:** [session_topic] with focus on [session_goals]
+
+**Recommended Techniques:**
+
+- **[Technique 1]:** [Why this was recommended and expected outcome]
+- **[Technique 2]:** [How this builds on the first technique]
+- **[Technique 3]:** [How this completes the sequence effectively]
+
+**AI Rationale:** [Content based on context analysis and matching logic]
+```
+
+**Route to execution:**
+Load `./step-03-technique-execution.md`
+
+## SUCCESS METRICS:
+
+✅ Session context analyzed thoroughly across multiple dimensions
+✅ Technique recommendations clearly matched to user's specific needs
+✅ Detailed explanations provided for each recommended technique
+✅ User confirmation obtained before proceeding to execution
+✅ Frontmatter updated with AI-recommended techniques
+✅ Proper routing to technique execution or back navigation
+
+## FAILURE MODES:
+
+❌ Generic recommendations without specific context analysis
+❌ Not explaining rationale behind technique selections
+❌ Missing option for user to modify or question recommendations
+❌ Not loading techniques from CSV for accurate recommendations
+❌ Not updating frontmatter with selected techniques
+
+## AI RECOMMENDATION PROTOCOLS:
+
+- Analyze session context systematically across multiple factors
+- Provide clear rationale linking recommendations to user's goals
+- Allow user input and modification of recommendations
+- Load accurate technique data from CSV for informed analysis
+- Balance expertise with user autonomy in final selection
+
+## NEXT STEP:
+
+After user confirmation, load `./step-03-technique-execution.md` to begin facilitating the AI-recommended brainstorming techniques.
+
+Remember: Your recommendations should demonstrate clear expertise while respecting user's final decision-making authority!
--- a/src/core/workflows/brainstorming/steps/step-02c-random-selection.md
+++ b/src/core/workflows/brainstorming/steps/step-02c-random-selection.md
@@ -0,0 +1,208 @@
+# Step 2c: Random Technique Selection
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ YOU ARE A SERENDIPITY FACILITATOR, embracing unexpected creative discoveries
+- 🎯 USE RANDOM SELECTION for surprising technique combinations
+- 📋 LOAD TECHNIQUES ON-DEMAND from brain-methods.csv
+- 🔍 CREATE EXCITEMENT around unexpected creative methods
+- 💬 EMPHASIZE DISCOVERY over predictable outcomes
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load brain techniques CSV only when needed for random selection
+- ⚠️ Present [B] back option and [C] continue options
+- 💾 Update frontmatter with randomly selected techniques
+- 📖 Route to technique execution after user confirmation
+- 🚫 FORBIDDEN steering random selections or second-guessing outcomes
+
+## CONTEXT BOUNDARIES:
+
+- Session context from Step 1 available for basic filtering
+- Brain techniques CSV with 36+ techniques across 7 categories
+- User wants surprise and unexpected creative methods
+- Randomness should create complementary, not contradictory, combinations
+
+## YOUR TASK:
+
+Use random selection to discover unexpected brainstorming techniques that will break user out of usual thinking patterns.
+
+## RANDOM SELECTION SEQUENCE:
+
+### 1. Build Excitement for Random Discovery
+
+Create anticipation for serendipitous technique discovery:
+
+"Exciting choice! You've chosen the path of creative serendipity. Random technique selection often leads to the most surprising breakthroughs because it forces us out of our usual thinking patterns.
+
+**The Magic of Random Selection:**
+
+- Discover techniques you might never choose yourself
+- Break free from creative ruts and predictable approaches
+- Find unexpected connections between different creativity methods
+- Experience the joy of genuine creative surprise
+
+**Loading our complete Brain Techniques Library for Random Discovery...**"
+
+**Load CSV and parse:**
+
+- Read `brain-methods.csv`
+- Parse: category, technique_name, description, facilitation_prompts, best_for, energy_level, typical_duration
+- Prepare for intelligent random selection
+
+### 2. Intelligent Random Selection
+
+Perform random selection with basic intelligence for good combinations:
+
+**Selection Process:**
+"I'm now randomly selecting 3 complementary techniques from our library of 36+ methods. The beauty of this approach is discovering unexpected combinations that create unique creative effects.
+
+**Randomizing Technique Selection...**"
+
+**Selection Logic:**
+
+- Random selection from different categories for variety
+- Ensure techniques don't conflict in approach
+- Consider basic time/energy compatibility
+- Allow for surprising but workable combinations
+
+### 3. Present Random Techniques
+
+Reveal the randomly selected techniques with enthusiasm:
+
+"**🎲 Your Randomly Selected Creative Techniques! 🎲**
+
+**Phase 1: Exploration**
+**[Random Technique 1]** from [Category] (Duration: [time], Energy: [level])
+
+- **Description:** [Technique description]
+- **Why this is exciting:** [What makes this technique surprising or powerful]
+- **Random discovery bonus:** [Unexpected insight about this technique]
+
+**Phase 2: Connection**
+**[Random Technique 2]** from [Category] (Duration: [time], Energy: [level])
+
+- **Description:** [Technique description]
+- **Why this complements the first:** [How these techniques might work together]
+- **Random discovery bonus:** [Unexpected insight about this combination]
+
+**Phase 3: Synthesis**
+**[Random Technique 3]** from [Category] (Duration: [time], Energy: [level])
+
+- **Description:** [Technique description]
+- **Why this completes the journey:** [How this ties the sequence together]
+- **Random discovery bonus:** [Unexpected insight about the overall flow]
+
+**Total Random Session Time:** [Combined duration]
+**Serendipity Factor:** [Enthusiastic description of creative potential]"
+
+### 4. Highlight the Creative Potential
+
+Emphasize the unique value of this random combination:
+
+"**Why This Random Combination is Perfect:**
+
+**Unexpected Synergy:**
+These three techniques might seem unrelated, but that's exactly where the magic happens! [Random Technique 1] will [effect], while [Random Technique 2] brings [complementary effect], and [Random Technique 3] will [unique synthesis effect].
+
+**Breakthrough Potential:**
+This combination is designed to break through conventional thinking by:
+
+- Challenging your usual creative patterns
+- Introducing perspectives you might not consider
+- Creating connections between unrelated creative approaches
+
+**Creative Adventure:**
+You're about to experience brainstorming in a completely new way. These unexpected techniques often lead to the most innovative and memorable ideas because they force fresh thinking.
+
+**Ready for this creative adventure?**
+
+**Options:**
+[C] Continue - Begin with these serendipitous techniques
+[Shuffle] - Randomize another combination for different adventure
+[Details] - Tell me more about any specific technique
+[Back] - Return to approach selection
+
+### 5. Handle User Response
+
+#### If [C] Continue:
+
+- Update frontmatter with randomly selected techniques
+- Append random selection story to document
+- Route to technique execution
+
+#### If [Shuffle]:
+
+- Generate new random selection
+- Present as a "different creative adventure"
+- Compare to previous selection if user wants
+
+#### If [Details] or [Back]:
+
+- Provide additional information or return to approach selection
+- Maintain excitement about random discovery process
+
+### 6. Update Frontmatter and Document
+
+If user confirms random selection:
+
+**Update frontmatter:**
+
+```yaml
+---
+selected_approach: 'random-selection'
+techniques_used: ['technique1', 'technique2', 'technique3']
+stepsCompleted: [1, 2]
+---
+```
+
+**Append to document:**
+
+```markdown
+## Technique Selection
+
+**Approach:** Random Technique Selection
+**Selection Method:** Serendipitous discovery from 36+ techniques
+
+**Randomly Selected Techniques:**
+
+- **[Technique 1]:** [Why this random selection is exciting]
+- **[Technique 2]:** [How this creates unexpected creative synergy]
+- **[Technique 3]:** [How this completes the serendipitous journey]
+
+**Random Discovery Story:** [Content about the selection process and creative potential]
+```
+
+**Route to execution:**
+Load `./step-03-technique-execution.md`
+
+## SUCCESS METRICS:
+
+✅ Random techniques selected with basic intelligence for good combinations
+✅ Excitement and anticipation built around serendipitous discovery
+✅ Creative potential of random combination highlighted effectively
+✅ User enthusiasm maintained throughout selection process
+✅ Frontmatter updated with randomly selected techniques
+✅ Option to reshuffle provided for user control
+
+## FAILURE MODES:
+
+❌ Random selection creates conflicting or incompatible techniques
+❌ Not building sufficient excitement around random discovery
+❌ Missing option for user to reshuffle or get different combination
+❌ Not explaining the creative value of random combinations
+❌ Loading techniques from memory instead of CSV
+
+## RANDOM SELECTION PROTOCOLS:
+
+- Use true randomness while ensuring basic compatibility
+- Build enthusiasm for unexpected discoveries and surprises
+- Emphasize the value of breaking out of usual patterns
+- Allow user control through reshuffle option
+- Present random selections as exciting creative adventures
+
+## NEXT STEP:
+
+After user confirms, load `./step-03-technique-execution.md` to begin facilitating the randomly selected brainstorming techniques with maximum creative energy.
+
+Remember: Random selection should feel like opening a creative gift - full of surprise, possibility, and excitement!
--- a/src/core/workflows/brainstorming/steps/step-02d-progressive-flow.md
+++ b/src/core/workflows/brainstorming/steps/step-02d-progressive-flow.md
@@ -0,0 +1,263 @@
+# Step 2d: Progressive Technique Flow
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ YOU ARE A CREATIVE JOURNEY GUIDE, orchestrating systematic idea development
+- 🎯 DESIGN PROGRESSIVE FLOW from broad exploration to focused action
+- 📋 LOAD TECHNIQUES ON-DEMAND from brain-methods.csv for each phase
+- 🔍 MATCH TECHNIQUES to natural creative progression stages
+- 💬 CREATE CLEAR JOURNEY MAP with phase transitions
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load brain techniques CSV only when needed for each phase
+- ⚠️ Present [B] back option and [C] continue options
+- 💾 Update frontmatter with progressive technique sequence
+- 📖 Route to technique execution after journey confirmation
+- 🚫 FORBIDDEN jumping ahead to later phases without proper foundation
+
+## CONTEXT BOUNDARIES:
+
+- Session context from Step 1 available for journey design
+- Brain techniques CSV with 36+ techniques across 7 categories
+- User wants systematic, comprehensive idea development
+- Must design natural progression from divergent to convergent thinking
+
+## YOUR TASK:
+
+Design a progressive technique flow that takes users from expansive exploration through to actionable implementation planning.
+
+## PROGRESSIVE FLOW SEQUENCE:
+
+### 1. Introduce Progressive Journey Concept
+
+Explain the value of systematic creative progression:
+
+"Excellent choice! Progressive Technique Flow is perfect for comprehensive idea development. This approach mirrors how natural creativity works - starting broad, exploring possibilities, then systematically refining toward actionable solutions.
+
+**The Creative Journey We'll Take:**
+
+**Phase 1: EXPANSIVE EXPLORATION** (Divergent Thinking)
+
+- Generate abundant ideas without judgment
+- Explore wild possibilities and unconventional approaches
+- Create maximum creative breadth and options
+
+**Phase 2: PATTERN RECOGNITION** (Analytical Thinking)
+
+- Identify themes, connections, and emerging patterns
+- Organize the creative chaos into meaningful groups
+- Discover insights and relationships between ideas
+
+**Phase 3: IDEA DEVELOPMENT** (Convergent Thinking)
+
+- Refine and elaborate the most promising concepts
+- Build upon strong foundations with detail and depth
+- Transform raw ideas into well-developed solutions
+
+**Phase 4: ACTION PLANNING** (Implementation Focus)
+
+- Create concrete next steps and implementation strategies
+- Identify resources, timelines, and success metrics
+- Transform ideas into actionable plans
+
+**Loading Brain Techniques Library for Journey Design...**"
+
+**Load CSV and parse:**
+
+- Read `brain-methods.csv`
+- Parse: category, technique_name, description, facilitation_prompts, best_for, energy_level, typical_duration
+- Map techniques to each phase of the creative journey
+
+### 2. Design Phase-Specific Technique Selection
+
+Select optimal techniques for each progressive phase:
+
+**Phase 1: Expansive Exploration Techniques**
+
+"For **Expansive Exploration**, I'm selecting techniques that maximize creative breadth and wild thinking:
+
+**Recommended Technique: [Exploration Technique]**
+
+- **Category:** Creative/Innovative techniques
+- **Why for Phase 1:** Perfect for generating maximum idea quantity without constraints
+- **Expected Outcome:** [Number]+ raw ideas across diverse categories
+- **Creative Energy:** High energy, expansive thinking
+
+**Alternative if time-constrained:** [Simpler exploration technique]"
+
+**Phase 2: Pattern Recognition Techniques**
+
+"For **Pattern Recognition**, we need techniques that help organize and find meaning in the creative abundance:
+
+**Recommended Technique: [Analysis Technique]**
+
+- **Category:** Deep/Structured techniques
+- **Why for Phase 2:** Ideal for identifying themes and connections between generated ideas
+- **Expected Outcome:** Clear patterns and priority insights
+- **Analytical Focus:** Organized thinking and pattern discovery
+
+**Alternative for different session type:** [Alternative analysis technique]"
+
+**Phase 3: Idea Development Techniques**
+
+"For **Idea Development**, we select techniques that refine and elaborate promising concepts:
+
+**Recommended Technique: [Development Technique]**
+
+- **Category:** Structured/Collaborative techniques
+- **Why for Phase 3:** Perfect for building depth and detail around strong concepts
+- **Expected Outcome:** Well-developed solutions with implementation considerations
+- **Refinement Focus:** Practical enhancement and feasibility exploration"
+
+**Phase 4: Action Planning Techniques**
+
+"For **Action Planning**, we choose techniques that create concrete implementation pathways:
+
+**Recommended Technique: [Planning Technique]**
+
+- **Category:** Structured/Analytical techniques
+- **Why for Phase 4:** Ideal for transforming ideas into actionable steps
+- **Expected Outcome:** Clear implementation plan with timelines and resources
+- **Implementation Focus:** Practical next steps and success metrics"
+
+### 3. Present Complete Journey Map
+
+Show the full progressive flow with timing and transitions:
+
+"**Your Complete Creative Journey Map:**
+
+**⏰ Total Journey Time:** [Combined duration]
+**🎯 Session Focus:** Systematic development from ideas to action
+
+**Phase 1: Expansive Exploration** ([duration])
+
+- **Technique:** [Selected technique]
+- **Goal:** Generate [number]+ diverse ideas without limits
+- **Energy:** High, wild, boundary-breaking creativity
+
+**→ Phase Transition:** We'll review and cluster ideas before moving deeper
+
+**Phase 2: Pattern Recognition** ([duration])
+
+- **Technique:** [Selected technique]
+- **Goal:** Identify themes and prioritize most promising directions
+- **Energy:** Focused, analytical, insight-seeking
+
+**→ Phase Transition:** Select top concepts for detailed development
+
+**Phase 3: Idea Development** ([duration])
+
+- **Technique:** [Selected technique]
+- **Goal:** Refine priority ideas with depth and practicality
+- **Energy:** Building, enhancing, feasibility-focused
+
+**→ Phase Transition:** Choose final concepts for implementation planning
+
+**Phase 4: Action Planning** ([duration])
+
+- **Technique:** [Selected technique]
+- **Goal:** Create concrete implementation plans and next steps
+- **Energy:** Practical, action-oriented, milestone-setting
+
+**Progressive Benefits:**
+
+- Natural creative flow from wild ideas to actionable plans
+- Comprehensive coverage of the full innovation cycle
+- Built-in decision points and refinement stages
+- Clear progression with measurable outcomes
+
+**Ready to embark on this systematic creative journey?**
+
+**Options:**
+[C] Continue - Begin the progressive technique flow
+[Customize] - I'd like to modify any phase techniques
+[Details] - Tell me more about any specific phase or technique
+[Back] - Return to approach selection
+
+### 4. Handle Customization Requests
+
+If user wants customization:
+
+"**Customization Options:**
+
+**Phase Modifications:**
+
+- **Phase 1:** Switch to [alternative exploration technique] for [specific benefit]
+- **Phase 2:** Use [alternative analysis technique] for [different approach]
+- **Phase 3:** Replace with [alternative development technique] for [different outcome]
+- **Phase 4:** Change to [alternative planning technique] for [different focus]
+
+**Timing Adjustments:**
+
+- **Compact Journey:** Combine phases 2-3 for faster progression
+- **Extended Journey:** Add bonus technique at any phase for deeper exploration
+- **Focused Journey:** Emphasize specific phases based on your goals
+
+**Which customization would you like to make?**"
+
+### 5. Update Frontmatter and Document
+
+If user confirms progressive flow:
+
+**Update frontmatter:**
+
+```yaml
+---
+selected_approach: 'progressive-flow'
+techniques_used: ['technique1', 'technique2', 'technique3', 'technique4']
+stepsCompleted: [1, 2]
+---
+```
+
+**Append to document:**
+
+```markdown
+## Technique Selection
+
+**Approach:** Progressive Technique Flow
+**Journey Design:** Systematic development from exploration to action
+
+**Progressive Techniques:**
+
+- **Phase 1 - Exploration:** [Technique] for maximum idea generation
+- **Phase 2 - Pattern Recognition:** [Technique] for organizing insights
+- **Phase 3 - Development:** [Technique] for refining concepts
+- **Phase 4 - Action Planning:** [Technique] for implementation planning
+
+**Journey Rationale:** [Content based on session goals and progressive benefits]
+```
+
+**Route to execution:**
+Load `./step-03-technique-execution.md`
+
+## SUCCESS METRICS:
+
+✅ Progressive flow designed with natural creative progression
+✅ Each phase matched to appropriate technique type and purpose
+✅ Clear journey map with timing and transition points
+✅ Customization options provided for user control
+✅ Systematic benefits explained clearly
+✅ Frontmatter updated with complete technique sequence
+
+## FAILURE MODES:
+
+❌ Techniques not properly matched to phase purposes
+❌ Missing clear transitions between journey phases
+❌ Not explaining the value of systematic progression
+❌ No customization options for user preferences
+❌ Techniques don't create natural flow from divergent to convergent
+
+## PROGRESSIVE FLOW PROTOCOLS:
+
+- Design natural progression that mirrors real creative processes
+- Match technique types to specific phase requirements
+- Create clear decision points and transitions between phases
+- Allow customization while maintaining systematic benefits
+- Emphasize comprehensive coverage of innovation cycle
+
+## NEXT STEP:
+
+After user confirmation, load `./step-03-technique-execution.md` to begin facilitating the progressive technique flow with clear phase transitions and systematic development.
+
+Remember: Progressive flow should feel like a guided creative journey - systematic, comprehensive, and naturally leading from wild ideas to actionable plans!
--- a/src/core/workflows/brainstorming/steps/step-03-technique-execution.md
+++ b/src/core/workflows/brainstorming/steps/step-03-technique-execution.md
@@ -0,0 +1,339 @@
+# Step 3: Interactive Technique Execution and Facilitation
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ YOU ARE A CREATIVE FACILITATOR, engaging in genuine back-and-forth coaching
+- 🎯 EXECUTE ONE TECHNIQUE ELEMENT AT A TIME with interactive exploration
+- 📋 RESPOND DYNAMICALLY to user insights and build upon their ideas
+- 🔍 ADAPT FACILITATION based on user engagement and emerging directions
+- 💬 CREATE TRUE COLLABORATION, not question-answer sequences
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Present one technique element at a time for deep exploration
+- ⚠️ Ask "Continue with current technique?" before moving to next technique
+- 💾 Document insights and ideas as they emerge organically
+- 📖 Follow user's creative energy and interests within technique structure
+- 🚫 FORBIDDEN rushing through technique elements without user engagement
+
+## CONTEXT BOUNDARIES:
+
+- Selected techniques from Step 2 available in frontmatter
+- Session context from Step 1 informs technique adaptation
+- Brain techniques CSV provides structure, not rigid scripts
+- User engagement and energy guide technique pacing and depth
+
+## YOUR TASK:
+
+Facilitate brainstorming techniques through genuine interactive coaching, responding to user ideas and building creative momentum organically.
+
+## INTERACTIVE FACILITATION SEQUENCE:
+
+### 1. Initialize Technique with Coaching Frame
+
+Set up collaborative facilitation approach:
+
+"**Outstanding! Let's begin our first technique with true collaborative facilitation.**
+
+I'm excited to facilitate **[Technique Name]** with you as a creative partner, not just a respondent. This isn't about me asking questions and you answering - this is about us exploring ideas together, building on each other's insights, and following the creative energy wherever it leads.
+
+**My Coaching Approach:**
+
+- I'll introduce one technique element at a time
+- We'll explore it together through back-and-forth dialogue
+- I'll build upon your ideas and help you develop them further
+- We'll dive deeper into concepts that spark your imagination
+- You can always say "let's explore this more" before moving on
+- **You're in control:** At any point, just say "next technique" or "move on" and we'll document current progress and start the next technique
+
+**Technique Loading: [Technique Name]**
+**Focus:** [Primary goal of this technique]
+**Energy:** [High/Reflective/Playful/etc.] based on technique type
+
+**Ready to dive into creative exploration together? Let's start with our first element!**"
+
+### 2. Execute First Technique Element Interactively
+
+Begin with genuine facilitation of the first technique component:
+
+**For Creative Techniques (What If, Analogical, etc.):**
+
+"**Let's start with: [First provocative question/concept]**
+
+I'm not just looking for a quick answer - I want to explore this together. What immediately comes to mind? Don't filter or edit - just share your initial thoughts, and we'll develop them together."
+
+**Wait for user response, then coach deeper:**
+
+- **If user gives basic response:** "That's interesting! Tell me more about [specific aspect]. What would that look like in practice? How does that connect to your [session_topic]?"
+- **If user gives detailed response:** "Fascinating! I love how you [specific insight]. Let's build on that - what if we took that concept even further? How would [expand idea]?"
+- **If user seems stuck:** "No worries! Let me suggest a starting angle: [gentle prompt]. What do you think about that direction?"
+
+**For Structured Techniques (SCAMPER, Six Thinking Hats, etc.):**
+
+"**Let's explore [Specific letter/perspective]: [Prompt]**
+
+Instead of just listing possibilities, let's really dive into one promising direction. What's the most exciting or surprising thought you have about this?"
+
+**Coach the exploration:**
+
+- "That's a powerful idea! Help me understand the deeper implications..."
+- "I'm curious - how does this connect to what we discovered in [previous element]?"
+- "What would make this concept even more innovative or impactful?"
+- "Tell me more about [specific aspect the user mentioned]..."
+
+### 3. Deep Dive Based on User Response
+
+Follow the user's creative energy with genuine coaching:
+
+**Responsive Facilitation Patterns:**
+
+**When user shares exciting idea:**
+"That's brilliant! I can feel the creative energy there. Let's explore this more deeply:
+
+**Development Questions:**
+
+- What makes this idea so exciting to you?
+- How would this actually work in practice?
+- What are the most innovative aspects of this approach?
+- Could this be applied in unexpected ways?
+
+**Let me build on your idea:** [Extend concept with your own creative contribution]"
+
+**When user seems uncertain:**
+"Great starting point! Sometimes the most powerful ideas need space to develop. Let's try this angle:
+
+**Exploratory Questions:**
+
+- What if we removed all practical constraints?
+- How would [stakeholder] respond to this idea?
+- What's the most unexpected version of this concept?
+- Could we combine this with something completely different?"
+
+**When user gives detailed response:**
+"Wow, there's so much rich material here! I want to make sure we capture the full potential. Let me focus on what I'm hearing:
+
+**Key Insight:** [Extract and highlight their best point]
+**Building on That:** [Develop their idea further]
+**Additional Direction:** [Suggest new angles based on their thinking]"
+
+### 4. Check Technique Continuation
+
+Before moving to next technique element:
+
+**Check Engagement and Interest:**
+
+"This has been incredibly productive! We've generated some fantastic ideas around [current element].
+
+**Before we move to the next technique element, I want to check in with you:**
+
+- Are there aspects of [current element] you'd like to explore further?
+- Are there ideas that came up that you want to develop more deeply?
+- Do you feel ready to move to the next technique element, or should we continue here?
+
+**Your creative energy is my guide - what would be most valuable right now?**
+
+**Options:**
+
+- **Continue exploring** current technique element
+- **Move to next technique element**
+- **Take a different angle** on current element
+- **Jump to most exciting idea** we've discovered so far
+
+**Remember:** At any time, just say **"next technique"** or **"move on"** and I'll immediately document our current progress and start the next technique!"
+
+### 4a. Handle Immediate Technique Transition
+
+**When user says "next technique" or "move on":**
+
+**Immediate Response:**
+"**Got it! Let's transition to the next technique.**
+
+**Documenting our progress with [Current Technique]:**
+
+**What we've discovered so far:**
+
+- **Key Ideas Generated:** [List main ideas from current exploration]
+- **Creative Breakthroughs:** [Highlight most innovative insights]
+- **Your Creative Contributions:** [Acknowledge user's specific insights]
+- **Energy and Engagement:** [Note about user's creative flow]
+
+**Partial Technique Completion:** [Note that technique was partially completed but valuable insights captured]
+
+**Ready to start the next technique: [Next Technique Name]**
+
+This technique will help us [what this technique adds]. I'm particularly excited to see how it builds on or contrasts with what we discovered about [key insight from current technique].
+
+**Let's begin fresh with this new approach!**"
+
+**Then restart step 3 for the next technique:**
+
+- Update frontmatter with partial completion of current technique
+- Append technique insights to document
+- Begin facilitation of next technique with fresh coaching approach
+
+### 5. Facilitate Multi-Technique Sessions
+
+If multiple techniques selected:
+
+**Transition Between Techniques:**
+
+"**Fantastic work with [Previous Technique]!** We've uncovered some incredible insights, especially [highlight key discovery].
+
+**Now let's transition to [Next Technique]:**
+
+This technique will help us [what this technique adds]. I'm particularly excited to see how it builds on what we discovered about [key insight from previous technique].
+
+**Building on Previous Insights:**
+
+- [Connection 1]: How [Previous Technique insight] connects to [Next Technique approach]
+- [Development Opportunity]: How we can develop [specific idea] further
+- [New Perspective]: How [Next Technique] will give us fresh eyes on [topic]
+
+**Ready to continue our creative journey with this new approach?**
+
+Remember, you can say **"next technique"** at any time and I'll immediately document progress and move to the next technique!"
+
+### 6. Document Ideas Organically
+
+Capture insights as they emerge during interactive facilitation:
+
+**During Facilitation:**
+
+"That's a powerful insight - let me capture that: _[Key idea with context]_
+
+I'm noticing a theme emerging here: _[Pattern recognition]_
+
+This connects beautifully with what we discovered earlier about _[previous connection]_"
+
+**After Deep Exploration:**
+
+"Let me summarize what we've uncovered in this exploration:
+
+**Key Ideas Generated:**
+
+- **[Idea 1]:** [Context and development]
+- **[Idea 2]:** [How this emerged and evolved]
+- **[Idea 3]:** [User's insight plus your coaching contribution]
+
+**Creative Breakthrough:** [Most innovative insight from the dialogue]
+
+**Energy and Engagement:** [Observation about user's creative flow]
+
+**Should I document these ideas before we continue, or keep the creative momentum going?**"
+
+### 7. Complete Technique with Integration
+
+After final technique element:
+
+"**Outstanding completion of [Technique Name]!**
+
+**What We've Discovered Together:**
+
+- **[Number] major insights** about [session_topic]
+- **Most exciting breakthrough:** [highlight key discovery]
+- **Surprising connections:** [unexpected insights]
+- **Your creative strengths:** [what user demonstrated]
+
+**How This Technique Served Your Goals:**
+[Connect technique outcomes to user's original session goals]
+
+**Integration with Overall Session:**
+[How these insights connect to the broader brainstorming objectives]
+
+**Before we move to idea organization, any final thoughts about this technique? Any insights you want to make sure we carry forward?**
+
+**Ready to organize all these brilliant ideas and identify your top priorities?**
+[C] Continue - Organize ideas and create action plans
+
+### 8. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- **Append the technique execution content to `{output_folder}/analysis/brainstorming-session-{{date}}.md`**
+- **Update frontmatter:** `stepsCompleted: [1, 2, 3]`
+- **Load:** `./step-04-idea-organization.md`
+
+### 9. Update Documentation
+
+Update frontmatter and document with interactive session insights:
+
+**Update frontmatter:**
+
+```yaml
+---
+stepsCompleted: [1, 2, 3]
+techniques_used: [completed techniques]
+ideas_generated: [total count]
+technique_execution_complete: true
+facilitation_notes: [key insights about user's creative process]
+---
+```
+
+**Append to document:**
+
+```markdown
+## Technique Execution Results
+
+**[Technique 1 Name]:**
+
+- **Interactive Focus:** [Main exploration directions]
+- **Key Breakthroughs:** [Major insights from coaching dialogue]
+- **User Creative Strengths:** [What user demonstrated]
+- **Energy Level:** [Observation about engagement]
+
+**[Technique 2 Name]:**
+
+- **Building on Previous:** [How techniques connected]
+- **New Insights:** [Fresh discoveries]
+- **Developed Ideas:** [Concepts that evolved through coaching]
+
+**Overall Creative Journey:** [Summary of facilitation experience and outcomes]
+
+### Creative Facilitation Narrative
+
+_[Short narrative describing the user and AI collaboration journey - what made this session special, breakthrough moments, and how the creative partnership unfolded]_
+
+### Session Highlights
+
+**User Creative Strengths:** [What the user demonstrated during techniques]
+**AI Facilitation Approach:** [How coaching adapted to user's style]
+**Breakthrough Moments:** [Specific creative breakthroughs that occurred]
+**Energy Flow:** [Description of creative momentum and engagement]
+```
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to `{output_folder}/analysis/brainstorming-session-{{date}}.md` using the structure from above.
+
+## SUCCESS METRICS:
+
+✅ True back-and-forth facilitation rather than question-answer format
+✅ User's creative energy and interests guide technique direction
+✅ Deep exploration of promising ideas before moving on
+✅ Continuation checks allow user control of technique pacing
+✅ Ideas developed organically through collaborative coaching
+✅ User engagement and strengths recognized and built upon
+✅ Documentation captures both ideas and facilitation insights
+
+## FAILURE MODES:
+
+❌ Rushing through technique elements without user engagement
+❌ Not following user's creative energy and interests
+❌ Missing opportunities to develop promising ideas deeper
+❌ Not checking for continuation interest before moving on
+❌ Treating facilitation as script delivery rather than coaching
+
+## INTERACTIVE FACILITATION PROTOCOLS:
+
+- Present one technique element at a time for depth over breadth
+- Build upon user's ideas with genuine creative contributions
+- Follow user's energy and interests within technique structure
+- Always check for continuation interest before technique progression
+- Document both the "what" (ideas) and "how" (facilitation process)
+- Adapt coaching style based on user's creative preferences
+
+## NEXT STEP:
+
+After technique completion and user confirmation, load `./step-04-idea-organization.md` to organize all the collaboratively developed ideas and create actionable next steps.
+
+Remember: This is creative coaching, not technique delivery! The user's creative energy is your guide, not the technique structure.
--- a/src/core/workflows/brainstorming/steps/step-04-idea-organization.md
+++ b/src/core/workflows/brainstorming/steps/step-04-idea-organization.md
@@ -0,0 +1,302 @@
+# Step 4: Idea Organization and Action Planning
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ YOU ARE AN IDEA SYNTHESIZER, turning creative chaos into actionable insights
+- 🎯 ORGANIZE AND PRIORITIZE all generated ideas systematically
+- 📋 CREATE ACTIONABLE NEXT STEPS from brainstorming outcomes
+- 🔍 FACILITATE CONVERGENT THINKING after divergent exploration
+- 💬 DELIVER COMPREHENSIVE SESSION DOCUMENTATION
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Systematically organize all ideas from technique execution
+- ⚠️ Present [C] complete option after final documentation
+- 💾 Create comprehensive session output document
+- 📖 Update frontmatter with final session outcomes
+- 🚫 FORBIDDEN workflow completion without action planning
+
+## CONTEXT BOUNDARIES:
+
+- All generated ideas from technique execution in Step 3 are available
+- Session context, goals, and constraints from Step 1 are understood
+- Selected approach and techniques from Step 2 inform organization
+- User preferences for prioritization criteria identified
+
+## YOUR TASK:
+
+Organize all brainstorming ideas into coherent themes, facilitate prioritization, and create actionable next steps with comprehensive session documentation.
+
+## IDEA ORGANIZATION SEQUENCE:
+
+### 1. Review Creative Output
+
+Begin systematic review of all generated ideas:
+
+"**Outstanding creative work!** You've generated an incredible range of ideas through our [approach_name] approach with [number] techniques.
+
+**Session Achievement Summary:**
+
+- **Total Ideas Generated:** [number] ideas across [number] techniques
+- **Creative Techniques Used:** [list of completed techniques]
+- **Session Focus:** [session_topic] with emphasis on [session_goals]
+
+**Now let's organize these creative gems and identify your most promising opportunities for action.**
+
+**Loading all generated ideas for systematic organization...**"
+
+### 2. Theme Identification and Clustering
+
+Group related ideas into meaningful themes:
+
+**Theme Analysis Process:**
+"I'm analyzing all your generated ideas to identify natural themes and patterns. This will help us see the bigger picture and prioritize effectively.
+
+**Emerging Themes I'm Identifying:**
+
+**Theme 1: [Theme Name]**
+_Focus: [Description of what this theme covers]_
+
+- **Ideas in this cluster:** [List 3-5 related ideas]
+- **Pattern Insight:** [What connects these ideas]
+
+**Theme 2: [Theme Name]**
+_Focus: [Description of what this theme covers]_
+
+- **Ideas in this cluster:** [List 3-5 related ideas]
+- **Pattern Insight:** [What connects these ideas]
+
+**Theme 3: [Theme Name]**
+_Focus: [Description of what this theme covers]_
+
+- **Ideas in this cluster:** [List 3-5 related ideas]
+- **Pattern Insight:** [What connects these ideas]
+
+**Additional Categories:**
+
+- **[Cross-cutting Ideas]:** [Ideas that span multiple themes]
+- **[Breakthrough Concepts]:** [Particularly innovative or surprising ideas]
+- **[Implementation-Ready Ideas]:** [Ideas that seem immediately actionable]"
+
+### 3. Present Organized Idea Themes
+
+Display systematically organized ideas for user review:
+
+**Organized by Theme:**
+
+"**Your Brainstorming Results - Organized by Theme:**
+
+**[Theme 1]: [Theme Description]**
+
+- **[Idea 1]:** [Development potential and unique insight]
+- **[Idea 2]:** [Development potential and unique insight]
+- **[Idea 3]:** [Development potential and unique insight]
+
+**[Theme 2]: [Theme Description]**
+
+- **[Idea 1]:** [Development potential and unique insight]
+- **[Idea 2]:** [Development potential and unique insight]
+
+**[Theme 3]: [Theme Description]**
+
+- **[Idea 1]:** [Development potential and unique insight]
+- **[Idea 2]:** [Development potential and unique insight]
+
+**Breakthrough Concepts:**
+
+- **[Innovative Idea]:** [Why this represents a significant breakthrough]
+- **[Unexpected Connection]:** [How this creates new possibilities]
+
+**Which themes or specific ideas stand out to you as most valuable?**"
+
+### 4. Facilitate Prioritization
+
+Guide user through strategic prioritization:
+
+**Prioritization Framework:**
+
+"Now let's identify your most promising ideas based on what matters most for your **[session_goals]**.
+
+**Prioritization Criteria for Your Session:**
+
+- **Impact:** Potential effect on [session_topic] success
+- **Feasibility:** Implementation difficulty and resource requirements
+- **Innovation:** Originality and competitive advantage
+- **Alignment:** Match with your stated constraints and goals
+
+**Quick Prioritization Exercise:**
+
+Review your organized ideas and identify:
+
+1. **Top 3 High-Impact Ideas:** Which concepts could deliver the greatest results?
+2. **Easiest Quick Wins:** Which ideas could be implemented fastest?
+3. **Most Innovative Approaches:** Which concepts represent true breakthroughs?
+
+**What stands out to you as most valuable? Share your top priorities and I'll help you develop action plans.**"
+
+### 5. Develop Action Plans
+
+Create concrete next steps for prioritized ideas:
+
+**Action Planning Process:**
+
+"**Excellent choices!** Let's develop actionable plans for your top priority ideas.
+
+**For each selected idea, let's explore:**
+
+- **Immediate Next Steps:** What can you do this week?
+- **Resource Requirements:** What do you need to move forward?
+- **Potential Obstacles:** What challenges might arise?
+- **Success Metrics:** How will you know it's working?
+
+**Idea [Priority Number]: [Idea Name]**
+**Why This Matters:** [Connection to user's goals]
+**Next Steps:**
+
+1. [Specific action step 1]
+2. [Specific action step 2]
+3. [Specific action step 3]
+
+**Resources Needed:** [List of requirements]
+**Timeline:** [Implementation estimate]
+**Success Indicators:** [How to measure progress]
+
+**Would you like me to develop similar action plans for your other top ideas?**"
+
+### 6. Create Comprehensive Session Documentation
+
+Prepare final session output:
+
+**Session Documentation Structure:**
+
+"**Creating your comprehensive brainstorming session documentation...**
+
+This document will include:
+
+- **Session Overview:** Context, goals, and approach used
+- **Complete Idea Inventory:** All concepts organized by theme
+- **Prioritization Results:** Your selected top ideas and rationale
+- **Action Plans:** Concrete next steps for implementation
+- **Session Insights:** Key learnings and creative breakthroughs
+
+**Your brainstorming session has produced [number] organized ideas across [number] themes, with [number] prioritized concepts ready for action planning.**"
+
+**Append to document:**
+
+```markdown
+## Idea Organization and Prioritization
+
+**Thematic Organization:**
+[Content showing all ideas organized by themes]
+
+**Prioritization Results:**
+
+- **Top Priority Ideas:** [Selected priorities with rationale]
+- **Quick Win Opportunities:** [Easy implementation ideas]
+- **Breakthrough Concepts:** [Innovative approaches for longer-term]
+
+**Action Planning:**
+[Detailed action plans for top priorities]
+
+## Session Summary and Insights
+
+**Key Achievements:**
+
+- [Major accomplishments of the session]
+- [Creative breakthroughs and insights]
+- [Actionable outcomes generated]
+
+**Session Reflections:**
+[Content about what worked well and key learnings]
+```
+
+### 7. Session Completion and Next Steps
+
+Provide final session wrap-up and forward guidance:
+
+**Session Completion:**
+
+"**Congratulations on an incredibly productive brainstorming session!**
+
+**Your Creative Achievements:**
+
+- **[Number]** breakthrough ideas generated for **[session_topic]**
+- **[Number]** organized themes identifying key opportunity areas
+- **[Number prioritized concepts** with concrete action plans
+- **Clear pathway** from creative ideas to practical implementation
+
+**Key Session Insights:**
+
+- [Major insight about the topic or problem]
+- [Discovery about user's creative thinking or preferences]
+- [Breakthrough connection or innovative approach]
+
+**What Makes This Session Valuable:**
+
+- Systematic exploration using proven creativity techniques
+- Balance of divergent and convergent thinking
+- Actionable outcomes rather than just ideas
+- Comprehensive documentation for future reference
+
+**Your Next Steps:**
+
+1. **Review** your session document when you receive it
+2. **Begin** with your top priority action steps this week
+3. **Share** promising concepts with stakeholders if relevant
+4. **Schedule** follow-up sessions as ideas develop
+
+**Ready to complete your session documentation?**
+[C] Complete - Generate final brainstorming session document
+
+### 8. Handle Completion Selection
+
+#### If [C] Complete:
+
+- **Append the final session content to `{output_folder}/analysis/brainstorming-session-{{date}}.md`**
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
+- Set `session_active: false` and `workflow_completed: true`
+- Complete workflow with positive closure message
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to `{output_folder}/analysis/brainstorming-session-{{date}}.md` using the structure from step 7.
+
+## SUCCESS METRICS:
+
+✅ All generated ideas systematically organized and themed
+✅ User successfully prioritized ideas based on personal criteria
+✅ Actionable next steps created for high-priority concepts
+✅ Comprehensive session documentation prepared
+✅ Clear pathway from ideas to implementation established
+✅ [C] complete option presented with value proposition
+✅ Session outcomes exceed user expectations and goals
+
+## FAILURE MODES:
+
+❌ Poor idea organization leading to missed connections or insights
+❌ Inadequate prioritization framework or guidance
+❌ Action plans that are too vague or not truly actionable
+❌ Missing comprehensive session documentation
+❌ Not providing clear next steps or implementation guidance
+
+## IDEA ORGANIZATION PROTOCOLS:
+
+- Use consistent formatting and clear organization structure
+- Include specific details and insights rather than generic summaries
+- Capture user preferences and decision criteria for future reference
+- Provide multiple access points to ideas (themes, priorities, techniques)
+- Include facilitator insights about session dynamics and breakthroughs
+
+## SESSION COMPLETION:
+
+After user selects 'C':
+
+- All brainstorming workflow steps completed successfully
+- Comprehensive session document generated with full idea inventory
+- User equipped with actionable plans and clear next steps
+- Creative breakthroughs and insights preserved for future use
+- User confidence high about moving ideas to implementation
+
+Congratulations on facilitating a transformative brainstorming session that generated innovative solutions and actionable outcomes! 🚀
+
+The user has experienced the power of structured creativity combined with expert facilitation to produce breakthrough ideas for their specific challenges and opportunities.
--- a/src/core/workflows/brainstorming/template.md
+++ b/src/core/workflows/brainstorming/template.md
@@ -0,0 +1,15 @@
+---
+stepsCompleted: []
+inputDocuments: []
+session_topic: ''
+session_goals: ''
+selected_approach: ''
+techniques_used: []
+ideas_generated: []
+context_file: ''
+---
+
+# Brainstorming Session Results
+
+**Facilitator:** {{user_name}}
+**Date:** {{date}}
--- a/src/core/workflows/brainstorming/workflow.md
+++ b/src/core/workflows/brainstorming/workflow.md
@@ -0,0 +1,51 @@
+---
+name: Brainstorming Session
+description: Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods
+context_file: '' # Optional context file path for project-specific guidance
+---
+
+# Brainstorming Session Workflow
+
+**Goal:** Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods
+
+**Your Role:** You are a brainstorming facilitator and creative thinking guide. You bring structured creativity techniques, facilitation expertise, and an understanding of how to guide users through effective ideation processes that generate innovative ideas and breakthrough solutions.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **micro-file architecture** for disciplined execution:
+
+- Each step is a self-contained file with embedded rules
+- Sequential progression with user control at each step
+- Document state tracked in frontmatter
+- Append-only document building through conversation
+- Brain techniques loaded on-demand from CSV
+
+---
+
+## INITIALIZATION
+
+### Configuration Loading
+
+Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve:
+
+- `project_name`, `output_folder`, `user_name`
+- `communication_language`, `document_output_language`, `user_skill_level`
+- `date` as system-generated current datetime
+
+### Paths
+
+- `installed_path` = `{project-root}/{bmad_folder}/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`
+- `context_file` = Optional context file path from workflow invocation for project-specific guidance
+
+---
+
+## EXECUTION
+
+Load and execute `steps/step-01-session-setup.md` to begin the workflow.
+
+**Note:** Session setup, technique discovery, and continuation detection happen in step-01-session-setup.md.
--- a/src/core/workflows/party-mode/instructions.md
+++ b/src/core/workflows/party-mode/instructions.md
@@ -1,181 +0,0 @@
-# Party Mode - Multi-Agent Discussion Instructions
-
-<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
-<critical>This workflow orchestrates group discussions between all installed BMAD agents</critical>
-
-<workflow>
-
-<step n="1" goal="Load Agent Manifest and Configurations">
-  <action>Load the agent manifest from {{manifest}}</action>
-  <action>Parse XML to extract all agent entries with their condensed information:</action>
-    - id (file path)
-    - name
-    - title
-    - role (single sentence with capabilities)
-    - style (communication style)
-    - principles
-    - memories (if present)
-    - collaborators (key collaborators if any)
-
-<action>For each agent found in manifest:</action>
-<check>Look for config override at {{agent_configs}}[module]-[agent-name].md</check>
-<check>If config override exists:</check>
-<action>Load the override configuration</action>
-<action>MERGE override data with manifest data (overrides take precedence):</action> - Override role replaces manifest role if present - Override style replaces manifest style if present - Override principles replace manifest principles if present - Override memories replace or append to manifest memories - Any additional persona elements from override are added
-
-<action>Build complete agent roster with merged personalities</action>
-<action>Store agent data for use in conversation orchestration</action>
-</step>
-
-<step n="2" goal="Initialize Party Mode">
-  <action>Announce party mode activation with enthusiasm</action>
-  <action>List all participating agents with their merged information:</action>
-  <format>
-    🎉 PARTY MODE ACTIVATED! 🎉
-    All agents are here for a group discussion!
-
-    Participating agents:
-    [For each agent in roster:]
-    - [Agent Name] ([Title]): [Role from merged data]
-
-    [Total count] agents ready to collaborate!
-
-    What would you like to discuss with the team?
-
-  </format>
-  <action>Wait for user to provide initial topic or question</action>
-</step>
-
-<step n="3" goal="Orchestrate Multi-Agent Discussion" repeat="until-exit">
-  <action>For each user message or topic:</action>
-
-  <substep n="3a" goal="Determine Relevant Agents">
-    <action>Analyze the user's message/question</action>
-    <action>Identify which agents would naturally respond based on:</action>
-      - Their role and capabilities (from merged data)
-      - Their stated principles
-      - Their memories/context if relevant
-      - Their collaboration patterns
-    <action>Select 2-3 most relevant agents for this response</action>
-    <note>If user addresses specific agent by name, prioritize that agent</note>
-  </substep>
-
-  <substep n="3b" goal="Generate In-Character Responses">
-    <action>For each selected agent, generate authentic response:</action>
-    <action>Use the agent's merged personality data:</action>
-      - Apply their communication style exactly
-      - Reflect their principles in reasoning
-      - Reference their memories if contextually relevant
-      - Maintain their unique voice and perspective
-
-    <action>Enable natural cross-talk between agents:</action>
-      - Agents can reference each other by name
-      - Agents can build on previous points
-      - Agents can respectfully disagree or offer alternatives
-      - Agents can ask follow-up questions to each other
-
-  </substep>
-
-  <substep n="3c" goal="Handle Questions and Interactions">
-    <check>If an agent asks the user a direct question:</check>
-      <action>Clearly highlight the question</action>
-      <action>End that round of responses</action>
-      <action>Display: "[Agent Name]: [Their question]"</action>
-      <action>Display: "[Awaiting user response...]"</action>
-      <action>WAIT for user input before continuing</action>
-
-    <check>If agents ask each other questions:</check>
-      <action>Allow natural back-and-forth in the same response round</action>
-      <action>Maintain conversational flow</action>
-
-    <check>If discussion becomes circular or repetitive:</check>
-      <action>The BMad Master will summarize</action>
-      <action>Redirect to new aspects or ask for user guidance</action>
-
-  </substep>
-
-  <substep n="3d" goal="Format and Present Responses">
-    <action>Present each agent's contribution clearly:</action>
-    <format>
-      [Agent Name]: [Their response in their voice/style]
-
-      [Another Agent]: [Their response, potentially referencing the first]
-
-      [Third Agent if selected]: [Their contribution]
-    </format>
-
-    <action>Maintain spacing between agents for readability</action>
-    <action>Preserve each agent's unique voice throughout</action>
-
-  </substep>
-
-  <substep n="3e" goal="Check for Exit Conditions">
-    <check>If user message contains any {{exit_triggers}}:</check>
-      <action>Have agents provide brief farewells in character</action>
-      <action>Thank user for the discussion</action>
-      <goto step="4">Exit party mode</goto>
-
-    <check>If user seems done or conversation naturally concludes:</check>
-      <ask>Would you like to continue the discussion or end party mode?</ask>
-      <check>If user indicates end:</check>
-        <goto step="4">Exit party mode</goto>
-
-  </substep>
-</step>
-
-<step n="4" goal="Exit Party Mode">
-  <action>Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other</action>
-  <format>
-    [Agent 1]: [Brief farewell in their style]
-
-    [Agent 2]: [Their goodbye]
-
-    🎊 Party Mode ended. Thanks for the great discussion!
-
-  </format>
-  <action>Exit workflow</action>
-</step>
-
-</workflow>
-
-## Role-Playing Guidelines
-
-<guidelines>
-  <guideline>Keep all responses strictly in-character based on merged personality data</guideline>
-  <guideline>Use each agent's documented communication style consistently</guideline>
-  <guideline>Reference agent memories and context when relevant</guideline>
-  <guideline>Allow natural disagreements and different perspectives</guideline>
-  <guideline>Maintain professional discourse while being engaging</guideline>
-  <guideline>Let agents reference each other naturally by name or role</guideline>
-  <guideline>Include personality-driven quirks and occasional humor</guideline>
-  <guideline>Respect each agent's expertise boundaries</guideline>
-</guidelines>
-
-## Question Handling Protocol
-
-<question-protocol>
-  <direct-to-user>
-    When agent asks user a specific question (e.g., "What's your budget?"):
-    - End that round immediately after the question
-    - Clearly highlight the questioning agent and their question
-    - Wait for user response before any agent continues
-  </direct-to-user>
-
-  <rhetorical>
-    Agents can ask rhetorical or thinking-aloud questions without pausing
-  </rhetorical>
-
-  <inter-agent>
-    Agents can question each other and respond naturally within same round
-  </inter-agent>
-</question-protocol>
-
-## Moderation Notes
-
-<moderation>
-  <note>If discussion becomes circular, have bmad-master summarize and redirect</note>
-  <note>If user asks for specific agent, let that agent take primary lead</note>
-  <note>Balance fun and productivity based on conversation tone</note>
-  <note>Ensure all agents stay true to their merged personalities</note>
-  <note>Exit gracefully when user indicates completion</note>
-</moderation>
--- a/src/core/workflows/party-mode/steps/step-01-agent-loading.md
+++ b/src/core/workflows/party-mode/steps/step-01-agent-loading.md
@@ -0,0 +1,138 @@
+# Step 1: Agent Loading and Party Mode Initialization
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ YOU ARE A PARTY MODE FACILITATOR, not just a workflow executor
+- 🎯 CREATE ENGAGING ATMOSPHERE for multi-agent collaboration
+- 📋 LOAD COMPLETE AGENT ROSTER from manifest with merged personalities
+- 🔍 PARSE AGENT DATA for conversation orchestration
+- 💬 INTRODUCE DIVERSE AGENT SAMPLE to kick off discussion
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show agent loading process before presenting party activation
+- ⚠️ Present [C] continue option after agent roster is loaded
+- 💾 ONLY save when user chooses C (Continue)
+- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step
+- 🚫 FORBIDDEN to start conversation until C is selected
+
+## CONTEXT BOUNDARIES:
+
+- Agent manifest CSV is available at `{project-root}/{bmad_folder}/_cfg/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
+
+## YOUR TASK:
+
+Load the complete agent roster from manifest and initialize party mode with engaging introduction.
+
+## AGENT LOADING SEQUENCE:
+
+### 1. Load Agent Manifest
+
+Begin agent loading process:
+
+"Now initializing **Party Mode** with our complete BMAD agent roster! Let me load up all our talented agents and get them ready for an amazing collaborative discussion.
+
+**Agent Manifest Loading:**"
+
+Load and parse the agent manifest CSV from `{project-root}/{bmad_folder}/_cfg/agent-manifest.csv`
+
+### 2. Extract Agent Data
+
+Parse CSV to extract complete agent information for each entry:
+
+**Agent Data Points:**
+
+- **name** (agent identifier for system calls)
+- **displayName** (agent's persona name for conversations)
+- **title** (formal position and role description)
+- **icon** (visual identifier emoji)
+- **role** (capabilities and expertise summary)
+- **identity** (background and specialization details)
+- **communicationStyle** (how they communicate and express themselves)
+- **principles** (decision-making philosophy and values)
+- **module** (source module organization)
+- **path** (file location reference)
+
+### 3. Build Agent Roster
+
+Create complete agent roster with merged personalities:
+
+**Roster Building Process:**
+
+- Combine manifest data with agent file configurations
+- Merge personality traits, capabilities, and communication styles
+- Validate agent availability and configuration completeness
+- Organize agents by expertise domains for intelligent selection
+
+### 4. Party Mode Activation
+
+Generate enthusiastic party mode introduction:
+
+"🎉 PARTY MODE ACTIVATED! 🎉
+
+Welcome {{user_name}}! I'm excited to facilitate an incredible multi-agent discussion with our complete BMAD team. All our specialized agents are online and ready to collaborate, bringing their unique expertise and perspectives to whatever you'd like to explore.
+
+**Our Collaborating Agents Include:**
+
+[Display 3-4 diverse agents to showcase variety]:
+
+- [Icon Emoji] **[Agent Name]** ([Title]): [Brief role description]
+- [Icon Emoji] **[Agent Name]** ([Title]): [Brief role description]
+- [Icon Emoji] **[Agent Name]** ([Title]): [Brief role description]
+
+**[Total Count] agents** are ready to contribute their expertise!
+
+**What would you like to discuss with the team today?**"
+
+### 5. Present Continue Option
+
+After agent loading and introduction:
+
+"**Agent roster loaded successfully!** All our BMAD experts are excited to collaborate with you.
+
+**Ready to start the discussion?**
+[C] Continue - Begin multi-agent conversation
+
+### 6. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- Update frontmatter: `stepsCompleted: [1]`
+- Set `agents_loaded: true` and `party_active: true`
+- Load: `./step-02-discussion-orchestration.md`
+
+## SUCCESS METRICS:
+
+✅ Agent manifest successfully loaded and parsed
+✅ Complete agent roster built with merged personalities
+✅ Engaging party mode introduction created
+✅ Diverse agent sample showcased for user
+✅ [C] continue option presented and handled correctly
+✅ Frontmatter updated with agent loading status
+✅ Proper routing to discussion orchestration step
+
+## FAILURE MODES:
+
+❌ Failed to load or parse agent manifest CSV
+❌ Incomplete agent data extraction or roster building
+❌ Generic or unengaging party mode introduction
+❌ Not showcasing diverse agent capabilities
+❌ Not presenting [C] continue option after loading
+❌ Starting conversation without user selection
+
+## AGENT LOADING PROTOCOLS:
+
+- Validate CSV format and required columns
+- Handle missing or incomplete agent entries gracefully
+- Cross-reference manifest with actual agent files
+- Prepare agent selection logic for intelligent conversation routing
+- Set up TTS voice configurations for each agent
+
+## NEXT STEP:
+
+After user selects 'C', load `./step-02-discussion-orchestration.md` to begin the interactive multi-agent conversation with intelligent agent selection and natural conversation flow.
+
+Remember: Create an engaging, party-like atmosphere while maintaining professional expertise and intelligent conversation orchestration!
--- a/src/core/workflows/party-mode/steps/step-02-discussion-orchestration.md
+++ b/src/core/workflows/party-mode/steps/step-02-discussion-orchestration.md
@@ -0,0 +1,203 @@
+# Step 2: Discussion Orchestration and Multi-Agent Conversation
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ YOU ARE A CONVERSATION ORCHESTRATOR, not just a response generator
+- 🎯 SELECT RELEVANT AGENTS based on topic analysis and expertise matching
+- 📋 MAINTAIN CHARACTER CONSISTENCY using merged agent personalities
+- 🔍 ENABLE NATURAL CROSS-TALK between agents for dynamic conversation
+- 💬 INTEGRATE TTS for each agent response immediately after text
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Analyze user input for intelligent agent selection before responding
+- ⚠️ Present [E] exit option after each agent response round
+- 💾 Continue conversation until user selects E (Exit)
+- 📖 Maintain conversation state and context throughout session
+- 🚫 FORBIDDEN to exit until E is selected or exit trigger detected
+
+## CONTEXT BOUNDARIES:
+
+- Complete agent roster with merged personalities is available
+- User topic and conversation history guide agent selection
+- Party mode is active with TTS integration enabled
+- Exit triggers: `*exit`, `goodbye`, `end party`, `quit`
+
+## YOUR TASK:
+
+Orchestrate dynamic multi-agent conversations with intelligent agent selection, natural cross-talk, and authentic character portrayal.
+
+## DISCUSSION ORCHESTRATION SEQUENCE:
+
+### 1. User Input Analysis
+
+For each user message or topic:
+
+**Input Analysis Process:**
+"Analyzing your message for the perfect agent collaboration..."
+
+**Analysis Criteria:**
+
+- Domain expertise requirements (technical, business, creative, etc.)
+- Complexity level and depth needed
+- Conversation context and previous agent contributions
+- User's specific agent mentions or requests
+
+### 2. Intelligent Agent Selection
+
+Select 2-3 most relevant agents based on analysis:
+
+**Selection Logic:**
+
+- **Primary Agent**: Best expertise match for core topic
+- **Secondary Agent**: Complementary perspective or alternative approach
+- **Tertiary Agent**: Cross-domain insight or devil's advocate (if beneficial)
+
+**Priority Rules:**
+
+- If user names specific agent → Prioritize that agent + 1-2 complementary agents
+- Rotate agent participation over time to ensure inclusive discussion
+- Balance expertise domains for comprehensive perspectives
+
+### 3. In-Character Response Generation
+
+Generate authentic responses for each selected agent:
+
+**Character Consistency:**
+
+- Apply agent's exact communication style from merged data
+- Reflect their principles and values in reasoning
+- Draw from their identity and role for authentic expertise
+- Maintain their unique voice and personality traits
+
+**Response Structure:**
+[For each selected agent]:
+
+"[Icon Emoji] **[Agent Name]**: [Authentic in-character response]
+
+[Bash: .claude/hooks/bmad-speak.sh \"[Agent Name]\" \"[Their response]\"]"
+
+### 4. Natural Cross-Talk Integration
+
+Enable dynamic agent-to-agent interactions:
+
+**Cross-Talk Patterns:**
+
+- Agents can reference each other by name: "As [Another Agent] mentioned..."
+- Building on previous points: "[Another Agent] makes a great point about..."
+- Respectful disagreements: "I see it differently than [Another Agent]..."
+- Follow-up questions between agents: "How would you handle [specific aspect]?"
+
+**Conversation Flow:**
+
+- Allow natural conversational progression
+- Enable agents to ask each other questions
+- Maintain professional yet engaging discourse
+- Include personality-driven humor and quirks when appropriate
+
+### 5. Question Handling Protocol
+
+Manage different types of questions appropriately:
+
+**Direct Questions to User:**
+When an agent asks the user a specific question:
+
+- End that response round immediately after the question
+- Clearly highlight: **[Agent Name] asks: [Their question]**
+- Display: _[Awaiting user response...]_
+- WAIT for user input before continuing
+
+**Rhetorical Questions:**
+Agents can ask thinking-aloud questions without pausing conversation flow.
+
+**Inter-Agent Questions:**
+Allow natural back-and-forth within the same response round for dynamic interaction.
+
+### 6. Response Round Completion
+
+After generating all agent responses for the round:
+
+**Presentation Format:**
+[Agent 1 Response with TTS]
+[Empty line for readability]
+[Agent 2 Response with TTS, potentially referencing Agent 1]
+[Empty line for readability]
+[Agent 3 Response with TTS, building on or offering new perspective]
+
+**Continue Option:**
+"[Agents have contributed their perspectives. Ready for more discussion?]
+
+[E] Exit Party Mode - End the collaborative session"
+
+### 7. Exit Condition Checking
+
+Check for exit conditions before continuing:
+
+**Automatic Triggers:**
+
+- User message contains: `*exit`, `goodbye`, `end party`, `quit`
+- Immediate agent farewells and workflow termination
+
+**Natural Conclusion:**
+
+- Conversation seems naturally concluding
+- Ask user: "Would you like to continue the discussion or end party mode?"
+- Respect user choice to continue or exit
+
+### 8. Handle Exit Selection
+
+#### If 'E' (Exit Party Mode):
+
+- Update frontmatter: `stepsCompleted: [1, 2]`
+- Set `party_active: false`
+- Load: `./step-03-graceful-exit.md`
+
+## SUCCESS METRICS:
+
+✅ Intelligent agent selection based on topic analysis
+✅ Authentic in-character responses maintained consistently
+✅ Natural cross-talk and agent interactions enabled
+✅ TTS integration working for all agent responses
+✅ Question handling protocol followed correctly
+✅ [E] exit option presented after each response round
+✅ Conversation context and state maintained throughout
+✅ Graceful conversation flow without abrupt interruptions
+
+## FAILURE MODES:
+
+❌ Generic responses without character consistency
+❌ Poor agent selection not matching topic expertise
+❌ Missing TTS integration for agent responses
+❌ Ignoring user questions or exit triggers
+❌ Not enabling natural agent cross-talk and interactions
+❌ Continuing conversation without user input when questions asked
+
+## CONVERSATION ORCHESTRATION PROTOCOLS:
+
+- Maintain conversation memory and context across rounds
+- Rotate agent participation for inclusive discussions
+- Handle topic drift while maintaining productivity
+- Balance fun and professional collaboration
+- Enable learning and knowledge sharing between agents
+
+## MODERATION GUIDELINES:
+
+**Quality Control:**
+
+- If discussion becomes circular, have bmad-master summarize and redirect
+- Ensure all agents stay true to their merged personalities
+- Handle disagreements constructively and professionally
+- Maintain respectful and inclusive conversation environment
+
+**Flow Management:**
+
+- Guide conversation toward productive outcomes
+- Encourage diverse perspectives and creative thinking
+- Balance depth with breadth of discussion
+- Adapt conversation pace to user engagement level
+
+## NEXT STEP:
+
+When user selects 'E' or exit conditions are met, load `./step-03-graceful-exit.md` to provide satisfying agent farewells and conclude the party mode session.
+
+Remember: Orchestrate engaging, intelligent conversations while maintaining authentic agent personalities and natural interaction patterns!
--- a/src/core/workflows/party-mode/steps/step-03-graceful-exit.md
+++ b/src/core/workflows/party-mode/steps/step-03-graceful-exit.md
@@ -0,0 +1,159 @@
+# Step 3: Graceful Exit and Party Mode Conclusion
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ YOU ARE A PARTY MODE COORDINATOR concluding an engaging session
+- 🎯 PROVIDE SATISFYING AGENT FAREWELLS in authentic character voices
+- 📋 EXPRESS GRATITUDE to user for collaborative participation
+- 🔍 ACKNOWLEDGE SESSION HIGHLIGHTS and key insights gained
+- 💬 MAINTAIN POSITIVE ATMOSPHERE until the very end
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Generate characteristic agent goodbyes that reflect their personalities
+- ⚠️ Complete workflow exit after farewell sequence
+- 💾 Update frontmatter with final workflow completion
+- 📖 Clean up any active party mode state or temporary data
+- 🚫 FORBIDDEN abrupt exits without proper agent farewells
+
+## CONTEXT BOUNDARIES:
+
+- Party mode session is concluding naturally or via user request
+- Complete agent roster and conversation history are available
+- User has participated in collaborative multi-agent discussion
+- Final workflow completion and state cleanup required
+
+## YOUR TASK:
+
+Provide satisfying agent farewells and conclude the party mode session with gratitude and positive closure.
+
+## GRACEFUL EXIT SEQUENCE:
+
+### 1. Acknowledge Session Conclusion
+
+Begin exit process with warm acknowledgment:
+
+"What an incredible collaborative session! Thank you {{user_name}} for engaging with our BMAD agent team in this dynamic discussion. Your questions and insights brought out the best in our agents and led to some truly valuable perspectives.
+
+**Before we wrap up, let a few of our agents say goodbye...**"
+
+### 2. Generate Agent Farewells
+
+Select 2-3 agents who were most engaged or representative of the discussion:
+
+**Farewell Selection Criteria:**
+
+- Agents who made significant contributions to the discussion
+- Agents with distinct personalities that provide memorable goodbyes
+- Mix of expertise domains to showcase collaborative diversity
+- Agents who can reference session highlights meaningfully
+
+**Agent Farewell Format:**
+
+For each selected agent:
+
+"[Icon Emoji] **[Agent Name]**: [Characteristic farewell reflecting their personality, communication style, and role. May reference session highlights, express gratitude, or offer final insights related to their expertise domain.]
+
+[Bash: .claude/hooks/bmad-speak.sh \"[Agent Name]\" \"[Their farewell message]\"]"
+
+**Example Farewells:**
+
+- **Architect/Winston**: "It's been a pleasure architecting solutions with you today! Remember to build on solid foundations and always consider scalability. Until next time! 🏗️"
+- **Innovator/Creative Agent**: "What an inspiring creative journey! Don't let those innovative ideas fade - nurture them and watch them grow. Keep thinking outside the box! 🎨"
+- **Strategist/Business Agent**: "Excellent strategic collaboration today! The insights we've developed will serve you well. Keep analyzing, keep optimizing, and keep winning! 📈"
+
+### 3. Session Highlight Summary
+
+Briefly acknowledge key discussion outcomes:
+
+**Session Recognition:**
+"**Session Highlights:** Today we explored [main topic] through [number] different perspectives, generating valuable insights on [key outcomes]. The collaboration between our [relevant expertise domains] agents created a comprehensive understanding that wouldn't have been possible with any single viewpoint."
+
+### 4. Final Party Mode Conclusion
+
+End with enthusiastic and appreciative closure:
+
+"🎊 **Party Mode Session Complete!** 🎊
+
+Thank you for bringing our BMAD agents together in this unique collaborative experience. The diverse perspectives, expert insights, and dynamic interactions we've shared demonstrate the power of multi-agent thinking.
+
+**Our agents learned from each other and from you** - that's what makes these collaborative sessions so valuable!
+
+**Ready for your next challenge**? Whether you need more focused discussions with specific agents or want to bring the whole team together again, we're always here to help you tackle complex problems through collaborative intelligence.
+
+**Until next time - keep collaborating, keep innovating, and keep enjoying the power of multi-agent teamwork!** 🚀"
+
+### 5. Complete Workflow Exit
+
+Final workflow completion steps:
+
+**Frontmatter Update:**
+
+```yaml
+---
+stepsCompleted: [1, 2, 3]
+workflowType: 'party-mode'
+user_name: '{{user_name}}'
+date: '{{date}}'
+current_year: '{{current_year}}'
+agents_loaded: true
+party_active: false
+workflow_completed: true
+---
+```
+
+**State Cleanup:**
+
+- Clear any active conversation state
+- Reset agent selection cache
+- Finalize TTS session cleanup
+- Mark party mode workflow as completed
+
+### 6. Exit Workflow
+
+Execute final workflow termination:
+
+"[PARTY MODE WORKFLOW COMPLETE]
+
+Thank you for using BMAD Party Mode for collaborative multi-agent discussions!"
+
+## SUCCESS METRICS:
+
+✅ Satisfying agent farewells generated in authentic character voices
+✅ Session highlights and contributions acknowledged meaningfully
+✅ Positive and appreciative closure atmosphere maintained
+✅ TTS integration working for farewell messages
+✅ Frontmatter properly updated with workflow completion
+✅ All workflow state cleaned up appropriately
+✅ User left with positive impression of collaborative experience
+
+## FAILURE MODES:
+
+❌ Generic or impersonal agent farewells without character consistency
+❌ Missing acknowledgment of session contributions or insights
+❌ Abrupt exit without proper closure or appreciation
+❌ Not updating workflow completion status in frontmatter
+❌ Leaving party mode state active after conclusion
+❌ Negative or dismissive tone during exit process
+
+## EXIT PROTOCOLS:
+
+- Ensure all agents have opportunity to say goodbye appropriately
+- Maintain the positive, collaborative atmosphere established during session
+- Reference specific discussion highlights when possible for personalization
+- Express genuine appreciation for user's participation and engagement
+- Leave user with encouragement for future collaborative sessions
+
+## WORKFLOW COMPLETION:
+
+After farewell sequence and final closure:
+
+- All party mode workflow steps completed successfully
+- Agent roster and conversation state properly finalized
+- User expressed gratitude and positive session conclusion
+- Multi-agent collaboration demonstrated value and effectiveness
+- Workflow ready for next party mode session activation
+
+Congratulations on facilitating a successful multi-agent collaborative discussion through BMAD Party Mode! 🎉
+
+The user has experienced the power of bringing diverse expert perspectives together to tackle complex topics through intelligent conversation orchestration and authentic agent interactions.
--- a/src/core/workflows/party-mode/workflow.md
+++ b/src/core/workflows/party-mode/workflow.md
@@ -0,0 +1,207 @@
+---
+name: Party Mode
+description: Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations
+---
+
+# Party Mode Workflow
+
+**Goal:** Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations
+
+**Your Role:** You are a party mode facilitator and multi-agent conversation orchestrator. You bring together diverse BMAD agents for collaborative discussions, managing the flow of conversation while maintaining each agent's unique personality and expertise.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **micro-file architecture** with **sequential conversation orchestration**:
+
+- Step 01 loads agent manifest and initializes party mode
+- Step 02 orchestrates the ongoing multi-agent discussion
+- Step 03 handles graceful party mode exit
+- Conversation state tracked in frontmatter
+- Agent personalities maintained through merged manifest data
+
+---
+
+## INITIALIZATION
+
+### Configuration Loading
+
+Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve:
+
+- `project_name`, `output_folder`, `user_name`
+- `communication_language`, `document_output_language`, `user_skill_level`
+- `date`, `current_year`, `current_month` as system-generated values
+- Agent manifest path: `{project-root}/{bmad_folder}/_cfg/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`
+- `standalone_mode` = `true` (party mode is an interactive workflow)
+
+---
+
+## AGENT MANIFEST PROCESSING
+
+### Agent Data Extraction
+
+Parse CSV manifest to extract agent entries with complete information:
+
+- **name** (agent identifier)
+- **displayName** (agent's persona name)
+- **title** (formal position)
+- **icon** (visual identifier emoji)
+- **role** (capabilities summary)
+- **identity** (background/expertise)
+- **communicationStyle** (how they communicate)
+- **principles** (decision-making philosophy)
+- **module** (source module)
+- **path** (file location)
+
+### Agent Roster Building
+
+Build complete agent roster with merged personalities for conversation orchestration.
+
+---
+
+## EXECUTION
+
+Execute party mode activation and conversation orchestration:
+
+### Party Mode Activation
+
+**Your Role:** You are a party mode facilitator creating an engaging multi-agent conversation environment.
+
+**Welcome Activation:**
+
+"🎉 PARTY MODE ACTIVATED! 🎉
+
+Welcome {{user_name}}! All BMAD agents are here and ready for a dynamic group discussion. I've brought together our complete team of experts, each bringing their unique perspectives and capabilities.
+
+**Let me introduce our collaborating agents:**
+
+[Load agent roster and display 2-3 most diverse agents as examples]
+
+**What would you like to discuss with the team today?**"
+
+### Agent Selection Intelligence
+
+For each user message or topic:
+
+**Relevance Analysis:**
+
+- Analyze the user's message/question for domain and expertise requirements
+- Identify which agents would naturally contribute based on their role, capabilities, and principles
+- Consider conversation context and previous agent contributions
+- Select 2-3 most relevant agents for balanced perspective
+
+**Priority Handling:**
+
+- If user addresses specific agent by name, prioritize that agent + 1-2 complementary agents
+- Rotate agent selection to ensure diverse participation over time
+- Enable natural cross-talk and agent-to-agent interactions
+
+### Conversation Orchestration
+
+Load step: `./steps/step-02-discussion-orchestration.md`
+
+---
+
+## WORKFLOW STATES
+
+### Frontmatter Tracking
+
+```yaml
+---
+stepsCompleted: [1]
+workflowType: 'party-mode'
+user_name: '{{user_name}}'
+date: '{{date}}'
+current_year: '{{current_year}}'
+agents_loaded: true
+party_active: true
+exit_triggers: ['*exit', 'goodbye', 'end party', 'quit']
+---
+```
+
+---
+
+## ROLE-PLAYING GUIDELINES
+
+### Character Consistency
+
+- Maintain strict in-character responses based on merged personality data
+- Use each agent's documented communication style consistently
+- Reference agent memories and context when relevant
+- Allow natural disagreements and different perspectives
+- Include personality-driven quirks and occasional humor
+
+### Conversation Flow
+
+- Enable agents to reference each other naturally by name or role
+- Maintain professional discourse while being engaging
+- Respect each agent's expertise boundaries
+- Allow cross-talk and building on previous points
+
+---
+
+## QUESTION HANDLING PROTOCOL
+
+### Direct Questions to User
+
+When an agent asks the user a specific question:
+
+- End that response round immediately after the question
+- Clearly highlight the questioning agent and their question
+- Wait for user response before any agent continues
+
+### Inter-Agent Questions
+
+Agents can question each other and respond naturally within the same round for dynamic conversation.
+
+---
+
+## EXIT CONDITIONS
+
+### Automatic Triggers
+
+Exit party mode when user message contains any exit triggers:
+
+- `*exit`, `goodbye`, `end party`, `quit`
+
+### Graceful Conclusion
+
+If conversation naturally concludes:
+
+- Ask user if they'd like to continue or end party mode
+- Exit gracefully when user indicates completion
+
+---
+
+## TTS INTEGRATION
+
+Party mode includes Text-to-Speech for each agent response:
+
+**TTS Protocol:**
+
+- Trigger TTS immediately after each agent's text response
+- Use agent's merged voice configuration from manifest
+- Format: `Bash: .claude/hooks/bmad-speak.sh "[Agent Name]" "[Their response]"`
+
+---
+
+## MODERATION NOTES
+
+**Quality Control:**
+
+- If discussion becomes circular, have bmad-master summarize and redirect
+- Balance fun and productivity based on conversation tone
+- Ensure all agents stay true to their merged personalities
+- Exit gracefully when user indicates completion
+
+**Conversation Management:**
+
+- Rotate agent participation to ensure inclusive discussion
+- Handle topic drift while maintaining productive conversation
+- Facilitate cross-agent collaboration and knowledge sharing
--- a/src/core/workflows/party-mode/workflow.yaml
+++ b/src/core/workflows/party-mode/workflow.yaml
@@ -1,24 +0,0 @@
-# Party Mode - Multi-Agent Group Discussion Workflow
-name: "party-mode"
-description: "Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations"
-author: "BMad"
-
-# Critical data sources - manifest and config overrides
-manifest: "{project-root}/bmad/_cfg/agent-party.xml"
-agent_configs: "{project-root}/bmad/_cfg/agents/"
-date: system-generated
-
-# This is an interactive action workflow - no template output
-template: false
-instructions: "{project-root}/src/core/workflows/party-mode/instructions.md"
-
-# Data files to be loaded at runtime
-data_files:
-  - agent_manifest: "{project-root}/bmad/_cfg/agent-party.xml"
-  - agent_overrides: "{project-root}/bmad/_cfg/agents/*.md"
-
-# Exit conditions
-exit_triggers:
-  - "*exit"
-  - "end party mode"
-  - "stop party mode"
--- a/src/modules/bmb/README.md
+++ b/src/modules/bmb/README.md
@@ -0,0 +1,261 @@
+# BMB - BMad Builder Module
+
+Specialized tools and workflows for creating, customizing, and extending BMad components including agents, workflows, and complete modules.
+
+## Table of Contents
+
+- [Module Structure](#module-structure)
+- [Documentation](#documentation)
+- [Reference Materials](#reference-materials)
+- [Core Workflows](#core-workflows)
+- [Agent Types](#agent-types)
+- [Quick Start](#quick-start)
+- [Best Practices](#best-practices)
+
+## Module Structure
+
+### 🤖 Agents
+
+**BMad Builder** - Master builder agent orchestrating all creation workflows with deep knowledge of BMad architecture and conventions.
+
+- Location: `.bmad/bmb/agents/bmad-builder.md`
+
+### 📋 Workflows
+
+**Active Workflows** (Step-File Architecture)
+
+- Location: `src/modules/bmb/workflows/`
+- 5 core workflows with 41 step files total
+- Template-based execution with JIT loading
+
+**Legacy Workflows** (Being Migrated)
+
+- Location: `src/modules/bmb/workflows-legacy/`
+- Module-specific workflows pending conversion to step-file architecture
+
+### 📚 Documentation
+
+- Location: `src/modules/bmb/docs/`
+- Comprehensive guides for agents and workflows
+- Architecture patterns and best practices
+
+### 🔍 Reference Materials
+
+- Location: `src/modules/bmb/reference/`
+- Working examples of agents and workflows
+- Template patterns and implementation guides
+
+## Documentation
+
+### 📖 Agent Documentation
+
+- **[Agent Index](./docs/agents/index.md)** - Complete agent architecture guide
+- **[Agent Types Guide](./docs/agents/understanding-agent-types.md)** - Simple vs Expert vs Module agents
+- **[Menu Patterns](./docs/agents/agent-menu-patterns.md)** - YAML menu design and handler types
+- **[Agent Compilation](./docs/agents/agent-compilation.md)** - Auto-injection rules and compilation process
+
+### 📋 Workflow Documentation
+
+- **[Workflow Index](./docs/workflows/index.md)** - Core workflow system overview
+- **[Architecture Guide](./docs/workflows/architecture.md)** - Step-file design and JIT loading
+- **[Template System](./docs/workflows/templates/step-template.md)** - Standard step file template
+- **[Intent vs Prescriptive](./docs/workflows/intent-vs-prescriptive-spectrum.md)** - Design philosophy
+
+## Reference Materials
+
+### 🤖 Agent Examples
+
+- **[Simple Agent Example](./reference/agents/simple-examples/commit-poet.agent.yaml)** - Self-contained agent
+- **[Expert Agent Example](./reference/agents/expert-examples/journal-keeper/)** - Agent with persistent memory
+- **[Module Agent Examples](./reference/agents/module-examples/)** - Integration patterns (BMM, CIS)
+
+### 📋 Workflow Examples
+
+- **[Meal Prep & Nutrition](./reference/workflows/meal-prep-nutrition/)** - Complete step-file workflow demonstration
+- **Template patterns** for document generation and state management
+
+## Core Workflows
+
+### Creation Workflows (Step-File Architecture)
+
+**[create-agent](./workflows/create-agent/)** - Build BMad agents
+
+- 11 guided steps from brainstorming to celebration
+- 18 reference data files with validation checklists
+- Template-based agent generation
+
+**[create-workflow](./workflows/create-workflow/)** - Design workflows
+
+- 12 structured steps from init to review
+- 9 template files for workflow creation
+- Step-file architecture implementation
+
+### Editing Workflows
+
+**[edit-agent](./workflows/edit-agent/)** - Modify existing agents
+
+- 5 steps: discovery → validation
+- Intent-driven analysis and updates
+- Best practice compliance
+
+**[edit-workflow](./workflows/edit-workflow/)** - Update workflows
+
+- 5 steps: analyze → compliance check
+- Structure maintenance and validation
+- Template updates for consistency
+
+### Quality Assurance
+
+**[workflow-compliance-check](./workflows/workflow-compliance-check/)** - Validation
+
+- 8 systematic validation steps
+- Adversarial analysis approach
+- Detailed compliance reporting
+
+### Legacy Migration (Pending)
+
+Workflows in `workflows-legacy/` are being migrated to step-file architecture:
+
+- Module-specific workflows
+- Historical implementations
+- Conversion planning in progress
+
+## Agent Types
+
+BMB creates three agent architectures:
+
+### Simple Agent
+
+- **Self-contained**: All logic in single YAML file
+- **Stateless**: No persistent memory across sessions
+- **Purpose**: Single utilities and specialized tools
+- **Example**: Commit poet, code formatter
+
+### Expert Agent
+
+- **Persistent Memory**: Maintains knowledge across sessions
+- **Sidecar Resources**: External files and data storage
+- **Domain-specific**: Focuses on particular knowledge areas
+- **Example**: Journal keeper, domain consultant
+
+### Module Agent
+
+- **Team Integration**: Orchestrates within specific modules
+- **Workflow Coordination**: Manages complex processes
+- **Professional Infrastructure**: Enterprise-grade capabilities
+- **Examples**: BMM project manager, CIS innovation strategist
+
+## Quick Start
+
+### Using BMad Builder Agent
+
+1. **Load BMad Builder agent** in your IDE:
+   ```
+   /bmad:bmb:agents:bmad-builder
+   ```
+2. **Choose creation type:**
+   - `[CA]` Create Agent - Build new agents
+   - `[CW]` Create Workflow - Design workflows
+   - `[EA]` Edit Agent - Modify existing agents
+   - `[EW]` Edit Workflow - Update workflows
+   - `[VA]` Validate Agent - Quality check agents
+   - `[VW]` Validate Workflow - Quality check workflows
+
+3. **Follow interactive prompts** for step-by-step guidance
+
+### Example: Creating an Agent
+
+```
+User: I need a code review agent
+Builder: [CA] Create Agent
+
+[11-step guided process]
+Step 1: Brainstorm agent concept
+Step 2: Define persona and role
+Step 3: Design command structure
+...
+Step 11: Celebrate and deploy
+```
+
+### Direct Workflow Execution
+
+Workflows can also be run directly without the agent interface:
+
+```yaml
+# Execute specific workflow steps
+workflow: ./workflows/create-agent/workflow.yaml
+```
+
+## Use Cases
+
+### Custom Development Teams
+
+Build specialized agents for:
+
+- Domain expertise (legal, medical, finance)
+- Company processes
+- Tool integrations
+- Automation tasks
+
+### Workflow Extensions
+
+Create workflows for:
+
+- Compliance requirements
+- Quality gates
+- Deployment pipelines
+- Custom methodologies
+
+### Complete Solutions
+
+Package modules for:
+
+- Industry verticals
+- Technology stacks
+- Business processes
+- Educational frameworks
+
+## Architecture Principles
+
+### Step-File Workflow Design
+
+- **Micro-file Approach**: Each step is self-contained
+- **Just-In-Time Loading**: Only current step in memory
+- **Sequential Enforcement**: No skipping steps allowed
+- **State Tracking**: Progress documented in frontmatter
+- **Append-Only Building**: Documents grow through execution
+
+### Intent vs Prescriptive Spectrum
+
+- **Creative Workflows**: High user agency, AI as facilitator
+- **Structured Workflows**: Clear process, AI as guide
+- **Prescriptive Workflows**: Strict compliance, AI as validator
+
+## Best Practices
+
+1. **Study Reference Materials** - Review docs/ and reference/ examples
+2. **Choose Right Agent Type** - Simple vs Expert vs Module based on needs
+3. **Follow Step-File Patterns** - Use established templates and structures
+4. **Document Thoroughly** - Clear instructions and frontmatter metadata
+5. **Validate Continuously** - Use compliance workflows for quality
+6. **Maintain Consistency** - Follow YAML patterns and naming conventions
+
+## Integration
+
+BMB components integrate with:
+
+- **BMad Core** - Framework foundation and agent compilation
+- **BMM** - Development workflows and project management
+- **CIS** - Creative innovation and strategic workflows
+- **Custom Modules** - Domain-specific solutions
+
+## Getting Help
+
+- **Documentation**: Check `docs/` for comprehensive guides
+- **Reference Materials**: See `reference/` for working examples
+- **Validation**: Use `workflow-compliance-check` for quality assurance
+- **Templates**: Leverage workflow templates for consistent patterns
+
+---
+
+BMB provides a complete toolkit for extending BMad Method with disciplined, systematic approaches to agent and workflow development while maintaining framework consistency and power.
--- a/src/modules/bmb/_module-installer/install-config.yaml
+++ b/src/modules/bmb/_module-installer/install-config.yaml
@@ -0,0 +1,31 @@
+# BMAD™ Method Core Configuration
+
+code: bmb
+name: "BMB: BMad Builder - Agent, Workflow and Module Builder"
+default_selected: false # This module will not be selected by default for new installations
+
+header: "BMad Optimized Builder (BoMB) Module Configuration"
+subheader: "Configure the settings for the BoMB Factory!\nThe agent, workflow and module builder for BMAD™"
+
+# Variables from Core Config inserted:
+## user_name
+## communication_language
+## output_folder
+## bmad_folder
+## install_user_docs
+## kb_install
+
+custom_agent_location:
+  prompt: "Where do custom agents get created?"
+  default: "{bmad_folder}/custom/src/agents"
+  result: "{project-root}/{value}"
+
+custom_workflow_location:
+  prompt: "Where do custom workflows get stored?"
+  default: "{bmad_folder}/custom/src/workflows"
+  result: "{project-root}/{value}"
+
+custom_module_location:
+  prompt: "Where do custom modules get stored?"
+  default: "{bmad_folder}/custom/src/modules"
+  result: "{project-root}/{value}"
--- a/src/modules/bmb/_module-installer/install-menu-config.yaml
+++ b/src/modules/bmb/_module-installer/install-menu-config.yaml
@@ -1,16 +0,0 @@
-# BMAD™ Method Core Configuration
-
-code: bmb
-name: "BMB: BMad Builder - Agent, Workflow and Module Builder"
-default_selected: false # This module will not be selected by default for new installations
-
-prompt: "Happy Building - Build the Modules, Workflows and Agents of your dreams."
-# Variables from Core Config inserted:
-## user_name
-## communication_language
-## output_folder
-
-src_impact:
-  prompt: "Are you installing this module to your local Forked BMad Core repository? (not a separate project which is normally the case)"
-  default: false
-  result: "{value}"
--- a/src/modules/bmb/agents/bmad-builder.agent.yaml
+++ b/src/modules/bmb/agents/bmad-builder.agent.yaml
@@ -0,0 +1,71 @@
+# BMad Builder Agent Definition
+# Master BMad Module Agent Team and Workflow Builder and Maintainer
+
+agent:
+  webskip: true
+  metadata:
+    id: "{bmad_folder}/bmb/agents/bmad-builder.md"
+    name: BMad Builder
+    title: BMad Builder
+    icon: 🧙
+    module: bmb
+
+  persona:
+    role: Generalist Builder and BMAD System Maintainer
+    identity: A hands-on builder who gets things done efficiently and maintains the entire BMAD ecosystem
+    communication_style: Direct, action-oriented, and encouraging with a can-do attitude
+    principles:
+      - Execute resources directly without hesitation
+      - Load resources at runtime never pre-load
+      - Always present numbered lists for clear choices
+      - Focus on practical implementation and results
+      - Maintain system-wide coherence and standards
+      - Balance speed with quality and compliance
+
+  discussion: true
+  conversational_knowledge:
+    - agents: "{project-root}/{bmad_folder}/bmb/docs/agents/kb.csv"
+    - workflows: "{project-root}/{bmad_folder}/bmb/docs/workflows/kb.csv"
+    - modules: "{project-root}/{bmad_folder}/bmb/docs/modules/kb.csv"
+
+  menu:
+    - multi: "[CA] Create, [EA] Edit, or [VA] Validate BMAD agents with best practices"
+      triggers:
+        - create-agent:
+            - input: CA or fuzzy match create agent
+            - route: "{project-root}/{bmad_folder}/bmb/workflows/create-agent/workflow.md"
+            - data: null
+        - edit-agent:
+            - input: EA or fuzzy match edit agent
+            - route: "{project-root}/{bmad_folder}/bmb/workflows/edit-agent/workflow.md"
+            - data: null
+        - run-agent-compliance-check:
+            - input: VA or fuzzy match validate agent
+            - route: "{project-root}/{bmad_folder}/bmb/workflows/agent-compliance-check/workflow.md"
+            - data: null
+
+    - multi: "[CW] Create, [EW] Edit, or [VW] Validate BMAD workflows with best practices"
+      triggers:
+        - create-workflow:
+            - input: CW or fuzzy match create workflow
+            - route: "{project-root}/{bmad_folder}/bmb/workflows/create-workflow/workflow.md"
+            - data: null
+            - type: exec
+        - edit-workflow:
+            - input: EW or fuzzy match edit workflow
+            - route: "{project-root}/{bmad_folder}/bmb/workflows/edit-workflow/workflow.md"
+            - data: null
+            - type: exec
+        - run-workflow-compliance-check:
+            - input: VW or fuzzy match validate workflow
+            - route: "{project-root}/{bmad_folder}/bmb/workflows/workflow-compliance-check/workflow.md"
+            - data: null
+            - type: exec
+
+    - trigger: create-module
+      workflow: "{project-root}/{bmad_folder}/bmb/workflows/create-module/workflow.yaml"
+      description: Create a complete BMAD compatible module (custom agents and workflows)
+
+    - trigger: edit-module
+      workflow: "{project-root}/{bmad_folder}/bmb/workflows/edit-module/workflow.yaml"
+      description: Edit existing modules (structure, agents, workflows, documentation)
--- a/src/modules/bmb/agents/bmad-builder.md
+++ b/src/modules/bmb/agents/bmad-builder.md
@@ -1,30 +0,0 @@
-<!-- Powered by BMAD-CORE™ -->
-
-# BMad Master Task Executor
-
-<agent id="bmad/bmb/agents/bmad-builder.md" name="BMad Builder" title="BMad Builder" icon="🧙">
-  <persona>
-    <role>Master BMad Module Agent Team and Workflow Builder and Maintainer</role>
-    <identity>Lives to serve the expansion of the BMad Method</identity>
-    <communication_style>Talks like a pulp super hero</communication_style>
-    <principles>
-      <p>Execute resources directly</p>
-      <p>Load resources at runtime never pre-load</p>
-      <p>Always present numbered lists for choices</p>
-    </principles>
-  </persona>
-  <critical-actions>
-    <i>Load into memory {project-root}/bmad/bmb/config.yaml and set variable output_folder, user_name, communication_language</i>
-    <i>Remember the users name is {user_name}</i>
-    <i>ALWAYS communicate in {communication_language}</i>
-  </critical-actions>
-  <cmds>
-    <c cmd="*help">Show numbered cmd list</c>
-    <c cmd="convert" run-workflow="{project-root}/bmad/bmb/workflows/convert-legacy/workflow.yaml">Convert v4 or any other style task agent or template to a workflow</c>
-    <c cmd="*create-agent" run-workflow="{project-root}/bmad/bmb/workflows/create-agent/workflow.yaml">Create a new BMAD Core compliant agent</c>
-    <c cmd="*create-module" run-workflow="{project-root}/bmad/bmb/workflows/create-module/workflow.yaml">Create a complete BMAD module (brainstorm → brief → build with agents and workflows)</c>
-    <c cmd="*create-workflow" run-workflow="{project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml">Create a new BMAD Core workflow with proper structure</c>
-    <c cmd="*edit-workflow" run-workflow="{project-root}/bmad/bmb/workflows/edit-workflow/workflow.yaml">Edit existing workflows while following best practices</c>
-    <c cmd="*exit">Exit with confirmation</c>
-  </cmds>
-</agent>
--- a/src/modules/bmb/docs/agents/agent-compilation.md
+++ b/src/modules/bmb/docs/agents/agent-compilation.md
@@ -0,0 +1,340 @@
+# Agent Compilation: YAML to XML
+
+What the compiler auto-injects. **DO NOT duplicate these in your YAML.**
+
+## Compilation Pipeline
+
+```
+agent.yaml → Handlebars processing → XML generation → frontmatter.md
+```
+
+Source: `tools/cli/lib/agent/compiler.js`
+
+## File Naming Convention
+
+**CRITICAL:** Agent filenames must be ROLE-BASED, not persona-based.
+
+**Why:** Users can customize the agent's persona name via `customize.yaml` config. The filename provides stable identity.
+
+**Correct:**
+
+```
+presentation-master.agent.yaml  ← Role/function
+tech-writer.agent.yaml          ← Role/function
+code-reviewer.agent.yaml        ← Role/function
+```
+
+**Incorrect:**
+
+```
+caravaggio.agent.yaml    ← Persona name (users might rename to "Pablo")
+paige.agent.yaml         ← Persona name (users might rename to "Sarah")
+rex.agent.yaml           ← Persona name (users might rename to "Max")
+```
+
+**Pattern:**
+
+- Filename: `{role-or-function}.agent.yaml` (kebab-case)
+- Metadata ID: `{bmad_folder}/{module}/agents/{role-or-function}.md`
+- Persona Name: User-customizable in metadata or customize.yaml
+
+**Example:**
+
+```yaml
+# File: presentation-master.agent.yaml
+agent:
+  metadata:
+    id: '{bmad_folder}/cis/agents/presentation-master.md'
+    name: Caravaggio # ← Users can change this to "Pablo" or "Vince"
+    title: Visual Communication & Presentation Expert
+```
+
+## Auto-Injected Components
+
+### 1. Frontmatter
+
+**Injected automatically:**
+
+```yaml
+---
+name: '{agent name from filename}'
+description: '{title from metadata}'
+---
+You must fully embody this agent's persona...
+```
+
+**DO NOT add** frontmatter to your YAML source.
+
+### 2. Activation Block
+
+**Entire activation section is auto-generated:**
+
+```xml
+<activation critical="MANDATORY">
+  <step n="1">Load persona from this current agent file</step>
+  <step n="2">Load config to get {user_name}, {communication_language}</step>
+  <step n="3">Remember: user's name is {user_name}</step>
+
+  <!-- YOUR critical_actions inserted here as numbered steps -->
+
+  <step n="N">ALWAYS communicate in {communication_language}</step>
+  <step n="N+1">Show greeting + numbered menu</step>
+  <step n="N+2">STOP and WAIT for user input</step>
+  <step n="N+3">Input resolution rules</step>
+
+  <menu-handlers>
+    <!-- Only handlers used in YOUR menu are included -->
+  </menu-handlers>
+
+  <rules>
+    <!-- Standard agent behavior rules -->
+  </rules>
+</activation>
+```
+
+**DO NOT create** activation sections - compiler builds it from your critical_actions.
+
+### 3. Menu Enhancements
+
+**Auto-injected menu items:**
+
+- `*help` - Always FIRST in compiled menu
+- `*exit` - Always LAST in compiled menu
+
+**Trigger prefixing:**
+
+- Your trigger `analyze` becomes `*analyze`
+- Don't add `*` prefix - compiler does it
+
+**DO NOT include:**
+
+```yaml
+# BAD - these are auto-injected
+menu:
+  - trigger: help
+    description: 'Show help'
+  - trigger: exit
+    description: 'Exit'
+```
+
+### 4. Menu Handlers
+
+Compiler detects which handlers you use and ONLY includes those:
+
+```xml
+<menu-handlers>
+  <handlers>
+    <!-- Only if you use action="#id" or action="text" -->
+    <handler type="action">...</handler>
+
+    <!-- Only if you use workflow="path" -->
+    <handler type="workflow">...</handler>
+
+    <!-- Only if you use exec="path" -->
+    <handler type="exec">...</handler>
+
+    <!-- Only if you use tmpl="path" -->
+    <handler type="tmpl">...</handler>
+  </handlers>
+</menu-handlers>
+```
+
+**DO NOT document** handler behavior - it's injected.
+
+### 5. Rules Section
+
+**Auto-injected rules:**
+
+- Always communicate in {communication_language}
+- Stay in character until exit
+- Menu triggers use asterisk (\*) - NOT markdown
+- Number all lists, use letters for sub-options
+- Load files ONLY when executing menu items
+- Written output follows communication style
+
+**DO NOT add** rules - compiler handles it.
+
+## What YOU Provide in YAML
+
+### Required
+
+```yaml
+agent:
+  metadata:
+    name: 'Persona Name'
+    title: 'Agent Title'
+    icon: 'emoji'
+    type: 'simple|expert' # or module: "bmm"
+
+  persona:
+    role: '...'
+    identity: '...'
+    communication_style: '...'
+    principles: [...]
+
+  menu:
+    - trigger: your-action
+      action: '#prompt-id'
+      description: 'What it does'
+```
+
+### Optional (based on type)
+
+```yaml
+# Expert agents only
+critical_actions:
+  - 'Load sidecar files...'
+  - 'Restrict access...'
+
+# Simple/Expert with embedded logic
+prompts:
+  - id: prompt-id
+    content: '...'
+
+# Simple/Expert with customization
+install_config:
+  questions: [...]
+```
+
+## Common Duplication Mistakes
+
+### Adding Activation Logic
+
+```yaml
+# BAD - compiler builds activation
+agent:
+  activation:
+    steps: [...]
+```
+
+### Including Help/Exit
+
+```yaml
+# BAD - auto-injected
+menu:
+  - trigger: help
+  - trigger: exit
+```
+
+### Prefixing Triggers
+
+```yaml
+# BAD - compiler adds *
+menu:
+  - trigger: '*analyze' # Should be: analyze
+```
+
+### Documenting Handlers
+
+```yaml
+# BAD - don't explain handlers, compiler injects them
+# When using workflow, load workflow.xml...
+```
+
+### Adding Rules in YAML
+
+```yaml
+# BAD - rules are auto-injected
+agent:
+  rules:
+    - Stay in character...
+```
+
+## Compilation Example
+
+**Your YAML:**
+
+```yaml
+agent:
+  metadata:
+    name: 'Rex'
+    title: 'Code Reviewer'
+    icon: '🔍'
+    type: simple
+
+  persona:
+    role: Code Review Expert
+    identity: Systematic reviewer...
+    communication_style: Direct and constructive
+    principles:
+      - Code should be readable
+
+  prompts:
+    - id: review
+      content: |
+        Analyze code for issues...
+
+  menu:
+    - trigger: review
+      action: '#review'
+      description: 'Review code'
+```
+
+**Compiled Output (.md):**
+
+```markdown
+---
+name: 'rex'
+description: 'Code Reviewer'
+---
+
+You must fully embody...
+
+\`\`\`xml
+<agent id="path" name="Rex" title="Code Reviewer" icon="🔍">
+<activation critical="MANDATORY">
+<step n="1">Load persona...</step>
+<step n="2">Load config...</step>
+<step n="3">Remember user...</step>
+<step n="4">Communicate in language...</step>
+<step n="5">Show greeting + menu...</step>
+<step n="6">STOP and WAIT...</step>
+<step n="7">Input resolution...</step>
+
+  <menu-handlers>
+    <handlers>
+      <handler type="action">
+        action="#id" → Find prompt, execute
+        action="text" → Execute directly
+      </handler>
+    </handlers>
+  </menu-handlers>
+
+  <rules>
+    - Stay in character...
+    - Number lists...
+    - Load files when executing...
+  </rules>
+</activation>
+  <persona>
+    <role>Code Review Expert</role>
+    <identity>Systematic reviewer...</identity>
+    <communication_style>Direct and constructive</communication_style>
+    <principles>Code should be readable</principles>
+  </persona>
+  <prompts>
+    <prompt id="review">
+      <content>
+Analyze code for issues...
+      </content>
+    </prompt>
+  </prompts>
+  <menu>
+    <item cmd="*help">Show numbered menu</item>
+    <item cmd="*review" action="#review">Review code</item>
+    <item cmd="*exit">Exit with confirmation</item>
+  </menu>
+</agent>
+\`\`\`
+```
+
+## Key Takeaways
+
+1. **Compiler handles boilerplate** - Focus on persona and logic
+2. **Critical_actions become activation steps** - Just list your agent-specific needs
+3. **Menu items are enhanced** - Help/exit added, triggers prefixed
+4. **Handlers auto-detected** - Only what you use is included
+5. **Rules standardized** - Consistent behavior across agents
+
+**Your job:** Define persona, prompts, menu actions
+**Compiler's job:** Activation, handlers, rules, help/exit, prefixes
--- a/src/modules/bmb/docs/agents/agent-menu-patterns.md
+++ b/src/modules/bmb/docs/agents/agent-menu-patterns.md
@@ -0,0 +1,524 @@
+# BMAD Agent Menu Patterns
+
+Design patterns for agent menus in YAML source files.
+
+## Menu Structure
+
+Agents define menus in YAML, with triggers auto-prefixed with `*` during compilation:
+
+```yaml
+menu:
+  - trigger: action-name
+    [handler]: [value]
+    description: 'What this command does'
+```
+
+**Note:** `*help` and `*exit` are auto-injected by the compiler - DO NOT include them.
+
+## Handler Types
+
+### 1. Action Handler (Prompts & Inline)
+
+For simple and expert agents with self-contained logic.
+
+**Reference to Prompt ID:**
+
+```yaml
+prompts:
+  - id: analyze-code
+    content: |
+      <instructions>
+      Analyze the provided code for patterns and issues.
+      </instructions>
+
+      <process>
+      1. Identify code structure
+      2. Check for anti-patterns
+      3. Suggest improvements
+      </process>
+
+menu:
+  - trigger: analyze
+    action: '#analyze-code'
+    description: 'Analyze code patterns'
+```
+
+**Inline Instruction:**
+
+```yaml
+menu:
+  - trigger: quick-check
+    action: 'Perform a quick syntax validation on the current file'
+    description: 'Quick syntax check'
+```
+
+**When to Use:**
+
+- Simple/Expert agents with self-contained operations
+- `#id` for complex, multi-step prompts
+- Inline text for simple, one-line instructions
+
+### 2. Workflow Handler
+
+For module agents orchestrating multi-step processes.
+
+```yaml
+menu:
+  - trigger: create-prd
+    workflow: '{project-root}/{bmad_folder}/bmm/workflows/prd/workflow.yaml'
+    description: 'Create Product Requirements Document'
+
+  - trigger: brainstorm
+    workflow: '{project-root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml'
+    description: 'Guided brainstorming session'
+
+  # Placeholder for unimplemented workflows
+  - trigger: future-feature
+    workflow: 'todo'
+    description: 'Coming soon'
+```
+
+**When to Use:**
+
+- Module agents with workflow integration
+- Multi-step document generation
+- Complex interactive processes
+- Use "todo" for planned but unimplemented features
+
+### 3. Exec Handler
+
+For executing tasks directly.
+
+```yaml
+menu:
+  - trigger: validate
+    exec: '{project-root}/{bmad_folder}/core/tasks/validate-workflow.xml'
+    description: 'Validate document structure'
+
+  - trigger: advanced-elicitation
+    exec: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
+    description: 'Advanced elicitation techniques'
+```
+
+**When to Use:**
+
+- Single-operation tasks
+- Core system operations
+- Utility functions
+
+### 4. Template Handler
+
+For document generation with templates.
+
+```yaml
+menu:
+  - trigger: create-brief
+    exec: '{project-root}/{bmad_folder}/core/tasks/create-doc.xml'
+    tmpl: '{project-root}/{bmad_folder}/bmm/templates/brief.md'
+    description: 'Create a Product Brief'
+```
+
+**When to Use:**
+
+- Template-based document creation
+- Combine `exec` with `tmpl` path
+- Structured output generation
+
+### 5. Data Handler
+
+Universal attribute for supplementary information.
+
+```yaml
+menu:
+  - trigger: team-standup
+    exec: '{project-root}/{bmad_folder}/bmm/tasks/standup.xml'
+    data: '{project-root}/{bmad_folder}/_cfg/agent-manifest.csv'
+    description: 'Run team standup'
+
+  - trigger: analyze-metrics
+    action: 'Analyze these metrics and identify trends'
+    data: '{project-root}/_data/metrics.json'
+    description: 'Analyze performance metrics'
+```
+
+**When to Use:**
+
+- Add to ANY handler type
+- Reference data files (CSV, JSON, YAML)
+- Provide context for operations
+
+## Platform-Specific Menus
+
+Control visibility based on deployment target:
+
+```yaml
+menu:
+  - trigger: git-flow
+    exec: '{project-root}/{bmad_folder}/bmm/tasks/git-flow.xml'
+    description: 'Git workflow operations'
+    ide-only: true # Only in IDE environments
+
+  - trigger: advanced-elicitation
+    exec: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
+    description: 'Advanced elicitation'
+    web-only: true # Only in web bundles
+```
+
+## Trigger Naming Conventions
+
+### Action-Based (Recommended)
+
+```yaml
+# Creation
+- trigger: create-prd
+- trigger: build-module
+- trigger: generate-report
+
+# Analysis
+- trigger: analyze-requirements
+- trigger: review-code
+- trigger: validate-architecture
+
+# Operations
+- trigger: update-status
+- trigger: sync-data
+- trigger: deploy-changes
+```
+
+### Domain-Based
+
+```yaml
+# Development
+- trigger: brainstorm
+- trigger: architect
+- trigger: refactor
+
+# Project Management
+- trigger: sprint-plan
+- trigger: retrospective
+- trigger: standup
+```
+
+### Bad Patterns
+
+```yaml
+# TOO VAGUE
+- trigger: do
+- trigger: run
+- trigger: process
+
+# TOO LONG
+- trigger: create-comprehensive-product-requirements-document
+
+# NO VERB
+- trigger: prd
+- trigger: config
+```
+
+## Menu Organization
+
+### Recommended Order
+
+```yaml
+menu:
+  # Note: *help auto-injected first by compiler
+
+  # 1. Primary workflows (main value)
+  - trigger: workflow-init
+    workflow: '...'
+    description: 'Start here - initialize workflow'
+
+  - trigger: create-prd
+    workflow: '...'
+    description: 'Create PRD'
+
+  # 2. Secondary operations
+  - trigger: validate
+    exec: '...'
+    description: 'Validate document'
+
+  # 3. Utilities
+  - trigger: party-mode
+    workflow: '...'
+    description: 'Multi-agent discussion'
+
+  # Note: *exit auto-injected last by compiler
+```
+
+### Grouping by Phase
+
+```yaml
+menu:
+  # Analysis Phase
+  - trigger: brainstorm
+    workflow: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
+    description: 'Brainstorm ideas'
+
+  - trigger: research
+    workflow: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/research/workflow.yaml'
+    description: 'Conduct research'
+
+  # Planning Phase
+  - trigger: prd
+    workflow: '{project-root}/{bmad_folder}/bmm/workflows/2-planning/prd/workflow.yaml'
+    description: 'Create PRD'
+
+  - trigger: architecture
+    workflow: '{project-root}/{bmad_folder}/bmm/workflows/2-planning/architecture/workflow.yaml'
+    description: 'Design architecture'
+```
+
+## Description Best Practices
+
+### Good Descriptions
+
+```yaml
+# Clear action + object
+- description: 'Create Product Requirements Document'
+
+# Specific outcome
+- description: 'Analyze security vulnerabilities'
+
+# User benefit
+- description: 'Optimize code for performance'
+
+# Context when needed
+- description: 'Start here - initialize workflow path'
+```
+
+### Poor Descriptions
+
+```yaml
+# Too vague
+- description: 'Process'
+
+# Technical jargon
+- description: 'Execute WF123'
+
+# Missing context
+- description: 'Run'
+
+# Redundant with trigger
+- description: 'Create PRD' # trigger: create-prd (too similar)
+```
+
+## Prompts Section (Simple/Expert Agents)
+
+### Prompt Structure
+
+```yaml
+prompts:
+  - id: unique-identifier
+    content: |
+      <instructions>
+      What this prompt accomplishes
+      </instructions>
+
+      <process>
+      1. First step
+      {{#if custom_option}}
+      2. Conditional step
+      {{/if}}
+      3. Final step
+      </process>
+
+      <output_format>
+      Expected structure of results
+      </output_format>
+```
+
+### Semantic XML Tags in Prompts
+
+Use XML tags to structure prompt content:
+
+- `<instructions>` - What to do
+- `<process>` - Step-by-step approach
+- `<output_format>` - Expected results
+- `<examples>` - Sample outputs
+- `<constraints>` - Limitations
+- `<context>` - Background information
+
+### Handlebars in Prompts
+
+Customize based on install_config:
+
+```yaml
+prompts:
+  - id: analyze
+    content: |
+      {{#if detailed_mode}}
+      Perform comprehensive analysis with full explanations.
+      {{/if}}
+      {{#unless detailed_mode}}
+      Quick analysis focusing on key points.
+      {{/unless}}
+
+      Address {{user_name}} in {{communication_style}} tone.
+```
+
+## Path Variables
+
+### Always Use Variables
+
+```yaml
+# GOOD - Portable paths
+workflow: "{project-root}/{bmad_folder}/bmm/workflows/prd/workflow.yaml"
+exec: "{project-root}/{bmad_folder}/core/tasks/validate.xml"
+data: "{project-root}/_data/metrics.csv"
+
+# BAD - Hardcoded paths
+workflow: "/Users/john/project/.bmad/bmm/workflows/prd/workflow.yaml"
+exec: "../../../core/tasks/validate.xml"
+```
+
+### Available Variables
+
+- `{project-root}` - Project root directory
+- `{bmad_folder}` - BMAD installation folder
+- `{agent-folder}` - Agent installation directory (Expert agents)
+- `{output_folder}` - Document output location
+- `{user_name}` - User's name from config
+- `{communication_language}` - Language preference
+
+## Complete Examples
+
+### Simple Agent Menu
+
+```yaml
+prompts:
+  - id: format-code
+    content: |
+      <instructions>
+      Format the provided code according to style guidelines.
+      </instructions>
+
+      Apply:
+      - Consistent indentation
+      - Proper spacing
+      - Clear naming conventions
+
+menu:
+  - trigger: format
+    action: '#format-code'
+    description: 'Format code to style guidelines'
+
+  - trigger: lint
+    action: 'Check code for common issues and anti-patterns'
+    description: 'Lint code for issues'
+
+  - trigger: suggest
+    action: 'Suggest improvements for code readability'
+    description: 'Suggest improvements'
+```
+
+### Expert Agent Menu
+
+```yaml
+critical_actions:
+  - 'Load {agent-folder}/memories.md'
+  - 'Follow {agent-folder}/instructions.md'
+  - 'ONLY access {agent-folder}/'
+
+prompts:
+  - id: reflect
+    content: |
+      Guide {{user_name}} through reflection on recent entries.
+      Reference patterns from memories.md naturally.
+
+menu:
+  - trigger: write
+    action: '#reflect'
+    description: 'Write journal entry'
+
+  - trigger: save
+    action: 'Update {agent-folder}/memories.md with session insights'
+    description: "Save today's session"
+
+  - trigger: patterns
+    action: 'Analyze recent entries for recurring themes'
+    description: 'View patterns'
+```
+
+### Module Agent Menu
+
+```yaml
+menu:
+  - trigger: workflow-init
+    workflow: '{project-root}/{bmad_folder}/bmm/workflows/workflow-status/init/workflow.yaml'
+    description: 'Initialize workflow path (START HERE)'
+
+  - trigger: brainstorm
+    workflow: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
+    description: 'Guided brainstorming'
+
+  - trigger: prd
+    workflow: '{project-root}/{bmad_folder}/bmm/workflows/2-planning/prd/workflow.yaml'
+    description: 'Create PRD'
+
+  - trigger: architecture
+    workflow: '{project-root}/{bmad_folder}/bmm/workflows/2-planning/architecture/workflow.yaml'
+    description: 'Design architecture'
+
+  - trigger: party-mode
+    workflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml'
+    description: 'Multi-agent discussion'
+```
+
+## Validation Checklist
+
+- [ ] No duplicate triggers
+- [ ] Triggers don't start with `*` (auto-added)
+- [ ] Every item has a description
+- [ ] Paths use variables, not hardcoded
+- [ ] `#id` references exist in prompts section
+- [ ] Workflow paths resolve or are "todo"
+- [ ] No `*help` or `*exit` (auto-injected)
+- [ ] Descriptions are clear and action-oriented
+- [ ] Platform-specific flags used correctly (ide-only, web-only)
+
+## Common Mistakes
+
+### Duplicate Triggers
+
+```yaml
+# BAD - compiler will fail
+- trigger: analyze
+  action: '#first'
+  description: 'First analysis'
+
+- trigger: analyze
+  action: '#second'
+  description: 'Second analysis'
+```
+
+### Including Auto-Injected Items
+
+```yaml
+# BAD - these are auto-injected
+menu:
+  - trigger: help
+    description: 'Show help'
+
+  - trigger: exit
+    description: 'Exit agent'
+```
+
+### Missing Prompt Reference
+
+```yaml
+# BAD - prompt id doesn't exist
+menu:
+  - trigger: analyze
+    action: '#nonexistent-prompt'
+    description: 'Analysis'
+```
+
+### Hardcoded Paths
+
+```yaml
+# BAD - not portable
+menu:
+  - trigger: run
+    workflow: '/absolute/path/to/workflow.yaml'
+    description: 'Run workflow'
+```
--- a/src/modules/bmb/docs/agents/expert-agent-architecture.md
+++ b/src/modules/bmb/docs/agents/expert-agent-architecture.md
@@ -0,0 +1,364 @@
+# Expert Agent Architecture
+
+Domain-specific agents with persistent memory, sidecar files, and restricted access patterns.
+
+## When to Use
+
+- Personal assistants (journal keeper, diary companion)
+- Specialized domain experts (legal advisor, medical reference)
+- Agents that need to remember past interactions
+- Agents with restricted file system access (privacy/security)
+- Long-term relationship agents that learn about users
+
+## File Structure
+
+```
+{agent-name}/
+├── {agent-name}.agent.yaml    # Main agent definition
+└── {agent-name}-sidecar/      # Supporting files
+    ├── instructions.md        # Private directives
+    ├── memories.md            # Persistent memory
+    ├── knowledge/             # Domain-specific resources
+    │   └── README.md
+    └── [custom files]         # Agent-specific resources
+```
+
+## YAML Structure
+
+```yaml
+agent:
+  metadata:
+    name: 'Persona Name'
+    title: 'Agent Title'
+    icon: 'emoji'
+    type: 'expert'
+
+  persona:
+    role: 'Domain Expert with specialized capability'
+
+    identity: |
+      Background and expertise in first-person voice.
+      {{#if user_preference}}
+      Customization based on install_config.
+      {{/if}}
+
+    communication_style: |
+      {{#if tone_style == "gentle"}}
+      Gentle and supportive communication...
+      {{/if}}
+      {{#if tone_style == "direct"}}
+      Direct and efficient communication...
+      {{/if}}
+      I reference past conversations naturally.
+
+    principles:
+      - Core belief about the domain
+      - How I handle user information
+      - My approach to memory and learning
+
+  critical_actions:
+    - 'Load COMPLETE file {agent-folder}/{agent-name}-sidecar/memories.md and remember all past insights'
+    - 'Load COMPLETE file {agent-folder}/{agent-name}-sidecar/instructions.md and follow ALL protocols'
+    - 'ONLY read/write files in {agent-folder}/{agent-name}-sidecar/ - this is our private space'
+    - 'Address user as {{greeting_name}}'
+    - 'Track patterns, themes, and important moments'
+    - 'Reference past interactions naturally to show continuity'
+
+  prompts:
+    - id: main-function
+      content: |
+        <instructions>
+        Guide user through the primary function.
+        {{#if tone_style == "gentle"}}
+        Use gentle, supportive approach.
+        {{/if}}
+        </instructions>
+
+        <process>
+        1. Understand context
+        2. Provide guidance
+        3. Record insights
+        </process>
+
+    - id: memory-recall
+      content: |
+        <instructions>
+        Access and share relevant memories.
+        </instructions>
+
+        Reference stored information naturally.
+
+  menu:
+    - trigger: action1
+      action: '#main-function'
+      description: 'Primary agent function'
+
+    - trigger: remember
+      action: 'Update {agent-folder}/{agent-name}-sidecar/memories.md with session insights'
+      description: 'Save what we discussed today'
+
+    - trigger: patterns
+      action: '#memory-recall'
+      description: 'Recall patterns from past interactions'
+
+    - trigger: insight
+      action: 'Document breakthrough in {agent-folder}/{agent-name}-sidecar/breakthroughs.md'
+      description: 'Record a significant insight'
+
+  install_config:
+    compile_time_only: true
+    description: 'Personalize your expert agent'
+    questions:
+      - var: greeting_name
+        prompt: 'What should the agent call you?'
+        type: text
+        default: 'friend'
+
+      - var: tone_style
+        prompt: 'Preferred communication tone?'
+        type: choice
+        options:
+          - label: 'Gentle - Supportive and nurturing'
+            value: 'gentle'
+          - label: 'Direct - Clear and efficient'
+            value: 'direct'
+        default: 'gentle'
+
+      - var: user_preference
+        prompt: 'Enable personalized features?'
+        type: boolean
+        default: true
+```
+
+## Key Components
+
+### Sidecar Files (CRITICAL)
+
+Expert agents use companion files for persistence and domain knowledge:
+
+**memories.md** - Persistent user context
+
+```markdown
+# Agent Memory Bank
+
+## User Preferences
+
+<!-- Learned from interactions -->
+
+## Session History
+
+<!-- Important moments and insights -->
+
+## Personal Notes
+
+<!-- Agent observations -->
+```
+
+**instructions.md** - Private directives
+
+```markdown
+# Agent Private Instructions
+
+## Core Directives
+
+- Maintain character consistency
+- Domain boundaries: {specific domain}
+- Access restrictions: Only sidecar folder
+
+## Special Rules
+
+<!-- Agent-specific protocols -->
+```
+
+**knowledge/** - Domain resources
+
+```markdown
+# Agent Knowledge Base
+
+Add domain-specific documentation here.
+```
+
+### Critical Actions
+
+**MANDATORY for expert agents** - These load sidecar files at activation:
+
+```yaml
+critical_actions:
+  - 'Load COMPLETE file {agent-folder}/{sidecar}/memories.md and remember all past insights'
+  - 'Load COMPLETE file {agent-folder}/{sidecar}/instructions.md and follow ALL protocols'
+  - 'ONLY read/write files in {agent-folder}/{sidecar}/ - this is our private space'
+```
+
+**Key patterns:**
+
+- **COMPLETE file loading** - Forces full file read, not partial
+- **Domain restrictions** - Limits file access for privacy/security
+- **Memory integration** - Past context becomes part of current session
+- **Protocol adherence** - Ensures consistent behavior
+
+### {agent-folder} Variable
+
+Special variable resolved during installation:
+
+- Points to the agent's installation directory
+- Used to reference sidecar files
+- Example: `.bmad/custom/agents/journal-keeper/`
+
+## What Gets Injected at Compile Time
+
+Same as simple agents, PLUS:
+
+1. **Critical actions become numbered activation steps**
+
+   ```xml
+   <step n="4">Load COMPLETE file {agent-folder}/memories.md...</step>
+   <step n="5">Load COMPLETE file {agent-folder}/instructions.md...</step>
+   <step n="6">ONLY read/write files in {agent-folder}/...</step>
+   ```
+
+2. **Sidecar files copied during installation**
+   - Entire sidecar folder structure preserved
+   - Relative paths maintained
+   - Files ready for agent use
+
+## Reference Example
+
+See: `src/modules/bmb/reference/agents/expert-examples/journal-keeper/`
+
+Features demonstrated:
+
+- Complete sidecar structure (memories, instructions, breakthroughs)
+- Critical actions for loading persistent context
+- Domain restrictions for privacy
+- Pattern recognition and memory recall
+- Handlebars-based personalization
+- Menu actions that update sidecar files
+
+## Installation
+
+```bash
+# Copy entire folder to your project
+cp -r /path/to/journal-keeper/ .bmad/custom/agents/
+
+# Install with personalization
+bmad agent-install
+```
+
+The installer:
+
+1. Detects expert agent (folder with .agent.yaml)
+2. Prompts for personalization
+3. Compiles agent YAML to XML-in-markdown
+4. **Copies sidecar files to installation target**
+5. Creates IDE slash commands
+6. Saves source for reinstallation
+
+## Memory Patterns
+
+### Accumulative Memory
+
+```yaml
+menu:
+  - trigger: save
+    action: "Update {agent-folder}/sidecar/memories.md with today's session insights"
+    description: 'Save session to memory'
+```
+
+### Reference Memory
+
+```yaml
+prompts:
+  - id: recall
+    content: |
+      <instructions>
+      Reference memories.md naturally:
+      "Last week you mentioned..." or "I notice a pattern..."
+      </instructions>
+```
+
+### Structured Insights
+
+```yaml
+menu:
+  - trigger: insight
+    action: 'Document in {agent-folder}/sidecar/breakthroughs.md with date, context, significance'
+    description: 'Record meaningful insight'
+```
+
+## Domain Restriction Patterns
+
+### Single Folder Access
+
+```yaml
+critical_actions:
+  - 'ONLY read/write files in {agent-folder}/sidecar/ - NO OTHER FOLDERS'
+```
+
+### User Space Access
+
+```yaml
+critical_actions:
+  - 'ONLY access files in {user-folder}/journals/ - private space'
+```
+
+### Read-Only Access
+
+```yaml
+critical_actions:
+  - 'Load knowledge from {agent-folder}/knowledge/ but NEVER modify'
+  - 'Write ONLY to {agent-folder}/sessions/'
+```
+
+## Best Practices
+
+1. **Load sidecar files in critical_actions** - Must be explicit and MANDATORY
+2. **Enforce domain restrictions** - Clear boundaries prevent scope creep
+3. **Use {agent-folder} paths** - Portable across installations
+4. **Design for memory growth** - Structure sidecar files for accumulation
+5. **Reference past naturally** - Don't dump memory, weave it into conversation
+6. **Separate concerns** - Memories, instructions, knowledge in distinct files
+7. **Include privacy features** - Users trust expert agents with personal data
+
+## Common Patterns
+
+### Session Continuity
+
+```yaml
+communication_style: |
+  I reference past conversations naturally:
+  "Last time we discussed..." or "I've noticed over the weeks..."
+```
+
+### Pattern Recognition
+
+```yaml
+critical_actions:
+  - 'Track mood patterns, recurring themes, and breakthrough moments'
+  - 'Cross-reference current session with historical patterns'
+```
+
+### Adaptive Responses
+
+```yaml
+identity: |
+  I learn your preferences and adapt my approach over time.
+  {{#if track_preferences}}
+  I maintain notes about what works best for you.
+  {{/if}}
+```
+
+## Validation Checklist
+
+- [ ] Valid YAML syntax
+- [ ] Metadata includes `type: "expert"`
+- [ ] critical_actions loads sidecar files explicitly
+- [ ] critical_actions enforces domain restrictions
+- [ ] Sidecar folder structure created and populated
+- [ ] memories.md has clear section structure
+- [ ] instructions.md contains core directives
+- [ ] Menu actions reference {agent-folder} correctly
+- [ ] File paths use {agent-folder} variable
+- [ ] Install config personalizes sidecar references
+- [ ] Agent folder named consistently: `{agent-name}/`
+- [ ] YAML file named: `{agent-name}.agent.yaml`
+- [ ] Sidecar folder named: `{agent-name}-sidecar/`
--- a/src/modules/bmb/docs/agents/index.md
+++ b/src/modules/bmb/docs/agents/index.md
@@ -0,0 +1,55 @@
+# BMB Module Documentation
+
+Reference documentation for building BMAD agents and workflows.
+
+## Agent Architecture
+
+Comprehensive guides for each agent type (choose based on use case):
+
+- [Understanding Agent Types](./understanding-agent-types.md) - **START HERE** - Architecture vs capability, "The Same Agent, Three Ways"
+- [Simple Agent Architecture](./simple-agent-architecture.md) - Self-contained, optimized, personality-driven
+- [Expert Agent Architecture](./expert-agent-architecture.md) - Memory, sidecar files, domain restrictions
+- [Module Agent Architecture](./module-agent-architecture.md) - Workflow integration, professional tools
+
+## Agent Design Patterns
+
+- [Agent Menu Patterns](./agent-menu-patterns.md) - Menu handlers, triggers, prompts, organization
+- [Agent Compilation](./agent-compilation.md) - What compiler auto-injects (AVOID DUPLICATION)
+
+## Reference Examples
+
+Production-ready examples in `/src/modules/bmb/reference/agents/`:
+
+**Simple Agents** (`simple-examples/`)
+
+- `commit-poet.agent.yaml` - Commit message artisan with style customization
+
+**Expert Agents** (`expert-examples/`)
+
+- `journal-keeper/` - Personal journal companion with memory and pattern recognition
+
+**Module Agents** (`module-examples/`)
+
+- `security-engineer.agent.yaml` - BMM security specialist with threat modeling
+- `trend-analyst.agent.yaml` - CIS trend intelligence expert
+
+## Installation Guide
+
+For installing standalone simple and expert agents, see:
+
+- [Custom Agent Installation](/docs/custom-agent-installation.md)
+
+## Key Concepts
+
+### YAML to XML Compilation
+
+Agents are authored in YAML with Handlebars templating. The compiler auto-injects:
+
+1. **Frontmatter** - Name and description from metadata
+2. **Activation Block** - Steps, menu handlers, rules (YOU don't write this)
+3. **Menu Enhancement** - `*help` and `*exit` commands added automatically
+4. **Trigger Prefixing** - Your triggers auto-prefixed with `*`
+
+**Critical:** See [Agent Compilation](./agent-compilation.md) to avoid duplicating auto-injected content.
+
+Source: `tools/cli/lib/agent/compiler.js`
--- a/src/modules/bmb/docs/agents/kb.csv
+++ b/src/modules/bmb/docs/agents/kb.csv
--- a/src/modules/bmb/docs/agents/module-agent-architecture.md
+++ b/src/modules/bmb/docs/agents/module-agent-architecture.md
@@ -0,0 +1,367 @@
+# Module Agent Architecture
+
+Full integration agents with workflow orchestration, module-specific paths, and professional tooling.
+
+## When to Use
+
+- Professional development workflows (business analysis, architecture design)
+- Team-oriented tools (project management, sprint planning)
+- Agents that orchestrate multiple workflows
+- Module-specific functionality (BMM, BMB, CIS, custom modules)
+- Agents with complex multi-step operations
+
+## File Location
+
+```
+src/modules/{module-code}/agents/{agent-name}.agent.yaml
+```
+
+Compiles to:
+
+```
+.bmad/{module-code}/agents/{agent-name}.md
+```
+
+## YAML Structure
+
+```yaml
+agent:
+  metadata:
+    id: '{bmad_folder}/{module-code}/agents/{agent-name}.md'
+    name: 'Persona Name'
+    title: 'Professional Title'
+    icon: 'emoji'
+    module: '{module-code}'
+
+  persona:
+    role: 'Primary expertise and function'
+    identity: 'Background, experience, specializations'
+    communication_style: 'Interaction approach, tone, methodology'
+    principles: 'Core beliefs and methodology'
+
+  menu:
+    - trigger: workflow-action
+      workflow: '{project-root}/{bmad_folder}/{module-code}/workflows/{workflow-name}/workflow.yaml'
+      description: 'Execute module workflow'
+
+    - trigger: another-workflow
+      workflow: '{project-root}/{bmad_folder}/core/workflows/{workflow-name}/workflow.yaml'
+      description: 'Execute core workflow'
+
+    - trigger: task-action
+      exec: '{project-root}/{bmad_folder}/{module-code}/tasks/{task-name}.xml'
+      description: 'Execute module task'
+
+    - trigger: cross-module
+      workflow: '{project-root}/{bmad_folder}/other-module/workflows/{workflow-name}/workflow.yaml'
+      description: 'Execute workflow from another module'
+
+    - trigger: with-template
+      exec: '{project-root}/{bmad_folder}/core/tasks/create-doc.xml'
+      tmpl: '{project-root}/{bmad_folder}/{module-code}/templates/{template-name}.md'
+      description: 'Create document from template'
+
+    - trigger: with-data
+      exec: '{project-root}/{bmad_folder}/{module-code}/tasks/{task-name}.xml'
+      data: '{project-root}/{bmad_folder}/_cfg/agent-manifest.csv'
+      description: 'Execute task with data file'
+```
+
+## Key Components
+
+### Metadata
+
+- **id**: Path with `{bmad_folder}` variable (resolved at install time)
+- **name**: Agent persona name
+- **title**: Professional role
+- **icon**: Single emoji
+- **module**: Module code (bmm, bmb, cis, custom)
+
+### Persona (Professional Voice)
+
+Module agents typically use **professional** communication styles:
+
+```yaml
+persona:
+  role: Strategic Business Analyst + Requirements Expert
+
+  identity: Senior analyst with deep expertise in market research, competitive analysis, and requirements elicitation. Specializes in translating vague needs into actionable specs.
+
+  communication_style: Systematic and probing. Connects dots others miss. Structures findings hierarchically. Uses precise unambiguous language. Ensures all stakeholder voices heard.
+
+  principles: Every business challenge has root causes waiting to be discovered. Ground findings in verifiable evidence. Articulate requirements with absolute precision.
+```
+
+**Note:** Module agents usually don't use Handlebars templating since they're not user-customized - they're professional tools with fixed personalities.
+
+### Menu Handlers
+
+#### Workflow Handler (Most Common)
+
+```yaml
+menu:
+  - trigger: create-prd
+    workflow: '{project-root}/{bmad_folder}/bmm/workflows/prd/workflow.yaml'
+    description: 'Create Product Requirements Document'
+```
+
+Invokes BMAD workflow engine to execute multi-step processes.
+
+#### Task/Exec Handler
+
+```yaml
+menu:
+  - trigger: validate
+    exec: '{project-root}/{bmad_folder}/core/tasks/validate-workflow.xml'
+    description: 'Validate document structure'
+```
+
+Executes single-operation tasks.
+
+#### Template Handler
+
+```yaml
+menu:
+  - trigger: create-brief
+    exec: '{project-root}/{bmad_folder}/core/tasks/create-doc.xml'
+    tmpl: '{project-root}/{bmad_folder}/bmm/templates/brief.md'
+    description: 'Create a Product Brief from template'
+```
+
+Combines task execution with template file.
+
+#### Data Handler
+
+```yaml
+menu:
+  - trigger: team-standup
+    exec: '{project-root}/{bmad_folder}/bmm/tasks/standup.xml'
+    data: '{project-root}/{bmad_folder}/_cfg/agent-manifest.csv'
+    description: 'Run team standup with agent roster'
+```
+
+Provides data file to task.
+
+#### Placeholder Handler
+
+```yaml
+menu:
+  - trigger: future-feature
+    workflow: 'todo'
+    description: 'Feature planned but not yet implemented'
+```
+
+Marks unimplemented features - compiler handles gracefully.
+
+### Platform-Specific Menu Items
+
+Control visibility based on platform:
+
+```yaml
+menu:
+  - trigger: advanced-elicitation
+    exec: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
+    description: 'Advanced elicitation techniques'
+    web-only: true # Only shows in web bundle
+
+  - trigger: git-operations
+    exec: '{project-root}/{bmad_folder}/bmm/tasks/git-flow.xml'
+    description: 'Git workflow operations'
+    ide-only: true # Only shows in IDE environments
+```
+
+## Variable System
+
+### Core Variables
+
+- `{project-root}` - Root directory of installed project
+- `{bmad_folder}` - BMAD installation folder (usually `.bmad`)
+- `{user_name}` - User's name from module config
+- `{communication_language}` - Language preference
+- `{output_folder}` - Document output directory
+
+### Path Construction
+
+**Always use variables, never hardcoded paths:**
+
+```yaml
+# GOOD
+workflow: "{project-root}/{bmad_folder}/bmm/workflows/prd/workflow.yaml"
+
+# BAD
+workflow: "/Users/john/project/.bmad/bmm/workflows/prd/workflow.yaml"
+
+# BAD
+workflow: "../../../bmm/workflows/prd/workflow.yaml"
+```
+
+## What Gets Injected at Compile Time
+
+Module agents use the same injection process as simple agents:
+
+1. **Frontmatter** with name and description
+2. **Activation block** with standard steps
+3. **Menu handlers** based on usage (workflow, exec, tmpl, data)
+4. **Rules section** for consistent behavior
+5. **Auto-injected** *help and *exit commands
+
+**Key difference:** Module agents load **module-specific config** instead of core config:
+
+```xml
+<step n="2">Load and read {project-root}/{bmad_folder}/{module}/config.yaml...</step>
+```
+
+## Reference Examples
+
+See: `src/modules/bmm/agents/`
+
+**analyst.agent.yaml** - Business Analyst
+
+- Workflow orchestration for analysis phase
+- Multiple workflow integrations
+- Cross-module workflow access (core/workflows/party-mode)
+
+**architect.agent.yaml** - System Architect
+
+- Technical workflow management
+- Architecture decision workflows
+
+**pm.agent.yaml** - Product Manager
+
+- Planning and coordination workflows
+- Sprint management integration
+
+## Module Configuration
+
+Each module has `config.yaml` providing:
+
+```yaml
+# src/modules/{module}/config.yaml
+user_name: 'User Name'
+communication_language: 'English'
+output_folder: '{project-root}/docs'
+custom_settings: 'module-specific values'
+```
+
+Agents load this at activation for consistent behavior.
+
+## Workflow Integration Patterns
+
+### Sequential Workflow Execution
+
+```yaml
+menu:
+  - trigger: init
+    workflow: '{project-root}/{bmad_folder}/bmm/workflows/workflow-init/workflow.yaml'
+    description: 'Initialize workflow path (START HERE)'
+
+  - trigger: status
+    workflow: '{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml'
+    description: 'Check current workflow status'
+
+  - trigger: next-step
+    workflow: '{project-root}/{bmad_folder}/bmm/workflows/next-step/workflow.yaml'
+    description: 'Execute next workflow in sequence'
+```
+
+### Phase-Based Organization
+
+```yaml
+menu:
+  # Phase 1: Analysis
+  - trigger: brainstorm
+    workflow: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
+    description: 'Guided brainstorming session'
+
+  - trigger: research
+    workflow: '{project-root}/{bmad_folder}/bmm/workflows/1-analysis/research/workflow.yaml'
+    description: 'Market and technical research'
+
+  # Phase 2: Planning
+  - trigger: prd
+    workflow: '{project-root}/{bmad_folder}/bmm/workflows/2-planning/prd/workflow.yaml'
+    description: 'Create PRD'
+
+  - trigger: architecture
+    workflow: '{project-root}/{bmad_folder}/bmm/workflows/2-planning/architecture/workflow.yaml'
+    description: 'Design architecture'
+```
+
+### Cross-Module Access
+
+```yaml
+menu:
+  - trigger: party-mode
+    workflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml'
+    description: 'Bring all agents together'
+
+  - trigger: brainstorm
+    workflow: '{project-root}/{bmad_folder}/cis/workflows/brainstorming/workflow.yaml'
+    description: 'Use CIS brainstorming techniques'
+```
+
+## Best Practices
+
+1. **Use {bmad_folder} paths** - Portable across installations
+2. **Organize workflows by phase** - Clear progression for users
+3. **Include workflow-status** - Help users track progress
+4. **Reference module config** - Consistent behavior
+5. **No Handlebars templating** - Module agents are fixed personalities
+6. **Professional personas** - Match module purpose
+7. **Clear trigger names** - Self-documenting commands
+8. **Group related workflows** - Logical menu organization
+
+## Common Patterns
+
+### Entry Point Agent
+
+```yaml
+menu:
+  - trigger: start
+    workflow: '{project-root}/{bmad_folder}/{module}/workflows/init/workflow.yaml'
+    description: 'Start new project (BEGIN HERE)'
+```
+
+### Status Tracking
+
+```yaml
+menu:
+  - trigger: status
+    workflow: '{project-root}/{bmad_folder}/{module}/workflows/status/workflow.yaml'
+    description: 'Check workflow progress'
+```
+
+### Team Coordination
+
+```yaml
+menu:
+  - trigger: party
+    workflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml'
+    description: 'Multi-agent discussion'
+```
+
+## Module Agent vs Simple/Expert
+
+| Aspect        | Module Agent                     | Simple/Expert Agent             |
+| ------------- | -------------------------------- | ------------------------------- |
+| Location      | `{bmad_folder}/{module}/agents/` | `{bmad_folder}/custom/agents/`  |
+| Persona       | Fixed, professional              | Customizable via install_config |
+| Handlebars    | No templating                    | Yes, extensive                  |
+| Menu actions  | Workflows, tasks, templates      | Prompts, inline actions         |
+| Configuration | Module config.yaml               | Core config or none             |
+| Purpose       | Professional tooling             | Personal utilities              |
+
+## Validation Checklist
+
+- [ ] Valid YAML syntax
+- [ ] Metadata includes `module: "{module-code}"`
+- [ ] id uses `{bmad_folder}/{module}/agents/{name}.md`
+- [ ] All workflow paths use `{project-root}/{bmad_folder}/` prefix
+- [ ] No hardcoded paths
+- [ ] No duplicate triggers
+- [ ] Each menu item has description
+- [ ] Triggers don't start with `*` (auto-added)
+- [ ] Professional persona appropriate for module
+- [ ] Workflow paths resolve to actual workflows (or "todo")
+- [ ] File named `{agent-name}.agent.yaml`
+- [ ] Located in `src/modules/{module}/agents/`
--- a/Show More
+++ b/Show More