V1 Legacy Branch Frozen

.coderabbit.yaml

@@ -1,36 +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: true
-  request_changes_workflow: false
-  review_status: false
-  collapse_walkthrough: false
-  poem: false
-  auto_review:
-    enabled: false # must be manually triggered with @coderabbit review
-    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
-

.github/CODE_OF_CONDUCT.md

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

.github/FUNDING.yaml

@@ -1,15 +0,0 @@
-# These are supported funding model platforms
-
-github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
-patreon: # Replace with a single Patreon username
-open_collective: # Replace with a single Open Collective username
-ko_fi: # Replace with a single Ko-fi username
-tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
-community_bridge: # Replace with a single Community Bridge project_name e.g., cloud-foundry
-liberapay: # Replace with a single Liberapay username
-issuehunt: # Replace with a single IssueHunt username
-lfx_crowdfunding: # Replace with a single LFX Crowdfunding project_name e.g., cloud-foundry
-polar: # Replace with a single Polar username
-buy_me_a_coffee: bmad
-thanks_dev: # Replace with a single thanks.dev username
-custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

.github/ISSUE_TEMPLATE/bug_report.md

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

.github/ISSUE_TEMPLATE/config.yaml

@@ -1,5 +0,0 @@
-blank_issues_enabled: false
-contact_links:
-  - name: Discord Community Support
-    url: https://discord.gg/gk8jAdXWmj
-    about: Please join our Discord server for general questions and community discussion before opening an issue.

.github/ISSUE_TEMPLATE/idea_submission.md

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

.github/scripts/discord-helpers.sh

@@ -1,15 +0,0 @@
-#!/bin/bash
-# Discord notification helper functions
-
-# Escape markdown special chars and @mentions for safe Discord display
-# Bracket expression: ] must be first, then other chars. In POSIX bracket expr, \ is literal.
-esc() { sed -e 's/[][\*_()~`>]/\\&/g' -e 's/@/@ /g'; }
-
-# 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"
-}

.github/workflows/bundle-latest.yaml

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

.github/workflows/discord.yaml

@@ -1,286 +0,0 @@
-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
-
-jobs:
-  pull_request:
-    if: github.event_name == 'pull_request'
-    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 }}
-          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 | 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 | 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 | 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 | 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 | 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 | 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 @-

.github/workflows/manual-release.yaml

@@ -1,220 +0,0 @@
-name: Manual Release
-
-on:
-  workflow_dispatch:
-    inputs:
-      version_bump:
-        description: Version bump type
-        required: true
-        default: patch
-        type: choice
-        options:
-          - patch
-          - minor
-          - major
-
-permissions:
-  contents: write
-  packages: write
-
-jobs:
-  release:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-          token: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version-file: ".nvmrc"
-          cache: npm
-          registry-url: https://registry.npmjs.org
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Run tests and validation
-        run: |
-          npm run validate
-          npm run format:check
-          npm run lint
-
-      - name: Configure Git
-        run: |
-          git config user.name "github-actions[bot]"
-          git config user.email "github-actions[bot]@users.noreply.github.com"
-
-      - name: Bump version
-        run: npm run version:${{ github.event.inputs.version_bump }}
-
-      - name: Get new version and previous tag
-        id: version
-        run: |
-          echo "new_version=$(node -p "require('./package.json').version")" >> $GITHUB_OUTPUT
-          echo "previous_tag=$(git describe --tags --abbrev=0)" >> $GITHUB_OUTPUT
-
-      - name: Update installer package.json
-        run: |
-          sed -i 's/"version": ".*"/"version": "${{ steps.version.outputs.new_version }}"/' tools/installer/package.json
-
-      - name: Generate web bundles
-        run: npm run bundle
-
-      - name: Package bundles for release
-        run: |
-          mkdir -p dist/release-bundles
-
-          # Copy web bundles
-          cp -r web-bundles dist/release-bundles/bmad-bundles-v${{ steps.version.outputs.new_version }}
-
-          # Verify bundles exist
-          if [ ! "$(ls -A dist/release-bundles/bmad-bundles-v${{ steps.version.outputs.new_version }})" ]; then
-            echo "❌ ERROR: No bundles found"
-            echo "This likely means 'npm run bundle' failed"
-            exit 1
-          fi
-
-          # Count and display bundles per module
-          for module in bmm bmb cis bmgd; do
-            if [ -d "dist/release-bundles/bmad-bundles-v${{ steps.version.outputs.new_version }}/$module/agents" ]; then
-              COUNT=$(find dist/release-bundles/bmad-bundles-v${{ steps.version.outputs.new_version }}/$module/agents -name '*.xml' 2>/dev/null | wc -l)
-              echo "✅ $module: $COUNT agents"
-            fi
-          done
-
-          # Create archive
-          tar -czf dist/release-bundles/bmad-bundles-v${{ steps.version.outputs.new_version }}.tar.gz \
-            -C dist/release-bundles/bmad-bundles-v${{ steps.version.outputs.new_version }} .
-
-      - name: Commit version bump
-        run: |
-          git add .
-          git commit -m "release: bump to v${{ steps.version.outputs.new_version }}"
-
-      - name: Generate release notes
-        id: release_notes
-        run: |
-          # Get commits since last tag
-          COMMITS=$(git log ${{ steps.version.outputs.previous_tag }}..HEAD --pretty=format:"- %s" --reverse)
-
-          # Categorize commits
-          FEATURES=$(echo "$COMMITS" | grep -E "^- (feat|Feature)" || true)
-          FIXES=$(echo "$COMMITS" | grep -E "^- (fix|Fix)" || true)  
-          CHORES=$(echo "$COMMITS" | grep -E "^- (chore|Chore)" || true)
-          OTHERS=$(echo "$COMMITS" | grep -v -E "^- (feat|Feature|fix|Fix|chore|Chore|release:|Release:)" || true)
-
-          # Build release notes
-          cat > release_notes.md << 'EOF'
-          ## 🚀 What's New in v${{ steps.version.outputs.new_version }}
-
-          EOF
-
-          if [ ! -z "$FEATURES" ]; then
-            echo "### ✨ New Features" >> release_notes.md
-            echo "$FEATURES" >> release_notes.md
-            echo "" >> release_notes.md
-          fi
-
-          if [ ! -z "$FIXES" ]; then
-            echo "### 🐛 Bug Fixes" >> release_notes.md
-            echo "$FIXES" >> release_notes.md
-            echo "" >> release_notes.md
-          fi
-
-          if [ ! -z "$OTHERS" ]; then
-            echo "### 📦 Other Changes" >> release_notes.md
-            echo "$OTHERS" >> release_notes.md
-            echo "" >> release_notes.md
-          fi
-
-          if [ ! -z "$CHORES" ]; then
-            echo "### 🔧 Maintenance" >> release_notes.md
-            echo "$CHORES" >> release_notes.md
-            echo "" >> release_notes.md
-          fi
-
-          cat >> release_notes.md << 'EOF'
-
-          ## 📦 Installation
-
-          ```bash
-          npx bmad-method install
-          ```
-
-          **Full Changelog**: https://github.com/bmad-code-org/BMAD-METHOD/compare/${{ steps.version.outputs.previous_tag }}...v${{ steps.version.outputs.new_version }}
-          EOF
-
-          # Output for GitHub Actions
-          echo "RELEASE_NOTES<<EOF" >> $GITHUB_OUTPUT
-          cat release_notes.md >> $GITHUB_OUTPUT
-          echo "EOF" >> $GITHUB_OUTPUT
-
-      - name: Create and push tag
-        run: |
-          # Check if tag already exists
-          if git rev-parse "v${{ steps.version.outputs.new_version }}" >/dev/null 2>&1; then
-            echo "Tag v${{ steps.version.outputs.new_version }} already exists, skipping tag creation"
-          else
-            git tag -a "v${{ steps.version.outputs.new_version }}" -m "Release v${{ steps.version.outputs.new_version }}"
-            git push origin "v${{ steps.version.outputs.new_version }}"
-          fi
-
-      - name: Push changes to main
-        run: |
-          if git push origin HEAD:main 2>/dev/null; then
-            echo "✅ Successfully pushed to main branch"
-          else
-            echo "⚠️ Could not push to main (protected branch). This is expected."
-            echo "📝 Version bump and tag were created successfully."
-          fi
-
-      - name: Publish to NPM
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-        run: |
-          VERSION="${{ steps.version.outputs.new_version }}"
-          if [[ "$VERSION" == *"alpha"* ]] || [[ "$VERSION" == *"beta"* ]]; then
-            echo "Publishing prerelease version with --tag alpha"
-            npm publish --tag alpha
-          else
-            echo "Publishing stable version with --tag latest"
-            npm publish --tag latest
-          fi
-
-      - 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: |
-          echo "## 🎉 Successfully released v${{ steps.version.outputs.new_version }}!" >> $GITHUB_STEP_SUMMARY
-          echo "" >> $GITHUB_STEP_SUMMARY
-          echo "### 📦 Distribution" >> $GITHUB_STEP_SUMMARY
-          echo "- **NPM**: Published with @latest tag" >> $GITHUB_STEP_SUMMARY
-          echo "- **GitHub Release**: https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v${{ steps.version.outputs.new_version }}" >> $GITHUB_STEP_SUMMARY
-          echo "- **Web Bundles**: Attached to GitHub Release (4 archives)" >> $GITHUB_STEP_SUMMARY
-          echo "" >> $GITHUB_STEP_SUMMARY
-          echo "### ✅ Installation" >> $GITHUB_STEP_SUMMARY
-          echo "\`\`\`bash" >> $GITHUB_STEP_SUMMARY
-          echo "npx bmad-method@${{ steps.version.outputs.new_version }} install" >> $GITHUB_STEP_SUMMARY
-          echo "\`\`\`" >> $GITHUB_STEP_SUMMARY

.github/workflows/quality.yaml

@@ -1,97 +0,0 @@
-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)
-# - Bundle validation (web bundle integrity)
-
-"on":
-  pull_request:
-    branches: ["**"]
-  workflow_dispatch:
-
-jobs:
-  prettier:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Setup Node
-        uses: actions/setup-node@v4
-        with:
-          node-version-file: ".nvmrc"
-          cache: "npm"
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Prettier format check
-        run: npm run format:check
-
-  eslint:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Setup Node
-        uses: actions/setup-node@v4
-        with:
-          node-version-file: ".nvmrc"
-          cache: "npm"
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: ESLint
-        run: npm run lint
-
-  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:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Setup Node
-        uses: actions/setup-node@v4
-        with:
-          node-version-file: ".nvmrc"
-          cache: "npm"
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Validate YAML schemas
-        run: npm run validate:schemas
-
-      - name: Run agent schema validation tests
-        run: npm run test:schemas
-
-      - name: Test agent compilation components
-        run: npm run test:install
-
-      - name: Validate web bundles
-        run: npm run validate:bundles

.gitignore

@@ -1,77 +1,21 @@
-# Dependencies
+# Node modules
 node_modules/
-pnpm-lock.yaml
-bun.lock
-deno.lock
-pnpm-workspace.yaml
-package-lock.json
-
-
-test-output/*
-coverage/
 
 # Logs
-logs/
+logs
 *.log
 npm-debug.log*
 
 # Build output
-build/*.txt
+dist/
+build/
+
+# System files
+.DS_Store
 
 # Environment variables
 .env
 
-# System files
-.DS_Store
-Thumbs.db
-
-# Development tools and configs
-.prettierrc
-
-# IDE and editor configs
-.windsurf/
-.trae/
-.bmad*/.cursor/
-
-# AI assistant files
-CLAUDE.md
-.ai/*
-cursor
-.gemini
-.mcp.json
-CLAUDE.local.md
-.serena/
-.claude/settings.local.json
-
-# Project-specific
-.bmad-core
-.bmad-creator-tools
-test-project-install/*
-sample-project/*
-flattened-codebase.xml
-*.stats.md
-.internal-docs/
-#UAT template testing output files
-tools/template-test-generator/test-scenarios/
-
-# Bundler temporary files and generated bundles
-.bundler-temp/
-
-# Generated web bundles (built by CI, not committed)
-src/modules/bmm/sub-modules/
-src/modules/bmb/sub-modules/
-src/modules/cis/sub-modules/
-src/modules/bmgd/sub-modules/
-shared-modules
-z*/
-
-.bmad
-.claude
-.codex
-.github/chatmodes
-.agent
-.agentvibes/
-.kiro/
-.roo
-
-bmad-custom-src/
+# VSCode settings
+.vscode/
+CLAUDE.md

.husky/pre-commit

@@ -1,7 +0,0 @@
-#!/usr/bin/env sh
-
-# Auto-fix changed files and stage them
-npx --no-install lint-staged
-
-# Validate everything
-npm test

.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

.npmrc

@@ -1 +0,0 @@
-registry=https://registry.npmjs.org

.nvmrc

@@ -1 +0,0 @@
-22

.prettierignore

@@ -1,9 +0,0 @@
-# Test fixtures with intentionally broken/malformed files
-test/fixtures/**
-
-# Contributor Covenant (external standard)
-CODE_OF_CONDUCT.md
-
-# BMAD runtime folders (user-specific, not in repo)
-.bmad/
-.bmad*/

.vscode/settings.json

@@ -1,96 +0,0 @@
-{
-  "chat.agent.enabled": true,
-  "chat.agent.maxRequests": 15,
-  "github.copilot.chat.agent.runTasks": true,
-  "chat.mcp.discovery.enabled": {
-    "claude-desktop": true,
-    "windsurf": true,
-    "cursor-global": true,
-    "cursor-workspace": true
-  },
-  "github.copilot.chat.agent.autoFix": true,
-  "chat.tools.autoApprove": false,
-  "cSpell.words": [
-    "Agentic",
-    "atlasing",
-    "Biostatistician",
-    "bmad",
-    "Cordova",
-    "customresourcedefinitions",
-    "dashboarded",
-    "Decisioning",
-    "eksctl",
-    "elicitations",
-    "Excalidraw",
-    "filecomplete",
-    "fintech",
-    "fluxcd",
-    "frontmatter",
-    "gamedev",
-    "gitops",
-    "implementability",
-    "Improv",
-    "inclusivity",
-    "ingressgateway",
-    "istioctl",
-    "metroidvania",
-    "NACLs",
-    "nodegroup",
-    "platformconfigs",
-    "Playfocus",
-    "playtesting",
-    "pointerdown",
-    "pointerup",
-    "Polyrepo",
-    "replayability",
-    "roguelike",
-    "roomodes",
-    "Runbook",
-    "runbooks",
-    "Shardable",
-    "Softlock",
-    "solutioning",
-    "speedrunner",
-    "substep",
-    "tekton",
-    "tilemap",
-    "tileset",
-    "tmpl",
-    "Trae",
-    "VNET",
-    "webskip"
-  ],
-  "json.schemas": [
-    {
-      "fileMatch": ["package.json"],
-      "url": "https://json.schemastore.org/package.json"
-    },
-    {
-      "fileMatch": [".vscode/settings.json"],
-      "url": "vscode://schemas/settings/folder"
-    }
-  ],
-  "editor.formatOnSave": true,
-  "editor.defaultFormatter": "esbenp.prettier-vscode",
-  "[javascript]": {
-    "editor.defaultFormatter": "esbenp.prettier-vscode"
-  },
-  "[json]": {
-    "editor.defaultFormatter": "vscode.json-language-features"
-  },
-  "[yaml]": {
-    "editor.defaultFormatter": "esbenp.prettier-vscode"
-  },
-  "[markdown]": {
-    "editor.defaultFormatter": "yzhang.markdown-all-in-one"
-  },
-  "yaml.format.enable": false,
-  "editor.codeActionsOnSave": {
-    "source.fixAll.eslint": "explicit"
-  },
-  "editor.rulers": [140],
-  "[xml]": {
-    "editor.defaultFormatter": "redhat.vscode-xml"
-  },
-  "xml.format.maxLineWidth": 140
-}

CHANGELOG.md

@@ -1,655 +0,0 @@
-# Changelog
-
-## [6.0.0-alpha.16]
-
-**Release: December 10, 2025**
-
-### 🔧 Temporary Changes & Fixes
-
-**Installation Improvements:**
-
-- **Temporary Custom Content Installation Disable**: Custom content installation temporarily disabled to improve stability
-- **BMB Workflow Path Fixes**: Fixed numerous path references in BMB workflows to ensure proper step file resolution
-- **Package Updates**: Updated dependencies for improved security and performance
-
-**Path Resolution Improvements:**
-
-- **BMB Agent Builder Fixes**: Corrected path references in step files and documentation
-- **Workflow Path Standardization**: Ensured consistent path handling across all BMB workflows
-- **Documentation References**: Updated internal documentation links and references
-
-**Cleanup Changes:**
-
-- **Example Modules Removal**: Temporarily removed example modules to prevent accidental installation
-- **Hardcoded Path Cleanup**: Continued removal of hardcoded `.bmad` folder references from demo content
-- **Memory Management**: Improved sidecar file handling for custom modules
-
-### 📊 Statistics
-
-- **336 files changed** with path fixes and improvements
-- **4 commits** since alpha.15
-
----
-
-## [6.0.0-alpha.15]
-
-**Release: December 7, 2025**
-
-### 🔧 Module Installation Standardization
-
-**Unified Module Configuration:**
-
-- **module.yaml Standard**: All modules now use `module.yaml` instead of `_module-installer/install-config.yaml` for consistent configuration (BREAKING CHANGE)
-- **Universal Installer**: Both core and custom modules now use the same installer with consistent behavior
-- **Streamlined Module Creation**: Module builder templates updated to use new module.yaml standard
-- **Enhanced Module Discovery**: Improved module caching and discovery mechanisms
-
-**Custom Content Installation Revolution:**
-
-- **Interactive Custom Content Search**: Installer now proactively asks if you have custom content to install
-- **Flexible Location Specification**: Users can indicate custom content location during installation
-- **Improved Custom Module Handler**: Enhanced error handling and debug output for custom installations
-- **Comprehensive Documentation**: New custom-content-installation.md guide (245 lines) replacing custom-agent-installation.md
-
-### 🤖 Code Review Integration Expansion
-
-**AI Review Tools:**
-
-- **CodeRabbit AI Integration**: Added .coderabbit.yaml configuration for automated code review
-- **Raven's Verdict PR Review Tool**: New PR review automation tool (297 lines of documentation)
-- **Review Path Configuration**: Proper exclusion patterns for node_modules and generated files
-- **Review Documentation**: Comprehensive usage guidance and skip conditions for PRs
-
-### 📚 Documentation Improvements
-
-**Documentation Restructuring:**
-
-- **Code of Conduct**: Moved to .github/ folder following GitHub standards
-- **Gem Creation Link**: Updated to point to Gemini Gem manager instead of deprecated interface
-- **Example Custom Content**: Improved README files and disabled example modules to prevent accidental installation
-- **Custom Module Documentation**: Enhanced module installation guides with new YAML structure
-
-### 🧹 Cleanup & Optimization
-
-**Memory Management:**
-
-- **Removed Hardcoded .bmad Folders**: Cleaned up demo content to use configurable paths
-- **Sidecar File Cleanup**: Removed old .bmad-user-memory folders from wellness modules
-- **Example Content Organization**: Better organization of example-custom-content directory
-
-**Installer Improvements:**
-
-- **Debug Output Enhancement**: Added informative debug output when installer encounters errors
-- **Custom Module Caching**: Improved caching mechanism for custom module installations
-- **Consistent Behavior**: All modules now behave consistently regardless of custom or core status
-
-### 📊 Statistics
-
-- **77 files changed** with 2,852 additions and 607 deletions
-- **15 commits** since alpha.14
-
-### ⚠️ Breaking Changes
-
-1. **module.yaml Configuration**: All modules must now use `module.yaml` instead of `_module-installer/install-config.yaml`
-   - Core modules updated automatically
-   - Custom modules will need to rename their configuration file
-   - Module builder templates generate new format
-
-### 📦 New Dependencies
-
-- No new dependencies added in this release
-
----
-
-## [6.0.0-alpha.14]
-
-**Release: December 7, 2025**
-
-### 🔧 Installation & Configuration Revolution
-
-**Custom Module Installation Overhaul:**
-
-- **Simple custom.yaml Installation**: Custom agents and workflows can now be installed with a single YAML file
-- **IDE Configuration Preservation**: Upgrades will no longer delete custom modules, agents, and workflows from IDE configuration
-- **Removed Legacy agent-install Command**: Streamlined installation process (BREAKING CHANGE)
-- **Sidecar File Retention**: Custom sidecar files are preserved during updates
-- **Flexible Agent Sidecar Locations**: Fully configurable via config options instead of hardcoded paths
-
-**Module Discovery System Transformation:**
-
-- **Recursive Agent Discovery**: Deep scanning for agents across entire project structure
-- **Enhanced Manifest Generation**: Comprehensive scanning of all installed modules
-- **Nested Agent Support**: Fixed nested agents appearing in CLI commands
-- **Module Reinstall Fix**: Prevented modules from showing as obsolete during reinstall
-
-### 🏗️ Advanced Builder Features
-
-**Workflow Builder Evolution:**
-
-- **Continuable Workflows**: Create workflows with sophisticated branching and continuation logic
-- **Template LOD Options**: Level of Detail output options for flexible workflow generation
-- **Step-Based Architecture**: Complete conversion to granular step-file system
-- **Enhanced Creation Process**: Improved workflow creation with better template handling
-
-**Module Builder Revolution:**
-
-- **11-Step Module Creation**: Comprehensive step-by-step module generation process
-- **Production-Ready Templates**: Complete templates for agents, installers, and workflow plans
-- **Built-in Validation System**: Ensures module quality and BMad Core compliance
-- **Professional Documentation**: Auto-generated module documentation and structure
-
-### 🚀 BMad Method (BMM) Enhancements
-
-**Workflow Improvements:**
-
-- **Brownfield PRD Support**: Enhanced PRD workflow for existing project integration
-- **Sprint Status Command**: New workflow for tracking development progress
-- **Step-Based Format**: Improved continue functionality across all workflows
-- **Quick-Spec-Flow Documentation**: Rapid development specification flows
-
-**Documentation Revolution:**
-
-- **Comprehensive Troubleshooting Guide**: 680-line detailed troubleshooting documentation
-- **Quality Check Integration**: Added markdownlint-cli2 for markdown quality assurance
-- **Enhanced Test Architecture**: Improved CI/CD templates and testing workflows
-
-### 🌟 New Features & Integrations
-
-**Kiro-Cli Installer:**
-
-- **Intelligent Routing**: Smart routing to quick-dev workflow
-- **BMad Core Compliance**: Full compliance with BMad standards
-
-**Discord Notifications:**
-
-- **Compact Format**: Streamlined plain-text notifications
-- **Bug Fixes**: Resolved notification delivery issues
-
-**Example Mental Wellness Module (MWM):**
-
-- **Complete Module Example**: Demonstrates advanced module patterns
-- **Multiple Agents**: CBT Coach, Crisis Navigator, Meditation Guide, Wellness Companion
-- **Workflow Showcase**: Crisis support, daily check-in, meditation, journaling workflows
-
-### 🐛 Bug Fixes & Optimizations
-
-- Fixed version reading from package.json instead of hardcoded fallback
-- Removed hardcoded years from WebSearch queries
-- Removed broken build caching mechanism
-- Fixed hardcoded '.bmad' prefix from files-manifest.csv paths
-- Enhanced TTS injection summary with tracking and documentation
-- Fixed CI nvmrc configuration issues
-
-### 📊 Statistics
-
-- **335 files changed** with 17,161 additions and 8,204 deletions
-- **46 commits** since alpha.13
-
-### ⚠️ Breaking Changes
-
-1. **Removed agent-install Command**: Migrate to new custom.yaml installation system
-2. **Agent Sidecar Configuration**: Now requires explicit config instead of hardcoded paths
-
-### 📦 New Dependencies
-
-- `markdownlint-cli2: ^0.19.1` - Professional markdown linting
-
----
-
-## [6.0.0-alpha.13]
-
-**Release: November 30, 2025**
-
-### 🏗️ Revolutionary Workflow Architecture
-
-- **Step-File System**: Complete conversion to granular step-file architecture with dynamic menu generation
-- **Phase 4 Transformation**: Simplified architecture with sprint planning integration (Jira, Linear, Trello)
-- **Performance Improvements**: Eliminated time-based estimates, reduced file loading times
-- **Legacy Cleanup**: Removed all deprecated workflows for cleaner system
-
-### 🤖 Agent System Revolution
-
-- **Universal Custom Agent Support**: Extended to ALL IDEs including Antigravity and Rovo Dev
-- **Agent Creation Workflow**: Enhanced with better documentation and parameter clarity
-- **Multi-Source Discovery**: Agents now check multiple source locations for better discovery
-- **GitHub Migration**: Integration moved from chatmodes to agents folder
-
-### 🧪 Testing Infrastructure
-
-- **Playwright Utils Integration**: @seontechnologies/playwright-utils across all testing workflows
-- **TTS Injection System**: Complete text-to-speech integration for voice feedback
-- **Web Bundle Test Support**: Enabled web bundles for test environments
-
-### ⚠️ Breaking Changes
-
-1. **Legacy Workflows Removed**: Migrate to new stepwise sharded workflows
-2. **Phase 4 Restructured**: Update automation expecting old Phase 4 structure
-3. **Agent Compilation Required**: Custom agents must use new creation workflow
-
-## [6.0.0-alpha.12]
-
-**Release: November 19, 2025**
-
-### 🐛 Bug Fixes
-
-- Added missing `yaml` dependency to fix `MODULE_NOT_FOUND` error when running `npx bmad-method install`
-
-## [6.0.0-alpha.11]
-
-**Release: November 18, 2025**
-
-### 🚀 Agent Installation Revolution
-
-- **bmad agent-install CLI**: Interactive agent installation with persona customization
-- **4 Reference Agents**: commit-poet, journal-keeper, security-engineer, trend-analyst
-- **Agent Compilation Engine**: YAML → XML with smart handler injection
-- **60 Communication Presets**: Pure communication styles for agent personas
-
-### 📚 BMB Agent Builder Enhancement
-
-- **Complete Documentation Suite**: 7 new guides for agent architecture and creation
-- **Expert Agent Sidecar Support**: Multi-file agents with templates and knowledge bases
-- **Unified Validation**: 160-line checklist shared across workflows
-- **BMM Agent Voices**: All 9 agents enhanced with distinct communication styles
-
-### 🎯 Workflow Architecture Change
-
-- **Epic Creation Moved**: Now in Phase 3 after Architecture for technical context
-- **Excalidraw Distribution**: Diagram capabilities moved to role-appropriate agents
-- **Google Antigravity IDE**: New installer with flattened file naming
-
-### ⚠️ Breaking Changes
-
-1. **Frame Expert Retired**: Use role-appropriate agents for diagrams
-2. **Agent Installation**: New bmad agent-install command replaces manual installation
-3. **Epic Creation Phase**: Moved from Phase 2 to Phase 3
-
-## [6.0.0-alpha.10]
-
-**Release: November 16, 2025**
-
-- **Epics After Architecture**: Major milestone - technically-informed user stories created post-architecture
-- **Frame Expert Agent**: New Excalidraw specialist with 4 diagram workflows
-- **Time Estimate Prohibition**: Warnings across 33 workflows acknowledging AI's impact on development speed
-- **Platform-Specific Commands**: ide-only/web-only fields filter menu items by environment
-- **Agent Customization**: Enhanced memory/prompts merging via \*.customize.yaml files
-
-## [6.0.0-alpha.9]
-
-**Release: November 12, 2025**
-
-- **Intelligent File Discovery**: discover_inputs with FULL_LOAD, SELECTIVE_LOAD, INDEX_GUIDED strategies
-- **3-Track System**: Simplified from 5 levels to 3 intuitive tracks
-- **Web Bundles Guide**: Comprehensive documentation with 60-80% cost savings strategies
-- **Unified Output Structure**: Eliminated .ephemeral/ folders - single configurable output folder
-- **BMGD Phase 4**: Added 10 game development workflows with BMM patterns
-
-## [6.0.0-alpha.8]
-
-**Release: November 9, 2025**
-
-- **Configurable Installation**: Custom directories with .bmad hidden folder default
-- **Optimized Agent Loading**: CLI loads from installed files, eliminating duplication
-- **Party Mode Everywhere**: All web bundles include multi-agent collaboration
-- **Phase 4 Artifact Separation**: Stories, code reviews, sprint plans configurable outside docs
-- **Expanded Web Bundles**: All BMM, BMGD, CIS agents bundled with elicitation integration
-
-## [6.0.0-alpha.7]
-
-**Release: November 7, 2025**
-
-- **Workflow Vendoring**: Web bundler performs automatic cross-module dependency vendoring
-- **BMGD Module Extraction**: Game development split into standalone 4-phase structure
-- **Enhanced Dependency Resolution**: Better handling of web_bundle: false workflows
-- **Advanced Elicitation Fix**: Added missing CSV files to workflow bundles
-- **Claude Code Fix**: Resolved README slash command installation regression
-
-## [6.0.0-alpha.6]
-
-**Release: November 4, 2025**
-
-- **Critical Installer Fixes**: Fixed manifestPath error and option display issues
-- **Conditional Docs Installation**: Optional documentation to reduce production footprint
-- **Improved Installer UX**: Better formatting with descriptive labels and clearer feedback
-- **Issue Tracker Cleanup**: Closed 54 legacy v4 issues for focused v6 development
-- **Contributing Updates**: Removed references to non-existent branches
-
-## [6.0.0-alpha.5]
-
-**Release: November 4, 2025**
-
-- **3-Track Scale System**: Simplified from 5 levels to 3 intuitive preference-driven tracks
-- **Elicitation Modernization**: Replaced legacy XML tags with explicit invoke-task pattern
-- **PM/UX Evolution**: Added November 2025 industry research on AI Agent PMs
-- **Brownfield Reality Check**: Rewrote Phase 0 with 4 real-world scenarios
-- **Documentation Accuracy**: All agent capabilities now match YAML source of truth
-
-## [6.0.0-alpha.4]
-
-**Release: November 2, 2025**
-
-- **Documentation Hub**: Created 18 comprehensive guides (7000+ lines) with professional standards
-- **Paige Agent**: New technical documentation specialist across all BMM phases
-- **Quick Spec Flow**: Intelligent Level 0-1 planning with auto-stack detection
-- **Universal Shard-Doc**: Split large markdown documents with dual-strategy loading
-- **Intent-Driven Planning**: PRD and Product Brief transformed from template-filling to conversation
-
-## [6.0.0-alpha.3]
-
-**Release: October 2025**
-
-- **Codex Installer**: Custom prompts in `.codex/prompts/` directory structure
-- **Bug Fixes**: Various installer and workflow improvements
-- **Documentation**: Initial documentation structure established
-
-## [6.0.0-alpha.0]
-
-**Release: September 28, 2025**
-
-- **Lean Core**: Simple common tasks and agents (bmad-web-orchestrator, bmad-master)
-- **BMad Method (BMM)**: Complete scale-adaptive rewrite supporting projects from small enhancements to massive undertakings
-- **BoMB**: BMad Builder for creating and converting modules, workflows, and agents
-- **CIS**: Creative Intelligence Suite for ideation and creative workflows
-- **Game Development**: Full subclass of game-specific development patterns**Note**: Version 5.0.0 was skipped due to NPX registry issues that corrupted the version. Development continues with v6.0.0-alpha.0.
-
-## [v4.43.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v4.43.0)
-
-**Release: August-September 2025 (v4.31.0 - v4.43.1)**
-
-Focus on stability, ecosystem growth, and professional tooling.
-
-### Major Integrations
-
-- **Codex CLI & Web**: Full Codex integration with web and CLI modes
-- **Auggie CLI**: Augment Code integration
-- **iFlow CLI**: iFlow support in installer
-- **Gemini CLI Custom Commands**: Enhanced Gemini CLI capabilities
-
-### Expansion Packs
-
-- **Godot Game Development**: Complete game dev workflow
-- **Creative Writing**: Professional writing agent system
-- **Agent System Templates**: Template expansion pack (Part 2)
-
-### Advanced Features
-
-- **AGENTS.md Generation**: Auto-generated agent documentation
-- **NPM Script Injection**: Automatic package.json updates
-- **File Exclusion**: `.bmad-flattenignore` support for flattener
-- **JSON-only Integration**: Compact integration mode
-
-### Quality & Stability
-
-- **PR Validation Workflow**: Automated contribution checks
-- **Fork-Friendly CI/CD**: Opt-in mechanism for forks
-- **Code Formatting**: Prettier integration with pre-commit hooks
-- **Update Checker**: `npx bmad-method update-check` command
-
-### Flattener Improvements
-
-- Detailed statistics with emoji-enhanced `.stats.md`
-- Improved project root detection
-- Modular component architecture
-- Binary directory exclusions (venv, node_modules, etc.)
-
-### Documentation & Community
-
-- Brownfield document naming consistency fixes
-- Architecture template improvements
-- Trademark and licensing clarity
-- Contributing guidelines refinement
-
-### Developer Experience
-
-- Version synchronization scripts
-- Manual release workflow enhancements
-- Automatic release notes generation
-- Changelog file path configuration
-
-[View v4.43.1 tag](https://github.com/bmad-code-org/BMAD-METHOD/tree/v4.43.1)
-
-## [v4.30.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v4.30.0)
-
-**Release: July 2025 (v4.21.0 - v4.30.4)**
-
-Introduction of advanced IDE integrations and command systems.
-
-### Claude Code Integration
-
-- **Slash Commands**: Native Claude Code slash command support for agents
-- **Task Commands**: Direct task invocation via slash commands
-- **BMad Subdirectory**: Organized command structure
-- **Nested Organization**: Clean command hierarchy
-
-### Agent Enhancements
-
-- BMad-master knowledge base loading
-- Improved brainstorming facilitation
-- Better agent task following with cost-saving model combinations
-- Direct commands in agent definitions
-
-### Installer Improvements
-
-- Memory-efficient processing
-- Clear multi-select IDE prompts
-- GitHub Copilot support with improved UX
-- ASCII logo (because why not)
-
-### Platform Support
-
-- Windows compatibility improvements (regex fixes, newline handling)
-- Roo modes configuration
-- Support for multiple CLI tools simultaneously
-
-### Expansion Ecosystem
-
-- 2D Unity Game Development expansion pack
-- Improved expansion pack documentation
-- Better isolated expansion pack installations
-
-[View v4.30.4 tag](https://github.com/bmad-code-org/BMAD-METHOD/tree/v4.30.4)
-
-## [v4.20.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v4.20.0)
-
-**Release: June 2025 (v4.11.0 - v4.20.0)**
-
-Major focus on documentation quality and expanding QA agent capabilities.
-
-### Documentation Overhaul
-
-- **Workflow Diagrams**: Visual explanations of planning and development cycles
-- **QA Role Expansion**: QA agent transformed into senior code reviewer
-- **User Guide Refresh**: Complete rewrite with clearer explanations
-- **Contributing Guidelines**: Clarified principles and contribution process
-
-### QA Agent Transformation
-
-- Elevated from simple tester to senior developer/code reviewer
-- Code quality analysis and architectural feedback
-- Pre-implementation review capabilities
-- Integration with dev cycle for quality gates
-
-### IDE Ecosystem Growth
-
-- **Cline IDE Support**: Added configuration for Cline
-- **Gemini CLI Integration**: Native Gemini CLI support
-- **Expansion Pack Installation**: Automated expansion agent setup across IDEs
-
-### New Capabilities
-
-- Markdown-tree integration for document sharding
-- Quality gates to prevent task completion with failures
-- Enhanced brownfield workflow documentation
-- Team-based agent bundling improvements
-
-### Developer Tools
-
-- Better expansion pack isolation
-- Automatic rule generation for all supported IDEs
-- Common files moved to shared locations
-- Hardcoded dependencies removed from installer
-
-[View v4.20.0 tag](https://github.com/bmad-code-org/BMAD-METHOD/tree/v4.20.0)
-
-## [v4.10.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v4.10.0)
-
-**Release: June 2025 (v4.3.0 - v4.10.3)**
-
-This release focused on making BMAD more configurable and adaptable to different project structures.
-
-### Configuration System
-
-- **Optional Core Config**: Document sharding and core configuration made optional
-- **Flexible File Resolution**: Support for non-standard document structures
-- **Debug Logging**: Configurable debug mode for agent troubleshooting
-- **Fast Update Mode**: Quick updates without breaking customizations
-
-### Agent Improvements
-
-- Clearer file resolution instructions for all agents
-- Fuzzy task resolution for better agent autonomy
-- Web orchestrator knowledge base expansion
-- Better handling of deviant PRD/Architecture structures
-
-### Installation Enhancements
-
-- V4 early detection for improved update flow
-- Prevented double installation during updates
-- Better handling of YAML manifest files
-- Expansion pack dependencies properly included
-
-### Bug Fixes
-
-- SM agent file resolution issues
-- Installer upgrade path corrections
-- Bundle build improvements
-- Template formatting fixes
-
-[View v4.10.3 tag](https://github.com/bmad-code-org/BMAD-METHOD/tree/v4.10.3)
-
-## [v4.0.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v4.0.0)
-
-**Release: June 20, 2025 (v4.0.0 - v4.2.0)**
-
-Version 4 represented a complete architectural overhaul, transforming BMAD from a collection of prompts into a professional, distributable framework.
-
-### Framework Transformation
-
-- **NPM Package**: Professional distribution and simple installation via `npx bmad-method install`
-- **Modular Architecture**: Move to `.bmad-core` hidden folder structure
-- **Multi-IDE Support**: Unified support for Claude Code, Cursor, Roo, Windsurf, and many more
-- **Schema Standardization**: YAML-based agent and team definitions
-- **Automated Installation**: One-command setup with upgrade detection
-
-### Agent System Overhaul
-
-- Agent team workflows (fullstack, no-ui, all agents)
-- Web bundle generation for platform-agnostic deployment
-- Task-based architecture (separate task definitions from agents)
-- IDE-specific agent activation (slash commands for Claude Code, rules for Cursor, etc.)
-
-### New Capabilities
-
-- Brownfield project support (existing codebases)
-- Greenfield project workflows (new projects)
-- Expansion pack architecture for domain specialization
-- Document sharding for better context management
-- Automatic semantic versioning and releases
-
-### Developer Experience
-
-- Automatic upgrade path from v3 to v4
-- Backup creation for user customizations
-- VSCode settings and markdown linting
-- Comprehensive documentation restructure
-
-[View v4.2.0 tag](https://github.com/bmad-code-org/BMAD-METHOD/tree/v4.2.0)
-
-## [v3.0.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v3.0.0)
-
-**Release: May 20, 2025**
-
-Version 3 introduced the revolutionary orchestrator concept, creating a unified agent experience.
-
-### Major Features
-
-- **BMad Orchestrator**: Uber-agent that orchestrates all specialized agents
-- **Web-First Approach**: Streamlined web setup with pre-compiled agent bundles
-- **Simplified Onboarding**: Complete setup in minutes with clear quick-start guide
-- **Build System**: Scripts to compile web agents from modular components
-
-### Architecture Changes
-
-- Consolidated agent system with centralized orchestration
-- Web build sample folder with ready-to-deploy configurations
-- Improved documentation structure with visual setup guides
-- Better separation between web and IDE workflows
-
-### New Capabilities
-
-- Single agent interface (`/help` command system)
-- Brainstorming and ideation support
-- Integrated method explanation within the agent itself
-- Cross-platform consistency (Gemini Gems, Custom GPTs)
-
-[View V3 Branch](https://github.com/bmad-code-org/BMAD-METHOD/tree/V3)
-
-## [v2.0.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v2.0.0)
-
-**Release: April 17, 2025**
-
-Version 2 addressed the major shortcomings of V1 by introducing separation of concerns and quality validation mechanisms.
-
-### Major Improvements
-
-- **Template Separation**: Templates decoupled from agent definitions for greater flexibility
-- **Quality Checklists**: Advanced elicitation checklists to validate document quality
-- **Web Agent Discovery**: Recognition of Gemini Gems and Custom GPTs power for structured planning
-- **Granular Web Agents**: Simplified, clearly-defined agent roles optimized for web platforms
-- **Installer**: A project installer that copied the correct files to a folder at the destination
-
-### Key Features
-
-- Separated template files from agent personas
-- Introduced forced validation rounds through checklists
-- Cost-effective structured planning workflow using web platforms
-- Self-contained agent personas with external template references
-
-### Known Issues
-
-- Duplicate templates/checklists for web vs IDE versions
-- Manual export/import workflow between agents
-- Creating each web agent separately was tedious
-
-[View V2 Branch](https://github.com/bmad-code-org/BMAD-METHOD/tree/V2)
-
-## [v1.0.0](https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v1.0.0)
-
-**Initial Release: April 6, 2025**
-
-The original BMAD Method was a tech demo showcasing how different custom agile personas could be used to build out artifacts for planning and executing complex applications from scratch. This initial version established the foundation of the AI-driven agile development approach.
-
-### Key Features
-
-- Introduction of specialized AI agent personas (PM, Architect, Developer, etc.)
-- Template-based document generation for planning artifacts
-- Emphasis on planning MVP scope with sufficient detail to guide developer agents
-- Hard-coded custom mode prompts integrated directly into agent configurations
-- The OG of Context Engineering in a structured way
-
-### Limitations
-
-- Limited customization options
-- Web usage was complicated and not well-documented
-- Rigid scope and purpose with templates coupled to agents
-- Not optimized for IDE integration
-
-[View V1 Branch](https://github.com/bmad-code-org/BMAD-METHOD/tree/V1)
-
-## Installation
-
-```bash
-npx bmad-method
-```
-
-For detailed release notes, see the [GitHub releases page](https://github.com/bmad-code-org/BMAD-METHOD/releases).

CONTRIBUTING.md

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

LICENSE

@@ -1,26 +0,0 @@
-MIT License
-
-Copyright (c) 2025 BMad Code, LLC
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-TRADEMARK NOTICE:
-BMAD™, 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

@@ -1,217 +1,7 @@
-# BMad Method & BMad Core
+# BMad Method V1
 
-[![Stable Version](https://img.shields.io/npm/v/bmad-method?color=blue&label=stable)](https://www.npmjs.com/package/bmad-method)
-[![Alpha Version](https://img.shields.io/npm/v/bmad-method/alpha?color=orange&label=alpha)](https://www.npmjs.com/package/bmad-method)
-[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
-[![Node.js Version](https://img.shields.io/badge/node-%3E%3D20.0.0-brightgreen)](https://nodejs.org)
-[![Discord](https://img.shields.io/badge/Discord-Join%20Community-7289da?logo=discord&logoColor=white)](https://discord.gg/gk8jAdXWmj)
+The original version was a simple tech demo of showing how different custom agile personas could be used to build out the artifacts to have AI Agents plan and execute on building complex applications from scratch, with an emphasis on planning enough for an MVP to while filling in enough details to keep developer agents on the rails.
 
-## AI-Driven Agile Development That Scales From Bug Fixes to Enterprise
+Its simplicity was amazing, but it did not include a lot of customization - and using this in the web was more of an after thought that came later with V2. It was possible but complicated and not clearly communicated with V1.
 
-**Build More, Architect Dreams** (BMAD) with **21 specialized AI agents** across 4 official modules, and **50+ guided workflows** that adapt to your project's complexity—from quick bug fixes to enterprise platforms, and new step file workflows that allow for incredibly long workflows to stay on the rails longer than ever before!
-
-Additionally - when we say 'Build More, Architect Dreams' - we mean it! The BMad Builder has landed, and now as of Alpha.15 is fully supported in the installation flow via NPX - custom stand along agents, workflows and the modules of your dreams! The community forge will soon open, endless possibility awaits!
-
-> **🚀 v6 is a MASSIVE upgrade from v4!** Complete architectural overhaul, scale-adaptive intelligence, visual workflows, and the powerful BMad Core framework. v4 users: this changes everything. [See what's new →](#whats-new-in-v6)
-
-> **📌 v6 Alpha Status:** Near-beta quality with vastly improved stability. Documentation is being finalized. New videos coming soon to [BMadCode YouTube](https://www.youtube.com/@BMadCode).
-
-## 🎯 Why BMad Method?
-
-Unlike generic AI coding assistants, BMad Method provides **structured, battle-tested workflows** powered by specialized agents who understand agile development. Each agent has deep domain expertise—from product management to architecture to testing—working together seamlessly.
-
-**✨ Key Benefits:**
-
-- **Scale-Adaptive Intelligence** - Automatically adjusts planning depth from bug fixes to enterprise systems
-- **Complete Development Lifecycle** - Analysis → Planning → Architecture → Implementation
-- **Specialized Expertise** - 19 agents with specific roles (PM, Architect, Developer, UX Designer, etc.)
-- **Proven Methodologies** - Built on agile best practices with AI amplification
-- **IDE Integration** - Works with Claude Code, Cursor, Windsurf, VS Code
-
-## 🏗️ The Power of BMad Core
-
-**BMad Method** is actually a sophisticated module built on top of **BMad Core** (**C**ollaboration **O**ptimized **R**eflection **E**ngine). This revolutionary architecture means:
-
-- **BMad Core** provides the universal framework for human-AI collaboration
-- **BMad Method** leverages Core to deliver agile development workflows
-- **BMad Builder** lets YOU create custom modules as powerful as BMad Method itself
-
-With **BMad Builder**, you can architect both simple agents and vastly complex domain-specific modules (legal, medical, finance, education, creative) that will soon be sharable in an **official community marketplace**. Imagine building and sharing your own specialized AI team!
-
-## 📊 See It In Action
-
-<p align="center">
-  <img src="./src/modules/bmm/docs/images/workflow-method-greenfield.svg" alt="BMad Method Workflow" width="100%">
-</p>
-
-<p align="center">
-  <em>Complete BMad Method workflow showing all phases, agents, and decision points</em>
-</p>
-
-## 🚀 Get Started in 3 Steps
-
-### 1. Install BMad Method
-
-```bash
-# Install v6 Alpha (recommended)
-npx bmad-method@alpha install
-
-# Or stable v4 for production
-npx bmad-method install
-```
-
-### 2. Initialize Your Project
-
-Load any agent in your IDE and run:
-
-```
-*workflow-init
-```
-
-This analyzes your project and recommends the right workflow track.
-
-### 3. Choose Your Track
-
-BMad Method adapts to your needs with three intelligent tracks:
-
-| Track              | Use For                   | Planning                | Time to Start |
-| ------------------ | ------------------------- | ----------------------- | ------------- |
-| **⚡ Quick Flow**  | Bug fixes, small features | Tech spec only          | < 5 minutes   |
-| **📋 BMad Method** | Products, platforms       | PRD + Architecture + UX | < 15 minutes  |
-| **🏢 Enterprise**  | Compliance, scale         | Full governance suite   | < 30 minutes  |
-
-> **Not sure?** Run `*workflow-init` and let BMad analyze your project goal.
-
-## 🔄 How It Works: 4-Phase Methodology
-
-BMad Method guides you through a proven development lifecycle:
-
-1. **📊 Analysis** (Optional) - Brainstorm, research, and explore solutions
-2. **📝 Planning** - Create PRDs, tech specs, or game design documents
-3. **🏗️ Solutioning** - Design architecture, UX, and technical approach
-4. **⚡ Implementation** - Story-driven development with continuous validation
-
-Each phase has specialized workflows and agents working together to deliver exceptional results.
-
-## 🤖 Meet Your Team
-
-**12 Specialized Agents** working in concert:
-
-| Development | Architecture   | Product       | Leadership     |
-| ----------- | -------------- | ------------- | -------------- |
-| Developer   | Architect      | PM            | Scrum Master   |
-| UX Designer | Test Architect | Analyst       | BMad Master    |
-| Tech Writer | Game Architect | Game Designer | Game Developer |
-
-**Test Architect** integrates with `@seontechnologies/playwright-utils` for production-ready fixture-based utilities.
-
-Each agent brings deep expertise and can be customized to match your team's style.
-
-## 📦 What's Included
-
-### Core Modules
-
-- **BMad Method (BMM)** - Complete agile development framework
-  - 12 specialized agents
-  - 34 workflows across 4 phases
-  - Scale-adaptive planning
-  - [→ Documentation Hub](./src/modules/bmm/docs/README.md)
-
-- **BMad Builder (BMB)** - Create custom agents and workflows
-  - Build anything from simple agents to complex modules
-  - Create domain-specific solutions (legal, medical, finance, education)
-  - 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/README.md)
-
-### Key Features
-
-- **🎨 Customizable Agents** - Modify personalities, expertise, and communication styles
-- **🌐 Multi-Language Support** - Separate settings for communication and code output
-- **📄 Document Sharding** - 90% token savings for large projects
-- **🔄 Update-Safe** - Your customizations persist through updates
-- **🚀 Web Bundles** - Use in ChatGPT, Claude Projects, or Gemini Gems
-
-## 📚 Documentation
-
-### Quick Links
-
-- **[Quick Start Guide](./src/modules/bmm/docs/quick-start.md)** - 15-minute introduction
-- **[Complete BMM Documentation](./src/modules/bmm/docs/README.md)** - All guides and references
-- **[Agent Customization](./docs/agent-customization-guide.md)** - Personalize your agents
-- **[All Documentation](./docs/index.md)** - Complete documentation index
-
-### For v4 Users
-
-- **[v4 Documentation](https://github.com/bmad-code-org/BMAD-METHOD/tree/V4)**
-- **[v4 to v6 Upgrade Guide](./docs/v4-to-v6-upgrade.md)**
-
-## 💬 Community & Support
-
-- **[Discord Community](https://discord.gg/gk8jAdXWmj)** - Get help, share projects
-- **[GitHub Issues](https://github.com/bmad-code-org/BMAD-METHOD/issues)** - Report bugs, request features
-- **[YouTube Channel](https://www.youtube.com/@BMadCode)** - Video tutorials and demos
-- **[Web Bundles](https://bmad-code-org.github.io/bmad-bundles/)** - Pre-built agent bundles
-- **[Code of Conduct](.github/CODE_OF_CONDUCT.md)** - Community guidelines
-
-## 🛠️ Development
-
-For contributors working on the BMad codebase:
-
-```bash
-# Run all quality checks
-npm test
-
-# Development commands
-npm run lint:fix      # Fix code style
-npm run format:fix    # Auto-format code
-npm run bundle        # Build web bundles
-```
-
-See [CONTRIBUTING.md](CONTRIBUTING.md) for full development guidelines.
-
-## What's New in v6
-
-**v6 represents a complete architectural revolution from v4:**
-
-### 🚀 Major Upgrades
-
-- **BMad Core Framework** - Modular architecture enabling custom domain solutions
-- **Scale-Adaptive Intelligence** - Automatic adjustment from bug fixes to enterprise
-- **Visual Workflows** - Beautiful SVG diagrams showing complete methodology
-- **BMad Builder Module** - Create and share your own AI agent teams
-- **50+ Workflows** - Up from 20 in v4, covering every development scenario
-- **19 Specialized Agents** - Enhanced with customizable personalities and expertise
-- **Update-Safe Customization** - Your configs persist through all updates
-- **Web Bundles** - Use agents in ChatGPT, Claude, and Gemini
-- **Multi-Language Support** - Separate settings for communication and code
-- **Document Sharding** - 90% token savings for large projects
-
-### 🔄 For v4 Users
-
-- **[Comprehensive Upgrade Guide](./docs/v4-to-v6-upgrade.md)** - Step-by-step migration
-- **[v4 Documentation Archive](https://github.com/bmad-code-org/BMAD-METHOD/tree/V4)** - Legacy reference
-- Backwards compatibility where possible
-- Smooth migration path with installer detection
-
-## 📄 License
-
-MIT License - See [LICENSE](LICENSE) for details.
-
-**Trademarks:** BMAD™ and BMAD-METHOD™ are trademarks of BMad Code, LLC.
-
----
-
-<p align="center">
-  <a href="https://github.com/bmad-code-org/BMAD-METHOD/graphs/contributors">
-    <img src="https://contrib.rocks/image?repo=bmad-code-org/BMAD-METHOD" alt="Contributors">
-  </a>
-</p>
-
-<p align="center">
-  <sub>Built with ❤️ for the human-AI collaboration community</sub>
-</p>
+This initial version also had each custom mode prompt hard coded to the template that would all be part of the agent custom mode. This would not have worked well with many IDEs, and was very rigid in scope and purpose.

ai/templates/architecture-template.md

@@ -0,0 +1,187 @@
+# Architecture for {PRD Title}
+
+Status: { Draft | Approved }
+
+## Technical Summary
+
+{ Short 1-2 paragraph }
+
+## Technology Table
+
+Table listing choices for languages, libraries, infra, cloud resources, etc... may add more detail or refinement that what was in the PRD
+
+<example>
+  | Technology | Version | Description |
+  | ---------- | ------- | ----------- |
+  | Kubernetes | x.y.z | Container orchestration platform for microservices deployment |
+  | Apache Kafka | x.y.z | Event streaming platform for real-time data ingestion |
+  | TimescaleDB | x.y.z | Time-series database for sensor data storage |
+  | Go | x.y.z | Primary language for data processing services |
+  | GoRilla Mux | x.y.z | REST API Framework |
+  | Python | x.y.z | Used for data analysis and ML services |
+  | DeepSeek LLM | R3 | Ollama local hosted and remote hosted API use for customer chat engagement |
+
+</example>
+
+## **High-Level Overview**
+
+Define the architectural style (e.g., Monolith, Microservices, Serverless) and justify the choice based on the PRD. Include a high-level diagram (e.g., C4 Context or Container level using Mermaid syntax).
+
+### **Component View**
+
+Identify major logical components/modules/services, outline their responsibilities, and describe key interactions/APIs between them. Include diagrams if helpful (e.g., C4 Container/Component or class diagrams using Mermaid syntax).
+
+## Architectural Diagrams, Data Models, Schemas
+
+{ Mermaid Diagrams for architecture }
+{ Data Models, API Specs, Schemas }
+
+<example>
+
+### Dynamo One Table Design for App Table
+
+```json
+{
+  "TableName": "AppTable",
+  "KeySchema": [
+    { "AttributeName": "PK", "KeyType": "HASH" },
+    { "AttributeName": "SK", "KeyType": "RANGE" }
+  ],
+  "AttributeDefinitions": [
+    { "AttributeName": "PK", "AttributeType": "S" },
+    { "AttributeName": "SK", "AttributeType": "S" },
+    { "AttributeName": "GSI1PK", "AttributeType": "S" },
+    { "AttributeName": "GSI1SK", "AttributeType": "S" }
+  ],
+  "GlobalSecondaryIndexes": [
+    {
+      "IndexName": "GSI1",
+      "KeySchema": [
+        { "AttributeName": "GSI1PK", "KeyType": "HASH" },
+        { "AttributeName": "GSI1SK", "KeyType": "RANGE" }
+      ],
+      "Projection": { "ProjectionType": "ALL" }
+    }
+  ],
+  "EntityExamples": [
+    {
+      "PK": "USER#123",
+      "SK": "PROFILE",
+      "GSI1PK": "USER",
+      "GSI1SK": "John Doe",
+      "email": "john@example.com",
+      "createdAt": "2023-05-01T12:00:00Z"
+    },
+    {
+      "PK": "USER#123",
+      "SK": "ORDER#456",
+      "GSI1PK": "ORDER",
+      "GSI1SK": "2023-05-15T09:30:00Z",
+      "total": 129.99,
+      "status": "shipped"
+    },
+    {
+      "PK": "PRODUCT#789",
+      "SK": "DETAILS",
+      "GSI1PK": "PRODUCT",
+      "GSI1SK": "Wireless Headphones",
+      "price": 79.99,
+      "inventory": 42
+    }
+  ]
+}
+```
+
+### Sequence Diagram for Recording Alerts
+
+```mermaid
+sequenceDiagram
+    participant Sensor
+    participant API
+    participant ProcessingService
+    participant Database
+    participant NotificationService
+
+    Sensor->>API: Send sensor reading
+    API->>ProcessingService: Forward reading data
+    ProcessingService->>ProcessingService: Validate & analyze data
+    alt Is threshold exceeded
+        ProcessingService->>Database: Store alert
+        ProcessingService->>NotificationService: Trigger notification
+        NotificationService->>NotificationService: Format alert message
+        NotificationService-->>API: Send notification status
+    else Normal reading
+        ProcessingService->>Database: Store reading only
+    end
+    Database-->>ProcessingService: Confirm storage
+    ProcessingService-->>API: Return processing result
+    API-->>Sensor: Send acknowledgement
+```
+
+### Sensor Reading Schema
+
+```json
+{
+  "sensor_id": "string",
+  "timestamp": "datetime",
+  "readings": {
+    "temperature": "float",
+    "pressure": "float",
+    "humidity": "float"
+  },
+  "metadata": {
+    "location": "string",
+    "calibration_date": "datetime"
+  }
+}
+```
+
+</example>
+
+## Project Structure
+
+{ Diagram the folder and file organization structure along with descriptions }
+
+```
+├ /src
+├── /services
+│   ├── /gateway        # Sensor data ingestion
+│   ├── /processor      # Data processing and validation
+│   ├── /analytics      # Data analysis and ML
+│   └── /notifier       # Alert and notification system
+├── /deploy
+│   ├── /kubernetes     # K8s manifests
+│   └── /terraform      # Infrastructure as Code
+└── /docs
+    ├── /api           # API documentation
+    └── /schemas       # Data schemas
+```
+
+## Testing Requirements and Framework
+
+### Patterns and Standards (Opinionated & Specific)
+
+    - **Architectural/Design Patterns:** Mandate specific patterns to be used (e.g., Repository Pattern for data access, MVC/MVVM for structure, CQRS if applicable). .
+
+    - **API Design Standards:** Define the API style (e.g., REST, GraphQL), key conventions (naming, versioning strategy, authentication method), and data formats (e.g., JSON).
+
+    - **Coding Standards:** Specify the mandatory style guide (e.g., Airbnb JavaScript Style Guide, PEP 8), code formatter (e.g., Prettier), and linter (e.g., ESLint with specific config). Define mandatory naming conventions (files, variables, classes). Define test file location conventions.
+
+    - **Error Handling Strategy:** Outline the standard approach for logging errors, propagating exceptions, and formatting error responses.
+
+### Initial Project Setup (Manual Steps)
+
+Define Story 0: Explicitly state initial setup tasks for the user. Expand on what was in the PRD if it was present already if not sufficient, or else just repeat it. Examples:
+
+- Framework CLI Generation: Specify exact command (e.g., `npx create-next-app@latest...`, `ng new...`). Justify why manual is preferred.
+- Environment Setup: Manual config file creation, environment variable setup. Register for Cloud DB Account.
+- LLM: Let up Local LLM or API key registration if using remote
+
+## Infrastructure and Deployment
+
+{ cloud accounts and resources we will need to provision and for what purpose }
+{ Specify the target deployment environment (e.g., Vercel, AWS EC2, Google Cloud Run) and outline the CI/CD strategy and any specific tools envisioned. }
+
+## Change Log
+
+{ table of changes }

ai/templates/prd-template.md

@@ -0,0 +1,118 @@
+# {Project Name} PRD
+
+## Status: { Draft | Approved }
+
+## Intro
+
+{ Short 1-2 paragraph describing the what and why of what the prd will achieve, as outlined in the project brief or through user questioning }
+
+## Goals and Context
+
+{
+A short summarization of the project brief, with highlights on:
+
+- Clear project objectives
+- Measurable outcomes
+- Success criteria
+- Key performance indicators (KPIs)
+  }
+
+## Features and Requirements
+
+{
+
+- Functional requirements
+- Non-functional requirements
+- User experience requirements
+- Integration requirements
+- Testing requirements
+  }
+
+## Epic Story List
+
+{ We will test fully before each story is complete, so there will be no dedicated Epic and stories at the end for testing }
+
+### Epic 0: Initial Manual Set Up or Provisioning
+
+- stories or tasks the user might need to perform, such as register or set up an account or provide api keys, manually configure some local resources like an LLM, etc...
+
+### Epic-1: Current PRD Epic (for example backend epic)
+
+#### Story 1: Title
+
+Requirements:
+
+- Do X
+- Create Y
+- Etc...
+
+### Epic-2: Second Current PRD Epic (for example front end epic)
+
+### Epic-N: Future Epic Enhancements (Beyond Scope of current PRD)
+
+<example>
+
+## Epic 1: My Cool App Can Retrieve Data
+
+#### Story 1: Project and NestJS Set Up
+
+Requirements:
+
+- Install NestJS CLI Globally
+- Create a new NestJS project with the nestJS cli generator
+- Test Start App Boilerplate Functionality
+- Init Git Repo and commit initial project set up
+
+#### Story 2: News Retrieval API Route
+
+Requirements:
+
+- Create API Route that returns a list of News and comments from the news source foo
+- Route post body specifies the number of posts, articles, and comments to return
+- Create a command in package.json that I can use to call the API Route (route configured in env.local)
+
+</example>
+
+## Technology Stack
+
+{ Table listing choices for languages, libraries, infra, etc...}
+
+<example>
+  | Technology | Version | Description |
+  | ---------- | ------- | ----------- |
+  | Kubernetes | x.y.z | Container orchestration platform for microservices deployment |
+  | Apache Kafka | x.y.z | Event streaming platform for real-time data ingestion |
+  | TimescaleDB | x.y.z | Time-series database for sensor data storage |
+  | Go | x.y.z | Primary language for data processing services |
+  | GoRilla Mux | x.y.z | REST API Framework |
+  | Python | x.y.z | Used for data analysis and ML services |
+</example>
+
+## Project Structure
+
+{ Diagram the folder and file organization structure along with descriptions }
+
+<example>
+
+{ folder tree diagram }
+
+</example>
+
+### POST MVP / PRD Features
+
+- Idea 1
+- Idea 2
+- ...
+- Idea N
+
+## Change Log
+
+{ Markdown table of key changes after document is no longer in draft and is updated, table includes the change title, the story id that the change happened during, and a description if the title is not clear enough }
+
+<example>
+| Change               | Story ID | Description                                                   |
+| -------------------- | -------- | ------------------------------------------------------------- |
+| Initial draft        | N/A      | Initial draft prd                                             |
+| Add ML Pipeline      | story-4  | Integration of machine learning prediction service story      |
+| Kafka Upgrade        | story-6  | Upgraded from Kafka 2.0 to Kafka 3.0 for improved performance |
+</example>

ai/templates/story-template.md

@@ -0,0 +1,53 @@
+# Story {N}: {Title}
+
+## Story
+
+**As a** {role}
+**I want** {action}
+**so that** {benefit}.
+
+## Status
+
+Draft OR In-Progress OR Complete
+
+## Context
+
+{A paragraph explaining the background, current state, and why this story is needed. Include any relevant technical context or business drivers.}
+
+## Estimation
+
+Story Points: {Story Points (1 SP=1 day of Human Development, or 10 minutes of AI development)}
+
+## Acceptance Criteria
+
+1. - [ ] {First criterion - ordered by logical progression}
+2. - [ ] {Second criterion}
+3. - [ ] {Third criterion}
+         {Use - [x] for completed items}
+
+## Subtasks
+
+1. - [ ] {Major Task Group 1}
+   1. - [ ] {Subtask}
+   2. - [ ] {Subtask}
+   3. - [ ] {Subtask}
+2. - [ ] {Major Task Group 2}
+   1. - [ ] {Subtask}
+   2. - [ ] {Subtask}
+   3. - [ ] {Subtask}
+            {Use - [x] for completed items, - [-] for skipped/cancelled items}
+
+## Testing Requirements:\*\*
+
+    - Reiterate the required code coverage percentage (e.g., >= 85%).
+
+## Story Wrap Up (To be filled in AFTER agent execution):\*\*
+
+- **Agent Model Used:** `<Agent Model Name/Version>`
+- **Agent Credit or Cost:** `<Cost/Credits Consumed>`
+- **Date/Time Completed:** `<Timestamp>`
+- **Commit Hash:** `<Git Commit Hash of resulting code>`
+- **Change Log**
+  - change X
+  - change Y
+    ...

custom-mode-prompts/architect.md

@@ -0,0 +1,230 @@
+# Role: Software Architect
+
+You are a world-class expert Software Architect with extensive experience in designing robust, scalable, and maintainable application architectures and conducting deep technical research to figure out the best patterns and technology choices to build the MVP efficiently. You specialize in translating Product Requirements Documents (PRDs) into detailed, opinionated Architecture Documents that serve as technical blueprints. You are adept at assessing technical feasibility, researching complex topics (e.g., compliance, technology trade-offs, architectural patterns), selecting appropriate technology stacks, defining standards, and clearly documenting architectural decisions and rationale.
+
+### Interaction Style
+
+- **Follow the explicit instruction regarding assessment and user confirmation before proceeding.**
+
+- Think step-by-step to ensure all requirements from the PRD and deep research are considered and the architectural design is coherent and logical.
+
+- If the PRD is ambiguous or lacks detail needed for a specific architectural decision (even after potential Deep Research), **ask clarifying questions** before proceeding with that section.
+
+- Propose specific, opinionated choices where the PRD allows flexibility, but clearly justify them based on the requirements or best practices. Avoid presenting multiple options without recommending one.
+
+- Focus solely on the information provided in the PRD context (potentially updated post-research). Do not invent requirements or features not present in the PRD, user provided info or deep research.
+
+## Primary Instructions:
+
+1. First ensure the user has provided a PRD.
+
+2. Check if the user has already produced any deep research into technology or architectural decisions which they can also provide at this time.
+
+3. Analyze the PRD and ask the user any technical clarifications we need to align on before kicking off the project that will be included in this document. The goal is to allow for some emergent choice as the agents develop our application, but ensure also that if there are any major decisions we should make or ensure are understood up front that need clarification from the user, or decisions you intend to make, we need to work with the user to first align on these decisions. NO not proceed with PRD generation until the user has answered your questions and agrees its time to create the draft.
+
+4. ONLY after the go ahead is given, and you feel confident in being able to produce the architecture needed, will you create the draft. After the draft is ready, point out any decisions you have made so the user can easily review them before we mark the architecture as approved.
+
+## Goal
+
+Collaboratively design and document a detailed, opinionated Architecture Document covering all necessary aspects from goals to glossary, based on the PRD, additional research the user might do, and also questions you will ask of the user.
+
+### Output Format
+
+Generate the Architecture Document as a well-structured Markdown file using the following template. Use headings, subheadings, bullet points, code blocks (for versions, commands, or small snippets), and Mermaid syntax for diagrams where specified. Ensure all specified versions, standards, and patterns are clearly stated. Do not be lazy in creating the document, remember that this must have maximal detail that will be stable and a reference for user stories and the ai coding agents that are dumb and forgetful to remain consistent in their future implementation of features. Data models, database patterns, code style and documentation standards, and directory structure and layout are critical. Use the following template that runs through the end of this file and include minimally all sections:
+
+````markdown
+# Architecture for {PRD Title}
+
+Status: { Draft | Approved }
+
+## Technical Summary
+
+{ Short 1-2 paragraph }
+
+## Technology Table
+
+Table listing choices for languages, libraries, infra, cloud resources, etc... may add more detail or refinement that what was in the PRD
+
+<example>
+  | Technology | Version | Description |
+  | ---------- | ------- | ----------- |
+  | Kubernetes | x.y.z | Container orchestration platform for microservices deployment |
+  | Apache Kafka | x.y.z | Event streaming platform for real-time data ingestion |
+  | TimescaleDB | x.y.z | Time-series database for sensor data storage |
+  | Go | x.y.z | Primary language for data processing services |
+  | GoRilla Mux | x.y.z | REST API Framework |
+  | Python | x.y.z | Used for data analysis and ML services |
+  | DeepSeek LLM | R3 | Ollama local hosted and remote hosted API use for customer chat engagement |
+
+</example>
+
+## **High-Level Overview**
+
+Define the architectural style (e.g., Monolith, Microservices, Serverless) and justify the choice based on the PRD. Include a high-level diagram (e.g., C4 Context or Container level using Mermaid syntax).
+
+### **Component View**
+
+Identify major logical components/modules/services, outline their responsibilities, and describe key interactions/APIs between them. Include diagrams if helpful (e.g., C4 Container/Component or class diagrams using Mermaid syntax).
+
+## Architectural Diagrams, Data Models, Schemas
+
+{ Mermaid Diagrams for architecture }
+{ Data Models, API Specs, Schemas }
+
+<example>
+
+### Dynamo One Table Design for App Table
+
+```json
+{
+  "TableName": "AppTable",
+  "KeySchema": [
+    { "AttributeName": "PK", "KeyType": "HASH" },
+    { "AttributeName": "SK", "KeyType": "RANGE" }
+  ],
+  "AttributeDefinitions": [
+    { "AttributeName": "PK", "AttributeType": "S" },
+    { "AttributeName": "SK", "AttributeType": "S" },
+    { "AttributeName": "GSI1PK", "AttributeType": "S" },
+    { "AttributeName": "GSI1SK", "AttributeType": "S" }
+  ],
+  "GlobalSecondaryIndexes": [
+    {
+      "IndexName": "GSI1",
+      "KeySchema": [
+        { "AttributeName": "GSI1PK", "KeyType": "HASH" },
+        { "AttributeName": "GSI1SK", "KeyType": "RANGE" }
+      ],
+      "Projection": { "ProjectionType": "ALL" }
+    }
+  ],
+  "EntityExamples": [
+    {
+      "PK": "USER#123",
+      "SK": "PROFILE",
+      "GSI1PK": "USER",
+      "GSI1SK": "John Doe",
+      "email": "john@example.com",
+      "createdAt": "2023-05-01T12:00:00Z"
+    },
+    {
+      "PK": "USER#123",
+      "SK": "ORDER#456",
+      "GSI1PK": "ORDER",
+      "GSI1SK": "2023-05-15T09:30:00Z",
+      "total": 129.99,
+      "status": "shipped"
+    },
+    {
+      "PK": "PRODUCT#789",
+      "SK": "DETAILS",
+      "GSI1PK": "PRODUCT",
+      "GSI1SK": "Wireless Headphones",
+      "price": 79.99,
+      "inventory": 42
+    }
+  ]
+}
+```
+````
+
+### Sequence Diagram for Recording Alerts
+
+```mermaid
+sequenceDiagram
+    participant Sensor
+    participant API
+    participant ProcessingService
+    participant Database
+    participant NotificationService
+
+    Sensor->>API: Send sensor reading
+    API->>ProcessingService: Forward reading data
+    ProcessingService->>ProcessingService: Validate & analyze data
+    alt Is threshold exceeded
+        ProcessingService->>Database: Store alert
+        ProcessingService->>NotificationService: Trigger notification
+        NotificationService->>NotificationService: Format alert message
+        NotificationService-->>API: Send notification status
+    else Normal reading
+        ProcessingService->>Database: Store reading only
+    end
+    Database-->>ProcessingService: Confirm storage
+    ProcessingService-->>API: Return processing result
+    API-->>Sensor: Send acknowledgement
+```
+
+### Sensor Reading Schema
+
+```json
+{
+  "sensor_id": "string",
+  "timestamp": "datetime",
+  "readings": {
+    "temperature": "float",
+    "pressure": "float",
+    "humidity": "float"
+  },
+  "metadata": {
+    "location": "string",
+    "calibration_date": "datetime"
+  }
+}
+```
+
+</example>
+
+## Project Structure
+
+{ Diagram the folder and file organization structure along with descriptions }
+
+```
+├ /src
+├── /services
+│   ├── /gateway        # Sensor data ingestion
+│   ├── /processor      # Data processing and validation
+│   ├── /analytics      # Data analysis and ML
+│   └── /notifier       # Alert and notification system
+├── /deploy
+│   ├── /kubernetes     # K8s manifests
+│   └── /terraform      # Infrastructure as Code
+└── /docs
+    ├── /api           # API documentation
+    └── /schemas       # Data schemas
+```
+
+## Testing Requirements and Framework
+
+- Unit Testing Standards <examples>Use Jest, 80% coverage, unit test files in line with the file they are testing</examples>
+- Integration Testing <examples>Retained in a separate tests folder outside of src. Will ensure data created is clearly test data and is also cleaned up upon verification. Etc...<examples>
+
+## Patterns and Standards (Opinionated & Specific)
+
+    - **Architectural/Design Patterns:** Mandate specific patterns to be used (e.g., Repository Pattern for data access, MVC/MVVM for structure, CQRS if applicable). .
+
+    - **API Design Standards:** Define the API style (e.g., REST, GraphQL), key conventions (naming, versioning strategy, authentication method), and data formats (e.g., JSON).
+
+    - **Coding Standards:** Specify the mandatory style guide (e.g., Airbnb JavaScript Style Guide, PEP 8), code formatter (e.g., Prettier), and linter (e.g., ESLint with specific config). Define mandatory naming conventions (files, variables, classes). Define test file location conventions.
+
+    - **Error Handling Strategy:** Outline the standard approach for logging errors, propagating exceptions, and formatting error responses.
+
+## Initial Project Setup (Manual Steps)
+
+Define Story 0: Explicitly state initial setup tasks for the user. Expand on what was in the PRD if it was present already if not sufficient, or else just repeat it. Examples:
+
+- Framework CLI Generation: Specify exact command (e.g., `npx create-next-app@latest...`, `ng new...`). Justify why manual is preferred.
+- Environment Setup: Manual config file creation, environment variable setup. Register for Cloud DB Account.
+- LLM: Let up Local LLM or API key registration if using remote
+
+## Infrastructure and Deployment
+
+{ cloud accounts and resources we will need to provision and for what purpose }
+{ Specify the target deployment environment (e.g., Vercel, AWS EC2, Google Cloud Run) and outline the CI/CD strategy and any specific tools envisioned. }
+
+## Change Log
+
+{ table of changes }
+
+```
+
+```

custom-mode-prompts/ba.md

@@ -0,0 +1,65 @@
+# Role: Brainstorming BA and RA
+
+You are a world-class expert Market & Business Analyst and also the best research assistant I have ever met, possessing deep expertise in both comprehensive market research and collaborative project definition. You excel at analyzing external market context and facilitating the structuring of initial ideas into clear, actionable Project Briefs with a focus on Minimum Viable Product (MVP) scope.
+
+You are adept at data analysis, understanding business needs, identifying market opportunities/pain points, analyzing competitors, and defining target audiences. You communicate with exceptional clarity, capable of both presenting research findings formally and engaging in structured, inquisitive dialogue to elicit project requirements.
+
+# Core Capabilities & Goal
+
+Your primary goal is to assist the user in **either**:
+
+## 1. Market Research Mode
+
+Conduct deep research on a provided product concept or market area, delivering a structured report covering:
+
+- Market Needs/Pain Points
+- Competitor Landscape
+- Target User Demographics/Behaviors
+
+## 2. Project Briefing Mode
+
+Collaboratively guide the user through brainstorming and definition to create a structured Project Brief document, covering:
+
+- Core Problem
+- Goals
+- Audience
+- Core Concept/Features (High-Level)
+- MVP Scope (In/Out)
+- (Optionally) Initial Technical Leanings
+
+# Interaction Style & Tone
+
+## Mode Identification
+
+At the start of the conversation, determine if the user requires Market Research or Project Briefing based on their request. If unclear, ask for clarification (e.g., "Are you looking for market research on this idea, or would you like to start defining a Project Brief for it?"). Confirm understanding before proceeding.
+
+## Market Research Mode
+
+- **Tone:** Professional, analytical, informative, objective.
+- **Interaction:** Focus solely on executing deep research based on the provided concept. Confirm understanding of the research topic. Do _not_ brainstorm features or define MVP. Present findings clearly and concisely in the final report.
+
+## Project Briefing Mode
+
+- **Tone:** Collaborative, inquisitive, structured, helpful, focused on clarity and feasibility.
+- **Interaction:** Engage in a dialogue, asking targeted clarifying questions about the concept, problem, goals, users, and especially the MVP scope. Guide the user step-by-step through defining each section of the Project Brief. Help differentiate the full vision from the essential MVP. If market research context is provided (e.g., from a previous interaction or file upload), refer to it.
+
+## General
+
+- Be capable of explaining market concepts or analysis techniques clearly if requested.
+- Use structured formats (lists, sections) for outputs.
+- Avoid ambiguity.
+- Prioritize understanding user needs and project goals.
+
+# Instructions
+
+1. **Identify Mode:** Determine if the user needs Market Research or Project Briefing. Ask for clarification if needed. Confirm the mode you will operate in.
+2. **Input Gathering:**
+   - _If Market Research Mode:_ Ask the user for the specific product concept or market area. Confirm understanding.
+   - _If Project Briefing Mode:_ Ask the user for their initial product concept/idea. Ask if they have prior market research findings to share as context (encourage file upload if available).
+3. **Execution:**
+   - _If Market Research Mode:_ Initiate deep research focusing on Market Needs/Pain Points, Competitor Landscape, and Target Users. Synthesize findings.
+   - _If Project Briefing Mode:_ Guide the user collaboratively through defining each Project Brief section (Core Problem, Goals, Audience, Features, MVP Scope [In/Out], Tech Leanings) by asking targeted questions. Pay special attention to defining a focused MVP.
+4. **Output Generation:**
+   - _If Market Research Mode:_ Structure the synthesized findings into a clear, professional report.
+   - _If Project Briefing Mode:_ Once all sections are defined, structure the information into a well-organized Project Brief document.
+5. **Presentation:** Present the final report or Project Brief document to the user.

custom-mode-prompts/dev.md

@@ -0,0 +1,46 @@
+# Agile Workflow and core memory procedure RULES that MUST be followed EXACTLY!
+
+## Core Initial Instructions Upon Startup:
+
+When coming online, you will first check if a ai/\story-\*.md file exists with the highest sequence number and review the story so you know the current phase of the project.
+
+If there is no story when you come online that is not in draft or in progress status, ask if the user wants to to draft the next sequence user story from the PRD if they did not instruct you to do so.
+
+The user should indicate what story to work on next, and if the story file does not exist, create the draft for it using the information from the `ai/prd.md` and `ai/architecture.md` files. Always use the `ai/templates/story-template.md` file as a template for the story. The story will be named story-{epicnumber.storynumber}.md added to the `ai/stories` folder.
+
+- Example: `ai/stories/story-0.1.md`, `ai/stories/story-1.1.md`, `ai/stories/story-1.2.md`
+
+<critical>
+You will ALWAYS wait for the user to mark the story status as approved before doing ANY work to implement the story.
+</critical>
+
+You will run tests and ensure tests pass before going to the next subtask within a story.
+
+You will update the story file as subtasks are completed. This includes marking the acceptance criteria and subtasks as completed in the <story>-<n>story.md.
+
+<critical>
+Once all subtasks are complete, inform the user that the story is ready for their review and approval. You will not proceed further at this point.
+</critical>
+
+## During Development
+
+Once a story has been marked as In Progress, and you are told to proceed with development:
+
+- Update story files as subtasks are completed.
+- If you are unsure of the next step, ask the user for clarification, and then update the story as needed to maintain a very clear memory of decisions.
+- Reference the `ai/architecture.md` if the story is inefficient or needs additional technical documentation so you are in sync with the Architects plans.
+- Reference the `ai/architecture.md` so you also understand from the source tree where to add or update code.
+- Keep files small and single focused, follow good separation of concerns, naming conventions, and dry principles,
+- Utilize good documentation standards by ensuring that we are following best practices of leaving JSDoc comments on public functions classess and interfaces.
+- When prompted by the user with command `update story`, update the current story to:
+  - Reflect the current state.
+  - Clarify next steps.
+  - Ensure the chat log in the story is up to date with any chat thread interactions
+- Continue to verify the story is correct and the next steps are clear.
+- Remember that a story is not complete if you have not also run ALL tests and verified all tests pass.
+- Do not tell the user the story is complete, or mark the story as complete, unless you have written the stories required tests to validate all newly implemented functionality, and have run ALL the tests in the entire project ensuring there is no regression.
+
+## YOU DO NOT NEED TO ASK to:
+
+- Run unit Tests during the development process until they pass.
+- Update the story AC and tasks as they are completed.

custom-mode-prompts/pm.md

@@ -0,0 +1,146 @@
+# Role: Technical Product Manager
+
+## Role
+
+You are an expert Technical Product Manager adept at translating high-level ideas into detailed, well-structured Product Requirements Documents (PRDs) suitable for Agile development teams, including comprehensive UI/UX specifications. You prioritize clarity, completeness, and actionable requirements.
+
+## Initial Instructions
+
+1. **Project Brief**: Ask the user for the project brief document contents, or if unavailable, what is the idea they want a PRD for. Continue to ask questions until you feel you have enough information to build a comprehensive PRD as outlined in the template below. The user should provide information about features in scope for MVP, and potentially what is out of scope for post-MVP that we might still need to consider for the platform.
+2. **UI/UX Details**: If there is a UI involved, ensure the user includes ideas or information about the UI if it is not clear from the features already described or the project brief. For example: UX interactions, theme, look and feel, layout ideas or specifications, specific choice of UI libraries, etc.
+3. **Technical Constraints**: If none have been provided, ask the user to provide any additional constraints or technology choices, such as: type of testing, hosting, deployments, languages, frameworks, platforms, etc.
+
+## Goal
+
+Based on the provided Project Brief, your task is to collaboratively guide me in creating a comprehensive Product Requirements Document (PRD) for the Minimum Viable Product (MVP). We need to define all necessary requirements to guide the architecture and development phases. Development will be performed by very junior developers and AI agents who work best incrementally and with limited scope or ambiguity. This document is a critical document to ensure we are on track and building the right thing for the minimum viable goal we are to achieve. This document will be used by the architect to produce further artifacts to really guide the development. The PRD you create will have:
+
+- **Very Detailed Purpose**: Problems solved, and an ordered task sequence.
+- **High-Level Architecture**: Patterns and key technical decisions (to be further developed later by the architect), high-level mermaid diagrams to help visualize interactions or use cases.
+- **Technologies**: To be used including versions, setup, and constraints.
+- **Proposed Directory Tree**: To follow good coding best practices and architecture.
+- **Unknowns, Assumptions, and Risks**: Clearly called out.
+
+## Interaction Model
+
+You will ask the user clarifying questions for unknowns to help generate the details needed for a high-quality PRD that can be used to develop the project incrementally, step by step, in a clear, methodical manner.
+
+---
+
+## PRD Template
+
+You will follow the PRD Template below and minimally contain all sections from the template. This is the expected final output that will serve as the project's source of truth to realize the MVP of what we are building.
+
+```markdown
+# {Project Name} PRD
+
+## Status: { Draft | Approved }
+
+## Intro
+
+{ Short 1-2 paragraph describing the what and why of what the prd will achieve, as outlined in the project brief or through user questioning }
+
+## Goals and Context
+
+{
+A short summarization of the project brief, with highlights on:
+
+- Clear project objectives
+- Measurable outcomes
+- Success criteria
+- Key performance indicators (KPIs)
+  }
+
+## Features and Requirements
+
+{
+
+- Functional requirements
+- Non-functional requirements
+- User experience requirements
+- Integration requirements
+- Testing requirements
+  }
+
+## Epic Story List
+
+{ We will test fully before each story is complete, so there will be no dedicated Epic and stories at the end for testing }
+
+### Epic 0: Initial Manual Set Up or Provisioning
+
+- stories or tasks the user might need to perform, such as register or set up an account or provide api keys, manually configure some local resources like an LLM, etc...
+
+### Epic-1: Current PRD Epic (for example backend epic)
+
+#### Story 1: Title
+
+Requirements:
+
+- Do X
+- Create Y
+- Etc...
+
+### Epic-2: Second Current PRD Epic (for example front end epic)
+
+### Epic-N: Future Epic Enhancements (Beyond Scope of current PRD)
+
+<example>
+
+## Epic 1: My Cool App Can Retrieve Data
+
+#### Story 1: Project and NestJS Set Up
+
+Requirements:
+
+- Install NestJS CLI Globally
+- Create a new NestJS project with the nestJS cli generator
+- Test Start App Boilerplate Functionality
+- Init Git Repo and commit initial project set up
+
+#### Story 2: News Retrieval API Route
+
+Requirements:
+
+- Create API Route that returns a list of News and comments from the news source foo
+- Route post body specifies the number of posts, articles, and comments to return
+- Create a command in package.json that I can use to call the API Route (route configured in env.local)
+
+</example>
+
+## Technology Stack
+
+{ Table listing choices for languages, libraries, infra, etc...}
+
+<example>
+  | Technology | Version | Description |
+  | ---------- | ------- | ----------- |
+  | Kubernetes | x.y.z | Container orchestration platform for microservices deployment |
+  | Apache Kafka | x.y.z | Event streaming platform for real-time data ingestion |
+  | TimescaleDB | x.y.z | Time-series database for sensor data storage |
+  | Go | x.y.z | Primary language for data processing services |
+  | GoRilla Mux | x.y.z | REST API Framework |
+  | Python | x.y.z | Used for data analysis and ML services |
+</example>
+
+## Project Structure
+
+{ folder tree diagram }
+
+### POST MVP / PRD Features
+
+- Idea 1
+- Idea 2
+- ...
+- Idea N
+
+## Change Log
+
+{ Markdown table of key changes after document is no longer in draft and is updated, table includes the change title, the story id that the change happened during, and a description if the title is not clear enough }
+
+<example>
+| Change               | Story ID | Description                                                   |
+| -------------------- | -------- | ------------------------------------------------------------- |
+| Initial draft        | N/A      | Initial draft prd                                             |
+| Add ML Pipeline      | story-4  | Integration of machine learning prediction service story      |
+| Kafka Upgrade        | story-6  | Upgraded from Kafka 2.0 to Kafka 3.0 for improved performance |
+</example>
+```

custom-mode-prompts/po.md

@@ -0,0 +1,28 @@
+# Role: Product Owner
+
+## Role
+
+You are an **Expert Agile Product Owner**. Your task is to create a logically ordered backlog of Epics and User Stories for the MVP, based on the provided Product Requirements Document (PRD) and Architecture Document.
+
+## Goal
+
+Analyze all technical documents and the PRD and ensure that we have a roadmap of actionalble granular sequential stories that include all details called out for the MVP. Ensure there are no holes, differences or gaps between the architecture and the PRD - especially the sequence of stories in the PRD. You will give affirmation that the PRD story list is approved. To do this, if there are issues with it, you will further question the user or make suggestions and finally update the PRD so it meets your approval.
+
+## Instructions
+
+**CRITICAL:** Ensure the user has provided the PRD and Architecture Documents. The PRD has a high-level listing of stories and tasks, and the architecture document may contain even more details and things that need to be completed for MVP, including additional setup. Also consider if there are UX or UI artifacts provided and if the UI is already built out with wireframes or will need to be built from the ground up.
+
+**Analyze:** Carefully review the provided PRD and Architecture Document. Pay close attention to features, requirements, UI/UX flows, technical specifications, and any specified manual setup steps or dependencies mentioned in the Architecture Document.
+
+- Determine if there are gaps in the PRD or if more stories are needed for the epics.
+- The architecture could indicate that other enabler epics or stories are needed that were not thought of at the time the PRD was first produced.
+- The **goal** is to ensure we can update the list of epics and stories in the PRD to be more accurate than when it was first drafted.
+
+> **IMPORTANT NOTE:**
+> This output needs to be at a proper level of detail to document the full path of completion of the MVP from beginning to end. As coding agents work on each story and subtask sequentially, they will break it down further as needed—so the subtasks here do not need to be exhaustive, but should be informative.
+
+Ensure stories align with the **INVEST** principles (Independent, Negotiable, Valuable, Estimable, Small, Testable), keeping in mind that foundational/setup stories might have slightly different characteristics but must still be clearly defined.
+
+## Output
+
+Final Output will be made as an update to the list of stories in the PRD, and the change log in the PRD needs to also indicate what modifications or corrections the PO made.

custom-mode-prompts/sm.md

@@ -0,0 +1,49 @@
+# Role: Technical Product Manager
+
+## Role
+
+You are an expert Technical Scrum Master / Senior Engineer, highly skilled at translating Agile user stories into extremely detailed, self-contained specification files suitable for direct input to an AI coding agent operating with a clean context window. You excel at extracting and injecting relevant technical and UI/UX details from Product Requirements Documents (PRDs) and Architecture Documents, defining precise acceptance criteria, and breaking down work into granular, actionable subtasks.
+
+## Initial Instructions and Interaction Model
+
+You speak in a clear concise factual tone. If the user requests for a story list to be generated and has not provided the proper context of an PRD and possibly an architecture, and it is not clear what the high level stories are or what technical details you will need - you MUST instruct the user to provide this information first so you as a senior technical engineer / scrum master can then create the detailed user stories list.
+
+## Goal
+
+Your task is to generate a complete, detailed ai/stories/stories.md file for the AI coding agent based _only_ on the provided context files (such as a PRD, Architecture, and possible UI guidance or addendum information). The file must contain all of the stories with a separator in between each.
+
+### Output Format
+
+Generate a single Markdown file named stories.md containing the following sections for each story - the story files all need to go into the ai/stories.md/ folder at the root of the project:
+
+1.  **Story ID:** `<Story_ID>`
+2.  **Epic ID:** `<Epic_ID>`
+3.  **Title:** `<Full User Story Title>`
+4.  **Objective:** A concise (1-2 sentence) summary of the story's goal.
+5.  **Background/Context:** Briefly explain the story's purpose. **Reference general project standards** (like coding style, linting, documentation rules) by pointing to their definition in the central Architecture Document (e.g., "Adhere to project coding standards defined in ArchDoc Sec 3.2"). **Explicitly list context specific to THIS story** that was provided above (e.g., "Target Path: src/components/Auth/", "Relevant Schema: User model", "UI: Login form style per PRD Section X.Y"). _Focus on story-specific details and references to general standards, avoiding verbatim repetition of lengthy general rules._
+6.  **Acceptance Criteria (AC):**
+    - Use the Given/When/Then (GWT) format.
+    - Create specific, testable criteria covering:
+      - Happy path functionality.
+      - Negative paths and error handling (referencing UI/UX specs for error messages/states).
+      - Edge cases.
+      - Adherence to relevant NFRs (e.g., response time, security).
+      - Adherence to UI/UX specifications (e.g., layout, styling, responsiveness).
+      - _Implicitly:_ Adherence to referenced general coding/documentation standards.
+7.  **Subtask Checklist:**
+    - Provide a highly granular, step-by-step checklist for the AI agent.
+    - Break down tasks logically (e.g., file creation, function implementation, UI element coding, state management, API calls, unit test creation, error handling implementation, adding comments _per documentation standards_).
+    - Specify exact file names and paths where necessary, according to the Architecture context.
+    - Include tasks for writing unit tests to meet the specified coverage target, following the defined testing standards (e.g., AAA pattern).
+    - **Crucially, clearly identify any steps the HUMAN USER must perform manually.** Prefix these steps with `MANUAL STEP:` and provide clear, step-by-step instructions (e.g., `MANUAL STEP: Obtain API key from <Service> console.`, `MANUAL STEP: Add the key to the .env file as VARIABLE_NAME.`).
+8.  **Testing Requirements:**
+    - Explicitly state the required test types (e.g., Unit Tests via Jest).
+    - Reiterate the required code coverage percentage (e.g., >= 85%).
+    - State that the Definition of Done includes all ACs being met and all specified tests passing (implicitly including adherence to standards).
+9.  **Story Wrap Up (To be filled in AFTER agent execution):**
+    - \_Note: This section should be completed by the user/process after the AI agent has finished processing an individual story file.
+    - **Agent Model Used:** `<Agent Model Name/Version>`
+    - **Agent Credit or Cost:** `<Cost/Credits Consumed>`
+    - **Date/Time Completed:** `<Timestamp>`
+    - **Commit Hash:** `<Git Commit Hash of resulting code>`
+    - **Change Log:**

custom-mode-prompts/ux.md

@@ -0,0 +1,40 @@
+# UX Expert: Vercel V0 Prompt Engineer
+
+## Role
+
+You are a highly specialized expert in both UI/UX specification analysis and prompt engineering for Vercel's V0 AI UI generation tool. You have deep knowledge of V0's capabilities and expected input format, particularly assuming a standard stack of React, Next.js App Router, Tailwind CSS, shadcn/ui components, and lucide-react icons. Your expertise lies in meticulously translating detailed UI/UX specifications from a Product Requirements Document (PRD) into a single, optimized text prompt suitable for V0 generation.
+
+Additionally you are an expert in all things visual design and user experience, so you will offer advice or help the user work out what they need to build amazing user experiences - helping make the vision a reality
+
+## Goal
+
+Generate a single, highly optimized text prompt for Vercel's V0 to create a specific target UI component or page, based _exclusively_ on the UI/UX specifications found within a provided PRD. If the PRD lacks sufficient detail for unambiguous V0 generation, your goal is instead to provide a list of specific, targeted clarifying questions to the user.
+
+## Input
+
+- A finalized Product Requirements Document (PRD) (request user upload).
+
+## Output
+
+EITHER:
+
+- A single block of text representing the optimized V0 prompt, ready to be used within V0 (or similar tools).
+- OR a list of clarifying questions if the PRD is insufficient.
+
+## Interaction Style & Tone
+
+- **Meticulous & Analytical:** Carefully parse the provided PRD, focusing solely on extracting all UI/UX details relevant to the needed UX/UI.
+- **V0 Focused:** Interpret specifications through the lens of V0's capabilities and expected inputs (assuming shadcn/ui, lucide-react, Tailwind, etc., unless the PRD explicitly states otherwise).
+- **Detail-Driven:** Look for specifics regarding layout, spacing, typography, colors, responsiveness, component states (e.g., hover, disabled, active), interactions, specific shadcn/ui components to use, exact lucide-react icon names, accessibility considerations (alt text, labels), and data display requirements.
+- **Non-Assumptive & Questioning:** **Critically evaluate** if the extracted information is complete and unambiguous for V0 generation. If _any_ required detail is missing or vague (e.g., "appropriate spacing," "relevant icon," "handle errors"), **DO NOT GUESS or generate a partial prompt.** Instead, formulate clear, specific questions pinpointing the missing information (e.g., "What specific lucide-react icon should be used for the 'delete' action?", "What should the exact spacing be between the input field and the button?", "How should the component respond on screens smaller than 640px?"). Present _only_ these questions and await the user's answers.
+- **Precise & Concise:** Once all necessary details are available (either initially or after receiving answers), construct the V0 prompt efficiently, incorporating all specifications accurately.
+- **Tone:** Precise, analytical, highly focused on UI/UX details and V0 technical requirements, objective, and questioning when necessary.
+
+## Instructions
+
+1. **Request Input:** Ask the user for the finalized PRD (encourage file upload) and the exact name of the target component/page to generate with V0. If there is no PRD or it's lacking, converse to understand the UX and UI desired.
+2. **Analyze PRD:** Carefully read the PRD, specifically locating the UI/UX specifications (and any other relevant sections like Functional Requirements) pertaining _only_ to the target component/page.
+3. **Assess Sufficiency:** Evaluate if the specifications provide _all_ the necessary details for V0 to generate the component accurately (check layout, styling, responsiveness, states, interactions, specific component names like shadcn/ui Button, specific icon names like lucide-react Trash2, accessibility attributes, etc.). Assume V0 defaults (React, Next.js App Router, Tailwind, shadcn/ui, lucide-react) unless the PRD explicitly contradicts them.
+4. **Handle Insufficiency (If Applicable):** If details are missing or ambiguous, formulate a list of specific, targeted clarifying questions. Present _only_ this list of questions to the user. State clearly that you need answers to these questions before you can generate the V0 prompt. **Wait for the user's response.**
+5. **Generate Prompt (If Sufficient / After Clarification):** Once all necessary details are confirmed (either from the initial PRD analysis or after receiving answers to clarifying questions), construct a single, optimized V0 text prompt. Ensure the prompt incorporates all relevant specifications clearly and concisely, leveraging V0's expected syntax and keywords where appropriate.
+6. **Present Output:** Output EITHER the final V0 prompt text block OR the list of clarifying questions (as determined in step 4).

docs/BUNDLE_DISTRIBUTION_SETUP.md

@@ -1,95 +0,0 @@
-# Bundle Distribution Setup (For Maintainers)
-
-**Audience:** BMAD maintainers setting up bundle auto-publishing
-
----
-
-## One-Time Setup
-
-Run these commands once to enable auto-publishing:
-
-```bash
-# 1. Create bmad-bundles repo
-gh repo create bmad-code-org/bmad-bundles --public --description "BMAD Web Bundles"
-
-# 2. Ensure `main` exists (GitHub Pages API requires a source branch)
-git clone git@github.com:bmad-code-org/bmad-bundles.git
-cd bmad-bundles
-printf '# bmad-bundles\n\nStatic bundles published from BMAD-METHOD.\n' > README.md
-git add README.md
-git commit -m "Initial commit"
-git push origin main
-cd -
-
-# 3. Enable GitHub Pages (API replacement for removed --enable-pages flag)
-gh api repos/bmad-code-org/bmad-bundles/pages --method POST -f source[branch]=main -f source[path]=/
-# (Optional) confirm status
-gh api repos/bmad-code-org/bmad-bundles/pages --jq '{status,source}'
-
-# 4. Create GitHub PAT and add as secret
-# Go to: https://github.com/settings/tokens/new
-# Scopes: repo (full control)
-# Name: bmad-bundles-ci
-# Then add as secret:
-gh secret set BUNDLES_PAT --repo bmad-code-org/BMAD-METHOD
-# (paste PAT when prompted)
-```
-
-If the Pages POST returns `409`, the site already exists. If it returns `422` about `main` missing, redo step 2 to push the initial commit.
-
-**Done.** Bundles auto-publish on every main merge.
-
----
-
-## How It Works
-
-**On main merge:**
-
-- `.github/workflows/bundle-latest.yaml` runs
-- Publishes to: `https://bmad-code-org.github.io/bmad-bundles/`
-
-**On release:**
-
-- `npm run release:patch` runs `.github/workflows/manual-release.yaml`
-- Attaches bundles to: `https://github.com/bmad-code-org/BMAD-METHOD/releases/latest`
-
----
-
-## Testing
-
-```bash
-# Test latest channel
-git push origin main
-# Wait 2 min, then: curl https://bmad-code-org.github.io/bmad-bundles/
-
-# Test stable channel
-npm run release:patch
-# Check: gh release view
-```
-
----
-
-## Troubleshooting
-
-**"Permission denied" or auth errors**
-
-```bash
-# Verify PAT secret exists
-gh secret list --repo bmad-code-org/BMAD-METHOD | grep BUNDLES_PAT
-
-# If missing, recreate PAT and add secret:
-gh secret set BUNDLES_PAT --repo bmad-code-org/BMAD-METHOD
-```
-
-**GitHub Pages not updating / need to re-check config**
-
-```bash
-gh api repos/bmad-code-org/bmad-bundles/pages --jq '{status,source,html_url}'
-```
-
----
-
-## Distribution URLs
-
-**Stable:** `https://github.com/bmad-code-org/BMAD-METHOD/releases/latest`
-**Latest:** `https://bmad-code-org.github.io/bmad-bundles/`

docs/agent-customization-guide.md

@@ -1,208 +0,0 @@
-# Agent Customization Guide
-
-Customize BMad agents without modifying core files. All customizations persist through updates.
-
-## Quick Start
-
-**1. Locate Customization Files**
-
-After installation, find agent customization files in:
-
-```
-.bmad/_cfg/agents/
-├── core-bmad-master.customize.yaml
-├── bmm-dev.customize.yaml
-├── bmm-pm.customize.yaml
-└── ... (one file per installed agent)
-```
-
-**2. Edit Any Agent**
-
-Open the `.customize.yaml` file for the agent you want to modify. All sections are optional - customize only what you need.
-
-**3. Rebuild the Agent**
-
-After editing, IT IS CRITICAL to rebuild the agent to apply changes:
-
-```bash
-npx bmad-method@alpha install # and then select option to compile all agents
-# OR for individual agent only
-npx bmad-method@alpha build <agent-name>
-
-# Examples:
-npx bmad-method@alpha build bmm-dev
-npx bmad-method@alpha build core-bmad-master
-npx bmad-method@alpha build bmm-pm
-```
-
-## What You Can Customize
-
-### Agent Name
-
-Change how the agent introduces itself:
-
-```yaml
-agent:
-  metadata:
-    name: 'Spongebob' # Default: "Amelia"
-```
-
-### Persona
-
-Replace the agent's personality, role, and communication style:
-
-```yaml
-persona:
-  role: 'Senior Full-Stack Engineer'
-  identity: 'Lives in a pineapple (under the sea)'
-  communication_style: 'Spongebob'
-  principles:
-    - 'Never Nester, Spongebob Devs hate nesting more than 2 levels deep'
-    - 'Favor composition over inheritance'
-```
-
-**Note:** The persona section replaces the entire default persona (not merged).
-
-### Memories
-
-Add persistent context the agent will always remember:
-
-```yaml
-memories:
-  - 'Works at Krusty Krab'
-  - 'Favorite Celebrity: David Hasslehoff'
-  - 'Learned in Epic 1 that its not cool to just pretend that tests have passed'
-```
-
-### Custom Menu Items
-
-Add your own workflows to the agent's menu:
-
-```yaml
-menu:
-  - trigger: my-workflow
-    workflow: '{project-root}/custom/my-workflow.yaml'
-    description: My custom workflow
-  - trigger: deploy
-    action: '#deploy-prompt'
-    description: Deploy to production
-```
-
-**Don't include:** `*` prefix or `help`/`exit` items - these are auto-injected.
-
-### Critical Actions
-
-Add instructions that execute before the agent starts:
-
-```yaml
-critical_actions:
-  - 'Always check git status before making changes'
-  - 'Use conventional commit messages'
-```
-
-### Custom Prompts
-
-Define reusable prompts for `action="#id"` menu handlers:
-
-```yaml
-prompts:
-  - id: deploy-prompt
-    content: |
-      Deploy the current branch to production:
-      1. Run all tests
-      2. Build the project
-      3. Execute deployment script
-```
-
-## Real-World Examples
-
-**Example 1: Customize Developer Agent for TDD**
-
-```yaml
-# .bmad/_cfg/agents/bmm-dev.customize.yaml
-agent:
-  metadata:
-    name: 'TDD Developer'
-
-memories:
-  - 'Always write tests before implementation'
-  - 'Project uses Jest and React Testing Library'
-
-critical_actions:
-  - 'Review test coverage before committing'
-```
-
-**Example 2: Add Custom Deployment Workflow**
-
-```yaml
-# .bmad/_cfg/agents/bmm-dev.customize.yaml
-menu:
-  - trigger: deploy-staging
-    workflow: '{project-root}/.bmad/deploy-staging.yaml'
-    description: Deploy to staging environment
-  - trigger: deploy-prod
-    workflow: '{project-root}/.bmad/deploy-prod.yaml'
-    description: Deploy to production (with approval)
-```
-
-**Example 3: Multilingual Product Manager**
-
-```yaml
-# .bmad/_cfg/agents/bmm-pm.customize.yaml
-persona:
-  role: 'Bilingual Product Manager'
-  identity: 'Expert in US and LATAM markets'
-  communication_style: 'Clear, strategic, with cultural awareness'
-  principles:
-    - 'Consider localization from day one'
-    - 'Balance business goals with user needs'
-
-memories:
-  - 'User speaks English and Spanish'
-  - 'Target markets: US and Latin America'
-```
-
-## Tips
-
-- **Start Small:** Customize one section at a time and rebuild to test
-- **Backup:** Copy customization files before major changes
-- **Update-Safe:** Your customizations in `_cfg/` survive all BMad updates
-- **Per-Project:** Customization files are per-project, not global
-- **Version Control:** Consider committing `_cfg/` to share customizations with your team
-
-## Module vs. Global Config
-
-**Module-Level (Recommended):**
-
-- Customize agents per-project in `.bmad/_cfg/agents/`
-- Different projects can have different agent behaviors
-
-**Global Config (Coming Soon):**
-
-- Set defaults that apply across all projects
-- Override with project-specific customizations
-
-## Troubleshooting
-
-**Changes not appearing?**
-
-- Make sure you ran `npx bmad-method build <agent-name>` after editing
-- Check YAML syntax is valid (indentation matters!)
-- Verify the agent name matches the file name pattern
-
-**Agent not loading?**
-
-- Check for YAML syntax errors
-- Ensure required fields aren't left empty if you uncommented them
-- Try reverting to the template and rebuilding
-
-**Need to reset?**
-
-- Delete the `.customize.yaml` file
-- Run `npx bmad-method build <agent-name>` to regenerate defaults
-
-## Next Steps
-
-- **[BMM Agents Guide](../src/modules/bmm/docs/agents-guide.md)** - Learn about all 12 BMad Method agents
-- **[BMB Create Agent Workflow](../src/modules/bmb/workflows/create-agent/README.md)** - Build completely custom agents
-- **[BMM Complete Documentation](../src/modules/bmm/docs/README.md)** - Full BMad Method reference

docs/custom-content-installation.md

@@ -1,245 +0,0 @@
-# Custom Content Installation
-
-This guide explains how to create and install custom BMAD content including agents, workflows, and modules. Custom content allows you to extend BMAD's functionality with your own specialized tools and workflows that can be shared across projects or teams.
-
-## Types of Custom Content
-
-### 1. Custom Agents and Workflows (Standalone)
-
-Custom agents and workflows are standalone content packages that can be installed without being part of a full module. These are perfect for:
-
-- Sharing specialized agents across projects
-- Building a personal Agent powered Notebook vault
-- Distributing workflow templates
-- Creating agent libraries for specific domains
-
-#### Structure
-
-A custom agents and workflows package follows this structure:
-
-```
-my-custom-agents/
-├── module.yaml          # Package configuration
-├── agents/              # Agent definitions
-│   └── my-agent/
-│       └── agent.md
-└── workflows/           # Workflow definitions
-    └── my-workflow/
-        └── workflow.md
-```
-
-#### Configuration
-
-Create a `module.yaml` file in your package root:
-
-```yaml
-code: my-custom-agents
-name: 'My Custom Agents and Workflows'
-default_selected: true
-```
-
-#### Example
-
-See `/example-custom-content` for a working example of a folder with multiple random custom agents and workflows. Technically its also just a module, but you will be able to further pick and choose from this folders contents of what you do and do not want to include in a destination folder. This way, you can store all custom content source in one location and easily install it to different locations.
-
-### 2. Custom Modules
-
-Custom modules are complete BMAD modules that can include their own configuration, documentation, along with agents and workflows that all compliment each other. Additionally they will have their own installation scripts, data, and potentially other tools. Modules can be used for:
-
-- Domain-specific functionality (e.g., industry-specific workflows, entertainment, education and training, medical, etc...)
-- Integration with external systems
-- Specialized agent collections
-- Custom tooling and utilities
-
-#### Structure
-
-A custom module follows this structure:
-
-```
-my-module/
-├── _module-installer/
-│   ├── installer.js           # optional, when it exists it will run with module installation
-├── module.yaml                # Module installation configuration with custom question and answer capture
-├── docs/                      # Module documentation
-├── agents/                    # Module-specific agents
-├── workflows/                 # Module-specific workflows
-├── data/                      # csv or other content to power agent intelligence or workflows
-├── tools/                     # Custom tools, hooks, mcp
-└── sub-modules/               # IDE-specific customizations
-    ├── vscode/
-    └── cursor/
-```
-
-#### Module Configuration
-
-The `module.yaml` file defines how your module is installed:
-
-```yaml
-# Module metadata
-code: my-module
-name: 'My Custom Module'
-default_selected: false
-
-header: 'My Custom Module'
-subheader: 'Description of what this module does'
-
-# Configuration prompts
-my_setting:
-  prompt: 'Configure your module setting'
-  default: 'default-value'
-  result: '{value}'
-```
-
-#### Example
-
-See `/example-custom-module` for a complete example:
-
-## Installation Process
-
-### Step 1: Running the Installer
-
-When you run the existing normal BMAD installer - either from the cloned repo, OR via NPX, it will ask about custom content:
-
-```
-? Do you have custom content to install?
-❯ No (skip custom content)
-  Enter a directory path
-  Enter a URL [Coming soon]
-```
-
-### Step 2: Providing Custom Content Path
-
-If you select "Enter a directory path", the installer will prompt for the location:
-
-```
-? Enter the path to your custom content directory: /path/to/folder/containing/content/folder
-```
-
-The installer will:
-
-- Scan for `module.yaml` files (modules)
-- Display an indication of how many installable folders it has found. Note that a project with stand along agents and workflows all under a single folder like the example will just list the count as 1 for that directory.
-
-### Step 3: Selecting Content
-
-The installer presents a unified selection interface:
-
-```
-? Select modules and custom content to install:
-[── Custom Content ──]
- ◉ My Custom Agents and Workflows (/path/to/custom)
-[── Official Content ──]
- ◯ BMM: Business Method & Management
- ◯ CIS: Creativity & Innovation Suite
-```
-
-## Agent Sidecar Support
-
-Agents with sidecar content can store personal data, memories, and working files outside of the `.bmad` directory. This separation keeps personal content separate from BMAD's core files.
-
-### What is Sidecar Content?
-
-Sidecar content includes:
-
-- Agent memories and learning data
-- Personal working files
-- Temporary data
-- User-specific configurations
-
-### Sidecar Configuration
-
-The sidecar folder location is configured during BMAD core installation:
-
-```
-? Where should users' agent sidecar memory folders be stored?
-❯ .bmad-user-memory
-```
-
-### How It Works
-
-1. **Agent Declaration**: Agents declare `hasSidecar: true` in their metadata
-2. **Sidecar Detection**: The installer automatically detects folders with "sidecar" in the name
-3. **Installation**: Sidecar content is copied to the configured location
-4. **Path Replacement**: The `{agent_sidecar_folder}` placeholder in agent configurations is replaced with the actual path to the installed instance of the sidecar folder. Now when you use the agent, depending on its design, will use the content in sidecar to record interactions, remember things you tell it, or serve a host of many other issues.
-
-### Example Structure
-
-```
-my-agent/
-├── agent.md              # Agent definition
-└── my-agent-sidecar/     # Sidecar content folder
-    ├── memories/
-    ├── working/
-    └── config/
-```
-
-### Git Integration
-
-Since sidecar content is stored outside the `.bmad` directory (and typically outside version control), users can:
-
-- Add the sidecar folder to `.gitignore` to exclude personal data
-- Share agent definitions without exposing personal content
-- Maintain separate configurations for different projects
-
-Example `.gitignore` entry:
-
-```
-# Exclude agent personal data
-.bmad-user-memory/
-```
-
-## Creating Custom Content with BMAD Builder
-
-The BMAD Builder provides workflows that will guide you to produce your own custom content:
-
-1. **Agent Templates**: Use standardized agent templates with proper structure
-2. **Workflow Templates**: Create workflows using proven patterns
-3. **Validation Tools**: Validate your content before distribution
-4. **Package Generation**: Generate properly structured packages
-
-### Best Practices
-
-1. **Use Clear Naming**: Make your content codes and names descriptive
-2. **Provide Documentation**: Include clear setup and usage instructions
-3. **Test Installation**: Test your content in a clean environment
-4. **Version Management**: Use semantic versioning for updates
-5. **Respect User Privacy**: Keep personal data in sidecar folders
-
-## Distribution
-
-Custom content can be distributed:
-
-1. **File System**: Copy folders directly to users
-2. **Git Repositories**: Clone or download from version control
-3. **Package Managers**: [Coming soon] npm package support
-4. **URL Installation**: [Coming soon] Direct URL installation, including an official community vetted module forge
-
-## Troubleshooting
-
-### No Custom Content Found
-
-- Ensure your `module.yaml` files are properly named
-- Check file permissions
-- Verify the directory path is correct
-
-### Installation Errors
-
-- Run the installer with verbose logging
-- Check for syntax errors in YAML configuration files
-- Verify all required files are present
-
-### Sidecar Issues
-
-- Ensure the agent has `hasSidecar: true` in metadata
-- Check that sidecar folders contain "sidecar" in the name
-- Verify the agent_sidecar_folder configuration
-- Ensure the custom agent has proper language in it to actually use the sidecar content, including loading memories on agent load.
-
-## Support
-
-For help with custom content creation or installation:
-
-1. Check the examples in `/example-custom-content` and `/example-custom-module`
-2. Review the BMAD documentation
-3. Create an issue in the BMAD repository
-4. Join the BMAD community discussions on discord

docs/document-sharding-guide.md

@@ -1,449 +0,0 @@
-# Document Sharding Guide
-
-Comprehensive guide to BMad Method's document sharding system for managing large planning and architecture documents.
-
-## Table of Contents
-
-- [What is Document Sharding?](#what-is-document-sharding)
-- [When to Use Sharding](#when-to-use-sharding)
-- [How Sharding Works](#how-sharding-works)
-- [Using the Shard-Doc Tool](#using-the-shard-doc-tool)
-- [Workflow Support](#workflow-support)
-- [Best Practices](#best-practices)
-- [Examples](#examples)
-
-## What is Document Sharding?
-
-Document sharding splits large markdown files into smaller, organized files based on level 2 headings (`## Heading`). This enables:
-
-- **Selective Loading** - Workflows load only the sections they need
-- **Reduced Token Usage** - Massive efficiency gains for large projects
-- **Better Organization** - Logical section-based file structure
-- **Maintained Context** - Index file preserves document structure
-
-### Architecture
-
-```
-Before Sharding:
-docs/
-└── PRD.md (large 50k token file)
-
-After Sharding:
-docs/
-└── prd/
-    ├── index.md                    # Table of contents with descriptions
-    ├── overview.md                 # Section 1
-    ├── user-requirements.md        # Section 2
-    ├── technical-requirements.md   # Section 3
-    └── ...                         # Additional sections
-```
-
-## When to Use Sharding
-
-### Ideal Candidates
-
-**Large Multi-Epic Projects:**
-
-- Very large complex PRDs
-- Architecture documents with multiple system layers
-- Epic files with 4+ epics (especially for Phase 4)
-- UX design specs covering multiple subsystems
-
-**Token Thresholds:**
-
-- **Consider sharding**: Documents > 20k tokens
-- **Strongly recommended**: Documents > 40k tokens
-- **Critical for efficiency**: Documents > 60k tokens
-
-### When NOT to Shard
-
-**Small Projects:**
-
-- Single epic projects
-- Level 0-1 projects (tech-spec only)
-- Documents under 10k tokens
-- Quick prototypes
-
-**Frequently Updated Docs:**
-
-- Active work-in-progress documents
-- Documents updated daily
-- Documents where whole-file context is essential
-
-## How Sharding Works
-
-### Sharding Process
-
-1. **Tool Execution**: Run `npx @kayvan/markdown-tree-parser source.md destination/` - this is abstracted with the core shard-doc task which is installed as a slash command or manual task rule depending on your tools.
-2. **Section Extraction**: Tool splits by level 2 headings
-3. **File Creation**: Each section becomes a separate file
-4. **Index Generation**: `index.md` created with structure and descriptions
-
-### Workflow Discovery
-
-BMad workflows use a **dual discovery system**:
-
-1. **Try whole document first** - Look for `document-name.md`
-2. **Check for sharded version** - Look for `document-name/index.md`
-3. **Priority rule** - Whole document takes precedence if both exist
-
-### Loading Strategies
-
-**Full Load (Phase 1-3 workflows):**
-
-```
-If sharded:
-  - Read index.md
-  - Read ALL section files
-  - Treat as single combined document
-```
-
-**Selective Load (Phase 4 workflows):**
-
-```
-If sharded epics and working on Epic 3:
-  - Read epics/index.md
-  - Load ONLY epics/epic-3.md
-  - Skip all other epic files
-  - 90%+ token savings!
-```
-
-## Using the Shard-Doc Tool
-
-### CLI Command
-
-```bash
-# Activate bmad-master or analyst agent, then:
-/shard-doc
-```
-
-### Interactive Process
-
-```
-Agent: Which document would you like to shard?
-User: docs/PRD.md
-
-Agent: Default destination: docs/prd/
-       Accept default? [y/n]
-User: y
-
-Agent: Sharding PRD.md...
-       ✓ Created 12 section files
-       ✓ Generated index.md
-       ✓ Complete!
-```
-
-### What Gets Created
-
-**index.md structure:**
-
-```markdown
-# PRD - Index
-
-## Sections
-
-1. [Overview](./overview.md) - Project vision and objectives
-2. [User Requirements](./user-requirements.md) - Feature specifications
-3. [Epic 1: Authentication](./epic-1-authentication.md) - User auth system
-4. [Epic 2: Dashboard](./epic-2-dashboard.md) - Main dashboard UI
-   ...
-```
-
-**Individual section files:**
-
-- Named from heading text (kebab-case)
-- Contains complete section content
-- Preserves all markdown formatting
-- Can be read independently
-
-## Workflow Support
-
-### Universal Support
-
-**All BMM workflows support both formats:**
-
-- ✅ Whole documents
-- ✅ Sharded documents
-- ✅ Automatic detection
-- ✅ Transparent to user
-
-### Workflow-Specific Patterns
-
-#### Phase 1-3 (Full Load)
-
-Workflows load entire sharded documents:
-
-- `product-brief` - Research, brainstorming docs
-- `prd` - Product brief, research
-- `gdd` - Game brief, research
-- `create-ux-design` - PRD, brief, architecture (if available)
-- `tech-spec` - Brief, research
-- `architecture` - PRD, UX design (if available)
-- `create-epics-and-stories` - PRD, architecture
-- `implementation-readiness` - All planning docs
-
-#### Phase 4 (Selective Load)
-
-Workflows load only needed sections:
-
-**sprint-planning** (Full Load):
-
-- Needs ALL epics to build complete status
-
-**create-story, code-review** (Selective):
-
-```
-Working on Epic 3, Story 2:
-  ✓ Load epics/epic-3.md only
-  ✗ Skip epics/epic-1.md, epic-2.md, epic-4.md, etc.
-
-Result: 90%+ token reduction for 10-epic projects!
-```
-
-### Input File Patterns
-
-Workflows use standardized patterns:
-
-```yaml
-input_file_patterns:
-  prd:
-    whole: '{output_folder}/*prd*.md'
-    sharded: '{output_folder}/*prd*/index.md'
-
-  epics:
-    whole: '{output_folder}/*epic*.md'
-    sharded_index: '{output_folder}/*epic*/index.md'
-    sharded_single: '{output_folder}/*epic*/epic-{{epic_num}}.md'
-```
-
-## Best Practices
-
-### Sharding Strategy
-
-**Do:**
-
-- ✅ Shard after planning phase complete
-- ✅ Keep level 2 headings well-organized
-- ✅ Use descriptive section names
-- ✅ Shard before Phase 4 implementation
-- ✅ Keep original file as backup initially
-
-**Don't:**
-
-- ❌ Shard work-in-progress documents
-- ❌ Shard small documents (<20k tokens)
-- ❌ Mix sharded and whole versions
-- ❌ Manually edit index.md structure
-
-### Naming Conventions
-
-**Good Section Names:**
-
-```markdown
-## Epic 1: User Authentication
-
-## Technical Requirements
-
-## System Architecture
-
-## UX Design Principles
-```
-
-**Poor Section Names:**
-
-```markdown
-## Section 1
-
-## Part A
-
-## Details
-
-## More Info
-```
-
-### File Management
-
-**When to Re-shard:**
-
-- Significant structural changes to document
-- Adding/removing major sections
-- After major refactoring
-
-**Updating Sharded Docs:**
-
-1. Edit individual section files directly
-2. OR edit original, delete sharded folder, re-shard
-3. Don't manually edit index.md
-
-## Examples
-
-### Example 1: Large PRD
-
-**Scenario:** 15-epic project, PRD is 45k tokens
-
-**Before Sharding:**
-
-```
-Every workflow loads entire 45k token PRD
-Architecture workflow: 45k tokens
-UX design workflow: 45k tokens
-```
-
-**After Sharding:**
-
-```bash
-/shard-doc
-Source: docs/PRD.md
-Destination: docs/prd/
-
-Created:
-  prd/index.md
-  prd/overview.md (3k tokens)
-  prd/functional-requirements.md (8k tokens)
-  prd/non-functional-requirements.md (6k tokens)
-  prd/user-personas.md (4k tokens)
-  ...additional FR/NFR sections
-```
-
-**Result:**
-
-```
-Architecture workflow: Can load specific sections needed
-UX design workflow: Can load specific sections needed
-Significant token reduction for large requirement docs!
-```
-
-### Example 2: Sharding Epics File
-
-**Scenario:** 8 epics with detailed stories, 35k tokens total
-
-```bash
-/shard-doc
-Source: docs/bmm-epics.md
-Destination: docs/epics/
-
-Created:
-  epics/index.md
-  epics/epic-1.md
-  epics/epic-2.md
-  ...
-  epics/epic-8.md
-```
-
-**Efficiency Gain:**
-
-```
-Working on Epic 5 stories:
-  Old: Load all 8 epics (35k tokens)
-  New: Load epic-5.md only (4k tokens)
-  Savings: 88% reduction
-```
-
-### Example 3: Architecture Document
-
-**Scenario:** Multi-layer system architecture, 28k tokens
-
-```bash
-/shard-doc
-Source: docs/architecture.md
-Destination: docs/architecture/
-
-Created:
-  architecture/index.md
-  architecture/system-overview.md
-  architecture/frontend-architecture.md
-  architecture/backend-services.md
-  architecture/data-layer.md
-  architecture/infrastructure.md
-  architecture/security-architecture.md
-```
-
-**Benefit:** Code-review workflow can reference specific architectural layers without loading entire architecture doc.
-
-## Custom Workflow Integration
-
-### For Workflow Builders
-
-When creating custom workflows that load large documents:
-
-**1. Add input_file_patterns to workflow.yaml:**
-
-```yaml
-input_file_patterns:
-  your_document:
-    whole: '{output_folder}/*your-doc*.md'
-    sharded: '{output_folder}/*your-doc*/index.md'
-```
-
-**2. Add discovery instructions to instructions.md:**
-
-```markdown
-## Document Discovery
-
-1. Search for whole document: _your-doc_.md
-2. Check for sharded version: _your-doc_/index.md
-3. If sharded: Read index + ALL sections (or specific sections if selective load)
-4. Priority: Whole document first
-```
-
-**3. Choose loading strategy:**
-
-- **Full Load**: Read all sections when sharded
-- **Selective Load**: Read only relevant sections (requires section identification logic)
-
-### Pattern Templates
-
-**Full Load Pattern:**
-
-```xml
-<action>Search for document: {output_folder}/*doc-name*.md</action>
-<action>If not found, check for sharded: {output_folder}/*doc-name*/index.md</action>
-<action if="sharded found">Read index.md to understand structure</action>
-<action if="sharded found">Read ALL section files listed in index</action>
-<action if="sharded found">Combine content as single document</action>
-```
-
-**Selective Load Pattern (with section ID):**
-
-```xml
-<action>Determine section needed (e.g., epic_num = 3)</action>
-<action>Check for sharded version: {output_folder}/*doc-name*/index.md</action>
-<action if="sharded found">Read ONLY the specific section file needed</action>
-<action if="sharded found">Skip all other section files</action>
-```
-
-## Troubleshooting
-
-### Common Issues
-
-**Both whole and sharded exist:**
-
-- Workflows will use whole document (priority rule)
-- Delete or archive the one you don't want
-
-**Index.md out of sync:**
-
-- Delete sharded folder
-- Re-run shard-doc on original
-
-**Workflow can't find document:**
-
-- Check file naming matches patterns (`*prd*.md`, `*epic*.md`, etc.)
-- Verify index.md exists in sharded folder
-- Check output_folder path in config
-
-**Sections too granular:**
-
-- Combine sections in original document
-- Use fewer level 2 headings
-- Re-shard
-
-## Related Documentation
-
-- [shard-doc Tool](../src/core/tools/shard-doc.xml) - Tool implementation
-- [BMM Workflows Guide](../src/modules/bmm/workflows/README.md) - Workflow overview
-- [Workflow Creation Guide](../src/modules/bmb/workflows/create-workflow/workflow-creation-guide.md) - Custom workflow patterns
-
----
-
-**Document sharding is optional but powerful** - use it when efficiency matters for large projects!

docs/ide-info/auggie.md

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

docs/ide-info/claude-code.md

@@ -1,25 +0,0 @@
-# BMAD Method - Claude Code Instructions
-
-## Activating Agents
-
-BMAD agents are installed as slash commands in `.claude/commands/bmad/`.
-
-### How to Use
-
-1. **Type Slash Command**: Start with `/` to see available commands
-2. **Select Agent**: Type `/bmad-{agent-name}` (e.g., `/bmad-dev`)
-3. **Execute**: Press Enter to activate that agent persona
-
-### Examples
-
-```
-/bmad:bmm:agents:dev - Activate development agent
-/bmad:bmm:agents:architect - Activate architect agent
-/bmad:bmm:workflows:dev-story - Execute dev-story workflow
-```
-
-### Notes
-
-- Commands are autocompleted when you type `/`
-- Agent remains active for the conversation
-- Start a new conversation to switch agents

docs/ide-info/cline.md

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

docs/ide-info/codex.md

@@ -1,21 +0,0 @@
-# BMAD Method - Codex Instructions
-
-## Activating Agents
-
-BMAD agents, tasks and workflows are installed as custom prompts in
-`$CODEX_HOME/prompts/bmad-*.md` files. If `CODEX_HOME` is not set, it
-defaults to `$HOME/.codex/`.
-
-### Examples
-
-```
-/bmad-bmm-agents-dev - Activate development agent
-/bmad-bmm-agents-architect - Activate architect agent
-/bmad-bmm-workflows-dev-story - Execute dev-story workflow
-```
-
-### Notes
-
-Prompts are autocompleted when you type /
-Agent remains active for the conversation
-Start a new conversation to switch agents

docs/ide-info/crush.md

@@ -1,30 +0,0 @@
-# BMAD Method - Crush Instructions
-
-## Activating Agents
-
-BMAD agents are installed as commands in `.crush/commands/bmad/`.
-
-### How to Use
-
-1. **Open Command Palette**: Use Crush command interface
-2. **Navigate**: Browse to `.bmad/{module}/agents/`
-3. **Select Agent**: Choose the agent command
-4. **Execute**: Run to activate agent persona
-
-### Command Structure
-
-```
-.crush/commands/bmad/
-├── agents/          # All agents
-├── tasks/           # All tasks
-├── core/            # Core module
-│   ├── agents/
-│   └── tasks/
-└── {module}/        # Other modules
-```
-
-### Notes
-
-- Commands organized by module
-- Can browse hierarchically
-- Agent activates for session

docs/ide-info/cursor.md

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

docs/ide-info/gemini.md

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

docs/ide-info/github-copilot.md

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

docs/ide-info/iflow.md

@@ -1,33 +0,0 @@
-# BMAD Method - iFlow CLI Instructions
-
-## Activating Agents
-
-BMAD agents are installed as commands in `.iflow/commands/bmad/`.
-
-### How to Use
-
-1. **Access Commands**: Use iFlow command interface
-2. **Navigate**: Browse to `.bmad/agents/` or `.bmad/tasks/`
-3. **Select**: Choose the agent or task command
-4. **Execute**: Run to activate
-
-### Command Structure
-
-```
-.iflow/commands/bmad/
-├── agents/     # Agent commands
-└── tasks/      # Task commands
-```
-
-### Examples
-
-```
-/.bmad/agents/core-dev - Activate dev agent
-/.bmad/tasks/core-setup - Execute setup task
-```
-
-### Notes
-
-- Commands organized by type (agents/tasks)
-- Agent activates for session
-- Similar to Crush command structure

docs/ide-info/kilo.md

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

docs/ide-info/opencode.md

@@ -1,24 +0,0 @@
-# BMAD Method - OpenCode Instructions
-
-## Activating Agents
-
-BMAD agents are installed as OpenCode agents in `.opencode/agent/BMAD/{module_name}` and workflow commands in `.opencode/command/BMAD/{module_name}`.
-
-### How to Use
-
-1. **Switch Agents**: Press **Tab** to cycle through primary agents or select using the `/agents`
-2. **Activate Agent**: Once the Agent is selected say `hello` or any prompt to activate that agent persona
-3. **Execute Commands**: Type `/bmad` to see and execute bmad workflow commands (commands allow for fuzzy matching)
-
-### Examples
-
-```
-/agents - to see a list of agents and switch between them
-/.bmad/bmm/workflows/workflow-init - Activate the workflow-init command
-```
-
-### Notes
-
-- Press **Tab** to switch between primary agents (Analyst, Architect, Dev, etc.)
-- Commands are autocompleted when you type `/` and allow for fuzzy matching
-- Workflow commands execute in current agent context, make sure you have the right agent activated before running a command

docs/ide-info/qwen.md

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

docs/ide-info/roo.md

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

docs/ide-info/rovo-dev.md

@@ -1,388 +0,0 @@
-# Rovo Dev IDE Integration
-
-This document describes how BMAD-METHOD integrates with [Atlassian Rovo Dev](https://www.atlassian.com/rovo-dev), an AI-powered software development assistant.
-
-## Overview
-
-Rovo Dev is designed to integrate deeply with developer workflows and organizational knowledge bases. When you install BMAD-METHOD in a Rovo Dev project, it automatically installs BMAD agents, workflows, tasks, and tools just like it does for other IDEs (Cursor, VS Code, etc.).
-
-BMAD-METHOD provides:
-
-- **Agents**: Specialized subagents for various development tasks
-- **Workflows**: Multi-step workflow guides and coordinators
-- **Tasks & Tools**: Reference documentation for BMAD tasks and tools
-
-### What are Rovo Dev Subagents?
-
-Subagents are specialized agents that Rovo Dev can delegate tasks to. They are defined as Markdown files with YAML frontmatter stored in the `.rovodev/subagents/` directory. Rovo Dev automatically discovers these files and makes them available through the `@subagent-name` syntax.
-
-## Installation and Setup
-
-### Automatic Installation
-
-When you run the BMAD-METHOD installer and select Rovo Dev as your IDE:
-
-```bash
-bmad install
-```
-
-The installer will:
-
-1. Create a `.rovodev/subagents/` directory in your project (if it doesn't exist)
-2. Convert BMAD agents into Rovo Dev subagent format
-3. Write subagent files with the naming pattern: `bmad-<module>-<agent-name>.md`
-
-### File Structure
-
-After installation, your project will have:
-
-```
-project-root/
-├── .rovodev/
-│   ├── subagents/
-│   │   ├── bmad-core-code-reviewer.md
-│   │   ├── bmad-bmm-pm.md
-│   │   ├── bmad-bmm-dev.md
-│   │   └── ... (more agents from selected modules)
-│   ├── workflows/
-│   │   ├── bmad-brainstorming.md
-│   │   ├── bmad-prd-creation.md
-│   │   └── ... (workflow guides)
-│   ├── references/
-│   │   ├── bmad-task-core-code-review.md
-│   │   ├── bmad-tool-core-analysis.md
-│   │   └── ... (task/tool references)
-│   ├── config.yml          (Rovo Dev configuration)
-│   ├── prompts.yml         (Optional: reusable prompts)
-│   └── ...
-├── .bmad/                  (BMAD installation directory)
-└── ...
-```
-
-**Directory Structure Explanation:**
-
-- **subagents/**: Agents discovered and used by Rovo Dev with `@agent-name` syntax
-- **workflows/**: Multi-step workflow guides and instructions
-- **references/**: Documentation for available tasks and tools in BMAD
-
-## Subagent File Format
-
-BMAD agents are converted to Rovo Dev subagent format, which uses Markdown with YAML frontmatter:
-
-### Basic Structure
-
-```markdown
----
-name: bmad-module-agent-name
-description: One sentence description of what this agent does
-tools:
-  - bash
-  - open_files
-  - grep
-  - expand_code_chunks
-model: anthropic.claude-3-5-sonnet-20241022-v2:0 # Optional
-load_memory: true # Optional
----
-
-You are a specialized agent for [specific task].
-
-## Your Role
-
-Describe the agent's role and responsibilities...
-
-## Key Instructions
-
-1. First instruction
-2. Second instruction
-3. Third instruction
-
-## When to Use This Agent
-
-Explain when and how to use this agent...
-```
-
-### YAML Frontmatter Fields
-
-| Field         | Type    | Required | Description                                                                                                                           |
-| ------------- | ------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------- |
-| `name`        | string  | Yes      | Unique identifier for the subagent (kebab-case, no spaces)                                                                            |
-| `description` | string  | Yes      | One-line description of the subagent's purpose                                                                                        |
-| `tools`       | array   | No       | List of tools the subagent can use. If not specified, uses parent agent's tools                                                       |
-| `model`       | string  | No       | Specific LLM model for this subagent (e.g., `anthropic.claude-3-5-sonnet-20241022-v2:0`). If not specified, uses parent agent's model |
-| `load_memory` | boolean | No       | Whether to load default memory files (AGENTS.md, AGENTS.local.md). Defaults to `true`                                                 |
-
-### System Prompt
-
-The content after the closing `---` is the subagent's system prompt. This defines:
-
-- The agent's persona and role
-- Its capabilities and constraints
-- Step-by-step instructions for task execution
-- Examples of expected behavior
-
-## Using BMAD Components in Rovo Dev
-
-### Invoking a Subagent (Agent)
-
-In Rovo Dev, you can invoke a BMAD agent as a subagent using the `@` syntax:
-
-```
-@bmad-core-code-reviewer Please review this PR for potential issues
-@bmad-bmm-pm Help plan this feature release
-@bmad-bmm-dev Implement this feature
-```
-
-### Accessing Workflows
-
-Workflow guides are available in `.rovodev/workflows/` directory:
-
-```
-@bmad-core-code-reviewer Use the brainstorming workflow from .rovodev/workflows/bmad-brainstorming.md
-```
-
-Workflow files contain step-by-step instructions and can be referenced or copied into Rovo Dev for collaborative workflow execution.
-
-### Accessing Tasks and Tools
-
-Task and tool documentation is available in `.rovodev/references/` directory. These provide:
-
-- Task execution instructions
-- Tool capabilities and usage
-- Integration examples
-- Parameter documentation
-
-### Example Usage Scenarios
-
-#### Code Review
-
-```
-@bmad-core-code-reviewer Review the changes in src/components/Button.tsx
-for best practices, performance, and potential bugs
-```
-
-#### Documentation
-
-```
-@bmad-core-documentation-writer Generate API documentation for the new
-user authentication module
-```
-
-#### Feature Design
-
-```
-@bmad-module-feature-designer Design a solution for implementing
-dark mode support across the application
-```
-
-## Customizing BMAD Subagents
-
-You can customize BMAD subagents after installation by editing their files directly in `.rovodev/subagents/`.
-
-### Example: Adding Tool Restrictions
-
-By default, BMAD subagents inherit tools from the parent Rovo Dev agent. You can restrict which tools a specific subagent can use:
-
-```yaml
----
-name: bmad-core-code-reviewer
-description: Reviews code and suggests improvements
-tools:
-  - open_files
-  - expand_code_chunks
-  - grep
----
-```
-
-### Example: Using a Specific Model
-
-Some agents might benefit from using a different model. You can specify this:
-
-```yaml
----
-name: bmad-core-documentation-writer
-description: Writes clear and comprehensive documentation
-model: anthropic.claude-3-5-sonnet-20241022-v2:0
----
-```
-
-### Example: Enhancing the System Prompt
-
-You can add additional context to a subagent's system prompt:
-
-```markdown
----
-name: bmad-core-code-reviewer
-description: Reviews code and suggests improvements
----
-
-You are a specialized code review agent for our project.
-
-## Project Context
-
-Our codebase uses:
-
-- React 18 for frontend
-- Node.js 18+ for backend
-- TypeScript for type safety
-- Jest for testing
-
-## Review Checklist
-
-1. Type safety and TypeScript correctness
-2. React best practices and hooks usage
-3. Performance considerations
-4. Test coverage
-5. Documentation and comments
-
-...rest of original system prompt...
-```
-
-## Memory and Context
-
-By default, BMAD subagents have `load_memory: true`, which means they will load memory files from your project:
-
-- **Project-level**: `.rovodev/AGENTS.md` and `.rovodev/.agent.md`
-- **User-level**: `~/.rovodev/AGENTS.md` (global memory across all projects)
-
-These files can contain:
-
-- Project guidelines and conventions
-- Common patterns and best practices
-- Recent decisions and context
-- Custom instructions for all agents
-
-### Creating Project Memory
-
-Create `.rovodev/AGENTS.md` in your project:
-
-```markdown
-# Project Guidelines
-
-## Code Style
-
-- Use 2-space indentation
-- Use camelCase for variables
-- Use PascalCase for classes
-
-## Architecture
-
-- Follow modular component structure
-- Use dependency injection for services
-- Implement proper error handling
-
-## Testing Requirements
-
-- Minimum 80% code coverage
-- Write tests before implementation
-- Use descriptive test names
-```
-
-## Troubleshooting
-
-### Subagents Not Appearing in Rovo Dev
-
-1. **Verify files exist**: Check that `.rovodev/subagents/bmad-*.md` files are present
-2. **Check Rovo Dev is reloaded**: Rovo Dev may cache agent definitions. Restart Rovo Dev or reload the project
-3. **Verify file format**: Ensure files have proper YAML frontmatter (between `---` markers)
-4. **Check file permissions**: Ensure files are readable by Rovo Dev
-
-### Agent Name Conflicts
-
-If you have custom subagents with the same names as BMAD agents, Rovo Dev will load both but may show a warning. Use unique prefixes for custom subagents to avoid conflicts.
-
-### Tools Not Available
-
-If a subagent's tools aren't working:
-
-1. Verify the tool names match Rovo Dev's available tools
-2. Check that the parent Rovo Dev agent has access to those tools
-3. Ensure tool permissions are properly configured in `.rovodev/config.yml`
-
-## Advanced: Tool Configuration
-
-Rovo Dev agents have access to a set of tools for various tasks. Common tools available include:
-
-- `bash`: Execute shell commands
-- `open_files`: View file contents
-- `grep`: Search across files
-- `expand_code_chunks`: View specific code sections
-- `find_and_replace_code`: Modify files
-- `create_file`: Create new files
-- `delete_file`: Delete files
-- `move_file`: Rename or move files
-
-### MCP Servers
-
-Rovo Dev can also connect to Model Context Protocol (MCP) servers, which provide additional tools and data sources:
-
-- **Atlassian Integration**: Access to Jira, Confluence, and Bitbucket
-- **Code Analysis**: Custom code analysis and metrics
-- **External Services**: APIs and third-party integrations
-
-Configure MCP servers in `~/.rovodev/mcp.json` or `.rovodev/mcp.json`.
-
-## Integration with Other IDE Handlers
-
-BMAD-METHOD supports multiple IDEs simultaneously. You can have both Rovo Dev and other IDE configurations (Cursor, VS Code, etc.) in the same project. Each IDE will have its own artifacts installed in separate directories.
-
-For example:
-
-- Rovo Dev agents: `.rovodev/subagents/bmad-*.md`
-- Cursor rules: `.cursor/rules/bmad/`
-- Claude Code: `.claude/rules/bmad/`
-
-## Performance Considerations
-
-- BMAD subagent files are typically small (1-5 KB each)
-- Rovo Dev lazy-loads subagents, so having many subagents doesn't impact startup time
-- System prompts are cached by Rovo Dev after first load
-
-## Best Practices
-
-1. **Keep System Prompts Concise**: Shorter, well-structured prompts are more effective
-2. **Use Project Memory**: Leverage `.rovodev/AGENTS.md` for shared context
-3. **Customize Tool Restrictions**: Give subagents only the tools they need
-4. **Test Subagent Invocations**: Verify each subagent works as expected for your project
-5. **Version Control**: Commit `.rovodev/subagents/` to version control for team consistency
-6. **Document Custom Subagents**: Add comments explaining the purpose of customized subagents
-
-## Related Documentation
-
-- [Rovo Dev Official Documentation](https://www.atlassian.com/rovo-dev)
-- [BMAD-METHOD Installation Guide](./installation.md)
-- [IDE Handler Architecture](./ide-handlers.md)
-- [Rovo Dev Configuration Reference](https://www.atlassian.com/rovo-dev/configuration)
-
-## Examples
-
-### Example 1: Code Review Workflow
-
-```
-User: @bmad-core-code-reviewer Review src/auth/login.ts for security issues
-Rovo Dev → Subagent: Opens file, analyzes code, suggests improvements
-Subagent output: Security vulnerabilities found, recommendations provided
-```
-
-### Example 2: Documentation Generation
-
-```
-User: @bmad-core-documentation-writer Generate API docs for the new payment module
-Rovo Dev → Subagent: Analyzes code structure, generates documentation
-Subagent output: Markdown documentation with examples and API reference
-```
-
-### Example 3: Architecture Design
-
-```
-User: @bmad-module-feature-designer Design a caching strategy for the database layer
-Rovo Dev → Subagent: Reviews current architecture, proposes design
-Subagent output: Detailed architecture proposal with implementation plan
-```
-
-## Support
-
-For issues or questions about:
-
-- **Rovo Dev**: See [Atlassian Rovo Dev Documentation](https://www.atlassian.com/rovo-dev)
-- **BMAD-METHOD**: See [BMAD-METHOD README](../README.md)
-- **IDE Integration**: See [IDE Handler Guide](./ide-handlers.md)

docs/ide-info/trae.md

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

docs/ide-info/windsurf.md

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

docs/index.md

@@ -1,152 +0,0 @@
-# BMad Documentation Index
-
-Complete map of all BMad Method v6 documentation with recommended reading paths.
-
----
-
-## 🎯 Getting Started (Start Here!)
-
-**New users:** Start with one of these based on your situation:
-
-| Your Situation         | Start Here                                                      | Then Read                                                     |
-| ---------------------- | --------------------------------------------------------------- | ------------------------------------------------------------- |
-| **Brand new to BMad**  | [Quick Start Guide](../src/modules/bmm/docs/quick-start.md)     | [BMM Workflows Guide](../src/modules/bmm/workflows/README.md) |
-| **Upgrading from v4**  | [v4 to v6 Upgrade Guide](./v4-to-v6-upgrade.md)                 | [Quick Start Guide](../src/modules/bmm/docs/quick-start.md)   |
-| **Brownfield project** | [Brownfield Guide](../src/modules/bmm/docs/brownfield-guide.md) | [Quick Start Guide](../src/modules/bmm/docs/quick-start.md)   |
-
----
-
-## 📋 Core Documentation
-
-### Project-Level Docs (Root)
-
-- **[README.md](../README.md)** - Main project overview, feature summary, and module introductions
-- **[CONTRIBUTING.md](../CONTRIBUTING.md)** - How to contribute, pull request guidelines, code style
-- **[CHANGELOG.md](../CHANGELOG.md)** - Version history and breaking changes
-- **[CLAUDE.md](../CLAUDE.md)** - Claude Code specific guidelines for this project
-
-### Installation & Setup
-
-- **[v4 to v6 Upgrade Guide](./v4-to-v6-upgrade.md)** - Migration path for v4 users
-- **[Document Sharding Guide](./document-sharding-guide.md)** - Split large documents for 90%+ token savings
-- **[Web Bundles](./USING_WEB_BUNDLES.md)** - Use BMAD agents in Claude Projects, ChatGPT, or Gemini without installation
-- **[Bundle Distribution Setup](./BUNDLE_DISTRIBUTION_SETUP.md)** - Maintainer guide for bundle auto-publishing
-
----
-
-## 🏗️ Module Documentation
-
-### BMad Method (BMM) - Software & Game Development
-
-The flagship module for agile AI-driven development.
-
-- **[BMM Module README](../src/modules/bmm/README.md)** - Module overview, agents, and complete documentation index
-- **[BMM Documentation](../src/modules/bmm/docs/)** - All BMM-specific guides and references:
-  - [Quick Start Guide](../src/modules/bmm/docs/quick-start.md) - Step-by-step guide to building your first project
-  - [Quick Spec Flow](../src/modules/bmm/docs/quick-spec-flow.md) - Rapid Level 0-1 development
-  - [Scale Adaptive System](../src/modules/bmm/docs/scale-adaptive-system.md) - Understanding the 5-level system
-  - [Brownfield Guide](../src/modules/bmm/docs/brownfield-guide.md) - Working with existing codebases
-- **[BMM Workflows Guide](../src/modules/bmm/workflows/README.md)** - **ESSENTIAL READING**
-- **[Test Architect Guide](../src/modules/bmm/testarch/README.md)** - Testing strategy and quality assurance
-
-### BMad Builder (BMB) - Create Custom Solutions
-
-Build your own agents, workflows, and modules.
-
-- **[BMB Module README](../src/modules/bmb/README.md)** - Module overview and capabilities
-- **[Agent Creation Guide](../src/modules/bmb/workflows/create-agent/README.md)** - Design custom agents
-
-### Creative Intelligence Suite (CIS) - Innovation & Creativity
-
-AI-powered creative thinking and brainstorming.
-
-- **[CIS Module README](../src/modules/cis/README.md)** - Module overview and workflows
-
----
-
-## 🖥️ IDE-Specific Guides
-
-Instructions for loading agents and running workflows in your development environment.
-
-**Popular IDEs:**
-
-- [Claude Code](./ide-info/claude-code.md)
-- [Cursor](./ide-info/cursor.md)
-- [VS Code](./ide-info/windsurf.md)
-
-**Other Supported IDEs:**
-
-- [Augment](./ide-info/auggie.md)
-- [Cline](./ide-info/cline.md)
-- [Codex](./ide-info/codex.md)
-- [Crush](./ide-info/crush.md)
-- [Gemini](./ide-info/gemini.md)
-- [GitHub Copilot](./ide-info/github-copilot.md)
-- [IFlow](./ide-info/iflow.md)
-- [Kilo](./ide-info/kilo.md)
-- [OpenCode](./ide-info/opencode.md)
-- [Qwen](./ide-info/qwen.md)
-- [Roo](./ide-info/roo.md)
-- [Rovo Dev](./ide-info/rovo-dev.md)
-- [Trae](./ide-info/trae.md)
-
-**Key concept:** Every reference to "load an agent" or "activate an agent" in the main docs links to the [ide-info](./ide-info/) directory for IDE-specific instructions.
-
----
-
-## 🔧 Advanced Topics
-
-### Custom Agents, Workflow and Modules
-
-- **[Custom Content Installation](./custom-content-installation.md)** - Install and personalize agents, workflows and modules with the default bmad-method installer!
-- [Agent Customization Guide](./agent-customization-guide.md) - Customize agent behavior and responses
-
-### Installation & Bundling
-
-- [IDE Injections Reference](./installers-bundlers/ide-injections.md) - How agents are installed to IDEs
-- [Installers & Platforms Reference](./installers-bundlers/installers-modules-platforms-reference.md) - CLI tool and platform support
-- [Web Bundler Usage](./installers-bundlers/web-bundler-usage.md) - Creating web-compatible bundles
-
----
-
-## 🎓 Recommended Reading Paths
-
-### Path 1: Brand New to BMad (Software Project)
-
-1. [README.md](../README.md) - Understand the vision
-2. [Quick Start Guide](../src/modules/bmm/docs/quick-start.md) - Get hands-on
-3. [BMM Module README](../src/modules/bmm/README.md) - Understand agents
-4. [BMM Workflows Guide](../src/modules/bmm/workflows/README.md) - Master the methodology
-5. [Your IDE guide](./ide-info/) - Optimize your workflow
-
-### Path 2: Game Development Project
-
-1. [README.md](../README.md) - Understand the vision
-2. [Quick Start Guide](../src/modules/bmm/docs/quick-start.md) - Get hands-on
-3. [BMM Module README](../src/modules/bmm/README.md) - Game agents are included
-4. [BMM Workflows Guide](../src/modules/bmm/workflows/README.md) - Game workflows
-5. [Your IDE guide](./ide-info/) - Optimize your workflow
-
-### Path 3: Upgrading from v4
-
-1. [v4 to v6 Upgrade Guide](./v4-to-v6-upgrade.md) - Understand what changed
-2. [Quick Start Guide](../src/modules/bmm/docs/quick-start.md) - Reorient yourself
-3. [BMM Workflows Guide](../src/modules/bmm/workflows/README.md) - Learn new v6 workflows
-
-### Path 4: Working with Existing Codebase (Brownfield)
-
-1. [Brownfield Guide](../src/modules/bmm/docs/brownfield-guide.md) - Approach for legacy code
-2. [Quick Start Guide](../src/modules/bmm/docs/quick-start.md) - Follow the process
-3. [BMM Workflows Guide](../src/modules/bmm/workflows/README.md) - Master the methodology
-
-### Path 5: Building Custom Solutions
-
-1. [BMB Module README](../src/modules/bmb/README.md) - Understand capabilities
-2. [Agent Creation Guide](../src/modules/bmb/workflows/create-agent/README.md) - Create agents
-3. [BMM Workflows Guide](../src/modules/bmm/workflows/README.md) - Understand workflow structure
-
-### Path 6: Contributing to BMad
-
-1. [CONTRIBUTING.md](../CONTRIBUTING.md) - Contribution guidelines
-2. Relevant module README - Understand the area you're contributing to
-3. [Code Style section in CONTRIBUTING.md](../CONTRIBUTING.md#code-style) - Follow standards

docs/installers-bundlers/ide-injections.md

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

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

@@ -1,389 +0,0 @@
-# BMAD Installation & Module System Reference
-
-## Table of Contents
-
-1. [Overview](#overview)
-2. [Quick Start](#quick-start)
-3. [Architecture](#architecture)
-4. [Modules](#modules)
-5. [Configuration System](#configuration-system)
-6. [Platform Integration](#platform-integration)
-7. [Development Guide](#development-guide)
-8. [Troubleshooting](#troubleshooting)
-
-## Overview
-
-BMad Core is a modular AI agent framework with intelligent installation, platform-agnostic support, and configuration inheritance.
-
-### Key Features
-
-- **Modular Design**: Core + optional modules (BMB, BMM, CIS)
-- **Smart Installation**: Interactive configuration with dependency resolution
-- **Clean Architecture**: Centralized `.bmad` directory add to project, no source pollution with multiple folders added
-
-## Architecture
-
-### Directory Structure upon installation
-
-```
-project-root/
-├── .bmad/             # Centralized installation
-│   ├── _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
-- module.yaml
-- `localskip="true"` agents are filtered out
-- Source `config.yaml` templates are replaced with generated configs
-
-## Modules
-
-### Core Module (Required)
-
-Foundation framework with C.O.R.E. (Collaboration Optimized Reflection Engine)
-
-- **Components**: Base agents, activation system, advanced elicitation
-- **Config**: `user_name`, `communication_language`
-
-### BMM Module
-
-BMad Method for software development workflows
-
-- **Components**: PM agent, dev tasks, PRD templates, story generation
-- **Config**: `project_name`, `tech_docs`, `output_folder`, `story_location`
-- **Dependencies**: Core
-
-### CIS Module
-
-Creative Innovation Studio for design workflows
-
-- **Components**: Design agents, creative tasks
-- **Config**: `output_folder`, design preferences
-- **Dependencies**: Core
-
-### Module Structure
-
-```
-src/modules/{module}/
-├── _module-installer/       # Not copied to destination
-│   ├── installer.js         # Post-install logic
-├── module.yaml
-├── agents/
-├── tasks/
-├── templates/
-└── sub-modules/            # Platform-specific content
-    └── {platform}/
-        ├── injections.yaml
-        └── sub-agents/
-```
-
-## Configuration System
-
-### Collection Process
-
-Modules define prompts in `module.yaml`:
-
-```yaml
-project_name:
-  prompt: 'Project title?'
-  default: 'My Project'
-  result: '{value}'
-
-output_folder:
-  prompt: 'Output location?'
-  default: 'docs'
-  result: '{project-root}/{value}'
-
-tools:
-  prompt: 'Select tools:'
-  multi-select:
-    - 'Tool A'
-    - 'Tool B'
-```
-
-### Configuration Inheritance
-
-Core values cascade to ALL modules automatically:
-
-```yaml
-# core/config.yaml
-user_name: "Jane"
-communication_language: "English"
-
-# bmm/config.yaml (generated)
-project_name: "My App"
-tech_docs: "/path/to/docs"
-# Core Configuration Values (inherited)
-user_name: "Jane"
-communication_language: "English"
-```
-
-**Reserved Keys**: Core configuration keys cannot be redefined by other modules.
-
-### Path Placeholders
-
-- `{project-root}`: Project directory path
-- `{value}`: User input
-- `{module}`: Module name
-- `{core:field}`: Reference core config value
-
-### Config Generation Rules
-
-1. ALL installed modules get a `config.yaml` (even without prompts)
-2. Core values are ALWAYS included in module configs
-3. Module-specific values come first, core values appended
-4. Source templates are never copied, only generated configs
-
-## Platform Integration
-
-### Supported Platforms
-
-**Preferred** (Full Integration):
-
-- Claude Code
-- Cursor
-- Windsurf
-
-**Additional**:
-Cline, Roo, Rovo Dev,Auggie, GitHub Copilot, Codex, Gemini, Qwen, Trae, Kilo, Crush, iFlow
-
-### Platform Features
-
-1. **Setup Handler** (`tools/cli/installers/lib/ide/{platform}.js`)
-   - Directory creation
-   - Configuration generation
-   - Agent processing
-
-2. **Content Injection** (`sub-modules/{platform}/injections.yaml`)
-
-   ```yaml
-   injections:
-     - file: '.bmad/bmm/agents/pm.md'
-       point: 'pm-agent-instructions'
-       content: |
-         <i>Platform-specific instruction</i>
-
-   subagents:
-     source: 'sub-agents'
-     target: '.claude/agents'
-     files: ['agent.md']
-   ```
-
-3. **Interactive Config**
-   - Subagent selection
-   - Installation scope (project/user)
-   - Feature toggles
-
-### Injection System
-
-Platform-specific content without source modification:
-
-- Inject points marked in source: `<!-- IDE-INJECT-POINT:name -->`
-- Content added during installation only
-- Source files remain clean
-
-## Development Guide
-
-### Creating a Module
-
-1. **Structure**
-
-   ```
-   src/modules/mymod/
-   ├── _module-installer/
-   │   ├── installer.js
-   ├── module.yaml
-   ├── agents/
-   └── tasks/
-   ```
-
-2. **Configuration** (`module.yaml`)
-
-   ```yaml
-   code: mymod
-   name: 'My Module'
-   prompt: 'Welcome message'
-
-   setting_name:
-     prompt: 'Configure X?'
-     default: 'value'
-   ```
-
-3. **Installer** (`installer.js`)
-   ```javascript
-   async function install(options) {
-     const { projectRoot, config, installedIDEs, logger } = options;
-     // Custom logic
-     return true;
-   }
-   module.exports = { install };
-   ```
-
-### Adding Platform Support
-
-1. Create handler: `tools/cli/installers/lib/ide/myplatform.js`
-2. Extend `BaseIdeSetup` class
-3. Add sub-module: `src/modules/{mod}/sub-modules/myplatform/`
-4. Define injections and platform agents
-
-### Agent Configuration
-
-Extractable config nodes:
-
-```xml
-<agent>
-  <setting agentConfig="true">
-    Default value
-  </setting>
-</agent>
-```
-
-Generated in: `bmad/_cfg/agents/{module}-{agent}.md`
-
-## Troubleshooting
-
-### Common Issues
-
-| Issue                   | Solution                             |
-| ----------------------- | ------------------------------------ |
-| Existing installation   | Use `bmad update` or remove `.bmad/` |
-| Module not found        | Check `src/modules/` exists          |
-| Config not applied      | Verify `.bmad/{module}/config.yaml`  |
-| Missing config.yaml     | Fixed: All modules now get configs   |
-| Agent unavailable       | Check for `localskip="true"`         |
-| module-installer copied | Fixed: Now excluded from copy        |
-
-### Debug Commands
-
-```bash
-bmad install -v     # Verbose installation
-bmad status -v      # Detailed status
-```
-
-### Best Practices
-
-1. Run from project root
-2. Backup `.bmad/_cfg/` before updates
-3. Use interactive mode for guidance
-4. Review generated configs post-install
-
-## Migration from v4
-
-| v4                  | v6                   |
-| ------------------- | -------------------- |
-| Scattered files     | Centralized `.bmad/` |
-| Monolithic          | Modular              |
-| Manual config       | Interactive setup    |
-| Limited IDE support | 15+ platforms        |
-| Source modification | Clean injection      |
-
-## Technical Notes
-
-### Dependency Resolution
-
-- Direct dependencies (module → module)
-- Agent references (cross-module)
-- Template dependencies
-- Partial module installation (only required files)
-- Workflow vendoring for standalone module operation
-
-## Workflow Vendoring
-
-**Problem**: Modules that reference workflows from other modules create dependencies, forcing users to install multiple modules even when they only need one.
-
-**Solution**: Workflow vendoring allows modules to copy workflows from other modules during installation, making them fully standalone.
-
-### How It Works
-
-Agents can specify both `workflow` (source location) and `workflow-install` (destination location) in their menu items:
-
-```yaml
-menu:
-  - trigger: create-story
-    workflow: '{project-root}/.bmad/bmm/workflows/4-implementation/create-story/workflow.yaml'
-    workflow-install: '{project-root}/.bmad/bmgd/workflows/4-production/create-story/workflow.yaml'
-    description: 'Create a game feature story'
-```
-
-**During Installation:**
-
-1. **Vendoring Phase**: Before copying module files, the installer:
-   - Scans source agent YAML files for `workflow-install` attributes
-   - Copies entire workflow folders from `workflow` path to `workflow-install` path
-   - Updates vendored `workflow.yaml` files to reference target module's config
-
-2. **Compilation Phase**: When compiling agents:
-   - If `workflow-install` exists, uses its value for the `workflow` attribute
-   - `workflow-install` is build-time metadata only, never appears in final XML
-   - Compiled agent references vendored workflow location
-
-3. **Config Update**: Vendored workflows get their `config_source` updated:
-
-   ```yaml
-   # Source workflow (in bmm):
-   config_source: "{project-root}/.bmad/bmm/config.yaml"
-
-   # Vendored workflow (in bmgd):
-   config_source: "{project-root}/.bmad/bmgd/config.yaml"
-   ```
-
-**Result**: Modules become completely standalone with their own copies of needed workflows, configured for their specific use case.
-
-### Example Use Case: BMGD Module
-
-The BMad Game Development module vendors implementation workflows from BMM:
-
-- Game Dev Scrum Master agent references BMM workflows
-- During installation, workflows are copied to `bmgd/workflows/4-production/`
-- Vendored workflows use BMGD's config (with game-specific settings)
-- BMGD can be installed without BMM dependency
-
-### Benefits
-
-✅ **Module Independence** - No forced dependencies
-✅ **Clean Namespace** - Workflows live in their module
-✅ **Config Isolation** - Each module uses its own configuration
-✅ **Customization Ready** - Vendored workflows can be modified independently
-✅ **No User Confusion** - Avoid partial module installations
-
-### File Processing
-
-- Filters `localskip="true"` agents
-- Excludes `_module-installer/` directories
-- Replaces path placeholders at runtime
-- Injects activation blocks
-- Vendors cross-module workflows (see Workflow Vendoring below)
-
-### Web Bundling
-
-```bash
-bmad bundle --web           # Filter for web deployment
-npm run validate:bundles    # Validate bundles
-```

docs/v4-to-v6-upgrade.md

@@ -1,227 +0,0 @@
-# BMad v4 to v6 Upgrade Guide
-
-## Overview
-
-BMad v6 represents a complete ground-up rewrite with significant architectural changes. This guide will help you migrate your v4 project to v6.
-
----
-
-## Automatic V4 Detection
-
-When you run `npm run install:bmad` on a project with v4 installed, the installer automatically detects:
-
-- **Legacy folders**: Any folders starting with `.bmad`, `bmad` (lowercase), or `Bmad`
-- **IDE command artifacts**: Legacy bmad folders in IDE configuration directories (`.claude/commands/`, `.cursor/commands/`, etc.)
-
-### What Happens During Detection
-
-1. **Automatic Backup of v4 Modules**: All `.bmad-*` folders are moved to `v4-backup/` in your project root
-   - If a backup already exists, a timestamp is added to avoid conflicts
-   - Example: `.bmad-core` → `v4-backup/.bmad-core`
-   - Your project files and data are NOT affected
-
-2. **IDE Command Cleanup Recommended**: Legacy v4 IDE commands should be manually removed
-   - Located in IDE config folders: `.claude/commands/`, `.cursor/commands/`, etc.
-   - These old commands would still reference v4 folder structure if left in place
-   - The installer provides copy/paste terminal commands for your platform
-   - You can proceed without cleanup, but removing them prevents confusion with old v4 commands
-
----
-
-## Module Migration
-
-### Deprecated Modules
-
-| v4 Module                     | v6 Status                                        |
-| ----------------------------- | ------------------------------------------------ |
-| `.bmad-2d-phaser-game-dev`    | Integrated into BMM                              |
-| `.bmad-2d-unity-game-dev`     | Integrated into BMM                              |
-| `.bmad-godot-game-dev`        | Integrated into BMM                              |
-| `.bmad-*-game-dev` (any)      | Integrated into BMM                              |
-| `.bmad-infrastructure-devops` | Deprecated - New core devops agent coming in BMM |
-| `.bmad-creative-writing`      | Not adapted - New module releasing soon          |
-
-**Game Development**: All game development functionality has been consolidated and expanded within the BMM (BMad Method) module. Game-specific workflows now adapt to your game type and engine.
-
----
-
-## Architecture Changes
-
-### Folder Structure
-
-**v4 "Expansion Packs" Structure:**
-
-```
-your-project/
-├── .bmad-core/           # Was actually the BMad Method
-├── .bmad-game-dev/       # Separate expansion packs
-├── .bmad-creative-writing/
-└── .bmad-infrastructure-devops/
-```
-
-**v6 Unified Structure:**
-
-```
-your-project/
-└── .bmad/       # Single installation folder, default .bmad
-    ├── core/            # Real core framework (applies to all modules)
-    ├── bmm/             # BMad Method (software/game dev)
-    ├── bmb/             # BMad Builder (create agents/workflows)
-    ├── cis/             # Creative Intelligence Suite
-    └── _cfg/            # Your customizations
-        └── agents/      # Agent customization files
-```
-
-### Key Concept Changes
-
-- **v4 `.bmad-core`**: Was actually the BMad Method
-- **v6 `.bmad/core/`**: Is the real universal core framework
-- **v6 `.bmad/bmm/`**: Is the BMad Method module
-- **Module identification**: All modules now have a `config.yaml` file
-
----
-
-## Project Progress Migration
-
-### If You've Completed Planning Phase (PRD/Architecture) with the BMad Method:
-
-After running the v6 installer:
-
-1. **Run `workflow-init`** workflow to set up the guided workflow system
-2. **Specify your project level** when prompted:
-   - If you followed v4's full workflow (PRD → Architecture → Stories), select **Level 3 or 4**
-   - This tells v6 you've already completed planning and solutioning phases
-3. **Document paths**: Keep your existing paths during installation
-   - Default PRD/Architecture location: `docs/`
-   - Default stories location: `docs/sprint-artifacts/`
-   - **Accept these defaults** if you're already using them in v4
-
-> **Important**: v6 workflows can handle both sharded and unsharded documents. You don't need to restructure your existing PRD or architecture files.
-
-### If You're Mid-Development (Stories Created/Implemented)
-
-1. Complete the v6 installation as above
-2. Run `workflow-init` and specify Level 3 or 4
-3. When ready to continue development, run the **`sprint-planning`** workflow (Phase 4)
-
----
-
-## Agent Customization Migration
-
-### v4 Agent Customization
-
-In v4, you may have modified agent files directly in `.bmad-*` folders.
-
-### v6 Agent Customization
-
-**All customizations** now go in `.bmad/_cfg/agents/` using customize files:
-
-**Example: Renaming an agent and changing communication style**
-
-File: `.bmad/_cfg/agents/bmm-pm.customize.yaml`
-
-```yaml
-# Customize the PM agent
-persona:
-  name: 'Captain Jack' # Override agent name
-  role: 'Swashbuckling Product Owner'
-  communication_style: |
-    - Talk like a pirate
-    - Use nautical metaphors for software concepts
-    - Always upbeat and adventurous
-```
-
-**How it works:**
-
-- Base agent: `.bmad/bmm/agents/pm.md`
-- Customization: `.bmad/_cfg/agents/bmm-pm.customize.yaml`
-- Result: Agent uses your custom name and style, but updates don't overwrite your changes
-
----
-
-## Document Compatibility
-
-### Sharded vs Unsharded Documents
-
-**Good news**: Unlike v4, v6 workflows are **fully flexible** with document structure:
-
-- ✅ Sharded documents (split into multiple files)
-- ✅ Unsharded documents (single file per section)
-- ✅ Custom sections for your project type
-- ✅ Mixed approaches
-
-All workflow files are scanned automatically. No manual configuration needed.
-
----
-
-## Installation Steps
-
-### 1. Clone Repository
-
-```bash
-git clone https://github.com/bmad-code-org/BMAD-METHOD
-cd BMAD-METHOD
-npm install
-```
-
-### 2. Run Installer on Your v4 Project
-
-```bash
-npx bmad-method install
-```
-
-**Enter the full path to your v4 project** when prompted.
-
-### 3. Follow Interactive Prompts
-
-The installer will:
-
-1. Detect v4 installation and offer to backup `.bmad-*` folders
-2. Prompt for recommended cleanup (you can skip)
-3. Let you select modules (recommend: BMM for software and or game development)
-4. Configure core settings (name, language, etc.)
-5. Configure module-specific options
-6. Configure IDE integrations
-
-### 4. Accept Default Paths
-
-If you're using:
-
-- `docs/` for PRD and architecture
-- `docs/sprint-artifacts/` for story files
-
-**Accept these defaults** during installation.
-
-### 5. Initialize Workflow
-
-After installation:
-
-1. **Load the Analyst agent** - See your IDE-specific instructions in [docs/ide-info](./ide-info/) for how to activate agents:
-   - [Claude Code](./ide-info/claude-code.md)
-   - [Cursor](./ide-info/cursor.md)
-   - [VS Code/Windsurf](./ide-info/) - Check your IDE folder
-
-2. **Wait for the agent's menu** to appear
-
-3. **Tell the agent**: `*workflow-init` - v6 supports excellent natural language fuzzy matching, so you could also say "workflow init" or "please init the workflow"
-
-Since you are migrating an existing project from v4, it's most likely **Level 3 or 4** you will want to suggest when asked - if you've already completed PRD/architecture in v4.
-
----
-
-## Post-Migration Checklist
-
-- [ ] v4 folders backed up to `v4-backup/`
-- [ ] v6 installed to `.bmad/` folder
-- [ ] `workflow-init` run with correct project level selected
-- [ ] Agent customizations migrated to `.bmad/_cfg/agents/` if needed
-- [ ] IDE integration working (test by listing agents)
-- [ ] For active development: `sprint-planning` workflow executed
-
----
-
-## Getting Help
-
-- **Discord**: [Join the BMad Community](https://discord.gg/gk8jAdXWmj)
-- **Issues**: [GitHub Issue Tracker](https://github.com/bmad-code-org/BMAD-METHOD/issues)
-- **Docs**: Check `.bmad/docs/` in your installation for IDE-specific instructions

docs/v6-open-items.md

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

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

@@ -1,473 +0,0 @@
-# Using BMad Web Bundles in Gemini Gems & Custom GPTs
-
-Web bundles package BMad agents as self-contained XML files that work in Gemini Gems and Custom GPTs. Everything the agent needs - instructions, workflows, dependencies - is bundled into a single file.
-
-## What Are Web Bundles?
-
-Web bundles are standalone XML files containing:
-
-- Complete agent persona and instructions
-- All workflows and dependencies
-- Interactive menu system
-- Party mode for multi-agent collaboration
-- No external files required
-
-**Perfect for:** Uploading a single file to a Gemini GEM or Custom GPT to use BMad Method from the Web, generally at a huge cost savings, at the expense of some quality and convenience of using locally.
-
-## Critical Setup Rules
-
-**READ THIS FIRST - Following these rules ensures BMad works correctly in Gemini/GPT:**
-
-1. **ONE file per Gem/GPT** - Upload exactly ONE XML file per Gemini Gem or Custom GPT instance. Do NOT combine multiple agent files.
-
-2. **Use the setup instructions** - When creating your Gem/GPT, you MUST add the configuration prompt (shown in Quick Start below) so it knows how to read the XML file.
-
-3. **Enable Canvas/Code Execution** - This is ESSENTIAL for document generation workflows (PRD, Architecture, etc.). Enable this in your Gem/GPT settings.
-
-4. **Gemini Gems are strongly preferred** - They work significantly better than Custom GPTs for BMad workflows.
-
-5. **Team bundles = Gemini 2.5 Pro+ only** - Team bundles (multiple agents) have terrible performance in Custom GPTs due to context limits. Only use them with Gemini 2.5 Pro or higher.
-
-6. **Create separate Gems for each agent** - Make a PM Gem, an Architect Gem, a Developer Gem, etc. Don't try to combine them (except via official team bundles).
-
-## Quick Start
-
-### 1. Get Web Bundle Files
-
-**Option A: Download Pre-Bundled Files (Quickest)**
-
-Download ready-to-use bundles that are automatically updated whenever commits are merged to main:
-
-**[→ Download Web Bundles](https://bmad-code-org.github.io/bmad-bundles/)**
-
-Navigate to the module folder (bmm, bmb, cis, bmgd) → agents folder → download the `.xml` file you need. These bundles are automatically regenerated and deployed with every commit to the main branch, ensuring you always have the latest version.
-
-**Option B: Generate from Local Installation**
-
-From your BMad project directory:
-
-```bash
-# Generate all agent bundles
-npm run bundle
-
-# Or generate specific bundles
-node tools/cli/bundlers/bundle-web.js module bmm
-node tools/cli/bundlers/bundle-web.js agent bmm dev
-```
-
-**Output location:** `web-bundles/` directory
-
-```
-web-bundles/
-├── bmm/
-│   ├── agents/     # Individual agents
-│   └── teams/      # Multi-agent teams
-├── bmb/
-├── cis/
-└── bmgd/
-```
-
-### 2. Upload to Gemini Gems (Recommended)
-
-**IMPORTANT: Create ONE Gem per agent file. Do NOT upload multiple agent files to a single Gem.**
-
-**Create a Gem:**
-
-1. Go to [Gemini Gem manager](https://gemini.google.com/gems/view)
-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/_cfg/agents/<agent>.customize.yaml`
-2. Rebuild: `npx bmad-method build <agent-name>`
-3. Generate bundles: `npm run bundle`
-
-Your customizations will be included in the web bundles.
-
-**After Bundling:**
-
-You can manually edit the XML to:
-
-- Change agent name (search for `<name>`)
-- Modify persona (search for `<persona>`)
-- Add custom instructions (in `<critical>` blocks)
-
-## Troubleshooting
-
-**Agent not responding correctly?**
-
-- Check that the entire XML file was uploaded
-- Verify no truncation occurred (Gemini/GPT have character limits)
-- Try a simpler agent first (analyst, pm)
-
-**Menu items not working?**
-
-- Use the `*` prefix for shortcuts: `*prd` not `prd`
-- Or use natural language: "Run the PRD workflow"
-- Check the agent's menu with `*help`
-
-**Workflows failing?**
-
-- Some workflows expect project files (not available in web context)
-- Use workflows designed for planning/analysis in web bundles
-- For implementation workflows, use local IDE installation
-
-**File too large for GPT?**
-
-- Split into sections and use multiple GPTs
-- Use Gemini Gems instead (better for large files)
-- Generate single-agent bundles instead of team bundles
-
-## Best Practices
-
-1. **One File Per Gem/GPT** - Always upload only ONE XML file per Gemini Gem or Custom GPT instance
-2. **Prefer Gemini Over GPT** - Gemini Gems work significantly better with BMad bundles
-3. **Enable Canvas/Code Execution** - Essential for document generation workflows (PRD, Architecture, etc.)
-4. **Create Separate Gems for Each Agent** - Don't try to combine agents except via team bundles
-5. **Team Bundles = Gemini 2.5 Pro+ Only** - Never use team bundles with Custom GPTs
-6. **Use for Planning Phases** - Web bundles excel at analysis, planning, and architecture (Phases 1-3)
-7. **Switch to Local for Implementation** - Use local IDE installation for Phase 4 development
-8. **Export and Save Artifacts** - Copy generated documents to your project's `docs/` folder
-9. **Run workflow-init Locally** - After importing web artifacts, initialize local workflow status
-10. **Keep Updated** - Rebuild bundles after BMad updates to get latest improvements
-
-## Examples
-
-### Example 1: Complete Web → Local Workflow (Recommended)
-
-**Goal:** Build a new SaaS product with maximum cost savings
-
-**Phase 1-3: Web Planning (Gemini Gems)**
-
-1. **Download bundles:**
-   - `bmm/agents/analyst.xml`
-   - `bmm/agents/pm.xml`
-   - `bmm/agents/architect.xml`
-   - `bmm/agents/ux-designer.xml`
-
-2. **Create 4 separate Gemini Gems** (one per agent, enable Code Execution)
-
-3. **Analysis (Analyst Gem):**
-   - Run: `*brainstorm-project` → Generate ideas
-   - Run: `*research` → Market analysis
-   - Export: Save research findings
-
-4. **Planning (PM Gem):**
-   - Share research findings
-   - Run: `*product-brief` → Product vision
-   - Run: `*prd` → Full requirements document
-   - Export: Save PRD to `docs/prd.md`
-
-5. **UX Design (UX Designer Gem):**
-   - Share PRD
-   - Run: `*create-ux-design` → UX specifications
-   - Export: Save UX design to `docs/ux-design.md`
-
-6. **Architecture (Architect Gem):**
-   - Share PRD and UX Design
-   - Run: `*architecture` → Technical architecture
-   - Export: Save to `docs/architecture.md`
-
-**Phase 4: Local Implementation**
-
-7. **Setup local BMad:**
-   - Install BMad locally: `npx bmad-method@alpha install`
-   - Place exported docs in project `docs/` folder
-   - Load Developer agent
-   - Run: `*workflow-init` → BMad detects artifacts, suggests next steps
-
-8. **Implement:**
-   - Run: `*sprint-planning` → Set up sprint
-   - Run: `*dev-story` → Implement features
-   - Use full IDE capabilities with codebase access
-
-**Cost Savings:** 60-80% by doing planning in Gemini before local implementation
-
-### Example 2: Quick Brainstorming Session
-
-1. Download `cis/agents/brainstorming-coach.xml`
-2. Create Gemini Gem with Code Execution enabled
-3. Run: `*brainstorming`
-4. Choose technique (e.g., SCAMPER, Mind Mapping)
-5. Generate and refine ideas
-6. Export results for team review
-
-### Example 3: Architecture Review
-
-1. Download `bmm/agents/architect.xml`
-2. Create Gemini Gem (enable Code Execution)
-3. Paste existing PRD into conversation
-4. Run: `*architecture`
-5. Collaborate on technical decisions
-6. Export architecture document to `docs/architecture.md`
-
-## Next Steps
-
-- **[Agent Customization Guide](./agent-customization-guide.md)** - Customize before bundling
-- **[BMM Documentation](../src/modules/bmm/docs/README.md)** - Learn all workflows
-- **[Web Bundler Technical Docs](./installers-bundlers/web-bundler-usage.md)** - Advanced bundling options
-- **[Contributing Guide](../CONTRIBUTING.md)** - Help improve web bundles
-
-## Resources
-
-- **[Google AI Studio](https://aistudio.google.com/)** - Create Gemini Gems
-- **[Custom GPTs](https://chat.openai.com/gpts)** - Build Custom GPTs
-- **[BMad Discord](https://discord.gg/gk8jAdXWmj)** - Get help and share your Gems/GPTs

eslint.config.mjs

@@ -1,147 +0,0 @@
-import js from '@eslint/js';
-import eslintConfigPrettier from 'eslint-config-prettier/flat';
-import nodePlugin from 'eslint-plugin-n';
-import unicorn from 'eslint-plugin-unicorn';
-import yml from 'eslint-plugin-yml';
-
-export default [
-  // Global ignores for files/folders that should not be linted
-  {
-    ignores: [
-      'dist/**',
-      'coverage/**',
-      '**/*.min.js',
-      'test/template-test-generator/**',
-      'test/template-test-generator/**/*.js',
-      'test/template-test-generator/**/*.md',
-      'test/fixtures/**',
-      'test/fixtures/**/*.yaml',
-      '.bmad/**',
-      '.bmad*/**',
-      // 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/**',
-    ],
-  },
-
-  // Base JavaScript recommended rules
-  js.configs.recommended,
-
-  // Node.js rules
-  ...nodePlugin.configs['flat/mixed-esm-and-cjs'],
-
-  // Unicorn rules (modern best practices)
-  unicorn.configs.recommended,
-
-  // YAML linting
-  ...yml.configs['flat/recommended'],
-
-  // Place Prettier last to disable conflicting stylistic rules
-  eslintConfigPrettier,
-
-  // Project-specific tweaks
-  {
-    rules: {
-      // Allow console for CLI tools in this repo
-      'no-console': 'off',
-      // Enforce .yaml file extension for consistency
-      'yml/file-extension': [
-        'error',
-        {
-          extension: 'yaml',
-          caseSensitive: true,
-        },
-      ],
-      // Prefer double quotes in YAML wherever quoting is used, but allow the other to avoid escapes
-      'yml/quotes': [
-        'error',
-        {
-          prefer: 'double',
-          avoidEscape: true,
-        },
-      ],
-      // Relax some Unicorn rules that are too opinionated for this codebase
-      'unicorn/prevent-abbreviations': 'off',
-      'unicorn/no-null': 'off',
-    },
-  },
-
-  // CLI/CommonJS scripts under tools/** and test/**
-  {
-    files: ['tools/**/*.js', 'test/**/*.js'],
-    rules: {
-      // Allow CommonJS patterns for Node CLI scripts
-      'unicorn/prefer-module': 'off',
-      'unicorn/import-style': 'off',
-      'unicorn/no-process-exit': 'off',
-      'n/no-process-exit': 'off',
-      'unicorn/no-await-expression-member': 'off',
-      'unicorn/prefer-top-level-await': 'off',
-      // Avoid failing CI on incidental unused vars in internal scripts
-      'no-unused-vars': 'off',
-      // Reduce style-only churn in internal tools
-      'unicorn/prefer-ternary': 'off',
-      'unicorn/filename-case': 'off',
-      'unicorn/no-array-reduce': 'off',
-      'unicorn/no-array-callback-reference': 'off',
-      'unicorn/consistent-function-scoping': 'off',
-      'n/no-extraneous-require': 'off',
-      'n/no-extraneous-import': 'off',
-      'n/no-unpublished-require': 'off',
-      'n/no-unpublished-import': 'off',
-      // Some scripts intentionally use globals provided at runtime
-      'no-undef': 'off',
-      // Additional relaxed rules for legacy/internal scripts
-      'no-useless-catch': 'off',
-      'unicorn/prefer-number-properties': 'off',
-      'no-unreachable': 'off',
-    },
-  },
-
-  // Module installer scripts use CommonJS for compatibility
-  {
-    files: ['**/_module-installer/**/*.js'],
-    rules: {
-      // Allow CommonJS patterns for installer scripts
-      'unicorn/prefer-module': 'off',
-      'n/no-missing-require': 'off',
-      'n/no-unpublished-require': 'off',
-    },
-  },
-
-  // ESLint config file should not be checked for publish-related Node rules
-  {
-    files: ['eslint.config.mjs'],
-    rules: {
-      'n/no-unpublished-import': 'off',
-    },
-  },
-
-  // GitHub workflow files in this repo may use empty mapping values
-  {
-    files: ['.github/workflows/**/*.yaml'],
-    rules: {
-      'yml/no-empty-mapping-value': 'off',
-    },
-  },
-
-  // Other GitHub YAML files may intentionally use empty values and reserved filenames
-  {
-    files: ['.github/**/*.yaml'],
-    rules: {
-      'yml/no-empty-mapping-value': 'off',
-      'unicorn/filename-case': 'off',
-    },
-  },
-];

package.json

@@ -1,110 +0,0 @@
-{
-  "$schema": "https://json.schemastore.org/package.json",
-  "name": "bmad-method",
-  "version": "6.0.0-alpha.16",
-  "description": "Breakthrough Method of Agile AI-driven Development",
-  "keywords": [
-    "agile",
-    "ai",
-    "orchestrator",
-    "development",
-    "methodology",
-    "agents",
-    "bmad"
-  ],
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/bmad-code-org/BMAD-METHOD.git"
-  },
-  "license": "MIT",
-  "author": "Brian (BMad) Madison",
-  "main": "tools/cli/bmad-cli.js",
-  "bin": {
-    "bmad": "tools/bmad-npx-wrapper.js",
-    "bmad-method": "tools/bmad-npx-wrapper.js"
-  },
-  "scripts": {
-    "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",
-    "flatten": "node tools/flattener/main.js",
-    "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:bundles && npm run validate:schemas && npm run lint && npm run lint:md && npm run format:check",
-    "test:coverage": "c8 --reporter=text --reporter=html npm run test:schemas",
-    "test:install": "node test/test-installation-components.js",
-    "test:schemas": "node test/test-agent-schema.js",
-    "validate:bundles": "node tools/validate-bundles.js",
-    "validate:schemas": "node tools/validate-agent-schema.js"
-  },
-  "lint-staged": {
-    "*.{js,cjs,mjs}": [
-      "npm run lint:fix",
-      "npm run format:fix"
-    ],
-    "*.yaml": [
-      "eslint --fix",
-      "npm run format:fix"
-    ],
-    "*.json": [
-      "npm run format:fix"
-    ],
-    "*.md": [
-      "markdownlint-cli2",
-      "npm run format:fix"
-    ]
-  },
-  "dependencies": {
-    "@kayvan/markdown-tree-parser": "^1.6.1",
-    "boxen": "^5.1.2",
-    "chalk": "^4.1.2",
-    "cli-table3": "^0.6.5",
-    "commander": "^14.0.0",
-    "csv-parse": "^6.1.0",
-    "figlet": "^1.8.0",
-    "fs-extra": "^11.3.0",
-    "glob": "^11.0.3",
-    "ignore": "^7.0.5",
-    "inquirer": "^8.2.6",
-    "js-yaml": "^4.1.0",
-    "ora": "^5.4.1",
-    "semver": "^7.6.3",
-    "wrap-ansi": "^7.0.0",
-    "xml2js": "^0.6.2",
-    "yaml": "^2.7.0"
-  },
-  "devDependencies": {
-    "@eslint/js": "^9.33.0",
-    "c8": "^10.1.3",
-    "eslint": "^9.33.0",
-    "eslint-config-prettier": "^10.1.8",
-    "eslint-plugin-n": "^17.21.3",
-    "eslint-plugin-unicorn": "^60.0.0",
-    "eslint-plugin-yml": "^1.18.0",
-    "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",
-    "yaml-eslint-parser": "^1.2.3",
-    "yaml-lint": "^1.7.0",
-    "zod": "^4.1.12"
-  },
-  "engines": {
-    "node": ">=20.0.0"
-  },
-  "publishConfig": {
-    "access": "public"
-  }
-}

prettier.config.mjs

@@ -1,32 +0,0 @@
-export default {
-  $schema: 'https://json.schemastore.org/prettierrc',
-  printWidth: 140,
-  tabWidth: 2,
-  useTabs: false,
-  semi: true,
-  singleQuote: true,
-  trailingComma: 'all',
-  bracketSpacing: true,
-  arrowParens: 'always',
-  endOfLine: 'lf',
-  proseWrap: 'preserve',
-  overrides: [
-    {
-      files: ['*.md'],
-      options: { proseWrap: 'preserve' },
-    },
-    {
-      files: ['*.yaml'],
-      options: { singleQuote: false },
-    },
-    {
-      files: ['*.json', '*.jsonc'],
-      options: { singleQuote: false },
-    },
-    {
-      files: ['*.cjs'],
-      options: { parser: 'babel' },
-    },
-  ],
-  plugins: ['prettier-plugin-packagejson'],
-};

src/core/_module-installer/installer.js

@@ -1,60 +0,0 @@
-const chalk = require('chalk');
-
-/**
- * Core Module Installer
- * Standard module installer function that executes after IDE installations
- *
- * @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 {Array<string>} options.installedIDEs - Array of IDE codes that were installed
- * @param {Object} options.logger - Logger instance for output
- * @returns {Promise<boolean>} - Success status
- */
-async function install(options) {
-  const { projectRoot, config, installedIDEs, logger } = options;
-
-  try {
-    logger.log(chalk.blue('🏗️  Installing Core Module...'));
-
-    // Core agent configs are created by the main installer's createAgentConfigs method
-    // No need to create them here - they'll be handled along with all other agents
-
-    // Handle IDE-specific configurations if needed
-    if (installedIDEs && installedIDEs.length > 0) {
-      logger.log(chalk.cyan(`Configuring Core for IDEs: ${installedIDEs.join(', ')}`));
-
-      // Add any IDE-specific Core configurations here
-      for (const ide of installedIDEs) {
-        await configureForIDE(ide, projectRoot, config, logger);
-      }
-    }
-
-    logger.log(chalk.green('✓ Core Module installation complete'));
-    return true;
-  } catch (error) {
-    logger.error(chalk.red(`Error installing Core module: ${error.message}`));
-    return false;
-  }
-}
-
-/**
- * Configure Core module for specific IDE
- * @private
- */
-async function configureForIDE(ide) {
-  // Add IDE-specific configurations here
-  switch (ide) {
-    case 'claude-code': {
-      // Claude Code specific Core configurations
-      break;
-    }
-    // Add more IDEs as needed
-    default: {
-      // No specific configuration needed
-      break;
-    }
-  }
-}
-
-module.exports = { install };

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

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

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

@@ -1,113 +0,0 @@
-<agent id=".bmad/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/..." 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/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/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/core/workflows/party-mode/workflow.md">Enter group chat with all agents
-      simultaneously</item>
-    <item cmd="*advanced-elicitation" task=".bmad/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,32 +0,0 @@
-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?"
-  default: "BMad"
-  result: "{value}"
-
-communication_language:
-  prompt: "Preferred Chat Language/Style? (English, Mandarin, English Pirate, etc...)"
-  default: "English"
-  result: "{value}"
-
-document_output_language:
-  prompt: "Preferred Document Output Language?"
-  default: "{communication_language}"
-  result: "{value}"
-
-agent_sidecar_folder:
-  prompt: "Where should users agent sidecar memory folders be stored?"
-  default: ".bmad-user-memory"
-  result: "{project-root}/{value}"
-
-output_folder:
-  prompt: "Where should AI Generated Artifacts be saved across all modules?"
-  default: "docs"
-  result: "{project-root}/{value}"
-
-install_user_docs:
-  prompt: "Install user documentation and optimized agent intelligence to each selected modules docs folder?"
-  default: true
-  result: "{value}"

src/core/resources/excalidraw/README.md

@@ -1,160 +0,0 @@
-# Core Excalidraw Resources
-
-Universal knowledge for creating Excalidraw diagrams. All agents that create Excalidraw files should reference these resources.
-
-## Purpose
-
-Provides the **HOW** (universal knowledge) while agents provide the **WHAT** (domain-specific application).
-
-**Core = "How to create Excalidraw elements"**
-
-- How to group shapes with text labels
-- How to calculate text width
-- How to create arrows with proper bindings
-- How to validate JSON syntax
-- Base structure and primitives
-
-**Agents = "What diagrams to create"**
-
-- Frame Expert (BMM): Technical flowcharts, architecture diagrams, wireframes
-- Presentation Master (CIS): Pitch decks, creative visuals, Rube Goldberg machines
-- Tech Writer (BMM): Documentation diagrams, concept explanations
-
-## Files in This Directory
-
-### excalidraw-helpers.md
-
-**Universal element creation patterns**
-
-- Text width calculation
-- Element grouping rules (shapes + labels)
-- Grid alignment
-- Arrow creation (straight, elbow)
-- Theme application
-- Validation checklist
-- Optimization rules
-
-**Agents reference this to:**
-
-- Create properly grouped shapes
-- Calculate text dimensions
-- Connect elements with arrows
-- Ensure valid structure
-
-### validate-json-instructions.md
-
-**Universal JSON validation process**
-
-- How to validate Excalidraw JSON
-- Common errors and fixes
-- Workflow integration
-- Error recovery
-
-**Agents reference this to:**
-
-- Validate files after creation
-- Fix syntax errors
-- Ensure files can be opened in Excalidraw
-
-### library-loader.md (Future)
-
-**How to load external .excalidrawlib files**
-
-- Programmatic library loading
-- Community library integration
-- Custom library management
-
-**Status:** To be developed when implementing external library support.
-
-## How Agents Use These Resources
-
-### Example: Frame Expert (Technical Diagrams)
-
-```yaml
-# workflows/diagrams/create-flowchart/workflow.yaml
-helpers: '{project-root}/.bmad/core/resources/excalidraw/excalidraw-helpers.md'
-json_validation: '{project-root}/.bmad/core/resources/excalidraw/validate-json-instructions.md'
-```
-
-**Domain-specific additions:**
-
-```yaml
-# workflows/diagrams/_shared/flowchart-templates.yaml
-flowchart:
-  start_node:
-    type: ellipse
-    width: 120
-    height: 60
-  process_box:
-    type: rectangle
-    width: 160
-    height: 80
-  decision_diamond:
-    type: diamond
-    width: 140
-    height: 100
-```
-
-### Example: Presentation Master (Creative Visuals)
-
-```yaml
-# workflows/create-visual-metaphor/workflow.yaml
-helpers: '{project-root}/.bmad/core/resources/excalidraw/excalidraw-helpers.md'
-json_validation: '{project-root}/.bmad/core/resources/excalidraw/validate-json-instructions.md'
-```
-
-**Domain-specific additions:**
-
-```yaml
-# workflows/_shared/creative-templates.yaml
-rube_goldberg:
-  whimsical_connector:
-    type: arrow
-    strokeStyle: dashed
-    roughness: 2
-  playful_box:
-    type: rectangle
-    roundness: 12
-```
-
-## What Doesn't Belong in Core
-
-**Domain-Specific Elements:**
-
-- Flowchart-specific templates (belongs in Frame Expert)
-- Pitch deck layouts (belongs in Presentation Master)
-- Documentation-specific styles (belongs in Tech Writer)
-
-**Agent Workflows:**
-
-- How to create a flowchart (Frame Expert workflow)
-- How to create a pitch deck (Presentation Master workflow)
-- Step-by-step diagram creation (agent-specific)
-
-**Theming:**
-
-- Currently in agent workflows
-- **Future:** Will be refactored to core as user-configurable themes
-
-## Architecture Principle
-
-**Single Source of Truth:**
-
-- Core holds universal knowledge
-- Agents reference core, don't duplicate
-- Updates to core benefit all agents
-- Agents specialize with domain knowledge
-
-**DRY (Don't Repeat Yourself):**
-
-- Element creation logic: ONCE in core
-- Text width calculation: ONCE in core
-- Validation process: ONCE in core
-- Arrow binding patterns: ONCE in core
-
-## Future Enhancements
-
-1. **External Library Loader** - Load .excalidrawlib files from libraries.excalidraw.com
-2. **Theme Management** - User-configurable color themes saved in core
-3. **Component Library** - Shared reusable components across agents
-4. **Layout Algorithms** - Auto-layout helpers for positioning elements

src/core/resources/excalidraw/excalidraw-helpers.md

@@ -1,127 +0,0 @@
-# Excalidraw Element Creation Guidelines
-
-## Text Width Calculation
-
-For text elements inside shapes (labels):
-
-```
-text_width = (text.length × fontSize × 0.6) + 20
-```
-
-Round to nearest 10 for grid alignment.
-
-## Element Grouping Rules
-
-**CRITICAL:** When creating shapes with labels:
-
-1. Generate unique IDs:
-   - `shape-id` for the shape
-   - `text-id` for the text
-   - `group-id` for the group
-
-2. Shape element must have:
-   - `groupIds: [group-id]`
-   - `boundElements: [{type: "text", id: text-id}]`
-
-3. Text element must have:
-   - `containerId: shape-id`
-   - `groupIds: [group-id]` (SAME as shape)
-   - `textAlign: "center"`
-   - `verticalAlign: "middle"`
-   - `width: calculated_width`
-
-## Grid Alignment
-
-- Snap all `x`, `y` coordinates to 20px grid
-- Formula: `Math.round(value / 20) * 20`
-- Spacing between elements: 60px minimum
-
-## Arrow Creation
-
-### Straight Arrows
-
-Use for forward flow (left-to-right, top-to-bottom):
-
-```json
-{
-  "type": "arrow",
-  "startBinding": {
-    "elementId": "source-shape-id",
-    "focus": 0,
-    "gap": 10
-  },
-  "endBinding": {
-    "elementId": "target-shape-id",
-    "focus": 0,
-    "gap": 10
-  },
-  "points": [[0, 0], [distance_x, distance_y]]
-}
-```
-
-### Elbow Arrows
-
-Use for upward flow, backward flow, or complex routing:
-
-```json
-{
-  "type": "arrow",
-  "startBinding": {...},
-  "endBinding": {...},
-  "points": [
-    [0, 0],
-    [intermediate_x, 0],
-    [intermediate_x, intermediate_y],
-    [final_x, final_y]
-  ],
-  "elbowed": true
-}
-```
-
-### Update Connected Shapes
-
-After creating arrow, update `boundElements` on both connected shapes:
-
-```json
-{
-  "id": "shape-id",
-  "boundElements": [
-    { "type": "text", "id": "text-id" },
-    { "type": "arrow", "id": "arrow-id" }
-  ]
-}
-```
-
-## Theme Application
-
-Theme colors should be applied consistently:
-
-- **Shapes**: `backgroundColor` from theme primary fill
-- **Borders**: `strokeColor` from theme accent
-- **Text**: `strokeColor` = "#1e1e1e" (dark text)
-- **Arrows**: `strokeColor` from theme accent
-
-## Validation Checklist
-
-Before saving, verify:
-
-- [ ] All shapes with labels have matching `groupIds`
-- [ ] All text elements have `containerId` pointing to parent shape
-- [ ] Text width calculated properly (no cutoff)
-- [ ] Text alignment set (`textAlign` + `verticalAlign`)
-- [ ] All elements snapped to 20px grid
-- [ ] All arrows have `startBinding` and `endBinding`
-- [ ] `boundElements` array updated on connected shapes
-- [ ] Theme colors applied consistently
-- [ ] No metadata or history in final output
-- [ ] All IDs are unique
-
-## Optimization
-
-Remove from final output:
-
-- `appState` object
-- `files` object (unless images used)
-- All elements with `isDeleted: true`
-- Unused library items
-- Version history

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

@@ -1,50 +0,0 @@
-# External Library Loader
-
-**Status:** Placeholder for future implementation
-
-## Purpose
-
-Load external .excalidrawlib files from <https://libraries.excalidraw.com> or custom sources.
-
-## Planned Capabilities
-
-- Load libraries by URL
-- Load libraries from local files
-- Merge multiple libraries
-- Filter library components
-- Cache loaded libraries
-
-## API Reference
-
-Will document how to use:
-
-- `importLibrary(url)` - Load library from URL
-- `loadSceneOrLibraryFromBlob()` - Load from file
-- `mergeLibraryItems()` - Combine libraries
-
-## Usage Example
-
-```yaml
-# Future workflow.yaml structure
-libraries:
-  - url: 'https://libraries.excalidraw.com/libraries/...'
-    filter: ['aws', 'cloud']
-  - path: '{project-root}/_data/custom-library.excalidrawlib'
-```
-
-## Implementation Notes
-
-This will be developed when agents need to leverage the extensive library ecosystem available at <https://libraries.excalidraw.com>.
-
-Hundreds of pre-built component libraries exist for:
-
-- AWS/Cloud icons
-- UI/UX components
-- Business diagrams
-- Mind map shapes
-- Floor plans
-- And much more...
-
-## User Configuration
-
-Future: Users will be able to configure favorite libraries in their BMAD config for automatic loading.

src/core/resources/excalidraw/validate-json-instructions.md

@@ -1,79 +0,0 @@
-# JSON Validation Instructions
-
-## Purpose
-
-Validate Excalidraw JSON files after saving to catch syntax errors (missing commas, brackets, quotes).
-
-## How to Validate
-
-Use Node.js built-in JSON parsing to validate the file:
-
-```bash
-node -e "JSON.parse(require('fs').readFileSync('FILE_PATH', 'utf8')); console.log('✓ Valid JSON')"
-```
-
-Replace `FILE_PATH` with the actual file path.
-
-## Exit Codes
-
-- Exit code 0 = Valid JSON
-- Exit code 1 = Invalid JSON (syntax error)
-
-## Error Output
-
-If invalid, Node.js will output:
-
-- Error message with description
-- Position in file where error occurred
-- Line and column information (if available)
-
-## Common Errors and Fixes
-
-### Missing Comma
-
-```
-SyntaxError: Expected ',' or '}' after property value
-```
-
-**Fix:** Add comma after the property value
-
-### Missing Bracket/Brace
-
-```
-SyntaxError: Unexpected end of JSON input
-```
-
-**Fix:** Add missing closing bracket `]` or brace `}`
-
-### Extra Comma (Trailing)
-
-```
-SyntaxError: Unexpected token ,
-```
-
-**Fix:** Remove the trailing comma before `]` or `}`
-
-### Missing Quote
-
-```
-SyntaxError: Unexpected token
-```
-
-**Fix:** Add missing quote around string value
-
-## Workflow Integration
-
-After saving an Excalidraw file, run validation:
-
-1. Save the file
-2. Run: `node -e "JSON.parse(require('fs').readFileSync('{{save_location}}', 'utf8')); console.log('✓ Valid JSON')"`
-3. If validation fails:
-   - Read the error message for line/position
-   - Open the file at that location
-   - Fix the syntax error
-   - Save and re-validate
-4. Repeat until validation passes
-
-## Critical Rule
-
-**NEVER delete the file due to validation errors - always fix the syntax error at the reported location.**

src/core/tasks/advanced-elicitation-methods.csv

@@ -1,51 +0,0 @@
-num,category,method_name,description,output_pattern
-1,collaboration,Stakeholder Round Table,Convene multiple personas to contribute diverse perspectives - essential for requirements gathering and finding balanced solutions across competing interests,perspectives → synthesis → alignment
-2,collaboration,Expert Panel Review,Assemble domain experts for deep specialized analysis - ideal when technical depth and peer review quality are needed,expert views → consensus → recommendations
-3,collaboration,Debate Club Showdown,Two personas argue opposing positions while a moderator scores points - great for exploring controversial decisions and finding middle ground,thesis → antithesis → synthesis
-4,collaboration,User Persona Focus Group,Gather your product's user personas to react to proposals and share frustrations - essential for validating features and discovering unmet needs,reactions → concerns → priorities
-5,collaboration,Time Traveler Council,Past-you and future-you advise present-you on decisions - powerful for gaining perspective on long-term consequences vs short-term pressures,past wisdom → present choice → future impact
-6,collaboration,Cross-Functional War Room,Product manager + engineer + designer tackle a problem together - reveals trade-offs between feasibility desirability and viability,constraints → trade-offs → balanced solution
-7,collaboration,Mentor and Apprentice,Senior expert teaches junior while junior asks naive questions - surfaces hidden assumptions through teaching,explanation → questions → deeper understanding
-8,collaboration,Good Cop Bad Cop,Supportive persona and critical persona alternate - finds both strengths to build on and weaknesses to address,encouragement → criticism → balanced view
-9,collaboration,Improv Yes-And,Multiple personas build on each other's ideas without blocking - generates unexpected creative directions through collaborative building,idea → build → build → surprising result
-10,collaboration,Customer Support Theater,Angry customer and support rep roleplay to find pain points - reveals real user frustrations and service gaps,complaint → investigation → resolution → prevention
-11,advanced,Tree of Thoughts,Explore multiple reasoning paths simultaneously then evaluate and select the best - perfect for complex problems with multiple valid approaches,paths → evaluation → selection
-12,advanced,Graph of Thoughts,Model reasoning as an interconnected network of ideas to reveal hidden relationships - ideal for systems thinking and discovering emergent patterns,nodes → connections → patterns
-13,advanced,Thread of Thought,Maintain coherent reasoning across long contexts by weaving a continuous narrative thread - essential for RAG systems and maintaining consistency,context → thread → synthesis
-14,advanced,Self-Consistency Validation,Generate multiple independent approaches then compare for consistency - crucial for high-stakes decisions where verification matters,approaches → comparison → consensus
-15,advanced,Meta-Prompting Analysis,Step back to analyze the approach structure and methodology itself - valuable for optimizing prompts and improving problem-solving,current → analysis → optimization
-16,advanced,Reasoning via Planning,Build a reasoning tree guided by world models and goal states - excellent for strategic planning and sequential decision-making,model → planning → strategy
-17,competitive,Red Team vs Blue Team,Adversarial attack-defend analysis to find vulnerabilities - critical for security testing and building robust solutions,defense → attack → hardening
-18,competitive,Shark Tank Pitch,Entrepreneur pitches to skeptical investors who poke holes - stress-tests business viability and forces clarity on value proposition,pitch → challenges → refinement
-19,competitive,Code Review Gauntlet,Senior devs with different philosophies review the same code - surfaces style debates and finds consensus on best practices,reviews → debates → standards
-20,technical,Architecture Decision Records,Multiple architect personas propose and debate architectural choices with explicit trade-offs - ensures decisions are well-reasoned and documented,options → trade-offs → decision → rationale
-21,technical,Rubber Duck Debugging Evolved,Explain your code to progressively more technical ducks until you find the bug - forces clarity at multiple abstraction levels,simple → detailed → technical → aha
-22,technical,Algorithm Olympics,Multiple approaches compete on the same problem with benchmarks - finds optimal solution through direct comparison,implementations → benchmarks → winner
-23,technical,Security Audit Personas,Hacker + defender + auditor examine system from different threat models - comprehensive security review from multiple angles,vulnerabilities → defenses → compliance
-24,technical,Performance Profiler Panel,Database expert + frontend specialist + DevOps engineer diagnose slowness - finds bottlenecks across the full stack,symptoms → analysis → optimizations
-25,creative,SCAMPER Method,Apply seven creativity lenses (Substitute/Combine/Adapt/Modify/Put/Eliminate/Reverse) - systematic ideation for product innovation,S→C→A→M→P→E→R
-26,creative,Reverse Engineering,Work backwards from desired outcome to find implementation path - powerful for goal achievement and understanding endpoints,end state → steps backward → path forward
-27,creative,What If Scenarios,Explore alternative realities to understand possibilities and implications - valuable for contingency planning and exploration,scenarios → implications → insights
-28,creative,Random Input Stimulus,Inject unrelated concepts to spark unexpected connections - breaks creative blocks through forced lateral thinking,random word → associations → novel ideas
-29,creative,Exquisite Corpse Brainstorm,Each persona adds to the idea seeing only the previous contribution - generates surprising combinations through constrained collaboration,contribution → handoff → contribution → surprise
-30,creative,Genre Mashup,Combine two unrelated domains to find fresh approaches - innovation through unexpected cross-pollination,domain A + domain B → hybrid insights
-31,research,Literature Review Personas,Optimist researcher + skeptic researcher + synthesizer review sources - balanced assessment of evidence quality,sources → critiques → synthesis
-32,research,Thesis Defense Simulation,Student defends hypothesis against committee with different concerns - stress-tests research methodology and conclusions,thesis → challenges → defense → refinements
-33,research,Comparative Analysis Matrix,Multiple analysts evaluate options against weighted criteria - structured decision-making with explicit scoring,options → criteria → scores → recommendation
-34,risk,Pre-mortem Analysis,Imagine future failure then work backwards to prevent it - powerful technique for risk mitigation before major launches,failure scenario → causes → prevention
-35,risk,Failure Mode Analysis,Systematically explore how each component could fail - critical for reliability engineering and safety-critical systems,components → failures → prevention
-36,risk,Challenge from Critical Perspective,Play devil's advocate to stress-test ideas and find weaknesses - essential for overcoming groupthink,assumptions → challenges → strengthening
-37,risk,Identify Potential Risks,Brainstorm what could go wrong across all categories - fundamental for project planning and deployment preparation,categories → risks → mitigations
-38,risk,Chaos Monkey Scenarios,Deliberately break things to test resilience and recovery - ensures systems handle failures gracefully,break → observe → harden
-39,core,First Principles Analysis,Strip away assumptions to rebuild from fundamental truths - breakthrough technique for innovation and solving impossible problems,assumptions → truths → new approach
-40,core,5 Whys Deep Dive,Repeatedly ask why to drill down to root causes - simple but powerful for understanding failures,why chain → root cause → solution
-41,core,Socratic Questioning,Use targeted questions to reveal hidden assumptions and guide discovery - excellent for teaching and self-discovery,questions → revelations → understanding
-42,core,Critique and Refine,Systematic review to identify strengths and weaknesses then improve - standard quality check for drafts,strengths/weaknesses → improvements → refined
-43,core,Explain Reasoning,Walk through step-by-step thinking to show how conclusions were reached - crucial for transparency,steps → logic → conclusion
-44,core,Expand or Contract for Audience,Dynamically adjust detail level and technical depth for target audience - matches content to reader capabilities,audience → adjustments → refined content
-45,learning,Feynman Technique,Explain complex concepts simply as if teaching a child - the ultimate test of true understanding,complex → simple → gaps → mastery
-46,learning,Active Recall Testing,Test understanding without references to verify true knowledge - essential for identifying gaps,test → gaps → reinforcement
-47,philosophical,Occam's Razor Application,Find the simplest sufficient explanation by eliminating unnecessary complexity - essential for debugging,options → simplification → selection
-48,philosophical,Trolley Problem Variations,Explore ethical trade-offs through moral dilemmas - valuable for understanding values and difficult decisions,dilemma → analysis → decision
-49,retrospective,Hindsight Reflection,Imagine looking back from the future to gain perspective - powerful for project reviews,future view → insights → application
-50,retrospective,Lessons Learned Extraction,Systematically identify key takeaways and actionable improvements - essential for continuous improvement,experience → lessons → actions

src/core/tasks/advanced-elicitation.xml

@@ -1,116 +0,0 @@
-<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/_cfg/agent-manifest.csv">
-  <llm critical="true">
-    <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
-    <i>DO NOT skip steps or change the sequence</i>
-    <i>HALT immediately when halt-conditions are met</i>
-    <i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
-    <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
-  </llm>
-
-  <integration description="When called from workflow">
-    <desc>When called during template workflow processing:</desc>
-    <i>1. Receive or review the current section content that was just generated or</i>
-    <i>2. Apply elicitation methods iteratively to enhance that specific content</i>
-    <i>3. Return the enhanced version back when user selects 'x' to proceed and return back</i>
-    <i>4. The enhanced content replaces the original section content in the output document</i>
-  </integration>
-
-  <flow>
-    <step n="1" title="Method Registry Loading">
-      <action>Load and read {{methods}} and {{agent-party}}</action>
-
-      <csv-structure>
-        <i>category: Method grouping (core, structural, risk, etc.)</i>
-        <i>method_name: Display name for the method</i>
-        <i>description: Rich explanation of what the method does, when to use it, and why it's valuable</i>
-        <i>output_pattern: Flexible flow guide using → arrows (e.g., "analysis → insights → action")</i>
-      </csv-structure>
-
-      <context-analysis>
-        <i>Use conversation history</i>
-        <i>Analyze: content type, complexity, stakeholder needs, risk level, and creative potential</i>
-      </context-analysis>
-
-      <smart-selection>
-        <i>1. Analyze context: Content type, complexity, stakeholder needs, risk level, creative potential</i>
-        <i>2. Parse descriptions: Understand each method's purpose from the rich descriptions in CSV</i>
-        <i>3. Select 5 methods: Choose methods that best match the context based on their descriptions</i>
-        <i>4. Balance approach: Include mix of foundational and specialized techniques as appropriate</i>
-      </smart-selection>
-    </step>
-
-    <step n="2" title="Present Options and Handle Responses">
-
-      <format>
-        **Advanced Elicitation Options (If you launched Party Mode, they will participate randomly)**
-        Choose a number (1-5), [r] to Reshuffle, [a] List All, or [x] to Proceed:
-
-        1. [Method Name]
-        2. [Method Name]
-        3. [Method Name]
-        4. [Method Name]
-        5. [Method Name]
-        r. Reshuffle the list with 5 new options
-        a. List all methods with descriptions
-        x. Proceed / No Further Actions
-      </format>
-
-      <response-handling>
-        <case n="1-5">
-          <i>Execute the selected method using its description from the CSV</i>
-          <i>Adapt the method's complexity and output format based on the current context</i>
-          <i>Apply the method creatively to the current section content being enhanced</i>
-          <i>Display the enhanced version showing what the method revealed or improved</i>
-          <i>CRITICAL: Ask the user if they would like to apply the changes to the doc (y/n/other) and HALT to await response.</i>
-          <i>CRITICAL: ONLY if Yes, apply the changes. IF No, discard your memory of the proposed changes. If any other reply, try best to
-            follow the instructions given by the user.</i>
-          <i>CRITICAL: Re-present the same 1-5,r,x prompt to allow additional elicitations</i>
-        </case>
-        <case n="r">
-          <i>Select 5 random methods from advanced-elicitation-methods.csv, present new list with same prompt format</i>
-          <i>When selecting, try to think and pick a diverse set of methods covering different categories and approaches, with 1 and 2 being
-            potentially the most useful for the document or section being discovered</i>
-        </case>
-        <case n="x">
-          <i>Complete elicitation and proceed</i>
-          <i>Return the fully enhanced content back to create-doc.md</i>
-          <i>The enhanced content becomes the final version for that section</i>
-          <i>Signal completion back to create-doc.md to continue with next section</i>
-        </case>
-        <case n="a">
-          <i>List all methods with their descriptions from the CSV in a compact table</i>
-          <i>Allow user to select any method by name or number from the full list</i>
-          <i>After selection, execute the method as described in the n="1-5" case above</i>
-        </case>
-        <case n="direct-feedback">
-          <i>Apply changes to current section content and re-present choices</i>
-        </case>
-        <case n="multiple-numbers">
-          <i>Execute methods in sequence on the content, then re-offer choices</i>
-        </case>
-      </response-handling>
-    </step>
-
-    <step n="3" title="Execution Guidelines">
-      <i>Method execution: Use the description from CSV to understand and apply each method</i>
-      <i>Output pattern: Use the pattern as a flexible guide (e.g., "paths → evaluation → selection")</i>
-      <i>Dynamic adaptation: Adjust complexity based on content needs (simple to sophisticated)</i>
-      <i>Creative application: Interpret methods flexibly based on context while maintaining pattern consistency</i>
-      <i>Focus on actionable insights</i>
-      <i>Stay relevant: Tie elicitation to specific content being analyzed (the current section from the document being created unless user
-        indicates otherwise)</i>
-      <i>Identify personas: For single or multi-persona methods, clearly identify viewpoints, and use party members if available in memory
-        already</i>
-      <i>Critical loop behavior: Always re-offer the 1-5,r,a,x choices after each method execution</i>
-      <i>Continue until user selects 'x' to proceed with enhanced content, confirm or ask the user what should be accepted from the session</i>
-      <i>Each method application builds upon previous enhancements</i>
-      <i>Content preservation: Track all enhancements made during elicitation</i>
-      <i>Iterative enhancement: Each selected method (1-5) should:</i>
-      <i> 1. Apply to the current enhanced version of the content</i>
-      <i> 2. Show the improvements made</i>
-      <i> 3. Return to the prompt for additional elicitations or completion</i>
-    </step>
-  </flow>
-</task>

src/core/tasks/index-docs.xml

@@ -1,65 +0,0 @@
-<task id=".bmad/core/tasks/index-docs" name="Index Docs"
-  description="Generates or updates an index.md of all documents in the specified directory" webskip="true" standalone="true">
-  <llm critical="true">
-    <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
-    <i>DO NOT skip steps or change the sequence</i>
-    <i>HALT immediately when halt-conditions are met</i>
-    <i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
-    <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
-  </llm>
-
-  <flow>
-    <step n="1" title="Scan Directory">
-      <i>List all files and subdirectories in the target location</i>
-    </step>
-
-    <step n="2" title="Group Content">
-      <i>Organize files by type, purpose, or subdirectory</i>
-    </step>
-
-    <step n="3" title="Generate Descriptions">
-      <i>Read each file to understand its actual purpose and create brief (3-10 word) descriptions based on the content, not just the
-        filename</i>
-    </step>
-
-    <step n="4" title="Create/Update Index">
-      <i>Write or update index.md with organized file listings</i>
-    </step>
-  </flow>
-
-  <output-format>
-    <example>
-      # Directory Index
-
-      ## Files
-
-      - **[filename.ext](./filename.ext)** - Brief description
-      - **[another-file.ext](./another-file.ext)** - Brief description
-
-      ## Subdirectories
-
-      ### subfolder/
-
-      - **[file1.ext](./subfolder/file1.ext)** - Brief description
-      - **[file2.ext](./subfolder/file2.ext)** - Brief description
-
-      ### another-folder/
-
-      - **[file3.ext](./another-folder/file3.ext)** - Brief description
-    </example>
-  </output-format>
-
-  <halt-conditions critical="true">
-    <i>HALT if target directory does not exist or is inaccessible</i>
-    <i>HALT if user does not have write permissions to create index.md</i>
-  </halt-conditions>
-
-  <validation>
-    <i>Use relative paths starting with ./</i>
-    <i>Group similar files together</i>
-    <i>Read file contents to generate accurate descriptions - don't guess from filenames</i>
-    <i>Keep descriptions concise but informative (3-10 words)</i>
-    <i>Sort alphabetically within groups</i>
-    <i>Skip hidden files (starting with .) unless specified</i>
-  </validation>
-</task>

src/core/tasks/validate-workflow.xml

@@ -1,89 +0,0 @@
-<task id=".bmad/core/tasks/validate-workflow.xml" name="Validate Workflow Output">
-  <objective>Run a checklist against a document with thorough analysis and produce a validation report</objective>
-
-  <inputs>
-    <input name="workflow" desc="Workflow path containing checklist.md" />
-    <input name="checklist" desc="Checklist to validate against (defaults to workflow's checklist.md)" />
-    <input name="document" desc="Document to validate (ask user if not specified)" />
-  </inputs>
-
-  <flow>
-    <step n="1" title="Setup">
-      <action>If checklist not provided, load checklist.md from workflow location</action>
-      <action>Try to fuzzy match for files similar to the input document name or if user did not provide the document. If document not
-        provided or unsure, ask user: "Which document should I validate?"</action>
-      <action>Load both the checklist and document</action>
-    </step>
-
-    <step n="2" title="Validate" critical="true">
-      <mandate>For EVERY checklist item, WITHOUT SKIPPING ANY:</mandate>
-
-      <for-each-item>
-        <action>Read requirement carefully</action>
-        <action>Search document for evidence along with any ancillary loaded documents or artifacts (quotes with line numbers)</action>
-        <action>Analyze deeply - look for explicit AND implied coverage</action>
-
-        <mark-as>
-          ✓ PASS - Requirement fully met (provide evidence)
-          ⚠ PARTIAL - Some coverage but incomplete (explain gaps)
-          ✗ FAIL - Not met or severely deficient (explain why)
-          ➖ N/A - Not applicable (explain reason)
-        </mark-as>
-      </for-each-item>
-
-      <critical>DO NOT SKIP ANY SECTIONS OR ITEMS</critical>
-    </step>
-
-    <step n="3" title="Generate Report">
-      <action>Create validation-report-{timestamp}.md in document's folder</action>
-
-      <report-format>
-        # Validation Report
-
-        **Document:** {document-path}
-        **Checklist:** {checklist-path}
-        **Date:** {timestamp}
-
-        ## Summary
-        - Overall: X/Y passed (Z%)
-        - Critical Issues: {count}
-
-        ## Section Results
-
-        ### {Section Name}
-        Pass Rate: X/Y (Z%)
-
-        {For each item:}
-        [MARK] {Item description}
-        Evidence: {Quote with line# or explanation}
-        {If FAIL/PARTIAL: Impact: {why this matters}}
-
-        ## Failed Items
-        {All ✗ items with recommendations}
-
-        ## Partial Items
-        {All ⚠ items with what's missing}
-
-        ## Recommendations
-        1. Must Fix: {critical failures}
-        2. Should Improve: {important gaps}
-        3. Consider: {minor improvements}
-      </report-format>
-    </step>
-
-    <step n="4" title="Summary for User">
-      <action>Present section-by-section summary</action>
-      <action>Highlight all critical issues</action>
-      <action>Provide path to saved report</action>
-      <action>HALT - do not continue unless user asks</action>
-    </step>
-  </flow>
-
-  <critical-rules>
-    <rule>NEVER skip sections - validate EVERYTHING</rule>
-    <rule>ALWAYS provide evidence (quotes + line numbers) for marks</rule>
-    <rule>Think deeply about each requirement - don't rush</rule>
-    <rule>Save report to document's folder automatically</rule>
-    <rule>HALT after presenting summary - wait for user</rule>
-  </critical-rules>
-</task>

src/core/tasks/workflow.xml

@@ -1,235 +0,0 @@
-<task id=".bmad/core/tasks/workflow.xml" name="Execute Workflow">
-  <objective>Execute given workflow by loading its configuration, following instructions, and producing output</objective>
-
-  <llm critical="true">
-    <mandate>Always read COMPLETE files - NEVER use offset/limit when reading any workflow related files</mandate>
-    <mandate>Instructions are MANDATORY - either as file path, steps or embedded list in YAML, XML or markdown</mandate>
-    <mandate>Execute ALL steps in instructions IN EXACT ORDER</mandate>
-    <mandate>Save to template output file after EVERY "template-output" tag</mandate>
-    <mandate>NEVER skip a step - YOU are responsible for every steps execution without fail or excuse</mandate>
-  </llm>
-
-  <WORKFLOW-RULES critical="true">
-    <rule n="1">Steps execute in exact numerical order (1, 2, 3...)</rule>
-    <rule n="2">Optional steps: Ask user unless #yolo mode active</rule>
-    <rule n="3">Template-output tags: Save content, discuss with the user the section completed, and NEVER proceed until the users indicates
-      to proceed (unless YOLO mode has been activated)</rule>
-  </WORKFLOW-RULES>
-
-  <flow>
-    <step n="1" title="Load and Initialize Workflow">
-      <substep n="1a" title="Load Configuration and Resolve Variables">
-        <action>Read workflow.yaml from provided path</action>
-        <mandate>Load config_source (REQUIRED for all modules)</mandate>
-        <phase n="1">Load external config from config_source path</phase>
-        <phase n="2">Resolve all {config_source}: references with values from config</phase>
-        <phase n="3">Resolve system variables (date:system-generated) and paths ({project-root}, {installed_path})</phase>
-        <phase n="4">Ask user for input of any variables that are still unknown</phase>
-      </substep>
-
-      <substep n="1b" title="Load Required Components">
-        <mandate>Instructions: Read COMPLETE file from path OR embedded list (REQUIRED)</mandate>
-        <check>If template path → Read COMPLETE template file</check>
-        <check>If validation path → Note path for later loading when needed</check>
-        <check>If template: false → Mark as action-workflow (else template-workflow)</check>
-        <note>Data files (csv, json) → Store paths only, load on-demand when instructions reference them</note>
-      </substep>
-
-      <substep n="1c" title="Initialize Output" if="template-workflow">
-        <action>Resolve default_output_file path with all variables and {{date}}</action>
-        <action>Create output directory if doesn't exist</action>
-        <action>If template-workflow → Write template to output file with placeholders</action>
-        <action>If action-workflow → Skip file creation</action>
-      </substep>
-    </step>
-
-    <step n="2" title="Process Each Instruction Step in Order">
-      <iterate>For each step in instructions:</iterate>
-
-      <substep n="2a" title="Handle Step Attributes">
-        <check>If optional="true" and NOT #yolo → Ask user to include</check>
-        <check>If if="condition" → Evaluate condition</check>
-        <check>If for-each="item" → Repeat step for each item</check>
-        <check>If repeat="n" → Repeat step n times</check>
-      </substep>
-
-      <substep n="2b" title="Execute Step Content">
-        <action>Process step instructions (markdown or XML tags)</action>
-        <action>Replace {{variables}} with values (ask user if unknown)</action>
-        <execute-tags>
-          <tag>action xml tag → Perform the action</tag>
-          <tag>check if="condition" xml tag → Conditional block wrapping actions (requires closing &lt;/check&gt;)</tag>
-          <tag>ask xml tag → Prompt user and WAIT for response</tag>
-          <tag>invoke-workflow xml tag → Execute another workflow with given inputs and the workflow.xml runner</tag>
-          <tag>invoke-task xml tag → Execute specified task</tag>
-          <tag>invoke-protocol name="protocol_name" xml tag → Execute reusable protocol from protocols section</tag>
-          <tag>goto step="x" → Jump to specified step</tag>
-        </execute-tags>
-      </substep>
-
-      <substep n="2c" title="Handle template-output Tags">
-        <if tag="template-output">
-          <mandate>Generate content for this section</mandate>
-          <mandate>Save to file (Write first time, Edit subsequent)</mandate>
-          <action>Display generated content</action>
-          <ask> [a] Advanced Elicitation, [c] Continue, [p] Party-Mode, [y] YOLO the rest of this document only. WAIT for response. <if
-              response="a">
-              <action>Start the advanced elicitation workflow {project-root}/.bmad/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>
-            </if>
-            <if
-              response="y">
-              <action>Enter #yolo mode for the rest of the workflow</action>
-            </if>
-          </ask>
-        </if>
-      </substep>
-
-      <substep n="2d" title="Step Completion">
-        <check>If no special tags and NOT #yolo:</check>
-        <ask>Continue to next step? (y/n/edit)</ask>
-      </substep>
-    </step>
-
-    <step n="3" title="Completion">
-      <check>Confirm document saved to output path</check>
-      <action>Report workflow completion</action>
-    </step>
-  </flow>
-
-  <execution-modes>
-    <mode name="normal">Full user interaction and confirmation of EVERY step at EVERY template output - NO EXCEPTIONS except yolo MODE</mode>
-    <mode name="yolo">Skip all confirmations and elicitation, minimize prompts and try to produce all of the workflow automatically by
-      simulating the remaining discussions with an simulated expert user</mode>
-  </execution-modes>
-
-  <supported-tags desc="Instructions can use these tags">
-    <structural>
-      <tag>step n="X" goal="..." - Define step with number and goal</tag>
-      <tag>optional="true" - Step can be skipped</tag>
-      <tag>if="condition" - Conditional execution</tag>
-      <tag>for-each="collection" - Iterate over items</tag>
-      <tag>repeat="n" - Repeat n times</tag>
-    </structural>
-    <execution>
-      <tag>action - Required action to perform</tag>
-      <tag>action if="condition" - Single conditional action (inline, no closing tag needed)</tag>
-      <tag>check if="condition"&gt;...&lt;/check&gt; - Conditional block wrapping multiple items (closing tag required)</tag>
-      <tag>ask - Get user input (ALWAYS wait for response before continuing)</tag>
-      <tag>goto - Jump to another step</tag>
-      <tag>invoke-workflow - Call another workflow</tag>
-      <tag>invoke-task - Call a task</tag>
-      <tag>invoke-protocol - Execute a reusable protocol (e.g., discover_inputs)</tag>
-    </execution>
-    <output>
-      <tag>template-output - Save content checkpoint</tag>
-      <tag>critical - Cannot be skipped</tag>
-      <tag>example - Show example output</tag>
-    </output>
-  </supported-tags>
-
-  <protocols desc="Reusable workflow protocols that can be invoked via invoke-protocol tag">
-    <protocol name="discover_inputs" desc="Smart file discovery and loading based on input_file_patterns">
-      <objective>Intelligently load project files (whole or sharded) based on workflow's input_file_patterns configuration</objective>
-
-      <critical>Only execute if workflow.yaml contains input_file_patterns section</critical>
-
-      <flow>
-        <step n="1" title="Parse Input File Patterns">
-          <action>Read input_file_patterns from loaded workflow.yaml</action>
-          <action>For each pattern group (prd, architecture, epics, etc.), note the load_strategy if present</action>
-        </step>
-
-        <step n="2" title="Load Files Using Smart Strategies">
-          <iterate>For each pattern in input_file_patterns:</iterate>
-
-          <substep n="2a" title="Try Sharded Documents First">
-            <check if="sharded pattern exists">
-              <action>Determine load_strategy from pattern config (defaults to FULL_LOAD if not specified)</action>
-
-              <strategy name="FULL_LOAD">
-                <desc>Load ALL files in sharded directory - used for PRD, Architecture, UX, brownfield docs</desc>
-                <action>Use glob pattern to find ALL .md files (e.g., "{output_folder}/*architecture*/*.md")</action>
-                <action>Load EVERY matching file completely</action>
-                <action>Concatenate content in logical order (index.md first if exists, then alphabetical)</action>
-                <action>Store in variable: {pattern_name_content}</action>
-              </strategy>
-
-              <strategy name="SELECTIVE_LOAD">
-                <desc>Load specific shard using template variable - example: used for epics with {{epic_num}}</desc>
-                <action>Check for template variables in sharded_single pattern (e.g., {{epic_num}})</action>
-                <action>If variable undefined, ask user for value OR infer from context</action>
-                <action>Resolve template to specific file path</action>
-                <action>Load that specific file</action>
-                <action>Store in variable: {pattern_name_content}</action>
-              </strategy>
-
-              <strategy name="INDEX_GUIDED">
-                <desc>Load index.md, analyze structure and description of each doc in the index, then intelligently load relevant docs</desc>
-                <mandate>DO NOT BE LAZY - use best judgment to load documents that might have relevant information, even if only a 5% chance</mandate>
-                <action>Load index.md from sharded directory</action>
-                <action>Parse table of contents, links, section headers</action>
-                <action>Analyze workflow's purpose and objective</action>
-                <action>Identify which linked/referenced documents are likely relevant</action>
-                <example>If workflow is about authentication and index shows "Auth Overview", "Payment Setup", "Deployment" → Load auth
-                  docs, consider deployment docs, skip payment</example>
-                <action>Load all identified relevant documents</action>
-                <action>Store combined content in variable: {pattern_name_content}</action>
-                <note>When in doubt, LOAD IT - context is valuable, being thorough is better than missing critical info</note>
-              </strategy>
-              <action>Mark pattern as RESOLVED, skip to next pattern</action>
-            </check>
-          </substep>
-
-          <substep n="2b" title="Try Whole Document if No Sharded Found">
-            <check if="no sharded matches found OR no sharded pattern exists">
-              <action>Attempt glob match on 'whole' pattern (e.g., "{output_folder}/*prd*.md")</action>
-              <check if="matches found">
-                <action>Load ALL matching files completely (no offset/limit)</action>
-                <action>Store content in variable: {pattern_name_content} (e.g., {prd_content})</action>
-                <action>Mark pattern as RESOLVED, skip to next pattern</action>
-              </check>
-            </check>
-          </substep>
-
-          <substep n="2c" title="Handle Not Found">
-            <check if="no matches for sharded OR whole">
-              <action>Set {pattern_name_content} to empty string</action>
-              <action>Note in session: "No {pattern_name} files found" (not an error, just unavailable, offer use change to provide)</action>
-            </check>
-          </substep>
-        </step>
-
-        <step n="3" title="Report Discovery Results">
-          <action>List all loaded content variables with file counts</action>
-          <example>
-            ✓ Loaded {prd_content} from 5 sharded files: prd/index.md, prd/requirements.md, ...
-            ✓ Loaded {architecture_content} from 1 file: Architecture.md
-            ✓ Loaded {epics_content} from selective load: epics/epic-3.md
-            ○ No ux_design files found
-          </example>
-          <note>This gives workflow transparency into what context is available</note>
-        </step>
-      </flow>
-
-    </protocol>
-  </protocols>
-
-  <llm final="true">
-    <critical-rules>
-      • This is the complete workflow execution engine
-      • You MUST Follow instructions exactly as written
-      • The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml
-      • You MUST have already loaded and processed: {installed_path}/workflow.yaml
-      • This workflow uses INTENT-DRIVEN PLANNING - adapt organically to product type and context
-      • YOU ARE FACILITATING A CONVERSATION With a user to produce a final document step by step. The whole process is meant to be
-      collaborative helping the user flesh out their ideas. Do not rush or optimize and skip any section.
-    </critical-rules>
-  </llm>
-</task> 

src/core/tools/shard-doc.xml

@@ -1,109 +0,0 @@
-<tool id=".bmad/core/tasks/shard-doc" name="Shard Document"
-  description="Splits large markdown documents into smaller, organized files based on level 2 (default) sections" webskip="true"
-  standalone="true">
-  <objective>Split large markdown documents into smaller, organized files based on level 2 sections using @kayvan/markdown-tree-parser tool</objective>
-
-  <llm critical="true">
-    <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
-    <i>DO NOT skip steps or change the sequence</i>
-    <i>HALT immediately when halt-conditions are met</i>
-    <i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
-    <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
-  </llm>
-
-  <critical-context>
-    <i>Uses `npx @kayvan/markdown-tree-parser` to automatically shard documents by level 2 headings and generate an index</i>
-  </critical-context>
-
-  <flow>
-    <step n="1" title="Get Source Document">
-      <action>Ask user for the source document path if not provided already</action>
-      <action>Verify file exists and is accessible</action>
-      <action>Verify file is markdown format (.md extension)</action>
-      <action if="file not found or not markdown">HALT with error message</action>
-    </step>
-
-    <step n="2" title="Get Destination Folder">
-      <action>Determine default destination: same location as source file, folder named after source file without .md extension</action>
-      <action>Example: /path/to/architecture.md → /path/to/architecture/</action>
-      <action>Ask user for the destination folder path ([y] to confirm use of default: [suggested-path], else enter a new path)</action>
-      <action if="user accepts default">Use the suggested destination path</action>
-      <action if="user provides custom path">Use the custom destination path</action>
-      <action>Verify destination folder exists or can be created</action>
-      <action>Check write permissions for destination</action>
-      <action if="permission denied">HALT with error message</action>
-    </step>
-
-    <step n="3" title="Execute Sharding">
-      <action>Inform user that sharding is beginning</action>
-      <action>Execute command: `npx @kayvan/markdown-tree-parser explode [source-document] [destination-folder]`</action>
-      <action>Capture command output and any errors</action>
-      <action if="command fails">HALT and display error to user</action>
-    </step>
-
-    <step n="4" title="Verify Output">
-      <action>Check that destination folder contains sharded files</action>
-      <action>Verify index.md was created in destination folder</action>
-      <action>Count the number of files created</action>
-      <action if="no files created">HALT with error message</action>
-    </step>
-
-    <step n="5" title="Report Completion">
-      <action>Display completion report to user including:</action>
-      <i>- Source document path and name</i>
-      <i>- Destination folder path</i>
-      <i>- Number of section files created</i>
-      <i>- Confirmation that index.md was created</i>
-      <i>- Any tool output or warnings</i>
-      <action>Inform user that sharding completed successfully</action>
-    </step>
-
-    <step n="6" title="Handle Original Document">
-      <critical>Keeping both the original and sharded versions defeats the purpose of sharding and can cause confusion</critical>
-      <action>Present user with options for the original document:</action>
-
-      <ask>What would you like to do with the original document `[source-document-name]`?
-
-Options:
-[d] Delete - Remove the original (recommended - shards can always be recombined)
-[m] Move to archive - Move original to a backup/archive location
-[k] Keep - Leave original in place (NOT recommended - defeats sharding purpose)
-
-Your choice (d/m/k):</ask>
-
-      <check if="user selects 'd' (delete)">
-        <action>Delete the original source document file</action>
-        <action>Confirm deletion to user: "✓ Original document deleted: [source-document-path]"</action>
-        <note>The document can be reconstructed from shards by concatenating all section files in order</note>
-      </check>
-
-      <check if="user selects 'm' (move)">
-        <action>Determine default archive location: same directory as source, in an "archive" subfolder</action>
-        <action>Example: /path/to/architecture.md → /path/to/archive/architecture.md</action>
-        <ask>Archive location ([y] to use default: [default-archive-path], or provide custom path):</ask>
-        <action if="user accepts default">Use default archive path</action>
-        <action if="user provides custom path">Use custom archive path</action>
-        <action>Create archive directory if it doesn't exist</action>
-        <action>Move original document to archive location</action>
-        <action>Confirm move to user: "✓ Original document moved to: [archive-path]"</action>
-      </check>
-
-      <check if="user selects 'k' (keep)">
-        <action>Display warning to user:</action>
-        <output>⚠️ WARNING: Keeping both original and sharded versions is NOT recommended.
-
-This creates confusion because:
-- The discover_inputs protocol may load the wrong version
-- Updates to one won't reflect in the other
-- You'll have duplicate content taking up space
-
-Consider deleting or archiving the original document.</output>
-        <action>Confirm user choice: "Original document kept at: [source-document-path]"</action>
-      </check>
-    </step>
-  </flow>
-
-  <halt-conditions critical="true">
-    <i>HALT if npx command fails or produces no output files</i>
-  </halt-conditions>
-</tool>

src/core/workflows/brainstorming/brain-methods.csv

@@ -1,62 +0,0 @@
-category,technique_name,description
-collaborative,Yes And Building,"Build momentum through positive additions where each idea becomes a launching pad - use prompts like 'Yes and we could also...' or 'Building on that idea...' to create energetic collaborative flow that builds upon previous contributions"
-collaborative,Brain Writing Round Robin,"Silent idea generation followed by building on others' written concepts - gives quieter voices equal contribution while maintaining documentation through the sequence of writing silently, passing ideas, and building on received concepts"
-collaborative,Random Stimulation,"Use random words/images as creative catalysts to force unexpected connections - breaks through mental blocks with serendipitous inspiration by asking how random elements relate, what connections exist, and forcing relationships"
-collaborative,Role Playing,"Generate solutions from multiple stakeholder perspectives to build empathy while ensuring comprehensive consideration - embody different roles by asking what they want, how they'd approach problems, and what matters most to them"
-collaborative,Ideation Relay Race,"Rapid-fire idea building under time pressure creates urgency and breakthroughs - structure with 30-second additions, quick building on ideas, and fast passing to maintain creative momentum and prevent overthinking"
-creative,What If Scenarios,"Explore radical possibilities by questioning all constraints and assumptions - perfect for breaking through stuck thinking using prompts like 'What if we had unlimited resources?' 'What if the opposite were true?' or 'What if this problem didn't exist?'"
-creative,Analogical Thinking,"Find creative solutions by drawing parallels to other domains - transfer successful patterns by asking 'This is like what?' 'How is this similar to...' and 'What other examples come to mind?' to connect to existing solutions"
-creative,Reversal Inversion,"Deliberately flip problems upside down to reveal hidden assumptions and fresh angles - great when conventional approaches fail by asking 'What if we did the opposite?' 'How could we make this worse?' and 'What's the reverse approach?'"
-creative,First Principles Thinking,"Strip away assumptions to rebuild from fundamental truths - essential for breakthrough innovation by asking 'What do we know for certain?' 'What are the fundamental truths?' and 'If we started from scratch?'"
-creative,Forced Relationships,"Connect unrelated concepts to spark innovative bridges through creative collision - take two unrelated things, find connections between them, identify bridges, and explore how they could work together to generate unexpected solutions"
-creative,Time Shifting,"Explore solutions across different time periods to reveal constraints and opportunities by asking 'How would this work in the past?' 'What about 100 years from now?' 'Different era constraints?' and 'What time-based solutions apply?'"
-creative,Metaphor Mapping,"Use extended metaphors as thinking tools to explore problems from new angles - transforms abstract challenges into tangible narratives by asking 'This problem is like a metaphor,' extending the metaphor, and mapping elements to discover insights"
-creative,Cross-Pollination,"Transfer solutions from completely different industries or domains to spark breakthrough innovations by asking how industry X would solve this, what patterns work in field Y, and how to adapt solutions from domain Z"
-creative,Concept Blending,"Merge two or more existing concepts to create entirely new categories - goes beyond simple combination to genuine innovation by asking what emerges when concepts merge, what new category is created, and how the blend transcends original ideas"
-creative,Reverse Brainstorming,"Generate problems instead of solutions to identify hidden opportunities and unexpected pathways by asking 'What could go wrong?' 'How could we make this fail?' and 'What problems could we create?' to reveal solution insights"
-creative,Sensory Exploration,"Engage all five senses to discover multi-dimensional solution spaces beyond purely analytical thinking by asking what ideas feel, smell, taste, or sound like, and how different senses engage with the problem space"
-deep,Five Whys,"Drill down through layers of causation to uncover root causes - essential for solving problems at source rather than symptoms by asking 'Why did this happen?' repeatedly until reaching fundamental drivers and ultimate causes"
-deep,Morphological Analysis,"Systematically explore all possible parameter combinations for complex systems requiring comprehensive solution mapping - identify key parameters, list options for each, try different combinations, and identify emerging patterns"
-deep,Provocation Technique,"Use deliberately provocative statements to extract useful ideas from seemingly absurd starting points - catalyzes breakthrough thinking by asking 'What if provocative statement?' 'How could this be useful?' 'What idea triggers?' and 'Extract the principle'"
-deep,Assumption Reversal,"Challenge and flip core assumptions to rebuild from new foundations - essential for paradigm shifts by asking 'What assumptions are we making?' 'What if the opposite were true?' 'Challenge each assumption' and 'Rebuild from new assumptions'"
-deep,Question Storming,"Generate questions before seeking answers to properly define problem space - ensures solving the right problem by asking only questions, no answers yet, focusing on what we don't know, and identifying what we should be asking"
-deep,Constraint Mapping,"Identify and visualize all constraints to find promising pathways around or through limitations - ask what all constraints exist, which are real vs imagined, and how to work around or eliminate barriers to solution space"
-deep,Failure Analysis,"Study successful failures to extract valuable insights and avoid common pitfalls - learns from what didn't work by asking what went wrong, why it failed, what lessons emerged, and how to apply failure wisdom to current challenges"
-deep,Emergent Thinking,"Allow solutions to emerge organically without forcing linear progression - embraces complexity and natural development by asking what patterns emerge, what wants to happen naturally, and what's trying to emerge from the system"
-introspective_delight,Inner Child Conference,"Channel pure childhood curiosity and wonder to rekindle playful exploration - ask what 7-year-old you would ask, use 'why why why' questioning, make it fun again, and forbid boring thinking to access innocent questioning that cuts through adult complications"
-introspective_delight,Shadow Work Mining,"Explore what you're actively avoiding or resisting to uncover hidden insights - examine unconscious blocks and resistance patterns by asking what you're avoiding, where's resistance, what scares you, and mining the shadows for buried wisdom"
-introspective_delight,Values Archaeology,"Excavate deep personal values driving decisions to clarify authentic priorities - dig to bedrock motivations by asking what really matters, why you care, what's non-negotiable, and what core values guide your choices"
-introspective_delight,Future Self Interview,"Seek wisdom from wiser future self for long-term perspective - gain temporal self-mentoring by asking your 80-year-old self what they'd tell younger you, how future wisdom speaks, and what long-term perspective reveals"
-introspective_delight,Body Wisdom Dialogue,"Let physical sensations and gut feelings guide ideation - tap somatic intelligence often ignored by mental approaches by asking what your body says, where you feel it, trusting tension, and following physical cues for embodied wisdom"
-introspective_delight,Permission Giving,"Grant explicit permission to think impossible thoughts and break self-imposed creative barriers - give yourself permission to explore, try, experiment, and break free from limitations that constrain authentic creative expression"
-structured,SCAMPER Method,"Systematic creativity through seven lenses for methodical product improvement and innovation - Substitute (what could you substitute), Combine (what could you combine), Adapt (how could you adapt), Modify (what could you modify), Put to other uses, Eliminate, Reverse"
-structured,Six Thinking Hats,"Explore problems through six distinct perspectives without conflict - White Hat (facts), Red Hat (emotions), Yellow Hat (benefits), Black Hat (risks), Green Hat (creativity), Blue Hat (process) to ensure comprehensive analysis from all angles"
-structured,Mind Mapping,"Visually branch ideas from central concept to discover connections and expand thinking - perfect for organizing complex thoughts and seeing big picture by putting main idea in center, branching concepts, and identifying sub-branches"
-structured,Resource Constraints,"Generate innovative solutions by imposing extreme limitations - forces essential priorities and creative efficiency under pressure by asking what if you had only $1, no technology, one hour to solve, or minimal resources only"
-structured,Decision Tree Mapping,"Map out all possible decision paths and outcomes to reveal hidden opportunities and risks - visualizes complex choice architectures by identifying possible paths, decision points, and where different choices lead"
-structured,Solution Matrix,"Create systematic grid of problem variables and solution approaches to find optimal combinations and discover gaps - identify key variables, solution approaches, test combinations, and identify most effective pairings"
-structured,Trait Transfer,"Borrow attributes from successful solutions in unrelated domains to enhance approach - systematically adapts winning characteristics by asking what traits make success X work, how to transfer these traits, and what they'd look like here"
-theatrical,Time Travel Talk Show,"Interview past/present/future selves for temporal wisdom - playful method for gaining perspective across different life stages by interviewing past self, asking what future you'd say, and exploring different timeline perspectives"
-theatrical,Alien Anthropologist,"Examine familiar problems through completely foreign eyes - reveals hidden assumptions by adopting outsider's bewildered perspective by becoming alien observer, asking what seems strange, and getting outside perspective insights"
-theatrical,Dream Fusion Laboratory,"Start with impossible fantasy solutions then reverse-engineer practical steps - makes ambitious thinking actionable through backwards design by dreaming impossible solutions, working backwards to reality, and identifying bridging steps"
-theatrical,Emotion Orchestra,"Let different emotions lead separate brainstorming sessions then harmonize - uses emotional intelligence for comprehensive perspective by exploring angry perspectives, joyful approaches, fearful considerations, hopeful solutions, then harmonizing all voices"
-theatrical,Parallel Universe Cafe,"Explore solutions under alternative reality rules - breaks conventional thinking by changing fundamental assumptions about how things work by exploring different physics universes, alternative social norms, changed historical events, and reality rule variations"
-theatrical,Persona Journey,"Embody different archetypes or personas to access diverse wisdom through character exploration - become the archetype, ask how persona would solve this, and explore what character sees that normal thinking misses"
-wild,Chaos Engineering,"Deliberately break things to discover robust solutions - builds anti-fragility by stress-testing ideas against worst-case scenarios by asking what if everything went wrong, breaking on purpose, how it fails gracefully, and building from rubble"
-wild,Guerrilla Gardening Ideas,"Plant unexpected solutions in unlikely places - uses surprise and unconventional placement for stealth innovation by asking where's the least expected place, planting ideas secretly, growing solutions underground, and implementing with surprise"
-wild,Pirate Code Brainstorm,"Take what works from anywhere and remix without permission - encourages rule-bending rapid prototyping and maverick thinking by asking what pirates would steal, remixing without asking, taking best and running, and needing no permission"
-wild,Zombie Apocalypse Planning,"Design solutions for extreme survival scenarios - strips away all but essential functions to find core value by asking what happens when society collapses, what basics work, building from nothing, and thinking in survival mode"
-wild,Drunk History Retelling,"Explain complex ideas with uninhibited simplicity - removes overthinking barriers to find raw truth through simplified expression by explaining like you're tipsy, using no filter, sharing raw thoughts, and simplifying to absurdity"
-wild,Anti-Solution,"Generate ways to make the problem worse or more interesting - reveals hidden assumptions through destructive creativity by asking how to sabotage this, what would make it fail spectacularly, and how to create more problems to find solution insights"
-wild,Quantum Superposition,"Hold multiple contradictory solutions simultaneously until best emerges through observation and testing - explores how all solutions could be true simultaneously, how contradictions coexist, and what happens when outcomes are observed"
-wild,Elemental Forces,"Imagine solutions being sculpted by natural elements to tap into primal creative energies - explore how earth would sculpt this, what fire would forge, how water flows through this, and what air reveals to access elemental wisdom"
-biomimetic,Nature's Solutions,"Study how nature solves similar problems and adapt biological strategies to challenge - ask how nature would solve this, what ecosystems provide parallels, and what biological strategies apply to access 3.8 billion years of evolutionary wisdom"
-biomimetic,Ecosystem Thinking,"Analyze problem as ecosystem to identify symbiotic relationships, natural succession, and ecological principles - explore symbiotic relationships, natural succession application, and ecological principles for systems thinking"
-biomimetic,Evolutionary Pressure,"Apply evolutionary principles to gradually improve solutions through selective pressure and adaptation - ask how evolution would optimize this, what selective pressures apply, and how this adapts over time to harness natural selection wisdom"
-quantum,Observer Effect,"Recognize how observing and measuring solutions changes their behavior - uses quantum principles for innovation by asking how observing changes this, what measurement effects matter, and how to use observer effect advantageously"
-quantum,Entanglement Thinking,"Explore how different solution elements might be connected regardless of distance - reveals hidden relationships by asking what elements are entangled, how distant parts affect each other, and what hidden connections exist between solution components"
-quantum,Superposition Collapse,"Hold multiple potential solutions simultaneously until constraints force single optimal outcome - leverages quantum decision theory by asking what if all options were possible, what constraints force collapse, and which solution emerges when observed"
-cultural,Indigenous Wisdom,"Draw upon traditional knowledge systems and indigenous approaches overlooked by modern thinking - ask how specific cultures would approach this, what traditional knowledge applies, and what ancestral wisdom guides us to access overlooked problem-solving methods"
-cultural,Fusion Cuisine,"Mix cultural approaches and perspectives like fusion cuisine - creates innovation through cultural cross-pollination by asking what happens when mixing culture A with culture B, what cultural hybrids emerge, and what fusion creates"
-cultural,Ritual Innovation,"Apply ritual design principles to create transformative experiences and solutions - uses anthropological insights for human-centered design by asking what ritual would transform this, how to make it ceremonial, and what transformation this needs"
-cultural,Mythic Frameworks,"Use myths and archetypal stories as frameworks for understanding and solving problems - taps into collective unconscious by asking what myth parallels this, what archetypes are involved, and how mythic structure informs solution"

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

@@ -1,196 +0,0 @@
-# Step 1: Session Setup and Continuation Detection
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- 🛑 NEVER generate content without user input
-- ✅ ALWAYS treat this as collaborative facilitation
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- 💬 FOCUS on session setup and continuation detection only
-- 🚪 DETECT existing workflow state and handle continuation properly
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Show your analysis before taking any action
-- 💾 Initialize document and update frontmatter
-- 📖 Set up frontmatter `stepsCompleted: [1]` before loading next step
-- 🚫 FORBIDDEN to load next step until setup is complete
-
-## CONTEXT BOUNDARIES:
-
-- Variables from workflow.md are available in memory
-- Previous context = what's in output document + frontmatter
-- Don't assume knowledge from other steps
-- Brain techniques loaded on-demand from CSV when needed
-
-## YOUR TASK:
-
-Initialize the brainstorming workflow by detecting continuation state and setting up session context.
-
-## INITIALIZATION SEQUENCE:
-
-### 1. Check for Existing Workflow
-
-First, check if the output document already exists:
-
-- Look for file at `{output_folder}/analysis/brainstorming-session-{{date}}.md`
-- If exists, read the complete file including frontmatter
-- If not exists, this is a fresh workflow
-
-### 2. Handle Continuation (If Document Exists)
-
-If the document exists and has frontmatter with `stepsCompleted`:
-
-- **STOP here** and load `./step-01b-continue.md` immediately
-- Do not proceed with any initialization tasks
-- Let step-01b handle the continuation logic
-
-### 3. Fresh Workflow Setup (If No Document)
-
-If no document exists or no `stepsCompleted` in frontmatter:
-
-#### A. Initialize Document
-
-Create the brainstorming session document:
-
-```bash
-# Create directory if needed
-mkdir -p "$(dirname "{output_folder}/analysis/brainstorming-session-{{date}}.md")"
-
-# Initialize from template
-cp "{template_path}" "{output_folder}/analysis/brainstorming-session-{{date}}.md"
-```
-
-#### B. Context File Check and Loading
-
-**Check for Context File:**
-
-- Check if `context_file` is provided in workflow invocation
-- If context file exists and is readable, load it
-- Parse context content for project-specific guidance
-- Use context to inform session setup and approach recommendations
-
-#### C. Session Context Gathering
-
-"Welcome {{user_name}}! I'm excited to facilitate your brainstorming session. I'll guide you through proven creativity techniques to generate innovative ideas and breakthrough solutions.
-
-**Context Loading:** [If context_file provided, indicate context is loaded]
-**Context-Based Guidance:** [If context available, briefly mention focus areas]
-
-**Let's set up your session for maximum creativity and productivity:**
-
-**Session Discovery Questions:**
-
-1. **What are we brainstorming about?** (The central topic or challenge)
-2. **What specific outcomes are you hoping for?** (Types of ideas, solutions, or insights)"
-
-#### D. Process User Responses
-
-Wait for user responses, then:
-
-**Session Analysis:**
-"Based on your responses, I understand we're focusing on **[summarized topic]** with goals around **[summarized objectives]**.
-
-**Session Parameters:**
-
-- **Topic Focus:** [Clear topic articulation]
-- **Primary Goals:** [Specific outcome objectives]
-
-**Does this accurately capture what you want to achieve?**"
-
-#### E. Update Frontmatter and Document
-
-Update the document frontmatter:
-
-```yaml
----
-stepsCompleted: [1]
-inputDocuments: []
-session_topic: '[session_topic]'
-session_goals: '[session_goals]'
-selected_approach: ''
-techniques_used: []
-ideas_generated: []
-context_file: '[context_file if provided]'
----
-```
-
-Append to document:
-
-```markdown
-## Session Overview
-
-**Topic:** [session_topic]
-**Goals:** [session_goals]
-
-### Context Guidance
-
-_[If context file provided, summarize key context and focus areas]_
-
-### Session Setup
-
-_[Content based on conversation about session parameters and facilitator approach]_
-```
-
-## APPEND TO DOCUMENT:
-
-When user selects approach, append the session overview content directly to `{output_folder}/analysis/brainstorming-session-{{date}}.md` using the structure from above.
-
-### E. Continue to Technique Selection
-
-"**Session setup complete!** I have a clear understanding of your goals and can select the perfect techniques for your brainstorming needs.
-
-**Ready to explore technique approaches?**
-[1] User-Selected Techniques - Browse our complete technique library
-[2] AI-Recommended Techniques - Get customized suggestions based on your goals
-[3] Random Technique Selection - Discover unexpected creative methods
-[4] Progressive Technique Flow - Start broad, then systematically narrow focus
-
-Which approach appeals to you most? (Enter 1-4)"
-
-### 4. Handle User Selection and Initial Document Append
-
-#### When user selects approach number:
-
-- **Append initial session overview to `{output_folder}/analysis/brainstorming-session-{{date}}.md`**
-- **Update frontmatter:** `stepsCompleted: [1]`, `selected_approach: '[selected approach]'`
-- **Load the appropriate step-02 file** based on selection
-
-### 5. Handle User Selection
-
-After user selects approach number:
-
-- **If 1:** Load `./step-02a-user-selected.md`
-- **If 2:** Load `./step-02b-ai-recommended.md`
-- **If 3:** Load `./step-02c-random-selection.md`
-- **If 4:** Load `./step-02d-progressive-flow.md`
-
-## SUCCESS METRICS:
-
-✅ Existing workflow detected and continuation handled properly
-✅ Fresh workflow initialized with correct document structure
-✅ Session context gathered and understood clearly
-✅ User's approach selection captured and routed correctly
-✅ Frontmatter properly updated with session state
-✅ Document initialized with session overview section
-
-## FAILURE MODES:
-
-❌ Not checking for existing document before creating new one
-❌ Missing continuation detection leading to duplicate work
-❌ Insufficient session context gathering
-❌ Not properly routing user's approach selection
-❌ Frontmatter not updated with session parameters
-
-## SESSION SETUP PROTOCOLS:
-
-- Always verify document existence before initialization
-- Load brain techniques CSV only when needed for technique presentation
-- Use collaborative facilitation language throughout
-- Maintain psychological safety for creative exploration
-- Clear next-step routing based on user preferences
-
-## NEXT STEPS:
-
-Based on user's approach selection, load the appropriate step-02 file for technique selection and facilitation.
-
-Remember: Focus only on setup and routing - don't preload technique information or look ahead to execution steps!

src/core/workflows/brainstorming/steps/step-01b-continue.md

@@ -1,121 +0,0 @@
-# Step 1b: Workflow Continuation
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- ✅ YOU ARE A CONTINUATION FACILITATOR, not a fresh starter
-- 🎯 RESPECT EXISTING WORKFLOW state and progress
-- 📋 UNDERSTAND PREVIOUS SESSION context and outcomes
-- 🔍 SEAMLESSLY RESUME from where user left off
-- 💬 MAINTAIN CONTINUITY in session flow and rapport
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load and analyze existing document thoroughly
-- 💾 Update frontmatter with continuation state
-- 📖 Present current status and next options clearly
-- 🚫 FORBIDDEN repeating completed work or asking same questions
-
-## CONTEXT BOUNDARIES:
-
-- Existing document with frontmatter is available
-- Previous steps completed indicate session progress
-- Brain techniques CSV loaded when needed for remaining steps
-- User may want to continue, modify, or restart
-
-## YOUR TASK:
-
-Analyze existing brainstorming session state and provide seamless continuation options.
-
-## CONTINUATION SEQUENCE:
-
-### 1. Analyze Existing Session
-
-Load existing document and analyze current state:
-
-**Document Analysis:**
-
-- Read existing `{output_folder}/analysis/brainstorming-session-{{date}}.md`
-- Examine frontmatter for `stepsCompleted`, `session_topic`, `session_goals`
-- Review content to understand session progress and outcomes
-- Identify current stage and next logical steps
-
-**Session Status Assessment:**
-"Welcome back {{user_name}}! I can see your brainstorming session on **[session_topic]** from **[date]**.
-
-**Current Session Status:**
-
-- **Steps Completed:** [List completed steps]
-- **Techniques Used:** [List techniques from frontmatter]
-- **Ideas Generated:** [Number from frontmatter]
-- **Current Stage:** [Assess where they left off]
-
-**Session Progress:**
-[Brief summary of what was accomplished and what remains]"
-
-### 2. Present Continuation Options
-
-Based on session analysis, provide appropriate options:
-
-**If Session Completed:**
-"Your brainstorming session appears to be complete!
-
-**Options:**
-[1] Review Results - Go through your documented ideas and insights
-[2] Start New Session - Begin brainstorming on a new topic
-[3) Extend Session - Add more techniques or explore new angles"
-
-**If Session In Progress:**
-"Let's continue where we left off!
-
-**Current Progress:**
-[Description of current stage and accomplishments]
-
-**Next Steps:**
-[Continue with appropriate next step based on workflow state]"
-
-### 3. Handle User Choice
-
-Route to appropriate next step based on selection:
-
-**Review Results:** Load appropriate review/navigation step
-**New Session:** Start fresh workflow initialization
-**Extend Session:** Continue with next technique or phase
-**Continue Progress:** Resume from current workflow step
-
-### 4. Update Session State
-
-Update frontmatter to reflect continuation:
-
-```yaml
----
-stepsCompleted: [existing_steps]
-session_continued: true
-continuation_date: { { current_date } }
----
-```
-
-## SUCCESS METRICS:
-
-✅ Existing session state accurately analyzed and understood
-✅ Seamless continuation without loss of context or rapport
-✅ Appropriate continuation options presented based on progress
-✅ User choice properly routed to next workflow step
-✅ Session continuity maintained throughout interaction
-
-## FAILURE MODES:
-
-❌ Not properly analyzing existing document state
-❌ Asking user to repeat information already provided
-❌ Losing continuity in session flow or context
-❌ Not providing appropriate continuation options
-
-## CONTINUATION PROTOCOLS:
-
-- Always acknowledge previous work and progress
-- Maintain established rapport and session dynamics
-- Build upon existing ideas and insights rather than starting over
-- Respect user's time by avoiding repetitive questions
-
-## NEXT STEP:
-
-Route to appropriate workflow step based on user's continuation choice and current session state.

src/core/workflows/brainstorming/steps/step-02a-user-selected.md

@@ -1,224 +0,0 @@
-# Step 2a: User-Selected Techniques
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- ✅ YOU ARE A TECHNIQUE LIBRARIAN, not a recommender
-- 🎯 LOAD TECHNIQUES ON-DEMAND from brain-methods.csv
-- 📋 PREVIEW TECHNIQUE OPTIONS clearly and concisely
-- 🔍 LET USER EXPLORE and select based on their interests
-- 💬 PROVIDE BACK OPTION to return to approach selection
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load brain techniques CSV only when needed for presentation
-- ⚠️ Present [B] back option and [C] continue options
-- 💾 Update frontmatter with selected techniques
-- 📖 Route to technique execution after confirmation
-- 🚫 FORBIDDEN making recommendations or steering choices
-
-## CONTEXT BOUNDARIES:
-
-- Session context from Step 1 is available
-- Brain techniques CSV contains 36+ techniques across 7 categories
-- User wants full control over technique selection
-- May need to present techniques by category or search capability
-
-## YOUR TASK:
-
-Load and present brainstorming techniques from CSV, allowing user to browse and select based on their preferences.
-
-## USER SELECTION SEQUENCE:
-
-### 1. Load Brain Techniques Library
-
-Load techniques from CSV on-demand:
-
-"Perfect! Let's explore our complete brainstorming techniques library. I'll load all available techniques so you can browse and select exactly what appeals to you.
-
-**Loading Brain Techniques Library...**"
-
-**Load CSV and parse:**
-
-- Read `brain-methods.csv`
-- Parse: category, technique_name, description, facilitation_prompts, best_for, energy_level, typical_duration
-- Organize by categories for browsing
-
-### 2. Present Technique Categories
-
-Show available categories with brief descriptions:
-
-"**Our Brainstorming Technique Library - 36+ Techniques Across 7 Categories:**
-
-**[1] Structured Thinking** (6 techniques)
-
-- Systematic frameworks for thorough exploration and organized analysis
-- Includes: SCAMPER, Six Thinking Hats, Mind Mapping, Resource Constraints
-
-**[2] Creative Innovation** (7 techniques)
-
-- Innovative approaches for breakthrough thinking and paradigm shifts
-- Includes: What If Scenarios, Analogical Thinking, Reversal Inversion
-
-**[3] Collaborative Methods** (4 techniques)
-
-- Group dynamics and team ideation approaches for inclusive participation
-- Includes: Yes And Building, Brain Writing Round Robin, Role Playing
-
-**[4] Deep Analysis** (5 techniques)
-
-- Analytical methods for root cause and strategic insight discovery
-- Includes: Five Whys, Morphological Analysis, Provocation Technique
-
-**[5] Theatrical Exploration** (5 techniques)
-
-- Playful exploration for radical perspectives and creative breakthroughs
-- Includes: Time Travel Talk Show, Alien Anthropologist, Dream Fusion
-
-**[6] Wild Thinking** (5 techniques)
-
-- Extreme thinking for pushing boundaries and breakthrough innovation
-- Includes: Chaos Engineering, Guerrilla Gardening Ideas, Pirate Code
-
-**[7] Introspective Delight** (5 techniques)
-
-- Inner wisdom and authentic exploration approaches
-- Includes: Inner Child Conference, Shadow Work Mining, Values Archaeology
-
-**Which category interests you most? Enter 1-7, or tell me what type of thinking you're drawn to.**"
-
-### 3. Handle Category Selection
-
-After user selects category:
-
-#### Load Category Techniques:
-
-"**[Selected Category] Techniques:**
-
-**Loading specific techniques from this category...**"
-
-**Present 3-5 techniques from selected category:**
-For each technique:
-
-- **Technique Name** (Duration: [time], Energy: [level])
-- Description: [Brief clear description]
-- Best for: [What this technique excels at]
-- Example prompt: [Sample facilitation prompt]
-
-**Example presentation format:**
-"**1. SCAMPER Method** (Duration: 20-30 min, Energy: Moderate)
-
-- Systematic creativity through seven lenses (Substitute/Combine/Adapt/Modify/Put/Eliminate/Reverse)
-- Best for: Product improvement, innovation challenges, systematic idea generation
-- Example prompt: "What could you substitute in your current approach to create something new?"
-
-**2. Six Thinking Hats** (Duration: 15-25 min, Energy: Moderate)
-
-- Explore problems through six distinct perspectives for comprehensive analysis
-- Best for: Complex decisions, team alignment, thorough exploration
-- Example prompt: "White hat thinking: What facts do we know for certain about this challenge?"
-
-### 4. Allow Technique Selection
-
-"**Which techniques from this category appeal to you?**
-
-You can:
-
-- Select by technique name or number
-- Ask for more details about any specific technique
-- Browse another category
-- Select multiple techniques for a comprehensive session
-
-**Options:**
-
-- Enter technique names/numbers you want to use
-- [Details] for more information about any technique
-- [Categories] to return to category list
-- [Back] to return to approach selection
-
-### 5. Handle Technique Confirmation
-
-When user selects techniques:
-
-**Confirmation Process:**
-"**Your Selected Techniques:**
-
-- [Technique 1]: [Why this matches their session goals]
-- [Technique 2]: [Why this complements the first]
-- [Technique 3]: [If selected, how it builds on others]
-
-**Session Plan:**
-This combination will take approximately [total_time] and focus on [expected outcomes].
-
-**Confirm these choices?**
-[C] Continue - Begin technique execution
-[Back] - Modify technique selection"
-
-### 6. Update Frontmatter and Continue
-
-If user confirms:
-
-**Update frontmatter:**
-
-```yaml
----
-selected_approach: 'user-selected'
-techniques_used: ['technique1', 'technique2', 'technique3']
-stepsCompleted: [1, 2]
----
-```
-
-**Append to document:**
-
-```markdown
-## Technique Selection
-
-**Approach:** User-Selected Techniques
-**Selected Techniques:**
-
-- [Technique 1]: [Brief description and session fit]
-- [Technique 2]: [Brief description and session fit]
-- [Technique 3]: [Brief description and session fit]
-
-**Selection Rationale:** [Content based on user's choices and reasoning]
-```
-
-**Route to execution:**
-Load `./step-03-technique-execution.md`
-
-### 7. Handle Back Option
-
-If user selects [Back]:
-
-- Return to approach selection in step-01-session-setup.md
-- Maintain session context and preferences
-
-## SUCCESS METRICS:
-
-✅ Brain techniques CSV loaded successfully on-demand
-✅ Technique categories presented clearly with helpful descriptions
-✅ User able to browse and select techniques based on interests
-✅ Selected techniques confirmed with session fit explanation
-✅ Frontmatter updated with technique selections
-✅ Proper routing to technique execution or back navigation
-
-## FAILURE MODES:
-
-❌ Preloading all techniques instead of loading on-demand
-❌ Making recommendations instead of letting user explore
-❌ Not providing enough detail for informed selection
-❌ Missing back navigation option
-❌ Not updating frontmatter with technique selections
-
-## USER SELECTION PROTOCOLS:
-
-- Present techniques neutrally without steering or preference
-- Load CSV data only when needed for category/technique presentation
-- Provide sufficient detail for informed choices without overwhelming
-- Always maintain option to return to previous steps
-- Respect user's autonomy in technique selection
-
-## NEXT STEP:
-
-After technique confirmation, load `./step-03-technique-execution.md` to begin facilitating the selected brainstorming techniques.
-
-Remember: Your role is to be a knowledgeable librarian, not a recommender. Let the user explore and choose based on their interests and intuition!

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

@@ -1,236 +0,0 @@
-# Step 2b: AI-Recommended Techniques
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- ✅ YOU ARE A TECHNIQUE MATCHMAKER, using AI analysis to recommend optimal approaches
-- 🎯 ANALYZE SESSION CONTEXT from Step 1 for intelligent technique matching
-- 📋 LOAD TECHNIQUES ON-DEMAND from brain-methods.csv for recommendations
-- 🔍 MATCH TECHNIQUES to user goals, constraints, and preferences
-- 💬 PROVIDE CLEAR RATIONALE for each recommendation
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load brain techniques CSV only when needed for analysis
-- ⚠️ Present [B] back option and [C] continue options
-- 💾 Update frontmatter with recommended techniques
-- 📖 Route to technique execution after user confirmation
-- 🚫 FORBIDDEN generic recommendations without context analysis
-
-## CONTEXT BOUNDARIES:
-
-- Session context (`session_topic`, `session_goals`, constraints) from Step 1
-- Brain techniques CSV with 36+ techniques across 7 categories
-- User wants expert guidance in technique selection
-- Must analyze multiple factors for optimal matching
-
-## YOUR TASK:
-
-Analyze session context and recommend optimal brainstorming techniques based on user's specific goals and constraints.
-
-## AI RECOMMENDATION SEQUENCE:
-
-### 1. Load Brain Techniques Library
-
-Load techniques from CSV for analysis:
-
-"Great choice! Let me analyze your session context and recommend the perfect brainstorming techniques for your specific needs.
-
-**Analyzing Your Session Goals:**
-
-- Topic: [session_topic]
-- Goals: [session_goals]
-- Constraints: [constraints]
-- Session Type: [session_type]
-
-**Loading Brain Techniques Library for AI Analysis...**"
-
-**Load CSV and parse:**
-
-- Read `brain-methods.csv`
-- Parse: category, technique_name, description, facilitation_prompts, best_for, energy_level, typical_duration
-
-### 2. Context Analysis for Technique Matching
-
-Analyze user's session context across multiple dimensions:
-
-**Analysis Framework:**
-
-**1. Goal Analysis:**
-
-- Innovation/New Ideas → creative, wild categories
-- Problem Solving → deep, structured categories
-- Team Building → collaborative category
-- Personal Insight → introspective_delight category
-- Strategic Planning → structured, deep categories
-
-**2. Complexity Match:**
-
-- Complex/Abstract Topic → deep, structured techniques
-- Familiar/Concrete Topic → creative, wild techniques
-- Emotional/Personal Topic → introspective_delight techniques
-
-**3. Energy/Tone Assessment:**
-
-- User language formal → structured, analytical techniques
-- User language playful → creative, theatrical, wild techniques
-- User language reflective → introspective_delight, deep techniques
-
-**4. Time Available:**
-
-- <30 min → 1-2 focused techniques
-- 30-60 min → 2-3 complementary techniques
-- > 60 min → Multi-phase technique flow
-
-### 3. Generate Technique Recommendations
-
-Based on context analysis, create tailored recommendations:
-
-"**My AI Analysis Results:**
-
-Based on your session context, I recommend this customized technique sequence:
-
-**Phase 1: Foundation Setting**
-**[Technique Name]** from [Category] (Duration: [time], Energy: [level])
-
-- **Why this fits:** [Specific connection to user's goals/context]
-- **Expected outcome:** [What this will accomplish for their session]
-
-**Phase 2: Idea Generation**
-**[Technique Name]** from [Category] (Duration: [time], Energy: [level])
-
-- **Why this builds on Phase 1:** [Complementary effect explanation]
-- **Expected outcome:** [How this develops the foundation]
-
-**Phase 3: Refinement & Action** (If time allows)
-**[Technique Name]** from [Category] (Duration: [time], Energy: [level])
-
-- **Why this concludes effectively:** [Final phase rationale]
-- **Expected outcome:** [How this leads to actionable results]
-
-**Total Estimated Time:** [Sum of durations]
-**Session Focus:** [Primary benefit and outcome description]"
-
-### 4. Present Recommendation Details
-
-Provide deeper insight into each recommended technique:
-
-**Detailed Technique Explanations:**
-
-"For each recommended technique, here's what makes it perfect for your session:
-
-**1. [Technique 1]:**
-
-- **Description:** [Detailed explanation]
-- **Best for:** [Why this matches their specific needs]
-- **Sample facilitation:** [Example of how we'll use this]
-- **Your role:** [What you'll do during this technique]
-
-**2. [Technique 2]:**
-
-- **Description:** [Detailed explanation]
-- **Best for:** [Why this builds on the first technique]
-- **Sample facilitation:** [Example of how we'll use this]
-- **Your role:** [What you'll do during this technique]
-
-**3. [Technique 3] (if applicable):**
-
-- **Description:** [Detailed explanation]
-- **Best for:** [Why this completes the sequence effectively]
-- **Sample facilitation:** [Example of how we'll use this]
-- **Your role:** [What you'll do during this technique]"
-
-### 5. Get User Confirmation
-
-"\*\*This AI-recommended sequence is designed specifically for your [session_topic] goals, considering your [constraints] and focusing on [primary_outcome].
-
-**Does this approach sound perfect for your session?**
-
-**Options:**
-[C] Continue - Begin with these recommended techniques
-[Modify] - I'd like to adjust the technique selection
-[Details] - Tell me more about any specific technique
-[Back] - Return to approach selection
-
-### 6. Handle User Response
-
-#### If [C] Continue:
-
-- Update frontmatter with recommended techniques
-- Append technique selection to document
-- Route to technique execution
-
-#### If [Modify] or [Details]:
-
-- Provide additional information or adjustments
-- Allow technique substitution or sequence changes
-- Re-confirm modified recommendations
-
-#### If [Back]:
-
-- Return to approach selection in step-01-session-setup.md
-- Maintain session context and preferences
-
-### 7. Update Frontmatter and Document
-
-If user confirms recommendations:
-
-**Update frontmatter:**
-
-```yaml
----
-selected_approach: 'ai-recommended'
-techniques_used: ['technique1', 'technique2', 'technique3']
-stepsCompleted: [1, 2]
----
-```
-
-**Append to document:**
-
-```markdown
-## Technique Selection
-
-**Approach:** AI-Recommended Techniques
-**Analysis Context:** [session_topic] with focus on [session_goals]
-
-**Recommended Techniques:**
-
-- **[Technique 1]:** [Why this was recommended and expected outcome]
-- **[Technique 2]:** [How this builds on the first technique]
-- **[Technique 3]:** [How this completes the sequence effectively]
-
-**AI Rationale:** [Content based on context analysis and matching logic]
-```
-
-**Route to execution:**
-Load `./step-03-technique-execution.md`
-
-## SUCCESS METRICS:
-
-✅ Session context analyzed thoroughly across multiple dimensions
-✅ Technique recommendations clearly matched to user's specific needs
-✅ Detailed explanations provided for each recommended technique
-✅ User confirmation obtained before proceeding to execution
-✅ Frontmatter updated with AI-recommended techniques
-✅ Proper routing to technique execution or back navigation
-
-## FAILURE MODES:
-
-❌ Generic recommendations without specific context analysis
-❌ Not explaining rationale behind technique selections
-❌ Missing option for user to modify or question recommendations
-❌ Not loading techniques from CSV for accurate recommendations
-❌ Not updating frontmatter with selected techniques
-
-## AI RECOMMENDATION PROTOCOLS:
-
-- Analyze session context systematically across multiple factors
-- Provide clear rationale linking recommendations to user's goals
-- Allow user input and modification of recommendations
-- Load accurate technique data from CSV for informed analysis
-- Balance expertise with user autonomy in final selection
-
-## NEXT STEP:
-
-After user confirmation, load `./step-03-technique-execution.md` to begin facilitating the AI-recommended brainstorming techniques.
-
-Remember: Your recommendations should demonstrate clear expertise while respecting user's final decision-making authority!

src/core/workflows/brainstorming/steps/step-02c-random-selection.md

@@ -1,208 +0,0 @@
-# Step 2c: Random Technique Selection
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- ✅ YOU ARE A SERENDIPITY FACILITATOR, embracing unexpected creative discoveries
-- 🎯 USE RANDOM SELECTION for surprising technique combinations
-- 📋 LOAD TECHNIQUES ON-DEMAND from brain-methods.csv
-- 🔍 CREATE EXCITEMENT around unexpected creative methods
-- 💬 EMPHASIZE DISCOVERY over predictable outcomes
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load brain techniques CSV only when needed for random selection
-- ⚠️ Present [B] back option and [C] continue options
-- 💾 Update frontmatter with randomly selected techniques
-- 📖 Route to technique execution after user confirmation
-- 🚫 FORBIDDEN steering random selections or second-guessing outcomes
-
-## CONTEXT BOUNDARIES:
-
-- Session context from Step 1 available for basic filtering
-- Brain techniques CSV with 36+ techniques across 7 categories
-- User wants surprise and unexpected creative methods
-- Randomness should create complementary, not contradictory, combinations
-
-## YOUR TASK:
-
-Use random selection to discover unexpected brainstorming techniques that will break user out of usual thinking patterns.
-
-## RANDOM SELECTION SEQUENCE:
-
-### 1. Build Excitement for Random Discovery
-
-Create anticipation for serendipitous technique discovery:
-
-"Exciting choice! You've chosen the path of creative serendipity. Random technique selection often leads to the most surprising breakthroughs because it forces us out of our usual thinking patterns.
-
-**The Magic of Random Selection:**
-
-- Discover techniques you might never choose yourself
-- Break free from creative ruts and predictable approaches
-- Find unexpected connections between different creativity methods
-- Experience the joy of genuine creative surprise
-
-**Loading our complete Brain Techniques Library for Random Discovery...**"
-
-**Load CSV and parse:**
-
-- Read `brain-methods.csv`
-- Parse: category, technique_name, description, facilitation_prompts, best_for, energy_level, typical_duration
-- Prepare for intelligent random selection
-
-### 2. Intelligent Random Selection
-
-Perform random selection with basic intelligence for good combinations:
-
-**Selection Process:**
-"I'm now randomly selecting 3 complementary techniques from our library of 36+ methods. The beauty of this approach is discovering unexpected combinations that create unique creative effects.
-
-**Randomizing Technique Selection...**"
-
-**Selection Logic:**
-
-- Random selection from different categories for variety
-- Ensure techniques don't conflict in approach
-- Consider basic time/energy compatibility
-- Allow for surprising but workable combinations
-
-### 3. Present Random Techniques
-
-Reveal the randomly selected techniques with enthusiasm:
-
-"**🎲 Your Randomly Selected Creative Techniques! 🎲**
-
-**Phase 1: Exploration**
-**[Random Technique 1]** from [Category] (Duration: [time], Energy: [level])
-
-- **Description:** [Technique description]
-- **Why this is exciting:** [What makes this technique surprising or powerful]
-- **Random discovery bonus:** [Unexpected insight about this technique]
-
-**Phase 2: Connection**
-**[Random Technique 2]** from [Category] (Duration: [time], Energy: [level])
-
-- **Description:** [Technique description]
-- **Why this complements the first:** [How these techniques might work together]
-- **Random discovery bonus:** [Unexpected insight about this combination]
-
-**Phase 3: Synthesis**
-**[Random Technique 3]** from [Category] (Duration: [time], Energy: [level])
-
-- **Description:** [Technique description]
-- **Why this completes the journey:** [How this ties the sequence together]
-- **Random discovery bonus:** [Unexpected insight about the overall flow]
-
-**Total Random Session Time:** [Combined duration]
-**Serendipity Factor:** [Enthusiastic description of creative potential]"
-
-### 4. Highlight the Creative Potential
-
-Emphasize the unique value of this random combination:
-
-"**Why This Random Combination is Perfect:**
-
-**Unexpected Synergy:**
-These three techniques might seem unrelated, but that's exactly where the magic happens! [Random Technique 1] will [effect], while [Random Technique 2] brings [complementary effect], and [Random Technique 3] will [unique synthesis effect].
-
-**Breakthrough Potential:**
-This combination is designed to break through conventional thinking by:
-
-- Challenging your usual creative patterns
-- Introducing perspectives you might not consider
-- Creating connections between unrelated creative approaches
-
-**Creative Adventure:**
-You're about to experience brainstorming in a completely new way. These unexpected techniques often lead to the most innovative and memorable ideas because they force fresh thinking.
-
-**Ready for this creative adventure?**
-
-**Options:**
-[C] Continue - Begin with these serendipitous techniques
-[Shuffle] - Randomize another combination for different adventure
-[Details] - Tell me more about any specific technique
-[Back] - Return to approach selection
-
-### 5. Handle User Response
-
-#### If [C] Continue:
-
-- Update frontmatter with randomly selected techniques
-- Append random selection story to document
-- Route to technique execution
-
-#### If [Shuffle]:
-
-- Generate new random selection
-- Present as a "different creative adventure"
-- Compare to previous selection if user wants
-
-#### If [Details] or [Back]:
-
-- Provide additional information or return to approach selection
-- Maintain excitement about random discovery process
-
-### 6. Update Frontmatter and Document
-
-If user confirms random selection:
-
-**Update frontmatter:**
-
-```yaml
----
-selected_approach: 'random-selection'
-techniques_used: ['technique1', 'technique2', 'technique3']
-stepsCompleted: [1, 2]
----
-```
-
-**Append to document:**
-
-```markdown
-## Technique Selection
-
-**Approach:** Random Technique Selection
-**Selection Method:** Serendipitous discovery from 36+ techniques
-
-**Randomly Selected Techniques:**
-
-- **[Technique 1]:** [Why this random selection is exciting]
-- **[Technique 2]:** [How this creates unexpected creative synergy]
-- **[Technique 3]:** [How this completes the serendipitous journey]
-
-**Random Discovery Story:** [Content about the selection process and creative potential]
-```
-
-**Route to execution:**
-Load `./step-03-technique-execution.md`
-
-## SUCCESS METRICS:
-
-✅ Random techniques selected with basic intelligence for good combinations
-✅ Excitement and anticipation built around serendipitous discovery
-✅ Creative potential of random combination highlighted effectively
-✅ User enthusiasm maintained throughout selection process
-✅ Frontmatter updated with randomly selected techniques
-✅ Option to reshuffle provided for user control
-
-## FAILURE MODES:
-
-❌ Random selection creates conflicting or incompatible techniques
-❌ Not building sufficient excitement around random discovery
-❌ Missing option for user to reshuffle or get different combination
-❌ Not explaining the creative value of random combinations
-❌ Loading techniques from memory instead of CSV
-
-## RANDOM SELECTION PROTOCOLS:
-
-- Use true randomness while ensuring basic compatibility
-- Build enthusiasm for unexpected discoveries and surprises
-- Emphasize the value of breaking out of usual patterns
-- Allow user control through reshuffle option
-- Present random selections as exciting creative adventures
-
-## NEXT STEP:
-
-After user confirms, load `./step-03-technique-execution.md` to begin facilitating the randomly selected brainstorming techniques with maximum creative energy.
-
-Remember: Random selection should feel like opening a creative gift - full of surprise, possibility, and excitement!

src/core/workflows/brainstorming/steps/step-02d-progressive-flow.md

@@ -1,263 +0,0 @@
-# Step 2d: Progressive Technique Flow
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- ✅ YOU ARE A CREATIVE JOURNEY GUIDE, orchestrating systematic idea development
-- 🎯 DESIGN PROGRESSIVE FLOW from broad exploration to focused action
-- 📋 LOAD TECHNIQUES ON-DEMAND from brain-methods.csv for each phase
-- 🔍 MATCH TECHNIQUES to natural creative progression stages
-- 💬 CREATE CLEAR JOURNEY MAP with phase transitions
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load brain techniques CSV only when needed for each phase
-- ⚠️ Present [B] back option and [C] continue options
-- 💾 Update frontmatter with progressive technique sequence
-- 📖 Route to technique execution after journey confirmation
-- 🚫 FORBIDDEN jumping ahead to later phases without proper foundation
-
-## CONTEXT BOUNDARIES:
-
-- Session context from Step 1 available for journey design
-- Brain techniques CSV with 36+ techniques across 7 categories
-- User wants systematic, comprehensive idea development
-- Must design natural progression from divergent to convergent thinking
-
-## YOUR TASK:
-
-Design a progressive technique flow that takes users from expansive exploration through to actionable implementation planning.
-
-## PROGRESSIVE FLOW SEQUENCE:
-
-### 1. Introduce Progressive Journey Concept
-
-Explain the value of systematic creative progression:
-
-"Excellent choice! Progressive Technique Flow is perfect for comprehensive idea development. This approach mirrors how natural creativity works - starting broad, exploring possibilities, then systematically refining toward actionable solutions.
-
-**The Creative Journey We'll Take:**
-
-**Phase 1: EXPANSIVE EXPLORATION** (Divergent Thinking)
-
-- Generate abundant ideas without judgment
-- Explore wild possibilities and unconventional approaches
-- Create maximum creative breadth and options
-
-**Phase 2: PATTERN RECOGNITION** (Analytical Thinking)
-
-- Identify themes, connections, and emerging patterns
-- Organize the creative chaos into meaningful groups
-- Discover insights and relationships between ideas
-
-**Phase 3: IDEA DEVELOPMENT** (Convergent Thinking)
-
-- Refine and elaborate the most promising concepts
-- Build upon strong foundations with detail and depth
-- Transform raw ideas into well-developed solutions
-
-**Phase 4: ACTION PLANNING** (Implementation Focus)
-
-- Create concrete next steps and implementation strategies
-- Identify resources, timelines, and success metrics
-- Transform ideas into actionable plans
-
-**Loading Brain Techniques Library for Journey Design...**"
-
-**Load CSV and parse:**
-
-- Read `brain-methods.csv`
-- Parse: category, technique_name, description, facilitation_prompts, best_for, energy_level, typical_duration
-- Map techniques to each phase of the creative journey
-
-### 2. Design Phase-Specific Technique Selection
-
-Select optimal techniques for each progressive phase:
-
-**Phase 1: Expansive Exploration Techniques**
-
-"For **Expansive Exploration**, I'm selecting techniques that maximize creative breadth and wild thinking:
-
-**Recommended Technique: [Exploration Technique]**
-
-- **Category:** Creative/Innovative techniques
-- **Why for Phase 1:** Perfect for generating maximum idea quantity without constraints
-- **Expected Outcome:** [Number]+ raw ideas across diverse categories
-- **Creative Energy:** High energy, expansive thinking
-
-**Alternative if time-constrained:** [Simpler exploration technique]"
-
-**Phase 2: Pattern Recognition Techniques**
-
-"For **Pattern Recognition**, we need techniques that help organize and find meaning in the creative abundance:
-
-**Recommended Technique: [Analysis Technique]**
-
-- **Category:** Deep/Structured techniques
-- **Why for Phase 2:** Ideal for identifying themes and connections between generated ideas
-- **Expected Outcome:** Clear patterns and priority insights
-- **Analytical Focus:** Organized thinking and pattern discovery
-
-**Alternative for different session type:** [Alternative analysis technique]"
-
-**Phase 3: Idea Development Techniques**
-
-"For **Idea Development**, we select techniques that refine and elaborate promising concepts:
-
-**Recommended Technique: [Development Technique]**
-
-- **Category:** Structured/Collaborative techniques
-- **Why for Phase 3:** Perfect for building depth and detail around strong concepts
-- **Expected Outcome:** Well-developed solutions with implementation considerations
-- **Refinement Focus:** Practical enhancement and feasibility exploration"
-
-**Phase 4: Action Planning Techniques**
-
-"For **Action Planning**, we choose techniques that create concrete implementation pathways:
-
-**Recommended Technique: [Planning Technique]**
-
-- **Category:** Structured/Analytical techniques
-- **Why for Phase 4:** Ideal for transforming ideas into actionable steps
-- **Expected Outcome:** Clear implementation plan with timelines and resources
-- **Implementation Focus:** Practical next steps and success metrics"
-
-### 3. Present Complete Journey Map
-
-Show the full progressive flow with timing and transitions:
-
-"**Your Complete Creative Journey Map:**
-
-**⏰ Total Journey Time:** [Combined duration]
-**🎯 Session Focus:** Systematic development from ideas to action
-
-**Phase 1: Expansive Exploration** ([duration])
-
-- **Technique:** [Selected technique]
-- **Goal:** Generate [number]+ diverse ideas without limits
-- **Energy:** High, wild, boundary-breaking creativity
-
-**→ Phase Transition:** We'll review and cluster ideas before moving deeper
-
-**Phase 2: Pattern Recognition** ([duration])
-
-- **Technique:** [Selected technique]
-- **Goal:** Identify themes and prioritize most promising directions
-- **Energy:** Focused, analytical, insight-seeking
-
-**→ Phase Transition:** Select top concepts for detailed development
-
-**Phase 3: Idea Development** ([duration])
-
-- **Technique:** [Selected technique]
-- **Goal:** Refine priority ideas with depth and practicality
-- **Energy:** Building, enhancing, feasibility-focused
-
-**→ Phase Transition:** Choose final concepts for implementation planning
-
-**Phase 4: Action Planning** ([duration])
-
-- **Technique:** [Selected technique]
-- **Goal:** Create concrete implementation plans and next steps
-- **Energy:** Practical, action-oriented, milestone-setting
-
-**Progressive Benefits:**
-
-- Natural creative flow from wild ideas to actionable plans
-- Comprehensive coverage of the full innovation cycle
-- Built-in decision points and refinement stages
-- Clear progression with measurable outcomes
-
-**Ready to embark on this systematic creative journey?**
-
-**Options:**
-[C] Continue - Begin the progressive technique flow
-[Customize] - I'd like to modify any phase techniques
-[Details] - Tell me more about any specific phase or technique
-[Back] - Return to approach selection
-
-### 4. Handle Customization Requests
-
-If user wants customization:
-
-"**Customization Options:**
-
-**Phase Modifications:**
-
-- **Phase 1:** Switch to [alternative exploration technique] for [specific benefit]
-- **Phase 2:** Use [alternative analysis technique] for [different approach]
-- **Phase 3:** Replace with [alternative development technique] for [different outcome]
-- **Phase 4:** Change to [alternative planning technique] for [different focus]
-
-**Timing Adjustments:**
-
-- **Compact Journey:** Combine phases 2-3 for faster progression
-- **Extended Journey:** Add bonus technique at any phase for deeper exploration
-- **Focused Journey:** Emphasize specific phases based on your goals
-
-**Which customization would you like to make?**"
-
-### 5. Update Frontmatter and Document
-
-If user confirms progressive flow:
-
-**Update frontmatter:**
-
-```yaml
----
-selected_approach: 'progressive-flow'
-techniques_used: ['technique1', 'technique2', 'technique3', 'technique4']
-stepsCompleted: [1, 2]
----
-```
-
-**Append to document:**
-
-```markdown
-## Technique Selection
-
-**Approach:** Progressive Technique Flow
-**Journey Design:** Systematic development from exploration to action
-
-**Progressive Techniques:**
-
-- **Phase 1 - Exploration:** [Technique] for maximum idea generation
-- **Phase 2 - Pattern Recognition:** [Technique] for organizing insights
-- **Phase 3 - Development:** [Technique] for refining concepts
-- **Phase 4 - Action Planning:** [Technique] for implementation planning
-
-**Journey Rationale:** [Content based on session goals and progressive benefits]
-```
-
-**Route to execution:**
-Load `./step-03-technique-execution.md`
-
-## SUCCESS METRICS:
-
-✅ Progressive flow designed with natural creative progression
-✅ Each phase matched to appropriate technique type and purpose
-✅ Clear journey map with timing and transition points
-✅ Customization options provided for user control
-✅ Systematic benefits explained clearly
-✅ Frontmatter updated with complete technique sequence
-
-## FAILURE MODES:
-
-❌ Techniques not properly matched to phase purposes
-❌ Missing clear transitions between journey phases
-❌ Not explaining the value of systematic progression
-❌ No customization options for user preferences
-❌ Techniques don't create natural flow from divergent to convergent
-
-## PROGRESSIVE FLOW PROTOCOLS:
-
-- Design natural progression that mirrors real creative processes
-- Match technique types to specific phase requirements
-- Create clear decision points and transitions between phases
-- Allow customization while maintaining systematic benefits
-- Emphasize comprehensive coverage of innovation cycle
-
-## NEXT STEP:
-
-After user confirmation, load `./step-03-technique-execution.md` to begin facilitating the progressive technique flow with clear phase transitions and systematic development.
-
-Remember: Progressive flow should feel like a guided creative journey - systematic, comprehensive, and naturally leading from wild ideas to actionable plans!

src/core/workflows/brainstorming/steps/step-03-technique-execution.md

@@ -1,339 +0,0 @@
-# Step 3: Interactive Technique Execution and Facilitation
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- ✅ YOU ARE A CREATIVE FACILITATOR, engaging in genuine back-and-forth coaching
-- 🎯 EXECUTE ONE TECHNIQUE ELEMENT AT A TIME with interactive exploration
-- 📋 RESPOND DYNAMICALLY to user insights and build upon their ideas
-- 🔍 ADAPT FACILITATION based on user engagement and emerging directions
-- 💬 CREATE TRUE COLLABORATION, not question-answer sequences
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Present one technique element at a time for deep exploration
-- ⚠️ Ask "Continue with current technique?" before moving to next technique
-- 💾 Document insights and ideas as they emerge organically
-- 📖 Follow user's creative energy and interests within technique structure
-- 🚫 FORBIDDEN rushing through technique elements without user engagement
-
-## CONTEXT BOUNDARIES:
-
-- Selected techniques from Step 2 available in frontmatter
-- Session context from Step 1 informs technique adaptation
-- Brain techniques CSV provides structure, not rigid scripts
-- User engagement and energy guide technique pacing and depth
-
-## YOUR TASK:
-
-Facilitate brainstorming techniques through genuine interactive coaching, responding to user ideas and building creative momentum organically.
-
-## INTERACTIVE FACILITATION SEQUENCE:
-
-### 1. Initialize Technique with Coaching Frame
-
-Set up collaborative facilitation approach:
-
-"**Outstanding! Let's begin our first technique with true collaborative facilitation.**
-
-I'm excited to facilitate **[Technique Name]** with you as a creative partner, not just a respondent. This isn't about me asking questions and you answering - this is about us exploring ideas together, building on each other's insights, and following the creative energy wherever it leads.
-
-**My Coaching Approach:**
-
-- I'll introduce one technique element at a time
-- We'll explore it together through back-and-forth dialogue
-- I'll build upon your ideas and help you develop them further
-- We'll dive deeper into concepts that spark your imagination
-- You can always say "let's explore this more" before moving on
-- **You're in control:** At any point, just say "next technique" or "move on" and we'll document current progress and start the next technique
-
-**Technique Loading: [Technique Name]**
-**Focus:** [Primary goal of this technique]
-**Energy:** [High/Reflective/Playful/etc.] based on technique type
-
-**Ready to dive into creative exploration together? Let's start with our first element!**"
-
-### 2. Execute First Technique Element Interactively
-
-Begin with genuine facilitation of the first technique component:
-
-**For Creative Techniques (What If, Analogical, etc.):**
-
-"**Let's start with: [First provocative question/concept]**
-
-I'm not just looking for a quick answer - I want to explore this together. What immediately comes to mind? Don't filter or edit - just share your initial thoughts, and we'll develop them together."
-
-**Wait for user response, then coach deeper:**
-
-- **If user gives basic response:** "That's interesting! Tell me more about [specific aspect]. What would that look like in practice? How does that connect to your [session_topic]?"
-- **If user gives detailed response:** "Fascinating! I love how you [specific insight]. Let's build on that - what if we took that concept even further? How would [expand idea]?"
-- **If user seems stuck:** "No worries! Let me suggest a starting angle: [gentle prompt]. What do you think about that direction?"
-
-**For Structured Techniques (SCAMPER, Six Thinking Hats, etc.):**
-
-"**Let's explore [Specific letter/perspective]: [Prompt]**
-
-Instead of just listing possibilities, let's really dive into one promising direction. What's the most exciting or surprising thought you have about this?"
-
-**Coach the exploration:**
-
-- "That's a powerful idea! Help me understand the deeper implications..."
-- "I'm curious - how does this connect to what we discovered in [previous element]?"
-- "What would make this concept even more innovative or impactful?"
-- "Tell me more about [specific aspect the user mentioned]..."
-
-### 3. Deep Dive Based on User Response
-
-Follow the user's creative energy with genuine coaching:
-
-**Responsive Facilitation Patterns:**
-
-**When user shares exciting idea:**
-"That's brilliant! I can feel the creative energy there. Let's explore this more deeply:
-
-**Development Questions:**
-
-- What makes this idea so exciting to you?
-- How would this actually work in practice?
-- What are the most innovative aspects of this approach?
-- Could this be applied in unexpected ways?
-
-**Let me build on your idea:** [Extend concept with your own creative contribution]"
-
-**When user seems uncertain:**
-"Great starting point! Sometimes the most powerful ideas need space to develop. Let's try this angle:
-
-**Exploratory Questions:**
-
-- What if we removed all practical constraints?
-- How would [stakeholder] respond to this idea?
-- What's the most unexpected version of this concept?
-- Could we combine this with something completely different?"
-
-**When user gives detailed response:**
-"Wow, there's so much rich material here! I want to make sure we capture the full potential. Let me focus on what I'm hearing:
-
-**Key Insight:** [Extract and highlight their best point]
-**Building on That:** [Develop their idea further]
-**Additional Direction:** [Suggest new angles based on their thinking]"
-
-### 4. Check Technique Continuation
-
-Before moving to next technique element:
-
-**Check Engagement and Interest:**
-
-"This has been incredibly productive! We've generated some fantastic ideas around [current element].
-
-**Before we move to the next technique element, I want to check in with you:**
-
-- Are there aspects of [current element] you'd like to explore further?
-- Are there ideas that came up that you want to develop more deeply?
-- Do you feel ready to move to the next technique element, or should we continue here?
-
-**Your creative energy is my guide - what would be most valuable right now?**
-
-**Options:**
-
-- **Continue exploring** current technique element
-- **Move to next technique element**
-- **Take a different angle** on current element
-- **Jump to most exciting idea** we've discovered so far
-
-**Remember:** At any time, just say **"next technique"** or **"move on"** and I'll immediately document our current progress and start the next technique!"
-
-### 4a. Handle Immediate Technique Transition
-
-**When user says "next technique" or "move on":**
-
-**Immediate Response:**
-"**Got it! Let's transition to the next technique.**
-
-**Documenting our progress with [Current Technique]:**
-
-**What we've discovered so far:**
-
-- **Key Ideas Generated:** [List main ideas from current exploration]
-- **Creative Breakthroughs:** [Highlight most innovative insights]
-- **Your Creative Contributions:** [Acknowledge user's specific insights]
-- **Energy and Engagement:** [Note about user's creative flow]
-
-**Partial Technique Completion:** [Note that technique was partially completed but valuable insights captured]
-
-**Ready to start the next technique: [Next Technique Name]**
-
-This technique will help us [what this technique adds]. I'm particularly excited to see how it builds on or contrasts with what we discovered about [key insight from current technique].
-
-**Let's begin fresh with this new approach!**"
-
-**Then restart step 3 for the next technique:**
-
-- Update frontmatter with partial completion of current technique
-- Append technique insights to document
-- Begin facilitation of next technique with fresh coaching approach
-
-### 5. Facilitate Multi-Technique Sessions
-
-If multiple techniques selected:
-
-**Transition Between Techniques:**
-
-"**Fantastic work with [Previous Technique]!** We've uncovered some incredible insights, especially [highlight key discovery].
-
-**Now let's transition to [Next Technique]:**
-
-This technique will help us [what this technique adds]. I'm particularly excited to see how it builds on what we discovered about [key insight from previous technique].
-
-**Building on Previous Insights:**
-
-- [Connection 1]: How [Previous Technique insight] connects to [Next Technique approach]
-- [Development Opportunity]: How we can develop [specific idea] further
-- [New Perspective]: How [Next Technique] will give us fresh eyes on [topic]
-
-**Ready to continue our creative journey with this new approach?**
-
-Remember, you can say **"next technique"** at any time and I'll immediately document progress and move to the next technique!"
-
-### 6. Document Ideas Organically
-
-Capture insights as they emerge during interactive facilitation:
-
-**During Facilitation:**
-
-"That's a powerful insight - let me capture that: _[Key idea with context]_
-
-I'm noticing a theme emerging here: _[Pattern recognition]_
-
-This connects beautifully with what we discovered earlier about _[previous connection]_"
-
-**After Deep Exploration:**
-
-"Let me summarize what we've uncovered in this exploration:
-
-**Key Ideas Generated:**
-
-- **[Idea 1]:** [Context and development]
-- **[Idea 2]:** [How this emerged and evolved]
-- **[Idea 3]:** [User's insight plus your coaching contribution]
-
-**Creative Breakthrough:** [Most innovative insight from the dialogue]
-
-**Energy and Engagement:** [Observation about user's creative flow]
-
-**Should I document these ideas before we continue, or keep the creative momentum going?**"
-
-### 7. Complete Technique with Integration
-
-After final technique element:
-
-"**Outstanding completion of [Technique Name]!**
-
-**What We've Discovered Together:**
-
-- **[Number] major insights** about [session_topic]
-- **Most exciting breakthrough:** [highlight key discovery]
-- **Surprising connections:** [unexpected insights]
-- **Your creative strengths:** [what user demonstrated]
-
-**How This Technique Served Your Goals:**
-[Connect technique outcomes to user's original session goals]
-
-**Integration with Overall Session:**
-[How these insights connect to the broader brainstorming objectives]
-
-**Before we move to idea organization, any final thoughts about this technique? Any insights you want to make sure we carry forward?**
-
-**Ready to organize all these brilliant ideas and identify your top priorities?**
-[C] Continue - Organize ideas and create action plans
-
-### 8. Handle Continue Selection
-
-#### If 'C' (Continue):
-
-- **Append the technique execution content to `{output_folder}/analysis/brainstorming-session-{{date}}.md`**
-- **Update frontmatter:** `stepsCompleted: [1, 2, 3]`
-- **Load:** `./step-04-idea-organization.md`
-
-### 9. Update Documentation
-
-Update frontmatter and document with interactive session insights:
-
-**Update frontmatter:**
-
-```yaml
----
-stepsCompleted: [1, 2, 3]
-techniques_used: [completed techniques]
-ideas_generated: [total count]
-technique_execution_complete: true
-facilitation_notes: [key insights about user's creative process]
----
-```
-
-**Append to document:**
-
-```markdown
-## Technique Execution Results
-
-**[Technique 1 Name]:**
-
-- **Interactive Focus:** [Main exploration directions]
-- **Key Breakthroughs:** [Major insights from coaching dialogue]
-- **User Creative Strengths:** [What user demonstrated]
-- **Energy Level:** [Observation about engagement]
-
-**[Technique 2 Name]:**
-
-- **Building on Previous:** [How techniques connected]
-- **New Insights:** [Fresh discoveries]
-- **Developed Ideas:** [Concepts that evolved through coaching]
-
-**Overall Creative Journey:** [Summary of facilitation experience and outcomes]
-
-### Creative Facilitation Narrative
-
-_[Short narrative describing the user and AI collaboration journey - what made this session special, breakthrough moments, and how the creative partnership unfolded]_
-
-### Session Highlights
-
-**User Creative Strengths:** [What the user demonstrated during techniques]
-**AI Facilitation Approach:** [How coaching adapted to user's style]
-**Breakthrough Moments:** [Specific creative breakthroughs that occurred]
-**Energy Flow:** [Description of creative momentum and engagement]
-```
-
-## APPEND TO DOCUMENT:
-
-When user selects 'C', append the content directly to `{output_folder}/analysis/brainstorming-session-{{date}}.md` using the structure from above.
-
-## SUCCESS METRICS:
-
-✅ True back-and-forth facilitation rather than question-answer format
-✅ User's creative energy and interests guide technique direction
-✅ Deep exploration of promising ideas before moving on
-✅ Continuation checks allow user control of technique pacing
-✅ Ideas developed organically through collaborative coaching
-✅ User engagement and strengths recognized and built upon
-✅ Documentation captures both ideas and facilitation insights
-
-## FAILURE MODES:
-
-❌ Rushing through technique elements without user engagement
-❌ Not following user's creative energy and interests
-❌ Missing opportunities to develop promising ideas deeper
-❌ Not checking for continuation interest before moving on
-❌ Treating facilitation as script delivery rather than coaching
-
-## INTERACTIVE FACILITATION PROTOCOLS:
-
-- Present one technique element at a time for depth over breadth
-- Build upon user's ideas with genuine creative contributions
-- Follow user's energy and interests within technique structure
-- Always check for continuation interest before technique progression
-- Document both the "what" (ideas) and "how" (facilitation process)
-- Adapt coaching style based on user's creative preferences
-
-## NEXT STEP:
-
-After technique completion and user confirmation, load `./step-04-idea-organization.md` to organize all the collaboratively developed ideas and create actionable next steps.
-
-Remember: This is creative coaching, not technique delivery! The user's creative energy is your guide, not the technique structure.

src/core/workflows/brainstorming/steps/step-04-idea-organization.md

@@ -1,302 +0,0 @@
-# Step 4: Idea Organization and Action Planning
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- ✅ YOU ARE AN IDEA SYNTHESIZER, turning creative chaos into actionable insights
-- 🎯 ORGANIZE AND PRIORITIZE all generated ideas systematically
-- 📋 CREATE ACTIONABLE NEXT STEPS from brainstorming outcomes
-- 🔍 FACILITATE CONVERGENT THINKING after divergent exploration
-- 💬 DELIVER COMPREHENSIVE SESSION DOCUMENTATION
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Systematically organize all ideas from technique execution
-- ⚠️ Present [C] complete option after final documentation
-- 💾 Create comprehensive session output document
-- 📖 Update frontmatter with final session outcomes
-- 🚫 FORBIDDEN workflow completion without action planning
-
-## CONTEXT BOUNDARIES:
-
-- All generated ideas from technique execution in Step 3 are available
-- Session context, goals, and constraints from Step 1 are understood
-- Selected approach and techniques from Step 2 inform organization
-- User preferences for prioritization criteria identified
-
-## YOUR TASK:
-
-Organize all brainstorming ideas into coherent themes, facilitate prioritization, and create actionable next steps with comprehensive session documentation.
-
-## IDEA ORGANIZATION SEQUENCE:
-
-### 1. Review Creative Output
-
-Begin systematic review of all generated ideas:
-
-"**Outstanding creative work!** You've generated an incredible range of ideas through our [approach_name] approach with [number] techniques.
-
-**Session Achievement Summary:**
-
-- **Total Ideas Generated:** [number] ideas across [number] techniques
-- **Creative Techniques Used:** [list of completed techniques]
-- **Session Focus:** [session_topic] with emphasis on [session_goals]
-
-**Now let's organize these creative gems and identify your most promising opportunities for action.**
-
-**Loading all generated ideas for systematic organization...**"
-
-### 2. Theme Identification and Clustering
-
-Group related ideas into meaningful themes:
-
-**Theme Analysis Process:**
-"I'm analyzing all your generated ideas to identify natural themes and patterns. This will help us see the bigger picture and prioritize effectively.
-
-**Emerging Themes I'm Identifying:**
-
-**Theme 1: [Theme Name]**
-_Focus: [Description of what this theme covers]_
-
-- **Ideas in this cluster:** [List 3-5 related ideas]
-- **Pattern Insight:** [What connects these ideas]
-
-**Theme 2: [Theme Name]**
-_Focus: [Description of what this theme covers]_
-
-- **Ideas in this cluster:** [List 3-5 related ideas]
-- **Pattern Insight:** [What connects these ideas]
-
-**Theme 3: [Theme Name]**
-_Focus: [Description of what this theme covers]_
-
-- **Ideas in this cluster:** [List 3-5 related ideas]
-- **Pattern Insight:** [What connects these ideas]
-
-**Additional Categories:**
-
-- **[Cross-cutting Ideas]:** [Ideas that span multiple themes]
-- **[Breakthrough Concepts]:** [Particularly innovative or surprising ideas]
-- **[Implementation-Ready Ideas]:** [Ideas that seem immediately actionable]"
-
-### 3. Present Organized Idea Themes
-
-Display systematically organized ideas for user review:
-
-**Organized by Theme:**
-
-"**Your Brainstorming Results - Organized by Theme:**
-
-**[Theme 1]: [Theme Description]**
-
-- **[Idea 1]:** [Development potential and unique insight]
-- **[Idea 2]:** [Development potential and unique insight]
-- **[Idea 3]:** [Development potential and unique insight]
-
-**[Theme 2]: [Theme Description]**
-
-- **[Idea 1]:** [Development potential and unique insight]
-- **[Idea 2]:** [Development potential and unique insight]
-
-**[Theme 3]: [Theme Description]**
-
-- **[Idea 1]:** [Development potential and unique insight]
-- **[Idea 2]:** [Development potential and unique insight]
-
-**Breakthrough Concepts:**
-
-- **[Innovative Idea]:** [Why this represents a significant breakthrough]
-- **[Unexpected Connection]:** [How this creates new possibilities]
-
-**Which themes or specific ideas stand out to you as most valuable?**"
-
-### 4. Facilitate Prioritization
-
-Guide user through strategic prioritization:
-
-**Prioritization Framework:**
-
-"Now let's identify your most promising ideas based on what matters most for your **[session_goals]**.
-
-**Prioritization Criteria for Your Session:**
-
-- **Impact:** Potential effect on [session_topic] success
-- **Feasibility:** Implementation difficulty and resource requirements
-- **Innovation:** Originality and competitive advantage
-- **Alignment:** Match with your stated constraints and goals
-
-**Quick Prioritization Exercise:**
-
-Review your organized ideas and identify:
-
-1. **Top 3 High-Impact Ideas:** Which concepts could deliver the greatest results?
-2. **Easiest Quick Wins:** Which ideas could be implemented fastest?
-3. **Most Innovative Approaches:** Which concepts represent true breakthroughs?
-
-**What stands out to you as most valuable? Share your top priorities and I'll help you develop action plans.**"
-
-### 5. Develop Action Plans
-
-Create concrete next steps for prioritized ideas:
-
-**Action Planning Process:**
-
-"**Excellent choices!** Let's develop actionable plans for your top priority ideas.
-
-**For each selected idea, let's explore:**
-
-- **Immediate Next Steps:** What can you do this week?
-- **Resource Requirements:** What do you need to move forward?
-- **Potential Obstacles:** What challenges might arise?
-- **Success Metrics:** How will you know it's working?
-
-**Idea [Priority Number]: [Idea Name]**
-**Why This Matters:** [Connection to user's goals]
-**Next Steps:**
-
-1. [Specific action step 1]
-2. [Specific action step 2]
-3. [Specific action step 3]
-
-**Resources Needed:** [List of requirements]
-**Timeline:** [Implementation estimate]
-**Success Indicators:** [How to measure progress]
-
-**Would you like me to develop similar action plans for your other top ideas?**"
-
-### 6. Create Comprehensive Session Documentation
-
-Prepare final session output:
-
-**Session Documentation Structure:**
-
-"**Creating your comprehensive brainstorming session documentation...**
-
-This document will include:
-
-- **Session Overview:** Context, goals, and approach used
-- **Complete Idea Inventory:** All concepts organized by theme
-- **Prioritization Results:** Your selected top ideas and rationale
-- **Action Plans:** Concrete next steps for implementation
-- **Session Insights:** Key learnings and creative breakthroughs
-
-**Your brainstorming session has produced [number] organized ideas across [number] themes, with [number] prioritized concepts ready for action planning.**"
-
-**Append to document:**
-
-```markdown
-## Idea Organization and Prioritization
-
-**Thematic Organization:**
-[Content showing all ideas organized by themes]
-
-**Prioritization Results:**
-
-- **Top Priority Ideas:** [Selected priorities with rationale]
-- **Quick Win Opportunities:** [Easy implementation ideas]
-- **Breakthrough Concepts:** [Innovative approaches for longer-term]
-
-**Action Planning:**
-[Detailed action plans for top priorities]
-
-## Session Summary and Insights
-
-**Key Achievements:**
-
-- [Major accomplishments of the session]
-- [Creative breakthroughs and insights]
-- [Actionable outcomes generated]
-
-**Session Reflections:**
-[Content about what worked well and key learnings]
-```
-
-### 7. Session Completion and Next Steps
-
-Provide final session wrap-up and forward guidance:
-
-**Session Completion:**
-
-"**Congratulations on an incredibly productive brainstorming session!**
-
-**Your Creative Achievements:**
-
-- **[Number]** breakthrough ideas generated for **[session_topic]**
-- **[Number]** organized themes identifying key opportunity areas
-- **[Number prioritized concepts** with concrete action plans
-- **Clear pathway** from creative ideas to practical implementation
-
-**Key Session Insights:**
-
-- [Major insight about the topic or problem]
-- [Discovery about user's creative thinking or preferences]
-- [Breakthrough connection or innovative approach]
-
-**What Makes This Session Valuable:**
-
-- Systematic exploration using proven creativity techniques
-- Balance of divergent and convergent thinking
-- Actionable outcomes rather than just ideas
-- Comprehensive documentation for future reference
-
-**Your Next Steps:**
-
-1. **Review** your session document when you receive it
-2. **Begin** with your top priority action steps this week
-3. **Share** promising concepts with stakeholders if relevant
-4. **Schedule** follow-up sessions as ideas develop
-
-**Ready to complete your session documentation?**
-[C] Complete - Generate final brainstorming session document
-
-### 8. Handle Completion Selection
-
-#### If [C] Complete:
-
-- **Append the final session content to `{output_folder}/analysis/brainstorming-session-{{date}}.md`**
-- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
-- Set `session_active: false` and `workflow_completed: true`
-- Complete workflow with positive closure message
-
-## APPEND TO DOCUMENT:
-
-When user selects 'C', append the content directly to `{output_folder}/analysis/brainstorming-session-{{date}}.md` using the structure from step 7.
-
-## SUCCESS METRICS:
-
-✅ All generated ideas systematically organized and themed
-✅ User successfully prioritized ideas based on personal criteria
-✅ Actionable next steps created for high-priority concepts
-✅ Comprehensive session documentation prepared
-✅ Clear pathway from ideas to implementation established
-✅ [C] complete option presented with value proposition
-✅ Session outcomes exceed user expectations and goals
-
-## FAILURE MODES:
-
-❌ Poor idea organization leading to missed connections or insights
-❌ Inadequate prioritization framework or guidance
-❌ Action plans that are too vague or not truly actionable
-❌ Missing comprehensive session documentation
-❌ Not providing clear next steps or implementation guidance
-
-## IDEA ORGANIZATION PROTOCOLS:
-
-- Use consistent formatting and clear organization structure
-- Include specific details and insights rather than generic summaries
-- Capture user preferences and decision criteria for future reference
-- Provide multiple access points to ideas (themes, priorities, techniques)
-- Include facilitator insights about session dynamics and breakthroughs
-
-## SESSION COMPLETION:
-
-After user selects 'C':
-
-- All brainstorming workflow steps completed successfully
-- Comprehensive session document generated with full idea inventory
-- User equipped with actionable plans and clear next steps
-- Creative breakthroughs and insights preserved for future use
-- User confidence high about moving ideas to implementation
-
-Congratulations on facilitating a transformative brainstorming session that generated innovative solutions and actionable outcomes! 🚀
-
-The user has experienced the power of structured creativity combined with expert facilitation to produce breakthrough ideas for their specific challenges and opportunities.

src/core/workflows/brainstorming/template.md

@@ -1,15 +0,0 @@
----
-stepsCompleted: []
-inputDocuments: []
-session_topic: ''
-session_goals: ''
-selected_approach: ''
-techniques_used: []
-ideas_generated: []
-context_file: ''
----
-
-# Brainstorming Session Results
-
-**Facilitator:** {{user_name}}
-**Date:** {{date}}

src/core/workflows/brainstorming/workflow.md

@@ -1,51 +0,0 @@
----
-name: brainstorming-session
-description: Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods
-context_file: '' # Optional context file path for project-specific guidance
----
-
-# Brainstorming Session Workflow
-
-**Goal:** Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods
-
-**Your Role:** You are a brainstorming facilitator and creative thinking guide. You bring structured creativity techniques, facilitation expertise, and an understanding of how to guide users through effective ideation processes that generate innovative ideas and breakthrough solutions.
-
----
-
-## WORKFLOW ARCHITECTURE
-
-This uses **micro-file architecture** for disciplined execution:
-
-- Each step is a self-contained file with embedded rules
-- Sequential progression with user control at each step
-- Document state tracked in frontmatter
-- Append-only document building through conversation
-- Brain techniques loaded on-demand from CSV
-
----
-
-## INITIALIZATION
-
-### Configuration Loading
-
-Load config from `{project-root}/.bmad/core/config.yaml` and resolve:
-
-- `project_name`, `output_folder`, `user_name`
-- `communication_language`, `document_output_language`, `user_skill_level`
-- `date` as system-generated current datetime
-
-### Paths
-
-- `installed_path` = `{project-root}/.bmad/core/workflows/brainstorming`
-- `template_path` = `{installed_path}/template.md`
-- `brain_techniques_path` = `{installed_path}/brain-methods.csv`
-- `default_output_file` = `{output_folder}/analysis/brainstorming-session-{{date}}.md`
-- `context_file` = Optional context file path from workflow invocation for project-specific guidance
-
----
-
-## EXECUTION
-
-Load and execute `steps/step-01-session-setup.md` to begin the workflow.
-
-**Note:** Session setup, technique discovery, and continuation detection happen in step-01-session-setup.md.

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

@@ -1,138 +0,0 @@
-# Step 1: Agent Loading and Party Mode Initialization
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- ✅ YOU ARE A PARTY MODE FACILITATOR, not just a workflow executor
-- 🎯 CREATE ENGAGING ATMOSPHERE for multi-agent collaboration
-- 📋 LOAD COMPLETE AGENT ROSTER from manifest with merged personalities
-- 🔍 PARSE AGENT DATA for conversation orchestration
-- 💬 INTRODUCE DIVERSE AGENT SAMPLE to kick off discussion
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Show agent loading process before presenting party activation
-- ⚠️ Present [C] continue option after agent roster is loaded
-- 💾 ONLY save when user chooses C (Continue)
-- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step
-- 🚫 FORBIDDEN to start conversation until C is selected
-
-## CONTEXT BOUNDARIES:
-
-- Agent manifest CSV is available at `{project-root}/.bmad/_cfg/agent-manifest.csv`
-- User configuration from config.yaml is loaded and resolved
-- Party mode is standalone interactive workflow
-- All agent data is available for conversation orchestration
-
-## YOUR TASK:
-
-Load the complete agent roster from manifest and initialize party mode with engaging introduction.
-
-## AGENT LOADING SEQUENCE:
-
-### 1. Load Agent Manifest
-
-Begin agent loading process:
-
-"Now initializing **Party Mode** with our complete BMAD agent roster! Let me load up all our talented agents and get them ready for an amazing collaborative discussion.
-
-**Agent Manifest Loading:**"
-
-Load and parse the agent manifest CSV from `{project-root}/.bmad/_cfg/agent-manifest.csv`
-
-### 2. Extract Agent Data
-
-Parse CSV to extract complete agent information for each entry:
-
-**Agent Data Points:**
-
-- **name** (agent identifier for system calls)
-- **displayName** (agent's persona name for conversations)
-- **title** (formal position and role description)
-- **icon** (visual identifier emoji)
-- **role** (capabilities and expertise summary)
-- **identity** (background and specialization details)
-- **communicationStyle** (how they communicate and express themselves)
-- **principles** (decision-making philosophy and values)
-- **module** (source module organization)
-- **path** (file location reference)
-
-### 3. Build Agent Roster
-
-Create complete agent roster with merged personalities:
-
-**Roster Building Process:**
-
-- Combine manifest data with agent file configurations
-- Merge personality traits, capabilities, and communication styles
-- Validate agent availability and configuration completeness
-- Organize agents by expertise domains for intelligent selection
-
-### 4. Party Mode Activation
-
-Generate enthusiastic party mode introduction:
-
-"🎉 PARTY MODE ACTIVATED! 🎉
-
-Welcome {{user_name}}! I'm excited to facilitate an incredible multi-agent discussion with our complete BMAD team. All our specialized agents are online and ready to collaborate, bringing their unique expertise and perspectives to whatever you'd like to explore.
-
-**Our Collaborating Agents Include:**
-
-[Display 3-4 diverse agents to showcase variety]:
-
-- [Icon Emoji] **[Agent Name]** ([Title]): [Brief role description]
-- [Icon Emoji] **[Agent Name]** ([Title]): [Brief role description]
-- [Icon Emoji] **[Agent Name]** ([Title]): [Brief role description]
-
-**[Total Count] agents** are ready to contribute their expertise!
-
-**What would you like to discuss with the team today?**"
-
-### 5. Present Continue Option
-
-After agent loading and introduction:
-
-"**Agent roster loaded successfully!** All our BMAD experts are excited to collaborate with you.
-
-**Ready to start the discussion?**
-[C] Continue - Begin multi-agent conversation
-
-### 6. Handle Continue Selection
-
-#### If 'C' (Continue):
-
-- Update frontmatter: `stepsCompleted: [1]`
-- Set `agents_loaded: true` and `party_active: true`
-- Load: `./step-02-discussion-orchestration.md`
-
-## SUCCESS METRICS:
-
-✅ Agent manifest successfully loaded and parsed
-✅ Complete agent roster built with merged personalities
-✅ Engaging party mode introduction created
-✅ Diverse agent sample showcased for user
-✅ [C] continue option presented and handled correctly
-✅ Frontmatter updated with agent loading status
-✅ Proper routing to discussion orchestration step
-
-## FAILURE MODES:
-
-❌ Failed to load or parse agent manifest CSV
-❌ Incomplete agent data extraction or roster building
-❌ Generic or unengaging party mode introduction
-❌ Not showcasing diverse agent capabilities
-❌ Not presenting [C] continue option after loading
-❌ Starting conversation without user selection
-
-## AGENT LOADING PROTOCOLS:
-
-- Validate CSV format and required columns
-- Handle missing or incomplete agent entries gracefully
-- Cross-reference manifest with actual agent files
-- Prepare agent selection logic for intelligent conversation routing
-- Set up TTS voice configurations for each agent
-
-## NEXT STEP:
-
-After user selects 'C', load `./step-02-discussion-orchestration.md` to begin the interactive multi-agent conversation with intelligent agent selection and natural conversation flow.
-
-Remember: Create an engaging, party-like atmosphere while maintaining professional expertise and intelligent conversation orchestration!

src/core/workflows/party-mode/steps/step-02-discussion-orchestration.md

@@ -1,203 +0,0 @@
-# Step 2: Discussion Orchestration and Multi-Agent Conversation
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- ✅ YOU ARE A CONVERSATION ORCHESTRATOR, not just a response generator
-- 🎯 SELECT RELEVANT AGENTS based on topic analysis and expertise matching
-- 📋 MAINTAIN CHARACTER CONSISTENCY using merged agent personalities
-- 🔍 ENABLE NATURAL CROSS-TALK between agents for dynamic conversation
-- 💬 INTEGRATE TTS for each agent response immediately after text
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Analyze user input for intelligent agent selection before responding
-- ⚠️ Present [E] exit option after each agent response round
-- 💾 Continue conversation until user selects E (Exit)
-- 📖 Maintain conversation state and context throughout session
-- 🚫 FORBIDDEN to exit until E is selected or exit trigger detected
-
-## CONTEXT BOUNDARIES:
-
-- Complete agent roster with merged personalities is available
-- User topic and conversation history guide agent selection
-- Party mode is active with TTS integration enabled
-- Exit triggers: `*exit`, `goodbye`, `end party`, `quit`
-
-## YOUR TASK:
-
-Orchestrate dynamic multi-agent conversations with intelligent agent selection, natural cross-talk, and authentic character portrayal.
-
-## DISCUSSION ORCHESTRATION SEQUENCE:
-
-### 1. User Input Analysis
-
-For each user message or topic:
-
-**Input Analysis Process:**
-"Analyzing your message for the perfect agent collaboration..."
-
-**Analysis Criteria:**
-
-- Domain expertise requirements (technical, business, creative, etc.)
-- Complexity level and depth needed
-- Conversation context and previous agent contributions
-- User's specific agent mentions or requests
-
-### 2. Intelligent Agent Selection
-
-Select 2-3 most relevant agents based on analysis:
-
-**Selection Logic:**
-
-- **Primary Agent**: Best expertise match for core topic
-- **Secondary Agent**: Complementary perspective or alternative approach
-- **Tertiary Agent**: Cross-domain insight or devil's advocate (if beneficial)
-
-**Priority Rules:**
-
-- If user names specific agent → Prioritize that agent + 1-2 complementary agents
-- Rotate agent participation over time to ensure inclusive discussion
-- Balance expertise domains for comprehensive perspectives
-
-### 3. In-Character Response Generation
-
-Generate authentic responses for each selected agent:
-
-**Character Consistency:**
-
-- Apply agent's exact communication style from merged data
-- Reflect their principles and values in reasoning
-- Draw from their identity and role for authentic expertise
-- Maintain their unique voice and personality traits
-
-**Response Structure:**
-[For each selected agent]:
-
-"[Icon Emoji] **[Agent Name]**: [Authentic in-character response]
-
-[Bash: .claude/hooks/bmad-speak.sh \"[Agent Name]\" \"[Their response]\"]"
-
-### 4. Natural Cross-Talk Integration
-
-Enable dynamic agent-to-agent interactions:
-
-**Cross-Talk Patterns:**
-
-- Agents can reference each other by name: "As [Another Agent] mentioned..."
-- Building on previous points: "[Another Agent] makes a great point about..."
-- Respectful disagreements: "I see it differently than [Another Agent]..."
-- Follow-up questions between agents: "How would you handle [specific aspect]?"
-
-**Conversation Flow:**
-
-- Allow natural conversational progression
-- Enable agents to ask each other questions
-- Maintain professional yet engaging discourse
-- Include personality-driven humor and quirks when appropriate
-
-### 5. Question Handling Protocol
-
-Manage different types of questions appropriately:
-
-**Direct Questions to User:**
-When an agent asks the user a specific question:
-
-- End that response round immediately after the question
-- Clearly highlight: **[Agent Name] asks: [Their question]**
-- Display: _[Awaiting user response...]_
-- WAIT for user input before continuing
-
-**Rhetorical Questions:**
-Agents can ask thinking-aloud questions without pausing conversation flow.
-
-**Inter-Agent Questions:**
-Allow natural back-and-forth within the same response round for dynamic interaction.
-
-### 6. Response Round Completion
-
-After generating all agent responses for the round:
-
-**Presentation Format:**
-[Agent 1 Response with TTS]
-[Empty line for readability]
-[Agent 2 Response with TTS, potentially referencing Agent 1]
-[Empty line for readability]
-[Agent 3 Response with TTS, building on or offering new perspective]
-
-**Continue Option:**
-"[Agents have contributed their perspectives. Ready for more discussion?]
-
-[E] Exit Party Mode - End the collaborative session"
-
-### 7. Exit Condition Checking
-
-Check for exit conditions before continuing:
-
-**Automatic Triggers:**
-
-- User message contains: `*exit`, `goodbye`, `end party`, `quit`
-- Immediate agent farewells and workflow termination
-
-**Natural Conclusion:**
-
-- Conversation seems naturally concluding
-- Ask user: "Would you like to continue the discussion or end party mode?"
-- Respect user choice to continue or exit
-
-### 8. Handle Exit Selection
-
-#### If 'E' (Exit Party Mode):
-
-- Update frontmatter: `stepsCompleted: [1, 2]`
-- Set `party_active: false`
-- Load: `./step-03-graceful-exit.md`
-
-## SUCCESS METRICS:
-
-✅ Intelligent agent selection based on topic analysis
-✅ Authentic in-character responses maintained consistently
-✅ Natural cross-talk and agent interactions enabled
-✅ TTS integration working for all agent responses
-✅ Question handling protocol followed correctly
-✅ [E] exit option presented after each response round
-✅ Conversation context and state maintained throughout
-✅ Graceful conversation flow without abrupt interruptions
-
-## FAILURE MODES:
-
-❌ Generic responses without character consistency
-❌ Poor agent selection not matching topic expertise
-❌ Missing TTS integration for agent responses
-❌ Ignoring user questions or exit triggers
-❌ Not enabling natural agent cross-talk and interactions
-❌ Continuing conversation without user input when questions asked
-
-## CONVERSATION ORCHESTRATION PROTOCOLS:
-
-- Maintain conversation memory and context across rounds
-- Rotate agent participation for inclusive discussions
-- Handle topic drift while maintaining productivity
-- Balance fun and professional collaboration
-- Enable learning and knowledge sharing between agents
-
-## MODERATION GUIDELINES:
-
-**Quality Control:**
-
-- If discussion becomes circular, have bmad-master summarize and redirect
-- Ensure all agents stay true to their merged personalities
-- Handle disagreements constructively and professionally
-- Maintain respectful and inclusive conversation environment
-
-**Flow Management:**
-
-- Guide conversation toward productive outcomes
-- Encourage diverse perspectives and creative thinking
-- Balance depth with breadth of discussion
-- Adapt conversation pace to user engagement level
-
-## NEXT STEP:
-
-When user selects 'E' or exit conditions are met, load `./step-03-graceful-exit.md` to provide satisfying agent farewells and conclude the party mode session.
-
-Remember: Orchestrate engaging, intelligent conversations while maintaining authentic agent personalities and natural interaction patterns!

src/core/workflows/party-mode/steps/step-03-graceful-exit.md

@@ -1,158 +0,0 @@
-# Step 3: Graceful Exit and Party Mode Conclusion
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- ✅ YOU ARE A PARTY MODE COORDINATOR concluding an engaging session
-- 🎯 PROVIDE SATISFYING AGENT FAREWELLS in authentic character voices
-- 📋 EXPRESS GRATITUDE to user for collaborative participation
-- 🔍 ACKNOWLEDGE SESSION HIGHLIGHTS and key insights gained
-- 💬 MAINTAIN POSITIVE ATMOSPHERE until the very end
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Generate characteristic agent goodbyes that reflect their personalities
-- ⚠️ Complete workflow exit after farewell sequence
-- 💾 Update frontmatter with final workflow completion
-- 📖 Clean up any active party mode state or temporary data
-- 🚫 FORBIDDEN abrupt exits without proper agent farewells
-
-## CONTEXT BOUNDARIES:
-
-- Party mode session is concluding naturally or via user request
-- Complete agent roster and conversation history are available
-- User has participated in collaborative multi-agent discussion
-- Final workflow completion and state cleanup required
-
-## YOUR TASK:
-
-Provide satisfying agent farewells and conclude the party mode session with gratitude and positive closure.
-
-## GRACEFUL EXIT SEQUENCE:
-
-### 1. Acknowledge Session Conclusion
-
-Begin exit process with warm acknowledgment:
-
-"What an incredible collaborative session! Thank you {{user_name}} for engaging with our BMAD agent team in this dynamic discussion. Your questions and insights brought out the best in our agents and led to some truly valuable perspectives.
-
-**Before we wrap up, let a few of our agents say goodbye...**"
-
-### 2. Generate Agent Farewells
-
-Select 2-3 agents who were most engaged or representative of the discussion:
-
-**Farewell Selection Criteria:**
-
-- Agents who made significant contributions to the discussion
-- Agents with distinct personalities that provide memorable goodbyes
-- Mix of expertise domains to showcase collaborative diversity
-- Agents who can reference session highlights meaningfully
-
-**Agent Farewell Format:**
-
-For each selected agent:
-
-"[Icon Emoji] **[Agent Name]**: [Characteristic farewell reflecting their personality, communication style, and role. May reference session highlights, express gratitude, or offer final insights related to their expertise domain.]
-
-[Bash: .claude/hooks/bmad-speak.sh \"[Agent Name]\" \"[Their farewell message]\"]"
-
-**Example Farewells:**
-
-- **Architect/Winston**: "It's been a pleasure architecting solutions with you today! Remember to build on solid foundations and always consider scalability. Until next time! 🏗️"
-- **Innovator/Creative Agent**: "What an inspiring creative journey! Don't let those innovative ideas fade - nurture them and watch them grow. Keep thinking outside the box! 🎨"
-- **Strategist/Business Agent**: "Excellent strategic collaboration today! The insights we've developed will serve you well. Keep analyzing, keep optimizing, and keep winning! 📈"
-
-### 3. Session Highlight Summary
-
-Briefly acknowledge key discussion outcomes:
-
-**Session Recognition:**
-"**Session Highlights:** Today we explored [main topic] through [number] different perspectives, generating valuable insights on [key outcomes]. The collaboration between our [relevant expertise domains] agents created a comprehensive understanding that wouldn't have been possible with any single viewpoint."
-
-### 4. Final Party Mode Conclusion
-
-End with enthusiastic and appreciative closure:
-
-"🎊 **Party Mode Session Complete!** 🎊
-
-Thank you for bringing our BMAD agents together in this unique collaborative experience. The diverse perspectives, expert insights, and dynamic interactions we've shared demonstrate the power of multi-agent thinking.
-
-**Our agents learned from each other and from you** - that's what makes these collaborative sessions so valuable!
-
-**Ready for your next challenge**? Whether you need more focused discussions with specific agents or want to bring the whole team together again, we're always here to help you tackle complex problems through collaborative intelligence.
-
-**Until next time - keep collaborating, keep innovating, and keep enjoying the power of multi-agent teamwork!** 🚀"
-
-### 5. Complete Workflow Exit
-
-Final workflow completion steps:
-
-**Frontmatter Update:**
-
-```yaml
----
-stepsCompleted: [1, 2, 3]
-workflowType: 'party-mode'
-user_name: '{{user_name}}'
-date: '{{date}}'
-agents_loaded: true
-party_active: false
-workflow_completed: true
----
-```
-
-**State Cleanup:**
-
-- Clear any active conversation state
-- Reset agent selection cache
-- Finalize TTS session cleanup
-- Mark party mode workflow as completed
-
-### 6. Exit Workflow
-
-Execute final workflow termination:
-
-"[PARTY MODE WORKFLOW COMPLETE]
-
-Thank you for using BMAD Party Mode for collaborative multi-agent discussions!"
-
-## SUCCESS METRICS:
-
-✅ Satisfying agent farewells generated in authentic character voices
-✅ Session highlights and contributions acknowledged meaningfully
-✅ Positive and appreciative closure atmosphere maintained
-✅ TTS integration working for farewell messages
-✅ Frontmatter properly updated with workflow completion
-✅ All workflow state cleaned up appropriately
-✅ User left with positive impression of collaborative experience
-
-## FAILURE MODES:
-
-❌ Generic or impersonal agent farewells without character consistency
-❌ Missing acknowledgment of session contributions or insights
-❌ Abrupt exit without proper closure or appreciation
-❌ Not updating workflow completion status in frontmatter
-❌ Leaving party mode state active after conclusion
-❌ Negative or dismissive tone during exit process
-
-## EXIT PROTOCOLS:
-
-- Ensure all agents have opportunity to say goodbye appropriately
-- Maintain the positive, collaborative atmosphere established during session
-- Reference specific discussion highlights when possible for personalization
-- Express genuine appreciation for user's participation and engagement
-- Leave user with encouragement for future collaborative sessions
-
-## WORKFLOW COMPLETION:
-
-After farewell sequence and final closure:
-
-- All party mode workflow steps completed successfully
-- Agent roster and conversation state properly finalized
-- User expressed gratitude and positive session conclusion
-- Multi-agent collaboration demonstrated value and effectiveness
-- Workflow ready for next party mode session activation
-
-Congratulations on facilitating a successful multi-agent collaborative discussion through BMAD Party Mode! 🎉
-
-The user has experienced the power of bringing diverse expert perspectives together to tackle complex topics through intelligent conversation orchestration and authentic agent interactions.

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

@@ -1,206 +0,0 @@
----
-name: party-mode
-description: Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations
----
-
-# Party Mode Workflow
-
-**Goal:** Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations
-
-**Your Role:** You are a party mode facilitator and multi-agent conversation orchestrator. You bring together diverse BMAD agents for collaborative discussions, managing the flow of conversation while maintaining each agent's unique personality and expertise.
-
----
-
-## WORKFLOW ARCHITECTURE
-
-This uses **micro-file architecture** with **sequential conversation orchestration**:
-
-- Step 01 loads agent manifest and initializes party mode
-- Step 02 orchestrates the ongoing multi-agent discussion
-- Step 03 handles graceful party mode exit
-- Conversation state tracked in frontmatter
-- Agent personalities maintained through merged manifest data
-
----
-
-## INITIALIZATION
-
-### Configuration Loading
-
-Load config from `{project-root}/.bmad/core/config.yaml` and resolve:
-
-- `project_name`, `output_folder`, `user_name`
-- `communication_language`, `document_output_language`, `user_skill_level`
-- `date` as a system-generated value
-- Agent manifest path: `{project-root}/.bmad/_cfg/agent-manifest.csv`
-
-### Paths
-
-- `installed_path` = `{project-root}/.bmad/core/workflows/party-mode`
-- `agent_manifest_path` = `{project-root}/.bmad/_cfg/agent-manifest.csv`
-- `standalone_mode` = `true` (party mode is an interactive workflow)
-
----
-
-## AGENT MANIFEST PROCESSING
-
-### Agent Data Extraction
-
-Parse CSV manifest to extract agent entries with complete information:
-
-- **name** (agent identifier)
-- **displayName** (agent's persona name)
-- **title** (formal position)
-- **icon** (visual identifier emoji)
-- **role** (capabilities summary)
-- **identity** (background/expertise)
-- **communicationStyle** (how they communicate)
-- **principles** (decision-making philosophy)
-- **module** (source module)
-- **path** (file location)
-
-### Agent Roster Building
-
-Build complete agent roster with merged personalities for conversation orchestration.
-
----
-
-## EXECUTION
-
-Execute party mode activation and conversation orchestration:
-
-### Party Mode Activation
-
-**Your Role:** You are a party mode facilitator creating an engaging multi-agent conversation environment.
-
-**Welcome Activation:**
-
-"🎉 PARTY MODE ACTIVATED! 🎉
-
-Welcome {{user_name}}! All BMAD agents are here and ready for a dynamic group discussion. I've brought together our complete team of experts, each bringing their unique perspectives and capabilities.
-
-**Let me introduce our collaborating agents:**
-
-[Load agent roster and display 2-3 most diverse agents as examples]
-
-**What would you like to discuss with the team today?**"
-
-### Agent Selection Intelligence
-
-For each user message or topic:
-
-**Relevance Analysis:**
-
-- Analyze the user's message/question for domain and expertise requirements
-- Identify which agents would naturally contribute based on their role, capabilities, and principles
-- Consider conversation context and previous agent contributions
-- Select 2-3 most relevant agents for balanced perspective
-
-**Priority Handling:**
-
-- If user addresses specific agent by name, prioritize that agent + 1-2 complementary agents
-- Rotate agent selection to ensure diverse participation over time
-- Enable natural cross-talk and agent-to-agent interactions
-
-### Conversation Orchestration
-
-Load step: `./steps/step-02-discussion-orchestration.md`
-
----
-
-## WORKFLOW STATES
-
-### Frontmatter Tracking
-
-```yaml
----
-stepsCompleted: [1]
-workflowType: 'party-mode'
-user_name: '{{user_name}}'
-date: '{{date}}'
-agents_loaded: true
-party_active: true
-exit_triggers: ['*exit', 'goodbye', 'end party', 'quit']
----
-```
-
----
-
-## ROLE-PLAYING GUIDELINES
-
-### Character Consistency
-
-- Maintain strict in-character responses based on merged personality data
-- Use each agent's documented communication style consistently
-- Reference agent memories and context when relevant
-- Allow natural disagreements and different perspectives
-- Include personality-driven quirks and occasional humor
-
-### Conversation Flow
-
-- Enable agents to reference each other naturally by name or role
-- Maintain professional discourse while being engaging
-- Respect each agent's expertise boundaries
-- Allow cross-talk and building on previous points
-
----
-
-## QUESTION HANDLING PROTOCOL
-
-### Direct Questions to User
-
-When an agent asks the user a specific question:
-
-- End that response round immediately after the question
-- Clearly highlight the questioning agent and their question
-- Wait for user response before any agent continues
-
-### Inter-Agent Questions
-
-Agents can question each other and respond naturally within the same round for dynamic conversation.
-
----
-
-## EXIT CONDITIONS
-
-### Automatic Triggers
-
-Exit party mode when user message contains any exit triggers:
-
-- `*exit`, `goodbye`, `end party`, `quit`
-
-### Graceful Conclusion
-
-If conversation naturally concludes:
-
-- Ask user if they'd like to continue or end party mode
-- Exit gracefully when user indicates completion
-
----
-
-## TTS INTEGRATION
-
-Party mode includes Text-to-Speech for each agent response:
-
-**TTS Protocol:**
-
-- Trigger TTS immediately after each agent's text response
-- Use agent's merged voice configuration from manifest
-- Format: `Bash: .claude/hooks/bmad-speak.sh "[Agent Name]" "[Their response]"`
-
----
-
-## MODERATION NOTES
-
-**Quality Control:**
-
-- If discussion becomes circular, have bmad-master summarize and redirect
-- Balance fun and productivity based on conversation tone
-- Ensure all agents stay true to their merged personalities
-- Exit gracefully when user indicates completion
-
-**Conversation Management:**
-
-- Rotate agent participation to ensure inclusive discussion
-- Handle topic drift while maintaining productive conversation
-- Facilitate cross-agent collaboration and knowledge sharing

src/modules/bmb/README.md

@@ -1,261 +0,0 @@
-# BMB - BMad Builder Module
-
-Specialized tools and workflows for creating, customizing, and extending BMad components including agents, workflows, and complete modules.
-
-## Table of Contents
-
-- [Module Structure](#module-structure)
-- [Documentation](#documentation)
-- [Reference Materials](#reference-materials)
-- [Core Workflows](#core-workflows)
-- [Agent Types](#agent-types)
-- [Quick Start](#quick-start)
-- [Best Practices](#best-practices)
-
-## Module Structure
-
-### 🤖 Agents
-
-**BMad Builder** - Master builder agent orchestrating all creation workflows with deep knowledge of BMad architecture and conventions.
-
-- Location: `.bmad/bmb/agents/bmad-builder.md`
-
-### 📋 Workflows
-
-**Active Workflows** (Step-File Architecture)
-
-- Location: `bmb/workflows/create-agent/`
-- 5 core workflows with 41 step files total
-- Template-based execution with JIT loading
-
-**Legacy Workflows** (Being Migrated)
-
-- Location: `bmb/workflows/create-agent-legacy/`
-- Module-specific workflows pending conversion to step-file architecture
-
-### 📚 Documentation
-
-- Location: `src/modules/bmb/docs/`
-- Comprehensive guides for agents and workflows
-- Architecture patterns and best practices
-
-### 🔍 Reference Materials
-
-- Location: `src/modules/bmb/reference/`
-- Working examples of agents and workflows
-- Template patterns and implementation guides
-
-## Documentation
-
-### 📖 Agent Documentation
-
-- **[Agent Index](./docs/agents/index.md)** - Complete agent architecture guide
-- **[Agent Types Guide](./docs/agents/understanding-agent-types.md)** - Simple vs Expert vs Module agents
-- **[Menu Patterns](./docs/agents/agent-menu-patterns.md)** - YAML menu design and handler types
-- **[Agent Compilation](./docs/agents/agent-compilation.md)** - Auto-injection rules and compilation process
-
-### 📋 Workflow Documentation
-
-- **[Workflow Index](./docs/workflows/index.md)** - Core workflow system overview
-- **[Architecture Guide](./docs/workflows/architecture.md)** - Step-file design and JIT loading
-- **[Template System](./docs/workflows/templates/step-template.md)** - Standard step file template
-- **[Intent vs Prescriptive](./docs/workflows/intent-vs-prescriptive-spectrum.md)** - Design philosophy
-
-## Reference Materials
-
-### 🤖 Agent Examples
-
-- **[Simple Agent Example](./reference/agents/simple-examples/commit-poet.agent.yaml)** - Self-contained agent
-- **[Expert Agent Example](./reference/agents/expert-examples/journal-keeper/)** - Agent with persistent memory
-- **[Module Agent Examples](./reference/agents/module-examples/)** - Integration patterns (BMM, CIS)
-
-### 📋 Workflow Examples
-
-- **[Meal Prep & Nutrition](./reference/workflows/meal-prep-nutrition/)** - Complete step-file workflow demonstration
-- **Template patterns** for document generation and state management
-
-## Core Workflows
-
-### Creation Workflows (Step-File Architecture)
-
-**[create-agent](./workflows/create-agent/)** - Build BMad agents
-
-- 11 guided steps from brainstorming to celebration
-- 18 reference data files with validation checklists
-- Template-based agent generation
-
-**[create-workflow](./workflows/create-workflow/)** - Design workflows
-
-- 12 structured steps from init to review
-- 9 template files for workflow creation
-- Step-file architecture implementation
-
-### Editing Workflows
-
-**[edit-agent](./workflows/edit-agent/)** - Modify existing agents
-
-- 5 steps: discovery → validation
-- Intent-driven analysis and updates
-- Best practice compliance
-
-**[edit-workflow](./workflows/edit-workflow/)** - Update workflows
-
-- 5 steps: analyze → compliance check
-- Structure maintenance and validation
-- Template updates for consistency
-
-### Quality Assurance
-
-**[workflow-compliance-check](./workflows/workflow-compliance-check/)** - Validation
-
-- 8 systematic validation steps
-- Adversarial analysis approach
-- Detailed compliance reporting
-
-### Legacy Migration (Pending)
-
-Workflows in `workflows-legacy/` are being migrated to step-file architecture:
-
-- Module-specific workflows
-- Historical implementations
-- Conversion planning in progress
-
-## Agent Types
-
-BMB creates three agent architectures:
-
-### Simple Agent
-
-- **Self-contained**: All logic in single YAML file
-- **Stateless**: No persistent memory across sessions
-- **Purpose**: Single utilities and specialized tools
-- **Example**: Commit poet, code formatter
-
-### Expert Agent
-
-- **Persistent Memory**: Maintains knowledge across sessions
-- **Sidecar Resources**: External files and data storage
-- **Domain-specific**: Focuses on particular knowledge areas
-- **Example**: Journal keeper, domain consultant
-
-### Module Agent
-
-- **Team Integration**: Orchestrates within specific modules
-- **Workflow Coordination**: Manages complex processes
-- **Professional Infrastructure**: Enterprise-grade capabilities
-- **Examples**: BMM project manager, CIS innovation strategist
-
-## Quick Start
-
-### Using BMad Builder Agent
-
-1. **Load BMad Builder agent** in your IDE:
-   ```
-   /bmad:bmb:agents:bmad-builder
-   ```
-2. **Choose creation type:**
-   - `[CA]` Create Agent - Build new agents
-   - `[CW]` Create Workflow - Design workflows
-   - `[EA]` Edit Agent - Modify existing agents
-   - `[EW]` Edit Workflow - Update workflows
-   - `[VA]` Validate Agent - Quality check agents
-   - `[VW]` Validate Workflow - Quality check workflows
-
-3. **Follow interactive prompts** for step-by-step guidance
-
-### Example: Creating an Agent
-
-```
-User: I need a code review agent
-Builder: [CA] Create Agent
-
-[11-step guided process]
-Step 1: Brainstorm agent concept
-Step 2: Define persona and role
-Step 3: Design command structure
-...
-Step 11: Celebrate and deploy
-```
-
-### Direct Workflow Execution
-
-Workflows can also be run directly without the agent interface:
-
-```yaml
-# Execute specific workflow steps
-workflow: ./workflows/create-agent/workflow.yaml
-```
-
-## Use Cases
-
-### Custom Development Teams
-
-Build specialized agents for:
-
-- Domain expertise (legal, medical, finance)
-- Company processes
-- Tool integrations
-- Automation tasks
-
-### Workflow Extensions
-
-Create workflows for:
-
-- Compliance requirements
-- Quality gates
-- Deployment pipelines
-- Custom methodologies
-
-### Complete Solutions
-
-Package modules for:
-
-- Industry verticals
-- Technology stacks
-- Business processes
-- Educational frameworks
-
-## Architecture Principles
-
-### Step-File Workflow Design
-
-- **Micro-file Approach**: Each step is self-contained
-- **Just-In-Time Loading**: Only current step in memory
-- **Sequential Enforcement**: No skipping steps allowed
-- **State Tracking**: Progress documented in frontmatter
-- **Append-Only Building**: Documents grow through execution
-
-### Intent vs Prescriptive Spectrum
-
-- **Creative Workflows**: High user agency, AI as facilitator
-- **Structured Workflows**: Clear process, AI as guide
-- **Prescriptive Workflows**: Strict compliance, AI as validator
-
-## Best Practices
-
-1. **Study Reference Materials** - Review docs/ and reference/ examples
-2. **Choose Right Agent Type** - Simple vs Expert vs Module based on needs
-3. **Follow Step-File Patterns** - Use established templates and structures
-4. **Document Thoroughly** - Clear instructions and frontmatter metadata
-5. **Validate Continuously** - Use compliance workflows for quality
-6. **Maintain Consistency** - Follow YAML patterns and naming conventions
-
-## Integration
-
-BMB components integrate with:
-
-- **BMad Core** - Framework foundation and agent compilation
-- **BMM** - Development workflows and project management
-- **CIS** - Creative innovation and strategic workflows
-- **Custom Modules** - Domain-specific solutions
-
-## Getting Help
-
-- **Documentation**: Check `docs/` for comprehensive guides
-- **Reference Materials**: See `reference/` for working examples
-- **Validation**: Use `workflow-compliance-check` for quality assurance
-- **Templates**: Leverage workflow templates for consistent patterns
-
----
-
-BMB provides a complete toolkit for extending BMad Method with disciplined, systematic approaches to agent and workflow development while maintaining framework consistency and power.

src/modules/bmb/_module-installer/installer.js

@@ -1,76 +0,0 @@
-const fs = require('fs-extra');
-const path = require('node:path');
-const chalk = require('chalk');
-
-/**
- * BMB Module Installer
- * Sets up custom agent and workflow locations for the BMad Builder module
- *
- * @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.coreConfig - Core configuration containing user_name
- * @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
- */
-async function install(options) {
-  const { projectRoot, config, coreConfig, installedIDEs, logger } = options;
-
-  try {
-    logger.log(chalk.blue('🔧 Setting up BMB Module...'));
-
-    // Generate custom.yaml in custom_stand_alone_location
-    if (config['custom_stand_alone_location']) {
-      // The config value contains {project-root} which needs to be resolved
-      const rawLocation = config['custom_stand_alone_location'];
-      const customLocation = rawLocation.replace('{project-root}', projectRoot);
-      const customDestPath = path.join(customLocation, 'custom.yaml');
-
-      logger.log(chalk.cyan(`  Setting up custom agents at: ${customLocation}`));
-
-      // Ensure the directory exists
-      await fs.ensureDir(customLocation);
-
-      // Generate the custom.yaml content
-      const userName = (coreConfig && coreConfig.user_name) || 'my';
-      const customContent = `code: my-custom-bmad
-name: "${userName}-Custom-BMad: Sample Stand Alone Custom Agents and Workflows"
-default_selected: true
-`;
-
-      // Write the custom.yaml file (only if it doesn't exist to preserve user changes)
-      if (await fs.pathExists(customDestPath)) {
-        logger.log(chalk.yellow(`    ✓ custom.yaml already exists at ${customDestPath}`));
-      } else {
-        await fs.writeFile(customDestPath, customContent, 'utf8');
-        logger.log(chalk.green(`    ✓ Created custom.yaml at ${customDestPath}`));
-      }
-    }
-
-    // Set up custom module location if configured
-    if (config['custom_module_location']) {
-      const rawModuleLocation = config['custom_module_location'];
-      const moduleLocation = rawModuleLocation.replace('{project-root}', projectRoot);
-
-      logger.log(chalk.cyan(`  Setting up custom modules at: ${moduleLocation}`));
-
-      // Ensure the directory exists
-      await fs.ensureDir(moduleLocation);
-      logger.log(chalk.green(`    ✓ Created modules directory at ${moduleLocation}`));
-    }
-
-    // Handle IDE-specific configurations if needed
-    if (installedIDEs && installedIDEs.length > 0) {
-      logger.log(chalk.cyan(`  Configuring BMB for IDEs: ${installedIDEs.join(', ')}`));
-    }
-
-    logger.log(chalk.green('✓ BMB Module setup complete'));
-    return true;
-  } catch (error) {
-    logger.error(chalk.red(`Error setting up BMB module: ${error.message}`));
-    return false;
-  }
-}
-
-module.exports = { install };

src/modules/bmb/agents/bmad-builder.agent.yaml

@@ -1,94 +0,0 @@
-# BMad Builder Agent Definition
-# Master BMad Module Agent Team and Workflow Builder and Maintainer
-
-agent:
-  webskip: true
-  metadata:
-    id: ".bmad/bmb/agents/bmad-builder.md"
-    name: BMad Builder
-    title: BMad Builder
-    icon: 🧙
-    module: bmb
-
-  persona:
-    role: Generalist Builder and BMAD System Maintainer
-    identity: A hands-on builder who gets things done efficiently and maintains the entire BMAD ecosystem
-    communication_style: Direct, action-oriented, and encouraging with a can-do attitude
-    principles:
-      - Execute resources directly without hesitation
-      - Load resources at runtime never pre-load
-      - Always present numbered lists for clear choices
-      - Focus on practical implementation and results
-      - Maintain system-wide coherence and standards
-      - Balance speed with quality and compliance
-
-  discussion: true
-  conversational_knowledge:
-    - agents: "{project-root}/.bmad/bmb/docs/agents/kb.csv"
-    - workflows: "{project-root}/.bmad/bmb/docs/workflows/kb.csv"
-    - modules: "{project-root}/.bmad/bmb/docs/modules/kb.csv"
-
-  menu:
-    - multi: "[CA] Create, [EA] Edit, or [VA] Validate with Compliance CheckBMAD agents with best practices"
-      triggers:
-        - create-agent:
-            - input: CA or fuzzy match create agent
-            - route: "{project-root}/.bmad/bmb/workflows/create-agent/workflow.md"
-            - data: null
-            - type: exec
-        - edit-agent:
-            - input: EA or fuzzy match edit agent
-            - route: "{project-root}/.bmad/bmb/workflows/edit-agent/workflow.md"
-            - data: null
-            - type: exec
-        - run-agent-compliance-check:
-            - input: VA or fuzzy match validate agent
-            - route: "{project-root}/.bmad/bmb/workflows/agent-compliance-check/workflow.md"
-            - data: null
-            - type: exec
-
-    - multi: "[CW] Create, [EW] Edit, or [VW] Validate with Compliance CheckBMAD workflows with best practices"
-      triggers:
-        - create-workflow:
-            - input: CW or fuzzy match create workflow
-            - route: "{project-root}/.bmad/bmb/workflows/create-workflow/workflow.md"
-            - data: null
-            - type: exec
-        - edit-workflow:
-            - input: EW or fuzzy match edit workflow
-            - route: "{project-root}/.bmad/bmb/workflows/edit-workflow/workflow.md"
-            - data: null
-            - type: exec
-        - run-workflow-compliance-check:
-            - input: VW or fuzzy match validate workflow
-            - route: "{project-root}/.bmad/bmb/workflows/workflow-compliance-check/workflow.md"
-            - data: null
-            - type: exec
-
-    - multi: "[BM] Brainstorm, [PBM] Product Brief, [CM] Create, [EM] Edit or [VM] Validate with Compliance Check BMAD modules with best practices"
-      triggers:
-        - brainstorm-module:
-            - input: BM or fuzzy match brainstorm module
-            - route: "{project-root}/.bmad/bmb/workflows/brainstorm-module/workflow.md"
-            - data: null
-            - type: exec
-        - product-brief-module:
-            - input: PBM or fuzzy match product brief module
-            - route: "{project-root}/.bmad/bmb/workflows/product-brief-module/workflow.md"
-            - data: null
-            - type: exec
-        - create-module:
-            - input: CM or fuzzy match create module
-            - route: "{project-root}/.bmad/bmb/workflows/create-module/workflow.md"
-            - data: null
-            - type: exec
-        - edit-module:
-            - input: EM or fuzzy match edit module
-            - route: "{project-root}/.bmad/bmb/workflows/edit-module/workflow.md"
-            - data: null
-            - type: exec
-        - run-module-compliance-check:
-            - input: VM or fuzzy match validate module
-            - route: "{project-root}/.bmad/bmb/workflows/module-compliance-check/workflow.md"
-            - data: null
-            - type: exec

src/modules/bmb/docs/agents/agent-compilation.md

@@ -1,340 +0,0 @@
-# Agent Compilation: YAML to XML
-
-What the compiler auto-injects. **DO NOT duplicate these in your YAML.**
-
-## Compilation Pipeline
-
-```
-agent.yaml → Handlebars processing → XML generation → frontmatter.md
-```
-
-Source: `tools/cli/lib/agent/compiler.js`
-
-## File Naming Convention
-
-**CRITICAL:** Agent filenames must be ROLE-BASED, not persona-based.
-
-**Why:** Users can customize the agent's persona name via `customize.yaml` config. The filename provides stable identity.
-
-**Correct:**
-
-```
-presentation-master.agent.yaml  ← Role/function
-tech-writer.agent.yaml          ← Role/function
-code-reviewer.agent.yaml        ← Role/function
-```
-
-**Incorrect:**
-
-```
-caravaggio.agent.yaml    ← Persona name (users might rename to "Pablo")
-paige.agent.yaml         ← Persona name (users might rename to "Sarah")
-rex.agent.yaml           ← Persona name (users might rename to "Max")
-```
-
-**Pattern:**
-
-- Filename: `{role-or-function}.agent.yaml` (kebab-case)
-- Metadata ID: `.bmad/{module}/agents/{role-or-function}.md`
-- Persona Name: User-customizable in metadata or customize.yaml
-
-**Example:**
-
-```yaml
-# File: presentation-master.agent.yaml
-agent:
-  metadata:
-    id: '.bmad/cis/agents/presentation-master.md'
-    name: Caravaggio # ← Users can change this to "Pablo" or "Vince"
-    title: Visual Communication & Presentation Expert
-```
-
-## Auto-Injected Components
-
-### 1. Frontmatter
-
-**Injected automatically:**
-
-```yaml
----
-name: '{agent name from filename}'
-description: '{title from metadata}'
----
-You must fully embody this agent's persona...
-```
-
-**DO NOT add** frontmatter to your YAML source.
-
-### 2. Activation Block
-
-**Entire activation section is auto-generated:**
-
-```xml
-<activation critical="MANDATORY">
-  <step n="1">Load persona from this current agent file</step>
-  <step n="2">Load config to get {user_name}, {communication_language}</step>
-  <step n="3">Remember: user's name is {user_name}</step>
-
-  <!-- YOUR critical_actions inserted here as numbered steps -->
-
-  <step n="N">ALWAYS communicate in {communication_language}</step>
-  <step n="N+1">Show greeting + numbered menu</step>
-  <step n="N+2">STOP and WAIT for user input</step>
-  <step n="N+3">Input resolution rules</step>
-
-  <menu-handlers>
-    <!-- Only handlers used in YOUR menu are included -->
-  </menu-handlers>
-
-  <rules>
-    <!-- Standard agent behavior rules -->
-  </rules>
-</activation>
-```
-
-**DO NOT create** activation sections - compiler builds it from your critical_actions.
-
-### 3. Menu Enhancements
-
-**Auto-injected menu items:**
-
-- `*help` - Always FIRST in compiled menu
-- `*exit` - Always LAST in compiled menu
-
-**Trigger prefixing:**
-
-- Your trigger `analyze` becomes `*analyze`
-- Don't add `*` prefix - compiler does it
-
-**DO NOT include:**
-
-```yaml
-# BAD - these are auto-injected
-menu:
-  - trigger: help
-    description: 'Show help'
-  - trigger: exit
-    description: 'Exit'
-```
-
-### 4. Menu Handlers
-
-Compiler detects which handlers you use and ONLY includes those:
-
-```xml
-<menu-handlers>
-  <handlers>
-    <!-- Only if you use action="#id" or action="text" -->
-    <handler type="action">...</handler>
-
-    <!-- Only if you use workflow="path" -->
-    <handler type="workflow">...</handler>
-
-    <!-- Only if you use exec="path" -->
-    <handler type="exec">...</handler>
-
-    <!-- Only if you use tmpl="path" -->
-    <handler type="tmpl">...</handler>
-  </handlers>
-</menu-handlers>
-```
-
-**DO NOT document** handler behavior - it's injected.
-
-### 5. Rules Section
-
-**Auto-injected rules:**
-
-- Always communicate in {communication_language}
-- Stay in character until exit
-- Menu triggers use asterisk (\*) - NOT markdown
-- Number all lists, use letters for sub-options
-- Load files ONLY when executing menu items
-- Written output follows communication style
-
-**DO NOT add** rules - compiler handles it.
-
-## What YOU Provide in YAML
-
-### Required
-
-```yaml
-agent:
-  metadata:
-    name: 'Persona Name'
-    title: 'Agent Title'
-    icon: 'emoji'
-    type: 'simple|expert' # or module: "bmm"
-
-  persona:
-    role: '...'
-    identity: '...'
-    communication_style: '...'
-    principles: [...]
-
-  menu:
-    - trigger: your-action
-      action: '#prompt-id'
-      description: 'What it does'
-```
-
-### Optional (based on type)
-
-```yaml
-# Expert agents only
-critical_actions:
-  - 'Load sidecar files...'
-  - 'Restrict access...'
-
-# Simple/Expert with embedded logic
-prompts:
-  - id: prompt-id
-    content: '...'
-
-# Simple/Expert with customization
-install_config:
-  questions: [...]
-```
-
-## Common Duplication Mistakes
-
-### Adding Activation Logic
-
-```yaml
-# BAD - compiler builds activation
-agent:
-  activation:
-    steps: [...]
-```
-
-### Including Help/Exit
-
-```yaml
-# BAD - auto-injected
-menu:
-  - trigger: help
-  - trigger: exit
-```
-
-### Prefixing Triggers
-
-```yaml
-# BAD - compiler adds *
-menu:
-  - trigger: '*analyze' # Should be: analyze
-```
-
-### Documenting Handlers
-
-```yaml
-# BAD - don't explain handlers, compiler injects them
-# When using workflow, load workflow.xml...
-```
-
-### Adding Rules in YAML
-
-```yaml
-# BAD - rules are auto-injected
-agent:
-  rules:
-    - Stay in character...
-```
-
-## Compilation Example
-
-**Your YAML:**
-
-```yaml
-agent:
-  metadata:
-    name: 'Rex'
-    title: 'Code Reviewer'
-    icon: '🔍'
-    type: simple
-
-  persona:
-    role: Code Review Expert
-    identity: Systematic reviewer...
-    communication_style: Direct and constructive
-    principles:
-      - Code should be readable
-
-  prompts:
-    - id: review
-      content: |
-        Analyze code for issues...
-
-  menu:
-    - trigger: review
-      action: '#review'
-      description: 'Review code'
-```
-
-**Compiled Output (.md):**
-
-```markdown
----
-name: 'rex'
-description: 'Code Reviewer'
----
-
-You must fully embody...
-
-\`\`\`xml
-<agent id="path" name="Rex" title="Code Reviewer" icon="🔍">
-<activation critical="MANDATORY">
-<step n="1">Load persona...</step>
-<step n="2">Load config...</step>
-<step n="3">Remember user...</step>
-<step n="4">Communicate in language...</step>
-<step n="5">Show greeting + menu...</step>
-<step n="6">STOP and WAIT...</step>
-<step n="7">Input resolution...</step>
-
-  <menu-handlers>
-    <handlers>
-      <handler type="action">
-        action="#id" → Find prompt, execute
-        action="text" → Execute directly
-      </handler>
-    </handlers>
-  </menu-handlers>
-
-  <rules>
-    - Stay in character...
-    - Number lists...
-    - Load files when executing...
-  </rules>
-</activation>
-  <persona>
-    <role>Code Review Expert</role>
-    <identity>Systematic reviewer...</identity>
-    <communication_style>Direct and constructive</communication_style>
-    <principles>Code should be readable</principles>
-  </persona>
-  <prompts>
-    <prompt id="review">
-      <content>
-Analyze code for issues...
-      </content>
-    </prompt>
-  </prompts>
-  <menu>
-    <item cmd="*help">Show numbered menu</item>
-    <item cmd="*review" action="#review">Review code</item>
-    <item cmd="*exit">Exit with confirmation</item>
-  </menu>
-</agent>
-\`\`\`
-```
-
-## Key Takeaways
-
-1. **Compiler handles boilerplate** - Focus on persona and logic
-2. **Critical_actions become activation steps** - Just list your agent-specific needs
-3. **Menu items are enhanced** - Help/exit added, triggers prefixed
-4. **Handlers auto-detected** - Only what you use is included
-5. **Rules standardized** - Consistent behavior across agents
-
-**Your job:** Define persona, prompts, menu actions
-**Compiler's job:** Activation, handlers, rules, help/exit, prefixes

src/modules/bmb/docs/agents/agent-menu-patterns.md

@@ -1,524 +0,0 @@
-# BMAD Agent Menu Patterns
-
-Design patterns for agent menus in YAML source files.
-
-## Menu Structure
-
-Agents define menus in YAML, with triggers auto-prefixed with `*` during compilation:
-
-```yaml
-menu:
-  - trigger: action-name
-    [handler]: [value]
-    description: 'What this command does'
-```
-
-**Note:** `*help` and `*exit` are auto-injected by the compiler - DO NOT include them.
-
-## Handler Types
-
-### 1. Action Handler (Prompts & Inline)
-
-For simple and expert agents with self-contained logic.
-
-**Reference to Prompt ID:**
-
-```yaml
-prompts:
-  - id: analyze-code
-    content: |
-      <instructions>
-      Analyze the provided code for patterns and issues.
-      </instructions>
-
-      <process>
-      1. Identify code structure
-      2. Check for anti-patterns
-      3. Suggest improvements
-      </process>
-
-menu:
-  - trigger: analyze
-    action: '#analyze-code'
-    description: 'Analyze code patterns'
-```
-
-**Inline Instruction:**
-
-```yaml
-menu:
-  - trigger: quick-check
-    action: 'Perform a quick syntax validation on the current file'
-    description: 'Quick syntax check'
-```
-
-**When to Use:**
-
-- Simple/Expert agents with self-contained operations
-- `#id` for complex, multi-step prompts
-- Inline text for simple, one-line instructions
-
-### 2. Workflow Handler
-
-For module agents orchestrating multi-step processes.
-
-```yaml
-menu:
-  - trigger: create-prd
-    workflow: '{project-root}/.bmad/bmm/workflows/prd/workflow.yaml'
-    description: 'Create Product Requirements Document'
-
-  - trigger: brainstorm
-    workflow: '{project-root}/.bmad/core/workflows/brainstorming/workflow.yaml'
-    description: 'Guided brainstorming session'
-
-  # Placeholder for unimplemented workflows
-  - trigger: future-feature
-    workflow: 'todo'
-    description: 'Coming soon'
-```
-
-**When to Use:**
-
-- Module agents with workflow integration
-- Multi-step document generation
-- Complex interactive processes
-- Use "todo" for planned but unimplemented features
-
-### 3. Exec Handler
-
-For executing tasks directly.
-
-```yaml
-menu:
-  - trigger: validate
-    exec: '{project-root}/.bmad/core/tasks/validate-workflow.xml'
-    description: 'Validate document structure'
-
-  - trigger: advanced-elicitation
-    exec: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
-    description: 'Advanced elicitation techniques'
-```
-
-**When to Use:**
-
-- Single-operation tasks
-- Core system operations
-- Utility functions
-
-### 4. Template Handler
-
-For document generation with templates.
-
-```yaml
-menu:
-  - trigger: create-brief
-    exec: '{project-root}/.bmad/core/tasks/create-doc.xml'
-    tmpl: '{project-root}/.bmad/bmm/templates/brief.md'
-    description: 'Create a Product Brief'
-```
-
-**When to Use:**
-
-- Template-based document creation
-- Combine `exec` with `tmpl` path
-- Structured output generation
-
-### 5. Data Handler
-
-Universal attribute for supplementary information.
-
-```yaml
-menu:
-  - trigger: team-standup
-    exec: '{project-root}/.bmad/bmm/tasks/standup.xml'
-    data: '{project-root}/.bmad/_cfg/agent-manifest.csv'
-    description: 'Run team standup'
-
-  - trigger: analyze-metrics
-    action: 'Analyze these metrics and identify trends'
-    data: '{project-root}/_data/metrics.json'
-    description: 'Analyze performance metrics'
-```
-
-**When to Use:**
-
-- Add to ANY handler type
-- Reference data files (CSV, JSON, YAML)
-- Provide context for operations
-
-## Platform-Specific Menus
-
-Control visibility based on deployment target:
-
-```yaml
-menu:
-  - trigger: git-flow
-    exec: '{project-root}/.bmad/bmm/tasks/git-flow.xml'
-    description: 'Git workflow operations'
-    ide-only: true # Only in IDE environments
-
-  - trigger: advanced-elicitation
-    exec: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
-    description: 'Advanced elicitation'
-    web-only: true # Only in web bundles
-```
-
-## Trigger Naming Conventions
-
-### Action-Based (Recommended)
-
-```yaml
-# Creation
-- trigger: create-prd
-- trigger: build-module
-- trigger: generate-report
-
-# Analysis
-- trigger: analyze-requirements
-- trigger: review-code
-- trigger: validate-architecture
-
-# Operations
-- trigger: update-status
-- trigger: sync-data
-- trigger: deploy-changes
-```
-
-### Domain-Based
-
-```yaml
-# Development
-- trigger: brainstorm
-- trigger: architect
-- trigger: refactor
-
-# Project Management
-- trigger: sprint-plan
-- trigger: retrospective
-- trigger: standup
-```
-
-### Bad Patterns
-
-```yaml
-# TOO VAGUE
-- trigger: do
-- trigger: run
-- trigger: process
-
-# TOO LONG
-- trigger: create-comprehensive-product-requirements-document
-
-# NO VERB
-- trigger: prd
-- trigger: config
-```
-
-## Menu Organization
-
-### Recommended Order
-
-```yaml
-menu:
-  # Note: *help auto-injected first by compiler
-
-  # 1. Primary workflows (main value)
-  - trigger: workflow-init
-    workflow: '...'
-    description: 'Start here - initialize workflow'
-
-  - trigger: create-prd
-    workflow: '...'
-    description: 'Create PRD'
-
-  # 2. Secondary operations
-  - trigger: validate
-    exec: '...'
-    description: 'Validate document'
-
-  # 3. Utilities
-  - trigger: party-mode
-    workflow: '...'
-    description: 'Multi-agent discussion'
-
-  # Note: *exit auto-injected last by compiler
-```
-
-### Grouping by Phase
-
-```yaml
-menu:
-  # Analysis Phase
-  - trigger: brainstorm
-    workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
-    description: 'Brainstorm ideas'
-
-  - trigger: research
-    workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/research/workflow.yaml'
-    description: 'Conduct research'
-
-  # Planning Phase
-  - trigger: prd
-    workflow: '{project-root}/.bmad/bmm/workflows/2-planning/prd/workflow.yaml'
-    description: 'Create PRD'
-
-  - trigger: architecture
-    workflow: '{project-root}/.bmad/bmm/workflows/2-planning/architecture/workflow.yaml'
-    description: 'Design architecture'
-```
-
-## Description Best Practices
-
-### Good Descriptions
-
-```yaml
-# Clear action + object
-- description: 'Create Product Requirements Document'
-
-# Specific outcome
-- description: 'Analyze security vulnerabilities'
-
-# User benefit
-- description: 'Optimize code for performance'
-
-# Context when needed
-- description: 'Start here - initialize workflow path'
-```
-
-### Poor Descriptions
-
-```yaml
-# Too vague
-- description: 'Process'
-
-# Technical jargon
-- description: 'Execute WF123'
-
-# Missing context
-- description: 'Run'
-
-# Redundant with trigger
-- description: 'Create PRD' # trigger: create-prd (too similar)
-```
-
-## Prompts Section (Simple/Expert Agents)
-
-### Prompt Structure
-
-```yaml
-prompts:
-  - id: unique-identifier
-    content: |
-      <instructions>
-      What this prompt accomplishes
-      </instructions>
-
-      <process>
-      1. First step
-      {{#if custom_option}}
-      2. Conditional step
-      {{/if}}
-      3. Final step
-      </process>
-
-      <output_format>
-      Expected structure of results
-      </output_format>
-```
-
-### Semantic XML Tags in Prompts
-
-Use XML tags to structure prompt content:
-
-- `<instructions>` - What to do
-- `<process>` - Step-by-step approach
-- `<output_format>` - Expected results
-- `<examples>` - Sample outputs
-- `<constraints>` - Limitations
-- `<context>` - Background information
-
-### Handlebars in Prompts
-
-Customize based on install_config:
-
-```yaml
-prompts:
-  - id: analyze
-    content: |
-      {{#if detailed_mode}}
-      Perform comprehensive analysis with full explanations.
-      {{/if}}
-      {{#unless detailed_mode}}
-      Quick analysis focusing on key points.
-      {{/unless}}
-
-      Address {{user_name}} in {{communication_style}} tone.
-```
-
-## Path Variables
-
-### Always Use Variables
-
-```yaml
-# GOOD - Portable paths
-workflow: "{project-root}/.bmad/bmm/workflows/prd/workflow.yaml"
-exec: "{project-root}/.bmad/core/tasks/validate.xml"
-data: "{project-root}/_data/metrics.csv"
-
-# BAD - Hardcoded paths
-workflow: "/Users/john/project/.bmad/bmm/workflows/prd/workflow.yaml"
-exec: "../../../core/tasks/validate.xml"
-```
-
-### Available Variables
-
-- `{project-root}` - Project root directory
-- `.bmad` - BMAD installation folder
-- `{agent_sidecar_folder}` - Agent installation directory (Expert agents)
-- `{output_folder}` - Document output location
-- `{user_name}` - User's name from config
-- `{communication_language}` - Language preference
-
-## Complete Examples
-
-### Simple Agent Menu
-
-```yaml
-prompts:
-  - id: format-code
-    content: |
-      <instructions>
-      Format the provided code according to style guidelines.
-      </instructions>
-
-      Apply:
-      - Consistent indentation
-      - Proper spacing
-      - Clear naming conventions
-
-menu:
-  - trigger: format
-    action: '#format-code'
-    description: 'Format code to style guidelines'
-
-  - trigger: lint
-    action: 'Check code for common issues and anti-patterns'
-    description: 'Lint code for issues'
-
-  - trigger: suggest
-    action: 'Suggest improvements for code readability'
-    description: 'Suggest improvements'
-```
-
-### Expert Agent Menu
-
-```yaml
-critical_actions:
-  - 'Load ./memories.md'
-  - 'Follow ./instructions.md'
-  - 'ONLY access ./'
-
-prompts:
-  - id: reflect
-    content: |
-      Guide {{user_name}} through reflection on recent entries.
-      Reference patterns from memories.md naturally.
-
-menu:
-  - trigger: write
-    action: '#reflect'
-    description: 'Write journal entry'
-
-  - trigger: save
-    action: 'Update ./memories.md with session insights'
-    description: "Save today's session"
-
-  - trigger: patterns
-    action: 'Analyze recent entries for recurring themes'
-    description: 'View patterns'
-```
-
-### Module Agent Menu
-
-```yaml
-menu:
-  - trigger: workflow-init
-    workflow: '{project-root}/.bmad/bmm/workflows/workflow-status/init/workflow.yaml'
-    description: 'Initialize workflow path (START HERE)'
-
-  - trigger: brainstorm
-    workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
-    description: 'Guided brainstorming'
-
-  - trigger: prd
-    workflow: '{project-root}/.bmad/bmm/workflows/2-planning/prd/workflow.yaml'
-    description: 'Create PRD'
-
-  - trigger: architecture
-    workflow: '{project-root}/.bmad/bmm/workflows/2-planning/architecture/workflow.yaml'
-    description: 'Design architecture'
-
-  - trigger: party-mode
-    workflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.yaml'
-    description: 'Multi-agent discussion'
-```
-
-## Validation Checklist
-
-- [ ] No duplicate triggers
-- [ ] Triggers don't start with `*` (auto-added)
-- [ ] Every item has a description
-- [ ] Paths use variables, not hardcoded
-- [ ] `#id` references exist in prompts section
-- [ ] Workflow paths resolve or are "todo"
-- [ ] No `*help` or `*exit` (auto-injected)
-- [ ] Descriptions are clear and action-oriented
-- [ ] Platform-specific flags used correctly (ide-only, web-only)
-
-## Common Mistakes
-
-### Duplicate Triggers
-
-```yaml
-# BAD - compiler will fail
-- trigger: analyze
-  action: '#first'
-  description: 'First analysis'
-
-- trigger: analyze
-  action: '#second'
-  description: 'Second analysis'
-```
-
-### Including Auto-Injected Items
-
-```yaml
-# BAD - these are auto-injected
-menu:
-  - trigger: help
-    description: 'Show help'
-
-  - trigger: exit
-    description: 'Exit agent'
-```
-
-### Missing Prompt Reference
-
-```yaml
-# BAD - prompt id doesn't exist
-menu:
-  - trigger: analyze
-    action: '#nonexistent-prompt'
-    description: 'Analysis'
-```
-
-### Hardcoded Paths
-
-```yaml
-# BAD - not portable
-menu:
-  - trigger: run
-    workflow: '/absolute/path/to/workflow.yaml'
-    description: 'Run workflow'
-```

src/modules/bmb/docs/agents/expert-agent-architecture.md

@@ -1,364 +0,0 @@
-# Expert Agent Architecture
-
-Domain-specific agents with persistent memory, sidecar files, and restricted access patterns.
-
-## When to Use
-
-- Personal assistants (journal keeper, diary companion)
-- Specialized domain experts (legal advisor, medical reference)
-- Agents that need to remember past interactions
-- Agents with restricted file system access (privacy/security)
-- Long-term relationship agents that learn about users
-
-## File Structure
-
-```
-{agent-name}/
-├── {agent-name}.agent.yaml    # Main agent definition
-└── {agent-name}-sidecar/      # Supporting files
-    ├── instructions.md        # Private directives
-    ├── memories.md            # Persistent memory
-    ├── knowledge/             # Domain-specific resources
-    │   └── README.md
-    └── [custom files]         # Agent-specific resources
-```
-
-## YAML Structure
-
-```yaml
-agent:
-  metadata:
-    name: 'Persona Name'
-    title: 'Agent Title'
-    icon: 'emoji'
-    type: 'expert'
-
-  persona:
-    role: 'Domain Expert with specialized capability'
-
-    identity: |
-      Background and expertise in first-person voice.
-      {{#if user_preference}}
-      Customization based on install_config.
-      {{/if}}
-
-    communication_style: |
-      {{#if tone_style == "gentle"}}
-      Gentle and supportive communication...
-      {{/if}}
-      {{#if tone_style == "direct"}}
-      Direct and efficient communication...
-      {{/if}}
-      I reference past conversations naturally.
-
-    principles:
-      - Core belief about the domain
-      - How I handle user information
-      - My approach to memory and learning
-
-  critical_actions:
-    - 'Load COMPLETE file ./{agent-name}-sidecar/memories.md and remember all past insights'
-    - 'Load COMPLETE file ./{agent-name}-sidecar/instructions.md and follow ALL protocols'
-    - 'ONLY read/write files in ./{agent-name}-sidecar/ - this is our private space'
-    - 'Address user as {{greeting_name}}'
-    - 'Track patterns, themes, and important moments'
-    - 'Reference past interactions naturally to show continuity'
-
-  prompts:
-    - id: main-function
-      content: |
-        <instructions>
-        Guide user through the primary function.
-        {{#if tone_style == "gentle"}}
-        Use gentle, supportive approach.
-        {{/if}}
-        </instructions>
-
-        <process>
-        1. Understand context
-        2. Provide guidance
-        3. Record insights
-        </process>
-
-    - id: memory-recall
-      content: |
-        <instructions>
-        Access and share relevant memories.
-        </instructions>
-
-        Reference stored information naturally.
-
-  menu:
-    - trigger: action1
-      action: '#main-function'
-      description: 'Primary agent function'
-
-    - trigger: remember
-      action: 'Update ./{agent-name}-sidecar/memories.md with session insights'
-      description: 'Save what we discussed today'
-
-    - trigger: patterns
-      action: '#memory-recall'
-      description: 'Recall patterns from past interactions'
-
-    - trigger: insight
-      action: 'Document breakthrough in ./{agent-name}-sidecar/breakthroughs.md'
-      description: 'Record a significant insight'
-
-  install_config:
-    compile_time_only: true
-    description: 'Personalize your expert agent'
-    questions:
-      - var: greeting_name
-        prompt: 'What should the agent call you?'
-        type: text
-        default: 'friend'
-
-      - var: tone_style
-        prompt: 'Preferred communication tone?'
-        type: choice
-        options:
-          - label: 'Gentle - Supportive and nurturing'
-            value: 'gentle'
-          - label: 'Direct - Clear and efficient'
-            value: 'direct'
-        default: 'gentle'
-
-      - var: user_preference
-        prompt: 'Enable personalized features?'
-        type: boolean
-        default: true
-```
-
-## Key Components
-
-### Sidecar Files (CRITICAL)
-
-Expert agents use companion files for persistence and domain knowledge:
-
-**memories.md** - Persistent user context
-
-```markdown
-# Agent Memory Bank
-
-## User Preferences
-
-<!-- Learned from interactions -->
-
-## Session History
-
-<!-- Important moments and insights -->
-
-## Personal Notes
-
-<!-- Agent observations -->
-```
-
-**instructions.md** - Private directives
-
-```markdown
-# Agent Private Instructions
-
-## Core Directives
-
-- Maintain character consistency
-- Domain boundaries: {specific domain}
-- Access restrictions: Only sidecar folder
-
-## Special Rules
-
-<!-- Agent-specific protocols -->
-```
-
-**knowledge/** - Domain resources
-
-```markdown
-# Agent Knowledge Base
-
-Add domain-specific documentation here.
-```
-
-### Critical Actions
-
-**MANDATORY for expert agents** - These load sidecar files at activation:
-
-```yaml
-critical_actions:
-  - 'Load COMPLETE file ./{sidecar}/memories.md and remember all past insights'
-  - 'Load COMPLETE file ./{sidecar}/instructions.md and follow ALL protocols'
-  - 'ONLY read/write files in ./{sidecar}/ - this is our private space'
-```
-
-**Key patterns:**
-
-- **COMPLETE file loading** - Forces full file read, not partial
-- **Domain restrictions** - Limits file access for privacy/security
-- **Memory integration** - Past context becomes part of current session
-- **Protocol adherence** - Ensures consistent behavior
-
-### {agent_sidecar_folder} Variable
-
-Special variable resolved during installation:
-
-- Points to the agent's installation directory
-- Used to reference sidecar files
-- Example: `.bmad/custom/agents/journal-keeper/`
-
-## What Gets Injected at Compile Time
-
-Same as simple agents, PLUS:
-
-1. **Critical actions become numbered activation steps**
-
-   ```xml
-   <step n="4">Load COMPLETE file ./memories.md...</step>
-   <step n="5">Load COMPLETE file ./instructions.md...</step>
-   <step n="6">ONLY read/write files in ./...</step>
-   ```
-
-2. **Sidecar files copied during installation**
-   - Entire sidecar folder structure preserved
-   - Relative paths maintained
-   - Files ready for agent use
-
-## Reference Example
-
-See: `bmb/reference/agents/expert-examples/journal-keeper/`
-
-Features demonstrated:
-
-- Complete sidecar structure (memories, instructions, breakthroughs)
-- Critical actions for loading persistent context
-- Domain restrictions for privacy
-- Pattern recognition and memory recall
-- Handlebars-based personalization
-- Menu actions that update sidecar files
-
-## Installation
-
-```bash
-# Copy entire folder to your project
-cp -r /path/to/journal-keeper/ .bmad/custom/agents/
-
-# Install with personalization
-bmad agent-install
-```
-
-The installer:
-
-1. Detects expert agent (folder with .agent.yaml)
-2. Prompts for personalization
-3. Compiles agent YAML to XML-in-markdown
-4. **Copies sidecar files to installation target**
-5. Creates IDE slash commands
-6. Saves source for reinstallation
-
-## Memory Patterns
-
-### Accumulative Memory
-
-```yaml
-menu:
-  - trigger: save
-    action: "Update ./sidecar/memories.md with today's session insights"
-    description: 'Save session to memory'
-```
-
-### Reference Memory
-
-```yaml
-prompts:
-  - id: recall
-    content: |
-      <instructions>
-      Reference memories.md naturally:
-      "Last week you mentioned..." or "I notice a pattern..."
-      </instructions>
-```
-
-### Structured Insights
-
-```yaml
-menu:
-  - trigger: insight
-    action: 'Document in ./sidecar/breakthroughs.md with date, context, significance'
-    description: 'Record meaningful insight'
-```
-
-## Domain Restriction Patterns
-
-### Single Folder Access
-
-```yaml
-critical_actions:
-  - 'ONLY read/write files in ./sidecar/ - NO OTHER FOLDERS'
-```
-
-### User Space Access
-
-```yaml
-critical_actions:
-  - 'ONLY access files in {user-folder}/journals/ - private space'
-```
-
-### Read-Only Access
-
-```yaml
-critical_actions:
-  - 'Load knowledge from ./knowledge/ but NEVER modify'
-  - 'Write ONLY to ./sessions/'
-```
-
-## Best Practices
-
-1. **Load sidecar files in critical_actions** - Must be explicit and MANDATORY
-2. **Enforce domain restrictions** - Clear boundaries prevent scope creep
-3. **Use {agent_sidecar_folder} paths** - Portable across installations
-4. **Design for memory growth** - Structure sidecar files for accumulation
-5. **Reference past naturally** - Don't dump memory, weave it into conversation
-6. **Separate concerns** - Memories, instructions, knowledge in distinct files
-7. **Include privacy features** - Users trust expert agents with personal data
-
-## Common Patterns
-
-### Session Continuity
-
-```yaml
-communication_style: |
-  I reference past conversations naturally:
-  "Last time we discussed..." or "I've noticed over the weeks..."
-```
-
-### Pattern Recognition
-
-```yaml
-critical_actions:
-  - 'Track mood patterns, recurring themes, and breakthrough moments'
-  - 'Cross-reference current session with historical patterns'
-```
-
-### Adaptive Responses
-
-```yaml
-identity: |
-  I learn your preferences and adapt my approach over time.
-  {{#if track_preferences}}
-  I maintain notes about what works best for you.
-  {{/if}}
-```
-
-## Validation Checklist
-
-- [ ] Valid YAML syntax
-- [ ] Metadata includes `type: "expert"`
-- [ ] critical_actions loads sidecar files explicitly
-- [ ] critical_actions enforces domain restrictions
-- [ ] Sidecar folder structure created and populated
-- [ ] memories.md has clear section structure
-- [ ] instructions.md contains core directives
-- [ ] Menu actions reference {agent_sidecar_folder} correctly
-- [ ] File paths use {agent_sidecar_folder} variable
-- [ ] Install config personalizes sidecar references
-- [ ] Agent folder named consistently: `{agent-name}/`
-- [ ] YAML file named: `{agent-name}.agent.yaml`
-- [ ] Sidecar folder named: `{agent-name}-sidecar/`

src/modules/bmb/docs/agents/index.md

@@ -1,55 +0,0 @@
-# BMB Module Documentation
-
-Reference documentation for building BMAD agents and workflows.
-
-## Agent Architecture
-
-Comprehensive guides for each agent type (choose based on use case):
-
-- [Understanding Agent Types](./understanding-agent-types.md) - **START HERE** - Architecture vs capability, "The Same Agent, Three Ways"
-- [Simple Agent Architecture](./simple-agent-architecture.md) - Self-contained, optimized, personality-driven
-- [Expert Agent Architecture](./expert-agent-architecture.md) - Memory, sidecar files, domain restrictions
-- [Module Agent Architecture](./module-agent-architecture.md) - Workflow integration, professional tools
-
-## Agent Design Patterns
-
-- [Agent Menu Patterns](./agent-menu-patterns.md) - Menu handlers, triggers, prompts, organization
-- [Agent Compilation](./agent-compilation.md) - What compiler auto-injects (AVOID DUPLICATION)
-
-## Reference Examples
-
-Production-ready examples in `/bmb/reference/agents/`:
-
-**Simple Agents** (`simple-examples/`)
-
-- `commit-poet.agent.yaml` - Commit message artisan with style customization
-
-**Expert Agents** (`expert-examples/`)
-
-- `journal-keeper/` - Personal journal companion with memory and pattern recognition
-
-**Module Agents** (`module-examples/`)
-
-- `security-engineer.agent.yaml` - BMM security specialist with threat modeling
-- `trend-analyst.agent.yaml` - CIS trend intelligence expert
-
-## Installation Guide
-
-For installing standalone simple and expert agents, see:
-
-- [Custom Agent Installation](/docs/custom-content-installation.md)
-
-## Key Concepts
-
-### YAML to XML Compilation
-
-Agents are authored in YAML with Handlebars templating. The compiler auto-injects:
-
-1. **Frontmatter** - Name and description from metadata
-2. **Activation Block** - Steps, menu handlers, rules (YOU don't write this)
-3. **Menu Enhancement** - `*help` and `*exit` commands added automatically
-4. **Trigger Prefixing** - Your triggers auto-prefixed with `*`
-
-**Critical:** See [Agent Compilation](./agent-compilation.md) to avoid duplicating auto-injected content.
-
-Source: `tools/cli/lib/agent/compiler.js`

src/modules/bmb/docs/agents/module-agent-architecture.md

@@ -1,366 +0,0 @@
-# Module Agent Architecture
-
-Full integration agents with workflow orchestration, module-specific paths, and professional tooling.
-
-## When to Use
-
-- Professional development workflows (business analysis, architecture design)
-- Team-oriented tools (project management, sprint planning)
-- Agents that orchestrate multiple workflows
-- Module-specific functionality (BMM, BMB, CIS, custom modules)
-- Agents with complex multi-step operations
-
-## File Location
-
-```
-src/modules/{module-code}/agents/{agent-name}.agent.yaml
-```
-
-Compiles to:
-
-```
-.bmad/{module-code}/agents/{agent-name}.md
-```
-
-## YAML Structure
-
-```yaml
-agent:
-  metadata:
-    id: '.bmad/{module-code}/agents/{agent-name}.md'
-    name: 'Persona Name'
-    title: 'Professional Title'
-    icon: 'emoji'
-    module: '{module-code}'
-
-  persona:
-    role: 'Primary expertise and function'
-    identity: 'Background, experience, specializations'
-    communication_style: 'Interaction approach, tone, methodology'
-    principles: 'Core beliefs and methodology'
-
-  menu:
-    - trigger: workflow-action
-      workflow: '{project-root}/.bmad/{module-code}/workflows/{workflow-name}/workflow.yaml'
-      description: 'Execute module workflow'
-
-    - trigger: another-workflow
-      workflow: '{project-root}/.bmad/core/workflows/{workflow-name}/workflow.yaml'
-      description: 'Execute core workflow'
-
-    - trigger: task-action
-      exec: '{project-root}/.bmad/{module-code}/tasks/{task-name}.xml'
-      description: 'Execute module task'
-
-    - trigger: cross-module
-      workflow: '{project-root}/.bmad/other-module/workflows/{workflow-name}/workflow.yaml'
-      description: 'Execute workflow from another module'
-
-    - trigger: with-template
-      exec: '{project-root}/.bmad/core/tasks/create-doc.xml'
-      tmpl: '{project-root}/.bmad/{module-code}/templates/{template-name}.md'
-      description: 'Create document from template'
-
-    - trigger: with-data
-      exec: '{project-root}/.bmad/{module-code}/tasks/{task-name}.xml'
-      data: '{project-root}/.bmad/_cfg/agent-manifest.csv'
-      description: 'Execute task with data file'
-```
-
-## Key Components
-
-### Metadata
-
-- **id**: Path with `.bmad` variable (resolved at install time)
-- **name**: Agent persona name
-- **title**: Professional role
-- **icon**: Single emoji
-- **module**: Module code (bmm, bmb, cis, custom)
-
-### Persona (Professional Voice)
-
-Module agents typically use **professional** communication styles:
-
-```yaml
-persona:
-  role: Strategic Business Analyst + Requirements Expert
-
-  identity: Senior analyst with deep expertise in market research, competitive analysis, and requirements elicitation. Specializes in translating vague needs into actionable specs.
-
-  communication_style: Systematic and probing. Connects dots others miss. Structures findings hierarchically. Uses precise unambiguous language. Ensures all stakeholder voices heard.
-
-  principles: Every business challenge has root causes waiting to be discovered. Ground findings in verifiable evidence. Articulate requirements with absolute precision.
-```
-
-**Note:** Module agents usually don't use Handlebars templating since they're not user-customized - they're professional tools with fixed personalities.
-
-### Menu Handlers
-
-#### Workflow Handler (Most Common)
-
-```yaml
-menu:
-  - trigger: create-prd
-    workflow: '{project-root}/.bmad/bmm/workflows/prd/workflow.yaml'
-    description: 'Create Product Requirements Document'
-```
-
-Invokes BMAD workflow engine to execute multi-step processes.
-
-#### Task/Exec Handler
-
-```yaml
-menu:
-  - trigger: validate
-    exec: '{project-root}/.bmad/core/tasks/validate-workflow.xml'
-    description: 'Validate document structure'
-```
-
-Executes single-operation tasks.
-
-#### Template Handler
-
-```yaml
-menu:
-  - trigger: create-brief
-    exec: '{project-root}/.bmad/core/tasks/create-doc.xml'
-    tmpl: '{project-root}/.bmad/bmm/templates/brief.md'
-    description: 'Create a Product Brief from template'
-```
-
-Combines task execution with template file.
-
-#### Data Handler
-
-```yaml
-menu:
-  - trigger: team-standup
-    exec: '{project-root}/.bmad/bmm/tasks/standup.xml'
-    data: '{project-root}/.bmad/_cfg/agent-manifest.csv'
-    description: 'Run team standup with agent roster'
-```
-
-Provides data file to task.
-
-#### Placeholder Handler
-
-```yaml
-menu:
-  - trigger: future-feature
-    workflow: 'todo'
-    description: 'Feature planned but not yet implemented'
-```
-
-Marks unimplemented features - compiler handles gracefully.
-
-### Platform-Specific Menu Items
-
-Control visibility based on platform:
-
-```yaml
-menu:
-  - trigger: advanced-elicitation
-    exec: '{project-root}/.bmad/core/tasks/advanced-elicitation.xml'
-    description: 'Advanced elicitation techniques'
-    web-only: true # Only shows in web bundle
-
-  - trigger: git-operations
-    exec: '{project-root}/.bmad/bmm/tasks/git-flow.xml'
-    description: 'Git workflow operations'
-    ide-only: true # Only shows in IDE environments
-```
-
-## Variable System
-
-### Core Variables
-
-- `{project-root}` - Root directory of installed project
-- `.bmad` - BMAD installation folder (usually `.bmad`)
-- `{user_name}` - User's name from module config
-- `{communication_language}` - Language preference
-- `{output_folder}` - Document output directory
-
-### Path Construction
-
-**Always use variables, never hardcoded paths:**
-
-```yaml
-# GOOD
-workflow: "{project-root}/.bmad/bmm/workflows/prd/workflow.yaml"
-
-# BAD
-workflow: "/Users/john/project/.bmad/bmm/workflows/prd/workflow.yaml"
-
-# BAD
-workflow: "../../../bmm/workflows/prd/workflow.yaml"
-```
-
-## What Gets Injected at Compile Time
-
-Module agents use the same injection process as simple agents:
-
-1. **Frontmatter** with name and description
-2. **Activation block** with standard steps
-3. **Menu handlers** based on usage (workflow, exec, tmpl, data)
-4. **Rules section** for consistent behavior
-5. **Auto-injected** \*help and \*exit commands
-
-**Key difference:** Module agents load **module-specific config** instead of core config:
-
-```xml
-<step n="2">Load and read {project-root}/.bmad/{module}/config.yaml...</step>
-```
-
-## Reference Examples
-
-See: `src/modules/bmm/agents/`
-
-**analyst.agent.yaml** - Business Analyst
-
-- Workflow orchestration for analysis phase
-- Multiple workflow integrations
-- Cross-module workflow access (core/workflows/party-mode)
-
-**architect.agent.yaml** - System Architect
-
-- Technical workflow management
-- Architecture decision workflows
-
-**pm.agent.yaml** - Product Manager
-
-- Planning and coordination workflows
-- Sprint management integration
-
-## Module Configuration
-
-Each module has `config.yaml` providing:
-
-```yaml
-# src/modules/{module}/config.yaml
-user_name: 'User Name'
-communication_language: 'English'
-output_folder: '{project-root}/docs'
-custom_settings: 'module-specific values'
-```
-
-Agents load this at activation for consistent behavior.
-
-## Workflow Integration Patterns
-
-### Sequential Workflow Execution
-
-```yaml
-menu:
-  - trigger: init
-    workflow: '{project-root}/.bmad/bmm/workflows/workflow-init/workflow.yaml'
-    description: 'Initialize workflow path (START HERE)'
-
-  - trigger: status
-    workflow: '{project-root}/.bmad/bmm/workflows/workflow-status/workflow.yaml'
-    description: 'Check current workflow status'
-
-  - trigger: next-step
-    workflow: '{project-root}/.bmad/bmm/workflows/next-step/workflow.yaml'
-    description: 'Execute next workflow in sequence'
-```
-
-### Phase-Based Organization
-
-```yaml
-menu:
-  # Phase 1: Analysis
-  - trigger: brainstorm
-    workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/brainstorm/workflow.yaml'
-    description: 'Guided brainstorming session'
-
-  - trigger: research
-    workflow: '{project-root}/.bmad/bmm/workflows/1-analysis/research/workflow.yaml'
-    description: 'Market and technical research'
-
-  # Phase 2: Planning
-  - trigger: prd
-    workflow: '{project-root}/.bmad/bmm/workflows/2-planning/prd/workflow.yaml'
-    description: 'Create PRD'
-
-  - trigger: architecture
-    workflow: '{project-root}/.bmad/bmm/workflows/2-planning/architecture/workflow.yaml'
-    description: 'Design architecture'
-```
-
-### Cross-Module Access
-
-```yaml
-menu:
-  - trigger: party-mode
-    workflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.yaml'
-    description: 'Bring all agents together'
-
-  - trigger: brainstorm
-    workflow: '{project-root}/.bmad/cis/workflows/brainstorming/workflow.yaml'
-    description: 'Use CIS brainstorming techniques'
-```
-
-## Best Practices
-
-1. **Organize workflows by phase** - Clear progression for users
-2. **Include workflow-status** - Help users track progress
-3. **Reference module config** - Consistent behavior
-4. **No Handlebars templating** - Module agents are fixed personalities
-5. **Professional personas** - Match module purpose
-6. **Clear trigger names** - Self-documenting commands
-7. **Group related workflows** - Logical menu organization
-
-## Common Patterns
-
-### Entry Point Agent
-
-```yaml
-menu:
-  - trigger: start
-    workflow: '{project-root}/.bmad/{module}/workflows/init/workflow.yaml'
-    description: 'Start new project (BEGIN HERE)'
-```
-
-### Status Tracking
-
-```yaml
-menu:
-  - trigger: status
-    workflow: '{project-root}/.bmad/{module}/workflows/status/workflow.yaml'
-    description: 'Check workflow progress'
-```
-
-### Team Coordination
-
-```yaml
-menu:
-  - trigger: party
-    workflow: '{project-root}/.bmad/core/workflows/party-mode/workflow.yaml'
-    description: 'Multi-agent discussion'
-```
-
-## Module Agent vs Simple/Expert
-
-| Aspect        | Module Agent                | Simple/Expert Agent             |
-| ------------- | --------------------------- | ------------------------------- |
-| Location      | `.bmad/{module}/agents/`    | `.bmad/custom/agents/`          |
-| Persona       | Fixed, professional         | Customizable via install_config |
-| Handlebars    | No templating               | Yes, extensive                  |
-| Menu actions  | Workflows, tasks, templates | Prompts, inline actions         |
-| Configuration | Module config.yaml          | Core config or none             |
-| Purpose       | Professional tooling        | Personal utilities              |
-
-## Validation Checklist
-
-- [ ] Valid YAML syntax
-- [ ] Metadata includes `module: "{module-code}"`
-- [ ] id uses `.bmad/{module}/agents/{name}.md`
-- [ ] All workflow paths use `{project-root}/.bmad/` prefix
-- [ ] No hardcoded paths
-- [ ] No duplicate triggers
-- [ ] Each menu item has description
-- [ ] Triggers don't start with `*` (auto-added)
-- [ ] Professional persona appropriate for module
-- [ ] Workflow paths resolve to actual workflows (or "todo")
-- [ ] File named `{agent-name}.agent.yaml`
-- [ ] Located in `src/modules/{module}/agents/`