agentvibes 3.1.0 → 3.2.0

package/.claude/commands/bmad/bmm/workflows/{create-wireframe.md → create-excalidraw-wireframe.md}

@@ -6,8 +6,8 @@ IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the c
 
 <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/frame-expert/create-wireframe/workflow.yaml
-3. Pass the yaml path .bmad/bmm/workflows/frame-expert/create-wireframe/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/diagrams/create-wireframe/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/diagrams/create-wireframe/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/create-prd.md

@@ -0,0 +1,5 @@
+---
+description: 'Creates a comprehensive PRDs through collaborative step-by-step discovery between two product managers working as peers.'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmm/workflows/2-plan-workflows/prd/workflow.md, READ its entire contents and follow its directions exactly!

package/.claude/commands/bmad/bmm/workflows/create-product-brief.md

@@ -0,0 +1,5 @@
+---
+description: 'Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmm/workflows/1-analysis/product-brief/workflow.md, READ its entire contents and follow its directions exactly!

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

@@ -1,5 +1,5 @@
 ---
-description: 'Create the next user story markdown from epics/PRD and architecture, using a standard template and saving to the stories folder'
+description: 'Create the next user story from epics+stories with enhanced context analysis and direct ready-for-dev marking'
 ---
 
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:

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

@@ -0,0 +1,13 @@
+---
+description: 'Conversational spec engineering - ask questions, investigate code, produce implementation-ready tech-spec.'
+---
+
+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/bmad-quick-flow/create-tech-spec/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/bmad-quick-flow/create-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/create-ux-design.md

@@ -1,13 +1,5 @@
 ---
-description: 'Collaborative UX design facilitation workflow that creates exceptional user experiences through visual exploration and informed decision-making. Unlike template-driven approaches, this workflow facilitates discovery, generates visual options, and collaboratively designs the UX with the user at every step.'
+description: 'Work with a peer UX Design expert to plan your applications UX patterns, look and feel.'
 ---
 
-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/create-ux-design/workflow.yaml
-3. Pass the yaml path .bmad/bmm/workflows/2-plan-workflows/create-ux-design/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>
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md, READ its entire contents and follow its directions exactly!

package/.claude/commands/bmad/bmm/workflows/generate-project-context.md

@@ -0,0 +1,5 @@
+---
+description: 'Creates a concise project_context.md file with critical rules and patterns that AI agents must follow when implementing code. Optimized for LLM context efficiency.'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmm/workflows/generate-project-context/workflow.md, READ its entire contents and follow its directions exactly!

package/.claude/commands/bmad/bmm/workflows/{domain-research.md → quick-dev.md}

@@ -1,13 +1,13 @@
 ---
-description: 'Collaborative exploration of domain-specific requirements, regulations, and patterns for complex projects'
+description: 'Flexible development - execute tech-specs OR direct instructions with optional planning.'
 ---
 
 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/domain-research/workflow.yaml
-3. Pass the yaml path .bmad/bmm/workflows/1-analysis/domain-research/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/bmad-quick-flow/quick-dev/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/research.md

@@ -1,13 +1,5 @@
 ---
-description: 'Adaptive research workflow supporting multiple research types: market research, deep research prompt generation, technical/architecture evaluation, competitive intelligence, user research, and domain analysis'
+description: 'Conduct comprehensive research across multiple domains using current web data and verified sources - Market, Technical, Domain and other research types.'
 ---
 
-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>
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/bmm/workflows/1-analysis/research/workflow.md, READ its entire contents and follow its directions exactly!

package/.claude/commands/bmad/bmm/workflows/{story-context.md → sprint-status.md}

@@ -1,13 +1,13 @@
 ---
-description: 'Assemble a dynamic Story Context XML by pulling latest documentation and existing code/library artifacts relevant to a drafted story'
+description: 'Summarize sprint-status.yaml, surface risks, and route to the right implementation 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 @.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
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/4-implementation/sprint-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/bmm/workflows/testarch-atdd.md

@@ -0,0 +1,13 @@
+---
+description: 'Generate failing acceptance tests before implementation using TDD red-green-refactor cycle'
+---
+
+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/testarch/atdd/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/testarch/atdd/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/testarch-automate.md

@@ -0,0 +1,13 @@
+---
+description: 'Expand test automation coverage after implementation or analyze existing codebase to generate comprehensive test suite'
+---
+
+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/testarch/automate/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/testarch/automate/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/testarch-ci.md

@@ -0,0 +1,13 @@
+---
+description: 'Scaffold CI/CD quality pipeline with test execution, burn-in loops, and artifact collection'
+---
+
+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/testarch/ci/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/testarch/ci/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/testarch-framework.md

@@ -0,0 +1,13 @@
+---
+description: 'Initialize production-ready test framework architecture (Playwright or Cypress) with fixtures, helpers, and configuration'
+---
+
+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/testarch/framework/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/testarch/framework/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/testarch-nfr.md

