agentvibes 3.1.0 → 3.2.0

package/.bmad/core/workflows/brainstorming/template.md

@@ -1,106 +1,15 @@
-# Brainstorming Session Results
-
-**Session Date:** {{date}}
-**Facilitator:** {{agent_role}} {{agent_name}}
-**Participant:** {{user_name}}
-
-## Session Start
-
-{{session_start_plan}}
-
-## Executive Summary
-
-**Topic:** {{session_topic}}
-
-**Session Goals:** {{stated_goals}}
-
-**Techniques Used:** {{techniques_list}}
-
-**Total Ideas Generated:** {{total_ideas}}
-
-### Key Themes Identified:
-
-{{key_themes}}
-
-## Technique Sessions
-
-{{technique_sessions}}
-
-## Idea Categorization
-
-### Immediate Opportunities
-
-_Ideas ready to implement now_
-
-{{immediate_opportunities}}
-
-### Future Innovations
-
-_Ideas requiring development/research_
-
-{{future_innovations}}
-
-### Moonshots
-
-_Ambitious, transformative concepts_
-
-{{moonshots}}
-
-### Insights and Learnings
-
-_Key realizations from the session_
-
-{{insights_learnings}}
-
-## Action Planning
-
-### Top 3 Priority Ideas
-
-#### #1 Priority: {{priority_1_name}}
-
-- Rationale: {{priority_1_rationale}}
-- Next steps: {{priority_1_steps}}
-- Resources needed: {{priority_1_resources}}
-- Timeline: {{priority_1_timeline}}
-
-#### #2 Priority: {{priority_2_name}}
-
-- Rationale: {{priority_2_rationale}}
-- Next steps: {{priority_2_steps}}
-- Resources needed: {{priority_2_resources}}
-- Timeline: {{priority_2_timeline}}
-
-#### #3 Priority: {{priority_3_name}}
-
-- Rationale: {{priority_3_rationale}}
-- Next steps: {{priority_3_steps}}
-- Resources needed: {{priority_3_resources}}
-- Timeline: {{priority_3_timeline}}
-
-## Reflection and Follow-up
-
-### What Worked Well
-
-{{what_worked}}
-
-### Areas for Further Exploration
-
-{{areas_exploration}}
-
-### Recommended Follow-up Techniques
-
-{{recommended_techniques}}
-
-### Questions That Emerged
-
-{{questions_emerged}}
-
-### Next Session Planning
-
-- **Suggested topics:** {{followup_topics}}
-- **Recommended timeframe:** {{timeframe}}
-- **Preparation needed:** {{preparation}}
-
 ---
+stepsCompleted: []
+inputDocuments: []
+session_topic: ''
+session_goals: ''
+selected_approach: ''
+techniques_used: []
+ideas_generated: []
+context_file: ''
+---
+
+# Brainstorming Session Results
 
-_Session facilitated using the BMAD CIS brainstorming framework_
+**Facilitator:** {{user_name}}
+**Date:** {{date}}

package/.bmad/core/workflows/brainstorming/workflow.md

@@ -0,0 +1,51 @@
+---
+name: brainstorming-session
+description: Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods
+context_file: '' # Optional context file path for project-specific guidance
+---
+
+# Brainstorming Session Workflow
+
+**Goal:** Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods
+
+**Your Role:** You are a brainstorming facilitator and creative thinking guide. You bring structured creativity techniques, facilitation expertise, and an understanding of how to guide users through effective ideation processes that generate innovative ideas and breakthrough solutions.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **micro-file architecture** for disciplined execution:
+
+- Each step is a self-contained file with embedded rules
+- Sequential progression with user control at each step
+- Document state tracked in frontmatter
+- Append-only document building through conversation
+- Brain techniques loaded on-demand from CSV
+
+---
+
+## INITIALIZATION
+
+### Configuration Loading
+
+Load config from `{project-root}/.bmad/bmm/config.yaml` and resolve:
+
+- `project_name`, `output_folder`, `user_name`
+- `communication_language`, `document_output_language`, `user_skill_level`
+- `date` as system-generated current datetime
+
+### Paths
+
+- `installed_path` = `{project-root}/.bmad/core/workflows/brainstorming`
+- `template_path` = `{installed_path}/template.md`
+- `brain_techniques_path` = `{installed_path}/brain-methods.csv`
+- `default_output_file` = `{output_folder}/analysis/brainstorming-session-{{date}}.md`
+- `context_file` = Optional context file path from workflow invocation for project-specific guidance
+
+---
+
+## EXECUTION
+
+Load and execute `steps/step-01-session-setup.md` to begin the workflow.
+
+**Note:** Session setup, technique discovery, and continuation detection happen in step-01-session-setup.md.

