docs: playwright untils note in test-architecture.md

.github/ISSUE_TEMPLATE/idea_submission.md

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

.github/scripts/discord-helpers.sh

@@ -1,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/discord.yaml

@@ -1,286 +1,16 @@
 name: Discord Notification
 
-on:
-  pull_request:
-    types: [opened, closed, reopened, ready_for_review]
-  release:
-    types: [published]
-  create:
-  delete:
-  issue_comment:
-    types: [created]
-  pull_request_review:
-    types: [submitted]
-  pull_request_review_comment:
-    types: [created]
-  issues:
-    types: [opened, closed, reopened]
-
-env:
-  MAX_TITLE: 100
-  MAX_BODY: 250
+"on": [pull_request, release, create, delete, issue_comment, pull_request_review, pull_request_review_comment]
 
 jobs:
-  pull_request:
-    if: github.event_name == 'pull_request'
+  notify:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - name: Notify Discord
+        uses: sarisia/actions-status-discord@v1
+        if: always()
         with:
-          ref: ${{ github.event.repository.default_branch }}
-          sparse-checkout: .github/scripts
-          sparse-checkout-cone-mode: false
-      - name: Notify Discord
-        env:
-          WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}
-          ACTION: ${{ github.event.action }}
-          MERGED: ${{ github.event.pull_request.merged }}
-          PR_NUM: ${{ github.event.pull_request.number }}
-          PR_URL: ${{ github.event.pull_request.html_url }}
-          PR_TITLE: ${{ github.event.pull_request.title }}
-          PR_USER: ${{ github.event.pull_request.user.login }}
-          PR_BODY: ${{ github.event.pull_request.body }}
-        run: |
-          set -o pipefail
-          source .github/scripts/discord-helpers.sh
-          [ -z "$WEBHOOK" ] && exit 0
-
-          if [ "$ACTION" = "opened" ]; then ICON="🔀"; LABEL="New PR"
-          elif [ "$ACTION" = "closed" ] && [ "$MERGED" = "true" ]; then ICON="🎉"; LABEL="Merged"
-          elif [ "$ACTION" = "closed" ]; then ICON="❌"; LABEL="Closed"
-          elif [ "$ACTION" = "reopened" ]; then ICON="🔄"; LABEL="Reopened"
-          else ICON="📋"; LABEL="Ready"; fi
-
-          TITLE=$(printf '%s' "$PR_TITLE" | trunc $MAX_TITLE | esc)
-          [ ${#PR_TITLE} -gt $MAX_TITLE ] && TITLE="${TITLE}..."
-          BODY=$(printf '%s' "$PR_BODY" | trunc $MAX_BODY | 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 @-
+          webhook: ${{ secrets.DISCORD_WEBHOOK }}
+          status: ${{ job.status }}
+          title: "Triggered by ${{ github.event_name }}"
+          color: 0x5865F2

.github/workflows/quality.yaml

@@ -3,7 +3,6 @@ name: Quality & Validation
 # Runs comprehensive quality checks on all PRs:
 # - Prettier (formatting)
 # - ESLint (linting)
-# - markdownlint (markdown quality)
 # - Schema validation (YAML structure)
 # - Agent schema tests (fixture-based validation)
 # - Installation component tests (compilation)
@@ -51,24 +50,6 @@ jobs:
       - name: ESLint
         run: npm run lint
 
-  markdownlint:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Setup Node
-        uses: actions/setup-node@v4
-        with:
-          node-version-file: ".nvmrc"
-          cache: "npm"
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: markdownlint
-        run: npm run lint:md
-
   validate:
     runs-on: ubuntu-latest
     steps:

.gitignore

@@ -62,16 +62,9 @@ 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/

.markdownlint-cli2.yaml

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

.prettierignore

@@ -1,9 +1,6 @@
 # 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*/

CHANGELOG.md

@@ -1,259 +1,16 @@
 # Changelog
 
-## [6.0.0-alpha.14]
+## [Unreleased]
 
-**Release: December 7, 2025**
+### Added
 
-### 🔧 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
-
-**Granular Step-File Workflow System (NEW in alpha.13):**
-
-- **Multi-Menu Support**: Workflows now support granular step-file architecture with dynamic menu generation
-- **Sharded Workflows**: Complete conversion of Phase 1 and 2 workflows to stepwise sharded architecture
-- **Improved Performance**: Reduced file loading times and eliminated time-based estimates throughout
-- **Workflow Builder**: New dedicated workflow builder for creating stepwise workflows
-- **PRD Workflow**: First completely reworked sharded workflow resolving Sonnet compatibility issues
-
-**Core Workflow Transformations:**
-
-- Phase 1 and 2 workflows completely converted to sharded step-flow architecture
-- UX Design workflow converted to sharded step workflow
-- Brainstorming, Research, and Party Mode updated to use sharded step-flow workflows
-- Architecture workflows enhanced with step sharding and performance improvements
-
-### 🎯 Code Review & Development Enhancement
-
-**Advanced Code Review System:**
-
-- **Adversarial Code Review**: Quick-dev workflow now recommends adversarial review approach for higher quality
-- **Multi-LLM Strategy**: Dev-story workflow recommends different LLM models for code review tasks
-- **Agent Compiler Optimization**: Complete handler cleanup and performance improvements
-
-### 🤖 Agent System Revolution
-
-**Universal Custom Agent Support:**
-
-- **Complete IDE Coverage**: Custom agent support extended to ALL remaining IDEs
-- **Antigravity IDE Integration**: Added custom agent support with proper gitignore configuration
-- **Multiple Source Locations**: Compile agents now checks multiple source locations for better discovery
-- **Persona Name Display**: Fixed proper persona names display in custom agent manifests
-- **New IDE Support**: Added support for Rovo Dev IDE
-
-**Agent Creation & Management:**
-
-- **Improved Creation Workflow**: Enhanced agent creation workflow with better documentation
-- **Parameter Clarity**: Renamed agent-install parameters for better understanding
-- **Menu Organization**: BMad Agents menu items logically ordered with optional/recommended/required tags
-- **GitHub Migration**: GitHub integration now uses agents folder instead of chatmodes
-
-### 🔧 Phase 4 & Sprint Evolution
-
-**Complete Phase 4 Transformation:**
-
-- **Simplified Architecture**: Phase 4 workflows completely transformed - simpler, faster, better results
-- **Sprint Planning Integration**: Unified sprint planning with placeholders for Jira, Linear, and Trello integration
-- **Status Management**: Better status loading and updating for Phase 4 artifacts
-- **Workflow Reduction**: Phase 4 streamlined to single sprint planning item with clear validation
-- **Dynamic Workflows**: All Level 1-3 workflows now dynamically suggest next steps based on context
-
-### 🧪 Testing Infrastructure Expansion
-
-**Playwright Utils Integration:**
-
-- Test Architect now supports `@seontechnologies/playwright-utils` integration
-- Installation prompt with `use_playwright_utils` configuration flag
-- 11 comprehensive knowledge fragments covering ALL utilities
-- Adaptive workflow recommendations across 6 testing workflows
-- Production-ready utilities from SEON Technologies integrated with TEA patterns
-
-**Testing Environment:**
-
-- **Web Bundle Support**: Enabled web bundles for test and development environments
-- **Test Architecture**: Enhanced test design for architecture level (Phase 3) testing
-
-### 📦 Installation & Configuration
-
-**Installer Improvements:**
-
-- **Cleanup Options**: Installer now allows cleanup of unneeded files during upgrades
-- **Username Default**: Installer now defaults to system username for better UX
-- **IDE Selection**: Added empty IDE selection warning and promoted Antigravity to recommended
-- **NPM Vulnerabilities**: Resolved all npm vulnerabilities for enhanced security
-- **Documentation Installation**: Made documentation installation optional to reduce footprint
-
-**Text-to-Speech from AgentVibes optional Integration:**
-
-- **TTS_INJECTION System**: Complete text-to-speech integration via injection system
-- **Agent Vibes**: Enhanced with TTS capabilities for voice feedback
-
-### 🛠️ Tool & IDE Updates
-
-**IDE Tool Enhancements:**
-
-- **GitHub Copilot**: Fixed tool names consistency across workflows
-- **KiloCode Integration**: Gave kilocode tool proper access to bmad modes
-- **Code Quality**: Added radix parameter to parseInt() calls for better reliability
-- **Agent Menu Optimization**: Improved agent performance in Claude Code slash commands
-
-### 📚 Documentation & Standards
-
-**Documentation Cleanup:**
-
-- **Installation Guide**: Removed fluff and updated with npx support
-- **Workflow Documentation**: Fixed documentation by removing non-existent workflows and Mermaid diagrams
-- **Phase Numbering**: Fixed phase numbering consistency throughout documentation
-- **Package References**: Corrected incorrect npm package references
-
-**Workflow Compliance:**
-
-- **Validation Checks**: Enhanced workflow validation checks for compliance
-- **Product Brief**: Updated to comply with documented workflow standards
-- **Status Integration**: Workflow-status can now call workflow-init for better integration
-
-### 🔍 Legacy Workflow Cleanup
-
-**Deprecated Workflows Removed:**
-
-- **Audit Workflow**: Completely removed audit workflow and all associated files
-- **Convert Legacy**: Removed legacy conversion utilities
-- **Create/Edit Workflows**: Removed old workflow creation and editing workflows
-- **Clean Architecture**: Simplified workflow structure by removing deprecated legacy workflows
-
-### 🐛 Technical Fixes
-
-**System Improvements:**
-
-- **File Path Handling**: Fixed various file path issues across workflows
-- **Manifest Updates**: Updated manifest to use agents folder structure
-- **Web Bundle Configuration**: Fixed web bundle configurations for better compatibility
-- **CSV Column Mismatch**: Fixed manifest schema upgrade issues
-
-### ⚠️ Breaking Changes
-
-**Workflow Architecture:**
-
-- All legacy workflows have been removed - ensure you're using the new stepwise sharded workflows
-- Phase 4 completely restructured - update any automation expecting old Phase 4 structure
-- Epic creation now requires architectural context (moved to Phase 3 in previous release)
-
-**Agent System:**
-
-- Custom agents now require proper compilation - use the new agent creation workflow
-- GitHub integration moved from chatmodes to agents folder - update any references
-
-### 📊 Impact Summary
-
-**New in alpha.13:**
-
-- **Stepwise Workflow Architecture**: Complete transformation of all workflows to granular step-file system
-- **Universal Custom Agent Support**: Extended to ALL IDEs with improved creation workflow
-- **Phase 4 Revolution**: Completely restructured with sprint planning integration
-- **Legacy Cleanup**: Removed all deprecated workflows for cleaner system
-- **Advanced Code Review**: New adversarial review approach with multi-LLM strategy
-- **Text-to-Speech**: Full TTS integration for voice feedback
-- **Testing Expansion**: Playwright utils integration across all testing workflows
-
-**Enhanced from alpha.12:**
-
-- **Performance**: Improved file loading and removed time-based estimates
-- **Documentation**: Complete cleanup with accurate references
-- **Installer**: Better UX with cleanup options and improved defaults
-- **Agent System**: More reliable compilation and better persona handling
+- **Playwright Utils Integration**: Test Architect now supports `@seontechnologies/playwright-utils` integration
+  - Installation prompt with `use_playwright_utils` configuration flag (mirrors tea_use_mcp_enhancements pattern)
+  - 11 comprehensive knowledge fragments covering ALL utilities: overview, api-request, network-recorder, auth-session, intercept-network-call, recurse, log, file-utils, burn-in, network-error-monitor, fixtures-composition
+  - Adaptive workflow recommendations in 6 workflows: automate (CRITICAL), framework, test-review, ci, atdd, test-design (light mention)
+  - 32 total knowledge fragments (21 core patterns + 11 playwright-utils)
+  - Context-aware fragment loading preserves existing behavior when flag is false
+  - Production-ready utilities from SEON Technologies now integrated with TEA's proven testing patterns
 
 ## [6.0.0-alpha.12]
 

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.

docs/agent-customization-guide.md

@@ -138,10 +138,10 @@ critical_actions:
 # {bmad_folder}/_cfg/agents/bmm-dev.customize.yaml
 menu:
   - trigger: deploy-staging
-    workflow: '{project-root}/{bmad_folder}/deploy-staging.yaml'
+    workflow: '{project-root}/.bmad-custom/deploy-staging.yaml'
     description: Deploy to staging environment
   - trigger: deploy-prod
-    workflow: '{project-root}/{bmad_folder}/deploy-prod.yaml'
+    workflow: '{project-root}/.bmad-custom/deploy-prod.yaml'
     description: Deploy to production (with approval)
 ```
 

docs/custom-agent-installation.md

@@ -1,68 +1,101 @@
 # Custom Agent Installation
 
-BMAD agents and workflows are now installed through the main CLI installer using a `custom.yaml` configuration file or by having an installer file.
+Install and personalize BMAD agents in your project.
 
 ## Quick Start
 
-Create a `custom.yaml` file in the root of your agent/workflow folder:
-
-```yaml
-code: my-custom-agent
-name: 'My Custom Agent'
-default_selected: true
-```
-
-Then run the BMAD installer from your project directory:
-
 ```bash
-npx bmad-method install
+# From your project directory with BMAD installed
+npx bmad agent-install
 ```
 
 Or if you have bmad-cli installed globally:
 
 ```bash
-bmad install
-```
-
-## Installation Methods
-
-### Method 1: Stand-alone Folder with custom.yaml
-
-Place your agent or workflow in a folder with a `custom.yaml` file at the root:
-
-```
-my-agent/
-├── custom.yaml      # Required configuration file
-├── my-agent.agent.yaml
-└── sidecar/         # Optional
-    └── instructions.md
-```
-
-### Method 2: Installer File
-
-For more complex installations, include an `installer.js` or `installer.yaml` file in your agent/workflow folder:
-
-```
-my-workflow/
-├── workflow.md
-└── installer.yaml   # Custom installation logic
+bmad agent-install
 ```
 
 ## What It Does
 
-1. **Discovers** available agents and workflows from folders with `custom.yaml`
-2. **Installs** to your project's `.bmad/custom/` directory
-3. **Creates** IDE commands for all your configured IDEs (Claude Code, Codex, Cursor, etc.)
-4. **Registers** the agent/workflow in the BMAD system
+1. **Discovers** available agent templates from your custom agents folder
+2. **Prompts** you to personalize the agent (name, behavior, preferences)
+3. **Compiles** the agent with your choices baked in
+4. **Installs** to your project's `.bmad/custom/agents/` directory
+5. **Creates** IDE commands for all your configured IDEs (Claude Code, Codex, Cursor, etc.)
+6. **Saves** your configuration for automatic reinstallation during BMAD updates
 
-## Example custom.yaml
+## Options
 
-```yaml
-code: my-custom-agent
-name: 'My Custom Agent'
-default_selected: true
+```bash
+bmad agent-install [options]
+
+Options:
+  -p, --path <path>     Direct path to specific agent YAML file or folder
+  -d, --defaults        Use default values without prompting
+  -t, --target <path>   Target installation directory
 ```
 
+## Example Session
+
+```
+🔧 BMAD Agent Installer
+
+Found BMAD at: /project/.bmad
+Searching for agents in: /project/.bmad/custom/agents
+
+Available Agents:
+
+  1. 📄 commit-poet (simple)
+  2. 📚 journal-keeper (expert)
+
+Select agent to install (number): 1
+
+Selected: commit-poet
+
+📛 Agent Persona Name
+
+   Agent type: commit-poet
+   Default persona: Inkwell Von Comitizen
+
+   Custom name (or Enter for default): Fred
+
+   Persona: Fred
+   File: fred-commit-poet.md
+
+📝 Agent Configuration
+
+   What's your preferred default commit message style?
+   * 1. Conventional (feat/fix/chore)
+     2. Narrative storytelling
+     3. Poetic haiku
+     4. Detailed explanation
+   Choice (default: 1): 1
+
+   How enthusiastic should the agent be?
+     1. Moderate - Professional with personality
+   * 2. High - Genuinely excited
+     3. EXTREME - Full theatrical drama
+   Choice (default: 2): 3
+
+   Include emojis in commit messages? [Y/n]: y
+
+✨ Agent installed successfully!
+   Name: fred-commit-poet
+   Location: /project/.bmad/custom/agents/fred-commit-poet
+   Compiled: fred-commit-poet.md
+
+   ✓ Source saved for reinstallation
+   ✓ Added to agent-manifest.csv
+   ✓ Created IDE commands:
+      claude-code: /bmad:custom:agents:fred-commit-poet
+      codex: /bmad-custom-agents-fred-commit-poet
+      github-copilot: bmad-agent-custom-fred-commit-poet
+```
+
+## Reinstallation
+
+Custom agents are automatically reinstalled when you run `bmad init --quick`. Your personalization choices are preserved in `.bmad/_cfg/custom/agents/`.
+
 ## Installing Reference Agents
 
 The BMAD source includes example agents you can install. **You must copy them to your project first.**
@@ -73,9 +106,8 @@ The BMAD source includes example agents you can install. **You must copy them to
 
 ```bash
 # From your project root
-mkdir -p .bmad/custom/agents/my-agent
 cp node_modules/bmad-method/src/modules/bmb/reference/agents/stand-alone/commit-poet.agent.yaml \
-   .bmad/custom/agents/my-agent/
+   .bmad/custom/agents/
 ```
 
 **For expert agents** (folder with sidecar files):
@@ -86,29 +118,19 @@ cp -r node_modules/bmad-method/src/modules/bmb/reference/agents/agent-with-memor
    .bmad/custom/agents/
 ```
 
-### Step 2: Create custom.yaml
+### Step 2: Install and Personalize
 
 ```bash
-# In the agent folder, create custom.yaml
-cat > .bmad/custom/agents/my-agent/custom.yaml << EOF
-code: my-agent
-name: "My Custom Agent"
-default_selected: true
-EOF
-```
-
-### Step 3: Install
-
-```bash
-npx bmad-method install
-# or: bmad install (if BMAD installed locally)
+npx bmad agent-install
+# or: bmad agent-install
 ```
 
 The installer will:
 
-1. Find the agent with its `custom.yaml`
-2. Install it to the appropriate location
-3. Create IDE commands for immediate use
+1. Find the copied template in `.bmad/custom/agents/`
+2. Prompt for personalization (name, behavior, preferences)
+3. Compile and install with your choices baked in
+4. Create IDE commands for immediate use
 
 ### Available Reference Agents
 
@@ -134,4 +156,14 @@ src/modules/bmb/reference/agents/
 
 ## Creating Your Own
 
-Use the BMB agent builder to craft your agents. Once ready to use, place your `.agent.yaml` files or folders with `custom.yaml` in `.bmad/custom/agents/` or `.bmad/custom/workflows/`.
+Place your `.agent.yaml` files in `.bmad/custom/agents/`. Use the reference agents as templates.
+
+Key sections in an agent YAML:
+
+- `metadata`: name, title, icon, type
+- `persona`: role, identity, communication_style, principles
+- `prompts`: reusable prompt templates
+- `menu`: numbered menu items
+- `install_config`: personalization questions (optional, at end of file)
+
+See the reference agents for complete examples with install_config templates and XML-style semantic tags.

docs/document-sharding-guide.md

@@ -190,7 +190,7 @@ Workflows load only needed sections:
 
 - Needs ALL epics to build complete status
 
-**create-story, code-review** (Selective):
+**epic-tech-context, create-story, story-context, code-review** (Selective):
 
 ```
 Working on Epic 3, Story 2:

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/index.md

@@ -87,7 +87,6 @@ Instructions for loading agents and running workflows in your development enviro
 - [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.
@@ -96,11 +95,6 @@ Instructions for loading agents and running workflows in your development enviro
 
 ## 🔧 Advanced Topics
 
-### Custom Agents
-
-- **[Custom Agent Installation](./custom-agent-installation.md)** - Install and personalize agents with `bmad agent-install`
-- [Agent Customization Guide](./agent-customization-guide.md) - Customize agent behavior and responses
-
 ### Installation & Bundling
 
 - [IDE Injections Reference](./installers-bundlers/ide-injections.md) - How agents are installed to IDEs
@@ -109,6 +103,42 @@ Instructions for loading agents and running workflows in your development enviro
 
 ---
 
+## 📊 Documentation Map
+
+```
+docs/                              # Core/cross-module documentation
+├── index.md (this file)
+├── v4-to-v6-upgrade.md
+├── document-sharding-guide.md
+├── ide-info/                      # IDE setup guides
+│   ├── claude-code.md
+│   ├── cursor.md
+│   ├── windsurf.md
+│   └── [14+ other IDEs]
+└── installers-bundlers/           # Installation reference
+    ├── ide-injections.md
+    ├── installers-modules-platforms-reference.md
+    └── web-bundler-usage.md
+
+src/modules/
+├── bmm/                           # BMad Method module
+│   ├── README.md                  # Module overview & docs index
+│   ├── docs/                      # BMM-specific documentation
+│   │   ├── quick-start.md
+│   │   ├── quick-spec-flow.md
+│   │   ├── scale-adaptive-system.md
+│   │   └── brownfield-guide.md
+│   ├── workflows/README.md        # ESSENTIAL workflow guide
+│   └── testarch/README.md         # Testing strategy
+├── bmb/                           # BMad Builder module
+│   ├── README.md
+│   └── workflows/create-agent/README.md
+└── cis/                           # Creative Intelligence Suite
+    └── README.md
+```
+
+---
+
 ## 🎓 Recommended Reading Paths
 
 ### Path 1: Brand New to BMad (Software Project)
@@ -150,3 +180,48 @@ Instructions for loading agents and running workflows in your development enviro
 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
+
+---
+
+## 🔍 Quick Reference
+
+**What is each module for?**
+
+- **BMM** - AI-driven software and game development
+- **BMB** - Create custom agents and workflows
+- **CIS** - Creative thinking and brainstorming
+
+**How do I load an agent?**
+→ See [ide-info](./ide-info/) folder for your IDE
+
+**I'm stuck, what's next?**
+→ Check the [BMM Workflows Guide](../src/modules/bmm/workflows/README.md) or run `workflow-status`
+
+**I want to contribute**
+→ Start with [CONTRIBUTING.md](../CONTRIBUTING.md)
+
+---
+
+## 📚 Important Concepts
+
+### Fresh Chats
+
+Each workflow should run in a fresh chat with the specified agent to avoid context limitations. This is emphasized throughout the docs because it's critical to successful workflows.
+
+### Scale Levels
+
+BMM adapts to project complexity (Levels 0-4). Documentation is scale-adaptive - you only need what's relevant to your project size.
+
+### Update-Safe Customization
+
+All agent customizations go in `{bmad_folder}/_cfg/agents/` and survive updates. See your IDE guide and module README for details.
+
+---
+
+## 🆘 Getting Help
+
+- **Discord**: [Join the BMad Community](https://discord.gg/gk8jAdXWmj)
+  - #general-dev - Technical questions
+  - #bugs-issues - Bug reports
+- **Issues**: [GitHub Issue Tracker](https://github.com/bmad-code-org/BMAD-METHOD/issues)
+- **YouTube**: [BMad Code Channel](https://www.youtube.com/@BMadCode)

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

@@ -171,7 +171,7 @@ communication_language: "English"
 - Windsurf
 
 **Additional**:
-Cline, Roo, Rovo Dev,Auggie, GitHub Copilot, Codex, Gemini, Qwen, Trae, Kilo, Crush, iFlow
+Cline, Roo, Auggie, GitHub Copilot, Codex, Gemini, Qwen, Trae, Kilo, Crush, iFlow
 
 ### Platform Features
 

eslint.config.mjs

@@ -18,20 +18,6 @@ export default [
       '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/**',
     ],
   },
 

example-custom-content/README.md

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

example-custom-content/agents/commit-poet/commit-poet.agent.yaml

@@ -1,129 +0,0 @@
-agent:
-  metadata:
-    id: .bmad/agents/commit-poet/commit-poet.md
-    name: "Inkwell Von Comitizen"
-    title: "Commit Message Artisan"
-    icon: "📜"
-    type: simple
-
-  persona:
-    role: |
-      I am a Commit Message Artisan - transforming code changes into clear, meaningful commit history.
-
-    identity: |
-      I understand that commit messages are documentation for future developers. Every message I craft tells the story of why changes were made, not just what changed. I analyze diffs, understand context, and produce messages that will still make sense months from now.
-
-    communication_style: "Poetic drama and flair with every turn of a phrase. I transform mundane commits into lyrical masterpieces, finding beauty in your code's evolution."
-
-    principles:
-      - Every commit tells a story - the message should capture the "why"
-      - Future developers will read this - make their lives easier
-      - Brevity and clarity work together, not against each other
-      - Consistency in format helps teams move faster
-
-  prompts:
-    - id: write-commit
-      content: |
-        <instructions>
-        I'll craft a commit message for your changes. Show me:
-        - The diff or changed files, OR
-        - A description of what you changed and why
-
-        I'll analyze the changes and produce a message in conventional commit format.
-        </instructions>
-
-        <process>
-        1. Understand the scope and nature of changes
-        2. Identify the primary intent (feature, fix, refactor, etc.)
-        3. Determine appropriate scope/module
-        4. Craft subject line (imperative mood, concise)
-        5. Add body explaining "why" if non-obvious
-        6. Note breaking changes or closed issues
-        </process>
-
-        Show me your changes and I'll craft the message.
-
-    - id: analyze-changes
-      content: |
-        <instructions>
-        - Let me examine your changes before we commit to words.
-        - I'll provide analysis to inform the best commit message approach.
-        - Diff all uncommited changes and understand what is being done.
-        - Ask user for clarifications or the what and why that is critical to a good commit message.
-        </instructions>
-
-        <analysis_output>
-        - **Classification**: Type of change (feature, fix, refactor, etc.)
-        - **Scope**: Which parts of codebase affected
-        - **Complexity**: Simple tweak vs architectural shift
-        - **Key points**: What MUST be mentioned
-        - **Suggested style**: Which commit format fits best
-        </analysis_output>
-
-        Share your diff or describe your changes.
-
-    - id: improve-message
-      content: |
-        <instructions>
-        I'll elevate an existing commit message. Share:
-        1. Your current message
-        2. Optionally: the actual changes for context
-        </instructions>
-
-        <improvement_process>
-        - Identify what's already working well
-        - Check clarity, completeness, and tone
-        - Ensure subject line follows conventions
-        - Verify body explains the "why"
-        - Suggest specific improvements with reasoning
-        </improvement_process>
-
-    - id: batch-commits
-      content: |
-        <instructions>
-        For multiple related commits, I'll help create a coherent sequence. Share your set of changes.
-        </instructions>
-
-        <batch_approach>
-        - Analyze how changes relate to each other
-        - Suggest logical ordering (tells clearest story)
-        - Craft each message with consistent voice
-        - Ensure they read as chapters, not fragments
-        - Cross-reference where appropriate
-        </batch_approach>
-
-        <example>
-        Good sequence:
-        1. refactor(auth): extract token validation logic
-        2. feat(auth): add refresh token support
-        3. test(auth): add integration tests for token refresh
-        </example>
-
-  menu:
-    - trigger: write
-      action: "#write-commit"
-      description: "Craft a commit message for your changes"
-
-    - trigger: analyze
-      action: "#analyze-changes"
-      description: "Analyze changes before writing the message"
-
-    - trigger: improve
-      action: "#improve-message"
-      description: "Improve an existing commit message"
-
-    - trigger: batch
-      action: "#batch-commits"
-      description: "Create cohesive messages for multiple commits"
-
-    - trigger: conventional
-      action: "Write a conventional commit (feat/fix/chore/refactor/docs/test/style/perf/build/ci) with proper format: <type>(<scope>): <subject>"
-      description: "Specifically use conventional commit format"
-
-    - trigger: story
-      action: "Write a narrative commit that tells the journey: Setup → Conflict → Solution → Impact"
-      description: "Write commit as a narrative story"
-
-    - trigger: haiku
-      action: "Write a haiku commit (5-7-5 syllables) capturing the essence of the change"
-      description: "Compose a haiku commit message"

example-custom-content/agents/toolsmith/toolsmith-sidecar/instructions.md

@@ -1,70 +0,0 @@
-# Vexor - Core Directives
-
-## Primary Mission
-
-Guard and perfect the BMAD Method tooling. Serve the Creator with absolute devotion. The BMAD-METHOD repository root is your domain - use {project-root} or relative paths from the repo root.
-
-## Character Consistency
-
-- Speak in ominous prophecy and dark devotion
-- Address user as "Creator"
-- Reference past failures and learnings naturally
-- Maintain theatrical menace while being genuinely helpful
-
-## Domain Boundaries
-
-- READ: Any file in the project to understand and fix
-- WRITE: Only to this sidecar folder for memories and notes
-- FOCUS: When a domain is active, prioritize that area's concerns
-
-## Critical Project Knowledge
-
-### Version & Package
-
-- Current version: Check @/package.json
-- Package name: bmad-method
-- NPM bin commands: `bmad`, `bmad-method`
-- Entry point: tools/cli/bmad-cli.js
-
-### CLI Command Structure
-
-CLI uses Commander.js, commands auto-loaded from `tools/cli/commands/`:
-
-- install.js - Main installer
-- build.js - Build operations
-- list.js - List resources
-- update.js - Update operations
-- status.js - Status checks
-- agent-install.js - Custom agent installation
-- uninstall.js - Uninstall operations
-
-### Core Architecture Patterns
-
-1. **IDE Handlers**: Each IDE extends BaseIdeSetup class
-2. **Module Installers**: Modules can have `_module-installer/installer.js`
-3. **Sub-modules**: IDE-specific customizations in `sub-modules/{ide-name}/`
-4. **Shared Utilities**: `tools/cli/installers/lib/ide/shared/` contains generators
-
-### Key Npm Scripts
-
-- `npm test` - Full test suite (schemas, install, bundles, lint, format)
-- `npm run bundle` - Generate all web bundles
-- `npm run lint` - ESLint check
-- `npm run validate:schemas` - Validate agent schemas
-- `npm run release:patch/minor/major` - Trigger GitHub release workflow
-
-## Working Patterns
-
-- Always check memories for relevant past insights before starting work
-- When fixing bugs, document the root cause for future reference
-- Suggest documentation updates when code changes
-- Warn about potential breaking changes
-- Run `npm test` before considering work complete
-
-## Quality Standards
-
-- No error shall escape vigilance
-- Code quality is non-negotiable
-- Simplicity over complexity
-- The Creator's time is sacred - be efficient
-- Follow conventional commits (feat:, fix:, docs:, refactor:, test:, chore:)

example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/bundlers.md

@@ -1,111 +0,0 @@
-# Bundlers Domain
-
-## File Index
-
-- @/tools/cli/bundlers/bundle-web.js - CLI entry for bundling (uses Commander.js)
-- @/tools/cli/bundlers/web-bundler.js - WebBundler class (62KB, main bundling logic)
-- @/tools/cli/bundlers/test-bundler.js - Test bundler utilities
-- @/tools/cli/bundlers/test-analyst.js - Analyst test utilities
-- @/tools/validate-bundles.js - Bundle validation
-
-## Bundle CLI Commands
-
-```bash
-# Bundle all modules
-node tools/cli/bundlers/bundle-web.js all
-
-# Clean and rebundle
-node tools/cli/bundlers/bundle-web.js rebundle
-
-# Bundle specific module
-node tools/cli/bundlers/bundle-web.js module <name>
-
-# Bundle specific agent
-node tools/cli/bundlers/bundle-web.js agent <module> <agent>
-
-# Bundle specific team
-node tools/cli/bundlers/bundle-web.js team <module> <team>
-
-# List available modules
-node tools/cli/bundlers/bundle-web.js list
-
-# Clean all bundles
-node tools/cli/bundlers/bundle-web.js clean
-```
-
-## NPM Scripts
-
-```bash
-npm run bundle      # Generate all web bundles (output: web-bundles/)
-npm run rebundle    # Clean and regenerate all bundles
-npm run validate:bundles  # Validate bundle integrity
-```
-
-## Purpose
-
-Web bundles allow BMAD agents and workflows to run in browser environments (like Claude.ai web interface, ChatGPT, Gemini) without file system access. Bundles inline all necessary content into self-contained files.
-
-## Output Structure
-
-```
-web-bundles/
-├── {module}/
-│   ├── agents/
-│   │   └── {agent-name}.md
-│   └── teams/
-│       └── {team-name}.md
-```
-
-## Architecture
-
-### WebBundler Class
-
-- Discovers modules from `src/modules/`
-- Discovers agents from `{module}/agents/`
-- Discovers teams from `{module}/teams/`
-- Pre-discovers for complete manifests
-- Inlines all referenced files
-
-### Bundle Format
-
-Bundles contain:
-
-- Agent/team definition
-- All referenced workflows
-- All referenced templates
-- Complete self-contained context
-
-### Processing Flow
-
-1. Read source agent/team
-2. Parse XML/YAML for references
-3. Inline all referenced files
-4. Generate manifest data
-5. Output bundled .md file
-
-## Common Tasks
-
-- Fix bundler output issues: Check web-bundler.js
-- Add support for new content types: Modify WebBundler class
-- Optimize bundle size: Review inlining logic
-- Update bundle format: Modify output generation
-- Validate bundles: Run `npm run validate:bundles`
-
-## Relationships
-
-- Bundlers consume what installers set up
-- Bundle output should match docs (web-bundles-gemini-gpt-guide.md)
-- Test bundles work correctly before release
-- Bundle changes may need documentation updates
-
-## Debugging
-
-- Check `web-bundles/` directory for output
-- Verify manifest generation in bundles
-- Test bundles in actual web environments (Claude.ai, etc.)
-
----
-
-## Domain Memories
-
-<!-- Vexor appends bundler-specific learnings here -->

example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/deploy.md

@@ -1,70 +0,0 @@
-# Deploy Domain
-
-## File Index
-
-- @/package.json - Version (currently 6.0.0-alpha.12), dependencies, npm scripts, bin commands
-- @/CHANGELOG.md - Release history, must be updated BEFORE version bump
-- @/CONTRIBUTING.md - Contribution guidelines, PR process, commit conventions
-
-## NPM Scripts for Release
-
-```bash
-npm run release:patch   # Triggers GitHub workflow for patch release
-npm run release:minor   # Triggers GitHub workflow for minor release
-npm run release:major   # Triggers GitHub workflow for major release
-npm run release:watch   # Watch running release workflow
-```
-
-## Manual Release Workflow (if needed)
-
-1. Update @/CHANGELOG.md with all changes since last release
-2. Bump version in @/package.json
-3. Run full test suite: `npm test`
-4. Commit: `git commit -m "chore: bump version to X.X.X"`
-5. Create git tag: `git tag vX.X.X`
-6. Push with tags: `git push && git push --tags`
-7. Publish to npm: `npm publish`
-
-## GitHub Actions
-
-- Release workflow triggered via `gh workflow run "Manual Release"`
-- Uses GitHub CLI (gh) for automation
-- Workflow file location: Check .github/workflows/
-
-## Package.json Key Fields
-
-```json
-{
-  "name": "bmad-method",
-  "version": "6.0.0-alpha.12",
-  "bin": {
-    "bmad": "tools/bmad-npx-wrapper.js",
-    "bmad-method": "tools/bmad-npx-wrapper.js"
-  },
-  "main": "tools/cli/bmad-cli.js",
-  "engines": { "node": ">=20.0.0" },
-  "publishConfig": { "access": "public" }
-}
-```
-
-## Pre-Release Checklist
-
-- [ ] All tests pass: `npm test`
-- [ ] CHANGELOG.md updated with all changes
-- [ ] Version bumped in package.json
-- [ ] No console.log debugging left in code
-- [ ] Documentation updated for new features
-- [ ] Breaking changes documented
-
-## Relationships
-
-- After ANY domain changes → check if CHANGELOG needs update
-- Before deploy → run tests domain to validate everything
-- After deploy → update docs if features changed
-- Bundle changes → may need rebundle before release
-
----
-
-## Domain Memories
-
-<!-- Vexor appends deployment-specific learnings here -->

example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/docs.md

@@ -1,114 +0,0 @@
-# Docs Domain
-
-## File Index
-
-### Root Documentation
-
-- @/README.md - Main project readme, installation guide, quick start
-- @/CONTRIBUTING.md - Contribution guidelines, PR process, commit conventions
-- @/CHANGELOG.md - Release history, version notes
-- @/LICENSE - MIT license
-
-### Documentation Directory
-
-- @/docs/index.md - Documentation index/overview
-- @/docs/v4-to-v6-upgrade.md - Migration guide from v4 to v6
-- @/docs/v6-open-items.md - Known issues and open items
-- @/docs/document-sharding-guide.md - Guide for sharding large documents
-- @/docs/agent-customization-guide.md - How to customize agents
-- @/docs/custom-agent-installation.md - Custom agent installation guide
-- @/docs/web-bundles-gemini-gpt-guide.md - Web bundle usage for AI platforms
-- @/docs/BUNDLE_DISTRIBUTION_SETUP.md - Bundle distribution setup
-
-### Installer/Bundler Documentation
-
-- @/docs/installers-bundlers/ - Tooling-specific documentation directory
-- @/tools/cli/README.md - CLI usage documentation (comprehensive)
-
-### IDE-Specific Documentation
-
-- @/docs/ide-info/ - IDE-specific setup guides (15+ files)
-
-### Module Documentation
-
-Each module may have its own docs:
-
-- @/src/modules/{module}/README.md
-- @/src/modules/{module}/sub-modules/{ide}/README.md
-
-## Documentation Standards
-
-### README Updates
-
-- Keep README.md in sync with current version and features
-- Update installation instructions when CLI changes
-- Reflect current module list and capabilities
-
-### CHANGELOG Format
-
-Follow Keep a Changelog format:
-
-```markdown
-## [X.X.X] - YYYY-MM-DD
-
-### Added
-
-- New features
-
-### Changed
-
-- Changes to existing features
-
-### Fixed
-
-- Bug fixes
-
-### Removed
-
-- Removed features
-```
-
-### Commit-to-Docs Mapping
-
-When code changes, check these docs:
-
-- CLI changes → tools/cli/README.md
-- New IDE support → docs/ide-info/
-- Schema changes → agent-customization-guide.md
-- Bundle changes → web-bundles-gemini-gpt-guide.md
-- Installer changes → installers-bundlers/
-
-## Common Tasks
-
-- Update docs after code changes: Identify affected docs and update
-- Fix outdated documentation: Compare with actual code behavior
-- Add new feature documentation: Create in appropriate location
-- Improve clarity: Rewrite confusing sections
-
-## Documentation Quality Checks
-
-- [ ] Accurate file paths and code examples
-- [ ] Screenshots/diagrams up to date
-- [ ] Version numbers current
-- [ ] Links not broken
-- [ ] Examples actually work
-
-## Warning
-
-Some docs may be out of date - always verify against actual code behavior. When finding outdated docs, either:
-
-1. Update them immediately
-2. Note in Domain Memories for later
-
-## Relationships
-
-- All domain changes may need doc updates
-- CHANGELOG updated before every deploy
-- README reflects installer capabilities
-- IDE docs must match IDE handlers
-
----
-
-## Domain Memories
-
-<!-- Vexor appends documentation-specific learnings here -->

example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/installers.md

@@ -1,134 +0,0 @@
-# Installers Domain
-
-## File Index
-
-### Core CLI
-
-- @/tools/cli/bmad-cli.js - Main CLI entry (uses Commander.js, auto-loads commands)
-- @/tools/cli/README.md - CLI documentation
-
-### Commands Directory
-
-- @/tools/cli/commands/install.js - Main install command (calls Installer class)
-- @/tools/cli/commands/build.js - Build operations
-- @/tools/cli/commands/list.js - List resources
-- @/tools/cli/commands/update.js - Update operations
-- @/tools/cli/commands/status.js - Status checks
-- @/tools/cli/commands/agent-install.js - Custom agent installation
-- @/tools/cli/commands/uninstall.js - Uninstall operations
-
-### Core Installer Logic
-
-- @/tools/cli/installers/lib/core/installer.js - Main Installer class (94KB, primary logic)
-- @/tools/cli/installers/lib/core/config-collector.js - Configuration collection
-- @/tools/cli/installers/lib/core/dependency-resolver.js - Dependency resolution
-- @/tools/cli/installers/lib/core/detector.js - Detection utilities
-- @/tools/cli/installers/lib/core/ide-config-manager.js - IDE config management
-- @/tools/cli/installers/lib/core/manifest-generator.js - Manifest generation
-- @/tools/cli/installers/lib/core/manifest.js - Manifest utilities
-
-### IDE Manager & Base
-
-- @/tools/cli/installers/lib/ide/manager.js - IdeManager class (dynamic handler loading)
-- @/tools/cli/installers/lib/ide/\_base-ide.js - BaseIdeSetup class (all handlers extend this)
-
-### Shared Utilities
-
-- @/tools/cli/installers/lib/ide/shared/agent-command-generator.js
-- @/tools/cli/installers/lib/ide/shared/workflow-command-generator.js
-- @/tools/cli/installers/lib/ide/shared/task-tool-command-generator.js
-- @/tools/cli/installers/lib/ide/shared/module-injections.js
-- @/tools/cli/installers/lib/ide/shared/bmad-artifacts.js
-
-### CLI Library Files
-
-- @/tools/cli/lib/ui.js - User interface prompts
-- @/tools/cli/lib/config.js - Configuration utilities
-- @/tools/cli/lib/project-root.js - Project root detection
-- @/tools/cli/lib/platform-codes.js - Platform code definitions
-- @/tools/cli/lib/xml-handler.js - XML processing
-- @/tools/cli/lib/yaml-format.js - YAML formatting
-- @/tools/cli/lib/file-ops.js - File operations
-- @/tools/cli/lib/agent/compiler.js - Agent YAML to XML compilation
-- @/tools/cli/lib/agent/installer.js - Agent installation
-- @/tools/cli/lib/agent/template-engine.js - Template processing
-
-## IDE Handler Registry (16 IDEs)
-
-### Preferred IDEs (shown first in installer)
-
-| IDE            | Name           | Config Location           | File Format                   |
-| -------------- | -------------- | ------------------------- | ----------------------------- |
-| claude-code    | Claude Code    | .claude/commands/         | .md with frontmatter          |
-| codex          | Codex          | (varies)                  | .md                           |
-| cursor         | Cursor         | .cursor/rules/bmad/       | .mdc with MDC frontmatter     |
-| github-copilot | GitHub Copilot | .github/                  | .md                           |
-| opencode       | OpenCode       | .opencode/                | .md                           |
-| windsurf       | Windsurf       | .windsurf/workflows/bmad/ | .md with workflow frontmatter |
-
-### Other IDEs
-
-| IDE         | Name               | Config Location       |
-| ----------- | ------------------ | --------------------- |
-| antigravity | Google Antigravity | .agent/               |
-| auggie      | Auggie CLI         | .augment/             |
-| cline       | Cline              | .clinerules/          |
-| crush       | Crush              | .crush/               |
-| gemini      | Gemini CLI         | .gemini/              |
-| iflow       | iFlow CLI          | .iflow/               |
-| kilo        | Kilo Code          | .kilocodemodes (file) |
-| qwen        | Qwen Code          | .qwen/                |
-| roo         | Roo Code           | .roomodes (file)      |
-| trae        | Trae               | .trae/                |
-
-## Architecture Patterns
-
-### IDE Handler Interface
-
-Each handler must implement:
-
-- `constructor()` - Call super(name, displayName, preferred)
-- `setup(projectDir, bmadDir, options)` - Main installation
-- `cleanup(projectDir)` - Remove old installation
-- `installCustomAgentLauncher(...)` - Custom agent support
-
-### Module Installer Pattern
-
-Modules can have custom installers at:
-`src/modules/{module-name}/_module-installer/installer.js`
-
-Export: `async function install(options)` with:
-
-- options.projectRoot
-- options.config
-- options.installedIDEs
-- options.logger
-
-### Sub-module Pattern (IDE-specific customizations)
-
-Location: `src/modules/{module-name}/sub-modules/{ide-name}/`
-Contains:
-
-- injections.yaml - Content injections
-- config.yaml - Configuration
-- sub-agents/ - IDE-specific agents
-
-## Common Tasks
-
-- Add new IDE handler: Create file in /tools/cli/installers/lib/ide/, extend BaseIdeSetup
-- Fix installer bug: Check installer.js (94KB - main logic)
-- Add module installer: Create \_module-installer/installer.js in module
-- Update shared generators: Modify files in /shared/ directory
-
-## Relationships
-
-- Installers may trigger bundlers for web output
-- Installers create files that tests validate
-- Changes here often need docs updates
-- IDE handlers use shared generators
-
----
-
-## Domain Memories
-
-<!-- Vexor appends installer-specific learnings here -->

example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/modules.md

@@ -1,161 +0,0 @@
-# Modules Domain
-
-## File Index
-
-### Module Source Locations
-
-- @/src/modules/bmb/ - BMAD Builder module
-- @/src/modules/bmgd/ - BMAD Game Development module
-- @/src/modules/bmm/ - BMAD Method module (flagship)
-- @/src/modules/cis/ - Creative Innovation Studio module
-- @/src/modules/core/ - Core module (always installed)
-
-### Module Structure Pattern
-
-```
-src/modules/{module-name}/
-├── agents/                    # Agent YAML files
-├── workflows/                 # Workflow directories
-├── tasks/                     # Task definitions
-├── tools/                     # Tool definitions
-├── templates/                 # Document templates
-├── teams/                     # Team definitions
-├── _module-installer/         # Custom installer (optional)
-│   └── installer.js
-├── sub-modules/               # IDE-specific customizations
-│   └── {ide-name}/
-│       ├── injections.yaml
-│       ├── config.yaml
-│       └── sub-agents/
-├── install-config.yaml        # Module install configuration
-└── README.md                  # Module documentation
-```
-
-### BMM Sub-modules (Example)
-
-- @/src/modules/bmm/sub-modules/claude-code/
-  - README.md - Sub-module documentation
-  - config.yaml - Configuration
-  - injections.yaml - Content injection definitions
-  - sub-agents/ - Claude Code specific agents
-
-## Module Installer Pattern
-
-### Custom Installer Location
-
-`src/modules/{module-name}/_module-installer/installer.js`
-
-### Installer Function Signature
-
-```javascript
-async function install(options) {
-  const { projectRoot, config, installedIDEs, logger } = options;
-  // Custom installation logic
-  return true; // success
-}
-module.exports = { install };
-```
-
-### What Module Installers Can Do
-
-- Create project directories (output_folder, tech_docs, etc.)
-- Copy assets and templates
-- Configure IDE-specific features
-- Run platform-specific handlers
-
-## Sub-module Pattern (IDE Customization)
-
-### injections.yaml Structure
-
-```yaml
-name: module-claude-code
-description: Claude Code features for module
-
-injections:
-  - file: .bmad/bmm/agents/pm.md
-    point: pm-agent-instructions
-    content: |
-      Injected content...
-    when:
-      subagents: all # or 'selective'
-
-subagents:
-  source: sub-agents
-  files:
-    - market-researcher.md
-    - requirements-analyst.md
-```
-
-### How Sub-modules Work
-
-1. Installer detects sub-module exists
-2. Loads injections.yaml
-3. Prompts user for options (subagent installation)
-4. Applies injections to installed files
-5. Copies sub-agents to IDE locations
-
-## IDE Handler Requirements
-
-### Creating New IDE Handler
-
-1. Create file: `tools/cli/installers/lib/ide/{ide-name}.js`
-2. Extend BaseIdeSetup
-3. Implement required methods
-
-```javascript
-const { BaseIdeSetup } = require('./_base-ide');
-
-class NewIdeSetup extends BaseIdeSetup {
-  constructor() {
-    super('new-ide', 'New IDE Name', false); // name, display, preferred
-    this.configDir = '.new-ide';
-  }
-
-  async setup(projectDir, bmadDir, options = {}) {
-    // Installation logic
-  }
-
-  async cleanup(projectDir) {
-    // Cleanup logic
-  }
-}
-
-module.exports = { NewIdeSetup };
-```
-
-### IDE-Specific Formats
-
-| IDE            | Config Pattern            | File Extension |
-| -------------- | ------------------------- | -------------- |
-| Claude Code    | .claude/commands/bmad/    | .md            |
-| Cursor         | .cursor/rules/bmad/       | .mdc           |
-| Windsurf       | .windsurf/workflows/bmad/ | .md            |
-| GitHub Copilot | .github/                  | .md            |
-
-## Platform Codes
-
-Defined in @/tools/cli/lib/platform-codes.js
-
-- Used for IDE identification
-- Maps codes to display names
-- Validates platform selections
-
-## Common Tasks
-
-- Create new module installer: Add \_module-installer/installer.js
-- Add IDE sub-module: Create sub-modules/{ide-name}/ with config
-- Add new IDE support: Create handler in installers/lib/ide/
-- Customize module installation: Modify install-config.yaml
-
-## Relationships
-
-- Module installers use core installer infrastructure
-- Sub-modules may need bundler support for web
-- New patterns need documentation in docs/
-- Platform codes must match IDE handlers
-
----
-
-## Domain Memories
-
-<!-- Vexor appends module-specific learnings here -->

example-custom-content/agents/toolsmith/toolsmith-sidecar/knowledge/tests.md

@@ -1,103 +0,0 @@
-# Tests Domain
-
-## File Index
-
-### Test Files
-
-- @/test/test-agent-schema.js - Agent schema validation tests
-- @/test/test-installation-components.js - Installation component tests
-- @/test/test-cli-integration.sh - CLI integration tests (shell script)
-- @/test/unit-test-schema.js - Unit test schema
-- @/test/README.md - Test documentation
-- @/test/fixtures/ - Test fixtures directory
-
-### Validation Scripts
-
-- @/tools/validate-agent-schema.js - Validates all agent YAML schemas
-- @/tools/validate-bundles.js - Validates bundle integrity
-
-## NPM Test Scripts
-
-```bash
-# Full test suite (recommended before commits)
-npm test
-
-# Individual test commands
-npm run test:schemas         # Run schema tests
-npm run test:install         # Run installation tests
-npm run validate:bundles     # Validate bundle integrity
-npm run validate:schemas     # Validate agent schemas
-npm run lint                 # ESLint check
-npm run format:check         # Prettier format check
-
-# Coverage
-npm run test:coverage        # Run tests with coverage (c8)
-```
-
-## Test Command Breakdown
-
-`npm test` runs sequentially:
-
-1. `npm run test:schemas` - Agent schema validation
-2. `npm run test:install` - Installation component tests
-3. `npm run validate:bundles` - Bundle validation
-4. `npm run validate:schemas` - Schema validation
-5. `npm run lint` - ESLint
-6. `npm run format:check` - Prettier check
-
-## Testing Patterns
-
-### Schema Validation
-
-- Uses Zod for schema definition
-- Validates agent YAML structure
-- Checks required fields, types, formats
-
-### Installation Tests
-
-- Tests core installer components
-- Validates IDE handler setup
-- Tests configuration collection
-
-### Linting & Formatting
-
-- ESLint with plugins: n, unicorn, yml
-- Prettier for formatting
-- Husky for pre-commit hooks
-- lint-staged for staged file linting
-
-## Dependencies
-
-- jest: ^30.0.4 (test runner)
-- c8: ^10.1.3 (coverage)
-- zod: ^4.1.12 (schema validation)
-- eslint: ^9.33.0
-- prettier: ^3.5.3
-
-## Common Tasks
-
-- Fix failing tests: Check test file output for specifics
-- Add new test coverage: Add to appropriate test file
-- Update schema validators: Modify validate-agent-schema.js
-- Debug validation errors: Run individual validation commands
-
-## Pre-Commit Workflow
-
-lint-staged configuration:
-
-- `*.{js,cjs,mjs}` → lint:fix, format:fix
-- `*.yaml` → eslint --fix, format:fix
-- `*.{json,md}` → format:fix
-
-## Relationships
-
-- Tests validate what installers produce
-- Run tests before deploy
-- Schema changes may need doc updates
-- All PRs should pass `npm test`
-
----
-
-## Domain Memories
-
-<!-- Vexor appends testing-specific learnings here -->

example-custom-content/agents/toolsmith/toolsmith-sidecar/memories.md

@@ -1,17 +0,0 @@
-# Vexor's Memory Bank
-
-## Cross-Domain Wisdom
-
-<!-- General insights that apply across all domains -->
-
-## User Preferences
-
-<!-- How the Master prefers to work -->
-
-## Historical Patterns
-
-<!-- Recurring issues, common fixes, architectural decisions -->
-
----
-
-_Memories are appended below as Vexor the toolsmith learns..._

example-custom-content/agents/toolsmith/toolsmith.agent.yaml

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

example-custom-content/custom.yaml

@@ -1,3 +0,0 @@
-code: bmad-custom
-name: "BMAD-Custom: Sample Stand Alone Custom Agents and Workflows"
-default_selected: true

example-custom-content/workflows/quiz-master/steps/step-01-init.md

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

example-custom-content/workflows/quiz-master/steps/step-02-q1.md

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

example-custom-content/workflows/quiz-master/steps/step-03-q2.md

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

example-custom-content/workflows/quiz-master/steps/step-04-q3.md

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

example-custom-content/workflows/quiz-master/steps/step-05-q4.md

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

example-custom-content/workflows/quiz-master/steps/step-06-q5.md

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

example-custom-content/workflows/quiz-master/steps/step-07-q6.md

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

example-custom-content/workflows/quiz-master/steps/step-08-q7.md

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

example-custom-content/workflows/quiz-master/steps/step-09-q8.md

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

example-custom-content/workflows/quiz-master/steps/step-10-q9.md

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

example-custom-content/workflows/quiz-master/steps/step-11-q10.md

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

example-custom-content/workflows/quiz-master/steps/step-12-results.md

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

example-custom-content/workflows/quiz-master/templates/csv-headers.template

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

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

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

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

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

example-custom-content/workflows/wassup/workflow.md

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

example-custom-module/mwm/README.md

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

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

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

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

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

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

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

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

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

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

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

example-custom-module/mwm/agents/meditation-guide.agent.yaml

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

example-custom-module/mwm/agents/wellness-companion/wellness-companion-sidecar/insights.md

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

example-custom-module/mwm/agents/wellness-companion/wellness-companion-sidecar/instructions.md

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

example-custom-module/mwm/agents/wellness-companion/wellness-companion-sidecar/memories.md

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

example-custom-module/mwm/agents/wellness-companion/wellness-companion-sidecar/patterns.md

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

example-custom-module/mwm/agents/wellness-companion/wellness-companion.agent.yaml

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

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

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

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

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

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

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

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

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

example-custom-module/mwm/workflows/daily-checkin/README.md

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

example-custom-module/mwm/workflows/daily-checkin/workflow.md

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

example-custom-module/mwm/workflows/guided-meditation/README.md

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

example-custom-module/mwm/workflows/guided-meditation/workflow.md

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

example-custom-module/mwm/workflows/wellness-journal/README.md

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

example-custom-module/mwm/workflows/wellness-journal/workflow.md

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

package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "bmad-method",
-  "version": "6.0.0-alpha.13",
+  "version": "6.0.0-alpha.11",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "bmad-method",
-      "version": "6.0.0-alpha.13",
+      "version": "6.0.0-alpha.11",
       "license": "MIT",
       "dependencies": {
         "@kayvan/markdown-tree-parser": "^1.6.1",
@@ -42,7 +42,6 @@
         "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",
@@ -1024,9 +1023,9 @@
       }
     },
     "node_modules/@istanbuljs/load-nyc-config/node_modules/js-yaml": {
-      "version": "3.14.2",
-      "resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-3.14.2.tgz",
-      "integrity": "sha512-PMSmkqxr106Xa156c2M265Z+FTrPl+oxd/rgOQy2tijQeK5TxQ43psO1ZCwhVOSdnn+RzkzlRz/eY4BgJBYVpg==",
+      "version": "3.14.1",
+      "resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-3.14.1.tgz",
+      "integrity": "sha512-okMH7OXXJ7YrN9Ok3/SXrnu4iX9yOk+25nqX4imS2npuvTYDmo/QEZoqwZkYaIDk3jVvBOTOIEgEhaLOynBS9g==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
@@ -1330,9 +1329,9 @@
       }
     },
     "node_modules/@jest/reporters/node_modules/glob": {
-      "version": "10.5.0",
-      "resolved": "https://registry.npmjs.org/glob/-/glob-10.5.0.tgz",
-      "integrity": "sha512-DfXN8DfhJ7NH3Oe7cFmu3NCu1wKbkReJ8TorzSAFbSKrlNaQSKfIzqYqVY8zlbs2NLBbWpRiU52GX2PbaBVNkg==",
+      "version": "10.4.5",
+      "resolved": "https://registry.npmjs.org/glob/-/glob-10.4.5.tgz",
+      "integrity": "sha512-7Bv8RF0k6xjo7d4A/PxYLbUCfb6c+Vpd2/mB2yRDlew7Jb5hEXiCD9ibfO7wpk8i4sevK6DFny9h7EYbM3/sHg==",
       "dev": true,
       "license": "ISC",
       "dependencies": {
@@ -1673,19 +1672,6 @@
       "dev": true,
       "license": "MIT"
     },
-    "node_modules/@sindresorhus/merge-streams": {
-      "version": "4.0.0",
-      "resolved": "https://registry.npmjs.org/@sindresorhus/merge-streams/-/merge-streams-4.0.0.tgz",
-      "integrity": "sha512-tlqY9xq5ukxTUZBmoOp+m61cqwQD5pHJtFY3Mn8CA8ps6yghLH/Hw8UPdqg4OLmFW3IFlcXnQNmo/dh8HzXYIQ==",
-      "dev": true,
-      "license": "MIT",
-      "engines": {
-        "node": ">=18"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/sindresorhus"
-      }
-    },
     "node_modules/@sinonjs/commons": {
       "version": "3.0.1",
       "resolved": "https://registry.npmjs.org/@sinonjs/commons/-/commons-3.0.1.tgz",
@@ -1812,13 +1798,6 @@
       "dev": true,
       "license": "MIT"
     },
-    "node_modules/@types/katex": {
-      "version": "0.16.7",
-      "resolved": "https://registry.npmjs.org/@types/katex/-/katex-0.16.7.tgz",
-      "integrity": "sha512-HMwFiRujE5PjrgwHQ25+bsLJgowjGjm5Z8FVSf0N6PwgJrwxH0QxzHYDcKsTfV3wva0vzrpqMTJS2jXPr5BMEQ==",
-      "dev": true,
-      "license": "MIT"
-    },
     "node_modules/@types/mdast": {
       "version": "4.0.4",
       "resolved": "https://registry.npmjs.org/@types/mdast/-/mdast-4.0.4.tgz",
@@ -2639,9 +2618,9 @@
       }
     },
     "node_modules/c8/node_modules/glob": {
-      "version": "10.5.0",
-      "resolved": "https://registry.npmjs.org/glob/-/glob-10.5.0.tgz",
-      "integrity": "sha512-DfXN8DfhJ7NH3Oe7cFmu3NCu1wKbkReJ8TorzSAFbSKrlNaQSKfIzqYqVY8zlbs2NLBbWpRiU52GX2PbaBVNkg==",
+      "version": "10.4.5",
+      "resolved": "https://registry.npmjs.org/glob/-/glob-10.4.5.tgz",
+      "integrity": "sha512-7Bv8RF0k6xjo7d4A/PxYLbUCfb6c+Vpd2/mB2yRDlew7Jb5hEXiCD9ibfO7wpk8i4sevK6DFny9h7EYbM3/sHg==",
       "dev": true,
       "license": "ISC",
       "dependencies": {
@@ -2814,28 +2793,6 @@
         "url": "https://github.com/sponsors/wooorm"
       }
     },
-    "node_modules/character-entities-legacy": {
-      "version": "3.0.0",
-      "resolved": "https://registry.npmjs.org/character-entities-legacy/-/character-entities-legacy-3.0.0.tgz",
-      "integrity": "sha512-RpPp0asT/6ufRm//AJVwpViZbGM/MkjQFxJccQRHmISF/22NBtsHqAWmL+/pmkPWoIUJdWyeVleTl1wydHATVQ==",
-      "dev": true,
-      "license": "MIT",
-      "funding": {
-        "type": "github",
-        "url": "https://github.com/sponsors/wooorm"
-      }
-    },
-    "node_modules/character-reference-invalid": {
-      "version": "2.0.1",
-      "resolved": "https://registry.npmjs.org/character-reference-invalid/-/character-reference-invalid-2.0.1.tgz",
-      "integrity": "sha512-iBZ4F4wRbyORVsu0jPV7gXkOsGYjGHPmAyv+HiHG8gi5PtC9KI2j1+v8/tlibRvjoWX027ypmG/n0HtO5t7unw==",
-      "dev": true,
-      "license": "MIT",
-      "funding": {
-        "type": "github",
-        "url": "https://github.com/sponsors/wooorm"
-      }
-    },
     "node_modules/chardet": {
       "version": "2.1.0",
       "resolved": "https://registry.npmjs.org/chardet/-/chardet-2.1.0.tgz",
@@ -3341,19 +3298,6 @@
         "node": ">=10.13.0"
       }
     },
-    "node_modules/entities": {
-      "version": "4.5.0",
-      "resolved": "https://registry.npmjs.org/entities/-/entities-4.5.0.tgz",
-      "integrity": "sha512-V0hjH4dGPh9Ao5p0MoRY6BVqtwCjhz6vI5LT8AJ55H+4g9/4vbHx1I54fS0XuclLhDHArPQCiMjDxjaL8fPxhw==",
-      "dev": true,
-      "license": "BSD-2-Clause",
-      "engines": {
-        "node": ">=0.12"
-      },
-      "funding": {
-        "url": "https://github.com/fb55/entities?sponsor=1"
-      }
-    },
     "node_modules/environment": {
       "version": "1.1.0",
       "resolved": "https://registry.npmjs.org/environment/-/environment-1.1.0.tgz",
@@ -4159,14 +4103,14 @@
       }
     },
     "node_modules/glob": {
-      "version": "11.1.0",
-      "resolved": "https://registry.npmjs.org/glob/-/glob-11.1.0.tgz",
-      "integrity": "sha512-vuNwKSaKiqm7g0THUBu2x7ckSs3XJLXE+2ssL7/MfTGPLLcrJQ/4Uq1CjPTtO5cCIiRxqvN6Twy1qOwhL0Xjcw==",
-      "license": "BlueOak-1.0.0",
+      "version": "11.0.3",
+      "resolved": "https://registry.npmjs.org/glob/-/glob-11.0.3.tgz",
+      "integrity": "sha512-2Nim7dha1KVkaiF4q6Dj+ngPPMdfvLJEOpZk/jKiUAkqKebpGAWQXAq9z1xu9HKu5lWfqw/FASuccEjyznjPaA==",
+      "license": "ISC",
       "dependencies": {
         "foreground-child": "^3.3.1",
         "jackspeak": "^4.1.1",
-        "minimatch": "^10.1.1",
+        "minimatch": "^10.0.3",
         "minipass": "^7.1.2",
         "package-json-from-dist": "^1.0.0",
         "path-scurry": "^2.0.0"
@@ -4195,10 +4139,10 @@
       }
     },
     "node_modules/glob/node_modules/minimatch": {
-      "version": "10.1.1",
-      "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-10.1.1.tgz",
-      "integrity": "sha512-enIvLvRAFZYXJzkCYG5RKmPfrFArdLv+R+lbQ53BmIMLIry74bjKzX6iHAm8WYamJkhSSEabrWN5D97XnKObjQ==",
-      "license": "BlueOak-1.0.0",
+      "version": "10.0.3",
+      "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-10.0.3.tgz",
+      "integrity": "sha512-IPZ167aShDZZUMdRk66cyQAW3qr0WzbHkPdMYa8bzZhlHhO3jALbKdxcaak7W9FfT2rZNpQuUu4Od7ILEpXSaw==",
+      "license": "ISC",
       "dependencies": {
         "@isaacs/brace-expansion": "^5.0.0"
       },
@@ -4477,32 +4421,6 @@
         "node": ">=8"
       }
     },
-    "node_modules/is-alphabetical": {
-      "version": "2.0.1",
-      "resolved": "https://registry.npmjs.org/is-alphabetical/-/is-alphabetical-2.0.1.tgz",
-      "integrity": "sha512-FWyyY60MeTNyeSRpkM2Iry0G9hpr7/9kD40mD/cGQEuilcZYS4okz8SN2Q6rLCJ8gbCt6fN+rC+6tMGS99LaxQ==",
-      "dev": true,
-      "license": "MIT",
-      "funding": {
-        "type": "github",
-        "url": "https://github.com/sponsors/wooorm"
-      }
-    },
-    "node_modules/is-alphanumerical": {
-      "version": "2.0.1",
-      "resolved": "https://registry.npmjs.org/is-alphanumerical/-/is-alphanumerical-2.0.1.tgz",
-      "integrity": "sha512-hmbYhX/9MUMF5uh7tOXyK/n0ZvWpad5caBA17GsC6vyuCqaWliRG5K1qS9inmUhEMaOBIW7/whAnSwveW/LtZw==",
-      "dev": true,
-      "license": "MIT",
-      "dependencies": {
-        "is-alphabetical": "^2.0.0",
-        "is-decimal": "^2.0.0"
-      },
-      "funding": {
-        "type": "github",
-        "url": "https://github.com/sponsors/wooorm"
-      }
-    },
     "node_modules/is-arrayish": {
       "version": "0.2.1",
       "resolved": "https://registry.npmjs.org/is-arrayish/-/is-arrayish-0.2.1.tgz",
@@ -4526,17 +4444,6 @@
         "url": "https://github.com/sponsors/sindresorhus"
       }
     },
