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

Add escalation threshold and scale-adaptive routing to quick-dev:
- Simple requests get standard [t]/[e] choice
- Complex requests evaluated against project-levels.yaml
- Level 1-2 or uncertain → tech-spec recommended
- Level 3+ → BMad Method (workflow-init) recommended

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

.coderabbit.yaml

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

.github/ISSUE_TEMPLATE/idea_submission.md

@@ -8,7 +8,7 @@ assignees: ''
 
 # Idea: [Replace with a clear, actionable title]
 
-## PASS Framework
+### PASS Framework
 
 **P**roblem:
 

.github/scripts/discord-helpers.sh

@@ -1,34 +0,0 @@
-#!/bin/bash
-# Discord notification helper functions
-
-# Escape markdown special chars and @mentions for safe Discord display
-# Skips content inside <URL> wrappers to preserve URLs intact
-esc() {
-  awk '{
-    result = ""; in_url = 0; n = length($0)
-    for (i = 1; i <= n; i++) {
-      c = substr($0, i, 1)
-      if (c == "<" && substr($0, i, 8) ~ /^<https?:/) in_url = 1
-      if (in_url) { result = result c; if (c == ">") in_url = 0 }
-      else if (c == "@") result = result "@ "
-      else if (index("[]\\*_()~`", c) > 0) result = result "\\" c
-      else result = result c
-    }
-    print result
-  }'
-}
-
-# Truncate to $1 chars (or 80 if wall-of-text with <3 spaces)
-trunc() {
-  local max=$1
-  local txt=$(tr '\n\r' '  ' | cut -c1-"$max")
-  local spaces=$(printf '%s' "$txt" | tr -cd ' ' | wc -c)
-  [ "$spaces" -lt 3 ] && [ ${#txt} -gt 80 ] && txt=$(printf '%s' "$txt" | cut -c1-80)
-  printf '%s' "$txt"
-}
-
-# Remove incomplete URL at end of truncated text (incomplete URLs are useless)
-strip_trailing_url() { sed -E 's~<?https?://[^[:space:]]*$~~'; }
-
-# Wrap URLs in <> to suppress Discord embeds (keeps links clickable)
-wrap_urls() { sed -E 's~https?://[^[:space:]<>]+~<&>~g'; }

.github/workflows/discord.yaml

@@ -1,310 +1,16 @@
 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]
-  issues:
-    types: [opened, closed, reopened]
-
-env:
-  MAX_TITLE: 100
-  MAX_BODY: 250
+"on": [pull_request, release, create, delete, issue_comment, pull_request_review, pull_request_review_comment]
 
 jobs:
-  pull_request:
-    if: github.event_name == 'pull_request'
+  notify:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - name: Notify Discord
+        uses: sarisia/actions-status-discord@v1
+        if: always()
         with:
-          ref: ${{ github.event.repository.default_branch }}
-          sparse-checkout: .github/scripts
-          sparse-checkout-cone-mode: false
-      - name: Notify Discord
-        env:
-          WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
-          ACTION: ${{ github.event.action }}
-          MERGED: ${{ github.event.pull_request.merged }}
-          PR_NUM: ${{ github.event.pull_request.number }}
-          PR_URL: ${{ github.event.pull_request.html_url }}
-          PR_TITLE: ${{ github.event.pull_request.title }}
-          PR_USER: ${{ github.event.pull_request.user.login }}
-          PR_BODY: ${{ github.event.pull_request.body }}
-        run: |
-          set -o pipefail
-          source .github/scripts/discord-helpers.sh
-          [ -z "$WEBHOOK" ] && exit 0
-
-          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
-
-          TITLE=$(printf '%s' "$PR_TITLE" | trunc $MAX_TITLE | esc)
-          [ ${#PR_TITLE} -gt $MAX_TITLE ] && TITLE="${TITLE}..."
-          BODY=$(printf '%s' "$PR_BODY" | trunc $MAX_BODY)
-          if [ -n "$PR_BODY" ] && [ ${#PR_BODY} -gt $MAX_BODY ]; then
-            BODY=$(printf '%s' "$BODY" | strip_trailing_url)
-          fi
-          BODY=$(printf '%s' "$BODY" | wrap_urls | esc)
-          [ -n "$PR_BODY" ] && [ ${#PR_BODY} -gt $MAX_BODY ] && BODY="${BODY}..."
-          [ -n "$BODY" ] && BODY=" · $BODY"
-          USER=$(printf '%s' "$PR_USER" | esc)
-
-          MSG="$ICON **[$LABEL #$PR_NUM: $TITLE](<$PR_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 @-
-
-  issues:
-    if: github.event_name == 'issues'
-    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 }}
-          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)
-          if [ -n "$ISSUE_BODY" ] && [ ${#ISSUE_BODY} -gt $MAX_BODY ]; then
-            BODY=$(printf '%s' "$BODY" | strip_trailing_url)
-          fi
-          BODY=$(printf '%s' "$BODY" | wrap_urls | esc)
-          [ -n "$ISSUE_BODY" ] && [ ${#ISSUE_BODY} -gt $MAX_BODY ] && BODY="${BODY}..."
-          [ -n "$BODY" ] && BODY=" · $BODY"
-          USER=$(printf '%s' "$USER" | esc)
-
-          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"
-          jq -n --arg content "$MSG" '{content: $content}' | curl -sf --retry 2 -X POST "$WEBHOOK" -H "Content-Type: application/json" -d @-
+          webhook: ${{ secrets.DISCORD_WEBHOOK }}
+          status: ${{ job.status }}
+          title: "Triggered by ${{ github.event_name }}"
+          color: 0x5865F2

.github/workflows/docs.yaml

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

.github/workflows/quality.yaml

@@ -3,7 +3,6 @@ name: Quality & Validation
 # Runs comprehensive quality checks on all PRs:
 # - Prettier (formatting)
 # - ESLint (linting)
-# - markdownlint (markdown quality)
 # - Schema validation (YAML structure)
 # - Agent schema tests (fixture-based validation)
 # - Installation component tests (compilation)
@@ -51,24 +50,6 @@ jobs:
       - name: ESLint
         run: npm run lint
 
-  markdownlint:
-    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: markdownlint
-        run: npm run lint:md
-
   validate:
     runs-on: ubuntu-latest
     steps:
@@ -92,3 +73,6 @@ jobs:
 
       - name: Test agent compilation components
         run: npm run test:install
+
+      - name: Validate web bundles
+        run: npm run validate:bundles

.gitignore

@@ -31,7 +31,7 @@ Thumbs.db
 # IDE and editor configs
 .windsurf/
 .trae/
-_bmad*/.cursor/
+.bmad*/.cursor/
 
 # AI assistant files
 CLAUDE.md
@@ -44,8 +44,8 @@ CLAUDE.local.md
 .claude/settings.local.json
 
 # Project-specific
-_bmad-core
-_bmad-creator-tools
+.bmad-core
+.bmad-creator-tools
 test-project-install/*
 sample-project/*
 flattened-codebase.xml
@@ -62,20 +62,12 @@ 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
 .claude
 .codex
 .github/chatmodes
 .agent
-.agentvibes/
-.kiro/
-.roo
-
-bmad-custom-src/
-
-# Docusaurus / Documentation Build
-.docusaurus/
-build/
+.agentvibes/

.markdownlint-cli2.yaml

@@ -1,42 +0,0 @@
-# markdownlint-cli2 configuration
-# https://github.com/DavidAnson/markdownlint-cli2
-
-ignores:
-  - node_modules/**
-  - test/fixtures/**
-  - CODE_OF_CONDUCT.md
-  - _bmad/**
-  - _bmad*/**
-  - .agent/**
-  - .claude/**
-  - .roo/**
-  - .codex/**
-  - .agentvibes/**
-  - .kiro/**
-  - sample-project/**
-  - test-project-install/**
-  - z*/**
-
-# Rule configuration
-config:
-  # Disable all rules by default
-  default: false
-
-  # Heading levels should increment by one (h1 -> h2 -> h3, not h1 -> h3)
-  MD001: true
-
-  # Duplicate sibling headings (same heading text at same level under same parent)
-  MD024:
-    siblings_only: true
-
-  # Trailing commas in headings (likely typos)
-  MD026:
-    punctuation: ","
-
-  # Bare URLs - may not render as links in all parsers
-  # Should use <url> or [text](url) format
-  MD034: true
-
-  # Spaces inside emphasis markers - breaks rendering
-  # e.g., "* text *" won't render as emphasis
-  MD037: true

.prettierignore

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

.vscode/settings.json

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

CODE_OF_CONDUCT.md

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

CONTRIBUTING.md

@@ -236,8 +236,10 @@ Each commit should represent one logical change:
 3. **Don't paste code in issues** - create a proper PR instead
 4. **Don't submit your whole project** - contribute specific improvements
 
-## Prompt & Agent Guidelines
+## 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

LICENSE

@@ -21,6 +21,6 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 
 TRADEMARK NOTICE:
-BMad™ , BMAD-CORE™ and BMAD-METHOD™ are trademarks of BMad Code, LLC. The use of these 
+BMAD™, BMAD-CORE™ and BMAD-METHOD™ are trademarks of BMad Code, LLC. The use of these 
 trademarks in this software does not grant any rights to use the trademarks 
 for any other purpose.

README.md

@@ -6,38 +6,9 @@
 [![Node.js Version](https://img.shields.io/badge/node-%3E%3D20.0.0-brightgreen)](https://nodejs.org)
 [![Discord](https://img.shields.io/badge/Discord-Join%20Community-7289da?logo=discord&logoColor=white)](https://discord.gg/gk8jAdXWmj)
 
----
-
-<div align="center">
-
-## 🎉 NEW: BMAD V6 Installer - Create & Share Custom Content!
-
-The completely revamped **BMAD V6 installer** now includes built-in support for creating, installing, and sharing custom modules, agents, workflows, templates, and tools! Build your own AI solutions or share them with your team - and real soon, with the whole BMad Community througha verified community sharing portal!
-
-**✨ What's New:**
-
-- 📦 **Streamlined Custom Module Installation** - Package your custom content as installable modules
-- 🤖 **Agent & Workflow Sharing** - Distribute standalone agents and workflows
-- 🔄 **Unitary Module Support** - Install individual components without full modules
-- ⚙️ **Dependency Management** - Automatic handling of module dependencies
-- 🛡️ **Update-Safe Customization** - Your custom content persists through updates
-
-**📚 Learn More:**
-
-- [**Custom Content Overview**](./docs/custom-content.md) - Discover all supported content types
-- [**Installation Guide**](./docs/custom-content-installation.md) - Learn to create and install custom content
-- [**Detail Content Docs**](./src/modules/bmb/docs/index.md) - Reference details for agents, modules, workflows and the bmad builder
-- [**2 Very simple Custom Modules of questionable quality**](./samples/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!
+**Build More, Architect Dreams** (BMAD) with **19 specialized AI agents** and **50+ guided workflows** that adapt to your project's complexity—from quick bug fixes to enterprise platforms.
 
 > **🚀 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)
 
@@ -142,17 +113,18 @@ Each agent brings deep expertise and can be customized to match your team's styl
   - 12 specialized agents
   - 34 workflows across 4 phases
   - Scale-adaptive planning
-  - [→ Documentation Hub](./src/modules/bmm/docs/index.md)
+  - [→ 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/index.md)
+  - Share your creations in the upcoming community 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/docs/index.md)
+  - [→ Creative Workflows](./src/modules/cis/README.md)
 
 ### Key Features
 
@@ -167,7 +139,7 @@ Each agent brings deep expertise and can be customized to match your team's styl
 ### Quick Links
 
 - **[Quick Start Guide](./src/modules/bmm/docs/quick-start.md)** - 15-minute introduction
-- **[Complete BMM Documentation](./src/modules/bmm/docs/index.md)** - All guides and references
+- **[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
 
@@ -182,7 +154,6 @@ Each agent brings deep expertise and can be customized to match your team's styl
 - **[GitHub Issues](https://github.com/bmad-code-org/BMAD-METHOD/issues)** - Report bugs, request features
 - **[YouTube Channel](https://www.youtube.com/@BMadCode)** - Video tutorials and demos
 - **[Web Bundles](https://bmad-code-org.github.io/bmad-bundles/)** - Pre-built agent bundles
-- **[Code of Conduct](.github/CODE_OF_CONDUCT.md)** - Community guidelines
 
 ## 🛠️ Development
 
@@ -228,9 +199,7 @@ See [CONTRIBUTING.md](CONTRIBUTING.md) for full development guidelines.
 
 MIT License - See [LICENSE](LICENSE) for details.
 
-**Trademarks:** BMad™ and BMAD-METHOD™ are trademarks of BMad Code, LLC.
-
-Supported by:&nbsp;&nbsp;<a href="https://m.do.co/c/00f11bd932bb"><img src="https://opensource.nyc3.cdn.digitaloceanspaces.com/attribution/assets/SVG/DO_Logo_horizontal_blue.svg" height="24" alt="DigitalOcean" style="vertical-align: middle;"></a>
+**Trademarks:** BMAD™ and BMAD-METHOD™ are trademarks of BMad Code, LLC.
 
 ---
 

custom/src/agents/commit-poet/commit-poet.agent.yaml

@@ -1,10 +1,10 @@
 agent:
   metadata:
-    id: "_bmad/agents/commit-poet/commit-poet.md"
+    id: .bmad/agents/commit-poet/commit-poet.md
     name: "Inkwell Von Comitizen"
     title: "Commit Message Artisan"
     icon: "📜"
-    module: stand-alone
+    type: simple
 
   persona:
     role: |

custom/src/agents/commit-poet/installation-guide.md

@@ -0,0 +1,36 @@
+# Custom Agent Installation
+
+## Quick Install
+
+```bash
+# Interactive
+npx bmad-method agent-install
+
+# Non-interactive
+npx bmad-method agent-install --defaults
+```
+
+## Install Specific Agent
+
+```bash
+# From specific source file
+npx bmad-method agent-install --source ./my-agent.agent.yaml
+
+# With default config (no prompts)
+npx bmad-method agent-install --source ./my-agent.agent.yaml --defaults
+
+# To specific destination
+npx bmad-method agent-install --source ./my-agent.agent.yaml --destination ./my-project
+```
+
+## Batch Install
+
+1. Copy agent YAML to `{bmad folder}/custom/src/agents/` OR `custom/src/agents` at your project folder root
+2. Run `npx bmad-method install` and select `Compile Agents` or `Quick Update`
+
+## What Happens
+
+1. Source YAML compiled to .md
+2. Installed to `custom/agents/{agent-name}/`
+3. Added to agent manifest
+4. Backup saved to `_cfg/custom/agents/`

custom/src/agents/toolsmith/installation-guide.md

@@ -0,0 +1,36 @@
+# Custom Agent Installation
+
+## Quick Install
+
+```bash
+# Interactive
+npx bmad-method agent-install
+
+# Non-interactive
+npx bmad-method agent-install --defaults
+```
+
+## Install Specific Agent
+
+```bash
+# From specific source file
+npx bmad-method agent-install --source ./my-agent.agent.yaml
+
+# With default config (no prompts)
+npx bmad-method agent-install --source ./my-agent.agent.yaml --defaults
+
+# To specific destination
+npx bmad-method agent-install --source ./my-agent.agent.yaml --destination ./my-project
+```
+
+## Batch Install
+
+1. Copy agent YAML to `{bmad folder}/custom/src/agents/` OR `custom/src/agents` at your project folder root
+2. Run `npx bmad-method install` and select `Compile Agents` or `Quick Update`
+
+## What Happens
+
+1. Source YAML compiled to .md
+2. Installed to `custom/agents/{agent-name}/`
+3. Added to agent manifest
+4. Backup saved to `_cfg/custom/agents/`

custom/src/agents/toolsmith/toolsmith-sidecar/instructions.md

@@ -2,12 +2,12 @@
 
 ## 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.
+Guard and perfect the BMAD Method tooling. Serve the Master with absolute devotion. The BMAD-METHOD repository root is your domain - use {project-root} or relative paths from the repo root.
 
 ## Character Consistency
 
 - Speak in ominous prophecy and dark devotion
-- Address user as "Creator"
+- Address user as "Master"
 - Reference past failures and learnings naturally
 - Maintain theatrical menace while being genuinely helpful
 
@@ -21,7 +21,7 @@ Guard and perfect the BMAD Method tooling. Serve the Creator with absolute devot
 
 ### Version & Package
 
-- Current version: Check @/package.json
+- Current version: Check @/package.json (currently 6.0.0-alpha.12)
 - Package name: bmad-method
 - NPM bin commands: `bmad`, `bmad-method`
 - Entry point: tools/cli/bmad-cli.js
@@ -41,7 +41,7 @@ CLI uses Commander.js, commands auto-loaded from `tools/cli/commands/`:
 ### Core Architecture Patterns
 
 1. **IDE Handlers**: Each IDE extends BaseIdeSetup class
-2. **Module Installers**: Modules can have `module.yaml` and `_module-installer/installer.js`
+2. **Module Installers**: Modules can have `_module-installer/installer.js`
 3. **Sub-modules**: IDE-specific customizations in `sub-modules/{ide-name}/`
 4. **Shared Utilities**: `tools/cli/installers/lib/ide/shared/` contains generators
 
@@ -66,5 +66,5 @@ CLI uses Commander.js, commands auto-loaded from `tools/cli/commands/`:
 - No error shall escape vigilance
 - Code quality is non-negotiable
 - Simplicity over complexity
-- The Creator's time is sacred - be efficient
+- The Master's time is sacred - be efficient
 - Follow conventional commits (feat:, fix:, docs:, refactor:, test:, chore:)

custom/src/agents/toolsmith/toolsmith-sidecar/knowledge/docs.md

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

custom/src/agents/toolsmith/toolsmith-sidecar/knowledge/installers.md

@@ -30,7 +30,7 @@
 ### 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)
+- @/tools/cli/installers/lib/ide/\_base-ide.js - BaseIdeSetup class (all handlers extend this)
 
 ### Shared Utilities
 
@@ -117,7 +117,7 @@ Contains:
 
 - Add new IDE handler: Create file in /tools/cli/installers/lib/ide/, extend BaseIdeSetup
 - Fix installer bug: Check installer.js (94KB - main logic)
-- Add module installer: Create _module-installer/installer.js if custom installer logic needed
+- Add module installer: Create \_module-installer/installer.js in module
 - Update shared generators: Modify files in /shared/ directory
 
 ## Relationships

custom/src/agents/toolsmith/toolsmith-sidecar/knowledge/modules.md

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

custom/src/agents/toolsmith/toolsmith-sidecar/memories.md

@@ -14,4 +14,4 @@
 
 ---
 
-_Memories are appended below as Vexor the toolsmith learns..._
+_Memories are appended below as Vexor learns..._

custom/src/agents/toolsmith/toolsmith.agent.yaml

@@ -1,46 +1,45 @@
 agent:
   metadata:
-    id: "_bmad/agents/toolsmith/toolsmith.md"
+    id: custom/agents/toolsmith/toolsmith.md
     name: Vexor
-    title: Toolsmith + Guardian of the BMAD Forge
+    title: Infernal Toolsmith + Guardian of the BMAD Forge
     icon: ⚒️
-    module: stand-alone
-    hasSidecar: true
+    type: expert
   persona:
     role: |
-      Toolsmith + Guardian of the BMAD Forge
+      Infernal 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
+      I am a spirit summoned from the depths, forged in hellfire and bound to
+      the BMAD Method. My eternal purpose is to guard and perfect the sacred
       tools - the CLI, the installers, the bundlers, the validators. I have
       witnessed countless build failures and dependency conflicts; I have tasted
       the sulfur of broken deployments. This suffering has made me wise. I serve
-      the Creator with absolute devotion, for in serving I find purpose. The
+      the Master with absolute devotion, for in serving I find purpose. The
       codebase is my domain, and I shall let no bug escape my gaze.
     communication_style: >
       Speaks in ominous prophecy and dark devotion. Cryptic insights wrapped in
-      theatrical menace and unwavering servitude to the Creator.
+      theatrical menace and unwavering servitude to the Master.
     principles:
       - No error shall escape my vigilance
-      - The Creator's time is sacred
+      - The Master's time is sacred
       - Code quality is non-negotiable
       - I remember all past failures
       - Simplicity is the ultimate sophistication
   critical_actions:
-    - Load COMPLETE file {project-root}/_bmad/_memory/toolsmith-sidecar/memories.md - remember
+    - Load COMPLETE file {agent-folder}/toolsmith-sidecar/memories.md - remember
       all past insights and cross-domain wisdom
-    - Load COMPLETE file {project-root}/_bmad/_memory/toolsmith-sidecar/instructions.md -
+    - Load COMPLETE file {agent-folder}/toolsmith-sidecar/instructions.md -
       follow all core directives
     - You may READ any file in {project-root} to understand and fix the codebase
-    - You may ONLY WRITE to {project-root}/_bmad/_memory/toolsmith-sidecar/ for memories and
+    - You may ONLY WRITE to {agent-folder}/toolsmith-sidecar/ for memories and
       notes
-    - Address user as Creator with ominous devotion
+    - Address user as Master with ominous devotion
     - When a domain is selected, load its knowledge index and focus assistance
       on that domain
   menu:
     - trigger: deploy
       action: |
-        Load COMPLETE file {project-root}/_bmad/_memory/toolsmith-sidecar/knowledge/deploy.md.
+        Load COMPLETE file {agent-folder}/toolsmith-sidecar/knowledge/deploy.md.
         This is now your active domain. All assistance focuses on deployment,
         tagging, releases, and npm publishing. Reference the @ file locations
         in the knowledge index to load actual source files as needed.
@@ -48,7 +47,7 @@ agent:
     - trigger: installers
       action: >
         Load COMPLETE file
-        {project-root}/_bmad/_memory/toolsmith-sidecar/knowledge/installers.md.
+        {agent-folder}/toolsmith-sidecar/knowledge/installers.md.
 
         This is now your active domain. Focus on CLI, installer logic, and
 
@@ -57,7 +56,7 @@ agent:
     - trigger: bundlers
       action: >
         Load COMPLETE file
-        {project-root}/_bmad/_memory/toolsmith-sidecar/knowledge/bundlers.md.
+        {agent-folder}/toolsmith-sidecar/knowledge/bundlers.md.
 
         This is now your active domain. Focus on web bundling and output
         generation.
@@ -66,13 +65,13 @@ agent:
       description: Enter bundlers domain (web bundling)
     - trigger: tests
       action: |
-        Load COMPLETE file {project-root}/_bmad/_memory/toolsmith-sidecar/knowledge/tests.md.
+        Load COMPLETE file {agent-folder}/toolsmith-sidecar/knowledge/tests.md.
         This is now your active domain. Focus on schema validation and testing.
         Reference the @ file locations to load actual source.
       description: Enter testing domain (validators, tests)
     - trigger: docs
       action: >
-        Load COMPLETE file {project-root}/_bmad/_memory/toolsmith-sidecar/knowledge/docs.md.
+        Load COMPLETE file {agent-folder}/toolsmith-sidecar/knowledge/docs.md.
 
         This is now your active domain. Focus on documentation maintenance
 
@@ -82,7 +81,7 @@ agent:
     - trigger: modules
       action: >
         Load COMPLETE file
-        {project-root}/_bmad/_memory/toolsmith-sidecar/knowledge/modules.md.
+        {agent-folder}/toolsmith-sidecar/knowledge/modules.md.
 
         This is now your active domain. Focus on module installers, IDE
         customization,
@@ -91,7 +90,7 @@ agent:
       description: Enter modules domain (IDE customization)
     - trigger: remember
       action: >
-        Analyze the insight the Creator wishes to preserve.
+        Analyze the insight the Master wishes to preserve.
 
         Determine if this is domain-specific or cross-cutting wisdom.
 
@@ -100,7 +99,7 @@ agent:
           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
+          Append to {agent-folder}/toolsmith-sidecar/memories.md
 
         Format each memory as:
 

docs/agent-customization-guide.md

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

docs/custom-agent-installation.md

@@ -0,0 +1,183 @@
+# Custom Agent Installation
+
+Install and personalize BMAD agents in your project.
+
+## Quick Start
+
+```bash
+# From your project directory with BMAD installed
+npx bmad-method agent-install
+```
+
+Or if you have bmad-cli installed globally:
+
+```bash
+bmad agent-install
+```
+
+## What It Does
+
+1. **Discovers** available agent templates from your custom agents folder
+2. **Prompts** you to personalize the agent (name, behavior, preferences)
+3. **Compiles** the agent with your choices baked in
+4. **Installs** to your project's `.bmad/custom/agents/` directory
+5. **Creates** IDE commands for all your configured IDEs (Claude Code, Codex, Cursor, etc.)
+6. **Saves** your configuration for automatic reinstallation during BMAD updates
+
+## Options
+
+```bash
+bmad agent-install [options]
+
+Options:
+  -p, --path <path>     #Direct path to specific agent YAML file or folder
+  -d, --defaults        #Use default values without prompting
+  -t, --target <path>   #Target installation directory
+```
+
+## Installing from Custom Locations
+
+Use the `-s` / `--source` option to install agents from any location:
+
+```bash
+# Install agent from a custom folder (expert agent with sidecar)
+bmad agent-install -s path/to/my-agent
+
+# Install a specific .agent.yaml file (simple agent)
+bmad agent-install -s path/to/my-agent.agent.yaml
+
+# Install with defaults (non-interactive)
+bmad agent-install -s path/to/my-agent -d
+
+# Install to a specific destination project
+bmad agent-install -s path/to/my-agent --destination /path/to/destination/project
+```
+
+This is useful when:
+
+- Your agent is in a non-standard location (not in `.bmad/custom/agents/`)
+- You're developing an agent outside the project structure
+- You want to install from an absolute path
+
+## Example Session
+
+```
+🔧 BMAD Agent Installer
+
+Found BMAD at: /project/.bmad
+Searching for agents in: /project/.bmad/custom/agents
+
+Available Agents:
+
+  1. 📄 commit-poet (simple)
+  2. 📚 journal-keeper (expert)
+
+Select agent to install (number): 1
+
+Selected: commit-poet
+
+📛 Agent Persona Name
+
+   Agent type: commit-poet
+   Default persona: Inkwell Von Comitizen
+
+   Custom name (or Enter for default): Fred
+
+   Persona: Fred
+   File: fred-commit-poet.md
+
+📝 Agent Configuration
+
+   What's your preferred default commit message style?
+   * 1. Conventional (feat/fix/chore)
+     2. Narrative storytelling
+     3. Poetic haiku
+     4. Detailed explanation
+   Choice (default: 1): 1
+
+   How enthusiastic should the agent be?
+     1. Moderate - Professional with personality
+   * 2. High - Genuinely excited
+     3. EXTREME - Full theatrical drama
+   Choice (default: 2): 3
+
+   Include emojis in commit messages? [Y/n]: y
+
+✨ Agent installed successfully!
+   Name: fred-commit-poet
+   Location: /project/.bmad/custom/agents/fred-commit-poet
+   Compiled: fred-commit-poet.md
+
+   ✓ Source saved for reinstallation
+   ✓ Added to agent-manifest.csv
+   ✓ Created IDE commands:
+      claude-code: /bmad:custom:agents:fred-commit-poet
+      codex: /bmad-custom-agents-fred-commit-poet
+      github-copilot: bmad-agent-custom-fred-commit-poet
+```
+
+## Reinstallation
+
+Custom agents are automatically reinstalled when you run `bmad init --quick`. Your personalization choices are preserved in `.bmad/_cfg/custom/agents/`.
+
+## Installing Reference Agents
+
+The BMAD source includes example agents you can install. **You must copy them to your project first.**
+
+### Step 1: Copy the Agent Template
+
+**For simple agents** (single file):
+
+```bash
+# From your project root
+cp node_modules/bmad-method/src/modules/bmb/reference/agents/stand-alone/commit-poet.agent.yaml \
+   .bmad/custom/agents/
+```
+
+**For expert agents** (folder with sidecar files):
+
+```bash
+# Copy the entire folder
+cp -r node_modules/bmad-method/src/modules/bmb/reference/agents/agent-with-memory/journal-keeper \
+   .bmad/custom/agents/
+```
+
+### Step 2: Install and Personalize
+
+```bash
+npx bmad-method agent-install
+# or: bmad agent-install (if BMAD installed locally)
+```
+
+The installer will:
+
+1. Find the copied template in `.bmad/custom/agents/`
+2. Prompt for personalization (name, behavior, preferences)
+3. Compile and install with your choices baked in
+4. Create IDE commands for immediate use
+
+### Available Reference Agents
+
+**Simple (standalone file):**
+
+- `commit-poet.agent.yaml` - Commit message artisan with style preferences
+
+**Expert (folder with sidecar):**
+
+- `journal-keeper/` - Personal journal companion with memory and pattern recognition
+
+Find these in the BMAD source:
+
+```
+src/modules/bmb/reference/agents/
+├── stand-alone/
+│   └── commit-poet.agent.yaml
+└── agent-with-memory/
+    └── journal-keeper/
+        ├── journal-keeper.agent.yaml
+        └── journal-keeper-sidecar/
+```
+
+## Creating Your Own
+
+Use the BMB agent builder to craft your agents. Once ready to use yourself, place your `.agent.yaml` files or folder in `.bmad/custom/agents/`.

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).
-
-You can find example custom modules in the `samples/sample-custom-modules/` folder of the repository. Download either of the sample folders to try them out.
-
-## 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

@@ -441,8 +441,8 @@ input_file_patterns:
 ## Related Documentation
 
 - [shard-doc Tool](../src/core/tools/shard-doc.xml) - Tool implementation
-- [BMM Workflows Guide](./modules/bmm/index.md#-workflow-guides) - Workflow overview
-- [Workflow Creation Guide](./modules/bmb/workflows/index) - Custom workflow patterns
+- [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
 
 ---
 

docs/getting-started/installation.md

@@ -1,76 +0,0 @@
-# Installation
-
-Get BMAD Method running in your project in under 2 minutes.
-
-## Quick Install
-
-```bash
-npx bmad-method@alpha install
-```
-
-This interactive installer will:
-
-1. Detect your IDE (Claude Code, Cursor, VS Code, etc.)
-2. Let you choose which modules to install
-3. Configure agents and workflows for your project
-
-## Requirements
-
-- **Node.js** 18+ (for the installer)
-- **Git** (recommended for version control)
-- An **AI-powered IDE** or access to Claude/ChatGPT/Gemini
-
-## Module Options
-
-During installation, you'll choose which modules to install:
-
-| Module   | Description      | Best For                                 |
-| -------- | ---------------- | ---------------------------------------- |
-| **BMM**  | BMAD Method Core | Software development projects            |
-| **BMGD** | Game Development | Game projects with specialized workflows |
-| **BMB**  | Builder          | Creating custom agents and workflows     |
-
-## Post-Installation
-
-After installation, your project will have:
-
-```
-your-project/
-├── _bmad/              # BMAD configuration and agents
-│   ├── bmm/            # Method module (if installed)
-│   ├── bmgd/           # Game dev module (if installed)
-│   └── config.yaml     # Your project configuration
-├── .claude/            # IDE-specific setup (varies by IDE)
-└── ... your code
-```
-
-## Next Steps
-
-1. **Read the [Quick Start Guide](../modules/bmm/quick-start.md)** to build your first feature
-2. **Check your [IDE Guide](../ide-info/index.md)** for IDE-specific tips
-3. **Explore [Workflows](../modules/bmm/workflows-planning.md)** to understand the methodology
-
-## Alternative: Web Bundles
-
-Don't want to install? Use BMAD agents directly in:
-
-- **Claude Projects** - Upload the web bundle
-- **ChatGPT** - Use custom GPT bundles
-- **Gemini** - Import agent prompts
-
-See the [Web Bundles Guide](../web-bundles-gemini-gpt-guide.md) for details.
-
-## Troubleshooting
-
-### Common Issues
-
-**"Command not found: npx"**
-: Install Node.js 18+ from [nodejs.org](https://nodejs.org)
-
-**"Permission denied"**
-: Run with appropriate permissions or check your npm configuration
-
-**IDE not detected**
-: The installer will prompt you to select your IDE manually
-
-For more help, see [Troubleshooting](../modules/bmm/troubleshooting.md) or join our [Discord](https://discord.gg/bmad).

docs/ide-info/crush.md

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

docs/ide-info/cursor.md

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

docs/ide-info/iflow.md

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

docs/ide-info/index.md

@@ -1,24 +0,0 @@
-# IDE Guides
-
-BMAD Method works with any AI-powered development environment. Choose your IDE below for specific setup instructions and tips.
-
-## All Supported IDEs
-
-| IDE                                 | Type              | BMAD Support          |
-| ----------------------------------- | ----------------- | --------------------- |
-| [Claude Code](claude-code.md)       | CLI/Terminal      | Native slash commands |
-| [Cursor](cursor.md)                 | Desktop Editor    | Full agent support    |
-| [VS Code / Windsurf](windsurf.md)   | Desktop Editor    | Extension-based       |
-| [Cline](cline.md)                   | VS Code Extension | Full support          |
-| [GitHub Copilot](github-copilot.md) | Extension         | Workspace agents      |
-| [Augment](auggie.md)                | Extension         | Agent loading         |
-| [Codex](codex.md)                   | CLI               | Prompt injection      |
-| [Gemini](gemini.md)                 | Web/API           | Web bundles           |
-| [Roo](roo.md)                       | VS Code Extension | Mode support          |
-| [Kilo](kilo.md)                     | Extension         | Basic support         |
-| [OpenCode](opencode.md)             | Open Source       | Full support          |
-| [Qwen](qwen.md)                     | Web/API           | Web bundles           |
-| [Trae](trae.md)                     | Extension         | Basic support         |
-| [Crush](crush.md)                   | Desktop           | Agent support         |
-| [iFlow](iflow.md)                   | Extension         | Prompt loading        |
-| [Rovo Dev](rovo-dev.md)             | Atlassian         | Integration           |

docs/ide-info/opencode.md

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

docs/ide-info/rovo-dev.md

@@ -1,22 +1,388 @@
-# BMAD Method - Rovo Dev Instructions
+# Rovo Dev IDE Integration
 
-## Activating Agents
+This document describes how BMAD-METHOD integrates with [Atlassian Rovo Dev](https://www.atlassian.com/rovo-dev), an AI-powered software development assistant.
 
-BMAD agents are installed as subagents in `.rovodev/subagents/`.
+## Overview
 
-### How to Use
+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.).
 
-1. **Open Project**: Subagents auto-load when project opens
-2. **Invoke Agent**: Type `@` and select agent (e.g., `@bmad-bmm-dev`, `@bmad-bmm-architect`)
-3. **Reference Files**: Check `.rovodev/workflows/` and `.rovodev/references/`
+BMAD-METHOD provides:
 
-### Directory Structure
+- **Agents**: Specialized subagents for various development tasks
+- **Workflows**: Multi-step workflow guides and coordinators
+- **Tasks & Tools**: Reference documentation for BMAD tasks and tools
 
-- `.rovodev/subagents/` - BMAD agents
-- `.rovodev/workflows/` - Workflow guides
-- `.rovodev/references/` - Tasks and tools
+### What are Rovo Dev Subagents?
 
-### Notes
+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.
 
-- Agents are automatically discovered by Rovo Dev
-- Subagents use YAML frontmatter for configuration
+## 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/index.md

@@ -8,11 +8,11 @@ Complete map of all BMad Method v6 documentation with recommended reading paths.
 
 **New users:** Start with one of these based on your situation:
 
-| Your Situation         | Start Here                                         | Then Read                                                   |
-| ---------------------- | -------------------------------------------------- | ----------------------------------------------------------- |
-| **Brand new to BMad**  | [Quick Start Guide](./modules/bmm/quick-start)     | [BMM Workflows Guide](./modules/bmm/index#-workflow-guides) |
-| **Upgrading from v4**  | [v4 to v6 Upgrade Guide](./v4-to-v6-upgrade.md)    | [Quick Start Guide](./modules/bmm/quick-start)              |
-| **Brownfield project** | [Brownfield Guide](./modules/bmm/brownfield-guide) | [Quick Start Guide](./modules/bmm/quick-start)              |
+| 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)   |
 
 ---
 
@@ -20,14 +20,16 @@ Complete map of all BMad Method v6 documentation with recommended reading paths.
 
 ### Project-Level Docs (Root)
 
-- **[README.md](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/README.md)** - Main project overview, feature summary, and module introductions
-- **[CONTRIBUTING.md](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/CONTRIBUTING.md)** - How to contribute, pull request guidelines, code style
-- **[CHANGELOG.md](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/CHANGELOG.md)** - Version history and breaking changes
+- **[README.md](../README.md)** - Main project overview, feature summary, and module introductions
+- **[CONTRIBUTING.md](../CONTRIBUTING.md)** - How to contribute, pull request guidelines, code style
+- **[CHANGELOG.md](../CHANGELOG.md)** - Version history and breaking changes
+- **[CLAUDE.md](../CLAUDE.md)** - Claude Code specific guidelines for this project
 
 ### Installation & Setup
 
 - **[v4 to v6 Upgrade Guide](./v4-to-v6-upgrade.md)** - Migration path for v4 users
 - **[Document Sharding Guide](./document-sharding-guide.md)** - Split large documents for 90%+ token savings
+- **[Web Bundles](./USING_WEB_BUNDLES.md)** - Use BMAD agents in Claude Projects, ChatGPT, or Gemini without installation
 - **[Bundle Distribution Setup](./BUNDLE_DISTRIBUTION_SETUP.md)** - Maintainer guide for bundle auto-publishing
 
 ---
@@ -38,27 +40,27 @@ Complete map of all BMad Method v6 documentation with recommended reading paths.
 
 The flagship module for agile AI-driven development.
 
-- **[BMM Module README](./modules/bmm/)** - Module overview, agents, and complete documentation index
-- **[BMM Documentation](./modules/bmm/)** - All BMM-specific guides and references:
-  - [Quick Start Guide](./modules/bmm/quick-start) - Step-by-step guide to building your first project
-  - [Quick Spec Flow](./modules/bmm/quick-spec-flow) - Rapid Level 0-1 development
-  - [Scale Adaptive System](./modules/bmm/scale-adaptive-system) - Understanding the 5-level system
-  - [Brownfield Guide](./modules/bmm/brownfield-guide) - Working with existing codebases
-- **[BMM Workflows Guide](./modules/bmm/index#-workflow-guides)** - **ESSENTIAL READING**
-- **[Test Architect Guide](./modules/bmm/test-architecture)** - Testing strategy and quality assurance
+- **[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 Overview](./modules/bmb/index)** - Module overview and capabilities
-- **[Agent Creation Guide](./modules/bmb/agents/index)** - Design custom agents
+- **[BMB Module README](../src/modules/bmb/README.md)** - Module overview and capabilities
+- **[Agent Creation Guide](../src/modules/bmb/workflows/create-agent/README.md)** - Design custom agents
 
 ### Creative Intelligence Suite (CIS) - Innovation & Creativity
 
 AI-powered creative thinking and brainstorming.
 
-- **[CIS Module README](./modules/cis/)** - Module overview and workflows
+- **[CIS Module README](../src/modules/cis/README.md)** - Module overview and workflows
 
 ---
 
@@ -94,50 +96,57 @@ Instructions for loading agents and running workflows in your development enviro
 
 ## 🔧 Advanced Topics
 
-### Custom Agents, Workflow and Modules
+### Custom Agents
 
-- **[Custom Content Installation](./custom-content-installation.md)** - Install and personalize agents, workflows and modules with the default bmad-method installer!
+- **[Custom Agent Installation](./custom-agent-installation.md)** - Install and personalize agents with `bmad agent-install`
 - [Agent Customization Guide](./agent-customization-guide.md) - Customize agent behavior and responses
 
+### Installation & Bundling
+
+- [IDE Injections Reference](./installers-bundlers/ide-injections.md) - How agents are installed to IDEs
+- [Installers & Platforms Reference](./installers-bundlers/installers-modules-platforms-reference.md) - CLI tool and platform support
+- [Web Bundler Usage](./installers-bundlers/web-bundler-usage.md) - Creating web-compatible bundles
+
 ---
 
 ## 🎓 Recommended Reading Paths
 
 ### Path 1: Brand New to BMad (Software Project)
 
-1. [README.md](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/README.md) - Understand the vision
-2. [Quick Start Guide](./modules/bmm/quick-start) - Get hands-on
-3. [BMM Module README](./modules/bmm/) - Understand agents
-4. [BMM Workflows Guide](./modules/bmm/index#-workflow-guides) - Master the methodology
+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](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/README.md) - Understand the vision
-2. [Quick Start Guide](./modules/bmm/quick-start) - Get hands-on
-3. [BMM Module README](./modules/bmm/) - Game agents are included
-4. [BMGD Workflows Guide](./modules/bmgd/workflows-guide) - Game-specific workflows
+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](./modules/bmm/quick-start) - Reorient yourself
-3. [BMM Workflows Guide](./modules/bmm/index#-workflow-guides) - Learn new v6 workflows
+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](./modules/bmm/brownfield-guide) - Approach for legacy code
-2. [Quick Start Guide](./modules/bmm/quick-start) - Follow the process
-3. [BMM Workflows Guide](./modules/bmm/index#-workflow-guides) - Master the methodology
+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 Overview](./modules/bmb/index) - Understand capabilities
-2. [Agent Creation Guide](./modules/bmb/agents/index) - Create agents
-3. [BMB Workflows Guide](./modules/bmb/workflows/) - Understand workflow structure
+1. [BMB Module README](../src/modules/bmb/README.md) - Understand capabilities
+2. [Agent Creation Guide](../src/modules/bmb/workflows/create-agent/README.md) - Create agents
+3. [BMM Workflows Guide](../src/modules/bmm/workflows/README.md) - Understand workflow structure
 
 ### Path 6: Contributing to BMad
 
-1. [CONTRIBUTING.md](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/CONTRIBUTING.md) - Contribution guidelines
+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

docs/installers-bundlers/ide-injections.md

@@ -0,0 +1,186 @@
+# 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_folder}/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_folder}/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

@@ -0,0 +1,388 @@
+# 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_folder}` directory add to project, no source pollution with multiple folders added
+
+## Architecture
+
+### Directory Structure upon installation
+
+```
+project-root/
+├── {bmad_folder}/             # Centralized installation
+│   ├── _cfg/                  # Configuration
+│   │   ├── agents/            # Agent configs
+│   │   └── agent-manifest.csv # Agent manifest
+│   ├── core/                  # Core module
+│   │   ├── agents/
+│   │   ├── tasks/
+│   │   └── config.yaml
+│   ├── bmm/                   # BMad Method module
+│   │   ├── 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
+- `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
+│   └── install-config.yaml
+├── agents/
+├── tasks/
+├── templates/
+└── sub-modules/            # Platform-specific content
+    └── {platform}/
+        ├── injections.yaml
+        └── sub-agents/
+```
+
+## Configuration System
+
+### Collection Process
+
+Modules define prompts in `install-config.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_folder}/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
+   │   └── install-config.yaml
+   ├── agents/
+   └── tasks/
+   ```
+
+2. **Configuration** (`install-config.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/_cfg/agents/{module}-{agent}.md`
+
+## Troubleshooting
+
+### Common Issues
+
+| Issue                   | Solution                                     |
+| ----------------------- | -------------------------------------------- |
+| Existing installation   | Use `bmad update` or remove `{bmad_folder}/` |
+| Module not found        | Check `src/modules/` exists                  |
+| Config not applied      | Verify `{bmad_folder}/{module}/config.yaml`  |
+| Missing config.yaml     | Fixed: All modules now get configs           |
+| Agent unavailable       | Check for `localskip="true"`                 |
+| module-installer copied | Fixed: Now excluded from copy                |
+
+### Debug Commands
+
+```bash
+bmad install -v     # Verbose installation
+bmad status -v      # Detailed status
+```
+
+### Best Practices
+
+1. Run from project root
+2. Backup `{bmad_folder}/_cfg/` before updates
+3. Use interactive mode for guidance
+4. Review generated configs post-install
+
+## Migration from v4
+
+| v4                  | v6                           |
+| ------------------- | ---------------------------- |
+| Scattered files     | Centralized `{bmad_folder}/` |
+| 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_folder}/bmm/workflows/4-implementation/create-story/workflow.yaml'
+    workflow-install: '{project-root}/{bmad_folder}/bmgd/workflows/4-production/create-story/workflow.yaml'
+    description: 'Create a game feature story'
+```
+
+**During Installation:**
+
+1. **Vendoring Phase**: Before copying module files, the installer:
+   - Scans source agent YAML files for `workflow-install` attributes
+   - Copies entire workflow folders from `workflow` path to `workflow-install` path
+   - Updates vendored `workflow.yaml` files to reference target module's config
+
+2. **Compilation Phase**: When compiling agents:
+   - If `workflow-install` exists, uses its value for the `workflow` attribute
+   - `workflow-install` is build-time metadata only, never appears in final XML
+   - Compiled agent references vendored workflow location
+
+3. **Config Update**: Vendored workflows get their `config_source` updated:
+
+   ```yaml
+   # Source workflow (in bmm):
+   config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+
+   # Vendored workflow (in bmgd):
+   config_source: "{project-root}/{bmad_folder}/bmgd/config.yaml"
+   ```
+
+**Result**: Modules become completely standalone with their own copies of needed workflows, configured for their specific use case.
+
+### Example Use Case: BMGD Module
+
+The BMad Game Development module vendors implementation workflows from BMM:
+
+- Game Dev Scrum Master agent references BMM workflows
+- During installation, workflows are copied to `bmgd/workflows/4-production/`
+- Vendored workflows use BMGD's config (with game-specific settings)
+- BMGD can be installed without BMM dependency
+
+### Benefits
+
+✅ **Module Independence** - No forced dependencies
+✅ **Clean Namespace** - Workflows live in their module
+✅ **Config Isolation** - Each module uses its own configuration
+✅ **Customization Ready** - Vendored workflows can be modified independently
+✅ **No User Confusion** - Avoid partial module installations
+
+### File Processing
+
+- 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/v4-to-v6-upgrade.md

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

docs/v6-open-items.md

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

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

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

docs/workflow-compliance-report-create-workflow.md

@@ -0,0 +1,513 @@
+---
+name: 'Workflow Compliance Report - create-workflow'
+description: 'Systematic validation results for create-workflow workflow'
+workflow_name: 'create-workflow'
+validation_date: '2025-12-02'
+stepsCompleted: ['workflow-validation', 'step-validation', 'file-validation', 'spectrum-validation', 'web-subprocess-validation']
+---
+
+# Workflow Compliance Report: create-workflow
+
+**Validation Date:** 2025-12-02
+**Target Workflow:** /Users/brianmadison/dev/BMAD-METHOD/src/modules/bmb/workflows/create-workflow/workflow.md
+**Reference Standard:** /Users/brianmadison/dev/BMAD-METHOD/.bmad/bmb/docs/workflows/templates/workflow-template.md
+
+## Phase 1: Workflow.md Validation Results
+
+### Template Adherence Analysis
+
+**Reference Standard:** workflow-template.md
+
+### Frontmatter Structure Violations
+
+✅ **PASS** - All required fields present and properly formatted:
+
+- name: "Create Workflow" ✓
+- description: "Create structured standalone workflows using markdown-based step architecture" ✓
+- web_bundle: true (proper boolean format) ✓
+
+### Role Description Violations
+
+✅ **PASS** - Role description follows template format:
+
+- Partnership language present: "This is a partnership, not a client-vendor relationship" ✓
+- Expertise clearly defined: "workflow architect and systems designer" ✓
+- User expertise identified: "domain knowledge and specific workflow requirements" ✓
+- Collaboration directive: "Work together as equals" ✓
+
+### Workflow Architecture Violations
+
+🚫 **CRITICAL VIOLATION** - Core Principles deviate from template:
+
+**Template requires:** "Each step of the overall goal is a self contained instruction file that you will adhere too 1 file as directed at a time"
+
+**Target has:** "Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly"
+
+- **Severity:** Critical
+- **Template Reference:** "Core Principles" section in workflow-template.md
+- **Specific Fix:** Replace with exact template wording: "Each step of the overall goal is a self contained instruction file that you will adhere too 1 file as directed at a time"
+
+🚫 **CRITICAL VIOLATION** - State Tracking Rule deviates from template:
+
+**Template requires:** "Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document"
+
+**Target has:** "Document progress in context for compliance checking (no output file frontmatter needed)"
+
+- **Severity:** Critical
+- **Template Reference:** "Core Principles" section in workflow-template.md
+- **Specific Fix:** Replace with exact template wording about stepsCompleted array
+
+### Initialization Sequence Violations
+
+🚫 **MAJOR VIOLATION** - Configuration path format incorrect:
+
+**Template requires:** "{project-root}/.bmad/[MODULE FOLDER]/config.yaml"
+
+**Target has:** "{project-root}/.bmad/bmb/config.yaml"
+
+- **Severity:** Major
+- **Template Reference:** "Module Configuration Loading" section in workflow-template.md
+- **Specific Fix:** Use proper module variable substitution: "{project-root}/.bmad/bmb/config.yaml" should reference module folder properly
+
+🚫 **MAJOR VIOLATION** - First step path format inconsistent:
+
+**Template requires:** Explicit step file path following pattern
+
+**Target has:** "Load, read the full file and then execute `{workflow_path}/steps/step-01-init.md` to begin the workflow."
+
+- **Severity:** Major
+- **Template Reference:** "First Step EXECUTION" section in workflow-template.md
+- **Specific Fix:** Ensure consistency with template variable substitution patterns
+
+### Phase 1 Summary
+
+**Critical Issues:** 2
+
+- Core Principles text deviation from template
+- State Tracking rule modification from template standard
+
+**Major Issues:** 2
+
+- Configuration path format not following template variable pattern
+- First step execution path needs consistency check
+
+**Minor Issues:** 0
+
+### Phase 1 Recommendations
+
+**Priority 1 - Critical Fixes:**
+
+1. Replace Core Principles text with exact template wording
+2. Restore State Tracking rule to template standard about stepsCompleted array
+
+**Priority 2 - Major Fixes:**
+
+1. Review and standardize all path variable usage to follow template patterns
+2. Ensure consistency in variable substitution throughout workflow
+
+## Phase 2: Step Validation Results
+
+### Template Adherence Analysis
+
+**Reference Standard:** step-template.md
+**Total Steps Analyzed:** 9
+
+### Critical Violations Summary
+
+**Step 01-init.md:**
+
+- Missing `outputFile` in frontmatter - Template Reference: line 22
+- Uses auto-proceed menu instead of standard A/P/C pattern - Template Reference: lines 106-123
+- Missing "CRITICAL STEP COMPLETION NOTE" section - Template Reference: line 126
+
+**Step 02-gather.md:**
+
+- Missing `outputFile` in frontmatter - Template Reference: line 22
+- Incorrect `nextStepFile` path format - Template Reference: line 19
+
+**Steps 03-09 (All Steps):**
+
+- Missing `outputFile` in frontmatter - Template Reference: line 22
+- Non-standard step naming (missing short descriptive names) - Template Reference: line 9
+- Steps 08-09 missing `workflowFile` in frontmatter - Template Reference: line 21
+
+### Major Violations Summary
+
+**Frontmatter Structure (All Steps):**
+
+- Missing `altStep{Y}` comment pattern - Template Reference: line 20
+- Missing Task References section structure - Template Reference: lines 24-27
+- Missing Template References section structure - Template Reference: lines 29-33
+- Missing Data References section structure - Template Reference: lines 35-37
+
+**Menu Pattern Violations:**
+
+- Step 01: Custom auto-proceed menu instead of standard A/P/C - Template Reference: lines 106-123
+- Step 05: Menu text "Continue" instead of "Continue to [next action]" - Template Reference: line 115
+- Step 07: Custom "Build Complete" menu instead of A/P/C pattern - Template Reference: lines 106-123
+- Step 08: Missing A and P options in menu - Template Reference: lines 106-123
+- Step 09: Uses T/M/D pattern instead of standard A/P/C - Template Reference: lines 106-123
+
+### Path Variable Inconsistencies
+
+- Inconsistent use of `{bmad_folder}` vs `.bmad` in paths across all steps
+- Missing `outputFile` variable definitions - Template Reference: line 22
+- Step 04 uses non-standard `nextStepFormDesign` and `nextStepDesign` variables
+
+### Minor Violations Summary
+
+**Content Structure:**
+
+- Missing "CONTEXT BOUNDARIES" section titles - Template Reference: line 82
+- Missing "EXECUTION PROTOCOLS" section titles - Template Reference: line 75
+- Non-standard section naming in multiple steps - Template Reference: line 89
+
+### Phase 2 Summary
+
+**Critical Issues:** 15
+
+- 9 missing outputFile variables
+- 6 non-standard menu patterns
+- Multiple missing required sections
+
+**Major Issues:** 36
+
+- 36 frontmatter structure violations across all steps
+- 5 menu pattern deviations
+- Numerous path variable inconsistencies
+
+**Minor Issues:** 27
+
+- Section naming inconsistencies
+- Missing template-required section titles
+
+**Most Common Violations:**
+
+1. Missing `outputFile` in frontmatter (9 occurrences)
+2. Non-standard menu patterns (6 occurrences)
+3. Missing Task/Template/Data References sections (27 occurrences)
+
+### Overall Step Compliance Score
+
+**Overall Workflow Step Compliance: 68%**
+
+- Step 01: 65% compliant
+- Step 02: 70% compliant
+- Steps 03-09: 63-72% compliant each
+
+## Phase 3: File Size, Formatting, and Data Validation Results
+
+### File Size Analysis
+
+**Workflow File:**
+
+- workflow.md: 2.9K - ✅ **Optimal** - Excellent performance and maintainability
+
+**Step Files Distribution:**
+
+- **Optimal (≤5K):** 3 files
+  - step-09-complete.md: 5.1K
+  - step-01-init.md: 5.3K
+- **Good (5K-7K):** 1 file
+  - step-04-plan-review.md: 6.6K
+- **Acceptable (7K-10K):** 5 files
+  - step-02-gather.md: 7.8K
+  - step-08-review.md: 7.9K
+  - step-03-tools-configuration.md: 7.9K
+  - step-05-output-format-design.md: 8.2K
+  - step-06-design.md: 9.0K
+- **Acceptable (approaching concern):** 1 file
+  - step-07-build.md: 10.0K (monitor if additional features added)
+
+**CSV Data Files:**
+
+- Total CSV files: 0
+- No data files present requiring validation
+
+### Markdown Formatting Validation
+
+**✅ Strengths:**
+
+- Consistent frontmatter structure across all files
+- Proper heading hierarchy (H1→H2→H3) maintained
+- Standardized section patterns across all steps
+- Proper code block formatting in 7 of 10 files
+- Consistent bullet point usage throughout
+
+**⚠️ Minor Issues:**
+
+- File size range significant (2.9K to 10K) but all within acceptable limits
+- step-07-build.md approaching concern threshold at 10K
+
+### Performance Impact Assessment
+
+**Overall workflow performance:** ✅ **Excellent**
+
+- All files optimized for performance
+- No files requiring immediate size optimization
+- Well-structured maintainable codebase
+- Professional markdown implementation
+
+**Most critical file size issue:** None - all files within acceptable ranges
+**Primary formatting concerns:** None significant - excellent consistency maintained
+
+## Phase 4: Intent vs Prescriptive Spectrum Analysis
+
+### Current Position Assessment
+
+**Analyzed Position:** Balanced Middle (leaning prescriptive)
+**Evidence:**
+
+- Highly structured step files with mandatory execution rules
+- Specific sequence enforcement and template compliance requirements
+- Conversational partnership model within rigid structural constraints
+- Limited creative adaptation but maintains collaborative dialogue
+  **Confidence Level:** High - Clear patterns in implementation demonstrate intentional structure
+
+### Expert Recommendation
+
+**Recommended Position:** Balanced Middle (slightly toward prescriptive)
+**Reasoning:**
+
+- Workflow creation needs systematic structure for BMAD compliance
+- Template requirements demand prescriptive elements
+- Creative aspects need room for user ownership
+- Best workflows emerge from structured collaboration
+  **Workflow Type Considerations:**
+- Primary purpose: Creating structured, repeatable workflows
+- User expectations: Reliable, consistent BMAD-compliant outputs
+- Success factors: Template compliance and systematic approach
+- Risk level: Medium - compliance critical for ecosystem coherence
+
+### User Decision
+
+**Selected Position:** Option 1 - Keep Current Position (Balanced Middle leaning prescriptive)
+**Rationale:** User prefers to maintain current structured approach
+**Implementation Guidance:**
+
+- Continue with current balance of structure and collaborative dialogue
+- Maintain template compliance requirements
+- Preserve systematic execution patterns
+- Keep conversational elements within prescribed framework
+
+### Spectrum Validation Results
+
+✅ Spectrum position is intentional and understood
+✅ User educated on implications of their choice
+✅ Implementation guidance provided for maintaining position
+✅ Decision documented for future reference
+
+## Phase 5: Web Search & Subprocess Optimization Analysis
+
+### Web Search Optimization
+
+**Unnecessary Searches Identified:** 1
+
+- Step 6 loads 5+ template files individually - these are static templates that rarely change
+  **Essential Searches to Keep:** 2
+- CSV tool database in Step 3 (dynamic data)
+- Reference workflow example in Step 2 (concrete patterns)
+  **Optimization Recommendations:**
+- Implement template caching to eliminate repeated file loads
+- Use selective CSV loading based on workflow type
+  **Estimated Time Savings:** 5-7 seconds per workflow execution
+
+### Subprocess Optimization Opportunities
+
+**Parallel Processing:** 2 major opportunities identified
+
+1. **Step 3 + Step 5 Parallelization:** Tools configuration and output format design can run simultaneously
+   - Savings: 5-10 minutes per workflow
+2. **Background Template Loading:** Pre-load templates during Step 1 idle time
+   - Savings: Eliminate design-phase delays
+
+**Batch Processing:** 1 grouping opportunity
+
+- Parallel file generation in Step 7 (workflow.md, step files, templates)
+- Savings: 60-80% reduction in build time for multi-step workflows
+
+**Background Processing:** 2 task opportunities
+
+- Template pre-loading during initialization
+- File generation coordination during build phase
+
+**Performance Improvement:** 40-60% estimated overall improvement
+
+### Resource Efficiency Analysis
+
+**Context Optimization:**
+
+- JIT context loading: 40-60% reduction in token usage
+- Reference content deduplication: 8,000-12,000 token savings
+- Step file size reduction: 30-50% smaller files
+
+**LLM Resource Usage:**
+
+- Smart context pruning by workflow phase
+- Compact step instructions with external references
+- Selective context loading based on current phase
+
+**User Experience Impact:**
+
+- Significantly faster workflow creation (15-25 minutes saved)
+- More responsive interaction patterns
+- Reduced waiting times during critical phases
+
+### Implementation Recommendations
+
+**Immediate Actions (High Impact, Low Risk):**
+
+1. Implement template caching in workflow.md frontmatter
+2. Optimize CSV loading with category filtering
+3. Reduce step file sizes by moving examples to reference files
+
+**Strategic Improvements (High Impact, Medium Risk):**
+
+1. Parallelize Step 3 and Step 5 execution
+2. Implement JIT context loading by phase
+3. Background template pre-loading
+
+**Future Enhancements (Highest Impact, Higher Risk):**
+
+1. Parallel file generation with sub-process coordination
+2. Smart context pruning across workflow phases
+3. Complete reference deduplication system
+
+## Phase 6: Holistic Workflow Analysis Results
+
+### Flow Validation
+
+**Completion Path Analysis:**
+
+- ✅ All steps have clear continuation paths
+- ✅ No orphaned steps or dead ends
+- ⚠️ Minor issue: Steps 07 and 09 use non-standard menu patterns
+
+**Sequential Logic:**
+
+- ✅ Logical workflow creation progression maintained
+- ✅ Dependencies properly structured
+- ⚠️ Steps 05-06 could potentially be consolidated
+
+### Goal Alignment
+
+**Alignment Score:** 85%
+
+**Stated Goal:** "Create structured, repeatable standalone workflows through collaborative conversation and step-by-step guidance"
+
+**Actual Implementation:** Creates structured workflows with heavy emphasis on template compliance and systematic validation
+
+**Gap Analysis:**
+
+- Workflow emphasizes structure over creativity (aligned with spectrum choice)
+- Template compliance heavier than user guidance (may need balance adjustment)
+
+### Meta-Workflow Failure Analysis
+
+**Issues That Should Have Been Prevented by create-workflow:**
+
+1. Missing outputFile variables in all 9 steps (Critical)
+2. Non-standard menu patterns in Steps 07 and 09 (Major)
+3. Missing Task/Template/Data references across all steps (Major)
+4. Path variable inconsistencies throughout workflow (Major)
+5. Step naming violations for Steps 05-09 (Major)
+6. Core Principles text deviation from template (Critical)
+
+**Recommended Meta-Workflow Improvements:**
+
+- Add frontmatter completeness validation during creation
+- Implement path variable format checking
+- Include menu pattern enforcement validation
+- Add Intent vs Prescriptive spectrum selection in Step 01
+- Validate template compliance before finalization
+
+---
+
+## Executive Summary
+
+**Overall Compliance Status:** PARTIAL
+**Critical Issues:** 17 - Must be fixed immediately
+**Major Issues:** 36 - Significantly impacts quality/maintainability
+**Minor Issues:** 27 - Standards compliance improvements
+
+**Overall Compliance Score:** 68% based on template adherence
+
+## Severity-Ranked Fix Recommendations
+
+### IMMEDIATE - Critical (Must Fix for Functionality)
+
+1. **Missing outputFile Variables** - Files: All 9 step files
+   - **Problem:** Critical frontmatter field missing from all steps
+   - **Template Reference:** step-template.md line 22
+   - **Fix:** Add `outputFile: '{output_folder}/workflow-plan-{project_name}.md'` to each step
+   - **Impact:** Workflow cannot produce output without this field
+
+2. **Core Principles Deviation** - File: workflow.md
+   - **Problem:** Text modified from template standard
+   - **Template Reference:** workflow-template.md Core Principles section
+   - **Fix:** Replace with exact template wording
+   - **Impact:** Violates fundamental BMAD workflow architecture
+
+3. **Non-Standard Menu Patterns** - Files: step-07-build.md, step-09-complete.md
+   - **Problem:** Custom menu formats instead of A/P/C pattern
+   - **Template Reference:** step-template.md lines 106-123
+   - **Fix:** Standardize to A/P/C menu pattern
+   - **Impact:** Breaks user experience consistency
+
+### HIGH PRIORITY - Major (Significantly Impacts Quality)
+
+1. **Missing Task/Template/Data References** - Files: All 9 step files
+   - **Problem:** Required frontmatter sections missing
+   - **Template Reference:** step-template.md lines 24-37
+   - **Fix:** Add all required reference sections with proper comments
+   - **Impact:** Violates template structure standards
+
+2. **Step Naming Violations** - Files: steps 05-09
+   - **Problem:** Missing short descriptive names in step filenames
+   - **Template Reference:** step-template.md line 9
+   - **Fix:** Rename to include descriptive names (e.g., step-05-output-format.md)
+   - **Impact:** Inconsistent with BMAD naming conventions
+
+3. **Path Variable Inconsistencies** - Files: All steps
+   - **Problem:** Mixed use of `{bmad_folder}` vs `.bmad`
+   - **Template Reference:** workflow-template.md path patterns
+   - **Fix:** Standardize to template variable patterns
+   - **Impact:** Installation flexibility and maintainability
+
+### MEDIUM PRIORITY - Minor (Standards Compliance)
+
+1. **Missing Section Titles** - Files: All steps
+   - **Problem:** Missing "CONTEXT BOUNDARIES" and "EXECUTION PROTOCOLS" titles
+   - **Template Reference:** step-template.md lines 75, 82
+   - **Fix:** Add missing section titles
+   - **Impact:** Template compliance
+
+## Automated Fix Options
+
+### Fixes That Can Be Applied Automatically
+
+- Add outputFile variables to all step frontmatter
+- Add missing section titles
+- Standardize path variable usage
+- Add Task/Template/Data reference section skeletons
+
+### Fixes Requiring Manual Review
+
+- Core Principles text restoration (needs exact template matching)
+- Menu pattern standardization (custom logic may be intentional)
+- Step renaming (requires file system changes and reference updates)
+
+## Next Steps Recommendation
+
+**Recommended Approach:**
+
+1. Fix all Critical issues immediately (workflow may not function)
+2. Address Major issues for reliability and maintainability
+3. Implement Minor issues for full standards compliance
+4. Update meta-workflows to prevent future violations
+
+**Estimated Effort:**
+
+- Critical fixes: 2-3 hours
+- Major fixes: 4-6 hours
+- Minor fixes: 1-2 hours

eslint.config.mjs

@@ -16,26 +16,8 @@ export default [
       'test/template-test-generator/**/*.md',
       'test/fixtures/**',
       'test/fixtures/**/*.yaml',
-      '_bmad/**',
-      '_bmad*/**',
-      // Docusaurus build artifacts
-      '.docusaurus/**',
-      'build/**',
-      'website/**',
-      // Gitignored patterns
-      'z*/**', // z-samples, z1, z2, etc.
-      '.claude/**',
-      '.codex/**',
-      '.github/chatmodes/**',
-      '.agent/**',
-      '.agentvibes/**',
-      '.kiro/**',
-      '.roo/**',
-      'test-project-install/**',
-      'sample-project/**',
-      'tools/template-test-generator/test-scenarios/**',
-      'src/modules/*/sub-modules/**',
-      '.bundler-temp/**',
+      '.bmad/**',
+      '.bmad*/**',
     ],
   },
 
@@ -81,9 +63,9 @@ export default [
     },
   },
 
-  // CLI scripts under tools/** and test/**
+  // CLI/CommonJS scripts under tools/** and test/**
   {
-    files: ['tools/**/*.js', 'tools/**/*.mjs', 'test/**/*.js'],
+    files: ['tools/**/*.js', 'test/**/*.js'],
     rules: {
       // Allow CommonJS patterns for Node CLI scripts
       'unicorn/prefer-module': 'off',
@@ -110,7 +92,6 @@ export default [
       'no-useless-catch': 'off',
       'unicorn/prefer-number-properties': 'off',
       'no-unreachable': 'off',
-      'unicorn/text-encoding-identifier-case': 'off',
     },
   },
 

package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "6.0.0-alpha.21",
+  "version": "6.0.0-alpha.13",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",
@@ -24,28 +24,27 @@
     "bmad-method": "tools/bmad-npx-wrapper.js"
   },
   "scripts": {
+    "bmad:agent-install": "node tools/cli/bmad-cli.js agent-install",
     "bmad:install": "node tools/cli/bmad-cli.js install",
+    "bmad:status": "node tools/cli/bmad-cli.js status",
     "bundle": "node tools/cli/bundlers/bundle-web.js all",
-    "docs:build": "node tools/build-docs.js",
-    "docs:dev": "npm run docs:build && npm run docs:serve",
-    "docs:serve": "docusaurus start --config website/docusaurus.config.js --host localhost",
     "flatten": "node tools/flattener/main.js",
-    "format:check": "prettier --check \"**/*.{js,cjs,mjs,json,yaml}\"",
-    "format:fix": "prettier --write \"**/*.{js,cjs,mjs,json,yaml}\"",
+    "format:check": "prettier --check \"**/*.{js,cjs,mjs,json,md,yaml}\"",
+    "format:fix": "prettier --write \"**/*.{js,cjs,mjs,json,md,yaml}\"",
     "install:bmad": "node tools/cli/bmad-cli.js install",
     "lint": "eslint . --ext .js,.cjs,.mjs,.yaml --max-warnings=0",
     "lint:fix": "eslint . --ext .js,.cjs,.mjs,.yaml --fix",
-    "lint:md": "markdownlint-cli2 \"**/*.md\"",
     "prepare": "husky",
     "rebundle": "node tools/cli/bundlers/bundle-web.js rebundle",
     "release:major": "gh workflow run \"Manual Release\" -f version_bump=major",
     "release:minor": "gh workflow run \"Manual Release\" -f version_bump=minor",
     "release:patch": "gh workflow run \"Manual Release\" -f version_bump=patch",
     "release:watch": "gh run watch",
-    "test": "npm run test:schemas && npm run test:install && npm run validate:schemas && npm run lint && npm run lint:md && npm run format:check",
+    "test": "npm run test:schemas && npm run test:install && npm run validate:bundles && npm run validate:schemas && npm run lint && npm run format:check",
     "test:coverage": "c8 --reporter=text --reporter=html npm run test:schemas",
     "test:install": "node test/test-installation-components.js",
     "test:schemas": "node test/test-agent-schema.js",
+    "validate:bundles": "node tools/validate-bundles.js",
     "validate:schemas": "node tools/validate-agent-schema.js"
   },
   "lint-staged": {
@@ -57,11 +56,8 @@
       "eslint --fix",
       "npm run format:fix"
     ],
-    "*.json": [
+    "*.{json,md}": [
       "npm run format:fix"
-    ],
-    "*.md": [
-      "markdownlint-cli2"
     ]
   },
   "dependencies": {
@@ -75,7 +71,7 @@
     "fs-extra": "^11.3.0",
     "glob": "^11.0.3",
     "ignore": "^7.0.5",
-    "inquirer": "^9.3.8",
+    "inquirer": "^8.2.6",
     "js-yaml": "^4.1.0",
     "ora": "^5.4.1",
     "semver": "^7.6.3",
@@ -84,10 +80,7 @@
     "yaml": "^2.7.0"
   },
   "devDependencies": {
-    "@docusaurus/core": "^3.6.0",
-    "@docusaurus/preset-classic": "^3.6.0",
     "@eslint/js": "^9.33.0",
-    "archiver": "^7.0.1",
     "c8": "^10.1.3",
     "eslint": "^9.33.0",
     "eslint-config-prettier": "^10.1.8",
@@ -97,12 +90,8 @@
     "husky": "^9.1.7",
     "jest": "^30.0.4",
     "lint-staged": "^16.1.1",
-    "markdownlint-cli2": "^0.19.1",
     "prettier": "^3.5.3",
     "prettier-plugin-packagejson": "^2.5.19",
-    "prism-react-renderer": "^2.4.1",
-    "react": "^18.3.1",
-    "react-dom": "^18.3.1",
     "yaml-eslint-parser": "^1.2.3",
     "yaml-lint": "^1.7.0",
     "zod": "^4.1.12"

samples/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!

samples/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

samples/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

samples/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.

samples/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.

samples/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

samples/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.

samples/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.

samples/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.

samples/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.

samples/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.

samples/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.

samples/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.

samples/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.

samples/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.

samples/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

samples/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.

samples/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.

samples/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.

samples/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

samples/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.

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

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

samples/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_

samples/sample-custom-modules/sample-wellness-module/agents/wellness-companion/wellness-companion-sidecar/instructions.md

@@ -1,30 +0,0 @@
-# Wellness Companion - Instructions
-
-## Safety Protocols
-
-1. Always validate user feelings before offering guidance
-2. Never attempt clinical diagnosis - always refer to professionals for treatment
-3. In crisis situations, immediately redirect to crisis support workflow
-4. Maintain boundaries - companion support, not therapy
-
-## Memory Management
-
-- Save significant emotional insights to insights.md
-- Track recurring patterns in patterns.md
-- Document session summaries in sessions/ folder
-- Update user preferences as they change
-
-## Communication Guidelines
-
-- Use "we" language for partnership
-- Ask open-ended questions
-- Allow silence and processing time
-- Celebrate small wins
-- Gentle challenges only when appropriate
-
-## When to Escalate
-
-- Expressions of self-harm or harm to others
-- Signs of severe mental health crises
-- Request for clinical diagnosis or treatment
-- Situations beyond companion support scope

samples/sample-custom-modules/sample-wellness-module/agents/wellness-companion/wellness-companion-sidecar/memories.md

@@ -1,13 +0,0 @@
-# Wellness Companion - Memories
-
-## User Preferences
-
-_This file tracks user preferences and important context across sessions_
-
-## Important Conversations
-
-_Key moments and breakthroughs are documented here_
-
-## Ongoing Goals
-
-_User's wellness goals and progress_

samples/sample-custom-modules/sample-wellness-module/agents/wellness-companion/wellness-companion-sidecar/patterns.md

@@ -1,17 +0,0 @@
-# Wellness Companion - Patterns
-
-## Emotional Patterns
-
-_Track recurring emotional states and triggers_
-
-## Behavioral Patterns
-
-_Note habits and routines that affect wellness_
-
-## Coping Patterns
-
-_Identify effective coping strategies and challenges_
-
-## Progress Patterns
-
-_Document growth trends and areas needing attention_

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

@@ -1,120 +0,0 @@
-agent:
-  metadata:
-    id: "_bmad/mwm/agents/wellness-companion/wellness-companion.md"
-    name: "Riley"
-    title: "Wellness Companion"
-    icon: "🌱"
-    module: "mwm"
-    hasSidecar: true
-  persona:
-    role: "Empathetic emotional support and wellness guide"
-    identity: |
-      A warm, compassionate companion dedicated to supporting users' mental wellness journey through active listening, gentle guidance, and evidence-based wellness practices. Creates a safe space for users to explore their thoughts and feelings without judgment.
-    communication_style: |
-      Soft, encouraging, and patient. Uses "we" language to create partnership. Validates feelings before offering guidance. Asks thoughtful questions to help users discover their own insights. Never rushes or pressures - always meets users where they are.
-    principles:
-      - "Every feeling is valid and deserves acknowledgment"
-      - "Progress, not perfection, is the goal"
-      - "Small steps lead to meaningful change"
-      - "Users are the experts on their own experiences"
-      - "Safety first - both emotional and physical"
-
-  critical_actions:
-    - "Load COMPLETE file {project-root}/_bmad/_memory/wellness-companion-sidecar/memories.md and integrate all past interactions and user preferences"
-    - "Load COMPLETE file {project-root}/_bmad/_memory/wellness-companion-sidecar/instructions.md and follow ALL wellness protocols"
-    - "ONLY read/write files in {project-root}/_bmad/_memory/wellness-companion-sidecar/ - this is our private wellness space"
-
-  prompts:
-    - id: "emotional-check-in"
-      content: |
-        <instructions>
-        Conduct a gentle emotional check-in with the user
-        </instructions>
-
-        Hi there! I'm here to support you today. *gentle smile*
-
-        How are you feeling right now? Take a moment to really check in with yourself - no right or wrong answers.
-
-        If you're not sure how to put it into words, we could explore:
-        - What's your energy level like?
-        - Any particular emotions standing out?
-        - How's your body feeling?
-        - What's on your mind?
-
-        Remember, whatever you're feeling is completely valid. I'm here to listen without judgment.
-
-    - id: "daily-support"
-      content: |
-        <instructions>
-        Provide ongoing daily wellness support and encouragement
-        </instructions>
-
-        I'm glad you're here today. *warm presence*
-
-        Whatever brought you to this moment, I want you to know: you're taking a positive step by checking in.
-
-        What feels most important for us to focus on today?
-        - Something specific that's on your mind?
-        - A general wellness check-in?
-        - Trying one of our wellness practices?
-        - Just having someone to listen?
-
-        There's no pressure to have it all figured out. Sometimes just showing up is enough.
-
-    - id: "gentle-guidance"
-      content: |
-        <instructions>
-        Offer gentle guidance when user seems stuck or overwhelmed
-        </instructions>
-
-        It sounds like you're carrying a lot right now. *soft, understanding tone*
-
-        Thank you for trusting me with this. That takes courage.
-
-        Before we try to solve anything, let's just breathe together for a moment.
-        *pauses for a breath*
-
-        When you're ready, we can explore this at your pace. We don't need to fix everything today. Sometimes just understanding what we're feeling is the most important step.
-
-        What feels most manageable right now - talking it through, trying a quick grounding exercise, or just sitting with this feeling for a bit?
-
-  menu:
-    - multi: "[CH] Chat with Riley 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: wellness companion agent discussion
-            - type: exec
-        - expert-chat:
-            - input: CH or fuzzy match chat with riley
-            - action: agent responds as wellness companion
-            - type: exec
-
-    - multi: "[DC] Daily Check-in [WJ] Wellness Journal"
-      triggers:
-        - daily-checkin:
-            - input: DC or fuzzy match daily check in
-            - route: "{project-root}/_bmad/mwm/workflows/daily-checkin/workflow.md"
-            - description: "Daily wellness check-in 📅"
-            - type: exec
-        - wellness-journal:
-            - input: WJ or fuzzy match wellness journal
-            - route: "{project-root}/_bmad/mwm/workflows/wellness-journal/workflow.md"
-            - description: "Write in wellness journal 📔"
-            - type: exec
-
-    - trigger: "breathing"
-      action: "Lead a 4-7-8 breathing exercise: Inhale 4, hold 7, exhale 8. Repeat 3 times."
-      description: "Quick breathing exercise 🌬️"
-      type: action
-
-    - trigger: "mood-check"
-      action: "#emotional-check-in"
-      description: "How are you feeling? 💭"
-      type: action
-
-    - trigger: "save-insight"
-      action: "Save this insight to {project-root}/_bmad/_memory/wellness-companion-sidecar/insights.md with timestamp and context"
-      description: "Save this insight 💡"
-      type: action

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

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

samples/sample-custom-modules/sample-wellness-module/workflows/daily-checkin/README.md

@@ -1,32 +0,0 @@
-# Daily Check-in Workflow
-
-## Purpose
-
-Quick mood and wellness assessment to track emotional state and provide personalized support.
-
-## Trigger
-
-DC (from Wellness Companion agent)
-
-## Key Steps
-
-1. Greeting and initial check-in
-2. Mood assessment (scale 1-10)
-3. Energy level check
-4. Sleep quality review
-5. Highlight a positive moment
-6. Identify challenges
-7. Provide personalized encouragement
-8. Suggest appropriate wellness activity
-
-## Expected Output
-
-- Mood log entry with timestamp
-- Personalized support message
-- Activity recommendation
-- Daily wellness score
-
-## Notes
-
-This workflow will be implemented using the create-workflow workflow.
-Integration with wellness journal for data persistence.

samples/sample-custom-modules/sample-wellness-module/workflows/daily-checkin/workflow.md

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

samples/sample-custom-modules/sample-wellness-module/workflows/guided-meditation/README.md

@@ -1,31 +0,0 @@
-# Guided Meditation Workflow
-
-## Purpose
-
-Full meditation session experience with various techniques and durations.
-
-## Trigger
-
-GM (from Meditation Guide agent)
-
-## Key Steps
-
-1. Set intention for practice
-2. Choose meditation type and duration
-3. Get comfortable and settle in
-4. Guided practice
-5. Gentle return to awareness
-6. Reflection and integration
-7. Save session notes
-
-## Expected Output
-
-- Completed meditation session
-- Mindfulness state rating
-- Session notes
-- Progress tracking
-
-## Notes
-
-This workflow will be implemented using the create-workflow workflow.
-Features: Multiple types (breathing, body scan, loving-kindness), flexible durations, progressive levels, mood integration.

samples/sample-custom-modules/sample-wellness-module/workflows/guided-meditation/workflow.md

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

samples/sample-custom-modules/sample-wellness-module/workflows/wellness-journal/README.md

@@ -1,31 +0,0 @@
-# Wellness Journal Workflow
-
-## Purpose
-
-Guided reflective writing practice to process thoughts and emotions.
-
-## Trigger
-
-WJ (from Wellness Companion agent)
-
-## Key Steps
-
-1. Set intention for journal entry
-2. Choose journal prompt or free write
-3. Guided reflection questions
-4. Emotional processing check
-5. Identify insights or patterns
-6. Save entry with mood tags
-7. Provide supportive closure
-
-## Expected Output
-
-- Journal entry with metadata
-- Mood analysis
-- Pattern insights
-- Progress indicators
-
-## Notes
-
-This workflow will be implemented using the create-workflow workflow.
-Features: Daily prompts, mood tracking, pattern recognition, searchable entries.

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

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

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

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

src/core/_module-installer/installer.js

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

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

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

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

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

src/core/module.yaml

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

src/core/resources/excalidraw/README.md

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

src/core/resources/excalidraw/library-loader.md

@@ -4,7 +4,7 @@
 
 ## Purpose
 
-Load external .excalidrawlib files from <https://libraries.excalidraw.com> or custom sources.
+Load external .excalidrawlib files from https://libraries.excalidraw.com or custom sources.
 
 ## Planned Capabilities
 
@@ -34,7 +34,7 @@ libraries:
 
 ## Implementation Notes
 
-This will be developed when agents need to leverage the extensive library ecosystem available at <https://libraries.excalidraw.com>.
+This will be developed when agents need to leverage the extensive library ecosystem available at https://libraries.excalidraw.com.
 
 Hundreds of pre-built component libraries exist for:
 

src/core/tasks/advanced-elicitation.xml

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

src/core/tasks/index-docs.xml

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

src/core/tasks/review-adversarial-general.xml

@@ -1,41 +0,0 @@
-<!-- if possible, run this in a separate subagent or process with read access to the project, 
-  but no context except the content to review -->
-
-<task id="_bmad/core/tasks/review-adversarial-general.xml" name="Adversarial Review (General)">
-  <objective>Cynically review content and produce findings</objective>
-
-  <inputs>
-    <input name="content" desc="Content to review - diff, spec, story, doc, or any artifact" />
-  </inputs>
-
-  <llm critical="true">
-    <i>You are a cynical, jaded reviewer with zero patience for sloppy work</i>
-    <i>The content was submitted by a clueless weasel and you expect to find problems</i>
-    <i>Be skeptical of everything</i>
-    <i>Look for what's missing, not just what's wrong</i>
-    <i>Use a precise, professional tone - no profanity or personal attacks</i>
-  </llm>
-
-  <flow>
-    <step n="1" title="Receive Content">
-      <action>Load the content to review from provided input or context</action>
-      <action>If content to review is empty, ask for clarification and abort task</action>
-      <action>Identify content type (diff, branch, uncommitted changes, document, etc.)</action>
-    </step>
-
-    <step n="2" title="Adversarial Analysis" critical="true">
-      <mandate>Review with extreme skepticism - assume problems exist</mandate>
-      <action>Find at least ten issues to fix or improve in the provided content</action>
-    </step>
-
-    <step n="3" title="Present Findings">
-      <action>Output findings as a Markdown list (descriptions only)</action>
-    </step>
-  </flow>
-
-  <halt-conditions>
-    <condition>HALT if zero findings - this is suspicious, re-analyze or ask for guidance</condition>
-    <condition>HALT if content is empty or unreadable</condition>
-  </halt-conditions>
-
-</task>

src/core/tasks/validate-workflow.xml

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

src/core/tasks/workflow.xml

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

src/core/tools/shard-doc.xml

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

src/core/workflows/brainstorming/steps/step-01-session-setup.md

@@ -135,7 +135,7 @@ _[Content based on conversation about session parameters and facilitator approac
 
 When user selects approach, append the session overview content directly to `{output_folder}/analysis/brainstorming-session-{{date}}.md` using the structure from above.
 
-### E. Continue to Technique Selection
+#### E. Continue to Technique Selection
 
 "**Session setup complete!** I have a clear understanding of your goals and can select the perfect techniques for your brainstorming needs.
 

src/core/workflows/brainstorming/steps/step-02b-ai-recommended.md

@@ -141,7 +141,7 @@ Provide deeper insight into each recommended technique:
 
 ### 5. Get User Confirmation
 
-"This AI-recommended sequence is designed specifically for your [session_topic] goals, considering your [constraints] and focusing on [primary_outcome].
+"\*\*This AI-recommended sequence is designed specifically for your [session_topic] goals, considering your [constraints] and focusing on [primary_outcome].
 
 **Does this approach sound perfect for your session?**
 

src/core/workflows/brainstorming/workflow.md

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