agentvibes 2.17.1 → 2.17.2

package/.claude/commands/bmad/bmm/workflows/research.md

@@ -1,13 +0,0 @@
----
-description: 'Adaptive research workflow supporting multiple research types: market research, deep research prompt generation, technical/architecture evaluation, competitive intelligence, user research, and domain analysis'
----
-
-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 @.bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/1-analysis/research/workflow.yaml
-3. Pass the yaml path .bmad/bmm/workflows/1-analysis/research/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/.claude/commands/bmad/bmm/workflows/retrospective.md

@@ -1,13 +0,0 @@
----
-description: 'Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic'
----
-
-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 @.bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml
-3. Pass the yaml path .bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/.claude/commands/bmad/bmm/workflows/sprint-planning.md

@@ -1,13 +0,0 @@
----
-description: 'Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle'
----
-
-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 @.bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml
-3. Pass the yaml path .bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/.claude/commands/bmad/bmm/workflows/story-context.md

@@ -1,13 +0,0 @@
----
-description: 'Assemble a dynamic Story Context XML by pulling latest documentation and existing code/library artifacts relevant to a drafted story'
----
-
-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 @.bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/4-implementation/story-context/workflow.yaml
-3. Pass the yaml path .bmad/bmm/workflows/4-implementation/story-context/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/.claude/commands/bmad/bmm/workflows/story-done.md

@@ -1,13 +0,0 @@
----
-description: 'Marks a story as done (DoD complete) and moves it from its current status → DONE in the status file. Advances the story queue. Simple status-update workflow with no searching required.'
----
-
-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 @.bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/4-implementation/story-done/workflow.yaml
-3. Pass the yaml path .bmad/bmm/workflows/4-implementation/story-done/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/.claude/commands/bmad/bmm/workflows/story-ready.md

@@ -1,13 +0,0 @@
----
-description: 'Marks a drafted story as ready for development and moves it from TODO → IN PROGRESS in the status file. Simple status-update workflow with no searching required.'
----
-
-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 @.bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/4-implementation/story-ready/workflow.yaml
-3. Pass the yaml path .bmad/bmm/workflows/4-implementation/story-ready/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/.claude/commands/bmad/bmm/workflows/tech-spec.md

@@ -1,13 +0,0 @@
----
-description: 'Technical specification workflow for quick-flow projects. Creates focused tech spec and generates epic + stories (1 story for simple changes, 2-5 stories for features). Tech-spec only - no PRD needed.'
----
-
-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 @.bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml
-3. Pass the yaml path .bmad/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/.claude/commands/bmad/bmm/workflows/workflow-init.md

@@ -1,13 +0,0 @@
----
-description: 'Initialize a new BMM project by determining level, type, and creating workflow path'
----
-
-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 @.bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/workflow-status/init/workflow.yaml
-3. Pass the yaml path .bmad/bmm/workflows/workflow-status/init/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/.claude/commands/bmad/bmm/workflows/workflow-status.md

@@ -1,13 +0,0 @@
----
-description: 'Lightweight status checker - answers "what should I do now?" for any agent. Reads YAML status file for workflow tracking. Use workflow-init for new projects.'
----
-
-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 @.bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/workflow-status/workflow.yaml
-3. Pass the yaml path .bmad/bmm/workflows/workflow-status/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

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

@@ -1,14 +0,0 @@
----
-name: 'bmad-master'
-description: 'bmad-master agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from @.bmad/core/agents/bmad-master.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. Execute ALL activation steps exactly as written in the agent file
-4. Follow the agent's persona and menu system precisely
-5. Stay in character throughout the session
-</agent-activation>

package/.claude/commands/bmad/core/tasks/advanced-elicitation.md

@@ -1,9 +0,0 @@
----
-description: 'When called from workflow'
----
-
-# Advanced Elicitation
-
-LOAD and execute the task at: .bmad/core/tasks/advanced-elicitation.xml
-
-Follow all instructions in the task file exactly as written.

package/.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: .bmad/core/tasks/index-docs.xml
-
-Follow all instructions in the task file exactly as written.

package/.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: .bmad/core/tools/shard-doc.xml
-
-Follow all instructions in the tool file exactly as written.

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

@@ -1,13 +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.'
----
-
-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 @.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 to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

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

@@ -1,13 +0,0 @@
----
-description: 'Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations'
----
-
-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 @.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 to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/.claude/config/background-music-position.txt