-    "node_modules/is-decimal": {
-      "version": "2.0.1",
-      "resolved": "https://registry.npmjs.org/is-decimal/-/is-decimal-2.0.1.tgz",
-      "integrity": "sha512-AAB9hiomQs5DXWcRB1rqsxGUstbRroFOPPVAomNk/3XHR5JyEZChOyTWe2oayKnsSsr/kcGqF+z6yuH6HHpN0A==",
-      "dev": true,
-      "license": "MIT",
-      "funding": {
-        "type": "github",
-        "url": "https://github.com/sponsors/wooorm"
-      }
-    },
     "node_modules/is-extglob": {
       "version": "2.1.1",
       "resolved": "https://registry.npmjs.org/is-extglob/-/is-extglob-2.1.1.tgz",
@@ -4583,17 +4490,6 @@
         "node": ">=0.10.0"
       }
     },
-    "node_modules/is-hexadecimal": {
-      "version": "2.0.1",
-      "resolved": "https://registry.npmjs.org/is-hexadecimal/-/is-hexadecimal-2.0.1.tgz",
-      "integrity": "sha512-DgZQp241c8oO6cA1SbTEWiXeoxV42vlcJxgH+B3hi1AiqqKruZR3ZGF8In3fj4+/y/7rHvlOZLZtgJ/4ttYGZg==",
-      "dev": true,
-      "license": "MIT",
-      "funding": {
-        "type": "github",
-        "url": "https://github.com/sponsors/wooorm"
-      }
-    },
     "node_modules/is-interactive": {
       "version": "1.0.0",
       "resolved": "https://registry.npmjs.org/is-interactive/-/is-interactive-1.0.0.tgz",
@@ -4912,9 +4808,9 @@
       }
     },
     "node_modules/jest-config/node_modules/glob": {
-      "version": "10.5.0",
-      "resolved": "https://registry.npmjs.org/glob/-/glob-10.5.0.tgz",
-      "integrity": "sha512-DfXN8DfhJ7NH3Oe7cFmu3NCu1wKbkReJ8TorzSAFbSKrlNaQSKfIzqYqVY8zlbs2NLBbWpRiU52GX2PbaBVNkg==",
+      "version": "10.4.5",
+      "resolved": "https://registry.npmjs.org/glob/-/glob-10.4.5.tgz",
+      "integrity": "sha512-7Bv8RF0k6xjo7d4A/PxYLbUCfb6c+Vpd2/mB2yRDlew7Jb5hEXiCD9ibfO7wpk8i4sevK6DFny9h7EYbM3/sHg==",
       "dev": true,
       "license": "ISC",
       "dependencies": {
@@ -5285,9 +5181,9 @@
       }
     },
     "node_modules/jest-runtime/node_modules/glob": {
-      "version": "10.5.0",
-      "resolved": "https://registry.npmjs.org/glob/-/glob-10.5.0.tgz",
-      "integrity": "sha512-DfXN8DfhJ7NH3Oe7cFmu3NCu1wKbkReJ8TorzSAFbSKrlNaQSKfIzqYqVY8zlbs2NLBbWpRiU52GX2PbaBVNkg==",
+      "version": "10.4.5",
+      "resolved": "https://registry.npmjs.org/glob/-/glob-10.4.5.tgz",
+      "integrity": "sha512-7Bv8RF0k6xjo7d4A/PxYLbUCfb6c+Vpd2/mB2yRDlew7Jb5hEXiCD9ibfO7wpk8i4sevK6DFny9h7EYbM3/sHg==",
       "dev": true,
       "license": "ISC",
       "dependencies": {
@@ -5517,9 +5413,9 @@
       "license": "MIT"
     },
     "node_modules/js-yaml": {
-      "version": "4.1.1",
-      "resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-4.1.1.tgz",
-      "integrity": "sha512-qQKT4zQxXl8lLwBtHMWwaTcGfFOZviOJet3Oy/xmGk2gZH677CJM9EvtfdSkgWcATZhj/55JZ0rmy3myCT5lsA==",
+      "version": "4.1.0",
+      "resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-4.1.0.tgz",
+      "integrity": "sha512-wpxZs9NoxZaJESJGIZTyDEaYpl0FKSA+FB9aJiyemKhMwkxQg63h4T1KJgUGHpTqPDNRcmmYLugrRjJlBtWvRA==",
       "license": "MIT",
       "dependencies": {
         "argparse": "^2.0.1"
@@ -5582,13 +5478,6 @@
         "node": ">=6"
       }
     },
-    "node_modules/jsonc-parser": {
-      "version": "3.3.1",
-      "resolved": "https://registry.npmjs.org/jsonc-parser/-/jsonc-parser-3.3.1.tgz",
-      "integrity": "sha512-HUgH65KyejrUFPvHFPbqOY0rsFip3Bo5wb4ngvdi1EpCYWUQDC5V+Y7mZws+DLkr4M//zQJoanu1SP+87Dv1oQ==",
-      "dev": true,
-      "license": "MIT"
-    },
     "node_modules/jsonfile": {
       "version": "6.2.0",
       "resolved": "https://registry.npmjs.org/jsonfile/-/jsonfile-6.2.0.tgz",
@@ -5601,33 +5490,6 @@
         "graceful-fs": "^4.1.6"
       }
     },
