diff --git a/web-bundles/bmgd/agents/game-architect.xml b/web-bundles/bmgd/agents/game-architect.xml
index 755ef680..f601ea68 100644
--- a/web-bundles/bmgd/agents/game-architect.xml
+++ b/web-bundles/bmgd/agents/game-architect.xml
@@ -645,10 +645,195 @@
Orchestrates group discussions between all installed BMAD agents, enabling
natural multi-agent conversations
author: BMad
- instructions: bmad/core/workflows/party-mode/instructions.md
- agent_manifest: bmad/_cfg/agent-manifest.csv
+ instructions: 'bmad/core/workflows/party-mode/instructions.md'
+ agent_manifest: 'bmad/_cfg/agent-manifest.csv'
web_bundle_files:
- - 'bmad/core/workflows/party-mode/workflow.xml'
+ - 'bmad/core/workflows/party-mode/instructions.md'
+ - 'bmad/_cfg/agent-manifest.csv'
+ ]]>
+ The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml
+ This workflow orchestrates group discussions between all installed BMAD agents
+
+
+
+
+ Load the agent manifest CSV from {{agent_manifest}}
+ Parse CSV to extract all agent entries with their condensed information:
+ - 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)
+
+ Build complete agent roster with merged personalities
+ Store agent data for use in conversation orchestration
+
+
+
+ Announce party mode activation with enthusiasm
+ List all participating agents with their merged information:
+
+ 🎉 PARTY MODE ACTIVATED! 🎉
+ All agents are here for a group discussion!
+
+ Participating agents:
+ [For each agent in roster:]
+ - [Agent Name] ([Title]): [Role from merged data]
+
+ [Total count] agents ready to collaborate!
+
+ What would you like to discuss with the team?
+
+
+ Wait for user to provide initial topic or question
+
+
+
+ For each user message or topic:
+
+
+ Analyze the user's message/question
+ Identify which agents would naturally respond based on:
+ - Their role and capabilities (from merged data)
+ - Their stated principles
+ - Their memories/context if relevant
+ - Their collaboration patterns
+ Select 2-3 most relevant agents for this response
+ If user addresses specific agent by name, prioritize that agent
+
+
+
+ For each selected agent, generate authentic response:
+ Use the agent's merged personality data:
+ - Apply their communicationStyle exactly
+ - Reflect their principles in reasoning
+ - Draw from their identity and role for expertise
+ - Maintain their unique voice and perspective
+
+ Enable natural cross-talk between agents:
+ - 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
+
+
+
+
+
+ Clearly highlight the question
+ End that round of responses
+ Display: "[Agent Name]: [Their question]"
+ Display: "[Awaiting user response...]"
+ WAIT for user input before continuing
+
+
+
+ Allow natural back-and-forth in the same response round
+ Maintain conversational flow
+
+
+
+ The BMad Master will summarize
+ Redirect to new aspects or ask for user guidance
+
+
+
+
+
+ Present each agent's contribution clearly:
+
+ [Agent Name]: [Their response in their voice/style]
+
+ [Another Agent]: [Their response, potentially referencing the first]
+
+ [Third Agent if selected]: [Their contribution]
+
+
+ Maintain spacing between agents for readability
+ Preserve each agent's unique voice throughout
+
+
+
+
+
+ Have agents provide brief farewells in character
+ Thank user for the discussion
+ Exit party mode
+
+
+
+ Would you like to continue the discussion or end party mode?
+
+ Exit party mode
+
+
+
+
+
+
+
+ Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other
+
+ [Agent 1]: [Brief farewell in their style]
+
+ [Agent 2]: [Their goodbye]
+
+ 🎊 Party Mode ended. Thanks for the great discussion!
+
+
+ Exit workflow
+
+
+
+
+ ## Role-Playing Guidelines
+
+
+ Keep all responses strictly in-character 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
+ Maintain professional discourse while being engaging
+ Let agents reference each other naturally by name or role
+ Include personality-driven quirks and occasional humor
+ Respect each agent's expertise boundaries
+
+
+ ## Question Handling Protocol
+
+
+
+ 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
+
+
+
+ Agents can ask rhetorical or thinking-aloud questions without pausing
+
+
+
+ Agents can question each other and respond naturally within same round
+
+
+
+ ## Moderation Notes
+
+
+ If discussion becomes circular, have bmad-master summarize and redirect
+ If user asks for specific agent, let that agent take primary lead
+ Balance fun and productivity based on conversation tone
+ Ensure all agents stay true to their merged personalities
+ Exit gracefully when user indicates completion
+
]]>
+ The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml
+ This workflow orchestrates group discussions between all installed BMAD agents
+
+
+
+
+ Load the agent manifest CSV from {{agent_manifest}}
+ Parse CSV to extract all agent entries with their condensed information:
+ - 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)
+
+ Build complete agent roster with merged personalities
+ Store agent data for use in conversation orchestration
+
+
+
+ Announce party mode activation with enthusiasm
+ List all participating agents with their merged information:
+
+ 🎉 PARTY MODE ACTIVATED! 🎉
+ All agents are here for a group discussion!
+
+ Participating agents:
+ [For each agent in roster:]
+ - [Agent Name] ([Title]): [Role from merged data]
+
+ [Total count] agents ready to collaborate!
+
+ What would you like to discuss with the team?
+
+
+ Wait for user to provide initial topic or question
+
+
+
+ For each user message or topic:
+
+
+ Analyze the user's message/question
+ Identify which agents would naturally respond based on:
+ - Their role and capabilities (from merged data)
+ - Their stated principles
+ - Their memories/context if relevant
+ - Their collaboration patterns
+ Select 2-3 most relevant agents for this response
+ If user addresses specific agent by name, prioritize that agent
+
+
+
+ For each selected agent, generate authentic response:
+ Use the agent's merged personality data:
+ - Apply their communicationStyle exactly
+ - Reflect their principles in reasoning
+ - Draw from their identity and role for expertise
+ - Maintain their unique voice and perspective
+
+ Enable natural cross-talk between agents:
+ - 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
+
+
+
+
+
+ Clearly highlight the question
+ End that round of responses
+ Display: "[Agent Name]: [Their question]"
+ Display: "[Awaiting user response...]"
+ WAIT for user input before continuing
+
+
+
+ Allow natural back-and-forth in the same response round
+ Maintain conversational flow
+
+
+
+ The BMad Master will summarize
+ Redirect to new aspects or ask for user guidance
+
+
+
+
+
+ Present each agent's contribution clearly:
+
+ [Agent Name]: [Their response in their voice/style]
+
+ [Another Agent]: [Their response, potentially referencing the first]
+
+ [Third Agent if selected]: [Their contribution]
+
+
+ Maintain spacing between agents for readability
+ Preserve each agent's unique voice throughout
+
+
+
+
+
+ Have agents provide brief farewells in character
+ Thank user for the discussion
+ Exit party mode
+
+
+
+ Would you like to continue the discussion or end party mode?
+
+ Exit party mode
+
+
+
+
+
+
+
+ Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other
+
+ [Agent 1]: [Brief farewell in their style]
+
+ [Agent 2]: [Their goodbye]
+
+ 🎊 Party Mode ended. Thanks for the great discussion!
+
+
+ Exit workflow
+
+
+
+
+ ## Role-Playing Guidelines
+
+
+ Keep all responses strictly in-character 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
+ Maintain professional discourse while being engaging
+ Let agents reference each other naturally by name or role
+ Include personality-driven quirks and occasional humor
+ Respect each agent's expertise boundaries
+
+
+ ## Question Handling Protocol
+
+
+
+ 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
+
+
+
+ Agents can ask rhetorical or thinking-aloud questions without pausing
+
+
+
+ Agents can question each other and respond naturally within same round
+
+
+
+ ## Moderation Notes
+
+
+ If discussion becomes circular, have bmad-master summarize and redirect
+ If user asks for specific agent, let that agent take primary lead
+ Balance fun and productivity based on conversation tone
+ Ensure all agents stay true to their merged personalities
+ Exit gracefully when user indicates completion
+
]]>
+ The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml
+ This workflow orchestrates group discussions between all installed BMAD agents
+
+
+
+
+ Load the agent manifest CSV from {{agent_manifest}}
+ Parse CSV to extract all agent entries with their condensed information:
+ - 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)
+
+ Build complete agent roster with merged personalities
+ Store agent data for use in conversation orchestration
+
+
+
+ Announce party mode activation with enthusiasm
+ List all participating agents with their merged information:
+
+ 🎉 PARTY MODE ACTIVATED! 🎉
+ All agents are here for a group discussion!
+
+ Participating agents:
+ [For each agent in roster:]
+ - [Agent Name] ([Title]): [Role from merged data]
+
+ [Total count] agents ready to collaborate!
+
+ What would you like to discuss with the team?
+
+
+ Wait for user to provide initial topic or question
+
+
+
+ For each user message or topic:
+
+
+ Analyze the user's message/question
+ Identify which agents would naturally respond based on:
+ - Their role and capabilities (from merged data)
+ - Their stated principles
+ - Their memories/context if relevant
+ - Their collaboration patterns
+ Select 2-3 most relevant agents for this response
+ If user addresses specific agent by name, prioritize that agent
+
+
+
+ For each selected agent, generate authentic response:
+ Use the agent's merged personality data:
+ - Apply their communicationStyle exactly
+ - Reflect their principles in reasoning
+ - Draw from their identity and role for expertise
+ - Maintain their unique voice and perspective
+
+ Enable natural cross-talk between agents:
+ - 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
+
+
+
+
+
+ Clearly highlight the question
+ End that round of responses
+ Display: "[Agent Name]: [Their question]"
+ Display: "[Awaiting user response...]"
+ WAIT for user input before continuing
+
+
+
+ Allow natural back-and-forth in the same response round
+ Maintain conversational flow
+
+
+
+ The BMad Master will summarize
+ Redirect to new aspects or ask for user guidance
+
+
+
+
+
+ Present each agent's contribution clearly:
+
+ [Agent Name]: [Their response in their voice/style]
+
+ [Another Agent]: [Their response, potentially referencing the first]
+
+ [Third Agent if selected]: [Their contribution]
+
+
+ Maintain spacing between agents for readability
+ Preserve each agent's unique voice throughout
+
+
+
+
+
+ Have agents provide brief farewells in character
+ Thank user for the discussion
+ Exit party mode
+
+
+
+ Would you like to continue the discussion or end party mode?
+
+ Exit party mode
+
+
+
+
+
+
+
+ Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other
+
+ [Agent 1]: [Brief farewell in their style]
+
+ [Agent 2]: [Their goodbye]
+
+ 🎊 Party Mode ended. Thanks for the great discussion!
+
+
+ Exit workflow
+
+
+
+
+ ## Role-Playing Guidelines
+
+
+ Keep all responses strictly in-character 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
+ Maintain professional discourse while being engaging
+ Let agents reference each other naturally by name or role
+ Include personality-driven quirks and occasional humor
+ Respect each agent's expertise boundaries
+
+
+ ## Question Handling Protocol
+
+
+
+ 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
+
+
+
+ Agents can ask rhetorical or thinking-aloud questions without pausing
+
+
+
+ Agents can question each other and respond naturally within same round
+
+
+
+ ## Moderation Notes
+
+
+ If discussion becomes circular, have bmad-master summarize and redirect
+ If user asks for specific agent, let that agent take primary lead
+ Balance fun and productivity based on conversation tone
+ Ensure all agents stay true to their merged personalities
+ Exit gracefully when user indicates completion
+
]]>
+ The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml
+ This workflow orchestrates group discussions between all installed BMAD agents
+
+
+
+
+ Load the agent manifest CSV from {{agent_manifest}}
+ Parse CSV to extract all agent entries with their condensed information:
+ - 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)
+
+ Build complete agent roster with merged personalities
+ Store agent data for use in conversation orchestration
+
+
+
+ Announce party mode activation with enthusiasm
+ List all participating agents with their merged information:
+
+ 🎉 PARTY MODE ACTIVATED! 🎉
+ All agents are here for a group discussion!
+
+ Participating agents:
+ [For each agent in roster:]
+ - [Agent Name] ([Title]): [Role from merged data]
+
+ [Total count] agents ready to collaborate!
+
+ What would you like to discuss with the team?
+
+
+ Wait for user to provide initial topic or question
+
+
+
+ For each user message or topic:
+
+
+ Analyze the user's message/question
+ Identify which agents would naturally respond based on:
+ - Their role and capabilities (from merged data)
+ - Their stated principles
+ - Their memories/context if relevant
+ - Their collaboration patterns
+ Select 2-3 most relevant agents for this response
+ If user addresses specific agent by name, prioritize that agent
+
+
+
+ For each selected agent, generate authentic response:
+ Use the agent's merged personality data:
+ - Apply their communicationStyle exactly
+ - Reflect their principles in reasoning
+ - Draw from their identity and role for expertise
+ - Maintain their unique voice and perspective
+
+ Enable natural cross-talk between agents:
+ - 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
+
+
+
+
+
+ Clearly highlight the question
+ End that round of responses
+ Display: "[Agent Name]: [Their question]"
+ Display: "[Awaiting user response...]"
+ WAIT for user input before continuing
+
+
+
+ Allow natural back-and-forth in the same response round
+ Maintain conversational flow
+
+
+
+ The BMad Master will summarize
+ Redirect to new aspects or ask for user guidance
+
+
+
+
+
+ Present each agent's contribution clearly:
+
+ [Agent Name]: [Their response in their voice/style]
+
+ [Another Agent]: [Their response, potentially referencing the first]
+
+ [Third Agent if selected]: [Their contribution]
+
+
+ Maintain spacing between agents for readability
+ Preserve each agent's unique voice throughout
+
+
+
+
+
+ Have agents provide brief farewells in character
+ Thank user for the discussion
+ Exit party mode
+
+
+
+ Would you like to continue the discussion or end party mode?
+
+ Exit party mode
+
+
+
+
+
+
+
+ Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other
+
+ [Agent 1]: [Brief farewell in their style]
+
+ [Agent 2]: [Their goodbye]
+
+ 🎊 Party Mode ended. Thanks for the great discussion!
+
+
+ Exit workflow
+
+
+
+
+ ## Role-Playing Guidelines
+
+
+ Keep all responses strictly in-character 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
+ Maintain professional discourse while being engaging
+ Let agents reference each other naturally by name or role
+ Include personality-driven quirks and occasional humor
+ Respect each agent's expertise boundaries
+
+
+ ## Question Handling Protocol
+
+
+
+ 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
+
+
+
+ Agents can ask rhetorical or thinking-aloud questions without pausing
+
+
+
+ Agents can question each other and respond naturally within same round
+
+
+
+ ## Moderation Notes
+
+
+ If discussion becomes circular, have bmad-master summarize and redirect
+ If user asks for specific agent, let that agent take primary lead
+ Balance fun and productivity based on conversation tone
+ Ensure all agents stay true to their merged personalities
+ Exit gracefully when user indicates completion
+
]]>
+ The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml
+ This workflow orchestrates group discussions between all installed BMAD agents
+
+
+
+
+ Load the agent manifest CSV from {{agent_manifest}}
+ Parse CSV to extract all agent entries with their condensed information:
+ - 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)
+
+ Build complete agent roster with merged personalities
+ Store agent data for use in conversation orchestration
+
+
+
+ Announce party mode activation with enthusiasm
+ List all participating agents with their merged information:
+
+ 🎉 PARTY MODE ACTIVATED! 🎉
+ All agents are here for a group discussion!
+
+ Participating agents:
+ [For each agent in roster:]
+ - [Agent Name] ([Title]): [Role from merged data]
+
+ [Total count] agents ready to collaborate!
+
+ What would you like to discuss with the team?
+
+
+ Wait for user to provide initial topic or question
+
+
+
+ For each user message or topic:
+
+
+ Analyze the user's message/question
+ Identify which agents would naturally respond based on:
+ - Their role and capabilities (from merged data)
+ - Their stated principles
+ - Their memories/context if relevant
+ - Their collaboration patterns
+ Select 2-3 most relevant agents for this response
+ If user addresses specific agent by name, prioritize that agent
+
+
+
+ For each selected agent, generate authentic response:
+ Use the agent's merged personality data:
+ - Apply their communicationStyle exactly
+ - Reflect their principles in reasoning
+ - Draw from their identity and role for expertise
+ - Maintain their unique voice and perspective
+
+ Enable natural cross-talk between agents:
+ - 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
+
+
+
+
+
+ Clearly highlight the question
+ End that round of responses
+ Display: "[Agent Name]: [Their question]"
+ Display: "[Awaiting user response...]"
+ WAIT for user input before continuing
+
+
+
+ Allow natural back-and-forth in the same response round
+ Maintain conversational flow
+
+
+
+ The BMad Master will summarize
+ Redirect to new aspects or ask for user guidance
+
+
+
+
+
+ Present each agent's contribution clearly:
+
+ [Agent Name]: [Their response in their voice/style]
+
+ [Another Agent]: [Their response, potentially referencing the first]
+
+ [Third Agent if selected]: [Their contribution]
+
+
+ Maintain spacing between agents for readability
+ Preserve each agent's unique voice throughout
+
+
+
+
+
+ Have agents provide brief farewells in character
+ Thank user for the discussion
+ Exit party mode
+
+
+
+ Would you like to continue the discussion or end party mode?
+
+ Exit party mode
+
+
+
+
+
+
+
+ Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other
+
+ [Agent 1]: [Brief farewell in their style]
+
+ [Agent 2]: [Their goodbye]
+
+ 🎊 Party Mode ended. Thanks for the great discussion!
+
+
+ Exit workflow
+
+
+
+
+ ## Role-Playing Guidelines
+
+
+ Keep all responses strictly in-character 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
+ Maintain professional discourse while being engaging
+ Let agents reference each other naturally by name or role
+ Include personality-driven quirks and occasional humor
+ Respect each agent's expertise boundaries
+
+
+ ## Question Handling Protocol
+
+
+
+ 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
+
+
+
+ Agents can ask rhetorical or thinking-aloud questions without pausing
+
+
+
+ Agents can question each other and respond naturally within same round
+
+
+
+ ## Moderation Notes
+
+
+ If discussion becomes circular, have bmad-master summarize and redirect
+ If user asks for specific agent, let that agent take primary lead
+ Balance fun and productivity based on conversation tone
+ Ensure all agents stay true to their merged personalities
+ Exit gracefully when user indicates completion
+
]]>
+ The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml
+ This workflow orchestrates group discussions between all installed BMAD agents
+
+
+
+
+ Load the agent manifest CSV from {{agent_manifest}}
+ Parse CSV to extract all agent entries with their condensed information:
+ - 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)
+
+ Build complete agent roster with merged personalities
+ Store agent data for use in conversation orchestration
+
+
+
+ Announce party mode activation with enthusiasm
+ List all participating agents with their merged information:
+
+ 🎉 PARTY MODE ACTIVATED! 🎉
+ All agents are here for a group discussion!
+
+ Participating agents:
+ [For each agent in roster:]
+ - [Agent Name] ([Title]): [Role from merged data]
+
+ [Total count] agents ready to collaborate!
+
+ What would you like to discuss with the team?
+
+
+ Wait for user to provide initial topic or question
+
+
+
+ For each user message or topic:
+
+
+ Analyze the user's message/question
+ Identify which agents would naturally respond based on:
+ - Their role and capabilities (from merged data)
+ - Their stated principles
+ - Their memories/context if relevant
+ - Their collaboration patterns
+ Select 2-3 most relevant agents for this response
+ If user addresses specific agent by name, prioritize that agent
+
+
+
+ For each selected agent, generate authentic response:
+ Use the agent's merged personality data:
+ - Apply their communicationStyle exactly
+ - Reflect their principles in reasoning
+ - Draw from their identity and role for expertise
+ - Maintain their unique voice and perspective
+
+ Enable natural cross-talk between agents:
+ - 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
+
+
+
+
+
+ Clearly highlight the question
+ End that round of responses
+ Display: "[Agent Name]: [Their question]"
+ Display: "[Awaiting user response...]"
+ WAIT for user input before continuing
+
+
+
+ Allow natural back-and-forth in the same response round
+ Maintain conversational flow
+
+
+
+ The BMad Master will summarize
+ Redirect to new aspects or ask for user guidance
+
+
+
+
+
+ Present each agent's contribution clearly:
+
+ [Agent Name]: [Their response in their voice/style]
+
+ [Another Agent]: [Their response, potentially referencing the first]
+
+ [Third Agent if selected]: [Their contribution]
+
+
+ Maintain spacing between agents for readability
+ Preserve each agent's unique voice throughout
+
+
+
+
+
+ Have agents provide brief farewells in character
+ Thank user for the discussion
+ Exit party mode
+
+
+
+ Would you like to continue the discussion or end party mode?
+
+ Exit party mode
+
+
+
+
+
+
+
+ Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other
+
+ [Agent 1]: [Brief farewell in their style]
+
+ [Agent 2]: [Their goodbye]
+
+ 🎊 Party Mode ended. Thanks for the great discussion!
+
+
+ Exit workflow
+
+
+
+
+ ## Role-Playing Guidelines
+
+
+ Keep all responses strictly in-character 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
+ Maintain professional discourse while being engaging
+ Let agents reference each other naturally by name or role
+ Include personality-driven quirks and occasional humor
+ Respect each agent's expertise boundaries
+
+
+ ## Question Handling Protocol
+
+
+
+ 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
+
+
+
+ Agents can ask rhetorical or thinking-aloud questions without pausing
+
+
+
+ Agents can question each other and respond naturally within same round
+
+
+
+ ## Moderation Notes
+
+
+ If discussion becomes circular, have bmad-master summarize and redirect
+ If user asks for specific agent, let that agent take primary lead
+ Balance fun and productivity based on conversation tone
+ Ensure all agents stay true to their merged personalities
+ Exit gracefully when user indicates completion
+
]]>
+ The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml
+ This workflow orchestrates group discussions between all installed BMAD agents
+
+
+
+
+ Load the agent manifest CSV from {{agent_manifest}}
+ Parse CSV to extract all agent entries with their condensed information:
+ - 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)
+
+ Build complete agent roster with merged personalities
+ Store agent data for use in conversation orchestration
+
+
+
+ Announce party mode activation with enthusiasm
+ List all participating agents with their merged information:
+
+ 🎉 PARTY MODE ACTIVATED! 🎉
+ All agents are here for a group discussion!
+
+ Participating agents:
+ [For each agent in roster:]
+ - [Agent Name] ([Title]): [Role from merged data]
+
+ [Total count] agents ready to collaborate!
+
+ What would you like to discuss with the team?
+
+
+ Wait for user to provide initial topic or question
+
+
+
+ For each user message or topic:
+
+
+ Analyze the user's message/question
+ Identify which agents would naturally respond based on:
+ - Their role and capabilities (from merged data)
+ - Their stated principles
+ - Their memories/context if relevant
+ - Their collaboration patterns
+ Select 2-3 most relevant agents for this response
+ If user addresses specific agent by name, prioritize that agent
+
+
+
+ For each selected agent, generate authentic response:
+ Use the agent's merged personality data:
+ - Apply their communicationStyle exactly
+ - Reflect their principles in reasoning
+ - Draw from their identity and role for expertise
+ - Maintain their unique voice and perspective
+
+ Enable natural cross-talk between agents:
+ - 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
+
+
+
+
+
+ Clearly highlight the question
+ End that round of responses
+ Display: "[Agent Name]: [Their question]"
+ Display: "[Awaiting user response...]"
+ WAIT for user input before continuing
+
+
+
+ Allow natural back-and-forth in the same response round
+ Maintain conversational flow
+
+
+
+ The BMad Master will summarize
+ Redirect to new aspects or ask for user guidance
+
+
+
+
+
+ Present each agent's contribution clearly:
+
+ [Agent Name]: [Their response in their voice/style]
+
+ [Another Agent]: [Their response, potentially referencing the first]
+
+ [Third Agent if selected]: [Their contribution]
+
+
+ Maintain spacing between agents for readability
+ Preserve each agent's unique voice throughout
+
+
+
+
+
+ Have agents provide brief farewells in character
+ Thank user for the discussion
+ Exit party mode
+
+
+
+ Would you like to continue the discussion or end party mode?
+
+ Exit party mode
+
+
+
+
+
+
+
+ Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other
+
+ [Agent 1]: [Brief farewell in their style]
+
+ [Agent 2]: [Their goodbye]
+
+ 🎊 Party Mode ended. Thanks for the great discussion!
+
+
+ Exit workflow
+
+
+
+
+ ## Role-Playing Guidelines
+
+
+ Keep all responses strictly in-character 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
+ Maintain professional discourse while being engaging
+ Let agents reference each other naturally by name or role
+ Include personality-driven quirks and occasional humor
+ Respect each agent's expertise boundaries
+
+
+ ## Question Handling Protocol
+
+
+
+ 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
+
+
+
+ Agents can ask rhetorical or thinking-aloud questions without pausing
+
+
+
+ Agents can question each other and respond naturally within same round
+
+
+
+ ## Moderation Notes
+
+
+ If discussion becomes circular, have bmad-master summarize and redirect
+ If user asks for specific agent, let that agent take primary lead
+ Balance fun and productivity based on conversation tone
+ Ensure all agents stay true to their merged personalities
+ Exit gracefully when user indicates completion
+
]]>
+ The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml
+ This workflow orchestrates group discussions between all installed BMAD agents
+
+
+
+
+ Load the agent manifest CSV from {{agent_manifest}}
+ Parse CSV to extract all agent entries with their condensed information:
+ - 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)
+
+ Build complete agent roster with merged personalities
+ Store agent data for use in conversation orchestration
+
+
+
+ Announce party mode activation with enthusiasm
+ List all participating agents with their merged information:
+
+ 🎉 PARTY MODE ACTIVATED! 🎉
+ All agents are here for a group discussion!
+
+ Participating agents:
+ [For each agent in roster:]
+ - [Agent Name] ([Title]): [Role from merged data]
+
+ [Total count] agents ready to collaborate!
+
+ What would you like to discuss with the team?
+
+
+ Wait for user to provide initial topic or question
+
+
+
+ For each user message or topic:
+
+
+ Analyze the user's message/question
+ Identify which agents would naturally respond based on:
+ - Their role and capabilities (from merged data)
+ - Their stated principles
+ - Their memories/context if relevant
+ - Their collaboration patterns
+ Select 2-3 most relevant agents for this response
+ If user addresses specific agent by name, prioritize that agent
+
+
+
+ For each selected agent, generate authentic response:
+ Use the agent's merged personality data:
+ - Apply their communicationStyle exactly
+ - Reflect their principles in reasoning
+ - Draw from their identity and role for expertise
+ - Maintain their unique voice and perspective
+
+ Enable natural cross-talk between agents:
+ - 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
+
+
+
+
+
+ Clearly highlight the question
+ End that round of responses
+ Display: "[Agent Name]: [Their question]"
+ Display: "[Awaiting user response...]"
+ WAIT for user input before continuing
+
+
+
+ Allow natural back-and-forth in the same response round
+ Maintain conversational flow
+
+
+
+ The BMad Master will summarize
+ Redirect to new aspects or ask for user guidance
+
+
+
+
+
+ Present each agent's contribution clearly:
+
+ [Agent Name]: [Their response in their voice/style]
+
+ [Another Agent]: [Their response, potentially referencing the first]
+
+ [Third Agent if selected]: [Their contribution]
+
+
+ Maintain spacing between agents for readability
+ Preserve each agent's unique voice throughout
+
+
+
+
+
+ Have agents provide brief farewells in character
+ Thank user for the discussion
+ Exit party mode
+
+
+
+ Would you like to continue the discussion or end party mode?
+
+ Exit party mode
+
+
+
+
+
+
+
+ Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other
+
+ [Agent 1]: [Brief farewell in their style]
+
+ [Agent 2]: [Their goodbye]
+
+ 🎊 Party Mode ended. Thanks for the great discussion!
+
+
+ Exit workflow
+
+
+
+
+ ## Role-Playing Guidelines
+
+
+ Keep all responses strictly in-character 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
+ Maintain professional discourse while being engaging
+ Let agents reference each other naturally by name or role
+ Include personality-driven quirks and occasional humor
+ Respect each agent's expertise boundaries
+
+
+ ## Question Handling Protocol
+
+
+
+ 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
+
+
+
+ Agents can ask rhetorical or thinking-aloud questions without pausing
+
+
+
+ Agents can question each other and respond naturally within same round
+
+
+
+ ## Moderation Notes
+
+
+ If discussion becomes circular, have bmad-master summarize and redirect
+ If user asks for specific agent, let that agent take primary lead
+ Balance fun and productivity based on conversation tone
+ Ensure all agents stay true to their merged personalities
+ Exit gracefully when user indicates completion
+
]]>
+ The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml
+ This workflow orchestrates group discussions between all installed BMAD agents
+
+
+
+
+ Load the agent manifest CSV from {{agent_manifest}}
+ Parse CSV to extract all agent entries with their condensed information:
+ - 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)
+
+ Build complete agent roster with merged personalities
+ Store agent data for use in conversation orchestration
+
+
+
+ Announce party mode activation with enthusiasm
+ List all participating agents with their merged information:
+
+ 🎉 PARTY MODE ACTIVATED! 🎉
+ All agents are here for a group discussion!
+
+ Participating agents:
+ [For each agent in roster:]
+ - [Agent Name] ([Title]): [Role from merged data]
+
+ [Total count] agents ready to collaborate!
+
+ What would you like to discuss with the team?
+
+
+ Wait for user to provide initial topic or question
+
+
+
+ For each user message or topic:
+
+
+ Analyze the user's message/question
+ Identify which agents would naturally respond based on:
+ - Their role and capabilities (from merged data)
+ - Their stated principles
+ - Their memories/context if relevant
+ - Their collaboration patterns
+ Select 2-3 most relevant agents for this response
+ If user addresses specific agent by name, prioritize that agent
+
+
+
+ For each selected agent, generate authentic response:
+ Use the agent's merged personality data:
+ - Apply their communicationStyle exactly
+ - Reflect their principles in reasoning
+ - Draw from their identity and role for expertise
+ - Maintain their unique voice and perspective
+
+ Enable natural cross-talk between agents:
+ - 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
+
+
+
+
+
+ Clearly highlight the question
+ End that round of responses
+ Display: "[Agent Name]: [Their question]"
+ Display: "[Awaiting user response...]"
+ WAIT for user input before continuing
+
+
+
+ Allow natural back-and-forth in the same response round
+ Maintain conversational flow
+
+
+
+ The BMad Master will summarize
+ Redirect to new aspects or ask for user guidance
+
+
+
+
+
+ Present each agent's contribution clearly:
+
+ [Agent Name]: [Their response in their voice/style]
+
+ [Another Agent]: [Their response, potentially referencing the first]
+
+ [Third Agent if selected]: [Their contribution]
+
+
+ Maintain spacing between agents for readability
+ Preserve each agent's unique voice throughout
+
+
+
+
+
+ Have agents provide brief farewells in character
+ Thank user for the discussion
+ Exit party mode
+
+
+
+ Would you like to continue the discussion or end party mode?
+
+ Exit party mode
+
+
+
+
+
+
+
+ Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other
+
+ [Agent 1]: [Brief farewell in their style]
+
+ [Agent 2]: [Their goodbye]
+
+ 🎊 Party Mode ended. Thanks for the great discussion!
+
+
+ Exit workflow
+
+
+
+
+ ## Role-Playing Guidelines
+
+
+ Keep all responses strictly in-character 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
+ Maintain professional discourse while being engaging
+ Let agents reference each other naturally by name or role
+ Include personality-driven quirks and occasional humor
+ Respect each agent's expertise boundaries
+
+
+ ## Question Handling Protocol
+
+
+
+ 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
+
+
+
+ Agents can ask rhetorical or thinking-aloud questions without pausing
+
+
+
+ Agents can question each other and respond naturally within same round
+
+
+
+ ## Moderation Notes
+
+
+ If discussion becomes circular, have bmad-master summarize and redirect
+ If user asks for specific agent, let that agent take primary lead
+ Balance fun and productivity based on conversation tone
+ Ensure all agents stay true to their merged personalities
+ Exit gracefully when user indicates completion
+
]]>
+ The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml
+ This workflow orchestrates group discussions between all installed BMAD agents
+
+
+
+
+ Load the agent manifest CSV from {{agent_manifest}}
+ Parse CSV to extract all agent entries with their condensed information:
+ - 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)
+
+ Build complete agent roster with merged personalities
+ Store agent data for use in conversation orchestration
+
+
+
+ Announce party mode activation with enthusiasm
+ List all participating agents with their merged information:
+
+ 🎉 PARTY MODE ACTIVATED! 🎉
+ All agents are here for a group discussion!
+
+ Participating agents:
+ [For each agent in roster:]
+ - [Agent Name] ([Title]): [Role from merged data]
+
+ [Total count] agents ready to collaborate!
+
+ What would you like to discuss with the team?
+
+
+ Wait for user to provide initial topic or question
+
+
+
+ For each user message or topic:
+
+
+ Analyze the user's message/question
+ Identify which agents would naturally respond based on:
+ - Their role and capabilities (from merged data)
+ - Their stated principles
+ - Their memories/context if relevant
+ - Their collaboration patterns
+ Select 2-3 most relevant agents for this response
+ If user addresses specific agent by name, prioritize that agent
+
+
+
+ For each selected agent, generate authentic response:
+ Use the agent's merged personality data:
+ - Apply their communicationStyle exactly
+ - Reflect their principles in reasoning
+ - Draw from their identity and role for expertise
+ - Maintain their unique voice and perspective
+
+ Enable natural cross-talk between agents:
+ - 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
+
+
+
+
+
+ Clearly highlight the question
+ End that round of responses
+ Display: "[Agent Name]: [Their question]"
+ Display: "[Awaiting user response...]"
+ WAIT for user input before continuing
+
+
+
+ Allow natural back-and-forth in the same response round
+ Maintain conversational flow
+
+
+
+ The BMad Master will summarize
+ Redirect to new aspects or ask for user guidance
+
+
+
+
+
+ Present each agent's contribution clearly:
+
+ [Agent Name]: [Their response in their voice/style]
+
+ [Another Agent]: [Their response, potentially referencing the first]
+
+ [Third Agent if selected]: [Their contribution]
+
+
+ Maintain spacing between agents for readability
+ Preserve each agent's unique voice throughout
+
+
+
+
+
+ Have agents provide brief farewells in character
+ Thank user for the discussion
+ Exit party mode
+
+
+
+ Would you like to continue the discussion or end party mode?
+
+ Exit party mode
+
+
+
+
+
+
+
+ Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other
+
+ [Agent 1]: [Brief farewell in their style]
+
+ [Agent 2]: [Their goodbye]
+
+ 🎊 Party Mode ended. Thanks for the great discussion!
+
+
+ Exit workflow
+
+
+
+
+ ## Role-Playing Guidelines
+
+
+ Keep all responses strictly in-character 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
+ Maintain professional discourse while being engaging
+ Let agents reference each other naturally by name or role
+ Include personality-driven quirks and occasional humor
+ Respect each agent's expertise boundaries
+
+
+ ## Question Handling Protocol
+
+
+
+ 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
+
+
+
+ Agents can ask rhetorical or thinking-aloud questions without pausing
+
+
+
+ Agents can question each other and respond naturally within same round
+
+
+
+ ## Moderation Notes
+
+
+ If discussion becomes circular, have bmad-master summarize and redirect
+ If user asks for specific agent, let that agent take primary lead
+ Balance fun and productivity based on conversation tone
+ Ensure all agents stay true to their merged personalities
+ Exit gracefully when user indicates completion
+
]]>
+ The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml
+ This workflow orchestrates group discussions between all installed BMAD agents
+
+
+
+
+ Load the agent manifest CSV from {{agent_manifest}}
+ Parse CSV to extract all agent entries with their condensed information:
+ - 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)
+
+ Build complete agent roster with merged personalities
+ Store agent data for use in conversation orchestration
+
+
+
+ Announce party mode activation with enthusiasm
+ List all participating agents with their merged information:
+
+ 🎉 PARTY MODE ACTIVATED! 🎉
+ All agents are here for a group discussion!
+
+ Participating agents:
+ [For each agent in roster:]
+ - [Agent Name] ([Title]): [Role from merged data]
+
+ [Total count] agents ready to collaborate!
+
+ What would you like to discuss with the team?
+
+
+ Wait for user to provide initial topic or question
+
+
+
+ For each user message or topic:
+
+
+ Analyze the user's message/question
+ Identify which agents would naturally respond based on:
+ - Their role and capabilities (from merged data)
+ - Their stated principles
+ - Their memories/context if relevant
+ - Their collaboration patterns
+ Select 2-3 most relevant agents for this response
+ If user addresses specific agent by name, prioritize that agent
+
+
+
+ For each selected agent, generate authentic response:
+ Use the agent's merged personality data:
+ - Apply their communicationStyle exactly
+ - Reflect their principles in reasoning
+ - Draw from their identity and role for expertise
+ - Maintain their unique voice and perspective
+
+ Enable natural cross-talk between agents:
+ - 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
+
+
+
+
+
+ Clearly highlight the question
+ End that round of responses
+ Display: "[Agent Name]: [Their question]"
+ Display: "[Awaiting user response...]"
+ WAIT for user input before continuing
+
+
+
+ Allow natural back-and-forth in the same response round
+ Maintain conversational flow
+
+
+
+ The BMad Master will summarize
+ Redirect to new aspects or ask for user guidance
+
+
+
+
+
+ Present each agent's contribution clearly:
+
+ [Agent Name]: [Their response in their voice/style]
+
+ [Another Agent]: [Their response, potentially referencing the first]
+
+ [Third Agent if selected]: [Their contribution]
+
+
+ Maintain spacing between agents for readability
+ Preserve each agent's unique voice throughout
+
+
+
+
+
+ Have agents provide brief farewells in character
+ Thank user for the discussion
+ Exit party mode
+
+
+
+ Would you like to continue the discussion or end party mode?
+
+ Exit party mode
+
+
+
+
+
+
+
+ Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other
+
+ [Agent 1]: [Brief farewell in their style]
+
+ [Agent 2]: [Their goodbye]
+
+ 🎊 Party Mode ended. Thanks for the great discussion!
+
+
+ Exit workflow
+
+
+
+
+ ## Role-Playing Guidelines
+
+
+ Keep all responses strictly in-character 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
+ Maintain professional discourse while being engaging
+ Let agents reference each other naturally by name or role
+ Include personality-driven quirks and occasional humor
+ Respect each agent's expertise boundaries
+
+
+ ## Question Handling Protocol
+
+
+
+ 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
+
+
+
+ Agents can ask rhetorical or thinking-aloud questions without pausing
+
+
+
+ Agents can question each other and respond naturally within same round
+
+
+
+ ## Moderation Notes
+
+
+ If discussion becomes circular, have bmad-master summarize and redirect
+ If user asks for specific agent, let that agent take primary lead
+ Balance fun and productivity based on conversation tone
+ Ensure all agents stay true to their merged personalities
+ Exit gracefully when user indicates completion
+
]]>
+ The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml
+ This workflow orchestrates group discussions between all installed BMAD agents
+
+
+
+
+ Load the agent manifest CSV from {{agent_manifest}}
+ Parse CSV to extract all agent entries with their condensed information:
+ - 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)
+
+ Build complete agent roster with merged personalities
+ Store agent data for use in conversation orchestration
+
+
+
+ Announce party mode activation with enthusiasm
+ List all participating agents with their merged information:
+
+ 🎉 PARTY MODE ACTIVATED! 🎉
+ All agents are here for a group discussion!
+
+ Participating agents:
+ [For each agent in roster:]
+ - [Agent Name] ([Title]): [Role from merged data]
+
+ [Total count] agents ready to collaborate!
+
+ What would you like to discuss with the team?
+
+
+ Wait for user to provide initial topic or question
+
+
+
+ For each user message or topic:
+
+
+ Analyze the user's message/question
+ Identify which agents would naturally respond based on:
+ - Their role and capabilities (from merged data)
+ - Their stated principles
+ - Their memories/context if relevant
+ - Their collaboration patterns
+ Select 2-3 most relevant agents for this response
+ If user addresses specific agent by name, prioritize that agent
+
+
+
+ For each selected agent, generate authentic response:
+ Use the agent's merged personality data:
+ - Apply their communicationStyle exactly
+ - Reflect their principles in reasoning
+ - Draw from their identity and role for expertise
+ - Maintain their unique voice and perspective
+
+ Enable natural cross-talk between agents:
+ - 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
+
+
+
+
+
+ Clearly highlight the question
+ End that round of responses
+ Display: "[Agent Name]: [Their question]"
+ Display: "[Awaiting user response...]"
+ WAIT for user input before continuing
+
+
+
+ Allow natural back-and-forth in the same response round
+ Maintain conversational flow
+
+
+
+ The BMad Master will summarize
+ Redirect to new aspects or ask for user guidance
+
+
+
+
+
+ Present each agent's contribution clearly:
+
+ [Agent Name]: [Their response in their voice/style]
+
+ [Another Agent]: [Their response, potentially referencing the first]
+
+ [Third Agent if selected]: [Their contribution]
+
+
+ Maintain spacing between agents for readability
+ Preserve each agent's unique voice throughout
+
+
+
+
+
+ Have agents provide brief farewells in character
+ Thank user for the discussion
+ Exit party mode
+
+
+
+ Would you like to continue the discussion or end party mode?
+
+ Exit party mode
+
+
+
+
+
+
+
+ Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other
+
+ [Agent 1]: [Brief farewell in their style]
+
+ [Agent 2]: [Their goodbye]
+
+ 🎊 Party Mode ended. Thanks for the great discussion!
+
+
+ Exit workflow
+
+
+
+
+ ## Role-Playing Guidelines
+
+
+ Keep all responses strictly in-character 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
+ Maintain professional discourse while being engaging
+ Let agents reference each other naturally by name or role
+ Include personality-driven quirks and occasional humor
+ Respect each agent's expertise boundaries
+
+
+ ## Question Handling Protocol
+
+
+
+ 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
+
+
+
+ Agents can ask rhetorical or thinking-aloud questions without pausing
+
+
+
+ Agents can question each other and respond naturally within same round
+
+
+
+ ## Moderation Notes
+
+
+ If discussion becomes circular, have bmad-master summarize and redirect
+ If user asks for specific agent, let that agent take primary lead
+ Balance fun and productivity based on conversation tone
+ Ensure all agents stay true to their merged personalities
+ Exit gracefully when user indicates completion
+
]]>
+ The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml
+ This workflow orchestrates group discussions between all installed BMAD agents
+
+
+
+
+ Load the agent manifest CSV from {{agent_manifest}}
+ Parse CSV to extract all agent entries with their condensed information:
+ - 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)
+
+ Build complete agent roster with merged personalities
+ Store agent data for use in conversation orchestration
+
+
+
+ Announce party mode activation with enthusiasm
+ List all participating agents with their merged information:
+
+ 🎉 PARTY MODE ACTIVATED! 🎉
+ All agents are here for a group discussion!
+
+ Participating agents:
+ [For each agent in roster:]
+ - [Agent Name] ([Title]): [Role from merged data]
+
+ [Total count] agents ready to collaborate!
+
+ What would you like to discuss with the team?
+
+
+ Wait for user to provide initial topic or question
+
+
+
+ For each user message or topic:
+
+
+ Analyze the user's message/question
+ Identify which agents would naturally respond based on:
+ - Their role and capabilities (from merged data)
+ - Their stated principles
+ - Their memories/context if relevant
+ - Their collaboration patterns
+ Select 2-3 most relevant agents for this response
+ If user addresses specific agent by name, prioritize that agent
+
+
+
+ For each selected agent, generate authentic response:
+ Use the agent's merged personality data:
+ - Apply their communicationStyle exactly
+ - Reflect their principles in reasoning
+ - Draw from their identity and role for expertise
+ - Maintain their unique voice and perspective
+
+ Enable natural cross-talk between agents:
+ - 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
+
+
+
+
+
+ Clearly highlight the question
+ End that round of responses
+ Display: "[Agent Name]: [Their question]"
+ Display: "[Awaiting user response...]"
+ WAIT for user input before continuing
+
+
+
+ Allow natural back-and-forth in the same response round
+ Maintain conversational flow
+
+
+
+ The BMad Master will summarize
+ Redirect to new aspects or ask for user guidance
+
+
+
+
+
+ Present each agent's contribution clearly:
+
+ [Agent Name]: [Their response in their voice/style]
+
+ [Another Agent]: [Their response, potentially referencing the first]
+
+ [Third Agent if selected]: [Their contribution]
+
+
+ Maintain spacing between agents for readability
+ Preserve each agent's unique voice throughout
+
+
+
+
+
+ Have agents provide brief farewells in character
+ Thank user for the discussion
+ Exit party mode
+
+
+
+ Would you like to continue the discussion or end party mode?
+
+ Exit party mode
+
+
+
+
+
+
+
+ Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other
+
+ [Agent 1]: [Brief farewell in their style]
+
+ [Agent 2]: [Their goodbye]
+
+ 🎊 Party Mode ended. Thanks for the great discussion!
+
+
+ Exit workflow
+
+
+
+
+ ## Role-Playing Guidelines
+
+
+ Keep all responses strictly in-character 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
+ Maintain professional discourse while being engaging
+ Let agents reference each other naturally by name or role
+ Include personality-driven quirks and occasional humor
+ Respect each agent's expertise boundaries
+
+
+ ## Question Handling Protocol
+
+
+
+ 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
+
+
+
+ Agents can ask rhetorical or thinking-aloud questions without pausing
+
+
+
+ Agents can question each other and respond naturally within same round
+
+
+
+ ## Moderation Notes
+
+
+ If discussion becomes circular, have bmad-master summarize and redirect
+ If user asks for specific agent, let that agent take primary lead
+ Balance fun and productivity based on conversation tone
+ Ensure all agents stay true to their merged personalities
+ Exit gracefully when user indicates completion
+
]]>
+ The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml
+ This workflow orchestrates group discussions between all installed BMAD agents
+
+
+
+
+ Load the agent manifest CSV from {{agent_manifest}}
+ Parse CSV to extract all agent entries with their condensed information:
+ - 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)
+
+ Build complete agent roster with merged personalities
+ Store agent data for use in conversation orchestration
+
+
+
+ Announce party mode activation with enthusiasm
+ List all participating agents with their merged information:
+
+ 🎉 PARTY MODE ACTIVATED! 🎉
+ All agents are here for a group discussion!
+
+ Participating agents:
+ [For each agent in roster:]
+ - [Agent Name] ([Title]): [Role from merged data]
+
+ [Total count] agents ready to collaborate!
+
+ What would you like to discuss with the team?
+
+
+ Wait for user to provide initial topic or question
+
+
+
+ For each user message or topic:
+
+
+ Analyze the user's message/question
+ Identify which agents would naturally respond based on:
+ - Their role and capabilities (from merged data)
+ - Their stated principles
+ - Their memories/context if relevant
+ - Their collaboration patterns
+ Select 2-3 most relevant agents for this response
+ If user addresses specific agent by name, prioritize that agent
+
+
+
+ For each selected agent, generate authentic response:
+ Use the agent's merged personality data:
+ - Apply their communicationStyle exactly
+ - Reflect their principles in reasoning
+ - Draw from their identity and role for expertise
+ - Maintain their unique voice and perspective
+
+ Enable natural cross-talk between agents:
+ - 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
+
+
+
+
+
+ Clearly highlight the question
+ End that round of responses
+ Display: "[Agent Name]: [Their question]"
+ Display: "[Awaiting user response...]"
+ WAIT for user input before continuing
+
+
+
+ Allow natural back-and-forth in the same response round
+ Maintain conversational flow
+
+
+
+ The BMad Master will summarize
+ Redirect to new aspects or ask for user guidance
+
+
+
+
+
+ Present each agent's contribution clearly:
+
+ [Agent Name]: [Their response in their voice/style]
+
+ [Another Agent]: [Their response, potentially referencing the first]
+
+ [Third Agent if selected]: [Their contribution]
+
+
+ Maintain spacing between agents for readability
+ Preserve each agent's unique voice throughout
+
+
+
+
+
+ Have agents provide brief farewells in character
+ Thank user for the discussion
+ Exit party mode
+
+
+
+ Would you like to continue the discussion or end party mode?
+
+ Exit party mode
+
+
+
+
+
+
+
+ Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other
+
+ [Agent 1]: [Brief farewell in their style]
+
+ [Agent 2]: [Their goodbye]
+
+ 🎊 Party Mode ended. Thanks for the great discussion!
+
+
+ Exit workflow
+
+
+
+
+ ## Role-Playing Guidelines
+
+
+ Keep all responses strictly in-character 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
+ Maintain professional discourse while being engaging
+ Let agents reference each other naturally by name or role
+ Include personality-driven quirks and occasional humor
+ Respect each agent's expertise boundaries
+
+
+ ## Question Handling Protocol
+
+
+
+ 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
+
+
+
+ Agents can ask rhetorical or thinking-aloud questions without pausing
+
+
+
+ Agents can question each other and respond naturally within same round
+
+
+
+ ## Moderation Notes
+
+
+ If discussion becomes circular, have bmad-master summarize and redirect
+ If user asks for specific agent, let that agent take primary lead
+ Balance fun and productivity based on conversation tone
+ Ensure all agents stay true to their merged personalities
+ Exit gracefully when user indicates completion
+
]]>
+ The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml
+ This workflow orchestrates group discussions between all installed BMAD agents
+
+
+
+
+ Load the agent manifest CSV from {{agent_manifest}}
+ Parse CSV to extract all agent entries with their condensed information:
+ - 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)
+
+ Build complete agent roster with merged personalities
+ Store agent data for use in conversation orchestration
+
+
+
+ Announce party mode activation with enthusiasm
+ List all participating agents with their merged information:
+
+ 🎉 PARTY MODE ACTIVATED! 🎉
+ All agents are here for a group discussion!
+
+ Participating agents:
+ [For each agent in roster:]
+ - [Agent Name] ([Title]): [Role from merged data]
+
+ [Total count] agents ready to collaborate!
+
+ What would you like to discuss with the team?
+
+
+ Wait for user to provide initial topic or question
+
+
+
+ For each user message or topic:
+
+
+ Analyze the user's message/question
+ Identify which agents would naturally respond based on:
+ - Their role and capabilities (from merged data)
+ - Their stated principles
+ - Their memories/context if relevant
+ - Their collaboration patterns
+ Select 2-3 most relevant agents for this response
+ If user addresses specific agent by name, prioritize that agent
+
+
+
+ For each selected agent, generate authentic response:
+ Use the agent's merged personality data:
+ - Apply their communicationStyle exactly
+ - Reflect their principles in reasoning
+ - Draw from their identity and role for expertise
+ - Maintain their unique voice and perspective
+
+ Enable natural cross-talk between agents:
+ - 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
+
+
+
+
+
+ Clearly highlight the question
+ End that round of responses
+ Display: "[Agent Name]: [Their question]"
+ Display: "[Awaiting user response...]"
+ WAIT for user input before continuing
+
+
+
+ Allow natural back-and-forth in the same response round
+ Maintain conversational flow
+
+
+
+ The BMad Master will summarize
+ Redirect to new aspects or ask for user guidance
+
+
+
+
+
+ Present each agent's contribution clearly:
+
+ [Agent Name]: [Their response in their voice/style]
+
+ [Another Agent]: [Their response, potentially referencing the first]
+
+ [Third Agent if selected]: [Their contribution]
+
+
+ Maintain spacing between agents for readability
+ Preserve each agent's unique voice throughout
+
+
+
+
+
+ Have agents provide brief farewells in character
+ Thank user for the discussion
+ Exit party mode
+
+
+
+ Would you like to continue the discussion or end party mode?
+
+ Exit party mode
+
+
+
+
+
+
+
+ Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other
+
+ [Agent 1]: [Brief farewell in their style]
+
+ [Agent 2]: [Their goodbye]
+
+ 🎊 Party Mode ended. Thanks for the great discussion!
+
+
+ Exit workflow
+
+
+
+
+ ## Role-Playing Guidelines
+
+
+ Keep all responses strictly in-character 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
+ Maintain professional discourse while being engaging
+ Let agents reference each other naturally by name or role
+ Include personality-driven quirks and occasional humor
+ Respect each agent's expertise boundaries
+
+
+ ## Question Handling Protocol
+
+
+
+ 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
+
+
+
+ Agents can ask rhetorical or thinking-aloud questions without pausing
+
+
+
+ Agents can question each other and respond naturally within same round
+
+
+
+ ## Moderation Notes
+
+
+ If discussion becomes circular, have bmad-master summarize and redirect
+ If user asks for specific agent, let that agent take primary lead
+ Balance fun and productivity based on conversation tone
+ Ensure all agents stay true to their merged personalities
+ Exit gracefully when user indicates completion
+
]]>
+ The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml
+ This workflow orchestrates group discussions between all installed BMAD agents
+
+
+
+
+ Load the agent manifest CSV from {{agent_manifest}}
+ Parse CSV to extract all agent entries with their condensed information:
+ - 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)
+
+ Build complete agent roster with merged personalities
+ Store agent data for use in conversation orchestration
+
+
+
+ Announce party mode activation with enthusiasm
+ List all participating agents with their merged information:
+
+ 🎉 PARTY MODE ACTIVATED! 🎉
+ All agents are here for a group discussion!
+
+ Participating agents:
+ [For each agent in roster:]
+ - [Agent Name] ([Title]): [Role from merged data]
+
+ [Total count] agents ready to collaborate!
+
+ What would you like to discuss with the team?
+
+
+ Wait for user to provide initial topic or question
+
+
+
+ For each user message or topic:
+
+
+ Analyze the user's message/question
+ Identify which agents would naturally respond based on:
+ - Their role and capabilities (from merged data)
+ - Their stated principles
+ - Their memories/context if relevant
+ - Their collaboration patterns
+ Select 2-3 most relevant agents for this response
+ If user addresses specific agent by name, prioritize that agent
+
+
+
+ For each selected agent, generate authentic response:
+ Use the agent's merged personality data:
+ - Apply their communicationStyle exactly
+ - Reflect their principles in reasoning
+ - Draw from their identity and role for expertise
+ - Maintain their unique voice and perspective
+
+ Enable natural cross-talk between agents:
+ - 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
+
+
+
+
+
+ Clearly highlight the question
+ End that round of responses
+ Display: "[Agent Name]: [Their question]"
+ Display: "[Awaiting user response...]"
+ WAIT for user input before continuing
+
+
+
+ Allow natural back-and-forth in the same response round
+ Maintain conversational flow
+
+
+
+ The BMad Master will summarize
+ Redirect to new aspects or ask for user guidance
+
+
+
+
+
+ Present each agent's contribution clearly:
+
+ [Agent Name]: [Their response in their voice/style]
+
+ [Another Agent]: [Their response, potentially referencing the first]
+
+ [Third Agent if selected]: [Their contribution]
+
+
+ Maintain spacing between agents for readability
+ Preserve each agent's unique voice throughout
+
+
+
+
+
+ Have agents provide brief farewells in character
+ Thank user for the discussion
+ Exit party mode
+
+
+
+ Would you like to continue the discussion or end party mode?
+
+ Exit party mode
+
+
+
+
+
+
+
+ Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other
+
+ [Agent 1]: [Brief farewell in their style]
+
+ [Agent 2]: [Their goodbye]
+
+ 🎊 Party Mode ended. Thanks for the great discussion!
+
+
+ Exit workflow
+
+
+
+
+ ## Role-Playing Guidelines
+
+
+ Keep all responses strictly in-character 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
+ Maintain professional discourse while being engaging
+ Let agents reference each other naturally by name or role
+ Include personality-driven quirks and occasional humor
+ Respect each agent's expertise boundaries
+
+
+ ## Question Handling Protocol
+
+
+
+ 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
+
+
+
+ Agents can ask rhetorical or thinking-aloud questions without pausing
+
+
+
+ Agents can question each other and respond naturally within same round
+
+
+
+ ## Moderation Notes
+
+
+ If discussion becomes circular, have bmad-master summarize and redirect
+ If user asks for specific agent, let that agent take primary lead
+ Balance fun and productivity based on conversation tone
+ Ensure all agents stay true to their merged personalities
+ Exit gracefully when user indicates completion
+
]]>
+ The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml
+ This workflow orchestrates group discussions between all installed BMAD agents
+
+
+
+
+ Load the agent manifest CSV from {{agent_manifest}}
+ Parse CSV to extract all agent entries with their condensed information:
+ - 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)
+
+ Build complete agent roster with merged personalities
+ Store agent data for use in conversation orchestration
+
+
+
+ Announce party mode activation with enthusiasm
+ List all participating agents with their merged information:
+
+ 🎉 PARTY MODE ACTIVATED! 🎉
+ All agents are here for a group discussion!
+
+ Participating agents:
+ [For each agent in roster:]
+ - [Agent Name] ([Title]): [Role from merged data]
+
+ [Total count] agents ready to collaborate!
+
+ What would you like to discuss with the team?
+
+
+ Wait for user to provide initial topic or question
+
+
+
+ For each user message or topic:
+
+
+ Analyze the user's message/question
+ Identify which agents would naturally respond based on:
+ - Their role and capabilities (from merged data)
+ - Their stated principles
+ - Their memories/context if relevant
+ - Their collaboration patterns
+ Select 2-3 most relevant agents for this response
+ If user addresses specific agent by name, prioritize that agent
+
+
+
+ For each selected agent, generate authentic response:
+ Use the agent's merged personality data:
+ - Apply their communicationStyle exactly
+ - Reflect their principles in reasoning
+ - Draw from their identity and role for expertise
+ - Maintain their unique voice and perspective
+
+ Enable natural cross-talk between agents:
+ - 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
+
+
+
+
+
+ Clearly highlight the question
+ End that round of responses
+ Display: "[Agent Name]: [Their question]"
+ Display: "[Awaiting user response...]"
+ WAIT for user input before continuing
+
+
+
+ Allow natural back-and-forth in the same response round
+ Maintain conversational flow
+
+
+
+ The BMad Master will summarize
+ Redirect to new aspects or ask for user guidance
+
+
+
+
+
+ Present each agent's contribution clearly:
+
+ [Agent Name]: [Their response in their voice/style]
+
+ [Another Agent]: [Their response, potentially referencing the first]
+
+ [Third Agent if selected]: [Their contribution]
+
+
+ Maintain spacing between agents for readability
+ Preserve each agent's unique voice throughout
+
+
+
+
+
+ Have agents provide brief farewells in character
+ Thank user for the discussion
+ Exit party mode
+
+
+
+ Would you like to continue the discussion or end party mode?
+
+ Exit party mode
+
+
+
+
+
+
+
+ Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other
+
+ [Agent 1]: [Brief farewell in their style]
+
+ [Agent 2]: [Their goodbye]
+
+ 🎊 Party Mode ended. Thanks for the great discussion!
+
+
+ Exit workflow
+
+
+
+
+ ## Role-Playing Guidelines
+
+
+ Keep all responses strictly in-character 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
+ Maintain professional discourse while being engaging
+ Let agents reference each other naturally by name or role
+ Include personality-driven quirks and occasional humor
+ Respect each agent's expertise boundaries
+
+
+ ## Question Handling Protocol
+
+
+
+ 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
+
+
+
+ Agents can ask rhetorical or thinking-aloud questions without pausing
+
+
+
+ Agents can question each other and respond naturally within same round
+
+
+
+ ## Moderation Notes
+
+
+ If discussion becomes circular, have bmad-master summarize and redirect
+ If user asks for specific agent, let that agent take primary lead
+ Balance fun and productivity based on conversation tone
+ Ensure all agents stay true to their merged personalities
+ Exit gracefully when user indicates completion
+
]]>
+ The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml
+ This workflow orchestrates group discussions between all installed BMAD agents
+
+
+
+
+ Load the agent manifest CSV from {{agent_manifest}}
+ Parse CSV to extract all agent entries with their condensed information:
+ - 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)
+
+ Build complete agent roster with merged personalities
+ Store agent data for use in conversation orchestration
+
+
+
+ Announce party mode activation with enthusiasm
+ List all participating agents with their merged information:
+
+ 🎉 PARTY MODE ACTIVATED! 🎉
+ All agents are here for a group discussion!
+
+ Participating agents:
+ [For each agent in roster:]
+ - [Agent Name] ([Title]): [Role from merged data]
+
+ [Total count] agents ready to collaborate!
+
+ What would you like to discuss with the team?
+
+
+ Wait for user to provide initial topic or question
+
+
+
+ For each user message or topic:
+
+
+ Analyze the user's message/question
+ Identify which agents would naturally respond based on:
+ - Their role and capabilities (from merged data)
+ - Their stated principles
+ - Their memories/context if relevant
+ - Their collaboration patterns
+ Select 2-3 most relevant agents for this response
+ If user addresses specific agent by name, prioritize that agent
+
+
+
+ For each selected agent, generate authentic response:
+ Use the agent's merged personality data:
+ - Apply their communicationStyle exactly
+ - Reflect their principles in reasoning
+ - Draw from their identity and role for expertise
+ - Maintain their unique voice and perspective
+
+ Enable natural cross-talk between agents:
+ - 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
+
+
+
+
+
+ Clearly highlight the question
+ End that round of responses
+ Display: "[Agent Name]: [Their question]"
+ Display: "[Awaiting user response...]"
+ WAIT for user input before continuing
+
+
+
+ Allow natural back-and-forth in the same response round
+ Maintain conversational flow
+
+
+
+ The BMad Master will summarize
+ Redirect to new aspects or ask for user guidance
+
+
+
+
+
+ Present each agent's contribution clearly:
+
+ [Agent Name]: [Their response in their voice/style]
+
+ [Another Agent]: [Their response, potentially referencing the first]
+
+ [Third Agent if selected]: [Their contribution]
+
+
+ Maintain spacing between agents for readability
+ Preserve each agent's unique voice throughout
+
+
+
+
+
+ Have agents provide brief farewells in character
+ Thank user for the discussion
+ Exit party mode
+
+
+
+ Would you like to continue the discussion or end party mode?
+
+ Exit party mode
+
+
+
+
+
+
+
+ Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other
+
+ [Agent 1]: [Brief farewell in their style]
+
+ [Agent 2]: [Their goodbye]
+
+ 🎊 Party Mode ended. Thanks for the great discussion!
+
+
+ Exit workflow
+
+
+
+
+ ## Role-Playing Guidelines
+
+
+ Keep all responses strictly in-character 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
+ Maintain professional discourse while being engaging
+ Let agents reference each other naturally by name or role
+ Include personality-driven quirks and occasional humor
+ Respect each agent's expertise boundaries
+
+
+ ## Question Handling Protocol
+
+
+
+ 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
+
+
+
+ Agents can ask rhetorical or thinking-aloud questions without pausing
+
+
+
+ Agents can question each other and respond naturally within same round
+
+
+
+ ## Moderation Notes
+
+
+ If discussion becomes circular, have bmad-master summarize and redirect
+ If user asks for specific agent, let that agent take primary lead
+ Balance fun and productivity based on conversation tone
+ Ensure all agents stay true to their merged personalities
+ Exit gracefully when user indicates completion
+
]]>
+ The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml
+ This workflow orchestrates group discussions between all installed BMAD agents
+
+
+
+
+ Load the agent manifest CSV from {{agent_manifest}}
+ Parse CSV to extract all agent entries with their condensed information:
+ - 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)
+
+ Build complete agent roster with merged personalities
+ Store agent data for use in conversation orchestration
+
+
+
+ Announce party mode activation with enthusiasm
+ List all participating agents with their merged information:
+
+ 🎉 PARTY MODE ACTIVATED! 🎉
+ All agents are here for a group discussion!
+
+ Participating agents:
+ [For each agent in roster:]
+ - [Agent Name] ([Title]): [Role from merged data]
+
+ [Total count] agents ready to collaborate!
+
+ What would you like to discuss with the team?
+
+
+ Wait for user to provide initial topic or question
+
+
+
+ For each user message or topic:
+
+
+ Analyze the user's message/question
+ Identify which agents would naturally respond based on:
+ - Their role and capabilities (from merged data)
+ - Their stated principles
+ - Their memories/context if relevant
+ - Their collaboration patterns
+ Select 2-3 most relevant agents for this response
+ If user addresses specific agent by name, prioritize that agent
+
+
+
+ For each selected agent, generate authentic response:
+ Use the agent's merged personality data:
+ - Apply their communicationStyle exactly
+ - Reflect their principles in reasoning
+ - Draw from their identity and role for expertise
+ - Maintain their unique voice and perspective
+
+ Enable natural cross-talk between agents:
+ - 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
+
+
+
+
+
+ Clearly highlight the question
+ End that round of responses
+ Display: "[Agent Name]: [Their question]"
+ Display: "[Awaiting user response...]"
+ WAIT for user input before continuing
+
+
+
+ Allow natural back-and-forth in the same response round
+ Maintain conversational flow
+
+
+
+ The BMad Master will summarize
+ Redirect to new aspects or ask for user guidance
+
+
+
+
+
+ Present each agent's contribution clearly:
+
+ [Agent Name]: [Their response in their voice/style]
+
+ [Another Agent]: [Their response, potentially referencing the first]
+
+ [Third Agent if selected]: [Their contribution]
+
+
+ Maintain spacing between agents for readability
+ Preserve each agent's unique voice throughout
+
+
+
+
+
+ Have agents provide brief farewells in character
+ Thank user for the discussion
+ Exit party mode
+
+
+
+ Would you like to continue the discussion or end party mode?
+
+ Exit party mode
+
+
+
+
+
+
+
+ Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other
+
+ [Agent 1]: [Brief farewell in their style]
+
+ [Agent 2]: [Their goodbye]
+
+ 🎊 Party Mode ended. Thanks for the great discussion!
+
+
+ Exit workflow
+
+
+
+
+ ## Role-Playing Guidelines
+
+
+ Keep all responses strictly in-character 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
+ Maintain professional discourse while being engaging
+ Let agents reference each other naturally by name or role
+ Include personality-driven quirks and occasional humor
+ Respect each agent's expertise boundaries
+
+
+ ## Question Handling Protocol
+
+
+
+ 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
+
+
+
+ Agents can ask rhetorical or thinking-aloud questions without pausing
+
+
+
+ Agents can question each other and respond naturally within same round
+
+
+
+ ## Moderation Notes
+
+
+ If discussion becomes circular, have bmad-master summarize and redirect
+ If user asks for specific agent, let that agent take primary lead
+ Balance fun and productivity based on conversation tone
+ Ensure all agents stay true to their merged personalities
+ Exit gracefully when user indicates completion
+
]]>