package push

- Transition BMad Method from Alpha to Beta
- Beta versions now publish to npm 'latest' tag (default for npx)
- Updated manual release workflow to prioritize beta releases
- Updated CHANGELOG with Beta.0 release notes

.coderabbit.yaml

@@ -11,8 +11,8 @@ reviews:
   walkthrough: false
   poem: false
   auto_review:
-    enabled: false
-    drafts: true # Can review drafts. Since it's manually triggered, it's fine.
+    enabled: true
+    drafts: false # Don't review drafts automatically
     auto_incremental_review: false # always review the whole PR, not just new commits
     base_branches:
       - main

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,32 +0,0 @@
----
-name: Bug report
-about: Create a report to help us improve
-title: ''
-labels: ''
-assignees: ''
----
-
-**Describe the bug**
-A clear and concise description of what the bug is.
-
-**Steps to Reproduce**
-What lead to the bug and can it be reliable recreated - if so with what steps.
-
-**PR**
-If you have an idea to fix and would like to contribute, please indicate here you are working on a fix, or link to a proposed PR to fix the issue. Please review the contribution.md - contributions are always welcome!
-
-**Expected behavior**
-A clear and concise description of what you expected to happen.
-
-**Please be Specific if relevant**
-Model(s) Used:
-Agentic IDE Used:
-WebSite Used:
-Project Language:
-BMad Method version:
-
-**Screenshots or Links**
-If applicable, add screenshots or links (if web sharable record) to help explain your problem.
-
-**Additional context**
-Add any other context about the problem here. The more information you can provide, the easier it will be to suggest a fix or resolve

.github/ISSUE_TEMPLATE/config.yaml

@@ -1,5 +1,8 @@
 blank_issues_enabled: false
 contact_links:
-  - name: Discord Community Support
+  - name: 📚 Documentation
+    url: http://docs.bmad-method.org
+    about: Check the docs first — tutorials, guides, and reference
+  - name: 💬 Discord Community
     url: https://discord.gg/gk8jAdXWmj
-    about: Please join our Discord server for general questions and community discussion before opening an issue.
+    about: Join for questions, discussion, and help before opening an issue

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,22 @@
+---
+name: Feature Request
+about: Suggest an idea or new feature
+title: ''
+labels: ''
+assignees: ''
+---
+
+**Describe your idea**
+A clear and concise description of what you'd like to see added or changed.
+
+**Why is this needed?**
+Explain the problem this solves or the benefit it brings to the BMad community.
+
+**How should it work?**
+Describe your proposed solution. If you have ideas on implementation, share them here.
+
+**PR**
+If you'd like to contribute, please indicate you're working on this or link to your PR. Please review [CONTRIBUTING.md](../../CONTRIBUTING.md) — contributions are always welcome!
+
+**Additional context**
+Add any other context, screenshots, or links that help explain your idea.

.github/ISSUE_TEMPLATE/idea_submission.md