@@ -0,0 +1,13 @@
+---
+description: 'Assess non-functional requirements (performance, security, reliability, maintainability) before release with evidence-based validation'
+---
+
+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/testarch/nfr-assess/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/testarch/nfr-assess/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/{prd.md → testarch-test-design.md}

@@ -1,13 +1,13 @@
 ---
-description: 'Unified PRD workflow for BMad Method and Enterprise Method tracks. Produces strategic PRD and tactical epic breakdown. Hands off to architecture workflow for technical design. Note: Quick Flow track uses tech-spec workflow.'
+description: 'Dual-mode workflow: (1) System-level testability review in Solutioning phase, or (2) Epic-level test planning in Implementation phase. Auto-detects mode based on project phase.'
 ---
 
 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/prd/workflow.yaml
-3. Pass the yaml path .bmad/bmm/workflows/2-plan-workflows/prd/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @.bmad/bmm/workflows/testarch/test-design/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/testarch/test-design/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/testarch-test-review.md

@@ -0,0 +1,13 @@
+---
+description: 'Review test quality using comprehensive knowledge base and best practices validation'
+---
+
+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/testarch/test-review/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/testarch/test-review/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/testarch-trace.md

@@ -0,0 +1,13 @@
+---
+description: 'Generate requirements-to-tests traceability matrix, analyze coverage, and make quality gate decision (PASS/CONCERNS/FAIL/WAIVED)'
+---
+
+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/testarch/trace/workflow.yaml
+3. Pass the yaml path .bmad/bmm/workflows/testarch/trace/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/brainstorming-session.md

@@ -0,0 +1,5 @@
+---
+description: 'Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods'
+---
+
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @.bmad/core/workflows/brainstorming/workflow.md, READ its entire contents and follow its directions exactly!

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

@@ -1 +1 @@
-20260122
+20260127

package/.clawdbot/README.md

@@ -0,0 +1,105 @@
+# Clawdbot Integration
+
+AgentVibes TTS integration for Clawdbot - the AI assistant framework.
+
+## What is Clawdbot?
+
+Clawdbot is a powerful AI assistant framework that connects Claude AI to messaging platforms (WhatsApp, Telegram, Discord, etc.) and provides extensible skills.
+
+**Website**: https://clawd.bot
+**GitHub**: https://github.com/clawdbot/clawdbot
+
+## AgentVibes + Clawdbot
+
+This integration provides Clawdbot with professional TTS capabilities using AgentVibes:
+
+- **Free & Offline**: No API costs, works without internet
+- **50+ Voices**: Professional AI voices in 30+ languages
+- **Remote SSH Support**: Audio tunnels from server to local machine
+- **Zero Setup**: Automatic when AgentVibes is installed
+
+## Installation
+
+```bash
+npx agentvibes install
+```
+
+That's it! AgentVibes is ready to use.
+
+## Usage from Clawdbot
+
+Once installed, use AgentVibes for TTS:
+
+```bash
+npx agentvibes speak "Hello from Clawdbot"
+```
+
+## Features
+
+- **Automatic Detection**: Clawdbot automatically uses AgentVibes when available
+- **Voice Selection**: 50+ voices across 30+ languages
+- **SSH Tunneling**: Audio plays on local machine from remote servers
+- **Zero Config**: Works out of the box once AgentVibes is installed
+
+## Remote SSH Audio
+
+When running Clawdbot on a remote server, set up PulseAudio tunneling so audio plays on your local machine:
+
+**Quick Setup:**
+
+1. **Remote server** (`~/.bashrc`):
+```bash
+export PULSE_SERVER=tcp:localhost:14713
+```
+
+2. **Local machine** (`~/.ssh/config`):
+```
+Host your-server
+    RemoteForward 14713 localhost:14713
+```
+
+3. **Connect and test**:
+```bash
+ssh your-server
+agentvibes speak "Testing remote audio"
+```
+
+**Full guide**: https://github.com/paulpreibisch/AgentVibes/blob/master/docs/remote-audio-setup.md
+
+## Documentation
+
+- **Skill Documentation**: [skill/SKILL.md](skill/SKILL.md)
+- **AgentVibes Docs**: https://agentvibes.org
+- **Clawdbot Docs**: https://docs.clawd.bot
+
+## Architecture
+
+```
+Clawdbot Request
+    ↓
+AgentVibes Skill (this)
+    ↓
+AgentVibes CLI (agentvibes speak)
+    ↓
+Piper TTS Engine
+    ↓
+PulseAudio → SSH Tunnel → Local Speakers
+```
+
+## Development
+
+The skill is automatically packaged with AgentVibes npm releases. To update:
+
+1. Edit `skill/SKILL.md`
+2. Test with Clawdbot
+3. Commit to AgentVibes repo
+4. Publish new AgentVibes version
+
+## Support
+
+- **AgentVibes Issues**: https://github.com/paulpreibisch/AgentVibes/issues
+- **Clawdbot Issues**: https://github.com/clawdbot/clawdbot/issues
+
+## License
+
+Apache 2.0 - Same as AgentVibes