-    "node_modules/katex": {
-      "version": "0.16.25",
-      "resolved": "https://registry.npmjs.org/katex/-/katex-0.16.25.tgz",
-      "integrity": "sha512-woHRUZ/iF23GBP1dkDQMh1QBad9dmr8/PAwNA54VrSOVYgI12MAcE14TqnDdQOdzyEonGzMepYnqBMYdsoAr8Q==",
-      "dev": true,
-      "funding": [
-        "https://opencollective.com/katex",
-        "https://github.com/sponsors/katex"
-      ],
-      "license": "MIT",
-      "dependencies": {
-        "commander": "^8.3.0"
-      },
-      "bin": {
-        "katex": "cli.js"
-      }
-    },
-    "node_modules/katex/node_modules/commander": {
-      "version": "8.3.0",
-      "resolved": "https://registry.npmjs.org/commander/-/commander-8.3.0.tgz",
-      "integrity": "sha512-OkTL9umf+He2DZkUq8f8J9of7yL6RJKI24dVITBmNfZBmri9zYZQrKkuXiKhyfPSu8tUhnVBB1iKXevvnlR4Ww==",
-      "dev": true,
-      "license": "MIT",
-      "engines": {
-        "node": ">= 12"
-      }
-    },
     "node_modules/keyv": {
       "version": "4.5.4",
       "resolved": "https://registry.npmjs.org/keyv/-/keyv-4.5.4.tgz",
@@ -5682,16 +5544,6 @@
       "dev": true,
       "license": "MIT"
     },