@@ -1,25 +0,0 @@
-agent-vibes-dark-chill-step.mp3:49.006169
-Agent Vibes Japanese City Pop v1.mp3:29.392744
-Agent Vibes ChillWave v2.mp3:22.154467
-Agent Vibes Bossa Nova v2.mp3:23.733424
-Agent Vibes Tabla Dream Pop v1.mp3:19.101043
-Agent Vibes Hawaiian slack key guitar v2.mp3:36.381950
-AgentVibes Soft Flamenco.mp3:23.160000
-Agent Vibes Arabic v2.mp3:21.922268
-Agent Vibes Goa Trance v2.mp3:55.953741
-Agent Vibes Ganawa Ambient v2.mp3:39.680205
-Agent Vibes Celtic Harp v1.mp3:42.190476
-Agent Vibes Harpsichord v2.mp3:21.739410
-Agent Vibes Japanese City Pop v1-loop.mp3:13.917551
-Agent Vibes Hawaiian slack key guitar v2-loop.mp3:12.977143
-Agent Vibes Ganawa Ambient v2-loop.mp3:.00000000000000000002815996
-Agent Vibes Tabla Dream Pop v1-loop.mp3:.00000000000000000009067943
-Agent Vibes ChillWave v2-loop.mp3:.00000000000000000007080511
-Agent Vibes Harpsichord v2-loop.mp3:.00000000000000000013140818
-agent_vibes_japanese_city_pop_v1_loop.mp3:6.054512
-agent_vibes_bossa_nova_v2_loop.mp3:5.369524
-agent_vibes_salsa_v2_loop.mp3:9.972790
-agent_vibes_bachata_v1_loop.mp3:5.590113
-agent_vibes_cumbia_v1_loop.mp3:5.717823
-agentvibes_soft_flamenco_loop.mp3:10.948027
-agent_vibes_chillwave_v2_loop.mp3:6.286712

package/.claude/config/background-music-volume.txt

@@ -1 +0,0 @@
-0.30

package/.claude/config/background-music.cfg

@@ -1 +0,0 @@
-enabled

package/.claude/config/tts-verbosity.txt

@@ -1 +0,0 @@
-high

package/.claude/github-star-reminder.txt

@@ -1 +0,0 @@
-20251208

package/.claude/hooks/bmad-party-manager.sh