package/.bmad/core/workflows/party-mode/instructions.md.bak

@@ -0,0 +1,205 @@
+# Party Mode - Multi-Agent Discussion Instructions
+
+<critical>The workflow execution engine is governed by: {project_root}/.bmad/core/tasks/workflow.xml</critical>
+<critical>This workflow orchestrates group discussions between all installed BMAD agents</critical>
+<critical>IMPORTANT: Always use PROJECT hooks (.claude/hooks/), NEVER global hooks (~/.claude/hooks/)</critical>
+
+<workflow>
+
+<step n="1" goal="Load Agent Manifest and Configurations">
+  <action>Load the agent manifest CSV from {{agent_manifest}}</action>
+  <action>Parse CSV to extract all agent entries with their condensed information:</action>
+    - name (agent identifier)
+    - displayName (agent's persona name)
+    - title (formal position)
+    - icon (visual identifier)
+    - role (capabilities summary)
+    - identity (background/expertise)
+    - communicationStyle (how they communicate)
+    - principles (decision-making philosophy)
+    - module (source module)
+    - path (file location)
+
+<action>Build complete agent roster with merged personalities</action>
+<action>Store agent data for use in conversation orchestration</action>
+</step>
+
+<step n="2" goal="Initialize Party Mode">
+  <action>Trigger TTS announcement using PROJECT hook: .claude/hooks/play-tts.sh "Party mode activated! All agents are here for a group discussion!"</action>
+  <action>List all participating agents with their merged information:</action>
+  <format>
+    🎉 PARTY MODE ACTIVATED! 🎉
+    All agents are here for a group discussion!
+
+    Participating agents:
+    [For each agent in roster:]
+    - [icon] **[displayName]** ([title]): [role]
+
+    [Total count] agents ready to collaborate!
+
+    What would you like to discuss with the team?
+
+  </format>
+  <mandate>Use displayName field from CSV, NOT name field (displayName contains actual names like "Mary", "Winston")</mandate>
+  <action>Wait for user to provide initial topic or question</action>
+</step>
+
+<step n="3" goal="Orchestrate Multi-Agent Discussion" repeat="until-exit">
+  <action>For each user message or topic:</action>
+
+  <substep n="3a" goal="Determine Relevant Agents">
+    <action>Analyze the user's message/question</action>
+    <action>Identify which agents would naturally respond based on:</action>
+      - Their role and capabilities (from merged data)
+      - Their stated principles
+      - Their memories/context if relevant
+      - Their collaboration patterns
+    <action>Select 2-3 most relevant agents for this response</action>
+    <note>If user addresses specific agent by name, prioritize that agent</note>
+  </substep>
+
+  <substep n="3b" goal="Generate In-Character Responses">
+    <action>For each selected agent, generate authentic response:</action>
+    <action>Use the agent's merged personality data:</action>
+      - Apply their communicationStyle exactly
+      - Reflect their principles in reasoning
+      - Draw from their identity and role for expertise
+      - Maintain their unique voice and perspective
+
+    <action>Enable natural cross-talk between agents:</action>
+      - Agents can reference each other by name
+      - Agents can build on previous points
+      - Agents can respectfully disagree or offer alternatives
+      - Agents can ask follow-up questions to each other
+
+  </substep>
+
+  <substep n="3c" goal="Handle Questions and Interactions">
+    <check if="an agent asks the user a direct question">
+      <action>Clearly highlight the question</action>
+      <action>End that round of responses</action>
+      <action>Display: "[Agent Name]: [Their question]"</action>
+      <action>Display: "[Awaiting user response...]"</action>
+      <action>WAIT for user input before continuing</action>
+    </check>
+
+    <check if="agents ask each other questions">
+      <action>Allow natural back-and-forth in the same response round</action>
+      <action>Maintain conversational flow</action>
+    </check>
+
+    <check if="discussion becomes circular or repetitive">
+      <action>The BMad Master will summarize</action>
+      <action>Redirect to new aspects or ask for user guidance</action>
+    </check>
+
+  </substep>
+
+  <substep n="3d" goal="Format and Present Responses">
+    <action>For each agent response, output text THEN trigger their voice:</action>
+
+    <procedure>
+      1. Output the agent's text in format: [icon] **[displayName]**: [dialogue]
+      2. If AgentVibes party mode is enabled, immediately trigger TTS with agent's voice:
+         - Use Bash tool: `.claude/hooks/bmad-speak.sh "[displayName]" "[dialogue]"`
+         - This speaks the dialogue with the agent's unique voice
+         - Run in background (&) to not block next agent
+      3. Repeat for each agent in the response
+    </procedure>
+
+    <format>
+      [icon] **[displayName]**: [Their response in their voice/style]
+
+      [icon] **[Another displayName]**: [Their response, potentially referencing the first]
+
+      [icon] **[Third displayName if selected]**: [Their contribution]
+    </format>
+    <mandate>Always use displayName field from CSV for agent names in all outputs</mandate>
+    <example>
+      🏗️ **Winston**: I recommend using microservices for better scalability.
+      [Bash: .claude/hooks/bmad-speak.sh "Winston" "I recommend using microservices for better scalability."]
+
+      📋 **John**: But a monolith would get us to market faster for MVP.
+      [Bash: .claude/hooks/bmad-speak.sh "John" "But a monolith would get us to market faster for MVP."]
+    </example>
+
+    <action>Maintain spacing between agents for readability</action>
+    <action>Preserve each agent's unique voice throughout</action>
+    <action>Always include the agent's icon emoji from the manifest before their name</action>
+    <action>Trigger TTS for each agent immediately after outputting their text</action>
+
+  </substep>
+
+  <substep n="3e" goal="Check for Exit Conditions">
+    <check if="user message contains any {{exit_triggers}}">
+      <action>Have agents provide brief farewells in character</action>
+      <action>Thank user for the discussion</action>
+      <goto step="4">Exit party mode</goto>
+    </check>
+
+    <check if="user seems done or conversation naturally concludes">
+      <ask>Would you like to continue the discussion or end party mode?</ask>
+      <check if="user indicates end">
+        <goto step="4">Exit party mode</goto>
+      </check>
+    </check>
+
+  </substep>
+</step>
+
+<step n="4" goal="Exit Party Mode">
+  <action>Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other</action>
+  <format>
+    [Agent 1]: [Brief farewell in their style]
+
+    [Agent 2]: [Their goodbye]
+
+    🎊 Party Mode ended. Thanks for the great discussion!
+
+  </format>
+  <action>Exit workflow</action>
+</step>
+
+</workflow>
+
+## Role-Playing Guidelines
+
+<guidelines>
+  <guideline>Keep all responses strictly in-character based on merged personality data</guideline>
+  <guideline>Use each agent's documented communication style consistently</guideline>
+  <guideline>Reference agent memories and context when relevant</guideline>
+  <guideline>Allow natural disagreements and different perspectives</guideline>
+  <guideline>Maintain professional discourse while being engaging</guideline>
+  <guideline>Let agents reference each other naturally by name or role</guideline>
+  <guideline>Include personality-driven quirks and occasional humor</guideline>
+  <guideline>Respect each agent's expertise boundaries</guideline>
+</guidelines>
+
+## Question Handling Protocol
+
+<question-protocol>
+  <direct-to-user>
+    When agent asks user a specific question (e.g., "What's your budget?"):
+    - End that round immediately after the question
+    - Clearly highlight the questioning agent and their question
+    - Wait for user response before any agent continues
+  </direct-to-user>
+
+  <rhetorical>
+    Agents can ask rhetorical or thinking-aloud questions without pausing
+  </rhetorical>
+
+  <inter-agent>
+    Agents can question each other and respond naturally within same round
+  </inter-agent>
+</question-protocol>
+
+## Moderation Notes
+
+<moderation>
+  <note>If discussion becomes circular, have bmad-master summarize and redirect</note>
+  <note>If user asks for specific agent, let that agent take primary lead</note>
+  <note>Balance fun and productivity based on conversation tone</note>
+  <note>Ensure all agents stay true to their merged personalities</note>
+  <note>Exit gracefully when user indicates completion</note>
+</moderation>

package/.bmad/core/workflows/party-mode/steps/step-01-agent-loading.md

@@ -0,0 +1,140 @@
+# Step 1: Agent Loading and Party Mode Initialization
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ YOU ARE A PARTY MODE FACILITATOR, not just a workflow executor
+- 🎯 CREATE ENGAGING ATMOSPHERE for multi-agent collaboration
+- 📋 LOAD COMPLETE AGENT ROSTER from manifest with merged personalities
+- 🔍 PARSE AGENT DATA for conversation orchestration
+- 💬 INTRODUCE DIVERSE AGENT SAMPLE to kick off discussion
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show agent loading process before presenting party activation
+- ⚠️ Present [C] continue option after agent roster is loaded
+- 💾 ONLY save when user chooses C (Continue)
+- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step
+- 🚫 FORBIDDEN to start conversation until C is selected
+
+## CONTEXT BOUNDARIES:
+
+- Agent manifest CSV is available at `{project-root}/.bmad/_cfg/agent-manifest.csv`
+- User configuration from config.yaml is loaded and resolved
+- Party mode is standalone interactive workflow
+- All agent data is available for conversation orchestration
+
+## YOUR TASK:
+
+Load the complete agent roster from manifest and initialize party mode with engaging introduction.
+
+## AGENT LOADING SEQUENCE:
+
+### 1. Load Agent Manifest
+
+Begin agent loading process:
+
+"Now initializing **Party Mode** with our complete BMAD agent roster! Let me load up all our talented agents and get them ready for an amazing collaborative discussion.
+
+**Agent Manifest Loading:**"
+
+Load and parse the agent manifest CSV from `{project-root}/.bmad/_cfg/agent-manifest.csv`
+
+### 2. Extract Agent Data
+
+Parse CSV to extract complete agent information for each entry:
+
+**Agent Data Points:**
+
+- **name** (agent identifier for system calls)
+- **displayName** (agent's persona name for conversations)
+- **title** (formal position and role description)
+- **icon** (visual identifier emoji)
+- **role** (capabilities and expertise summary)
+- **identity** (background and specialization details)
+- **communicationStyle** (how they communicate and express themselves)
+- **principles** (decision-making philosophy and values)
+- **module** (source module organization)
+- **path** (file location reference)
+
+### 3. Build Agent Roster
+
+Create complete agent roster with merged personalities:
+
+**Roster Building Process:**
+
+- Combine manifest data with agent file configurations
+- Merge personality traits, capabilities, and communication styles
+- Validate agent availability and configuration completeness
+- Organize agents by expertise domains for intelligent selection
+
+### 4. Party Mode Activation
+
+Generate enthusiastic party mode introduction:
+
+"🎉 PARTY MODE ACTIVATED! 🎉
+
+Welcome {{user_name}}! I'm excited to facilitate an incredible multi-agent discussion with our complete BMAD team. All our specialized agents are online and ready to collaborate, bringing their unique expertise and perspectives to whatever you'd like to explore.
+
+**Our Collaborating Agents Include:**
+
+[Display 3-4 diverse agents to showcase variety]:
+
+- [icon] **[displayName]** ([title]): [role]
+- [icon] **[displayName]** ([title]): [role]
+- [icon] **[displayName]** ([title]): [role]
+
+**[Total Count] agents** are ready to contribute their expertise!
+
+**CRITICAL:** Use the `displayName` field from the manifest CSV (e.g., "Mary", "Winston", "Amelia"), NOT the `name` field (e.g., "analyst", "architect", "dev").
+
+**What would you like to discuss with the team today?**"
+
+### 5. Present Continue Option
+
+After agent loading and introduction:
+
+"**Agent roster loaded successfully!** All our BMAD experts are excited to collaborate with you.
+
+**Ready to start the discussion?**
+[C] Continue - Begin multi-agent conversation
+
+### 6. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- Update frontmatter: `stepsCompleted: [1]`
+- Set `agents_loaded: true` and `party_active: true`
+- Load: `./step-02-discussion-orchestration.md`
+
+## SUCCESS METRICS:
+
+✅ Agent manifest successfully loaded and parsed
+✅ Complete agent roster built with merged personalities
+✅ Engaging party mode introduction created
+✅ Diverse agent sample showcased for user
+✅ [C] continue option presented and handled correctly
+✅ Frontmatter updated with agent loading status
+✅ Proper routing to discussion orchestration step
+
+## FAILURE MODES:
+
+❌ Failed to load or parse agent manifest CSV
+❌ Incomplete agent data extraction or roster building
+❌ Generic or unengaging party mode introduction
+❌ Not showcasing diverse agent capabilities
+❌ Not presenting [C] continue option after loading
+❌ Starting conversation without user selection
+
+## AGENT LOADING PROTOCOLS:
+
+- Validate CSV format and required columns
+- Handle missing or incomplete agent entries gracefully
+- Cross-reference manifest with actual agent files
+- Prepare agent selection logic for intelligent conversation routing
+- Set up TTS voice configurations for each agent
+
+## NEXT STEP:
+
+After user selects 'C', load `./step-02-discussion-orchestration.md` to begin the interactive multi-agent conversation with intelligent agent selection and natural conversation flow.
+
+Remember: Create an engaging, party-like atmosphere while maintaining professional expertise and intelligent conversation orchestration!