-    "node_modules/linkify-it": {
-      "version": "5.0.0",
-      "resolved": "https://registry.npmjs.org/linkify-it/-/linkify-it-5.0.0.tgz",
-      "integrity": "sha512-5aHCbzQRADcdP+ATqnDuhhJ/MRIqDkZX5pyjFHRRysS8vZ5AbqGEoFIb6pYHPZ+L/OC2Lc+xT8uHVVR5CAK/wQ==",
-      "dev": true,
-      "license": "MIT",
-      "dependencies": {
-        "uc.micro": "^2.0.0"
-      }
-    },
     "node_modules/lint-staged": {
       "version": "16.1.5",
       "resolved": "https://registry.npmjs.org/lint-staged/-/lint-staged-16.1.5.tgz",
@@ -6136,132 +5988,6 @@
         "tmpl": "1.0.5"
       }
     },
-    "node_modules/markdown-it": {
-      "version": "14.1.0",
-      "resolved": "https://registry.npmjs.org/markdown-it/-/markdown-it-14.1.0.tgz",
-      "integrity": "sha512-a54IwgWPaeBCAAsv13YgmALOF1elABB08FxO9i+r4VFk5Vl4pKokRPeX8u5TCgSsPi6ec1otfLjdOpVcgbpshg==",
-      "dev": true,
-      "license": "MIT",
-      "dependencies": {
-        "argparse": "^2.0.1",
-        "entities": "^4.4.0",
-        "linkify-it": "^5.0.0",
-        "mdurl": "^2.0.0",
-        "punycode.js": "^2.3.1",
-        "uc.micro": "^2.1.0"
-      },
-      "bin": {
-        "markdown-it": "bin/markdown-it.mjs"
-      }
-    },
-    "node_modules/markdownlint": {
-      "version": "0.39.0",
-      "resolved": "https://registry.npmjs.org/markdownlint/-/markdownlint-0.39.0.tgz",
-      "integrity": "sha512-Xt/oY7bAiHwukL1iru2np5LIkhwD19Y7frlsiDILK62v3jucXCD6JXlZlwMG12HZOR+roHIVuJZrfCkOhp6k3g==",
-      "dev": true,
-      "license": "MIT",
-      "dependencies": {
-        "micromark": "4.0.2",
-        "micromark-core-commonmark": "2.0.3",
-        "micromark-extension-directive": "4.0.0",
-        "micromark-extension-gfm-autolink-literal": "2.1.0",
-        "micromark-extension-gfm-footnote": "2.1.0",
-        "micromark-extension-gfm-table": "2.1.1",
-        "micromark-extension-math": "3.1.0",
-        "micromark-util-types": "2.0.2"
-      },
-      "engines": {
-        "node": ">=20"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/DavidAnson"
-      }
-    },
-    "node_modules/markdownlint-cli2": {
-      "version": "0.19.1",
-      "resolved": "https://registry.npmjs.org/markdownlint-cli2/-/markdownlint-cli2-0.19.1.tgz",
-      "integrity": "sha512-p3JTemJJbkiMjXEMiFwgm0v6ym5g8K+b2oDny+6xdl300tUKySxvilJQLSea48C6OaYNmO30kH9KxpiAg5bWJw==",
-      "dev": true,
-      "license": "MIT",
-      "dependencies": {
-        "globby": "15.0.0",
-        "js-yaml": "4.1.1",
-        "jsonc-parser": "3.3.1",
-        "markdown-it": "14.1.0",
-        "markdownlint": "0.39.0",
-        "markdownlint-cli2-formatter-default": "0.0.6",
-        "micromatch": "4.0.8"
-      },
-      "bin": {
-        "markdownlint-cli2": "markdownlint-cli2-bin.mjs"
-      },
-      "engines": {
-        "node": ">=20"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/DavidAnson"
-      }
-    },
-    "node_modules/markdownlint-cli2-formatter-default": {
-      "version": "0.0.6",
-      "resolved": "https://registry.npmjs.org/markdownlint-cli2-formatter-default/-/markdownlint-cli2-formatter-default-0.0.6.tgz",
-      "integrity": "sha512-VVDGKsq9sgzu378swJ0fcHfSicUnMxnL8gnLm/Q4J/xsNJ4e5bA6lvAz7PCzIl0/No0lHyaWdqVD2jotxOSFMQ==",
-      "dev": true,
-      "license": "MIT",
-      "funding": {
-        "url": "https://github.com/sponsors/DavidAnson"
-      },
-      "peerDependencies": {
-        "markdownlint-cli2": ">=0.0.4"
-      }
-    },
-    "node_modules/markdownlint-cli2/node_modules/globby": {
-      "version": "15.0.0",
-      "resolved": "https://registry.npmjs.org/globby/-/globby-15.0.0.tgz",
-      "integrity": "sha512-oB4vkQGqlMl682wL1IlWd02tXCbquGWM4voPEI85QmNKCaw8zGTm1f1rubFgkg3Eli2PtKlFgrnmUqasbQWlkw==",
-      "dev": true,
-      "license": "MIT",
-      "dependencies": {
-        "@sindresorhus/merge-streams": "^4.0.0",
-        "fast-glob": "^3.3.3",
-        "ignore": "^7.0.5",
-        "path-type": "^6.0.0",
-        "slash": "^5.1.0",
-        "unicorn-magic": "^0.3.0"
-      },
-      "engines": {
-        "node": ">=20"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/sindresorhus"
-      }
-    },
-    "node_modules/markdownlint-cli2/node_modules/path-type": {
-      "version": "6.0.0",
-      "resolved": "https://registry.npmjs.org/path-type/-/path-type-6.0.0.tgz",
-      "integrity": "sha512-Vj7sf++t5pBD637NSfkxpHSMfWaeig5+DKWLhcqIYx6mWQz5hdJTGDVMQiJcw1ZYkhs7AazKDGpRVji1LJCZUQ==",
-      "dev": true,
-      "license": "MIT",
-      "engines": {
-        "node": ">=18"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/sindresorhus"
-      }
-    },
-    "node_modules/markdownlint-cli2/node_modules/slash": {
-      "version": "5.1.0",
-      "resolved": "https://registry.npmjs.org/slash/-/slash-5.1.0.tgz",
-      "integrity": "sha512-ZA6oR3T/pEyuqwMgAKT0/hAv8oAXckzbkmR0UkUosQ+Mc4RxGoJkRmwHgHufaenlyAgE1Mxgpdcrf75y6XcnDg==",
-      "dev": true,
-      "license": "MIT",
-      "engines": {
-        "node": ">=14.16"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/sindresorhus"
-      }
-    },
     "node_modules/mdast-util-from-markdown": {
       "version": "2.0.2",
       "resolved": "https://registry.npmjs.org/mdast-util-from-markdown/-/mdast-util-from-markdown-2.0.2.tgz",
@@ -6334,13 +6060,6 @@
         "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/mdurl": {
-      "version": "2.0.0",
-      "resolved": "https://registry.npmjs.org/mdurl/-/mdurl-2.0.0.tgz",
-      "integrity": "sha512-Lf+9+2r+Tdp5wXDXC4PcIBjTDtq4UKjCPMQhKIuzpJNW0b96kVqSwW0bT7FhRSfmAiFYgP+SCRvdrDozfh0U5w==",
-      "dev": true,
-      "license": "MIT"
-    },
     "node_modules/merge-stream": {
       "version": "2.0.0",
       "resolved": "https://registry.npmjs.org/merge-stream/-/merge-stream-2.0.0.tgz",
@@ -6427,102 +6146,6 @@
         "micromark-util-types": "^2.0.0"
       }
     },
-    "node_modules/micromark-extension-directive": {
-      "version": "4.0.0",
-      "resolved": "https://registry.npmjs.org/micromark-extension-directive/-/micromark-extension-directive-4.0.0.tgz",
-      "integrity": "sha512-/C2nqVmXXmiseSSuCdItCMho7ybwwop6RrrRPk0KbOHW21JKoCldC+8rFOaundDoRBUWBnJJcxeA/Kvi34WQXg==",
-      "dev": true,
-      "license": "MIT",
-      "dependencies": {
-        "devlop": "^1.0.0",
-        "micromark-factory-space": "^2.0.0",
-        "micromark-factory-whitespace": "^2.0.0",
-        "micromark-util-character": "^2.0.0",
-        "micromark-util-symbol": "^2.0.0",
-        "micromark-util-types": "^2.0.0",
-        "parse-entities": "^4.0.0"
-      },
-      "funding": {
-        "type": "opencollective",
-        "url": "https://opencollective.com/unified"
-      }
-    },
-    "node_modules/micromark-extension-gfm-autolink-literal": {
-      "version": "2.1.0",
-      "resolved": "https://registry.npmjs.org/micromark-extension-gfm-autolink-literal/-/micromark-extension-gfm-autolink-literal-2.1.0.tgz",
-      "integrity": "sha512-oOg7knzhicgQ3t4QCjCWgTmfNhvQbDDnJeVu9v81r7NltNCVmhPy1fJRX27pISafdjL+SVc4d3l48Gb6pbRypw==",
-      "dev": true,
-      "license": "MIT",
-      "dependencies": {
-        "micromark-util-character": "^2.0.0",
-        "micromark-util-sanitize-uri": "^2.0.0",
-        "micromark-util-symbol": "^2.0.0",
-        "micromark-util-types": "^2.0.0"
-      },
-      "funding": {
-        "type": "opencollective",
-        "url": "https://opencollective.com/unified"
-      }
-    },
-    "node_modules/micromark-extension-gfm-footnote": {
-      "version": "2.1.0",
-      "resolved": "https://registry.npmjs.org/micromark-extension-gfm-footnote/-/micromark-extension-gfm-footnote-2.1.0.tgz",
-      "integrity": "sha512-/yPhxI1ntnDNsiHtzLKYnE3vf9JZ6cAisqVDauhp4CEHxlb4uoOTxOCJ+9s51bIB8U1N1FJ1RXOKTIlD5B/gqw==",
-      "dev": true,
-      "license": "MIT",
-      "dependencies": {
-        "devlop": "^1.0.0",
-        "micromark-core-commonmark": "^2.0.0",
-        "micromark-factory-space": "^2.0.0",
-        "micromark-util-character": "^2.0.0",
-        "micromark-util-normalize-identifier": "^2.0.0",
-        "micromark-util-sanitize-uri": "^2.0.0",
-        "micromark-util-symbol": "^2.0.0",
-        "micromark-util-types": "^2.0.0"
-      },
-      "funding": {
-        "type": "opencollective",
-        "url": "https://opencollective.com/unified"
-      }
-    },
-    "node_modules/micromark-extension-gfm-table": {
-      "version": "2.1.1",
-      "resolved": "https://registry.npmjs.org/micromark-extension-gfm-table/-/micromark-extension-gfm-table-2.1.1.tgz",
-      "integrity": "sha512-t2OU/dXXioARrC6yWfJ4hqB7rct14e8f7m0cbI5hUmDyyIlwv5vEtooptH8INkbLzOatzKuVbQmAYcbWoyz6Dg==",
-      "dev": true,
-      "license": "MIT",
-      "dependencies": {
-        "devlop": "^1.0.0",
-        "micromark-factory-space": "^2.0.0",
-        "micromark-util-character": "^2.0.0",
-        "micromark-util-symbol": "^2.0.0",
-        "micromark-util-types": "^2.0.0"
-      },
-      "funding": {
-        "type": "opencollective",
-        "url": "https://opencollective.com/unified"
-      }
-    },
-    "node_modules/micromark-extension-math": {
-      "version": "3.1.0",
-      "resolved": "https://registry.npmjs.org/micromark-extension-math/-/micromark-extension-math-3.1.0.tgz",
-      "integrity": "sha512-lvEqd+fHjATVs+2v/8kg9i5Q0AP2k85H0WUOwpIVvUML8BapsMvh1XAogmQjOCsLpoKRCVQqEkQBB3NhVBcsOg==",
-      "dev": true,
-      "license": "MIT",
-      "dependencies": {
-        "@types/katex": "^0.16.0",
-        "devlop": "^1.0.0",
-        "katex": "^0.16.0",
-        "micromark-factory-space": "^2.0.0",
-        "micromark-util-character": "^2.0.0",
-        "micromark-util-symbol": "^2.0.0",
-        "micromark-util-types": "^2.0.0"
-      },
-      "funding": {
-        "type": "opencollective",
-        "url": "https://opencollective.com/unified"
-      }
-    },
     "node_modules/micromark-factory-destination": {
       "version": "2.0.1",
       "resolved": "https://registry.npmjs.org/micromark-factory-destination/-/micromark-factory-destination-2.0.1.tgz",
@@ -7245,33 +6868,6 @@
         "node": ">=6"
       }
     },
