agentvibes 2.9.7 → 2.12.0

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/README-personality-defaults.md

@@ -1,162 +0,0 @@
-# Personality Voice Defaults
-
-## What is this?
-
-This configuration file (`personality-voice-defaults.json`) maps each AgentVibes personality to a specific Piper TTS voice that sounds best for that character.
-
-## How it works for new users
-
-When someone installs AgentVibes with Piper TTS:
-
-### 1. Installation Process
-
-```bash
-# User installs Piper
-.claude/hooks/piper-installer.sh
-```
-
-**What happens:**
-- Piper TTS binary gets installed via `pipx`
-- User is asked: "Download voice models now?"
-- If yes, runs `piper-download-voices.sh` which downloads:
-  - **16Speakers** (~25MB) - Multi-voice model with 16 speakers
-  - **en_GB-alan-medium** (~25MB) - British male voice
-  - **en_GB-semaine-medium** (~25MB) - British female voice
-  - Plus a few other standard voices
-- Default personality mappings are installed automatically
-
-### 2. What gets downloaded
-
-**Required voices for personality defaults:**
-- ✅ **16Speakers** (1 file) - Provides 16 different speakers:
-  - #0: Cori Samuel (female) - Used for: flirty, dramatic, dry_humor, sassy
-  - #2: Kristin Hughes (female) - Used for: poetic, sarcastic
-  - #4: Mike Pelton (male) - Used for: grandpa
-  - #8: Rose Ibex (female) - Used for: moody
-  - #13: Jennifer Dorr (female) - Used for: millennial
-  - #14: Emily Cripps (female) - Used for: zen
-  - #15: Martin Clifton (male) - Used for: pirate
-
-- ✅ **en_GB-alan-medium** - British male voice
-  - Used for: angry, professional, surfer_dude
-
-- ✅ **en_GB-semaine-medium** - British female voice
-  - Used for: funny
-
-**Total download size: ~75MB** (3 voice models)
-
-### 3. First time using a personality
-
-```bash
-# User switches personality
-/agent-vibes:personality flirty
-```
-
-**What happens:**
-1. AgentVibes reads `personality-voice-defaults.json`
-2. Finds that "flirty" → "16Speakers#0" (Cori Samuel)
-3. Checks if 16Speakers is downloaded
-4. **If not downloaded:**
-   - Prompts: "Voice model not found: 16Speakers. Download? [y/N]"
-   - User says yes → Downloads automatically from HuggingFace
-   - Only happens once per voice model
-5. **If already downloaded:**
-   - Switches to the voice immediately
-   - Plays personality-appropriate TTS
-
-### 4. Graceful fallbacks
-
-If a user:
-- Skips voice downloads during install → On-demand download when needed
-- Deletes the defaults file → Falls back to basic `en_US-lessac-medium`
-- Uses a personality without a mapping → Uses default voice
-
-## For power users
-
-### Customizing defaults
-
-Edit `.claude/personality-voice-defaults.json`:
-
-```json
-{
-  "mappings": {
-    "flirty": {
-      "voice": "16Speakers#0",
-      "rating": 10,
-      "display_name": "Cori Samuel"
-    }
-  }
-}
-```
-
-Change the `voice` field to any Piper voice name.
-
-### Using the voice tester
-
-1. Run the voice tester (in `voice-tester/` folder)
-2. Rate voices for each personality
-3. Export ratings as JSON
-4. Import with: `./import-voice-ratings.sh my-ratings.json`
-
-### Available voices
-
-List all Piper voices: https://huggingface.co/rhasspy/piper-voices
-
-Any voice can be used - AgentVibes will download it on first use.
-
-## FAQ
-
-**Q: Do new users need to download all voices upfront?**
-A: No! Only 3 files (~75MB total) are recommended. Others download on-demand.
-
-**Q: What if a user doesn't download any voices?**
-A: First personality switch will prompt to download the needed voice.
-
-**Q: Can users change the defaults?**
-A: Yes! Edit the JSON file or use the voice tester to rate and export new preferences.
-
-**Q: What if 16Speakers isn't available?**
-A: It's hosted on AgentVibes HuggingFace and included in the download script.
-
-**Q: What happens on slow connections?**
-A: Each voice is ~25MB. Downloads are one-time only and optional.
-
-## Architecture
-
-```
-Installation Flow:
-1. User runs piper-installer.sh
-   ↓
-2. Piper binary installed via pipx
-   ↓
-3. Ask: "Download voices?" → Yes
-   ↓
-4. piper-download-voices.sh runs
-   - Downloads 16Speakers (custom, HuggingFace)
-   - Downloads en_GB-alan-medium (official Piper)
-   - Downloads en_GB-semaine-medium (official Piper)
-   - Downloads other optional voices
-   ↓
-5. install-personality-defaults.sh runs
-   - Copies personality-voice-defaults.json to user config
-   ↓
-6. Ready! Personalities now auto-select best voices
-
-Runtime Flow:
-User: /agent-vibes:personality flirty
-   ↓
-personality-manager.sh checks:
-   1. User defaults (.claude/personality-voice-defaults.json)
-   2. Personality file (piper_voice: field)
-   3. Global default (en_US-lessac-medium)
-   ↓
-Found: 16Speakers#0
-   ↓
-Check if downloaded → Yes
-   ↓
-Switch to voice & play TTS!
-```
-
-## Credits
-
-Voice selections curated by Paul Preibisch based on extensive testing with the AgentVibes voice tester (16 personalities × 19 voices).

package/.claude/config/agentvibes.json

@@ -1 +0,0 @@
-{"pretext": "AgentVibes"}

package/.claude/config/bmad-voices.md