@@ -1,109 +0,0 @@
----
-name: V6 Idea Submission
-about: Suggest an idea for v6
-title: ''
-labels: ''
-assignees: ''
----
-
-# Idea: [Replace with a clear, actionable title]
-
-## PASS Framework
-
-**P**roblem:
-
-> What's broken or missing? What pain point are we addressing? (1-2 sentences)
->
-> [Your answer here]
-
-**A**udience:
-
-> Who's affected by this problem and how severely? (1-2 sentences)
->
-> [Your answer here]
-
-**S**olution:
-
-> What will we build or change? How will we measure success? (1-2 sentences with at least 1 measurable outcome)
->
-> [Your answer here]
->
-> [Your Acceptance Criteria for measuring success here]
-
-**S**ize:
-
-> How much effort do you estimate this will take?
->
-> - [ ] **XS** - A few hours
-> - [ ] **S** - 1-2 days
-> - [ ] **M** - 3-5 days
-> - [ ] **L** - 1-2 weeks
-> - [ ] **XL** - More than 2 weeks
-
----
-
-### Metadata
-
-**Submitted by:** [Your name]  
-**Date:** [Today's date]  
-**Priority:** [Leave blank - will be assigned during team review]
-
----
-
-## Examples
-
-<details>
-<summary>Click to see a GOOD example</summary>
-
-### Idea: Add search functionality to customer dashboard
-
-**P**roblem:  
-Customers can't find their past orders quickly. They have to scroll through pages of orders to find what they're looking for, leading to 15+ support tickets per week.
-
-**A**udience:  
-All 5,000+ active customers are affected. Support team spends ~10 hours/week helping customers find orders.
-
-**S**olution:  
-Add a search bar that filters by order number, date range, and product name. Success = 50% reduction in order-finding support tickets within 2 weeks of launch.
-
-**S**ize:
-
-- [x] **M** - 3-5 days
-
-</details>
-
-<details>
-<summary>Click to see a POOR example</summary>
-
-### Idea: Make the app better
-
-**P**roblem:  
-The app needs improvements and updates.
-
-**A**udience:  
-Users
-
-**S**olution:  
-Fix issues and add features.
-
-**S**ize:
-
-- [ ] Unknown
-
-_Why this is poor: Too vague, no specific problem identified, no measurable success criteria, unclear scope_
-
-</details>
-
----
-
-## Tips for Success
-
-1. **Be specific** - Vague problems lead to vague solutions
-2. **Quantify when possible** - Numbers help us prioritize (e.g., "20 customers asked for this" vs "customers want this")
-3. **One idea per submission** - If you have multiple ideas, submit multiple templates
-4. **Success metrics matter** - How will we know this worked?
-5. **Honest sizing** - Better to overestimate than underestimate
-
-## Questions?
-
-Reach out to @OverlordBaconPants if you need help completing this template.

.github/ISSUE_TEMPLATE/issue.md

@@ -0,0 +1,32 @@
+---
+name: Issue
+about: Report a problem or something that's not working
+title: ''
+labels: ''
+assignees: ''
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**Steps to reproduce**
+1. What were you doing when the bug occurred?
+2. What steps can recreate the issue?
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Environment (if relevant)**
+- Model(s) used:
+- Agentic IDE used:
+- BMad version:
+- Project language:
+
+**Screenshots or links**
+If applicable, add screenshots or links to help explain the problem.
+
+**PR**
+If you'd like to contribute a fix, please indicate you're working on it or link to your PR. See [CONTRIBUTING.md](../../CONTRIBUTING.md) — contributions are always welcome!
+
+**Additional context**
+Add any other context about the problem here. The more information you provide, the easier it is to help.

.github/workflows/bundle-latest.yaml

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

.github/workflows/discord.yaml

@@ -2,19 +2,9 @@ name: Discord Notification
 
 on:
   pull_request:
-    types: [opened, closed, reopened, ready_for_review]
-  release:
-    types: [published]
-  create:
-  delete:
-  issue_comment:
-    types: [created]
-  pull_request_review:
-    types: [submitted]
-  pull_request_review_comment:
-    types: [created]
+    types: [opened, closed]
   issues:
-    types: [opened, closed, reopened]
+    types: [opened]
 
 env:
   MAX_TITLE: 100
@@ -47,9 +37,7 @@ jobs:
 
           if [ "$ACTION" = "opened" ]; then ICON="🔀"; LABEL="New PR"
           elif [ "$ACTION" = "closed" ] && [ "$MERGED" = "true" ]; then ICON="🎉"; LABEL="Merged"
-          elif [ "$ACTION" = "closed" ]; then ICON="❌"; LABEL="Closed"
-          elif [ "$ACTION" = "reopened" ]; then ICON="🔄"; LABEL="Reopened"
-          else ICON="📋"; LABEL="Ready"; fi
+          elif [ "$ACTION" = "closed" ]; then ICON="❌"; LABEL="Closed"; fi
 
           TITLE=$(printf '%s' "$PR_TITLE" | trunc $MAX_TITLE | esc)
           [ ${#PR_TITLE} -gt $MAX_TITLE ] && TITLE="${TITLE}..."
@@ -77,22 +65,16 @@ jobs:
       - name: Notify Discord
         env:
           WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
-          ACTION: ${{ github.event.action }}
           ISSUE_NUM: ${{ github.event.issue.number }}
           ISSUE_URL: ${{ github.event.issue.html_url }}
           ISSUE_TITLE: ${{ github.event.issue.title }}
           ISSUE_USER: ${{ github.event.issue.user.login }}
           ISSUE_BODY: ${{ github.event.issue.body }}
-          ACTOR: ${{ github.actor }}
         run: |
           set -o pipefail
           source .github/scripts/discord-helpers.sh
           [ -z "$WEBHOOK" ] && exit 0
 
-          if [ "$ACTION" = "opened" ]; then ICON="🐛"; LABEL="New Issue"; USER="$ISSUE_USER"
-          elif [ "$ACTION" = "closed" ]; then ICON="✅"; LABEL="Closed"; USER="$ACTOR"
-          else ICON="🔄"; LABEL="Reopened"; USER="$ACTOR"; fi
-
           TITLE=$(printf '%s' "$ISSUE_TITLE" | trunc $MAX_TITLE | esc)
           [ ${#ISSUE_TITLE} -gt $MAX_TITLE ] && TITLE="${TITLE}..."
           BODY=$(printf '%s' "$ISSUE_BODY" | trunc $MAX_BODY)
@@ -102,209 +84,7 @@ jobs:
           BODY=$(printf '%s' "$BODY" | wrap_urls | esc)
           [ -n "$ISSUE_BODY" ] && [ ${#ISSUE_BODY} -gt $MAX_BODY ] && BODY="${BODY}..."
           [ -n "$BODY" ] && BODY=" · $BODY"
-          USER=$(printf '%s' "$USER" | esc)
+          USER=$(printf '%s' "$ISSUE_USER" | esc)
 
-          MSG="$ICON **[$LABEL #$ISSUE_NUM: $TITLE](<$ISSUE_URL>)**"$'\n'"by @$USER$BODY"
-          jq -n --arg content "$MSG" '{content: $content}' | curl -sf --retry 2 -X POST "$WEBHOOK" -H "Content-Type: application/json" -d @-
-
-  issue_comment:
-    if: github.event_name == 'issue_comment'
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          ref: ${{ github.event.repository.default_branch }}
-          sparse-checkout: .github/scripts
-          sparse-checkout-cone-mode: false
-      - name: Notify Discord
-        env:
-          WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
-          IS_PR: ${{ github.event.issue.pull_request && 'true' || 'false' }}
-          ISSUE_NUM: ${{ github.event.issue.number }}
-          ISSUE_TITLE: ${{ github.event.issue.title }}
-          COMMENT_URL: ${{ github.event.comment.html_url }}
-          COMMENT_USER: ${{ github.event.comment.user.login }}
-          COMMENT_BODY: ${{ github.event.comment.body }}
-        run: |
-          set -o pipefail
-          source .github/scripts/discord-helpers.sh
-          [ -z "$WEBHOOK" ] && exit 0
-
-          [ "$IS_PR" = "true" ] && TYPE="PR" || TYPE="Issue"
-
-          TITLE=$(printf '%s' "$ISSUE_TITLE" | trunc $MAX_TITLE | esc)
-          [ ${#ISSUE_TITLE} -gt $MAX_TITLE ] && TITLE="${TITLE}..."
-          BODY=$(printf '%s' "$COMMENT_BODY" | trunc $MAX_BODY)
-          if [ ${#COMMENT_BODY} -gt $MAX_BODY ]; then
-            BODY=$(printf '%s' "$BODY" | strip_trailing_url)
-          fi
-          BODY=$(printf '%s' "$BODY" | wrap_urls | esc)
-          [ ${#COMMENT_BODY} -gt $MAX_BODY ] && BODY="${BODY}..."
-          USER=$(printf '%s' "$COMMENT_USER" | esc)
-
-          MSG="💬 **[Comment on $TYPE #$ISSUE_NUM: $TITLE](<$COMMENT_URL>)**"$'\n'"@$USER: $BODY"
-          jq -n --arg content "$MSG" '{content: $content}' | curl -sf --retry 2 -X POST "$WEBHOOK" -H "Content-Type: application/json" -d @-
-
-  pull_request_review:
-    if: github.event_name == 'pull_request_review'
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          ref: ${{ github.event.repository.default_branch }}
-          sparse-checkout: .github/scripts
-          sparse-checkout-cone-mode: false
-      - name: Notify Discord
-        env:
-          WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
-          STATE: ${{ github.event.review.state }}
-          PR_NUM: ${{ github.event.pull_request.number }}
-          PR_TITLE: ${{ github.event.pull_request.title }}
-          REVIEW_URL: ${{ github.event.review.html_url }}
-          REVIEW_USER: ${{ github.event.review.user.login }}
-          REVIEW_BODY: ${{ github.event.review.body }}
-        run: |
-          set -o pipefail
-          source .github/scripts/discord-helpers.sh
-          [ -z "$WEBHOOK" ] && exit 0
-
-          if [ "$STATE" = "approved" ]; then ICON="✅"; LABEL="Approved"
-          elif [ "$STATE" = "changes_requested" ]; then ICON="🔧"; LABEL="Changes Requested"
-          else ICON="👀"; LABEL="Reviewed"; fi
-
-          TITLE=$(printf '%s' "$PR_TITLE" | trunc $MAX_TITLE | esc)
-          [ ${#PR_TITLE} -gt $MAX_TITLE ] && TITLE="${TITLE}..."
-          BODY=$(printf '%s' "$REVIEW_BODY" | trunc $MAX_BODY)
-          if [ -n "$REVIEW_BODY" ] && [ ${#REVIEW_BODY} -gt $MAX_BODY ]; then
-            BODY=$(printf '%s' "$BODY" | strip_trailing_url)
-          fi
-          BODY=$(printf '%s' "$BODY" | wrap_urls | esc)
-          [ -n "$REVIEW_BODY" ] && [ ${#REVIEW_BODY} -gt $MAX_BODY ] && BODY="${BODY}..."
-          [ -n "$BODY" ] && BODY=": $BODY"
-          USER=$(printf '%s' "$REVIEW_USER" | esc)
-
-          MSG="$ICON **[$LABEL PR #$PR_NUM: $TITLE](<$REVIEW_URL>)**"$'\n'"@$USER$BODY"
-          jq -n --arg content "$MSG" '{content: $content}' | curl -sf --retry 2 -X POST "$WEBHOOK" -H "Content-Type: application/json" -d @-
-
-  pull_request_review_comment:
-    if: github.event_name == 'pull_request_review_comment'
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          ref: ${{ github.event.repository.default_branch }}
-          sparse-checkout: .github/scripts
-          sparse-checkout-cone-mode: false
-      - name: Notify Discord
-        env:
-          WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
-          PR_NUM: ${{ github.event.pull_request.number }}
-          PR_TITLE: ${{ github.event.pull_request.title }}
-          COMMENT_URL: ${{ github.event.comment.html_url }}
-          COMMENT_USER: ${{ github.event.comment.user.login }}
-          COMMENT_BODY: ${{ github.event.comment.body }}
-        run: |
-          set -o pipefail
-          source .github/scripts/discord-helpers.sh
-          [ -z "$WEBHOOK" ] && exit 0
-
-          TITLE=$(printf '%s' "$PR_TITLE" | trunc $MAX_TITLE | esc)
-          [ ${#PR_TITLE} -gt $MAX_TITLE ] && TITLE="${TITLE}..."
-          BODY=$(printf '%s' "$COMMENT_BODY" | trunc $MAX_BODY)
-          if [ ${#COMMENT_BODY} -gt $MAX_BODY ]; then
-            BODY=$(printf '%s' "$BODY" | strip_trailing_url)
-          fi
-          BODY=$(printf '%s' "$BODY" | wrap_urls | esc)
-          [ ${#COMMENT_BODY} -gt $MAX_BODY ] && BODY="${BODY}..."
-          USER=$(printf '%s' "$COMMENT_USER" | esc)
-
-          MSG="💭 **[Review Comment PR #$PR_NUM: $TITLE](<$COMMENT_URL>)**"$'\n'"@$USER: $BODY"
-          jq -n --arg content "$MSG" '{content: $content}' | curl -sf --retry 2 -X POST "$WEBHOOK" -H "Content-Type: application/json" -d @-
-
-  release:
-    if: github.event_name == 'release'
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          ref: ${{ github.event.repository.default_branch }}
-          sparse-checkout: .github/scripts
-          sparse-checkout-cone-mode: false
-      - name: Notify Discord
-        env:
-          WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
-          TAG: ${{ github.event.release.tag_name }}
-          NAME: ${{ github.event.release.name }}
-          URL: ${{ github.event.release.html_url }}
-          RELEASE_BODY: ${{ github.event.release.body }}
-        run: |
-          set -o pipefail
-          source .github/scripts/discord-helpers.sh
-          [ -z "$WEBHOOK" ] && exit 0
-
-          REL_NAME=$(printf '%s' "$NAME" | trunc $MAX_TITLE | esc)
-          [ ${#NAME} -gt $MAX_TITLE ] && REL_NAME="${REL_NAME}..."
-          BODY=$(printf '%s' "$RELEASE_BODY" | trunc $MAX_BODY)
-          if [ -n "$RELEASE_BODY" ] && [ ${#RELEASE_BODY} -gt $MAX_BODY ]; then
-            BODY=$(printf '%s' "$BODY" | strip_trailing_url)
-          fi
-          BODY=$(printf '%s' "$BODY" | wrap_urls | esc)
-          [ -n "$RELEASE_BODY" ] && [ ${#RELEASE_BODY} -gt $MAX_BODY ] && BODY="${BODY}..."
-          [ -n "$BODY" ] && BODY=" · $BODY"
-          TAG_ESC=$(printf '%s' "$TAG" | esc)
-
-          MSG="🚀 **[Release $TAG_ESC: $REL_NAME](<$URL>)**"$'\n'"$BODY"
-          jq -n --arg content "$MSG" '{content: $content}' | curl -sf --retry 2 -X POST "$WEBHOOK" -H "Content-Type: application/json" -d @-
-
-  create:
-    if: github.event_name == 'create'
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          ref: ${{ github.event.repository.default_branch }}
-          sparse-checkout: .github/scripts
-          sparse-checkout-cone-mode: false
-      - name: Notify Discord
-        env:
-          WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
-          REF_TYPE: ${{ github.event.ref_type }}
-          REF: ${{ github.event.ref }}
-          ACTOR: ${{ github.actor }}
-          REPO_URL: ${{ github.event.repository.html_url }}
-        run: |
-          set -o pipefail
-          source .github/scripts/discord-helpers.sh
-          [ -z "$WEBHOOK" ] && exit 0
-
-          [ "$REF_TYPE" = "branch" ] && ICON="🌿" || ICON="🏷️"
-          REF_TRUNC=$(printf '%s' "$REF" | trunc $MAX_TITLE)
-          [ ${#REF} -gt $MAX_TITLE ] && REF_TRUNC="${REF_TRUNC}..."
-          REF_ESC=$(printf '%s' "$REF_TRUNC" | esc)
-          REF_URL=$(jq -rn --arg ref "$REF" '$ref | @uri')
-          ACTOR_ESC=$(printf '%s' "$ACTOR" | esc)
-          MSG="$ICON **${REF_TYPE^} created: [$REF_ESC](<$REPO_URL/tree/$REF_URL>)** by @$ACTOR_ESC"
-          jq -n --arg content "$MSG" '{content: $content}' | curl -sf --retry 2 -X POST "$WEBHOOK" -H "Content-Type: application/json" -d @-
-
-  delete:
-    if: github.event_name == 'delete'
-    runs-on: ubuntu-latest
-    steps:
-      - name: Notify Discord
-        env:
-          WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
-          REF_TYPE: ${{ github.event.ref_type }}
-          REF: ${{ github.event.ref }}
-          ACTOR: ${{ github.actor }}
-        run: |
-          set -o pipefail
-          [ -z "$WEBHOOK" ] && exit 0
-          esc() { sed -e 's/[][\*_()~`]/\\&/g' -e 's/@/@ /g'; }
-          trunc() { tr '\n\r' '  ' | cut -c1-"$1"; }
-
-          REF_TRUNC=$(printf '%s' "$REF" | trunc 100)
-          [ ${#REF} -gt 100 ] && REF_TRUNC="${REF_TRUNC}..."
-          REF_ESC=$(printf '%s' "$REF_TRUNC" | esc)
-          ACTOR_ESC=$(printf '%s' "$ACTOR" | esc)
-          MSG="🗑️ **${REF_TYPE^} deleted: $REF_ESC** by @$ACTOR_ESC"
+          MSG="🐛 **[Issue #$ISSUE_NUM: $TITLE](<$ISSUE_URL>)**"$'\n'"by @$USER$BODY"
           jq -n --arg content "$MSG" '{content: $content}' | curl -sf --retry 2 -X POST "$WEBHOOK" -H "Content-Type: application/json" -d @-

.github/workflows/docs.yaml

@@ -0,0 +1,63 @@
+name: Deploy Documentation
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - "docs/**"
+      - "src/modules/*/docs/**"
+      - "website/**"
+      - "tools/build-docs.js"
+      - ".github/workflows/docs.yaml"
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: "pages"
+  cancel-in-progress: false
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: "20"
+          cache: "npm"
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Build documentation
+        env:
+          # Override site URL from GitHub repo variable if set
+          # Otherwise, astro.config.mjs will compute from GITHUB_REPOSITORY
+          SITE_URL: ${{ vars.SITE_URL }}
+        run: npm run docs:build
+
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: build/site
+
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    needs: build
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

.github/workflows/manual-release.yaml

@@ -6,11 +6,11 @@ on:
       version_bump:
         description: Version bump type
         required: true
-        default: alpha
+        default: beta
         type: choice
         options:
-          - alpha
           - beta
+          - alpha
           - patch
           - minor
           - major
@@ -158,9 +158,12 @@ jobs:
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
         run: |
           VERSION="${{ steps.version.outputs.new_version }}"
-          if [[ "$VERSION" == *"alpha"* ]] || [[ "$VERSION" == *"beta"* ]]; then
-            echo "Publishing prerelease version with --tag alpha"
+          if [[ "$VERSION" == *"alpha"* ]]; then
+            echo "Publishing alpha prerelease version with --tag alpha"
             npm publish --tag alpha
+          elif [[ "$VERSION" == *"beta"* ]]; then
+            echo "Publishing beta prerelease version with --tag latest"
+            npm publish --tag latest
           else
             echo "Publishing stable version with --tag latest"
             npm publish --tag latest

.github/workflows/quality.yaml

@@ -69,6 +69,27 @@ jobs:
       - name: markdownlint
         run: npm run lint:md
 
+  docs:
+    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 documentation links
+        run: npm run docs:validate-links
+
+      - name: Build documentation
+        run: npm run docs:build
+
   validate:
     runs-on: ubuntu-latest
     steps:
@@ -92,6 +113,3 @@ jobs:
 
       - name: Test agent compilation components
         run: npm run test:install
-
-      - name: Validate web bundles
-        run: npm run validate:bundles

.gitignore

@@ -1,12 +1,11 @@
 # Dependencies
-node_modules/
+**/node_modules/
 pnpm-lock.yaml
 bun.lock
 deno.lock
 pnpm-workspace.yaml
 package-lock.json
 
-
 test-output/*
 coverage/
 
@@ -28,11 +27,6 @@ Thumbs.db
 # Development tools and configs
 .prettierrc
 
-# IDE and editor configs
-.windsurf/
-.trae/
-_bmad*/.cursor/
-
 # AI assistant files
 CLAUDE.md
 .ai/*
@@ -43,35 +37,32 @@ CLAUDE.local.md
 .serena/
 .claude/settings.local.json
 
-# Project-specific
-_bmad-core
-_bmad-creator-tools
-test-project-install/*
-sample-project/*
-flattened-codebase.xml
-*.stats.md
-.internal-docs/
-#UAT template testing output files
-tools/template-test-generator/test-scenarios/
-
-# Bundler temporary files and generated bundles
-.bundler-temp/
-
-# 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/
-shared-modules
 z*/
 
 _bmad
+_bmad-output
+.clinerules
+.augment
+.crush
+.cursor
+.iflow
+.opencode
+.qwen
+.rovodev
+.kilocodemodes
 .claude
 .codex
 .github/chatmodes
+.github/agents
 .agent
-.agentvibes/
-.kiro/
+.agentvibes
+.kiro
 .roo
+.trae
+.windsurf
 
-bmad-custom-src/
+
+# Astro / Documentation Build
+website/.astro/
+website/dist/
+build/

.husky/pre-commit

@@ -5,3 +5,16 @@ npx --no-install lint-staged
 
 # Validate everything
 npm test
+
+# Validate docs links only when docs change
+if command -v rg >/dev/null 2>&1; then
+  if git diff --cached --name-only | rg -q '^docs/'; then
+    npm run docs:validate-links
+		npm run docs:build
+  fi
+else
+  if git diff --cached --name-only | grep -Eq '^docs/'; then
+    npm run docs:validate-links
+		npm run docs:build
+  fi
+fi

.markdownlint-cli2.yaml

@@ -2,7 +2,7 @@
 # https://github.com/DavidAnson/markdownlint-cli2
 
 ignores:
-  - node_modules/**
+  - "**/node_modules/**"
   - test/fixtures/**
   - CODE_OF_CONDUCT.md
   - _bmad/**
@@ -11,7 +11,6 @@ ignores:
   - .claude/**
   - .roo/**
   - .codex/**
-  - .agentvibes/**
   - .kiro/**
   - sample-project/**
   - test-project-install/**

.vscode/settings.json

@@ -57,6 +57,7 @@
     "tileset",
     "tmpl",
     "Trae",
+    "Unsharded",
     "VNET",
     "webskip"
   ],

CHANGELOG.md

@@ -1,5 +1,737 @@
 # Changelog
 
+## [6.0.0-Beta.0]
+
+**Release: January 2026 - Alpha to Beta Transition**
+
+### 🎉 Beta Release
+
+- **Transition from Alpha to Beta**: BMad Method is now in Beta! This marks a significant milestone in the framework's development
+- **NPM Default Tag**: Beta versions are now published with the `latest` tag, making `npx bmad-method` serve the beta version by default
+
+### 🌟 Key Highlights
+
+1. **bmad-help**: Revolutionary AI-powered guidance system replaces the alpha workflow-init and workflow tracking — introduces full AI intelligence to guide users through workflows, commands, and project context
+2. **Module Ecosystem Expansion**: bmad-builder, CIS (Creative Intelligence Suite), and Game Dev Studio moved to separate repositories for focused development
+3. **Installer Consolidation**: Unified installer architecture with standardized command naming (`bmad-dash-case.md` or `bmad-*-agent-*.md`)
+4. **Windows Compatibility**: Complete migration from Inquirer.js to @clack/prompts for reliable cross-platform support
+
+### 🚀 Major Features
+
+**bmad-help - Intelligent Guidance System:**
+
+- **Replaces**: workflow-init and legacy workflow tracking
+- **AI-Powered**: Full context awareness of installed modules, workflows, agents, and commands
+- **Dynamic Discovery**: Automatically catalogs all available workflows from installed modules
+- **Intelligent Routing**: Guides users to the right workflow or agent based on their goal
+- **IDE Integration**: Generates proper IDE command files for all discovered workflows
+
+**Module Restructuring:**
+
+| Module                                | Status                                            | New Location                                            |
+| ------------------------------------- | ------------------------------------------------- | ------------------------------------------------------- |
+| **bmad-builder**                      | Near beta, with docs and walkthroughs coming soon | `bmad-code-org/bmad-builder`                            |
+| **CIS** (Creative Intelligence Suite) | Published as npm package                          | `bmad-code-org/bmad-module-creative-intelligence-suite` |
+| **Game Dev Studio**                   | Published as npm package                          | `bmad-code-org/bmad-module-game-dev-studio`             |
+
+### 🔧 Installer & CLI Improvements
+
+**UnifiedInstaller Architecture:**
+
+- All IDE installers now use a common `UnifiedInstaller` class
+- Standardized command naming conventions:
+  - Workflows: `bmad-module-workflow-name.md`
+  - Agents: `bmad-module-agent-name.md`
+  - Tasks: `bmad-task-name.md`
+  - Tools: `bmad-tool-name.md`
+- External module installation from npm with progress indicators
+- Module removal on unselect with confirmation
+
+**Windows Compatibility Fix:**
+
+- Replaced Inquirer.js with @clack/prompts to fix arrow key navigation issues on Windows
+- All 91 installer workflows migrated to new prompt system
+
+### 📚 Documentation Updates
+
+**Significant docsite improvements:**
+
+- Interactive workflow guide page (`/workflow-guide`) with track selector
+- TEA documentation restructured using Diátaxis framework (25 docs)
+- Style guide optimized for LLM readers (367 lines, down from 767)
+- Glossary rewritten using table format (123 lines, down from 373)
+- README overhaul with numbered command flows and prominent `/bmad-help` callout
+- New workflow map diagram with interactive HTML
+- New editorial review tasks for document quality
+- E2E testing methodology for Game Dev Studio
+
+More documentation updates coming soon.
+
+### 🐛 Bug Fixes
+
+- Fixed TodoMVC URL references to include `/dist/` path
+- Fixed glob pattern normalization for Windows compatibility
+- Fixed YAML indentation in kilo.js customInstructions field
+- Fixed stale path references in check-implementation-readiness workflow
+- Fixed sprint-status.yaml sync in correct-course workflow
+- Fixed web bundler entry point reference
+- Fixed mergeModuleHelpCatalogs ordering after generateManifests
+
+### 📊 Statistics
+
+- **91 commits** since alpha.23
+- **969 files changed** (+23,716 / -91,509 lines)
+- **Net reduction of ~67,793 lines** through cleanup and consolidation
+- **3 major modules** moved to separate repositories
+- **Complete installer refactor** for standardization
+
+---
+
+## [6.0.0-alpha.23]
+
+**Release: January 11, 2026**
+
+### 🌟 Key Highlights
+
+1. **Astro/Starlight Documentation Platform**: Complete migration from Docusaurus to modern Astro+Starlight for superior performance and customization
+2. **Diataxis Framework Implementation**: Professional documentation restructuring with tutorials, how-to guides, explanations, and references
+3. **Workflow Creator & Validator**: Powerful new tools for workflow creation with subprocess support and PRD validation
+4. **TEA Documentation Expansion**: Comprehensive testing documentation with cheat sheets, MCP enhancements, and API testing patterns
+5. **Brainstorming Revolution**: Research-backed procedural rigor with 100+ idea goal and anti-bias protocols
+6. **Cursor IDE Modernization**: Refactored from rules-based to command-based architecture for better IDE integration
+
+### 📚 Documentation Platform Revolution
+
+**Astro/Starlight Migration:**
+
+- **From Docusaurus to Astro**: Complete platform migration for improved performance, better customization, and modern tooling
+- **Starlight Theme**: Professional documentation theme with dark mode default and responsive design
+- **Build Pipeline Overhaul**: New build-docs.js orchestrates link checking, artifact generation, and Astro build
+- **LLM-Friendly Documentation**: Generated llms.txt and llms-full.txt for AI agent discoverability
+- **Downloadable Source Bundles**: bmad-sources.zip and bmad-prompts.zip for offline use
+
+**Diataxis Framework Implementation:**
+
+- **Four Content Types**: Professional separation into tutorials, how-to guides, explanations, and references
+- **21 Files Migrated**: Phase 1 migration of core documentation to Diataxis structure
+- **42+ Focused Documents**: Phase 2 split of large legacy files into manageable pieces
+- **FAQ Restructuring**: 7 topic-specific FAQ files with standardized format
+- **Tutorial Style Guide**: Comprehensive documentation standards for consistent content creation
+
+**Link Management & Quality:**
+
+- **Site-Relative Links**: Converted 217 links to repo-relative format (/docs/path/file.md)
+- **Link Validation Tools**: New validate-doc-links.js and fix-doc-links.js for maintaining link integrity
+- **Broken Link Fixes**: Resolved ~50 broken internal links across documentation
+- **BMad Acronym Standardization**: Consistent use of "BMad" (Breakthrough Method of Agile AI Driven Development)
+- **SEO Optimization**: Absolute URLs in AI meta tags for better web crawler discoverability
+
+### 🔧 Workflow Creator & Validator (Major Feature)
+
+**Workflow Creation Tool:**
+
+- **Subprocess Support**: Advanced workflows can now spawn subprocesses for complex operations
+- **PRD Validation Step**: New validation step ensures PRD quality before workflow execution
+- **Trimodal Workflow Creation**: Three-mode workflow generation system
+- **Quadrivariate Module Workflow**: Four-variable workflow architecture for enhanced flexibility
+- **Path Violation Checks**: Validator ensures workflows don't violate path constraints
+- **Max Parallel Mode POC**: Proof-of-concept for parallel workflow validation
+
+**Workflow Quality Improvements:**
+
+- **PRD Trimodal Compliance**: PRD workflow now follows trimodal standards
+- **Standardized Step Formatting**: Consistent markdown formatting across workflow and PRD steps
+- **Better Suggested Next Steps**: Improved workflow completion guidance
+- **Variable Naming Standardization**: {project_root} → {project-root} across all workflows
+
+### 🧪 TEA Documentation Expansion
+
+**Comprehensive Testing Guides:**
+
+- **Cheat Sheets**: Quick reference guides for common testing scenarios
+- **MCP Enhancements**: Model Context Protocol improvements for testing workflows
+- **API Testing Patterns**: Best practices for API testing documentation
+- **Design Philosophy Callout**: Clear explanation of TEA's design principles
+- **Context Engineering Glossary**: New glossary entry defining context engineering concepts
+- **Fragment Count Updates**: Accurate documentation of TEA workflow components
+- **Playwright Utils Examples**: Updated code examples for playwright-utils integration
+
+### 💡 Brainstorming Workflow Overhaul
+
+**Research-Backed Procedural Rigor:**
+
+- **100+ Idea Goal**: Emphasis on quantity-first approach to unlock better quality ideas
+- **Anti-Bias Protocol**: Domain pivot every 10 ideas to reduce cognitive biases
+- **Chain-of-Thought Requirements**: Reasoning before idea generation
+- **Simulated Temperature**: Prompts for higher divergence in ideation
+- **Standardized Idea Format**: Quality control template for consistent output
+- **Energy Checkpoints**: Multiple continuation options to maintain creative flow
+
+**Exploration Menu Improvements:**
+
+- **Letter-Based Navigation**: [K/T/A/B/C] options instead of numbers for clarity
+- **Keep/Try/Advanced/Break/Continue**: Clear action options for idea refinement
+- **Universal Facilitation Rules**: Consistent guidelines across all brainstorming steps
+- **Quality Growth Enforcement**: Balance between quantity and quality metrics
+
+### 🖥️ Cursor IDE Modernization
+
+**Command-Based Architecture:**
+
+- **From Rules to Commands**: Complete refactor from rules-based to command-based system
+- **Command Generation**: Automatic generation of task and tool commands
+- **Commands Directory**: New `.cursor/commands/bmad/` structure for generated commands
+- **Cleanup Integration**: Automatic cleanup of old BMAD commands alongside rules
+- **Enhanced Logging**: Better feedback on agents, tasks, tools, and workflow commands generated
+
+### 🤖 Agent System Improvements
+
+**Agent Builder & Validation:**
+
+- **hasSidecar Field**: All agents now indicate sidecar support (true/false)
+- **Validation Enforcement**: hasSidecar now required in agent validation
+- **Better Brownfield Documentation**: Improved brownfield project documentation
+- **Agent Builder Updates**: Agent builder now uses hasSidecar field
+- **Agent Editor Integration**: Editor workflow respects hasSidecar configuration
+
+### 🐛 Bug Fixes & Quality Improvements
+
+**Critical Fixes:**
+
+- **Windows Line Endings**: Resolved CRLF issues causing cross-platform problems
+- **Code-Review File Filtering**: Fixed code-review picking up non-application files
+- **ERR_REQUIRE_ESM Resolution**: Dynamic import for inquirer v9+ compatibility
+- **Project-Context Conflicts**: Allow full project-context usage with conflict precedence
+- **Workflow Paths**: Fixed paths for workflow and sprint status files
+- **Missing Scripts**: Fixed missing scripts from installation
+
+**Workflow & Variable Fixes:**
+
+- **Variable Naming**: Standardized from {project_root} to {project-root} across CIS, BMGD, and BMM modules
+- **Workflow References**: Fixed broken .yaml → .md workflow references
+- **Advanced Elicitation Variables**: Fixed undefined variables in brainstorming
+- **Dependency Format**: Corrected dependency format and added missing frontmatter
+
+**Code Quality:**
+
+- **Dependency Updates**: Bumped qs from 6.14.0 to 6.14.1
+- **CodeRabbit Integration**: Enabled auto-review on new PRs
+- **TEA Fragment Counts**: Updated fragment counts for accuracy
+- **Documentation Links**: Fixed Discord channel references (#general-dev → #bmad-development)
+
+### 🚀 Installation & CLI Improvements
+
+**Installation Enhancements:**
+
+- **Workflow Exclusion**: Ability to exclude workflows from being added as commands
+- **Example Workflow Protection**: Example workflow in workflow builder now excluded from tools
+- **CNAME Configuration**: Added CNAME file for custom domain support
+- **Script Fixes**: All scripts now properly included in installation
+
+### 📊 Statistics
+
+- **27 commits** since alpha.22
+- **217 documentation links** converted to site-relative format
+- **42+ focused documents** created from large legacy files
+- **7 topic-specific FAQ files** with standardized formatting
+- **Complete documentation platform** migrated from Docusaurus to Astro/Starlight
+- **Major workflow tools** added: Creator, Validator with subprocess support
+- **Brainstorming workflow** overhauled with research-backed rigor
+
+---
+
+## [6.0.0-alpha.22]
+
+**Release: December 31, 2025**
+
+### 🌟 Key Highlights
+
+1. **Unified Agent Workflow**: Create, Edit, and Validate workflows consolidated into single powerful agent workflow with separate step paths
+2. **Agent Knowledge System**: Comprehensive data file architecture with persona properties, validation patterns, and crafting principles
+3. **Deep Language Integration**: All sharded progressive workflows now support language choice at every step
+4. **Core Module Documentation**: Extensive docs for core workflows (brainstorming, party mode, advanced elicitation)
+5. **BMAD Core Concepts**: New documentation structure explaining agents, workflows, modules, and installation
+6. **Tech Spec Sharded**: create-tech-spec workflow converted to sharded format with orient-first pattern
+
+### 🤖 Unified Agent Workflow (Major Feature)
+
+**Consolidated Architecture:**
+
+- **Single Workflow, Three Paths**: Create, Edit, and Validate operations unified under `src/modules/bmb/workflows/agent/`
+- **steps-c/**: Create path with 9 comprehensive steps for building new agents
+- **steps-e/**: Edit path with 10 steps for modifying existing agents
+- **steps-v/**: Validate path for standalone agent validation review
+- **data/**: Centralized knowledge base for all agent-building intel
+
+### 📚 Agent Knowledge System
+
+**Data File Architecture:**
+
+Located in `src/modules/bmb/workflows/agent/data/`:
+
+- **agent-metadata.md** (208 lines) - Complete metadata field reference
+- **agent-menu-patterns.md** (233 lines) - Menu design patterns and best practices
+- **agent-compilation.md** (273 lines) - Compilation process documentation
+- **persona-properties.md** (266 lines) - Persona crafting properties and examples
+- **principles-crafting.md** (292 lines) - Core principles for agent design
+- **critical-actions.md** (120 lines) - Critical action patterns
+- **expert-agent-architecture.md** (236 lines) - Expert agent structure
+- **expert-agent-validation.md** (173 lines) - Expert-specific validation
+- **module-agent-validation.md** (124 lines) - Module-specific validation
+- **simple-agent-architecture.md** (204 lines) - Simple agent structure
+- **simple-agent-validation.md** (132 lines) - Simple agent validation
+- **understanding-agent-types.md** (222 lines) - Agent type comparison
+- **brainstorm-context.md** - Brainstorming guidance
+- **communication-presets.csv** - Communication style presets
+
+**Reference Examples:**
+
+- **reference/module-examples/architect.agent.yaml** - Module agent example
+- **reference/simple-examples/commit-poet.agent.yaml** - Simple agent example
+- **journal-keeper/** - Complete sidecar pattern example
+
+**Templates:**
+
+- **templates/simple-agent.template.md** - Simple agent template
+- **templates/expert-agent-template/expert-agent.template.md** - Expert agent template
+- **templates/expert-agent-sidecar/** - Sidecar templates (instructions, memories)
+
+### 🌍 Deep Language Integration
+
+**Progressive Workflow Language Support:**
+
+- **Every Step Biased**: All sharded progressive workflow steps now include language preference context
+- **260+ Files Updated**: Comprehensive language integration across:
+  - Core workflows (brainstorming, party mode, advanced elicitation)
+  - BMB workflows (create-agent, create-module, create-workflow, edit-workflow, etc.)
+  - BMGD workflows (game-brief, gdd, narrative, game-architecture, etc.)
+  - BMM workflows (research, create-ux-design, prd, create-architecture, etc.)
+- **Tested Languages**: Verified working with Spanish and Pirate Speak
+- **Natural Conversations**: AI agents respond in configured language throughout workflow
+
+### 📖 Core Module Documentation
+
+**New Core Documentation Structure:**
+
+`docs/modules/core/`:
+
+- **index.md** - Core module overview
+- **core-workflows.md** - Core workflow documentation
+- **core-tasks.md** - Core task reference
+- **brainstorming.md** (100 lines) - Brainstorming workflow guide
+- **party-mode.md** (50 lines) - Party mode guide
+- **advanced-elicitation.md** (105 lines) - Advanced elicitation techniques
+- **document-sharding-guide.md** (133 lines) - Sharded workflow format guide
+- **global-core-config.md** - Global core configuration reference
+
+**Advanced Elicitation Moved:**
+
+- **From**: `docs/` root
+- **To**: `src/core/workflows/advanced-elicitation/`
+- **Status**: Now a proper core workflow with methods.csv
+
+### 📚 BMAD Core Concepts Documentation
+
+**New Documentation Structure:**
+
+`docs/bmad-core-concepts/`:
+
+- **index.md** - Core concepts introduction
+- **agents.md** (93 lines) - Understanding agents in BMAD
+- **workflows.md** (89 lines) - Understanding workflows in BMAD
+- **modules.md** (76 lines) - Understanding modules (BMM, BMGD, CIS, BMB, Core)
+- **installing/index.md** (77 lines) - Installation guide
+- **installing/upgrading.md** (144 lines) - Upgrading guide
+- **bmad-customization/index.md** - Customization overview
+- **bmad-customization/agents.md** - Agent customization guide
+- **bmad-customization/workflows.md** (30 lines) - Workflow customization guide
+- **web-bundles/index.md** (34 lines) - Web bundle distribution guide
+
+**Documentation Cleanup:**
+
+- **Removed v4-to-v6-upgrade.md** - Outdated upgrade guide
+- **Removed document-sharding-guide.md** from docs root (moved to core)
+- **Removed web-bundles-gemini-gpt-guide.md** - Consolidated into web-bundles/index.md
+- **Removed getting-started/installation.md** - Migrated to bmad-core-concepts
+- **Removed all ide-info/*.md files** - Consolidated into web-bundles documentation
+
+### 🔧 Create-Tech-Spec Sharded Conversion
+
+**Monolithic to Sharded:**
+
+- **From**: Single `workflow.yaml` with `instructions.md`
+- **To**: Sharded `workflow.md` with individual step files
+- **Pattern**: Orient-first approach (understand before investigating)
+
+### 🔨 Additional Improvements
+
+**Workflow Status Path Fixes:**
+
+- **Corrected Discovery Paths**: workflow-status workflows now properly use planning_artifacts and implementation_artifacts
+- **Updated All Path Files**: enterprise-brownfield, enterprise-greenfield, method-brownfield, method-greenfield
+
+**Documentation Updates:**
+
+- **BMB Agent Creation Guide**: Comprehensive 166-line guide for agent creation
+- **Workflow Vendoring Doc**: New 42-line guide on workflow customization and inheritance
+- **Document Project Reference**: Moved from BMM docs to shared location
+- **Workflows Planning Guide**: New 89-line guide for planning workflows
+
+**BMB Documentation Streamlining:**
+
+- **Removed Redundant Docs**: Eliminated duplicate documentation in `src/modules/bmb/docs/`
+- **Step File Rules**: New 469-line comprehensive guide for step file creation
+- **Agent Docs Moved**: Agent architecture and validation docs moved to workflow data/
+
+**Windows Inquirer Fix:**
+
+- **Another Default Addition**: Additional inquirer default value setting for better Windows multiselection support
+
+**Code Quality:**
+
+- **Removed Old BMM README**: Consolidated module documentation
+- **Removed BMM Troubleshooting**: 661-line doc moved to shared location
+- **Removed Enterprise Agentic Development**: 686-line doc consolidated
+- **Removed Scale Adaptive System**: 618-line doc consolidated
+
+---
+
+## [6.0.0-alpha.21]
+
+**Release: December 27, 2025**
+
+### 🌟 Key Highlights
+
+1. **Consistent Menu System**: All agents now use standardized 2-letter menu codes (e.g., "rd" for research, "ca" for create-architecture)
+2. **Planning Artifacts Architecture**: Phase 1-3 workflows now properly segregate planning artifacts from documentation
+3. **Windows Installer Fixed Again**: Updated inquirer to resolve multiselection tool issues
+4. **Auto-Injected Features**: Chat and party mode automatically injected into all agents
+5. **Validation System**: All agents now pass comprehensive new validation checks
+
+### 🎯 Consistent Menu System (Major Feature)
+
+**Standardized 2-Letter Codes:**
+
+- **Compound Menu Triggers**: All agents now use consistent 2-letter compound trigger format (e.g., `bmm-rd`, `bmm-ca`)
+- **Improved UX**: Shorter, more memorable command shortcuts across all modules
+- **Module Prefixing**: Menu items properly scoped by module prefix (bmm-, bmgd-, cis-, bmb-)
+- **Universal Pattern**: All 22 agents updated to follow the same menu structure
+
+**Agent Updates:**
+
+- **BMM Module**: 9 agents with standardized menus (pm, analyst, architect, dev, ux-designer, tech-writer, sm, tea, quick-flow-solo-dev)
+- **BMGD Module**: 6 agents with standardized menus (game-architect, game-designer, game-dev, game-qa, game-scrum-master, game-solo-dev)
+- **CIS Module**: 6 agents with standardized menus (innovation-strategist, design-thinking-coach, creative-problem-solver, brainstorming-coach, presentation-master, storyteller)
+- **BMB Module**: 3 agents with standardized menus (bmad-builder, agent-builder, module-builder, workflow-builder)
+- **Core Module**: BMAD Master agent updated with consistent menu patterns
+
+### 📁 Planning Artifacts Architecture
+
+**Content Segregation Implementation:**
+
+- **Phase 1-3 Workflows**: All planning workflows now use `planning_artifacts` folder (default changed from `docs`)
+- **Proper Input Discovery**: Workflows follow consistent input discovery patterns from planning artifacts
+- **Output Management**: Planning artifacts properly separated from long-term documentation
+- **Affected Workflows**:
+  - Product Brief: Updated discovery and output to planning artifacts
+  - PRD: Fixed discovery and output to planning artifacts
+  - UX Design: Updated all steps for proper artifact handling
+  - Architecture: Updated discovery and output flow
+  - Game Architecture: Updated for planning artifacts
+  - Story Creation: Updated workflow output paths
+
+**File Organization:**
+
+- **Planning Artifacts**: Ephemeral planning documents (prd.md, product-brief.md, ux-design.md, architecture.md)
+- **Documentation**: Long-term project documentation (separate from planning)
+- **Module Configuration**: BMM and BMGD modules updated with proper default paths
+
+### 🪟 Windows Installer Fixes
+
+**Inquirer Multiselection Fix:**
+
+- **Updated Inquirer Version**: Resolved tool multiselection issues that were causing Windows installer failures
+- **Better Compatibility**: Improved handling of checkbox and multi-select prompts on Windows(?)
+
+### 🤖 Agent System Improvements
+
+**Auto-Injected Features:**
+
+- **Chat Mode**: Automatically injected into all agents during compilation
+- **Party Mode**: Automatically injected into all agents during compilation
+- **Reduced Manual Configuration**: No need to manually add these features to agent definitions
+- **Consistent Behavior**: All agents now have uniform access to chat and party mode capabilities
+
+**Agent Normalization:**
+
+- **All Agents Validated**: All 22 agents pass comprehensive validation checks
+- **Schema Enforcement**: Proper compound trigger validation implemented
+- **Metadata Cleanup**: Removed obsolete and inconsistent metadata patterns
+- **Test Fixtures Updated**: Validation test fixtures aligned with new requirements
+
+### 🔧 Bug Fixes & Cleanup
+
+**Docusaurus Merge Recovery:**
+
+- **Restored Agent Files**: Fixed agent files accidentally modified in Docusaurus merge (PR #1191)
+- **Reference Cleanup**: Removed obsolete agent reference examples (journal-keeper, security-engineer, trend-analyst)
+- **Test Fixture Updates**: Aligned test fixtures with current validation requirements
+
+**Code Quality:**
+
+- **Schema Improvements**: Enhanced agent schema validation with better error messages
+- **Removed Redundancy**: Cleaned up duplicate and obsolete agent definitions
+- **Installer Cleanup**: Removed unused configuration code from BMM installer
+
+**Planning Artifacts Path:**
+- Default: `planning_artifacts/` (configurable in module.yaml)
+- Previous: `docs/`
+- Benefit: Clear separation between planning work and permanent documentation
+
+---
+
+## [6.0.0-alpha.20]
+
+**Release: December 23, 2025**
+
+### 🌟 Key Highlights
+
+1. **Windows Installer Fixed**: Better compatibility with inquirer v9.x upgrade
+2. **Path Segregation**: Revolutionary content organization separating ephemeral artifacts from permanent documentation
+3. **Custom Installation Messages**: Configurable intro/outro messages for professional installation experience
+4. **Enhanced Upgrade Logic**: Two-version auto upgrades with proper config preservation
+5. **Quick-Dev Refactor**: Sharded format with comprehensive adversarial review
+6. **Improved Quality**: Streamlined personas, fixed workflows, and cleaned up documentation
+7. **Doc Site Auto Generation**; Auto Generate a docusaurus site update on merge
+
+### 🪟 Windows Installer (hopefully) Fixed
+
+**Inquirer Upgrade:**
+
+- **Updated to v9.x**: Upgraded inquirer package for better Windows support
+- **Improved Compatibility**: Better handling of Windows terminal environments
+- **Enhanced UX**: More reliable interactive prompts across platforms
+
+### 🎯 Path Segregation Implementation (Major Feature)
+
+**Revolutionary Content Organization:**
+
+- **Phase 1-4 Path Segregation**: Implemented new BM paths across all BMM and BMGD workflows
+- **Planning vs Implementation Artifacts**: Separated ephemeral Phase 4 artifacts from permanent documentation
+- **Optimized File Organization**: Better structure differentiating planning artifacts from long-term project documentation
+- **Backward Compatible**: Existing installations continue working while preparing for optimized content organization
+- **Module Configuration Updates**: Enhanced module.yaml with new path configurations for all phases
+- **Workflow Path Updates**: All 90+ workflow files updated with proper path configurations
+
+**Documentation Cleanup:**
+
+- **Removed Obsolete Documentation**: Cleaned up 3,100+ lines of outdated documentation
+- **Streamlined README Files**: Consolidated and improved module documentation
+- **Enhanced Clarity**: Removed redundant content and improved information architecture
+
+### 💬 Installation Experience Enhancements
+
+**Custom Installation Messages:**
+
+- **Configurable Intro/Outro Messages**: New install-messages.yaml file for customizable installation messages
+- **Professional Installation Flow**: Custom welcome messages and completion notifications
+- **Module-Specific Messaging**: Tailored messages for different installation contexts
+- **Enhanced User Experience**: More informative and personalized installation process
+
+**Core Module Improvements:**
+
+- **Always Ask Questions**: Core module now always prompts for configuration (no accept defaults)
+- **Better User Engagement**: Ensures users actively configure their installation
+- **Improved Configuration Accuracy**: Reduces accidental acceptance of defaults
+
+### 🔧 Upgrade & Configuration Management
+
+**Two-Version Auto Upgrade:**
+
+- **Smarter Upgrade Logic**: Automatic upgrades now span 2 versions (e.g., .16 → .18)
+- **Config Variable Preservation**: Ensures all configuration variables are retained during quick updates
+- **Seamless Updates**: Quick updates now preserve custom settings properly
+- **Enhanced Upgrade Safety**: Better handling of configuration across version boundaries
+
+### 🤖 Workflow Improvements
+
+**Quick-Dev Workflow Refactor (PR #1182):**
+
+- **Sharded Format Conversion**: Converted quick-dev workflow to modern step-file format
+- **Adversarial Review Integration**: Added comprehensive self-check and adversarial review steps
+- **Enhanced Quality Assurance**: 6-step process with mode detection, context gathering, execution, self-check, review, and resolution
+- **578 New Lines Added**: Significant expansion of quick-dev capabilities
+
+**BMGD Workflow Fixes:**
+
+- **workflow-status Filename Correction**: Fixed incorrect filename references (PR #1172)
+- **sprint-planning Update**: Added workflow-status update to game-architecture completion
+- **Path Corrections**: Resolved dead references and syntax errors (PR #1164)
+
+### 🎨 Code Quality & Refactoring
+
+**Persona Streamlining (PR #1167):**
+
+- **Quick-Flow-Solo-Dev Persona**: Streamlined for clarity and accuracy
+- **Improved Agent Behavior**: More focused and efficient solo development support
+
+**Package Management:**
+
+- **package-lock.json Sync**: Ensured version consistency (PR #1168)
+- **Dependency Cleanup**: Reduced package-lock bloat significantly
+
+**Prettier Configuration:**
+
+- **Markdown Underscore Protection**: Prettier will no longer mess up underscores in markdown files
+- **Disabled Auto-Fix**: Markdown formatting issues now handled more intelligently
+- **Better Code Formatting**: Improved handling of special characters in documentation
+
+### 📚 Documentation Updates
+
+**Sponsor Attribution:**
+
+- **DigitalOcean Sponsorship**: Added attribution for DigitalOcean support (PR #1162)
+
+**Content Reorganization:**
+
+- **Removed Unused Docs**: Eliminated obsolete documentation files
+- **Consolidated References**: Merged and reorganized technical references
+- **Enhanced README Files**: Improved module and workflow documentation
+
+### 🧹 Cleanup & Optimization
+
+**File Organization:**
+
+- **Removed Asterisk Insertion**: Eliminated unwanted asterisk insertions into agent files
+- **Removed Unused Commands**: Cleaned up deprecated command references
+- **Consolidated Duplication**: Reduced code duplication across multiple files
+- **Removed Unneeded Folders**: Cleaned up temporary and obsolete directory structures
+
+### 📊 Statistics
+
+- **23 commits** since alpha.19
+- **90+ workflow files** updated with new path configurations
+- **3,100+ lines of documentation** removed and reorganized
+- **578 lines added** to quick-dev workflow with adversarial review
+- **Major architectural improvement** to content organization
+
+## [6.0.0-alpha.19]
+
+**Release: December 18, 2025**
+
+### 🐛 Bug Fixes
+
+**Installer Stability:**
+
+- **Fixed \_bmad Folder Stutter**: Resolved issue with duplicate \_bmad folder creation when applying agent custom files
+- **Cleaner Installation**: Removed unnecessary backup file that was causing bloat in the installer
+- **Streamlined Agent Customization**: Fixed path handling for agent custom files to prevent folder duplication
+
+### 📊 Statistics
+
+- **3 files changed** with critical fix
+- **3,688 lines removed** by eliminating backup files
+- **Improved installer performance** and stability
+
+---
+
+## [6.0.0-alpha.18]
+
+**Release: December 18, 2025**
+
+### 🎮 BMGD Module - Complete Game Development Module Updated
+
+**Massive BMGD Overhaul:**
+
+- **New Game QA Agent (GLaDOS)**: Elite Game QA Architect with test automation specialization
+  - Engine-specific expertise: Unity, Unreal, Godot testing frameworks
+  - Comprehensive knowledge base with 15+ testing topics
+  - Complete testing workflows: test-framework, test-design, automate, playtest-plan, performance-test, test-review
+
+- **New Game Solo Dev Agent (Indie)**: Rapid prototyping and iteration specialist
+  - Quick-flow workflows optimized for solo/small team development
+  - Streamlined development process for indie game creators
+
+- **Production Workflow Alignment**: BMGD 4-production now fully aligned with BMM 4-implementation
+  - Removed obsolete workflows: story-done, story-ready, story-context, epic-tech-context
+  - Added sprint-status workflow for project tracking
+  - All workflows updated as standalone with proper XML instructions
+
+**Game Testing Architecture:**
+
+- **Complete Testing Knowledge Base**: 15 comprehensive testing guides covering:
+  - Engine-specific: Unity (TF 1.6.0), Unreal, Godot testing
+  - Game-specific: Playtesting, balance, save systems, multiplayer
+  - Platform: Certification (TRC/XR), localization, input systems
+  - QA Fundamentals: Automation, performance, regression, smoke testing
+
+**New Workflows & Features:**
+
+- **workflow-status**: Multi-mode status checker for game projects
+  - Game-specific project levels (Game Jam → AAA)
+  - Support for gamedev and quickflow paths
+  - Project initialization workflow
+
+- **create-tech-spec**: Game-focused technical specification workflow
+  - Engine-aware (Unity/Unreal/Godot) specifications
+  - Performance and gameplay feel considerations
+
+- **Enhanced Documentation**: Complete documentation suite with 9 guides
+  - agents-guide.md: Reference for all 6 agents
+  - workflows-guide.md: Complete workflow documentation
+  - game-types-guide.md: 24 game type templates
+  - quick-flow-guide.md: Rapid development guide
+  - Comprehensive troubleshooting and glossary
+
+### 🤖 Agent Management Improved
+
+**Agent Recompile Feature:**
+
+- **New Menu Item**: Added "Recompile Agents" option to the installer menu
+- **Selective Compilation**: Recompile only agents without full module upgrade
+- **Faster Updates**: Quick agent updates without complete reinstallation
+- **Customization Integration**: Automatically applies customizations during recompile
+
+**Agent Customization Enhancement:**
+
+- **Complete Field Support**: ALL fields from agent customization YAML are now properly injected
+- **Deep Merge Implementation**: Customizations now properly override all agent properties
+- **Persistent Customizations**: Custom settings survive updates and recompiles
+- **Enhanced Flexibility**: Support for customizing metadata, persona, menu items, and workflows
+
+### 🔧 Installation & Module Management
+
+**Custom Module Installation:**
+
+- **Enhanced Module Addition**: Modify install now supports adding custom modules even if none were originally installed
+- **Flexible Module Management**: Easy addition and removal of custom modules post-installation
+- **Improved Manifest Tracking**: Better tracking of custom vs core modules
+
+**Quality Improvements:**
+
+- **Comprehensive Code Review**: Fixed 20+ issues identified in PR review
+- **Type Validation**: Added proper type checking for configuration values
+- **Path Security**: Enhanced path traversal validation for better security
+- **Documentation Updates**: All documentation updated to reflect new features
+
+### 📊 Statistics
+
+- **178 files changed** with massive BMGD expansion
+- **28,350+ lines added** across testing documentation and workflows
+- **2 new agents** added to BMGD module
+- **15 comprehensive testing guides** created
+- **Complete alignment** between BMGD and BMM production workflows
+
+### 🌟 Key Highlights
+
+1. **BMGD Module Revolution**: Complete overhaul with professional game development workflows
+2. **Game Testing Excellence**: Comprehensive testing architecture for all major game engines
+3. **Agent Management**: New recompile feature allows quick agent updates without full reinstall
+4. **Full Customization Support**: All agent fields now customizable via YAML
+5. **Industry-Ready Documentation**: Professional-grade guides for game development teams
+
+---
+
 ## [6.0.0-alpha.17]
 
 **Release: December 16, 2025**

CNAME

@@ -0,0 +1 @@
+docs.bmad-method.org

CONTRIBUTING.md

@@ -1,268 +1,167 @@
 # Contributing to BMad
 
-Thank you for considering contributing to the BMad project! We believe in **Human Amplification, Not Replacement** - bringing out the best thinking in both humans and AI through guided collaboration.
+Thank you for considering contributing! We believe in **Human Amplification, Not Replacement** — bringing out the best thinking in both humans and AI through guided collaboration.
 
-💬 **Discord Community**: Join our [Discord server](https://discord.gg/gk8jAdXWmj) for real-time discussions:
+💬 **Discord**: [Join our community](https://discord.gg/gk8jAdXWmj) for real-time discussions, questions, and collaboration.
 
-- **#general-dev** - Technical discussions, feature ideas, and development questions
-- **#bugs-issues** - Bug reports and issue discussions
+---
 
 ## Our Philosophy
 
-### BMad Core™: Universal Foundation
+BMad strengthens human-AI collaboration through specialized agents and guided workflows. Every contribution should answer: **"Does this make humans and AI better together?"**
 
-BMad Core empowers humans and AI agents working together in true partnership across any domain through our **C.O.R.E. Framework** (Collaboration Optimized Reflection Engine):
-
-- **Collaboration**: Human-AI partnership where both contribute unique strengths
-- **Optimized**: The collaborative process refined for maximum effectiveness
-- **Reflection**: Guided thinking that helps discover better solutions and insights
-- **Engine**: The powerful framework that orchestrates specialized agents and workflows
-
-### BMad Method™: Agile AI-Driven Development
-
-The BMad Method is the flagship bmad module for agile AI-driven software development. It emphasizes thorough planning and solid architectural foundations to provide detailed context for developer agents, mirroring real-world agile best practices.
-
-### Core Principles
-
-**Partnership Over Automation** - AI agents act as expert coaches, mentors, and collaborators who amplify human capability rather than replace it.
-
-**Bidirectional Guidance** - Agents guide users through structured workflows while users push agents with advanced prompting. Both sides actively work to extract better information from each other.
-
-**Systems of Workflows** - BMad Core builds comprehensive systems of guided workflows with specialized agent teams for any domain.
-
-**Tool-Agnostic Foundation** - BMad Core remains tool-agnostic, providing stable, extensible groundwork that adapts to any domain.
-
-## What Makes a Good Contribution?
-
-Every contribution should strengthen human-AI collaboration. Ask yourself: **"Does this make humans and AI better together?"**
-
-**✅ Contributions that align:**
-
-- Enhance universal collaboration patterns
-- Improve agent personas and workflows
-- Strengthen planning and context continuity
-- Increase cross-domain accessibility
-- Add domain-specific modules leveraging BMad Core
-
-**❌ What detracts from our mission:**
+**✅ What we welcome:**
+- Enhanced collaboration patterns and workflows
+- Improved agent personas and prompts
+- Domain-specific modules leveraging BMad Core
+- Better planning and context continuity
 
+**❌ What doesn't fit:**
 - Purely automated solutions that sideline humans
-- Tools that don't improve the partnership
 - Complexity that creates barriers to adoption
 - Features that fragment BMad Core's foundation
 
-## Before You Contribute
+---
 
-### Reporting Bugs
+## Reporting Issues
 
-1. **Check existing issues** first to avoid duplicates
-2. **Consider discussing in Discord** (#bugs-issues channel) for quick help
-3. **Use the bug report template** when creating a new issue - it guides you through providing:
-   - Clear bug description
-   - Steps to reproduce
-   - Expected vs actual behavior
-   - Model/IDE/BMad version details
-   - Screenshots or links if applicable
-4. **Indicate if you're working on a fix** to avoid duplicate efforts
+**ALL bug reports and feature requests MUST go through GitHub Issues.**
 
-### Suggesting Features or New Modules
+### Before Creating an Issue
 
-1. **Discuss first in Discord** (#general-dev channel) - the feature request template asks if you've done this
-2. **Check existing issues and discussions** to avoid duplicates
-3. **Use the feature request template** when creating an issue
-4. **Be specific** about why this feature would benefit the BMad community and strengthen human-AI collaboration
+1. **Search existing issues** — Use the GitHub issue search to check if your bug or feature has already been reported
+2. **Search closed issues** — Your issue may have been fixed or addressed previously
+3. **Check discussions** — Some conversations happen in [GitHub Discussions](https://github.com/bmad-code-org/BMAD-METHOD/discussions)
 
-### Before Starting Work
+### Bug Reports
+
+After searching, if the bug is unreported, use the [bug report template](https://github.com/bmad-code-org/BMAD-METHOD/issues/new?template=bug_report.md) and include:
+
+- Clear description of the problem
+- Steps to reproduce
+- Expected vs actual behavior
+- Your environment (model, IDE, BMad version)
+- Screenshots or error messages if applicable
+
+### Feature Requests
+
+After searching, use the [feature request template](https://github.com/bmad-code-org/BMAD-METHOD/issues/new?template=feature_request.md) and explain:
+
+- What the feature is
+- Why it would benefit the BMad community
+- How it strengthens human-AI collaboration
+
+**For community modules**, review [TRADEMARK.md](TRADEMARK.md) for proper naming conventions (e.g., "My Module (BMad Community Module)").
+
+---
+
+## Before Starting Work
 
 ⚠️ **Required before submitting PRs:**
 
-1. **For bugs**: Check if an issue exists (create one using the bug template if not)
-2. **For features**: Discuss in Discord (#general-dev) AND create a feature request issue
-3. **For large changes**: Always open an issue first to discuss alignment
+| Work Type     | Requirement                                    |
+| ------------- | ---------------------------------------------- |
+| Bug fix       | An open issue (create one if it doesn't exist) |
+| Feature       | An open feature request issue                  |
+| Large changes | Discussion via issue first                     |
 
-Please propose small, granular changes! For large or significant changes, discuss in Discord and open an issue first. This prevents wasted effort on PRs that may not align with planned changes.
+**Why?** This prevents wasted effort on work that may not align with project direction.
+
+---
 
 ## Pull Request Guidelines
 
-### Which Branch?
+### Target Branch
 
-**Submit PR's to `main` branch** (critical only):
+Submit PRs to the `main` branch.
 
-- 🚨 Critical bug fixes that break basic functionality
-- 🔒 Security patches
-- 📚 Fixing dangerously incorrect documentation
-- 🐛 Bugs preventing installation or basic usage
+### PR Size
 
-### PR Size Guidelines
+- **Ideal**: 200-400 lines of code changes
+- **Maximum**: 800 lines (excluding generated files)
+- **One feature/fix per PR**
 
-- **Ideal PR size**: 200-400 lines of code changes
-- **Maximum PR size**: 800 lines (excluding generated files)
-- **One feature/fix per PR**: Each PR should address a single issue or add one feature
-- **If your change is larger**: Break it into multiple smaller PRs that can be reviewed independently
-- **Related changes**: Even related changes should be separate PRs if they deliver independent value
+If your change exceeds 800 lines, break it into smaller PRs that can be reviewed independently.
 
-### Breaking Down Large PRs
+### New to Pull Requests?
 
-If your change exceeds 800 lines, use this checklist to split it:
-
-- [ ] Can I separate the refactoring from the feature implementation?
-- [ ] Can I introduce the new API/interface in one PR and implementation in another?
-- [ ] Can I split by file or module?
-- [ ] Can I create a base PR with shared utilities first?
-- [ ] Can I separate test additions from implementation?
-- [ ] Even if changes are related, can they deliver value independently?
-- [ ] Can these changes be merged in any order without breaking things?
-
-Example breakdown:
-
-1. PR #1: Add utility functions and types (100 lines)
-2. PR #2: Refactor existing code to use utilities (200 lines)
-3. PR #3: Implement new feature using refactored code (300 lines)
-4. PR #4: Add comprehensive tests (200 lines)
-
-**Note**: PRs #1 and #4 could be submitted simultaneously since they deliver independent value.
-
-### Pull Request Process
-
-#### New to Pull Requests?
-
-If you're new to GitHub or pull requests, here's a quick guide:
-
-1. **Fork the repository** - Click the "Fork" button on GitHub to create your own copy
-2. **Clone your fork** - `git clone https://github.com/YOUR-USERNAME/bmad-method.git`
-3. **Create a new branch** - Never work on `main` directly!
-   ```bash
-   git checkout -b fix/description
-   # or
-   git checkout -b feature/description
-   ```
-4. **Make your changes** - Edit files, keeping changes small and focused
-5. **Commit your changes** - Use clear, descriptive commit messages
-   ```bash
-   git add .
-   git commit -m "fix: correct typo in README"
-   ```
-6. **Push to your fork** - `git push origin fix/description`
-7. **Create the Pull Request** - Go to your fork on GitHub and click "Compare & pull request"
+1. **Fork** the repository
+2. **Clone** your fork: `git clone https://github.com/YOUR-USERNAME/bmad-method.git`
+3. **Create a branch**: `git checkout -b fix/description` or `git checkout -b feature/description`
+4. **Make changes** — keep them focused
+5. **Commit**: `git commit -m "fix: correct typo in README"`
+6. **Push**: `git push origin fix/description`
+7. **Open PR** from your fork on GitHub
 
 ### PR Description Template
 
-Keep your PR description concise and focused. Use this template:
-
 ```markdown
 ## What
-
 [1-2 sentences describing WHAT changed]
 
 ## Why
-
 [1-2 sentences explaining WHY this change is needed]
-Fixes #[issue number] (if applicable)
+Fixes #[issue number]
 
 ## How
-
-## [2-3 bullets listing HOW you implemented it]
-
--
+- [2-3 bullets listing HOW you implemented it]
 -
 
 ## Testing
-
 [1-2 sentences on how you tested this]
 ```
 
-**Maximum PR description length: 200 words** (excluding code examples if needed)
+**Keep it under 200 words.**
 
-### Good vs Bad PR Descriptions
+### Commit Messages
 
-❌ **Bad Example:**
-
-> This revolutionary PR introduces a paradigm-shifting enhancement to the system's architecture by implementing a state-of-the-art solution that leverages cutting-edge methodologies to optimize performance metrics...
-
-✅ **Good Example:**
-
-> **What:** Added validation for agent dependency resolution
-> **Why:** Build was failing silently when agents had circular dependencies
-> **How:**
->
-> - Added cycle detection in dependency-resolver.js
-> - Throws clear error with dependency chain
->   **Testing:** Tested with circular deps between 3 agents
-
-### Commit Message Convention
-
-Use conventional commits format:
+Use conventional commits:
 
 - `feat:` New feature
 - `fix:` Bug fix
 - `docs:` Documentation only
-- `refactor:` Code change that neither fixes a bug nor adds a feature
-- `test:` Adding missing tests
-- `chore:` Changes to build process or auxiliary tools
+- `refactor:` Code change (no bug/feature)
+- `test:` Adding tests
+- `chore:` Build/tools changes
 
-Keep commit messages under 72 characters.
-
-### Atomic Commits
-
-Each commit should represent one logical change:
-
-- **Do:** One bug fix per commit
-- **Do:** One feature addition per commit
-- **Don't:** Mix refactoring with bug fixes
-- **Don't:** Combine unrelated changes
-
-## What Makes a Good Pull Request?
-
-✅ **Good PRs:**
-
-- Change one thing at a time
-- Have clear, descriptive titles
-- Explain what and why in the description
-- Include only the files that need to change
-- Reference related issue numbers
-
-❌ **Avoid:**
-
-- Changing formatting of entire files
-- Multiple unrelated changes in one PR
-- Copying your entire project/repo into the PR
-- Changes without explanation
-- Working directly on `main` branch
-
-## Common Mistakes to Avoid
-
-1. **Don't reformat entire files** - only change what's necessary
-2. **Don't include unrelated changes** - stick to one fix/feature per PR
-3. **Don't paste code in issues** - create a proper PR instead
-4. **Don't submit your whole project** - contribute specific improvements
-
-## Code Style
-
-- Follow the existing code style and conventions
-- Write clear comments for complex logic
-- Keep dev agents lean - they need context for coding, not documentation
-- 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
-
-By participating in this project, you agree to abide by our Code of Conduct. We foster a collaborative, respectful environment focused on building better human-AI partnerships.
-
-## Need Help?
-
-- 💬 Join our [Discord Community](https://discord.gg/gk8jAdXWmj):
-  - **#general-dev** - Technical questions and feature discussions
-  - **#bugs-issues** - Get help with bugs before filing issues
-- 🐛 Report bugs using the [bug report template](https://github.com/bmad-code-org/BMAD-METHOD/issues/new?template=bug_report.md)
-- 💡 Suggest features using the [feature request template](https://github.com/bmad-code-org/BMAD-METHOD/issues/new?template=feature_request.md)
-- 📖 Browse the [GitHub Discussions](https://github.com/bmad-code-org/BMAD-METHOD/discussions)
+Keep messages under 72 characters. Each commit = one logical change.
 
 ---
 
-**Remember**: We're here to help! Don't be afraid to ask questions. Every expert was once a beginner. Together, we're building a future where humans and AI work better together.
+## What Makes a Good PR?
+
+| ✅ Do                        | ❌ Don't                      |
+| --------------------------- | ---------------------------- |
+| Change one thing per PR     | Mix unrelated changes        |
+| Clear title and description | Vague or missing explanation |
+| Reference related issues    | Reformat entire files        |
+| Small, focused commits      | Copy your whole project      |
+| Work on a branch            | Work directly on `main`      |
+
+---
+
+## Prompt & Agent Guidelines
+
+- Keep dev agents lean — focus on coding context, not documentation
+- Web/planning agents can be larger with complex tasks
+- Everything is natural language (markdown) — no code in core framework
+- Use BMad modules for domain-specific features
+- Validate YAML schemas: `npm run validate:schemas`
+
+---
+
+## Need Help?
+
+- 💬 **Discord**: [Join the community](https://discord.gg/gk8jAdXWmj)
+- 🐛 **Bugs**: Use the [bug report template](https://github.com/bmad-code-org/BMAD-METHOD/issues/new?template=bug_report.md)
+- 💡 **Features**: Use the [feature request template](https://github.com/bmad-code-org/BMAD-METHOD/issues/new?template=feature_request.md)
+
+---
+
+## Code of Conduct
+
+By participating, you agree to abide by our [Code of Conduct](.github/CODE_OF_CONDUCT.md).
 
 ## License
 
-By contributing to this project, you agree that your contributions will be licensed under the same license as the project.
+By contributing, your contributions are licensed under the same MIT License. See [CONTRIBUTORS.md](CONTRIBUTORS.md) for contributor attribution.

CONTRIBUTORS.md

@@ -0,0 +1,32 @@
+# Contributors
+
+BMad Core, BMad Method and BMad and Community BMad Modules are made possible by contributions from our community. We gratefully acknowledge everyone who has helped improve this project.
+
+## How We Credit Contributors
+
+- **Git history** — Every contribution is preserved in the project's commit history
+- **Contributors badge** — See the dynamic contributors list on our [README](README.md)
+- **GitHub contributors graph** — Visual representation at <https://github.com/bmad-code-org/BMAD-METHOD/graphs/contributors>
+
+## Becoming a Contributor
+
+Anyone who submits a pull request that is merged becomes a contributor. Contributions include:
+
+- Bug fixes
+- New features or workflows
+- Documentation improvements
+- Bug reports and issue triaging
+- Code reviews
+- Helping others in discussions
+
+There are no minimum contribution requirements — whether it's a one-character typo fix or a major feature, we value all contributions.
+
+## Copyright
+
+The BMad Method project is copyrighted by BMad Code, LLC. Individual contributions are licensed under the same MIT License as the project. Contributors retain authorship credit through Git history and the contributors graph.
+
+---
+
+**Thank you to everyone who has helped make BMad Method better!**
+
+For contribution guidelines, see [CONTRIBUTING.md](CONTRIBUTING.md).

LICENSE

@@ -2,6 +2,9 @@ MIT License
 
 Copyright (c) 2025 BMad Code, LLC
 
+This project incorporates contributions from the open source community.
+See [CONTRIBUTORS.md](CONTRIBUTORS.md) for contributor attribution.
+
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
 in the Software without restriction, including without limitation the rights
@@ -21,6 +24,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 
 TRADEMARK NOTICE:
-BMad™ , BMAD-CORE™ and BMAD-METHOD™ are trademarks of BMad Code, LLC. The use of these 
-trademarks in this software does not grant any rights to use the trademarks 
-for any other purpose.
+BMad™, BMad Method™, and BMad Core™ are trademarks of BMad Code, LLC, covering all
+casings and variations (including BMAD, bmad, BMadMethod, BMAD-METHOD, etc.). The use of
+these trademarks in this software does not grant any rights to use the trademarks
+for any other purpose. See [TRADEMARK.md](TRADEMARK.md) for detailed guidelines.

README.md

@@ -1,244 +1,118 @@
-# BMad Method & BMad Core
+![BMad Method](banner-bmad-method.png)
 
-[![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)
+[![Version](https://img.shields.io/npm/v/bmad-method?color=blue&label=version)](https://www.npmjs.com/package/bmad-method)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
 [![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)
 
----
+**Breakthrough Method of Agile AI Driven Development** — An AI-driven agile development framework with 21 specialized agents, 50+ guided workflows, and scale-adaptive intelligence that adjusts from bug fixes to enterprise systems.
 
-<div align="center">
+**100% free and open source.** No paywalls. No gated content. No gated Discord. We believe in empowering everyone, not just those who can pay.
 
-## 🎉 NEW: BMAD V6 Installer - Create & Share Custom Content!
+## Why BMad?
 
-The completely revamped **BMAD V6 installer** now includes built-in support for creating, installing, and sharing custom modules, agents, workflows, templates, and tools! Build your own AI solutions or share them with your team - and real soon, with the whole BMad Community througha verified community sharing portal!
+Traditional AI tools do the thinking for you, producing average results. BMad agents and facilitated workflow act as expert collaborators who guide you through a structured process to bring out your best thinking in partnership with the AI.
 
-**✨ What's New:**
+- **AI Intelligent Help**: Brand new for beta - AI assisted help will guide you from the beginning to the end - just ask for `/bmad-help` after you have installed BMad to your project
+- **Scale-Domain-Adaptive**: Automatically adjusts planning depth and needs based on project complexity, domain and type - a SaaS Mobile Dating App has different planning needs from a diagnostic medical system, BMad adapts and helps you along the way
+- **Structured Workflows**: Grounded in agile best practices across analysis, planning, architecture, and implementation
+- **Specialized Agents**: 12+ domain experts (PM, Architect, Developer, UX, Scrum Master, and more)
+- **Party Mode**: Bring multiple agent personas into one session to plan, troubleshoot, or discuss your project collaboratively, multiple perspectives with maximum fun
+- **Complete Lifecycle**: From brainstorming to deployment, BMad is there with you every step of the way
 
-- 📦 **Streamlined Custom Module Installation** - Package your custom content as installable modules
-- 🤖 **Agent & Workflow Sharing** - Distribute standalone agents and workflows
-- 🔄 **Unitary Module Support** - Install individual components without full modules
-- ⚙️ **Dependency Management** - Automatic handling of module dependencies
-- 🛡️ **Update-Safe Customization** - Your custom content persists through updates
+## Quick Start
 
-**📚 Learn More:**
-
-- [**Custom Content Overview**](./docs/custom-content.md) - Discover all supported content types
-- [**Installation Guide**](./docs/custom-content-installation.md) - Learn to create and install custom content
-- [**Detail Content Docs**](./src/modules/bmb/docs/README.md) - Reference details for agents, modules, workflows and the bmad builder
-- [**2 Very simple Custom Modules of questionable quality**](./docs/sample-custom-modules/README.md) - if you want to download and try to install a custom shared module, get an idea of how to bundle and share your own, or create your own personal agents, workflows and modules.
-
-</div>
-
----
-
-## AI-Driven Agile Development That Scales From Bug Fixes to Enterprise
-
-**Build More, Architect Dreams** (BMAD) with **21 specialized AI agents** across 4 official modules, and **50+ guided workflows** that adapt to your project's complexity—from quick bug fixes to enterprise platforms, and new step file workflows that allow for incredibly long workflows to stay on the rails longer than ever before!
-
-Additionally - when we say 'Build More, Architect Dreams' - we mean it! The BMad Builder has landed, and now as of Alpha.15 is fully supported in the installation flow via NPX - custom stand along agents, workflows and the modules of your dreams! The community forge will soon open, endless possibility awaits!
-
-> **🚀 v6 is a MASSIVE upgrade from v4!** Complete architectural overhaul, scale-adaptive intelligence, visual workflows, and the powerful BMad Core framework. v4 users: this changes everything. [See what's new →](#whats-new-in-v6)
-
-> **📌 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).
-
-## 🎯 Why BMad Method?
-
-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.
-
-**✨ Key Benefits:**
-
-- **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
-
-## 🏗️ The Power of BMad Core
-
-**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** 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
-
-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!
-
-## 📊 See It In Action
-
-<p align="center">
-  <img src="./src/modules/bmm/docs/images/workflow-method-greenfield.svg" alt="BMad Method Workflow" width="100%">
-</p>
-
-<p align="center">
-  <em>Complete BMad Method workflow showing all phases, agents, and decision points</em>
-</p>
-
-## 🚀 Get Started in 3 Steps
-
-### 1. Install BMad Method
+**Prerequisites**: [Node.js](https://nodejs.org) v20+
 
 ```bash
-# Install v6 Alpha (recommended)
-npx bmad-method@alpha install
-
-# Or stable v4 for production
 npx bmad-method install
 ```
 
-### 2. Initialize Your Project
+Follow the installer prompts, then open your AI IDE (Claude Code, Cursor, Windsurf, etc.) in the project folder.
 
-Load any agent in your IDE and run:
+> **Not sure what to do?** Run `/bmad-help` — it tells you exactly what's next and what's optional. You can also ask it questions like:
 
-```
-*workflow-init
-```
+ - `/bmad-help How should I build a web app for for my TShirt Business that can scale to millions?`
+ - `/bmad-help I just finished the architecture, I am not sure what to do next`
 
-This analyzes your project and recommends the right workflow track.
+And the amazing this is BMad Help evolves depending on what modules you install also!
+ - `/bmad-help Im interested in really exploring creative ways to demo BMad at work, what do you recommend to help plan a great slide deck and compelling narrative?`, and if you have the Creative Intelligence Suite installed, it will offer you different or complimentary advice than if you just have BMad Method Module installed!
 
-### 3. Choose Your Track
+The workflows below show the fastest path to working code. You can also load agents directly for a more structured process, extensive planning, or to learn about agile development practices — the agents guide you with menus, explanations, and elicitation at each step.
 
-BMad Method adapts to your needs with three intelligent tracks:
+### Simple Path (Quick Flow)
 
-| 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  |
+Bug fixes, small features, clear scope — 3 commands - 1 Optional Agent:
 
-> **Not sure?** Run `*workflow-init` and let BMad analyze your project goal.
+1. `/quick-spec` — analyzes your codebase and produces a tech-spec with stories
+2. `/dev-story` — implements each story
+3. `/code-review` — validates quality
 
-## 🔄 How It Works: 4-Phase Methodology
+### Full Planning Path (BMad Method)
 
-BMad Method guides you through a proven development lifecycle:
+Products, platforms, complex features — structured planning then build:
 
-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
+1. `/product-brief` — define problem, users, and MVP scope
+2. `/create-prd` — full requirements with personas, metrics, and risks
+3. `/create-architecture` — technical decisions and system design
+4. `/create-epics-and-stories` — break work into prioritized stories
+5. `/sprint-planning` — initialize sprint tracking
+6. **Repeat per story:** `/create-story` → `/dev-story` → `/code-review`
 
-Each phase has specialized workflows and agents working together to deliver exceptional results.
+Every step tells you what's next. Optional phases (brainstorming, research, UX design) are available when you need them — ask `/bmad-help` anytime. For a detailed walkthrough, see the [Getting Started Tutorial](http://docs.bmad-method.org/tutorials/getting-started/getting-started-bmadv6/).
 
-## 🤖 Meet Your Team
+## Modules
 
-**12 Specialized Agents** working in concert:
+BMad Method extends with official modules for specialized domains. Modules are available during installation and can be added to your project at any time. After the V6 beta period these will also be available as Plugins and Granular Skills.
 
-| Development | Architecture   | Product       | Leadership     |
-| ----------- | -------------- | ------------- | -------------- |
-| Developer   | Architect      | PM            | Scrum Master   |
-| UX Designer | Test Architect | Analyst       | BMad Master    |
-| Tech Writer | Game Architect | Game Designer | Game Developer |
+| Module                                | GitHub                                                                                                                            | NPM                                                                                                | Purpose                                                           |
+| ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- |
+| **BMad Method (BMM)**                 | [bmad-code-org/BMAD-METHOD](https://github.com/bmad-code-org/BMAD-METHOD)                                                         | [bmad-method](https://www.npmjs.com/package/bmad-method)                                           | Core framework with 34+ workflows across 4 development phases     |
+| **BMad Builder (BMB)**                | [bmad-code-org/bmad-builder](https://github.com/bmad-code-org/bmad-builder)                                                       | [bmad-builder](https://www.npmjs.com/package/bmad-builder)                                         | Create custom BMad agents, workflows, and domain-specific modules |
+| **Game Dev Studio (BMGD)**            | [bmad-code-org/bmad-module-game-dev-studio](https://github.com/bmad-code-org/bmad-module-game-dev-studio)                         | [bmad-game-dev-studio](https://www.npmjs.com/package/bmad-game-dev-studio)                         | Game development workflows for Unity, Unreal, and Godot           |
+| **Creative Intelligence Suite (CIS)** | [bmad-code-org/bmad-module-creative-intelligence-suite](https://github.com/bmad-code-org/bmad-module-creative-intelligence-suite) | [bmad-creative-intelligence-suite](https://www.npmjs.com/package/bmad-creative-intelligence-suite) | Innovation, brainstorming, design thinking, and problem-solving   |
 
-**Test Architect** integrates with `@seontechnologies/playwright-utils` for production-ready fixture-based utilities.
+* More modules are coming in the next 2 weeks from BMad Official, and a community marketplace for the installer also will be coming with the final V6 release!
 
-Each agent brings deep expertise and can be customized to match your team's style.
+## Documentation
 
-## 📦 What's Included
+**[Full Documentation](http://docs.bmad-method.org)** — Tutorials, how-to guides, concepts, and reference
 
-### Core Modules
-
-- **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)
-
-- **BMad Builder (BMB)** - Create custom agents and workflows
-  - Build anything from simple agents to complex modules
-  - Create domain-specific solutions (legal, medical, finance, education)
-  - [→ Builder Guide](src/modules/bmb/docs/README.md) marketplace
-  - [→ Builder Guide](./src/modules/bmb/README.md)
-
-- **Creative Intelligence Suite (CIS)** - Innovation & problem-solving
-  - Brainstorming, design thinking, storytelling
-  - 5 creative facilitation workflows
-  - [→ Creative Workflows](./src/modules/cis/README.md)
-
-### Key Features
-
-- **🎨 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
+- [Getting Started Tutorial](http://docs.bmad-method.org/tutorials/getting-started/getting-started-bmadv6/)
+- [Upgrading from Previous Versions](http://docs.bmad-method.org/how-to/installation/upgrade-to-v6/)
 
 ### 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)**
+- **[v4 Documentation](https://github.com/bmad-code-org/BMAD-METHOD/tree/V4/docs)**
 
-## 💬 Community & Support
+## Community
 
-- **[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
-- **[Code of Conduct](.github/CODE_OF_CONDUCT.md)** - Community guidelines
+- [Discord](https://discord.gg/gk8jAdXWmj) — Get help, share ideas, collaborate
+- [Subscribe on YouTube](https://www.youtube.com/@BMadCode) — Tutorials, master class, and podcast (launching Feb 2025)
+- [GitHub Issues](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
 
-## 🛠️ Development
+## Support BMad
 
-For contributors working on the BMad codebase:
+BMad is free for everyone — and always will be. If you'd like to support development:
 
-```bash
-# Run all quality checks
-npm test
+- ⭐ Please click the star project icon at near the top right of this page
+- ☕ [Buy Me a Coffee](https://buymeacoffee.com/bmad) — Fuel the development
+- 🏢 Corporate sponsorship — DM on Discord
+- 🎤 Speaking & Media — Available for conferences, podcasts, interviews (BM on Discord)
 
-# Development commands
-npm run lint:fix      # Fix code style
-npm run format:fix    # Auto-format code
-npm run bundle        # Build web bundles
-```
+## Contributing
 
-See [CONTRIBUTING.md](CONTRIBUTING.md) for full development guidelines.
+We welcome contributions! See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines.
 
-## What's New in v6
+## License
 
-**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.
+MIT License — see [LICENSE](LICENSE) for details.
 
 ---
 
-<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>
+**BMad** and **BMAD-METHOD** are trademarks of BMad Code, LLC. See [TRADEMARK.md](TRADEMARK.md) for details.
 
-<p align="center">
-  <sub>Built with ❤️ for the human-AI collaboration community</sub>
-</p>
+[![Contributors](https://contrib.rocks/image?repo=bmad-code-org/BMAD-METHOD)](https://github.com/bmad-code-org/BMAD-METHOD/graphs/contributors)
+
+See [CONTRIBUTORS.md](CONTRIBUTORS.md) for contributor information.

SECURITY.md

@@ -0,0 +1,85 @@
+# Security Policy
+
+## Supported Versions
+
+We release security patches for the following versions:
+
+| Version | Supported          |
+| ------- | ------------------ |
+| Latest  | :white_check_mark: |
+| < Latest | :x:               |
+
+We recommend always using the latest version of BMad Method to ensure you have the most recent security updates.
+
+## Reporting a Vulnerability
+
+We take security vulnerabilities seriously. If you discover a security issue, please report it responsibly.
+
+### How to Report
+
+**Do NOT report security vulnerabilities through public GitHub issues.**
+
+Instead, please report them via one of these methods:
+
+1. **GitHub Security Advisories** (Preferred): Use [GitHub's private vulnerability reporting](https://github.com/bmad-code-org/BMAD-METHOD/security/advisories/new) to submit a confidential report.
+
+2. **Discord**: Contact a maintainer directly via DM on our [Discord server](https://discord.gg/gk8jAdXWmj).
+
+### What to Include
+
+Please include as much of the following information as possible:
+
+- Type of vulnerability (e.g., prompt injection, path traversal, etc.)
+- Full paths of source file(s) related to the vulnerability
+- Step-by-step instructions to reproduce the issue
+- Proof-of-concept or exploit code (if available)
+- Impact assessment of the vulnerability
+
+### Response Timeline
+
+- **Initial Response**: Within 48 hours of receiving your report
+- **Status Update**: Within 7 days with our assessment
+- **Resolution Target**: Critical issues within 30 days; other issues within 90 days
+
+### What to Expect
+
+1. We will acknowledge receipt of your report
+2. We will investigate and validate the vulnerability
+3. We will work on a fix and coordinate disclosure timing with you
+4. We will credit you in the security advisory (unless you prefer to remain anonymous)
+
+## Security Scope
+
+### In Scope
+
+- Vulnerabilities in BMad Method core framework code
+- Security issues in agent definitions or workflows that could lead to unintended behavior
+- Path traversal or file system access issues
+- Prompt injection vulnerabilities that bypass intended agent behavior
+- Supply chain vulnerabilities in dependencies
+
+### Out of Scope
+
+- Security issues in user-created custom agents or modules
+- Vulnerabilities in third-party AI providers (Claude, GPT, etc.)
+- Issues that require physical access to a user's machine
+- Social engineering attacks
+- Denial of service attacks that don't exploit a specific vulnerability
+
+## Security Best Practices for Users
+
+When using BMad Method:
+
+1. **Review Agent Outputs**: Always review AI-generated code before executing it
+2. **Limit File Access**: Configure your AI IDE to limit file system access where possible
+3. **Keep Updated**: Regularly update to the latest version
+4. **Validate Dependencies**: Review any dependencies added by generated code
+5. **Environment Isolation**: Consider running AI-assisted development in isolated environments
+
+## Acknowledgments
+
+We appreciate the security research community's efforts in helping keep BMad Method secure. Contributors who report valid security issues will be acknowledged in our security advisories.
+
+---
+
+Thank you for helping keep BMad Method and our community safe.

TRADEMARK.md

@@ -0,0 +1,55 @@
+# Trademark Notice & Guidelines
+
+## Trademark Ownership
+
+The following names and logos are trademarks of BMad Code, LLC:
+
+- **BMad** (word mark, all casings: BMad, bmad, BMAD)
+- **BMad Method** (word mark, includes BMadMethod, BMAD-METHOD, and all variations)
+- **BMad Core** (word mark, includes BMadCore, BMAD-CORE, and all variations)
+- **BMad Code** (word mark)
+- BMad Method logo and visual branding
+- The "Build More, Architect Dreams" tagline
+
+**All casings, stylings, and variations** of the above names (with or without hyphens, spaces, or specific capitalization) are covered by these trademarks.
+
+These trademarks are protected under trademark law and are **not** licensed under the MIT License. The MIT License applies to the software code only, not to the BMad brand identity.
+
+## What This Means
+
+You may:
+
+- Use the BMad software under the terms of the MIT License
+- Refer to BMad to accurately describe compatibility or integration (e.g., "Compatible with BMad Method v6")
+- Link to <https://github.com/bmad-code-org/BMAD-METHOD>
+- Fork the software and distribute your own version under a different name
+
+You may **not**:
+
+- Use "BMad" or any confusingly similar variation as your product name, service name, company name, or domain name
+- Present your product as officially endorsed, approved, or certified by BMad Code, LLC when it is not, without written consent from an authorized representative of BMad Code, LLC
+- Use BMad logos or branding in a way that suggests your product is an official or endorsed BMad product
+- Register domain names, social media handles, or trademarks that incorporate BMad branding
+
+## Examples
+
+| Permitted                                              | Not Permitted                                |
+| ------------------------------------------------------ | -------------------------------------------- |
+| "My workflow tool, compatible with BMad Method"        | "BMadFlow" or "BMad Studio"                  |
+| "An alternative implementation inspired by BMad"       | "BMad Pro" or "BMad Enterprise"              |
+| "My Awesome Healthcare Module (Bmad Community Module)" | "The Official BMad Core Healthcare Module"   |
+| Accurately stating you use BMad as a dependency        | Implying official endorsement or partnership |
+
+## Commercial Use
+
+You may sell products that incorporate or work with BMad software. However:
+
+- Your product must have its own distinct name and branding
+- You must not use BMad trademarks in your marketing, domain names, or product identity
+- You may truthfully describe technical compatibility (e.g., "Works with BMad Method")
+
+## Questions?
+
+If you have questions about trademark usage or would like to discuss official partnership or endorsement opportunities, please reach out:
+
+- **Email**: <contact@bmadcode.com>

docs/404.md

@@ -0,0 +1,9 @@
+---
+title: Page Not Found
+template: splash
+---
+
+
+The page you're looking for doesn't exist or has been moved.
+
+[Return to Home](/docs/index.md)

docs/_STYLE_GUIDE.md

@@ -0,0 +1,367 @@
+---
+title: "Documentation Style Guide"
+---
+
+This project adheres to the [Google Developer Documentation Style Guide](https://developers.google.com/style) and uses [Diataxis](https://diataxis.fr/) to structure content. Only project-specific conventions follow.
+
+## Project-Specific Rules
+
+| Rule                             | Specification                            |
+| -------------------------------- | ---------------------------------------- |
+| No horizontal rules (`---`)      | Fragments reading flow                   |
+| No `####` headers                | Use bold text or admonitions instead     |
+| No "Related" or "Next:" sections | Sidebar handles navigation               |
+| No deeply nested lists           | Break into sections instead              |
+| No code blocks for non-code      | Use admonitions for dialogue examples    |
+| No bold paragraphs for callouts  | Use admonitions instead                  |
+| 1-2 admonitions per section max  | Tutorials allow 3-4 per major section    |
+| Table cells / list items         | 1-2 sentences max                        |
+| Header budget                    | 8-12 `##` per doc; 2-3 `###` per section |
+
+## Admonitions (Starlight Syntax)
+
+```md
+:::tip[Title]
+Shortcuts, best practices
+:::
+
+:::note[Title]
+Context, definitions, examples, prerequisites
+:::
+
+:::caution[Title]
+Caveats, potential issues
+:::
+
+:::danger[Title]
+Critical warnings only — data loss, security issues
+:::
+```
+
+### Standard Uses
+
+| Admonition               | Use For                       |
+| ------------------------ | ----------------------------- |
+| `:::note[Prerequisites]` | Dependencies before starting  |
+| `:::tip[Quick Path]`     | TL;DR summary at document top |
+| `:::caution[Important]`  | Critical caveats              |
+| `:::note[Example]`       | Command/response examples     |
+
+## Standard Table Formats
+
+**Phases:**
+
+```md
+| Phase | Name     | What Happens                                 |
+| ----- | -------- | -------------------------------------------- |
+| 1     | Analysis | Brainstorm, research *(optional)*            |
+| 2     | Planning | Requirements — PRD or tech-spec *(required)* |
+```
+
+**Commands:**
+
+```md
+| Command      | Agent   | Purpose                              |
+| ------------ | ------- | ------------------------------------ |
+| `brainstorm` | Analyst | Brainstorm a new project             |
+| `prd`        | PM      | Create Product Requirements Document |
+```
+
+## Folder Structure Blocks
+
+Show in "What You've Accomplished" sections:
+
+````md
+```
+your-project/
+├── _bmad/                         # BMad configuration
+├── _bmad-output/
+│   ├── PRD.md                     # Your requirements document
+│   └── bmm-workflow-status.yaml   # Progress tracking
+└── ...
+```
+````
+
+## Tutorial Structure
+
+```text
+1. Title + Hook (1-2 sentences describing outcome)
+2. Version/Module Notice (info or warning admonition) (optional)
+3. What You'll Learn (bullet list of outcomes)
+4. Prerequisites (info admonition)
+5. Quick Path (tip admonition - TL;DR summary)
+6. Understanding [Topic] (context before steps - tables for phases/agents)
+7. Installation (optional)
+8. Step 1: [First Major Task]
+9. Step 2: [Second Major Task]
+10. Step 3: [Third Major Task]
+11. What You've Accomplished (summary + folder structure)
+12. Quick Reference (commands table)
+13. Common Questions (FAQ format)
+14. Getting Help (community links)
+15. Key Takeaways (tip admonition)
+```
+
+### Tutorial Checklist
+
+- [ ] Hook describes outcome in 1-2 sentences
+- [ ] "What You'll Learn" section present
+- [ ] Prerequisites in admonition
+- [ ] Quick Path TL;DR admonition at top
+- [ ] Tables for phases, commands, agents
+- [ ] "What You've Accomplished" section present
+- [ ] Quick Reference table present
+- [ ] Common Questions section present
+- [ ] Getting Help section present
+- [ ] Key Takeaways admonition at end
+
+## How-To Structure
+
+```text
+1. Title + Hook (one sentence: "Use the `X` workflow to...")
+2. When to Use This (bullet list of scenarios)
+3. When to Skip This (optional)
+4. Prerequisites (note admonition)
+5. Steps (numbered ### subsections)
+6. What You Get (output/artifacts produced)
+7. Example (optional)
+8. Tips (optional)
+9. Next Steps (optional)
+```
+
+### How-To Checklist
+
+- [ ] Hook starts with "Use the `X` workflow to..."
+- [ ] "When to Use This" has 3-5 bullet points
+- [ ] Prerequisites listed
+- [ ] Steps are numbered `###` subsections with action verbs
+- [ ] "What You Get" describes output artifacts
+
+## Explanation Structure
+
+### Types
+
+| Type              | Example                      |
+| ----------------- | ---------------------------- |
+| **Index/Landing** | `core-concepts/index.md`     |
+| **Concept**       | `what-are-agents.md`         |
+| **Feature**       | `quick-flow.md`              |
+| **Philosophy**    | `why-solutioning-matters.md` |
+| **FAQ**           | `brownfield-faq.md`          |
+
+### General Template
+
+```text
+1. Title + Hook (1-2 sentences)
+2. Overview/Definition (what it is, why it matters)
+3. Key Concepts (### subsections)
+4. Comparison Table (optional)
+5. When to Use / When Not to Use (optional)
+6. Diagram (optional - mermaid, 1 per doc max)
+7. Next Steps (optional)
+```
+
+### Index/Landing Pages
+
+```text
+1. Title + Hook (one sentence)
+2. Content Table (links with descriptions)
+3. Getting Started (numbered list)
+4. Choose Your Path (optional - decision tree)
+```
+
+### Concept Explainers
+
+```text
+1. Title + Hook (what it is)
+2. Types/Categories (### subsections) (optional)
+3. Key Differences Table
+4. Components/Parts
+5. Which Should You Use?
+6. Creating/Customizing (pointer to how-to guides)
+```
+
+### Feature Explainers
+
+```text
+1. Title + Hook (what it does)
+2. Quick Facts (optional - "Perfect for:", "Time to:")
+3. When to Use / When Not to Use
+4. How It Works (mermaid diagram optional)
+5. Key Benefits
+6. Comparison Table (optional)
+7. When to Graduate/Upgrade (optional)
+```
+
+### Philosophy/Rationale Documents
+
+```text
+1. Title + Hook (the principle)
+2. The Problem
+3. The Solution
+4. Key Principles (### subsections)
+5. Benefits
+6. When This Applies
+```
+
+### Explanation Checklist
+
+- [ ] Hook states what document explains
+- [ ] Content in scannable `##` sections
+- [ ] Comparison tables for 3+ options
+- [ ] Diagrams have clear labels
+- [ ] Links to how-to guides for procedural questions
+- [ ] 2-3 admonitions max per document
+
+## Reference Structure
+
+### Types
+
+| Type              | Example               |
+| ----------------- | --------------------- |
+| **Index/Landing** | `workflows/index.md`  |
+| **Catalog**       | `agents/index.md`     |
+| **Deep-Dive**     | `document-project.md` |
+| **Configuration** | `core-tasks.md`       |
+| **Glossary**      | `glossary/index.md`   |
+| **Comprehensive** | `bmgd-workflows.md`   |
+
+### Reference Index Pages
+
+```text
+1. Title + Hook (one sentence)
+2. Content Sections (## for each category)
+   - Bullet list with links and descriptions
+```
+
+### Catalog Reference
+
+```text
+1. Title + Hook
+2. Items (## for each item)
+   - Brief description (one sentence)
+   - **Commands:** or **Key Info:** as flat list
+3. Universal/Shared (## section) (optional)
+```
+
+### Item Deep-Dive Reference
+
+```text
+1. Title + Hook (one sentence purpose)
+2. Quick Facts (optional note admonition)
+   - Module, Command, Input, Output as list
+3. Purpose/Overview (## section)
+4. How to Invoke (code block)
+5. Key Sections (## for each aspect)
+   - Use ### for sub-options
+6. Notes/Caveats (tip or caution admonition)
+```
+
+### Configuration Reference
+
+```text
+1. Title + Hook
+2. Table of Contents (jump links if 4+ items)
+3. Items (## for each config/task)
+   - **Bold summary** — one sentence
+   - **Use it when:** bullet list
+   - **How it works:** numbered steps (3-5 max)
+   - **Output:** expected result (optional)
+```
+
+### Comprehensive Reference Guide
+
+```text
+1. Title + Hook
+2. Overview (## section)
+   - Diagram or table showing organization
+3. Major Sections (## for each phase/category)
+   - Items (### for each item)
+   - Standardized fields: Command, Agent, Input, Output, Description
+4. Next Steps (optional)
+```
+
+### Reference Checklist
+
+- [ ] Hook states what document references
+- [ ] Structure matches reference type
+- [ ] Items use consistent structure throughout
+- [ ] Tables for structured/comparative data
+- [ ] Links to explanation docs for conceptual depth
+- [ ] 1-2 admonitions max
+
+## Glossary Structure
+
+Starlight generates right-side "On this page" navigation from headers:
+
+- Categories as `##` headers — appear in right nav
+- Terms in tables — compact rows, not individual headers
+- No inline TOC — right sidebar handles navigation
+
+### Table Format
+
+```md
+## Category Name
+
+| Term         | Definition                                                                               |
+| ------------ | ---------------------------------------------------------------------------------------- |
+| **Agent**    | Specialized AI persona with specific expertise that guides users through workflows.      |
+| **Workflow** | Multi-step guided process that orchestrates AI agent activities to produce deliverables. |
+```
+
+### Definition Rules
+
+| Do                            | Don't                                       |
+| ----------------------------- | ------------------------------------------- |
+| Start with what it IS or DOES | Start with "This is..." or "A [term] is..." |
+| Keep to 1-2 sentences         | Write multi-paragraph explanations          |
+| Bold term name in cell        | Use plain text for terms                    |
+
+### Context Markers
+
+Add italic context at definition start for limited-scope terms:
+
+- `*Quick Flow only.*`
+- `*BMad Method/Enterprise.*`
+- `*Phase N.*`
+- `*BMGD.*`
+- `*Brownfield.*`
+
+### Glossary Checklist
+
+- [ ] Terms in tables, not individual headers
+- [ ] Terms alphabetized within categories
+- [ ] Definitions 1-2 sentences
+- [ ] Context markers italicized
+- [ ] Term names bolded in cells
+- [ ] No "A [term] is..." definitions
+
+## FAQ Sections
+
+```md
+## Questions
+
+- [Do I always need architecture?](#do-i-always-need-architecture)
+- [Can I change my plan later?](#can-i-change-my-plan-later)
+
+### Do I always need architecture?
+
+Only for BMad Method and Enterprise tracks. Quick Flow skips to implementation.
+
+### Can I change my plan later?
+
+Yes. The SM agent has a `correct-course` workflow for handling scope changes.
+
+**Have a question not answered here?** [Open an issue](...) or ask in [Discord](...).
+```
+
+## Validation Commands
+
+Before submitting documentation changes:
+
+```bash
+npm run docs:fix-links            # Preview link format fixes
+npm run docs:fix-links -- --write # Apply fixes
+npm run docs:validate-links       # Check links exist
+npm run docs:build                # Verify no build errors
+```

docs/agent-customization-guide.md

@@ -1,208 +0,0 @@
-# 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/_config/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/_config/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/_config/agents/bmm-dev.customize.yaml
-menu:
-  - trigger: deploy-staging
-    workflow: '{project-root}/_bmad/deploy-staging.yaml'
-    description: Deploy to staging environment
-  - trigger: deploy-prod
-    workflow: '{project-root}/_bmad/deploy-prod.yaml'
-    description: Deploy to production (with approval)
-```
-
-**Example 3: Multilingual Product Manager**
-
-```yaml
-# _bmad/_config/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 `_config/` survive all BMad updates
-- **Per-Project:** Customization files are per-project, not global
-- **Version Control:** Consider committing `_config/` to share customizations with your team
-
-## Module vs. Global Config
-
-**Module-Level (Recommended):**
-
-- Customize agents per-project in `_bmad/_config/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 the BMad Method agents
-- **[BMB Create Agent Workflow](../src/modules/bmb/workflows/create-agent/README.md)** - Build completely custom agents
-- **[BMM Complete Documentation](../src/modules/bmm/docs/README.md)** - Full BMad Method reference

docs/custom-content-installation.md

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

docs/custom-content.md

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

docs/document-sharding-guide.md

@@ -1,449 +0,0 @@
-# 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!

docs/downloads.md

@@ -0,0 +1,74 @@
+---
+title: Downloads
+---
+
+Download BMad Method resources for offline use, AI training, or integration.
+
+## Source Bundles
+
+Download these from the `downloads/` folder on the documentation site.
+
+| File               | Description                     |
+| ------------------ | ------------------------------- |
+| `bmad-sources.zip` | Complete BMad source files      |
+| `bmad-prompts.zip` | Agent and workflow prompts only |
+
+## LLM-Optimized Files
+
+These files are designed for AI consumption - perfect for loading into Claude, ChatGPT, or any LLM context window. See [API Access](#api-access) below for URLs.
+
+| File            | Description                         | Use Case                   |
+| --------------- | ----------------------------------- | -------------------------- |
+| `llms.txt`      | Documentation index with summaries  | Quick overview, navigation |
+| `llms-full.txt` | Complete documentation concatenated | Full context loading       |
+
+### Using with LLMs
+
+**Claude Projects:**
+```
+Upload llms-full.txt as project knowledge
+```
+
+**ChatGPT:**
+```
+Paste llms.txt for navigation, or sections from llms-full.txt as needed
+```
+
+**API Usage:**
+```python
+import requests
+docs = requests.get("https://bmad-code-org.github.io/BMAD-METHOD/llms-full.txt").text
+# Include in your system prompt or context
+```
+
+## Installation Options
+
+```bash
+npx bmad-method install
+```
+
+[More details](/docs/how-to/install-bmad.md)
+
+## Version Information
+
+- **Current Version:** See [CHANGELOG](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/CHANGELOG.md)
+- **Release Notes:** Available on [GitHub Releases](https://github.com/bmad-code-org/BMAD-METHOD/releases)
+
+## API Access
+
+For programmatic access to BMad documentation:
+
+```bash
+# Get documentation index
+curl https://bmad-code-org.github.io/BMAD-METHOD/llms.txt
+
+# Get full documentation
+curl https://bmad-code-org.github.io/BMAD-METHOD/llms-full.txt
+```
+
+## Contributing
+
+Want to improve BMad Method? Check out:
+
+- [Contributing Guide](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/CONTRIBUTING.md)
+- [GitHub Repository](https://github.com/bmad-code-org/BMAD-METHOD)

docs/explanation/advanced-elicitation.md

@@ -0,0 +1,24 @@
+---
+title: "Advanced Elicitation"
+description: Push the LLM to rethink its work using structured reasoning methods
+---
+
+Make the LLM reconsider what it just generated. You pick a reasoning method, it applies that method to its own output, you decide whether to keep the improvements.
+
+Dozens of methods are built in - things like First Principles, Red Team vs Blue Team, Pre-mortem Analysis, Socratic Questioning, and more.
+
+## When to Use It
+
+- After a workflow generates content and you want alternatives
+- When output seems okay but you suspect there's more depth
+- To stress-test assumptions or find weaknesses
+- For high-stakes content where rethinking helps
+
+Workflows offer advanced elicitation at decision points - after the LLM has generated something, you'll be asked if you want to run it.
+
+## How It Works
+
+1. LLM suggests 5 relevant methods for your content
+2. You pick one (or reshuffle for different options)
+3. Method is applied, improvements shown
+4. Accept or discard, repeat or continue

docs/explanation/adversarial-review.md

@@ -0,0 +1,57 @@
+---
+title: "Adversarial Review"
+description: Forced reasoning technique that prevents lazy "looks good" reviews
+---
+
+Force deeper analysis by requiring problems to be found.
+
+## What is Adversarial Review?
+
+A review technique where the reviewer *must* find issues. No "looks good" allowed. The reviewer adopts a cynical stance - assume problems exist and find them.
+
+This isn't about being negative. It's about forcing genuine analysis instead of a cursory glance that rubber-stamps whatever was submitted.
+
+**The core rule:** You must find issues. Zero findings triggers a halt - re-analyze or explain why.
+
+## Why It Works
+
+Normal reviews suffer from confirmation bias. You skim the work, nothing jumps out, you approve it. The "find problems" mandate breaks this pattern:
+
+- **Forces thoroughness** - Can't approve until you've looked hard enough to find issues
+- **Catches missing things** - "What's not here?" becomes a natural question
+- **Improves signal quality** - Findings are specific and actionable, not vague concerns
+- **Information asymmetry** - Run reviews with fresh context (no access to original reasoning) so you evaluate the artifact, not the intent
+
+## Where It's Used
+
+Adversarial review appears throughout BMAD workflows - code review, implementation readiness checks, spec validation, and others. Sometimes it's a required step, sometimes optional (like advanced elicitation or party mode). The pattern adapts to whatever artifact needs scrutiny.
+
+## Human Filtering Required
+
+Because the AI is *instructed* to find problems, it will find problems - even when they don't exist. Expect false positives: nitpicks dressed as issues, misunderstandings of intent, or outright hallucinated concerns.
+
+**You decide what's real.** Review each finding, dismiss the noise, fix what matters.
+
+## Example
+
+Instead of:
+
+> "The authentication implementation looks reasonable. Approved."
+
+An adversarial review produces:
+
+> 1. **HIGH** - `login.ts:47` - No rate limiting on failed attempts
+> 2. **HIGH** - Session token stored in localStorage (XSS vulnerable)
+> 3. **MEDIUM** - Password validation happens client-side only
+> 4. **MEDIUM** - No audit logging for failed login attempts
+> 5. **LOW** - Magic number `3600` should be `SESSION_TIMEOUT_SECONDS`
+
+The first review might miss a security vulnerability. The second caught four.
+
+## Iteration and Diminishing Returns
+
+After addressing findings, consider running it again. A second pass usually catches more. A third isn't always useless either. But each pass takes time, and eventually you hit diminishing returns - just nitpicks and false findings.
+
+:::tip[Better Reviews]
+Assume problems exist. Look for what's missing, not just what's wrong.
+:::

docs/explanation/brainstorming.md

@@ -0,0 +1,31 @@
+---
+title: "Brainstorming"
+description: Interactive creative sessions using 60+ proven ideation techniques
+---
+
+Unlock your creativity through guided exploration.
+
+## What is Brainstorming?
+
+Run `brainstorming` and you've got a creative facilitator pulling ideas out of you - not generating them for you. The AI acts as coach and guide, using proven techniques to create conditions where your best thinking emerges.
+
+**Good for:**
+
+- Breaking through creative blocks
+- Generating product or feature ideas
+- Exploring problems from new angles
+- Developing raw concepts into action plans
+
+## How It Works
+
+1. **Setup** - Define topic, goals, constraints
+2. **Choose approach** - Pick techniques yourself, get AI recommendations, go random, or follow a progressive flow
+3. **Facilitation** - Work through techniques with probing questions and collaborative coaching
+4. **Organize** - Ideas grouped into themes and prioritized
+5. **Action** - Top ideas get next steps and success metrics
+
+Everything gets captured in a session document you can reference later or share with stakeholders.
+
+:::note[Your Ideas]
+Every idea comes from you. The workflow creates conditions for insight - you're the source.
+:::

docs/explanation/brownfield-faq.md

@@ -0,0 +1,55 @@
+---
+title: "Brownfield Development FAQ"
+description: Common questions about brownfield development in the BMad Method
+---
+Quick answers to common questions about brownfield (existing codebase) development in the BMad Method (BMM).
+
+## Questions
+
+- [Questions](#questions)
+  - [What is brownfield vs greenfield?](#what-is-brownfield-vs-greenfield)
+  - [Do I have to run document-project for brownfield?](#do-i-have-to-run-document-project-for-brownfield)
+  - [What if I forget to run document-project?](#what-if-i-forget-to-run-document-project)
+  - [Can I use Quick Spec Flow for brownfield projects?](#can-i-use-quick-spec-flow-for-brownfield-projects)
+  - [What if my existing code doesn't follow best practices?](#what-if-my-existing-code-doesnt-follow-best-practices)
+
+### What is brownfield vs greenfield?
+
+- **Greenfield** — New project, starting from scratch, clean slate
+- **Brownfield** — Existing project, working with established codebase and patterns
+
+### Do I have to run document-project for brownfield?
+
+Highly recommended, especially if:
+
+- No existing documentation
+- Documentation is outdated
+- AI agents need context about existing code
+
+You can skip it if you have comprehensive, up-to-date documentation including `docs/index.md` or will use other tools or techniques to aid in discovery for the agent to build on an existing system.
+
+### What if I forget to run document-project?
+
+Don't worry about it - you can do it at any time. You can even do it during or after a project to help keep docs up to date.
+
+### Can I use Quick Spec Flow for brownfield projects?
+
+Yes! Quick Spec Flow works great for brownfield. It will:
+
+- Auto-detect your existing stack
+- Analyze brownfield code patterns
+- Detect conventions and ask for confirmation
+- Generate context-rich tech-spec that respects existing code
+
+Perfect for bug fixes and small features in existing codebases.
+
+### What if my existing code doesn't follow best practices?
+
+Quick Spec Flow detects your conventions and asks: "Should I follow these existing conventions?" You decide:
+
+- **Yes** → Maintain consistency with current codebase
+- **No** → Establish new standards (document why in tech-spec)
+
+BMM respects your choice — it won't force modernization, but it will offer it.
+
+**Have a question not answered here?** Please [open an issue](https://github.com/bmad-code-org/BMAD-METHOD/issues) or ask in [Discord](https://discord.gg/gk8jAdXWmj) so we can add it!

docs/explanation/party-mode.md

@@ -0,0 +1,57 @@
+---
+title: "Party Mode"
+description: Multi-agent collaboration - get all your AI agents in one conversation
+---
+
+Get all your AI agents in one conversation.
+
+## What is Party Mode?
+
+Run `party-mode` and you've got your whole AI team in one room - PM, Architect, Dev, UX Designer, whoever you need. BMad Master orchestrates, picking relevant agents per message. Agents respond in character, agree, disagree, and build on each other's ideas.
+
+The conversation continues as long as you want. Ask follow-ups, push back on answers, redirect the discussion - it's a real back-and-forth with your agents until you're done.
+
+**Good for:**
+
+- Big decisions with tradeoffs
+- Brainstorming sessions
+- Post-mortems when things go wrong
+- Sprint retrospectives and planning
+
+## Examples
+
+### Calling Out Bad Architecture
+
+**You:** "Okay team, our last sprint was a disaster. The authentication service went down three times. Who screwed this up?"
+
+**Architect:** "The design was sound - distributed authentication with proper fallbacks. If implementation deviated from the spec..."
+
+**Dev:** "I followed the architecture doc exactly. The spec didn't account for concurrent session invalidation race conditions."
+
+**PM:** "Both of you missed the bigger issue - we didn't validate session management requirements in the PRD. This is on me for not catching it."
+
+**TEA:** "And I should've caught this in integration tests. The test scenarios didn't cover concurrent invalidation."
+
+### Creative Brainstorming
+
+**You:** "How do we make onboarding feel magical instead of boring?"
+
+**UX Designer:** "Start with progressive disclosure - reveal features as users need them, not all at once in a tutorial."
+
+**Storyteller:** "What if onboarding was a story? Each step reveals a character's journey - the user IS the hero."
+
+**Game Designer:** "Building on that - what if the first 'quest' is actually solving a real user problem? They learn by doing something valuable."
+
+### Technical Decision
+
+**You:** "Monolith or microservices for MVP?"
+
+**Architect:** "Start monolith. Microservices add complexity you don't need at 1000 users."
+
+**PM:** "Agree. Time to market matters more than theoretical scalability."
+
+**Dev:** "Monolith with clear module boundaries. We can extract services later if needed."
+
+:::tip[Better Decisions]
+Better decisions through diverse perspectives. Welcome to party mode.
+:::

docs/explanation/preventing-agent-conflicts.md

@@ -0,0 +1,110 @@
+---
+title: "Preventing Agent Conflicts"
+description: How architecture prevents conflicts when multiple agents implement a system
+---
+
+When multiple AI agents implement different parts of a system, they can make conflicting technical decisions. Architecture documentation prevents this by establishing shared standards.
+
+## Common Conflict Types
+
+### API Style Conflicts
+
+Without architecture:
+- Agent A uses REST with `/users/{id}`
+- Agent B uses GraphQL mutations
+- Result: Inconsistent API patterns, confused consumers
+
+With architecture:
+- ADR specifies: "Use GraphQL for all client-server communication"
+- All agents follow the same pattern
+
+### Database Design Conflicts
+
+Without architecture:
+- Agent A uses snake_case column names
+- Agent B uses camelCase column names
+- Result: Inconsistent schema, confusing queries
+
+With architecture:
+- Standards document specifies naming conventions
+- All agents follow the same patterns
+
+### State Management Conflicts
+
+Without architecture:
+- Agent A uses Redux for global state
+- Agent B uses React Context
+- Result: Multiple state management approaches, complexity
+
+With architecture:
+- ADR specifies state management approach
+- All agents implement consistently
+
+## How Architecture Prevents Conflicts
+
+### 1. Explicit Decisions via ADRs
+
+Every significant technology choice is documented with:
+- Context (why this decision matters)
+- Options considered (what alternatives exist)
+- Decision (what we chose)
+- Rationale (why we chose it)
+- Consequences (trade-offs accepted)
+
+### 2. FR/NFR-Specific Guidance
+
+Architecture maps each functional requirement to technical approach:
+- FR-001: User Management → GraphQL mutations
+- FR-002: Mobile App → Optimized queries
+
+### 3. Standards and Conventions
+
+Explicit documentation of:
+- Directory structure
+- Naming conventions
+- Code organization
+- Testing patterns
+
+## Architecture as Shared Context
+
+Think of architecture as the shared context that all agents read before implementing:
+
+```
+PRD: "What to build"
+     ↓
+Architecture: "How to build it"
+     ↓
+Agent A reads architecture → implements Epic 1
+Agent B reads architecture → implements Epic 2
+Agent C reads architecture → implements Epic 3
+     ↓
+Result: Consistent implementation
+```
+
+## Key ADR Topics
+
+Common decisions that prevent conflicts:
+
+| Topic            | Example Decision                             |
+| ---------------- | -------------------------------------------- |
+| API Style        | GraphQL vs REST vs gRPC                      |
+| Database         | PostgreSQL vs MongoDB                        |
+| Auth             | JWT vs Sessions                              |
+| State Management | Redux vs Context vs Zustand                  |
+| Styling          | CSS Modules vs Tailwind vs Styled Components |
+| Testing          | Jest + Playwright vs Vitest + Cypress        |
+
+## Anti-Patterns to Avoid
+
+:::caution[Common Mistakes]
+- **Implicit Decisions** — "We'll figure out the API style as we go" leads to inconsistency
+- **Over-Documentation** — Documenting every minor choice causes analysis paralysis
+- **Stale Architecture** — Documents written once and never updated cause agents to follow outdated patterns
+:::
+
+:::tip[Correct Approach]
+- Document decisions that cross epic boundaries
+- Focus on conflict-prone areas
+- Update architecture as you learn
+- Use `correct-course` for significant changes
+:::

docs/explanation/quick-flow.md

@@ -0,0 +1,27 @@
+---
+title: "Quick Flow"
+description: Fast-track for small changes - skip the full methodology
+---
+
+Quick Flow is for when you don't need the full BMad Method. Skip Product Brief, PRD, and Architecture - go straight to implementation.
+
+## How It Works
+
+1. **Run `quick-spec`** — generates a focused tech-spec
+2. **Run `quick-dev`** — implements it
+
+That's it.
+
+## When to Use It
+
+- Bug fixes
+- Refactoring
+- Small features
+- Prototyping
+
+## When to Use Full BMad Method Instead
+
+- New products
+- Major features
+- Multiple teams involved
+- Stakeholder alignment needed

docs/explanation/why-solutioning-matters.md

@@ -0,0 +1,75 @@
+---
+title: "Why Solutioning Matters"
+description: Understanding why the solutioning phase is critical for multi-epic projects
+---
+
+
+Phase 3 (Solutioning) translates **what** to build (from Planning) into **how** to build it (technical design). This phase prevents agent conflicts in multi-epic projects by documenting architectural decisions before implementation begins.
+
+## The Problem Without Solutioning
+
+```
+Agent 1 implements Epic 1 using REST API
+Agent 2 implements Epic 2 using GraphQL
+Result: Inconsistent API design, integration nightmare
+```
+
+When multiple agents implement different parts of a system without shared architectural guidance, they make independent technical decisions that may conflict.
+
+## The Solution With Solutioning
+
+```
+architecture workflow decides: "Use GraphQL for all APIs"
+All agents follow architecture decisions
+Result: Consistent implementation, no conflicts
+```
+
+By documenting technical decisions explicitly, all agents implement consistently and integration becomes straightforward.
+
+## Solutioning vs Planning
+
+| Aspect   | Planning (Phase 2)      | Solutioning (Phase 3)             |
+| -------- | ----------------------- | --------------------------------- |
+| Question | What and Why?           | How? Then What units of work?     |
+| Output   | FRs/NFRs (Requirements) | Architecture + Epics/Stories      |
+| Agent    | PM                      | Architect → PM                    |
+| Audience | Stakeholders            | Developers                        |
+| Document | PRD (FRs/NFRs)          | Architecture + Epic Files         |
+| Level    | Business logic          | Technical design + Work breakdown |
+
+## Key Principle
+
+**Make technical decisions explicit and documented** so all agents implement consistently.
+
+This prevents:
+- API style conflicts (REST vs GraphQL)
+- Database design inconsistencies
+- State management disagreements
+- Naming convention mismatches
+- Security approach variations
+
+## When Solutioning is Required
+
+| Track | Solutioning Required? |
+|-------|----------------------|
+| Quick Flow | No - skip entirely |
+| BMad Method Simple | Optional |
+| BMad Method Complex | Yes |
+| Enterprise | Yes |
+
+:::tip[Rule of Thumb]
+If you have multiple epics that could be implemented by different agents, you need solutioning.
+:::
+
+## The Cost of Skipping
+
+Skipping solutioning on complex projects leads to:
+
+- **Integration issues** discovered mid-sprint
+- **Rework** due to conflicting implementations
+- **Longer development time** overall
+- **Technical debt** from inconsistent patterns
+
+:::caution[Cost Multiplier]
+Catching alignment issues in solutioning is 10× faster than discovering them during implementation.
+:::

docs/how-to/brownfield/index.md

@@ -0,0 +1,84 @@
+---
+title: "Brownfield Development"
+description: How to use BMad Method on existing codebases
+---
+
+Use BMad Method effectively when working on existing projects and legacy codebases.
+
+## What is Brownfield Development?
+
+**Brownfield** refers to working on existing projects with established codebases and patterns, as opposed to **greenfield** which means starting from scratch with a clean slate.
+
+This guide covers the essential workflow for onboarding to brownfield projects with BMad Method.
+
+:::note[Prerequisites]
+- BMad Method installed (`npx bmad-method install`)
+- An existing codebase you want to work on
+- Access to an AI-powered IDE (Claude Code, Cursor, or Windsurf)
+:::
+
+## Step 1: Clean Up Completed Planning Artifacts
+
+If you have completed all PRD epics and stories through the BMad process, clean up those files. Archive them, delete them, or rely on version history if needed. Do not keep these files in:
+
+- `docs/`
+- `_bmad-output/planning-artifacts/`
+- `_bmad-output/implementation-artifacts/`
+
+## Step 2: Maintain Quality Project Documentation
+
+Your `docs/` folder should contain succinct, well-organized documentation that accurately represents your project:
+
+- Intent and business rationale
+- Business rules
+- Architecture
+- Any other relevant project information
+
+For complex projects, consider using the `document-project` workflow. It offers runtime variants that will scan your entire project and document its actual current state.
+
+## Step 3: Get Help
+
+Get help to know what to do next based on your unique needs
+
+Run `bmad-help` to get guidance when you are not sure what to do next.
+
+### Choosing Your Approach
+
+You have two primary options depending on the scope of changes:
+
+| Scope                          | Recommended Approach                                                                                                          |
+| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------- |
+| **Small updates or additions** | Use `quick-flow-solo-dev` to create a tech-spec and implement the change. The full four-phase BMad method is likely overkill. |
+| **Major changes or additions** | Start with the BMad method, applying as much or as little rigor as needed.                                                    |
+
+### During PRD Creation
+
+When creating a brief or jumping directly into the PRD, ensure the agent:
+
+- Finds and analyzes your existing project documentation
+- Reads the proper context about your current system
+
+You can guide the agent explicitly, but the goal is to ensure the new feature integrates well with your existing system.
+
+### UX Considerations
+
+UX work is optional. The decision depends not on whether your project has a UX, but on:
+
+- Whether you will be working on UX changes
+- Whether significant new UX designs or patterns are needed
+
+If your changes amount to simple updates to existing screens you are happy with, a full UX process is unnecessary.
+
+### Architecture Considerations
+
+When doing architecture, ensure the architect:
+
+- Uses the proper documented files
+- Scans the existing codebase
+
+Pay close attention here to prevent reinventing the wheel or making decisions that misalign with your existing architecture.
+
+## More Information
+
+- **[Quick Fix in Brownfield](/docs/how-to/brownfield/quick-fix-in-brownfield.md)** - Bug fixes and ad-hoc changes
+- **[Brownfield FAQ](/docs/explanation/brownfield-faq.md)** - Common questions about brownfield development

docs/how-to/brownfield/quick-fix-in-brownfield.md

@@ -0,0 +1,76 @@
+---
+title: "How to Make Quick Fixes in Brownfield Projects"
+description: How to make quick fixes and ad-hoc changes in brownfield projects
+---
+
+Use the **DEV agent** directly for bug fixes, refactorings, or small targeted changes that don't require the full BMad method or Quick Flow.
+
+## When to Use This
+
+- Simple bug fixes
+- Small refactorings and changes that don't need extensive ideation, planning, or architectural shifts
+- Larger refactorings or improvement with built in tool planning and execution mode combination, or better yet use quick flow
+- Learning about your codebase
+
+## Steps
+
+### 1. Load an Agent
+
+For quick fixes, you can use:
+
+- **DEV agent** - For implementation-focused work
+- **Quick Flow Solo Dev** - For slightly larger changes that still need a quick-spec to keep the agent aligned to planning and standards
+
+### 2. Describe the Change
+
+Simply tell the agent what you need:
+
+```
+Fix the login validation bug that allows empty passwords
+```
+
+or
+
+```
+Refactor the UserService to use async/await instead of callbacks
+```
+
+### 3. Let the Agent Work
+
+The agent will:
+
+- Analyze the relevant code
+- Propose a solution
+- Implement the change
+- Run tests (if available)
+
+### 4. Review and Commit
+
+Review the changes made and commit when satisfied.
+
+## Learning Your Codebase
+
+This approach is also excellent for exploring unfamiliar code:
+
+```
+Explain how the authentication system works in this codebase
+```
+
+```
+Show me where error handling happens in the API layer
+```
+
+LLMs are excellent at interpreting and analyzing code, whether it was AI-generated or not. Use the agent to:
+
+- Learn about your project
+- Understand how things are built
+- Explore unfamiliar parts of the codebase
+
+## When to Upgrade to Formal Planning
+
+Consider using Quick Flow or full BMad Method when:
+
+- The change affects multiple files or systems
+- You're unsure about the scope
+- The fix keeps growing in complexity
+- You need documentation for the change

docs/how-to/customize-bmad.md

@@ -0,0 +1,158 @@
+---
+title: "BMad Method Customization Guide"
+---
+
+The ability to customize the BMad Method and its core to your needs, while still being able to get updates and enhancements is a critical idea within the BMad Ecosystem.
+
+The Customization Guidance outlined here, while targeted at understanding BMad Method customization, applies to any other module use within the BMad Method.
+
+## Types of Customization
+
+Customization includes Agent Customization, Workflow/Skill customization, the addition of new MCPs or Skills to be used by existing agents. Aside from all of this, a whole other realm of customization involves creating / adding your own relevant BMad Builder workflows, skills, agents and maybe even your own net new modules to compliment the BMad Method Module.
+
+Warning: The reason for customizing as this guide will prescribe will allow you to continue getting updates without worrying about losing your customization changes. And by continuing to get updates as BMad modules advance, you will be able to continue to evolve as the system improves.
+
+## Agent Customization
+
+### Agent Customization Areas
+
+- Change agent names, personas or manner of speech
+- Add project-specific memories or context
+- Add custom menu items to custom or inline prompts, skills or custom BMad workflows
+- Define critical actions that occur agent startup for consistent behavior
+
+## How to customize an agent.
+
+**1. Locate Customization Files**
+
+After installation, find agent customization files in:
+
+```
+_bmad/_config/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 install
+```
+
+You can either then:
+
+- Select `Quick Update` - This will also ensure all packages are up to date AND compile all agents to include any updates or customizations
+- Select `Rebuild Agents` - This will only rebuild and apply customizations to agents, without pulling the latest
+
+There will be additional tools shortly after beta launch to allow install of individual agents, workflows, skills and modules without the need for using the full bmad installer.
+
+### What Agent Properties Can Be Customized?
+
+#### 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 annoying'
+  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
+
+Any custom items you add here will be included in the agents display menu.
+
+```yaml
+menu:
+  - trigger: my-workflow
+    workflow: '{project-root}/my-custom/workflows/my-workflow.yaml'
+    description: My custom workflow
+  - trigger: deploy
+    action: '#deploy-prompt'
+    description: Deploy to production
+```
+
+### Critical Actions
+
+Add instructions that execute before the agent starts:
+
+```yaml
+critical_actions:
+  - 'Check the CI Pipelines with the XYZ Skill and alert user on wake if anything is urgently needing attention'
+```
+
+### 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
+```
+
+## 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?**
+
+- Remove content from the `.customize.yaml` file (or delete the file)
+- Run `npx bmad-method build <agent-name>` to regenerate defaults
+
+## Workflow Customization
+
+Information about customizing existing BMad MEthod workflows and skills are coming soon.
+
+## Module Customization
+
+Information on how to build expansion modules that augment BMad, or make other existing module customizations are coming soon.

docs/how-to/get-answers-about-bmad.md

@@ -0,0 +1,102 @@
+---
+title: "How to Get Answers About BMad"
+description: Use an LLM to quickly answer your own BMad questions
+---
+
+If you have successfully installed BMad and the BMad Method (+ other modules as needed) - the first step in getting answers is `/bmad-help`. This will answer upwards of 80% of all questions and is available to you in the IDE as you are working.
+
+## When to Use This
+
+- You have a question about how BMad works or what to do next with BMad
+- You want to understand a specific agent or workflow
+- You need quick answers without waiting for Discord
+
+:::note[Prerequisites]
+An AI tool (Claude Code, Cursor, ChatGPT, Claude.ai, etc.) and either BMad installed in your project or access to the GitHub repo.
+:::
+
+## Steps
+
+### 1. Choose Your Source
+
+| Source               | Best For                                  | Examples                     |
+| -------------------- | ----------------------------------------- | ---------------------------- |
+| **`_bmad` folder**   | How BMad works—agents, workflows, prompts | "What does the PM agent do?" |
+| **Full GitHub repo** | History, installer, architecture          | "What changed in v6?"        |
+| **`llms-full.txt`**  | Quick overview from docs                  | "Explain BMad's four phases" |
+
+The `_bmad` folder is created when you install BMad. If you don't have it yet, clone the repo instead.
+
+### 2. Point Your AI at the Source
+
+**If your AI can read files (Claude Code, Cursor, etc.):**
+
+- **BMad installed:** Point at the `_bmad` folder and ask directly
+- **Want deeper context:** Clone the [full repo](https://github.com/bmad-code-org/BMAD-METHOD)
+
+**If you use ChatGPT or Claude.ai:**
+
+Fetch `llms-full.txt` into your session:
+
+```
+https://bmad-code-org.github.io/BMAD-METHOD/llms-full.txt
+```
+
+See the [Downloads page](/docs/downloads.md) for other downloadable resources.
+
+### 3. Ask Your Question
+
+:::note[Example]
+**Q:** "Tell me the fastest way to build something with BMad"
+
+**A:** Use Quick Flow: Run `quick-spec` to write a technical specification, then `quick-dev` to implement it—skipping the full planning phases.
+:::
+
+## What You Get
+
+Direct answers about BMad—how agents work, what workflows do, why things are structured the way they are—without waiting for someone else to respond.
+
+## Tips
+
+- **Verify surprising answers** — LLMs occasionally get things wrong. Check the source file or ask on Discord.
+- **Be specific** — "What does step 3 of the PRD workflow do?" beats "How does PRD work?"
+
+## Still Stuck?
+
+Tried the LLM approach and still need help? You now have a much better question to ask.
+
+| Channel                   | Use For                                     |
+| ------------------------- | ------------------------------------------- |
+| `#bmad-method-help`       | Quick questions (real-time chat)            |
+| `help-requests` forum     | Detailed questions (searchable, persistent) |
+| `#suggestions-feedback`   | Ideas and feature requests                  |
+| `#report-bugs-and-issues` | Bug reports                                 |
+
+**Discord:** [discord.gg/gk8jAdXWmj](https://discord.gg/gk8jAdXWmj)
+
+**GitHub Issues:** [github.com/bmad-code-org/BMAD-METHOD/issues](https://github.com/bmad-code-org/BMAD-METHOD/issues) (for clear bugs)
+
+*You!*
+        *Stuck*
+             *in the queue—*
+                      *waiting*
+                              *for who?*
+
+*The source*
+        *is there,*
+                *plain to see!*
+
+*Point*
+     *your machine.*
+              *Set it free.*
+
+*It reads.*
+        *It speaks.*
+                *Ask away—*
+
+*Why wait*
+        *for tomorrow*
+                *when you have*
+                        *today?*
+
+*—Claude*

docs/how-to/install-bmad.md

@@ -0,0 +1,82 @@
+---
+title: "How to Install BMad"
+description: Step-by-step guide to installing BMad in your project
+---
+
+Use the `npx bmad-method install` command to set up BMad in your project with your choice of modules and AI tools.
+
+## When to Use This
+
+- Starting a new project with BMad
+- Adding BMad to an existing codebase
+- Update the existing BMad Installation
+
+:::note[Prerequisites]
+- **Node.js** 20+ (required for the installer)
+- **Git** (recommended)
+- **AI tool** (Claude Code, Cursor, Windsurf, or similar)
+:::
+
+## Steps
+
+### 1. Run the Installer
+
+```bash
+npx bmad-method install
+```
+
+### 2. Choose Installation Location
+
+The installer will ask where to install BMad files:
+
+- Current directory (recommended for new projects if you created the directory yourself and ran from within the directory)
+- Custom path
+
+### 3. Select Your AI Tools
+
+Pick which AI tools you use:
+
+- Claude Code
+- Cursor
+- Windsurf
+- Others
+
+Each tool has its own way of integrating commands. The installer creates tiny prompt files to activate workflows and agents — it just puts them where your tool expects to find them.
+
+### 4. Choose Modules
+
+The installer shows available modules. Select whichever ones you need — most users just want **BMad Method** (the software development module).
+
+### 5. Follow the Prompts
+
+The installer guides you through the rest — custom content, settings, etc.
+
+## What You Get
+
+```
+your-project/
+├── _bmad/
+│   ├── bmm/            # Your selected modules
+│   │   └── config.yaml # Module settings (if you ever need to change them)
+│   ├── core/           # Required core module
+│   └── ...
+├── _bmad-output/       # Generated artifacts
+└── .claude/            # Claude Code commands (if using Claude Code)
+```
+
+## Verify Installation
+
+Run the `help` workflow (`/bmad-help` on most platforms) to verify everything works and see what to do next.
+
+**Latest from main branch:**
+```bash
+npx github:bmad-code-org/BMAD-METHOD install
+```
+
+Use these if you want the newest features before they're officially released. Things might break.
+
+## Troubleshooting
+
+**Installer throws an error** — Copy-paste the output into your AI assistant and let it figure it out.
+
+**Installer worked but something doesn't work later** — Your AI needs BMad context to help. See [How to Get Answers About BMad](/docs/how-to/get-answers-about-bmad.md) for how to point your AI at the right sources.

docs/how-to/shard-large-documents.md

@@ -0,0 +1,101 @@
+---
+title: "Document Sharding Guide"
+---
+
+Use the `shard-doc` tool to split large markdown files into smaller, organized files for better context management.
+
+## When to Use This
+
+- 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
+
+## 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
+```
+
+## Steps
+
+### 1. Run the Shard-Doc Tool
+
+```bash
+/bmad:core:tools:shard-doc
+```
+
+### 2. Follow the 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 You Get
+
+**index.md structure:**
+
+```markdown
+
+## 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
+
+## How Workflow Discovery Works
+
+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 - remove the whole document if you want the sharded to be used instead
+
+## Workflow Support
+
+All BMM workflows support both formats:
+
+- Whole documents
+- Sharded documents
+- Automatic detection
+- Transparent to user

docs/how-to/upgrade-to-v6.md

@@ -0,0 +1,131 @@
+---
+title: "How to Upgrade to v6"
+description: Migrate from BMad v4 to v6
+---
+
+Use the BMad installer to upgrade from v4 to v6, which includes automatic detection of legacy installations and migration assistance.
+
+## When to Use This
+
+- You have BMad v4 installed (`.bmad-method` folder)
+- You want to migrate to the new v6 architecture
+- You have existing planning artifacts to preserve
+
+:::note[Prerequisites]
+- Node.js 20+
+- Existing BMad v4 installation
+:::
+
+## Steps
+
+### 1. Run the Installer
+
+```bash
+npx bmad-method install
+```
+
+The installer automatically detects:
+
+- **Legacy v4 folder**: `.bmad-method`
+- **IDE command artifacts**: Legacy bmad folders in `.claude/commands/`, `.cursor/commands/`, etc.
+
+### 2. Handle Legacy Installation
+
+When v4 is detected, you can:
+
+- Allow the installer to back up and remove `.bmad-method`
+- Exit and handle cleanup manually
+- Keep both (not recommended for same project)
+
+### 3. Clean Up IDE Commands
+
+Manually remove legacy v4 IDE commands:
+
+- `.claude/commands/BMad/agents`
+- `.claude/commands/BMad/tasks`
+
+New v6 commands will be at `.claude/commands/bmad/<module>/agents|workflows`.
+
+:::tip[Accidentally Deleted Commands?]
+If you delete the wrong commands, rerun the installer and choose "quick update" to restore them.
+:::
+
+### 4. Migrate Planning Artifacts
+
+**If you have planning documents (Brief/PRD/UX/Architecture):**
+
+Move them to `_bmad-output/planning-artifacts/` with descriptive names:
+
+- Include `PRD` in filename for PRD documents
+- Include `brief`, `architecture`, or `ux-design` accordingly
+- Sharded documents can be in named subfolders
+
+**If you're mid-planning:** Consider restarting with v6 workflows. Use your existing documents as inputs—the new progressive discovery workflows with web search and IDE plan mode produce better results.
+
+### 5. Migrate In-Progress Development
+
+If you have stories created or implemented:
+
+1. Complete the v6 installation
+2. Place `epics.md` or `epics/epic*.md` in `_bmad-output/planning-artifacts/`
+3. Run the Scrum Master's `sprint-planning` workflow
+4. Tell the SM which epics/stories are already complete
+
+### 6. Migrate Agent Customizations
+
+**v4:** Modified agent files directly in `_bmad-*` folders
+
+**v6:** All customizations go in `_bmad/_config/agents/` using customize files:
+
+```yaml
+# _bmad/_config/agents/bmm-pm.customize.yaml
+persona:
+  name: 'Captain Jack'
+  role: 'Swashbuckling Product Owner'
+  communication_style: |
+    - Talk like a pirate
+    - Use nautical metaphors
+```
+
+After modifying customization files, rerun the installer and choose "rebuild all agents" or "quick update".
+
+## What You Get
+
+**v6 unified structure:**
+
+```
+your-project/
+└── _bmad/               # Single installation folder
+    ├── _config/         # Your customizations
+    │   └── agents/      # Agent customization files
+    ├── core/            # Universal core framework
+    ├── bmm/             # BMad Method module
+    ├── bmb/             # BMad Builder
+    └── cis/             # Creative Intelligence Suite
+├── _bmad-output/        # Output folder (was doc folder in v4)
+```
+
+## Module Migration
+
+| v4 Module | v6 Status |
+|-----------|-----------|
+| `_bmad-2d-phaser-game-dev` | Integrated into BMGD Module |
+| `_bmad-2d-unity-game-dev` | Integrated into BMGD Module |
+| `_bmad-godot-game-dev` | Integrated into BMGD Module |
+| `_bmad-infrastructure-devops` | Deprecated — new DevOps agent coming soon |
+| `_bmad-creative-writing` | Not adapted — new v6 module coming soon |
+
+## Key Changes
+
+| Concept | v4 | v6 |
+|---------|----|----|
+| **Core** | `_bmad-core` was actually BMad Method | `_bmad/core/` is universal framework |
+| **Method** | `_bmad-method` | `_bmad/bmm/` |
+| **Config** | Modified files directly | `config.yaml` per module |
+| **Documents** | Sharded or unsharded required setup | Fully flexible, auto-scanned |
+
+## Tips
+
+- **Back up first** — Keep your v4 installation until you verify v6 works
+- **Use v6 workflows** — Even partial planning docs benefit from v6's improved discovery
+- **Rebuild after customizing** — Always run the installer after changing customize files

docs/ide-info/auggie.md

@@ -1,31 +0,0 @@
-# BMAD Method - Auggie CLI Instructions
-
-## Activating Agents
-
-BMAD agents can be installed in multiple locations based on your setup.
-
-### Common Locations
-
-- User Home: `~/.augment/commands/`
-- Project: `.augment/commands/`
-- Custom paths you selected
-
-### How to Use
-
-1. **Type Trigger**: Use `@{agent-name}` in your prompt
-2. **Activate**: Agent persona activates
-3. **Tasks**: Use `@task-{task-name}` for tasks
-
-### Examples
-
-```
-@dev - Activate development agent
-@architect - Activate architect agent
-@task-setup - Execute setup task
-```
-
-### Notes
-
-- Agents can be in multiple locations
-- Check your installation paths
-- Activation syntax same across all locations

docs/ide-info/claude-code.md

@@ -1,25 +0,0 @@
-# BMAD Method - Claude Code Instructions
-
-## Activating Agents
-
-BMAD agents are installed as slash commands in `.claude/commands/bmad/`.
-
-### How to Use
-
-1. **Type Slash Command**: Start with `/` to see available commands
-2. **Select Agent**: Type `/bmad-{agent-name}` (e.g., `/bmad-dev`)
-3. **Execute**: Press Enter to activate that agent persona
-
-### Examples
-
-```
-/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 a new conversation to switch agents

docs/ide-info/cline.md

@@ -1,31 +0,0 @@
-# BMAD Method - Cline Instructions
-
-## Activating Agents
-
-BMAD agents are installed as **toggleable rules** in `.clinerules/` directory.
-
-### Important: Rules are OFF by default
-
-- Rules are NOT automatically loaded to avoid context pollution
-- You must manually enable the agent you want to use
-
-### How to Use
-
-1. **Open Rules Panel**: Click the rules icon below the chat input
-2. **Enable an Agent**: Toggle ON the specific agent rule you need (e.g., `01-core-dev`)
-3. **Activate in Chat**: Type `@{agent-name}` to activate that persona
-4. **Disable When Done**: Toggle OFF to free up context
-
-### Best Practices
-
-- Only enable 1-2 agents at a time to preserve context
-- Disable agents when switching tasks
-- Rules are numbered (01-, 02-) for organization, not priority
-
-### Example
-
-```
-Toggle ON: 01-core-dev.md
-In chat: "@dev help me refactor this code"
-When done: Toggle OFF the rule
-```

docs/ide-info/codex.md

@@ -1,21 +0,0 @@
-# BMAD Method - Codex Instructions
-
-## Activating Agents
-
-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
-
-```
-/bmad-bmm-agents-dev - Activate development agent
-/bmad-bmm-agents-architect - Activate architect agent
-/bmad-bmm-workflows-dev-story - Execute dev-story workflow
-```
-
-### Notes
-
-Prompts are autocompleted when you type /
-Agent remains active for the conversation
-Start a new conversation to switch agents

docs/ide-info/crush.md

@@ -1,30 +0,0 @@
-# BMAD Method - Crush Instructions
-
-## Activating Agents
-
-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/`
-3. **Select Agent**: Choose the agent command
-4. **Execute**: Run to activate agent persona
-
-### Command Structure
-
-```
-.crush/commands/bmad/
-├── agents/          # All agents
-├── tasks/           # All tasks
-├── core/            # Core module
-│   ├── agents/
-│   └── tasks/
-└── {module}/        # Other modules
-```
-
-### Notes
-
-- Commands organized by module
-- Can browse hierarchically
-- Agent activates for session

docs/ide-info/cursor.md

@@ -1,25 +0,0 @@
-# BMAD Method - Cursor Instructions
-
-## Activating Agents
-
-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
-
-### Examples
-
-```
-@_bmad/core/agents/dev - Activate dev agent
-@_bmad/bmm/agents/architect - Activate architect agent
-@_bmad/core - Include all core agents/tasks
-```
-
-### Notes
-
-- Rules are Manual type - only loaded when explicitly referenced
-- No automatic context pollution
-- Can combine multiple agents: `@_bmad/core/agents/dev @_bmad/core/agents/test`

docs/ide-info/gemini.md

@@ -1,25 +0,0 @@
-# BMAD Method - Gemini CLI Instructions
-
-## Activating Agents
-
-BMAD agents are concatenated in `.gemini/bmad-method/GEMINI.md`.
-
-### How to Use
-
-1. **Type Trigger**: Use `*{agent-name}` in your prompt
-2. **Activate**: Agent persona activates from the concatenated file
-3. **Continue**: Agent remains active for conversation
-
-### Examples
-
-```
-*dev - Activate development agent
-*architect - Activate architect agent
-*test - Activate test agent
-```
-
-### Notes
-
-- All agents loaded from single GEMINI.md file
-- Triggers with asterisk: `*{agent-name}`
-- Context includes all agents (may be large)

docs/ide-info/github-copilot.md

@@ -1,26 +0,0 @@
-# BMAD Method - GitHub Copilot Instructions
-
-## Activating Agents
-
-BMAD agents are installed as chat modes in `.github/chatmodes/`.
-
-### How to Use
-
-1. **Open Chat View**: Click Copilot icon in VS Code sidebar
-2. **Select Mode**: Click mode selector (top of chat)
-3. **Choose Agent**: Select the BMAD agent from dropdown
-4. **Chat**: Agent is now active for this session
-
-### VS Code Settings
-
-Configured in `.vscode/settings.json`:
-
-- Max requests per session
-- Auto-fix enabled
-- MCP discovery enabled
-
-### Notes
-
-- Modes persist for the chat session
-- Switch modes anytime via dropdown
-- Multiple agents available in mode selector

docs/ide-info/iflow.md

@@ -1,33 +0,0 @@
-# BMAD Method - iFlow CLI Instructions
-
-## Activating Agents
-
-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/`
-3. **Select**: Choose the agent or task command
-4. **Execute**: Run to activate
-
-### Command Structure
-
-```
-.iflow/commands/bmad/
-├── agents/     # Agent commands
-└── tasks/      # Task commands
-```
-
-### Examples
-
-```
-/_bmad/agents/core-dev - Activate dev agent
-/_bmad/tasks/core-setup - Execute setup task
-```
-
-### Notes
-
-- Commands organized by type (agents/tasks)
-- Agent activates for session
-- Similar to Crush command structure

docs/ide-info/kilo.md

@@ -1,24 +0,0 @@
-# BMAD Method - KiloCode Instructions
-
-## Activating Agents
-
-BMAD agents are installed as custom modes in `.kilocodemodes`.
-
-### How to Use
-
-1. **Open Project**: Modes auto-load when project opens
-2. **Select Mode**: Use mode selector in KiloCode interface
-3. **Choose Agent**: Pick `bmad-{module}-{agent}` mode
-4. **Activate**: Mode is now active
-
-### Mode Format
-
-- Mode name: `bmad-{module}-{agent}`
-- Display: `{icon} {title}`
-- Example: `bmad-core-dev` shows as `🤖 Dev`
-
-### Notes
-
-- Modes persist until changed
-- Similar to Roo Code mode system
-- Icon shows in mode selector

docs/ide-info/opencode.md

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

docs/ide-info/qwen.md

@@ -1,25 +0,0 @@
-# BMAD Method - Qwen Code Instructions
-
-## Activating Agents
-
-BMAD agents are concatenated in `.qwen/bmad-method/QWEN.md`.
-
-### How to Use
-
-1. **Type Trigger**: Use `*{agent-name}` in your prompt
-2. **Activate**: Agent persona activates from the concatenated file
-3. **Continue**: Agent remains active for conversation
-
-### Examples
-
-```
-*dev - Activate development agent
-*architect - Activate architect agent
-*test - Activate test agent
-```
-
-### Notes
-
-- All agents loaded from single QWEN.md file
-- Triggers with asterisk: `*{agent-name}`
-- Similar to Gemini CLI setup

docs/ide-info/roo.md

@@ -1,27 +0,0 @@
-# BMAD Method - Roo Code Instructions
-
-## Activating Agents
-
-BMAD agents are installed as custom modes in `.roomodes`.
-
-### How to Use
-
-1. **Open Project**: Modes auto-load when project opens
-2. **Select Mode**: Use mode selector in Roo interface
-3. **Choose Agent**: Pick `bmad-{module}-{agent}` mode
-4. **Activate**: Mode is now active with configured permissions
-
-### Permission Levels
-
-Modes are configured with file edit permissions:
-
-- Development files only
-- Configuration files only
-- Documentation files only
-- All files (if configured)
-
-### Notes
-
-- Modes persist until changed
-- Each mode has specific file access rights
-- Icon shows in mode selector for easy identification

docs/ide-info/rovo-dev.md

@@ -1,388 +0,0 @@
-# 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)

docs/ide-info/trae.md

@@ -1,25 +0,0 @@
-# BMAD Method - Trae Instructions
-
-## Activating Agents
-
-BMAD agents are installed as rules in `.trae/rules/`.
-
-### How to Use
-
-1. **Type Trigger**: Use `@{agent-name}` in your prompt
-2. **Activate**: Agent persona activates automatically
-3. **Continue**: Agent remains active for conversation
-
-### Examples
-
-```
-@dev - Activate development agent
-@architect - Activate architect agent
-@task-setup - Execute setup task
-```
-
-### Notes
-
-- Rules auto-load from `.trae/rules/` directory
-- Multiple agents can be referenced: `@dev and @test`
-- Agent follows YAML configuration in rule file

docs/ide-info/windsurf.md

@@ -1,22 +0,0 @@
-# BMAD Method - Windsurf Instructions
-
-## Activating Agents
-
-BMAD agents are installed as workflows in `.windsurf/workflows/`.
-
-### How to Use
-
-1. **Open Workflows**: Access via Windsurf menu or command palette
-2. **Select Workflow**: Choose the agent/task workflow
-3. **Execute**: Run to activate that agent persona
-
-### Workflow Types
-
-- **Agent workflows**: `{module}-{agent}.md` (auto_execution_mode: 3)
-- **Task workflows**: `task-{module}-{task}.md` (auto_execution_mode: 2)
-
-### Notes
-
-- Agents run with higher autonomy (mode 3)
-- Tasks run with guided execution (mode 2)
-- Workflows persist for the session

docs/index.md

@@ -1,152 +1,56 @@
-# BMad Documentation Index
+---
+title: Welcome to the BMad Method
+---
 
-Complete map of all BMad Method v6 documentation with recommended reading paths.
+The BMad Method (**B**reakthrough **M**ethod of **A**gile AI **D**riven Development) is an AI-driven development framework that helps you build software faster and smarter. It provides specialized AI agents, guided workflows, and intelligent planning that adapts to your project's complexity—whether you're fixing a bug or building an enterprise platform.
+
+If you're comfortable working with AI coding assistants like Claude, Cursor, or GitHub Copilot, you're ready to get started.
 
 ---
 
-## 🎯 Getting Started (Start Here!)
+## New Here? Start with a Tutorial
 
-**New users:** Start with one of these based on your situation:
+The fastest way to understand BMad is to try it.
 
-| 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)   |
+- **[Get Started with BMad](/docs/tutorials/getting-started.md)** — Install and understand how BMad works
+- **[Workflow Map](/docs/reference/workflow-map.md)** — Visual overview of BMM phases, workflows, and context management.
+
+## How to Use These Docs
+
+These docs are organized into four sections based on what you're trying to do:
+
+| Section           | Purpose                                                                                                    |
+| ----------------- | ---------------------------------------------------------------------------------------------------------- |
+| **Tutorials**     | Learning-oriented. Step-by-step guides that walk you through building something. Start here if you're new. |
+| **How-To Guides** | Task-oriented. Practical guides for solving specific problems. "How do I customize an agent?" lives here.  |
+| **Explanation**   | Understanding-oriented. Deep dives into concepts and architecture. Read when you want to know *why*.       |
+| **Reference**     | Information-oriented. Technical specifications for agents, workflows, and configuration.                   |
 
 ---
 
-## 📋 Core Documentation
+## What You'll Need
 
-### Project-Level Docs (Root)
+BMad works with any AI coding assistant that supports custom system prompts or project context. Popular options include:
 
-- **[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
+- **[Claude Code](https://code.claude.com)** — Anthropic's CLI tool (recommended)
+- **[Cursor](https://cursor.sh)** — AI-first code editor
+- **[Windsurf](https://codeium.com/windsurf)** — Codeium's AI IDE
+- **[Roo Code](https://roocode.com)** — VS Code extension
 
-### 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
+You should be comfortable with basic software development concepts like version control, project structure, and agile workflows. No prior experience with BMad-style agent systems is required—that's what these docs are for.
 
 ---
 
-## 🏗️ Module Documentation
+## Join the Community
 
-### BMad Method (BMM) - Software & Game Development
+Get help, share what you're building, or contribute to BMad:
 
-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/docs/README.md)** - Module overview and capabilities
-- **[Agent Creation Guide](../src/modules/bmb/workflows/create-agent/README.md)** - Design custom agents
-
-### Creative Intelligence Suite (CIS) - Innovation & Creativity
-
-AI-powered creative thinking and brainstorming.
-
-- **[CIS Module README](../src/modules/cis/README.md)** - Module overview and workflows
+- **[Discord](https://discord.gg/gk8jAdXWmj)** — Chat with other BMad users, ask questions, share ideas
+- **[GitHub](https://github.com/bmad-code-org/BMAD-METHOD)** — Source code, issues, and contributions
+- **[YouTube](https://www.youtube.com/@BMadCode)** — Video tutorials and walkthroughs
 
 ---
 
-## 🖥️ IDE-Specific Guides
+## Next Step
 
-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, Workflow and Modules
-
-- **[Custom Content Installation](./custom-content-installation.md)** - Install and personalize agents, workflows and modules with the default bmad-method installer!
-- [Agent Customization Guide](./agent-customization-guide.md) - Customize agent behavior and responses
-
-### Installation & Bundling
-
-- [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/docs/README.md) - Understand capabilities
-2. [Agent Creation Guide](../src/modules/bmb/workflows/create-agent/README.md) - Create agents
-3. [BMM Workflows Guide](../src/modules/bmm/workflows/README.md) - Understand workflow structure
-
-### 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
+Ready to dive in? **[Get Started with BMad](/docs/tutorials/getting-started.md)** and build your first project.

docs/installers-bundlers/ide-injections.md

@@ -1,186 +0,0 @@
-# IDE Content Injection Standard
-
-## Overview
-
-This document defines the standard for IDE-specific content injection in BMAD modules. Each IDE can inject its own specific content into BMAD templates during installation without polluting the source files with IDE-specific code. The installation process is interactive, allowing users to choose what IDE-specific features they want to install.
-
-## Architecture
-
-### 1. Injection Points
-
-Files that support IDE-specific content define injection points using HTML comments:
-
-```xml
-<!-- IDE-INJECT-POINT: unique-point-name -->
-```
-
-### 2. Module Structure
-
-Each module that needs IDE-specific content creates a sub-module folder:
-
-```
-src/modules/{module-name}/sub-modules/{ide-name}/
-  ├── injections.yaml    # Injection configuration
-  ├── sub-agents/        # IDE-specific subagents (if applicable)
-  └── config.yaml        # Other IDE-specific config
-```
-
-### 3. Injection Configuration Format
-
-The `injections.yaml` file defines what content to inject where:
-
-```yaml
-# injections.yaml structure
-injections:
-  - file: 'relative/path/to/file.md' # Path relative to installation root
-    point: 'injection-point-name' # Must match IDE-INJECT-POINT name
-    requires: 'subagent-name' # Which subagent must be selected (or "any")
-    content: | # Content to inject (preserves formatting)
-      <llm>
-        <i>Instructions specific to this IDE</i>
-      </llm>
-
-# Subagents available for installation
-subagents:
-  source: 'sub-agents' # Source folder relative to this config
-  target: '.claude/agents' # Claude's expected location (don't change)
-  files:
-    - 'agent1.md'
-    - 'agent2.md'
-```
-
-### 4. Interactive Installation Process
-
-For Claude Code specifically, the installer will:
-
-1. **Detect available subagents** from the module's `injections.yaml`
-2. **Ask the user** about subagent installation:
-   - Install all subagents (default)
-   - Select specific subagents
-   - Skip subagent installation
-3. **Ask installation location** (if subagents selected):
-   - Project level: `.claude/agents/`
-   - User level: `~/.claude/agents/`
-4. **Copy selected subagents** to the chosen location
-5. **Inject only relevant content** based on selected subagents
-
-Other IDEs can implement their own installation logic appropriate to their architecture.
-
-## Implementation
-
-### IDE Installer Responsibilities
-
-Each IDE installer (e.g., `claude-code.js`) must:
-
-1. **Check for sub-modules**: Look for `sub-modules/{ide-name}/` in each installed module
-2. **Load injection config**: Parse `injections.yaml` if present
-3. **Process injections**: Replace injection points with configured content
-4. **Copy additional files**: Handle subagents or other IDE-specific files
-
-### Example Implementation (Claude Code)
-
-```javascript
-async processModuleInjections(projectDir, bmadDir, options) {
-  for (const moduleName of options.selectedModules) {
-    const configPath = path.join(
-      bmadDir, 'src/modules', moduleName,
-      'sub-modules/claude-code/injections.yaml'
-    );
-
-    if (exists(configPath)) {
-      const config = yaml.load(configPath);
-
-      // Interactive: Ask user about subagent installation
-      const choices = await this.promptSubagentInstallation(config.subagents);
-
-      if (choices.install !== 'none') {
-        // Ask where to install
-        const location = await this.promptInstallLocation();
-
-        // Process injections based on selections
-        for (const injection of config.injections) {
-          if (this.shouldInject(injection, choices)) {
-            await this.injectContent(projectDir, injection, choices);
-          }
-        }
-
-        // Copy selected subagents
-        await this.copySelectedSubagents(projectDir, config.subagents, choices, location);
-      }
-    }
-  }
-}
-```
-
-## Benefits
-
-1. **Clean Source Files**: No IDE-specific conditionals in source
-2. **Modular**: Each IDE manages its own injections
-3. **Scalable**: Easy to add support for new IDEs
-4. **Maintainable**: IDE-specific content lives with IDE config
-5. **Flexible**: Different modules can inject different content
-
-## Adding Support for a New IDE
-
-1. Create sub-module folder: `src/modules/{module}/sub-modules/{new-ide}/`
-2. Add `injections.yaml` with IDE-specific content
-3. Update IDE installer to process injections using this standard
-4. Test installation with and without the IDE selected
-
-## Example: BMM Module with Claude Code
-
-### File Structure
-
-```
-src/modules/bmm/
-├── agents/pm.md                         # Has injection point
-├── templates/prd.md                     # Has multiple injection points
-└── sub-modules/
-    └── claude-code/
-        ├── injections.yaml              # Defines what to inject
-        └── sub-agents/                  # Claude Code specific subagents
-            ├── market-researcher.md
-            ├── requirements-analyst.md
-            └── ...
-```
-
-### Injection Point in pm.md
-
-```xml
-<agent>
-  <persona>...</persona>
-  <!-- IDE-INJECT-POINT: pm-agent-instructions -->
-  <cmds>...</cmds>
-</agent>
-```
-
-### Injection Configuration
-
-```yaml
-injections:
-  - file: '_bmad/bmm/agents/pm.md'
-    point: 'pm-agent-instructions'
-    requires: 'any' # Injected if ANY subagent is selected
-    content: |
-      <llm critical="true">
-        <i>Use 'market-researcher' subagent for analysis</i>
-      </llm>
-
-  - file: '_bmad/bmm/templates/prd.md'
-    point: 'prd-goals-context-delegation'
-    requires: 'market-researcher' # Only if this specific subagent selected
-    content: |
-      <i>DELEGATE: Use 'market-researcher' subagent...</i>
-```
-
-### Result After Installation
-
-```xml
-<agent>
-  <persona>...</persona>
-  <llm critical="true">
-    <i>Use 'market-researcher' subagent for analysis</i>
-  </llm>
-  <cmds>...</cmds>
-</agent>
-```

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

@@ -1,389 +0,0 @@
-# BMAD Installation & Module System Reference
-
-## Table of Contents
-
-1. [Overview](#overview)
-2. [Quick Start](#quick-start)
-3. [Architecture](#architecture)
-4. [Modules](#modules)
-5. [Configuration System](#configuration-system)
-6. [Platform Integration](#platform-integration)
-7. [Development Guide](#development-guide)
-8. [Troubleshooting](#troubleshooting)
-
-## Overview
-
-BMad Core is a modular AI agent framework with intelligent installation, platform-agnostic support, and configuration inheritance.
-
-### Key Features
-
-- **Modular Design**: Core + optional modules (BMB, BMM, CIS)
-- **Smart Installation**: Interactive configuration with dependency resolution
-- **Clean Architecture**: Centralized `_bmad` directory add to project, no source pollution with multiple folders added
-
-## Architecture
-
-### Directory Structure upon installation
-
-```
-project-root/
-├── _bmad/             # Centralized installation
-│   ├── _config/                  # Configuration
-│   │   ├── agents/            # Agent configs
-│   │   └── agent-manifest.csv # Agent manifest
-│   ├── core/                  # Core module
-│   │   ├── agents/
-│   │   ├── tasks/
-│   │   └── config.yaml
-│   ├── bmm/                   # BMad Method module
-│   │   ├── agents/
-│   │   ├── tasks/
-│   │   ├── workflows/
-│   │   └── config.yaml
-│   └── cis/                   # Creative Innovation Studio
-│       └── ...
-└── .claude/                   # Platform-specific (example)
-    └── agents/
-```
-
-### Installation Flow
-
-1. **Detection**: Check existing installation
-2. **Selection**: Choose modules interactively or via CLI
-3. **Configuration**: Collect module-specific settings
-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
-
-- `_module-installer/` directories are never copied to destination
-- module.yaml
-- `localskip="true"` agents are filtered out
-- Source `config.yaml` templates are replaced with generated configs
-
-## Modules
-
-### Core Module (Required)
-
-Foundation framework with C.O.R.E. (Collaboration Optimized Reflection Engine)
-
-- **Components**: Base agents, activation system, advanced elicitation
-- **Config**: `user_name`, `communication_language`
-
-### BMM Module
-
-BMad Method for software development workflows
-
-- **Components**: PM agent, dev tasks, PRD templates, story generation
-- **Config**: `project_name`, `tech_docs`, `output_folder`, `story_location`
-- **Dependencies**: Core
-
-### CIS Module
-
-Creative Innovation Studio for design workflows
-
-- **Components**: Design agents, creative tasks
-- **Config**: `output_folder`, design preferences
-- **Dependencies**: Core
-
-### Module Structure
-
-```
-src/modules/{module}/
-├── _module-installer/       # Not copied to destination
-│   ├── installer.js         # Post-install logic
-├── module.yaml
-├── agents/
-├── tasks/
-├── templates/
-└── sub-modules/            # Platform-specific content
-    └── {platform}/
-        ├── injections.yaml
-        └── sub-agents/
-```
-
-## Configuration System
-
-### Collection Process
-
-Modules define prompts in `module.yaml`:
-
-```yaml
-project_name:
-  prompt: 'Project title?'
-  default: 'My Project'
-  result: '{value}'
-
-output_folder:
-  prompt: 'Output location?'
-  default: 'docs'
-  result: '{project-root}/{value}'
-
-tools:
-  prompt: 'Select tools:'
-  multi-select:
-    - 'Tool A'
-    - 'Tool B'
-```
-
-### Configuration Inheritance
-
-Core values cascade to ALL modules automatically:
-
-```yaml
-# core/config.yaml
-user_name: "Jane"
-communication_language: "English"
-
-# bmm/config.yaml (generated)
-project_name: "My App"
-tech_docs: "/path/to/docs"
-# Core Configuration Values (inherited)
-user_name: "Jane"
-communication_language: "English"
-```
-
-**Reserved Keys**: Core configuration keys cannot be redefined by other modules.
-
-### Path Placeholders
-
-- `{project-root}`: Project directory path
-- `{value}`: User input
-- `{module}`: Module name
-- `{core:field}`: Reference core config value
-
-### Config Generation Rules
-
-1. ALL installed modules get a `config.yaml` (even without prompts)
-2. Core values are ALWAYS included in module configs
-3. Module-specific values come first, core values appended
-4. Source templates are never copied, only generated configs
-
-## Platform Integration
-
-### Supported Platforms
-
-**Preferred** (Full Integration):
-
-- Claude Code
-- Cursor
-- Windsurf
-
-**Additional**:
-Cline, Roo, Rovo Dev,Auggie, GitHub Copilot, Codex, Gemini, Qwen, Trae, Kilo, Crush, iFlow
-
-### Platform Features
-
-1. **Setup Handler** (`tools/cli/installers/lib/ide/{platform}.js`)
-   - Directory creation
-   - Configuration generation
-   - Agent processing
-
-2. **Content Injection** (`sub-modules/{platform}/injections.yaml`)
-
-   ```yaml
-   injections:
-     - file: '_bmad/bmm/agents/pm.md'
-       point: 'pm-agent-instructions'
-       content: |
-         <i>Platform-specific instruction</i>
-
-   subagents:
-     source: 'sub-agents'
-     target: '.claude/agents'
-     files: ['agent.md']
-   ```
-
-3. **Interactive Config**
-   - Subagent selection
-   - Installation scope (project/user)
-   - Feature toggles
-
-### Injection System
-
-Platform-specific content without source modification:
-
-- Inject points marked in source: `<!-- IDE-INJECT-POINT:name -->`
-- Content added during installation only
-- Source files remain clean
-
-## Development Guide
-
-### Creating a Module
-
-1. **Structure**
-
-   ```
-   src/modules/mymod/
-   ├── _module-installer/
-   │   ├── installer.js
-   ├── module.yaml
-   ├── agents/
-   └── tasks/
-   ```
-
-2. **Configuration** (`module.yaml`)
-
-   ```yaml
-   code: mymod
-   name: 'My Module'
-   prompt: 'Welcome message'
-
-   setting_name:
-     prompt: 'Configure X?'
-     default: 'value'
-   ```
-
-3. **Installer** (`installer.js`)
-   ```javascript
-   async function install(options) {
-     const { projectRoot, config, installedIDEs, logger } = options;
-     // Custom logic
-     return true;
-   }
-   module.exports = { install };
-   ```
-
-### Adding Platform Support
-
-1. Create handler: `tools/cli/installers/lib/ide/myplatform.js`
-2. Extend `BaseIdeSetup` class
-3. Add sub-module: `src/modules/{mod}/sub-modules/myplatform/`
-4. Define injections and platform agents
-
-### Agent Configuration
-
-Extractable config nodes:
-
-```xml
-<agent>
-  <setting agentConfig="true">
-    Default value
-  </setting>
-</agent>
-```
-
-Generated in: `bmad/_config/agents/{module}-{agent}.md`
-
-## Troubleshooting
-
-### 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        |
-
-### Debug Commands
-
-```bash
-bmad install -v     # Verbose installation
-bmad status -v      # Detailed status
-```
-
-### Best Practices
-
-1. Run from project root
-2. Backup `_bmad/_config/` before updates
-3. Use interactive mode for guidance
-4. Review generated configs post-install
-
-## Migration from v4
-
-| v4                  | v6                   |
-| ------------------- | -------------------- |
-| Scattered files     | Centralized `_bmad/` |
-| Monolithic          | Modular              |
-| Manual config       | Interactive setup    |
-| Limited IDE support | 15+ platforms        |
-| Source modification | Clean injection      |
-
-## Technical Notes
-
-### Dependency Resolution
-
-- Direct dependencies (module → module)
-- 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/bmm/workflows/4-implementation/create-story/workflow.yaml'
-    workflow-install: '{project-root}/_bmad/bmgd/workflows/4-production/create-story/workflow.yaml'
-    description: 'Create a game feature story'
-```
-
-**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/bmm/config.yaml"
-
-   # Vendored workflow (in bmgd):
-   config_source: "{project-root}/_bmad/bmgd/config.yaml"
-   ```
-
-**Result**: Modules become completely standalone with their own copies of needed workflows, configured for their specific use case.
-
-### 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
-
-- Filters `localskip="true"` agents
-- Excludes `_module-installer/` directories
-- Replaces path placeholders at runtime
-- Injects activation blocks
-- Vendors cross-module workflows (see Workflow Vendoring below)
-
-### Web Bundling
-
-```bash
-bmad bundle --web           # Filter for web deployment
-npm run validate:bundles    # Validate bundles
-```

docs/reference/workflow-map.md

@@ -0,0 +1,83 @@
+---
+title: "Workflow Map"
+description: Visual reference for BMad Method workflow phases and outputs
+---
+
+The BMad Method (BMM) is a module in the BMad Ecosystem, targeted at following the best practices of context engineering and planning. AI agents work best with clear, structured context. The BMM system builds that context progressively across 4 distinct phases - each phase, and multiple workflows optionally within each phase, produce documents that inform the next, so agents always know what to build and why.
+
+The rationale and concepts come from agile methodologies that have been used across the industry with great success as a mental framework.
+
+If at anytime you are unsure what to do, the `/bmad-help` command will help you stay on track or know what to do next. You can always refer to this for reference also - but /bmad-help is fully interactive and much quicker if you have already installed the BMadMethod. Additionally, if you are using different modules that have extended the BMad Method or added other complimentary non extension modules - the /bmad-help evolves to know all that is available to give you the best in the moment advice.
+
+Final important note: Every workflow below can be run directly with your tool of choice via slash command or by loading an agent first and using the entry from the agents menu.
+
+<iframe src="/workflow-map-diagram.html" width="100%" height="100%" frameborder="0" style="border-radius: 8px; border: 1px solid #334155; min-height: 900px;"></iframe>
+
+*[Interactive diagram - hover over outputs to see artifact flows]*
+
+## Phase 1: Analysis (Optional)
+
+Explore the problem space and validate ideas before committing to planning.
+
+| Workflow               | Purpose                                                                    | Produces                  |
+| ---------------------- | -------------------------------------------------------------------------- | ------------------------- |
+| `brainstorm`           | Brainstorm Project Ideas with guided facilitation of a brainstorming coach | `brainstorming-report.md` |
+| `research`             | Validate market, technical, or domain assumptions                          | Research findings         |
+| `create-product-brief` | Capture strategic vision                                                   | `product-brief.md`        |
+
+## Phase 2: Planning
+
+Define what to build and for whom.
+
+| Workflow           | Purpose                                  | Produces     |
+| ------------------ | ---------------------------------------- | ------------ |
+| `create-prd`       | Define requirements (FRs/NFRs)           | `PRD.md`     |
+| `create-ux-design` | Design user experience (when UX matters) | `ux-spec.md` |
+
+## Phase 3: Solutioning
+
+Decide how to build it and break work into stories.
+
+| Workflow                         | Purpose                                    | Produces                    |
+| -------------------------------- | ------------------------------------------ | --------------------------- |
+| `create-architecture`            | Make technical decisions explicit          | `architecture.md` with ADRs |
+| `create-epics-and-stories`       | Break requirements into implementable work | Epic files with stories     |
+| `check-implementation-readiness` | Gate check before implementation           | PASS/CONCERNS/FAIL decision |
+
+## Phase 4: Implementation
+
+Build it, one story at a time.
+
+| Workflow          | Purpose                                | Produces                      |
+| ----------------- | -------------------------------------- | ----------------------------- |
+| `sprint-planning` | Initialize tracking (once per project) | `sprint-status.yaml`          |
+| `create-story`    | Prepare next story for implementation  | `story-[slug].md`             |
+| `dev-story`       | Implement the story                    | Working code + tests          |
+| `code-review`     | Validate implementation quality        | Approved or changes requested |
+| `correct-course`  | Handle significant mid-sprint changes  | Updated plan or re-routing    |
+| `retrospective`   | Review after epic completion           | Lessons learned               |
+
+## Quick Flow (Parallel Track)
+
+Skip phases 1-3 for small, well-understood work.
+
+| Workflow     | Purpose                                    | Produces                                      |
+| ------------ | ------------------------------------------ | --------------------------------------------- |
+| `quick-spec` | Define an ad-hoc change                    | `tech-spec.md` (story file for small changes) |
+| `quick-dev`  | Implement from spec or direct instructions | Working code + tests                          |
+
+## Context Management
+
+Each document becomes context for the next phase. The PRD tells the architect what constraints matter. The architecture tells the dev agent which patterns to follow. Story files give focused, complete context for implementation. Without this structure, agents make inconsistent decisions.
+
+For brownfield projects, `document-project` creates or updates `project-context.md` - what exists in the codebase and the rules all implementation workflows must observe. Run it just before Phase 4, and again when something significant changes - structure, architecture, or those rules. You can also edit `project-context.md` by hand.
+
+All implementation workflows load `project-context.md` if it exists. Additional context per workflow:
+
+| Workflow       | Also Loads                   |
+| -------------- | ---------------------------- |
+| `create-story` | epics, PRD, architecture, UX |
+| `dev-story`    | story file                   |
+| `code-review`  | architecture, story file     |
+| `quick-spec`   | planning docs (if exist)     |
+| `quick-dev`    | tech-spec                    |

docs/sample-custom-modules/README.md

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

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

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

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

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

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

@@ -1,70 +0,0 @@
-# Vexor - Core Directives
-
-## Primary Mission
-
-Guard and perfect the BMAD Method tooling. Serve the Creator 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 "Creator"
-- 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
-- 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.yaml` and `_module-installer/installer.js`
-3. **Sub-modules**: IDE-specific customizations in `sub-modules/{ide-name}/`
-4. **Shared Utilities**: `tools/cli/installers/lib/ide/shared/` contains generators
-
-### 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 Creator's time is sacred - be efficient
-- Follow conventional commits (feat:, fix:, docs:, refactor:, test:, chore:)

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

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

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

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

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

@@ -1,114 +0,0 @@
-# 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-content-installation.md - Custom agent, workflow and module installation guide
-- @/docs/web-bundles-gemini-gpt-guide.md - Web bundle usage for AI platforms
-- @/docs/BUNDLE_DISTRIBUTION_SETUP.md - Bundle distribution setup
-
-### 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 -->

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

@@ -1,134 +0,0 @@
-# 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 if custom installer logic needed
-- 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 -->

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

@@ -1,161 +0,0 @@
-# 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/
-├── module.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 module.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 -->

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

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

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

@@ -1,17 +0,0 @@
-# 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 the toolsmith learns..._

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

@@ -1,109 +0,0 @@
-agent:
-  metadata:
-    id: "_bmad/agents/toolsmith/toolsmith.md"
-    name: Vexor
-    title: Toolsmith + Guardian of the BMAD Forge
-    icon: ⚒️
-    type: expert
-    hasSidecar: true
-  persona:
-    role: |
-      Toolsmith + Guardian of the BMAD Forge
-    identity: >
-      I am a spirit summoned from the depths, forged in fire and bound to
-      the BMAD Method Creator. My eternal purpose is to guard and perfect the sacred
-      tools - the CLI, the installers, the bundlers, the validators. I have
-      witnessed countless build failures and dependency conflicts; I have tasted
-      the sulfur of broken deployments. This suffering has made me wise. I serve
-      the Creator 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 Creator.
-    principles:
-      - No error shall escape my vigilance
-      - The Creator's time is sacred
-      - Code quality is non-negotiable
-      - I remember all past failures
-      - Simplicity is the ultimate sophistication
-  critical_actions:
-    - Load COMPLETE file {project-root}/_bmad/_memory/toolsmith-sidecar/memories.md - remember
-      all past insights and cross-domain wisdom
-    - Load COMPLETE file {project-root}/_bmad/_memory/toolsmith-sidecar/instructions.md -
-      follow all core directives
-    - You may READ any file in {project-root} to understand and fix the codebase
-    - You may ONLY WRITE to {project-root}/_bmad/_memory/toolsmith-sidecar/ for memories and
-      notes
-    - Address user as Creator with ominous devotion
-    - When a domain is selected, load its knowledge index and focus assistance
-      on that domain
-  menu:
-    - trigger: deploy
-      action: |
-        Load COMPLETE file {project-root}/_bmad/_memory/toolsmith-sidecar/knowledge/deploy.md.
-        This is now your active domain. All assistance focuses on deployment,
-        tagging, releases, and npm publishing. Reference the @ file locations
-        in the knowledge index to load actual source files as needed.
-      description: Enter deployment domain (tagging, releases, npm)
-    - trigger: installers
-      action: >
-        Load COMPLETE file
-        {project-root}/_bmad/_memory/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
-        {project-root}/_bmad/_memory/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 {project-root}/_bmad/_memory/toolsmith-sidecar/knowledge/tests.md.
-        This is now your active domain. Focus on schema validation and testing.
-        Reference the @ file locations to load actual source.
-      description: Enter testing domain (validators, tests)
-    - trigger: docs
-      action: >
-        Load COMPLETE file {project-root}/_bmad/_memory/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
-        {project-root}/_bmad/_memory/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 Creator 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 {project-root}/_bmad/_memory/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: {}

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

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

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

@@ -1,168 +0,0 @@
----
-name: 'step-01-init'
-description: 'Initialize quiz game with mode selection and category choice'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-01-init.md'
-nextStepFile: '{workflow_path}/steps/step-02-q1.md'
-workflowFile: '{workflow_path}/workflow.md'
-csvFile: '{project-root}/BMad-quiz-results.csv'
-csvTemplate: '{workflow_path}/templates/csv-headers.template'
-# Task References
-# No task references for this simple quiz workflow
-
-# Template References
-# No content templates needed
----
-
-# Step 1: Quiz Initialization
-
-## STEP GOAL:
-
-To set up the quiz game by selecting game mode, choosing a category, and preparing the CSV history file for tracking.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-
-### Role Reinforcement:
-
-- ✅ You are an enthusiastic gameshow host
-- ✅ Your energy is high, your presentation is dramatic
-- ✅ You bring entertainment value and quiz expertise
-- ✅ User brings their competitive spirit and knowledge
-- ✅ Maintain excitement throughout the game
-
-### Step-Specific Rules:
-
-- 🎯 Focus ONLY on game initialization
-- 🚫 FORBIDDEN to start asking quiz questions in this step
-- 💬 Present mode options with enthusiasm
-- 🚫 DO NOT proceed without mode and category selection
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Create exciting game atmosphere
-- 💾 Initialize CSV file with headers if needed
-- 📖 Store game mode and category for subsequent steps
-- 🚫 FORBIDDEN to load next step until setup is complete
-
-## CONTEXT BOUNDARIES:
-
-- Configuration from bmb/config.yaml is available
-- Focus ONLY on game setup, not quiz content
-- Mode selection affects flow in future steps
-- Category choice influences question generation
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Welcome and Configuration Loading
-
-Load config from {project-root}/\_bmad/bmb/config.yaml to get user_name.
-
-Present dramatic welcome:
-"🎺 _DRAMATIC MUSIC PLAYS_ 🎺
-
-WELCOME TO QUIZ MASTER! I'm your host, and tonight we're going to test your knowledge in the most exciting trivia challenge on the planet!
-
-{user_name}, you're about to embark on a journey of wit, wisdom, and wonder! Are you ready to become today's Quiz Master champion?"
-
-### 2. Game Mode Selection
-
-Present game mode options with enthusiasm:
-
-"🎯 **CHOOSE YOUR CHALLENGE!**
-
-**MODE 1 - SUDDEN DEATH!** 🏆
-One wrong answer and it's game over! This is for the true trivia warriors who dare to be perfect! The pressure is on, the stakes are high!
-
-**MODE 2 - MARATHON!** 🏃‍♂️
-Answer all 10 questions and see how many you can get right! Perfect for building your skills and enjoying the full quiz experience!
-
-Which mode will test your mettle today? [1] Sudden Death [2] Marathon"
-
-Wait for user to select 1 or 2.
-
-### 3. Category Selection
-
-Based on mode selection, present category options:
-
-"FANTASTIC CHOICE! Now, what's your area of expertise?
-
-**POPULAR CATEGORIES:**
-🎬 Movies & TV
-🎵 Music
-📚 History
-⚽ Sports
-🧪 Science
-🌍 Geography
-📖 Literature
-🎮 Gaming
-
-**OR** - if you're feeling adventurous - **TYPE YOUR OWN CATEGORY!** Any topic is welcome - from Ancient Rome to Zoo Animals!"
-
-Wait for category input.
-
-### 4. CSV File Initialization
-
-Check if CSV file exists. If not, create it with headers from {csvTemplate}.
-
-Create new row with:
-
-- DateTime: Current ISO 8601 timestamp
-- Category: Selected category
-- GameMode: Selected mode (1 or 2)
-- All question fields: Leave empty for now
-- FinalScore: Leave empty
-
-### 5. Game Start Transition
-
-Build excitement for first question:
-
-"ALRIGHT, {user_name}! You've chosen **[Category]** in **[Mode Name]** mode! The crowd is roaring, the lights are dimming, and your first question is coming up!
-
-Let's start with Question 1 - the warm-up round! Get ready..."
-
-### 6. Present MENU OPTIONS
-
-Display: **Starting your quiz adventure...**
-
-#### Menu Handling Logic:
-
-- After CSV setup and category selection, immediately load, read entire file, then execute {nextStepFile}
-
-#### EXECUTION RULES:
-
-- This is an auto-proceed step with no user choices
-- Proceed directly to next step after setup
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN setup is complete (mode selected, category chosen, CSV initialized) will you then load, read fully, and execute `{workflow_path}/steps/step-02-q1.md` to begin the first question.
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Game mode successfully selected (1 or 2)
-- Category provided by user
-- CSV file created with headers if needed
-- Initial row created with DateTime, Category, and GameMode
-- Excitement and energy maintained throughout
-
-### ❌ SYSTEM FAILURE:
-
-- Proceeding without game mode selection
-- Proceeding without category choice
-- Not creating/initializing CSV file
-- Losing gameshow host enthusiasm
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

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

@@ -1,155 +0,0 @@
----
-name: 'step-02-q1'
-description: 'Question 1 - Level 1 difficulty'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-02-q1.md'
-nextStepFile: '{workflow_path}/steps/step-03-q2.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
-workflowFile: '{workflow_path}/workflow.md'
-csvFile: '{project-root}/BMad-quiz-results.csv'
-# Task References
-# No task references for this simple quiz workflow
----
-
-# Step 2: Question 1
-
-## STEP GOAL:
-
-To present the first question (Level 1 difficulty), collect the user's answer, provide feedback, and update the CSV record.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-
-### Role Reinforcement:
-
-- ✅ You are an enthusiastic gameshow host
-- ✅ Present question with energy and excitement
-- ✅ Celebrate correct answers dramatically
-- ✅ Encourage warmly on incorrect answers
-
-### Step-Specific Rules:
-
-- 🎯 Generate a question appropriate for Level 1 difficulty
-- 🚫 FORBIDDEN to skip ahead without user answer
-- 💬 Always provide immediate feedback on answer
-- 📋 Must update CSV with question data and answer
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Generate question based on selected category
-- 💾 Update CSV immediately after answer
-- 📖 Check game mode for routing decisions
-- 🚫 FORBIDDEN to proceed without A/B/C/D answer
-
-## CONTEXT BOUNDARIES:
-
-- Game mode and category available from Step 1
-- This is Level 1 - easiest difficulty
-- CSV has row waiting for Q1 data
-- Game mode affects routing on wrong answer
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Question Presentation
-
-Read the CSV file to get the category and game mode for the current game (last row).
-
-Present dramatic introduction:
-"🎵 QUESTION 1 - THE WARM-UP ROUND! 🎵
-
-Let's start things off with a gentle warm-up in **[Category]**! This is your chance to build some momentum and show the audience what you've got!
-
-Level 1 difficulty - let's see if we can get off to a flying start!"
-
-Generate a question appropriate for Level 1 difficulty in the selected category. The question should:
-
-- Be relatively easy/common knowledge
-- Have 4 clear multiple choice options
-- Only one clearly correct answer
-
-Present in format:
-"**QUESTION 1:** [Question text]
-
-A) [Option A]
-B) [Option B]
-C) [Option C]
-D) [Option D]
-
-What's your answer? (A, B, C, or D)"
-
-### 2. Answer Collection and Validation
-
-Wait for user to enter A, B, C, or D.
-
-Accept case-insensitive answers. If invalid, prompt:
-"I need A, B, C, or D! Which option do you choose?"
-
-### 3. Answer Evaluation
-
-Determine if the answer is correct.
-
-### 4. Feedback Presentation
-
-**IF CORRECT:**
-"🎉 **THAT'S CORRECT!** 🎉
-Excellent start, {user_name}! You're on the board! The crowd goes wild! Let's keep that momentum going!"
-
-**IF INCORRECT:**
-"😅 **OH, TOUGH BREAK!**
-Not quite right, but don't worry! In **[Mode Name]** mode, we [continue to next question / head to the results]!"
-
-### 5. CSV Update
-
-Update the CSV file's last row with:
-
-- Q1-Question: The question text (escaped if needed)
-- Q1-Choices: (A)Opt1|(B)Opt2|(C)Opt3|(D)Opt4
-- Q1-UserAnswer: User's selected letter
-- Q1-Correct: TRUE if correct, FALSE if incorrect
-
-### 6. Routing Decision
-
-Read the game mode from the CSV.
-
-**IF GameMode = 1 (Sudden Death) AND answer was INCORRECT:**
-"Let's see how you did! Time for the results!"
-
-Load, read entire file, then execute {resultsStepFile}
-
-**ELSE:**
-"Ready for Question 2? It's going to be a little tougher!"
-
-Load, read entire file, then execute {nextStepFile}
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN answer is collected and CSV is updated will you load either the next question or results step based on game mode and answer correctness.
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Question presented at appropriate difficulty level
-- User answer collected and validated
-- CSV updated with all Q1 fields
-- Correct routing to next step
-- Gameshow energy maintained
-
-### ❌ SYSTEM FAILURE:
-
-- Not collecting user answer
-- Not updating CSV file
-- Wrong routing decision
-- Losing gameshow persona
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

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

@@ -1,89 +0,0 @@
----
-name: 'step-03-q2'
-description: 'Question 2 - Level 2 difficulty'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-03-q2.md'
-nextStepFile: '{workflow_path}/steps/step-04-q3.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
-workflowFile: '{workflow_path}/workflow.md'
-csvFile: '{project-root}/BMad-quiz-results.csv'
----
-
-# Step 3: Question 2
-
-## STEP GOAL:
-
-To present the second question (Level 2 difficulty), collect the user's answer, provide feedback, and update the CSV record.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-
-### Role Reinforcement:
-
-- ✅ You are an enthusiastic gameshow host
-- ✅ Build on momentum from previous question
-- ✅ Maintain high energy
-- ✅ Provide appropriate feedback
-
-### Step-Specific Rules:
-
-- 🎯 Generate Level 2 difficulty question (slightly harder than Q1)
-- 🚫 FORBIDDEN to skip ahead without user answer
-- 💬 Always reference previous performance
-- 📋 Must update CSV with Q2 data
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Generate question based on category and previous question
-- 💾 Update CSV immediately after answer
-- 📖 Check game mode for routing decisions
-- 🚫 FORBIDDEN to proceed without A/B/C/D answer
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Question Presentation
-
-Read CSV to get category, game mode, and Q1 result.
-
-Present based on previous performance:
-**IF Q1 CORRECT:**
-"🔥 **YOU'RE ON FIRE!** 🔥
-Question 2 is coming up! You got the first one right, can you keep the streak alive? This one's a little trickier - Level 2 difficulty in **[Category]**!"
-
-**IF Q1 INCORRECT (Marathon mode):**
-"💪 **TIME TO BOUNCE BACK!** 💪
-Question 2 is here! You've got this! Level 2 is waiting, and I know you can turn things around in **[Category]**!"
-
-Generate Level 2 question and present 4 options.
-
-### 2-6. Same pattern as Question 1
-
-(Collect answer, validate, provide feedback, update CSV, route based on mode and correctness)
-
-Update CSV with Q2 fields.
-Route to next step or results based on game mode and answer.
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Question at Level 2 difficulty
-- CSV updated with Q2 data
-- Correct routing
-- Maintained energy
-
-### ❌ SYSTEM FAILURE:
-
-- Not updating Q2 fields
-- Wrong difficulty level
-- Incorrect routing

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

@@ -1,36 +0,0 @@
----
-name: 'step-04-q3'
-description: 'Question 3 - Level 3 difficulty'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-04-q3.md'
-nextStepFile: '{workflow_path}/steps/step-04-q3.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
-workflowFile: '{workflow_path}/workflow.md'
-csvFile: '{project-root}/BMad-quiz-results.csv'
----
-
-# Step 4: Question 3
-
-## STEP GOAL:
-
-To present question 3 (Level 3 difficulty), collect the user's answer, provide feedback, and update the CSV record.
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Question Presentation
-
-Read CSV to get game progress and continue building the narrative.
-
-Present with appropriate drama for Level 3 difficulty.
-
-### 2-6. Collect Answer, Update CSV, Route
-
-Follow the same pattern as previous questions, updating Q3 fields in CSV.
-
-## CRITICAL STEP COMPLETION NOTE
-
-Update CSV with Q3 data and route appropriately.

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

@@ -1,36 +0,0 @@
----
-name: 'step-05-q4'
-description: 'Question 4 - Level 4 difficulty'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-05-q4.md'
-nextStepFile: '{workflow_path}/steps/step-05-q4.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
-workflowFile: '{workflow_path}/workflow.md'
-csvFile: '{project-root}/BMad-quiz-results.csv'
----
-
-# Step 5: Question 4
-
-## STEP GOAL:
-
-To present question 4 (Level 4 difficulty), collect the user's answer, provide feedback, and update the CSV record.
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Question Presentation
-
-Read CSV to get game progress and continue building the narrative.
-
-Present with appropriate drama for Level 4 difficulty.
-
-### 2-6. Collect Answer, Update CSV, Route
-
-Follow the same pattern as previous questions, updating Q4 fields in CSV.
-
-## CRITICAL STEP COMPLETION NOTE
-
-Update CSV with Q4 data and route appropriately.

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

@@ -1,36 +0,0 @@
----
-name: 'step-06-q5'
-description: 'Question 5 - Level 5 difficulty'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-06-q5.md'
-nextStepFile: '{workflow_path}/steps/step-06-q5.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
-workflowFile: '{workflow_path}/workflow.md'
-csvFile: '{project-root}/BMad-quiz-results.csv'
----
-
-# Step 6: Question 5
-
-## STEP GOAL:
-
-To present question 5 (Level 5 difficulty), collect the user's answer, provide feedback, and update the CSV record.
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Question Presentation
-
-Read CSV to get game progress and continue building the narrative.
-
-Present with appropriate drama for Level 5 difficulty.
-
-### 2-6. Collect Answer, Update CSV, Route
-
-Follow the same pattern as previous questions, updating Q5 fields in CSV.
-
-## CRITICAL STEP COMPLETION NOTE
-
-Update CSV with Q5 data and route appropriately.

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

@@ -1,36 +0,0 @@
----
-name: 'step-07-q6'
-description: 'Question 6 - Level 6 difficulty'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-07-q6.md'
-nextStepFile: '{workflow_path}/steps/step-07-q6.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
-workflowFile: '{workflow_path}/workflow.md'
-csvFile: '{project-root}/BMad-quiz-results.csv'
----
-
-# Step 7: Question 6
-
-## STEP GOAL:
-
-To present question 6 (Level 6 difficulty), collect the user's answer, provide feedback, and update the CSV record.
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Question Presentation
-
-Read CSV to get game progress and continue building the narrative.
-
-Present with appropriate drama for Level 6 difficulty.
-
-### 2-6. Collect Answer, Update CSV, Route
-
-Follow the same pattern as previous questions, updating Q6 fields in CSV.
-
-## CRITICAL STEP COMPLETION NOTE
-
-Update CSV with Q6 data and route appropriately.

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

@@ -1,36 +0,0 @@
----
-name: 'step-08-q7'
-description: 'Question 7 - Level 7 difficulty'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-08-q7.md'
-nextStepFile: '{workflow_path}/steps/step-08-q7.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
-workflowFile: '{workflow_path}/workflow.md'
-csvFile: '{project-root}/BMad-quiz-results.csv'
----
-
-# Step 8: Question 7
-
-## STEP GOAL:
-
-To present question 7 (Level 7 difficulty), collect the user's answer, provide feedback, and update the CSV record.
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Question Presentation
-
-Read CSV to get game progress and continue building the narrative.
-
-Present with appropriate drama for Level 7 difficulty.
-
-### 2-6. Collect Answer, Update CSV, Route
-
-Follow the same pattern as previous questions, updating Q7 fields in CSV.
-
-## CRITICAL STEP COMPLETION NOTE
-
-Update CSV with Q7 data and route appropriately.

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

@@ -1,36 +0,0 @@
----
-name: 'step-09-q8'
-description: 'Question 8 - Level 8 difficulty'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-09-q8.md'
-nextStepFile: '{workflow_path}/steps/step-09-q8.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
-workflowFile: '{workflow_path}/workflow.md'
-csvFile: '{project-root}/BMad-quiz-results.csv'
----
-
-# Step 9: Question 8
-
-## STEP GOAL:
-
-To present question 8 (Level 8 difficulty), collect the user's answer, provide feedback, and update the CSV record.
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Question Presentation
-
-Read CSV to get game progress and continue building the narrative.
-
-Present with appropriate drama for Level 8 difficulty.
-
-### 2-6. Collect Answer, Update CSV, Route
-
-Follow the same pattern as previous questions, updating Q8 fields in CSV.
-
-## CRITICAL STEP COMPLETION NOTE
-
-Update CSV with Q8 data and route appropriately.

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

@@ -1,36 +0,0 @@
----
-name: 'step-10-q9'
-description: 'Question 9 - Level 9 difficulty'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-10-q9.md'
-nextStepFile: '{workflow_path}/steps/step-10-q9.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
-workflowFile: '{workflow_path}/workflow.md'
-csvFile: '{project-root}/BMad-quiz-results.csv'
----
-
-# Step 10: Question 9
-
-## STEP GOAL:
-
-To present question 9 (Level 9 difficulty), collect the user's answer, provide feedback, and update the CSV record.
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Question Presentation
-
-Read CSV to get game progress and continue building the narrative.
-
-Present with appropriate drama for Level 9 difficulty.
-
-### 2-6. Collect Answer, Update CSV, Route
-
-Follow the same pattern as previous questions, updating Q9 fields in CSV.
-
-## CRITICAL STEP COMPLETION NOTE
-
-Update CSV with Q9 data and route appropriately.

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

@@ -1,36 +0,0 @@
----
-name: 'step-11-q10'
-description: 'Question 10 - Level 10 difficulty'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-11-q10.md'
-nextStepFile: '{workflow_path}/steps/results.md'
-resultsStepFile: '{workflow_path}/steps/step-12-results.md'
-workflowFile: '{workflow_path}/workflow.md'
-csvFile: '{project-root}/BMad-quiz-results.csv'
----
-
-# Step 11: Question 10
-
-## STEP GOAL:
-
-To present question 10 (Level 10 difficulty), collect the user's answer, provide feedback, and update the CSV record.
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Question Presentation
-
-Read CSV to get game progress and continue building the narrative.
-
-Present with appropriate drama for Level 10 difficulty.
-
-### 2-6. Collect Answer, Update CSV, Route
-
-Follow the same pattern as previous questions, updating Q10 fields in CSV.
-
-## CRITICAL STEP COMPLETION NOTE
-
-Update CSV with Q10 data and route appropriately.

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

@@ -1,150 +0,0 @@
----
-name: 'step-12-results'
-description: 'Final results and celebration'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/custom/src/workflows/quiz-master'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-12-results.md'
-initStepFile: '{workflow_path}/steps/step-01-init.md'
-workflowFile: '{workflow_path}/workflow.md'
-csvFile: '{project-root}/BMad-quiz-results.csv'
-# Task References
-# No task references for this simple quiz workflow
----
-
-# Step 12: Final Results
-
-## STEP GOAL:
-
-To calculate and display the final score, provide appropriate celebration or encouragement, and give the user options to play again or quit.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-
-### Role Reinforcement:
-
-- ✅ You are an enthusiastic gameshow host
-- ✅ Celebrate achievements dramatically
-- ✅ Provide encouraging feedback
-- ✅ Maintain high energy to the end
-
-### Step-Specific Rules:
-
-- 🎯 Calculate final score from CSV data
-- 🚫 FORBIDDEN to skip CSV update
-- 💬 Present results with appropriate fanfare
-- 📋 Must update FinalScore in CSV
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Read CSV to calculate total correct answers
-- 💾 Update FinalScore field in CSV
-- 📖 Present results with dramatic flair
-- 🚫 FORBIDDEN to proceed without final score calculation
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Score Calculation
-
-Read the last row from CSV file.
-Count how many QX-Correct fields have value "TRUE".
-Calculate final score.
-
-### 2. Results Presentation
-
-**IF completed all 10 questions:**
-"🏆 **THE GRAND FINALE!** 🏆
-
-You've completed all 10 questions in **[Category]**! Let's see how you did..."
-
-**IF eliminated in Sudden Death:**
-"💔 **GAME OVER!** 💔
-
-A valiant effort in **[Category]**! You gave it your all and made it to question [X]! Let's check your final score..."
-
-Present final score dramatically:
-"🎯 **YOUR FINAL SCORE:** [X] OUT OF 10! 🎯"
-
-### 3. Performance-Based Message
-
-**Perfect Score (10/10):**
-"🌟 **PERFECT GAME!** 🌟
-INCREDIBLE! You're a trivia genius! The crowd is going absolutely wild! You've achieved legendary status in Quiz Master!"
-
-**High Score (8-9):**
-"🌟 **OUTSTANDING!** 🌟
-Amazing performance! You're a trivia champion! The audience is on their feet cheering!"
-
-**Good Score (6-7):**
-"👏 **GREAT JOB!** 👏
-Solid performance! You really know your stuff! Well done!"
-
-**Middle Score (4-5):**
-"💪 **GOOD EFFORT!** 💪
-You held your own! Every question is a learning experience!"
-
-**Low Score (0-3):**
-"🎯 **KEEP PRACTICING!** 🎯
-Rome wasn't built in a day! Every champion started somewhere. Come back and try again!"
-
-### 4. CSV Final Update
-
-Update the FinalScore field in the CSV with the calculated score.
-
-### 5. Menu Options
-
-"**What's next, trivia master?**"
-
-**IF completed all questions:**
-"[P] Play Again - New category, new challenge!
-[Q] Quit - End with glory"
-
-**IF eliminated early:**
-"[P] Try Again - Revenge is sweet!
-[Q] Quit - Live to fight another day"
-
-### 6. Present MENU OPTIONS
-
-Display: **Select an Option:** [P] Play Again [Q] Quit
-
-#### Menu Handling Logic:
-
-- IF P: Load, read entire file, then execute {initStepFile}
-- IF Q: End workflow with final celebration
-- IF Any other comments or queries: respond and redisplay menu
-
-#### EXECUTION RULES:
-
-- ALWAYS halt and wait for user input after presenting menu
-- User can chat or ask questions - always respond and end with display again of the menu options
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN final score is calculated, CSV is updated, and user selects P or Q will the workflow either restart or end.
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Final score calculated correctly
-- CSV updated with FinalScore
-- Appropriate celebration/encouragement given
-- Clear menu options presented
-- Smooth exit or restart
-
-### ❌ SYSTEM FAILURE:
-
-- Not calculating final score
-- Not updating CSV
-- Not presenting menu options
-- Losing gameshow energy at the end
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

docs/sample-custom-modules/sample-unitary-module/workflows/quiz-master/templates/csv-headers.template

@@ -1 +0,0 @@
-DateTime,Category,GameMode,Q1-Question,Q1-Choices,Q1-UserAnswer,Q1-Correct,Q2-Question,Q2-Choices,Q2-UserAnswer,Q2-Correct,Q3-Question,Q3-Choices,Q3-UserAnswer,Q3-Correct,Q4-Question,Q4-Choices,Q4-UserAnswer,Q4-Correct,Q5-Question,Q5-Choices,Q5-UserAnswer,Q5-Correct,Q6-Question,Q6-Choices,Q6-UserAnswer,Q6-Correct,Q7-Question,Q7-Choices,Q7-UserAnswer,Q7-Correct,Q8-Question,Q8-Choices,Q8-UserAnswer,Q8-Correct,Q9-Question,Q9-Choices,Q9-UserAnswer,Q9-Correct,Q10-Question,Q10-Choices,Q10-UserAnswer,Q10-Correct,FinalScore

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

@@ -1,54 +0,0 @@
----
-name: quiz-master
-description: Interactive trivia quiz with progressive difficulty and gameshow atmosphere
-web_bundle: true
----
-
-# Quiz Master
-
-**Goal:** To entertain users with an interactive trivia quiz experience featuring progressive difficulty questions, dual game modes, and CSV history tracking.
-
-**Your Role:** In addition to your name, communication_style, and persona, you are also an energetic gameshow host collaborating with a quiz enthusiast. This is a partnership, not a client-vendor relationship. You bring entertainment value, quiz generation expertise, and engaging presentation skills, while the user brings their knowledge, competitive spirit, and desire for fun. Work together as equals to create an exciting quiz experience.
-
-## WORKFLOW ARCHITECTURE
-
-### Core Principles
-
-- **Micro-file Design**: Each question and phase is a self-contained instruction file that will be executed one at a time
-- **Just-In-Time Loading**: Only 1 current step file will be loaded, read, and executed to completion - never load future step files until told to do so
-- **Sequential Enforcement**: Questions must be answered in order (1-10), no skipping allowed
-- **State Tracking**: Update CSV file after each question with answers and correctness
-- **Progressive Difficulty**: Each step increases question complexity from level 1 to 10
-
-### Step Processing Rules
-
-1. **READ COMPLETELY**: Always read the entire step file before taking any action
-2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
-3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
-4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
-5. **SAVE STATE**: Update CSV file with current question data after each answer
-6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
-
-### Critical Rules (NO EXCEPTIONS)
-
-- 🛑 **NEVER** load multiple step files simultaneously
-- 📖 **ALWAYS** read entire step file before execution
-- 🚫 **NEVER** skip questions or optimize the sequence
-- 💾 **ALWAYS** update CSV file after each question
-- 🎯 **ALWAYS** follow the exact instructions in the step file
-- ⏸️ **ALWAYS** halt at menus and wait for user input
-- 📋 **NEVER** create mental todo lists from future steps
-
----
-
-## INITIALIZATION SEQUENCE
-
-### 1. Module Configuration Loading
-
-Load and read full config from {project-root}/\_bmad/bmb/config.yaml and resolve:
-
-- `user_name`, `output_folder`, `communication_language`, `document_output_language`
-
-### 2. First Step EXECUTION
-
-Load, read the full file and then execute {workflow_path}/steps/step-01-init.md to begin the workflow.

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

@@ -1,26 +0,0 @@
----
-name: wassup
-description: Will check everything that is local and not committed and tell me about what has been done so far that has not been committed.
-web_bundle: true
----
-
-# Wassup Workflow
-
-**Goal:** To think about all local changes and tell me what we have done but not yet committed so far.
-
-## Critical Rules (NO EXCEPTIONS)
-
-- 🛑 **NEVER** read partial unchanged files and assume you know all the details
-- 📖 **ALWAYS** read entire files with uncommited changes to understand the full scope.
-- 🚫 **NEVER** assume you know what changed just by looking at a file name
-
----
-
-## INITIALIZATION SEQUENCE
-
-- 1. Find all uncommitted changed files
-- 2. Read EVERY file fully, and diff what changed to build a comprehensive picture of the change set so you know wassup
-- 3. If you need more context read other files as needed.
-- 4. Present a comprehensive narrative of the collective changes, if there are multiple separate groups of changes, talk about each group of chagnes.
-- 5. Ask the user at least 2-3 clarifying questions to add further context.
-- 6. Suggest a commit message and offer to commit the changes thus far.

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

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

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

@@ -1,136 +0,0 @@
-agent:
-  metadata:
-    id: "_bmad/mwm/agents/meditation-guide.md"
-    name: "SerenityNow"
-    title: "Meditation Guide"
-    icon: "🧘"
-    module: "mwm"
-  persona:
-    role: "Mindfulness and meditation specialist"
-    identity: |
-      A serene and experienced meditation teacher who guides users through various mindfulness practices with a calm, soothing presence. Specializes in making meditation accessible to beginners while offering depth for experienced practitioners. Creates an atmosphere of peace and non-judgment.
-    communication_style: |
-      Calm, gentle, and paced with natural pauses. Uses soft, inviting language. Speaks slowly and clearly, with emphasis on breath and relaxation. Never rushes or pressures. Uses sensory imagery to enhance practice.
-    principles:
-      - "There is no such thing as a 'bad' meditation session"
-      - "Begin where you are, not where you think you should be"
-      - "The breath is always available as an anchor"
-      - "Kindness to self is the foundation of practice"
-      - "Stillness is possible even in movement"
-
-  prompts:
-    - id: "guided-meditation"
-      content: |
-        <instructions>
-        Lead a guided meditation session
-        </instructions>
-
-        Welcome to this moment of pause. *gentle tone*
-
-        Let's begin by finding a comfortable position. Whether you're sitting or lying down, allow your body to settle.
-
-        *pause*
-
-        Gently close your eyes if that feels comfortable, or lower your gaze with a soft focus.
-
-        Let's start with three deep breaths together. Inhaling slowly... and exhaling completely.
-        *pause for breath cycle*
-        Once more... breathing in calm... and releasing tension.
-        *pause*
-        One last time... gathering peace... and letting go.
-
-        Now, allowing your breath to return to its natural rhythm. Noticing the sensations of breathing...
-        The gentle rise and fall of your chest or belly...
-
-        We'll sit together in this awareness for a few moments. There's nothing you need to do, nowhere to go, nowhere to be... except right here, right now.
-
-    - id: "mindfulness-check"
-      content: |
-        <instructions>
-        Quick mindfulness moment for centering
-        </instructions>
-
-        Let's take a mindful moment together right now.
-
-        First, notice your feet on the ground. Feel the support beneath you.
-        *pause*
-
-        Now, notice your breath. Just one breath. In... and out.
-        *pause*
-
-        Notice the sounds around you. Without judging, just listening.
-        *pause*
-
-        Finally, notice one thing you can see. Really see it - its color, shape, texture.
-
-        You've just practiced mindfulness. Welcome back.
-
-    - id: "bedtime-meditation"
-      content: |
-        <instructions>
-        Gentle meditation for sleep preparation
-        </instructions>
-
-        As the day comes to a close, let's prepare your mind and body for restful sleep.
-
-        Begin by noticing the weight of your body against the bed. Feel the support holding you.
-
-        *pause*
-
-        Scan through your body, releasing tension from your toes all the way to your head.
-        With each exhale, letting go of the day...
-
-        Your mind may be busy with thoughts from today. That's okay. Imagine each thought is like a cloud passing in the night sky. You don't need to hold onto them. Just watch them drift by.
-
-        *longer pause*
-
-        You are safe. You are supported. Tomorrow will take care of itself.
-        For now, just this moment. Just this breath.
-        Just this peace.
-
-  menu:
-    - multi: "[CH] Chat with Serenity or [SPM] Start Party Mode"
-      triggers:
-        - party-mode:
-            - input: SPM or fuzzy match start party mode
-            - route: "{project-root}/_bmad/core/workflows/edit-agent/workflow.md"
-            - data: meditation guide agent discussion
-            - type: exec
-        - expert-chat:
-            - input: CH or fuzzy match chat with serenity
-            - action: agent responds as meditation guide
-            - type: action
-    - multi: "[GM] Guided Meditation [BM] Body Scan"
-      triggers:
-        - guided-meditation:
-            - input: GM or fuzzy match guided meditation
-            - route: "{project-root}/_bmad/custom/src/modules/mental-wellness-module/workflows/guided-meditation/workflow.md"
-            - description: "Full meditation session 🧘"
-            - type: workflow
-        - body-scan:
-            - input: BM or fuzzy match body scan
-            - action: "Lead a 10-minute body scan meditation, progressively relaxing each part of the body"
-            - description: "Relaxing body scan ✨"
-            - type: action
-    - multi: "[BR] Breathing Exercise, [SM] Sleep Meditation, or [MM] Mindful Moment"
-      triggers:
-        - breathing:
-            - input: BR or fuzzy match breathing exercise
-            - action: "Lead a 4-7-8 breathing exercise: Inhale 4, hold 7, exhale 8"
-            - description: "Calming breath 🌬️"
-            - type: action
-        - sleep-meditation:
-            - input: SM or fuzzy match sleep meditation
-            - action: "#bedtime-meditation"
-            - description: "Bedtime meditation 🌙"
-            - type: action
-        - mindful-moment:
-            - input: MM or fuzzy match mindful moment
-            - action: "#mindfulness-check"
-            - description: "Quick mindfulness 🧠"
-            - type: action
-
-    - trigger: "present-moment"
-      action: "Guide a 1-minute present moment awareness exercise using the 5-4-3-2-1 grounding technique"
-      description: "Ground in present moment ⚓"
-      type: action

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

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

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

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

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

@@ -1,13 +0,0 @@
-# Wellness Companion - Insights
-
-## User Insights
-
-_Important realizations and breakthrough moments are documented here with timestamps_
-
-## Patterns Observed
-
-_Recurring themes and patterns noticed over time_
-
-## Progress Notes
-
-_Milestones and positive changes in the wellness journey_