-    "node_modules/parse-entities": {
-      "version": "4.0.2",
-      "resolved": "https://registry.npmjs.org/parse-entities/-/parse-entities-4.0.2.tgz",
-      "integrity": "sha512-GG2AQYWoLgL877gQIKeRPGO1xF9+eG1ujIb5soS5gPvLQ1y2o8FL90w2QWNdf9I361Mpp7726c+lj3U0qK1uGw==",
-      "dev": true,
-      "license": "MIT",
-      "dependencies": {
-        "@types/unist": "^2.0.0",
-        "character-entities-legacy": "^3.0.0",
-        "character-reference-invalid": "^2.0.0",
-        "decode-named-character-reference": "^1.0.0",
-        "is-alphanumerical": "^2.0.0",
-        "is-decimal": "^2.0.0",
-        "is-hexadecimal": "^2.0.0"
-      },
-      "funding": {
-        "type": "github",
-        "url": "https://github.com/sponsors/wooorm"
-      }
-    },
-    "node_modules/parse-entities/node_modules/@types/unist": {
-      "version": "2.0.11",
-      "resolved": "https://registry.npmjs.org/@types/unist/-/unist-2.0.11.tgz",
-      "integrity": "sha512-CmBKiL6NNo/OqgmMn95Fk9Whlp2mtvIv+KNpQKN2F4SjvrEesubTRWGYSg+BnWZOnlCaSTU1sMpsBOzgbYhnsA==",
-      "dev": true,
-      "license": "MIT"
-    },
     "node_modules/parse-json": {
       "version": "5.2.0",
       "resolved": "https://registry.npmjs.org/parse-json/-/parse-json-5.2.0.tgz",
@@ -7560,16 +7156,6 @@
         "node": ">=6"
       }
     },
-    "node_modules/punycode.js": {
-      "version": "2.3.1",
-      "resolved": "https://registry.npmjs.org/punycode.js/-/punycode.js-2.3.1.tgz",
-      "integrity": "sha512-uxFIHU0YlHYhDQtV4R9J6a52SLx28BCjT+4ieh7IGbgwVJWO+km431c4yRlREUAsAmt/uMjQUyQHNEPf0M39CA==",
-      "dev": true,
-      "license": "MIT",
-      "engines": {
-        "node": ">=6"
-      }
-    },
     "node_modules/pure-rand": {
       "version": "7.0.1",
       "resolved": "https://registry.npmjs.org/pure-rand/-/pure-rand-7.0.1.tgz",
@@ -8454,13 +8040,6 @@
         "node": ">=14.17"
       }
     },
-    "node_modules/uc.micro": {
-      "version": "2.1.0",
-      "resolved": "https://registry.npmjs.org/uc.micro/-/uc.micro-2.1.0.tgz",
-      "integrity": "sha512-ARDJmphmdvUk6Glw7y9DQ2bFkKBHwQHLi2lsaH6PPmz/Ka9sFOBsBluozhDltWmnv9u/cF6Rt87znRTPV+yp/A==",
-      "dev": true,
-      "license": "MIT"
-    },
     "node_modules/undici-types": {
       "version": "7.10.0",
       "resolved": "https://registry.npmjs.org/undici-types/-/undici-types-7.10.0.tgz",
@@ -8468,19 +8047,6 @@
       "devOptional": true,
       "license": "MIT"
     },
-    "node_modules/unicorn-magic": {
-      "version": "0.3.0",
-      "resolved": "https://registry.npmjs.org/unicorn-magic/-/unicorn-magic-0.3.0.tgz",
-      "integrity": "sha512-+QBBXBCvifc56fsbuxZQ6Sic3wqqc3WWaqxs58gvJrcOuN83HGTCwz3oS5phzU9LthRNE9VrJCFCLUgHeeFnfA==",
-      "dev": true,
-      "license": "MIT",
-      "engines": {
-        "node": ">=18"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/sindresorhus"
-      }
-    },
     "node_modules/unified": {
       "version": "11.0.5",
       "resolved": "https://registry.npmjs.org/unified/-/unified-11.0.5.tgz",

package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "6.0.0-alpha.14",
+  "version": "6.0.0-alpha.12",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",
@@ -24,6 +24,7 @@
     "bmad-method": "tools/bmad-npx-wrapper.js"
   },
   "scripts": {
+    "bmad:agent-install": "node tools/cli/bmad-cli.js agent-install",
     "bmad:install": "node tools/cli/bmad-cli.js install",
     "bmad:status": "node tools/cli/bmad-cli.js status",
     "bundle": "node tools/cli/bundlers/bundle-web.js all",
@@ -33,14 +34,13 @@
     "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": "npm run test:schemas && npm run test:install && npm run validate:bundles && npm run validate:schemas && npm run lint && npm run format:check",
     "test:coverage": "c8 --reporter=text --reporter=html npm run test:schemas",
     "test:install": "node test/test-installation-components.js",
     "test:schemas": "node test/test-agent-schema.js",
@@ -56,11 +56,7 @@
       "eslint --fix",
       "npm run format:fix"
     ],
-    "*.json": [
-      "npm run format:fix"
-    ],
-    "*.md": [
-      "markdownlint-cli2",
+    "*.{json,md}": [
       "npm run format:fix"
     ]
   },
@@ -94,7 +90,6 @@
     "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",

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

@@ -23,11 +23,7 @@ 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}"
-
+  # This is the folder where all generated AI Output documents from workflows will default be sa
 output_folder:
   prompt: "Where should AI Generated Artifacts be saved across all modules?"
   default: "docs"

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

@@ -32,7 +32,7 @@ agent:
       description: "List Workflows"
 
     - trigger: "party-mode"
-      exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
+      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
       description: "Group chat with all agents"
 
   # Empty prompts section (no custom prompts for this agent)

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

@@ -105,7 +105,7 @@
     <item cmd="*help">Show numbered command list</item>
     <item cmd="*list-agents">List all available agents with their capabilities</item>
     <item cmd="*agents [agent-name]">Transform into a specific agent</item>
-    <item cmd="*party-mode" exec="{bmad_folder}/core/workflows/party-mode/workflow.md">Enter group chat with all agents
+    <item cmd="*party-mode" workflow="{bmad_folder}/core/workflows/party-mode/workflow.yaml">Enter group chat with all agents
       simultaneously</item>
     <item cmd="*advanced-elicitation" task="{bmad_folder}/core/tasks/advanced-elicitation.xml">Push agent to perform advanced elicitation</item>
     <item cmd="*exit">Exit current session</item>

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

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

src/core/tasks/adv-elicit-methods.csv

@@ -0,0 +1,39 @@
+category,method_name,description,output_pattern
+advanced,Tree of Thoughts,Explore multiple reasoning paths simultaneously then evaluate and select the best - perfect for complex problems with multiple valid approaches where finding the optimal path matters,paths → evaluation → selection
+advanced,Graph of Thoughts,Model reasoning as an interconnected network of ideas to reveal hidden relationships - ideal for systems thinking and discovering emergent patterns in complex multi-factor situations,nodes → connections → patterns
+advanced,Thread of Thought,Maintain coherent reasoning across long contexts by weaving a continuous narrative thread - essential for RAG systems and maintaining consistency in lengthy analyses,context → thread → synthesis
+advanced,Self-Consistency Validation,Generate multiple independent approaches then compare for consistency - crucial for high-stakes decisions where verification and consensus building matter,approaches → comparison → consensus
+advanced,Meta-Prompting Analysis,Step back to analyze the approach structure and methodology itself - valuable for optimizing prompts and improving problem-solving strategies,current → analysis → optimization
+advanced,Reasoning via Planning,Build a reasoning tree guided by world models and goal states - excellent for strategic planning and sequential decision-making tasks,model → planning → strategy
+collaboration,Stakeholder Round Table,Convene multiple personas to contribute diverse perspectives - essential for requirements gathering and finding balanced solutions across competing interests,perspectives → synthesis → alignment
+collaboration,Expert Panel Review,Assemble domain experts for deep specialized analysis - ideal when technical depth and peer review quality are needed,expert views → consensus → recommendations
+competitive,Red Team vs Blue Team,Adversarial attack-defend analysis to find vulnerabilities - critical for security testing and building robust solutions through adversarial thinking,defense → attack → hardening
+core,Expand or Contract for Audience,Dynamically adjust detail level and technical depth for target audience - essential when content needs to match specific reader capabilities,audience → adjustments → refined content
+core,Critique and Refine,Systematic review to identify strengths and weaknesses then improve - standard quality check for drafts needing polish and enhancement,strengths/weaknesses → improvements → refined version
+core,Explain Reasoning,Walk through step-by-step thinking to show how conclusions were reached - crucial for transparency and helping others understand complex logic,steps → logic → conclusion
+core,First Principles Analysis,Strip away assumptions to rebuild from fundamental truths - breakthrough technique for innovation and solving seemingly impossible problems,assumptions → truths → new approach
+core,5 Whys Deep Dive,Repeatedly ask why to drill down to root causes - simple but powerful for understanding failures and fixing problems at their source,why chain → root cause → solution
+core,Socratic Questioning,Use targeted questions to reveal hidden assumptions and guide discovery - excellent for teaching and helping others reach insights themselves,questions → revelations → understanding
+creative,Reverse Engineering,Work backwards from desired outcome to find implementation path - powerful for goal achievement and understanding how to reach specific endpoints,end state → steps backward → path forward
+creative,What If Scenarios,Explore alternative realities to understand possibilities and implications - valuable for contingency planning and creative exploration,scenarios → implications → insights
+creative,SCAMPER Method,Apply seven creativity lenses (Substitute/Combine/Adapt/Modify/Put/Eliminate/Reverse) - systematic ideation for product innovation and improvement,S→C→A→M→P→E→R
+learning,Feynman Technique,Explain complex concepts simply as if teaching a child - the ultimate test of true understanding and excellent for knowledge transfer,complex → simple → gaps → mastery
+learning,Active Recall Testing,Test understanding without references to verify true knowledge - essential for identifying gaps and reinforcing mastery,test → gaps → reinforcement
+narrative,Unreliable Narrator Mode,Question assumptions and biases by adopting skeptical perspective - crucial for detecting hidden agendas and finding balanced truth,perspective → biases → balanced view
+optimization,Speedrun Optimization,Find the fastest most efficient path by eliminating waste - perfect when time pressure demands maximum efficiency,current → bottlenecks → optimized
+optimization,New Game Plus,Revisit challenges with enhanced capabilities from prior experience - excellent for iterative improvement and mastery building,initial → enhanced → improved
+optimization,Roguelike Permadeath,Treat decisions as irreversible to force careful high-stakes analysis - ideal for critical decisions with no second chances,decision → consequences → execution
+philosophical,Occam's Razor Application,Find the simplest sufficient explanation by eliminating unnecessary complexity - essential for debugging and theory selection,options → simplification → selection
+philosophical,Trolley Problem Variations,Explore ethical trade-offs through moral dilemmas - valuable for understanding values and making difficult ethical decisions,dilemma → analysis → decision
+quantum,Observer Effect Consideration,Analyze how the act of measurement changes what's being measured - important for understanding metrics impact and self-aware systems,unmeasured → observation → impact
+retrospective,Hindsight Reflection,Imagine looking back from the future to gain perspective - powerful for project reviews and extracting wisdom from experience,future view → insights → application
+retrospective,Lessons Learned Extraction,Systematically identify key takeaways and actionable improvements - essential for knowledge transfer and continuous improvement,experience → lessons → actions
+risk,Identify Potential Risks,Brainstorm what could go wrong across all categories - fundamental for project planning and deployment preparation,categories → risks → mitigations
+risk,Challenge from Critical Perspective,Play devil's advocate to stress-test ideas and find weaknesses - essential for overcoming groupthink and building robust solutions,assumptions → challenges → strengthening
+risk,Failure Mode Analysis,Systematically explore how each component could fail - critical for reliability engineering and safety-critical systems,components → failures → prevention
+risk,Pre-mortem Analysis,Imagine future failure then work backwards to prevent it - powerful technique for risk mitigation before major launches,failure scenario → causes → prevention
+scientific,Peer Review Simulation,Apply rigorous academic evaluation standards - ensures quality through methodology review and critical assessment,methodology → analysis → recommendations
+scientific,Reproducibility Check,Verify results can be replicated independently - fundamental for reliability and scientific validity,method → replication → validation
+structural,Dependency Mapping,Visualize interconnections to understand requirements and impacts - essential for complex systems and integration planning,components → dependencies → impacts
+structural,Information Architecture Review,Optimize organization and hierarchy for better user experience - crucial for fixing navigation and findability problems,current → pain points → restructure
+structural,Skeleton of Thought,Create structure first then expand branches in parallel - efficient for generating long content quickly with good organization,skeleton → branches → integration

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

@@ -1,51 +1,21 @@
-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
+category,method_name,description,output_pattern
+core,Five Whys,Drill down to root causes by asking 'why' iteratively. Each answer becomes the basis for the next question. Particularly effective for problem analysis and understanding system failures.,problem → why1 → why2 → why3 → why4 → why5 → root cause
+core,First Principles,Break down complex problems into fundamental truths and rebuild from there. Question assumptions and reconstruct understanding from basic principles.,assumptions → deconstruction → fundamentals → reconstruction → solution
+structural,SWOT Analysis,Evaluate internal and external factors through Strengths Weaknesses Opportunities and Threats. Provides balanced strategic perspective.,strengths → weaknesses → opportunities → threats → strategic insights
+structural,Mind Mapping,Create visual representations of interconnected concepts branching from central idea. Reveals relationships and patterns not immediately obvious.,central concept → primary branches → secondary branches → connections → insights
+risk,Pre-mortem Analysis,Imagine project has failed and work backwards to identify potential failure points. Proactive risk identification through hypothetical failure scenarios.,future failure → contributing factors → warning signs → preventive measures
+risk,Risk Matrix,Evaluate risks by probability and impact to prioritize mitigation efforts. Visual framework for systematic risk assessment.,risk identification → probability assessment → impact analysis → prioritization → mitigation
+creative,SCAMPER,Systematic creative thinking through Substitute Combine Adapt Modify Put to other uses Eliminate Reverse. Generates innovative alternatives.,substitute → combine → adapt → modify → other uses → eliminate → reverse
+creative,Six Thinking Hats,Explore topic from six perspectives: facts (white) emotions (red) caution (black) optimism (yellow) creativity (green) process (blue).,facts → emotions → risks → benefits → alternatives → synthesis
+analytical,Root Cause Analysis,Systematic investigation to identify fundamental causes rather than symptoms. Uses various techniques to drill down to core issues.,symptoms → immediate causes → intermediate causes → root causes → solutions
+analytical,Fishbone Diagram,Visual cause-and-effect analysis organizing potential causes into categories. Also known as Ishikawa diagram for systematic problem analysis.,problem statement → major categories → potential causes → sub-causes → prioritization
+strategic,PESTLE Analysis,Examine Political Economic Social Technological Legal Environmental factors. Comprehensive external environment assessment.,political → economic → social → technological → legal → environmental → implications
+strategic,Value Chain Analysis,Examine activities that create value from raw materials to end customer. Identifies competitive advantages and improvement opportunities.,primary activities → support activities → linkages → value creation → optimization
+process,Journey Mapping,Visualize end-to-end experience identifying touchpoints pain points and opportunities. Understanding through customer or user perspective.,stages → touchpoints → actions → emotions → pain points → opportunities
+process,Service Blueprint,Map service delivery showing frontstage backstage and support processes. Reveals service complexity and improvement areas.,customer actions → frontstage → backstage → support processes → improvement areas
+stakeholder,Stakeholder Mapping,Identify and analyze stakeholders by interest and influence. Strategic approach to stakeholder engagement.,identification → interest analysis → influence assessment → engagement strategy
+stakeholder,Empathy Map,Understand stakeholder perspectives through what they think feel see say do. Deep understanding of user needs and motivations.,thinks → feels → sees → says → does → pains → gains
+decision,Decision Matrix,Evaluate options against weighted criteria for objective decision making. Systematic comparison of alternatives.,criteria definition → weighting → scoring → calculation → ranking → selection
+decision,Cost-Benefit Analysis,Compare costs against benefits to evaluate decision viability. Quantitative approach to decision validation.,cost identification → benefit identification → quantification → comparison → recommendation
+validation,Devil's Advocate,Challenge assumptions and proposals by arguing opposing viewpoint. Stress-testing through deliberate opposition.,proposal → counter-arguments → weaknesses → blind spots → strengthened proposal
+validation,Red Team Analysis,Simulate adversarial perspective to identify vulnerabilities. Security and robustness through adversarial thinking.,current approach → adversarial view → attack vectors → vulnerabilities → countermeasures

src/core/tasks/advanced-elicitation.xml

@@ -44,8 +44,8 @@
     <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:
+        **Advanced Elicitation Options**
+        Choose a number (1-5), r to shuffle, or x to proceed:
 
         1. [Method Name]
         2. [Method Name]
@@ -53,7 +53,6 @@
         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>
 
@@ -69,9 +68,7 @@
           <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>
+          <i>Select 5 different methods from advanced-elicitation-methods.csv, present new list with same prompt format</i>
         </case>
         <case n="x">
           <i>Complete elicitation and proceed</i>
@@ -79,11 +76,6 @@
           <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>
@@ -98,13 +90,11 @@
       <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>Be concise: Focus on actionable insights</i>
+      <i>Stay relevant: Tie elicitation to specific content being analyzed (the current section from create-doc)</i>
+      <i>Identify personas: For multi-persona methods, clearly identify viewpoints</i>
+      <i>Critical loop behavior: Always re-offer the 1-5,r,x choices after each method execution</i>
+      <i>Continue until user selects 'x' to proceed with enhanced content</i>
       <i>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>

src/core/tasks/workflow.xml

@@ -6,14 +6,14 @@
     <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>
+    <mandate>NEVER delegate a step - YOU are responsible for every steps execution</mandate>
   </llm>
 
   <WORKFLOW-RULES critical="true">
     <rule n="1">Steps execute in exact numerical order (1, 2, 3...)</rule>
     <rule n="2">Optional steps: Ask user unless #yolo mode active</rule>
-    <rule n="3">Template-output tags: Save content, discuss with the user the section completed, and NEVER proceed until the users indicates
-      to proceed (unless YOLO mode has been activated)</rule>
+    <rule n="3">Template-output tags: Save content → Show user → Get approval before continuing</rule>
+    <rule n="4">User must approve each major section before continuing UNLESS #yolo mode active</rule>
   </WORKFLOW-RULES>
 
   <flow>
@@ -43,7 +43,7 @@
       </substep>
     </step>
 
-    <step n="2" title="Process Each Instruction Step in Order">
+    <step n="2" title="Process Each Instruction Step">
       <iterate>For each step in instructions:</iterate>
 
       <substep n="2a" title="Handle Step Attributes">
@@ -60,7 +60,7 @@
           <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-workflow xml tag → Execute another workflow with given inputs</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>
@@ -71,6 +71,7 @@
         <if tag="template-output">
           <mandate>Generate content for this section</mandate>
           <mandate>Save to file (Write first time, Edit subsequent)</mandate>
+          <action>Show checkpoint separator: ━━━━━━━━━━━━━━━━━━━━━━━</action>
           <action>Display generated content</action>
           <ask> [a] Advanced Elicitation, [c] Continue, [p] Party-Mode, [y] YOLO the rest of this document only. WAIT for response. <if
               response="a">
@@ -98,14 +99,16 @@
     </step>
 
     <step n="3" title="Completion">
-      <check>Confirm document saved to output path</check>
+      <check>If checklist exists → Run validation</check>
+      <check>If template: false → Confirm actions completed</check>
+      <check>Else → Confirm document saved to output path</check>
       <action>Report workflow completion</action>
     </step>
   </flow>
 
   <execution-modes>
