agentvibes 2.12.1 → 2.12.3

package/linkedin/vibe-coding-and-pulseaudio.md

@@ -0,0 +1,121 @@
+# Vibe Coding: How PulseAudio Can Give Your Remote SSH Session a Voice!
+
+My mornings and late evenings are when I'm at my creative peak. I like to use this time for things that are fun—or at least that I think are fun. Since I recently created AgentVibes (a way to make my computer speak back to me), I wanted to solve a limitation I was experiencing while working on a remote server. That curiosity led me down the PulseAudio rabbit hole, and what I discovered fundamentally changed how I code with AI.
+
+## What is "Vibe Coding"?
+
+According to Gene Kim, a researcher and author featured in the DORA report, **"vibe coding"** is defined as any form of coding where you don't type out code by hand. Instead of manual typing, the code emerges from an **iterative conversation with an AI**.
+
+This is the future of software development. Not replacing developers, but amplifying our capabilities through natural dialogue.
+
+## If We're Going to Have a Conversation, Let's Use Voice
+
+When I discovered whisper typing several months ago, it fundamentally changed the way I use my computer. Rather than typing everything to my AI assistant, I now **talk** using whisper typing. The speed, the naturalness, the flow—it was transformative.
+
+But then a thought struck me: **If I can talk to my computer, why can't it talk back?**
+
+That question led me to create [**AgentVibes**](https://github.com/paulpreibisch/AgentVibes)—a plugin for Claude Code that brings professional text-to-speech narration to your AI coding sessions. Your AI assistant can now acknowledge your requests, confirm task completion, and provide feedback through voice.
+
+Imagine this workflow:
+- You speak your coding request using whisper typing
+- Your AI assistant acknowledges with voice: "I'll refactor that authentication module for you"
+- You continue working while hearing real-time progress updates
+- The AI confirms: "Refactoring complete, all tests passing"
+
+This is vibe coding at its finest—a natural, conversational flow between human and AI.
+
+## The Remote Server Problem
+
+But I discovered a limitation. Since text-to-speech typically executes on the computer you're programming on, **what happens when you're programming on a remote machine via SSH?**
+
+This is the reality for many developers:
+- Cloud development environments
+- Powerful remote servers
+- Team shared infrastructure
+- Corporate VDI setups
+
+The audio plays on the remote server—where you can't hear it. The conversational flow breaks down. The vibe is lost.
+
+## Enter PulseAudio: The Hidden Hero
+
+I went to task trying to figure out if there was a way to somehow play audio from a remote machine onto my local machine. That's when I was introduced to the true capabilities of **PulseAudio**.
+
+Now, I've been a Linux user for many years and have used PulseAudio forever. But little did I know that **PulseAudio can actually stream audio over a network**, allowing a client to play audio from a remote server.
+
+This completely blew my mind. 🤯
+
+Here's what makes this powerful:
+
+### The Architecture
+```
+Remote Linux Server (PulseAudio)
+    ↓ SSH Reverse Tunnel
+Windows Client (WSL/RDP Audio)
+    ↓
+Local Speakers 🔊
+```
+
+### What This Enables
+- Run AgentVibes on your remote server
+- Hear TTS announcements on your local speakers
+- Maintain the conversational flow of vibe coding
+- Work from anywhere with full audio feedback
+
+I'll tell you, I was **floored** that this was even possible.
+
+## The Game-Changing Impact
+
+The ability to have your AI assistant **acknowledge what you've typed and provide vocal confirmation** really does change the game when vibe coding.
+
+Here's why it matters:
+
+**1. Cognitive Offloading**
+You don't need to constantly check the terminal to see if your AI understood. Voice acknowledgment lets you focus on problem-solving.
+
+**2. Natural Flow State**
+Conversations have rhythm. When both parties speak and listen, you stay in flow. Text-only breaks that rhythm.
+
+**3. Active Guidance with Voice Feedback**
+Vibe coding doesn't mean you stop paying attention—quite the opposite. You're actively guiding the AI through the implementation, reviewing its decisions, and course-correcting in real-time. Voice acknowledgment keeps you in the loop while your hands stay free to sketch architecture, review documentation, or reference other code. The conversation is continuous, and if you're an experienced developer, the depth and precision of that conversation becomes truly transformative.
+
+**4. Reduced Context Switching**
+No need to constantly alt-tab between terminal and code. Your ears keep you updated.
+
+## Try It Yourself
+
+Want to experience vibe coding with remote audio? I've documented the entire setup process.
+
+**Check out AgentVibes:**
+📦 GitHub: [github.com/paulpreibisch/AgentVibes](https://github.com/paulpreibisch/AgentVibes)
+
+**Remote Audio Setup Guide:**
+📚 Complete documentation: [Remote Audio Setup](https://github.com/paulpreibisch/AgentVibes/blob/master/docs/remote-audio-setup.md)
+
+The setup includes:
+- Automated scripts for Linux and Windows
+- PulseAudio network configuration
+- SSH tunnel setup
+- Troubleshooting guides
+- VS Code Remote-SSH integration
+
+It took me a morning to figure out, but now you can set it up in 10 minutes.
+
+## The Bigger Picture
+
+This journey taught me something important: **The best developer tools emerge from solving real problems in your own workflow.**
+
+I didn't set out to become a PulseAudio expert. I just wanted my AI assistant to talk back when I'm working on remote servers. The solution required diving deep into audio streaming, SSH tunneling, and network protocols—but the result is worth it.
+
+Vibe coding isn't just about AI generating code. It's about creating an **environment where human and AI collaborate naturally**—through conversation, through voice, through continuous feedback loops.
+
+And sometimes, that requires discovering that the tools you've been using for years have hidden superpowers you never knew existed.
+
+---
+
+**What's your experience with AI-assisted development? Have you tried vibe coding? Let's discuss in the comments!**
+
+#VibeCoding #AI #DeveloperTools #SoftwareEngineering #PulseAudio #RemoteDevelopment #DevOps #AIAssisted #ClaudeCode #OpenSource
+
+---
+
+*P.S. - If you found this interesting, check out the AgentVibes project on GitHub. It's open source, supports multiple TTS providers (including free Piper TTS), and has 30+ professional AI voices. Star the repo if you find it useful!* ⭐

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "agentvibes",
-  "version": "2.12.1",
+  "version": "2.12.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/scripts/audio-tunnel.config

@@ -0,0 +1,17 @@
+# AgentVibes Audio Tunnel Configuration
+# Personal configuration - DO NOT COMMIT
+
+# Remote server hostname (from your ~/.ssh/config)
+REMOTE_HOST="ubuntu-rdp"
+
+# Tunnel port (default: 14713)
+TUNNEL_PORT="14713"
+
+# PulseAudio socket path (WSL default)
+PULSE_SOCKET="/mnt/wslg/PulseServer"
+
+# Log file for automatic fixes
+AUTO_FIX_LOG="/tmp/audio-tunnel-autofix.log"
+
+# Healthcheck interval in minutes (for cron setup)
+CHECK_INTERVAL="5"

package/src/installer.js

@@ -585,32 +585,7 @@ async function copyPersonalityFiles(targetDir, spinner) {
   return personalityMdFiles.length;
 }
 
-/**
- * Copy output style files to target directory
- * @param {string} targetDir - Target installation directory
- * @param {Object} spinner - Ora spinner instance
- * @returns {Promise<number>} Number of files copied
- */
-async function copyOutputStyles(targetDir, spinner) {
-  spinner.start('Installing output styles...');
-  const srcOutputStylesDir = path.join(__dirname, '..', 'templates', 'output-styles');
-  const outputStylesDir = path.join(targetDir, '.claude', 'output-styles');
-
-  await fs.mkdir(outputStylesDir, { recursive: true });
-
-  const outputStyleFiles = await fs.readdir(srcOutputStylesDir);
-  console.log(chalk.cyan(`📝 Installing ${outputStyleFiles.length} output styles:`));
-
-  for (const file of outputStyleFiles) {
-    const srcPath = path.join(srcOutputStylesDir, file);
-    const destPath = path.join(outputStylesDir, file);
-    await fs.copyFile(srcPath, destPath);
-    console.log(chalk.gray(`   ✓ ${file}`));
-  }
-
-  spinner.succeed(chalk.green('Installed output styles!\n'));
-  return outputStyleFiles.length;
-}
+// Output styles removed - deprecated in favor of SessionStart hook system
 
 /**
  * Copy plugin files to target directory
@@ -1199,18 +1174,7 @@ async function updateAgentVibes(targetDir, options) {
     const personalityResult = await updatePersonalityFiles(targetDir, srcPersonalitiesDir);
     console.log(chalk.green(`✓ Updated ${personalityResult.updated} personalities, added ${personalityResult.new} new`));
 
-    // Update output styles
-    spinner.text = 'Updating output styles...';
-    const srcOutputStylesDir = path.join(__dirname, '..', '.claude', 'output-styles');
-    const outputStylesDir = path.join(claudeDir, 'output-styles');
-    const outputStyleFiles = await fs.readdir(srcOutputStylesDir);
-
-    for (const file of outputStyleFiles) {
-      const srcPath = path.join(srcOutputStylesDir, file);
-      const destPath = path.join(outputStylesDir, file);
-      await fs.copyFile(srcPath, destPath);
-    }
-    console.log(chalk.green(`✓ Updated ${outputStyleFiles.length} output styles`));
+    // Output styles removed - deprecated in favor of SessionStart hook system
 
     // Update plugin files
     const pluginFileCount = await copyPluginFiles(targetDir, { start: () => {}, succeed: () => {}, info: () => {}, fail: () => {} });
@@ -1327,7 +1291,7 @@ async function install(options = {}) {
   console.log(chalk.gray(`   • 16 slash commands → ${targetDir}/.claude/commands/agent-vibes/`));
   console.log(chalk.gray(`   • Multi-provider TTS system (ElevenLabs + Piper TTS) → ${targetDir}/.claude/hooks/`));
   console.log(chalk.gray(`   • 19 personality templates → ${targetDir}/.claude/personalities/`));
-  console.log(chalk.gray(`   • Agent Vibes output style → ${targetDir}/.claude/output-styles/`));
+  console.log(chalk.gray(`   • SessionStart hook for automatic TTS activation`));
   console.log(chalk.gray(`   • 27+ curated voices (ElevenLabs premium)`));
   console.log(chalk.gray(`   • 50+ neural voices (Piper TTS - free & offline)`));
   console.log(chalk.gray(`   • 30+ language support with native voices`));
@@ -1358,7 +1322,6 @@ async function install(options = {}) {
     const claudeDir = path.join(targetDir, '.claude');
     const commandsDir = path.join(claudeDir, 'commands');
     const hooksDir = path.join(claudeDir, 'hooks');
-    const outputStylesDir = path.join(claudeDir, 'output-styles');
 
     let exists = false;
     try {
@@ -1370,10 +1333,8 @@ async function install(options = {}) {
       spinner.info(chalk.yellow('Creating .claude directory structure...'));
       console.log(chalk.gray(`   → ${commandsDir}`));
       console.log(chalk.gray(`   → ${hooksDir}`));
-      console.log(chalk.gray(`   → ${outputStylesDir}`));
       await fs.mkdir(commandsDir, { recursive: true });
       await fs.mkdir(hooksDir, { recursive: true });
-      await fs.mkdir(outputStylesDir, { recursive: true });
       console.log(chalk.green('   ✓ Directories created!\n'));
     } else {
       spinner.succeed(chalk.green('.claude directory found!'));
@@ -1384,7 +1345,6 @@ async function install(options = {}) {
     const commandFileCount = await copyCommandFiles(targetDir, spinner);
     const hookFileCount = await copyHookFiles(targetDir, spinner);
     const personalityFileCount = await copyPersonalityFiles(targetDir, spinner);
-    const outputStyleCount = await copyOutputStyles(targetDir, spinner);
     const pluginFileCount = await copyPluginFiles(targetDir, spinner);
     const bmadConfigFileCount = await copyBmadConfigFiles(targetDir, spinner);
 
@@ -1417,7 +1377,7 @@ async function install(options = {}) {
     console.log(chalk.white(`   • ${commandFileCount} slash commands installed`));
     console.log(chalk.white(`   • ${hookFileCount} TTS scripts installed`));
     console.log(chalk.white(`   • ${personalityFileCount} personality templates installed`));
-    console.log(chalk.white(`   • ${outputStyleCount} output styles installed`));
+    console.log(chalk.white(`   • SessionStart hook configured for automatic TTS`));
     if (pluginFileCount > 0) {
       console.log(chalk.white(`   • ${pluginFileCount} BMAD plugin files installed`));
     }
@@ -1939,6 +1899,23 @@ program
     await resetBmadVoices(options);
   });
 
+// BMAD PR Testing Command
+program
+  .command('test-bmad-pr [pr-number]')
+  .description('Test BMAD PR with AgentVibes integration (default: PR #934)')
+  .action(async (prNumber = '934') => {
+    const testScript = path.join(__dirname, '..', 'bin', 'test-bmad-pr');
+
+    try {
+      execScript(`${testScript} ${prNumber}`, {
+        stdio: 'inherit',
+        env: process.env
+      });
+    } catch (error) {
+      process.exit(error.status || 1);
+    }
+  });
+
 // Help command
 program
   .command('help')

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

@@ -0,0 +1,15 @@
+# <!-- 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/v4-backup/.bmad-core/agent-teams/team-fullstack.yaml

@@ -0,0 +1,19 @@
+# <!-- 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/v4-backup/.bmad-core/agent-teams/team-ide-minimal.yaml

@@ -0,0 +1,11 @@
+# <!-- 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/v4-backup/.bmad-core/agent-teams/team-no-ui.yaml

@@ -0,0 +1,14 @@
+# <!-- 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/v4-backup/.bmad-core/agents/analyst.md

@@ -0,0 +1,84 @@
+<!-- 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/v4-backup/.bmad-core/agents/architect.md

@@ -0,0 +1,85 @@
+<!-- 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/v4-backup/.bmad-core/agents/bmad-master.md

@@ -0,0 +1,110 @@
+<!-- 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
+```