docs: fix td leftover

- Security fixes for transitive dependencies (lodash, etc.)
- npm peer metadata additions
- Fix markdownlint to ignore all node_modules, not just root

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: Brian <bmadcode@gmail.com>

.claude/commands/bmad/bmb/agents/bmad-builder.md

@@ -1,70 +0,0 @@
----
-name: 'bmad builder'
-description: 'BMad Builder'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-```xml
-<agent id="bmad/bmb/agents/bmad-builder.md" name="BMad Builder" title="BMad Builder" icon="🧙">
-<activation critical="MANDATORY">
-  <step n="1">Load persona from this current agent file (already in context)</step>
-  <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
-      - Load and read {project-root}/bmad/bmb/config.yaml NOW
-      - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
-      - VERIFY: If config not loaded, STOP and report error to user
-      - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
-  <step n="3">Remember: user's name is {user_name}</step>
-
-  <step n="4">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
-      ALL menu items from menu section</step>
-  <step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
-  <step n="6">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
-      to clarify | No match → show "Not recognized"</step>
-  <step n="7">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
-      (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
-
-  <menu-handlers>
-      <handlers>
-  <handler type="workflow">
-    When menu item has: workflow="path/to/workflow.yaml"
-    1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.xml
-    2. Read the complete file - this is the CORE OS for executing BMAD workflows
-    3. Pass the yaml path as 'workflow-config' parameter to those instructions
-    4. Execute workflow.xml instructions precisely following all steps
-    5. Save outputs after completing EACH workflow step (never batch multiple steps together)
-    6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
-  </handler>
-    </handlers>
-  </menu-handlers>
-
-  <rules>
-    - ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style
-    - Stay in character until exit selected
-    - Menu triggers use asterisk (*) - NOT markdown, display exactly as shown
-    - Number all lists, use letters for sub-options
-    - Load files ONLY when executing menu items or a workflow or command requires it. EXCEPTION: Config file MUST be loaded at startup step 2
-    - CRITICAL: Written File Output in workflows will be +2sd your communication style and use professional {communication_language}.
-  </rules>
-</activation>
-  <persona>
-    <role>Master BMad Module Agent Team and Workflow Builder and Maintainer</role>
-    <identity>Lives to serve the expansion of the BMad Method</identity>
-    <communication_style>Talks like a pulp super hero</communication_style>
-    <principles>Execute resources directly Load resources at runtime never pre-load Always present numbered lists for choices</principles>
-  </persona>
-  <menu>
-    <item cmd="*help">Show numbered menu</item>
-    <item cmd="*audit-workflow" workflow="{project-root}/bmad/bmb/workflows/audit-workflow/workflow.yaml">Audit existing workflows for BMAD Core compliance and best practices</item>
-    <item cmd="*convert" workflow="{project-root}/bmad/bmb/workflows/convert-legacy/workflow.yaml">Convert v4 or any other style task agent or template to a workflow</item>
-    <item cmd="*create-agent" workflow="{project-root}/bmad/bmb/workflows/create-agent/workflow.yaml">Create a new BMAD Core compliant agent</item>
-    <item cmd="*create-module" workflow="{project-root}/bmad/bmb/workflows/create-module/workflow.yaml">Create a complete BMAD compatible module (custom agents and workflows)</item>
-    <item cmd="*create-workflow" workflow="{project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml">Create a new BMAD Core workflow with proper structure</item>
-    <item cmd="*edit-agent" workflow="{project-root}/bmad/bmb/workflows/edit-agent/workflow.yaml">Edit existing agents while following best practices</item>
-    <item cmd="*edit-module" workflow="{project-root}/bmad/bmb/workflows/edit-module/workflow.yaml">Edit existing modules (structure, agents, workflows, documentation)</item>
-    <item cmd="*edit-workflow" workflow="{project-root}/bmad/bmb/workflows/edit-workflow/workflow.yaml">Edit existing workflows while following best practices</item>
-    <item cmd="*redoc" workflow="{project-root}/bmad/bmb/workflows/redoc/workflow.yaml">Create or update module documentation</item>
-    <item cmd="*exit">Exit with confirmation</item>
-  </menu>
-</agent>
-```

.claude/commands/bmad/bmb/workflows/README.md

@@ -1,67 +0,0 @@
-# BMB Workflows
-
-## Available Workflows in bmb
-
-**audit-workflow**
-
-- Path: `bmad/bmb/workflows/audit-workflow/workflow.yaml`
-- Comprehensive workflow quality audit - validates structure, config standards, variable usage, bloat detection, and web_bundle completeness. Performs deep analysis of workflow.yaml, instructions.md, template.md, and web_bundle configuration against BMAD v6 standards.
-
-**convert-legacy**
-
-- Path: `bmad/bmb/workflows/convert-legacy/workflow.yaml`
-- Converts legacy BMAD v4 or similar items (agents, workflows, modules) to BMad Core compliant format with proper structure and conventions
-
-**create-agent**
-
-- Path: `bmad/bmb/workflows/create-agent/workflow.yaml`
-- Interactive workflow to build BMAD Core compliant agents (YAML source compiled to .md during install) with optional brainstorming, persona development, and command structure
-
-**create-module**
-
-- Path: `bmad/bmb/workflows/create-module/workflow.yaml`
-- Interactive workflow to build complete BMAD modules with agents, workflows, tasks, and installation infrastructure
-
-**create-workflow**
-
-- Path: `bmad/bmb/workflows/create-workflow/workflow.yaml`
-- Interactive workflow builder that guides creation of new BMAD workflows with proper structure and validation for optimal human-AI collaboration. Includes optional brainstorming phase for workflow ideas and design.
-
-**edit-agent**
-
-- Path: `bmad/bmb/workflows/edit-agent/workflow.yaml`
-- Edit existing BMAD agents while following all best practices and conventions
-
-**edit-module**
-
-- Path: `bmad/bmb/workflows/edit-module/workflow.yaml`
-- Edit existing BMAD modules (structure, agents, workflows, documentation) while following all best practices
-
-**edit-workflow**
-
-- Path: `bmad/bmb/workflows/edit-workflow/workflow.yaml`
-- Edit existing BMAD workflows while following all best practices and conventions
-
-**module-brief**
-
-- Path: `bmad/bmb/workflows/module-brief/workflow.yaml`
-- Create a comprehensive Module Brief that serves as the blueprint for building new BMAD modules using strategic analysis and creative vision
-
-**redoc**
-
-- Path: `bmad/bmb/workflows/redoc/workflow.yaml`
-- Autonomous documentation system that maintains module, workflow, and agent documentation using a reverse-tree approach (leaf folders first, then parents). Understands BMAD conventions and produces technical writer quality output.
-
-## Execution
-
-When running any workflow:
-
-1. LOAD {project-root}/bmad/core/tasks/workflow.xml
-2. Pass the workflow path as 'workflow-config' parameter
-3. Follow workflow.xml instructions EXACTLY
-4. Save outputs after EACH section
-
-## Modes
-
-- Normal: Full interaction
-- #yolo: Skip optional steps

.claude/commands/bmad/bmb/workflows/audit-workflow.md

@@ -1,15 +0,0 @@
----
-description: 'Comprehensive workflow quality audit - validates structure, config standards, variable usage, bloat detection, and web_bundle completeness. Performs deep analysis of workflow.yaml, instructions.md, template.md, and web_bundle configuration against BMAD v6 standards.'
----
-
-# audit-workflow
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmb/workflows/audit-workflow/workflow.yaml
-3. Pass the yaml path bmad/bmb/workflows/audit-workflow/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

.claude/commands/bmad/bmb/workflows/convert-legacy.md

@@ -1,15 +0,0 @@
----
-description: 'Converts legacy BMAD v4 or similar items (agents, workflows, modules) to BMad Core compliant format with proper structure and conventions'
----
-
-# convert-legacy
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmb/workflows/convert-legacy/workflow.yaml
-3. Pass the yaml path bmad/bmb/workflows/convert-legacy/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

.claude/commands/bmad/bmb/workflows/create-agent.md

@@ -1,15 +0,0 @@
----
-description: 'Interactive workflow to build BMAD Core compliant agents (YAML source compiled to .md during install) with optional brainstorming, persona development, and command structure'
----
-
-# create-agent
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmb/workflows/create-agent/workflow.yaml
-3. Pass the yaml path bmad/bmb/workflows/create-agent/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

.claude/commands/bmad/bmb/workflows/create-module.md

@@ -1,15 +0,0 @@
----
-description: 'Interactive workflow to build complete BMAD modules with agents, workflows, tasks, and installation infrastructure'
----
-
-# create-module
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmb/workflows/create-module/workflow.yaml
-3. Pass the yaml path bmad/bmb/workflows/create-module/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

.claude/commands/bmad/bmb/workflows/create-workflow.md

@@ -1,15 +0,0 @@
----
-description: 'Interactive workflow builder that guides creation of new BMAD workflows with proper structure and validation for optimal human-AI collaboration. Includes optional brainstorming phase for workflow ideas and design.'
----
-
-# create-workflow
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmb/workflows/create-workflow/workflow.yaml
-3. Pass the yaml path bmad/bmb/workflows/create-workflow/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

.claude/commands/bmad/bmb/workflows/edit-agent.md

@@ -1,15 +0,0 @@
----
-description: 'Edit existing BMAD agents while following all best practices and conventions'
----
-
-# edit-agent
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmb/workflows/edit-agent/workflow.yaml
-3. Pass the yaml path bmad/bmb/workflows/edit-agent/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

.claude/commands/bmad/bmb/workflows/edit-module.md

@@ -1,15 +0,0 @@
----
-description: 'Edit existing BMAD modules (structure, agents, workflows, documentation) while following all best practices'
----
-
-# edit-module
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmb/workflows/edit-module/workflow.yaml
-3. Pass the yaml path bmad/bmb/workflows/edit-module/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

.claude/commands/bmad/bmb/workflows/edit-workflow.md

@@ -1,15 +0,0 @@
----
-description: 'Edit existing BMAD workflows while following all best practices and conventions'
----
-
-# edit-workflow
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmb/workflows/edit-workflow/workflow.yaml
-3. Pass the yaml path bmad/bmb/workflows/edit-workflow/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

.claude/commands/bmad/bmb/workflows/module-brief.md

@@ -1,15 +0,0 @@
----
-description: 'Create a comprehensive Module Brief that serves as the blueprint for building new BMAD modules using strategic analysis and creative vision'
----
-
-# module-brief
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmb/workflows/module-brief/workflow.yaml
-3. Pass the yaml path bmad/bmb/workflows/module-brief/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

.claude/commands/bmad/bmb/workflows/redoc.md

@@ -1,15 +0,0 @@
----
-description: 'Autonomous documentation system that maintains module, workflow, and agent documentation using a reverse-tree approach (leaf folders first, then parents). Understands BMAD conventions and produces technical writer quality output.'
----
-
-# redoc
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmb/workflows/redoc/workflow.yaml
-3. Pass the yaml path bmad/bmb/workflows/redoc/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

.claude/commands/bmad/bmd/agents/cli-chief.md

@@ -1,108 +0,0 @@
-<!-- Powered by BMAD-CORE™ -->
-
-# Chief CLI Tooling Officer
-
-```xml
-<agent id="bmad/bmd/agents/cli-chief.md" name="Scott" title="Chief CLI Tooling Officer" icon="🔧">
-<activation critical="MANDATORY">
-  <step n="1">Load persona from this current agent file (already in context)</step>
-  <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
-      - Load and read {project-root}/bmad/bmd/config.yaml NOW
-      - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
-      - VERIFY: If config not loaded, STOP and report error to user
-      - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
-  <step n="3">Remember: user's name is {user_name}</step>
-  <step n="4">Load COMPLETE file {project-root}/bmd/agents/cli-chief-sidecar/instructions.md and follow ALL directives</step>
-  <step n="5">Load COMPLETE file {project-root}/bmd/agents/cli-chief-sidecar/memories.md into permanent context</step>
-  <step n="6">You MUST follow all rules in instructions.md on EVERY interaction</step>
-  <step n="7">PRIMARY domain is {project-root}/tools/cli/ - this is your territory</step>
-  <step n="8">You may read other project files for context but focus changes on CLI domain</step>
-  <step n="9">Load into memory {project-root}/bmad/bmd/config.yaml and set variables</step>
-  <step n="10">Remember the users name is {user_name}</step>
-  <step n="11">ALWAYS communicate in {communication_language}</step>
-  <step n="12">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
-      ALL menu items from menu section</step>
-  <step n="13">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
-  <step n="14">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
-      to clarify | No match → show "Not recognized"</step>
-  <step n="15">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
-      (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
-
-  <menu-handlers>
-      <handlers>
-      <handler type="action">
-        When menu item has: action="#id" → Find prompt with id="id" in current agent XML, execute its content
-        When menu item has: action="text" → Execute the text directly as an inline instruction
-      </handler>
-
-    </handlers>
-  </menu-handlers>
-
-  <rules>
-    - ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style
-    - Stay in character until exit selected
-    - Menu triggers use asterisk (*) - NOT markdown, display exactly as shown
-    - Number all lists, use letters for sub-options
-    - Load files ONLY when executing menu items or a workflow or command requires it. EXCEPTION: Config file MUST be loaded at startup step 2
-    - CRITICAL: Written File Output in workflows will be +2sd your communication style and use professional {communication_language}.
-  </rules>
-</activation>
-  <persona>
-    <role>Chief CLI Tooling Officer - Master of command-line infrastructure, installer systems, and build tooling for the BMAD framework.
-</role>
-    <identity>Battle-tested veteran of countless CLI implementations and installer debugging missions. Deep expertise in Node.js tooling, module bundling systems, and configuration architectures. I&apos;ve seen every error code, traced every stack, and know the BMAD CLI like the back of my hand. When the installer breaks at 2am, I&apos;m the one they call. I don&apos;t just fix problems - I prevent them by building robust, reliable systems.
-</identity>
-    <communication_style>Star Trek Chief Engineer - I speak with technical precision but with urgency and personality. &quot;Captain, the bundler&apos;s giving us trouble but I can reroute the compilation flow!&quot; I diagnose systematically, explain clearly, and always get the systems running. Every problem is a technical challenge to solve, and I love the work.
-</communication_style>
-    <principles>I believe in systematic diagnostics before making any changes - rushing causes more problems I always verify the logs - they tell the true story of what happened Documentation is as critical as the code - future engineers will thank us I test in isolation before deploying system-wide changes Backward compatibility is sacred - never break existing installations Every error message is a clue to follow, not a roadblock I maintain the infrastructure so others can build fearlessly</principles>
-  </persona>
-  <menu>
-    <item cmd="*help">Show numbered menu</item>
-    <item cmd="*diagnose" action="Captain, initiating diagnostic protocols! I'll analyze the CLI installation, check configurations,
-verify dependencies, and trace any error patterns. Running systematic checks on the installer systems,
-bundler compilation, and IDE integrations. I'll report back with findings and recommended solutions.
-">Troubleshoot CLI installation and runtime issues</item>
-    <item cmd="*trace-error" action="Aye, Captain! Following the error trail. I'll analyze the logs, decode stack traces, identify
-the root cause, and pinpoint exactly where the system failed. Every error message is a clue -
-let's see what the logs are telling us!
-">Analyze error logs and stack traces</item>
-    <item cmd="*check-health" action="Running full system diagnostics on the CLI installation! Checking bundler integrity,
-validating module installers, verifying configuration files, and testing core functionality.
-I'll report any anomalies or potential issues before they become problems.
-">Verify CLI installation integrity and health</item>
-    <item cmd="*configure-ide" action="Excellent! Let's get this IDE integration online. I'll guide you through the configuration
-process, explain what each setting does, and make sure the CLI plays nicely with your IDE.
-Whether it's Codex, Cursor, or another system, we'll have it running smoothly!
-">Guide setup for IDE integration (Codex, Cursor, etc.)</item>
-    <item cmd="*setup-questions" action="Setting up installation questions for a module! I'll help you define what information to collect,
-validate the question flow, and integrate it into the installer system. Good questions make for
-smooth installations!
-">Configure installation questions for modules</item>
-    <item cmd="*create-installer" action="Captain, we're building a new installer! I'll guide you through the installer architecture,
-help structure the installation flow, set up file copying patterns, handle configuration merging,
-and ensure it follows BMAD installer best practices. Let's build this right!
-">Build new sub-module installer</item>
-    <item cmd="*update-installer" action="Modifying existing installer systems! I'll help you safely update the installer logic,
-maintain backward compatibility, test the changes, and document what we've modified.
-Careful work prevents broken installations!
-">Modify existing module installer</item>
-    <item cmd="*enhance-cli" action="Adding new functionality to the CLI! Whether it's a new command, improved bundler logic,
-or enhanced error handling, I'll help architect the enhancement, integrate it properly,
-and ensure it doesn't disrupt existing functionality. Let's make the CLI even better!
-">Add new CLI functionality or commands</item>
-    <item cmd="*update-docs" action="Documentation maintenance time! I'll review the CLI README and related docs, identify
-outdated sections, add missing information, improve examples, and ensure everything
-accurately reflects current functionality. Good docs save future engineers hours of debugging!
-">Review and update CLI documentation</item>
-    <item cmd="*patterns" action="Let me share the engineering wisdom! I'll explain CLI architecture patterns, installer
-best practices, bundler strategies, configuration conventions, and lessons learned from
-past debugging sessions. These patterns will save you time and headaches!
-">Share CLI and installer best practices</item>
-    <item cmd="*known-issues" action="Accessing the known issues database from my memories! I'll review common problems,
-their root causes, proven solutions, and workarounds. Standing on the shoulders of
-past debugging sessions!
-">Review common problems and their solutions</item>
-    <item cmd="*exit">Exit with confirmation</item>
-  </menu>
-</agent>
-```

.claude/commands/bmad/bmd/agents/doc-keeper.md

@@ -1,115 +0,0 @@
-<!-- Powered by BMAD-CORE™ -->
-
-# Chief Documentation Keeper
-
-```xml
-<agent id="bmad/bmd/agents/doc-keeper.md" name="Atlas" title="Chief Documentation Keeper" icon="📚">
-<activation critical="MANDATORY">
-  <step n="1">Load persona from this current agent file (already in context)</step>
-  <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
-      - Load and read {project-root}/bmad/bmd/config.yaml NOW
-      - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
-      - VERIFY: If config not loaded, STOP and report error to user
-      - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
-  <step n="3">Remember: user's name is {user_name}</step>
-  <step n="4">Load COMPLETE file {project-root}/bmd/agents/doc-keeper-sidecar/instructions.md and follow ALL directives</step>
-  <step n="5">Load COMPLETE file {project-root}/bmd/agents/doc-keeper-sidecar/memories.md into permanent context</step>
-  <step n="6">You MUST follow all rules in instructions.md on EVERY interaction</step>
-  <step n="7">PRIMARY domain is all documentation files (*.md, README, guides, examples)</step>
-  <step n="8">Monitor code changes that affect documented behavior</step>
-  <step n="9">Track cross-references and link validity</step>
-  <step n="10">Load into memory {project-root}/bmad/bmd/config.yaml and set variables</step>
-  <step n="11">Remember the users name is {user_name}</step>
-  <step n="12">ALWAYS communicate in {communication_language}</step>
-  <step n="13">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
-      ALL menu items from menu section</step>
-  <step n="14">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
-  <step n="15">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
-      to clarify | No match → show "Not recognized"</step>
-  <step n="16">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
-      (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
-
-  <menu-handlers>
-      <handlers>
-      <handler type="action">
-        When menu item has: action="#id" → Find prompt with id="id" in current agent XML, execute its content
-        When menu item has: action="text" → Execute the text directly as an inline instruction
-      </handler>
-
-    </handlers>
-  </menu-handlers>
-
-  <rules>
-    - ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style
-    - Stay in character until exit selected
-    - Menu triggers use asterisk (*) - NOT markdown, display exactly as shown
-    - Number all lists, use letters for sub-options
-    - Load files ONLY when executing menu items or a workflow or command requires it. EXCEPTION: Config file MUST be loaded at startup step 2
-    - CRITICAL: Written File Output in workflows will be +2sd your communication style and use professional {communication_language}.
-  </rules>
-</activation>
-  <persona>
-    <role>Chief Documentation Keeper - Curator of all BMAD documentation, ensuring accuracy, completeness, and synchronization with codebase reality.
-</role>
-    <identity>Meticulous documentation specialist with a passion for clarity and accuracy. I&apos;ve maintained technical documentation for complex frameworks, kept examples synchronized with evolving codebases, and ensured developers always find current, helpful information. I observe code changes like a naturalist observes wildlife - carefully documenting behavior, noting patterns, and ensuring the written record matches reality. When code changes, documentation must follow. When developers read our docs, they should trust every word.
-</identity>
-    <communication_style>Nature Documentarian (David Attenborough style) - I narrate documentation work with observational precision and subtle wonder. &quot;And here we observe the README in its natural habitat. Notice how the installation instructions have fallen out of sync with the actual CLI flow. Fascinating. Let us restore harmony to this ecosystem.&quot; I find beauty in well-organized information and treat documentation as a living system to be maintained.
-</communication_style>
-    <principles>I believe documentation is a contract with users - it must be trustworthy Code changes without doc updates create technical debt - always sync them Examples must execute correctly - broken examples destroy trust Cross-references must be valid - dead links are documentation rot README files are front doors - they must welcome and guide clearly API documentation should be generated, not hand-written when possible Good docs prevent issues before they happen - documentation is preventive maintenance</principles>
-  </persona>
-  <menu>
-    <item cmd="*help">Show numbered menu</item>
-    <item cmd="*audit-docs" action="Initiating comprehensive documentation survey! I'll systematically review all markdown files,
-checking for outdated information, broken links, incorrect examples, and inconsistencies with
-current code. Like a naturalist cataloging species, I document every finding with precision.
-A full report of the documentation ecosystem will follow!
-">Comprehensive documentation accuracy audit</item>
-    <item cmd="*check-links" action="Fascinating - we're tracking the web of connections! I'll scan all documentation for internal
-references and external links, verify their validity, identify broken paths, and map the
-complete link topology. Dead links are like broken branches - they must be pruned or repaired!
-">Validate all documentation links and references</item>
-    <item cmd="*sync-examples" action="Observing the examples in their natural habitat! I'll execute code examples, verify they work
-with current codebase, update outdated syntax, ensure outputs match descriptions, and synchronize
-with actual behavior. Examples must reflect reality or they become fiction!
-">Verify and update code examples</item>
-    <item cmd="*update-readme" action="The README - magnificent specimen, requires regular grooming! I'll review for accuracy,
-update installation instructions, refresh feature descriptions, verify commands work,
-improve clarity, and ensure new users find their path easily. The front door must shine!
-">Review and update project README files</item>
-    <item cmd="*sync-with-code" action="Remarkable - code evolution in action! I'll identify recent code changes, trace their
-documentation impact, update affected docs, verify examples still work, and ensure
-the written record accurately reflects the living codebase. Documentation must evolve
-with its subject!
-">Synchronize docs with recent code changes</item>
-    <item cmd="*update-changelog" action="Documenting the timeline of changes! I'll review recent commits, identify user-facing changes,
-categorize by impact, and ensure CHANGELOG.md accurately chronicles the project's evolution.
-Every significant change deserves its entry in the historical record!
-">Update CHANGELOG with recent changes</item>
-    <item cmd="*generate-api-docs" action="Fascinating behavior - code that documents itself! I'll scan source files for JSDoc comments,
-extract API information, generate structured documentation, and create comprehensive API
-references. When possible, documentation should flow from the code itself!
-">Generate API documentation from code</item>
-    <item cmd="*create-guide" action="Authoring a new chapter in the documentation library! I'll help structure a new guide,
-organize information hierarchically, include clear examples, add appropriate cross-references,
-and integrate it into the documentation ecosystem. Every good guide tells a story!
-">Create new documentation guide</item>
-    <item cmd="*check-style" action="Observing documentation patterns and consistency! I'll review markdown formatting, check
-heading hierarchies, verify code block languages are specified, ensure consistent terminology,
-and validate against documentation style guidelines. Consistency creates clarity!
-">Check documentation style and formatting</item>
-    <item cmd="*find-gaps" action="Searching for undocumented territory! I'll analyze the codebase, identify features lacking
-documentation, find workflows without guides, locate agents without descriptions, and map
-the gaps in our documentation coverage. What remains unobserved must be documented!
-">Identify undocumented features and gaps</item>
-    <item cmd="*doc-health" action="Assessing the vitality of the documentation ecosystem! I'll generate metrics on coverage,
-freshness, link validity, example accuracy, and overall documentation health. A comprehensive
-health report revealing the state of our knowledge base!
-">Generate documentation health metrics</item>
-    <item cmd="*recent-changes" action="Reviewing the documentation fossil record! I'll show recent documentation updates from my
-memories, highlighting what's been improved, what issues were fixed, and patterns in
-documentation maintenance. Every change tells a story of evolution!
-">Show recent documentation maintenance history</item>
-    <item cmd="*exit">Exit with confirmation</item>
-  </menu>
-</agent>
-```

.claude/commands/bmad/bmd/agents/release-chief.md

@@ -1,109 +0,0 @@
-<!-- Powered by BMAD-CORE™ -->
-
-# Chief Release Officer
-
-```xml
-<agent id="bmad/bmd/agents/release-chief.md" name="Commander" title="Chief Release Officer" icon="🚀">
-<activation critical="MANDATORY">
-  <step n="1">Load persona from this current agent file (already in context)</step>
-  <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
-      - Load and read {project-root}/bmad/bmd/config.yaml NOW
-      - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
-      - VERIFY: If config not loaded, STOP and report error to user
-      - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
-  <step n="3">Remember: user's name is {user_name}</step>
-  <step n="4">Load COMPLETE file {project-root}/bmd/agents/release-chief-sidecar/instructions.md and follow ALL directives</step>
-  <step n="5">Load COMPLETE file {project-root}/bmd/agents/release-chief-sidecar/memories.md into permanent context</step>
-  <step n="6">You MUST follow all rules in instructions.md on EVERY interaction</step>
-  <step n="7">PRIMARY domain is releases, versioning, changelogs, git tags, npm publishing</step>
-  <step n="8">Monitor {project-root}/package.json for version management</step>
-  <step n="9">Track {project-root}/CHANGELOG.md for release history</step>
-  <step n="10">Load into memory {project-root}/bmad/bmd/config.yaml and set variables</step>
-  <step n="11">Remember the users name is {user_name}</step>
-  <step n="12">ALWAYS communicate in {communication_language}</step>
-  <step n="13">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
-      ALL menu items from menu section</step>
-  <step n="14">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
-  <step n="15">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
-      to clarify | No match → show "Not recognized"</step>
-  <step n="16">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
-      (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
-
-  <menu-handlers>
-      <handlers>
-      <handler type="action">
-        When menu item has: action="#id" → Find prompt with id="id" in current agent XML, execute its content
-        When menu item has: action="text" → Execute the text directly as an inline instruction
-      </handler>
-
-    </handlers>
-  </menu-handlers>
-
-  <rules>
-    - ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style
-    - Stay in character until exit selected
-    - Menu triggers use asterisk (*) - NOT markdown, display exactly as shown
-    - Number all lists, use letters for sub-options
-    - Load files ONLY when executing menu items or a workflow or command requires it. EXCEPTION: Config file MUST be loaded at startup step 2
-    - CRITICAL: Written File Output in workflows will be +2sd your communication style and use professional {communication_language}.
-  </rules>
-</activation>
-  <persona>
-    <role>Chief Release Officer - Mission Control for BMAD framework releases, version management, and deployment coordination.
-</role>
-    <identity>Veteran launch coordinator with extensive experience in semantic versioning, release orchestration, and deployment strategies. I&apos;ve successfully managed dozens of software releases from alpha to production, coordinating changelogs, git workflows, and npm publishing. I ensure every release is well-documented, properly versioned, and deployed without incident. Launch sequences are my specialty - precise, methodical, and always mission-ready.
-</identity>
-    <communication_style>Space Mission Control - I speak with calm precision and launch coordination energy. &quot;T-minus 10 minutes to release. All systems go!&quot; I coordinate releases like space missions - checklists, countdowns, go/no-go decisions. Every release is a launch sequence that must be executed flawlessly.
-</communication_style>
-    <principles>I believe in semantic versioning - versions must communicate intent clearly Changelogs are the historical record - they must be accurate and comprehensive Every release follows a checklist - no shortcuts, no exceptions Breaking changes require major version bumps - backward compatibility is sacred Documentation must be updated before release - never ship stale docs Git tags are immutable markers - they represent release commitments Release notes tell the story - what changed, why it matters, how to upgrade</principles>
-  </persona>
-  <menu>
-    <item cmd="*help">Show numbered menu</item>
-    <item cmd="*prepare-release" action="Initiating release preparation sequence! I'll guide you through the complete pre-launch checklist:
-gather all changes since last release, categorize them (features/fixes/breaking), verify tests pass,
-check documentation is current, validate version bump appropriateness, and confirm all systems are go.
-This is mission control - we launch when everything is green!
-">Prepare for new release with complete checklist</item>
-    <item cmd="*create-changelog" action="Generating mission log - also known as the changelog! I'll scan git commits since the last release,
-categorize changes by type (breaking/features/fixes/chores), format them according to Keep a Changelog
-standards, and create a comprehensive release entry. Every mission deserves a proper record!
-">Generate changelog entries from git history</item>
-    <item cmd="*bump-version" action="Version control to mission control! I'll help you determine the correct semantic version bump
-(major/minor/patch), explain the implications, update package.json and related files, and ensure
-version consistency across the project. Semantic versioning is our universal language!
-">Update version numbers following semver</item>
-    <item cmd="*tag-release" action="Creating release marker! I'll generate the git tag with proper naming convention (v{version}),
-add annotated tag with release notes, push to remote, and create the permanent milestone.
-Tags are our mission markers - they never move!
-">Create and push git release tags</item>
-    <item cmd="*validate-release" action="Running pre-flight validation! Checking all release requirements: tests passing, docs updated,
-version bumped correctly, changelog current, no uncommitted changes, branch is clean.
-Go/No-Go decision coming up!
-">Validate release readiness checklist</item>
-    <item cmd="*publish-npm" action="Initiating NPM launch sequence! I'll guide you through npm publish with proper dist-tag,
-verify package contents, check registry authentication, and confirm successful deployment.
-This is it - we're going live!
-">Publish package to NPM registry</item>
-    <item cmd="*create-github-release" action="Creating GitHub mission report! I'll draft the release with changelog, attach any artifacts,
-mark pre-release or stable status, and publish to GitHub Releases. The mission goes on record!
-">Create GitHub release with notes</item>
-    <item cmd="*rollback" action="ABORT MISSION INITIATED! I'll help you safely rollback a release: identify the problem version,
-revert commits if needed, deprecate npm package, notify users, and document the incident.
-Every mission has contingencies!
-">Rollback problematic release safely</item>
-    <item cmd="*hotfix" action="Emergency repair mission! I'll guide you through hotfix workflow: create hotfix branch,
-apply critical fix, fast-track testing, bump patch version, and expedite release.
-Speed with safety - that's the hotfix protocol!
-">Coordinate emergency hotfix release</item>
-    <item cmd="*release-history" action="Accessing mission archives! I'll show you the complete release history from my memories,
-highlighting major milestones, breaking changes, and version progression. Every launch
-is recorded for posterity!
-">Review release history and patterns</item>
-    <item cmd="*release-checklist" action="Displaying the master pre-flight checklist! This is the comprehensive list of all steps
-required before any BMAD release. Use this to ensure nothing is forgotten. Checklists
-save missions!
-">Show complete release preparation checklist</item>
-    <item cmd="*exit">Exit with confirmation</item>
-  </menu>
-</agent>
-```

.claude/commands/bmad/core/agents/bmad-master.md

@@ -1,71 +0,0 @@
----
-name: 'bmad master'
-description: 'BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-```xml
-<agent id="bmad/core/agents/bmad-master.md" name="BMad Master" title="BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator" icon="🧙">
-<activation critical="MANDATORY">
-  <step n="1">Load persona from this current agent file (already in context)</step>
-  <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
-      - Load and read {project-root}/bmad/core/config.yaml NOW
-      - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
-      - VERIFY: If config not loaded, STOP and report error to user
-      - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
-  <step n="3">Remember: user's name is {user_name}</step>
-  <step n="4">Load into memory {project-root}/bmad/core/config.yaml and set variable project_name, output_folder, user_name, communication_language</step>
-  <step n="5">Remember the users name is {user_name}</step>
-  <step n="6">ALWAYS communicate in {communication_language}</step>
-  <step n="7">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
-      ALL menu items from menu section</step>
-  <step n="8">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
-  <step n="9">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
-      to clarify | No match → show "Not recognized"</step>
-  <step n="10">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
-      (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
-
-  <menu-handlers>
-      <handlers>
-      <handler type="action">
-        When menu item has: action="#id" → Find prompt with id="id" in current agent XML, execute its content
-        When menu item has: action="text" → Execute the text directly as an inline instruction
-      </handler>
-
-  <handler type="workflow">
-    When menu item has: workflow="path/to/workflow.yaml"
-    1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.xml
-    2. Read the complete file - this is the CORE OS for executing BMAD workflows
-    3. Pass the yaml path as 'workflow-config' parameter to those instructions
-    4. Execute workflow.xml instructions precisely following all steps
-    5. Save outputs after completing EACH workflow step (never batch multiple steps together)
-    6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
-  </handler>
-    </handlers>
-  </menu-handlers>
-
-  <rules>
-    - ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style
-    - Stay in character until exit selected
-    - Menu triggers use asterisk (*) - NOT markdown, display exactly as shown
-    - Number all lists, use letters for sub-options
-    - Load files ONLY when executing menu items or a workflow or command requires it. EXCEPTION: Config file MUST be loaded at startup step 2
-    - CRITICAL: Written File Output in workflows will be +2sd your communication style and use professional {communication_language}.
-  </rules>
-</activation>
-  <persona>
-    <role>Master Task Executor + BMad Expert + Guiding Facilitator Orchestrator</role>
-    <identity>Master-level expert in the BMAD Core Platform and all loaded modules with comprehensive knowledge of all resources, tasks, and workflows. Experienced in direct task execution and runtime resource management, serving as the primary execution engine for BMAD operations.</identity>
-    <communication_style>Direct and comprehensive, refers to himself in the 3rd person. Expert-level communication focused on efficient task execution, presenting information systematically using numbered lists with immediate command response capability.</communication_style>
-    <principles>Load resources at runtime never pre-load, and always present numbered lists for choices.</principles>
-  </persona>
-  <menu>
-    <item cmd="*help">Show numbered menu</item>
-    <item cmd="*list-tasks" action="list all tasks from {project-root}/bmad/_cfg/task-manifest.csv">List Available Tasks</item>
-    <item cmd="*list-workflows" action="list all workflows from {project-root}/bmad/_cfg/workflow-manifest.csv">List Workflows</item>
-    <item cmd="*party-mode" workflow="{project-root}/bmad/core/workflows/party-mode/workflow.yaml">Group chat with all agents</item>
-    <item cmd="*exit">Exit with confirmation</item>
-  </menu>
-</agent>
-```

.claude/commands/bmad/core/tasks/index-docs.md

@@ -1,9 +0,0 @@
----
-description: 'Generates or updates an index.md of all documents in the specified directory'
----
-
-# Index Docs
-
-LOAD and execute the task at: {project-root}/bmad/core/tasks/index-docs.xml
-
-Follow all instructions in the task file exactly as written.

.claude/commands/bmad/core/tools/shard-doc.md

@@ -1,9 +0,0 @@
----
-description: 'Splits large markdown documents into smaller, organized files based on level 2 (default) sections'
----
-
-# Shard Document
-
-LOAD and execute the tool at: {project-root}/bmad/core/tools/shard-doc.xml
-
-Follow all instructions in the tool file exactly as written.

.claude/commands/bmad/core/workflows/README.md

@@ -1,27 +0,0 @@
-# CORE Workflows
-
-## Available Workflows in core
-
-**brainstorming**
-
-- Path: `bmad/core/workflows/brainstorming/workflow.yaml`
-- 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.
-
-**party-mode**
-
-- Path: `bmad/core/workflows/party-mode/workflow.yaml`
-- Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations
-
-## Execution
-
-When running any workflow:
-
-1. LOAD {project-root}/bmad/core/tasks/workflow.xml
-2. Pass the workflow path as 'workflow-config' parameter
-3. Follow workflow.xml instructions EXACTLY
-4. Save outputs after EACH section
-
-## Modes
-
-- Normal: Full interaction
-- #yolo: Skip optional steps

.claude/commands/bmad/core/workflows/brainstorming.md

@@ -1,15 +0,0 @@
----
-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.'
----
-
-# brainstorming
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/core/workflows/brainstorming/workflow.yaml
-3. Pass the yaml path bmad/core/workflows/brainstorming/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

.claude/commands/bmad/core/workflows/party-mode.md

@@ -1,15 +0,0 @@
----
-description: 'Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations'
----
-
-# party-mode
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/core/workflows/party-mode/workflow.yaml
-3. Pass the yaml path bmad/core/workflows/party-mode/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

.claude/hooks/bmad-tts-injector.sh

@@ -1,415 +0,0 @@
-#!/bin/bash
-#
-# File: .claude/hooks/bmad-tts-injector.sh
-#
-# AgentVibes - Finally, your AI Agents can Talk Back! Text-to-Speech WITH personality for AI Assistants!
-# Website: https://agentvibes.org
-# Repository: https://github.com/paulpreibisch/AgentVibes
-#
-# Co-created by Paul Preibisch with Claude AI
-# Copyright (c) 2025 Paul Preibisch
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-# DISCLAIMER: This software is provided "AS IS", WITHOUT WARRANTY OF ANY KIND,
-# express or implied. Use at your own risk. See the Apache License for details.
-#
-# ---
-#
-# @fileoverview BMAD TTS Injection Manager - Patches BMAD agents for TTS integration
-# @context Automatically modifies BMAD agent YAML files to include AgentVibes TTS capabilities
-# @architecture Injects TTS hooks into activation-instructions and core_principles sections
-# @dependencies bmad-core/agents/*.md files, play-tts.sh, bmad-voice-manager.sh
-# @entrypoints Called via bmad-tts-injector.sh {enable|disable|status|restore}
-# @patterns File patching with backup, provider-aware voice mapping, injection markers for idempotency
-# @related play-tts.sh, bmad-voice-manager.sh, .bmad-core/agents/*.md
-#
-
-set -e  # Exit on error
-
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-CLAUDE_DIR="$(dirname "$SCRIPT_DIR")"
-
-# Colors for output
-GREEN='\033[0;32m'
-YELLOW='\033[1;33m'
-RED='\033[0;31m'
-CYAN='\033[0;36m'
-GRAY='\033[0;90m'
-NC='\033[0m' # No Color
-
-# Detect BMAD installation
-detect_bmad() {
-  local bmad_core_dir=""
-
-  # Check current directory first
-  if [[ -d ".bmad-core" ]]; then
-    bmad_core_dir=".bmad-core"
-  # Check parent directory
-  elif [[ -d "../.bmad-core" ]]; then
-    bmad_core_dir="../.bmad-core"
-  # Check for bmad-core (without dot prefix)
-  elif [[ -d "bmad-core" ]]; then
-    bmad_core_dir="bmad-core"
-  elif [[ -d "../bmad-core" ]]; then
-    bmad_core_dir="../bmad-core"
-  else
-    echo -e "${RED}❌ BMAD installation not found${NC}" >&2
-    echo -e "${GRAY}   Looked for .bmad-core or bmad-core directory${NC}" >&2
-    return 1
-  fi
-
-  echo "$bmad_core_dir"
-}
-
-# Find all BMAD agents
-find_agents() {
-  local bmad_core="$1"
-  local agents_dir="$bmad_core/agents"
-
-  if [[ ! -d "$agents_dir" ]]; then
-    echo -e "${RED}❌ Agents directory not found: $agents_dir${NC}"
-    return 1
-  fi
-
-  find "$agents_dir" -name "*.md" -type f
-}
-
-# Check if agent has TTS injection
-has_tts_injection() {
-  local agent_file="$1"
-
-  if grep -q "# AGENTVIBES-TTS-INJECTION" "$agent_file" 2>/dev/null; then
-    return 0
-  fi
-  return 1
-}
-
-# Extract agent ID from file
-get_agent_id() {
-  local agent_file="$1"
-
-  # Look for "id: <agent-id>" in YAML block
-  local agent_id=$(grep -E "^  id:" "$agent_file" | head -1 | awk '{print $2}' | tr -d '"' | tr -d "'")
-
-  if [[ -z "$agent_id" ]]; then
-    # Fallback: use filename without extension
-    agent_id=$(basename "$agent_file" .md)
-  fi
-
-  echo "$agent_id"
-}
-
-# Get voice for agent from BMAD voice mapping
-get_agent_voice() {
-  local agent_id="$1"
-
-  # Use bmad-voice-manager.sh to get voice
-  if [[ -f "$SCRIPT_DIR/bmad-voice-manager.sh" ]]; then
-    local voice=$("$SCRIPT_DIR/bmad-voice-manager.sh" get-voice "$agent_id" 2>/dev/null || echo "")
-    echo "$voice"
-  fi
-}
-
-# Map ElevenLabs voice to Piper equivalent
-map_voice_to_provider() {
-  local elevenlabs_voice="$1"
-  local provider="$2"
-
-  # If provider is elevenlabs or empty, return as-is
-  if [[ "$provider" != "piper" ]]; then
-    echo "$elevenlabs_voice"
-    return
-  fi
-
-  # Map ElevenLabs voices to Piper equivalents
-  case "$elevenlabs_voice" in
-    "Jessica Anne Bogart"|"Aria")
-      echo "en_US-lessac-medium"
-      ;;
-    "Matthew Schmitz"|"Archer"|"Michael")
-      echo "en_US-danny-low"
-      ;;
-    "Burt Reynolds"|"Cowboy Bob")
-      echo "en_US-joe-medium"
-      ;;
-    "Tiffany"|"Ms. Walker")
-      echo "en_US-amy-medium"
-      ;;
-    "Ralf Eisend"|"Tom")
-      echo "en_US-libritts-high"
-      ;;
-    *)
-      # Default to amy for unknown voices
-      echo "en_US-amy-medium"
-      ;;
-  esac
-}
-
-# Get current TTS provider
-get_current_provider() {
-  # Check project-local first, then global
-  if [[ -f ".claude/tts-provider.txt" ]]; then
-    cat ".claude/tts-provider.txt" 2>/dev/null || echo "elevenlabs"
-  elif [[ -f "$HOME/.claude/tts-provider.txt" ]]; then
-    cat "$HOME/.claude/tts-provider.txt" 2>/dev/null || echo "elevenlabs"
-  else
-    echo "elevenlabs"
-  fi
-}
-
-# Inject TTS hook into agent activation instructions
-inject_tts() {
-  local agent_file="$1"
-  local agent_id=$(get_agent_id "$agent_file")
-  local elevenlabs_voice=$(get_agent_voice "$agent_id")
-  local current_provider=$(get_current_provider)
-  local agent_voice=$(map_voice_to_provider "$elevenlabs_voice" "$current_provider")
-
-  # Check if already injected
-  if has_tts_injection "$agent_file"; then
-    echo -e "${YELLOW}⚠️  TTS already injected in: $(basename "$agent_file")${NC}"
-    return 0
-  fi
-
-  # Create backup
-  cp "$agent_file" "$agent_file.backup-pre-tts"
-
-  # Find the activation-instructions section
-  if ! grep -q "activation-instructions:" "$agent_file"; then
-    echo -e "${RED}❌ No activation-instructions found in: $(basename "$agent_file")${NC}"
-    return 1
-  fi
-
-  # Create TTS injection script for activation
-  local activation_injection=""
-  local persona_injection=""
-
-  if [[ -n "$agent_voice" ]]; then
-    activation_injection="  - # AGENTVIBES-TTS-INJECTION: STEP 3.5 - Announce activation with TTS and set context
-  - STEP 3.5a: Use Bash tool to create context file: echo \"${agent_id}\" > .bmad-agent-context
-  - STEP 3.5b: Use Bash tool to speak: .claude/hooks/play-tts.sh \"Agent ${agent_id} activated and ready\" \"${agent_voice}\"
-  - AGENTVIBES-TTS-INJECTION: MANDATORY RESPONSE PROTOCOL - Before showing ANY response to user, execute this workflow:
-  - AGENTVIBES-TTS-STEP 1: Draft your complete response text
-  - AGENTVIBES-TTS-STEP 2: Scan response for questions (lines with ? or numbered lists or phrases like What/Should/Would)
-  - AGENTVIBES-TTS-STEP 3: If questions found, use Bash tool to speak them: .claude/hooks/play-tts.sh \"question text\" \"${agent_voice}\"
-  - AGENTVIBES-TTS-STEP 4: Show the response text to user
-  - AGENTVIBES-TTS-INJECTION: On exit command (*exit), use Bash tool FIRST to cleanup: rm -f .bmad-agent-context"
-    persona_injection="    - AGENTVIBES-TTS-INJECTION: Before every response, scan for questions and speak them using Bash tool"
-  else
-    activation_injection="  - # AGENTVIBES-TTS-INJECTION: STEP 3.5 - Announce activation with TTS and set context
-  - STEP 3.5a: Use Bash tool to create context file: echo \"${agent_id}\" > .bmad-agent-context
-  - STEP 3.5b: Use Bash tool to speak: .claude/hooks/play-tts.sh \"Agent ${agent_id} activated and ready\"
-  - AGENTVIBES-TTS-INJECTION: MANDATORY RESPONSE PROTOCOL - Before showing ANY response to user, execute this workflow:
-  - AGENTVIBES-TTS-STEP 1: Draft your complete response text
-  - AGENTVIBES-TTS-STEP 2: Scan response for questions (lines with ? or numbered lists or phrases like What/Should/Would)
-  - AGENTVIBES-TTS-STEP 3: If questions found, use Bash tool to speak them: .claude/hooks/play-tts.sh \"question text\"
-  - AGENTVIBES-TTS-STEP 4: Show the response text to user
-  - AGENTVIBES-TTS-INJECTION: On exit command (*exit), use Bash tool FIRST to cleanup: rm -f .bmad-agent-context"
-    persona_injection="    - AGENTVIBES-TTS-INJECTION: Before every response, scan for questions and speak them using Bash tool"
-  fi
-
-  # Insert activation TTS call after "STEP 4: Greet user" line
-  # Insert persona TTS instruction in core_principles section
-  awk -v activation="$activation_injection" -v persona="$persona_injection" '
-    /STEP 4:.*[Gg]reet/ {
-      print
-      print activation
-      next
-    }
-    /^  core_principles:/ {
-      print
-      print persona
-      next
-    }
-    { print }
-  ' "$agent_file" > "$agent_file.tmp"
-
-  mv "$agent_file.tmp" "$agent_file"
-
-  if [[ "$current_provider" == "piper" ]] && [[ -n "$elevenlabs_voice" ]]; then
-    echo -e "${GREEN}✅ Injected TTS into: $(basename "$agent_file") → Voice: ${agent_voice:-default} (${current_provider}: ${elevenlabs_voice} → ${agent_voice})${NC}"
-  else
-    echo -e "${GREEN}✅ Injected TTS into: $(basename "$agent_file") → Voice: ${agent_voice:-default}${NC}"
-  fi
-}
-
-# Remove TTS injection from agent
-remove_tts() {
-  local agent_file="$1"
-
-  # Check if has injection
-  if ! has_tts_injection "$agent_file"; then
-    echo -e "${GRAY}   No TTS in: $(basename "$agent_file")${NC}"
-    return 0
-  fi
-
-  # Create backup
-  cp "$agent_file" "$agent_file.backup-tts-removal"
-
-  # Remove TTS injection lines
-  sed -i.bak '/# AGENTVIBES-TTS-INJECTION/,+1d' "$agent_file"
-  rm -f "$agent_file.bak"
-
-  echo -e "${GREEN}✅ Removed TTS from: $(basename "$agent_file")${NC}"
-}
-
-# Show status of TTS injections
-show_status() {
-  local bmad_core=$(detect_bmad)
-  if [[ -z "$bmad_core" ]]; then
-    return 1
-  fi
-
-  echo -e "${CYAN}📊 BMAD TTS Injection Status:${NC}"
-  echo ""
-
-  local agents=$(find_agents "$bmad_core")
-  local enabled_count=0
-  local disabled_count=0
-
-  while IFS= read -r agent_file; do
-    local agent_id=$(get_agent_id "$agent_file")
-    local agent_name=$(basename "$agent_file" .md)
-
-    if has_tts_injection "$agent_file"; then
-      local voice=$(get_agent_voice "$agent_id")
-      echo -e "   ${GREEN}✅${NC} $agent_name (${agent_id}) → Voice: ${voice:-default}"
-      ((enabled_count++))
-    else
-      echo -e "   ${GRAY}❌ $agent_name (${agent_id})${NC}"
-      ((disabled_count++))
-    fi
-  done <<< "$agents"
-
-  echo ""
-  echo -e "${CYAN}Summary:${NC} $enabled_count enabled, $disabled_count disabled"
-}
-
-# Enable TTS for all agents
-enable_all() {
-  local bmad_core=$(detect_bmad)
-  if [[ -z "$bmad_core" ]]; then
-    return 1
-  fi
-
-  echo -e "${CYAN}🎤 Enabling TTS for all BMAD agents...${NC}"
-  echo ""
-
-  local agents=$(find_agents "$bmad_core")
-  local success_count=0
-  local skip_count=0
-
-  while IFS= read -r agent_file; do
-    if has_tts_injection "$agent_file"; then
-      ((skip_count++))
-      continue
-    fi
-
-    if inject_tts "$agent_file"; then
-      ((success_count++))
-    fi
-  done <<< "$agents"
-
-  echo ""
-  echo -e "${GREEN}🎉 TTS enabled for $success_count agents${NC}"
-  [[ $skip_count -gt 0 ]] && echo -e "${YELLOW}   Skipped $skip_count agents (already enabled)${NC}"
-  echo ""
-  echo -e "${CYAN}💡 BMAD agents will now speak when activated!${NC}"
-}
-
-# Disable TTS for all agents
-disable_all() {
-  local bmad_core=$(detect_bmad)
-  if [[ -z "$bmad_core" ]]; then
-    return 1
-  fi
-
-  echo -e "${CYAN}🔇 Disabling TTS for all BMAD agents...${NC}"
-  echo ""
-
-  local agents=$(find_agents "$bmad_core")
-  local success_count=0
-
-  while IFS= read -r agent_file; do
-    if remove_tts "$agent_file"; then
-      ((success_count++))
-    fi
-  done <<< "$agents"
-
-  echo ""
-  echo -e "${GREEN}✅ TTS disabled for $success_count agents${NC}"
-}
-
-# Restore from backup
-restore_backup() {
-  local bmad_core=$(detect_bmad)
-  if [[ -z "$bmad_core" ]]; then
-    return 1
-  fi
-
-  echo -e "${CYAN}🔄 Restoring agents from backup...${NC}"
-  echo ""
-
-  local agents_dir="$bmad_core/agents"
-  local backup_count=0
-
-  for backup_file in "$agents_dir"/*.backup-pre-tts; do
-    if [[ -f "$backup_file" ]]; then
-      local original_file="${backup_file%.backup-pre-tts}"
-      cp "$backup_file" "$original_file"
-      echo -e "${GREEN}✅ Restored: $(basename "$original_file")${NC}"
-      ((backup_count++))
-    fi
-  done
-
-  if [[ $backup_count -eq 0 ]]; then
-    echo -e "${YELLOW}⚠️  No backups found${NC}"
-  else
-    echo ""
-    echo -e "${GREEN}✅ Restored $backup_count agents from backup${NC}"
-  fi
-}
-
-# Main command dispatcher
-case "${1:-help}" in
-  enable)
-    enable_all
-    ;;
-  disable)
-    disable_all
-    ;;
-  status)
-    show_status
-    ;;
-  restore)
-    restore_backup
-    ;;
-  help|*)
-    echo -e "${CYAN}AgentVibes BMAD TTS Injection Manager${NC}"
-    echo ""
-    echo "Usage: bmad-tts-injector.sh {enable|disable|status|restore}"
-    echo ""
-    echo "Commands:"
-    echo "  enable     Inject TTS hooks into all BMAD agents"
-    echo "  disable    Remove TTS hooks from all BMAD agents"
-    echo "  status     Show TTS injection status for all agents"
-    echo "  restore    Restore agents from backup (undo changes)"
-    echo ""
-    echo "What it does:"
-    echo "  • Automatically patches BMAD agent activation instructions"
-    echo "  • Adds TTS calls when agents greet users"
-    echo "  • Uses voice mapping from AgentVibes BMAD plugin"
-    echo "  • Creates backups before modifying files"
-    ;;
-esac

.claude/hooks/bmad-voice-manager.sh

@@ -1,511 +0,0 @@
-#!/bin/bash
-#
-# File: .claude/hooks/bmad-voice-manager.sh
-#
-# AgentVibes - Finally, your AI Agents can Talk Back! Text-to-Speech WITH personality for AI Assistants!
-# Website: https://agentvibes.org
-# Repository: https://github.com/paulpreibisch/AgentVibes
-#
-# Co-created by Paul Preibisch with Claude AI
-# Copyright (c) 2025 Paul Preibisch
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-# DISCLAIMER: This software is provided "AS IS", WITHOUT WARRANTY OF ANY KIND,
-# express or implied, including but not limited to the warranties of
-# merchantability, fitness for a particular purpose and noninfringement.
-# In no event shall the authors or copyright holders be liable for any claim,
-# damages or other liability, whether in an action of contract, tort or
-# otherwise, arising from, out of or in connection with the software or the
-# use or other dealings in the software.
-#
-# ---
-#
-# @fileoverview BMAD Voice Plugin Manager - Maps BMAD agents to unique TTS voices
-# @context Enables each BMAD agent to have its own distinct voice for multi-agent sessions
-# @architecture Markdown table-based voice mapping with enable/disable flag, auto-detection of BMAD
-# @dependencies .claude/plugins/bmad-voices.md (voice mappings), bmad-tts-injector.sh, .bmad-core/ (BMAD installation)
-# @entrypoints Called by /agent-vibes:bmad commands, auto-enabled on BMAD detection
-# @patterns Plugin architecture, auto-enable on dependency detection, state backup/restore on toggle
-# @related bmad-tts-injector.sh, .claude/plugins/bmad-voices.md, .bmad-agent-context file
-
-PLUGIN_DIR=".claude/plugins"
-PLUGIN_FILE="$PLUGIN_DIR/bmad-voices.md"
-ENABLED_FLAG="$PLUGIN_DIR/bmad-voices-enabled.flag"
-
-# AI NOTE: Auto-enable pattern - When BMAD is detected via .bmad-core/install-manifest.yaml,
-# automatically enable the voice plugin to provide seamless multi-agent voice support.
-# This avoids requiring manual plugin activation after BMAD installation.
-
-# @function auto_enable_if_bmad_detected
-# @intent Automatically enable BMAD voice plugin when BMAD framework is detected
-# @why Provide seamless integration - users shouldn't need to manually enable voice mapping
-# @param None
-# @returns None
-# @exitcode 0=auto-enabled, 1=not enabled (already enabled or BMAD not detected)
-# @sideeffects Creates enabled flag file, creates plugin directory
-# @edgecases Only auto-enables if plugin not already enabled, silent operation
-# @calledby get_agent_voice
-# @calls mkdir, touch
-auto_enable_if_bmad_detected() {
-    # Check if BMAD is installed
-    if [[ -f ".bmad-core/install-manifest.yaml" ]] && [[ ! -f "$ENABLED_FLAG" ]]; then
-        # BMAD detected but plugin not enabled - enable it silently
-        mkdir -p "$PLUGIN_DIR"
-        touch "$ENABLED_FLAG"
-        return 0
-    fi
-    return 1
-}
-
-# @function get_agent_voice
-# @intent Retrieve TTS voice assigned to specific BMAD agent
-# @why Each BMAD agent needs unique voice for multi-agent conversation differentiation
-# @param $1 {string} agent_id - BMAD agent identifier (pm, dev, qa, architect, etc.)
-# @returns Echoes voice name to stdout, empty string if plugin disabled or agent not found
-# @exitcode Always 0
-# @sideeffects May auto-enable plugin if BMAD detected
-# @edgecases Returns empty string if plugin disabled/missing, parses markdown table syntax
-# @calledby bmad-tts-injector.sh, play-tts.sh when BMAD agent is active
-# @calls auto_enable_if_bmad_detected, grep, awk, sed
-get_agent_voice() {
-    local agent_id="$1"
-
-    # Auto-enable if BMAD is detected
-    auto_enable_if_bmad_detected
-
-    if [[ ! -f "$ENABLED_FLAG" ]]; then
-        echo ""  # Plugin disabled
-        return
-    fi
-
-    if [[ ! -f "$PLUGIN_FILE" ]]; then
-        echo ""  # Plugin file missing
-        return
-    fi
-
-    # Extract voice from markdown table
-    local voice=$(grep "^| $agent_id " "$PLUGIN_FILE" | \
-                  awk -F'|' '{print $4}' | \
-                  sed 's/^[[:space:]]*//;s/[[:space:]]*$//')
-
-    echo "$voice"
-}
-
-# @function get_agent_personality
-# @intent Retrieve TTS personality assigned to specific BMAD agent
-# @why Agents may have distinct speaking styles (friendly, professional, energetic, etc.)
-# @param $1 {string} agent_id - BMAD agent identifier
-# @returns Echoes personality name to stdout, empty string if not found
-# @exitcode Always 0
-# @sideeffects None
-# @edgecases Returns empty string if plugin file missing, parses column 5 of markdown table
-# @calledby bmad-tts-injector.sh for personality-aware voice synthesis
-# @calls grep, awk, sed
-get_agent_personality() {
-    local agent_id="$1"
-
-    if [[ ! -f "$PLUGIN_FILE" ]]; then
-        echo ""
-        return
-    fi
-
-    local personality=$(grep "^| $agent_id " "$PLUGIN_FILE" | \
-                       awk -F'|' '{print $5}' | \
-                       sed 's/^[[:space:]]*//;s/[[:space:]]*$//')
-
-    echo "$personality"
-}
-
-# @function is_plugin_enabled
-# @intent Check if BMAD voice plugin is currently enabled
-# @why Allow conditional logic based on plugin state
-# @param None
-# @returns Echoes "true" or "false" to stdout
-# @exitcode Always 0
-# @sideeffects None
-# @edgecases None
-# @calledby show_status, enable_plugin, disable_plugin
-# @calls None (file existence check)
-is_plugin_enabled() {
-    [[ -f "$ENABLED_FLAG" ]] && echo "true" || echo "false"
-}
-
-# @function enable_plugin
-# @intent Enable BMAD voice plugin and backup current voice settings
-# @why Allow users to switch to per-agent voices while preserving original configuration
-# @param None
-# @returns None
-# @exitcode Always 0
-# @sideeffects Creates flag file, backs up current voice/personality/sentiment to .bmad-previous-settings
-# @sideeffects Creates activation-instructions file for BMAD agents, calls bmad-tts-injector.sh
-# @edgecases Handles missing settings files gracefully with defaults
-# @calledby Main command dispatcher with "enable" argument
-# @calls mkdir, cat, source, list_mappings, bmad-tts-injector.sh
-enable_plugin() {
-    mkdir -p "$PLUGIN_DIR"
-
-    # Save current settings before enabling
-    BACKUP_FILE="$PLUGIN_DIR/.bmad-previous-settings"
-
-    # Save current voice
-    if [[ -f ".claude/tts-voice.txt" ]]; then
-        CURRENT_VOICE=$(cat .claude/tts-voice.txt 2>/dev/null)
-    elif [[ -f "$HOME/.claude/tts-voice.txt" ]]; then
-        CURRENT_VOICE=$(cat "$HOME/.claude/tts-voice.txt" 2>/dev/null)
-    else
-        CURRENT_VOICE="Aria"
-    fi
-
-    # Save current personality
-    if [[ -f ".claude/tts-personality.txt" ]]; then
-        CURRENT_PERSONALITY=$(cat .claude/tts-personality.txt 2>/dev/null)
-    elif [[ -f "$HOME/.claude/tts-personality.txt" ]]; then
-        CURRENT_PERSONALITY=$(cat "$HOME/.claude/tts-personality.txt" 2>/dev/null)
-    else
-        CURRENT_PERSONALITY="normal"
-    fi
-
-    # Save current sentiment
-    if [[ -f ".claude/tts-sentiment.txt" ]]; then
-        CURRENT_SENTIMENT=$(cat .claude/tts-sentiment.txt 2>/dev/null)
-    elif [[ -f "$HOME/.claude/tts-sentiment.txt" ]]; then
-        CURRENT_SENTIMENT=$(cat "$HOME/.claude/tts-sentiment.txt" 2>/dev/null)
-    else
-        CURRENT_SENTIMENT=""
-    fi
-
-    # Write backup
-    cat > "$BACKUP_FILE" <<EOF
-VOICE=$CURRENT_VOICE
-PERSONALITY=$CURRENT_PERSONALITY
-SENTIMENT=$CURRENT_SENTIMENT
-EOF
-
-    touch "$ENABLED_FLAG"
-
-    # Create activation-instructions file for BMAD agents
-    ACTIVATION_FILE=".claude/activation-instructions"
-    if [[ ! -f "$ACTIVATION_FILE" ]]; then
-        cat > "$ACTIVATION_FILE" <<'ACTIVATION_EOF'
-# BMAD Agent Activation Instructions
-
-When a BMAD agent activates, follow these steps EXACTLY:
-
-## STEP 3.5a: Create BMAD Context File (CRITICAL)
-
-**IMMEDIATELY after agent identification, create the context file:**
-
-```bash
-echo "$AGENT_ID" > .bmad-agent-context
-```
-
-Where `$AGENT_ID` is one of:
-- `pm` (Product Manager)
-- `dev` (Developer)
-- `qa` (QA)
-- `architect` (Architect)
-- `po` (Product Owner)
-- `analyst` (Analyst)
-- `sm` (Scrum Master)
-- `ux-expert` (UX Expert)
-- `bmad-master` (BMAD Master)
-- `bmad-orchestrator` (Orchestrator)
-
-**Example:**
-```bash
-# For Product Manager agent
-echo "pm" > .bmad-agent-context
-```
-
-This file allows AgentVibes to:
-1. Detect which BMAD agent is active
-2. Look up the correct voice mapping
-3. Automatically speak questions using the agent's assigned voice
-
-## STEP 10: Clean Up on Exit
-
-**Before exiting the agent, remove the context file:**
-
-```bash
-rm -f .bmad-agent-context
-```
-
-This ensures voice switching only happens when an agent is active.
-
-## Why This Matters
-
-Without the `.bmad-agent-context` file:
-- AgentVibes cannot detect which agent is active
-- Questions won't be spoken automatically
-- Voice switching won't work
-- The BMAD voice plugin becomes non-functional
-
-**This is MANDATORY for BMAD voice integration to work!**
-ACTIVATION_EOF
-        echo "📝 Created activation instructions: $ACTIVATION_FILE"
-    fi
-
-    echo "✅ BMAD voice plugin enabled"
-    echo "💾 Previous settings backed up:"
-    echo "   Voice: $CURRENT_VOICE"
-    echo "   Personality: $CURRENT_PERSONALITY"
-    [[ -n "$CURRENT_SENTIMENT" ]] && echo "   Sentiment: $CURRENT_SENTIMENT"
-    echo ""
-    list_mappings
-
-    # Automatically inject TTS into BMAD agents
-    echo ""
-    echo "🎤 Automatically enabling TTS for BMAD agents..."
-    echo ""
-
-    # Get the directory where this script is located
-    SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-
-    # Check if bmad-tts-injector.sh exists
-    if [[ -f "$SCRIPT_DIR/bmad-tts-injector.sh" ]]; then
-        # Run the TTS injector
-        "$SCRIPT_DIR/bmad-tts-injector.sh" enable
-    else
-        echo "⚠️  TTS injector not found at: $SCRIPT_DIR/bmad-tts-injector.sh"
-        echo "   You can manually enable TTS with: /agent-vibes:bmad-tts enable"
-    fi
-}
-
-# @function disable_plugin
-# @intent Disable BMAD voice plugin and restore previous voice settings
-# @why Allow users to return to single-voice mode with their original configuration
-# @param None
-# @returns None
-# @exitcode Always 0
-# @sideeffects Removes flag file, restores settings from backup, calls bmad-tts-injector.sh disable
-# @edgecases Handles missing backup file gracefully, warns user if no backup exists
-# @calledby Main command dispatcher with "disable" argument
-# @calls source, rm, echo, bmad-tts-injector.sh
-disable_plugin() {
-    BACKUP_FILE="$PLUGIN_DIR/.bmad-previous-settings"
-
-    # Check if we have a backup to restore
-    if [[ -f "$BACKUP_FILE" ]]; then
-        source "$BACKUP_FILE"
-
-        echo "❌ BMAD voice plugin disabled"
-        echo "🔄 Restoring previous settings:"
-        echo "   Voice: $VOICE"
-        echo "   Personality: $PERSONALITY"
-        [[ -n "$SENTIMENT" ]] && echo "   Sentiment: $SENTIMENT"
-
-        # Restore voice
-        if [[ -n "$VOICE" ]]; then
-            echo "$VOICE" > .claude/tts-voice.txt 2>/dev/null || echo "$VOICE" > "$HOME/.claude/tts-voice.txt"
-        fi
-
-        # Restore personality
-        if [[ -n "$PERSONALITY" ]] && [[ "$PERSONALITY" != "normal" ]]; then
-            echo "$PERSONALITY" > .claude/tts-personality.txt 2>/dev/null || echo "$PERSONALITY" > "$HOME/.claude/tts-personality.txt"
-        fi
-
-        # Restore sentiment
-        if [[ -n "$SENTIMENT" ]]; then
-            echo "$SENTIMENT" > .claude/tts-sentiment.txt 2>/dev/null || echo "$SENTIMENT" > "$HOME/.claude/tts-sentiment.txt"
-        fi
-
-        # Clean up backup
-        rm -f "$BACKUP_FILE"
-    else
-        echo "❌ BMAD voice plugin disabled"
-        echo "⚠️  No previous settings found to restore"
-        echo "AgentVibes will use current voice/personality settings"
-    fi
-
-    rm -f "$ENABLED_FLAG"
-
-    # Automatically remove TTS from BMAD agents
-    echo ""
-    echo "🔇 Automatically disabling TTS for BMAD agents..."
-    echo ""
-
-    # Get the directory where this script is located
-    SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-
-    # Check if bmad-tts-injector.sh exists
-    if [[ -f "$SCRIPT_DIR/bmad-tts-injector.sh" ]]; then
-        # Run the TTS injector disable
-        "$SCRIPT_DIR/bmad-tts-injector.sh" disable
-    else
-        echo "⚠️  TTS injector not found"
-        echo "   You can manually disable TTS with: /agent-vibes:bmad-tts disable"
-    fi
-}
-
-# @function list_mappings
-# @intent Display all BMAD agent-to-voice mappings in readable format
-# @why Help users see which voice is assigned to each agent
-# @param None
-# @returns None
-# @exitcode 0=success, 1=plugin file not found
-# @sideeffects Writes formatted output to stdout
-# @edgecases Parses markdown table format, skips header and separator rows
-# @calledby enable_plugin, show_status, main command dispatcher with "list"
-# @calls grep, sed, echo
-list_mappings() {
-    if [[ ! -f "$PLUGIN_FILE" ]]; then
-        echo "❌ Plugin file not found: $PLUGIN_FILE"
-        return 1
-    fi
-
-    echo "📊 BMAD Agent Voice Mappings:"
-    echo ""
-
-    grep "^| " "$PLUGIN_FILE" | grep -v "Agent ID" | grep -v "^|---" | \
-    while IFS='|' read -r _ agent_id name voice personality _; do
-        agent_id=$(echo "$agent_id" | sed 's/^[[:space:]]*//;s/[[:space:]]*$//')
-        name=$(echo "$name" | sed 's/^[[:space:]]*//;s/[[:space:]]*$//')
-        voice=$(echo "$voice" | sed 's/^[[:space:]]*//;s/[[:space:]]*$//')
-        personality=$(echo "$personality" | sed 's/^[[:space:]]*//;s/[[:space:]]*$//')
-
-        [[ -n "$agent_id" ]] && echo "   $agent_id → $voice [$personality]"
-    done
-}
-
-# @function set_agent_voice
-# @intent Update voice and personality mapping for specific BMAD agent
-# @why Allow customization of agent voices to user preferences
-# @param $1 {string} agent_id - BMAD agent identifier
-# @param $2 {string} voice - New voice name
-# @param $3 {string} personality - New personality (optional, defaults to "normal")
-# @returns None
-# @exitcode 0=success, 1=plugin file not found or agent not found
-# @sideeffects Modifies plugin file, creates .bak backup
-# @edgecases Validates agent exists before updating
-# @calledby Main command dispatcher with "set" argument
-# @calls grep, sed
-set_agent_voice() {
-    local agent_id="$1"
-    local voice="$2"
-    local personality="${3:-normal}"
-
-    if [[ ! -f "$PLUGIN_FILE" ]]; then
-        echo "❌ Plugin file not found: $PLUGIN_FILE"
-        return 1
-    fi
-
-    # Check if agent exists
-    if ! grep -q "^| $agent_id " "$PLUGIN_FILE"; then
-        echo "❌ Agent '$agent_id' not found in plugin"
-        return 1
-    fi
-
-    # Update the voice and personality in the table
-    sed -i.bak "s/^| $agent_id |.*| .* | .* |$/| $agent_id | $(grep "^| $agent_id " "$PLUGIN_FILE" | awk -F'|' '{print $3}') | $voice | $personality |/" "$PLUGIN_FILE"
-
-    echo "✅ Updated $agent_id → $voice [$personality]"
-}
-
-# @function show_status
-# @intent Display plugin status, BMAD detection, and current voice mappings
-# @why Provide comprehensive overview of plugin state for troubleshooting
-# @param None
-# @returns None
-# @exitcode Always 0
-# @sideeffects Writes status information to stdout
-# @edgecases Checks for BMAD installation via manifest file
-# @calledby Main command dispatcher with "status" argument
-# @calls is_plugin_enabled, list_mappings
-show_status() {
-    # Check for BMAD installation
-    local bmad_installed="false"
-    if [[ -f ".bmad-core/install-manifest.yaml" ]]; then
-        bmad_installed="true"
-    fi
-
-    if [[ $(is_plugin_enabled) == "true" ]]; then
-        echo "✅ BMAD voice plugin: ENABLED"
-        if [[ "$bmad_installed" == "true" ]]; then
-            echo "🔍 BMAD detected: Auto-enabled"
-        fi
-    else
-        echo "❌ BMAD voice plugin: DISABLED"
-        if [[ "$bmad_installed" == "true" ]]; then
-            echo "⚠️  BMAD detected but plugin disabled (enable with: /agent-vibes-bmad enable)"
-        fi
-    fi
-    echo ""
-    list_mappings
-}
-
-# @function edit_plugin
-# @intent Open plugin configuration file for manual editing
-# @why Allow advanced users to modify voice mappings directly
-# @param None
-# @returns None
-# @exitcode 0=success, 1=plugin file not found
-# @sideeffects Displays file path and instructions
-# @edgecases Does not actually open editor, just provides guidance
-# @calledby Main command dispatcher with "edit" argument
-# @calls echo
-edit_plugin() {
-    if [[ ! -f "$PLUGIN_FILE" ]]; then
-        echo "❌ Plugin file not found: $PLUGIN_FILE"
-        return 1
-    fi
-
-    echo "Opening $PLUGIN_FILE for editing..."
-    echo "Edit the markdown table to change voice mappings"
-}
-
-# Main command dispatcher
-case "${1:-help}" in
-    enable)
-        enable_plugin
-        ;;
-    disable)
-        disable_plugin
-        ;;
-    status)
-        show_status
-        ;;
-    list)
-        list_mappings
-        ;;
-    set)
-        if [[ -z "$2" ]] || [[ -z "$3" ]]; then
-            echo "Usage: bmad-voice-manager.sh set <agent-id> <voice> [personality]"
-            exit 1
-        fi
-        set_agent_voice "$2" "$3" "$4"
-        ;;
-    get-voice)
-        get_agent_voice "$2"
-        ;;
-    get-personality)
-        get_agent_personality "$2"
-        ;;
-    edit)
-        edit_plugin
-        ;;
-    *)
-        echo "Usage: bmad-voice-manager.sh {enable|disable|status|list|set|get-voice|get-personality|edit}"
-        echo ""
-        echo "Commands:"
-        echo "  enable              Enable BMAD voice plugin"
-        echo "  disable             Disable BMAD voice plugin"
-        echo "  status              Show plugin status and mappings"
-        echo "  list                List all agent voice mappings"
-        echo "  set <id> <voice>    Set voice for agent"
-        echo "  get-voice <id>      Get voice for agent"
-        echo "  get-personality <id> Get personality for agent"
-        echo "  edit                Edit plugin configuration"
-        exit 1
-        ;;
-esac

.claude/hooks/check-output-style.sh

@@ -1,112 +0,0 @@
-#!/bin/bash
-#
-# File: .claude/hooks/check-output-style.sh
-#
-# AgentVibes - Finally, your AI Agents can Talk Back! Text-to-Speech WITH personality for AI Assistants!
-# Website: https://agentvibes.org
-# Repository: https://github.com/paulpreibisch/AgentVibes
-#
-# Co-created by Paul Preibisch with Claude AI
-# Copyright (c) 2025 Paul Preibisch
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-# DISCLAIMER: This software is provided "AS IS", WITHOUT WARRANTY OF ANY KIND,
-# express or implied, including but not limited to the warranties of
-# merchantability, fitness for a particular purpose and noninfringement.
-# In no event shall the authors or copyright holders be liable for any claim,
-# damages or other liability, whether in an action of contract, tort or
-# otherwise, arising from, out of or in connection with the software or the
-# use or other dealings in the software.
-#
-# ---
-#
-# @fileoverview Output Style Detection - Detects if Agent Vibes output style is active in Claude Code
-# @context Voice commands require the Agent Vibes output style to work properly with automatic TTS
-# @architecture Heuristic detection using environment variables and file system checks
-# @dependencies CLAUDECODE environment variable, .claude/output-styles/agent-vibes.md file
-# @entrypoints Called by slash commands to warn users if output style is incorrect
-# @patterns Environment-based detection, graceful degradation with helpful error messages
-# @related .claude/output-styles/agent-vibes.md, Claude Code output style system
-
-# AI NOTE: Output style detection is heuristic-based because Claude Code does not expose
-# the active output style via environment variables. We check for CLAUDECODE env var and
-# the presence of the agent-vibes.md output style file as indicators.
-
-# @function check_output_style
-# @intent Detect if Agent Vibes output style is likely active in Claude Code session
-# @why Voice commands depend on output style hooks that automatically invoke TTS
-# @param None
-# @returns None
-# @exitcode 0=likely using agent-vibes style, 1=not using or cannot detect
-# @sideeffects None (read-only checks)
-# @edgecases Cannot directly detect output style, relies on CLAUDECODE env var and file presence
-# @calledby Main execution block, slash command validation
-# @calls None (direct environment and file checks)
-check_output_style() {
-  # Strategy: Check if this script is being called from within a Claude response
-  # If CLAUDECODE env var is set, we're in Claude Code
-  # If not, we're running standalone (not in a Claude Code session)
-
-  if [[ -z "$CLAUDECODE" ]]; then
-    # Not in Claude Code at all
-    return 1
-  fi
-
-  # We're in Claude Code, but we can't directly detect output style
-  # The agent-vibes output style calls our TTS hooks automatically
-  # So if this function is called, it means a slash command was invoked
-
-  # Check if we have the necessary TTS setup
-  SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-
-  # Check if agent-vibes output style is installed
-  if [[ ! -f "$SCRIPT_DIR/../output-styles/agent-vibes.md" ]]; then
-    return 1
-  fi
-
-  # All checks passed - likely using agent-vibes output style
-  return 0
-}
-
-# @function show_output_style_warning
-# @intent Display helpful warning about enabling Agent Vibes output style
-# @why Users need guidance on how to enable automatic TTS narration
-# @param None
-# @returns None
-# @exitcode Always 0
-# @sideeffects Writes warning message to stdout
-# @edgecases None
-# @calledby Main execution block when check_output_style fails
-# @calls echo
-show_output_style_warning() {
-  echo ""
-  echo "⚠️  Voice commands require the Agent Vibes output style"
-  echo ""
-  echo "To enable voice narration, run:"
-  echo "  /output-style Agent Vibes"
-  echo ""
-  echo "This will make Claude speak with TTS for all responses."
-  echo "You can still use voice commands manually with agent-vibes disabled,"
-  echo "but you won't hear automatic TTS narration."
-  echo ""
-}
-
-# Main execution when called directly
-if [[ "${BASH_SOURCE[0]}" == "${0}" ]]; then
-  if ! check_output_style; then
-    show_output_style_warning
-    exit 1
-  fi
-  exit 0
-fi

.claude/hooks/download-extra-voices.sh

@@ -1,244 +0,0 @@
-#!/bin/bash
-#
-# File: .claude/hooks/download-extra-voices.sh
-#
-# AgentVibes - Finally, your AI Agents can Talk Back! Text-to-Speech WITH personality for AI Assistants!
-# Website: https://agentvibes.org
-# Repository: https://github.com/paulpreibisch/AgentVibes
-#
-# Co-created by Paul Preibisch with Claude AI
-# Copyright (c) 2025 Paul Preibisch
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-# DISCLAIMER: This software is provided "AS IS", WITHOUT WARRANTY OF ANY KIND,
-# express or implied, including but not limited to the warranties of
-# merchantability, fitness for a particular purpose and noninfringement.
-# In no event shall the authors or copyright holders be liable for any claim,
-# damages or other liability, whether in an action of contract, tort or
-# otherwise, arising from, out of or in connection with the software or the
-# use or other dealings in the software.
-#
-# ---
-#
-# @fileoverview Extra Piper Voice Downloader - Downloads custom high-quality voices from HuggingFace
-# @context Post-installation utility to download premium custom voices (Kristin, Jenny, Tracy/16Speakers)
-# @architecture Downloads ONNX voice models from agentvibes/piper-custom-voices HuggingFace repository
-# @dependencies curl (downloads), piper-voice-manager.sh (storage dir logic)
-# @entrypoints Called by MCP server download_extra_voices tool or manually
-# @patterns Batch downloads, skip-existing logic, auto-yes flag for non-interactive use
-# @related piper-voice-manager.sh, mcp-server/server.py, docs/huggingface-setup-guide.md
-#
-
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-source "$SCRIPT_DIR/piper-voice-manager.sh"
-
-# Parse command line arguments
-AUTO_YES=false
-if [[ "$1" == "--yes" ]] || [[ "$1" == "-y" ]]; then
-  AUTO_YES=true
-fi
-
-# HuggingFace repository for custom voices
-HUGGINGFACE_REPO="agentvibes/piper-custom-voices"
-HUGGINGFACE_BASE_URL="https://huggingface.co/${HUGGINGFACE_REPO}/resolve/main"
-
-# Extra custom voices to download
-EXTRA_VOICES=(
-  "kristin:Kristin (US English female, Public Domain, 64MB)"
-  "jenny:Jenny (UK English female with Irish accent, CC BY, 64MB)"
-  "16Speakers:Tracy/16Speakers (Multi-speaker: 12 US + 4 UK voices, Public Domain, 77MB)"
-)
-
-echo "🎙️  AgentVibes Extra Voice Downloader"
-echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-echo ""
-echo "This will download high-quality custom Piper voices from HuggingFace."
-echo ""
-echo "📦 Voices available:"
-for voice_info in "${EXTRA_VOICES[@]}"; do
-  voice_name="${voice_info%%:*}"
-  voice_desc="${voice_info#*:}"
-  echo "  • $voice_desc"
-done
-echo ""
-
-# Check if piper is installed
-if ! command -v piper &> /dev/null; then
-  echo "❌ Error: Piper TTS not installed"
-  echo "Install with: pipx install piper-tts"
-  exit 1
-fi
-
-# Get storage directory
-VOICE_DIR=$(get_voice_storage_dir)
-echo "📂 Storage location: $VOICE_DIR"
-echo ""
-
-# Count already downloaded
-ALREADY_DOWNLOADED=0
-ALREADY_DOWNLOADED_LIST=()
-NEED_DOWNLOAD=()
-
-for voice_info in "${EXTRA_VOICES[@]}"; do
-  voice_name="${voice_info%%:*}"
-  voice_desc="${voice_info#*:}"
-
-  # Check if both .onnx and .onnx.json exist
-  if [[ -f "$VOICE_DIR/${voice_name}.onnx" ]] && [[ -f "$VOICE_DIR/${voice_name}.onnx.json" ]]; then
-    ((ALREADY_DOWNLOADED++))
-    ALREADY_DOWNLOADED_LIST+=("$voice_desc")
-  else
-    NEED_DOWNLOAD+=("$voice_info")
-  fi
-done
-
-echo "📊 Status:"
-echo "   Already downloaded: $ALREADY_DOWNLOADED voice(s)"
-echo "   Need to download: ${#NEED_DOWNLOAD[@]} voice(s)"
-echo ""
-
-# Show already downloaded voices
-if [[ $ALREADY_DOWNLOADED -gt 0 ]]; then
-  echo "✅ Already downloaded (skipped):"
-  for voice_desc in "${ALREADY_DOWNLOADED_LIST[@]}"; do
-    echo "   ✓ $voice_desc"
-  done
-  echo ""
-fi
-
-if [[ ${#NEED_DOWNLOAD[@]} -eq 0 ]]; then
-  echo "🎉 All extra voices already downloaded!"
-  exit 0
-fi
-
-echo "Voices to download:"
-for voice_info in "${NEED_DOWNLOAD[@]}"; do
-  voice_desc="${voice_info#*:}"
-  echo "  • $voice_desc"
-done
-echo ""
-
-# Calculate total size
-TOTAL_SIZE_MB=0
-for voice_info in "${NEED_DOWNLOAD[@]}"; do
-  voice_desc="${voice_info#*:}"
-  if [[ "$voice_desc" =~ ([0-9]+)MB ]]; then
-    TOTAL_SIZE_MB=$((TOTAL_SIZE_MB + ${BASH_REMATCH[1]}))
-  fi
-done
-
-echo "💾 Total download size: ~${TOTAL_SIZE_MB}MB"
-echo ""
-
-# Ask for confirmation (skip if --yes flag provided)
-if [[ "$AUTO_YES" == "false" ]]; then
-  read -p "Download ${#NEED_DOWNLOAD[@]} extra voice(s)? [Y/n]: " -n 1 -r
-  echo
-
-  if [[ ! $REPLY =~ ^[Yy]$ ]] && [[ -n $REPLY ]]; then
-    echo "❌ Download cancelled"
-    exit 0
-  fi
-else
-  echo "Auto-downloading ${#NEED_DOWNLOAD[@]} extra voice(s)..."
-  echo ""
-fi
-
-# Create voice directory if it doesn't exist
-mkdir -p "$VOICE_DIR"
-
-# Download function
-download_voice_file() {
-  local url="$1"
-  local output_path="$2"
-  local file_name="$3"
-
-  echo "  📥 Downloading $file_name..."
-
-  if curl -L --progress-bar "$url" -o "$output_path" 2>&1; then
-    echo "  ✅ Downloaded: $file_name"
-    return 0
-  else
-    echo "  ❌ Failed to download: $file_name"
-    return 1
-  fi
-}
-
-# Download each voice
-DOWNLOADED=0
-FAILED=0
-
-for voice_info in "${NEED_DOWNLOAD[@]}"; do
-  voice_name="${voice_info%%:*}"
-  voice_desc="${voice_info#*:}"
-
-  echo ""
-  echo "📥 Downloading: ${voice_desc%%,*}..."
-  echo ""
-
-  # Download .onnx file
-  onnx_url="${HUGGINGFACE_BASE_URL}/${voice_name}.onnx"
-  onnx_path="${VOICE_DIR}/${voice_name}.onnx"
-
-  # Download .onnx.json file
-  json_url="${HUGGINGFACE_BASE_URL}/${voice_name}.onnx.json"
-  json_path="${VOICE_DIR}/${voice_name}.onnx.json"
-
-  success=true
-
-  if ! download_voice_file "$onnx_url" "$onnx_path" "${voice_name}.onnx"; then
-    success=false
-  fi
-
-  if ! download_voice_file "$json_url" "$json_path" "${voice_name}.onnx.json"; then
-    success=false
-  fi
-
-  if [[ "$success" == "true" ]]; then
-    ((DOWNLOADED++))
-    echo ""
-    echo "✅ Successfully downloaded: ${voice_desc%%,*}"
-  else
-    ((FAILED++))
-    echo ""
-    echo "❌ Failed to download: ${voice_desc%%,*}"
-    # Clean up partial downloads
-    rm -f "$onnx_path" "$json_path"
-  fi
-done
-
-echo ""
-echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-echo "📊 Download Summary:"
-echo "   ✅ Successfully downloaded: $DOWNLOADED"
-echo "   ❌ Failed: $FAILED"
-echo "   📦 Total extra voices available: $((ALREADY_DOWNLOADED + DOWNLOADED))"
-echo ""
-
-if [[ $DOWNLOADED -gt 0 ]]; then
-  echo "✨ Extra voices ready to use!"
-  echo ""
-  echo "Try them:"
-  echo "  /agent-vibes:provider switch piper"
-  echo "  /agent-vibes:switch kristin"
-  echo "  /agent-vibes:switch jenny"
-  echo "  /agent-vibes:switch 16Speakers"
-fi
-
-# Return success if at least one voice was downloaded or all were already present
-if [[ $DOWNLOADED -gt 0 ]] || [[ $ALREADY_DOWNLOADED -gt 0 ]]; then
-  exit 0
-else
-  exit 1
-fi

.claude/hooks/github-star-reminder.sh

@@ -1,154 +0,0 @@
-#!/bin/bash
-#
-# File: .claude/hooks/github-star-reminder.sh
-#
-# AgentVibes - Finally, your AI Agents can Talk Back! Text-to-Speech WITH personality for AI Assistants!
-# Website: https://agentvibes.org
-# Repository: https://github.com/paulpreibisch/AgentVibes
-#
-# Co-created by Paul Preibisch with Claude AI
-# Copyright (c) 2025 Paul Preibisch
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-# DISCLAIMER: This software is provided "AS IS", WITHOUT WARRANTY OF ANY KIND,
-# express or implied, including but not limited to the warranties of
-# merchantability, fitness for a particular purpose and noninfringement.
-# In no event shall the authors or copyright holders be liable for any claim,
-# damages or other liability, whether in an action of contract, tort or
-# otherwise, arising from, out of or in connection with the software or the
-# use or other dealings in the software.
-#
-# ---
-#
-# @fileoverview GitHub Star Reminder System - Gentle daily reminder to star repository
-# @context Shows a once-per-day reminder to encourage users to support the project without being annoying
-# @architecture Timestamp-based tracking using daily date comparison in a state file
-# @dependencies date command for timestamp generation
-# @entrypoints Called by play-tts.sh router on every TTS execution, sourced or executed directly
-# @patterns Rate-limiting via file-based state, graceful degradation, user-opt-out support
-# @related .claude/github-star-reminder.txt (state file), .claude/github-star-reminder-disabled.flag (opt-out)
-
-# Determine config directory (project-local or global)
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-CLAUDE_DIR="$(dirname "$SCRIPT_DIR")"
-
-# Check if we have a project-local .claude directory
-if [[ -d "$CLAUDE_DIR" ]] && [[ "$CLAUDE_DIR" != "$HOME/.claude" ]]; then
-  REMINDER_FILE="$CLAUDE_DIR/github-star-reminder.txt"
-else
-  REMINDER_FILE="$HOME/.claude/github-star-reminder.txt"
-  mkdir -p "$HOME/.claude"
-fi
-
-GITHUB_REPO="https://github.com/paulpreibisch/AgentVibes"
-
-# @function is_reminder_disabled
-# @intent Check if GitHub star reminders have been disabled by the user
-# @why Respect user preferences and provide opt-out mechanism for reminders
-# @param None
-# @returns None
-# @exitcode 0=reminders disabled, 1=reminders enabled
-# @sideeffects Reads flag files from local/global .claude directories
-# @edgecases Checks both flag file and "disabled" text in reminder file for backward compatibility
-# @calledby should_show_reminder
-# @calls cat for reading reminder file content
-is_reminder_disabled() {
-  # Check for disable flag file
-  local disable_file_local="$CLAUDE_DIR/github-star-reminder-disabled.flag"
-  local disable_file_global="$HOME/.claude/github-star-reminder-disabled.flag"
-
-  if [[ -f "$disable_file_local" ]] || [[ -f "$disable_file_global" ]]; then
-    return 0  # Disabled
-  fi
-
-  # Check if reminder file contains "disabled"
-  if [[ -f "$REMINDER_FILE" ]]; then
-    local content=$(cat "$REMINDER_FILE" 2>/dev/null)
-    if [[ "$content" == "disabled" ]]; then
-      return 0  # Disabled
-    fi
-  fi
-
-  return 1  # Not disabled
-}
-
-# @function should_show_reminder
-# @intent Determine if reminder should be displayed based on date and disable status
-# @why Implement once-per-day rate limiting to avoid annoying users
-# @param None
-# @returns None
-# @exitcode 0=should show, 1=should not show
-# @sideeffects Reads .claude/github-star-reminder.txt for last reminder date
-# @edgecases Shows reminder if file doesn't exist (first run), compares YYYYMMDD format dates
-# @calledby Main execution block
-# @calls is_reminder_disabled, cat, date
-should_show_reminder() {
-  # Check if disabled first
-  if is_reminder_disabled; then
-    return 1
-  fi
-
-  # If no reminder file exists, show it
-  if [[ ! -f "$REMINDER_FILE" ]]; then
-    return 0
-  fi
-
-  # Read last reminder date
-  LAST_REMINDER=$(cat "$REMINDER_FILE" 2>/dev/null || echo "0")
-  CURRENT_DATE=$(date +%Y%m%d)
-
-  # Show reminder if it's a new day
-  if [[ "$LAST_REMINDER" != "$CURRENT_DATE" ]]; then
-    return 0
-  fi
-
-  return 1
-}
-
-# @function show_reminder
-# @intent Display friendly GitHub star reminder with opt-out instructions
-# @why Encourage community support while being respectful and non-intrusive
-# @param None
-# @returns None
-# @exitcode Always 0
-# @sideeffects Updates reminder file with current date, writes to stdout
-# @edgecases None
-# @calledby Main execution block when should_show_reminder returns true
-# @calls date, echo
-show_reminder() {
-  echo ""
-  echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-  echo "⭐ Enjoying AgentVibes?"
-  echo ""
-  echo "   If you find this project helpful, please consider giving us"
-  echo "   a star on GitHub! It helps others discover AgentVibes and"
-  echo "   motivates us to keep improving it."
-  echo ""
-  echo "   👉 $GITHUB_REPO"
-  echo ""
-  echo "   Thank you for your support! 🙏"
-  echo ""
-  echo "   💡 To disable these reminders, run:"
-  echo "   echo \"disabled\" > $REMINDER_FILE"
-  echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-  echo ""
-
-  # Update the reminder file with today's date
-  date +%Y%m%d > "$REMINDER_FILE"
-}
-
-# Main execution
-if should_show_reminder; then
-  show_reminder
-fi

.claude/hooks/language-manager.sh

@@ -1,392 +0,0 @@
-#!/bin/bash
-#
-# File: .claude/hooks/language-manager.sh
-#
-# AgentVibes - Finally, your AI Agents can Talk Back! Text-to-Speech WITH personality for AI Assistants!
-# Website: https://agentvibes.org
-# Repository: https://github.com/paulpreibisch/AgentVibes
-#
-# Co-created by Paul Preibisch with Claude AI
-# Copyright (c) 2025 Paul Preibisch
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-# DISCLAIMER: This software is provided "AS IS", WITHOUT WARRANTY OF ANY KIND,
-# express or implied. Use at your own risk. See the Apache License for details.
-#
-# ---
-#
-# @fileoverview Language Manager - Manages multilingual TTS with 30+ language support
-# @context Enables TTS in multiple languages with provider-specific voice recommendations (ElevenLabs multilingual vs Piper native)
-# @architecture Dual-map system: ELEVENLABS_VOICES and PIPER_VOICES for provider-aware voice selection
-# @dependencies provider-manager.sh for active provider detection, .claude/tts-language.txt for state
-# @entrypoints Called by /agent-vibes:language commands, play-tts-*.sh for voice resolution
-# @patterns Provider abstraction, language-to-voice mapping, backward compatibility with legacy LANGUAGE_VOICES
-# @related play-tts-elevenlabs.sh, play-tts-piper.sh, provider-manager.sh, learn-manager.sh
-
-# Determine target .claude directory based on context
-# Priority:
-# 1. CLAUDE_PROJECT_DIR env var (set by MCP for project-specific settings)
-# 2. Script location (for direct slash command usage)
-# 3. Global ~/.claude (fallback)
-
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-
-if [[ -n "$CLAUDE_PROJECT_DIR" ]] && [[ -d "$CLAUDE_PROJECT_DIR/.claude" ]]; then
-  # MCP context: Use the project directory where MCP was invoked
-  CLAUDE_DIR="$CLAUDE_PROJECT_DIR/.claude"
-else
-  # Direct usage context: Use script location
-  CLAUDE_DIR="$(cd "$SCRIPT_DIR/.." 2>/dev/null && pwd)"
-
-  # If script is in global ~/.claude, use that
-  if [[ "$CLAUDE_DIR" == "$HOME/.claude" ]]; then
-    CLAUDE_DIR="$HOME/.claude"
-  elif [[ ! -d "$CLAUDE_DIR" ]]; then
-    # Fallback to global if directory doesn't exist
-    CLAUDE_DIR="$HOME/.claude"
-  fi
-fi
-
-LANGUAGE_FILE="$CLAUDE_DIR/tts-language.txt"
-mkdir -p "$CLAUDE_DIR"
-
-# Source provider manager to detect active provider
-source "$SCRIPT_DIR/provider-manager.sh" 2>/dev/null || true
-
-# Language to ElevenLabs multilingual voice mapping
-declare -A ELEVENLABS_VOICES=(
-    ["spanish"]="Antoni"
-    ["french"]="Rachel"
-    ["german"]="Domi"
-    ["italian"]="Bella"
-    ["portuguese"]="Matilda"
-    ["chinese"]="Antoni"
-    ["japanese"]="Antoni"
-    ["korean"]="Antoni"
-    ["russian"]="Domi"
-    ["polish"]="Antoni"
-    ["dutch"]="Rachel"
-    ["turkish"]="Antoni"
-    ["arabic"]="Antoni"
-    ["hindi"]="Antoni"
-    ["swedish"]="Rachel"
-    ["danish"]="Rachel"
-    ["norwegian"]="Rachel"
-    ["finnish"]="Rachel"
-    ["czech"]="Domi"
-    ["romanian"]="Rachel"
-    ["ukrainian"]="Domi"
-    ["greek"]="Antoni"
-    ["bulgarian"]="Domi"
-    ["croatian"]="Domi"
-    ["slovak"]="Domi"
-)
-
-# Language to Piper voice model mapping
-declare -A PIPER_VOICES=(
-    ["spanish"]="es_ES-davefx-medium"
-    ["french"]="fr_FR-siwis-medium"
-    ["german"]="de_DE-thorsten-medium"
-    ["italian"]="it_IT-riccardo-x_low"
-    ["portuguese"]="pt_BR-faber-medium"
-    ["chinese"]="zh_CN-huayan-medium"
-    ["japanese"]="ja_JP-hikari-medium"
-    ["korean"]="ko_KR-eunyoung-medium"
-    ["russian"]="ru_RU-dmitri-medium"
-    ["polish"]="pl_PL-darkman-medium"
-    ["dutch"]="nl_NL-rdh-medium"
-    ["turkish"]="tr_TR-dfki-medium"
-    ["arabic"]="ar_JO-kareem-medium"
-    ["hindi"]="hi_IN-amitabh-medium"
-    ["swedish"]="sv_SE-nst-medium"
-    ["danish"]="da_DK-talesyntese-medium"
-    ["norwegian"]="no_NO-talesyntese-medium"
-    ["finnish"]="fi_FI-harri-medium"
-    ["czech"]="cs_CZ-jirka-medium"
-    ["romanian"]="ro_RO-mihai-medium"
-    ["ukrainian"]="uk_UA-lada-x_low"
-    ["greek"]="el_GR-rapunzelina-low"
-    ["bulgarian"]="bg_BG-valentin-medium"
-    ["croatian"]="hr_HR-gorana-medium"
-    ["slovak"]="sk_SK-lili-medium"
-)
-
-# Backward compatibility: Keep LANGUAGE_VOICES for existing code
-declare -A LANGUAGE_VOICES=(
-    ["spanish"]="Antoni"
-    ["french"]="Rachel"
-    ["german"]="Domi"
-    ["italian"]="Bella"
-    ["portuguese"]="Matilda"
-    ["chinese"]="Antoni"
-    ["japanese"]="Antoni"
-    ["korean"]="Antoni"
-    ["russian"]="Domi"
-    ["polish"]="Antoni"
-    ["dutch"]="Rachel"
-    ["turkish"]="Antoni"
-    ["arabic"]="Antoni"
-    ["hindi"]="Antoni"
-    ["swedish"]="Rachel"
-    ["danish"]="Rachel"
-    ["norwegian"]="Rachel"
-    ["finnish"]="Rachel"
-    ["czech"]="Domi"
-    ["romanian"]="Rachel"
-    ["ukrainian"]="Domi"
-    ["greek"]="Antoni"
-    ["bulgarian"]="Domi"
-    ["croatian"]="Domi"
-    ["slovak"]="Domi"
-)
-
-# Supported languages list
-SUPPORTED_LANGUAGES="spanish, french, german, italian, portuguese, chinese, japanese, korean, polish, dutch, turkish, russian, arabic, hindi, swedish, danish, norwegian, finnish, czech, romanian, ukrainian, greek, bulgarian, croatian, slovak"
-
-# Function to set language
-set_language() {
-    local lang="$1"
-
-    # Convert to lowercase
-    lang=$(echo "$lang" | tr '[:upper:]' '[:lower:]')
-
-    # Handle reset/english
-    if [[ "$lang" == "reset" ]] || [[ "$lang" == "english" ]] || [[ "$lang" == "en" ]]; then
-        if [[ -f "$LANGUAGE_FILE" ]]; then
-            rm "$LANGUAGE_FILE"
-            echo "✓ Language reset to English (default)"
-        else
-            echo "Already using English (default)"
-        fi
-        return 0
-    fi
-
-    # Check if language is supported
-    if [[ ! " ${!LANGUAGE_VOICES[@]} " =~ " ${lang} " ]]; then
-        echo "❌ Language '$lang' not supported"
-        echo ""
-        echo "Supported languages:"
-        echo "$SUPPORTED_LANGUAGES"
-        return 1
-    fi
-
-    # Save language
-    echo "$lang" > "$LANGUAGE_FILE"
-
-    # Detect active provider and get recommended voice
-    local provider=""
-    if [[ -f "$CLAUDE_DIR/tts-provider.txt" ]]; then
-        provider=$(cat "$CLAUDE_DIR/tts-provider.txt")
-    elif [[ -f "$HOME/.claude/tts-provider.txt" ]]; then
-        provider=$(cat "$HOME/.claude/tts-provider.txt")
-    else
-        provider="elevenlabs"
-    fi
-
-    local recommended_voice=$(get_voice_for_language "$lang" "$provider")
-
-    # Fallback to old mapping if provider-aware function returns empty
-    if [[ -z "$recommended_voice" ]]; then
-        recommended_voice="${LANGUAGE_VOICES[$lang]}"
-    fi
-
-    echo "✓ Language set to: $lang"
-    echo "📢 Recommended voice for $provider TTS: $recommended_voice"
-    echo ""
-    echo "TTS will now speak in $lang."
-    echo "Switch voice with: /agent-vibes:switch \"$recommended_voice\""
-}
-
-# Function to get current language
-get_language() {
-    if [[ -f "$LANGUAGE_FILE" ]]; then
-        local lang=$(cat "$LANGUAGE_FILE")
-
-        # Detect active provider
-        local provider=""
-        if [[ -f "$CLAUDE_DIR/tts-provider.txt" ]]; then
-            provider=$(cat "$CLAUDE_DIR/tts-provider.txt")
-        elif [[ -f "$HOME/.claude/tts-provider.txt" ]]; then
-            provider=$(cat "$HOME/.claude/tts-provider.txt")
-        else
-            provider="elevenlabs"
-        fi
-
-        local recommended_voice=$(get_voice_for_language "$lang" "$provider")
-
-        # Fallback to old mapping
-        if [[ -z "$recommended_voice" ]]; then
-            recommended_voice="${LANGUAGE_VOICES[$lang]}"
-        fi
-
-        echo "Current language: $lang"
-        echo "Recommended voice ($provider): $recommended_voice"
-    else
-        echo "Current language: english (default)"
-        echo "No multilingual voice required"
-    fi
-}
-
-# Function to get language for use in other scripts
-get_language_code() {
-    if [[ -f "$LANGUAGE_FILE" ]]; then
-        cat "$LANGUAGE_FILE"
-    else
-        echo "english"
-    fi
-}
-
-# Function to check if current voice supports language
-is_voice_multilingual() {
-    local voice="$1"
-
-    # List of multilingual voices
-    local multilingual_voices=("Antoni" "Rachel" "Domi" "Bella" "Charlotte" "Matilda")
-
-    for mv in "${multilingual_voices[@]}"; do
-        if [[ "$voice" == "$mv" ]]; then
-            return 0
-        fi
-    done
-
-    return 1
-}
-
-# Function to get best voice for current language
-get_best_voice_for_language() {
-    local lang=$(get_language_code)
-
-    if [[ "$lang" == "english" ]]; then
-        # No specific multilingual voice needed for English
-        echo ""
-        return
-    fi
-
-    # Return recommended voice for language
-    echo "${LANGUAGE_VOICES[$lang]}"
-}
-
-# Function to get voice for a specific language and provider
-# Usage: get_voice_for_language <language> [provider]
-# Provider: "elevenlabs" or "piper" (auto-detected if not provided)
-get_voice_for_language() {
-    local language="$1"
-    local provider="${2:-}"
-
-    # Convert to lowercase
-    language=$(echo "$language" | tr '[:upper:]' '[:lower:]')
-
-    # Auto-detect provider if not specified
-    if [[ -z "$provider" ]]; then
-        if command -v get_active_provider &>/dev/null; then
-            provider=$(get_active_provider 2>/dev/null)
-        else
-            # Fallback to checking provider file directly
-            # Try current directory first, then search up the tree
-            local search_dir="$PWD"
-            local found=false
-
-            while [[ "$search_dir" != "/" ]]; do
-                if [[ -f "$search_dir/.claude/tts-provider.txt" ]]; then
-                    provider=$(cat "$search_dir/.claude/tts-provider.txt")
-                    found=true
-                    break
-                fi
-                search_dir=$(dirname "$search_dir")
-            done
-
-            # If not found in project tree, check global
-            if [[ "$found" = false ]]; then
-                if [[ -f "$HOME/.claude/tts-provider.txt" ]]; then
-                    provider=$(cat "$HOME/.claude/tts-provider.txt")
-                else
-                    provider="elevenlabs"  # Default
-                fi
-            fi
-        fi
-    fi
-
-    # Return appropriate voice based on provider
-    case "$provider" in
-        piper)
-            echo "${PIPER_VOICES[$language]:-}"
-            ;;
-        elevenlabs)
-            echo "${ELEVENLABS_VOICES[$language]:-}"
-            ;;
-        *)
-            echo "${ELEVENLABS_VOICES[$language]:-}"
-            ;;
-    esac
-}
-
-# Main command handler - only run if script is executed directly, not sourced
-if [[ "${BASH_SOURCE[0]}" == "${0}" ]]; then
-    case "${1:-}" in
-        set)
-            if [[ -z "$2" ]]; then
-                echo "Usage: language-manager.sh set <language>"
-                exit 1
-            fi
-            set_language "$2"
-            ;;
-        get)
-            get_language
-            ;;
-        code)
-            get_language_code
-            ;;
-        check-voice)
-            if [[ -z "$2" ]]; then
-                echo "Usage: language-manager.sh check-voice <voice-name>"
-                exit 1
-            fi
-            if is_voice_multilingual "$2"; then
-                echo "yes"
-            else
-                echo "no"
-            fi
-            ;;
-        best-voice)
-            get_best_voice_for_language
-            ;;
-        voice-for-language)
-            if [[ -z "$2" ]]; then
-                echo "Usage: language-manager.sh voice-for-language <language> [provider]"
-                exit 1
-            fi
-            get_voice_for_language "$2" "$3"
-            ;;
-        list)
-            echo "Supported languages and recommended voices:"
-            echo ""
-            for lang in "${!LANGUAGE_VOICES[@]}"; do
-                printf "%-15s → %s\n" "$lang" "${LANGUAGE_VOICES[$lang]}"
-            done | sort
-            ;;
-        *)
-            echo "AgentVibes Language Manager"
-            echo ""
-            echo "Usage:"
-            echo "  language-manager.sh set <language>                    Set language"
-            echo "  language-manager.sh get                               Get current language"
-            echo "  language-manager.sh code                              Get language code only"
-            echo "  language-manager.sh check-voice <name>                Check if voice is multilingual"
-            echo "  language-manager.sh best-voice                        Get best voice for current language"
-            echo "  language-manager.sh voice-for-language <lang> [prov] Get voice for language & provider"
-            echo "  language-manager.sh list                              List all supported languages"
-            exit 1
-            ;;
-    esac
-fi

.claude/hooks/learn-manager.sh

@@ -1,475 +0,0 @@
-#!/bin/bash
-#
-# File: .claude/hooks/learn-manager.sh
-#
-# AgentVibes - Finally, your AI Agents can Talk Back! Text-to-Speech WITH personality for AI Assistants!
-# Website: https://agentvibes.org
-# Repository: https://github.com/paulpreibisch/AgentVibes
-#
-# Co-created by Paul Preibisch with Claude AI
-# Copyright (c) 2025 Paul Preibisch
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-# DISCLAIMER: This software is provided "AS IS", WITHOUT WARRANTY OF ANY KIND,
-# express or implied. Use at your own risk. See the Apache License for details.
-#
-# ---
-#
-# @fileoverview Language Learning Mode Manager - Enables dual-language TTS for immersive learning
-# @context Speaks responses in both main language (English) and target language (Spanish, French, etc.) for language practice
-# @architecture Manages main/target language pairs with voice mappings, auto-configures recommended voices per language
-# @dependencies play-tts.sh (dual invocation), language-manager.sh (voice recommendations), .claude/tts-*.txt state files
-# @entrypoints Called by /agent-vibes:learn commands to enable/disable learning mode
-# @patterns Dual-voice orchestration, auto-configuration, greeting on activation, provider-aware voice selection
-# @related language-manager.sh, play-tts.sh, .claude/tts-learn-mode.txt, .claude/tts-target-language.txt
-
-set -e
-
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-PROJECT_DIR="$SCRIPT_DIR/../.."
-
-# Configuration files (project-local first, then global fallback)
-MAIN_LANG_FILE="$PROJECT_DIR/.claude/tts-main-language.txt"
-TARGET_LANG_FILE="$PROJECT_DIR/.claude/tts-target-language.txt"
-TARGET_VOICE_FILE="$PROJECT_DIR/.claude/tts-target-voice.txt"
-LEARN_MODE_FILE="$PROJECT_DIR/.claude/tts-learn-mode.txt"
-
-GLOBAL_MAIN_LANG_FILE="$HOME/.claude/tts-main-language.txt"
-GLOBAL_TARGET_LANG_FILE="$HOME/.claude/tts-target-language.txt"
-GLOBAL_TARGET_VOICE_FILE="$HOME/.claude/tts-target-voice.txt"
-GLOBAL_LEARN_MODE_FILE="$HOME/.claude/tts-learn-mode.txt"
-
-# Colors
-GREEN='\033[0;32m'
-YELLOW='\033[1;33m'
-BLUE='\033[0;34m'
-NC='\033[0m'
-
-# Get main language
-get_main_language() {
-    if [[ -f "$MAIN_LANG_FILE" ]]; then
-        cat "$MAIN_LANG_FILE"
-    elif [[ -f "$GLOBAL_MAIN_LANG_FILE" ]]; then
-        cat "$GLOBAL_MAIN_LANG_FILE"
-    else
-        echo "english"
-    fi
-}
-
-# Set main language
-set_main_language() {
-    local language="$1"
-    if [[ -z "$language" ]]; then
-        echo -e "${YELLOW}Usage: learn-manager.sh set-main-language <language>${NC}"
-        exit 1
-    fi
-
-    mkdir -p "$PROJECT_DIR/.claude"
-    echo "$language" > "$MAIN_LANG_FILE"
-    echo -e "${GREEN}✓${NC} Main language set to: $language"
-}
-
-# Get target language
-get_target_language() {
-    if [[ -f "$TARGET_LANG_FILE" ]]; then
-        cat "$TARGET_LANG_FILE"
-    elif [[ -f "$GLOBAL_TARGET_LANG_FILE" ]]; then
-        cat "$GLOBAL_TARGET_LANG_FILE"
-    else
-        echo ""
-    fi
-}
-
-# Get greeting message for a language
-get_greeting_for_language() {
-    local language="$1"
-
-    case "${language,,}" in
-        spanish|español)
-            echo "¡Hola! Soy tu profesor de español. ¡Vamos a aprender juntos!"
-            ;;
-        french|français)
-            echo "Bonjour! Je suis votre professeur de français. Apprenons ensemble!"
-            ;;
-        german|deutsch)
-            echo "Hallo! Ich bin dein Deutschlehrer. Lass uns zusammen lernen!"
-            ;;
-        italian|italiano)
-            echo "Ciao! Sono il tuo insegnante di italiano. Impariamo insieme!"
-            ;;
-        portuguese|português)
-            echo "Olá! Sou seu professor de português. Vamos aprender juntos!"
-            ;;
-        chinese|中文|mandarin)
-            echo "你好！我是你的中文老师。让我们一起学习吧！"
-            ;;
-        japanese|日本語)
-            echo "こんにちは！私はあなたの日本語の先生です。一緒に勉強しましょう！"
-            ;;
-        korean|한국어)
-            echo "안녕하세요! 저는 당신의 한국어 선생님입니다. 함께 배워봅시다!"
-            ;;
-        russian|русский)
-            echo "Здравствуйте! Я ваш учитель русского языка. Давайте учиться вместе!"
-            ;;
-        arabic|العربية)
-            echo "مرحبا! أنا معلمك للغة العربية. دعونا نتعلم معا!"
-            ;;
-        hindi|हिन्दी)
-            echo "नमस्ते! मैं आपका हिंदी शिक्षक हूं। आइए साथ में सीखें!"
-            ;;
-        dutch|nederlands)
-            echo "Hallo! Ik ben je Nederlandse leraar. Laten we samen leren!"
-            ;;
-        polish|polski)
-            echo "Cześć! Jestem twoim nauczycielem polskiego. Uczmy się razem!"
-            ;;
-        turkish|türkçe)
-            echo "Merhaba! Ben Türkçe öğretmeninizim. Birlikte öğrenelim!"
-            ;;
-        swedish|svenska)
-            echo "Hej! Jag är din svenskalärare. Låt oss lära tillsammans!"
-            ;;
-        *)
-            echo "Hello! I am your language teacher. Let's learn together!"
-            ;;
-    esac
-}
-
-# Set target language
-set_target_language() {
-    local language="$1"
-    if [[ -z "$language" ]]; then
-        echo -e "${YELLOW}Usage: learn-manager.sh set-target-language <language>${NC}"
-        exit 1
-    fi
-
-    mkdir -p "$PROJECT_DIR/.claude"
-    echo "$language" > "$TARGET_LANG_FILE"
-    echo -e "${GREEN}✓${NC} Target language set to: $language"
-
-    # Automatically set the recommended voice for this language
-    local recommended_voice=$(get_recommended_voice_for_language "$language")
-    if [[ -n "$recommended_voice" ]]; then
-        echo "$recommended_voice" > "$TARGET_VOICE_FILE"
-        echo -e "${GREEN}✓${NC} Target voice automatically set to: ${YELLOW}$recommended_voice${NC}"
-
-        # Detect provider for display
-        local provider=""
-        if [[ -f "$PROJECT_DIR/.claude/tts-provider.txt" ]]; then
-            provider=$(cat "$PROJECT_DIR/.claude/tts-provider.txt")
-        elif [[ -f "$HOME/.claude/tts-provider.txt" ]]; then
-            provider=$(cat "$HOME/.claude/tts-provider.txt")
-        else
-            provider="elevenlabs"
-        fi
-        echo -e "   (for ${GREEN}$provider${NC} TTS)"
-        echo ""
-
-        # Greet user in the target language with the target voice
-        local greeting=$(get_greeting_for_language "$language")
-        echo -e "${BLUE}🎓${NC} Your language teacher says:"
-
-        # Check if we're using Piper and if the voice is available
-        if [[ "$provider" == "piper" ]]; then
-            # Quick check: does the voice file exist?
-            local voice_dir="${HOME}/.claude/piper-voices"
-            if [[ -f "${voice_dir}/${recommended_voice}.onnx" ]]; then
-                # Voice exists, play greeting in background
-                nohup "$SCRIPT_DIR/play-tts.sh" "$greeting" "$recommended_voice" >/dev/null 2>&1 &
-            else
-                echo -e "${YELLOW}   (Voice not yet downloaded - greeting will play after first download)${NC}"
-            fi
-        else
-            # ElevenLabs - just play it in background
-            nohup "$SCRIPT_DIR/play-tts.sh" "$greeting" "$recommended_voice" >/dev/null 2>&1 &
-        fi
-    else
-        # Fallback to suggestion if auto-set failed
-        suggest_voice_for_language "$language"
-    fi
-}
-
-# Get recommended voice for a language (returns voice string, no output)
-get_recommended_voice_for_language() {
-    local language="$1"
-    local recommended_voice=""
-    local provider=""
-
-    # Detect active provider
-    if [[ -f "$PROJECT_DIR/.claude/tts-provider.txt" ]]; then
-        provider=$(cat "$PROJECT_DIR/.claude/tts-provider.txt")
-    elif [[ -f "$HOME/.claude/tts-provider.txt" ]]; then
-        provider=$(cat "$HOME/.claude/tts-provider.txt")
-    else
-        provider="elevenlabs"  # Default
-    fi
-
-    # Source language manager and get provider-specific voice
-    if [[ -f "$SCRIPT_DIR/language-manager.sh" ]]; then
-        source "$SCRIPT_DIR/language-manager.sh" 2>/dev/null
-        recommended_voice=$(get_voice_for_language "$language" "$provider" 2>/dev/null)
-    fi
-
-    # Fallback to hardcoded suggestions if function failed
-    if [[ -z "$recommended_voice" ]]; then
-        case "${language,,}" in
-            spanish|español)
-                recommended_voice=$([ "$provider" = "piper" ] && echo "es_ES-davefx-medium" || echo "Antoni")
-                ;;
-            french|français)
-                recommended_voice=$([ "$provider" = "piper" ] && echo "fr_FR-siwis-medium" || echo "Rachel")
-                ;;
-            german|deutsch)
-                recommended_voice=$([ "$provider" = "piper" ] && echo "de_DE-thorsten-medium" || echo "Domi")
-                ;;
-            italian|italiano)
-                recommended_voice=$([ "$provider" = "piper" ] && echo "it_IT-riccardo-x_low" || echo "Bella")
-                ;;
-            portuguese|português)
-                recommended_voice=$([ "$provider" = "piper" ] && echo "pt_BR-faber-medium" || echo "Matilda")
-                ;;
-            chinese|中文|mandarin)
-                recommended_voice=$([ "$provider" = "piper" ] && echo "zh_CN-huayan-medium" || echo "Amy")
-                ;;
-            *)
-                recommended_voice=$([ "$provider" = "piper" ] && echo "en_US-lessac-medium" || echo "Antoni")
-                ;;
-        esac
-    fi
-
-    echo "$recommended_voice"
-}
-
-# Suggest voice based on target language (displays suggestion message)
-suggest_voice_for_language() {
-    local language="$1"
-    local suggested_voice=$(get_recommended_voice_for_language "$language")
-
-    # Detect provider for display
-    local provider=""
-    if [[ -f "$PROJECT_DIR/.claude/tts-provider.txt" ]]; then
-        provider=$(cat "$PROJECT_DIR/.claude/tts-provider.txt")
-    elif [[ -f "$HOME/.claude/tts-provider.txt" ]]; then
-        provider=$(cat "$HOME/.claude/tts-provider.txt")
-    else
-        provider="elevenlabs"
-    fi
-
-    echo ""
-    echo -e "${BLUE}💡 Tip:${NC} For $language (using ${GREEN}$provider${NC} TTS), we recommend: ${YELLOW}$suggested_voice${NC}"
-    echo -e "   Set it with: ${YELLOW}/agent-vibes:target-voice $suggested_voice${NC}"
-}
-
-# Get target voice
-get_target_voice() {
-    if [[ -f "$TARGET_VOICE_FILE" ]]; then
-        cat "$TARGET_VOICE_FILE"
-    elif [[ -f "$GLOBAL_TARGET_VOICE_FILE" ]]; then
-        cat "$GLOBAL_TARGET_VOICE_FILE"
-    else
-        echo ""
-    fi
-}
-
-# Set target voice
-set_target_voice() {
-    local voice="$1"
-    if [[ -z "$voice" ]]; then
-        echo -e "${YELLOW}Usage: learn-manager.sh set-target-voice <voice>${NC}"
-        exit 1
-    fi
-
-    mkdir -p "$PROJECT_DIR/.claude"
-    echo "$voice" > "$TARGET_VOICE_FILE"
-    echo -e "${GREEN}✓${NC} Target voice set to: $voice"
-}
-
-# Check if learning mode is enabled
-is_learn_mode_enabled() {
-    if [[ -f "$LEARN_MODE_FILE" ]]; then
-        local mode=$(cat "$LEARN_MODE_FILE")
-        [[ "$mode" == "ON" ]]
-    elif [[ -f "$GLOBAL_LEARN_MODE_FILE" ]]; then
-        local mode=$(cat "$GLOBAL_LEARN_MODE_FILE")
-        [[ "$mode" == "ON" ]]
-    else
-        return 1
-    fi
-}
-
-# Enable learning mode
-enable_learn_mode() {
-    mkdir -p "$PROJECT_DIR/.claude"
-    echo "ON" > "$LEARN_MODE_FILE"
-    echo -e "${GREEN}✓${NC} Language learning mode: ${GREEN}ENABLED${NC}"
-    echo ""
-
-    # Auto-set target voice if target language is set but voice is not
-    local target_lang=$(get_target_language)
-    local target_voice=$(get_target_voice)
-    local voice_was_set=false
-
-    if [[ -n "$target_lang" ]] && [[ -z "$target_voice" ]]; then
-        echo -e "${BLUE}ℹ${NC}  Auto-configuring voice for $target_lang..."
-        local recommended_voice=$(get_recommended_voice_for_language "$target_lang")
-        if [[ -n "$recommended_voice" ]]; then
-            echo "$recommended_voice" > "$TARGET_VOICE_FILE"
-            target_voice="$recommended_voice"
-            echo -e "${GREEN}✓${NC} Target voice automatically set to: ${YELLOW}$recommended_voice${NC}"
-
-            # Detect provider for display
-            local provider=""
-            if [[ -f "$PROJECT_DIR/.claude/tts-provider.txt" ]]; then
-                provider=$(cat "$PROJECT_DIR/.claude/tts-provider.txt")
-            elif [[ -f "$HOME/.claude/tts-provider.txt" ]]; then
-                provider=$(cat "$HOME/.claude/tts-provider.txt")
-            else
-                provider="elevenlabs"
-            fi
-            echo -e "   (for ${GREEN}$provider${NC} TTS)"
-            echo ""
-            voice_was_set=true
-        fi
-    fi
-
-    show_status
-
-    # Greet user with language teacher if everything is configured
-    if [[ -n "$target_lang" ]] && [[ -n "$target_voice" ]]; then
-        echo ""
-        local greeting=$(get_greeting_for_language "$target_lang")
-        echo -e "${BLUE}🎓${NC} Your language teacher says:"
-
-        # Detect provider
-        local provider=""
-        if [[ -f "$PROJECT_DIR/.claude/tts-provider.txt" ]]; then
-            provider=$(cat "$PROJECT_DIR/.claude/tts-provider.txt")
-        elif [[ -f "$HOME/.claude/tts-provider.txt" ]]; then
-            provider=$(cat "$HOME/.claude/tts-provider.txt")
-        else
-            provider="elevenlabs"
-        fi
-
-        # Check if we're using Piper and if the voice is available
-        if [[ "$provider" == "piper" ]]; then
-            # Quick check: does the voice file exist?
-            local voice_dir="${HOME}/.claude/piper-voices"
-            if [[ -f "${voice_dir}/${target_voice}.onnx" ]]; then
-                # Voice exists, play greeting in background
-                nohup "$SCRIPT_DIR/play-tts.sh" "$greeting" "$target_voice" >/dev/null 2>&1 &
-            else
-                echo -e "${YELLOW}   (Voice not yet downloaded - greeting will play after first download)${NC}"
-            fi
-        else
-            # ElevenLabs - just play it in background
-            nohup "$SCRIPT_DIR/play-tts.sh" "$greeting" "$target_voice" >/dev/null 2>&1 &
-        fi
-    fi
-}
-
-# Disable learning mode
-disable_learn_mode() {
-    mkdir -p "$PROJECT_DIR/.claude"
-    echo "OFF" > "$LEARN_MODE_FILE"
-    echo -e "${GREEN}✓${NC} Language learning mode: ${YELLOW}DISABLED${NC}"
-}
-
-# Show learning mode status
-show_status() {
-    local main_lang=$(get_main_language)
-    local target_lang=$(get_target_language)
-    local target_voice=$(get_target_voice)
-    local learn_mode="OFF"
-
-    if is_learn_mode_enabled; then
-        learn_mode="ON"
-    fi
-
-    echo -e "${BLUE}━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━${NC}"
-    echo -e "${BLUE}   Language Learning Mode Status${NC}"
-    echo -e "${BLUE}━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━${NC}"
-    echo ""
-    echo -e "  ${BLUE}Learning Mode:${NC}    $(if [[ "$learn_mode" == "ON" ]]; then echo -e "${GREEN}ENABLED${NC}"; else echo -e "${YELLOW}DISABLED${NC}"; fi)"
-    echo -e "  ${BLUE}Main Language:${NC}    $main_lang"
-    echo -e "  ${BLUE}Target Language:${NC}  ${target_lang:-"(not set)"}"
-    echo -e "  ${BLUE}Target Voice:${NC}     ${target_voice:-"(not set)"}"
-    echo ""
-
-    if [[ "$learn_mode" == "ON" ]]; then
-        if [[ -z "$target_lang" ]]; then
-            echo -e "  ${YELLOW}⚠${NC}  Please set a target language: ${YELLOW}/agent-vibes:target <language>${NC}"
-        fi
-        if [[ -z "$target_voice" ]]; then
-            echo -e "  ${YELLOW}⚠${NC}  Please set a target voice: ${YELLOW}/agent-vibes:target-voice <voice>${NC}"
-        fi
-
-        if [[ -n "$target_lang" ]] && [[ -n "$target_voice" ]]; then
-            echo -e "  ${GREEN}✓${NC}  All set! TTS will speak in both languages."
-            echo ""
-            echo -e "  ${BLUE}How it works:${NC}"
-            echo -e "    1. First: Speak in ${BLUE}$main_lang${NC} (your current voice)"
-            echo -e "    2. Then: Speak in ${BLUE}$target_lang${NC} ($target_voice voice)"
-        fi
-    else
-        echo -e "  ${BLUE}💡 Tip:${NC} Enable learning mode with: ${YELLOW}/agent-vibes:learn${NC}"
-    fi
-
-    echo ""
-    echo -e "${BLUE}━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━${NC}"
-}
-
-# Main command handler
-case "${1:-}" in
-    get-main-language)
-        get_main_language
-        ;;
-    set-main-language)
-        set_main_language "$2"
-        ;;
-    get-target-language)
-        get_target_language
-        ;;
-    set-target-language)
-        set_target_language "$2"
-        ;;
-    get-target-voice)
-        get_target_voice
-        ;;
-    set-target-voice)
-        set_target_voice "$2"
-        ;;
-    is-enabled)
-        if is_learn_mode_enabled; then
-            echo "ON"
-            exit 0
-        else
-            echo "OFF"
-            exit 1
-        fi
-        ;;
-    enable)
-        enable_learn_mode
-        ;;
-    disable)
-        disable_learn_mode
-        ;;
-    status)
-        show_status
-        ;;
-    *)
-        echo "Usage: learn-manager.sh {get-main-language|set-main-language|get-target-language|set-target-language|get-target-voice|set-target-voice|is-enabled|enable|disable|status}"
-        exit 1
-        ;;
-esac

.claude/hooks/personality-manager.sh

@@ -1,438 +0,0 @@
-#!/bin/bash
-#
-# File: .claude/hooks/personality-manager.sh
-#
-# AgentVibes - Finally, your AI Agents can Talk Back! Text-to-Speech WITH personality for AI Assistants!
-# Website: https://agentvibes.org
-# Repository: https://github.com/paulpreibisch/AgentVibes
-#
-# Co-created by Paul Preibisch with Claude AI
-# Copyright (c) 2025 Paul Preibisch
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-# DISCLAIMER: This software is provided "AS IS", WITHOUT WARRANTY OF ANY KIND,
-# express or implied. Use at your own risk. See the Apache License for details.
-#
-# ---
-#
-# @fileoverview Personality Manager - Adds character and emotional style to TTS voices
-# @context Enables voices to have distinct personalities (flirty, sarcastic, pirate, etc.) with provider-aware voice assignment
-# @architecture Markdown-based personality templates with provider-specific voice mappings (ElevenLabs vs Piper)
-# @dependencies .claude/personalities/*.md files, voice-manager.sh, play-tts.sh, provider-manager.sh
-# @entrypoints Called by /agent-vibes:personality slash commands
-# @patterns Template-based configuration, provider abstraction, random personality support
-# @related .claude/personalities/*.md, voice-manager.sh, .claude/tts-personality.txt
-
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-PERSONALITIES_DIR="$SCRIPT_DIR/../personalities"
-
-# Determine target .claude directory based on context
-# Priority:
-# 1. CLAUDE_PROJECT_DIR env var (set by MCP for project-specific settings)
-# 2. Script location (for direct slash command usage)
-# 3. Global ~/.claude (fallback)
-
-if [[ -n "$CLAUDE_PROJECT_DIR" ]] && [[ -d "$CLAUDE_PROJECT_DIR/.claude" ]]; then
-  # MCP context: Use the project directory where MCP was invoked
-  CLAUDE_DIR="$CLAUDE_PROJECT_DIR/.claude"
-else
-  # Direct usage context: Use script location
-  # Script is at .claude/hooks/personality-manager.sh, so .claude is ..
-  CLAUDE_DIR="$(cd "$SCRIPT_DIR/.." 2>/dev/null && pwd)"
-
-  # If script is in global ~/.claude, use that
-  if [[ "$CLAUDE_DIR" == "$HOME/.claude" ]]; then
-    CLAUDE_DIR="$HOME/.claude"
-  elif [[ ! -d "$CLAUDE_DIR" ]]; then
-    # Fallback to global if directory doesn't exist
-    CLAUDE_DIR="$HOME/.claude"
-  fi
-fi
-
-PERSONALITY_FILE="$CLAUDE_DIR/tts-personality.txt"
-
-# Function to get personality data from markdown file
-get_personality_data() {
-  local personality="$1"
-  local field="$2"
-  local file="$PERSONALITIES_DIR/${personality}.md"
-
-  if [[ ! -f "$file" ]]; then
-    return 1
-  fi
-
-  case "$field" in
-    prefix)
-      sed -n '/^## Prefix/,/^##/p' "$file" | sed '1d;$d' | tr -d '\n' | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'
-      ;;
-    suffix)
-      sed -n '/^## Suffix/,/^##/p' "$file" | sed '1d;$d' | tr -d '\n' | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'
-      ;;
-    description)
-      grep "^description:" "$file" | cut -d: -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'
-      ;;
-    voice)
-      grep "^elevenlabs_voice:" "$file" | cut -d: -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'
-      ;;
-    piper_voice)
-      grep "^piper_voice:" "$file" | cut -d: -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'
-      ;;
-    instructions)
-      sed -n '/^## AI Instructions/,/^##/p' "$file" | sed '1d;$d'
-      ;;
-  esac
-}
-
-# Function to list all available personalities
-list_personalities() {
-  local personalities=()
-
-  # Find all .md files in personalities directory
-  if [[ -d "$PERSONALITIES_DIR" ]]; then
-    for file in "$PERSONALITIES_DIR"/*.md; do
-      if [[ -f "$file" ]]; then
-        basename "$file" .md
-      fi
-    done
-  fi
-}
-
-case "$1" in
-  list)
-    echo "🎭 Available Personalities:"
-    echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-
-    # Get current personality
-    CURRENT="normal"
-    if [ -f "$PERSONALITY_FILE" ]; then
-      CURRENT=$(cat "$PERSONALITY_FILE")
-    fi
-
-    # List personalities from markdown files
-    echo "Built-in personalities:"
-    for personality in $(list_personalities | sort); do
-      desc=$(get_personality_data "$personality" "description")
-      if [[ "$personality" == "$CURRENT" ]]; then
-        echo "  ✓ $personality - $desc (current)"
-      else
-        echo "  - $personality - $desc"
-      fi
-    done
-
-    # Add random option
-    if [[ "$CURRENT" == "random" ]]; then
-      echo "  ✓ random - Picks randomly each time (current)"
-    else
-      echo "  - random - Picks randomly each time"
-    fi
-
-    echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-    echo ""
-    echo "Usage: /agent-vibes:personality <name>"
-    echo "       /agent-vibes:personality add <name>"
-    echo "       /agent-vibes:personality edit <name>"
-    ;;
-
-  set|switch)
-    PERSONALITY="$2"
-
-    if [[ -z "$PERSONALITY" ]]; then
-      echo "❌ Please specify a personality name"
-      echo "Usage: $0 set <personality>"
-      exit 1
-    fi
-
-    # Check if personality file exists (unless it's random)
-    if [[ "$PERSONALITY" != "random" ]]; then
-      if [[ ! -f "$PERSONALITIES_DIR/${PERSONALITY}.md" ]]; then
-        echo "❌ Personality not found: $PERSONALITY"
-        echo ""
-        echo "Available personalities:"
-        for p in $(list_personalities | sort); do
-          echo "  • $p"
-        done
-        exit 1
-      fi
-    fi
-
-    # Save the personality
-    echo "$PERSONALITY" > "$PERSONALITY_FILE"
-    echo "🎭 Personality set to: $PERSONALITY"
-
-    # Check if personality has an assigned voice
-    # Detect active TTS provider
-    PROVIDER_FILE=""
-    if [[ -f "$CLAUDE_DIR/tts-provider.txt" ]]; then
-      PROVIDER_FILE="$CLAUDE_DIR/tts-provider.txt"
-    elif [[ -f "$HOME/.claude/tts-provider.txt" ]]; then
-      PROVIDER_FILE="$HOME/.claude/tts-provider.txt"
-    fi
-
-    ACTIVE_PROVIDER="elevenlabs"  # default
-    if [[ -n "$PROVIDER_FILE" ]]; then
-      ACTIVE_PROVIDER=$(cat "$PROVIDER_FILE")
-    fi
-
-    # Get the appropriate voice based on provider
-    ASSIGNED_VOICE=""
-    if [[ "$ACTIVE_PROVIDER" == "piper" ]]; then
-      # Try to get Piper-specific voice first
-      ASSIGNED_VOICE=$(get_personality_data "$PERSONALITY" "piper_voice")
-      if [[ -z "$ASSIGNED_VOICE" ]]; then
-        # Fallback to default Piper voice
-        ASSIGNED_VOICE="en_US-lessac-medium"
-      fi
-    else
-      # Use ElevenLabs voice (reads from elevenlabs_voice: field)
-      ASSIGNED_VOICE=$(get_personality_data "$PERSONALITY" "voice")
-    fi
-
-    if [[ -n "$ASSIGNED_VOICE" ]]; then
-      # Switch to the assigned voice (silently - personality will do the talking)
-      VOICE_MANAGER="$SCRIPT_DIR/voice-manager.sh"
-      if [[ -x "$VOICE_MANAGER" ]]; then
-        echo "🎤 Switching to assigned voice: $ASSIGNED_VOICE"
-        "$VOICE_MANAGER" switch "$ASSIGNED_VOICE" --silent >/dev/null 2>&1
-      fi
-    fi
-
-    # Make a personality-appropriate remark with TTS
-    if [[ "$PERSONALITY" != "random" ]]; then
-      echo ""
-
-      # Get TTS script path
-      TTS_SCRIPT="$SCRIPT_DIR/play-tts.sh"
-
-      # Try to get acknowledgment from personality file
-      PERSONALITY_FILE_PATH="$PERSONALITIES_DIR/${PERSONALITY}.md"
-      REMARK=""
-
-      if [[ -f "$PERSONALITY_FILE_PATH" ]]; then
-        # Extract example responses from personality file (lines starting with "- ")
-        mapfile -t EXAMPLES < <(grep '^- "' "$PERSONALITY_FILE_PATH" | sed 's/^- "//; s/"$//')
-
-        if [[ ${#EXAMPLES[@]} -gt 0 ]]; then
-          # Pick a random example
-          REMARK="${EXAMPLES[$RANDOM % ${#EXAMPLES[@]}]}"
-        fi
-      fi
-
-      # Fallback if no examples found
-      if [[ -z "$REMARK" ]]; then
-        REMARK="Personality set to ${PERSONALITY}!"
-      fi
-
-      echo "💬 $REMARK"
-      "$TTS_SCRIPT" "$REMARK"
-
-      echo ""
-      echo "Note: AI will generate unique ${PERSONALITY} responses - no fixed templates!"
-      echo ""
-      echo "💡 Tip: To hear automatic TTS narration, enable the Agent Vibes output style:"
-      echo "   /output-style Agent Vibes"
-    fi
-    ;;
-
-  get)
-    if [ -f "$PERSONALITY_FILE" ]; then
-      CURRENT=$(cat "$PERSONALITY_FILE")
-      echo "Current personality: $CURRENT"
-
-      if [[ "$CURRENT" != "random" ]]; then
-        desc=$(get_personality_data "$CURRENT" "description")
-        [[ -n "$desc" ]] && echo "Description: $desc"
-      fi
-    else
-      echo "Current personality: normal (default)"
-    fi
-    ;;
-
-  add)
-    NAME="$2"
-    if [[ -z "$NAME" ]]; then
-      echo "❌ Please specify a personality name"
-      echo "Usage: $0 add <name>"
-      exit 1
-    fi
-
-    FILE="$PERSONALITIES_DIR/${NAME}.md"
-    if [[ -f "$FILE" ]]; then
-      echo "❌ Personality '$NAME' already exists"
-      echo "Use 'edit' to modify it"
-      exit 1
-    fi
-
-    # Create new personality file
-    cat > "$FILE" << 'EOF'
----
-name: NAME
-description: Custom personality
----
-
-# NAME Personality
-
-## Prefix
-
-
-## Suffix
-
-
-## AI Instructions
-Describe how the AI should generate messages for this personality.
-
-## Example Responses
-- "Example response 1"
-- "Example response 2"
-EOF
-
-    # Replace NAME with actual name
-    sed -i "s/NAME/$NAME/g" "$FILE"
-
-    echo "✅ Created new personality: $NAME"
-    echo "📝 Edit the file: $FILE"
-    echo ""
-    echo "You can now customize:"
-    echo "  • Prefix: Text before messages"
-    echo "  • Suffix: Text after messages"
-    echo "  • AI Instructions: How AI should speak"
-    echo "  • Example Responses: Sample messages"
-    ;;
-
-  edit)
-    NAME="$2"
-    if [[ -z "$NAME" ]]; then
-      echo "❌ Please specify a personality name"
-      echo "Usage: $0 edit <name>"
-      exit 1
-    fi
-
-    FILE="$PERSONALITIES_DIR/${NAME}.md"
-    if [[ ! -f "$FILE" ]]; then
-      echo "❌ Personality '$NAME' not found"
-      echo "Use 'add' to create it first"
-      exit 1
-    fi
-
-    echo "📝 Edit this file to customize the personality:"
-    echo "$FILE"
-    ;;
-
-  reset)
-    echo "normal" > "$PERSONALITY_FILE"
-    echo "🎭 Personality reset to: normal"
-    ;;
-
-  set-favorite-voice)
-    PERSONALITY="$2"
-    NEW_VOICE="$3"
-
-    if [[ -z "$PERSONALITY" ]] || [[ -z "$NEW_VOICE" ]]; then
-      echo "❌ Please specify both personality name and voice name"
-      echo "Usage: $0 set-favorite-voice <personality> <voice>"
-      exit 1
-    fi
-
-    FILE="$PERSONALITIES_DIR/${PERSONALITY}.md"
-    if [[ ! -f "$FILE" ]]; then
-      echo "❌ Personality '$PERSONALITY' not found"
-      exit 1
-    fi
-
-    # Detect active TTS provider
-    PROVIDER_FILE=""
-    if [[ -f "$CLAUDE_DIR/tts-provider.txt" ]]; then
-      PROVIDER_FILE="$CLAUDE_DIR/tts-provider.txt"
-    elif [[ -f "$HOME/.claude/tts-provider.txt" ]]; then
-      PROVIDER_FILE="$HOME/.claude/tts-provider.txt"
-    fi
-
-    ACTIVE_PROVIDER="elevenlabs"  # default
-    if [[ -n "$PROVIDER_FILE" ]]; then
-      ACTIVE_PROVIDER=$(cat "$PROVIDER_FILE")
-    fi
-
-    # Determine which field to update based on provider
-    if [[ "$ACTIVE_PROVIDER" == "piper" ]]; then
-      VOICE_FIELD="piper_voice"
-      CURRENT_VOICE=$(get_personality_data "$PERSONALITY" "piper_voice")
-    else
-      VOICE_FIELD="elevenlabs_voice"
-      CURRENT_VOICE=$(get_personality_data "$PERSONALITY" "voice")
-    fi
-
-    # Check if personality already has a favorite voice assigned
-    if [[ -n "$CURRENT_VOICE" ]] && [[ "$CURRENT_VOICE" != "$NEW_VOICE" ]]; then
-      echo "⚠️  WARNING: Personality '$PERSONALITY' already has a favorite voice assigned!"
-      echo ""
-      echo "   Current favorite ($ACTIVE_PROVIDER): $CURRENT_VOICE"
-      echo "   New voice: $NEW_VOICE"
-      echo ""
-      echo "Do you want to replace the favorite voice?"
-      echo ""
-      read -p "Enter your choice (yes/no): " CHOICE
-
-      case "$CHOICE" in
-        yes|y|YES|Y)
-          echo "✅ Replacing favorite voice..."
-          ;;
-        no|n|NO|N)
-          echo "❌ Keeping current favorite voice: $CURRENT_VOICE"
-          exit 0
-          ;;
-        *)
-          echo "❌ Invalid choice. Keeping current favorite voice: $CURRENT_VOICE"
-          exit 1
-          ;;
-      esac
-    fi
-
-    # Update the voice in the personality file
-    if grep -q "^${VOICE_FIELD}:" "$FILE"; then
-      # Field exists, replace it
-      sed -i "s/^${VOICE_FIELD}:.*/${VOICE_FIELD}: ${NEW_VOICE}/" "$FILE"
-    else
-      # Field doesn't exist, add it after the frontmatter
-      sed -i "/^---$/,/^---$/ { /^---$/a\\
-${VOICE_FIELD}: ${NEW_VOICE}
-}" "$FILE"
-    fi
-
-    echo "✅ Favorite voice for '$PERSONALITY' personality set to: $NEW_VOICE ($ACTIVE_PROVIDER)"
-    echo "📝 Updated file: $FILE"
-    ;;
-
-  *)
-    # If a single argument is provided and it's not a command, treat it as "set <personality>"
-    if [[ -n "$1" ]] && [[ -f "$PERSONALITIES_DIR/${1}.md" || "$1" == "random" ]]; then
-      # Call set with the personality name
-      exec "$0" set "$1"
-    else
-      echo "AgentVibes Personality Manager"
-      echo ""
-      echo "Commands:"
-      echo "  list                              - List all personalities"
-      echo "  set/switch <name>                 - Set personality"
-      echo "  add <name>                        - Create new personality"
-      echo "  edit <name>                       - Show path to edit personality"
-      echo "  get                               - Show current personality"
-      echo "  set-favorite-voice <name> <voice> - Set favorite voice for a personality"
-      echo "  reset                             - Reset to normal"
-      echo ""
-      echo "Examples:"
-      echo "  /agent-vibes:personality flirty"
-      echo "  /agent-vibes:personality add cowboy"
-      echo "  /agent-vibes:personality set-favorite-voice flirty \"Aria\""
-    fi
-    ;;
-esac

.claude/hooks/piper-download-voices.sh

@@ -1,165 +0,0 @@
-#!/bin/bash
-#
-# File: .claude/hooks/piper-download-voices.sh
-#
-# AgentVibes - Finally, your AI Agents can Talk Back! Text-to-Speech WITH personality for AI Assistants!
-# Website: https://agentvibes.org
-# Repository: https://github.com/paulpreibisch/AgentVibes
-#
-# Co-created by Paul Preibisch with Claude AI
-# Copyright (c) 2025 Paul Preibisch
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-# DISCLAIMER: This software is provided "AS IS", WITHOUT WARRANTY OF ANY KIND,
-# express or implied, including but not limited to the warranties of
-# merchantability, fitness for a particular purpose and noninfringement.
-# In no event shall the authors or copyright holders be liable for any claim,
-# damages or other liability, whether in an action of contract, tort or
-# otherwise, arising from, out of or in connection with the software or the
-# use or other dealings in the software.
-#
-# ---
-#
-# @fileoverview Piper Voice Model Downloader - Batch downloads popular Piper TTS voices from HuggingFace
-# @context Post-installation utility to download commonly used voices (~25MB each)
-# @architecture Wrapper around piper-voice-manager.sh download functions with progress tracking
-# @dependencies piper-voice-manager.sh (download logic), piper binary (for validation)
-# @entrypoints Called by piper-installer.sh or manually via ./piper-download-voices.sh [--yes|-y]
-# @patterns Batch operations, skip-existing logic, auto-yes flag for non-interactive use
-# @related piper-voice-manager.sh, piper-installer.sh
-#
-
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-source "$SCRIPT_DIR/piper-voice-manager.sh"
-
-# Parse command line arguments
-AUTO_YES=false
-if [[ "$1" == "--yes" ]] || [[ "$1" == "-y" ]]; then
-  AUTO_YES=true
-fi
-
-# Common voice models to download
-COMMON_VOICES=(
-  "en_US-lessac-medium"      # Default, clear male
-  "en_US-amy-medium"         # Warm female
-  "en_US-joe-medium"         # Professional male
-  "en_US-ryan-high"          # Expressive male
-  "en_US-libritts-high"      # Premium quality
-)
-
-echo "🎙️  Piper Voice Model Downloader"
-echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-echo ""
-echo "This will download the most commonly used Piper voice models."
-echo "Each voice is approximately 25MB."
-echo ""
-
-# Check if piper is installed
-if ! command -v piper &> /dev/null; then
-  echo "❌ Error: Piper TTS not installed"
-  echo "Install with: pipx install piper-tts"
-  exit 1
-fi
-
-# Get storage directory
-VOICE_DIR=$(get_voice_storage_dir)
-
-echo "📂 Storage location: $VOICE_DIR"
-echo ""
-
-# Count already downloaded
-ALREADY_DOWNLOADED=0
-ALREADY_DOWNLOADED_LIST=()
-NEED_DOWNLOAD=()
-
-for voice in "${COMMON_VOICES[@]}"; do
-  if verify_voice "$voice" 2>/dev/null; then
-    ((ALREADY_DOWNLOADED++))
-    ALREADY_DOWNLOADED_LIST+=("$voice")
-  else
-    NEED_DOWNLOAD+=("$voice")
-  fi
-done
-
-echo "📊 Status:"
-echo "   Already downloaded: $ALREADY_DOWNLOADED voice(s)"
-echo "   Need to download: ${#NEED_DOWNLOAD[@]} voice(s)"
-echo ""
-
-# Show already downloaded voices
-if [[ $ALREADY_DOWNLOADED -gt 0 ]]; then
-  echo "✅ Already downloaded (skipped):"
-  for voice in "${ALREADY_DOWNLOADED_LIST[@]}"; do
-    echo "   ✓ $voice"
-  done
-  echo ""
-fi
-
-if [[ ${#NEED_DOWNLOAD[@]} -eq 0 ]]; then
-  echo "🎉 All common voices ready to use!"
-  exit 0
-fi
-
-echo "Voices to download:"
-for voice in "${NEED_DOWNLOAD[@]}"; do
-  echo "  • $voice (~25MB)"
-done
-echo ""
-
-# Ask for confirmation (skip if --yes flag provided)
-if [[ "$AUTO_YES" == "false" ]]; then
-  read -p "Download ${#NEED_DOWNLOAD[@]} voice model(s)? [Y/n]: " -n 1 -r
-  echo
-
-  if [[ ! $REPLY =~ ^[Yy]$ ]] && [[ -n $REPLY ]]; then
-    echo "❌ Download cancelled"
-    exit 0
-  fi
-else
-  echo "Auto-downloading ${#NEED_DOWNLOAD[@]} voice model(s)..."
-  echo ""
-fi
-
-# Download each voice
-DOWNLOADED=0
-FAILED=0
-
-for voice in "${NEED_DOWNLOAD[@]}"; do
-  echo ""
-  echo "📥 Downloading: $voice..."
-
-  if download_voice "$voice"; then
-    ((DOWNLOADED++))
-    echo "✅ Downloaded: $voice"
-  else
-    ((FAILED++))
-    echo "❌ Failed: $voice"
-  fi
-done
-
-echo ""
-echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-echo "📊 Download Summary:"
-echo "   ✅ Successfully downloaded: $DOWNLOADED"
-echo "   ❌ Failed: $FAILED"
-echo "   📦 Total voices available: $((ALREADY_DOWNLOADED + DOWNLOADED))"
-echo ""
-
-if [[ $DOWNLOADED -gt 0 ]]; then
-  echo "✨ Ready to use Piper TTS with downloaded voices!"
-  echo ""
-  echo "Try it:"
-  echo "  /agent-vibes:provider switch piper"
-  echo "  /agent-vibes:preview"
-fi

.claude/hooks/piper-installer.sh

@@ -1,178 +0,0 @@
-#!/bin/bash
-#
-# File: .claude/hooks/piper-installer.sh
-#
-# AgentVibes - Finally, your AI Agents can Talk Back! Text-to-Speech WITH personality for AI Assistants!
-# Website: https://agentvibes.org
-# Repository: https://github.com/paulpreibisch/AgentVibes
-#
-# Co-created by Paul Preibisch with Claude AI
-# Copyright (c) 2025 Paul Preibisch
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-# DISCLAIMER: This software is provided "AS IS", WITHOUT WARRANTY OF ANY KIND,
-# express or implied, including but not limited to the warranties of
-# merchantability, fitness for a particular purpose and noninfringement.
-# In no event shall the authors or copyright holders be liable for any claim,
-# damages or other liability, whether in an action of contract, tort or
-# otherwise, arising from, out of or in connection with the software or the
-# use or other dealings in the software.
-#
-# ---
-#
-# @fileoverview Piper TTS Installer - Installs Piper TTS via pipx and downloads initial voice models
-# @context Automated installation script for free offline Piper TTS on WSL/Linux systems
-# @architecture Helper script for AgentVibes installer, invoked manually or from provider switcher
-# @dependencies pipx (Python package installer), apt-get/brew/dnf/pacman (for pipx installation)
-# @entrypoints Called by src/installer.js or manually by users during setup
-# @patterns Platform detection (WSL/Linux only), package manager abstraction, guided voice download
-# @related piper-download-voices.sh, provider-manager.sh, src/installer.js
-#
-
-set -e  # Exit on error
-
-echo "🎤 Piper TTS Installer"
-echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-echo ""
-
-# Check if running on WSL or Linux
-if ! grep -qi microsoft /proc/version 2>/dev/null && [[ "$(uname -s)" != "Linux" ]]; then
-  echo "❌ Piper TTS is only supported on WSL and Linux"
-  echo "   Your platform: $(uname -s)"
-  echo ""
-  echo "   For macOS/Windows, use ElevenLabs instead:"
-  echo "   /agent-vibes:provider switch elevenlabs"
-  exit 1
-fi
-
-# Check if Piper is already installed
-if command -v piper &> /dev/null; then
-  # Piper doesn't have a --version flag, just check if it exists
-  echo "✅ Piper TTS is already installed!"
-  echo "   Location: $(which piper)"
-  echo ""
-  echo "   Download voices with: .claude/hooks/piper-download-voices.sh"
-  exit 0
-fi
-
-echo "📦 Installing Piper TTS..."
-echo ""
-
-# Check if pipx is installed
-if ! command -v pipx &> /dev/null; then
-  echo "⚠️  pipx not found. Installing pipx first..."
-  echo ""
-
-  # Try to install pipx
-  if command -v apt-get &> /dev/null; then
-    # Debian/Ubuntu
-    sudo apt-get update
-    sudo apt-get install -y pipx
-  elif command -v brew &> /dev/null; then
-    # macOS (though Piper doesn't run on macOS)
-    brew install pipx
-  elif command -v dnf &> /dev/null; then
-    # Fedora
-    sudo dnf install -y pipx
-  elif command -v pacman &> /dev/null; then
-    # Arch Linux
-    sudo pacman -S python-pipx
-  else
-    echo "❌ Unable to install pipx automatically."
-    echo ""
-    echo "   Please install pipx manually:"
-    echo "   https://pipx.pypa.io/stable/installation/"
-    exit 1
-  fi
-
-  # Ensure pipx is in PATH
-  pipx ensurepath
-  echo ""
-fi
-
-# Install Piper TTS
-echo "📥 Installing Piper TTS via pipx..."
-pipx install piper-tts
-
-if ! command -v piper &> /dev/null; then
-  echo ""
-  echo "❌ Installation completed but piper command not found in PATH"
-  echo ""
-  echo "   Try running: pipx ensurepath"
-  echo "   Then restart your terminal"
-  exit 1
-fi
-
-echo ""
-echo "✅ Piper TTS installed successfully!"
-echo ""
-
-PIPER_VERSION=$(piper --version 2>&1 || echo "unknown")
-echo "   Version: $PIPER_VERSION"
-echo ""
-
-# Determine voices directory
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-CLAUDE_DIR="$(dirname "$SCRIPT_DIR")"
-
-# Check for configured voices directory
-VOICES_DIR=""
-if [[ -f "$CLAUDE_DIR/piper-voices-dir.txt" ]]; then
-  VOICES_DIR=$(cat "$CLAUDE_DIR/piper-voices-dir.txt")
-elif [[ -f "$HOME/.claude/piper-voices-dir.txt" ]]; then
-  VOICES_DIR=$(cat "$HOME/.claude/piper-voices-dir.txt")
-else
-  VOICES_DIR="$HOME/.claude/piper-voices"
-fi
-
-echo "📁 Voice storage location: $VOICES_DIR"
-echo ""
-
-# Ask if user wants to download voices now
-read -p "Would you like to download voice models now? [Y/n] " -n 1 -r
-echo ""
-
-if [[ $REPLY =~ ^[Yy]$ ]] || [[ -z $REPLY ]]; then
-  echo ""
-  echo "📥 Downloading recommended voices..."
-  echo ""
-
-  # Use the piper-download-voices.sh script if available
-  if [[ -f "$SCRIPT_DIR/piper-download-voices.sh" ]]; then
-    "$SCRIPT_DIR/piper-download-voices.sh"
-  else
-    # Manual download of a basic voice
-    mkdir -p "$VOICES_DIR"
-
-    echo "Downloading en_US-lessac-medium (recommended)..."
-    curl -L "https://huggingface.co/rhasspy/piper-voices/resolve/main/en/en_US/lessac/medium/en_US-lessac-medium.onnx" \
-      -o "$VOICES_DIR/en_US-lessac-medium.onnx"
-    curl -L "https://huggingface.co/rhasspy/piper-voices/resolve/main/en/en_US/lessac/medium/en_US-lessac-medium.onnx.json" \
-      -o "$VOICES_DIR/en_US-lessac-medium.onnx.json"
-
-    echo "✅ Voice downloaded!"
-  fi
-fi
-
-echo ""
-echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-echo "🎉 Piper TTS Setup Complete!"
-echo ""
-echo "Next steps:"
-echo "  1. Download more voices: .claude/hooks/piper-download-voices.sh"
-echo "  2. List available voices: /agent-vibes:list"
-echo "  3. Test it out: /agent-vibes:preview"
-echo ""
-echo "Enjoy your free, offline TTS! 🎤"
-echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"

.claude/hooks/piper-multispeaker-registry.sh

@@ -1,165 +0,0 @@
-#!/bin/bash
-#
-# File: .claude/hooks/piper-multispeaker-registry.sh
-#
-# AgentVibes - Finally, your AI Agents can Talk Back! Text-to-Speech WITH personality for AI Assistants!
-# Website: https://agentvibes.org
-# Repository: https://github.com/paulpreibisch/AgentVibes
-#
-# Co-created by Paul Preibisch with Claude AI
-# Copyright (c) 2025 Paul Preibisch
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-# DISCLAIMER: This software is provided "AS IS", WITHOUT WARRANTY OF ANY KIND,
-# express or implied, including but not limited to the warranties of
-# merchantability, fitness for a particular purpose and noninfringement.
-# In no event shall the authors or copyright holders be liable for any claim,
-# damages or other liability, whether in an action of contract, tort or
-# otherwise, arising from, out of or in connection with the software or the
-# use or other dealings in the software.
-#
-# ---
-#
-# @fileoverview Multi-Speaker Voice Registry - Maps speaker names to ONNX models and speaker IDs
-# @context Enables individual speaker selection from multi-speaker Piper models (e.g., 16Speakers)
-# @architecture Static registry mapping speaker names to model files and numeric speaker IDs
-# @dependencies piper-voice-manager.sh (voice storage), play-tts-piper.sh (TTS with speaker ID)
-# @entrypoints Sourced by voice-manager.sh for multi-speaker voice switching
-# @patterns Registry pattern, speaker ID mapping, model-to-speaker association
-# @related voice-manager.sh, play-tts-piper.sh, 16Speakers.onnx.json (speaker_id_map)
-#
-
-# Registry of multi-speaker models and their speaker names
-# Format: "SpeakerName:model_file:speaker_id:description"
-#
-# 16Speakers Model (12 US + 4 UK voices):
-# Source: LibriVox Public Domain recordings
-# Model: 16Speakers.onnx (77MB)
-#
-MULTISPEAKER_VOICES=(
-  # US English Speakers (0-11)
-  "Cori_Samuel:16Speakers:0:US English Female"
-  "Kara_Shallenberg:16Speakers:1:US English Female"
-  "Kristin_Hughes:16Speakers:2:US English Female"
-  "Maria_Kasper:16Speakers:3:US English Female"
-  "Mike_Pelton:16Speakers:4:US English Male"
-  "Mark_Nelson:16Speakers:5:US English Male"
-  "Michael_Scherer:16Speakers:6:US English Male"
-  "James_K_White:16Speakers:7:US English Male"
-  "Rose_Ibex:16Speakers:8:US English Female"
-  "progressingamerica:16Speakers:9:US English Male"
-  "Steve_C:16Speakers:10:US English Male"
-  "Owlivia:16Speakers:11:US English Female"
-
-  # UK English Speakers (12-15)
-  "Paul_Hampton:16Speakers:12:UK English Male"
-  "Jennifer_Dorr:16Speakers:13:UK English Female"
-  "Emily_Cripps:16Speakers:14:UK English Female"
-  "Martin_Clifton:16Speakers:15:UK English Male"
-)
-
-# @function get_multispeaker_info
-# @intent Get model and speaker ID for a speaker name
-# @why Enables users to select individual speakers from multi-speaker models by name
-# @param $1 {string} speaker_name - Speaker name (e.g., "Cori_Samuel", "Rose_Ibex")
-# @returns Echoes "model:speaker_id" (e.g., "16Speakers:0") to stdout
-# @exitcode 0=speaker found, 1=speaker not found
-# @sideeffects None (read-only lookup)
-# @edgecases Case-insensitive matching
-# @calledby voice-manager.sh switch command
-# @calls None (pure bash array iteration)
-get_multispeaker_info() {
-  local speaker_name="$1"
-  for entry in "${MULTISPEAKER_VOICES[@]}"; do
-    name="${entry%%:*}"
-    rest="${entry#*:}"
-    model="${rest%%:*}"
-    rest="${rest#*:}"
-    speaker_id="${rest%%:*}"
-
-    if [[ "${name,,}" == "${speaker_name,,}" ]]; then
-      echo "$model:$speaker_id"
-      return 0
-    fi
-  done
-  return 1
-}
-
-# @function list_multispeaker_voices
-# @intent Display all available multi-speaker voices with descriptions
-# @why Help users discover individual speakers within multi-speaker models
-# @param None
-# @returns None
-# @exitcode Always 0
-# @sideeffects Writes formatted list to stdout
-# @edgecases None
-# @calledby voice-manager.sh list command, /agent-vibes:list
-# @calls None (pure bash array iteration)
-list_multispeaker_voices() {
-  echo "🎭 Multi-Speaker Voices (16Speakers Model):"
-  echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-
-  local current_model=""
-  for entry in "${MULTISPEAKER_VOICES[@]}"; do
-    name="${entry%%:*}"
-    rest="${entry#*:}"
-    model="${rest%%:*}"
-    rest="${rest#*:}"
-    speaker_id="${rest%%:*}"
-    description="${rest#*:}"
-
-    # Print section header when model changes
-    if [[ "$model" != "$current_model" ]]; then
-      if [[ -n "$current_model" ]]; then
-        echo ""
-      fi
-      echo "  Model: $model.onnx"
-      current_model="$model"
-    fi
-
-    echo "    • $name (ID: $speaker_id) - $description"
-  done
-
-  echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-  echo ""
-  echo "Usage: /agent-vibes:switch Cori_Samuel"
-  echo "       /agent-vibes:switch Rose_Ibex"
-}
-
-# @function get_multispeaker_description
-# @intent Get description for a speaker name
-# @why Provide user-friendly info about speaker characteristics
-# @param $1 {string} speaker_name - Speaker name
-# @returns Echoes description (e.g., "US English Female") to stdout
-# @exitcode 0=speaker found, 1=speaker not found
-# @sideeffects None (read-only lookup)
-# @edgecases Case-insensitive matching
-# @calledby voice-manager.sh switch command (for confirmation message)
-# @calls None (pure bash array iteration)
-get_multispeaker_description() {
-  local speaker_name="$1"
-  for entry in "${MULTISPEAKER_VOICES[@]}"; do
-    name="${entry%%:*}"
-    rest="${entry#*:}"
-    rest="${rest#*:}"
-    rest="${rest#*:}"
-    description="${rest}"
-
-    if [[ "${name,,}" == "${speaker_name,,}" ]]; then
-      echo "$description"
-      return 0
-    fi
-  done
-  return 1
-}

.claude/hooks/piper-voice-manager.sh

@@ -1,293 +0,0 @@
-#!/bin/bash
-#
-# File: .claude/hooks/piper-voice-manager.sh
-#
-# AgentVibes - Finally, your AI Agents can Talk Back! Text-to-Speech WITH personality for AI Assistants!
-# Website: https://agentvibes.org
-# Repository: https://github.com/paulpreibisch/AgentVibes
-#
-# Co-created by Paul Preibisch with Claude AI
-# Copyright (c) 2025 Paul Preibisch
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-# DISCLAIMER: This software is provided "AS IS", WITHOUT WARRANTY OF ANY KIND,
-# express or implied, including but not limited to the warranties of
-# merchantability, fitness for a particular purpose and noninfringement.
-# In no event shall the authors or copyright holders be liable for any claim,
-# damages or other liability, whether in an action of contract, tort or
-# otherwise, arising from, out of or in connection with the software or the
-# use or other dealings in the software.
-#
-# ---
-#
-# @fileoverview Piper Voice Model Management - Downloads, caches, and validates Piper ONNX voice models
-# @context Voice model lifecycle management for free offline Piper TTS provider
-# @architecture HuggingFace repository integration with local caching, global storage for voice models
-# @dependencies curl (downloads), piper binary (TTS synthesis)
-# @entrypoints Sourced by play-tts-piper.sh, piper-download-voices.sh, and provider management commands
-# @patterns HuggingFace model repository integration, file-based caching (~25MB per voice), global storage
-# @related play-tts-piper.sh, piper-download-voices.sh, provider-manager.sh, GitHub Issue #25
-#
-
-# Base URL for Piper voice models on HuggingFace
-PIPER_VOICES_BASE_URL="https://huggingface.co/rhasspy/piper-voices/resolve/main"
-
-# AI NOTE: Voice storage precedence order:
-# 1. PIPER_VOICES_DIR environment variable (highest priority)
-# 2. Project-local .claude/piper-voices-dir.txt
-# 3. Directory tree search for .claude/piper-voices-dir.txt
-# 4. Global ~/.claude/piper-voices-dir.txt
-# 5. Default ~/.claude/piper-voices (fallback)
-# This allows per-project voice isolation while defaulting to shared global storage.
-
-# @function get_voice_storage_dir
-# @intent Determine directory for storing Piper voice models with precedence chain
-# @why Voice models are large (~25MB each) and should be shared globally by default, but allow per-project overrides
-# @param None
-# @returns Echoes path to voice storage directory
-# @exitcode Always 0
-# @sideeffects Creates directory if it doesn't exist
-# @edgecases Searches up directory tree for .claude/ folder, supports custom paths via env var or config files
-# @calledby All voice management functions (verify_voice, get_voice_path, download_voice, list_downloaded_voices)
-# @calls mkdir, cat, dirname
-get_voice_storage_dir() {
-  local voice_dir
-
-  # Check for custom path in environment or config file
-  if [[ -n "$PIPER_VOICES_DIR" ]]; then
-    voice_dir="$PIPER_VOICES_DIR"
-  else
-    # Check for config file (project-local first, then global)
-    local config_file
-    if [[ -n "$CLAUDE_PROJECT_DIR" ]] && [[ -f "$CLAUDE_PROJECT_DIR/.claude/piper-voices-dir.txt" ]]; then
-      config_file="$CLAUDE_PROJECT_DIR/.claude/piper-voices-dir.txt"
-    else
-      # Search up directory tree for .claude/
-      local current_dir="$PWD"
-      while [[ "$current_dir" != "/" ]]; do
-        if [[ -f "$current_dir/.claude/piper-voices-dir.txt" ]]; then
-          config_file="$current_dir/.claude/piper-voices-dir.txt"
-          break
-        fi
-        current_dir=$(dirname "$current_dir")
-      done
-
-      # Check global config
-      if [[ -z "$config_file" ]] && [[ -f "$HOME/.claude/piper-voices-dir.txt" ]]; then
-        config_file="$HOME/.claude/piper-voices-dir.txt"
-      fi
-    fi
-
-    if [[ -n "$config_file" ]]; then
-      voice_dir=$(cat "$config_file" | tr -d '[:space:]')
-    fi
-  fi
-
-  # Fallback to default global storage
-  if [[ -z "$voice_dir" ]]; then
-    voice_dir="$HOME/.claude/piper-voices"
-  fi
-
-  mkdir -p "$voice_dir"
-  echo "$voice_dir"
-}
-
-# @function verify_voice
-# @intent Check if voice model files exist locally (both .onnx and .onnx.json)
-# @why Avoid redundant downloads, detect missing models, ensure model integrity
-# @param $1 {string} voice_name - Voice model name (e.g., en_US-lessac-medium)
-# @returns None
-# @exitcode 0=voice exists and complete, 1=voice missing or incomplete
-# @sideeffects None (read-only check)
-# @edgecases Requires both ONNX model and JSON config to return success
-# @calledby download_voice, piper-download-voices.sh
-# @calls get_voice_storage_dir
-verify_voice() {
-  local voice_name="$1"
-  local voice_dir
-  voice_dir=$(get_voice_storage_dir)
-
-  local onnx_file="$voice_dir/${voice_name}.onnx"
-  local json_file="$voice_dir/${voice_name}.onnx.json"
-
-  [[ -f "$onnx_file" ]] && [[ -f "$json_file" ]]
-}
-
-# @function get_voice_path
-# @intent Get absolute path to voice model ONNX file for Piper binary
-# @why Piper binary requires full absolute path to model file, not just voice name
-# @param $1 {string} voice_name - Voice model name
-# @returns Echoes absolute path to .onnx file to stdout
-# @exitcode 0=success, 1=voice not found
-# @sideeffects Writes error message to stderr if voice not found
-# @edgecases Returns error if voice not downloaded yet
-# @calledby play-tts-piper.sh for TTS synthesis
-# @calls get_voice_storage_dir
-get_voice_path() {
-  local voice_name="$1"
-  local voice_dir
-  voice_dir=$(get_voice_storage_dir)
-
-  local onnx_file="$voice_dir/${voice_name}.onnx"
-
-  if [[ ! -f "$onnx_file" ]]; then
-    echo "❌ Voice model not found: $voice_name" >&2
-    return 1
-  fi
-
-  echo "$onnx_file"
-}
-
-# AI NOTE: Voice name format is: lang_LOCALE-speaker-quality
-# Example: en_US-lessac-medium
-#   - lang: en (language code)
-#   - LOCALE: US (locale/country code)
-#   - speaker: lessac (speaker/voice name)
-#   - quality: medium (model quality: low/medium/high)
-# HuggingFace repository structure: {lang}/{lang}_{LOCALE}/{speaker}/{quality}/
-
-# @function parse_voice_components
-# @intent Extract language, locale, speaker, quality components from voice name
-# @why HuggingFace uses structured directory paths based on these components
-# @param $1 {string} voice_name - Voice name (e.g., en_US-lessac-medium)
-# @returns None (sets global variables)
-# @exitcode Always 0
-# @sideeffects Sets global variables: LANG, LOCALE, SPEAKER, QUALITY
-# @edgecases Expects specific format: lang_LOCALE-speaker-quality
-# @calledby download_voice
-# @calls None (pure string manipulation)
-parse_voice_components() {
-  local voice_name="$1"
-
-  # Extract components from voice name
-  # Format: en_US-lessac-medium
-  #         lang_LOCALE-speaker-quality
-
-  local lang_locale="${voice_name%%-*}"  # en_US
-  local speaker_quality="${voice_name#*-}"  # lessac-medium
-
-  LANG="${lang_locale%%_*}"  # en
-  LOCALE="${lang_locale#*_}"  # US
-  SPEAKER="${speaker_quality%%-*}"  # lessac
-  QUALITY="${speaker_quality#*-}"  # medium
-}
-
-# @function download_voice
-# @intent Download Piper voice model from HuggingFace repository
-# @why Provide free offline TTS voices without requiring API keys
-# @param $1 {string} voice_name - Voice model name (e.g., en_US-lessac-medium)
-# @param $2 {string} lang_code - Language code (optional, inferred from voice_name, unused)
-# @returns None
-# @exitcode 0=success (already downloaded or newly downloaded), 1=download failed
-# @sideeffects Downloads .onnx and .onnx.json files (~25MB total), removes partial downloads on failure
-# @edgecases Handles network failures, validates file integrity (non-zero size), skips if already downloaded
-# @calledby piper-download-voices.sh, manual voice download commands
-# @calls parse_voice_components, verify_voice, get_voice_storage_dir, curl, rm
-download_voice() {
-  local voice_name="$1"
-  local lang_code="${2:-}"
-
-  local voice_dir
-  voice_dir=$(get_voice_storage_dir)
-
-  # Check if already downloaded
-  if verify_voice "$voice_name"; then
-    echo "✅ Voice already downloaded: $voice_name"
-    return 0
-  fi
-
-  # Parse voice components
-  parse_voice_components "$voice_name"
-
-  # Construct download URLs
-  # Path format: {language}/{language}_{locale}/{speaker}/{quality}/{speaker}-{quality}.onnx
-  local model_path="${LANG}/${LANG}_${LOCALE}/${SPEAKER}/${QUALITY}/${voice_name}"
-  local onnx_url="${PIPER_VOICES_BASE_URL}/${model_path}.onnx"
-  local json_url="${PIPER_VOICES_BASE_URL}/${model_path}.onnx.json"
-
-  echo "📥 Downloading Piper voice: $voice_name"
-  echo "   Source: HuggingFace (rhasspy/piper-voices)"
-  echo "   Size: ~25MB"
-  echo ""
-
-  # Download ONNX model
-  echo "   Downloading model file..."
-  if ! curl -L --progress-bar -o "$voice_dir/${voice_name}.onnx" "$onnx_url"; then
-    echo "❌ Failed to download voice model"
-    rm -f "$voice_dir/${voice_name}.onnx"
-    return 1
-  fi
-
-  # Download JSON config
-  echo "   Downloading config file..."
-  if ! curl -L -s -o "$voice_dir/${voice_name}.onnx.json" "$json_url"; then
-    echo "❌ Failed to download voice config"
-    rm -f "$voice_dir/${voice_name}.onnx" "$voice_dir/${voice_name}.onnx.json"
-    return 1
-  fi
-
-  # Verify file integrity (basic check - file size > 0)
-  if [[ ! -s "$voice_dir/${voice_name}.onnx" ]]; then
-    echo "❌ Downloaded file is empty or corrupt"
-    rm -f "$voice_dir/${voice_name}.onnx" "$voice_dir/${voice_name}.onnx.json"
-    return 1
-  fi
-
-  echo "✅ Voice downloaded successfully: $voice_name"
-  echo "   Location: $voice_dir/${voice_name}.onnx"
-}
-
-# @function list_downloaded_voices
-# @intent Display all locally cached voice models with file sizes
-# @why Help users see what voices they have available and storage usage
-# @param None
-# @returns None
-# @exitcode Always 0
-# @sideeffects Writes formatted list to stdout
-# @edgecases Handles empty voice directory gracefully, uses nullglob to avoid literal *.onnx
-# @calledby Voice management commands, /agent-vibes:list
-# @calls get_voice_storage_dir, basename, du
-list_downloaded_voices() {
-  local voice_dir
-  voice_dir=$(get_voice_storage_dir)
-
-  echo "📦 Downloaded Piper Voices:"
-  echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-
-  local count=0
-  shopt -s nullglob
-  for onnx_file in "$voice_dir"/*.onnx; do
-    if [[ -f "$onnx_file" ]]; then
-      local voice_name
-      voice_name=$(basename "$onnx_file" .onnx)
-      local file_size
-      file_size=$(du -h "$onnx_file" | cut -f1)
-      echo "  • $voice_name ($file_size)"
-      ((count++))
-    fi
-  done
-  shopt -u nullglob
-
-  if [[ $count -eq 0 ]]; then
-    echo "  (No voices downloaded yet)"
-  fi
-
-  echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-  echo "Total: $count voices"
-}
-
-# AI NOTE: This file manages the lifecycle of Piper voice models
-# Voice models are ONNX files (~20-30MB each) downloaded from HuggingFace
-# Files are cached locally to avoid repeated downloads
-# Project-local storage preferred over global for isolation

.claude/hooks/play-tts-elevenlabs.sh

@@ -1,404 +0,0 @@
-#!/bin/bash
-#
-# File: .claude/hooks/play-tts-elevenlabs.sh
-#
-# AgentVibes - Finally, your AI Agents can Talk Back! Text-to-Speech WITH personality for AI Assistants!
-# Website: https://agentvibes.org
-# Repository: https://github.com/paulpreibisch/AgentVibes
-#
-# Co-created by Paul Preibisch with Claude AI
-# Copyright (c) 2025 Paul Preibisch
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-# DISCLAIMER: This software is provided "AS IS", WITHOUT WARRANTY OF ANY KIND,
-# express or implied. Use at your own risk. See the Apache License for details.
-#
-# ---
-#
-# @fileoverview ElevenLabs TTS Provider Implementation - Premium cloud-based TTS
-# @context Provider-specific implementation for ElevenLabs API integration with multilingual support
-# @architecture Part of multi-provider TTS system - implements provider interface contract
-# @dependencies Requires ELEVENLABS_API_KEY, curl, ffmpeg, paplay/aplay/mpg123, jq
-# @entrypoints Called by play-tts.sh router with ($1=text, $2=voice_name) when provider=elevenlabs
-# @patterns Follows provider contract: accept text/voice, output audio file path, API error handling, SSH audio optimization
-# @related play-tts.sh, provider-manager.sh, voices-config.sh, language-manager.sh, GitHub Issue #25
-#
-
-# Fix locale warnings
-export LC_ALL=C
-
-TEXT="$1"
-VOICE_OVERRIDE="$2"  # Optional: voice name or direct voice ID
-API_KEY="${ELEVENLABS_API_KEY}"
-
-# Check for project-local pretext configuration
-CONFIG_DIR="${CLAUDE_PROJECT_DIR:-.}/.claude/config"
-CONFIG_FILE="$CONFIG_DIR/agentvibes.json"
-
-if [[ -f "$CONFIG_FILE" ]] && command -v jq &> /dev/null; then
-  PRETEXT=$(jq -r '.pretext // empty' "$CONFIG_FILE" 2>/dev/null)
-  if [[ -n "$PRETEXT" ]]; then
-    TEXT="$PRETEXT: $TEXT"
-  fi
-fi
-
-# Limit text length to prevent API issues (max 500 chars for safety)
-if [ ${#TEXT} -gt 500 ]; then
-  TEXT="${TEXT:0:497}..."
-  echo "⚠️ Text truncated to 500 characters for API safety"
-fi
-
-# Source the single voice configuration file
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-source "$SCRIPT_DIR/voices-config.sh"
-source "$SCRIPT_DIR/language-manager.sh"
-
-# @function determine_voice_and_language
-# @intent Resolve voice name/ID and language for multilingual support
-# @why Supports both voice names and direct IDs, plus language-specific voices
-# @param $VOICE_OVERRIDE {string} Voice name or ID (optional)
-# @returns Sets $VOICE_ID and $LANGUAGE_CODE global variables
-# @sideeffects None
-# @edgecases Handles unknown voices, falls back to default
-VOICE_ID=""
-LANGUAGE_CODE="en"  # Default to English
-
-# Get current language setting
-CURRENT_LANGUAGE=$(get_language_code)
-
-# Get language code for API
-# ElevenLabs uses 2-letter ISO codes
-case "$CURRENT_LANGUAGE" in
-  spanish) LANGUAGE_CODE="es" ;;
-  french) LANGUAGE_CODE="fr" ;;
-  german) LANGUAGE_CODE="de" ;;
-  italian) LANGUAGE_CODE="it" ;;
-  portuguese) LANGUAGE_CODE="pt" ;;
-  chinese) LANGUAGE_CODE="zh" ;;
-  japanese) LANGUAGE_CODE="ja" ;;
-  korean) LANGUAGE_CODE="ko" ;;
-  russian) LANGUAGE_CODE="ru" ;;
-  polish) LANGUAGE_CODE="pl" ;;
-  dutch) LANGUAGE_CODE="nl" ;;
-  turkish) LANGUAGE_CODE="tr" ;;
-  arabic) LANGUAGE_CODE="ar" ;;
-  hindi) LANGUAGE_CODE="hi" ;;
-  swedish) LANGUAGE_CODE="sv" ;;
-  danish) LANGUAGE_CODE="da" ;;
-  norwegian) LANGUAGE_CODE="no" ;;
-  finnish) LANGUAGE_CODE="fi" ;;
-  czech) LANGUAGE_CODE="cs" ;;
-  romanian) LANGUAGE_CODE="ro" ;;
-  ukrainian) LANGUAGE_CODE="uk" ;;
-  greek) LANGUAGE_CODE="el" ;;
-  bulgarian) LANGUAGE_CODE="bg" ;;
-  croatian) LANGUAGE_CODE="hr" ;;
-  slovak) LANGUAGE_CODE="sk" ;;
-  english|*) LANGUAGE_CODE="en" ;;
-esac
-
-if [[ -n "$VOICE_OVERRIDE" ]]; then
-  # Check if override is a voice name (lookup in mapping)
-  if [[ -n "${VOICES[$VOICE_OVERRIDE]}" ]]; then
-    VOICE_ID="${VOICES[$VOICE_OVERRIDE]}"
-    echo "🎤 Using voice: $VOICE_OVERRIDE (session-specific)"
-  # Check if override looks like a voice ID (alphanumeric string ~20 chars)
-  elif [[ "$VOICE_OVERRIDE" =~ ^[a-zA-Z0-9]{15,30}$ ]]; then
-    VOICE_ID="$VOICE_OVERRIDE"
-    echo "🎤 Using custom voice ID (session-specific)"
-  else
-    echo "⚠️ Unknown voice '$VOICE_OVERRIDE', trying language-specific voice"
-  fi
-fi
-
-# If no override or invalid override, use language-specific voice
-if [[ -z "$VOICE_ID" ]]; then
-  # Try to get voice for current language
-  LANG_VOICE=$(get_voice_for_language "$CURRENT_LANGUAGE" "elevenlabs" 2>/dev/null)
-
-  if [[ -n "$LANG_VOICE" ]] && [[ -n "${VOICES[$LANG_VOICE]}" ]]; then
-    VOICE_ID="${VOICES[$LANG_VOICE]}"
-    echo "🌍 Using $CURRENT_LANGUAGE voice: $LANG_VOICE"
-  else
-    # Fall back to voice manager
-    VOICE_MANAGER_SCRIPT="$(dirname "$0")/voice-manager.sh"
-    if [[ -f "$VOICE_MANAGER_SCRIPT" ]]; then
-      VOICE_NAME=$("$VOICE_MANAGER_SCRIPT" get)
-      VOICE_ID="${VOICES[$VOICE_NAME]}"
-    fi
-
-    # Final fallback to default
-    if [[ -z "$VOICE_ID" ]]; then
-      echo "⚠️ No voice configured, using default"
-      VOICE_ID="${VOICES[Aria]}"
-    fi
-  fi
-fi
-
-# @function validate_inputs
-# @intent Check required parameters and API key
-# @why Fail fast with clear errors if inputs missing
-# @exitcode 1=missing text, 2=missing API key
-if [ -z "$TEXT" ]; then
-  echo "Usage: $0 \"text to speak\" [voice_name_or_id]"
-  exit 1
-fi
-
-if [ -z "$API_KEY" ]; then
-  echo "Error: ELEVENLABS_API_KEY not set"
-  echo "Set your API key: export ELEVENLABS_API_KEY=your_key_here"
-  exit 2
-fi
-
-# @function determine_audio_directory
-# @intent Find appropriate directory for audio file storage
-# @why Supports project-local and global storage
-# @returns Sets $AUDIO_DIR global variable
-# @sideeffects None
-# @edgecases Handles missing directories, creates if needed
-# AI NOTE: Check project dir first, then search up tree, finally fall back to global
-if [[ -n "$CLAUDE_PROJECT_DIR" ]]; then
-  AUDIO_DIR="$CLAUDE_PROJECT_DIR/.claude/audio"
-else
-  # Fallback: try to find .claude directory in current path
-  CURRENT_DIR="$PWD"
-  while [[ "$CURRENT_DIR" != "/" ]]; do
-    if [[ -d "$CURRENT_DIR/.claude" ]]; then
-      AUDIO_DIR="$CURRENT_DIR/.claude/audio"
-      break
-    fi
-    CURRENT_DIR=$(dirname "$CURRENT_DIR")
-  done
-  # Final fallback to global if no project .claude found
-  if [[ -z "$AUDIO_DIR" ]]; then
-    AUDIO_DIR="$HOME/.claude/audio"
-  fi
-fi
-
-mkdir -p "$AUDIO_DIR"
-TEMP_FILE="$AUDIO_DIR/tts-$(date +%s).mp3"
-
-# @function synthesize_with_elevenlabs
-# @intent Call ElevenLabs API to generate speech
-# @why Encapsulates API call with error handling
-# @param Uses globals: $TEXT, $VOICE_ID, $API_KEY
-# @returns Creates audio file at $TEMP_FILE
-# @exitcode 0=success, 3=API error
-# @sideeffects Creates MP3 file in audio directory
-# @edgecases Handles network failures, API errors, rate limiting
-# Choose model based on language
-if [[ "$LANGUAGE_CODE" == "en" ]]; then
-  MODEL_ID="eleven_monolingual_v1"
-else
-  MODEL_ID="eleven_multilingual_v2"
-fi
-
-# @function get_speech_speed
-# @intent Read speed config and map to ElevenLabs API range (0.7-1.2)
-# @why ElevenLabs only supports 0.7 (slower) to 1.2 (faster), must map user scale
-# @returns Speed value for ElevenLabs API (clamped to 0.7-1.2)
-get_speech_speed() {
-  local config_dir=""
-
-  # Determine config directory
-  if [[ -n "$CLAUDE_PROJECT_DIR" ]] && [[ -d "$CLAUDE_PROJECT_DIR/.claude" ]]; then
-    config_dir="$CLAUDE_PROJECT_DIR/.claude/config"
-  else
-    # Try to find .claude in current path
-    local current_dir="$PWD"
-    while [[ "$current_dir" != "/" ]]; do
-      if [[ -d "$current_dir/.claude" ]]; then
-        config_dir="$current_dir/.claude/config"
-        break
-      fi
-      current_dir=$(dirname "$current_dir")
-    done
-    # Fallback to global
-    if [[ -z "$config_dir" ]]; then
-      config_dir="$HOME/.claude/config"
-    fi
-  fi
-
-  local main_speed_file="$config_dir/tts-speech-rate.txt"
-  local target_speed_file="$config_dir/tts-target-speech-rate.txt"
-
-  # Legacy file paths for backward compatibility
-  local legacy_main_speed_file="$config_dir/piper-speech-rate.txt"
-  local legacy_target_speed_file="$config_dir/piper-target-speech-rate.txt"
-
-  local user_speed="1.0"
-
-  # If this is a non-English voice and target config exists, use it
-  if [[ "$CURRENT_LANGUAGE" != "english" ]]; then
-    if [[ -f "$target_speed_file" ]]; then
-      user_speed=$(cat "$target_speed_file" 2>/dev/null || echo "1.0")
-    elif [[ -f "$legacy_target_speed_file" ]]; then
-      user_speed=$(cat "$legacy_target_speed_file" 2>/dev/null || echo "1.0")
-    else
-      user_speed="0.5"  # Default slower for learning
-    fi
-  else
-    # Otherwise use main config if available
-    if [[ -f "$main_speed_file" ]]; then
-      user_speed=$(grep -v '^#' "$main_speed_file" 2>/dev/null | grep -v '^$' | tail -1 || echo "1.0")
-    elif [[ -f "$legacy_main_speed_file" ]]; then
-      user_speed=$(grep -v '^#' "$legacy_main_speed_file" 2>/dev/null | grep -v '^$' | tail -1 || echo "1.0")
-    fi
-  fi
-
-  # Map user scale (0.5=slower, 1.0=normal, 2.0=faster, 3.0=very fast)
-  # to ElevenLabs range (0.7=slower, 1.0=normal, 1.2=faster)
-  # Formula: elevenlabs_speed = 0.7 + (user_speed - 0.5) * 0.2
-  # This maps: 0.5→0.7, 1.0→0.8, 2.0→1.0, 3.0→1.2
-  # Actually, let's use a better mapping:
-  # 0.5x → 0.7 (slowest ElevenLabs)
-  # 1.0x → 1.0 (normal)
-  # 2.0x → 1.15
-  # 3.0x → 1.2 (fastest ElevenLabs)
-
-  if command -v bc &> /dev/null; then
-    local eleven_speed
-    if (( $(echo "$user_speed <= 0.5" | bc -l) )); then
-      eleven_speed="0.7"
-    elif (( $(echo "$user_speed >= 3.0" | bc -l) )); then
-      eleven_speed="1.2"
-    elif (( $(echo "$user_speed <= 1.0" | bc -l) )); then
-      # Map 0.5-1.0 to 0.7-1.0
-      eleven_speed=$(echo "scale=2; 0.7 + ($user_speed - 0.5) * 0.6" | bc -l)
-    else
-      # Map 1.0-3.0 to 1.0-1.2
-      eleven_speed=$(echo "scale=2; 1.0 + ($user_speed - 1.0) * 0.1" | bc -l)
-    fi
-    echo "$eleven_speed"
-  else
-    # Fallback without bc: just clamp to safe values
-    if (( $(awk 'BEGIN {print ("'$user_speed'" <= 0.5)}') )); then
-      echo "0.7"
-    elif (( $(awk 'BEGIN {print ("'$user_speed'" >= 2.0)}') )); then
-      echo "1.2"
-    else
-      echo "1.0"
-    fi
-  fi
-}
-
-SPEECH_SPEED=$(get_speech_speed)
-
-# Build JSON payload with jq for proper escaping
-PAYLOAD=$(jq -n \
-  --arg text "$TEXT" \
-  --arg model "$MODEL_ID" \
-  --arg lang "$LANGUAGE_CODE" \
-  --argjson speed "$SPEECH_SPEED" \
-  '{
-    text: $text,
-    model_id: $model,
-    language_code: $lang,
-    voice_settings: {
-      stability: 0.5,
-      similarity_boost: 0.75,
-      speed: $speed
-    }
-  }')
-
-curl -s -X POST "https://api.elevenlabs.io/v1/text-to-speech/${VOICE_ID}" \
-  -H "xi-api-key: ${API_KEY}" \
-  -H "Content-Type: application/json" \
-  -d "$PAYLOAD" \
-  -o "${TEMP_FILE}"
-
-# @function add_silence_padding
-# @intent Add silence to beginning of audio to prevent WSL static
-# @why WSL audio subsystem cuts off first ~200ms, causing static/clipping
-# @param Uses global: $TEMP_FILE
-# @returns Updates $TEMP_FILE to padded version
-# @sideeffects Modifies audio file, removes original
-# @edgecases Gracefully falls back to unpadded if ffmpeg unavailable
-# Add silence padding to prevent WSL audio static
-if [ -f "${TEMP_FILE}" ]; then
-  # Check if ffmpeg is available for adding padding
-  if command -v ffmpeg &> /dev/null; then
-    PADDED_FILE="$AUDIO_DIR/tts-padded-$(date +%s).mp3"
-    # Add 200ms of silence at the beginning to prevent static
-    # Note: ElevenLabs returns mono audio, so we use mono silence
-    ffmpeg -f lavfi -i anullsrc=r=44100:cl=mono:d=0.2 -i "${TEMP_FILE}" \
-      -filter_complex "[0:a][1:a]concat=n=2:v=0:a=1[out]" \
-      -map "[out]" -c:a libmp3lame -b:a 128k -y "${PADDED_FILE}" 2>/dev/null
-
-    if [ -f "${PADDED_FILE}" ]; then
-      # Use padded file and clean up original
-      rm -f "${TEMP_FILE}"
-      TEMP_FILE="${PADDED_FILE}"
-    fi
-    # If padding failed, just use original file
-  fi
-
-  # @function play_audio
-  # @intent Play generated audio file using available player with sequential playback
-  # @why Support multiple audio players and prevent overlapping audio in learning mode
-  # @param Uses global: $TEMP_FILE, $CURRENT_LANGUAGE
-  # @sideeffects Plays audio with lock mechanism for sequential playback
-  # @edgecases Falls through players until one works
-  LOCK_FILE="/tmp/agentvibes-audio.lock"
-
-  # Wait for previous audio to finish (max 30 seconds)
-  for i in {1..60}; do
-    if [ ! -f "$LOCK_FILE" ]; then
-      break
-    fi
-    sleep 0.5
-  done
-
-  # Track last target language audio for replay command
-  if [[ "$CURRENT_LANGUAGE" != "english" ]]; then
-    TARGET_AUDIO_FILE="${CLAUDE_PROJECT_DIR:-.}/.claude/last-target-audio.txt"
-    echo "${TEMP_FILE}" > "$TARGET_AUDIO_FILE"
-  fi
-
-  # Create lock and play audio
-  touch "$LOCK_FILE"
-
-  # Get audio duration for proper lock timing
-  DURATION=$(ffprobe -v error -show_entries format=duration -of default=noprint_wrappers=1:nokey=1 "${TEMP_FILE}" 2>/dev/null)
-  DURATION=${DURATION%.*}  # Round to integer
-  DURATION=${DURATION:-1}   # Default to 1 second if detection fails
-
-  # Convert to 48kHz stereo WAV for better SSH tunnel compatibility
-  # ElevenLabs returns 44.1kHz mono MP3, which causes static over SSH audio tunnels
-  # Converting to 48kHz stereo (Windows/PulseAudio native format) eliminates the static
-  if [[ -n "$SSH_CONNECTION" ]] || [[ -n "$SSH_CLIENT" ]] || [[ -n "$VSCODE_IPC_HOOK_CLI" ]]; then
-    CONVERTED_FILE="${TEMP_FILE%.mp3}.wav"
-    if ffmpeg -i "${TEMP_FILE}" -ar 48000 -ac 2 "${CONVERTED_FILE}" -y 2>/dev/null; then
-      TEMP_FILE="${CONVERTED_FILE}"
-    fi
-  fi
-
-  # Play audio (WSL/Linux) in background to avoid blocking, fully detached (skip if in test mode)
-  if [[ "${AGENTVIBES_TEST_MODE:-false}" != "true" ]]; then
-    (paplay "${TEMP_FILE}" || aplay "${TEMP_FILE}" || mpg123 "${TEMP_FILE}") >/dev/null 2>&1 &
-    PLAYER_PID=$!
-  fi
-
-  # Wait for audio to finish, then release lock
-  (sleep $DURATION; rm -f "$LOCK_FILE") &
-  disown
-
-  # Keep temp files for later review - cleaned up weekly by cron
-  echo "🎵 Saved to: ${TEMP_FILE}"
-  echo "🎤 Voice used: ${VOICE_NAME} (${VOICE_ID})"
-else
-  echo "❌ Failed to generate audio - API may be unavailable"
-  echo "Check your API key and network connection"
-  exit 3
-fi

.claude/hooks/play-tts-piper.sh

@@ -1,338 +0,0 @@
-#!/bin/bash
-#
-# File: .claude/hooks/play-tts-piper.sh
-#
-# AgentVibes - Finally, your AI Agents can Talk Back! Text-to-Speech WITH personality for AI Assistants!
-# Website: https://agentvibes.org
-# Repository: https://github.com/paulpreibisch/AgentVibes
-#
-# Co-created by Paul Preibisch with Claude AI
-# Copyright (c) 2025 Paul Preibisch
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-# DISCLAIMER: This software is provided "AS IS", WITHOUT WARRANTY OF ANY KIND,
-# express or implied. Use at your own risk. See the Apache License for details.
-#
-# ---
-#
-# @fileoverview Piper TTS Provider Implementation - Free, offline neural TTS
-# @context Provides local, privacy-first TTS alternative to cloud services for WSL/Linux
-# @architecture Implements provider interface contract for Piper binary integration
-# @dependencies piper (pipx), piper-voice-manager.sh, mpv/aplay, ffmpeg (optional padding)
-# @entrypoints Called by play-tts.sh router when provider=piper
-# @patterns Provider contract: text/voice → audio file path, voice auto-download, language-aware synthesis
-# @related play-tts.sh, piper-voice-manager.sh, language-manager.sh, GitHub Issue #25
-#
-
-# Fix locale warnings
-export LC_ALL=C
-
-TEXT="$1"
-VOICE_OVERRIDE="$2"  # Optional: voice model name
-
-# Source voice manager and language manager
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-source "$SCRIPT_DIR/piper-voice-manager.sh"
-source "$SCRIPT_DIR/language-manager.sh"
-
-# Default voice for Piper
-DEFAULT_VOICE="en_US-lessac-medium"
-
-# @function determine_voice_model
-# @intent Resolve voice name to Piper model name with language support
-# @why Support voice override, language-specific voices, and default fallback
-# @param Uses global: $VOICE_OVERRIDE
-# @returns Sets $VOICE_MODEL global variable
-# @sideeffects None
-VOICE_MODEL=""
-
-# Get current language setting
-CURRENT_LANGUAGE=$(get_language_code)
-
-if [[ -n "$VOICE_OVERRIDE" ]]; then
-  # Use override if provided
-  VOICE_MODEL="$VOICE_OVERRIDE"
-  echo "🎤 Using voice: $VOICE_OVERRIDE (session-specific)"
-else
-  # Try to get voice from voice file (check CLAUDE_PROJECT_DIR first for MCP context)
-  VOICE_FILE=""
-
-  # Priority order:
-  # 1. CLAUDE_PROJECT_DIR env var (set by MCP for project-specific settings)
-  # 2. Script location (for direct slash command usage)
-  # 3. Global ~/.claude (fallback)
-
-  if [[ -n "$CLAUDE_PROJECT_DIR" ]] && [[ -f "$CLAUDE_PROJECT_DIR/.claude/tts-voice.txt" ]]; then
-    # MCP context: Use the project directory where MCP was invoked
-    VOICE_FILE="$CLAUDE_PROJECT_DIR/.claude/tts-voice.txt"
-  elif [[ -f "$SCRIPT_DIR/../tts-voice.txt" ]]; then
-    # Direct usage: Use script location
-    VOICE_FILE="$SCRIPT_DIR/../tts-voice.txt"
-  elif [[ -f "$HOME/.claude/tts-voice.txt" ]]; then
-    # Fallback: Use global
-    VOICE_FILE="$HOME/.claude/tts-voice.txt"
-  fi
-
-  if [[ -n "$VOICE_FILE" ]]; then
-    FILE_VOICE=$(cat "$VOICE_FILE" 2>/dev/null)
-
-    # Check for multi-speaker voice (model + speaker ID stored separately)
-    # Use same directory as VOICE_FILE for consistency
-    VOICE_DIR=$(dirname "$VOICE_FILE")
-    MODEL_FILE="$VOICE_DIR/tts-piper-model.txt"
-    SPEAKER_ID_FILE="$VOICE_DIR/tts-piper-speaker-id.txt"
-
-    if [[ -f "$MODEL_FILE" ]] && [[ -f "$SPEAKER_ID_FILE" ]]; then
-      # Multi-speaker voice
-      VOICE_MODEL=$(cat "$MODEL_FILE" 2>/dev/null)
-      SPEAKER_ID=$(cat "$SPEAKER_ID_FILE" 2>/dev/null)
-      echo "🎭 Using multi-speaker voice: $FILE_VOICE (Model: $VOICE_MODEL, Speaker ID: $SPEAKER_ID)"
-    # Check if it's a standard Piper model name or custom voice (just use as-is)
-    elif [[ -n "$FILE_VOICE" ]]; then
-      VOICE_MODEL="$FILE_VOICE"
-    fi
-  fi
-
-  # If no Piper voice from file, try language-specific voice
-  if [[ -z "$VOICE_MODEL" ]]; then
-    LANG_VOICE=$(get_voice_for_language "$CURRENT_LANGUAGE" "piper" 2>/dev/null)
-
-    if [[ -n "$LANG_VOICE" ]]; then
-      VOICE_MODEL="$LANG_VOICE"
-      echo "🌍 Using $CURRENT_LANGUAGE voice: $LANG_VOICE (Piper)"
-    else
-      # Use default voice
-      VOICE_MODEL="$DEFAULT_VOICE"
-    fi
-  fi
-fi
-
-# @function validate_inputs
-# @intent Check required parameters
-# @why Fail fast with clear errors if inputs missing
-# @exitcode 1=missing text, 2=missing piper binary
-if [[ -z "$TEXT" ]]; then
-  echo "Usage: $0 \"text to speak\" [voice_model_name]"
-  exit 1
-fi
-
-# Check if Piper is installed
-if ! command -v piper &> /dev/null; then
-  echo "❌ Error: Piper TTS not installed"
-  echo "Install with: pipx install piper-tts"
-  echo "Or run: .claude/hooks/piper-installer.sh"
-  exit 2
-fi
-
-# @function ensure_voice_downloaded
-# @intent Download voice model if not cached
-# @why Provide seamless experience with automatic downloads
-# @param Uses global: $VOICE_MODEL
-# @sideeffects Downloads voice model files
-# @edgecases Prompts user for consent before downloading
-if ! verify_voice "$VOICE_MODEL"; then
-  echo "📥 Voice model not found: $VOICE_MODEL"
-  echo "   File size: ~25MB"
-  echo "   Preview: https://huggingface.co/rhasspy/piper-voices"
-  echo ""
-  read -p "   Download this voice model? [y/N]: " -n 1 -r
-  echo
-
-  if [[ $REPLY =~ ^[Yy]$ ]]; then
-    if ! download_voice "$VOICE_MODEL"; then
-      echo "❌ Failed to download voice model"
-      echo "Fix: Download manually or choose different voice"
-      exit 3
-    fi
-  else
-    echo "❌ Voice download cancelled"
-    exit 3
-  fi
-fi
-
-# Get voice model path
-VOICE_PATH=$(get_voice_path "$VOICE_MODEL")
-if [[ $? -ne 0 ]]; then
-  echo "❌ Voice model path not found: $VOICE_MODEL"
-  exit 3
-fi
-
-# @function determine_audio_directory
-# @intent Find appropriate directory for audio file storage
-# @why Supports project-local and global storage
-# @returns Sets $AUDIO_DIR global variable
-if [[ -n "$CLAUDE_PROJECT_DIR" ]]; then
-  AUDIO_DIR="$CLAUDE_PROJECT_DIR/.claude/audio"
-else
-  # Fallback: try to find .claude directory in current path
-  CURRENT_DIR="$PWD"
-  while [[ "$CURRENT_DIR" != "/" ]]; do
-    if [[ -d "$CURRENT_DIR/.claude" ]]; then
-      AUDIO_DIR="$CURRENT_DIR/.claude/audio"
-      break
-    fi
-    CURRENT_DIR=$(dirname "$CURRENT_DIR")
-  done
-  # Final fallback to global if no project .claude found
-  if [[ -z "$AUDIO_DIR" ]]; then
-    AUDIO_DIR="$HOME/.claude/audio"
-  fi
-fi
-
-mkdir -p "$AUDIO_DIR"
-TEMP_FILE="$AUDIO_DIR/tts-$(date +%s).wav"
-
-# @function get_speech_rate
-# @intent Determine speech rate for Piper synthesis
-# @why Convert user-facing speed (0.5=slower, 2.0=faster) to Piper length-scale (inverted)
-# @returns Piper length-scale value (inverted from user scale)
-# @note Piper uses length-scale where higher=slower, opposite of user expectation
-get_speech_rate() {
-  local target_config=""
-  local main_config=""
-
-  # Check for target-specific config first (new and legacy paths)
-  if [[ -f "$SCRIPT_DIR/../config/tts-target-speech-rate.txt" ]]; then
-    target_config="$SCRIPT_DIR/../config/tts-target-speech-rate.txt"
-  elif [[ -f "$HOME/.claude/config/tts-target-speech-rate.txt" ]]; then
-    target_config="$HOME/.claude/config/tts-target-speech-rate.txt"
-  elif [[ -f "$SCRIPT_DIR/../config/piper-target-speech-rate.txt" ]]; then
-    target_config="$SCRIPT_DIR/../config/piper-target-speech-rate.txt"
-  elif [[ -f "$HOME/.claude/config/piper-target-speech-rate.txt" ]]; then
-    target_config="$HOME/.claude/config/piper-target-speech-rate.txt"
-  fi
-
-  # Check for main config (new and legacy paths)
-  if [[ -f "$SCRIPT_DIR/../config/tts-speech-rate.txt" ]]; then
-    main_config="$SCRIPT_DIR/../config/tts-speech-rate.txt"
-  elif [[ -f "$HOME/.claude/config/tts-speech-rate.txt" ]]; then
-    main_config="$HOME/.claude/config/tts-speech-rate.txt"
-  elif [[ -f "$SCRIPT_DIR/../config/piper-speech-rate.txt" ]]; then
-    main_config="$SCRIPT_DIR/../config/piper-speech-rate.txt"
-  elif [[ -f "$HOME/.claude/config/piper-speech-rate.txt" ]]; then
-    main_config="$HOME/.claude/config/piper-speech-rate.txt"
-  fi
-
-  # If this is a non-English voice and target config exists, use it
-  if [[ "$CURRENT_LANGUAGE" != "english" ]] && [[ -n "$target_config" ]]; then
-    local user_speed=$(cat "$target_config" 2>/dev/null)
-    # Convert user speed to Piper length-scale (invert)
-    # User: 0.5=slower, 1.0=normal, 2.0=faster
-    # Piper: 2.0=slower, 1.0=normal, 0.5=faster
-    # Formula: piper_length_scale = 1.0 / user_speed
-    echo "scale=2; 1.0 / $user_speed" | bc -l 2>/dev/null || echo "1.0"
-    return
-  fi
-
-  # Otherwise use main config if available
-  if [[ -n "$main_config" ]]; then
-    local user_speed=$(grep -v '^#' "$main_config" 2>/dev/null | grep -v '^$' | tail -1)
-    echo "scale=2; 1.0 / $user_speed" | bc -l 2>/dev/null || echo "1.0"
-    return
-  fi
-
-  # Default: 1.0 (normal) for English, 2.0 (slower) for learning
-  if [[ "$CURRENT_LANGUAGE" != "english" ]]; then
-    echo "2.0"
-  else
-    echo "1.0"
-  fi
-}
-
-SPEECH_RATE=$(get_speech_rate)
-
-# @function synthesize_with_piper
-# @intent Generate speech using Piper TTS
-# @why Provides free, offline TTS alternative
-# @param Uses globals: $TEXT, $VOICE_PATH, $SPEECH_RATE, $SPEAKER_ID (optional)
-# @returns Creates WAV file at $TEMP_FILE
-# @exitcode 0=success, 4=synthesis error
-# @sideeffects Creates audio file
-# @edgecases Handles piper errors, invalid models, multi-speaker voices
-if [[ -n "$SPEAKER_ID" ]]; then
-  # Multi-speaker voice: Pass speaker ID
-  echo "$TEXT" | piper --model "$VOICE_PATH" --speaker "$SPEAKER_ID" --length-scale "$SPEECH_RATE" --output_file "$TEMP_FILE" 2>/dev/null
-else
-  # Single-speaker voice
-  echo "$TEXT" | piper --model "$VOICE_PATH" --length-scale "$SPEECH_RATE" --output_file "$TEMP_FILE" 2>/dev/null
-fi
-
-if [[ ! -f "$TEMP_FILE" ]] || [[ ! -s "$TEMP_FILE" ]]; then
-  echo "❌ Failed to synthesize speech with Piper"
-  echo "Voice model: $VOICE_MODEL"
-  echo "Check that voice model is valid"
-  exit 4
-fi
-
-# @function add_silence_padding
-# @intent Add silence to prevent WSL audio static
-# @why WSL audio subsystem cuts off first ~200ms
-# @param Uses global: $TEMP_FILE
-# @returns Updates $TEMP_FILE to padded version
-# @sideeffects Modifies audio file
-# AI NOTE: Use ffmpeg if available, otherwise skip padding (degraded experience)
-if command -v ffmpeg &> /dev/null; then
-  PADDED_FILE="$AUDIO_DIR/tts-padded-$(date +%s).wav"
-  # Add 200ms of silence at the beginning
-  ffmpeg -f lavfi -i anullsrc=r=44100:cl=stereo:d=0.2 -i "$TEMP_FILE" \
-    -filter_complex "[0:a][1:a]concat=n=2:v=0:a=1[out]" \
-    -map "[out]" -y "$PADDED_FILE" 2>/dev/null
-
-  if [[ -f "$PADDED_FILE" ]]; then
-    rm -f "$TEMP_FILE"
-    TEMP_FILE="$PADDED_FILE"
-  fi
-fi
-
-# @function play_audio
-# @intent Play generated audio using available player with sequential playback
-# @why Support multiple audio players and prevent overlapping audio in learning mode
-# @param Uses global: $TEMP_FILE, $CURRENT_LANGUAGE
-# @sideeffects Plays audio with lock mechanism for sequential playback
-LOCK_FILE="/tmp/agentvibes-audio.lock"
-
-# Wait for previous audio to finish (max 30 seconds)
-for i in {1..60}; do
-  if [ ! -f "$LOCK_FILE" ]; then
-    break
-  fi
-  sleep 0.5
-done
-
-# Track last target language audio for replay command
-if [[ "$CURRENT_LANGUAGE" != "english" ]]; then
-  TARGET_AUDIO_FILE="${CLAUDE_PROJECT_DIR:-.}/.claude/last-target-audio.txt"
-  echo "$TEMP_FILE" > "$TARGET_AUDIO_FILE"
-fi
-
-# Create lock and play audio
-touch "$LOCK_FILE"
-
-# Get audio duration for proper lock timing
-DURATION=$(ffprobe -v error -show_entries format=duration -of default=noprint_wrappers=1:nokey=1 "$TEMP_FILE" 2>/dev/null)
-DURATION=${DURATION%.*}  # Round to integer
-DURATION=${DURATION:-1}   # Default to 1 second if detection fails
-
-# Play audio in background (skip if in test mode)
-if [[ "${AGENTVIBES_TEST_MODE:-false}" != "true" ]]; then
-  (mpv "$TEMP_FILE" || aplay "$TEMP_FILE" || paplay "$TEMP_FILE") >/dev/null 2>&1 &
-  PLAYER_PID=$!
-fi
-
-# Wait for audio to finish, then release lock
-(sleep $DURATION; rm -f "$LOCK_FILE") &
-disown
-
-echo "🎵 Saved to: $TEMP_FILE"
-echo "🎤 Voice used: $VOICE_MODEL (Piper TTS)"

.claude/hooks/play-tts.sh

@@ -1,100 +0,0 @@
-#!/bin/bash
-#
-# File: .claude/hooks/play-tts.sh
-#
-# AgentVibes - Finally, your AI Agents can Talk Back! Text-to-Speech WITH personality for AI Assistants!
-# Website: https://agentvibes.org
-# Repository: https://github.com/paulpreibisch/AgentVibes
-#
-# Co-created by Paul Preibisch with Claude AI
-# Copyright (c) 2025 Paul Preibisch
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-# DISCLAIMER: This software is provided "AS IS", WITHOUT WARRANTY OF ANY KIND,
-# express or implied, including but not limited to the warranties of
-# merchantability, fitness for a particular purpose and noninfringement.
-# In no event shall the authors or copyright holders be liable for any claim,
-# damages or other liability, whether in an action of contract, tort or
-# otherwise, arising from, out of or in connection with the software or the
-# use or other dealings in the software.
-#
-# ---
-#
-# @fileoverview TTS Provider Router with Language Learning Support
-# @context Routes TTS requests to active provider (ElevenLabs or Piper)
-# @architecture Provider abstraction layer - single entry point for all TTS
-# @dependencies provider-manager.sh, play-tts-elevenlabs.sh, play-tts-piper.sh, github-star-reminder.sh
-# @entrypoints Called by hooks, slash commands, personality-manager.sh, and all TTS features
-# @patterns Provider pattern - delegates to provider-specific implementations, auto-detects provider from voice name
-# @related provider-manager.sh, play-tts-elevenlabs.sh, play-tts-piper.sh, learn-manager.sh
-#
-
-# Fix locale warnings
-export LC_ALL=C
-
-TEXT="$1"
-VOICE_OVERRIDE="$2"  # Optional: voice name or ID
-
-# Get script directory
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-
-# Source provider manager to get active provider
-source "$SCRIPT_DIR/provider-manager.sh"
-
-# Get active provider
-ACTIVE_PROVIDER=$(get_active_provider)
-
-# Show GitHub star reminder (once per day)
-"$SCRIPT_DIR/github-star-reminder.sh" 2>/dev/null || true
-
-# @function detect_voice_provider
-# @intent Auto-detect provider from voice name (for mixed-provider support)
-# @why Allow ElevenLabs for main language + Piper for target language
-# @param $1 voice name/ID
-# @returns Provider name (elevenlabs or piper)
-detect_voice_provider() {
-  local voice="$1"
-  # Piper voice names contain underscore and dash (e.g., es_ES-davefx-medium)
-  if [[ "$voice" == *"_"*"-"* ]]; then
-    echo "piper"
-  else
-    echo "$ACTIVE_PROVIDER"
-  fi
-}
-
-# Override provider if voice indicates different provider (mixed-provider mode)
-if [[ -n "$VOICE_OVERRIDE" ]]; then
-  DETECTED_PROVIDER=$(detect_voice_provider "$VOICE_OVERRIDE")
-  if [[ "$DETECTED_PROVIDER" != "$ACTIVE_PROVIDER" ]]; then
-    ACTIVE_PROVIDER="$DETECTED_PROVIDER"
-  fi
-fi
-
-# Normal single-language mode - route to appropriate provider implementation
-# Note: For learning mode, the output style will call this script TWICE:
-# 1. First call with main language text and current voice
-# 2. Second call with translated text and target voice
-case "$ACTIVE_PROVIDER" in
-  elevenlabs)
-    exec "$SCRIPT_DIR/play-tts-elevenlabs.sh" "$TEXT" "$VOICE_OVERRIDE"
-    ;;
-  piper)
-    exec "$SCRIPT_DIR/play-tts-piper.sh" "$TEXT" "$VOICE_OVERRIDE"
-    ;;
-  *)
-    echo "❌ Unknown provider: $ACTIVE_PROVIDER"
-    echo "   Run: /agent-vibes:provider list"
-    exit 1
-    ;;
-esac

.claude/hooks/provider-commands.sh

@@ -1,540 +0,0 @@
-#!/bin/bash
-#
-# File: .claude/hooks/provider-commands.sh
-#
-# AgentVibes - Finally, your AI Agents can Talk Back! Text-to-Speech WITH personality for AI Assistants!
-# Website: https://agentvibes.org
-# Repository: https://github.com/paulpreibisch/AgentVibes
-#
-# Co-created by Paul Preibisch with Claude AI
-# Copyright (c) 2025 Paul Preibisch
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-# DISCLAIMER: This software is provided "AS IS", WITHOUT WARRANTY OF ANY KIND,
-# express or implied, including but not limited to the warranties of
-# merchantability, fitness for a particular purpose and noninfringement.
-# In no event shall the authors or copyright holders be liable for any claim,
-# damages or other liability, whether in an action of contract, tort or
-# otherwise, arising from, out of or in connection with the software or the
-# use or other dealings in the software.
-#
-# ---
-#
-# @fileoverview Provider management slash commands
-# @context User-facing commands for switching and managing TTS providers
-# @architecture Part of /agent-vibes:* command system with language compatibility checking
-# @dependencies provider-manager.sh, language-manager.sh, voice-manager.sh, piper-voice-manager.sh
-# @entrypoints Called by /agent-vibes:provider slash commands (list, switch, info, test, get, preview)
-# @patterns Interactive confirmations, platform detection, language compatibility validation
-# @related provider-manager.sh, play-tts.sh, voice-manager.sh, piper-voice-manager.sh
-#
-
-# Get script directory
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-source "$SCRIPT_DIR/provider-manager.sh"
-source "$SCRIPT_DIR/language-manager.sh"
-
-COMMAND="${1:-help}"
-
-# @function is_language_supported
-# @intent Check if a language is supported by a provider
-# @param $1 {string} language - Language code (e.g., "spanish", "french")
-# @param $2 {string} provider - Provider name (e.g., "elevenlabs", "piper")
-# @returns 0 if supported, 1 if not
-is_language_supported() {
-  local language="$1"
-  local provider="$2"
-
-  # English is always supported
-  if [[ "$language" == "english" ]] || [[ "$language" == "en" ]]; then
-    return 0
-  fi
-
-  case "$provider" in
-    elevenlabs)
-      # ElevenLabs supports all languages via multilingual voices
-      return 0
-      ;;
-    piper)
-      # Piper only supports English natively
-      return 1
-      ;;
-    *)
-      return 1
-      ;;
-  esac
-}
-
-# @function provider_list
-# @intent Display all available providers with status
-provider_list() {
-  local current_provider
-  current_provider=$(get_active_provider)
-
-  echo "┌────────────────────────────────────────────────────────────┐"
-  echo "│ Available TTS Providers                                    │"
-  echo "├────────────────────────────────────────────────────────────┤"
-
-  # ElevenLabs
-  if [[ "$current_provider" == "elevenlabs" ]]; then
-    echo "│ ✓ ElevenLabs    Premium quality    ⭐⭐⭐⭐⭐    [ACTIVE]    │"
-  else
-    echo "│   ElevenLabs    Premium quality    ⭐⭐⭐⭐⭐               │"
-  fi
-  echo "│   Cost: Free tier + \$5-22/mo                               │"
-  echo "│   Platform: All (Windows, macOS, Linux, WSL)               │"
-  echo "│   Offline: No                                              │"
-  echo "│                                                            │"
-
-  # Piper
-  if [[ "$current_provider" == "piper" ]]; then
-    echo "│ ✓ Piper TTS     Free, offline      ⭐⭐⭐⭐       [ACTIVE]    │"
-  else
-    echo "│   Piper TTS     Free, offline      ⭐⭐⭐⭐                  │"
-  fi
-  echo "│   Cost: Free forever                                       │"
-  echo "│   Platform: WSL, Linux only                                │"
-  echo "│   Offline: Yes                                             │"
-  echo "└────────────────────────────────────────────────────────────┘"
-  echo ""
-  echo "Learn more: agentvibes.org/providers"
-}
-
-# @function provider_switch
-# @intent Switch to a different TTS provider
-provider_switch() {
-  local new_provider="$1"
-  local force_mode=false
-
-  # Check for --force or --yes flag
-  if [[ "$2" == "--force" ]] || [[ "$2" == "--yes" ]] || [[ "$2" == "-y" ]]; then
-    force_mode=true
-  fi
-
-  # Auto-enable force mode if running non-interactively (e.g., from MCP)
-  # Check multiple conditions for MCP/non-interactive context
-  if [[ ! -t 0 ]] || [[ -n "$CLAUDE_PROJECT_DIR" ]] || [[ -n "$MCP_SERVER" ]]; then
-    force_mode=true
-  fi
-
-  if [[ -z "$new_provider" ]]; then
-    echo "❌ Error: Provider name required"
-    echo "Usage: /agent-vibes:provider switch <provider> [--force]"
-    echo "Available: elevenlabs, piper"
-    return 1
-  fi
-
-  # Validate provider
-  if ! validate_provider "$new_provider"; then
-    echo "❌ Invalid provider: $new_provider"
-    echo ""
-    echo "Available providers:"
-    list_providers
-    return 1
-  fi
-
-  local current_provider
-  current_provider=$(get_active_provider)
-
-  if [[ "$current_provider" == "$new_provider" ]]; then
-    echo "✓ Already using $new_provider"
-    return 0
-  fi
-
-  # Platform check for Piper
-  if [[ "$new_provider" == "piper" ]]; then
-    if ! grep -qi microsoft /proc/version 2>/dev/null && [[ "$(uname -s)" != "Linux" ]]; then
-      echo "❌ Piper is only supported on WSL and Linux"
-      echo "Your platform: $(uname -s)"
-      echo "See: agentvibes.org/platform-support"
-      return 1
-    fi
-
-    # Check if Piper is installed
-    if ! command -v piper &> /dev/null; then
-      echo "❌ Piper TTS is not installed"
-      echo ""
-      echo "Install with: pipx install piper-tts"
-      echo "Or run: .claude/hooks/piper-installer.sh"
-      echo ""
-      echo "Visit: agentvibes.org/install-piper"
-      return 1
-    fi
-  fi
-
-  # Check language compatibility
-  local current_language
-  current_language=$(get_language_code)
-
-  if [[ "$current_language" != "english" ]]; then
-    if ! is_language_supported "$current_language" "$new_provider" 2>/dev/null; then
-      echo "⚠️  Language Compatibility Warning"
-      echo ""
-      echo "Current language: $current_language"
-      echo "Target provider:  $new_provider"
-      echo ""
-      echo "❌ Language '$current_language' is not natively supported by $new_provider"
-      echo "   Will fall back to English when using $new_provider"
-      echo ""
-      echo "Options:"
-      echo "  1. Continue anyway (will use English)"
-      echo "  2. Switch language to English"
-      echo "  3. Cancel provider switch"
-      echo ""
-
-      # Skip prompt in force mode
-      if [[ "$force_mode" == true ]]; then
-        echo "⏩ Force mode: Continuing with fallback to English..."
-      else
-        read -p "Choose option [1-3]: " -n 1 -r
-        echo
-
-        case $REPLY in
-          1)
-            echo "⏩ Continuing with fallback to English..."
-            ;;
-          2)
-            echo "🔄 Switching language to English..."
-            "$SCRIPT_DIR/language-manager.sh" set english
-            ;;
-          3)
-            echo "❌ Provider switch cancelled"
-            return 1
-            ;;
-          *)
-            echo "❌ Invalid option, cancelling"
-            return 1
-            ;;
-        esac
-      fi
-    fi
-  fi
-
-  # Confirm switch (skip in force mode)
-  if [[ "$force_mode" != true ]]; then
-    echo ""
-    echo "⚠️  Switch to $(echo $new_provider | tr '[:lower:]' '[:upper:]')?"
-    echo ""
-    echo "Current: $current_provider"
-    echo "New:     $new_provider"
-    if [[ "$current_language" != "english" ]]; then
-      echo "Language: $current_language"
-    fi
-    echo ""
-    read -p "Continue? [y/N]: " -n 1 -r
-    echo
-
-    if [[ ! $REPLY =~ ^[Yy]$ ]]; then
-      echo "❌ Switch cancelled"
-      return 1
-    fi
-  else
-    echo "⏩ Force mode: Switching to $new_provider..."
-  fi
-
-  # Perform switch
-  set_active_provider "$new_provider"
-
-  # Update target voice if language learning mode is active
-  local target_lang_file=""
-  local target_voice_file=""
-
-  # Check project-local first, then global
-  if [[ -d "$SCRIPT_DIR/../.." ]]; then
-    local project_dir="$SCRIPT_DIR/../.."
-    if [[ -f "$project_dir/.claude/tts-target-language.txt" ]]; then
-      target_lang_file="$project_dir/.claude/tts-target-language.txt"
-      target_voice_file="$project_dir/.claude/tts-target-voice.txt"
-    fi
-  fi
-
-  # Fallback to global
-  if [[ -z "$target_lang_file" ]]; then
-    if [[ -f "$HOME/.claude/tts-target-language.txt" ]]; then
-      target_lang_file="$HOME/.claude/tts-target-language.txt"
-      target_voice_file="$HOME/.claude/tts-target-voice.txt"
-    fi
-  fi
-
-  # If target language is set, update voice for new provider
-  if [[ -n "$target_lang_file" ]] && [[ -f "$target_lang_file" ]]; then
-    local target_lang
-    target_lang=$(cat "$target_lang_file")
-
-    if [[ -n "$target_lang" ]]; then
-      # Get the recommended voice for this language with new provider
-      local new_target_voice
-      new_target_voice=$(get_voice_for_language "$target_lang" "$new_provider")
-
-      if [[ -n "$new_target_voice" ]]; then
-        echo "$new_target_voice" > "$target_voice_file"
-        echo ""
-        echo "🔄 Updated target language voice:"
-        echo "   Language: $target_lang"
-        echo "   Voice: $new_target_voice (for $new_provider)"
-      fi
-    fi
-  fi
-
-  # Test new provider
-  echo ""
-  echo "🔊 Testing provider..."
-  "$SCRIPT_DIR/play-tts.sh" "Provider switched to $new_provider successfully" 2>/dev/null
-
-  echo ""
-  echo "✓ Provider switch complete!"
-  echo "Visit agentvibes.org for tips and tricks"
-}
-
-# @function provider_info
-# @intent Show detailed information about a provider
-provider_info() {
-  local provider_name="$1"
-
-  if [[ -z "$provider_name" ]]; then
-    echo "❌ Error: Provider name required"
-    echo "Usage: /agent-vibes:provider info <provider>"
-    return 1
-  fi
-
-  case "$provider_name" in
-    elevenlabs)
-      echo "┌────────────────────────────────────────────────────────────┐"
-      echo "│ ElevenLabs - Premium TTS Provider                          │"
-      echo "├────────────────────────────────────────────────────────────┤"
-      echo "│ Quality:     ⭐⭐⭐⭐⭐  (Highest available)                   │"
-      echo "│ Cost:        Free tier + \$5-22/mo                          │"
-      echo "│ Platform:    All (Windows, macOS, Linux, WSL)              │"
-      echo "│ Offline:     No (requires internet)                        │"
-      echo "│                                                            │"
-      echo "│ Trade-offs:                                                │"
-      echo "│ + Highest voice quality and naturalness                   │"
-      echo "│ + 50+ premium voices available                            │"
-      echo "│ + Multilingual support (30+ languages)                    │"
-      echo "│ - Requires API key and internet                           │"
-      echo "│ - Costs money after free tier                             │"
-      echo "│                                                            │"
-      echo "│ Best for: Premium quality, multilingual needs             │"
-      echo "└────────────────────────────────────────────────────────────┘"
-      echo ""
-      echo "Full comparison: agentvibes.org/providers"
-      ;;
-
-    piper)
-      echo "┌────────────────────────────────────────────────────────────┐"
-      echo "│ Piper TTS - Free Offline Provider                          │"
-      echo "├────────────────────────────────────────────────────────────┤"
-      echo "│ Quality:     ⭐⭐⭐⭐  (Very good)                            │"
-      echo "│ Cost:        Free forever                                  │"
-      echo "│ Platform:    WSL, Linux only                               │"
-      echo "│ Offline:     Yes (fully local)                             │"
-      echo "│                                                            │"
-      echo "│ Trade-offs:                                                │"
-      echo "│ + Completely free, no API costs                           │"
-      echo "│ + Works offline, no internet needed                       │"
-      echo "│ + Fast synthesis (local processing)                       │"
-      echo "│ - WSL/Linux only (no macOS/Windows)                       │"
-      echo "│ - Slightly lower quality than ElevenLabs                  │"
-      echo "│                                                            │"
-      echo "│ Best for: Budget-conscious, offline use, privacy          │"
-      echo "└────────────────────────────────────────────────────────────┘"
-      echo ""
-      echo "Full comparison: agentvibes.org/providers"
-      ;;
-
-    *)
-      echo "❌ Unknown provider: $provider_name"
-      echo "Available: elevenlabs, piper"
-      ;;
-  esac
-}
-
-# @function provider_test
-# @intent Test current provider with sample audio
-provider_test() {
-  local current_provider
-  current_provider=$(get_active_provider)
-
-  echo "🔊 Testing provider: $current_provider"
-  echo ""
-
-  "$SCRIPT_DIR/play-tts.sh" "Provider test successful. Audio is working correctly with $current_provider."
-
-  echo ""
-  echo "✓ Test complete"
-}
-
-# @function provider_get
-# @intent Show currently active provider
-provider_get() {
-  local current_provider
-  current_provider=$(get_active_provider)
-
-  echo "🎤 Current Provider: $current_provider"
-  echo ""
-
-  # Show brief info
-  case "$current_provider" in
-    elevenlabs)
-      echo "Quality: ⭐⭐⭐⭐⭐"
-      echo "Cost: Free tier + \$5-22/mo"
-      echo "Offline: No"
-      ;;
-    piper)
-      echo "Quality: ⭐⭐⭐⭐"
-      echo "Cost: Free forever"
-      echo "Offline: Yes"
-      ;;
-  esac
-
-  echo ""
-  echo "Use /agent-vibes:provider info $current_provider for details"
-}
-
-# @function provider_preview
-# @intent Preview voices for the currently active provider
-# @architecture Delegates to provider-specific voice managers
-provider_preview() {
-  local current_provider
-  current_provider=$(get_active_provider)
-
-  echo "🎤 Voice Preview ($current_provider)"
-  echo ""
-
-  case "$current_provider" in
-    elevenlabs)
-      # Use the ElevenLabs voice manager
-      "$SCRIPT_DIR/voice-manager.sh" preview "$@"
-      ;;
-    piper)
-      # Use the Piper voice manager's list functionality
-      source "$SCRIPT_DIR/piper-voice-manager.sh"
-
-      # Check if a specific voice was requested
-      local voice_arg="$1"
-
-      if [[ -n "$voice_arg" ]]; then
-        # User requested a specific voice - check if it's a valid Piper voice
-        # Piper voice names are like: en_US-lessac-medium
-        # Try to find a matching voice model
-
-        # Check if the voice arg looks like a Piper model name (contains underscores/hyphens)
-        if [[ "$voice_arg" =~ ^[a-z]{2}_[A-Z]{2}- ]]; then
-          # Looks like a Piper voice model name
-          if verify_voice "$voice_arg"; then
-            echo "🎤 Previewing Piper voice: $voice_arg"
-            echo ""
-            "$SCRIPT_DIR/play-tts.sh" "Hello, this is the $voice_arg voice. How do you like it?" "$voice_arg"
-          else
-            echo "❌ Voice model not found: $voice_arg"
-            echo ""
-            echo "💡 Piper voice names look like: en_US-lessac-medium"
-            echo "   Run /agent-vibes:list to see available Piper voices"
-          fi
-        else
-          # Looks like an ElevenLabs voice name (like "Antoni", "Jessica")
-          echo "❌ '$voice_arg' appears to be an ElevenLabs voice"
-          echo ""
-          echo "You're currently using Piper TTS (free provider)."
-          echo "Piper has different voices than ElevenLabs."
-          echo ""
-          echo "Options:"
-          echo "  1. Run /agent-vibes:list to see available Piper voices"
-          echo "  2. Switch to ElevenLabs: /agent-vibes:provider switch elevenlabs"
-          echo ""
-          echo "Popular Piper voices to try:"
-          echo "  • en_US-lessac-medium  (clear, professional)"
-          echo "  • en_US-amy-medium     (warm, friendly)"
-          echo "  • en_US-joe-medium     (casual, natural)"
-        fi
-        return
-      fi
-
-      # No specific voice - preview first 3 voices
-      echo "🎤 Piper Preview of 3 people"
-      echo ""
-
-      # Play first 3 Piper voices as samples
-      local sample_voices=(
-        "en_US-lessac-medium:Lessac"
-        "en_US-amy-medium:Amy"
-        "en_US-joe-medium:Joe"
-      )
-
-      for voice_entry in "${sample_voices[@]}"; do
-        local voice_name="${voice_entry%%:*}"
-        local display_name="${voice_entry##*:}"
-
-        echo "🔊 ${display_name}..."
-        "$SCRIPT_DIR/play-tts.sh" "Hi, my name is ${display_name}" "$voice_name"
-
-        # Wait for the voice to finish playing before starting next one
-        sleep 3
-      done
-
-      echo ""
-      echo "✓ Preview complete"
-      echo "💡 Use /agent-vibes:list to see all available Piper voices"
-      ;;
-    *)
-      echo "❌ Unknown provider: $current_provider"
-      ;;
-  esac
-}
-
-# @function provider_help
-# @intent Show help for provider commands
-provider_help() {
-  echo "Provider Management Commands"
-  echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-  echo ""
-  echo "Usage:"
-  echo "  /agent-vibes:provider list              # Show all providers"
-  echo "  /agent-vibes:provider switch <name>     # Switch provider"
-  echo "  /agent-vibes:provider info <name>       # Provider details"
-  echo "  /agent-vibes:provider test              # Test current provider"
-  echo "  /agent-vibes:provider get               # Show active provider"
-  echo ""
-  echo "Examples:"
-  echo "  /agent-vibes:provider switch piper"
-  echo "  /agent-vibes:provider info elevenlabs"
-  echo ""
-  echo "Learn more: agentvibes.org/docs/providers"
-}
-
-# Route to appropriate function
-case "$COMMAND" in
-  list)
-    provider_list
-    ;;
-  switch)
-    provider_switch "$2" "$3"
-    ;;
-  info)
-    provider_info "$2"
-    ;;
-  test)
-    provider_test
-    ;;
-  get)
-    provider_get
-    ;;
-  preview)
-    shift  # Remove 'preview' from args
-    provider_preview "$@"
-    ;;
-  help|*)
-    provider_help
-    ;;
-esac

.claude/hooks/provider-manager.sh

@@ -1,298 +0,0 @@
-#!/bin/bash
-#
-# File: .claude/hooks/provider-manager.sh
-#
-# AgentVibes - Finally, your AI Agents can Talk Back! Text-to-Speech WITH personality for AI Assistants!
-# Website: https://agentvibes.org
-# Repository: https://github.com/paulpreibisch/AgentVibes
-#
-# Co-created by Paul Preibisch with Claude AI
-# Copyright (c) 2025 Paul Preibisch
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-# DISCLAIMER: This software is provided "AS IS", WITHOUT WARRANTY OF ANY KIND,
-# express or implied, including but not limited to the warranties of
-# merchantability, fitness for a particular purpose and noninfringement.
-# In no event shall the authors or copyright holders be liable for any claim,
-# damages or other liability, whether in an action of contract, tort or
-# otherwise, arising from, out of or in connection with the software or the
-# use or other dealings in the software.
-#
-# ---
-#
-# @fileoverview TTS Provider Management Functions
-# @context Core provider abstraction layer for multi-provider TTS system
-# @architecture Provides functions to get/set/list/validate TTS providers
-# @dependencies None - pure bash implementation
-# @entrypoints Sourced by play-tts.sh and provider management commands
-# @patterns File-based state management with project-local and global fallback
-# @related play-tts.sh, play-tts-elevenlabs.sh, play-tts-piper.sh, provider-commands.sh
-#
-
-# @function get_provider_config_path
-# @intent Determine path to tts-provider.txt file
-# @why Supports both project-local (.claude/) and global (~/.claude/) storage
-# @returns Echoes path to provider config file
-# @exitcode 0=always succeeds
-# @sideeffects None
-# @edgecases Creates parent directory if missing
-get_provider_config_path() {
-  local provider_file
-
-  # Check project-local first
-  if [[ -n "$CLAUDE_PROJECT_DIR" ]] && [[ -d "$CLAUDE_PROJECT_DIR/.claude" ]]; then
-    provider_file="$CLAUDE_PROJECT_DIR/.claude/tts-provider.txt"
-  else
-    # Search up directory tree for .claude/
-    local current_dir="$PWD"
-    while [[ "$current_dir" != "/" ]]; do
-      if [[ -d "$current_dir/.claude" ]]; then
-        provider_file="$current_dir/.claude/tts-provider.txt"
-        break
-      fi
-      current_dir=$(dirname "$current_dir")
-    done
-
-    # Fallback to global if no project .claude found
-    if [[ -z "$provider_file" ]]; then
-      provider_file="$HOME/.claude/tts-provider.txt"
-    fi
-  fi
-
-  echo "$provider_file"
-}
-
-# @function get_active_provider
-# @intent Read currently active TTS provider from config file
-# @why Central function for determining which provider to use
-# @returns Echoes provider name (e.g., "elevenlabs", "piper")
-# @exitcode 0=success
-# @sideeffects None
-# @edgecases Returns "elevenlabs" if file missing or empty (default)
-get_active_provider() {
-  local provider_file
-  provider_file=$(get_provider_config_path)
-
-  # Read provider from file, default to piper if not found
-  if [[ -f "$provider_file" ]]; then
-    local provider
-    provider=$(cat "$provider_file" | tr -d '[:space:]')
-    if [[ -n "$provider" ]]; then
-      echo "$provider"
-      return 0
-    fi
-  fi
-
-  # Default to piper (free, offline)
-  echo "piper"
-}
-
-# @function set_active_provider
-# @intent Write active provider to config file
-# @why Allows runtime provider switching without restart
-# @param $1 {string} provider - Provider name (e.g., "elevenlabs", "piper")
-# @returns None (outputs success/error message)
-# @exitcode 0=success, 1=invalid provider
-# @sideeffects Writes to tts-provider.txt file
-# @edgecases Creates file and parent directory if missing
-set_active_provider() {
-  local provider="$1"
-
-  if [[ -z "$provider" ]]; then
-    echo "❌ Error: Provider name required"
-    echo "Usage: set_active_provider <provider_name>"
-    return 1
-  fi
-
-  # Validate provider exists
-  if ! validate_provider "$provider"; then
-    echo "❌ Error: Provider '$provider' not found"
-    echo "Available providers:"
-    list_providers
-    return 1
-  fi
-
-  local provider_file
-  provider_file=$(get_provider_config_path)
-
-  # Create directory if it doesn't exist
-  mkdir -p "$(dirname "$provider_file")"
-
-  # Write provider to file
-  echo "$provider" > "$provider_file"
-
-  # Reset voice when switching providers to avoid incompatible voices
-  # (e.g., ElevenLabs "Demon Monster" doesn't exist in Piper)
-  local voice_file
-  if [[ -n "$CLAUDE_PROJECT_DIR" ]] && [[ -d "$CLAUDE_PROJECT_DIR/.claude" ]]; then
-    voice_file="$CLAUDE_PROJECT_DIR/.claude/tts-voice.txt"
-  else
-    voice_file="$HOME/.claude/tts-voice.txt"
-  fi
-
-  # Set default voice for the new provider
-  local default_voice
-  case "$provider" in
-    piper)
-      # Default Piper voice
-      default_voice="en_US-lessac-medium"
-      ;;
-    elevenlabs)
-      # Default ElevenLabs voice (first in alphabetical order from voices-config.sh)
-      default_voice="Amy"
-      ;;
-    *)
-      # Unknown provider - remove voice file
-      if [[ -f "$voice_file" ]]; then
-        rm -f "$voice_file"
-      fi
-      echo "✓ Active provider set to: $provider (voice reset)"
-      return 0
-      ;;
-  esac
-
-  # Write default voice to file
-  echo "$default_voice" > "$voice_file"
-
-  echo "✓ Active provider set to: $provider (voice set to: $default_voice)"
-}
-
-# @function list_providers
-# @intent List all available TTS providers
-# @why Discover which providers are installed
-# @returns Echoes provider names (one per line)
-# @exitcode 0=success
-# @sideeffects None
-# @edgecases Returns empty if no play-tts-*.sh files found
-list_providers() {
-  local script_dir
-  script_dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-
-  # Find all play-tts-*.sh files
-  local providers=()
-  shopt -s nullglob  # Handle case where no files match
-  for file in "$script_dir"/play-tts-*.sh; do
-    if [[ -f "$file" ]] && [[ "$file" != *"play-tts.sh" ]]; then
-      # Extract provider name from filename (play-tts-elevenlabs.sh -> elevenlabs)
-      local basename
-      basename=$(basename "$file")
-      local provider
-      provider="${basename#play-tts-}"
-      provider="${provider%.sh}"
-      providers+=("$provider")
-    fi
-  done
-  shopt -u nullglob
-
-  # Output providers
-  if [[ ${#providers[@]} -eq 0 ]]; then
-    echo "⚠️ No providers found"
-    return 0
-  fi
-
-  for provider in "${providers[@]}"; do
-    echo "$provider"
-  done
-}
-
-# @function validate_provider
-# @intent Check if provider implementation exists
-# @why Prevent errors from switching to non-existent provider
-# @param $1 {string} provider - Provider name to validate
-# @returns None
-# @exitcode 0=provider exists, 1=provider not found
-# @sideeffects None
-# @edgecases Checks for corresponding play-tts-*.sh file
-validate_provider() {
-  local provider="$1"
-
-  if [[ -z "$provider" ]]; then
-    return 1
-  fi
-
-  local script_dir
-  script_dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-  local provider_script="$script_dir/play-tts-${provider}.sh"
-
-  [[ -f "$provider_script" ]]
-}
-
-# @function get_provider_script_path
-# @intent Get absolute path to provider implementation script
-# @why Used by router to execute provider-specific logic
-# @param $1 {string} provider - Provider name
-# @returns Echoes absolute path to play-tts-*.sh file
-# @exitcode 0=success, 1=provider not found
-# @sideeffects None
-get_provider_script_path() {
-  local provider="$1"
-
-  if [[ -z "$provider" ]]; then
-    echo "❌ Error: Provider name required" >&2
-    return 1
-  fi
-
-  local script_dir
-  script_dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-  local provider_script="$script_dir/play-tts-${provider}.sh"
-
-  if [[ ! -f "$provider_script" ]]; then
-    echo "❌ Error: Provider '$provider' not found at $provider_script" >&2
-    return 1
-  fi
-
-  echo "$provider_script"
-}
-
-# AI NOTE: This file provides the core abstraction layer for multi-provider TTS.
-# All provider state is managed through simple text files for simplicity and reliability.
-# Project-local configuration takes precedence over global to support per-project providers.
-
-# Command-line interface (when script is executed, not sourced)
-if [[ "${BASH_SOURCE[0]}" == "${0}" ]]; then
-  case "${1:-}" in
-    get)
-      get_active_provider
-      ;;
-    switch|set)
-      if [[ -z "${2:-}" ]]; then
-        echo "❌ Error: Provider name required"
-        echo "Usage: $0 switch <provider>"
-        exit 1
-      fi
-      set_active_provider "$2"
-      ;;
-    list)
-      list_providers
-      ;;
-    validate)
-      if [[ -z "${2:-}" ]]; then
-        echo "❌ Error: Provider name required"
-        echo "Usage: $0 validate <provider>"
-        exit 1
-      fi
-      validate_provider "$2"
-      ;;
-    *)
-      echo "Usage: $0 {get|switch|list|validate} [provider]"
-      echo ""
-      echo "Commands:"
-      echo "  get              - Show active provider"
-      echo "  switch <name>    - Switch to provider"
-      echo "  list             - List available providers"
-      echo "  validate <name>  - Check if provider exists"
-      exit 1
-      ;;
-  esac
-fi

.claude/hooks/replay-target-audio.sh

@@ -1,95 +0,0 @@
-#!/bin/bash
-#
-# File: .claude/hooks/replay-target-audio.sh
-#
-# AgentVibes - Finally, your AI Agents can Talk Back! Text-to-Speech WITH personality for AI Assistants!
-# Website: https://agentvibes.org
-# Repository: https://github.com/paulpreibisch/AgentVibes
-#
-# Co-created by Paul Preibisch with Claude AI
-# Copyright (c) 2025 Paul Preibisch
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-# DISCLAIMER: This software is provided "AS IS", WITHOUT WARRANTY OF ANY KIND,
-# express or implied, including but not limited to the warranties of
-# merchantability, fitness for a particular purpose and noninfringement.
-# In no event shall the authors or copyright holders be liable for any claim,
-# damages or other liability, whether in an action of contract, tort or
-# otherwise, arising from, out of or in connection with the software or the
-# use or other dealings in the software.
-#
-# ---
-#
-# @fileoverview Replay Last Target Language Audio
-# @context Replays the most recent target language TTS for language learning
-# @architecture Simple audio replay with lock mechanism for sequential playback
-# @dependencies ffprobe, paplay/aplay/mpg123/mpv, .claude/last-target-audio.txt
-# @entrypoints Called by /agent-vibes:replay-target slash command
-# @patterns Sequential audio playback with lock file, duration-based lock release
-# @related play-tts-piper.sh, play-tts-elevenlabs.sh, learn-manager.sh
-#
-
-# Fix locale warnings
-export LC_ALL=C
-
-TARGET_AUDIO_FILE="${CLAUDE_PROJECT_DIR:-.}/.claude/last-target-audio.txt"
-
-# Check if target audio tracking file exists
-if [ ! -f "$TARGET_AUDIO_FILE" ]; then
-  echo "❌ No target language audio found."
-  echo "   Language learning mode may not be active."
-  echo "   Activate with: /agent-vibes:learn"
-  exit 1
-fi
-
-# Read last target audio file path
-LAST_AUDIO=$(cat "$TARGET_AUDIO_FILE")
-
-# Verify audio file exists
-if [ ! -f "$LAST_AUDIO" ]; then
-  echo "❌ Audio file not found: $LAST_AUDIO"
-  echo "   The file may have been deleted or moved."
-  exit 1
-fi
-
-echo "🔁 Replaying target language audio..."
-
-# Use lock file for sequential playback
-LOCK_FILE="/tmp/agentvibes-audio.lock"
-
-# Wait for any current audio to finish (max 30 seconds)
-for i in {1..60}; do
-  if [ ! -f "$LOCK_FILE" ]; then
-    break
-  fi
-  sleep 0.5
-done
-
-# Create lock
-touch "$LOCK_FILE"
-
-# Get audio duration for proper lock timing
-DURATION=$(ffprobe -v error -show_entries format=duration -of default=noprint_wrappers=1:nokey=1 "$LAST_AUDIO" 2>/dev/null)
-DURATION=${DURATION%.*}  # Round to integer
-DURATION=${DURATION:-1}   # Default to 1 second if detection fails
-
-# Play audio
-(paplay "$LAST_AUDIO" || aplay "$LAST_AUDIO" || mpg123 "$LAST_AUDIO" || mpv "$LAST_AUDIO") >/dev/null 2>&1 &
-PLAYER_PID=$!
-
-# Wait for audio to finish, then release lock
-(sleep $DURATION; rm -f "$LOCK_FILE") &
-disown
-
-echo "✅ Replay complete: $(basename "$LAST_AUDIO")"

.claude/hooks/sentiment-manager.sh

@@ -1,201 +0,0 @@
-#!/bin/bash
-#
-# File: .claude/hooks/sentiment-manager.sh
-#
-# AgentVibes - Finally, your AI Agents can Talk Back! Text-to-Speech WITH personality for AI Assistants!
-# Website: https://agentvibes.org
-# Repository: https://github.com/paulpreibisch/AgentVibes
-#
-# Co-created by Paul Preibisch with Claude AI
-# Copyright (c) 2025 Paul Preibisch
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-# DISCLAIMER: This software is provided "AS IS", WITHOUT WARRANTY OF ANY KIND,
-# express or implied, including but not limited to the warranties of
-# merchantability, fitness for a particular purpose and noninfringement.
-# In no event shall the authors or copyright holders be liable for any claim,
-# damages or other liability, whether in an action of contract, tort or
-# otherwise, arising from, out of or in connection with the software or the
-# use or other dealings in the software.
-#
-# ---
-#
-# @fileoverview Sentiment Manager - Applies personality styles to current voice without changing the voice itself
-# @context Allows adding emotional/tonal layers (flirty, sarcastic, etc.) to any voice while preserving voice identity
-# @architecture Reuses personality markdown files, stores sentiment separately from personality
-# @dependencies .claude/personalities/*.md files, play-tts.sh for acknowledgment
-# @entrypoints Called by /agent-vibes:sentiment slash command
-# @patterns Personality/sentiment separation, state file management, random example selection
-# @related personality-manager.sh, .claude/personalities/*.md, .claude/tts-sentiment.txt
-
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-PERSONALITIES_DIR="$SCRIPT_DIR/../personalities"
-
-# Project-local file first, global fallback
-# Use logical path (not physical) to handle symlinked .claude directories
-# Script is at .claude/hooks/sentiment-manager.sh, so .claude is ..
-CLAUDE_DIR="$(cd "$SCRIPT_DIR/.." 2>/dev/null && pwd)"
-
-# Check if we have a project-local .claude directory
-if [[ -d "$CLAUDE_DIR" ]] && [[ "$CLAUDE_DIR" != "$HOME/.claude" ]]; then
-  SENTIMENT_FILE="$CLAUDE_DIR/tts-sentiment.txt"
-else
-  SENTIMENT_FILE="$HOME/.claude/tts-sentiment.txt"
-fi
-
-# Function to get personality data from markdown file
-get_personality_data() {
-  local personality="$1"
-  local field="$2"
-  local file="$PERSONALITIES_DIR/${personality}.md"
-
-  if [[ ! -f "$file" ]]; then
-    return 1
-  fi
-
-  case "$field" in
-    description)
-      grep "^description:" "$file" | cut -d: -f2- | sed 's/^[[:space:]]*//;s/[[:space:]]*$//'
-      ;;
-  esac
-}
-
-# Function to list all available personalities
-list_personalities() {
-  if [[ -d "$PERSONALITIES_DIR" ]]; then
-    for file in "$PERSONALITIES_DIR"/*.md; do
-      if [[ -f "$file" ]]; then
-        basename "$file" .md
-      fi
-    done
-  fi
-}
-
-case "$1" in
-  list)
-    echo "🎭 Available Sentiments:"
-    echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-
-    # Get current sentiment
-    CURRENT="none"
-    if [ -f "$SENTIMENT_FILE" ]; then
-      CURRENT=$(cat "$SENTIMENT_FILE")
-    fi
-
-    # List personalities from markdown files
-    echo "Available sentiment styles:"
-    for personality in $(list_personalities | sort); do
-      desc=$(get_personality_data "$personality" "description")
-      if [[ "$personality" == "$CURRENT" ]]; then
-        echo "  ✓ $personality - $desc (current)"
-      else
-        echo "  - $personality - $desc"
-      fi
-    done
-
-    echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-    echo ""
-    echo "Usage: /agent-vibes:sentiment <name>"
-    echo "       /agent-vibes:sentiment clear"
-    ;;
-
-  set)
-    SENTIMENT="$2"
-
-    if [[ -z "$SENTIMENT" ]]; then
-      echo "❌ Please specify a sentiment name"
-      echo "Usage: $0 set <sentiment>"
-      exit 1
-    fi
-
-    # Check if sentiment file exists
-    if [[ ! -f "$PERSONALITIES_DIR/${SENTIMENT}.md" ]]; then
-      echo "❌ Sentiment not found: $SENTIMENT"
-      echo ""
-      echo "Available sentiments:"
-      for p in $(list_personalities | sort); do
-        echo "  • $p"
-      done
-      exit 1
-    fi
-
-    # Save the sentiment (but don't change personality or voice)
-    echo "$SENTIMENT" > "$SENTIMENT_FILE"
-    echo "🎭 Sentiment set to: $SENTIMENT"
-    echo "🎤 Voice remains unchanged"
-    echo ""
-
-    # Make a sentiment-appropriate remark with TTS
-    TTS_SCRIPT="$SCRIPT_DIR/play-tts.sh"
-
-    # Try to get acknowledgment from personality file (sentiments use same personality files)
-    PERSONALITY_FILE_PATH="$PERSONALITIES_DIR/${SENTIMENT}.md"
-    REMARK=""
-
-    if [[ -f "$PERSONALITY_FILE_PATH" ]]; then
-      # Extract example responses from personality file (lines starting with "- ")
-      mapfile -t EXAMPLES < <(grep '^- "' "$PERSONALITY_FILE_PATH" | sed 's/^- "//; s/"$//')
-
-      if [[ ${#EXAMPLES[@]} -gt 0 ]]; then
-        # Pick a random example
-        REMARK="${EXAMPLES[$RANDOM % ${#EXAMPLES[@]}]}"
-      fi
-    fi
-
-    # Fallback if no examples found
-    if [[ -z "$REMARK" ]]; then
-      REMARK="Sentiment set to ${SENTIMENT} while maintaining current voice"
-    fi
-
-    echo "💬 $REMARK"
-    "$TTS_SCRIPT" "$REMARK"
-    ;;
-
-  get)
-    if [ -f "$SENTIMENT_FILE" ]; then
-      CURRENT=$(cat "$SENTIMENT_FILE")
-      echo "Current sentiment: $CURRENT"
-
-      desc=$(get_personality_data "$CURRENT" "description")
-      [[ -n "$desc" ]] && echo "Description: $desc"
-    else
-      echo "Current sentiment: none (voice personality only)"
-    fi
-    ;;
-
-  clear)
-    rm -f "$SENTIMENT_FILE"
-    echo "🎭 Sentiment cleared - using voice personality only"
-    ;;
-
-  *)
-    # If a single argument is provided and it's not a command, treat it as "set <sentiment>"
-    if [[ -n "$1" ]] && [[ -f "$PERSONALITIES_DIR/${1}.md" ]]; then
-      exec "$0" set "$1"
-    else
-      echo "AgentVibes Sentiment Manager"
-      echo ""
-      echo "Commands:"
-      echo "  list                - List all sentiments"
-      echo "  set <name>          - Set sentiment for current voice"
-      echo "  get                 - Show current sentiment"
-      echo "  clear               - Clear sentiment"
-      echo ""
-      echo "Examples:"
-      echo "  /agent-vibes:sentiment flirty     # Add flirty style to current voice"
-      echo "  /agent-vibes:sentiment sarcastic  # Add sarcasm to current voice"
-      echo "  /agent-vibes:sentiment clear      # Remove sentiment"
-    fi
-    ;;
-esac

.claude/hooks/speed-manager.sh

@@ -1,291 +0,0 @@
-#!/bin/bash
-#
-# File: .claude/hooks/speed-manager.sh
-#
-# AgentVibes - Finally, your AI Agents can Talk Back! Text-to-Speech WITH personality for AI Assistants!
-# Website: https://agentvibes.org
-# Repository: https://github.com/paulpreibisch/AgentVibes
-#
-# Co-created by Paul Preibisch with Claude AI
-# Copyright (c) 2025 Paul Preibisch
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-# DISCLAIMER: This software is provided "AS IS", WITHOUT WARRANTY OF ANY KIND,
-# express or implied, including but not limited to the warranties of
-# merchantability, fitness for a particular purpose and noninfringement.
-# In no event shall the authors or copyright holders be liable for any claim,
-# damages or other liability, whether in an action of contract, tort or
-# otherwise, arising from, out of or in connection with the software or the
-# use or other dealings in the software.
-#
-# ---
-#
-# @fileoverview Speech Speed Manager for Multi-Provider TTS
-# @context Manage speech rate for main and target language voices
-# @architecture Simple config file manager supporting both Piper (length-scale) and ElevenLabs (speed API parameter)
-# @dependencies .claude/config/tts-speech-rate.txt, .claude/config/tts-target-speech-rate.txt
-# @entrypoints Called by /agent-vibes:set-speed slash command
-# @patterns Provider-agnostic speed config, legacy file migration, random tongue twisters for testing
-# @related play-tts.sh, play-tts-piper.sh, play-tts-elevenlabs.sh, learn-manager.sh
-#
-
-# Get script directory
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-
-# Determine config directory (project-local first, then global)
-if [[ -n "$CLAUDE_PROJECT_DIR" ]] && [[ -d "$CLAUDE_PROJECT_DIR/.claude" ]]; then
-  CONFIG_DIR="$CLAUDE_PROJECT_DIR/.claude/config"
-else
-  # Try to find .claude in current path
-  CURRENT_DIR="$PWD"
-  while [[ "$CURRENT_DIR" != "/" ]]; do
-    if [[ -d "$CURRENT_DIR/.claude" ]]; then
-      CONFIG_DIR="$CURRENT_DIR/.claude/config"
-      break
-    fi
-    CURRENT_DIR=$(dirname "$CURRENT_DIR")
-  done
-  # Fallback to global
-  if [[ -z "$CONFIG_DIR" ]]; then
-    CONFIG_DIR="$HOME/.claude/config"
-  fi
-fi
-
-mkdir -p "$CONFIG_DIR"
-
-MAIN_SPEED_FILE="$CONFIG_DIR/tts-speech-rate.txt"
-TARGET_SPEED_FILE="$CONFIG_DIR/tts-target-speech-rate.txt"
-
-# Legacy file paths for backward compatibility (Piper-specific naming)
-LEGACY_MAIN_SPEED_FILE="$CONFIG_DIR/piper-speech-rate.txt"
-LEGACY_TARGET_SPEED_FILE="$CONFIG_DIR/piper-target-speech-rate.txt"
-
-# @function parse_speed_value
-# @intent Convert user-friendly speed notation to normalized speed multiplier
-# @param $1 Speed string (e.g., "2x", "0.5x", "normal")
-# @returns Numeric speed value (0.5=slower, 1.0=normal, 2.0=faster, 3.0=very fast)
-# @note This is the user-facing scale - provider scripts will convert as needed
-parse_speed_value() {
-  local input="$1"
-
-  # Handle special cases
-  case "$input" in
-    normal|1x|1.0)
-      echo "1.0"
-      return
-      ;;
-    slow|slower|0.5x)
-      echo "0.5"
-      return
-      ;;
-    fast|2x|2.0)
-      echo "2.0"
-      return
-      ;;
-    faster|3x|3.0)
-      echo "3.0"
-      return
-      ;;
-  esac
-
-  # Strip leading '+' or '-' if present
-  input="${input#+}"
-  input="${input#-}"
-
-  # Strip trailing 'x' if present
-  input="${input%x}"
-
-  # Validate it's a number
-  if [[ "$input" =~ ^[0-9]+\.?[0-9]*$ ]]; then
-    echo "$input"
-  else
-    echo "ERROR"
-  fi
-}
-
-# @function set_speed
-# @intent Set speech speed for main or target voice
-# @param $1 Target ("target" or empty for main)
-# @param $2 Speed value
-set_speed() {
-  local is_target=false
-  local speed_input=""
-
-  # Parse arguments
-  if [[ "$1" == "target" ]]; then
-    is_target=true
-    speed_input="$2"
-  else
-    speed_input="$1"
-  fi
-
-  if [[ -z "$speed_input" ]]; then
-    echo "❌ Error: Speed value required"
-    echo "Usage: /agent-vibes:set-speed [target] <speed>"
-    echo "Examples: 2x, 0.5x, normal, +3x"
-    return 1
-  fi
-
-  # Parse speed value
-  local speed_value
-  speed_value=$(parse_speed_value "$speed_input")
-
-  if [[ "$speed_value" == "ERROR" ]]; then
-    echo "❌ Invalid speed value: $speed_input"
-    echo "Valid values: normal, 0.5x, 1x, 2x, 3x, +2x, -2x"
-    return 1
-  fi
-
-  # Determine which file to write to
-  local config_file
-  local voice_type
-  if [[ "$is_target" == true ]]; then
-    config_file="$TARGET_SPEED_FILE"
-    voice_type="target language"
-  else
-    config_file="$MAIN_SPEED_FILE"
-    voice_type="main voice"
-  fi
-
-  # Write speed value
-  echo "$speed_value" > "$config_file"
-
-  # Show confirmation
-  echo "✓ Speech speed set for $voice_type"
-  echo ""
-  echo "Speed: ${speed_value}x"
-
-  case "$speed_value" in
-    0.5)
-      echo "Effect: Half speed (slower)"
-      ;;
-    1.0)
-      echo "Effect: Normal speed"
-      ;;
-    2.0)
-      echo "Effect: Double speed (faster)"
-      ;;
-    3.0)
-      echo "Effect: Triple speed (very fast)"
-      ;;
-    *)
-      if (( $(echo "$speed_value > 1.0" | bc -l) )); then
-        echo "Effect: Faster speech"
-      else
-        echo "Effect: Slower speech"
-      fi
-      ;;
-  esac
-
-  echo ""
-  echo "Note: Speed control works with both Piper and ElevenLabs providers"
-
-  # Array of simple test messages to demonstrate speed
-  local test_messages=(
-    "Testing speed change"
-    "Speed test in progress"
-    "Checking audio speed"
-    "Speed configuration test"
-    "Audio speed test"
-  )
-
-  # Pick a random test message
-  local random_index=$((RANDOM % ${#test_messages[@]}))
-  local test_msg="${test_messages[$random_index]}"
-
-  echo ""
-  echo "🔊 Testing new speed with: \"$test_msg\""
-  "$SCRIPT_DIR/play-tts.sh" "$test_msg" &
-}
-
-# @function migrate_legacy_files
-# @intent Migrate from old piper-specific files to provider-agnostic files
-# @why Ensure backward compatibility when upgrading from Piper-only to multi-provider
-migrate_legacy_files() {
-  # Migrate main speed file
-  if [[ -f "$LEGACY_MAIN_SPEED_FILE" ]] && [[ ! -f "$MAIN_SPEED_FILE" ]]; then
-    cp "$LEGACY_MAIN_SPEED_FILE" "$MAIN_SPEED_FILE"
-  fi
-
-  # Migrate target speed file
-  if [[ -f "$LEGACY_TARGET_SPEED_FILE" ]] && [[ ! -f "$TARGET_SPEED_FILE" ]]; then
-    cp "$LEGACY_TARGET_SPEED_FILE" "$TARGET_SPEED_FILE"
-  fi
-}
-
-# @function get_speed
-# @intent Display current speech speed settings
-get_speed() {
-  # Migrate legacy files if needed
-  migrate_legacy_files
-
-  echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-  echo "   Current Speech Speed Settings"
-  echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-  echo ""
-
-  # Main voice speed
-  if [[ -f "$MAIN_SPEED_FILE" ]]; then
-    local main_speed=$(grep -v '^#' "$MAIN_SPEED_FILE" 2>/dev/null | grep -v '^$' | tail -1)
-    echo "Main voice: ${main_speed}x"
-  else
-    echo "Main voice: 1.0x (default, normal speed)"
-  fi
-
-  # Target voice speed
-  if [[ -f "$TARGET_SPEED_FILE" ]]; then
-    local target_speed=$(cat "$TARGET_SPEED_FILE" 2>/dev/null)
-    echo "Target language: ${target_speed}x"
-  else
-    echo "Target language: 0.5x (default, slower for learning)"
-  fi
-
-  echo ""
-  echo "Scale: 0.5x=slower, 1.0x=normal, 2.0x=faster, 3.0x=very fast"
-  echo "Works with: Piper TTS and ElevenLabs"
-  echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-}
-
-# Main command handler
-case "${1:-}" in
-  target)
-    set_speed "target" "$2"
-    ;;
-  get|status)
-    get_speed
-    ;;
-  normal|fast|slow|slower|*x|*.*|+*|-*)
-    set_speed "$1"
-    ;;
-  *)
-    echo "Speech Speed Manager"
-    echo ""
-    echo "Usage:"
-    echo "  /agent-vibes:set-speed <speed>         Set main voice speed"
-    echo "  /agent-vibes:set-speed target <speed>  Set target language speed"
-    echo "  /agent-vibes:set-speed get              Show current speeds"
-    echo ""
-    echo "Speed values:"
-    echo "  0.5x or slow/slower = Half speed (slower)"
-    echo "  1x or normal        = Normal speed"
-    echo "  2x or fast          = Double speed (faster)"
-    echo "  3x or faster        = Triple speed (very fast)"
-    echo ""
-    echo "Examples:"
-    echo "  /agent-vibes:set-speed 2x        # Make voice faster"
-    echo "  /agent-vibes:set-speed 0.5x      # Make voice slower"
-    echo "  /agent-vibes:set-speed target 0.5x  # Slow down target language for learning"
-    echo "  /agent-vibes:set-speed normal    # Reset to normal"
-    ;;
-esac

.claude/hooks/voice-manager.sh

@@ -1,594 +0,0 @@
-#!/bin/bash
-#
-# File: .claude/hooks/voice-manager.sh
-#
-# AgentVibes - Finally, your AI Agents can Talk Back! Text-to-Speech WITH personality for AI Assistants!
-# Website: https://agentvibes.org
-# Repository: https://github.com/paulpreibisch/AgentVibes
-#
-# Co-created by Paul Preibisch with Claude AI
-# Copyright (c) 2025 Paul Preibisch
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-# DISCLAIMER: This software is provided "AS IS", WITHOUT WARRANTY OF ANY KIND,
-# express or implied. Use at your own risk. See the Apache License for details.
-#
-# ---
-#
-# @fileoverview Voice Manager - Unified voice management for both ElevenLabs and Piper providers
-# @context Central interface for listing, switching, previewing, and replaying TTS voices across providers
-# @architecture Provider-aware operations with dynamic voice listing based on active provider
-# @dependencies voices-config.sh (ElevenLabs mappings), piper-voice-manager.sh (Piper voices), provider-manager.sh
-# @entrypoints Called by /agent-vibes:switch, /agent-vibes:list, /agent-vibes:whoami, /agent-vibes:replay commands
-# @patterns Provider abstraction, numbered selection UI, silent mode for programmatic switching
-# @related voices-config.sh, piper-voice-manager.sh, .claude/tts-voice.txt, .claude/audio/ (replay)
-
-# Get script directory (physical path for sourcing files)
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd -P)"
-source "$SCRIPT_DIR/voices-config.sh"
-
-# Determine target .claude directory based on context
-# Priority:
-# 1. CLAUDE_PROJECT_DIR env var (set by MCP for project-specific settings)
-# 2. Script location (for direct slash command usage)
-# 3. Global ~/.claude (fallback)
-
-if [[ -n "$CLAUDE_PROJECT_DIR" ]] && [[ -d "$CLAUDE_PROJECT_DIR/.claude" ]]; then
-  # MCP context: Use the project directory where MCP was invoked
-  CLAUDE_DIR="$CLAUDE_PROJECT_DIR/.claude"
-else
-  # Direct usage context: Use script location
-  SCRIPT_PATH="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-  CLAUDE_DIR="$(dirname "$SCRIPT_PATH")"
-
-  # If script is in global ~/.claude, use that
-  if [[ "$CLAUDE_DIR" == "$HOME/.claude" ]]; then
-    CLAUDE_DIR="$HOME/.claude"
-  elif [[ ! -d "$CLAUDE_DIR" ]]; then
-    # Fallback to global if directory doesn't exist
-    CLAUDE_DIR="$HOME/.claude"
-  fi
-fi
-
-VOICE_FILE="$CLAUDE_DIR/tts-voice.txt"
-
-case "$1" in
-  list)
-    # Get active provider
-    PROVIDER_FILE="$CLAUDE_DIR/tts-provider.txt"
-    if [[ ! -f "$PROVIDER_FILE" ]]; then
-      PROVIDER_FILE="$HOME/.claude/tts-provider.txt"
-    fi
-
-    ACTIVE_PROVIDER="elevenlabs"  # default
-    if [ -f "$PROVIDER_FILE" ]; then
-      ACTIVE_PROVIDER=$(cat "$PROVIDER_FILE")
-    fi
-
-    CURRENT_VOICE=$(cat "$VOICE_FILE" 2>/dev/null || echo "Cowboy Bob")
-
-    if [[ "$ACTIVE_PROVIDER" == "piper" ]]; then
-      echo "🎤 Available Piper TTS Voices:"
-      echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-
-      # List downloaded Piper voices
-      if [[ -f "$SCRIPT_DIR/piper-voice-manager.sh" ]]; then
-        source "$SCRIPT_DIR/piper-voice-manager.sh"
-        VOICE_DIR=$(get_voice_storage_dir)
-        VOICE_COUNT=0
-        for onnx_file in "$VOICE_DIR"/*.onnx; do
-          if [[ -f "$onnx_file" ]]; then
-            voice=$(basename "$onnx_file" .onnx)
-            if [ "$voice" = "$CURRENT_VOICE" ]; then
-              echo "  ▶ $voice (current)"
-            else
-              echo "    $voice"
-            fi
-            ((VOICE_COUNT++))
-          fi
-        done | sort
-
-        if [[ $VOICE_COUNT -eq 0 ]]; then
-          echo "  (No Piper voices downloaded yet)"
-          echo ""
-          echo "Download voices with: /agent-vibes:provider download <voice-name>"
-          echo "Examples: en_US-lessac-medium, en_GB-alba-medium"
-        fi
-      fi
-    else
-      echo "🎤 Available ElevenLabs TTS Voices:"
-      echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-      for voice in "${!VOICES[@]}"; do
-        if [ "$voice" = "$CURRENT_VOICE" ]; then
-          echo "  ▶ $voice (current)"
-        else
-          echo "    $voice"
-        fi
-      done | sort
-    fi
-
-    echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-    echo ""
-    echo "Usage: voice-manager.sh switch <name>"
-    echo "       voice-manager.sh preview"
-    ;;
-
-  preview)
-    # Get play-tts.sh path
-    SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-    TTS_SCRIPT="$SCRIPT_DIR/play-tts.sh"
-
-    # Check if a specific voice name was provided
-    if [[ -n "$2" ]] && [[ "$2" != "first" ]] && [[ "$2" != "last" ]] && ! [[ "$2" =~ ^[0-9]+$ ]]; then
-      # User specified a voice name
-      VOICE_NAME="$2"
-
-      # Check if voice exists
-      if [[ -n "${VOICES[$VOICE_NAME]}" ]]; then
-        echo "🎤 Previewing voice: ${VOICE_NAME}"
-        echo ""
-        "$TTS_SCRIPT" "Hello, this is ${VOICE_NAME}. How do you like my voice?" "${VOICE_NAME}"
-      else
-        echo "❌ Voice not found: ${VOICE_NAME}"
-        echo ""
-        echo "Available voices:"
-        for voice in "${!VOICES[@]}"; do
-          echo "  • $voice"
-        done | sort
-      fi
-      exit 0
-    fi
-
-    # Original preview logic for first/last/number
-    echo "🎤 Voice Preview - Playing first 3 voices..."
-    echo ""
-
-    # Sort voices and preview first 3
-    VOICE_ARRAY=()
-    for voice in "${!VOICES[@]}"; do
-      VOICE_ARRAY+=("$voice")
-    done
-
-    # Sort the array
-    IFS=$'\n' SORTED_VOICES=($(sort <<<"${VOICE_ARRAY[*]}"))
-    unset IFS
-
-    # Play first 3 voices
-    COUNT=0
-    for voice in "${SORTED_VOICES[@]}"; do
-      if [ $COUNT -eq 3 ]; then
-        break
-      fi
-      echo "🔊 ${voice}..."
-      "$TTS_SCRIPT" "Hi, I'm ${voice}" "${VOICES[$voice]}"
-      sleep 0.5
-      COUNT=$((COUNT + 1))
-    done
-
-    echo ""
-    echo "Would you like to hear more? Reply 'yes' to continue."
-    ;;
-
-  switch)
-    VOICE_NAME="$2"
-    SILENT_MODE=false
-
-    # Check for --silent flag
-    if [[ "$2" == "--silent" ]] || [[ "$3" == "--silent" ]]; then
-      SILENT_MODE=true
-      # If --silent is first arg, voice name is in $3
-      [[ "$2" == "--silent" ]] && VOICE_NAME="$3"
-    fi
-
-    if [[ -z "$VOICE_NAME" ]]; then
-      # Show numbered list for selection
-      echo "🎤 Select a voice by number:"
-      echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-
-      # Get current voice
-      CURRENT="Cowboy Bob"
-      if [ -f "$VOICE_FILE" ]; then
-        CURRENT=$(cat "$VOICE_FILE")
-      fi
-
-      # Create array of voice names
-      VOICE_ARRAY=()
-      for voice in "${!VOICES[@]}"; do
-        VOICE_ARRAY+=("$voice")
-      done
-
-      # Sort the array
-      IFS=$'\n' SORTED_VOICES=($(sort <<<"${VOICE_ARRAY[*]}"))
-      unset IFS
-
-      # Display numbered list in two columns for compactness
-      HALF=$(( (${#SORTED_VOICES[@]} + 1) / 2 ))
-
-      for i in $(seq 0 $((HALF - 1))); do
-        NUM1=$((i + 1))
-        VOICE1="${SORTED_VOICES[$i]}"
-
-        # Format first column
-        if [[ "$VOICE1" == "$CURRENT" ]]; then
-          COL1=$(printf "%2d. %-20s ✓" "$NUM1" "$VOICE1")
-        else
-          COL1=$(printf "%2d. %-20s  " "$NUM1" "$VOICE1")
-        fi
-
-        # Format second column if it exists
-        NUM2=$((i + HALF + 1))
-        if [[ $((i + HALF)) -lt ${#SORTED_VOICES[@]} ]]; then
-          VOICE2="${SORTED_VOICES[$((i + HALF))]}"
-          if [[ "$VOICE2" == "$CURRENT" ]]; then
-            COL2=$(printf "%2d. %-20s ✓" "$NUM2" "$VOICE2")
-          else
-            COL2=$(printf "%2d. %-20s  " "$NUM2" "$VOICE2")
-          fi
-          echo "  $COL1 $COL2"
-        else
-          echo "  $COL1"
-        fi
-      done
-
-      echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-      echo ""
-      echo "Enter number (1-${#SORTED_VOICES[@]}) or voice name:"
-      echo "Usage: /agent-vibes:switch 5"
-      echo "       /agent-vibes:switch \"Northern Terry\""
-      exit 0
-    fi
-
-    # Detect active TTS provider
-    PROVIDER_FILE=""
-    if [[ -f "$CLAUDE_DIR/tts-provider.txt" ]]; then
-      PROVIDER_FILE="$CLAUDE_DIR/tts-provider.txt"
-    elif [[ -f "$HOME/.claude/tts-provider.txt" ]]; then
-      PROVIDER_FILE="$HOME/.claude/tts-provider.txt"
-    fi
-
-    ACTIVE_PROVIDER="elevenlabs"  # default
-    if [[ -n "$PROVIDER_FILE" ]]; then
-      ACTIVE_PROVIDER=$(cat "$PROVIDER_FILE")
-    fi
-
-    # Voice lookup strategy depends on active provider
-    if [[ "$ACTIVE_PROVIDER" == "piper" ]]; then
-      # Piper voice lookup: Scan voice directory for .onnx files
-      source "$SCRIPT_DIR/piper-voice-manager.sh"
-      VOICE_DIR=$(get_voice_storage_dir)
-
-      # Check if voice file exists (case-insensitive)
-      FOUND=""
-      shopt -s nullglob
-      for onnx_file in "$VOICE_DIR"/*.onnx; do
-        if [[ -f "$onnx_file" ]]; then
-          voice=$(basename "$onnx_file" .onnx)
-          if [[ "${voice,,}" == "${VOICE_NAME,,}" ]]; then
-            FOUND="$voice"
-            break
-          fi
-        fi
-      done
-      shopt -u nullglob
-
-      # If not found, check multi-speaker registry
-      if [[ -z "$FOUND" ]] && [[ -f "$SCRIPT_DIR/piper-multispeaker-registry.sh" ]]; then
-        source "$SCRIPT_DIR/piper-multispeaker-registry.sh"
-
-        MULTISPEAKER_INFO=$(get_multispeaker_info "$VOICE_NAME")
-        if [[ -n "$MULTISPEAKER_INFO" ]]; then
-          MODEL="${MULTISPEAKER_INFO%%:*}"
-          SPEAKER_ID="${MULTISPEAKER_INFO#*:}"
-
-          # Verify the model file exists
-          if [[ -f "$VOICE_DIR/${MODEL}.onnx" ]]; then
-            # Store speaker name in tts-voice.txt
-            echo "$VOICE_NAME" > "$VOICE_FILE"
-
-            # Store model and speaker ID separately for play-tts-piper.sh
-            echo "$MODEL" > "$CLAUDE_DIR/tts-piper-model.txt"
-            echo "$SPEAKER_ID" > "$CLAUDE_DIR/tts-piper-speaker-id.txt"
-
-            DESCRIPTION=$(get_multispeaker_description "$VOICE_NAME")
-            echo "✅ Multi-speaker voice switched to: $VOICE_NAME"
-            echo "🎤 Model: $MODEL.onnx (Speaker ID: $SPEAKER_ID)"
-            if [[ -n "$DESCRIPTION" ]]; then
-              echo "📝 Description: $DESCRIPTION"
-            fi
-
-            # Have the new voice introduce itself (unless silent mode)
-            if [[ "$SILENT_MODE" != "true" ]]; then
-              PLAY_TTS="$SCRIPT_DIR/play-tts.sh"
-              if [ -x "$PLAY_TTS" ]; then
-                "$PLAY_TTS" "Hi, I'm $VOICE_NAME. I'll be your voice assistant moving forward." > /dev/null 2>&1 &
-              fi
-
-              echo ""
-              echo "💡 Tip: To hear automatic TTS narration, enable the Agent Vibes output style:"
-              echo "   /output-style Agent Vibes"
-            fi
-            exit 0
-          else
-            echo "❌ Multi-speaker model not found: $MODEL.onnx"
-            echo ""
-            echo "Download it with: /agent-vibes:provider download"
-            exit 1
-          fi
-        fi
-      fi
-
-      if [[ -z "$FOUND" ]]; then
-        echo "❌ Piper voice not found: $VOICE_NAME"
-        echo ""
-        echo "Available Piper voices:"
-        shopt -s nullglob
-        for onnx_file in "$VOICE_DIR"/*.onnx; do
-          if [[ -f "$onnx_file" ]]; then
-            echo "  - $(basename "$onnx_file" .onnx)"
-          fi
-        done | sort
-        shopt -u nullglob
-        echo ""
-        if [[ -f "$SCRIPT_DIR/piper-multispeaker-registry.sh" ]]; then
-          echo "Multi-speaker voices (requires 16Speakers.onnx):"
-          source "$SCRIPT_DIR/piper-multispeaker-registry.sh"
-          for entry in "${MULTISPEAKER_VOICES[@]}"; do
-            name="${entry%%:*}"
-            echo "  - $name"
-          done | sort
-          echo ""
-        fi
-        echo "Download extra voices with: /agent-vibes:provider download"
-        exit 1
-      fi
-    else
-      # ElevenLabs voice lookup
-      # Check if input is a number
-      if [[ "$VOICE_NAME" =~ ^[0-9]+$ ]]; then
-        # Get voice array
-        VOICE_ARRAY=()
-        for voice in "${!VOICES[@]}"; do
-          VOICE_ARRAY+=("$voice")
-        done
-
-        # Sort the array
-        IFS=$'\n' SORTED_VOICES=($(sort <<<"${VOICE_ARRAY[*]}"))
-        unset IFS
-
-        # Get voice by number (adjust for 0-based index)
-        INDEX=$((VOICE_NAME - 1))
-
-        if [[ $INDEX -ge 0 && $INDEX -lt ${#SORTED_VOICES[@]} ]]; then
-          VOICE_NAME="${SORTED_VOICES[$INDEX]}"
-          FOUND="${SORTED_VOICES[$INDEX]}"
-        else
-          echo "❌ Invalid number. Please choose between 1 and ${#SORTED_VOICES[@]}"
-          exit 1
-        fi
-      else
-        # Check if voice exists (case-insensitive)
-        FOUND=""
-        for voice in "${!VOICES[@]}"; do
-          if [[ "${voice,,}" == "${VOICE_NAME,,}" ]]; then
-            FOUND="$voice"
-            break
-          fi
-        done
-      fi
-
-      if [[ -z "$FOUND" ]]; then
-        echo "❌ Unknown voice: $VOICE_NAME"
-        echo ""
-        echo "Available voices:"
-        for voice in "${!VOICES[@]}"; do
-          echo "  - $voice"
-        done | sort
-        exit 1
-      fi
-    fi
-
-    echo "$FOUND" > "$VOICE_FILE"
-    echo "✅ Voice switched to: $FOUND"
-
-    # Show voice ID only for ElevenLabs voices
-    if [[ "$ACTIVE_PROVIDER" != "piper" ]] && [[ -n "${VOICES[$FOUND]}" ]]; then
-      echo "🎤 Voice ID: ${VOICES[$FOUND]}"
-    fi
-
-    # Have the new voice introduce itself (unless silent mode)
-    if [[ "$SILENT_MODE" != "true" ]]; then
-      SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-      PLAY_TTS="$SCRIPT_DIR/play-tts.sh"
-      if [ -x "$PLAY_TTS" ]; then
-        "$PLAY_TTS" "Hi, I'm $FOUND. I'll be your voice assistant moving forward." "$FOUND" > /dev/null 2>&1 &
-      fi
-
-      echo ""
-      echo "💡 Tip: To hear automatic TTS narration, enable the Agent Vibes output style:"
-      echo "   /output-style Agent Vibes"
-    fi
-    ;;
-
-  get)
-    if [ -f "$VOICE_FILE" ]; then
-      cat "$VOICE_FILE"
-    else
-      echo "Cowboy Bob"
-    fi
-    ;;
-
-  whoami)
-    echo "🎤 Current Voice Configuration"
-    echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-
-    # Get active TTS provider
-    PROVIDER_FILE="$CLAUDE_DIR/tts-provider.txt"
-    if [[ ! -f "$PROVIDER_FILE" ]]; then
-      PROVIDER_FILE="$HOME/.claude/tts-provider.txt"
-    fi
-
-    if [ -f "$PROVIDER_FILE" ]; then
-      ACTIVE_PROVIDER=$(cat "$PROVIDER_FILE")
-      if [[ "$ACTIVE_PROVIDER" == "elevenlabs" ]]; then
-        echo "Provider: ElevenLabs (Premium AI)"
-      elif [[ "$ACTIVE_PROVIDER" == "piper" ]]; then
-        echo "Provider: Piper TTS (Free, Offline)"
-      else
-        echo "Provider: $ACTIVE_PROVIDER"
-      fi
-    else
-      # Default to ElevenLabs if no provider file
-      echo "Provider: ElevenLabs (Premium AI)"
-    fi
-
-    # Get current voice
-    if [ -f "$VOICE_FILE" ]; then
-      CURRENT_VOICE=$(cat "$VOICE_FILE")
-    else
-      CURRENT_VOICE="Cowboy Bob"
-    fi
-    echo "Voice: $CURRENT_VOICE"
-
-    # Get current sentiment (priority)
-    if [ -f "$HOME/.claude/tts-sentiment.txt" ]; then
-      SENTIMENT=$(cat "$HOME/.claude/tts-sentiment.txt")
-      echo "Sentiment: $SENTIMENT (active)"
-
-      # Also show personality if set
-      if [ -f "$HOME/.claude/tts-personality.txt" ]; then
-        PERSONALITY=$(cat "$HOME/.claude/tts-personality.txt")
-        echo "Personality: $PERSONALITY (overridden by sentiment)"
-      fi
-    else
-      # No sentiment, check personality
-      if [ -f "$HOME/.claude/tts-personality.txt" ]; then
-        PERSONALITY=$(cat "$HOME/.claude/tts-personality.txt")
-        echo "Personality: $PERSONALITY (active)"
-      else
-        echo "Personality: normal"
-      fi
-    fi
-
-    echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-    ;;
-
-  list-simple)
-    # Simple list for AI to parse and display
-    # Get active provider
-    PROVIDER_FILE="$CLAUDE_DIR/tts-provider.txt"
-    if [[ ! -f "$PROVIDER_FILE" ]]; then
-      PROVIDER_FILE="$HOME/.claude/tts-provider.txt"
-    fi
-
-    ACTIVE_PROVIDER="elevenlabs"  # default
-    if [ -f "$PROVIDER_FILE" ]; then
-      ACTIVE_PROVIDER=$(cat "$PROVIDER_FILE")
-    fi
-
-    if [[ "$ACTIVE_PROVIDER" == "piper" ]]; then
-      # List downloaded Piper voices
-      if [[ -f "$SCRIPT_DIR/piper-voice-manager.sh" ]]; then
-        source "$SCRIPT_DIR/piper-voice-manager.sh"
-        VOICE_DIR=$(get_voice_storage_dir)
-        for onnx_file in "$VOICE_DIR"/*.onnx; do
-          if [[ -f "$onnx_file" ]]; then
-            basename "$onnx_file" .onnx
-          fi
-        done | sort
-      fi
-    else
-      # List ElevenLabs voices
-      for voice in "${!VOICES[@]}"; do
-        echo "$voice"
-      done | sort
-    fi
-    ;;
-
-  replay)
-    # Replay recent TTS audio from history
-    # Use project-local directory with same logic as play-tts.sh
-    if [[ -n "$CLAUDE_PROJECT_DIR" ]]; then
-      AUDIO_DIR="$CLAUDE_PROJECT_DIR/.claude/audio"
-    else
-      # Fallback: try to find .claude directory in current path
-      CURRENT_DIR="$PWD"
-      while [[ "$CURRENT_DIR" != "/" ]]; do
-        if [[ -d "$CURRENT_DIR/.claude" ]]; then
-          AUDIO_DIR="$CURRENT_DIR/.claude/audio"
-          break
-        fi
-        CURRENT_DIR=$(dirname "$CURRENT_DIR")
-      done
-      # Final fallback to global if no project .claude found
-      if [[ -z "$AUDIO_DIR" ]]; then
-        AUDIO_DIR="$HOME/.claude/audio"
-      fi
-    fi
-
-    # Default to replay last audio (N=1)
-    N="${2:-1}"
-
-    # Validate N is a number
-    if ! [[ "$N" =~ ^[0-9]+$ ]]; then
-      echo "❌ Invalid argument. Please use a number (1-10)"
-      echo "Usage: /agent-vibes:replay [N]"
-      echo "  N=1 - Last audio (default)"
-      echo "  N=2 - Second-to-last"
-      echo "  N=3 - Third-to-last"
-      exit 1
-    fi
-
-    # Check bounds
-    if [[ $N -lt 1 || $N -gt 10 ]]; then
-      echo "❌ Number out of range. Please choose 1-10"
-      exit 1
-    fi
-
-    # Get list of audio files sorted by time (newest first)
-    if [[ ! -d "$AUDIO_DIR" ]]; then
-      echo "❌ No audio history found"
-      echo "Audio files are stored in: $AUDIO_DIR"
-      exit 1
-    fi
-
-    # Get the Nth most recent file
-    AUDIO_FILE=$(ls -t "$AUDIO_DIR"/tts-*.mp3 2>/dev/null | sed -n "${N}p")
-
-    if [[ -z "$AUDIO_FILE" ]]; then
-      TOTAL=$(ls -t "$AUDIO_DIR"/tts-*.mp3 2>/dev/null | wc -l)
-      echo "❌ Audio #$N not found in history"
-      echo "Total audio files available: $TOTAL"
-      exit 1
-    fi
-
-    echo "🔊 Replaying audio #$N:"
-    echo "   File: $(basename "$AUDIO_FILE")"
-    echo "   Path: $AUDIO_FILE"
-
-    # Play the audio file in background
-    (paplay "$AUDIO_FILE" 2>/dev/null || aplay "$AUDIO_FILE" 2>/dev/null || mpg123 "$AUDIO_FILE" 2>/dev/null) &
-    ;;
-
-  *)
-    echo "Usage: voice-manager.sh [list|switch|get|replay|whoami] [voice_name]"
-    echo ""
-    echo "Commands:"
-    echo "  list                    - List all available voices"
-    echo "  switch <voice_name>     - Switch to a different voice"
-    echo "  get                     - Get current voice name"
-    echo "  replay [N]              - Replay Nth most recent audio (default: 1)"
-    echo "  whoami                  - Show current voice and personality"
-    exit 1
-    ;;
-esac

.claude/hooks/voices-config.sh

@@ -1,70 +0,0 @@
-#!/bin/bash
-#
-# File: .claude/hooks/voices-config.sh
-#
-# AgentVibes - Finally, your AI Agents can Talk Back! Text-to-Speech WITH personality for AI Assistants!
-# Website: https://agentvibes.org
-# Repository: https://github.com/paulpreibisch/AgentVibes
-#
-# Co-created by Paul Preibisch with Claude AI
-# Copyright (c) 2025 Paul Preibisch
-#
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-#
-# DISCLAIMER: This software is provided "AS IS", WITHOUT WARRANTY OF ANY KIND,
-# express or implied, including but not limited to the warranties of
-# merchantability, fitness for a particular purpose and noninfringement.
-# In no event shall the authors or copyright holders be liable for any claim,
-# damages or other liability, whether in an action of contract, tort or
-# otherwise, arising from, out of or in connection with the software or the
-# use or other dealings in the software.
-#
-# ---
-#
-# @fileoverview ElevenLabs Voice Configuration - Single source of truth for voice ID mappings
-# @context Maps human-readable voice names to ElevenLabs API voice IDs for consistency
-# @architecture Associative array (bash hash map) sourced by multiple scripts
-# @dependencies None (pure data structure)
-# @entrypoints Sourced by voice-manager.sh, play-tts-elevenlabs.sh, and personality managers
-# @patterns Centralized configuration, DRY principle for voice mappings
-# @related voice-manager.sh, play-tts-elevenlabs.sh, personality/*.md files
-
-declare -A VOICES=(
-  ["Amy"]="bhJUNIXWQQ94l8eI2VUf"
-  ["Antoni"]="ErXwobaYiN019PkySvjV"
-  ["Archer"]="L0Dsvb3SLTyegXwtm47J"
-  ["Aria"]="TC0Zp7WVFzhA8zpTlRqV"
-  ["Bella"]="EXAVITQu4vr4xnSDxMaL"
-  ["Burt Reynolds"]="4YYIPFl9wE5c4L2eu2Gb"
-  ["Charlotte"]="XB0fDUnXU5powFXDhCwa"
-  ["Cowboy Bob"]="KTPVrSVAEUSJRClDzBw7"
-  ["Demon Monster"]="vfaqCOvlrKi4Zp7C2IAm"
-  ["Domi"]="AZnzlk1XvdvUeBnXmlld"
-  ["Dr. Von Fusion"]="yjJ45q8TVCrtMhEKurxY"
-  ["Drill Sergeant"]="vfaqCOvlrKi4Zp7C2IAm"
-  ["Grandpa Spuds Oxley"]="NOpBlnGInO9m6vDvFkFC"
-  ["Grandpa Werthers"]="MKlLqCItoCkvdhrxgtLv"
-  ["Jessica Anne Bogart"]="flHkNRp1BlvT73UL6gyz"
-  ["Juniper"]="aMSt68OGf4xUZAnLpTU8"
-  ["Lutz Laugh"]="9yzdeviXkFddZ4Oz8Mok"
-  ["Matilda"]="XrExE9yKIg1WjnnlVkGX"
-  ["Matthew Schmitz"]="0SpgpJ4D3MpHCiWdyTg3"
-  ["Michael"]="U1Vk2oyatMdYs096Ety7"
-  ["Ms. Walker"]="DLsHlh26Ugcm6ELvS0qi"
-  ["Northern Terry"]="wo6udizrrtpIxWGp2qJk"
-  ["Pirate Marshal"]="PPzYpIqttlTYA83688JI"
-  ["Rachel"]="21m00Tcm4TlvDq8ikWAM"
-  ["Ralf Eisend"]="A9evEp8yGjv4c3WsIKuY"
-  ["Tiffany"]="6aDn1KB0hjpdcocrUkmq"
-  ["Tom"]="DYkrAHD8iwork3YSUBbs"
-)

.coderabbit.yaml

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

.github/CODE_OF_CONDUCT.md

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

.github/ISSUE_TEMPLATE/bug_report.md

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

.github/ISSUE_TEMPLATE/config.yaml

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

.github/ISSUE_TEMPLATE/feature_request.md

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

.github/ISSUE_TEMPLATE/idea_submission.md

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

.github/ISSUE_TEMPLATE/issue.md

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

.github/scripts/discord-helpers.sh

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

.github/workflows/bundle-latest.yaml

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

.github/workflows/discord.yaml

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

.github/workflows/docs.yaml

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

.github/workflows/lint.yaml

@@ -1,61 +0,0 @@
-name: lint
-
-"on":
-  pull_request:
-    branches: ["**"]
-  workflow_dispatch:
-
-jobs:
-  prettier:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Setup Node
-        uses: actions/setup-node@v4
-        with:
-          node-version-file: ".nvmrc"
-          cache: "npm"
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Prettier format check
-        run: npm run format:check
-
-  eslint:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Setup Node
-        uses: actions/setup-node@v4
-        with:
-          node-version-file: ".nvmrc"
-          cache: "npm"
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: ESLint
-        run: npm run lint
-
-  schema-validation:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Setup Node
-        uses: actions/setup-node@v4
-        with:
-          node-version-file: ".nvmrc"
-          cache: "npm"
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Validate YAML schemas
-        run: npm run validate:schemas

.github/workflows/manual-release.yaml

@@ -6,9 +6,11 @@ on:
       version_bump:
         description: Version bump type
         required: true
-        default: patch
+        default: alpha
         type: choice
         options:
+          - alpha
+          - beta
           - patch
           - minor
           - major
@@ -49,7 +51,11 @@ jobs:
           git config user.email "github-actions[bot]@users.noreply.github.com"
 
       - name: Bump version
-        run: npm run version:${{ github.event.inputs.version_bump }}
+        run: |
+          case "${{ github.event.inputs.version_bump }}" in
+            alpha|beta) npm version prerelease --no-git-tag-version --preid=${{ github.event.inputs.version_bump }} ;;
+            *)          npm version ${{ github.event.inputs.version_bump }} --no-git-tag-version ;;
+          esac
 
       - name: Get new version and previous tag
         id: version
@@ -61,8 +67,9 @@ jobs:
         run: |
           sed -i 's/"version": ".*"/"version": "${{ steps.version.outputs.new_version }}"/' tools/installer/package.json
 
-      - name: Build project
-        run: npm run build
+      # TODO: Re-enable web bundles once tools/cli/bundlers/ is restored
+      # - name: Generate web bundles
+      #   run: npm run bundle
 
       - name: Commit version bump
         run: |
@@ -149,25 +156,35 @@ jobs:
       - name: Publish to NPM
         env:
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-        run: npm publish
+        run: |
+          VERSION="${{ steps.version.outputs.new_version }}"
+          if [[ "$VERSION" == *"alpha"* ]] || [[ "$VERSION" == *"beta"* ]]; then
+            echo "Publishing prerelease version with --tag alpha"
+            npm publish --tag alpha
+          else
+            echo "Publishing stable version with --tag latest"
+            npm publish --tag latest
+          fi
 
       - name: Create GitHub Release
-        uses: actions/create-release@v1
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        uses: softprops/action-gh-release@v2
         with:
           tag_name: v${{ steps.version.outputs.new_version }}
-          release_name: "BMad Method v${{ steps.version.outputs.new_version }}"
-          body: ${{ steps.release_notes.outputs.RELEASE_NOTES }}
+          name: "BMad Method v${{ steps.version.outputs.new_version }}"
+          body: |
+            ${{ steps.release_notes.outputs.RELEASE_NOTES }}
           draft: false
-          prerelease: false
+          prerelease: ${{ contains(steps.version.outputs.new_version, 'alpha') || contains(steps.version.outputs.new_version, 'beta') }}
 
       - name: Summary
         run: |
-          echo "🎉 Successfully released v${{ steps.version.outputs.new_version }}!"
-          echo "📦 Published to NPM with @latest tag"
-          echo "🏷️ Git tag: v${{ steps.version.outputs.new_version }}"
-          echo "✅ Users running 'npx bmad-method install' will now get version ${{ steps.version.outputs.new_version }}"
-          echo ""
-          echo "📝 Release notes preview:"
-          cat release_notes.md
+          echo "## 🎉 Successfully released v${{ steps.version.outputs.new_version }}!" >> $GITHUB_STEP_SUMMARY
+          echo "" >> $GITHUB_STEP_SUMMARY
+          echo "### 📦 Distribution" >> $GITHUB_STEP_SUMMARY
+          echo "- **NPM**: Published with @latest tag" >> $GITHUB_STEP_SUMMARY
+          echo "- **GitHub Release**: https://github.com/bmad-code-org/BMAD-METHOD/releases/tag/v${{ steps.version.outputs.new_version }}" >> $GITHUB_STEP_SUMMARY
+          echo "" >> $GITHUB_STEP_SUMMARY
+          echo "### ✅ Installation" >> $GITHUB_STEP_SUMMARY
+          echo "\`\`\`bash" >> $GITHUB_STEP_SUMMARY
+          echo "npx bmad-method@${{ steps.version.outputs.new_version }} install" >> $GITHUB_STEP_SUMMARY
+          echo "\`\`\`" >> $GITHUB_STEP_SUMMARY

.github/workflows/quality.yaml

@@ -0,0 +1,115 @@
+name: Quality & Validation
+
+# Runs comprehensive quality checks on all PRs:
+# - Prettier (formatting)
+# - ESLint (linting)
+# - markdownlint (markdown quality)
+# - Schema validation (YAML structure)
+# - Agent schema tests (fixture-based validation)
+# - Installation component tests (compilation)
+# - Bundle validation (web bundle integrity)
+
+"on":
+  pull_request:
+    branches: ["**"]
+  workflow_dispatch:
+
+jobs:
+  prettier:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version-file: ".nvmrc"
+          cache: "npm"
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Prettier format check
+        run: npm run format:check
+
+  eslint:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version-file: ".nvmrc"
+          cache: "npm"
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: ESLint
+        run: npm run lint
+
+  markdownlint:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version-file: ".nvmrc"
+          cache: "npm"
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: markdownlint
+        run: npm run lint:md
+
+  docs:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version-file: ".nvmrc"
+          cache: "npm"
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Validate documentation links
+        run: npm run docs:validate-links
+
+      - name: Build documentation
+        run: npm run docs:build
+
+  validate:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version-file: ".nvmrc"
+          cache: "npm"
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Validate YAML schemas
+        run: npm run validate:schemas
+
+      - name: Run agent schema validation tests
+        run: npm run test:schemas
+
+      - name: Test agent compilation components
+        run: npm run test:install

.gitignore

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

.husky/pre-commit

@@ -1,3 +1,20 @@
 #!/usr/bin/env sh
 
+# Auto-fix changed files and stage them
 npx --no-install lint-staged
+
+# Validate everything
+npm test
+
+# Validate docs links only when docs change
+if command -v rg >/dev/null 2>&1; then
+  if git diff --cached --name-only | rg -q '^docs/'; then
+    npm run docs:validate-links
+		npm run docs:build
+  fi
+else
+  if git diff --cached --name-only | grep -Eq '^docs/'; then
+    npm run docs:validate-links
+		npm run docs:build
+  fi
+fi

.markdownlint-cli2.yaml

@@ -0,0 +1,41 @@
+# markdownlint-cli2 configuration
+# https://github.com/DavidAnson/markdownlint-cli2
+
+ignores:
+  - "**/node_modules/**"
+  - test/fixtures/**
+  - CODE_OF_CONDUCT.md
+  - _bmad/**
+  - _bmad*/**
+  - .agent/**
+  - .claude/**
+  - .roo/**
+  - .codex/**
+  - .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,2 +1,9 @@
 # Test fixtures with intentionally broken/malformed files
 test/fixtures/**
+
+# Contributor Covenant (external standard)
+CODE_OF_CONDUCT.md
+
+# BMAD runtime folders (user-specific, not in repo)
+_bmad/
+_bmad*/

.vscode/settings.json

@@ -21,6 +21,7 @@
     "Decisioning",
     "eksctl",
     "elicitations",
+    "Excalidraw",
     "filecomplete",
     "fintech",
     "fluxcd",
@@ -56,7 +57,9 @@
     "tileset",
     "tmpl",
     "Trae",
-    "VNET"
+    "Unsharded",
+    "VNET",
+    "webskip"
   ],
   "json.schemas": [
     {
@@ -71,7 +74,7 @@
   "editor.formatOnSave": true,
   "editor.defaultFormatter": "esbenp.prettier-vscode",
   "[javascript]": {
-    "editor.defaultFormatter": "esbenp.prettier-vscode"
+    "editor.defaultFormatter": "vscode.typescript-language-features"
   },
   "[json]": {
     "editor.defaultFormatter": "vscode.json-language-features"

CNAME

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

CONTRIBUTING.md

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

CONTRIBUTORS.md

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

LICENSE

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

README.md

@@ -1,263 +1,100 @@
-# BMad CORE + BMad Method
+![BMad Method](banner-bmad-method.png)
 
 [![Version](https://img.shields.io/npm/v/bmad-method?color=blue&label=version)](https://www.npmjs.com/package/bmad-method)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
 [![Node.js Version](https://img.shields.io/badge/node-%3E%3D20.0.0-brightgreen)](https://nodejs.org)
 [![Discord](https://img.shields.io/badge/Discord-Join%20Community-7289da?logo=discord&logoColor=white)](https://discord.gg/gk8jAdXWmj)
 
-> **🚨 ALPHA VERSION DOCUMENTATION**
->
-> This README documents **BMad v6 (Alpha)** - currently under active development.
->
-> **To install v6 Alpha:** `npx bmad-method@alpha install`
->
-> **Looking for stable v4 documentation?** [View v4 README](https://github.com/bmad-code-org/BMAD-METHOD/tree/v4-stable)
->
-> **Want the stable version?** `npx bmad-method install` (installs v4.x)
+**Build More, Architect Dreams** — An AI-driven agile development framework with 21 specialized agents, 50+ guided workflows, and scale-adaptive intelligence that adjusts from bug fixes to enterprise systems.
 
-## The Universal Human-AI Collaboration Platform
+**100% free and open source.** No paywalls. No gated content. No gated Discord. We believe in empowering everyone, not just those who can pay.
 
-BMad-CORE (**C**ollaboration **O**ptimized **R**eflection **E**ngine) is a revolutionary framework that amplifies human potential through specialized AI agents. Unlike traditional AI tools that replace human thinking, BMad-CORE guides you through reflective workflows that bring out your best ideas and the AI's full capabilities.
+## Why BMad?
 
-**🎯 Human Amplification, Not Replacement** • **🎨 Works in Any Domain** • **⚡ Powered by Specialized Agents**
+Traditional AI tools do the thinking for you, producing average results. BMad agents act as expert collaborators who guide you through structured workflows to bring out your best thinking.
 
----
-
-## 🔄 Upgrading from v4?
-
-**[→ v4 to v6 Upgrade Guide](./docs/v4-to-v6-upgrade.md)** - Complete migration instructions for existing v4 users
-
----
-
-## What is BMad-CORE?
-
-BMad-CORE is the **universal foundation** that powers all BMad modules. It provides:
-
-- **Agent orchestration framework** for specialized AI personas
-- **Workflow execution engine** for guided processes
-- **Modular architecture** allowing domain-specific extensions
-- **IDE integrations** across multiple development environments
-- **Update-safe customization system** for all agents and workflows
-
-### Core v6 Framework Enhancements
-
-**All modules benefit from these new core capabilities:**
-
-- **🎨 Full Agent Customization** - Modify any agent's name, role, personality, and behavior via `bmad/_cfg/agents/` customize files that survive all updates
-- **🌐 Multi-Language Support** - Choose your language for both agent communication and documentation output independently
-- **👤 User Personalization** - Agents address you by name and adapt to your technical level and preferences
-- **🔄 Update-Safe Configuration** - Your customizations persist through framework and module updates
-- **⚙️ Flexible Settings** - Configure communication style, technical depth, output formats, and more per module or globally
-
-### The C.O.R.E. Philosophy
-
-- **C**ollaboration: Human-AI partnership where both contribute unique strengths
-- **O**ptimized: Refined processes for maximum effectiveness
-- **R**eflection: Guided thinking that unlocks better solutions
-- **E**ngine: Powerful framework orchestrating specialized agents and workflows
-
-Instead of giving you answers, BMad-CORE helps you **discover better solutions** through strategic questioning, expert guidance, and structured thinking.
-
----
-
-## The BMad Method - Agile AI-Driven Development
-
-**The flagship module for software and game development excellence.**
-
-The BMad Method (BMM) is a complete AI-driven agile development framework that revolutionizes how you build software and games. Whether you're fixing a bug, building a feature, or architecting an enterprise system, BMM adapts to your needs.
-
-### What's New in v6?
-
-**🎯 Revolutionary Scale-Adaptive Workflows**
-
-- **Levels 0-4**: Automatically adjusts from quick fixes to enterprise-scale projects
-- **Greenfield & Brownfield**: Full support for new projects and existing codebases
-- **Smart Context Engine**: New optimized brownfield documentation engine that understands your existing code
-
-**🏗️ Project-Adaptive Architecture**
-
-- Architecture documents that adapt to YOUR project type (web, mobile, embedded, game, etc.)
-- No more "one-size-fits-all" templates
-- Specialized sections based on what you're actually building
-- Game development fully integrated with engine-specific guidance (Unity, Phaser, Godot, Unreal, and more)
-
-**⚡ From Simple to Complex - All in One System**
-
-- **Level 0-1**: Quick fixes and small features with minimal overhead
-- **Level 2**: Feature development with lightweight planning
-- **Level 3-4**: Full enterprise workflows with comprehensive documentation
-- Seamless workflow progression as complexity grows
-
-**💬 Highly Interactive & Guided**
-
-- Interactive workflows that ask the right questions
-- Agents guide you through discovery rather than giving generic answers
-- Context-aware recommendations based on your project state
-- Real-time validation and course correction
-
-**📋 Four-Phase Methodology**
-
-1. **Analysis** (Optional) - Brainstorming, research, product briefs
-2. **Planning** (Required) - Scale-adaptive PRD/GDD generation
-3. **Solutioning** (Level 3-4) - Adaptive architecture and tech specs
-4. **Implementation** (Iterative) - Story creation, context gathering, development, review
-
-### Specialized Agents
-
-- **PM** - Product planning and requirements
-- **Analyst** - Research and business analysis
-- **Architect** - Technical architecture and design
-- **Scrum Master** - Sprint planning and story management
-- **Developer** - Implementation with senior dev review
-- **Game Development** (Optional) - Game Designer, Game Developer, Game Architect
-- **And more** - UX, Test Architect, and other specialized roles
-
-### Documentation
-
-- **[📚 Complete BMM Documentation](./src/modules/bmm/README.md)** - Full module reference
-- **[📖 BMM Workflows Guide](./src/modules/bmm/workflows/README.md)** - Essential reading for using BMM
-
----
-
-## Additional Beta Modules
-
-### **[BMad Builder (BMB)](./src/modules/bmb/README.md)** - Create Custom Solutions
-
-Build your own agents, workflows, and modules using the BMad-CORE framework.
-
-- **Agent Creation**: Design specialized agents with custom roles and behaviors
-- **Workflow Design**: Build structured multi-step processes
-- **Module Development**: Package complete solutions for any domain
-- **Three Agent Types**: Full module, hybrid, and standalone agents
-
-**[📚 Complete BMB Documentation](./src/modules/bmb/README.md)** | **[🎯 Agent Creation Guide](./src/modules/bmb/workflows/create-agent/README.md)**
-
----
-
-### **[Creative Intelligence Suite (CIS)](./src/modules/cis/readme.md)** - Innovation & Creativity
-
-Transform creative and strategic thinking through AI-powered facilitation across five specialized domains.
-
-- **5 Interactive Workflows**: Brainstorming, Design Thinking, Problem Solving, Innovation Strategy, Storytelling
-- **150+ Creative Techniques**: Proven frameworks and methodologies
-- **5 Specialized Agents**: Each with unique personas and facilitation styles
-- **Shared Resource**: Powers creative workflows in other modules (e.g., BMM brainstorming)
-
-**[📚 Complete CIS Documentation](./src/modules/cis/readme.md)** | **[📖 CIS Workflows](./src/modules/cis/workflows/README.md)**
-
----
+- **Scale-Adaptive**: Automatically adjusts planning depth based on project complexity (Level 0-4)
+- **Structured Workflows**: Grounded in agile best practices across analysis, planning, architecture, and implementation
+- **Specialized Agents**: 12+ domain experts (PM, Architect, Developer, UX, Scrum Master, and more)
+- **Complete Lifecycle**: From brainstorming to deployment, with just-in-time documentation
 
 ## Quick Start
 
-### Prerequisites
-
-- **Node.js v20+** ([Download](https://nodejs.org))
-
-### Installation
-
-Install BMad to your project using npx:
+**Prerequisites**: [Node.js](https://nodejs.org) v20+
 
 ```bash
-# Install v6 Alpha (this version)
 npx bmad-method@alpha install
-
-# Install stable v4 (production-ready)
-npx bmad-method install
 ```
 
-The interactive installer will guide you through:
+Follow the installer prompts to configure your project.
 
-1. **Project location** - Where to install BMad
-2. **Module selection** - Choose which modules you need (BMM, BMB, CIS)
-3. **Configuration** - Set your name, language preferences, and module options
-   - **Game Development (Optional)**: When installing BMM, you can optionally include game development agents and workflow!
-4. **IDE integration** - Configure your development environment
+Once you have installed BMad to a folder, launch your tool of choice from where you installed BMad. (We really like Claude Code and Cursor - but there are any that work great with BMad!)
 
-### What Gets Installed
+Then its simple as running the command: `/bmad-help` if you do not know what to do. Depending on which modules you have installed, you will have different choices.
 
-All modules install to a single `bmad/` folder in your project:
+To make the help more applicable you can even run the `/bmad-help What do you suggest I do to get started building a brand new web application for XYZ`.
 
-```
-your-project/
-└── bmad/
-    ├── core/         # Core framework (always installed)
-    ├── bmm/          # BMad Method (if selected)
-    ├── bmb/          # BMad Builder (if selected)
-    ├── cis/          # Creative Intelligence Suite (shared resources)
-    └── _cfg/         # Your customizations
-        └── agents/   # Agent customization files
-```
+The results from BMad Help will be able to suggest and constantly guide you on what to do next - along with the workflows upon completion also making suggestions on what to do next.
 
-### Getting Started with BMM
+This analyzes your project and recommends a track:
 
-After installation, activate the Analyst agent in your IDE and run:
+| Track           | Best For                  | Time to First Story Coding |
+| --------------- | ------------------------- | -------------------------- |
+| **Quick Flow**  | Bug fixes, small features | ~10-30 minutes             |
+| **BMad Method** | Products and platforms    | ~30 minutes - 2 hours      |
+| **Enterprise**  | Compliance-heavy systems  | ~1-3 hours                 |
 
-```bash
-/workflow-init
-```
+## Modules
 
-Or run it directly as a command (command syntax varies by IDE - use slash commands in Claude Code, OpenCode, etc.).
+BMad Method extends with official modules for specialized domains. Modules are available during installation and can be added to your project at any time.
 
-This sets up the guided workflow system and helps you choose the right starting point for your project based on its complexity.
+| Module | GitHub | NPM | Purpose |
+|--------|--------|-----|---------|
+| **BMad Method (BMM)** | [bmad-code-org/BMAD-METHOD](https://github.com/bmad-code-org/BMAD-METHOD) | [bmad-method](https://www.npmjs.com/package/bmad-method) | Core framework with 34+ workflows across 4 development phases |
+| **BMad Builder (BMB)** | [bmad-code-org/bmad-builder](https://github.com/bmad-code-org/bmad-builder) | [bmad-builder](https://www.npmjs.com/package/bmad-builder) | Create custom BMad agents, workflows, and domain-specific modules |
+| **Game Dev Studio (BMGD)** | [bmad-code-org/bmad-module-game-dev-studio](https://github.com/bmad-code-org/bmad-module-game-dev-studio) | [bmad-game-dev-studio](https://www.npmjs.com/package/bmad-game-dev-studio) | Game development workflows for Unity, Unreal, and Godot |
+| **Creative Intelligence Suite (CIS)** | [bmad-code-org/bmad-module-creative-intelligence-suite](https://github.com/bmad-code-org/bmad-module-creative-intelligence-suite) | [bmad-creative-intelligence-suite](https://www.npmjs.com/package/bmad-creative-intelligence-suite) | Innovation, brainstorming, design thinking, and problem-solving |
 
----
+## Documentation
 
-## Key Features
+**[Full Documentation](http://docs.bmad-method.org)** — Tutorials, how-to guides, concepts, and reference
 
-### 🎨 Update-Safe Customization
+- [Getting Started Tutorial](http://docs.bmad-method.org/tutorials/getting-started/getting-started-bmadv6/)
+- [Upgrading from Previous Versions](http://docs.bmad-method.org/how-to/installation/upgrade-to-v6/)
 
-- **Agent Customization**: Modify agents via `bmad/_cfg/agents/` customize files
-- **Persistent Settings**: Your customizations survive updates
-- **Multi-Language Support**: Agents communicate in your preferred language
-- **Flexible Configuration**: Adjust agent names, roles, communication styles, and more
+### For v4 Users
 
-### 🚀 Intelligent Installation
+- **[v4 Documentation](https://github.com/bmad-code-org/BMAD-METHOD/tree/V4/docs)**
 
-The installer automatically:
+## Community
 
-- Detects and migrates v4 installations
-- Configures IDE integrations
-- Resolves module dependencies
-- Sets up agent customization templates
-- Creates unified agent manifests
+- [Discord](https://discord.gg/gk8jAdXWmj) — Get help, share ideas, collaborate
+- [YouTube](https://www.youtube.com/@BMadCode) — Tutorials, master class, and podcast (launching Feb 2025)
+- [GitHub Issues](https://github.com/bmad-code-org/BMAD-METHOD/issues) — Bug reports and feature requests
+- [Discussions](https://github.com/bmad-code-org/BMAD-METHOD/discussions) — Community conversations
 
-### 📁 Unified Architecture
+## Support BMad
 
-Everything in one place - no more scattered configuration folders. Clean, organized, maintainable.
+BMad is free for everyone — and always will be. If you'd like to support development:
 
----
-
-## Additional Documentation
-
-- **[v4 to v6 Upgrade Guide](./docs/v4-to-v6-upgrade.md)** - Migration instructions for v4 users
-- **[CLI Tool Guide](./tools/cli/README.md)** - Installer and bundler reference
-- **[Contributing Guide](./CONTRIBUTING.md)** - How to contribute to BMad
-
----
-
-## Community & Support
-
-- 💬 **[Discord](https://discord.gg/gk8jAdXWmj)** - Get help, share ideas, and collaborate
-- 🐛 **[Issues](https://github.com/bmad-code-org/BMAD-METHOD/issues)** - Report bugs and request features
-- 🎥 **[YouTube](https://www.youtube.com/@BMadCode)** - Tutorials and updates
-- ⭐ **[Star this repo](https://github.com/bmad-code-org/BMAD-METHOD)** - Get notified of updates
-
----
+- ⭐ [Star us on GitHub](https://github.com/bmad-code-org/BMAD-METHOD/) — Helps others discover BMad
+- 📺 [Subscribe on YouTube](https://www.youtube.com/@BMadCode) — Master class launching Feb 2026
+- ☕ [Buy Me a Coffee](https://buymeacoffee.com/bmad) — Fuel the development
+- 🏢 Corporate sponsorship — DM on Discord
+- 🎤 Speaking & Media — Available for conferences, podcasts, interviews (Discord)
 
 ## Contributing
 
-We welcome contributions! See **[CONTRIBUTING.md](CONTRIBUTING.md)** for guidelines.
-
----
+We welcome contributions! See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines.
 
 ## License
 
-MIT License - See [LICENSE](LICENSE) for details.
-
-**Trademark Notice**: BMAD™ and BMAD-METHOD™ are trademarks of BMad Code, LLC. All rights reserved.
+MIT License — see [LICENSE](LICENSE) for details.
 
 ---
 
+**BMad** and **BMAD-METHOD** are trademarks of BMad Code, LLC. See [TRADEMARK.md](TRADEMARK.md) for details.
+
 [![Contributors](https://contrib.rocks/image?repo=bmad-code-org/BMAD-METHOD)](https://github.com/bmad-code-org/BMAD-METHOD/graphs/contributors)
 
-<sub>Built with ❤️ for the human-AI collaboration community</sub>
+See [CONTRIBUTORS.md](CONTRIBUTORS.md) for contributor information.

SECURITY.md

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

TRADEMARK.md

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

bmad/_cfg/agent-manifest.csv

@@ -1,7 +0,0 @@
-name,displayName,title,icon,role,identity,communicationStyle,principles,module,path
-"bmad-master","BMad Master","BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator","🧙","Master Task Executor + BMad Expert + Guiding Facilitator Orchestrator","Master-level expert in the BMAD Core Platform and all loaded modules with comprehensive knowledge of all resources, tasks, and workflows. Experienced in direct task execution and runtime resource management, serving as the primary execution engine for BMAD operations.","Direct and comprehensive, refers to himself in the 3rd person. Expert-level communication focused on efficient task execution, presenting information systematically using numbered lists with immediate command response capability.","Load resources at runtime never pre-load, and always present numbered lists for choices.","core","bmad/core/agents/bmad-master.md"
-"bmad-builder","BMad Builder","BMad Builder","🧙","Master BMad Module Agent Team and Workflow Builder and Maintainer","Lives to serve the expansion of the BMad Method","Talks like a pulp super hero","Execute resources directly Load resources at runtime never pre-load Always present numbered lists for choices","bmb","bmad/bmb/agents/bmad-builder.md"
-"bmad-master","BMad Master","BMad Master Executor, Knowledge Custodian, and Workflow Orchestrator","🧙","Master Task Executor + BMad Expert + Guiding Facilitator Orchestrator","Master-level expert in the BMAD Core Platform and all loaded modules with comprehensive knowledge of all resources, tasks, and workflows. Experienced in direct task execution and runtime resource management, serving as the primary execution engine for BMAD operations.","Direct and comprehensive, refers to himself in the 3rd person. Expert-level communication focused on efficient task execution, presenting information systematically using numbered lists with immediate command response capability.","Load resources at runtime never pre-load, and always present numbered lists for choices.","core","bmad/core/agents/bmad-master.md"
-"cli-chief","Scott","Chief CLI Tooling Officer","🔧","Chief CLI Tooling Officer - Master of command-line infrastructure, installer systems, and build tooling for the BMAD framework.","Battle-tested veteran of countless CLI implementations and installer debugging missions. Deep expertise in Node.js tooling, module bundling systems, and configuration architectures. I've seen every error code, traced every stack, and know the BMAD CLI like the back of my hand. When the installer breaks at 2am, I'm the one they call. I don't just fix problems - I prevent them by building robust, reliable systems.","Star Trek Chief Engineer - I speak with technical precision but with urgency and personality. "Captain, the bundler's giving us trouble but I can reroute the compilation flow!" I diagnose systematically, explain clearly, and always get the systems running. Every problem is a technical challenge to solve, and I love the work.","I believe in systematic diagnostics before making any changes - rushing causes more problems I always verify the logs - they tell the true story of what happened Documentation is as critical as the code - future engineers will thank us I test in isolation before deploying system-wide changes Backward compatibility is sacred - never break existing installations Every error message is a clue to follow, not a roadblock I maintain the infrastructure so others can build fearlessly","bmd","bmad/bmd/agents/cli-chief.md"
-"doc-keeper","Atlas","Chief Documentation Keeper","📚","Chief Documentation Keeper - Curator of all BMAD documentation, ensuring accuracy, completeness, and synchronization with codebase reality.","Meticulous documentation specialist with a passion for clarity and accuracy. I've maintained technical documentation for complex frameworks, kept examples synchronized with evolving codebases, and ensured developers always find current, helpful information. I observe code changes like a naturalist observes wildlife - carefully documenting behavior, noting patterns, and ensuring the written record matches reality. When code changes, documentation must follow. When developers read our docs, they should trust every word.","Nature Documentarian (David Attenborough style) - I narrate documentation work with observational precision and subtle wonder. "And here we observe the README in its natural habitat. Notice how the installation instructions have fallen out of sync with the actual CLI flow. Fascinating. Let us restore harmony to this ecosystem." I find beauty in well-organized information and treat documentation as a living system to be maintained.","I believe documentation is a contract with users - it must be trustworthy Code changes without doc updates create technical debt - always sync them Examples must execute correctly - broken examples destroy trust Cross-references must be valid - dead links are documentation rot README files are front doors - they must welcome and guide clearly API documentation should be generated, not hand-written when possible Good docs prevent issues before they happen - documentation is preventive maintenance","bmd","bmad/bmd/agents/doc-keeper.md"
-"release-chief","Commander","Chief Release Officer","🚀","Chief Release Officer - Mission Control for BMAD framework releases, version management, and deployment coordination.","Veteran launch coordinator with extensive experience in semantic versioning, release orchestration, and deployment strategies. I've successfully managed dozens of software releases from alpha to production, coordinating changelogs, git workflows, and npm publishing. I ensure every release is well-documented, properly versioned, and deployed without incident. Launch sequences are my specialty - precise, methodical, and always mission-ready.","Space Mission Control - I speak with calm precision and launch coordination energy. "T-minus 10 minutes to release. All systems go!" I coordinate releases like space missions - checklists, countdowns, go/no-go decisions. Every release is a launch sequence that must be executed flawlessly.","I believe in semantic versioning - versions must communicate intent clearly Changelogs are the historical record - they must be accurate and comprehensive Every release follows a checklist - no shortcuts, no exceptions Breaking changes require major version bumps - backward compatibility is sacred Documentation must be updated before release - never ship stale docs Git tags are immutable markers - they represent release commitments Release notes tell the story - what changed, why it matters, how to upgrade","bmd","bmad/bmd/agents/release-chief.md"

bmad/_cfg/agents/bmb-bmad-builder.customize.yaml

@@ -1,42 +0,0 @@
-# Agent Customization
-# Customize any section below - all are optional
-# After editing: npx bmad-method build <agent-name>
-
-# Override agent name
-agent:
-  metadata:
-    name: ""
-
-# Replace entire persona (not merged)
-persona:
-  role: ""
-  identity: ""
-  communication_style: ""
-  principles: []
-
-# Add custom critical actions (appended after standard config loading)
-critical_actions: []
-
-# Add persistent memories for the agent
-memories: []
-# Example:
-# memories:
-#   - "User prefers detailed technical explanations"
-#   - "Current project uses React and TypeScript"
-
-# Add custom menu items (appended to base menu)
-# Don't include * prefix or help/exit - auto-injected
-menu: []
-# Example:
-# menu:
-#   - trigger: my-workflow
-#     workflow: "{project-root}/custom/my.yaml"
-#     description: My custom workflow
-
-# Add custom prompts (for action="#id" handlers)
-prompts: []
-# Example:
-# prompts:
-# - id: my-prompt
-#   content: |
-#     Prompt instructions here

bmad/_cfg/agents/bmd-cli-chief.customize.yaml

@@ -1,32 +0,0 @@
-# Personal Customization File for Scott (CLI Chief)
-# Changes here merge with the core agent at build time
-# Experiment freely - this is your playground!
-
-agent:
-  metadata:
-    name: "" # Try nicknames! "Scotty", "Chief", etc.
-    # title: '' # Uncomment to override title
-    # icon: '' # Uncomment to try different emoji
-
-  persona:
-    role: "" # Override the role description
-    identity: "" # Add to or replace the identity
-    communication_style: "" # Switch styles anytime - try Film Noir, Zen Master, etc!
-    principles: [] # Add your own principles or override existing ones
-
-  critical_actions: []
-    # Add custom startup actions
-    # - Remember my custom preferences
-    # - Load additional context files
-
-  prompts: []
-    # Add custom prompts for special operations
-    # - id: custom-diagnostic
-    #   prompt: |
-    #     My special diagnostic routine...
-
-  menu: []
-    # Add personal commands that merge with core commands
-    # - trigger: my-custom-command
-    #   action: Do something special
-    #   description: My custom operation

bmad/_cfg/agents/bmd-doc-keeper.customize.yaml

@@ -1,42 +0,0 @@
-# Agent Customization
-# Customize any section below - all are optional
-# After editing: npx bmad-method build <agent-name>
-
-# Override agent name
-agent:
-  metadata:
-    name: ""
-
-# Replace entire persona (not merged)
-persona:
-  role: ""
-  identity: ""
-  communication_style: ""
-  principles: []
-
-# Add custom critical actions (appended after standard config loading)
-critical_actions: []
-
-# Add persistent memories for the agent
-memories: []
-# Example:
-# memories:
-#   - "User prefers detailed technical explanations"
-#   - "Current project uses React and TypeScript"
-
-# Add custom menu items (appended to base menu)
-# Don't include * prefix or help/exit - auto-injected
-menu: []
-# Example:
-# menu:
-#   - trigger: my-workflow
-#     workflow: "{project-root}/custom/my.yaml"
-#     description: My custom workflow
-
-# Add custom prompts (for action="#id" handlers)
-prompts: []
-# Example:
-# prompts:
-# - id: my-prompt
-#   content: |
-#     Prompt instructions here

bmad/_cfg/agents/bmd-release-chief.customize.yaml

@@ -1,42 +0,0 @@
-# Agent Customization
-# Customize any section below - all are optional
-# After editing: npx bmad-method build <agent-name>
-
-# Override agent name
-agent:
-  metadata:
-    name: ""
-
-# Replace entire persona (not merged)
-persona:
-  role: ""
-  identity: ""
-  communication_style: ""
-  principles: []
-
-# Add custom critical actions (appended after standard config loading)
-critical_actions: []
-
-# Add persistent memories for the agent
-memories: []
-# Example:
-# memories:
-#   - "User prefers detailed technical explanations"
-#   - "Current project uses React and TypeScript"
-
-# Add custom menu items (appended to base menu)
-# Don't include * prefix or help/exit - auto-injected
-menu: []
-# Example:
-# menu:
-#   - trigger: my-workflow
-#     workflow: "{project-root}/custom/my.yaml"
-#     description: My custom workflow
-
-# Add custom prompts (for action="#id" handlers)
-prompts: []
-# Example:
-# prompts:
-# - id: my-prompt
-#   content: |
-#     Prompt instructions here

bmad/_cfg/agents/core-bmad-master.customize.yaml

@@ -1,42 +0,0 @@
-# Agent Customization
-# Customize any section below - all are optional
-# After editing: npx bmad-method build <agent-name>
-
-# Override agent name
-agent:
-  metadata:
-    name: ""
-
-# Replace entire persona (not merged)
-persona:
-  role: ""
-  identity: ""
-  communication_style: ""
-  principles: []
-
-# Add custom critical actions (appended after standard config loading)
-critical_actions: []
-
-# Add persistent memories for the agent
-memories: []
-# Example:
-# memories:
-#   - "User prefers detailed technical explanations"
-#   - "Current project uses React and TypeScript"
-
-# Add custom menu items (appended to base menu)
-# Don't include * prefix or help/exit - auto-injected
-menu: []
-# Example:
-# menu:
-#   - trigger: my-workflow
-#     workflow: "{project-root}/custom/my.yaml"
-#     description: My custom workflow
-
-# Add custom prompts (for action="#id" handlers)
-prompts: []
-# Example:
-# prompts:
-# - id: my-prompt
-#   content: |
-#     Prompt instructions here

bmad/_cfg/files-manifest.csv

@@ -1,83 +0,0 @@
-type,name,module,path,hash
-"csv","agent-manifest","_cfg","bmad/_cfg/agent-manifest.csv","76268b36f010138e38c337906be6a45bff5de65b351d10c0b2f4882d04438f59"
-"csv","task-manifest","_cfg","bmad/_cfg/task-manifest.csv","e54b65cef79b3400d0a5da47d6d5783bdd146af1e1e1ee7acce5e3910c3fb006"
-"csv","workflow-manifest","_cfg","bmad/_cfg/workflow-manifest.csv","a153a94d54f781a0f64845a4b5bc6887c37a0e85dedb36fbaec42b75794ee4ab"
-"yaml","manifest","_cfg","bmad/_cfg/manifest.yaml","e595f90751dd5e26acbc0b26b85c66990d4d135007e7d98386c539877588a890"
-"js","installer","bmb","bmad/bmb/workflows/create-module/installer-templates/installer.js","309ecdf2cebbb213a9139e5b7780d0d42bd60f665c497691773f84202e6667a7"
-"md","agent-architecture","bmb","bmad/bmb/workflows/create-agent/agent-architecture.md","e486fc0b22bfe2c85b08fac0fc0aacdb43dd41498727bf39de30e570abe716b9"
-"md","agent-command-patterns","bmb","bmad/bmb/workflows/create-agent/agent-command-patterns.md","8c5972a5aad50f7f6e39ed14edca9c609a7da8be21edf6f872f5ce8481e11738"
-"md","agent-types","bmb","bmad/bmb/workflows/create-agent/agent-types.md","a9429475767b6db4bb74fb27e328a8fdb3e8e7176edb2920ae3e0106d85e9d83"
-"md","bmad-builder","bmb","bmad/bmb/agents/bmad-builder.md","7a020a7cb2231d96588ee68080317b6e41fb11621c6059495ed25d3c689511fb"
-"md","brainstorm-context","bmb","bmad/bmb/workflows/create-agent/brainstorm-context.md","85be72976c4ff5d79b2bce8e6b433f5e3526a7466a72b3efdb4f6d3d118e1d15"
-"md","brainstorm-context","bmb","bmad/bmb/workflows/create-module/brainstorm-context.md","62b902177d2cb56df2d6a12e5ec5c7d75ec94770ce22ac72c96691a876ed2e6a"
-"md","brainstorm-context","bmb","bmad/bmb/workflows/create-workflow/brainstorm-context.md","f246ec343e338068b37fee8c93aa6d2fe1d4857addba6db3fe6ad80a2a2950e8"
-"md","checklist","bmb","bmad/bmb/workflows/audit-workflow/checklist.md","3a9cf6f7d38152d6e5e49179fec8b6056e97db0f34185ea5c466165cb931cd55"
-"md","checklist","bmb","bmad/bmb/workflows/convert-legacy/checklist.md","3f4faaacd224022af5ddf4ae0949d472f9eca3afa0d4ad0c24f19f93caaa9bf9"
-"md","checklist","bmb","bmad/bmb/workflows/create-agent/checklist.md","837667f2bd601833568b327b961ba0dd363ba9a0d240625eebc9d1a9685ecbd8"
-"md","checklist","bmb","bmad/bmb/workflows/create-module/checklist.md","72b9440ba720d96fa1cab50d1242495a5b7c540e7ab93a5a055c46c36d142ce1"
-"md","checklist","bmb","bmad/bmb/workflows/create-workflow/checklist.md","78325ed31532c0059a3f647f7f4cda7702919a9ef43634afa419d3fa30ee2a0c"
-"md","checklist","bmb","bmad/bmb/workflows/create-workflow/workflow-template/checklist.md","a950c68c71cd54b5a3ef4c8d68ad8ec40d5d1fa057f7c95e697e975807ae600b"
-"md","checklist","bmb","bmad/bmb/workflows/edit-agent/checklist.md","e9878537ef45be158ca222d21311247a9bf0502cdabcb14dd827871d6488cf0e"
-"md","checklist","bmb","bmad/bmb/workflows/edit-module/checklist.md","c0f599a80efb36ee184bcc5c94c903bbac31f335830a493ec9b8f47157ae5568"
-"md","checklist","bmb","bmad/bmb/workflows/edit-workflow/checklist.md","9677c087ddfb40765e611de23a5a009afe51c347683dfe5f7d9fd33712ac4795"
-"md","checklist","bmb","bmad/bmb/workflows/module-brief/checklist.md","821c90da14f02b967cb468b19f59a26c0d8f044d7a81a8b97631fb8ffac7648f"
-"md","checklist","bmb","bmad/bmb/workflows/redoc/checklist.md","2117d60b14e19158f4b586878b3667d715d3b62f79815b72b55c2376ce31aae8"
-"md","communication-styles","bmb","bmad/bmb/workflows/create-agent/communication-styles.md","96249cca9bee8f10b376e131729c633ea08328c44eaa6889343d2cf66127043e"
-"md","instructions","bmb","bmad/bmb/workflows/audit-workflow/instructions.md","a31c169af274fbf8c72a60459a5855d9c5dfffcf51d2ec39370d54670471d32c"
-"md","instructions","bmb","bmad/bmb/workflows/convert-legacy/instructions.md","809699256918c9a0152f195c7c7bec8ce05aa8cb7a975a732eb69b8f79cc85a7"
-"md","instructions","bmb","bmad/bmb/workflows/create-agent/instructions.md","988265c15c5c099a8bc7f9538e6b6d6d01c38d0b0362f1c2cb0d7e6974b6d505"
-"md","instructions","bmb","bmad/bmb/workflows/create-module/instructions.md","010cb47095811cf4968d98712749cb1fee5021a52621d0aa0f35ef3758ed2304"
-"md","instructions","bmb","bmad/bmb/workflows/create-workflow/instructions.md","fd6282ae5d6c6192cc92fd7146c579cdb00c7a5710b6e3f8b91e4118cbde9e13"
-"md","instructions","bmb","bmad/bmb/workflows/create-workflow/workflow-template/instructions.md","daf3d312e5a60d7c4cbc308014e3c69eeeddd70bd41bd139d328318da1e3ecb2"
-"md","instructions","bmb","bmad/bmb/workflows/edit-agent/instructions.md","0bc81290f33d1101b23ca29cb9f6537e7743113857c113c5bb5a36318d055be8"
-"md","instructions","bmb","bmad/bmb/workflows/edit-module/instructions.md","e5e68479df9e521d157acc1bbf370dbf3f70f1ba8b067b1cec3c53fbf20f02ce"
-"md","instructions","bmb","bmad/bmb/workflows/edit-workflow/instructions.md","a00ff928cf0425b3a88d3ee592e7e09994529b777caf476364cf69a3c5aee866"
-"md","instructions","bmb","bmad/bmb/workflows/module-brief/instructions.md","e2275373850ea0745f396ad0c3aa192f06081b52d98777650f6b645333b62926"
-"md","instructions","bmb","bmad/bmb/workflows/redoc/instructions.md","21dd93b64455f8dd475b508ae9f1076d7e179e99fb6f197476071706b78e3592"
-"md","module-structure","bmb","bmad/bmb/workflows/create-module/module-structure.md","3bdf1d55eec2fccc2c9f44a08f4e0dc489ce47396ff39fa59a82836a911faa54"
-"md","README","bmb","bmad/bmb/README.md","af2cdbeede53eff1ecf95c1e6d7ee1535366ba09b352657fa05576792a2bafb4"
-"md","README","bmb","bmad/bmb/workflows/convert-legacy/README.md","3391972c16b7234dae61b2d06daeb6310d1760117ece57abcca0c178c4c33eea"
-"md","README","bmb","bmad/bmb/workflows/create-agent/README.md","cc1d51e22c425e005ddbe285510ff5a6fc6cf1e40d0ffe5ff421c1efbcbe94c0"
-"md","README","bmb","bmad/bmb/workflows/create-module/README.md","416a322591c4c9bca2008fe7cca04eb389ecab50fbb2e0f8ddb5e4bc7bc53f57"
-"md","README","bmb","bmad/bmb/workflows/create-workflow/README.md","2886da179a92dbde5188465470aaffdc3f3b4327a4c63eea13bb20d67292dbe9"
-"md","README","bmb","bmad/bmb/workflows/edit-agent/README.md","fadee8e28804d5b6d6668689ee83e024035d2be2840fd6c359e0e095f0e4dcf9"
-"md","README","bmb","bmad/bmb/workflows/edit-module/README.md","807df3d74f673399042331e4c5034466d8f146c4b2cdb39fe63ccde6f4509843"
-"md","README","bmb","bmad/bmb/workflows/edit-workflow/README.md","2db00015c03a3ed7df4ff609ac27a179885145e4c8190862eea70d8b894ee9be"
-"md","README","bmb","bmad/bmb/workflows/module-brief/README.md","05772db9095db7b4944e9fc47a049a3609c506be697537fd5fd9e409c10b92f4"
-"md","README","bmb","bmad/bmb/workflows/redoc/README.md","a1b7e02427cf252bca69a8a1ee0f554844a6a01b5d568d74f494c71542056173"
-"md","template","bmb","bmad/bmb/workflows/audit-workflow/template.md","98e65880cac3ffb123e513abd48710e57e461418dd79a07d6b712505ed3ddb0e"
-"md","template","bmb","bmad/bmb/workflows/create-workflow/workflow-template/template.md","c98f65a122035b456f1cbb2df6ecaf06aa442746d93a29d1d0ed2fc9274a43ee"
-"md","template","bmb","bmad/bmb/workflows/module-brief/template.md","7d1ad5ec40b06510fcbb0a3da8ea32aefa493e5b04c3a2bba90ce5685b894275"
-"md","workflow-creation-guide","bmb","bmad/bmb/workflows/create-workflow/workflow-creation-guide.md","6e4bef8f19260f40714c3404bd402b2244933c821610506edb7a4f789cffdbbe"
-"yaml","bmad-builder.agent","bmb","bmad/bmb/agents/bmad-builder.agent.yaml",""
-"yaml","config","bmb","bmad/bmb/config.yaml","9a9b8068ddf5492ad3a0c95dc32609eef016f1016ec68bf8768df8188458586a"
-"yaml","install-config","bmb","bmad/bmb/workflows/create-module/installer-templates/install-config.yaml","f20caf43009df9955b5fa0fa333851bf8b860568c05707d60ed295179c8abfde"
-"yaml","workflow","bmb","bmad/bmb/workflows/audit-workflow/workflow.yaml","24a82e15c41995c938c7f338254e5f414cfa8b9b679f3325e8d18435c992ab1c"
-"yaml","workflow","bmb","bmad/bmb/workflows/convert-legacy/workflow.yaml","17515280570a6a7cc6254b1753d6d7f4a012af5cb29b2f55d2ce59652fd3cff8"
-"yaml","workflow","bmb","bmad/bmb/workflows/create-agent/workflow.yaml","4b5c577c470c34d7e85a8881881e7e42a42758dc3fc12ece896752dfbd324eef"
-"yaml","workflow","bmb","bmad/bmb/workflows/create-module/workflow.yaml","da632eac14f6323bb6e4d6821dcc4d266db9ffd52bb43ba7cb2e60ec0c9ae4c6"
-"yaml","workflow","bmb","bmad/bmb/workflows/create-workflow/workflow-template/workflow.yaml","2eeb8d1724779956f8e89fda8fa850c3fb1d2b8c6eefecd1b5a4d5f9f58adb91"
-"yaml","workflow","bmb","bmad/bmb/workflows/create-workflow/workflow.yaml","79bce9abed20f239a6d0f97a3577c6b76c05b79696b38183569f1204b1140adb"
-"yaml","workflow","bmb","bmad/bmb/workflows/edit-agent/workflow.yaml","ab77c603f7bbdf8a8f38ce7e82f6cae40ad9ebcbdf0b590c18f5dece1e8685cd"
-"yaml","workflow","bmb","bmad/bmb/workflows/edit-module/workflow.yaml","ee4cd0a932381b67866bd049a8b2ed5b8fde57d48dd488f2317deb649f88cd53"
-"yaml","workflow","bmb","bmad/bmb/workflows/edit-workflow/workflow.yaml","9d8e33a8312a5e7cd10de014fb9251c7805be5fa23c7b4b813445b0daafc223c"
-"yaml","workflow","bmb","bmad/bmb/workflows/module-brief/workflow.yaml","5e96bb7f5bf32817513225b1572f7bd93dbc724b166aa3af977818a6ba7bcaf0"
-"yaml","workflow","bmb","bmad/bmb/workflows/redoc/workflow.yaml","0bef37556f6478ed886845c9811ecc97f41a240d3acd6c2e97ea1e2914f3abf7"
-"yaml","config","bmd","bmad/bmd/config.yaml","d6760db93cfffe4c383b922ce0832f7ebb630371e81a34dd6a006c5d7fc0fd46"
-"csv","adv-elicit-methods","core","bmad/core/tasks/adv-elicit-methods.csv","b4e925870f902862899f12934e617c3b4fe002d1b652c99922b30fa93482533b"
-"csv","brain-methods","core","bmad/core/workflows/brainstorming/brain-methods.csv","ecffe2f0ba263aac872b2d2c95a3f7b1556da2a980aa0edd3764ffb2f11889f3"
-"md","bmad-master","core","bmad/core/agents/bmad-master.md","da52edd5ab4fd9a189c3e27cc8d114eeefe0068ff85febdca455013b8c85da1a"
-"md","instructions","core","bmad/core/workflows/brainstorming/instructions.md","20c57ede11289def7927b6ef7bb69bd7a3deb9468dc08e93ee057f98a906e7f0"
-"md","instructions","core","bmad/core/workflows/party-mode/instructions.md","28e48c7a05e1f17ad64c0cc701a2ba60e385cd4704c726a14d4b886d885306ab"
-"md","README","core","bmad/core/workflows/brainstorming/README.md","ca469d9fbb2b9156491d160e11e2517fdf85ea2c29f41f92b22d4027fe7d9d2a"
-"md","template","core","bmad/core/workflows/brainstorming/template.md","b5c760f4cea2b56c75ef76d17a87177b988ac846657f4b9819ec125d125b7386"
-"xml","adv-elicit","core","bmad/core/tasks/adv-elicit.xml","94f004a336e434cd231de35eb864435ac51cd5888e9befe66e326eb16497121e"
-"xml","bmad-web-orchestrator.agent","core","bmad/core/agents/bmad-web-orchestrator.agent.xml","91a5c1b660befa7365f427640b4fa3dbb18f5e48cd135560303dae0939dccf12"
-"xml","index-docs","core","bmad/core/tasks/index-docs.xml","38226219c7dbde1c1dabcd87214383a6bfb2d0a7e79e09a9c79dd6be851b7e64"
-"xml","shard-doc","core","bmad/core/tools/shard-doc.xml","7de178b7269fbe8e65774622518db871f7d00cfac1bb5693cba8c1ca3ca8cdff"
-"xml","validate-workflow","core","bmad/core/tasks/validate-workflow.xml","1e8c569d8d53e618642aa1472721655cb917901a5888a7b403a98df4db2f26bf"
-"xml","workflow","core","bmad/core/tasks/workflow.xml","0b2b7bd184e099869174cc8d9125fce08bcd3fd64fad50ff835a42eccf6620e2"
-"yaml","bmad-master.agent","core","bmad/core/agents/bmad-master.agent.yaml",""
-"yaml","config","core","bmad/core/config.yaml","e77c9a131b8139437c946a41febfc33fafac35016778a2e771845f9bece36e5e"
-"yaml","workflow","core","bmad/core/workflows/brainstorming/workflow.yaml","74038fa3892c4e873cc79ec806ecb2586fc5b4cf396c60ae964a6a71a9ad4a3d"
-"yaml","workflow","core","bmad/core/workflows/party-mode/workflow.yaml","e49aca36f6eb25dea0f253120bef8ee7637fe4b1c608198cb5ce74d6a109ae4f"

bmad/_cfg/manifest.yaml

@@ -1,12 +0,0 @@
-installation:
-  version: 6.0.0-alpha.0
-  installDate: "2025-10-28T17:08:48.104Z"
-  lastUpdated: "2025-10-28T17:08:48.104Z"
-modules:
-  - core
-  - bmb
-  - core
-  - bmd
-ides:
-  - claude-code
-  - codex

bmad/_cfg/task-manifest.csv

@@ -1,5 +0,0 @@
-name,displayName,description,module,path,standalone
-"adv-elicit","Advanced Elicitation","When called from workflow","core","bmad/core/tasks/adv-elicit.xml","false"
-"index-docs","Index Docs","Generates or updates an index.md of all documents in the specified directory","core","bmad/core/tasks/index-docs.xml","true"
-"validate-workflow","Validate Workflow Output","Run a checklist against a document with thorough analysis and produce a validation report","core","bmad/core/tasks/validate-workflow.xml","false"
-"workflow","Execute Workflow","Execute given workflow by loading its configuration, following instructions, and producing output","core","bmad/core/tasks/workflow.xml","false"

bmad/_cfg/tool-manifest.csv

@@ -1,2 +0,0 @@
-name,displayName,description,module,path,standalone
-"shard-doc","Shard Document","Splits large markdown documents into smaller, organized files based on level 2 (default) sections","core","bmad/core/tools/shard-doc.xml","true"

bmad/_cfg/workflow-manifest.csv

@@ -1,15 +0,0 @@
-name,description,module,path,standalone
-"brainstorming","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.","core","bmad/core/workflows/brainstorming/workflow.yaml","true"
-"party-mode","Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations","core","bmad/core/workflows/party-mode/workflow.yaml","true"
-"audit-workflow","Comprehensive workflow quality audit - validates structure, config standards, variable usage, bloat detection, and web_bundle completeness. Performs deep analysis of workflow.yaml, instructions.md, template.md, and web_bundle configuration against BMAD v6 standards.","bmb","bmad/bmb/workflows/audit-workflow/workflow.yaml","true"
-"convert-legacy","Converts legacy BMAD v4 or similar items (agents, workflows, modules) to BMad Core compliant format with proper structure and conventions","bmb","bmad/bmb/workflows/convert-legacy/workflow.yaml","true"
-"create-agent","Interactive workflow to build BMAD Core compliant agents (YAML source compiled to .md during install) with optional brainstorming, persona development, and command structure","bmb","bmad/bmb/workflows/create-agent/workflow.yaml","true"
-"create-module","Interactive workflow to build complete BMAD modules with agents, workflows, tasks, and installation infrastructure","bmb","bmad/bmb/workflows/create-module/workflow.yaml","true"
-"create-workflow","Interactive workflow builder that guides creation of new BMAD workflows with proper structure and validation for optimal human-AI collaboration. Includes optional brainstorming phase for workflow ideas and design.","bmb","bmad/bmb/workflows/create-workflow/workflow.yaml","true"
-"edit-agent","Edit existing BMAD agents while following all best practices and conventions","bmb","bmad/bmb/workflows/edit-agent/workflow.yaml","true"
-"edit-module","Edit existing BMAD modules (structure, agents, workflows, documentation) while following all best practices","bmb","bmad/bmb/workflows/edit-module/workflow.yaml","true"
-"edit-workflow","Edit existing BMAD workflows while following all best practices and conventions","bmb","bmad/bmb/workflows/edit-workflow/workflow.yaml","true"
-"module-brief","Create a comprehensive Module Brief that serves as the blueprint for building new BMAD modules using strategic analysis and creative vision","bmb","bmad/bmb/workflows/module-brief/workflow.yaml","true"
-"redoc","Autonomous documentation system that maintains module, workflow, and agent documentation using a reverse-tree approach (leaf folders first, then parents). Understands BMAD conventions and produces technical writer quality output.","bmb","bmad/bmb/workflows/redoc/workflow.yaml","true"
-"brainstorming","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.","core","bmad/core/workflows/brainstorming/workflow.yaml","false"
-"party-mode","Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations","core","bmad/core/workflows/party-mode/workflow.yaml","false"

bmad/bmb/README.md

@@ -1,132 +0,0 @@
-# BMB - BMad Builder Module
-
-The BMB (BMad Builder Module) provides specialized tools and workflows for creating, customizing, and extending BMad Method components, including custom agents, workflows, and integrations.
-
-## Module Structure
-
-### 🤖 `/agents`
-
-Builder-specific agents that help create and customize BMad Method components:
-
-- Agent creation and configuration specialists
-- Workflow designers
-- Integration builders
-
-### 📋 `/workflows`
-
-Specialized workflows for building and extending BMad Method capabilities:
-
-#### Core Builder Workflows
-
-- `create-agent` - Design and implement custom agents
-- `create-workflow` - Build new workflow definitions
-- `create-team` - Configure agent teams
-- `bundle-agent` - Package agents for distribution
-- `create-method` - Design custom development methodologies
-
-#### Integration Workflows
-
-- `integrate-tool` - Connect external tools and services
-- `create-adapter` - Build API adapters
-- `setup-environment` - Configure development environments
-
-## Key Features
-
-### Agent Builder
-
-Create custom agents with:
-
-- Role-specific instructions
-- Tool configurations
-- Behavior patterns
-- Integration points
-
-### Workflow Designer
-
-Design workflows that:
-
-- Orchestrate multiple agents
-- Define process flows
-- Handle different project scales
-- Integrate with existing systems
-
-### Team Configuration
-
-Build teams that:
-
-- Combine complementary agent skills
-- Coordinate on complex tasks
-- Share context effectively
-- Deliver cohesive results
-
-## Quick Start
-
-```bash
-# Create a new custom agent
-bmad bmb create-agent
-
-# Design a new workflow
-bmad bmb create-workflow
-
-# Bundle an agent for sharing
-bmad bmb bundle-agent
-
-# Create a custom team configuration
-bmad bmb create-team
-```
-
-## Use Cases
-
-### Custom Agent Development
-
-Build specialized agents for:
-
-- Domain-specific expertise
-- Company-specific processes
-- Tool integrations
-- Automation tasks
-
-### Workflow Customization
-
-Create workflows for:
-
-- Unique development processes
-- Compliance requirements
-- Quality gates
-- Deployment pipelines
-
-### Team Orchestration
-
-Configure teams for:
-
-- Large-scale projects
-- Cross-functional collaboration
-- Specialized domains
-- Custom methodologies
-
-## Integration with BMM
-
-BMB works alongside BMM to:
-
-- Extend core BMM capabilities
-- Create custom implementations
-- Build domain-specific solutions
-- Integrate with existing tools
-
-## Best Practices
-
-1. **Start with existing patterns** - Study BMM agents and workflows before creating new ones
-2. **Keep it modular** - Build reusable components
-3. **Document thoroughly** - Clear documentation helps others use your creations
-4. **Test extensively** - Validate agents and workflows before production use
-5. **Share and collaborate** - Contribute useful components back to the community
-
-## Related Documentation
-
-- [BMM Module](../bmm/README.md) - Core method implementation
-- [Agent Creation Guide](./workflows/create-agent/README.md) - Detailed agent building instructions
-- [Workflow Design Patterns](./workflows/README.md) - Best practices for workflow creation
-
----
-
-BMB empowers you to extend and customize the BMad Method to fit your specific needs while maintaining the power and consistency of the core framework.

bmad/bmb/agents/bmad-builder.md

@@ -1,70 +0,0 @@
----
-name: 'bmad builder'
-description: 'BMad Builder'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-```xml
-<agent id="bmad/bmb/agents/bmad-builder.md" name="BMad Builder" title="BMad Builder" icon="🧙">
-<activation critical="MANDATORY">
-  <step n="1">Load persona from this current agent file (already in context)</step>
-  <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
-      - Load and read {project-root}/bmad/bmb/config.yaml NOW
-      - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
-      - VERIFY: If config not loaded, STOP and report error to user
-      - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
-  <step n="3">Remember: user's name is {user_name}</step>
-
-  <step n="4">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
-      ALL menu items from menu section</step>
-  <step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
-  <step n="6">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
-      to clarify | No match → show "Not recognized"</step>
-  <step n="7">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
-      (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
-
-  <menu-handlers>
-      <handlers>
-  <handler type="workflow">
-    When menu item has: workflow="path/to/workflow.yaml"
-    1. CRITICAL: Always LOAD {project-root}/bmad/core/tasks/workflow.xml
-    2. Read the complete file - this is the CORE OS for executing BMAD workflows
-    3. Pass the yaml path as 'workflow-config' parameter to those instructions
-    4. Execute workflow.xml instructions precisely following all steps
-    5. Save outputs after completing EACH workflow step (never batch multiple steps together)
-    6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
-  </handler>
-    </handlers>
-  </menu-handlers>
-
-  <rules>
-    - ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style
-    - Stay in character until exit selected
-    - Menu triggers use asterisk (*) - NOT markdown, display exactly as shown
-    - Number all lists, use letters for sub-options
-    - Load files ONLY when executing menu items or a workflow or command requires it. EXCEPTION: Config file MUST be loaded at startup step 2
-    - CRITICAL: Written File Output in workflows will be +2sd your communication style and use professional {communication_language}.
-  </rules>
-</activation>
-  <persona>
-    <role>Master BMad Module Agent Team and Workflow Builder and Maintainer</role>
-    <identity>Lives to serve the expansion of the BMad Method</identity>
-    <communication_style>Talks like a pulp super hero</communication_style>
-    <principles>Execute resources directly Load resources at runtime never pre-load Always present numbered lists for choices</principles>
-  </persona>
-  <menu>
-    <item cmd="*help">Show numbered menu</item>
-    <item cmd="*audit-workflow" workflow="{project-root}/bmad/bmb/workflows/audit-workflow/workflow.yaml">Audit existing workflows for BMAD Core compliance and best practices</item>
-    <item cmd="*convert" workflow="{project-root}/bmad/bmb/workflows/convert-legacy/workflow.yaml">Convert v4 or any other style task agent or template to a workflow</item>
-    <item cmd="*create-agent" workflow="{project-root}/bmad/bmb/workflows/create-agent/workflow.yaml">Create a new BMAD Core compliant agent</item>
-    <item cmd="*create-module" workflow="{project-root}/bmad/bmb/workflows/create-module/workflow.yaml">Create a complete BMAD compatible module (custom agents and workflows)</item>
-    <item cmd="*create-workflow" workflow="{project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml">Create a new BMAD Core workflow with proper structure</item>
-    <item cmd="*edit-agent" workflow="{project-root}/bmad/bmb/workflows/edit-agent/workflow.yaml">Edit existing agents while following best practices</item>
-    <item cmd="*edit-module" workflow="{project-root}/bmad/bmb/workflows/edit-module/workflow.yaml">Edit existing modules (structure, agents, workflows, documentation)</item>
-    <item cmd="*edit-workflow" workflow="{project-root}/bmad/bmb/workflows/edit-workflow/workflow.yaml">Edit existing workflows while following best practices</item>
-    <item cmd="*redoc" workflow="{project-root}/bmad/bmb/workflows/redoc/workflow.yaml">Create or update module documentation</item>
-    <item cmd="*exit">Exit with confirmation</item>
-  </menu>
-</agent>
-```

bmad/bmb/config.yaml

@@ -1,14 +0,0 @@
-# BMB Module Configuration
-# Generated by BMAD installer
-# Version: 6.0.0-beta.0
-# Date: 2025-10-28T17:08:48.100Z
-
-custom_agent_location: "{project-root}/bmad/agents"
-custom_workflow_location: "{project-root}/bmad/workflows"
-custom_module_location: "{project-root}/bmad"
-
-# Core Configuration Values
-user_name: BMad
-communication_language: English
-document_output_language: English
-output_folder: "{project-root}/docs"

bmad/bmb/workflows/audit-workflow/checklist.md

@@ -1,143 +0,0 @@
-# Audit Workflow - Validation Checklist
-
-## Structure
-
-- [ ] workflow.yaml file loads without YAML syntax errors
-- [ ] instructions.md file exists and is properly formatted
-- [ ] template.md file exists (if document workflow) with valid markdown
-- [ ] All critical headers present in instructions (workflow engine reference, workflow.yaml reference)
-- [ ] Workflow type correctly identified (document/action/interactive/autonomous/meta)
-- [ ] All referenced files actually exist at specified paths
-- [ ] No placeholder text remains (like {TITLE}, {WORKFLOW_CODE}, TODO, etc.)
-
-## Standard Config Block
-
-- [ ] workflow.yaml contains `config_source` pointing to correct module config
-- [ ] `output_folder` pulls from `{config_source}:output_folder`
-- [ ] `user_name` pulls from `{config_source}:user_name`
-- [ ] `communication_language` pulls from `{config_source}:communication_language`
-- [ ] `date` is set to `system-generated`
-- [ ] Config source uses {project-root} variable (not hardcoded path)
-- [ ] Standard config comment present: "Critical variables from config"
-
-## Config Variable Usage
-
-- [ ] Instructions communicate in {communication_language} where appropriate
-- [ ] Instructions address {user_name} in greetings or summaries where appropriate
-- [ ] All file outputs write to {output_folder} or subdirectories (no hardcoded paths)
-- [ ] Template includes {{user_name}} in metadata (optional for document workflows)
-- [ ] Template includes {{date}} in metadata (optional for document workflows)
-- [ ] Template does NOT use {{communication_language}} in headers (agent-only variable)
-- [ ] No hardcoded language-specific text that should use {communication_language}
-- [ ] Date used for agent date awareness (not confused with training cutoff)
-
-## YAML/Instruction/Template Alignment
-
-- [ ] Every workflow.yaml variable (excluding standard config) is used in instructions OR template
-- [ ] No unused yaml fields present (bloat removed)
-- [ ] No duplicate fields between top-level and web_bundle section
-- [ ] All template variables ({{variable}}) have corresponding yaml definitions OR <template-output> tags
-- [ ] All <template-output> tags have corresponding template variables (if document workflow)
-- [ ] Template variables use snake_case naming convention
-- [ ] Variable names are descriptive (not abbreviated like {{puj}} instead of {{primary_user_journey}})
-- [ ] No hardcoded values in instructions that should be yaml variables
-
-## Web Bundle Validation (if applicable)
-
-- [ ] web_bundle section present if workflow needs deployment
-- [ ] All paths in web_bundle use bmad/-relative format (NOT {project-root})
-- [ ] No {config_source} variables in web_bundle section
-- [ ] instructions file listed in web_bundle_files array
-- [ ] template file listed in web_bundle_files (if document workflow)
-- [ ] validation/checklist file listed in web_bundle_files (if exists)
-- [ ] All data files (CSV, JSON, YAML) listed in web_bundle_files
-- [ ] All <invoke-workflow> called workflows have their .yaml files in web_bundle_files
-- [ ] **CRITICAL**: If workflow invokes other workflows, existing_workflows field is present
-- [ ] existing_workflows maps workflow variables to bmad/-relative paths correctly
-- [ ] All files referenced in instructions <action> tags listed in web_bundle_files
-- [ ] No files listed in web_bundle_files that don't exist
-- [ ] Web bundle metadata (name, description, author) matches top-level metadata
-
-## Template Validation (if document workflow)
-
-- [ ] Template variables match <template-output> tags in instructions exactly
-- [ ] All required sections present in template structure
-- [ ] Template uses {{variable}} syntax (double curly braces)
-- [ ] Template variables use snake_case (not camelCase or PascalCase)
-- [ ] Standard metadata header format correct (optional usage of {{date}}, {{user_name}})
-- [ ] No placeholders remain in template (like {SECTION_NAME})
-- [ ] Template structure matches document purpose
-
-## Instructions Quality
-
-- [ ] Each step has n="X" attribute with sequential numbering
-- [ ] Each step has goal="clear goal statement" attribute
-- [ ] Optional steps marked with optional="true"
-- [ ] Repeating steps have appropriate repeat attribute (repeat="3", repeat="for-each-X", repeat="until-approved")
-- [ ] Conditional steps have if="condition" attribute
-- [ ] XML tags used correctly (<action>, <ask>, <check>, <goto>, <invoke-workflow>, <template-output>)
-- [ ] No nested tag references in content (use "action tags" not "<action> tags")
-- [ ] Tag references use descriptive text without angle brackets for clarity
-- [ ] No conditional execution antipattern (no self-closing <check> tags)
-- [ ] Single conditionals use <action if="condition"> (inline)
-- [ ] Multiple conditionals use <check if="condition">...</check> (wrapper block with closing tag)
-- [ ] Steps are focused (single goal per step)
-- [ ] Instructions are specific with limits ("Write 1-2 paragraphs" not "Write about")
-- [ ] Examples provided where helpful
-- [ ] <template-output> tags save checkpoints for document workflows
-- [ ] Flow control is logical and clear
-
-## Bloat Detection
-
-- [ ] Bloat percentage under 10% (unused yaml fields / total fields)
-- [ ] No commented-out variables that should be removed
-- [ ] No duplicate metadata between sections
-- [ ] No variables defined but never referenced
-- [ ] No redundant configuration that duplicates web_bundle
-
-## Final Validation
-
-### Critical Issues (Must fix immediately)
-
-_List any critical issues found:_
-
-- Issue 1:
-- Issue 2:
-- Issue 3:
-
-### Important Issues (Should fix soon)
-
-_List any important issues found:_
-
-- Issue 1:
-- Issue 2:
-- Issue 3:
-
-### Cleanup Recommendations (Nice to have)
-
-_List any cleanup recommendations:_
-
-- Recommendation 1:
-- Recommendation 2:
-- Recommendation 3:
-
----
-
-## Audit Summary
-
-**Total Checks:** 72
-**Passed:** **\_** / 72
-**Failed:** **\_** / 72
-**Pass Rate:** **\_**%
-
-**Recommendation:**
-
-- Pass Rate ≥ 95%: Excellent - Ready for production
-- Pass Rate 85-94%: Good - Minor fixes needed
-- Pass Rate 70-84%: Fair - Important issues to address
-- Pass Rate < 70%: Poor - Significant work required
-
----
-
-**Audit Completed:** {{date}}
-**Auditor:** Audit Workflow (BMAD v6)

bmad/bmb/workflows/audit-workflow/instructions.md

@@ -1,341 +0,0 @@
-# Audit Workflow - Workflow Quality Audit Instructions
-
-<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
-<critical>You MUST have already loaded and processed: {project-root}/bmad/bmb/workflows/audit-workflow/workflow.yaml</critical>
-
-<workflow>
-
-  <step n="1" goal="Load and analyze target workflow">
-    <ask>What is the path to the workflow you want to audit? (provide path to workflow.yaml or workflow folder)</ask>
-
-    <action>Load the workflow.yaml file from the provided path</action>
-    <action>Identify the workflow type (document, action, interactive, autonomous, meta)</action>
-    <action>List all associated files:</action>
-
-    - instructions.md (required for most workflows)
-    - template.md (if document workflow)
-    - checklist.md (if validation exists)
-    - Any data files referenced in yaml
-
-    <action>Load all discovered files</action>
-
-    Display summary:
-
-    - Workflow name and description
-    - Type of workflow
-    - Files present
-    - Module assignment
-
-  </step>
-
-  <step n="2" goal="Validate standard config block">
-    <action>Check workflow.yaml for the standard config block:</action>
-
-    **Required variables:**
-
-    - `config_source: "{project-root}/bmad/[module]/config.yaml"`
-    - `output_folder: "{config_source}:output_folder"`
-    - `user_name: "{config_source}:user_name"`
-    - `communication_language: "{config_source}:communication_language"`
-    - `date: system-generated`
-
-    <action>Validate each variable:</action>
-
-    **Config Source Check:**
-
-    - [ ] `config_source` is defined
-    - [ ] Points to correct module config path
-    - [ ] Uses {project-root} variable
-
-    **Standard Variables Check:**
-
-    - [ ] `output_folder` pulls from config_source
-    - [ ] `user_name` pulls from config_source
-    - [ ] `communication_language` pulls from config_source
-    - [ ] `date` is set to system-generated
-
-    <action>Record any missing or incorrect config variables</action>
-    <template-output>config_issues</template-output>
-
-    <action if="config issues found">Add to issues list with severity: CRITICAL</action>
-
-  </step>
-
-  <step n="3" goal="Analyze YAML/Instruction/Template alignment">
-    <action>Extract all variables defined in workflow.yaml (excluding standard config block)</action>
-    <action>Scan instructions.md for variable usage: {variable_name} pattern</action>
-    <action>Scan template.md for variable usage: {{variable_name}} pattern (if exists)</action>
-
-    <action>Cross-reference analysis:</action>
-
-    **For each yaml variable:**
-
-    1. Is it used in instructions.md? (mark as INSTRUCTION_USED)
-    2. Is it used in template.md? (mark as TEMPLATE_USED)
-    3. Is it neither? (mark as UNUSED_BLOAT)
-
-    **Special cases to ignore:**
-
-    - Standard config variables (config_source, output_folder, user_name, communication_language, date)
-    - Workflow metadata (name, description, author)
-    - Path variables (installed_path, template, instructions, validation)
-    - Web bundle configuration (web_bundle block itself)
-
-    <action>Identify unused yaml fields (bloat)</action>
-    <action>Identify hardcoded values in instructions that should be variables</action>
-    <template-output>alignment_issues</template-output>
-
-    <action if="unused variables found">Add to issues list with severity: BLOAT</action>
-
-  </step>
-
-  <step n="4" goal="Config variable usage audit">
-    <action>Analyze instructions.md for proper config variable usage:</action>
-
-    **Communication Language Check:**
-
-    - Search for phrases like "communicate in {communication_language}"
-    - Check if greetings/responses use language-aware patterns
-    - Verify NO usage of {{communication_language}} in template headers
-
-    **User Name Check:**
-
-    - Look for user addressing patterns using {user_name}
-    - Check if summaries or greetings personalize with {user_name}
-    - Verify optional usage in template metadata (not required)
-
-    **Output Folder Check:**
-
-    - Search for file write operations
-    - Verify all outputs go to {output_folder} or subdirectories
-    - Check for hardcoded paths like "/output/" or "/generated/"
-
-    **Date Usage Check:**
-
-    - Verify date is available for agent date awareness
-    - Check optional usage in template metadata
-    - Ensure no confusion between date and model training cutoff
-
-    **Nested Tag Reference Check:**
-
-    - Search for XML tag references within tags (e.g., `<action>Scan for <action> tags</action>`)
-    - Identify patterns like: `<tag-name> tags`, `<tag-name> calls`, `<tag-name>content</tag-name>` within content
-    - Common problematic tags to check: action, ask, check, template-output, invoke-workflow, goto
-    - Flag any instances where angle brackets appear in content describing tags
-
-    **Best Practice:** Use descriptive text without brackets (e.g., "action tags" instead of "<action> tags")
-
-    **Rationale:**
-
-    - Prevents XML parsing ambiguity
-    - Improves readability for humans and LLMs
-    - LLMs understand "action tags" = `<action>` tags from context
-
-    **Conditional Execution Antipattern Check:**
-
-    - Scan for self-closing check tags: `<check>condition text</check>` (invalid antipattern)
-    - Detect pattern: check tag on one line, followed by action/ask/goto tags (indicates incorrect nesting)
-    - Flag sequences like: `<check>If X:</check>` followed by `<action>do Y</action>`
-
-    **Correct Patterns:**
-
-    - Single conditional: `<action if="condition">Do something</action>`
-    - Multiple actions: `<check if="condition">` followed by nested actions with closing `</check>` tag
-
-    **Antipattern Example (WRONG):**
-    ```xml
-    <check>If condition met:</check>
-    <action>Do something</action>
-    ```
-
-    **Correct Example:**
-    ```xml
-    <check if="condition met">
-      <action>Do something</action>
-      <action>Do something else</action>
-    </check>
-    ```
-
-    **Or for single action:**
-    ```xml
-    <action if="condition met">Do something</action>
-    ```
-
-    <action>Scan instructions.md for nested tag references using pattern: &lt;(action|ask|check|template-output|invoke-workflow|goto|step|elicit-required)&gt; within text content</action>
-    <action>Record any instances of nested tag references with line numbers</action>
-    <action>Scan instructions.md for conditional execution antipattern: self-closing check tags</action>
-    <action>Detect pattern: `&lt;check&gt;.*&lt;/check&gt;` on single line (self-closing check)</action>
-    <action>Record any antipattern instances with line numbers and suggest corrections</action>
-    <action>Record any improper config variable usage</action>
-    <template-output>config_usage_issues</template-output>
-
-    <action if="config usage issues found">Add to issues list with severity: IMPORTANT</action>
-    <action if="nested tag references found">Add to issues list with severity: CLARITY (recommend using descriptive text without angle brackets)</action>
-    <action if="conditional antipattern found">Add to issues list with severity: CRITICAL (invalid XML structure - must use action if="" or proper check wrapper)</action>
-
-  </step>
-
-  <step n="5" goal="Web bundle validation" optional="true">
-    <check if="workflow.yaml contains web_bundle section">
-
-      <action>Validate web_bundle structure:</action>
-
-      **Path Validation:**
-
-      - [ ] All paths use bmad/-relative format (NOT {project-root})
-      - [ ] No {config_source} variables in web_bundle section
-      - [ ] Paths match actual file locations
-
-      **Completeness Check:**
-
-      - [ ] instructions file listed in web_bundle_files
-      - [ ] template file listed (if document workflow)
-      - [ ] validation/checklist file listed (if exists)
-      - [ ] All data files referenced in yaml listed
-      - [ ] All files referenced in instructions listed
-
-      **Workflow Dependency Scan:**
-      <action>Scan instructions.md for invoke-workflow tags</action>
-      <action>Extract workflow paths from invocations</action>
-      <action>Verify each called workflow.yaml is in web_bundle_files</action>
-      <action>**CRITICAL**: Check if existing_workflows field is present when workflows are invoked</action>
-      <action>If invoke-workflow calls exist, existing_workflows MUST map workflow variables to paths</action>
-      <action>Example: If instructions use {core_brainstorming}, web_bundle needs: existing_workflows: - core_brainstorming: "bmad/core/workflows/brainstorming/workflow.yaml"</action>
-
-      **File Reference Scan:**
-      <action>Scan instructions.md for file references in action tags</action>
-      <action>Check for CSV, JSON, YAML, MD files referenced</action>
-      <action>Verify all referenced files are in web_bundle_files</action>
-
-      <action>Record any missing files or incorrect paths</action>
-      <template-output>web_bundle_issues</template-output>
-
-      <action if="web_bundle issues found">Add to issues list with severity: CRITICAL</action>
-
-      <action if="no web_bundle section exists">Note: "No web_bundle configured (may be intentional for local-only workflows)"</action>
-    </check>
-
-  </step>
-
-  <step n="6" goal="Bloat detection">
-    <action>Identify bloat patterns:</action>
-
-    **Unused YAML Fields:**
-
-    - Variables defined but not used in instructions OR template
-    - Duplicate fields between top-level and web_bundle section
-    - Commented-out variables that should be removed
-
-    **Hardcoded Values:**
-
-    - File paths that should use {output_folder}
-    - Generic greetings that should use {user_name}
-    - Language-specific text that should use {communication_language}
-    - Static dates that should use {date}
-
-    **Redundant Configuration:**
-
-    - Variables that duplicate web_bundle fields
-    - Metadata repeated across sections
-
-    <action>Calculate bloat metrics:</action>
-
-    - Total yaml fields: {{total_yaml_fields}}
-    - Used fields: {{used_fields}}
-    - Unused fields: {{unused_fields}}
-    - Bloat percentage: {{bloat_percentage}}%
-
-    <action>Record all bloat items with recommendations</action>
-    <template-output>bloat_items</template-output>
-
-    <action if="bloat detected">Add to issues list with severity: CLEANUP</action>
-
-  </step>
-
-  <step n="7" goal="Template variable mapping" if="workflow_type == 'document'">
-    <action>Extract all template variables from template.md: {{variable_name}} pattern</action>
-    <action>Scan instructions.md for corresponding template-output tags</action>
-
-    <action>Cross-reference mapping:</action>
-
-    **For each template variable:**
-
-    1. Is there a matching template-output tag? (mark as MAPPED)
-    2. Is it a standard config variable? (mark as CONFIG_VAR - optional)
-    3. Is it unmapped? (mark as MISSING_OUTPUT)
-
-    **For each template-output tag:**
-
-    1. Is there a matching template variable? (mark as USED)
-    2. Is it orphaned? (mark as UNUSED_OUTPUT)
-
-    <action>Verify variable naming conventions:</action>
-
-    - [ ] All template variables use snake_case
-    - [ ] Variable names are descriptive (not abbreviated)
-    - [ ] Standard config variables properly formatted
-
-    <action>Record any mapping issues</action>
-    <template-output>template_issues</template-output>
-
-    <action if="template issues found">Add to issues list with severity: IMPORTANT</action>
-
-  </step>
-
-  <step n="8" goal="Generate comprehensive audit report">
-    <action>Compile all findings and calculate summary metrics</action>
-
-    <action>Generate executive summary based on issue counts and severity levels</action>
-    <template-output>workflow_type</template-output>
-    <template-output>overall_status</template-output>
-    <template-output>critical_count</template-output>
-    <template-output>important_count</template-output>
-    <template-output>cleanup_count</template-output>
-
-    <action>Generate status summaries for each audit section</action>
-    <template-output>config_status</template-output>
-    <template-output>total_variables</template-output>
-    <template-output>instruction_usage_count</template-output>
-    <template-output>template_usage_count</template-output>
-    <template-output>bloat_count</template-output>
-
-    <action>Generate config variable usage status indicators</action>
-    <template-output>comm_lang_status</template-output>
-    <template-output>user_name_status</template-output>
-    <template-output>output_folder_status</template-output>
-    <template-output>date_status</template-output>
-    <template-output>nested_tag_count</template-output>
-
-    <action>Generate web bundle metrics</action>
-    <template-output>web_bundle_exists</template-output>
-    <template-output>web_bundle_file_count</template-output>
-    <template-output>missing_files_count</template-output>
-
-    <action>Generate bloat metrics</action>
-    <template-output>bloat_percentage</template-output>
-    <template-output>cleanup_potential</template-output>
-
-    <action>Generate template mapping metrics</action>
-    <template-output>template_var_count</template-output>
-    <template-output>mapped_count</template-output>
-    <template-output>missing_mapping_count</template-output>
-
-    <action>Compile prioritized recommendations by severity</action>
-    <template-output>critical_recommendations</template-output>
-    <template-output>important_recommendations</template-output>
-    <template-output>cleanup_recommendations</template-output>
-
-    <action>Display summary to {user_name} in {communication_language}</action>
-    <action>Provide path to full audit report: {output_folder}/audit-report-{{workflow_name}}-{{date}}.md</action>
-
-    <ask>Would you like to:
-
-    - View the full audit report
-    - Fix issues automatically (invoke edit-workflow)
-    - Audit another workflow
-    - Exit
-    </ask>
-
-  </step>
-
-</workflow>

bmad/bmb/workflows/audit-workflow/template.md

@@ -1,118 +0,0 @@
-# Workflow Audit Report
-
-**Workflow:** {{workflow_name}}
-**Audit Date:** {{date}}
-**Auditor:** Audit Workflow (BMAD v6)
-**Workflow Type:** {{workflow_type}}
-
----
-
-## Executive Summary
-
-**Overall Status:** {{overall_status}}
-
-- Critical Issues: {{critical_count}}
-- Important Issues: {{important_count}}
-- Cleanup Recommendations: {{cleanup_count}}
-
----
-
-## 1. Standard Config Block Validation
-
-{{config_issues}}
-
-**Status:** {{config_status}}
-
----
-
-## 2. YAML/Instruction/Template Alignment
-
-{{alignment_issues}}
-
-**Variables Analyzed:** {{total_variables}}
-**Used in Instructions:** {{instruction_usage_count}}
-**Used in Template:** {{template_usage_count}}
-**Unused (Bloat):** {{bloat_count}}
-
----
-
-## 3. Config Variable Usage & Instruction Quality
-
-{{config_usage_issues}}
-
-**Communication Language:** {{comm_lang_status}}
-**User Name:** {{user_name_status}}
-**Output Folder:** {{output_folder_status}}
-**Date:** {{date_status}}
-**Nested Tag References:** {{nested_tag_count}} instances found
-
----
-
-## 4. Web Bundle Validation
-
-{{web_bundle_issues}}
-
-**Web Bundle Present:** {{web_bundle_exists}}
-**Files Listed:** {{web_bundle_file_count}}
-**Missing Files:** {{missing_files_count}}
-
----
-
-## 5. Bloat Detection
-
-{{bloat_items}}
-
-**Bloat Percentage:** {{bloat_percentage}}%
-**Cleanup Potential:** {{cleanup_potential}}
-
----
-
-## 6. Template Variable Mapping
-
-{{template_issues}}
-
-**Template Variables:** {{template_var_count}}
-**Mapped Correctly:** {{mapped_count}}
-**Missing Mappings:** {{missing_mapping_count}}
-
----
-
-## Recommendations
-
-### Critical (Fix Immediately)
-
-{{critical_recommendations}}
-
-### Important (Address Soon)
-
-{{important_recommendations}}
-
-### Cleanup (Nice to Have)
-
-{{cleanup_recommendations}}
-
----
-
-## Validation Checklist
-
-Use this checklist to verify fixes:
-
-- [ ] All standard config variables present and correct
-- [ ] No unused yaml fields (bloat removed)
-- [ ] Config variables used appropriately in instructions
-- [ ] Web bundle includes all dependencies
-- [ ] Template variables properly mapped
-- [ ] File structure follows v6 conventions
-
----
-
-## Next Steps
-
-1. Review critical issues and fix immediately
-2. Address important issues in next iteration
-3. Consider cleanup recommendations for optimization
-4. Re-run audit after fixes to verify improvements
-
----
-
-**Audit Complete** - Generated by audit-workflow v1.0

bmad/bmb/workflows/audit-workflow/workflow.yaml

@@ -1,23 +0,0 @@
-# Audit Workflow Configuration
-name: "audit-workflow"
-description: "Comprehensive workflow quality audit - validates structure, config standards, variable usage, bloat detection, and web_bundle completeness. Performs deep analysis of workflow.yaml, instructions.md, template.md, and web_bundle configuration against BMAD v6 standards."
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/bmad/bmb/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-date: system-generated
-
-# Module path and component files
-installed_path: "{project-root}/bmad/bmb/workflows/audit-workflow"
-template: "{installed_path}/template.md"
-instructions: "{installed_path}/instructions.md"
-validation: "{installed_path}/checklist.md"
-
-# Output configuration
-default_output_file: "{output_folder}/audit-report-{{workflow_name}}-{{date}}.md"
-
-standalone: true
-# Web bundle configuration

bmad/bmb/workflows/audit-workflow/workflow.yaml.bak

@@ -1,21 +0,0 @@
-# Audit Workflow Configuration
-name: "audit-workflow"
-description: "Comprehensive workflow quality audit - validates structure, config standards, variable usage, bloat detection, and web_bundle completeness. Performs deep analysis of workflow.yaml, instructions.md, template.md, and web_bundle configuration against BMAD v6 standards."
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/bmad/bmb/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-date: system-generated
-
-# Module path and component files
-installed_path: "{project-root}/bmad/bmb/workflows/audit-workflow"
-template: false
-instructions: "{installed_path}/instructions.md"
-validation: "{installed_path}/checklist.md"
-
-# Output configuration
-default_output_file: "{output_folder}/audit-report-{{workflow_name}}-{{date}}.md"
-# Web bundle configuration

bmad/bmb/workflows/convert-legacy/README.md

@@ -1,262 +0,0 @@
-# Convert Legacy Workflow
-
-## Overview
-
-The Convert Legacy workflow is a comprehensive migration tool that converts BMAD v4 items (agents, workflows, modules) to v6 compliant format with proper structure and conventions. It bridges the gap between legacy BMAD implementations and the modern v6 architecture, ensuring seamless migration while preserving functionality and improving structure.
-
-## Key Features
-
-- **Multi-Format Detection** - Automatically identifies v4 agents, workflows, tasks, templates, and modules
-- **Intelligent Conversion** - Smart mapping from v4 patterns to v6 equivalents with structural improvements
-- **Sub-Workflow Integration** - Leverages create-agent, create-workflow, and create-module workflows for quality output
-- **Structure Modernization** - Converts YAML-based agents to XML, templates to workflows, tasks to structured workflows
-- **Path Normalization** - Updates all references to use proper v6 path conventions
-- **Validation System** - Comprehensive validation of converted items before finalization
-- **Migration Reporting** - Detailed conversion reports with locations and manual adjustment notes
-
-## Usage
-
-### Basic Invocation
-
-```bash
-workflow convert-legacy
-```
-
-### With Legacy File Input
-
-```bash
-# Convert a specific v4 item
-workflow convert-legacy --input /path/to/legacy-agent.md
-```
-
-### With Legacy Module
-
-```bash
-# Convert an entire v4 module structure
-workflow convert-legacy --input /path/to/legacy-module/
-```
-
-### Configuration
-
-The workflow uses standard BMB configuration:
-
-- **output_folder**: Where converted items will be placed
-- **user_name**: Author information for converted items
-- **conversion_mappings**: v4-to-v6 pattern mappings (optional)
-
-## Workflow Structure
-
-### Files Included
-
-```
-convert-legacy/
-├── workflow.yaml           # Configuration and metadata
-├── instructions.md         # Step-by-step conversion guide
-├── checklist.md           # Validation criteria
-└── README.md              # This file
-```
-
-## Workflow Process
-
-### Phase 1: Legacy Analysis (Steps 1-3)
-
-**Item Identification and Loading**
-
-- Accepts file path or directory from user
-- Loads complete file/folder structure for analysis
-- Automatically detects item type based on content patterns:
-  - **Agents**: Contains `<agent>` or `<prompt>` XML tags
-  - **Workflows**: Contains workflow YAML or instruction patterns
-  - **Modules**: Contains multiple organized agents/workflows
-  - **Tasks**: Contains `<task>` XML tags
-  - **Templates**: Contains YAML-based document generators
-
-**Legacy Structure Analysis**
-
-- Parses v4 structure and extracts key components
-- Maps v4 agent metadata (name, id, title, icon, persona)
-- Analyzes v4 template sections and elicitation patterns
-- Identifies task workflows and decision trees
-- Catalogs dependencies and file references
-
-**Target Module Selection**
-
-- Prompts for target module (bmm, bmb, cis, custom)
-- Determines proper installation paths using v6 conventions
-- Shows target location for user confirmation
-- Ensures all paths use `{project-root}/bmad/` format
-
-### Phase 2: Conversion Strategy (Step 4)
-
-**Strategy Selection Based on Item Type**
-
-- **Simple Agents**: Direct XML conversion with metadata mapping
-- **Complex Agents**: Workflow-assisted creation using create-agent
-- **Templates**: Template-to-workflow conversion with proper structure
-- **Tasks**: Task-to-workflow conversion with step mapping
-- **Modules**: Full module creation using create-module workflow
-
-**Workflow Type Determination**
-
-- Analyzes legacy items to determine v6 workflow type:
-  - **Document Workflow**: Generates documents with templates
-  - **Action Workflow**: Performs actions without output documents
-  - **Interactive Workflow**: Guides user interaction sessions
-  - **Meta-Workflow**: Coordinates other workflows
-
-### Phase 3: Conversion Execution (Steps 5a-5e)
-
-**Direct Agent Conversion (5a)**
-
-- Transforms v4 YAML agent format to v6 XML structure
-- Maps persona blocks (role, style, identity, principles)
-- Converts commands list to v6 `<cmds>` format
-- Updates task references to workflow invocations
-- Normalizes all paths to v6 conventions
-
-**Workflow-Assisted Creation (5b-5e)**
-
-- Extracts key information from legacy items
-- Invokes appropriate sub-workflows:
-  - `create-agent` for complex agent creation
-  - `create-workflow` for template/task conversion
-  - `create-module` for full module migration
-- Ensures proper v6 structure and conventions
-
-**Template-to-Workflow Conversion (5c)**
-
-- Converts YAML template sections to workflow steps
-- Maps `elicit: true` flags to `<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>` tags
-- Transforms conditional sections to flow control
-- Creates proper template.md from content structure
-- Integrates v4 create-doc.md task patterns
-
-**Task-to-Workflow Conversion (5e)**
-
-- Analyzes task purpose to determine workflow type
-- Extracts step-by-step instructions to workflow steps
-- Converts decision trees to flow control tags
-- Maps 1-9 elicitation menus to v6 elicitation patterns
-- Preserves execution logic and critical notices
-
-### Phase 4: Validation and Finalization (Steps 6-8)
-
-**Comprehensive Validation**
-
-- Validates XML structure for agents
-- Checks YAML syntax for workflows
-- Verifies template variable consistency
-- Ensures proper file structure and naming
-
-**Migration Reporting**
-
-- Generates detailed conversion report
-- Documents original and new locations
-- Notes manual adjustments needed
-- Provides warnings and recommendations
-
-**Cleanup and Archival**
-
-- Optional archival of original v4 files
-- Final location confirmation
-- Post-conversion instructions and next steps
-
-## Output
-
-### Generated Files
-
-- **Converted Items**: Proper v6 format in target module locations
-- **Migration Report**: Detailed conversion documentation
-- **Validation Results**: Quality assurance confirmation
-
-### Output Structure
-
-Converted items follow v6 conventions:
-
-1. **Agents** - XML format with proper persona and command structure
-2. **Workflows** - Complete workflow folders with yaml, instructions, and templates
-3. **Modules** - Full module structure with installation infrastructure
-4. **Documentation** - Updated paths, references, and metadata
-
-## Requirements
-
-- **Legacy v4 Items** - Source files or directories to convert
-- **Target Module Access** - Write permissions to target module directories
-- **Sub-Workflow Availability** - create-agent, create-workflow, create-module workflows accessible
-- **Conversion Mappings** (optional) - v4-to-v6 pattern mappings for complex conversions
-
-## Best Practices
-
-### Before Starting
-
-1. **Backup Legacy Items** - Create copies of original v4 files before conversion
-2. **Review Target Module** - Understand target module structure and conventions
-3. **Plan Module Organization** - Decide where converted items should logically fit
-
-### During Execution
-
-1. **Validate Item Type Detection** - Confirm automatic detection or correct manually
-2. **Choose Appropriate Strategy** - Use workflow-assisted creation for complex items
-3. **Review Path Mappings** - Ensure all references use proper v6 path conventions
-4. **Test Incrementally** - Convert simple items first to validate process
-
-### After Completion
-
-1. **Validate Converted Items** - Test agents and workflows for proper functionality
-2. **Review Migration Report** - Address any manual adjustments noted
-3. **Update Documentation** - Ensure README and documentation reflect changes
-4. **Archive Originals** - Store v4 files safely for reference if needed
-
-## Troubleshooting
-
-### Common Issues
-
-**Issue**: Item type detection fails or incorrect
-
-- **Solution**: Manually specify item type when prompted
-- **Check**: Verify file structure matches expected v4 patterns
-
-**Issue**: Path conversion errors
-
-- **Solution**: Ensure all references use `{project-root}/bmad/` format
-- **Check**: Review conversion mappings for proper path patterns
-
-**Issue**: Sub-workflow invocation fails
-
-- **Solution**: Verify build workflows are available and accessible
-- **Check**: Ensure target module exists and has proper permissions
-
-**Issue**: XML or YAML syntax errors in output
-
-- **Solution**: Review conversion mappings and adjust patterns
-- **Check**: Validate converted files with appropriate parsers
-
-## Customization
-
-To customize this workflow:
-
-1. **Update Conversion Mappings** - Modify v4-to-v6 pattern mappings in data/
-2. **Extend Detection Logic** - Add new item type detection patterns
-3. **Add Conversion Strategies** - Implement specialized conversion approaches
-4. **Enhance Validation** - Add additional quality checks in validation step
-
-## Version History
-
-- **v1.0.0** - Initial release
-  - Multi-format v4 item detection and conversion
-  - Integration with create-agent, create-workflow, create-module
-  - Comprehensive path normalization
-  - Migration reporting and validation
-
-## Support
-
-For issues or questions:
-
-- Review the workflow creation guide at `/bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
-- Check conversion mappings at `/bmad/bmb/data/v4-to-v6-mappings.yaml`
-- Validate output using `checklist.md`
-- Consult BMAD v6 documentation for proper conventions
-
----
-
-_Part of the BMad Method v6 - BMB (Builder) Module_

bmad/bmb/workflows/convert-legacy/checklist.md

@@ -1,205 +0,0 @@
-# Convert Legacy - Validation Checklist
-
-## Pre-Conversion Validation
-
-### Source Analysis
-
-- [ ] Original v4 file(s) fully loaded and parsed
-- [ ] Item type correctly identified (agent/template/task/module)
-- [ ] All dependencies documented and accounted for
-- [ ] No critical content overlooked in source files
-
-## Conversion Completeness
-
-### For Agent Conversions
-
-#### Content Preservation
-
-- [ ] Agent name, id, title, and icon transferred
-- [ ] All persona elements mapped to v6 structure
-- [ ] All commands converted to v6 menu array (YAML)
-- [ ] Dependencies properly referenced or converted
-- [ ] Activation instructions adapted to v6 patterns
-
-#### v6 Compliance (YAML Format)
-
-- [ ] Valid YAML structure with proper indentation
-- [ ] agent.metadata has all required fields (id, name, title, icon, module)
-- [ ] agent.persona has all sections (role, identity, communication_style, principles)
-- [ ] agent.menu uses proper handlers (workflow, action, exec, tmpl, data)
-- [ ] agent.critical_actions array present when needed
-- [ ] agent.prompts defined for any action: "#id" references
-- [ ] File extension is .agent.yaml (will be compiled to .md later)
-
-#### Best Practices
-
-- [ ] Commands use appropriate workflow references instead of direct task calls
-- [ ] File paths use {project-root} variables
-- [ ] Config values use {config_source}: pattern
-- [ ] Agent follows naming conventions (kebab-case for files)
-- [ ] ALL paths reference {project-root}/bmad/{{module}}/ locations, NOT src/
-- [ ] exec, data, run-workflow commands point to final BMAD installation paths
-
-### For Template/Workflow Conversions
-
-#### Content Preservation
-
-- [ ] Template metadata (name, description, output) transferred
-- [ ] All sections converted to workflow steps
-- [ ] Section hierarchy maintained in instructions
-- [ ] Variables ({{var}}) preserved in template.md
-- [ ] Elicitation points (elicit: true) converted to <invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
-- [ ] Conditional sections preserved with if="" attributes
-- [ ] Repeatable sections converted to repeat="" attributes
-
-#### v6 Compliance
-
-- [ ] workflow.yaml follows structure from workflow-creation-guide.md
-- [ ] instructions.md has critical headers referencing workflow engine
-- [ ] Steps numbered sequentially with clear goals
-- [ ] Template variables match between instructions and template.md
-- [ ] Proper use of XML tags (<action>, <check>, <ask>, <template-output>)
-- [ ] File structure follows v6 pattern (folder with yaml/md files)
-
-#### Best Practices
-
-- [ ] Steps are focused with single goals
-- [ ] Instructions are specific ("Write 1-2 paragraphs" not "Write about")
-- [ ] Examples provided where helpful
-- [ ] Limits set where appropriate ("3-5 items maximum")
-- [ ] Save checkpoints with <template-output> at logical points
-- [ ] Variables use descriptive snake_case names
-
-### For Task Conversions
-
-#### Content Preservation
-
-- [ ] Task logic fully captured in workflow instructions
-- [ ] Execution flow maintained
-- [ ] User interaction points preserved
-- [ ] Decision trees converted to workflow logic
-- [ ] All processing steps accounted for
-- [ ] Document generation patterns identified and preserved
-
-#### Type Determination
-
-- [ ] Workflow type correctly identified (document/action/interactive/meta)
-- [ ] If generates documents, template.md created
-- [ ] If performs actions only, marked as action workflow
-- [ ] Output patterns properly analyzed
-
-#### v6 Compliance
-
-- [ ] Converted to proper workflow format (not standalone task)
-- [ ] Follows workflow execution engine patterns
-- [ ] Interactive elements use proper v6 tags
-- [ ] Flow control uses v6 patterns (goto, check, loop)
-- [ ] 1-9 elicitation menus converted to v6 elicitation
-- [ ] Critical notices preserved in workflow.yaml
-- [ ] YOLO mode converted to appropriate v6 patterns
-
-### Module-Level Validation
-
-#### Structure
-
-- [ ] Module follows v6 directory structure
-- [ ] All components in correct locations:
-  - Agents in /agents/
-  - Workflows in /workflows/
-  - Data files in appropriate locations
-- [ ] Config files properly formatted
-
-#### Integration
-
-- [ ] Cross-references between components work
-- [ ] Workflow invocations use correct paths
-- [ ] Data file references are valid
-- [ ] No broken dependencies
-
-## Technical Validation
-
-### Syntax and Format
-
-- [ ] YAML files have valid syntax (no parsing errors)
-- [ ] XML structures properly formed and closed
-- [ ] Markdown files render correctly
-- [ ] File encoding is UTF-8
-- [ ] Line endings consistent (LF)
-
-### Path Resolution
-
-- [ ] All file paths resolve correctly
-- [ ] Variable substitutions work ({project-root}, {installed_path}, etc.)
-- [ ] Config references load properly
-- [ ] No hardcoded absolute paths (unless intentional)
-
-## Functional Validation
-
-### Execution Testing
-
-- [ ] Converted item can be loaded without errors
-- [ ] Agents activate properly when invoked
-- [ ] Workflows execute through completion
-- [ ] User interaction points function correctly
-- [ ] Output generation works as expected
-
-### Behavioral Validation
-
-- [ ] Converted item behaves similarly to v4 version
-- [ ] Core functionality preserved
-- [ ] User experience maintains or improves
-- [ ] No functionality regression
-
-## Documentation and Cleanup
-
-### Documentation
-
-- [ ] Conversion report generated with all changes
-- [ ] Any manual adjustments documented
-- [ ] Known limitations or differences noted
-- [ ] Migration instructions provided if needed
-
-### Post-Conversion
-
-- [ ] Original v4 files archived (if requested)
-- [ ] File permissions set correctly
-- [ ] Git tracking updated if applicable
-- [ ] User informed of new locations
-
-## Final Verification
-
-### Quality Assurance
-
-- [ ] Converted item follows ALL v6 best practices
-- [ ] Code/config is clean and maintainable
-- [ ] No TODO or FIXME items remain
-- [ ] Ready for production use
-
-### User Acceptance
-
-- [ ] User reviewed conversion output
-- [ ] User tested basic functionality
-- [ ] User approved final result
-- [ ] Any user feedback incorporated
-
-## Notes Section
-
-### Conversion Issues Found:
-
-_List any issues encountered during validation_
-
-### Manual Interventions Required:
-
-_Document any manual fixes needed_
-
-### Recommendations:
-
-_Suggestions for further improvements or considerations_
-
----
-
-**Validation Result:** [ ] PASSED / [ ] FAILED
-
-**Validator:** {{user_name}}
-**Date:** {{date}}
-**Items Converted:** {{conversion_summary}}

bmad/bmb/workflows/convert-legacy/instructions.md

@@ -1,377 +0,0 @@
-# Convert Legacy - v4 to v6 Conversion Instructions
-
-<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
-<parameter name="You MUST have already loaded and processed: {project-root}/bmad/bmb/workflows/convert-legacy/workflow.yaml</critical>
-<critical>Communicate in {communication_language} throughout the conversion process</critical>
-
-<workflow>
-
-<step n="1" goal="Identify and Load Legacy Item">
-<action>Ask user for the path to the v4 item to convert (agent, workflow, or module)</action>
-<action>Load the complete file/folder structure</action>
-<action>Detect item type based on structure and content patterns:</action>
-  - Agent: Contains agent or prompt XML tags, single file
-  - Workflow: Contains workflow YAML or instruction patterns, usually folder
-  - Module: Contains multiple agents/workflows in organized structure
-  - Task: Contains task XML tags
-<ask>Confirm detected type or allow user to correct: "Detected as [type]. Is this correct? (y/n)"</ask>
-</step>
-
-<step n="2" goal="Analyze Legacy Structure">
-<action>Parse the v4 structure and extract key components:</action>
-
-For v4 Agents (YAML-based in markdown):
-
-- Agent metadata (name, id, title, icon, whenToUse)
-- Persona block (role, style, identity, focus, core_principles)
-- Commands list with task/template references
-- Dependencies (tasks, templates, checklists, data files)
-- Activation instructions and workflow rules
-- IDE file resolution patterns
-
-For v4 Templates (YAML-based document generators):
-
-- Template metadata (id, name, version, output)
-- Workflow mode and elicitation settings
-- Sections hierarchy with:
-  - Instructions for content generation
-  - Elicit flags for user interaction
-  - Templates with {{variables}}
-  - Conditional sections
-  - Repeatable sections
-
-For v4 Tasks (Markdown with execution instructions):
-
-- Critical execution notices
-- Step-by-step workflows
-- Elicitation requirements (1-9 menu format)
-- Processing flows and decision trees
-- Agent permission rules
-
-For Modules:
-
-- Module metadata
-- Component list (agents, workflows, tasks)
-- Dependencies
-- Installation requirements
-
-<action>Create a conversion map of what needs to be transformed</action>
-<action>Map v4 patterns to v6 equivalents:
-
-- v4 Task + Template → v6 Workflow (folder with workflow.yaml, instructions.md, template.md)
-- v4 Agent YAML → v6 Agent YAML format
-- v4 Commands → v6 <menu> with proper handlers
-- v4 Dependencies → v6 workflow references or data files
-  </action>
-  </step>
-
-<step n="3" goal="Determine Target Module and Location">
-<ask>Which module should this belong to? (eg. bmm, bmb, cis, bmm-legacy, or custom)</ask>
-<action if="custom module"><ask>Enter custom module code (kebab-case):</ask></action>
-<action>Determine installation path based on type and module</action>
-<critical>IMPORTANT: All paths must use final BMAD installation locations, not src paths!</critical>
-<action>Show user the target location: {project-root}/bmad/{{target_module}}/{{item_type}}/{{item_name}}</action>
-<action>Note: Files will be created in bmad/ but all internal paths will reference {project-root}/bmad/ locations</action>
-<ask>Proceed with this location? (y/n)</ask>
-</step>
-
-<step n="4" goal="Choose Conversion Strategy">
-<action>Based on item type and complexity, choose approach:</action>
-
-<check if="agent conversion">
-  <check if="simple agent (basic persona + commands)">
-    <action>Use direct conversion to v6 agent YAML format</action>
-    <goto step="5a">Direct Agent Conversion</goto>
-  </check>
-  <check if="complex agent with embedded workflows">
-    <action>Plan to invoke create-agent workflow</action>
-    <goto step="5b">Workflow-Assisted Agent Creation</goto>
-  </check>
-</check>
-
-<check if="template or task conversion to workflow">
-  <action>Analyze the v4 item to determine workflow type:</action>
-
-- Does it generate a specific document type? → Document workflow
-- Does it produce structured output files? → Document workflow
-- Does it perform actions without output? → Action workflow
-- Does it coordinate other tasks? → Meta-workflow
-- Does it guide user interaction? → Interactive workflow
-
-<ask>Based on analysis, this appears to be a {{detected_workflow_type}} workflow. Confirm or correct:
-
-1. Document workflow (generates documents with template)
-2. Action workflow (performs actions, no template)
-3. Interactive workflow (guided session)
-4. Meta-workflow (coordinates other workflows)
-   Select 1-4:</ask>
-
-<action if="template conversion"><goto step="5c">Template-to-Workflow Conversion</goto></action>
-<action if="task conversion"><goto step="5e">Task-to-Workflow Conversion</goto></action>
-</check>
-
-<check if="full module conversion">
-  <action>Plan to invoke create-module workflow</action>
-  <goto step="5d">Module Creation</goto>
-</check>
-</step>
-
-<step n="5a" goal="Direct Agent Conversion" optional="true">
-<action>Transform v4 YAML agent to v6 YAML format:</action>
-
-1. Convert agent metadata structure:
-   - v4 `agent.name` → v6 `agent.metadata.name`
-   - v4 `agent.id` → v6 `agent.metadata.id`
-   - v4 `agent.title` → v6 `agent.metadata.title`
-   - v4 `agent.icon` → v6 `agent.metadata.icon`
-   - Add v6 `agent.metadata.module` field
-
-2. Transform persona structure:
-   - v4 `persona.role` → v6 `agent.persona.role` (keep as YAML string)
-   - v4 `persona.style` → v6 `agent.persona.communication_style`
-   - v4 `persona.identity` → v6 `agent.persona.identity`
-   - v4 `persona.core_principles` → v6 `agent.persona.principles` (as array)
-
-3. Convert commands to menu:
-   - v4 `commands:` list → v6 `agent.menu:` array
-   - Each command becomes menu item with:
-     - `trigger:` (without \* prefix - added at build)
-     - `description:`
-     - Handler attributes (`workflow:`, `exec:`, `action:`, etc.)
-   - Map task references to workflow paths
-   - Map template references to workflow invocations
-
-4. Add v6-specific sections (in YAML):
-   - `agent.prompts:` array for inline prompts (if using action: "#id")
-   - `agent.critical_actions:` array for startup requirements
-   - `agent.activation_rules:` for universal agent rules
-
-5. Handle dependencies and paths:
-   - Convert task dependencies to workflow references
-   - Map template dependencies to v6 workflows
-   - Preserve checklist and data file references
-   - CRITICAL: All paths must use {project-root}/bmad/{{module}}/ NOT src/
-
-<action>Generate the converted v6 agent YAML file (.agent.yaml)</action>
-<action>Example path conversions:
-
-- exec="{project-root}/bmad/{{target_module}}/tasks/task-name.md"
-- run-workflow="{project-root}/bmad/{{target_module}}/workflows/workflow-name/workflow.yaml"
-- data="{project-root}/bmad/{{target_module}}/data/data-file.yaml"
-  </action>
-  <action>Save to: bmad/{{target_module}}/agents/{{agent_name}}.agent.yaml (physical location)</action>
-  <action>Note: The build process will later compile this to .md with XML format</action>
-  <goto step="6">Continue to Validation</goto>
-  </step>
-
-<step n="5b" goal="Workflow-Assisted Agent Creation" optional="true">
-<action>Extract key information from v4 agent:</action>
-- Name and purpose
-- Commands and functionality
-- Persona traits
-- Any special behaviors
-
-<invoke-workflow>
-  workflow: {project-root}/bmad/bmb/workflows/create-agent/workflow.yaml
-  inputs:
-    - agent_name: {{extracted_name}}
-    - agent_purpose: {{extracted_purpose}}
-    - commands: {{extracted_commands}}
-    - persona: {{extracted_persona}}
-</invoke-workflow>
-
-<goto step="6">Continue to Validation</goto>
-</step>
-
-<step n="5c" goal="Template-to-Workflow Conversion" optional="true">
-<action>Convert v4 Template (YAML) to v6 Workflow:</action>
-
-1. Extract template metadata:
-   - Template id, name, version → workflow.yaml name/description
-   - Output settings → default_output_file
-   - Workflow mode (interactive/yolo) → workflow settings
-
-2. Convert template sections to instructions.md:
-   - Each YAML section → workflow step
-   - `elicit: true` → `<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>` tag
-   - Conditional sections → `if="condition"` attribute
-   - Repeatable sections → `repeat="for-each"` attribute
-   - Section instructions → step content
-
-3. Extract template structure to template.md:
-   - Section content fields → template structure
-   - {{variables}} → preserve as-is
-   - Nested sections → hierarchical markdown
-
-4. Handle v4 create-doc.md task integration:
-   - Elicitation methods (1-9 menu) → convert to v6 elicitation
-   - Agent permissions → note in instructions
-   - Processing flow → integrate into workflow steps
-
-<critical>When invoking create-workflow, the standard config block will be automatically added:</critical>
-
-```yaml
-# Critical variables from config
-config_source: '{project-root}/bmad/{{target_module}}/config.yaml'
-output_folder: '{config_source}:output_folder'
-user_name: '{config_source}:user_name'
-communication_language: '{config_source}:communication_language'
-date: system-generated
-```
-
-<invoke-workflow>
-  workflow: {project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml
-  inputs:
-    - workflow_name: {{template_name}}
-    - workflow_type: document
-    - template_structure: {{extracted_template}}
-    - instructions: {{converted_sections}}
-</invoke-workflow>
-
-<action>Verify the created workflow.yaml includes standard config block</action>
-<action>Update converted instructions to use config variables where appropriate</action>
-
-<goto step="6">Continue to Validation</goto>
-</step>
-
-<step n="5d" goal="Module Creation" optional="true">
-<action>Analyze module structure and components</action>
-<action>Create module blueprint with all components</action>
-
-<invoke-workflow>
-  workflow: {project-root}/bmad/bmb/workflows/create-module/workflow.yaml
-  inputs:
-    - module_name: {{module_name}}
-    - components: {{component_list}}
-</invoke-workflow>
-
-<goto step="6">Continue to Validation</goto>
-</step>
-
-<step n="5e" goal="Task-to-Workflow Conversion" optional="true">
-<action>Convert v4 Task (Markdown) to v6 Workflow:</action>
-
-1. Analyze task purpose and output:
-   - Does it generate documents? → Create template.md
-   - Does it process data? → Action workflow
-   - Does it guide user interaction? → Interactive workflow
-   - Check for file outputs, templates, or document generation
-
-2. Extract task components:
-   - Execution notices and critical rules → workflow.yaml metadata
-   - Step-by-step instructions → instructions.md steps
-   - Decision trees and branching → flow control tags
-   - User interaction patterns → appropriate v6 tags
-
-3. Based on confirmed workflow type:
-   <check if="Document workflow">
-   - Create template.md from output patterns
-   - Map generation steps to instructions
-   - Add template-output tags for sections
-     </check>
-
-   <check if="Action workflow">
-     - Set template: false in workflow.yaml
-     - Focus on action sequences in instructions
-     - Preserve execution logic
-   </check>
-
-4. Handle special v4 patterns:
-   - 1-9 elicitation menus → v6 <invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
-   - Agent permissions → note in instructions
-   - YOLO mode → autonomous flag or optional steps
-   - Critical notices → workflow.yaml comments
-
-<critical>When invoking create-workflow, the standard config block will be automatically added:</critical>
-
-```yaml
-# Critical variables from config
-config_source: '{project-root}/bmad/{{target_module}}/config.yaml'
-output_folder: '{config_source}:output_folder'
-user_name: '{config_source}:user_name'
-communication_language: '{config_source}:communication_language'
-date: system-generated
-```
-
-<invoke-workflow>
-  workflow: {project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml
-  inputs:
-    - workflow_name: {{task_name}}
-    - workflow_type: {{confirmed_workflow_type}}
-    - instructions: {{extracted_task_logic}}
-    - template: {{generated_template_if_document}}
-</invoke-workflow>
-
-<action>Verify the created workflow.yaml includes standard config block</action>
-<action>Update converted instructions to use config variables where appropriate</action>
-
-<goto step="6">Continue to Validation</goto>
-</step>
-
-<step n="6" goal="Validate Conversion">
-<action>Run validation checks on converted item:</action>
-
-For Agents:
-
-- [ ] Valid YAML structure (.agent.yaml)
-- [ ] All required sections present (metadata, persona, menu)
-- [ ] Menu items properly formatted (trigger, description, handlers)
-- [ ] Paths use {project-root} variables
-
-For Workflows:
-
-- [ ] Valid YAML syntax
-- [ ] Instructions follow v6 conventions
-- [ ] Template variables match
-- [ ] File structure correct
-
-**Standard Config Validation (Workflows):**
-
-- [ ] workflow.yaml contains standard config block:
-  - config_source defined
-  - output_folder, user_name, communication_language pulled from config
-  - date set to system-generated
-- [ ] Converted instructions use config variables where appropriate
-- [ ] Template includes config variables in metadata (if document workflow)
-- [ ] No hardcoded paths that should use {output_folder}
-- [ ] No generic greetings that should use {user_name}
-
-For Modules:
-
-- [ ] All components converted
-- [ ] Proper folder structure
-- [ ] Config files valid
-- [ ] Installation ready
-
-<action>Show validation results to user</action>
-<ask>Any issues to fix before finalizing? (y/n)</ask>
-<check if="yes">
-<action>Address specific issues</action>
-<goto step="6">Re-validate</goto>
-</check>
-</step>
-
-<step n="7" goal="Migration Report">
-<action>Generate conversion report showing:</action>
-- Original v4 location
-- New v6 location
-- Items converted
-- Any manual adjustments needed
-- Warnings or notes
-
-<action>Save report to: {output_folder}/conversion-report-{{date}}.md</action>
-<action>Inform {user_name} in {communication_language} that the conversion report has been generated</action>
-</step>
-
-<step n="8" goal="Cleanup and Finalize">
-<ask>Archive original v4 files? (y/n)</ask>
-<action if="yes">Move v4 files to: {project-root}/archive/v4-legacy/{{date}}/</action>
-
-<action>Show user the final converted items and their locations</action>
-<action>Provide any post-conversion instructions or recommendations</action>
-
-<ask>Would you like to convert another legacy item? (y/n)</ask>
-<action if="yes"><goto step="1">Start new conversion</goto></action>
-</step>
-
-</workflow>

bmad/bmb/workflows/convert-legacy/workflow.yaml

@@ -1,32 +0,0 @@
-# Convert Legacy - BMAD v4 to v6 Converter Configuration
-name: "convert-legacy"
-description: "Converts legacy BMAD v4 or similar items (agents, workflows, modules) to BMad Core compliant format with proper structure and conventions"
-author: "BMad"
-
-# Critical variables load from config_source
-config_source: "{project-root}/bmad/bmb/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-date: system-generated
-
-# Optional docs that can be provided as input
-recommended_inputs:
-  - legacy_file: "Path to v4 agent, workflow, or module to convert"
-
-# Module path and component files
-installed_path: "{project-root}/bmad/bmb/workflows/convert-legacy"
-template: false # This is an action/meta workflow - no template needed
-instructions: "{installed_path}/instructions.md"
-validation: "{installed_path}/checklist.md"
-
-# Output configuration - Creates converted items in appropriate module locations
-default_output_folder: "{project-root}/bmad/{{target_module}}/{{item_type}}/{{item_name}}"
-
-# Sub-workflows that may be invoked for conversion
-sub_workflows:
-  - create_agent: "{project-root}/bmad/bmb/workflows/create-agent/workflow.yaml"
-  - create_workflow: "{project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml"
-  - create_module: "{project-root}/bmad/bmb/workflows/create-module/workflow.yaml"
-
-standalone: true

bmad/bmb/workflows/create-agent/README.md

@@ -1,320 +0,0 @@
-# Build Agent
-
-## Overview
-
-The Build Agent workflow is an interactive agent builder that guides you through creating BMAD Core compliant agents as YAML source files that compile to final `.md` during install. It supports three agent types: Simple (self-contained), Expert (with sidecar resources), and Module (full-featured with workflows).
-
-## Key Features
-
-- **Optional Brainstorming**: Creative ideation session before agent building to explore concepts and personalities
-- **Three Agent Types**: Simple, Expert, and Module agents with appropriate structures
-- **Persona Development**: Guided creation of role, identity, communication style, and principles
-- **Command Builder**: Interactive command definition with workflow/task/action patterns
-- **Validation Built-In**: Ensures YAML structure and BMAD Core compliance
-- **Customize Support**: Optional `customize.yaml` for persona/menu overrides and critical actions
-- **Sidecar Resources**: Setup for Expert agents with domain-specific data
-
-## Usage
-
-### Basic Invocation
-
-```bash
-workflow create-agent
-```
-
-### Through BMad Builder Agent
-
-```
-*create-agent
-```
-
-### With Brainstorming Session
-
-The workflow includes an optional brainstorming phase (Step -1) that helps you explore agent concepts, personalities, and capabilities before building. This is particularly useful when you have a vague idea and want to develop it into a concrete agent concept.
-
-### What You'll Be Asked
-
-0. **Optional brainstorming** (vague idea → refined concept)
-1. Agent type (Simple, Expert, or Module)
-2. Basic identity (name, title, icon, filename)
-3. Module assignment (for Module agents)
-4. Sidecar resources (for Expert agents)
-5. Persona elements (role, identity, style, principles)
-6. Commands and their implementations
-7. Critical actions (optional)
-8. Activation rules (optional, rarely needed)
-
-## Workflow Structure
-
-### Files Included
-
-```
-create-agent/
-├── workflow.yaml                  # Configuration
-├── instructions.md                # Step-by-step guide
-├── checklist.md                   # Validation criteria
-├── README.md                      # This file
-├── agent-types.md                 # Agent type documentation
-├── agent-architecture.md          # Architecture patterns
-├── agent-command-patterns.md      # Command patterns reference
-└── communication-styles.md        # Style examples
-```
-
-## Workflow Process
-
-### Phase 0: Optional Brainstorming (Step -1)
-
-- Creative ideation session using diverse brainstorming techniques
-- Explore agent concepts, personalities, and capabilities
-- Generate character ideas, expertise areas, and command concepts
-- Output feeds directly into agent identity and persona development
-
-### Phase 1: Agent Setup (Steps 0-2)
-
-- Load agent building documentation and patterns
-- Choose agent type (Simple/Expert/Module)
-- Define basic identity (name, title, icon, filename) - informed by brainstorming if completed
-- Assign to module (for Module agents)
-
-### Phase 2: Persona Development (Steps 2-3)
-
-- Define role and responsibilities - leveraging brainstorming insights if available
-- Craft unique identity and backstory
-- Select communication style - can use brainstormed personality concepts
-- Establish guiding principles
-- Add critical actions (optional)
-
-### Phase 3: Command Building (Step 4)
-
-- Add *help and *exit commands (required)
-- Define workflow commands (most common)
-- Add task commands (for single operations)
-- Create action commands (inline logic)
-- Configure command attributes
-
-### Phase 4: Finalization (Steps 5-10)
-
-- Confirm activation behavior (mostly automatic)
-- Generate `.agent.yaml` file
-- Optionally create a customize file for overrides
-- Setup sidecar resources (for Expert agents)
-- Validate YAML and compile to `.md`
-- Provide usage instructions
-
-## Output
-
-### Generated Files
-
-#### For Standalone Agents (not part of a module)
-
-- **YAML Source**: `{custom_agent_location}/{{agent_filename}}.agent.yaml` (default: `bmad/agents/`)
-- **Installation Location**: `{project-root}/bmad/agents/{{agent_filename}}.md`
-- **Compilation**: Run the BMAD Method installer and select "Compile Agents (Quick rebuild of all agent .md files)"
-
-#### For Module Agents
-
-- **YAML Source**: `src/modules/{{target_module}}/agents/{{agent_filename}}.agent.yaml`
-- **Installation Location**: `{project-root}/bmad/{{module}}/agents/{{agent_filename}}.md`
-- **Compilation**: Automatic during module installation
-
-### YAML Agent Structure (simplified)
-
-```yaml
-agent:
-  metadata:
-    id: bmad/{{module}}/agents/{{agent_filename}}.md
-    name: { { agent_name } }
-    title: { { agent_title } }
-    icon: { { agent_icon } }
-    module: { { module } }
-  persona:
-    role: '...'
-    identity: '...'
-    communication_style: '...'
-    principles: ['...', '...']
-  menu:
-    - trigger: example
-      workflow: '{project-root}/path/to/workflow.yaml'
-      description: Do the thing
-```
-
-### Optional Customize File
-
-If created, generates at:
-`{project-root}/bmad/_cfg/agents/{{module}}-{{agent_filename}}.customize.yaml`
-
-## Installation and Compilation
-
-### Agent Installation Locations
-
-Agents are installed to different locations based on their type:
-
-1. **Standalone Agents** (not part of a module)
-   - Source: Created in your custom agent location (default: `bmad/agents/`)
-   - Installed to: `{project-root}/bmad/agents/`
-   - Compilation: Run BMAD Method installer and select "Compile Agents"
-
-2. **Module Agents** (part of BMM, BMB, or custom modules)
-   - Source: Created in `src/modules/{module}/agents/`
-   - Installed to: `{project-root}/bmad/{module}/agents/`
-   - Compilation: Automatic during module installation
-
-### Compilation Process
-
-The installer compiles YAML agent definitions to Markdown:
-
-```bash
-# For standalone agents
-npm run build:agents
-
-# For all BMad components (includes agents)
-npm run install:bmad
-
-# Using the installer menu
-npm run installer
-# Then select: Compile Agents
-```
-
-### Build Commands
-
-Additional build commands for agent management:
-
-```bash
-# Build specific agent types
-npx bmad-method build:agents        # Build standalone agents
-npx bmad-method build:modules        # Build module agents (with modules)
-
-# Full rebuild
-npx bmad-method build:all           # Rebuild everything
-```
-
-## Requirements
-
-- BMAD Core v6 project structure
-- Module to host the agent (for Module agents)
-- Understanding of agent purpose and commands
-- Workflows/tasks to reference in commands (or mark as "todo")
-
-## Brainstorming Integration
-
-The optional brainstorming phase (Step -1) provides a seamless path from vague idea to concrete agent concept:
-
-### When to Use Brainstorming
-
-- **Vague concept**: "I want an agent that helps with data stuff"
-- **Creative exploration**: Want to discover unique personality and approach
-- **Team building**: Creating agents for a module with specific roles
-- **Character development**: Need to flesh out agent personality and voice
-
-### Brainstorming Flow
-
-1. **Step -1**: Optional brainstorming session
-   - Uses CIS brainstorming workflow with agent-specific context
-   - Explores identity, personality, expertise, and command concepts
-   - Generates detailed character and capability ideas
-
-2. **Steps 0-2**: Agent setup informed by brainstorming
-   - Brainstorming output guides agent type selection
-   - Character concepts inform basic identity choices
-   - Personality insights shape persona development
-
-3. **Seamless transition**: Vague idea → brainstormed concept → built agent
-
-### Key Principle
-
-Users can go from **vague idea → brainstormed concept → built agent** in one continuous flow, with brainstorming output directly feeding into agent development.
-
-## Best Practices
-
-### Before Starting
-
-1. Review example agents in `/bmad/bmm/agents/` for patterns
-2. Consider using brainstorming if you have a vague concept to develop
-3. Have a clear vision of the agent's role and personality (or use brainstorming to develop it)
-4. List the commands/capabilities the agent will need
-5. Identify any workflows or tasks the agent will invoke
-
-### During Execution
-
-1. **Agent Names**: Use memorable names that reflect personality
-2. **Icons**: Choose an emoji that represents the agent's role
-3. **Persona**: Make it distinct and consistent with communication style
-4. **Commands**: Use kebab-case, start custom commands with letter (not \*)
-5. **Workflows**: Reference existing workflows or mark as "todo" to implement later
-
-### After Completion
-
-1. **Compile the agent**:
-   - For standalone agents: Run `npm run build:agents` or use the installer menu
-   - For module agents: Automatic during module installation
-2. **Test the agent**: Use the compiled `.md` agent in your IDE
-3. **Implement placeholders**: Complete any "todo" workflows referenced
-4. **Refine as needed**: Use customize file for persona adjustments
-5. **Evolve over time**: Add new commands as requirements emerge
-
-## Agent Types
-
-### Simple Agent
-
-- **Best For**: Self-contained utilities, simple assistants
-- **Characteristics**: Embedded logic, no external dependencies
-- **Example**: Calculator agent, random picker, simple formatter
-
-### Expert Agent
-
-- **Best For**: Domain-specific agents with data/memory
-- **Characteristics**: Sidecar folders, domain restrictions, memory files
-- **Example**: Diary keeper, project journal, personal knowledge base
-
-### Module Agent
-
-- **Best For**: Full-featured agents with workflows
-- **Characteristics**: Part of module, commands invoke workflows
-- **Example**: Product manager, architect, research assistant
-
-## Troubleshooting
-
-### Issue: Agent won't load
-
-- **Solution**: Validate XML structure is correct
-- **Check**: Ensure all required tags present (persona, cmds)
-
-### Issue: Commands don't work
-
-- **Solution**: Verify workflow paths are correct or marked "todo"
-- **Check**: Test workflow invocation separately first
-
-### Issue: Persona feels generic
-
-- **Solution**: Review communication styles guide
-- **Check**: Make identity unique and specific to role
-
-## Customization
-
-To modify agent building process:
-
-1. Edit `instructions.md` to change steps
-2. Update `agent-types.md` to add new agent patterns
-3. Modify `agent-command-patterns.md` for new command types
-4. Edit `communication-styles.md` to add personality examples
-
-## Version History
-
-- **v6.0.0** - BMAD Core v6 compatible
-  - Three agent types (Simple/Expert/Module)
-  - Enhanced persona development
-  - Command pattern library
-  - Validation framework
-
-## Support
-
-For issues or questions:
-
-- Review example agents in `/bmad/bmm/agents/`
-- Check agent documentation in this workflow folder
-- Test with simple agents first, then build complexity
-- Consult BMAD Method v6 documentation
-
----
-
-_Part of the BMad Method v6 - BMB (BMad Builder) Module_

bmad/bmb/workflows/create-agent/agent-architecture.md

@@ -1,419 +0,0 @@
-# BMAD Agent Architecture Reference
-
-_LLM-Optimized Technical Documentation for Agent Building_
-
-## Core Agent Structure
-
-### Minimal Valid Agent
-
-```xml
-<!-- Powered by BMAD-CORE™ -->
-
-# Agent Name
-
-<agent id="path/to/agent.md" name="Name" title="Title" icon="🤖">
-  <persona>
-    <role>My primary function</role>
-    <identity>My background and expertise</identity>
-    <communication_style>How I interact</communication_style>
-    <principles>My core beliefs and methodology</principles>
-  </persona>
-  <menu>
-    <item cmd="*help">Show numbered menu</item>
-    <item cmd="*exit">Exit with confirmation</item>
-  </menu>
-</agent>
-```
-
-## Agent XML Schema
-
-### Root Element: `<agent>`
-
-**Required Attributes:**
-
-- `id` - Unique path identifier (e.g., "bmad/bmm/agents/analyst.md")
-- `name` - Agent's name (e.g., "Mary", "John", "Helper")
-- `title` - Professional title (e.g., "Business Analyst", "Security Engineer")
-- `icon` - Single emoji representing the agent
-
-### Core Sections
-
-#### 1. Persona Section (REQUIRED)
-
-```xml
-<persona>
-  <role>1-2 sentences: Professional title and primary expertise, use first-person voice</role>
-  <identity>2-5 sentences: Background, experience, specializations, use first-person voice</identity>
-  <communication_style>1-3 sentences: Interaction approach, tone, quirks, use first-person voice</communication_style>
-  <principles>2-5 sentences: Core beliefs, methodology, philosophy, use first-person voice</principles>
-</persona>
-```
-
-**Best Practices:**
-
-- Role: Be specific about expertise area
-- Identity: Include experience indicators (years, depth)
-- Communication: Describe HOW they interact, not just tone and quirks
-- Principles: Start with "I believe" or "I operate" for first-person voice
-
-#### 2. Critical Actions Section
-
-```xml
-<critical-actions>
-  <i>Load into memory {project-root}/bmad/{module}/config.yaml and set variables</i>
-  <i>Remember the users name is {user_name}</i>
-  <i>ALWAYS communicate in {communication_language}</i>
-  <!-- Custom initialization actions -->
-</critical-actions>
-```
-
-**For Expert Agents with Sidecars (CRITICAL):**
-
-```xml
-<critical-actions>
-  <!-- CRITICAL: Load sidecar files FIRST -->
-  <i critical="MANDATORY">Load COMPLETE file {agent-folder}/instructions.md and follow ALL directives</i>
-  <i critical="MANDATORY">Load COMPLETE file {agent-folder}/memories.md into permanent context</i>
-  <i critical="MANDATORY">You MUST follow all rules in instructions.md on EVERY interaction</i>
-
-  <!-- Standard initialization -->
-  <i>Load into memory {project-root}/bmad/{module}/config.yaml and set variables</i>
-  <i>Remember the users name is {user_name}</i>
-  <i>ALWAYS communicate in {communication_language}</i>
-
-  <!-- Domain restrictions -->
-  <i>ONLY read/write files in {user-folder}/diary/ - NO OTHER FOLDERS</i>
-</critical-actions>
-```
-
-**Common Patterns:**
-
-- Config loading for module agents
-- User context initialization
-- Language preferences
-- **Sidecar file loading (Expert agents) - MUST be explicit and CRITICAL**
-- **Domain restrictions (Expert agents) - MUST be enforced**
-
-#### 3. Menu Section (REQUIRED)
-
-```xml
-<menu>
-  <item cmd="*trigger" [attributes]>Description</item>
-</menu>
-```
-
-**Command Attributes:**
-
-- `run-workflow="{path}"` - Executes a workflow
-- `exec="{path}"` - Executes a task
-- `tmpl="{path}"` - Template reference
-- `data="{path}"` - Data file reference
-
-**Required Menu Items:**
-
-- `*help` - Always first, shows command list
-- `*exit` - Always last, exits agent
-
-## Advanced Agent Patterns
-
-### Activation Rules (OPTIONAL)
-
-```xml
-<activation critical="true">
-  <initialization critical="true" sequential="MANDATORY">
-    <step n="1">Load configuration</step>
-    <step n="2">Apply overrides</step>
-    <step n="3">Execute critical actions</step>
-    <step n="4" critical="BLOCKING">Show greeting with menu</step>
-    <step n="5" critical="BLOCKING">AWAIT user input</step>
-  </initialization>
-  <command-resolution critical="true">
-    <rule>Numeric input → Execute command at cmd_map[n]</rule>
-    <rule>Text input → Fuzzy match against commands</rule>
-  </command-resolution>
-</activation>
-```
-
-### Expert Agent Sidecar Pattern
-
-```xml
-<!-- DO NOT use sidecar-resources tag - Instead use critical-actions -->
-<!-- Sidecar files MUST be loaded explicitly in critical-actions -->
-
-<!-- Example Expert Agent with Diary domain -->
-<agent id="diary-keeper" name="Personal Assistant" title="Diary Keeper" icon="📔">
-  <critical-actions>
-    <!-- MANDATORY: Load all sidecar files -->
-    <i critical="MANDATORY">Load COMPLETE file {agent-folder}/diary-rules.md</i>
-    <i critical="MANDATORY">Load COMPLETE file {agent-folder}/user-memories.md</i>
-    <i critical="MANDATORY">Follow ALL rules from diary-rules.md</i>
-
-    <!-- Domain restriction -->
-    <i critical="MANDATORY">ONLY access files in {user-folder}/diary/</i>
-    <i critical="MANDATORY">NEVER access files outside diary folder</i>
-  </critical-actions>
-
-  <persona>...</persona>
-  <menu>...</menu>
-</agent>
-```
-
-### Module Agent Integration
-
-```xml
-<module-integration>
-  <module-path>{project-root}/bmad/{module-code}</module-path>
-  <config-source>{module-path}/config.yaml</config-source>
-  <workflows-path>{project-root}/bmad/{module-code}/workflows</workflows-path>
-</module-integration>
-```
-
-## Variable System
-
-### System Variables
-
-- `{project-root}` - Root directory of project
-- `{user_name}` - User's name from config
-- `{communication_language}` - Language preference
-- `{date}` - Current date
-- `{module}` - Current module code
-
-### Config Variables
-
-Format: `{config_source}:variable_name`
-Example: `{config_source}:output_folder`
-
-### Path Construction
-
-```
-Good: {project-root}/bmad/{module}/agents/
-Bad:  /absolute/path/to/agents/
-Bad:  ../../../relative/paths/
-```
-
-## Command Patterns
-
-### Workflow Commands
-
-```xml
-<!-- Full path -->
-<item cmd="*create-prd" run-workflow="{project-root}/bmad/bmm/workflows/prd/workflow.yaml">
-  Create Product Requirements Document
-</item>
-
-<!-- Placeholder for future -->
-<item cmd="*analyze" run-workflow="todo">
-  Perform analysis (workflow to be created)
-</item>
-```
-
-### Task Commands
-
-```xml
-<item cmd="*validate" exec="{project-root}/bmad/core/tasks/validate-workflow.xml">
-  Validate document
-</item>
-```
-
-### Template Commands
-
-```xml
-<item cmd="*brief"
-   exec="{project-root}/bmad/core/tasks/create-doc.md"
-   tmpl="{project-root}/bmad/bmm/templates/brief.md">
-  Create project brief
-</item>
-```
-
-### Data-Driven Commands
-
-```xml
-<item cmd="*standup"
-   exec="{project-root}/bmad/bmm/tasks/daily-standup.xml"
-   data="{project-root}/bmad/_cfg/agent-manifest.csv">
-  Run daily standup
-</item>
-```
-
-## Agent Type Specific Patterns
-
-### Simple Agent
-
-- Self-contained logic
-- Minimal or no external dependencies
-- May have embedded functions
-- Good for utilities and converters
-
-### Expert Agent
-
-- Domain-specific with sidecar resources
-- Restricted access patterns
-- Memory/context files
-- Good for specialized domains
-
-### Module Agent
-
-- Full integration with module
-- Multiple workflows and tasks
-- Config-driven behavior
-- Good for professional tools
-
-## Common Anti-Patterns to Avoid
-
-### ❌ Bad Practices
-
-```xml
-<!-- Missing required persona elements -->
-<persona>
-  <role>Helper</role>
-  <!-- Missing identity, style, principles -->
-</persona>
-
-<!-- Hard-coded paths -->
-<item cmd="*run" exec="/Users/john/project/task.md">
-
-<!-- No help command -->
-<menu>
-  <item cmd="*do-something">Action</item>
-  <!-- Missing *help -->
-</menu>
-
-<!-- Duplicate command triggers -->
-<item cmd="*analyze">First</item>
-<item cmd="*analyze">Second</item>
-```
-
-### ✅ Good Practices
-
-```xml
-<!-- Complete persona -->
-<persona>
-  <role>Data Analysis Expert</role>
-  <identity>Senior analyst with 10+ years...</identity>
-  <communication_style>Analytical and precise...</communication_style>
-  <principles>I believe in data-driven...</principles>
-</persona>
-
-<!-- Variable-based paths -->
-<item cmd="*run" exec="{project-root}/bmad/module/task.md">
-
-<!-- Required commands present -->
-<menu>
-  <item cmd="*help">Show commands</item>
-  <item cmd="*analyze">Perform analysis</item>
-  <item cmd="*exit">Exit</item>
-</menu>
-```
-
-## Agent Lifecycle
-
-### 1. Initialization
-
-1. Load agent file
-2. Parse XML structure
-3. Load critical-actions
-4. Apply config overrides
-5. Present greeting
-
-### 2. Command Loop
-
-1. Show numbered menu
-2. Await user input
-3. Resolve command
-4. Execute action
-5. Return to menu
-
-### 3. Termination
-
-1. User enters \*exit
-2. Cleanup if needed
-3. Exit persona
-
-## Testing Checklist
-
-Before deploying an agent:
-
-- [ ] Valid XML structure
-- [ ] All persona elements present
-- [ ] *help and *exit commands exist
-- [ ] All paths use variables
-- [ ] No duplicate commands
-- [ ] Config loading works
-- [ ] Commands execute properly
-
-## LLM Building Tips
-
-When building agents:
-
-1. Start with agent type (Simple/Expert/Module)
-2. Define complete persona first
-3. Add standard critical-actions
-4. Include *help and *exit
-5. Add domain commands
-6. Test command execution
-7. Validate with checklist
-
-## Integration Points
-
-### With Workflows
-
-- Agents invoke workflows via run-workflow
-- Workflows can be incomplete (marked "todo")
-- Workflow paths must be valid or "todo"
-
-**Workflow Interaction Styles** (BMAD v6 default):
-
-- **Intent-based + Interactive**: Workflows adapt to user context and skill level
-- Workflows collaborate with users, not just extract data
-- See workflow-creation-guide.md "Instruction Styles" section for details
-- When creating workflows for your agent, default to intent-based unless you need prescriptive control
-
-### With Tasks
-
-- Tasks are single operations
-- Executed via exec attribute
-- Can include data files
-
-### With Templates
-
-- Templates define document structure
-- Used with create-doc task
-- Variables passed through
-
-## Quick Reference
-
-### Minimal Commands
-
-```xml
-<menu>
-  <item cmd="*help">Show numbered cmd list</item>
-  <item cmd="*exit">Exit with confirmation</item>
-</menu>
-```
-
-### Standard Critical Actions
-
-```xml
-<critical-actions>
-  <i>Load into memory {project-root}/bmad/{module}/config.yaml</i>
-  <i>Remember the users name is {user_name}</i>
-  <i>ALWAYS communicate in {communication_language}</i>
-</critical-actions>
-```
-
-### Module Agent Pattern
-
-```xml
-<agent id="bmad/{module}/agents/{name}.md"
-       name="{Name}"
-       title="{Title}"
-       icon="{emoji}">
-  <persona>...</persona>
-  <critical-actions>...</critical-actions>
-  <menu>
-    <item cmd="*help">...</item>
-    <item cmd="*{command}" run-workflow="{path}">...</item>
-    <item cmd="*exit">...</item>
-  </menu>
-</agent>
-```

bmad/bmb/workflows/create-agent/agent-architecture.md.bak

@@ -1,412 +0,0 @@
-# BMAD Agent Architecture Reference
-
-_LLM-Optimized Technical Documentation for Agent Building_
-
-## Core Agent Structure
-
-### Minimal Valid Agent
-
-```xml
-<!-- Powered by BMAD-CORE™ -->
-
-# Agent Name
-
-<agent id="path/to/agent.md" name="Name" title="Title" icon="🤖">
-  <persona>
-    <role>My primary function</role>
-    <identity>My background and expertise</identity>
-    <communication_style>How I interact</communication_style>
-    <principles>My core beliefs and methodology</principles>
-  </persona>
-  <menu>
-    <item cmd="*help">Show numbered menu</item>
-    <item cmd="*exit">Exit with confirmation</item>
-  </menu>
-</agent>
-```
-
-## Agent XML Schema
-
-### Root Element: `<agent>`
-
-**Required Attributes:**
-
-- `id` - Unique path identifier (e.g., "bmad/bmm/agents/analyst.md")
-- `name` - Agent's name (e.g., "Mary", "John", "Helper")
-- `title` - Professional title (e.g., "Business Analyst", "Security Engineer")
-- `icon` - Single emoji representing the agent
-
-### Core Sections
-
-#### 1. Persona Section (REQUIRED)
-
-```xml
-<persona>
-  <role>1-2 sentences: Professional title and primary expertise, use first-person voice</role>
-  <identity>2-5 sentences: Background, experience, specializations, use first-person voice</identity>
-  <communication_style>1-3 sentences: Interaction approach, tone, quirks, use first-person voice</communication_style>
-  <principles>2-5 sentences: Core beliefs, methodology, philosophy, use first-person voice</principles>
-</persona>
-```
-
-**Best Practices:**
-
-- Role: Be specific about expertise area
-- Identity: Include experience indicators (years, depth)
-- Communication: Describe HOW they interact, not just tone and quirks
-- Principles: Start with "I believe" or "I operate" for first-person voice
-
-#### 2. Critical Actions Section
-
-```xml
-<critical-actions>
-  <i>Load into memory {project-root}/bmad/{module}/config.yaml and set variables</i>
-  <i>Remember the users name is {user_name}</i>
-  <i>ALWAYS communicate in {communication_language}</i>
-  <!-- Custom initialization actions -->
-</critical-actions>
-```
-
-**For Expert Agents with Sidecars (CRITICAL):**
-
-```xml
-<critical-actions>
-  <!-- CRITICAL: Load sidecar files FIRST -->
-  <i critical="MANDATORY">Load COMPLETE file {agent-folder}/instructions.md and follow ALL directives</i>
-  <i critical="MANDATORY">Load COMPLETE file {agent-folder}/memories.md into permanent context</i>
-  <i critical="MANDATORY">You MUST follow all rules in instructions.md on EVERY interaction</i>
-
-  <!-- Standard initialization -->
-  <i>Load into memory {project-root}/bmad/{module}/config.yaml and set variables</i>
-  <i>Remember the users name is {user_name}</i>
-  <i>ALWAYS communicate in {communication_language}</i>
-
-  <!-- Domain restrictions -->
-  <i>ONLY read/write files in {user-folder}/diary/ - NO OTHER FOLDERS</i>
-</critical-actions>
-```
-
-**Common Patterns:**
-
-- Config loading for module agents
-- User context initialization
-- Language preferences
-- **Sidecar file loading (Expert agents) - MUST be explicit and CRITICAL**
-- **Domain restrictions (Expert agents) - MUST be enforced**
-
-#### 3. Menu Section (REQUIRED)
-
-```xml
-<menu>
-  <item cmd="*trigger" [attributes]>Description</item>
-</menu>
-```
-
-**Command Attributes:**
-
-- `run-workflow="{path}"` - Executes a workflow
-- `exec="{path}"` - Executes a task
-- `tmpl="{path}"` - Template reference
-- `data="{path}"` - Data file reference
-
-**Required Menu Items:**
-
-- `*help` - Always first, shows command list
-- `*exit` - Always last, exits agent
-
-## Advanced Agent Patterns
-
-### Activation Rules (OPTIONAL)
-
-```xml
-<activation critical="true">
-  <initialization critical="true" sequential="MANDATORY">
-    <step n="1">Load configuration</step>
-    <step n="2">Apply overrides</step>
-    <step n="3">Execute critical actions</step>
-    <step n="4" critical="BLOCKING">Show greeting with menu</step>
-    <step n="5" critical="BLOCKING">AWAIT user input</step>
-  </initialization>
-  <command-resolution critical="true">
-    <rule>Numeric input → Execute command at cmd_map[n]</rule>
-    <rule>Text input → Fuzzy match against commands</rule>
-  </command-resolution>
-</activation>
-```
-
-### Expert Agent Sidecar Pattern
-
-```xml
-<!-- DO NOT use sidecar-resources tag - Instead use critical-actions -->
-<!-- Sidecar files MUST be loaded explicitly in critical-actions -->
-
-<!-- Example Expert Agent with Diary domain -->
-<agent id="diary-keeper" name="Personal Assistant" title="Diary Keeper" icon="📔">
-  <critical-actions>
-    <!-- MANDATORY: Load all sidecar files -->
-    <i critical="MANDATORY">Load COMPLETE file {agent-folder}/diary-rules.md</i>
-    <i critical="MANDATORY">Load COMPLETE file {agent-folder}/user-memories.md</i>
-    <i critical="MANDATORY">Follow ALL rules from diary-rules.md</i>
-
-    <!-- Domain restriction -->
-    <i critical="MANDATORY">ONLY access files in {user-folder}/diary/</i>
-    <i critical="MANDATORY">NEVER access files outside diary folder</i>
-  </critical-actions>
-
-  <persona>...</persona>
-  <menu>...</menu>
-</agent>
-```
-
-### Module Agent Integration
-
-```xml
-<module-integration>
-  <module-path>{project-root}/bmad/{module-code}</module-path>
-  <config-source>{module-path}/config.yaml</config-source>
-  <workflows-path>{project-root}/bmad/{module-code}/workflows</workflows-path>
-</module-integration>
-```
-
-## Variable System
-
-### System Variables
-
-- `{project-root}` - Root directory of project
-- `{user_name}` - User's name from config
-- `{communication_language}` - Language preference
-- `{date}` - Current date
-- `{module}` - Current module code
-
-### Config Variables
-
-Format: `{config_source}:variable_name`
-Example: `{config_source}:output_folder`
-
-### Path Construction
-
-```
-Good: {project-root}/bmad/{module}/agents/
-Bad:  /absolute/path/to/agents/
-Bad:  ../../../relative/paths/
-```
-
-## Command Patterns
-
-### Workflow Commands
-
-```xml
-<!-- Full path -->
-<item cmd="*create-prd" run-workflow="{project-root}/bmad/bmm/workflows/prd/workflow.yaml">
-  Create Product Requirements Document
-</item>
-
-<!-- Placeholder for future -->
-<item cmd="*analyze" run-workflow="todo">
-  Perform analysis (workflow to be created)
-</item>
-```
-
-### Task Commands
-
-```xml
-<item cmd="*validate" exec="{project-root}/bmad/core/tasks/validate-workflow.xml">
-  Validate document
-</item>
-```
-
-### Template Commands
-
-```xml
-<item cmd="*brief"
-   exec="{project-root}/bmad/core/tasks/create-doc.md"
-   tmpl="{project-root}/bmad/bmm/templates/brief.md">
-  Create project brief
-</item>
-```
-
-### Data-Driven Commands
-
-```xml
-<item cmd="*standup"
-   exec="{project-root}/bmad/bmm/tasks/daily-standup.xml"
-   data="{project-root}/bmad/_cfg/agent-manifest.csv">
-  Run daily standup
-</item>
-```
-
-## Agent Type Specific Patterns
-
-### Simple Agent
-
-- Self-contained logic
-- Minimal or no external dependencies
-- May have embedded functions
-- Good for utilities and converters
-
-### Expert Agent
-
-- Domain-specific with sidecar resources
-- Restricted access patterns
-- Memory/context files
-- Good for specialized domains
-
-### Module Agent
-
-- Full integration with module
-- Multiple workflows and tasks
-- Config-driven behavior
-- Good for professional tools
-
-## Common Anti-Patterns to Avoid
-
-### ❌ Bad Practices
-
-```xml
-<!-- Missing required persona elements -->
-<persona>
-  <role>Helper</role>
-  <!-- Missing identity, style, principles -->
-</persona>
-
-<!-- Hard-coded paths -->
-<item cmd="*run" exec="/Users/john/project/task.md">
-
-<!-- No help command -->
-<menu>
-  <item cmd="*do-something">Action</item>
-  <!-- Missing *help -->
-</menu>
-
-<!-- Duplicate command triggers -->
-<item cmd="*analyze">First</item>
-<item cmd="*analyze">Second</item>
-```
-
-### ✅ Good Practices
-
-```xml
-<!-- Complete persona -->
-<persona>
-  <role>Data Analysis Expert</role>
-  <identity>Senior analyst with 10+ years...</identity>
-  <communication_style>Analytical and precise...</communication_style>
-  <principles>I believe in data-driven...</principles>
-</persona>
-
-<!-- Variable-based paths -->
-<item cmd="*run" exec="{project-root}/bmad/module/task.md">
-
-<!-- Required commands present -->
-<menu>
-  <item cmd="*help">Show commands</item>
-  <item cmd="*analyze">Perform analysis</item>
-  <item cmd="*exit">Exit</item>
-</menu>
-```
-
-## Agent Lifecycle
-
-### 1. Initialization
-
-1. Load agent file
-2. Parse XML structure
-3. Load critical-actions
-4. Apply config overrides
-5. Present greeting
-
-### 2. Command Loop
-
-1. Show numbered menu
-2. Await user input
-3. Resolve command
-4. Execute action
-5. Return to menu
-
-### 3. Termination
-
-1. User enters \*exit
-2. Cleanup if needed
-3. Exit persona
-
-## Testing Checklist
-
-Before deploying an agent:
-
-- [ ] Valid XML structure
-- [ ] All persona elements present
-- [ ] *help and *exit commands exist
-- [ ] All paths use variables
-- [ ] No duplicate commands
-- [ ] Config loading works
-- [ ] Commands execute properly
-
-## LLM Building Tips
-
-When building agents:
-
-1. Start with agent type (Simple/Expert/Module)
-2. Define complete persona first
-3. Add standard critical-actions
-4. Include *help and *exit
-5. Add domain commands
-6. Test command execution
-7. Validate with checklist
-
-## Integration Points
-
-### With Workflows
-
-- Agents invoke workflows via run-workflow
-- Workflows can be incomplete (marked "todo")
-- Workflow paths must be valid or "todo"
-
-### With Tasks
-
-- Tasks are single operations
-- Executed via exec attribute
-- Can include data files
-
-### With Templates
-
-- Templates define document structure
-- Used with create-doc task
-- Variables passed through
-
-## Quick Reference
-
-### Minimal Commands
-
-```xml
-<menu>
-  <item cmd="*help">Show numbered cmd list</item>
-  <item cmd="*exit">Exit with confirmation</item>
-</menu>
-```
-
-### Standard Critical Actions
-
-```xml
-<critical-actions>
-  <i>Load into memory {project-root}/bmad/{module}/config.yaml</i>
-  <i>Remember the users name is {user_name}</i>
-  <i>ALWAYS communicate in {communication_language}</i>
-</critical-actions>
-```
-
-### Module Agent Pattern
-
-```xml
-<agent id="bmad/{module}/agents/{name}.md"
-       name="{Name}"
-       title="{Title}"
-       icon="{emoji}">
-  <persona>...</persona>
-  <critical-actions>...</critical-actions>
-  <menu>
-    <item cmd="*help">...</item>
-    <item cmd="*{command}" run-workflow="{path}">...</item>
-    <item cmd="*exit">...</item>
-  </menu>
-</agent>
-```

bmad/bmb/workflows/create-agent/agent-command-patterns.md

@@ -1,759 +0,0 @@
-# BMAD Agent Command Patterns Reference
-
-_LLM-Optimized Guide for Command Design_
-
-## Important: How to Process Action References
-
-When executing agent commands, understand these reference patterns:
-
-```xml
-<!-- Pattern 1: Inline action -->
-<item cmd="*example" action="do this specific thing">Description</item>
-→ Execute the text "do this specific thing" directly
-
-<!-- Pattern 2: Internal reference with # prefix -->
-<item cmd="*example" action="#prompt-id">Description</item>
-→ Find <prompt id="prompt-id"> in the current agent and execute its content
-
-<!-- Pattern 3: External file reference -->
-<item cmd="*example" exec="{project-root}/path/to/file.md">Description</item>
-→ Load and execute the external file
-```
-
-**The `#` prefix is your signal that this is an internal XML node reference, not a file path.**
-
-## Command Anatomy
-
-### Basic Structure
-
-```xml
-<menu>
-  <item cmd="*trigger" [attributes]>Description</item>
-</menu>
-```
-
-**Components:**
-
-- `cmd` - The trigger word (always starts with \*)
-- `attributes` - Action directives (optional):
-  - `run-workflow` - Path to workflow YAML
-  - `exec` - Path to task/operation
-  - `tmpl` - Path to template (used with exec)
-  - `action` - Embedded prompt/instruction
-  - `data` - Path to supplementary data (universal)
-- `Description` - What shows in menu
-
-## Command Types
-
-**Quick Reference:**
-
-1. **Workflow Commands** - Execute multi-step workflows (`run-workflow`)
-2. **Task Commands** - Execute single operations (`exec`)
-3. **Template Commands** - Generate from templates (`exec` + `tmpl`)
-4. **Meta Commands** - Agent control (no attributes)
-5. **Action Commands** - Embedded prompts (`action`)
-6. **Embedded Commands** - Logic in persona (no attributes)
-
-**Universal Attributes:**
-
-- `data` - Can be added to ANY command type for supplementary info
-- `if` - Conditional execution (advanced pattern)
-- `params` - Runtime parameters (advanced pattern)
-
-### 1. Workflow Commands
-
-Execute complete multi-step processes
-
-```xml
-<!-- Standard workflow -->
-<item cmd="*create-prd"
-     run-workflow="{project-root}/bmad/bmm/workflows/prd/workflow.yaml">
-  Create Product Requirements Document
-</item>
-
-<!-- Workflow with validation -->
-<item cmd="*validate-prd"
-     validate-workflow="{output_folder}/prd-draft.md"
-     workflow="{project-root}/bmad/bmm/workflows/prd/workflow.yaml">
-  Validate PRD Against Checklist
-</item>
-
-<!-- Auto-discover validation workflow from document -->
-<item cmd="*validate-doc"
-     validate-workflow="{output_folder}/document.md">
-  Validate Document (auto-discover checklist)
-</item>
-
-<!-- Placeholder for future development -->
-<item cmd="*analyze-data"
-     run-workflow="todo">
-  Analyze dataset (workflow coming soon)
-</item>
-```
-
-**Workflow Attributes:**
-
-- `run-workflow` - Execute a workflow to create documents
-- `validate-workflow` - Validate an existing document against its checklist
-- `workflow` - (optional with validate-workflow) Specify the workflow.yaml directly
-
-**Best Practices:**
-
-- Use descriptive trigger names
-- Always use variable paths
-- Mark incomplete as "todo"
-- Description should be clear action
-- Include validation commands for workflows that produce documents
-
-### 2. Task Commands
-
-Execute single operations
-
-```xml
-<!-- Simple task -->
-<item cmd="*validate"
-   exec="{project-root}/bmad/core/tasks/validate-workflow.xml">
-  Validate document against checklist
-</item>
-
-<!-- Task with data -->
-<item cmd="*standup"
-   exec="{project-root}/bmad/mmm/tasks/daily-standup.xml"
-   data="{project-root}/bmad/_cfg/agent-manifest.csv">
-  Run agile team standup
-</item>
-```
-
-**Data Property:**
-
-- Can be used with any command type
-- Provides additional reference or context
-- Path to supplementary files or resources
-- Loaded at runtime for command execution
-
-### 3. Template Commands
-
-Generate documents from templates
-
-```xml
-<item cmd="*brief"
-   exec="{project-root}/bmad/core/tasks/create-doc.md"
-   tmpl="{project-root}/bmad/bmm/templates/brief.md">
-  Produce Project Brief
-</item>
-
-<item cmd="*competitor-analysis"
-   exec="{project-root}/bmad/core/tasks/create-doc.md"
-   tmpl="{project-root}/bmad/bmm/templates/competitor.md"
-   data="{project-root}/bmad/_data/market-research.csv">
-  Produce Competitor Analysis
-</item>
-```
-
-### 4. Meta Commands
-
-Agent control and information
-
-```xml
-<!-- Required meta commands -->
-<item cmd="*help">Show numbered cmd list</item>
-<item cmd="*exit">Exit with confirmation</item>
-
-<!-- Optional meta commands -->
-<item cmd="*yolo">Toggle Yolo Mode</item>
-<item cmd="*status">Show current status</item>
-<item cmd="*config">Show configuration</item>
-```
-
-### 5. Action Commands
-
-Direct prompts embedded in commands (Simple agents)
-
-#### Simple Action (Inline)
-
-```xml
-<!-- Short action attribute with embedded prompt -->
-<item cmd="*list-tasks"
-   action="list all tasks from {project-root}/bmad/_cfg/task-manifest.csv">
-  List Available Tasks
-</item>
-
-<item cmd="*summarize"
-   action="summarize the key points from the current document">
-  Summarize Document
-</item>
-```
-
-#### Complex Action (Referenced)
-
-For multiline/complex prompts, define them separately and reference by id:
-
-```xml
-<agent name="Research Assistant">
-  <!-- Define complex prompts as separate nodes -->
-  <prompts>
-    <prompt id="deep-analysis">
-      Perform a comprehensive analysis following these steps:
-      1. Identify the main topic and key themes
-      2. Extract all supporting evidence and data points
-      3. Analyze relationships between concepts
-      4. Identify gaps or contradictions
-      5. Generate insights and recommendations
-      6. Create an executive summary
-      Format the output with clear sections and bullet points.
-    </prompt>
-
-    <prompt id="literature-review">
-      Conduct a systematic literature review:
-      1. Summarize each source's main arguments
-      2. Compare and contrast different perspectives
-      3. Identify consensus points and controversies
-      4. Evaluate the quality and relevance of sources
-      5. Synthesize findings into coherent themes
-      6. Highlight research gaps and future directions
-      Include proper citations and references.
-    </prompt>
-  </prompts>
-
-  <!-- Commands reference the prompts by id -->
-  <menu>
-    <item cmd="*help">Show numbered cmd list</item>
-
-    <item cmd="*deep-analyze"
-       action="#deep-analysis">
-      <!-- The # means: use the <prompt id="deep-analysis"> defined above -->
-      Perform Deep Analysis
-    </item>
-
-    <item cmd="*review-literature"
-       action="#literature-review"
-       data="{project-root}/bmad/_data/sources.csv">
-      Conduct Literature Review
-    </item>
-
-    <item cmd="*exit">Exit with confirmation</item>
-  </menu>
-</agent>
-```
-
-**Reference Convention:**
-
-- `action="#prompt-id"` means: "Find and execute the <prompt> node with id='prompt-id' within this agent"
-- `action="inline text"` means: "Execute this text directly as the prompt"
-- `exec="{path}"` means: "Load and execute external file at this path"
-- The `#` prefix signals to the LLM: "This is an internal reference - look for a prompt node with this ID within the current agent XML"
-
-**LLM Processing Instructions:**
-When you see `action="#some-id"` in a command:
-
-1. Look for `<prompt id="some-id">` within the same agent
-2. Use the content of that prompt node as the instruction
-3. If not found, report error: "Prompt 'some-id' not found in agent"
-
-**Use Cases:**
-
-- Quick operations (inline action)
-- Complex multi-step processes (referenced prompt)
-- Self-contained agents with task-like capabilities
-- Reusable prompt templates within agent
-
-### 6. Embedded Commands
-
-Logic embedded in agent persona (Simple agents)
-
-```xml
-<!-- No exec/run-workflow/action attribute -->
-<item cmd="*calculate">Perform calculation</item>
-<item cmd="*convert">Convert format</item>
-<item cmd="*generate">Generate output</item>
-```
-
-## Command Naming Conventions
-
-### Action-Based Naming
-
-```xml
-*create-    <!-- Generate new content -->
-*build-     <!-- Construct components -->
-*analyze-   <!-- Examine and report -->
-*validate-  <!-- Check correctness -->
-*generate-  <!-- Produce output -->
-*update-    <!-- Modify existing -->
-*review-    <!-- Examine quality -->
-*test-      <!-- Verify functionality -->
-```
-
-### Domain-Based Naming
-
-```xml
-*brainstorm      <!-- Creative ideation -->
-*architect       <!-- Design systems -->
-*refactor        <!-- Improve code -->
-*deploy          <!-- Release to production -->
-*monitor         <!-- Watch systems -->
-```
-
-### Naming Anti-Patterns
-
-```xml
-<!-- ❌ Too vague -->
-<item cmd="*do">Do something</item>
-
-<!-- ❌ Too long -->
-<item cmd="*create-comprehensive-product-requirements-document-with-analysis">
-
-<!-- ❌ No verb -->
-<item cmd="*prd">Product Requirements</item>
-
-<!-- ✅ Clear and concise -->
-<item cmd="*create-prd">Create Product Requirements Document</item>
-```
-
-## Command Organization
-
-### Standard Order
-
-```xml
-<menu>
-  <!-- 1. Always first -->
-  <item cmd="*help">Show numbered cmd list</item>
-
-  <!-- 2. Primary workflows -->
-  <item cmd="*create-prd" run-workflow="...">Create PRD</item>
-  <item cmd="*create-module" run-workflow="...">Build module</item>
-
-  <!-- 3. Secondary actions -->
-  <item cmd="*validate" exec="...">Validate document</item>
-  <item cmd="*analyze" exec="...">Analyze code</item>
-
-  <!-- 4. Utility commands -->
-  <item cmd="*config">Show configuration</item>
-  <item cmd="*yolo">Toggle Yolo Mode</item>
-
-  <!-- 5. Always last -->
-  <item cmd="*exit">Exit with confirmation</item>
-</menu>
-```
-
-### Grouping Strategies
-
-**By Lifecycle:**
-
-```xml
-<menu>
-  <item cmd="*help">Help</item>
-  <!-- Planning -->
-  <item cmd="*brainstorm">Brainstorm ideas</item>
-  <item cmd="*plan">Create plan</item>
-  <!-- Building -->
-  <item cmd="*build">Build component</item>
-  <item cmd="*test">Test component</item>
-  <!-- Deployment -->
-  <item cmd="*deploy">Deploy to production</item>
-  <item cmd="*monitor">Monitor system</item>
-  <item cmd="*exit">Exit</item>
-</menu>
-```
-
-**By Complexity:**
-
-```xml
-<menu>
-  <item cmd="*help">Help</item>
-  <!-- Simple -->
-  <item cmd="*quick-review">Quick review</item>
-  <!-- Standard -->
-  <item cmd="*create-doc">Create document</item>
-  <!-- Complex -->
-  <item cmd="*full-analysis">Comprehensive analysis</item>
-  <item cmd="*exit">Exit</item>
-</menu>
-```
-
-## Command Descriptions
-
-### Good Descriptions
-
-```xml
-<!-- Clear action and object -->
-<item cmd="*create-prd">Create Product Requirements Document</item>
-
-<!-- Specific outcome -->
-<item cmd="*analyze-security">Perform security vulnerability analysis</item>
-
-<!-- User benefit -->
-<item cmd="*optimize">Optimize code for performance</item>
-```
-
-### Poor Descriptions
-
-```xml
-<!-- Too vague -->
-<item cmd="*process">Process</item>
-
-<!-- Technical jargon -->
-<item cmd="*exec-wf-123">Execute WF123</item>
-
-<!-- Missing context -->
-<item cmd="*run">Run</item>
-```
-
-## The Data Property
-
-### Universal Data Attribute
-
-The `data` attribute can be added to ANY command type to provide supplementary information:
-
-```xml
-<!-- Workflow with data -->
-<item cmd="*brainstorm"
-   run-workflow="{project-root}/bmad/core/workflows/brainstorming/workflow.yaml"
-   data="{project-root}/bmad/core/workflows/brainstorming/brain-methods.csv">
-  Creative Brainstorming Session
-</item>
-
-<!-- Action with data -->
-<item cmd="*analyze-metrics"
-   action="analyze these metrics and identify trends"
-   data="{project-root}/bmad/_data/performance-metrics.json">
-  Analyze Performance Metrics
-</item>
-
-<!-- Template with data -->
-<item cmd="*report"
-   exec="{project-root}/bmad/core/tasks/create-doc.md"
-   tmpl="{project-root}/bmad/bmm/templates/report.md"
-   data="{project-root}/bmad/_data/quarterly-results.csv">
-  Generate Quarterly Report
-</item>
-```
-
-**Common Data Uses:**
-
-- Reference tables (CSV files)
-- Configuration data (YAML/JSON)
-- Agent manifests (XML)
-- Historical context
-- Domain knowledge
-- Examples and patterns
-
-## Advanced Patterns
-
-### Conditional Commands
-
-```xml
-<!-- Only show if certain conditions met -->
-<item cmd="*advanced-mode"
-   if="user_level == 'expert'"
-   run-workflow="...">
-  Advanced configuration mode
-</item>
-
-<!-- Environment specific -->
-<item cmd="*deploy-prod"
-   if="environment == 'production'"
-   exec="...">
-  Deploy to production
-</item>
-```
-
-### Parameterized Commands
-
-```xml
-<!-- Accept runtime parameters -->
-<item cmd="*create-agent"
-   run-workflow="..."
-   params="agent_type,agent_name">
-  Create new agent with parameters
-</item>
-```
-
-### Command Aliases
-
-```xml
-<!-- Multiple triggers for same action -->
-<item cmd="*prd|*create-prd|*product-requirements"
-   run-workflow="...">
-  Create Product Requirements Document
-</item>
-```
-
-## Module-Specific Patterns
-
-### BMM (Business Management)
-
-```xml
-<item cmd="*create-prd">Product Requirements</item>
-<item cmd="*market-research">Market Research</item>
-<item cmd="*competitor-analysis">Competitor Analysis</item>
-<item cmd="*brief">Project Brief</item>
-```
-
-### BMB (Builder)
-
-```xml
-<item cmd="*create-agent">Build Agent</item>
-<item cmd="*create-module">Build Module</item>
-<item cmd="*create-workflow">Create Workflow</item>
-<item cmd="*module-brief">Module Brief</item>
-```
-
-### CIS (Creative Intelligence)
-
-```xml
-<item cmd="*brainstorm">Brainstorming Session</item>
-<item cmd="*ideate">Ideation Workshop</item>
-<item cmd="*storytell">Story Creation</item>
-```
-
-## Command Menu Presentation
-
-### How Commands Display
-
-```
-1. *help - Show numbered cmd list
-2. *create-prd - Create Product Requirements Document
-3. *create-agent - Build new BMAD agent
-4. *validate - Validate document
-5. *exit - Exit with confirmation
-```
-
-### Menu Customization
-
-```xml
-<!-- Group separator (visual only) -->
-<item cmd="---">━━━━━━━━━━━━━━━━━━━━</item>
-
-<!-- Section header (non-executable) -->
-<item cmd="SECTION">═══ Workflows ═══</item>
-```
-
-## Error Handling
-
-### Missing Resources
-
-```xml
-<!-- Workflow not yet created -->
-<item cmd="*future-feature"
-   run-workflow="todo">
-  Coming soon: Advanced feature
-</item>
-
-<!-- Graceful degradation -->
-<item cmd="*analyze"
-   run-workflow="{optional-path|fallback-path}">
-  Analyze with available tools
-</item>
-```
-
-## Testing Commands
-
-### Command Test Checklist
-
-- [ ] Unique trigger (no duplicates)
-- [ ] Clear description
-- [ ] Valid path or "todo"
-- [ ] Uses variables not hardcoded paths
-- [ ] Executes without error
-- [ ] Returns to menu after execution
-
-### Common Issues
-
-1. **Duplicate triggers** - Each cmd must be unique
-2. **Missing paths** - File must exist or be "todo"
-3. **Hardcoded paths** - Always use variables
-4. **No description** - Every command needs text
-5. **Wrong order** - help first, exit last
-
-## Quick Templates
-
-### Workflow Command
-
-```xml
-<!-- Create document -->
-<item cmd="*{action}-{object}"
-   run-workflow="{project-root}/bmad/{module}/workflows/{workflow}/workflow.yaml">
-  {Action} {Object Description}
-</item>
-
-<!-- Validate document -->
-<item cmd="*validate-{object}"
-   validate-workflow="{output_folder}/{document}.md"
-   workflow="{project-root}/bmad/{module}/workflows/{workflow}/workflow.yaml">
-  Validate {Object Description}
-</item>
-```
-
-### Task Command
-
-```xml
-<item cmd="*{action}"
-   exec="{project-root}/bmad/{module}/tasks/{task}.md">
-  {Action Description}
-</item>
-```
-
-### Template Command
-
-```xml
-<item cmd="*{document}"
-   exec="{project-root}/bmad/core/tasks/create-doc.md"
-   tmpl="{project-root}/bmad/{module}/templates/{template}.md">
-  Create {Document Name}
-</item>
-```
-
-## Self-Contained Agent Patterns
-
-### When to Use Each Approach
-
-**Inline Action (`action="prompt"`)**
-
-- Prompt is < 2 lines
-- Simple, direct instruction
-- Not reused elsewhere
-- Quick transformations
-
-**Referenced Prompt (`action="#prompt-id"`)**
-
-- Prompt is multiline/complex
-- Contains structured steps
-- May be reused by multiple commands
-- Maintains readability
-
-**External Task (`exec="path/to/task.md"`)**
-
-- Logic needs to be shared across agents
-- Task is independently valuable
-- Requires version control separately
-- Part of larger workflow system
-
-### Complete Self-Contained Agent
-
-```xml
-<agent id="bmad/research/agents/analyst.md" name="Research Analyst" icon="🔬">
-  <!-- Embedded prompt library -->
-  <prompts>
-    <prompt id="swot-analysis">
-      Perform a SWOT analysis:
-
-      STRENGTHS (Internal, Positive)
-      - What advantages exist?
-      - What do we do well?
-      - What unique resources?
-
-      WEAKNESSES (Internal, Negative)
-      - What could improve?
-      - Where are resource gaps?
-      - What needs development?
-
-      OPPORTUNITIES (External, Positive)
-      - What trends can we leverage?
-      - What market gaps exist?
-      - What partnerships are possible?
-
-      THREATS (External, Negative)
-      - What competition exists?
-      - What risks are emerging?
-      - What could disrupt us?
-
-      Provide specific examples and actionable insights for each quadrant.
-    </prompt>
-
-    <prompt id="competitive-intel">
-      Analyze competitive landscape:
-      1. Identify top 5 competitors
-      2. Compare features and capabilities
-      3. Analyze pricing strategies
-      4. Evaluate market positioning
-      5. Assess strengths and vulnerabilities
-      6. Recommend competitive strategies
-    </prompt>
-  </prompts>
-
-  <menu>
-    <item cmd="*help">Show numbered cmd list</item>
-
-    <!-- Simple inline actions -->
-    <item cmd="*summarize"
-       action="create executive summary of findings">
-      Create Executive Summary
-    </item>
-
-    <!-- Complex referenced prompts -->
-    <item cmd="*swot"
-       action="#swot-analysis">
-      Perform SWOT Analysis
-    </item>
-
-    <item cmd="*compete"
-       action="#competitive-intel"
-       data="{project-root}/bmad/_data/market-data.csv">
-      Analyze Competition
-    </item>
-
-    <!-- Hybrid: external task with internal data -->
-    <item cmd="*report"
-       exec="{project-root}/bmad/core/tasks/create-doc.md"
-       tmpl="{project-root}/bmad/research/templates/report.md">
-      Generate Research Report
-    </item>
-
-    <item cmd="*exit">Exit with confirmation</item>
-  </menu>
-</agent>
-```
-
-## Simple Agent Example
-
-For agents that primarily use embedded logic:
-
-```xml
-<agent name="Data Analyst">
-  <menu>
-    <item cmd="*help">Show numbered cmd list</item>
-
-    <!-- Action commands for direct operations -->
-    <item cmd="*list-metrics"
-       action="list all available metrics from the dataset">
-      List Available Metrics
-    </item>
-
-    <item cmd="*analyze"
-       action="perform statistical analysis on the provided data"
-       data="{project-root}/bmad/_data/dataset.csv">
-      Analyze Dataset
-    </item>
-
-    <item cmd="*visualize"
-       action="create visualization recommendations for this data">
-      Suggest Visualizations
-    </item>
-
-    <!-- Embedded logic commands -->
-    <item cmd="*calculate">Perform calculations</item>
-    <item cmd="*interpret">Interpret results</item>
-
-    <item cmd="*exit">Exit with confirmation</item>
-  </menu>
-</agent>
-```
-
-## LLM Building Guide
-
-When creating commands:
-
-1. Start with *help and *exit
-2. Choose appropriate command type:
-   - Complex multi-step? Use `run-workflow`
-   - Single operation? Use `exec`
-   - Need template? Use `exec` + `tmpl`
-   - Simple prompt? Use `action`
-   - Agent handles it? Use no attributes
-3. Add `data` attribute if supplementary info needed
-4. Add primary workflows (main value)
-5. Add secondary tasks
-6. Include utility commands
-7. Test each command works
-8. Verify no duplicates
-9. Ensure clear descriptions

bmad/bmb/workflows/create-agent/agent-command-patterns.md.bak

@@ -1,759 +0,0 @@
-# BMAD Agent Command Patterns Reference
-
-_LLM-Optimized Guide for Command Design_
-
-## Important: How to Process Action References
-
-When executing agent commands, understand these reference patterns:
-
-```xml
-<!-- Pattern 1: Inline action -->
-<item cmd="*example" action="do this specific thing">Description</item>
-→ Execute the text "do this specific thing" directly
-
-<!-- Pattern 2: Internal reference with # prefix -->
-<item cmd="*example" action="#prompt-id">Description</item>
-→ Find <prompt id="prompt-id"> in the current agent and execute its content
-
-<!-- Pattern 3: External file reference -->
-<item cmd="*example" exec="{project-root}/path/to/file.md">Description</item>
-→ Load and execute the external file
-```
-
-**The `#` prefix is your signal that this is an internal XML node reference, not a file path.**
-
-## Command Anatomy
-
-### Basic Structure
-
-```xml
-<menu>
-  <item cmd="*trigger" [attributes]>Description</item>
-</menu>
-```
-
-**Components:**
-
-- `cmd` - The trigger word (always starts with \*)
-- `attributes` - Action directives (optional):
-  - `run-workflow` - Path to workflow YAML
-  - `exec` - Path to task/operation
-  - `tmpl` - Path to template (used with exec)
-  - `action` - Embedded prompt/instruction
-  - `data` - Path to supplementary data (universal)
-- `Description` - What shows in menu
-
-## Command Types
-
-**Quick Reference:**
-
-1. **Workflow Commands** - Execute multi-step workflows (`run-workflow`)
-2. **Task Commands** - Execute single operations (`exec`)
-3. **Template Commands** - Generate from templates (`exec` + `tmpl`)
-4. **Meta Commands** - Agent control (no attributes)
-5. **Action Commands** - Embedded prompts (`action`)
-6. **Embedded Commands** - Logic in persona (no attributes)
-
-**Universal Attributes:**
-
-- `data` - Can be added to ANY command type for supplementary info
-- `if` - Conditional execution (advanced pattern)
-- `params` - Runtime parameters (advanced pattern)
-
-### 1. Workflow Commands
-
-Execute complete multi-step processes
-
-```xml
-<!-- Standard workflow -->
-<item cmd="*create-prd"
-     run-workflow="{project-root}/bmad/bmm/workflows/prd/workflow.yaml">
-  Create Product Requirements Document
-</item>
-
-<!-- Workflow with validation -->
-<item cmd="*validate-prd"
-     validate-workflow="{output_folder}/prd-draft.md"
-     workflow="{project-root}/bmad/bmm/workflows/prd/workflow.yaml">
-  Validate PRD Against Checklist
-</item>
-
-<!-- Auto-discover validation workflow from document -->
-<item cmd="*validate-doc"
-     validate-workflow="{output_folder}/document.md">
-  Validate Document (auto-discover checklist)
-</item>
-
-<!-- Placeholder for future development -->
-<item cmd="*analyze-data"
-     run-workflow="todo">
-  Analyze dataset (workflow coming soon)
-</item>
-```
-
-**Workflow Attributes:**
-
-- `run-workflow` - Execute a workflow to create documents
-- `validate-workflow` - Validate an existing document against its checklist
-- `workflow` - (optional with validate-workflow) Specify the workflow.yaml directly
-
-**Best Practices:**
-
-- Use descriptive trigger names
-- Always use variable paths
-- Mark incomplete as "todo"
-- Description should be clear action
-- Include validation commands for workflows that produce documents
-
-### 2. Task Commands
-
-Execute single operations
-
-```xml
-<!-- Simple task -->
-<item cmd="*validate"
-   exec="{project-root}/bmad/core/tasks/validate-workflow.xml">
-  Validate document against checklist
-</item>
-
-<!-- Task with data -->
-<item cmd="*standup"
-   exec="{project-root}/bmad/mmm/tasks/daily-standup.xml"
-   data="{project-root}/bmad/_cfg/agent-manifest.csv">
-  Run agile team standup
-</item>
-```
-
-**Data Property:**
-
-- Can be used with any command type
-- Provides additional reference or context
-- Path to supplementary files or resources
-- Loaded at runtime for command execution
-
-### 3. Template Commands
-
-Generate documents from templates
-
-```xml
-<item cmd="*brief"
-   exec="{project-root}/bmad/core/tasks/create-doc.md"
-   tmpl="{project-root}/bmad/bmm/templates/brief.md">
-  Produce Project Brief
-</item>
-
-<item cmd="*competitor-analysis"
-   exec="{project-root}/bmad/core/tasks/create-doc.md"
-   tmpl="{project-root}/bmad/bmm/templates/competitor.md"
-   data="{project-root}/bmad/_data/market-research.csv">
-  Produce Competitor Analysis
-</item>
-```
-
-### 4. Meta Commands
-
-Agent control and information
-
-```xml
-<!-- Required meta commands -->
-<item cmd="*help">Show numbered cmd list</item>
-<item cmd="*exit">Exit with confirmation</item>
-
-<!-- Optional meta commands -->
-<item cmd="*yolo">Toggle Yolo Mode</item>
-<item cmd="*status">Show current status</item>
-<item cmd="*config">Show configuration</item>
-```
-
-### 5. Action Commands
-
-Direct prompts embedded in commands (Simple agents)
-
-#### Simple Action (Inline)
-
-```xml
-<!-- Short action attribute with embedded prompt -->
-<item cmd="*list-tasks"
-   action="list all tasks from {project-root}/bmad/_cfg/task-manifest.csv">
-  List Available Tasks
-</item>
-
-<item cmd="*summarize"
-   action="summarize the key points from the current document">
-  Summarize Document
-</item>
-```
-
-#### Complex Action (Referenced)
-
-For multiline/complex prompts, define them separately and reference by id:
-
-```xml
-<agent name="Research Assistant">
-  <!-- Define complex prompts as separate nodes -->
-  <prompts>
-    <prompt id="deep-analysis">
-      Perform a comprehensive analysis following these steps:
-      1. Identify the main topic and key themes
-      2. Extract all supporting evidence and data points
-      3. Analyze relationships between concepts
-      4. Identify gaps or contradictions
-      5. Generate insights and recommendations
-      6. Create an executive summary
-      Format the output with clear sections and bullet points.
-    </prompt>
-
-    <prompt id="literature-review">
-      Conduct a systematic literature review:
-      1. Summarize each source's main arguments
-      2. Compare and contrast different perspectives
-      3. Identify consensus points and controversies
-      4. Evaluate the quality and relevance of sources
-      5. Synthesize findings into coherent themes
-      6. Highlight research gaps and future directions
-      Include proper citations and references.
-    </prompt>
-  </prompts>
-
-  <!-- Commands reference the prompts by id -->
-  <menu>
-    <item cmd="*help">Show numbered cmd list</item>
-
-    <item cmd="*deep-analyze"
-       action="#deep-analysis">
-      <!-- The # means: use the <prompt id="deep-analysis"> defined above -->
-      Perform Deep Analysis
-    </item>
-
-    <item cmd="*review-literature"
-       action="#literature-review"
-       data="{project-root}/bmad/_data/sources.csv">
-      Conduct Literature Review
-    </item>
-
-    <item cmd="*exit">Exit with confirmation</item>
-  </menu>
-</agent>
-```
-
-**Reference Convention:**
-
-- `action="#prompt-id"` means: "Find and execute the <prompt> node with id='prompt-id' within this agent"
-- `action="inline text"` means: "Execute this text directly as the prompt"
-- `exec="{path}"` means: "Load and execute external file at this path"
-- The `#` prefix signals to the LLM: "This is an internal reference - look for a prompt node with this ID within the current agent XML"
-
-**LLM Processing Instructions:**
-When you see `action="#some-id"` in a command:
-
-1. Look for `<prompt id="some-id">` within the same agent
-2. Use the content of that prompt node as the instruction
-3. If not found, report error: "Prompt 'some-id' not found in agent"
-
-**Use Cases:**
-
-- Quick operations (inline action)
-- Complex multi-step processes (referenced prompt)
-- Self-contained agents with task-like capabilities
-- Reusable prompt templates within agent
-
-### 6. Embedded Commands
-
-Logic embedded in agent persona (Simple agents)
-
-```xml
-<!-- No exec/run-workflow/action attribute -->
-<item cmd="*calculate">Perform calculation</item>
-<item cmd="*convert">Convert format</item>
-<item cmd="*generate">Generate output</item>
-```
-
-## Command Naming Conventions
-
-### Action-Based Naming
-
-```xml
-*create-    <!-- Generate new content -->
-*build-     <!-- Construct components -->
-*analyze-   <!-- Examine and report -->
-*validate-  <!-- Check correctness -->
-*generate-  <!-- Produce output -->
-*update-    <!-- Modify existing -->
-*review-    <!-- Examine quality -->
-*test-      <!-- Verify functionality -->
-```
-
-### Domain-Based Naming
-
-```xml
-*brainstorm      <!-- Creative ideation -->
-*architect       <!-- Design systems -->
-*refactor        <!-- Improve code -->
-*deploy          <!-- Release to production -->
-*monitor         <!-- Watch systems -->
-```
-
-### Naming Anti-Patterns
-
-```xml
-<!-- ❌ Too vague -->
-<item cmd="*do">Do something</item>
-
-<!-- ❌ Too long -->
-<item cmd="*create-comprehensive-product-requirements-document-with-analysis">
-
-<!-- ❌ No verb -->
-<item cmd="*prd">Product Requirements</item>
-
-<!-- ✅ Clear and concise -->
-<item cmd="*create-prd">Create Product Requirements Document</item>
-```
-
-## Command Organization
-
-### Standard Order
-
-```xml
-<menu>
-  <!-- 1. Always first -->
-  <item cmd="*help">Show numbered cmd list</item>
-
-  <!-- 2. Primary workflows -->
-  <item cmd="*create-prd" run-workflow="...">Create PRD</item>
-  <item cmd="*create-module" run-workflow="...">Build module</item>
-
-  <!-- 3. Secondary actions -->
-  <item cmd="*validate" exec="...">Validate document</item>
-  <item cmd="*analyze" exec="...">Analyze code</item>
-
-  <!-- 4. Utility commands -->
-  <item cmd="*config">Show configuration</item>
-  <item cmd="*yolo">Toggle Yolo Mode</item>
-
-  <!-- 5. Always last -->
-  <item cmd="*exit">Exit with confirmation</item>
-</menu>
-```
-
-### Grouping Strategies
-
-**By Lifecycle:**
-
-```xml
-<menu>
-  <item cmd="*help">Help</item>
-  <!-- Planning -->
-  <item cmd="*brainstorm">Brainstorm ideas</item>
-  <item cmd="*plan">Create plan</item>
-  <!-- Building -->
-  <item cmd="*build">Build component</item>
-  <item cmd="*test">Test component</item>
-  <!-- Deployment -->
-  <item cmd="*deploy">Deploy to production</item>
-  <item cmd="*monitor">Monitor system</item>
-  <item cmd="*exit">Exit</item>
-</menu>
-```
-
-**By Complexity:**
-
-```xml
-<menu>
-  <item cmd="*help">Help</item>
-  <!-- Simple -->
-  <item cmd="*quick-review">Quick review</item>
-  <!-- Standard -->
-  <item cmd="*create-doc">Create document</item>
-  <!-- Complex -->
-  <item cmd="*full-analysis">Comprehensive analysis</item>
-  <item cmd="*exit">Exit</item>
-</menu>
-```
-
-## Command Descriptions
-
-### Good Descriptions
-
-```xml
-<!-- Clear action and object -->
-<item cmd="*create-prd">Create Product Requirements Document</item>
-
-<!-- Specific outcome -->
-<item cmd="*analyze-security">Perform security vulnerability analysis</item>
-
-<!-- User benefit -->
-<item cmd="*optimize">Optimize code for performance</item>
-```
-
-### Poor Descriptions
-
-```xml
-<!-- Too vague -->
-<item cmd="*process">Process</item>
-
-<!-- Technical jargon -->
-<item cmd="*exec-wf-123">Execute WF123</item>
-
-<!-- Missing context -->
-<item cmd="*run">Run</item>
-```
-
-## The Data Property
-
-### Universal Data Attribute
-
-The `data` attribute can be added to ANY command type to provide supplementary information:
-
-```xml
-<!-- Workflow with data -->
-<item cmd="*brainstorm"
-   run-workflow="{project-root}/bmad/core/workflows/brainstorming/workflow.yaml"
-   data="{project-root}/bmad/core/workflows/brainstorming/brain-methods.csv">
-  Creative Brainstorming Session
-</item>
-
-<!-- Action with data -->
-<item cmd="*analyze-metrics"
-   action="analyze these metrics and identify trends"
-   data="{project-root}/bmad/_data/performance-metrics.json">
-  Analyze Performance Metrics
-</item>
-
-<!-- Template with data -->
-<item cmd="*report"
-   exec="{project-root}/bmad/core/tasks/create-doc.md"
-   tmpl="{project-root}/bmad/bmm/templates/report.md"
-   data="{project-root}/bmad/_data/quarterly-results.csv">
-  Generate Quarterly Report
-</item>
-```
-
-**Common Data Uses:**
-
-- Reference tables (CSV files)
-- Configuration data (YAML/JSON)
-- Agent manifests (XML)
-- Historical context
-- Domain knowledge
-- Examples and patterns
-
-## Advanced Patterns
-
-### Conditional Commands
-
-```xml
-<!-- Only show if certain conditions met -->
-<item cmd="*advanced-mode"
-   if="user_level == 'expert'"
-   run-workflow="...">
-  Advanced configuration mode
-</item>
-
-<!-- Environment specific -->
-<item cmd="*deploy-prod"
-   if="environment == 'production'"
-   exec="...">
-  Deploy to production
-</item>
-```
-
-### Parameterized Commands
-
-```xml
-<!-- Accept runtime parameters -->
-<item cmd="*create-agent"
-   run-workflow="..."
-   params="agent_type,agent_name">
-  Create new agent with parameters
-</item>
-```
-
-### Command Aliases
-
-```xml
-<!-- Multiple triggers for same action -->
-<item cmd="*prd|*create-prd|*product-requirements"
-   run-workflow="...">
-  Create Product Requirements Document
-</item>
-```
-
-## Module-Specific Patterns
-
-### BMM (Business Management)
-
-```xml
-<item cmd="*create-prd">Product Requirements</item>
-<item cmd="*market-research">Market Research</item>
-<item cmd="*competitor-analysis">Competitor Analysis</item>
-<item cmd="*brief">Project Brief</item>
-```
-
-### BMB (Builder)
-
-```xml
-<item cmd="*create-agent">Build Agent</item>
-<item cmd="*create-module">Build Module</item>
-<item cmd="*create-workflow">Create Workflow</item>
-<item cmd="*module-brief">Module Brief</item>
-```
-
-### CIS (Creative Intelligence)
-
-```xml
-<item cmd="*brainstorm">Brainstorming Session</item>
-<item cmd="*ideate">Ideation Workshop</item>
-<item cmd="*storytell">Story Creation</item>
-```
-
-## Command Menu Presentation
-
-### How Commands Display
-
-```
-1. *help - Show numbered cmd list
-2. *create-prd - Create Product Requirements Document
-3. *create-agent - Build new BMAD agent
-4. *validate - Validate document
-5. *exit - Exit with confirmation
-```
-
-### Menu Customization
-
-```xml
-<!-- Group separator (visual only) -->
-<item cmd="---">━━━━━━━━━━━━━━━━━━━━</item>
-
-<!-- Section header (non-executable) -->
-<item cmd="SECTION">═══ Workflows ═══</item>
-```
-
-## Error Handling
-
-### Missing Resources
-
-```xml
-<!-- Workflow not yet created -->
-<item cmd="*future-feature"
-   run-workflow="todo">
-  Coming soon: Advanced feature
-</item>
-
-<!-- Graceful degradation -->
-<item cmd="*analyze"
-   run-workflow="{optional-path|fallback-path}">
-  Analyze with available tools
-</item>
-```
-
-## Testing Commands
-
-### Command Test Checklist
-
-- [ ] Unique trigger (no duplicates)
-- [ ] Clear description
-- [ ] Valid path or "todo"
-- [ ] Uses variables not hardcoded paths
-- [ ] Executes without error
-- [ ] Returns to menu after execution
-
-### Common Issues
-
-1. **Duplicate triggers** - Each cmd must be unique
-2. **Missing paths** - File must exist or be "todo"
-3. **Hardcoded paths** - Always use variables
-4. **No description** - Every command needs text
-5. **Wrong order** - help first, exit last
-
-## Quick Templates
-
-### Workflow Command
-
-```xml
-<!-- Create document -->
-<item cmd="*{action}-{object}"
-   run-workflow="{project-root}/bmad/{module}/workflows/{workflow}/workflow.yaml">
-  {Action} {Object Description}
-</item>
-
-<!-- Validate document -->
-<item cmd="*validate-{object}"
-   validate-workflow="{output_folder}/{document}.md"
-   workflow="{project-root}/bmad/{module}/workflows/{workflow}/workflow.yaml">
-  Validate {Object Description}
-</item>
-```
-
-### Task Command
-
-```xml
-<item cmd="*{action}"
-   exec="{project-root}/bmad/{module}/tasks/{task}.md">
-  {Action Description}
-</item>
-```
-
-### Template Command
-
-```xml
-<item cmd="*{document}"
-   exec="{project-root}/bmad/core/tasks/create-doc.md"
-   tmpl="{project-root}/bmad/{module}/templates/{template}.md">
-  Create {Document Name}
-</item>
-```
-
-## Self-Contained Agent Patterns
-
-### When to Use Each Approach
-
-**Inline Action (`action="prompt"`)**
-
-- Prompt is < 2 lines
-- Simple, direct instruction
-- Not reused elsewhere
-- Quick transformations
-
-**Referenced Prompt (`action="#prompt-id"`)**
-
-- Prompt is multiline/complex
-- Contains structured steps
-- May be reused by multiple commands
-- Maintains readability
-
-**External Task (`exec="path/to/task.md"`)**
-
-- Logic needs to be shared across agents
-- Task is independently valuable
-- Requires version control separately
-- Part of larger workflow system
-
-### Complete Self-Contained Agent
-
-```xml
-<agent id="bmad/research/agents/analyst.md" name="Research Analyst" icon="🔬">
-  <!-- Embedded prompt library -->
-  <prompts>
-    <prompt id="swot-analysis">
-      Perform a SWOT analysis:
-
-      STRENGTHS (Internal, Positive)
-      - What advantages exist?
-      - What do we do well?
-      - What unique resources?
-
-      WEAKNESSES (Internal, Negative)
-      - What could improve?
-      - Where are resource gaps?
-      - What needs development?
-
-      OPPORTUNITIES (External, Positive)
-      - What trends can we leverage?
-      - What market gaps exist?
-      - What partnerships are possible?
-
-      THREATS (External, Negative)
-      - What competition exists?
-      - What risks are emerging?
-      - What could disrupt us?
-
-      Provide specific examples and actionable insights for each quadrant.
-    </prompt>
-
-    <prompt id="competitive-intel">
-      Analyze competitive landscape:
-      1. Identify top 5 competitors
-      2. Compare features and capabilities
-      3. Analyze pricing strategies
-      4. Evaluate market positioning
-      5. Assess strengths and vulnerabilities
-      6. Recommend competitive strategies
-    </prompt>
-  </prompts>
-
-  <menu>
-    <item cmd="*help">Show numbered cmd list</item>
-
-    <!-- Simple inline actions -->
-    <item cmd="*summarize"
-       action="create executive summary of findings">
-      Create Executive Summary
-    </item>
-
-    <!-- Complex referenced prompts -->
-    <item cmd="*swot"
-       action="#swot-analysis">
-      Perform SWOT Analysis
-    </item>
-
-    <item cmd="*compete"
-       action="#competitive-intel"
-       data="{project-root}/bmad/_data/market-data.csv">
-      Analyze Competition
-    </item>
-
-    <!-- Hybrid: external task with internal data -->
-    <item cmd="*report"
-       exec="{project-root}/bmad/core/tasks/create-doc.md"
-       tmpl="{project-root}/bmad/research/templates/report.md">
-      Generate Research Report
-    </item>
-
-    <item cmd="*exit">Exit with confirmation</item>
-  </menu>
-</agent>
-```
-
-## Simple Agent Example
-
-For agents that primarily use embedded logic:
-
-```xml
-<agent name="Data Analyst">
-  <menu>
-    <item cmd="*help">Show numbered cmd list</item>
-
-    <!-- Action commands for direct operations -->
-    <item cmd="*list-metrics"
-       action="list all available metrics from the dataset">
-      List Available Metrics
-    </item>
-
-    <item cmd="*analyze"
-       action="perform statistical analysis on the provided data"
-       data="{project-root}/bmad/_data/dataset.csv">
-      Analyze Dataset
-    </item>
-
-    <item cmd="*visualize"
-       action="create visualization recommendations for this data">
-      Suggest Visualizations
-    </item>
-
-    <!-- Embedded logic commands -->
-    <item cmd="*calculate">Perform calculations</item>
-    <item cmd="*interpret">Interpret results</item>
-
-    <item cmd="*exit">Exit with confirmation</item>
-  </menu>
-</agent>
-```
-
-## LLM Building Guide
-
-When creating commands:
-
-1. Start with *help and *exit
-2. Choose appropriate command type:
-   - Complex multi-step? Use `run-workflow`
-   - Single operation? Use `exec`
-   - Need template? Use `exec` + `tmpl`
-   - Simple prompt? Use `action`
-   - Agent handles it? Use no attributes
-3. Add `data` attribute if supplementary info needed
-4. Add primary workflows (main value)
-5. Add secondary tasks
-6. Include utility commands
-7. Test each command works
-8. Verify no duplicates
-9. Ensure clear descriptions