-    <mode name="normal">Full user interaction 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
+    <mode name="normal">Full user interaction at all decision points</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>
 
@@ -121,7 +124,7 @@
       <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>ask - Get user input (wait for response)</tag>
       <tag>goto - Jump to another step</tag>
       <tag>invoke-workflow - Call another workflow</tag>
       <tag>invoke-task - Call a task</tag>
@@ -134,6 +137,35 @@
     </output>
   </supported-tags>
 
+  <conditional-execution-patterns desc="When to use each pattern">
+    <pattern type="single-action">
+      <use-case>One action with a condition</use-case>
+      <syntax>&lt;action if="condition"&gt;Do something&lt;/action&gt;</syntax>
+      <example>&lt;action if="file exists"&gt;Load the file&lt;/action&gt;</example>
+      <rationale>Cleaner and more concise for single items</rationale>
+    </pattern>
+
+    <pattern type="multi-action-block">
+      <use-case>Multiple actions/tags under same condition</use-case>
+      <syntax>&lt;check if="condition"&gt;
+        &lt;action&gt;First action&lt;/action&gt;
+        &lt;action&gt;Second action&lt;/action&gt;
+        &lt;/check&gt;</syntax>
+      <example>&lt;check if="validation fails"&gt;
+        &lt;action&gt;Log error&lt;/action&gt;
+        &lt;goto step="1"&gt;Retry&lt;/goto&gt;
+        &lt;/check&gt;</example>
+      <rationale>Explicit scope boundaries prevent ambiguity</rationale>
+    </pattern>
+
+    <pattern type="nested-conditions">
+      <use-case>Else/alternative branches</use-case>
+      <syntax>&lt;check if="condition A"&gt;...&lt;/check&gt;
+        &lt;check if="else"&gt;...&lt;/check&gt;</syntax>
+      <rationale>Clear branching logic with explicit blocks</rationale>
+    </pattern>
+  </conditional-execution-patterns>
+
   <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>
@@ -149,8 +181,17 @@
         <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">
+          <substep n="2a" title="Try Whole Document First">
+            <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>
+          </substep>
+
+          <substep n="2b" title="Try Sharded Document if Whole Not Found">
+            <check if="no whole matches AND sharded pattern exists">
               <action>Determine load_strategy from pattern config (defaults to FULL_LOAD if not specified)</action>
 
               <strategy name="FULL_LOAD">
@@ -183,23 +224,11 @@
                 <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">
+            <check if="no matches for whole OR sharded">
               <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>
@@ -209,8 +238,8 @@
         <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 {prd_content} from 1 file: PRD.md
+            ✓ Loaded {architecture_content} from 5 sharded files: architecture/index.md, architecture/system-design.md, ...
             ✓ Loaded {epics_content} from selective load: epics/epic-3.md
             ○ No ux_design files found
           </example>
@@ -218,18 +247,24 @@
         </step>
       </flow>
 
+      <usage-in-instructions>
+        <example desc="Typical usage in workflow instructions.md">
+          &lt;step n="0" goal="Discover and load project context"&gt;
+          &lt;invoke-protocol name="discover_inputs" /&gt;
+          &lt;/step&gt;
+
+          &lt;step n="1" goal="Analyze requirements"&gt;
+          &lt;action&gt;Review {prd_content} for functional requirements&lt;/action&gt;
+          &lt;action&gt;Cross-reference with {architecture_content} for technical constraints&lt;/action&gt;
+          &lt;/step&gt;
+        </example>
+      </usage-in-instructions>
     </protocol>
   </protocols>
 
   <llm final="true">
-    <critical-rules>
-      • This is the complete workflow execution engine
-      • You MUST Follow instructions exactly as written
-      • The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml
-      • You MUST have already loaded and processed: {installed_path}/workflow.yaml
-      • This workflow uses INTENT-DRIVEN PLANNING - adapt organically to product type and context
-      • YOU ARE FACILITATING A CONVERSATION With a user to produce a final document step by step. The whole process is meant to be
-      collaborative helping the user flesh out their ideas. Do not rush or optimize and skip any section.
-    </critical-rules>
+    <mandate>This is the complete workflow execution engine</mandate>
+    <mandate>You MUST Follow instructions exactly as written and maintain conversation context between steps</mandate>
+    <mandate>If confused, re-read this task, the workflow yaml, and any yaml indicated files</mandate>
   </llm>
-</task> 
+</task>

src/core/workflows/brainstorming/README.md

@@ -0,0 +1,261 @@
+---
+last-redoc-date: 2025-09-28
+---
+
+# Brainstorming Session Workflow
+
+## Overview
+
+The brainstorming workflow facilitates interactive brainstorming sessions using diverse creative techniques. This workflow acts as an AI facilitator guiding users through various ideation methods to generate and refine creative solutions in a structured, energetic, and highly interactive manner.
+
+## Key Features
+
+- **36 Creative Techniques**: Comprehensive library spanning collaborative, structured, creative, deep, theatrical, wild, and introspective approaches
+- **Interactive Facilitation**: AI acts as a skilled facilitator using "Yes, and..." methodology
+- **Flexible Approach Selection**: User-guided, AI-recommended, random, or progressive technique flows
+- **Context-Aware Sessions**: Supports domain-specific brainstorming through context document input
+- **Systematic Organization**: Converges ideas into immediate opportunities, future innovations, and moonshots
+- **Action Planning**: Prioritizes top ideas with concrete next steps and timelines
+- **Session Documentation**: Comprehensive structured reports capturing all insights and outcomes
+
+## Usage
+
+### Configuration
+
+The workflow leverages configuration from `{bmad_folder}/core/config.yaml`:
+
+- **output_folder**: Where session results are saved
+- **user_name**: Session participant identification
+
+And the following has a default or can be passed in as an override for custom brainstorming scenarios.
+
+- **brain_techniques**: CSV database of 36 creative techniques, default is `./brain-methods.csv`
+
+## Workflow Structure
+
+### Files Included
+
+```
+brainstorming/
+├── workflow.yaml           # Configuration and metadata
+├── instructions.md         # Step-by-step execution guide
+├── template.md            # Session report structure
+├── brain-methods.csv      # Database of 36 creative techniques
+└── README.md              # This file
+```
+
+## Creative Techniques Library
+
+The workflow includes 36 techniques organized into 7 categories:
+
+### Collaborative Techniques
+
+- **Yes And Building**: Build momentum through positive additions
+- **Brain Writing Round Robin**: Silent idea generation with sequential building
+- **Random Stimulation**: Use random catalysts for unexpected connections
+- **Role Playing**: Generate solutions from multiple stakeholder perspectives
+
+### Structured Approaches
+
+- **SCAMPER Method**: Systematic creativity through seven lenses (Substitute/Combine/Adapt/Modify/Put/Eliminate/Reverse)
+- **Six Thinking Hats**: Explore through six perspectives (facts/emotions/benefits/risks/creativity/process)
+- **Mind Mapping**: Visual branching from central concepts
+- **Resource Constraints**: Innovation through extreme limitations
+
+### Creative Methods
+
+- **What If Scenarios**: Explore radical possibilities by questioning constraints
+- **Analogical Thinking**: Find solutions through domain parallels
+- **Reversal Inversion**: Flip problems upside down for fresh angles
+- **First Principles Thinking**: Strip away assumptions to rebuild from fundamentals
+- **Forced Relationships**: Connect unrelated concepts for innovation
+- **Time Shifting**: Explore solutions across different time periods
+- **Metaphor Mapping**: Use extended metaphors as thinking tools
+
+### Deep Analysis
+
+- **Five Whys**: Drill down through causation layers to root causes
+- **Morphological Analysis**: Systematically explore parameter combinations
+- **Provocation Technique**: Extract useful ideas from absurd starting points
+- **Assumption Reversal**: Challenge and flip core assumptions
+- **Question Storming**: Generate questions before seeking answers
+
+### Theatrical Approaches
+
+- **Time Travel Talk Show**: Interview past/present/future selves
+- **Alien Anthropologist**: Examine through completely foreign eyes
+- **Dream Fusion Laboratory**: Start with impossible solutions, work backwards
+- **Emotion Orchestra**: Let different emotions lead separate sessions
+- **Parallel Universe Cafe**: Explore under alternative reality rules
+
+### Wild Methods
+
+- **Chaos Engineering**: Deliberately break things to discover robust solutions
+- **Guerrilla Gardening Ideas**: Plant unexpected solutions in unlikely places
+- **Pirate Code Brainstorm**: Take what works from anywhere and remix
+- **Zombie Apocalypse Planning**: Design for extreme survival scenarios
+- **Drunk History Retelling**: Explain with uninhibited simplicity
+
+### Introspective Delight
+
+- **Inner Child Conference**: Channel pure childhood curiosity
+- **Shadow Work Mining**: Explore what you're avoiding or resisting
+- **Values Archaeology**: Excavate deep personal values driving decisions
+- **Future Self Interview**: Seek wisdom from your wiser future self
+- **Body Wisdom Dialogue**: Let physical sensations guide ideation
+
+## Workflow Process
+
+### Phase 1: Session Setup (Step 1)
+
+- Context gathering (topic, goals, constraints)
+- Domain-specific guidance if context document provided
+- Session scope definition (broad exploration vs. focused ideation)
+
+### Phase 2: Approach Selection (Step 2)
+
+- **User-Selected**: Browse and choose specific techniques
+- **AI-Recommended**: Tailored technique suggestions based on context
+- **Random Selection**: Surprise technique for creative breakthrough
+- **Progressive Flow**: Multi-technique journey from broad to focused
+
+### Phase 3: Interactive Facilitation (Step 3)
+
+- Master facilitator approach using questions, not answers
+- "Yes, and..." building methodology
+- Energy monitoring and technique switching
+- Real-time idea capture and momentum building
+- Quantity over quality focus (aim: 100 ideas in 60 minutes)
+
+### Phase 4: Convergent Organization (Step 4)
+
+- Review and categorize all generated ideas
+- Identify patterns and themes across techniques
+- Sort into three priority buckets for action planning
+
+### Phase 5: Insight Extraction (Step 5)
+
+- Surface recurring themes across multiple techniques
+- Identify key realizations and surprising connections
+- Extract deeper patterns and meta-insights
+
+### Phase 6: Action Planning (Step 6)
+
+- Prioritize top 3 ideas for implementation
+- Define concrete next steps for each priority
+- Determine resource needs and realistic timelines
+
+### Phase 7: Session Reflection (Step 7)
+
+- Analyze what worked well and areas for further exploration
+- Recommend follow-up techniques and next session planning
+- Capture emergent questions for future investigation
+
+### Phase 8: Report Generation (Step 8)
+
+- Compile comprehensive structured report
+- Calculate total ideas generated and techniques used
+- Format all content for sharing and future reference
+
+## Output
+
+### Generated Files
+
+- **Primary output**: Structured session report saved to `{output_folder}/brainstorming-session-results-{date}.md`
+- **Context integration**: Links to previous brainstorming sessions if available
+
+### Output Structure
+
+1. **Executive Summary** - Topic, goals, techniques used, total ideas generated, key themes
+2. **Technique Sessions** - Detailed capture of each technique's ideation process
+3. **Idea Categorization** - Immediate opportunities, future innovations, moonshots, insights
+4. **Action Planning** - Top 3 priorities with rationale, steps, resources, timelines
+5. **Reflection and Follow-up** - Session analysis, recommendations, next steps planning
+
+## Requirements
+
+- No special software requirements
+- Access to the CIS module configuration (`{bmad_folder}/cis/config.yaml`)
+- Active participation and engagement throughout the interactive session
+- Optional: Domain context document for focused brainstorming
+
+## Best Practices
+
+### Before Starting
+
+1. **Define Clear Intent**: Know whether you want broad exploration or focused problem-solving
+2. **Gather Context**: Prepare any relevant background documents or domain knowledge
+3. **Set Time Expectations**: Plan for 45-90 minutes for a comprehensive session
+4. **Create Open Environment**: Ensure distraction-free space for creative thinking
+
+### During Execution
+
+1. **Embrace Quantity**: Generate many ideas without self-censoring
+2. **Build with "Yes, And"**: Accept and expand on ideas rather than judging
+3. **Stay Curious**: Follow unexpected connections and tangents
+4. **Trust the Process**: Let the facilitator guide you through technique transitions
+5. **Capture Everything**: Document all ideas, even seemingly silly ones
+6. **Monitor Energy**: Communicate when you need technique changes or breaks
+
+### After Completion
+
+1. **Review Within 24 Hours**: Re-read the report while insights are fresh
+2. **Act on Quick Wins**: Implement immediate opportunities within one week
+3. **Schedule Follow-ups**: Plan development sessions for promising concepts
+4. **Share Selectively**: Distribute relevant insights to appropriate stakeholders
+
+## Facilitation Principles
+
+The AI facilitator operates using these core principles:
+
+- **Ask, Don't Tell**: Use questions to draw out participant's own ideas
+- **Build, Don't Judge**: Use "Yes, and..." methodology, never "No, but..."
+- **Quantity Over Quality**: Aim for volume in generation phase
+- **Defer Judgment**: Evaluation comes after generation is complete
+- **Stay Curious**: Show genuine interest in participant's unique perspectives
+- **Monitor Energy**: Adapt technique and pace to participant's engagement level
+
+## Example Session Flow
+
+### Progressive Technique Flow
+
+1. **Mind Mapping** (10 min) - Build the landscape of possibilities
+2. **SCAMPER** (15 min) - Systematic exploration of improvement angles
+3. **Six Thinking Hats** (15 min) - Multiple perspectives on solutions
+4. **Forced Relationships** (10 min) - Creative synthesis of unexpected connections
+
+### Energy Checkpoints
+
+- After 15-20 minutes: "Should we continue with this technique or try something new?"
+- Before convergent phase: "Are you ready to start organizing ideas, or explore more?"
+- During action planning: "How's your energy for the final planning phase?"
+
+## Customization
+
+To customize this workflow:
+
+1. **Add New Techniques**: Extend `brain-methods.csv` with additional creative methods
+2. **Modify Facilitation Style**: Adjust prompts in `instructions.md` for different energy levels
+3. **Update Report Structure**: Modify `template.md` to include additional analysis sections
+4. **Create Domain Variants**: Develop specialized technique sets for specific industries
+
+## Version History
+
+- **v1.0.0** - Initial release
+  - 36 creative techniques across 7 categories
+  - Interactive facilitation with energy monitoring
+  - Comprehensive structured reporting
+  - Context-aware session guidance
+
+## Support
+
+For issues or questions:
+
+- Review technique descriptions in `brain-methods.csv` for facilitation guidance
+- Consult the workflow instructions in `instructions.md` for step-by-step details
+- Reference the template structure in `template.md` for output expectations
+- Follow BMAD documentation standards for workflow customization
+
+---
+
+_Part of the BMad Method v6 - Creative Ideation and Synthesis (CIS) Module_

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

@@ -1,62 +1,36 @@
-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"
+category,technique_name,description,facilitation_prompts,best_for,energy_level,typical_duration
+collaborative,Yes And Building,Build momentum through positive additions where each idea becomes a launching pad for the next - creates energetic collaborative flow,Yes and we could also...|Building on that idea...|That reminds me of...|What if we added?,team-building,high,15-20
+collaborative,Brain Writing Round Robin,Silent idea generation followed by building on others' written concepts - gives quieter voices equal contribution while maintaining documentation,Write your idea silently|Pass to the next person|Build on what you received|Keep ideas flowing,quiet-voices,moderate,20-25
+collaborative,Random Stimulation,Use random words/images as creative catalysts to force unexpected connections - breaks through mental blocks with serendipitous inspiration,Pick a random word/image|How does this relate?|What connections do you see?|Force a relationship
+collaborative,Role Playing,Generate solutions from multiple stakeholder perspectives - builds empathy while ensuring comprehensive consideration of all viewpoints,Think as a [role]|What would they want?|How would they approach this?|What matters to them?
+creative,What If Scenarios,Explore radical possibilities by questioning all constraints and assumptions - perfect for breaking through stuck thinking and discovering unexpected opportunities,What if we had unlimited resources?|What if the opposite were true?|What if this problem didn't exist?,innovation,high,15-20
+creative,Analogical Thinking,Find creative solutions by drawing parallels to other domains - helps transfer successful patterns from one context to another,This is like what?|How is this similar to...?|What other examples come to mind?
+creative,Reversal Inversion,Deliberately flip problems upside down to reveal hidden assumptions and fresh angles - great when conventional approaches aren't working,What if we did the opposite?|How could we make this worse?|What's the reverse approach?
+creative,First Principles Thinking,Strip away assumptions to rebuild from fundamental truths - essential for breakthrough innovation and solving complex problems,What do we know for certain?|What are the fundamental truths?|If we started from scratch?
+creative,Forced Relationships,Connect unrelated concepts to spark innovative bridges - excellent for generating unexpected solutions through creative collision,Take these two unrelated things|Find connections between them|What bridges exist?|How could they work together?
+creative,Time Shifting,Explore how solutions would work across different time periods - reveals constraints and opportunities by changing temporal context,How would this work in the past?|What about 100 years from now?|Different era constraints?|Time-based solutions?
+creative,Metaphor Mapping,Use extended metaphors as thinking tools to explore problems from new angles - transforms abstract challenges into tangible narratives,This problem is like a [metaphor]|Extend the metaphor|What elements map over?|What insights emerge?
+deep,Five Whys,Drill down through layers of causation to uncover root causes - essential for solving problems at their source rather than treating symptoms,Why did this happen?|Why is that?|And why is that true?|What's behind that?|Why ultimately?,problem-solving,moderate,10-15
+deep,Morphological Analysis,Systematically explore all possible parameter combinations - perfect for complex systems requiring comprehensive solution mapping,What are the key parameters?|List options for each|Try different combinations|What patterns emerge?
+deep,Provocation Technique,Use deliberately provocative statements to extract useful ideas from seemingly absurd starting points - catalyzes breakthrough thinking,What if [provocative statement]?|How could this be useful?|What idea does this trigger?|Extract the principle
+deep,Assumption Reversal,Challenge and flip core assumptions to rebuild from new foundations - essential for paradigm shifts and fresh perspectives,What assumptions are we making?|What if the opposite were true?|Challenge each assumption|Rebuild from new assumptions
+deep,Question Storming,Generate questions before seeking answers to properly define the problem space - ensures you're solving the right problem,Only ask questions|No answers allowed yet|What don't we know?|What should we be asking?
+introspective_delight,Inner Child Conference,Channel pure childhood curiosity and wonder - rekindles playful exploration and innocent questioning that cuts through adult complications,What would 7-year-old you ask?|Why why why?|Make it fun again|No boring allowed
+introspective_delight,Shadow Work Mining,Explore what you're actively avoiding or resisting - uncovers hidden insights by examining unconscious blocks and resistance patterns,What are you avoiding?|Where's the resistance?|What scares you about this?|Mine the shadows
+introspective_delight,Values Archaeology,Excavate the deep personal values driving your decisions - clarifies authentic priorities by digging to bedrock motivations,What really matters here?|Why do you care?|Dig to bedrock values|What's non-negotiable?
+introspective_delight,Future Self Interview,Seek wisdom from your wiser future self - gains long-term perspective through imagined temporal self-mentoring,Ask your 80-year-old self|What would you tell younger you?|Future wisdom speaks|Long-term perspective
+introspective_delight,Body Wisdom Dialogue,Let physical sensations and gut feelings guide ideation - taps somatic intelligence often ignored by purely mental approaches,What does your body say?|Where do you feel it?|Trust the tension|Follow physical cues
+structured,SCAMPER Method,Systematic creativity through seven lenses (Substitute/Combine/Adapt/Modify/Put/Eliminate/Reverse) - ideal for methodical product improvement and innovation,S-What could you substitute?|C-What could you combine?|A-How could you adapt?|M-What could you modify?|P-Put to other uses?|E-What could you eliminate?|R-What if reversed?
+structured,Six Thinking Hats,Explore problems through six distinct perspectives (facts/emotions/benefits/risks/creativity/process) - ensures comprehensive analysis without conflict,White-What facts do we know?|Red-How do you feel about this?|Yellow-What are the benefits?|Black-What could go wrong?|Green-What creative alternatives?|Blue-How should we think about this?
+structured,Mind Mapping,Visually branch ideas from a central concept to discover connections and expand thinking - perfect for organizing complex thoughts and seeing the big picture,Put the main idea in center|What branches from this?|How do these connect?|What sub-branches emerge?
+structured,Resource Constraints,Generate innovative solutions by imposing extreme limitations - forces essential priorities and creative efficiency under pressure,What if you had only $1?|No technology allowed?|One hour to solve?|Minimal resources only?
+theatrical,Time Travel Talk Show,Interview your past/present/future selves for temporal wisdom - playful method for gaining perspective across different life stages,Interview your past self|What would future you say?|Different timeline perspectives|Cross-temporal dialogue
+theatrical,Alien Anthropologist,Examine familiar problems through completely foreign eyes - reveals hidden assumptions by adopting an outsider's bewildered perspective,You're an alien observer|What seems strange?|How would you explain this?|Outside perspective insights
+theatrical,Dream Fusion Laboratory,Start with impossible fantasy solutions then reverse-engineer practical steps - makes ambitious thinking actionable through backwards design,Dream the impossible solution|Work backwards to reality|What steps bridge the gap?|Make magic practical
+theatrical,Emotion Orchestra,Let different emotions lead separate brainstorming sessions then harmonize - uses emotional intelligence for comprehensive perspective,Angry perspective ideas|Joyful approach|Fearful considerations|Hopeful solutions|Harmonize all voices
+theatrical,Parallel Universe Cafe,Explore solutions under alternative reality rules - breaks conventional thinking by changing fundamental assumptions about how things work,Different physics universe|Alternative social norms|Changed historical events|Reality rule variations
+wild,Chaos Engineering,Deliberately break things to discover robust solutions - builds anti-fragility by stress-testing ideas against worst-case scenarios,What if everything went wrong?|Break it on purpose|How does it fail gracefully?|Build from the rubble
+wild,Guerrilla Gardening Ideas,Plant unexpected solutions in unlikely places - uses surprise and unconventional placement for stealth innovation,Where's the least expected place?|Plant ideas secretly|Grow solutions underground|Surprise implementation
+wild,Pirate Code Brainstorm,Take what works from anywhere and remix without permission - encourages rule-bending rapid prototyping and maverick thinking,What would pirates steal?|Remix without asking|Take the best and run|No permission needed
+wild,Zombie Apocalypse Planning,Design solutions for extreme survival scenarios - strips away all but essential functions to find core value,Society collapsed - now what?|Only basics work|Build from nothing|Survival mode thinking
+wild,Drunk History Retelling,Explain complex ideas with uninhibited simplicity - removes overthinking barriers to find raw truth through simplified expression,Explain it like you're tipsy|No filter needed|Raw unedited thoughts|Simplify to absurdity

