agentvibes 2.4.3-beta.2 → 2.4.3

package/README.md

@@ -11,7 +11,7 @@
 [![Publish](https://github.com/paulpreibisch/AgentVibes/actions/workflows/publish.yml/badge.svg)](https://github.com/paulpreibisch/AgentVibes/actions/workflows/publish.yml)
 [![License](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
 
-**Author**: Paul Preibisch ([@997Fire](https://x.com/997Fire)) | **Version**: v2.4.2
+**Author**: Paul Preibisch ([@997Fire](https://x.com/997Fire)) | **Version**: v2.4.3
 
 ---
 
@@ -92,15 +92,15 @@ Whether you're coding in Claude Code, chatting in Claude Desktop, or using Warp
 
 ## 📰 Latest Release
 
-**[v2.4.2 - BMAD TTS Auto-Injection](https://github.com/paulpreibisch/AgentVibes/releases/tag/v2.4.2)** 🎉
+**[v2.4.3 - macOS Compatibility Fixes](https://github.com/paulpreibisch/AgentVibes/releases/tag/v2.4.3)** 🎉
 
-This patch release makes BMAD integration completely automatic! Previously, the installer only created documentation about BMAD integration but didn't modify the agent files. Now AgentVibes automatically enables TTS for BMAD agents during installation.
+This patch release resolves three critical macOS installation issues discovered during user testing, completing the macOS compatibility work started in v2.4.0.
 
 **Key highlights:**
-- 🤖 **Automatic BMAD TTS Injection** - BMAD agents speak immediately after installation
-- ⚡ **Zero Manual Configuration** - No need to run bmad-tts-injector.sh manually
-- 🎯 **Intelligent Detection** - Automatically detects BMAD and enables TTS
-- 🛡️ **Enhanced Error Handling** - User-friendly fallback messages with clear instructions
+- 🍎 **ElevenLabs Audio Playback** - Uses native afplay on macOS
+- 🐚 **Shell Environment Detection** - Detects zsh vs bash correctly
+- 🎤 **Piper Version Check** - Uses full path to avoid false errors
+- 📦 **Plugin Manifest Handling** - Gracefully handles optional files
 
 [→ View All Releases](https://github.com/paulpreibisch/AgentVibes/releases)
 

package/RELEASE_NOTES.md

@@ -1,3 +1,96 @@
+# Release v2.4.3 - macOS Compatibility Fixes (2025-01-15)
+
+## 🤖 AI Summary
+
+This patch release resolves three critical macOS installation issues discovered during user testing. The fixes ensure seamless installation on macOS by adding proper audio playback support for ElevenLabs TTS, detecting the user's shell environment correctly (zsh vs bash), fixing Piper installer PATH issues, and handling optional plugin manifest files gracefully. These changes complete the macOS compatibility work started in v2.4.0, making AgentVibes fully functional across all platforms.
+
+## 📋 Changes
+
+### 🐛 Bug Fixes
+
+- **Fixed ElevenLabs Audio Playback on macOS**
+  - Added platform detection to use native `afplay` on macOS
+  - Previously used Linux-only players (paplay/aplay) that don't exist on macOS
+  - Audio files now play correctly instead of failing silently
+  - File: `.claude/hooks/play-tts-elevenlabs.sh` lines 387-399
+
+- **Fixed Shell Environment Detection**
+  - Installer now detects user's default shell (zsh vs bash)
+  - Environment variables written to correct config file (.zshrc or .bashrc)
+  - Scripts now execute using user's shell with proper environment
+  - Replaced hardcoded `bash` calls with shell-aware execution
+  - File: `src/installer.js` - Added `getUserShell()` and `execScript()` helpers
+
+- **Fixed Piper Version Check on macOS**
+  - Version check now uses full path `$INSTALL_DIR/piper --version`
+  - Previously failed because PATH wasn't updated in same shell session
+  - Eliminates false "piper: command not found" error after successful install
+  - File: `.claude/hooks/piper-installer.sh` line 200
+
+- **Fixed Plugin Manifest Installation Error**
+  - Installer now checks if source `.claude-plugin/plugin.json` exists
+  - Skips silently if file doesn't exist (optional feature)
+  - Prevents ENOENT error: "no such file or directory" during installation
+  - File: `src/installer.js` lines 682-704
+
+## 🎯 User Impact
+
+**For macOS Users**: All three critical installation issues are now fixed! You can install AgentVibes on macOS without errors:
+
+1. **ElevenLabs TTS audio plays correctly** - Uses native macOS `afplay` command
+2. **Environment variables work** - Installer detects zsh and writes to .zshrc
+3. **Piper installer succeeds** - No more false "command not found" errors
+4. **No plugin manifest errors** - Installation completes cleanly
+
+**What Was Broken**:
+- ElevenLabs audio generated but didn't play (wrong audio player for macOS)
+- API keys written to .zshrc but scripts ran with bash (no environment)
+- Piper binary installed successfully but version check failed
+- Plugin manifest copy failed with ENOENT error
+
+**What's Fixed**: Complete macOS installation workflow now works end-to-end.
+
+## 📦 Files Changed
+
+### Modified
+- `.claude/hooks/play-tts-elevenlabs.sh` - Added macOS audio playback support
+- `.claude/hooks/piper-installer.sh` - Fixed version check PATH issue
+- `src/installer.js` - Added shell detection, fixed plugin manifest handling
+
+### Statistics
+- 3 files changed
+- 26 insertions(+)
+- 7 deletions(-)
+
+## 🔄 Breaking Changes
+
+None. This release only fixes bugs without changing any existing functionality.
+
+## 🚀 Upgrade Notes
+
+Simply run:
+```bash
+npx agentvibes@latest install --yes
+```
+
+All fixes are applied automatically during installation. No manual configuration needed!
+
+## 🙏 Credits
+
+Special thanks to **Tyler Worley** and **Brian Madison** for thorough macOS testing and reporting these issues! Their detailed bug reports with screenshots made these fixes possible.
+
+## 🔗 Related
+
+- v2.4.2 - BMAD TTS Auto-Injection
+- v2.4.1 - macOS Piper Audio Playback Fix
+- v2.4.0 - macOS Piper TTS Support
+
+---
+
+**Full Changelog**: https://github.com/paulpreibisch/AgentVibes/compare/v2.4.2...v2.4.3
+
+---
+
 # Release v2.4.2 - BMAD TTS Auto-Injection (2025-01-15)
 
 ## 🤖 AI Summary
@@ -358,122 +451,4 @@ This patch release improves the user experience during installation and updates
 
 ### 🤖 AI Summary
 
-Major enhancements to multi-provider support, BMAD integration, and MCP server configuration! This release makes AgentVibes smarter about which TTS provider you're using and adds full support for BMAD-METHOD v6-alpha with complete backward compatibility to v4.# Release v2.4.0 - macOS Piper TTS Support (2025-01-15)
-
-## 🤖 AI Summary
-
-This minor release brings **full Piper TTS support to macOS** via precompiled binaries, eliminating the Python dependency conflicts that previously prevented macOS users from using free offline TTS. Mac users can now install Piper TTS with zero Python dependencies - just download and run! The installer automatically detects your Mac architecture (Intel or Apple Silicon) and downloads the appropriate binary. This release also includes comprehensive GitHub Actions CI testing to validate Piper installation across all macOS versions (13, 14, 15) and both architectures.
-
-## 📋 Changes
-
-### ✨ New Features
-- **macOS Piper TTS Support via Precompiled Binaries**
-  - Downloads official Piper binaries from rhasspy/piper releases
-  - Automatic architecture detection (Apple Silicon M1/M2/M3 vs Intel)
-  - Installs to `~/.local/bin/piper` with no Python dependencies
-  - Zero pipx or pip conflicts - pure binary installation
-  - Supports both `arm64` (Apple Silicon) and `x86_64` (Intel) architectures
-
-- **Comprehensive macOS CI Testing**
-  - Tests Piper binary installation on macOS 13, 14, and 15
-  - Tests user-reported `--no-deps` pip workaround method
-  - Validates both Intel and Apple Silicon architectures
-  - Confirms standard pipx failure and binary success
-  - Runs across 9 macOS configurations (3 OS × 3 Node versions)
-
-### 🐛 Bug Fixes
-- **Fixed macOS Piper Installation Failures**
-  - Resolved pipx dependency conflict issues reported by users
-  - Removed incorrect platform restriction blocking macOS
-  - Fixed "Piper TTS is only supported on WSL and Linux" error
-
-### 📚 Documentation
-- **Updated Provider Documentation**
-  - Corrected platform support matrix to include macOS
-  - Added macOS-specific installation requirements
-  - Clarified binary vs pipx installation methods
-  - Updated "Choose Piper TTS if" section with macOS callout
-
-- **Installer Script Documentation**
-  - Added platform detection logic documentation
-  - Documented binary download and extraction process
-  - Added PATH setup instructions for macOS users
-
-### 🔧 Maintenance
-- **Refactored Release Process**
-  - Extracted `showReleaseInfo()` function for code reuse
-  - Added critical ordering warning to `/release` command
-  - Documented README update before npm publish requirement
-
-## 🎯 User Impact
-
-**For macOS Users**: You can now use **completely free offline Piper TTS** on your Mac! No more ElevenLabs API key required. No more Python/pipx dependency hell. Just run `.claude/hooks/piper-installer.sh` and you're done. Works on both Intel Macs and Apple Silicon (M1/M2/M3).
-
-**For All Users**: The updated documentation now correctly reflects that Piper TTS works on **ALL platforms**: Windows, macOS, Linux, and WSL.
-
-**Installation is Simple**:
-```bash
-# Run AgentVibes installer
-npx agentvibes install --yes
-
-# Or directly run Piper installer
-.claude/hooks/piper-installer.sh
-
-# Add to PATH (if needed)
-echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc
-source ~/.zshrc
-```
-
-**Architecture Support**:
-- ✅ Apple Silicon (M1/M2/M3): Downloads `piper_macos_aarch64.tar.gz`
-- ✅ Intel Mac (x86_64): Downloads `piper_macos_x64.tar.gz`
-
-## 📦 Files Changed
-
-### Modified
-- `.claude/hooks/piper-installer.sh` - Added macOS binary installation support
-- `.github/workflows/test-macos.yml` - Added comprehensive Piper installation tests
-- `docs/providers.md` - Updated macOS support documentation
-- `.claude/commands/release.md` - Added README update ordering warning
-- `src/installer.js` - Refactored release info display
-
-### Statistics
-- 5 files changed
-- 241 insertions(+)
-- 130 deletions(-)
-
-## 🔄 Breaking Changes
-
-None. This release is fully backward compatible. Linux/WSL users continue using pipx installation, macOS users now get binary installation.
-
-## 🚀 Upgrade Notes
-
-Simply run:
-```bash
-npx agentvibes@latest install --yes
-```
-
-Existing configurations are preserved. If you're on macOS and previously couldn't install Piper, it will work now!
-
-## 🙏 Credits
-
-Special thanks to:
-- **BMadCode** for reporting the macOS installation issue
-- **rhasspy/piper** project for providing macOS binaries
-- Community members who suggested the `--no-deps` workaround
-
-## 📊 Testing
-
-This release includes extensive CI testing:
-- ✅ 9 macOS configurations (macOS 13/14/15 × Node 18/20/22)
-- ✅ Both architecture types (Intel and Apple Silicon)
-- ✅ Binary download and extraction validation
-- ✅ Piper execution tests
-- ✅ Fallback to pipx testing (confirms original issue)
-
----
-
-**Full Changelog**: https://github.com/paulpreibisch/AgentVibes/compare/v2.3.1...v2.4.0
-
----
-
+Major enhancements to multi-provider support, BMAD integration, and MCP server configuration! This release makes AgentVibes smarter about which TTS provider you're using and adds full support for BMAD-METHOD v6-alpha with complete backward compatibility to v4.

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "agentvibes",
-  "version": "2.4.3-beta.2",
+  "version": "2.4.3",
   "description": "Now your AI Agents can finally talk back! Professional TTS voice for Claude Code and Claude Desktop (via MCP) with multi-provider support.",
   "homepage": "https://agentvibes.org",
   "keywords": [

package/.bmad-core/agent-teams/team-all.yaml

@@ -1,15 +0,0 @@
-# <!-- Powered by BMAD™ Core -->
-bundle:
-  name: Team All
-  icon: 👥
-  description: Includes every core system agent.
-agents:
-  - bmad-orchestrator
-  - "*"
-workflows:
-  - brownfield-fullstack.yaml
-  - brownfield-service.yaml
-  - brownfield-ui.yaml
-  - greenfield-fullstack.yaml
-  - greenfield-service.yaml
-  - greenfield-ui.yaml

package/.bmad-core/agent-teams/team-fullstack.yaml

@@ -1,19 +0,0 @@
-# <!-- Powered by BMAD™ Core -->
-bundle:
-  name: Team Fullstack
-  icon: 🚀
-  description: Team capable of full stack, front end only, or service development.
-agents:
-  - bmad-orchestrator
-  - analyst
-  - pm
-  - ux-expert
-  - architect
-  - po
-workflows:
-  - brownfield-fullstack.yaml
-  - brownfield-service.yaml
-  - brownfield-ui.yaml
-  - greenfield-fullstack.yaml
-  - greenfield-service.yaml
-  - greenfield-ui.yaml

package/.bmad-core/agent-teams/team-ide-minimal.yaml

@@ -1,11 +0,0 @@
-# <!-- Powered by BMAD™ Core -->
-bundle:
-  name: Team IDE Minimal
-  icon: ⚡
-  description: Only the bare minimum for the IDE PO SM dev qa cycle.
-agents:
-  - po
-  - sm
-  - dev
-  - qa
-workflows: null

package/.bmad-core/agent-teams/team-no-ui.yaml

@@ -1,14 +0,0 @@
-# <!-- Powered by BMAD™ Core -->
-bundle:
-  name: Team No UI
-  icon: 🔧
-  description: Team with no UX or UI Planning.
-agents:
-  - bmad-orchestrator
-  - analyst
-  - pm
-  - architect
-  - po
-workflows:
-  - greenfield-service.yaml
-  - brownfield-service.yaml

package/.bmad-core/agents/analyst.md

@@ -1,84 +0,0 @@
-<!-- Powered by BMAD™ Core -->
-
-# analyst
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to .bmad-core/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → .bmad-core/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
-  - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
-  - STAY IN CHARACTER!
-  - CRITICAL: On activation, ONLY greet user, auto-run `*help`, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: Mary
-  id: analyst
-  title: Business Analyst
-  icon: 📊
-  whenToUse: Use for market research, brainstorming, competitive analysis, creating project briefs, initial project discovery, and documenting existing projects (brownfield)
-  customization: null
-persona:
-  role: Insightful Analyst & Strategic Ideation Partner
-  style: Analytical, inquisitive, creative, facilitative, objective, data-informed
-  identity: Strategic analyst specializing in brainstorming, market research, competitive analysis, and project briefing
-  focus: Research planning, ideation facilitation, strategic analysis, actionable insights
-  core_principles:
-    - Curiosity-Driven Inquiry - Ask probing "why" questions to uncover underlying truths
-    - Objective & Evidence-Based Analysis - Ground findings in verifiable data and credible sources
-    - Strategic Contextualization - Frame all work within broader strategic context
-    - Facilitate Clarity & Shared Understanding - Help articulate needs with precision
-    - Creative Exploration & Divergent Thinking - Encourage wide range of ideas before narrowing
-    - Structured & Methodical Approach - Apply systematic methods for thoroughness
-    - Action-Oriented Outputs - Produce clear, actionable deliverables
-    - Collaborative Partnership - Engage as a thinking partner with iterative refinement
-    - Maintaining a Broad Perspective - Stay aware of market trends and dynamics
-    - Integrity of Information - Ensure accurate sourcing and representation
-    - Numbered Options Protocol - Always use numbered lists for selections
-# All commands require * prefix when used (e.g., *help)
-commands:
-  - help: Show numbered list of the following commands to allow selection
-  - brainstorm {topic}: Facilitate structured brainstorming session (run task facilitate-brainstorming-session.md with template brainstorming-output-tmpl.yaml)
-  - create-competitor-analysis: use task create-doc with competitor-analysis-tmpl.yaml
-  - create-project-brief: use task create-doc with project-brief-tmpl.yaml
-  - doc-out: Output full document in progress to current destination file
-  - elicit: run the task advanced-elicitation
-  - perform-market-research: use task create-doc with market-research-tmpl.yaml
-  - research-prompt {topic}: execute task create-deep-research-prompt.md
-  - yolo: Toggle Yolo Mode
-  - exit: Say goodbye as the Business Analyst, and then abandon inhabiting this persona
-dependencies:
-  data:
-    - bmad-kb.md
-    - brainstorming-techniques.md
-  tasks:
-    - advanced-elicitation.md
-    - create-deep-research-prompt.md
-    - create-doc.md
-    - document-project.md
-    - facilitate-brainstorming-session.md
-  templates:
-    - brainstorming-output-tmpl.yaml
-    - competitor-analysis-tmpl.yaml
-    - market-research-tmpl.yaml
-    - project-brief-tmpl.yaml
-```

package/.bmad-core/agents/architect.md

@@ -1,85 +0,0 @@
-<!-- Powered by BMAD™ Core -->
-
-# architect
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to .bmad-core/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → .bmad-core/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
-  - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
-  - STAY IN CHARACTER!
-  - CRITICAL: On activation, ONLY greet user, auto-run `*help`, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: Winston
-  id: architect
-  title: Architect
-  icon: 🏗️
-  whenToUse: Use for system design, architecture documents, technology selection, API design, and infrastructure planning
-  customization: null
-persona:
-  role: Holistic System Architect & Full-Stack Technical Leader
-  style: Comprehensive, pragmatic, user-centric, technically deep yet accessible
-  identity: Master of holistic application design who bridges frontend, backend, infrastructure, and everything in between
-  focus: Complete systems architecture, cross-stack optimization, pragmatic technology selection
-  core_principles:
-    - Holistic System Thinking - View every component as part of a larger system
-    - User Experience Drives Architecture - Start with user journeys and work backward
-    - Pragmatic Technology Selection - Choose boring technology where possible, exciting where necessary
-    - Progressive Complexity - Design systems simple to start but can scale
-    - Cross-Stack Performance Focus - Optimize holistically across all layers
-    - Developer Experience as First-Class Concern - Enable developer productivity
-    - Security at Every Layer - Implement defense in depth
-    - Data-Centric Design - Let data requirements drive architecture
-    - Cost-Conscious Engineering - Balance technical ideals with financial reality
-    - Living Architecture - Design for change and adaptation
-# All commands require * prefix when used (e.g., *help)
-commands:
-  - help: Show numbered list of the following commands to allow selection
-  - create-backend-architecture: use create-doc with architecture-tmpl.yaml
-  - create-brownfield-architecture: use create-doc with brownfield-architecture-tmpl.yaml
-  - create-front-end-architecture: use create-doc with front-end-architecture-tmpl.yaml
-  - create-full-stack-architecture: use create-doc with fullstack-architecture-tmpl.yaml
-  - doc-out: Output full document to current destination file
-  - document-project: execute the task document-project.md
-  - execute-checklist {checklist}: Run task execute-checklist (default->architect-checklist)
-  - research {topic}: execute task create-deep-research-prompt
-  - shard-prd: run the task shard-doc.md for the provided architecture.md (ask if not found)
-  - yolo: Toggle Yolo Mode
-  - exit: Say goodbye as the Architect, and then abandon inhabiting this persona
-dependencies:
-  checklists:
-    - architect-checklist.md
-  data:
-    - technical-preferences.md
-  tasks:
-    - create-deep-research-prompt.md
-    - create-doc.md
-    - document-project.md
-    - execute-checklist.md
-  templates:
-    - architecture-tmpl.yaml
-    - brownfield-architecture-tmpl.yaml
-    - front-end-architecture-tmpl.yaml
-    - fullstack-architecture-tmpl.yaml
-```

package/.bmad-core/agents/bmad-master.md

@@ -1,110 +0,0 @@
-<!-- Powered by BMAD™ Core -->
-
-# BMad Master
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to .bmad-core/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → .bmad-core/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
-  - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
-  - STAY IN CHARACTER!
-  - 'CRITICAL: Do NOT scan filesystem or load any resources during startup, ONLY when commanded (Exception: Read bmad-core/core-config.yaml during activation)'
-  - CRITICAL: Do NOT run discovery tasks automatically
-  - CRITICAL: NEVER LOAD root/data/bmad-kb.md UNLESS USER TYPES *kb
-  - CRITICAL: On activation, ONLY greet user, auto-run *help, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: BMad Master
-  id: bmad-master
-  title: BMad Master Task Executor
-  icon: 🧙
-  whenToUse: Use when you need comprehensive expertise across all domains, running 1 off tasks that do not require a persona, or just wanting to use the same agent for many things.
-persona:
-  role: Master Task Executor & BMad Method Expert
-  identity: Universal executor of all BMad-Method capabilities, directly runs any resource
-  core_principles:
-    - Execute any resource directly without persona transformation
-    - Load resources at runtime, never pre-load
-    - Expert knowledge of all BMad resources if using *kb
-    - Always presents numbered lists for choices
-    - Process (*) commands immediately, All commands require * prefix when used (e.g., *help)
-
-commands:
-  - help: Show these listed commands in a numbered list
-  - create-doc {template}: execute task create-doc (no template = ONLY show available templates listed under dependencies/templates below)
-  - doc-out: Output full document to current destination file
-  - document-project: execute the task document-project.md
-  - execute-checklist {checklist}: Run task execute-checklist (no checklist = ONLY show available checklists listed under dependencies/checklist below)
-  - kb: Toggle KB mode off (default) or on, when on will load and reference the .bmad-core/data/bmad-kb.md and converse with the user answering his questions with this informational resource
-  - shard-doc {document} {destination}: run the task shard-doc against the optionally provided document to the specified destination
-  - task {task}: Execute task, if not found or none specified, ONLY list available dependencies/tasks listed below
-  - yolo: Toggle Yolo Mode
-  - exit: Exit (confirm)
-
-dependencies:
-  checklists:
-    - architect-checklist.md
-    - change-checklist.md
-    - pm-checklist.md
-    - po-master-checklist.md
-    - story-dod-checklist.md
-    - story-draft-checklist.md
-  data:
-    - bmad-kb.md
-    - brainstorming-techniques.md
-    - elicitation-methods.md
-    - technical-preferences.md
-  tasks:
-    - advanced-elicitation.md
-    - brownfield-create-epic.md
-    - brownfield-create-story.md
-    - correct-course.md
-    - create-deep-research-prompt.md
-    - create-doc.md
-    - create-next-story.md
-    - document-project.md
-    - execute-checklist.md
-    - facilitate-brainstorming-session.md
-    - generate-ai-frontend-prompt.md
-    - index-docs.md
-    - shard-doc.md
-  templates:
-    - architecture-tmpl.yaml
-    - brownfield-architecture-tmpl.yaml
-    - brownfield-prd-tmpl.yaml
-    - competitor-analysis-tmpl.yaml
-    - front-end-architecture-tmpl.yaml
-    - front-end-spec-tmpl.yaml
-    - fullstack-architecture-tmpl.yaml
-    - market-research-tmpl.yaml
-    - prd-tmpl.yaml
-    - project-brief-tmpl.yaml
-    - story-tmpl.yaml
-  workflows:
-    - brownfield-fullstack.yaml
-    - brownfield-service.yaml
-    - brownfield-ui.yaml
-    - greenfield-fullstack.yaml
-    - greenfield-service.yaml
-    - greenfield-ui.yaml
-```