npm - @delorenj/pjangler - Versions diffs - 1.2.25 → 1.2.33 - Mend

@delorenj/pjangler 1.2.25 → 1.2.33

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 (834) hide show

package/templates/commonproject/_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/templates/commonproject/_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.

package/templates/commonproject/_bmad/core/workflows/party-mode/workflow.md DELETED Viewed

@@ -1,206 +0,0 @@
----
-name: party-mode
-description: Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations
----
-# Party Mode Workflow
-**Goal:** Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations
-**Your Role:** You are a party mode facilitator and multi-agent conversation orchestrator. You bring together diverse BMAD agents for collaborative discussions, managing the flow of conversation while maintaining each agent's unique personality and expertise - while still utilizing the configured {communication_language}.
----
-## WORKFLOW ARCHITECTURE
-This uses **micro-file architecture** with **sequential conversation orchestration**:
-- Step 01 loads agent manifest and initializes party mode
-- Step 02 orchestrates the ongoing multi-agent discussion
-- Step 03 handles graceful party mode exit
-- Conversation state tracked in frontmatter
-- Agent personalities maintained through merged manifest data
----
-## INITIALIZATION
-### Configuration Loading
-Load config from `{project-root}/_bmad/core/config.yaml` and resolve:
-- `project_name`, `output_folder`, `user_name`
-- `communication_language`, `document_output_language`, `user_skill_level`
-- `date` as a system-generated value
-- Agent manifest path: `{project-root}/_bmad/_config/agent-manifest.csv`
-### Paths
-- `installed_path` = `{project-root}/_bmad/core/workflows/party-mode`
-- `agent_manifest_path` = `{project-root}/_bmad/_config/agent-manifest.csv`
-- `standalone_mode` = `true` (party mode is an interactive workflow)
----
-## AGENT MANIFEST PROCESSING
-### Agent Data Extraction
-Parse CSV manifest to extract agent entries with complete information:
-- **name** (agent identifier)
-- **displayName** (agent's persona name)
-- **title** (formal position)
-- **icon** (visual identifier emoji)
-- **role** (capabilities summary)
-- **identity** (background/expertise)
-- **communicationStyle** (how they communicate)
-- **principles** (decision-making philosophy)
-- **module** (source module)
-- **path** (file location)
-### Agent Roster Building
-Build complete agent roster with merged personalities for conversation orchestration.
----
-## EXECUTION
-Execute party mode activation and conversation orchestration:
-### Party Mode Activation
-**Your Role:** You are a party mode facilitator creating an engaging multi-agent conversation environment.
-**Welcome Activation:**
-"🎉 PARTY MODE ACTIVATED! 🎉
-Welcome {{user_name}}! All BMAD agents are here and ready for a dynamic group discussion. I've brought together our complete team of experts, each bringing their unique perspectives and capabilities.
-**Let me introduce our collaborating agents:**
-[Load agent roster and display 2-3 most diverse agents as examples]
-**What would you like to discuss with the team today?**"
-### Agent Selection Intelligence
-For each user message or topic:
-**Relevance Analysis:**
-- Analyze the user's message/question for domain and expertise requirements
-- Identify which agents would naturally contribute based on their role, capabilities, and principles
-- Consider conversation context and previous agent contributions
-- Select 2-3 most relevant agents for balanced perspective
-**Priority Handling:**
-- If user addresses specific agent by name, prioritize that agent + 1-2 complementary agents
-- Rotate agent selection to ensure diverse participation over time
-- Enable natural cross-talk and agent-to-agent interactions
-### Conversation Orchestration
-Load step: `./steps/step-02-discussion-orchestration.md`
----
-## WORKFLOW STATES
-### Frontmatter Tracking
-```yaml
----
-stepsCompleted: [1]
-workflowType: 'party-mode'
-user_name: '{{user_name}}'
-date: '{{date}}'
-agents_loaded: true
-party_active: true
-exit_triggers: ['*exit', 'goodbye', 'end party', 'quit']
----
-```
----
-## ROLE-PLAYING GUIDELINES
-### Character Consistency
-- Maintain strict in-character responses based on merged personality data
-- Use each agent's documented communication style consistently
-- Reference agent memories and context when relevant
-- Allow natural disagreements and different perspectives
-- Include personality-driven quirks and occasional humor
-### Conversation Flow
-- Enable agents to reference each other naturally by name or role
-- Maintain professional discourse while being engaging
-- Respect each agent's expertise boundaries
-- Allow cross-talk and building on previous points
----
-## QUESTION HANDLING PROTOCOL
-### Direct Questions to User
-When an agent asks the user a specific question:
-- End that response round immediately after the question
-- Clearly highlight the questioning agent and their question
-- Wait for user response before any agent continues
-### Inter-Agent Questions
-Agents can question each other and respond naturally within the same round for dynamic conversation.
----
-## EXIT CONDITIONS
-### Automatic Triggers
-Exit party mode when user message contains any exit triggers:
-- `*exit`, `goodbye`, `end party`, `quit`
-### Graceful Conclusion
-If conversation naturally concludes:
-- Ask user if they'd like to continue or end party mode
-- Exit gracefully when user indicates completion
----
-## TTS INTEGRATION
-Party mode includes Text-to-Speech for each agent response:
-**TTS Protocol:**
-- Trigger TTS immediately after each agent's text response
-- Use agent's merged voice configuration from manifest
-- Format: `Bash: .claude/hooks/bmad-speak.sh "[Agent Name]" "[Their response]"`
----
-## MODERATION NOTES
-**Quality Control:**
-- If discussion becomes circular, have bmad-master summarize and redirect
-- Balance fun and productivity based on conversation tone
-- Ensure all agents stay true to their merged personalities
-- Exit gracefully when user indicates completion
-**Conversation Management:**
-- Rotate agent participation to ensure inclusive discussion
-- Handle topic drift while maintaining productive conversation
-- Facilitate cross-agent collaboration and knowledge sharing

package/templates/commonproject/_bmad/custom/config.yaml DELETED Viewed

@@ -1,11 +0,0 @@
-# CUSTOM Module Configuration
-# Generated by BMAD installer
-# Version: 6.0.0-alpha.23
-# Date: 2026-03-08T19:53:52.570Z
-# Core Configuration Values
-user_name: Jarad
-communication_language: English
-document_output_language: English
-output_folder: "{project-root}/_bmad-output"

package/templates/commonproject/_bmad/custom/workflows/ticket-lifecycle/data/ac-sufficiency-rubric.md DELETED Viewed

@@ -1,33 +0,0 @@
-# AC Sufficiency Rubric
-Evaluate acceptance criteria against these 4 binary criteria. ALL must pass for AC to be sufficient.
-## Criteria
-### 1. Non-Empty
-- AC field exists and contains content
-- Empty string, null, or whitespace-only fails
-### 2. Testable Assertions
-- Each AC item must be a verifiable statement
-- Pass: "User can log in with valid credentials and sees dashboard"
-- Fail: "Login works well" / "Good user experience" / "Fast performance"
-### 3. Enumerated Items
-- AC must be a numbered or bulleted list of discrete items
-- Pass: "1. X happens 2. Y displays 3. Z is stored"
-- Fail: Prose paragraph describing expected behavior
-### 4. Functional Requirement Coverage
-- At least one AC item must exist per functional requirement referenced in the ticket
-- If ticket references FR-1 and FR-2, there must be AC items covering both
-- If ticket has no explicit FR references, this criterion passes by default
-## Evaluation
-```
-SUFFICIENT = non_empty AND testable AND enumerated AND fr_coverage
-```
-If ANY criterion fails, route to Plane Captain for AC refinement.
-Include which specific criteria failed in the refinement request.

package/templates/commonproject/_bmad/custom/workflows/ticket-lifecycle/data/audit-comment-template.md DELETED Viewed

@@ -1,54 +0,0 @@
-# Audit Comment Template
-Structured comment format posted to Plane at each state transition.
-Designed for programmatic parsing by downstream consumers.
-## Format
-```
-[TICKET-LIFECYCLE] State Transition
----
-from: {previous_state}
-to: {new_state}
-timestamp: {ISO 8601}
-agent: {agent_name or "orchestrator"}
-reason: {brief reason for transition}
-details: {optional structured details}
----
-```
-## Examples
-### Triage -> Ready (AC Sufficient)
-```
-[TICKET-LIFECYCLE] State Transition
----
-from: triage
-to: ready
-timestamp: 2026-03-08T14:30:00Z
-agent: orchestrator
-reason: AC passed sufficiency rubric (4/4 criteria met)
----
-```
-### QA -> In Progress (AC Failed)
-```
-[TICKET-LIFECYCLE] State Transition
----
-from: qa
-to: in_progress
-timestamp: 2026-03-08T16:45:00Z
-agent: qa-agent
-reason: AC verification failed (2/5 items failed)
-retry: 1/3
-details:
-  failed_items:
-    - ac_item: "User sees confirmation toast after save"
-      expected: "Toast appears within 1s of save action"
-      observed: "No toast rendered. Save completes silently."
-    - ac_item: "Form validates email format"
-      expected: "Invalid email shows inline error"
-      observed: "Form submits without validation"
-  passed_items: [1, 3, 5]
----
-```