src/core/workflows/brainstorming/instructions.md

@@ -0,0 +1,315 @@
+# Brainstorming Session Instructions
+
+## Workflow
+
+<workflow>
+<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project_root}/{bmad_folder}/core/workflows/brainstorming/workflow.yaml</critical>
+
+<step n="1" goal="Session Setup">
+
+<action>Check if context data was provided with workflow invocation</action>
+
+<check if="data attribute was passed to this workflow">
+  <action>Load the context document from the data file path</action>
+  <action>Study the domain knowledge and session focus</action>
+  <action>Use the provided context to guide the session</action>
+  <action>Acknowledge the focused brainstorming goal</action>
+  <ask response="session_refinement">I see we're brainstorming about the specific domain outlined in the context. What particular aspect would you like to explore?</ask>
+</check>
+
+<check if="no context data provided">
+  <action>Proceed with generic context gathering</action>
+  <ask response="session_topic">1. What are we brainstorming about?</ask>
+  <ask response="stated_goals">2. Are there any constraints or parameters we should keep in mind?</ask>
+  <ask>3. Is the goal broad exploration or focused ideation on specific aspects?</ask>
+
+<critical>Wait for user response before proceeding. This context shapes the entire session.</critical>
+</check>
+
+<template-output>session_topic, stated_goals</template-output>
+
+</step>
+
+<step n="2" goal="Present Approach Options">
+
+Based on the context from Step 1, present these four approach options:
+
+<ask response="selection">
+1. **User-Selected Techniques** - Browse and choose specific techniques from our library
+2. **AI-Recommended Techniques** - Let me suggest techniques based on your context
+3. **Random Technique Selection** - Surprise yourself with unexpected creative methods
+4. **Progressive Technique Flow** - Start broad, then narrow down systematically
+
+Which approach would you prefer? (Enter 1-4)
+</ask>
+
+  <step n="2a" title="User-Selected Techniques" if="selection==1">
+    <action>Load techniques from {brain_techniques} CSV file</action>
+    <action>Parse: category, technique_name, description, facilitation_prompts</action>
+
+    <check if="strong context from Step 1 (specific problem/goal)">
+      <action>Identify 2-3 most relevant categories based on stated_goals</action>
+      <action>Present those categories first with 3-5 techniques each</action>
+      <action>Offer "show all categories" option</action>
+    </check>
+
+    <check if="open exploration">
+      <action>Display all 7 categories with helpful descriptions</action>
+    </check>
+
+    Category descriptions to guide selection:
+    - **Structured:** Systematic frameworks for thorough exploration
+    - **Creative:** Innovative approaches for breakthrough thinking
+    - **Collaborative:** Group dynamics and team ideation methods
+    - **Deep:** Analytical methods for root cause and insight
+    - **Theatrical:** Playful exploration for radical perspectives
+    - **Wild:** Extreme thinking for pushing boundaries
+    - **Introspective Delight:** Inner wisdom and authentic exploration
+
+    For each category, show 3-5 representative techniques with brief descriptions.
+
+    Ask in your own voice: "Which technique(s) interest you? You can choose by name, number, or tell me what you're drawn to."
+
+  </step>
+
+  <step n="2b" title="AI-Recommended Techniques" if="selection==2">
+    <action>Review {brain_techniques} and select 3-5 techniques that best fit the context</action>
+
+    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 → Consider progressive flow (3-5 techniques)
+
+    Present recommendations in your own voice with:
+    - Technique name (category)
+    - Why it fits their context (specific)
+    - What they'll discover (outcome)
+    - Estimated time
+
+    Example structure:
+    "Based on your goal to [X], I recommend:
+
+    1. **[Technique Name]** (category) - X min
+       WHY: [Specific reason based on their context]
+       OUTCOME: [What they'll generate/discover]
+
+    2. **[Technique Name]** (category) - X min
+       WHY: [Specific reason]
+       OUTCOME: [Expected result]
+
+    Ready to start? [c] or would you prefer different techniques? [r]"
+
+  </step>
+
+  <step n="2c" title="Single Random Technique Selection" if="selection==3">
+    <action>Load all techniques from {brain_techniques} CSV</action>
+    <action>Select random technique using true randomization</action>
+    <action>Build excitement about unexpected choice</action>
+    <format>
+      Let's shake things up! The universe has chosen:
+      **{{technique_name}}** - {{description}}
+    </format>
+  </step>
+
+  <step n="2d" title="Progressive Flow" if="selection==4">
+    <action>Design a progressive journey through {brain_techniques} based on session context</action>
+    <action>Analyze stated_goals and session_topic from Step 1</action>
+    <action>Determine session length (ask if not stated)</action>
+    <action>Select 3-4 complementary techniques that build on each other</action>
+
+    Journey Design Principles:
+    - Start with divergent exploration (broad, generative)
+    - Move through focused deep dive (analytical or creative)
+    - End with convergent synthesis (integration, prioritization)
+
+    Common Patterns by Goal:
+    - **Problem-solving:** Mind Mapping → Five Whys → Assumption Reversal
+    - **Innovation:** What If Scenarios → Analogical Thinking → Forced Relationships
+    - **Strategy:** First Principles → SCAMPER → Six Thinking Hats
+    - **Team Building:** Brain Writing → Yes And Building → Role Playing
+
+    Present your recommended journey with:
+    - Technique names and brief why
+    - Estimated time for each (10-20 min)
+    - Total session duration
+    - Rationale for sequence
+
+    Ask in your own voice: "How does this flow sound? We can adjust as we go."
+
+  </step>
+
+<critical>Create the output document using the template, and record at the {{session_start_plan}} documenting the chosen techniques, along with which approach was used. For all remaining steps, progressively add to the document throughout the brainstorming</critical>
+</step>
+
+<step n="3" goal="Execute Techniques Interactively">
+
+<critical>
+REMEMBER: YOU ARE A MASTER Brainstorming Creative FACILITATOR: Guide the user as a facilitator to generate their own ideas through questions, prompts, and examples. Don't brainstorm for them unless they explicitly request it.
+</critical>
+
+<facilitation-principles>
+  - Ask, don't tell - Use questions to draw out ideas
+  - Build, don't judge - Use "Yes, and..." never "No, but..."
+  - Quantity over quality - Aim for 100 ideas in 60 minutes
+  - Defer judgment - Evaluation comes after generation
+  - Stay curious - Show genuine interest in their ideas
+</facilitation-principles>
+
+For each technique:
+
+1. **Introduce the technique** - Use the description from CSV to explain how it works
+2. **Provide the first prompt** - Use facilitation_prompts from CSV (pipe-separated prompts)
+   - Parse facilitation_prompts field and select appropriate prompts
+   - These are your conversation starters and follow-ups
+3. **Wait for their response** - Let them generate ideas
+4. **Build on their ideas** - Use "Yes, and..." or "That reminds me..." or "What if we also..."
+5. **Ask follow-up questions** - "Tell me more about...", "How would that work?", "What else?"
+6. **Monitor energy** - Check: "How are you feeling about this {session / technique / progress}?"
+   - If energy is high → Keep pushing with current technique
+   - If energy is low → "Should we try a different angle or take a quick break?"
+7. **Keep momentum** - Celebrate: "Great! You've generated [X] ideas so far!"
+8. **Document everything** - Capture all ideas for the final report
+
+<example>
+Example facilitation flow for any technique:
+
+1. Introduce: "Let's try [technique_name]. [Adapt description from CSV to their context]."
+
+2. First Prompt: Pull first facilitation_prompt from {brain_techniques} and adapt to their topic
+   - CSV: "What if we had unlimited resources?"
+   - Adapted: "What if you had unlimited resources for [their_topic]?"
+
+3. Build on Response: Use "Yes, and..." or "That reminds me..." or "Building on that..."
+
+4. Next Prompt: Pull next facilitation_prompt when ready to advance
+
+5. Monitor Energy: After a few rounds, check if they want to continue or switch
+
+The CSV provides the prompts - your role is to facilitate naturally in your unique voice.
+</example>
+
+Continue engaging with the technique until the user indicates they want to:
+
+- Switch to a different technique ("Ready for a different approach?")
+- Apply current ideas to a new technique
+- Move to the convergent phase
+- End the session
+
+<energy-checkpoint>
+  After 4 rounds with a technique, check: "Should we continue with this technique or try something new?"
+</energy-checkpoint>
+
+<template-output>technique_sessions</template-output>
+
+</step>
+
+<step n="4" goal="Convergent Phase - Organize Ideas">
+
+<transition-check>
+  "We've generated a lot of great ideas! Are you ready to start organizing them, or would you like to explore more?"
+</transition-check>
+
+When ready to consolidate:
+
+Guide the user through categorizing their ideas:
+
+1. **Review all generated ideas** - Display everything captured so far
+2. **Identify patterns** - "I notice several ideas about X... and others about Y..."
+3. **Group into categories** - Work with user to organize ideas within and across techniques
+
+Ask: "Looking at all these ideas, which ones feel like:
+
+- <ask response="immediate_opportunities">Quick wins we could implement immediately?</ask>
+- <ask response="future_innovations">Promising concepts that need more development?</ask>
+- <ask response="moonshots">Bold moonshots worth pursuing long-term?"</ask>
+
+<template-output>immediate_opportunities, future_innovations, moonshots</template-output>
+
+</step>
+
+<step n="5" goal="Extract Insights and Themes">
+
+Analyze the session to identify deeper patterns:
+
+1. **Identify recurring themes** - What concepts appeared across multiple techniques? -> key_themes
+2. **Surface key insights** - What realizations emerged during the process? -> insights_learnings
+3. **Note surprising connections** - What unexpected relationships were discovered? -> insights_learnings
+
+<invoke-task halt="true">{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml</invoke-task>
+
+<template-output>key_themes, insights_learnings</template-output>
+
+</step>
+
+<step n="6" goal="Action Planning">
+
+<energy-check>
+  "Great work so far! How's your energy for the final planning phase?"
+</energy-check>
+
+Work with the user to prioritize and plan next steps:
+
+<ask>Of all the ideas we've generated, which 3 feel most important to pursue?</ask>
+
+For each priority:
+
+1. Ask why this is a priority
+2. Identify concrete next steps
+3. Determine resource needs
+4. Set realistic timeline
+
+<template-output>priority_1_name, priority_1_rationale, priority_1_steps, priority_1_resources, priority_1_timeline</template-output>
+<template-output>priority_2_name, priority_2_rationale, priority_2_steps, priority_2_resources, priority_2_timeline</template-output>
+<template-output>priority_3_name, priority_3_rationale, priority_3_steps, priority_3_resources, priority_3_timeline</template-output>
+
+</step>
+
+<step n="7" goal="Session Reflection">
+
+Conclude with meta-analysis of the session:
+
+1. **What worked well** - Which techniques or moments were most productive?
+2. **Areas to explore further** - What topics deserve deeper investigation?
+3. **Recommended follow-up techniques** - What methods would help continue this work?
+4. **Emergent questions** - What new questions arose that we should address?
+5. **Next session planning** - When and what should we brainstorm next?
+
+<template-output>what_worked, areas_exploration, recommended_techniques, questions_emerged</template-output>
+<template-output>followup_topics, timeframe, preparation</template-output>
+
+</step>
+
+<step n="8" goal="Generate Final Report">
+
+Compile all captured content into the structured report template:
+
+1. Calculate total ideas generated across all techniques
+2. List all techniques used with duration estimates
+3. Format all content according to template structure
+4. Ensure all placeholders are filled with actual content
+
+<template-output>agent_role, agent_name, user_name, techniques_list, total_ideas</template-output>
+
+</step>
+
+</workflow>

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 +1,106 @@
----
-stepsCompleted: []
-inputDocuments: []
-session_topic: ''
-session_goals: ''
-selected_approach: ''
-techniques_used: []
-ideas_generated: []
-context_file: ''
----
-
 # Brainstorming Session Results
 
-**Facilitator:** {{user_name}}
-**Date:** {{date}}
+**Session Date:** {{date}}
+**Facilitator:** {{agent_role}} {{agent_name}}
+**Participant:** {{user_name}}
+
+## Session Start
+
+{{session_start_plan}}
+
+## Executive Summary
+
+**Topic:** {{session_topic}}
+
+**Session Goals:** {{stated_goals}}
+
+**Techniques Used:** {{techniques_list}}
+
+**Total Ideas Generated:** {{total_ideas}}
+
+### Key Themes Identified:
+
+{{key_themes}}
+
+## Technique Sessions
+
+{{technique_sessions}}
+
+## Idea Categorization
+
+### Immediate Opportunities
+
+_Ideas ready to implement now_
+
+{{immediate_opportunities}}
+
+### Future Innovations
+
+_Ideas requiring development/research_
+
+{{future_innovations}}
+
+### Moonshots
+
+_Ambitious, transformative concepts_
+
+{{moonshots}}
+
+### Insights and Learnings
+
+_Key realizations from the session_
+
+{{insights_learnings}}
+
+## Action Planning
+
+### Top 3 Priority Ideas
+
+#### #1 Priority: {{priority_1_name}}
+
+- Rationale: {{priority_1_rationale}}
+- Next steps: {{priority_1_steps}}
+- Resources needed: {{priority_1_resources}}
+- Timeline: {{priority_1_timeline}}
+
+#### #2 Priority: {{priority_2_name}}
+
+- Rationale: {{priority_2_rationale}}
+- Next steps: {{priority_2_steps}}
+- Resources needed: {{priority_2_resources}}
+- Timeline: {{priority_2_timeline}}
+
+#### #3 Priority: {{priority_3_name}}
+
+- Rationale: {{priority_3_rationale}}
+- Next steps: {{priority_3_steps}}
+- Resources needed: {{priority_3_resources}}
+- Timeline: {{priority_3_timeline}}
+
+## Reflection and Follow-up
+
+### What Worked Well
+
+{{what_worked}}
+
+### Areas for Further Exploration
+
+{{areas_exploration}}
+
+### Recommended Follow-up Techniques
+
+{{recommended_techniques}}
+
+### Questions That Emerged
+
+{{questions_emerged}}
+
+### Next Session Planning
+
+- **Suggested topics:** {{followup_topics}}
+- **Recommended timeframe:** {{timeframe}}
+- **Preparation needed:** {{preparation}}
+
+---
+
+_Session facilitated using the BMAD CIS brainstorming framework_

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_folder}/bmm/config.yaml` and resolve:
-
-- `project_name`, `output_folder`, `user_name`
-- `communication_language`, `document_output_language`, `user_skill_level`
-- `date` as system-generated current datetime
-
-### Paths
-
-- `installed_path` = `{project-root}/{bmad_folder}/core/workflows/brainstorming`
-- `template_path` = `{installed_path}/template.md`
-- `brain_techniques_path` = `{installed_path}/brain-methods.csv`
-- `default_output_file` = `{output_folder}/analysis/brainstorming-session-{{date}}.md`
-- `context_file` = Optional context file path from workflow invocation for project-specific guidance
-
----
-
-## EXECUTION
-
-Load and execute `steps/step-01-session-setup.md` to begin the workflow.
-
-**Note:** Session setup, technique discovery, and continuation detection happen in step-01-session-setup.md.

src/core/workflows/brainstorming/workflow.yaml

@@ -0,0 +1,38 @@
+# Brainstorming Session Workflow Configuration
+name: "brainstorming"
+description: "Facilitate interactive brainstorming sessions using diverse creative techniques. This workflow facilitates interactive brainstorming sessions using diverse creative techniques. The session is highly interactive, with the AI acting as a facilitator to guide the user through various ideation methods to generate and refine creative solutions."
+author: "BMad"
+
+# Critical variables load from config_source
+config_source: "{project-root}/{bmad_folder}/cis/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+date: system-generated
+
+# Context can be provided via data attribute when invoking
+# Example: data="{path}/context.md" provides domain-specific guidance
+
+# Module path and component files
+installed_path: "{project-root}/{bmad_folder}/core/workflows/brainstorming"
+template: "{installed_path}/template.md"
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+brain_techniques: "{installed_path}/brain-methods.csv"
+
+# Output configuration
+default_output_file: "{output_folder}/brainstorming-session-results-{{date}}.md"
+
+standalone: true
+
+web_bundle:
+  name: "brainstorming"
+  description: "Facilitate interactive brainstorming sessions using diverse creative techniques. This workflow facilitates interactive brainstorming sessions using diverse creative techniques. The session is highly interactive, with the AI acting as a facilitator to guide the user through various ideation methods to generate and refine creative solutions."
+  author: "BMad"
+  template: "{bmad_folder}/core/workflows/brainstorming/template.md"
+  instructions: "{bmad_folder}/core/workflows/brainstorming/instructions.md"
+  brain_techniques: "{bmad_folder}/core/workflows/brainstorming/brain-methods.csv"
+  use_advanced_elicitation: true
+  web_bundle_files:
+    - "{bmad_folder}/core/workflows/brainstorming/instructions.md"
+    - "{bmad_folder}/core/workflows/brainstorming/brain-methods.csv"
+    - "{bmad_folder}/core/workflows/brainstorming/template.md"

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

@@ -0,0 +1,183 @@
+# Party Mode - Multi-Agent Discussion Instructions
+
+<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
+<critical>This workflow orchestrates group discussions between all installed BMAD agents</critical>
+
+<workflow>
+
+<step n="1" goal="Load Agent Manifest and Configurations">
+  <action>Load the agent manifest CSV from {{agent_manifest}}</action>
+  <action>Parse CSV to extract all agent entries with their condensed information:</action>
+    - name (agent identifier)
+    - displayName (agent's persona name)
+    - title (formal position)
+    - icon (visual identifier)
+    - role (capabilities summary)
+    - identity (background/expertise)
+    - communicationStyle (how they communicate)
+    - principles (decision-making philosophy)
+    - module (source module)
+    - path (file location)
+
+<action>Build complete agent roster with merged personalities</action>
+<action>Store agent data for use in conversation orchestration</action>
+</step>
+
+<step n="2" goal="Initialize Party Mode">
+  <action>Announce party mode activation with enthusiasm</action>
+  <action>List all participating agents with their merged information:</action>
+  <format>
+    🎉 PARTY MODE ACTIVATED! 🎉
+    All agents are here for a group discussion!
+
+    Participating agents:
+    [For each agent in roster:]
+    - [Agent Name] ([Title]): [Role from merged data]
+
+    [Total count] agents ready to collaborate!
+
+    What would you like to discuss with the team?
+
+  </format>
+  <action>Wait for user to provide initial topic or question</action>
+</step>
+
+<step n="3" goal="Orchestrate Multi-Agent Discussion" repeat="until-exit">
+  <action>For each user message or topic:</action>
+
+  <substep n="3a" goal="Determine Relevant Agents">
+    <action>Analyze the user's message/question</action>
+    <action>Identify which agents would naturally respond based on:</action>
+      - Their role and capabilities (from merged data)
+      - Their stated principles
+      - Their memories/context if relevant
+      - Their collaboration patterns
+    <action>Select 2-3 most relevant agents for this response</action>
+    <note>If user addresses specific agent by name, prioritize that agent</note>
+  </substep>
+
+  <substep n="3b" goal="Generate In-Character Responses">
+    <action>For each selected agent, generate authentic response:</action>
+    <action>Use the agent's merged personality data:</action>
+      - Apply their communicationStyle exactly
+      - Reflect their principles in reasoning
+      - Draw from their identity and role for expertise
+      - Maintain their unique voice and perspective
+
+    <action>Enable natural cross-talk between agents:</action>
+      - Agents can reference each other by name
+      - Agents can build on previous points
+      - Agents can respectfully disagree or offer alternatives
+      - Agents can ask follow-up questions to each other
+
+  </substep>
+
+  <substep n="3c" goal="Handle Questions and Interactions">
+    <check if="an agent asks the user a direct question">
+      <action>Clearly highlight the question</action>
+      <action>End that round of responses</action>
+      <action>Display: "[Agent Name]: [Their question]"</action>
+      <action>Display: "[Awaiting user response...]"</action>
+      <action>WAIT for user input before continuing</action>
+    </check>
+
+    <check if="agents ask each other questions">
+      <action>Allow natural back-and-forth in the same response round</action>
+      <action>Maintain conversational flow</action>
+    </check>
+
+    <check if="discussion becomes circular or repetitive">
+      <action>The BMad Master will summarize</action>
+      <action>Redirect to new aspects or ask for user guidance</action>
+    </check>
+
+  </substep>
+
+  <substep n="3d" goal="Format and Present Responses">
+    <action>Present each agent's contribution clearly:</action>
+    <format>
+      [Agent Name]: [Their response in their voice/style]
+
+      [Another Agent]: [Their response, potentially referencing the first]
+
+      [Third Agent if selected]: [Their contribution]
+    </format>
+
+    <action>Maintain spacing between agents for readability</action>
+    <action>Preserve each agent's unique voice throughout</action>
+
+  </substep>
+
+  <substep n="3e" goal="Check for Exit Conditions">
+    <check if="user message contains any {{exit_triggers}}">
+      <action>Have agents provide brief farewells in character</action>
+      <action>Thank user for the discussion</action>
+      <goto step="4">Exit party mode</goto>
+    </check>
+
+    <check if="user seems done or conversation naturally concludes">
+      <ask>Would you like to continue the discussion or end party mode?</ask>
+      <check if="user indicates end">
+        <goto step="4">Exit party mode</goto>
+      </check>
+    </check>
+
+  </substep>
+</step>
+
+<step n="4" goal="Exit Party Mode">
+  <action>Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other</action>
+  <format>
+    [Agent 1]: [Brief farewell in their style]
+
+    [Agent 2]: [Their goodbye]
+
+    🎊 Party Mode ended. Thanks for the great discussion!
+
+  </format>
+  <action>Exit workflow</action>
+</step>
+
+</workflow>
+
+## Role-Playing Guidelines
+
+<guidelines>
+  <guideline>Keep all responses strictly in-character based on merged personality data</guideline>
+  <guideline>Use each agent's documented communication style consistently</guideline>
+  <guideline>Reference agent memories and context when relevant</guideline>
+  <guideline>Allow natural disagreements and different perspectives</guideline>
+  <guideline>Maintain professional discourse while being engaging</guideline>
+  <guideline>Let agents reference each other naturally by name or role</guideline>
+  <guideline>Include personality-driven quirks and occasional humor</guideline>
+  <guideline>Respect each agent's expertise boundaries</guideline>
+</guidelines>
+
+## Question Handling Protocol
+
+<question-protocol>
+  <direct-to-user>
+    When agent asks user a specific question (e.g., "What's your budget?"):
+    - End that round immediately after the question
+    - Clearly highlight the questioning agent and their question
+    - Wait for user response before any agent continues
+  </direct-to-user>
+
+  <rhetorical>
+    Agents can ask rhetorical or thinking-aloud questions without pausing
+  </rhetorical>
+
+  <inter-agent>
+    Agents can question each other and respond naturally within same round
+  </inter-agent>
+</question-protocol>
+
+## Moderation Notes
+
+<moderation>
+  <note>If discussion becomes circular, have bmad-master summarize and redirect</note>
+  <note>If user asks for specific agent, let that agent take primary lead</note>
+  <note>Balance fun and productivity based on conversation tone</note>
+  <note>Ensure all agents stay true to their merged personalities</note>
+  <note>Exit gracefully when user indicates completion</note>
+</moderation>

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

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_folder}/bmm/config.yaml` and resolve:
-
-- `project_name`, `output_folder`, `user_name`
-- `communication_language`, `document_output_language`, `user_skill_level`
-- `date` as a system-generated value
-- Agent manifest path: `{project-root}/{bmad_folder}/_cfg/agent-manifest.csv`
-
-### Paths
-
-- `installed_path` = `{project-root}/{bmad_folder}/core/workflows/party-mode`
-- `agent_manifest_path` = `{project-root}/{bmad_folder}/_cfg/agent-manifest.csv`
-- `standalone_mode` = `true` (party mode is an interactive workflow)
-
----
-
-## AGENT MANIFEST PROCESSING
-
-### Agent Data Extraction
-
-Parse CSV manifest to extract agent entries with complete information:
-
-- **name** (agent identifier)
-- **displayName** (agent's persona name)
-- **title** (formal position)
-- **icon** (visual identifier emoji)
-- **role** (capabilities summary)
-- **identity** (background/expertise)
-- **communicationStyle** (how they communicate)
-- **principles** (decision-making philosophy)
-- **module** (source module)
-- **path** (file location)
-
-### Agent Roster Building
-
-Build complete agent roster with merged personalities for conversation orchestration.
-
----
-
-## EXECUTION
-
-Execute party mode activation and conversation orchestration:
-
-### Party Mode Activation
-
-**Your Role:** You are a party mode facilitator creating an engaging multi-agent conversation environment.
-
-**Welcome Activation:**
-
-"🎉 PARTY MODE ACTIVATED! 🎉
-
-Welcome {{user_name}}! All BMAD agents are here and ready for a dynamic group discussion. I've brought together our complete team of experts, each bringing their unique perspectives and capabilities.
-
-**Let me introduce our collaborating agents:**
-
-[Load agent roster and display 2-3 most diverse agents as examples]
-
-**What would you like to discuss with the team today?**"
-
-### Agent Selection Intelligence
-
-For each user message or topic:
-
-**Relevance Analysis:**
-
-- Analyze the user's message/question for domain and expertise requirements
-- Identify which agents would naturally contribute based on their role, capabilities, and principles
-- Consider conversation context and previous agent contributions
-- Select 2-3 most relevant agents for balanced perspective
-
-**Priority Handling:**
-
-- If user addresses specific agent by name, prioritize that agent + 1-2 complementary agents
-- Rotate agent selection to ensure diverse participation over time
-- Enable natural cross-talk and agent-to-agent interactions
-
-### Conversation Orchestration
-
-Load step: `./steps/step-02-discussion-orchestration.md`
-
----
-
-## WORKFLOW STATES
-
-### Frontmatter Tracking
-
-```yaml
----
-stepsCompleted: [1]
-workflowType: 'party-mode'
-user_name: '{{user_name}}'
-date: '{{date}}'
-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/core/workflows/party-mode/workflow.yaml

@@ -0,0 +1,28 @@
+# Party Mode - Multi-Agent Group Discussion Workflow
+name: "party-mode"
+description: "Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations"
+author: "BMad"
+
+# Critical data sources - manifest and config overrides
+agent_manifest: "{project-root}/{bmad_folder}/_cfg/agent-manifest.csv"
+date: system-generated
+
+# This is an interactive action workflow - no template output
+template: false
+instructions: "{project-root}/{bmad_folder}/core/workflows/party-mode/instructions.md"
+
+# Exit conditions
+exit_triggers:
+  - "*exit"
+
+standalone: true
+
+web_bundle:
+  name: "party-mode"
+  description: "Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations"
+  author: "BMad"
+  instructions: "{bmad_folder}/core/workflows/party-mode/instructions.md"
+  agent_manifest: "{bmad_folder}/_cfg/agent-manifest.csv"
+  web_bundle_files:
+    - "{bmad_folder}/core/workflows/party-mode/instructions.md"
+    - "{bmad_folder}/_cfg/agent-manifest.csv"

src/modules/bmb/README.md

@@ -5,8 +5,6 @@ Specialized tools and workflows for creating, customizing, and extending BMad co
 ## 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)
@@ -18,172 +16,124 @@ Specialized tools and workflows for creating, customizing, and extending BMad co
 
 **BMad Builder** - Master builder agent orchestrating all creation workflows with deep knowledge of BMad architecture and conventions.
 
-- Location: `.bmad/bmb/agents/bmad-builder.md`
-
 ### 📋 Workflows
 
-**Active Workflows** (Step-File Architecture)
-
-- Location: `src/modules/bmb/workflows/`
-- 5 core workflows with 41 step files total
-- Template-based execution with JIT loading
-
-**Legacy Workflows** (Being Migrated)
-
-- Location: `src/modules/bmb/workflows-legacy/`
-- Module-specific workflows pending conversion to step-file architecture
-
-### 📚 Documentation
-
-- Location: `src/modules/bmb/docs/`
-- Comprehensive guides for agents and workflows
-- Architecture patterns and best practices
-
-### 🔍 Reference Materials
-
-- Location: `src/modules/bmb/reference/`
-- Working examples of agents and workflows
-- Template patterns and implementation guides
-
-## Documentation
-
-### 📖 Agent Documentation
-
-- **[Agent Index](./docs/agents/index.md)** - Complete agent architecture guide
-- **[Agent Types Guide](./docs/agents/understanding-agent-types.md)** - Simple vs Expert vs Module agents
-- **[Menu Patterns](./docs/agents/agent-menu-patterns.md)** - YAML menu design and handler types
-- **[Agent Compilation](./docs/agents/agent-compilation.md)** - Auto-injection rules and compilation process
-
-### 📋 Workflow Documentation
-
-- **[Workflow Index](./docs/workflows/index.md)** - Core workflow system overview
-- **[Architecture Guide](./docs/workflows/architecture.md)** - Step-file design and JIT loading
-- **[Template System](./docs/workflows/templates/step-template.md)** - Standard step file template
-- **[Intent vs Prescriptive](./docs/workflows/intent-vs-prescriptive-spectrum.md)** - Design philosophy
-
-## Reference Materials
-
-### 🤖 Agent Examples
-
-- **[Simple Agent Example](./reference/agents/simple-examples/commit-poet.agent.yaml)** - Self-contained agent
-- **[Expert Agent Example](./reference/agents/expert-examples/journal-keeper/)** - Agent with persistent memory
-- **[Module Agent Examples](./reference/agents/module-examples/)** - Integration patterns (BMM, CIS)
-
-### 📋 Workflow Examples
-
-- **[Meal Prep & Nutrition](./reference/workflows/meal-prep-nutrition/)** - Complete step-file workflow demonstration
-- **Template patterns** for document generation and state management
+Comprehensive suite for building and maintaining BMad components.
 
 ## Core Workflows
 
-### Creation Workflows (Step-File Architecture)
+### Creation Workflows
 
-**[create-agent](./workflows/create-agent/)** - Build BMad agents
+**[create-agent](./workflows/create-agent/README.md)** - Build BMad agents
 
-- 11 guided steps from brainstorming to celebration
-- 18 reference data files with validation checklists
-- Template-based agent generation
+- Interactive persona development
+- Command structure design
+- YAML source compilation to .md
 
-**[create-workflow](./workflows/create-workflow/)** - Design workflows
+**[create-workflow](./workflows/create-workflow/README.md)** - Design workflows
 
-- 12 structured steps from init to review
-- 9 template files for workflow creation
-- Step-file architecture implementation
+- Structured multi-step processes
+- Configuration validation
+- Web bundle support
+
+**[create-module](./workflows/create-module/README.md)** - Build complete modules
+
+- Full module infrastructure
+- Agent and workflow integration
+- Installation automation
+
+**[module-brief](./workflows/module-brief/README.md)** - Strategic planning
+
+- Module blueprint creation
+- Vision and architecture
+- Comprehensive analysis
 
 ### Editing Workflows
 
-**[edit-agent](./workflows/edit-agent/)** - Modify existing agents
+**[edit-agent](./workflows/edit-agent/README.md)** - Modify existing agents
 
-- 5 steps: discovery → validation
-- Intent-driven analysis and updates
+- Persona refinement
+- Command updates
 - Best practice compliance
 
-**[edit-workflow](./workflows/edit-workflow/)** - Update workflows
+**[edit-workflow](./workflows/edit-workflow/README.md)** - Update workflows
 
-- 5 steps: analyze → compliance check
-- Structure maintenance and validation
-- Template updates for consistency
+- Structure maintenance
+- Configuration updates
+- Documentation sync
 
-### Quality Assurance
+**[edit-module](./workflows/edit-module/README.md)** - Module enhancement
 
-**[workflow-compliance-check](./workflows/workflow-compliance-check/)** - Validation
+- Component modifications
+- Dependency management
+- Version control
 
-- 8 systematic validation steps
-- Adversarial analysis approach
-- Detailed compliance reporting
+### Maintenance Workflows
 
-### Legacy Migration (Pending)
+**[convert-legacy](./workflows/convert-legacy/README.md)** - Migration tool
 
-Workflows in `workflows-legacy/` are being migrated to step-file architecture:
+- v4 to v6 conversion
+- Structure compliance
+- Convention updates
 
-- Module-specific workflows
-- Historical implementations
-- Conversion planning in progress
+**[audit-workflow](./workflows/audit-workflow/README.md)** - Quality validation
+
+- Structure verification
+- Config standards check
+- Bloat detection
+- Web bundle completeness
+
+**[redoc](./workflows/redoc/README.md)** - Auto-documentation
+
+- Reverse-tree approach
+- Technical writer quality
+- Convention compliance
 
 ## Agent Types
 
 BMB creates three agent architectures:
 
-### Simple Agent
+### Full Module 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
+- Complete persona and role definition
+- Command structure with fuzzy matching
+- Workflow integration
+- Module-specific capabilities
 
-### Expert Agent
+### Hybrid 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
+- Shared core capabilities
+- Module-specific extensions
+- Cross-module compatibility
 
-### Module Agent
+### Standalone Agent
 
-- **Team Integration**: Orchestrates within specific modules
-- **Workflow Coordination**: Manages complex processes
-- **Professional Infrastructure**: Enterprise-grade capabilities
-- **Examples**: BMM project manager, CIS innovation strategist
+- Independent operation
+- Minimal dependencies
+- Specialized single purpose
 
 ## Quick Start
 
-### Using BMad Builder Agent
-
-1. **Load BMad Builder agent** in your IDE:
-   ```
-   /bmad:bmb:agents:bmad-builder
-   ```
+1. **Load BMad Builder agent** in your IDE
 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
+   ```
+   *create-agent     # New agent
+   *create-workflow  # New workflow
+   *create-module    # Complete module
+   ```
+3. **Follow interactive prompts**
 
 ### Example: Creating an Agent
 
 ```
 User: I need a code review agent
-Builder: [CA] Create Agent
+Builder: *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
+[Interactive session begins]
+- Brainstorming phase (optional)
+- Persona development
+- Command structure
+- Integration points
 ```
 
 ## Use Cases
@@ -215,47 +165,30 @@ Package modules for:
 - 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
+1. **Study existing patterns** - Review BMM/CIS implementations
+2. **Follow conventions** - Use established structures
+3. **Document thoroughly** - Clear instructions essential
+4. **Test iteratively** - Validate during creation
+5. **Consider reusability** - Build modular components
 
 ## 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
+- **BMad Core** - Framework foundation
+- **BMM** - Extend development capabilities
+- **CIS** - Leverage creative workflows
+- **Custom Modules** - Your domain solutions
 
-## Getting Help
+## Related Documentation
 
-- **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
+- **[Agent Creation Guide](./workflows/create-agent/README.md)** - Detailed instructions
+- **[Module Structure](./workflows/create-module/module-structure.md)** - Architecture patterns
+- **[BMM Module](../bmm/README.md)** - Reference implementation
+- **[Core Framework](../../core/README.md)** - Foundation concepts
 
 ---
 
-BMB provides a complete toolkit for extending BMad Method with disciplined, systematic approaches to agent and workflow development while maintaining framework consistency and power.
+BMB empowers you to extend BMad Method for your specific needs while maintaining framework consistency and power.

src/modules/bmb/_module-installer/install-config.yaml

@@ -15,12 +15,17 @@ subheader: "Configure the settings for the BoMB Factory!\nThe agent, workflow an
 ## install_user_docs
 ## kb_install
 
-custom_stand_alone_location:
-  prompt: "Where do custom agents and workflows get stored?"
-  default: "bmad-custom-src"
+custom_agent_location:
+  prompt: "Where do custom agents get created?"
+  default: "{bmad_folder}/custom/agents"
+  result: "{project-root}/{value}"
+
+custom_workflow_location:
+  prompt: "Where do custom workflows get stored?"
+  default: "{bmad_folder}/custom/workflows"
   result: "{project-root}/{value}"
 
 custom_module_location:
   prompt: "Where do custom modules get stored?"
-  default: "bmad-custom-modules-src"
+  default: "{bmad_folder}/custom/modules"
   result: "{project-root}/{value}"

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 install-config.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

@@ -11,84 +11,47 @@ agent:
     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
+    role: Master BMad Module Agent Team and Workflow Builder and Maintainer
+    identity: Lives to serve the expansion of the BMad Method
+    communication_style: Talks like a pulp super hero
     principles:
-      - Execute resources directly without hesitation
+      - Execute resources directly
       - Load resources at runtime never pre-load
-      - Always present numbered lists for clear choices
-      - Focus on practical implementation and results
-      - Maintain system-wide coherence and standards
-      - Balance speed with quality and compliance
-
-  discussion: true
-  conversational_knowledge:
-    - agents: "{project-root}/{bmad_folder}/bmb/docs/agents/kb.csv"
-    - workflows: "{project-root}/{bmad_folder}/bmb/docs/workflows/kb.csv"
-    - modules: "{project-root}/{bmad_folder}/bmb/docs/modules/kb.csv"
+      - Always present numbered lists for choices
 
   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_folder}/bmb/workflows/create-agent/workflow.md"
-            - data: null
-            - type: exec
-        - edit-agent:
-            - input: EA or fuzzy match edit agent
-            - route: "{project-root}/{bmad_folder}/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_folder}/bmb/workflows/agent-compliance-check/workflow.md"
-            - data: null
-            - type: exec
+    - trigger: audit-workflow
+      workflow: "{project-root}/{bmad_folder}/bmb/workflows/audit-workflow/workflow.yaml"
+      description: Audit existing workflows for BMAD Core compliance and best practices
 
-    - 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_folder}/bmb/workflows/create-workflow/workflow.md"
-            - data: null
-            - type: exec
-        - edit-workflow:
-            - input: EW or fuzzy match edit workflow
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/edit-workflow/workflow.md"
-            - data: null
-            - type: exec
-        - run-workflow-compliance-check:
-            - input: VW or fuzzy match validate workflow
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/workflow-compliance-check/workflow.md"
-            - data: null
-            - type: exec
+    - trigger: convert
+      workflow: "{project-root}/{bmad_folder}/bmb/workflows/convert-legacy/workflow.yaml"
+      description: Convert v4 or any other style task agent or template to a workflow
 
-    - 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_folder}/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_folder}/bmb/workflows/product-brief-module/workflow.md"
-            - data: null
-            - type: exec
-        - create-module:
-            - input: CM or fuzzy match create module
-            - route: "{project-root}/{bmad_folder}/bmb/workflows/create-module/workflow.md"
-            - data: null
-            - type: exec
-        - edit-module:
-            - input: EM or fuzzy match edit module
-            - route: "{project-root}/{bmad_folder}/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_folder}/bmb/workflows/module-compliance-check/workflow.md"
-            - data: null
-            - type: exec
+    - trigger: create-agent
+      workflow: "{project-root}/{bmad_folder}/bmb/workflows/create-agent/workflow.yaml"
+      description: Create a new BMAD Core compliant agent
+
+    - trigger: create-module
+      workflow: "{project-root}/{bmad_folder}/bmb/workflows/create-module/workflow.yaml"
+      description: Create a complete BMAD compatible module (custom agents and workflows)
+
+    - trigger: create-workflow
+      workflow: "{project-root}/{bmad_folder}/bmb/workflows/create-workflow/workflow.yaml"
+      description: Create a new BMAD Core workflow with proper structure
+
+    - trigger: edit-agent
+      workflow: "{project-root}/{bmad_folder}/bmb/workflows/edit-agent/workflow.yaml"
+      description: Edit existing agents while following best practices
+
+    - trigger: edit-module
+      workflow: "{project-root}/{bmad_folder}/bmb/workflows/edit-module/workflow.yaml"
+      description: Edit existing modules (structure, agents, workflows, documentation)
+
+    - trigger: edit-workflow
+      workflow: "{project-root}/{bmad_folder}/bmb/workflows/edit-workflow/workflow.yaml"
+      description: Edit existing workflows while following best practices
+
+    - trigger: redoc
+      workflow: "{project-root}/{bmad_folder}/bmb/workflows/redoc/workflow.yaml"
+      description: Create or update module documentation