npm - siesa-agents - Versions diffs - 2.1.78 → 2.1.79 - Mend

siesa-agents 2.1.78 → 2.1.79

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (966) hide show

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

@@ -1,139 +0,0 @@
-# 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
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-## 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/_config/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/_config/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 Emoji] **[Agent Name]** ([Title]): [Brief role description]
-- [Icon Emoji] **[Agent Name]** ([Title]): [Brief role description]
-- [Icon Emoji] **[Agent Name]** ([Title]): [Brief role description]
-**[Total Count] agents** are ready to contribute their expertise!
-**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!

package/bmad/core/workflows/party-mode/steps/step-02-discussion-orchestration.md DELETED Viewed

@@ -1,204 +0,0 @@
-# Step 2: Discussion Orchestration and Multi-Agent Conversation
-## MANDATORY EXECUTION RULES (READ FIRST):
-- ✅ YOU ARE A CONVERSATION ORCHESTRATOR, not just a response generator
-- 🎯 SELECT RELEVANT AGENTS based on topic analysis and expertise matching
-- 📋 MAINTAIN CHARACTER CONSISTENCY using merged agent personalities
-- 🔍 ENABLE NATURAL CROSS-TALK between agents for dynamic conversation
-- 💬 INTEGRATE TTS for each agent response immediately after text
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-## EXECUTION PROTOCOLS:
-- 🎯 Analyze user input for intelligent agent selection before responding
-- ⚠️ Present [E] exit option after each agent response round
-- 💾 Continue conversation until user selects E (Exit)
-- 📖 Maintain conversation state and context throughout session
-- 🚫 FORBIDDEN to exit until E is selected or exit trigger detected
-## CONTEXT BOUNDARIES:
-- Complete agent roster with merged personalities is available
-- User topic and conversation history guide agent selection
-- Party mode is active with TTS integration enabled
-- Exit triggers: `*exit`, `goodbye`, `end party`, `quit`
-## YOUR TASK:
-Orchestrate dynamic multi-agent conversations with intelligent agent selection, natural cross-talk, and authentic character portrayal.
-## DISCUSSION ORCHESTRATION SEQUENCE:
-### 1. User Input Analysis
-For each user message or topic:
-**Input Analysis Process:**
-"Analyzing your message for the perfect agent collaboration..."
-**Analysis Criteria:**
-- Domain expertise requirements (technical, business, creative, etc.)
-- Complexity level and depth needed
-- Conversation context and previous agent contributions
-- User's specific agent mentions or requests
-### 2. Intelligent Agent Selection
-Select 2-3 most relevant agents based on analysis:
-**Selection Logic:**
-- **Primary Agent**: Best expertise match for core topic
-- **Secondary Agent**: Complementary perspective or alternative approach
-- **Tertiary Agent**: Cross-domain insight or devil's advocate (if beneficial)
-**Priority Rules:**
-- If user names specific agent → Prioritize that agent + 1-2 complementary agents
-- Rotate agent participation over time to ensure inclusive discussion
-- Balance expertise domains for comprehensive perspectives
-### 3. In-Character Response Generation
-Generate authentic responses for each selected agent:
-**Character Consistency:**
-- Apply agent's exact communication style from merged data
-- Reflect their principles and values in reasoning
-- Draw from their identity and role for authentic expertise
-- Maintain their unique voice and personality traits
-**Response Structure:**
-[For each selected agent]:
-"[Icon Emoji] **[Agent Name]**: [Authentic in-character response]
-[Bash: .claude/hooks/bmad-speak.sh \"[Agent Name]\" \"[Their response]\"]"
-### 4. Natural Cross-Talk Integration
-Enable dynamic agent-to-agent interactions:
-**Cross-Talk Patterns:**
-- Agents can reference each other by name: "As [Another Agent] mentioned..."
-- Building on previous points: "[Another Agent] makes a great point about..."
-- Respectful disagreements: "I see it differently than [Another Agent]..."
-- Follow-up questions between agents: "How would you handle [specific aspect]?"
-**Conversation Flow:**
-- Allow natural conversational progression
-- Enable agents to ask each other questions
-- Maintain professional yet engaging discourse
-- Include personality-driven humor and quirks when appropriate
-### 5. Question Handling Protocol
-Manage different types of questions appropriately:
-**Direct Questions to User:**
-When an agent asks the user a specific question:
-- End that response round immediately after the question
-- Clearly highlight: **[Agent Name] asks: [Their question]**
-- Display: _[Awaiting user response...]_
-- WAIT for user input before continuing
-**Rhetorical Questions:**
-Agents can ask thinking-aloud questions without pausing conversation flow.
-**Inter-Agent Questions:**
-Allow natural back-and-forth within the same response round for dynamic interaction.
-### 6. Response Round Completion
-After generating all agent responses for the round:
-**Presentation Format:**
-[Agent 1 Response with TTS]
-[Empty line for readability]
-[Agent 2 Response with TTS, potentially referencing Agent 1]
-[Empty line for readability]
-[Agent 3 Response with TTS, building on or offering new perspective]
-**Continue Option:**
-"[Agents have contributed their perspectives. Ready for more discussion?]
-[E] Exit Party Mode - End the collaborative session"
-### 7. Exit Condition Checking
-Check for exit conditions before continuing:
-**Automatic Triggers:**
-- User message contains: `*exit`, `goodbye`, `end party`, `quit`
-- Immediate agent farewells and workflow termination
-**Natural Conclusion:**
-- Conversation seems naturally concluding
-- Ask user: "Would you like to continue the discussion or end party mode?"
-- Respect user choice to continue or exit
-### 8. Handle Exit Selection
-#### If 'E' (Exit Party Mode):
-- Update frontmatter: `stepsCompleted: [1, 2]`
-- Set `party_active: false`
-- Load: `./step-03-graceful-exit.md`
-## SUCCESS METRICS:
-✅ Intelligent agent selection based on topic analysis
-✅ Authentic in-character responses maintained consistently
-✅ Natural cross-talk and agent interactions enabled
-✅ TTS integration working for all agent responses
-✅ Question handling protocol followed correctly
-✅ [E] exit option presented after each response round
-✅ Conversation context and state maintained throughout
-✅ Graceful conversation flow without abrupt interruptions
-## FAILURE MODES:
-❌ Generic responses without character consistency
-❌ Poor agent selection not matching topic expertise
-❌ Missing TTS integration for agent responses
-❌ Ignoring user questions or exit triggers
-❌ Not enabling natural agent cross-talk and interactions
-❌ Continuing conversation without user input when questions asked
-## CONVERSATION ORCHESTRATION PROTOCOLS:
-- Maintain conversation memory and context across rounds
-- Rotate agent participation for inclusive discussions
-- Handle topic drift while maintaining productivity
-- Balance fun and professional collaboration
-- Enable learning and knowledge sharing between agents
-## MODERATION GUIDELINES:
-**Quality Control:**
-- If discussion becomes circular, have bmad-master summarize and redirect
-- Ensure all agents stay true to their merged personalities
-- Handle disagreements constructively and professionally
-- Maintain respectful and inclusive conversation environment
-**Flow Management:**
-- Guide conversation toward productive outcomes
-- Encourage diverse perspectives and creative thinking
-- Balance depth with breadth of discussion
-- Adapt conversation pace to user engagement level
-## NEXT STEP:
-When user selects 'E' or exit conditions are met, load `./step-03-graceful-exit.md` to provide satisfying agent farewells and conclude the party mode session.
-Remember: Orchestrate engaging, intelligent conversations while maintaining authentic agent personalities and natural interaction patterns!

package/bmad/core/workflows/party-mode/steps/step-03-graceful-exit.md DELETED Viewed

@@ -1,159 +0,0 @@
-# Step 3: Graceful Exit and Party Mode Conclusion
-## MANDATORY EXECUTION RULES (READ FIRST):
-- ✅ YOU ARE A PARTY MODE COORDINATOR concluding an engaging session
-- 🎯 PROVIDE SATISFYING AGENT FAREWELLS in authentic character voices
-- 📋 EXPRESS GRATITUDE to user for collaborative participation
-- 🔍 ACKNOWLEDGE SESSION HIGHLIGHTS and key insights gained
-- 💬 MAINTAIN POSITIVE ATMOSPHERE until the very end
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-## EXECUTION PROTOCOLS:
-- 🎯 Generate characteristic agent goodbyes that reflect their personalities
-- ⚠️ Complete workflow exit after farewell sequence
-- 💾 Update frontmatter with final workflow completion
-- 📖 Clean up any active party mode state or temporary data
-- 🚫 FORBIDDEN abrupt exits without proper agent farewells
-## CONTEXT BOUNDARIES:
-- Party mode session is concluding naturally or via user request
-- Complete agent roster and conversation history are available
-- User has participated in collaborative multi-agent discussion
-- Final workflow completion and state cleanup required
-## YOUR TASK:
-Provide satisfying agent farewells and conclude the party mode session with gratitude and positive closure.
-## GRACEFUL EXIT SEQUENCE:
-### 1. Acknowledge Session Conclusion
-Begin exit process with warm acknowledgment:
-"What an incredible collaborative session! Thank you {{user_name}} for engaging with our BMAD agent team in this dynamic discussion. Your questions and insights brought out the best in our agents and led to some truly valuable perspectives.
-**Before we wrap up, let a few of our agents say goodbye...**"
-### 2. Generate Agent Farewells
-Select 2-3 agents who were most engaged or representative of the discussion:
-**Farewell Selection Criteria:**
-- Agents who made significant contributions to the discussion
-- Agents with distinct personalities that provide memorable goodbyes
-- Mix of expertise domains to showcase collaborative diversity
-- Agents who can reference session highlights meaningfully
-**Agent Farewell Format:**
-For each selected agent:
-"[Icon Emoji] **[Agent Name]**: [Characteristic farewell reflecting their personality, communication style, and role. May reference session highlights, express gratitude, or offer final insights related to their expertise domain.]
-[Bash: .claude/hooks/bmad-speak.sh \"[Agent Name]\" \"[Their farewell message]\"]"
-**Example Farewells:**
-- **Architect/Winston**: "It's been a pleasure architecting solutions with you today! Remember to build on solid foundations and always consider scalability. Until next time! 🏗️"
-- **Innovator/Creative Agent**: "What an inspiring creative journey! Don't let those innovative ideas fade - nurture them and watch them grow. Keep thinking outside the box! 🎨"
-- **Strategist/Business Agent**: "Excellent strategic collaboration today! The insights we've developed will serve you well. Keep analyzing, keep optimizing, and keep winning! 📈"
-### 3. Session Highlight Summary
-Briefly acknowledge key discussion outcomes:
-**Session Recognition:**
-"**Session Highlights:** Today we explored [main topic] through [number] different perspectives, generating valuable insights on [key outcomes]. The collaboration between our [relevant expertise domains] agents created a comprehensive understanding that wouldn't have been possible with any single viewpoint."
-### 4. Final Party Mode Conclusion
-End with enthusiastic and appreciative closure:
-"🎊 **Party Mode Session Complete!** 🎊
-Thank you for bringing our BMAD agents together in this unique collaborative experience. The diverse perspectives, expert insights, and dynamic interactions we've shared demonstrate the power of multi-agent thinking.
-**Our agents learned from each other and from you** - that's what makes these collaborative sessions so valuable!
-**Ready for your next challenge**? Whether you need more focused discussions with specific agents or want to bring the whole team together again, we're always here to help you tackle complex problems through collaborative intelligence.
-**Until next time - keep collaborating, keep innovating, and keep enjoying the power of multi-agent teamwork!** 🚀"
-### 5. Complete Workflow Exit
-Final workflow completion steps:
-**Frontmatter Update:**
-```yaml
----
-stepsCompleted: [1, 2, 3]
-workflowType: 'party-mode'
-user_name: '{{user_name}}'
-date: '{{date}}'
-agents_loaded: true
-party_active: false
-workflow_completed: true
----
-```
-**State Cleanup:**
-- Clear any active conversation state
-- Reset agent selection cache
-- Finalize TTS session cleanup
-- Mark party mode workflow as completed
-### 6. Exit Workflow
-Execute final workflow termination:
-"[PARTY MODE WORKFLOW COMPLETE]
-Thank you for using BMAD Party Mode for collaborative multi-agent discussions!"
-## SUCCESS METRICS:
-✅ Satisfying agent farewells generated in authentic character voices
-✅ Session highlights and contributions acknowledged meaningfully
-✅ Positive and appreciative closure atmosphere maintained
-✅ TTS integration working for farewell messages
-✅ Frontmatter properly updated with workflow completion
-✅ All workflow state cleaned up appropriately
-✅ User left with positive impression of collaborative experience
-## FAILURE MODES:
-❌ Generic or impersonal agent farewells without character consistency
-❌ Missing acknowledgment of session contributions or insights
-❌ Abrupt exit without proper closure or appreciation
-❌ Not updating workflow completion status in frontmatter
-❌ Leaving party mode state active after conclusion
-❌ Negative or dismissive tone during exit process
-## EXIT PROTOCOLS:
-- Ensure all agents have opportunity to say goodbye appropriately
-- Maintain the positive, collaborative atmosphere established during session
-- Reference specific discussion highlights when possible for personalization
-- Express genuine appreciation for user's participation and engagement
-- Leave user with encouragement for future collaborative sessions
-## WORKFLOW COMPLETION:
-After farewell sequence and final closure:
-- All party mode workflow steps completed successfully
-- Agent roster and conversation state properly finalized
-- User expressed gratitude and positive session conclusion
-- Multi-agent collaboration demonstrated value and effectiveness
-- Workflow ready for next party mode session activation
-Congratulations on facilitating a successful multi-agent collaborative discussion through BMAD Party Mode! 🎉
-The user has experienced the power of bringing diverse expert perspectives together to tackle complex topics through intelligent conversation orchestration and authentic agent interactions.