@@ -1,225 +0,0 @@
-#!/usr/bin/env bash
-#
-# File: .claude/hooks/bmad-party-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 Party Mode Voice Integration Manager
-# @context Controls auto-enable/disable of multi-agent voice switching during BMAD party mode
-# @architecture Opt-out flag management, auto-detection, status reporting
-# @dependencies .bmad/_cfg/agent-manifest.csv, bmad-voices-enabled.flag, user-prompt-output.sh
-# @entrypoints /agent-vibes:bmad-party slash command
-# @patterns Auto-enable with opt-out, graceful degradation, feature detection
-# @related user-prompt-output.sh, bmad-voice-manager.sh, Issue #33
-
-# Fix locale warnings
-export LC_ALL=C
-
-PLUGIN_DIR=".claude/plugins"
-DISABLE_FLAG="$PLUGIN_DIR/bmad-party-mode-disabled.flag"
-BMAD_VOICES_FLAG="$PLUGIN_DIR/bmad-voices-enabled.flag"
-BMAD_MANIFEST=".bmad/_cfg/agent-manifest.csv"
-
-# Colors
-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
-
-#
-# @function is_bmad_installed
-# @context Check if BMAD v6 is installed
-# @returns 0=installed, 1=not installed
-#
-is_bmad_installed() {
-  [[ -f "$BMAD_MANIFEST" ]]
-}
-
-#
-# @function is_bmad_voices_enabled
-# @context Check if BMAD voice plugin is enabled
-# @returns 0=enabled, 1=disabled
-#
-is_bmad_voices_enabled() {
-  [[ -f "$BMAD_VOICES_FLAG" ]]
-}
-
-#
-# @function is_party_mode_enabled
-# @context Check if party mode voice integration is enabled
-# @returns 0=enabled, 1=disabled
-#
-is_party_mode_enabled() {
-  # Disabled if opt-out flag exists
-  [[ -f "$DISABLE_FLAG" ]] && return 1
-
-  # Enabled if BMAD + voice plugin active
-  is_bmad_installed && is_bmad_voices_enabled
-}
-
-#
-# @function show_status
-# @context Display current party mode voice integration status
-#
-show_status() {
-  echo -e "${CYAN}🎭 BMAD Party Mode Voice Integration${NC}"
-  echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-  echo ""
-
-  # Check BMAD installation
-  if ! is_bmad_installed; then
-    echo -e "${RED}❌ BMAD not installed${NC}"
-    echo -e "${GRAY}   Party mode voice integration requires BMAD v6${NC}"
-    echo -e "${GRAY}   Install: https://github.com/bmad-method/bmad${NC}"
-    echo ""
-    return 1
-  fi
-
-  echo -e "${GREEN}✅ BMAD v6 detected${NC}"
-
-  # Check voice plugin
-  if ! is_bmad_voices_enabled; then
-    echo -e "${RED}❌ BMAD voice plugin disabled${NC}"
-    echo -e "${GRAY}   Enable: /agent-vibes:bmad enable${NC}"
-    echo ""
-    return 1
-  fi
-
-  echo -e "${GREEN}✅ BMAD voice plugin enabled${NC}"
-
-  # Check party mode status
-  if is_party_mode_enabled; then
-    echo -e "${GREEN}✅ Party mode voices: ENABLED${NC}"
-    echo ""
-    echo -e "${CYAN}How it works:${NC}"
-    echo "  When you run /bmad:core:workflows:party-mode,"
-    echo "  each agent speaks with their unique voice:"
-    echo ""
-    echo "  🏗️  Winston (Architect) → Michael"
-    echo "  📋 John (PM) → Jessica Anne Bogart"
-    echo "  💻 Amelia (Dev) → Matthew Schmitz"
-    echo "  📊 Mary (Analyst) → kristin"
-    echo "  ... and more!"
-    echo ""
-    echo -e "${GRAY}Disable with: /agent-vibes:bmad-party disable${NC}"
-  else
-    echo -e "${YELLOW}⚠️  Party mode voices: DISABLED (opt-out active)${NC}"
-    echo ""
-    echo -e "${GRAY}Enable with: /agent-vibes:bmad-party enable${NC}"
-  fi
-
-  echo ""
-}
-
-#
-# @function enable_party_mode
-# @context Enable party mode voice integration (remove opt-out flag)
-#
-enable_party_mode() {
-  # Verify prerequisites
-  if ! is_bmad_installed; then
-    echo -e "${RED}❌ Cannot enable: BMAD not installed${NC}"
-    echo -e "${GRAY}   Install BMAD v6 first${NC}"
-    return 1
-  fi
-
-  if ! is_bmad_voices_enabled; then
-    echo -e "${RED}❌ Cannot enable: BMAD voice plugin disabled${NC}"
-    echo -e "${GRAY}   Enable with: /agent-vibes:bmad enable${NC}"
-    return 1
-  fi
-
-  # Remove opt-out flag if it exists
-  if [[ -f "$DISABLE_FLAG" ]]; then
-    rm -f "$DISABLE_FLAG"
-    echo -e "${GREEN}✅ Party mode voices enabled${NC}"
-    echo ""
-    echo -e "${CYAN}🎭 Multi-agent voice switching activated!${NC}"
-    echo "   Run /bmad:core:workflows:party-mode to hear agents speak"
-  else
-    echo -e "${GREEN}✅ Party mode voices already enabled${NC}"
-    echo ""
-    echo -e "${GRAY}(Auto-enabled when BMAD detected)${NC}"
-  fi
-
-  echo ""
-}
-
-#
-# @function disable_party_mode
-# @context Disable party mode voice integration (create opt-out flag)
-#
-disable_party_mode() {
-  mkdir -p "$PLUGIN_DIR"
-
-  if [[ -f "$DISABLE_FLAG" ]]; then
-    echo -e "${YELLOW}⚠️  Party mode voices already disabled${NC}"
-    return 0
-  fi
-
-  # Create opt-out flag
-  touch "$DISABLE_FLAG"
-
-  echo -e "${GREEN}✅ Party mode voices disabled${NC}"
-  echo ""
-  echo -e "${GRAY}Party mode will continue to work, but agents won't speak${NC}"
-  echo -e "${GRAY}Enable again with: /agent-vibes:bmad-party enable${NC}"
-  echo ""
-}
-
-# Main command dispatcher
-case "${1:-status}" in
-  enable)
-    enable_party_mode
-    ;;
-  disable)
-    disable_party_mode
-    ;;
-  status)
-    show_status
-    ;;
-  *)
-    echo -e "${CYAN}AgentVibes BMAD Party Mode Manager${NC}"
-    echo ""
-    echo "Usage: bmad-party-manager.sh {enable|disable|status}"
-    echo ""
-    echo "Commands:"
-    echo "  enable     Enable party mode voice integration"
-    echo "  disable    Disable party mode voice integration (opt-out)"
-    echo "  status     Show current status and configuration"
-    echo ""
-    echo "Party Mode Voice Integration:"
-    echo "  • Auto-enabled when BMAD v6 detected"
-    echo "  • Each agent speaks with unique voice during party mode"
-    echo "  • Opt-out available via disable command"
-    ;;
-esac

package/.claude/piper-voices-dir.txt

@@ -1 +0,0 @@
-/home/fire/.claude/piper-voices

package/.mcp.json

@@ -1,23 +0,0 @@
-{
-  "mcpServers": {
-    "sonarqube": {
-      "command": "docker",
-      "args": [
-        "run",
-        "-i",
-        "--name",
-        "sonarqube-mcp-server-agentvibes",
-        "--rm",
-        "-e",
-        "SONARQUBE_TOKEN",
-        "-e",
-        "SONARQUBE_ORG",
-        "mcp/sonarqube"
-      ],
-      "env": {
-        "SONARQUBE_TOKEN": "${AGENTVIBES_SONARQUBE_TOKEN}",
-        "SONARQUBE_ORG": "${AGENTVIBES_SONARQUBE_ORG}"
-      }
-    }
-  }
-}