@@ -1,68 +0,0 @@
----
-plugin: bmad-voices
-version: 2.0.0
-enabled: true
-description: Provider-aware voice mappings for BMAD agents
----
-
-# BMAD Voice Plugin
-
-This plugin automatically assigns voices to BMAD agents based on their role and active TTS provider.
-
-## Agent Voice Mappings (Provider-Aware)
-
-| Agent ID | Agent Name | Intro | ElevenLabs Voice | Piper Voice | Personality |
-|----------|------------|-------|------------------|-------------|-------------|
-| pm | John (Product Manager) | John, Product Manager here | Matthew Schmitz | en_US-ryan-high | professional |
-| dev | Amelia (Developer) | Amelia, Developer here | Aria | en_US-amy-medium | normal |
-| analyst | Mary (Business Analyst) | Mary, Business Analyst here | Jessica Anne Bogart | kristin | normal |
-| architect | Winston (Architect) | Winston, Architect here | Michael | en_GB-alan-medium | normal |
-| sm | Bob (Scrum Master) | Bob, Scrum Master here | Matthew Schmitz | en_US-joe-medium | professional |
-| tea | Murat (Test Architect) | Murat, Test Architect here | Michael | en_US-arctic-medium | normal |
-| tech-writer | Paige (Technical Writer) | Paige, Technical Writer here | Aria | jenny | normal |
-| ux-designer | Sally (UX Designer) | Sally, UX Designer here | Jessica Anne Bogart | en_US-lessac-medium | normal |
-| frame-expert | Saif (Visual Designer) | Saif, Visual Designer here | Matthew Schmitz | en_GB-alan-medium | normal |
-| bmad-master | BMad Master | BMad Master here | Michael | en_US-danny-low | zen |
-
-## How It Works
-
-The voice manager automatically selects the appropriate voice based on your active TTS provider:
-- **ElevenLabs active**: Uses voices from the "ElevenLabs Voice" column
-- **Piper active**: Uses voices from the "Piper Voice" column
-
-This ensures BMAD agents work seamlessly regardless of which provider you're using.
-
-### Supports Both Display Names and Agent IDs
-
-The `bmad-speak.sh` script accepts both formats:
-
-**Party Mode** (multiple agents, uses display names):
-```bash
-.claude/hooks/bmad-speak.sh "Winston" "I recommend microservices for scalability"
-```
-
-**Individual Agents** (single agent sessions, uses agent IDs):
-```bash
-.claude/hooks/bmad-speak.sh "architect" "I recommend microservices for scalability"
-```
-
-Both formats map to the same voice configuration based on the agent ID in the table above. This allows BMAD to use customizable display names while maintaining stable voice mappings.
-
-## How to Edit
-
-Simply edit the table above to change voice mappings. The format is:
-- **Agent ID**: Must match BMAD's `agent.id` field (pm, dev, qa, etc.)
-- **Agent Name**: Display name (for reference only)
-- **Intro**: Text spoken before agent's message (e.g., "John, Product Manager here"). Leave empty to disable.
-- **ElevenLabs Voice**: Voice name for ElevenLabs provider
-- **Piper Voice**: Voice model name for Piper provider
-- **Personality**: Optional personality to apply (or "normal" for none)
-
-## Commands
-
-- `/agent-vibes:bmad enable` - Enable BMAD voice plugin
-- `/agent-vibes:bmad disable` - Disable BMAD voice plugin
-- `/agent-vibes:bmad status` - Show plugin status
-- `/agent-vibes:bmad edit` - Open this file for editing
-- `/agent-vibes:bmad list` - List all agent voice mappings
-- `/agent-vibes:bmad set <agent-id> <elevenlabs-voice> <piper-voice> [personality]` - Set voices for specific agent

package/.claude/config/personality-voice-defaults.default.json

@@ -1,21 +0,0 @@
-{
-  "version": "1.0",
-  "description": "Default Piper voice assignments for each personality",
-  "mappings": {
-    "angry": {"voice": "en_GB-alan-medium", "rating": 10, "display_name": "English GB - Alan"},
-    "dramatic": {"voice": "16Speakers#0", "rating": 10, "display_name": "Cori Samuel"},
-    "dry_humor": {"voice": "16Speakers#0", "rating": 10, "display_name": "Cori Samuel"},
-    "flirty": {"voice": "16Speakers#0", "rating": 10, "display_name": "Cori Samuel"},
-    "funny": {"voice": "en_GB-semaine-medium", "rating": 10, "display_name": "English GB - Semaine"},
-    "grandpa": {"voice": "16Speakers#4", "rating": 10, "display_name": "Mike Pelton"},
-    "millennial": {"voice": "16Speakers#13", "rating": 10, "display_name": "Jennifer Dorr"},
-    "moody": {"voice": "16Speakers#8", "rating": 10, "display_name": "Rose Ibex"},
-    "pirate": {"voice": "16Speakers#15", "rating": 10, "display_name": "Martin Clifton"},
-    "poetic": {"voice": "16Speakers#2", "rating": 10, "display_name": "Kristin Hughes"},
-    "professional": {"voice": "en_GB-alan-medium", "rating": 10, "display_name": "English GB - Alan"},
-    "sarcastic": {"voice": "16Speakers#2", "rating": 10, "display_name": "Kristin Hughes"},
-    "sassy": {"voice": "16Speakers#0", "rating": 10, "display_name": "Cori Samuel"},
-    "surfer_dude": {"voice": "en_GB-alan-medium", "rating": 10, "display_name": "English GB - Alan"},
-    "zen": {"voice": "16Speakers#14", "rating": 10, "display_name": "Emily Cripps"}
-  }
-}

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

@@ -1 +0,0 @@
-20251120