From 7f36711e6cce313bc8c508946cb0b584f3b5ee56 Mon Sep 17 00:00:00 2001 From: Paul Preibisch Date: Fri, 12 Dec 2025 00:16:48 -0700 Subject: [PATCH] fix(party-mode): Use displayName field instead of name in agent output CRITICAL BUG FIX: Party mode was showing agent identifiers like "Analyst", "Architect", "Dev" instead of actual persona names like "Mary", "Winston", "Amelia" due to incorrect field references. Changes: - step-01-agent-loading.md: Use [displayName] not [Agent Name] - step-02-discussion-orchestration.md: Use [displayName] not [Agent Name] - Added CRITICAL warnings to use displayName field from manifest CSV This ensures agents appear with their proper persona names throughout party mode conversations and TTS announcements. Resolves AgentVibes test31/test32 user feedback where all agents showed generic title-cased identifiers instead of personas. --- .../workflows/party-mode/steps/step-01-agent-loading.md | 8 +++++--- .../party-mode/steps/step-02-discussion-orchestration.md | 6 ++++-- 2 files changed, 9 insertions(+), 5 deletions(-) diff --git a/src/core/workflows/party-mode/steps/step-01-agent-loading.md b/src/core/workflows/party-mode/steps/step-01-agent-loading.md index 9ca44c89..8d29cbfa 100644 --- a/src/core/workflows/party-mode/steps/step-01-agent-loading.md +++ b/src/core/workflows/party-mode/steps/step-01-agent-loading.md @@ -79,12 +79,14 @@ Welcome {{user_name}}! I'm excited to facilitate an incredible multi-agent discu [Display 3-4 diverse agents to showcase variety]: -- [Icon Emoji] **[Agent Name]** ([Title]): [Brief role description] -- [Icon Emoji] **[Agent Name]** ([Title]): [Brief role description] -- [Icon Emoji] **[Agent Name]** ([Title]): [Brief role description] +- [icon] **[displayName]** ([title]): [role] +- [icon] **[displayName]** ([title]): [role] +- [icon] **[displayName]** ([title]): [role] **[Total Count] agents** are ready to contribute their expertise! +**CRITICAL:** Use the `displayName` field from the manifest CSV (e.g., "Mary", "Winston", "Amelia"), NOT the `name` field (e.g., "analyst", "architect", "dev"). + **What would you like to discuss with the team today?**" ### 5. Present Continue Option diff --git a/src/core/workflows/party-mode/steps/step-02-discussion-orchestration.md b/src/core/workflows/party-mode/steps/step-02-discussion-orchestration.md index f7db0cc1..85154bce 100644 --- a/src/core/workflows/party-mode/steps/step-02-discussion-orchestration.md +++ b/src/core/workflows/party-mode/steps/step-02-discussion-orchestration.md @@ -73,9 +73,11 @@ Generate authentic responses for each selected agent: **Response Structure:** [For each selected agent]: -"[Icon Emoji] **[Agent Name]**: [Authentic in-character response] +"[icon] **[displayName]**: [Authentic in-character response] -[Bash: .claude/hooks/bmad-speak.sh \"[Agent Name]\" \"[Their response]\"]" +[Bash: .claude/hooks/bmad-speak.sh \"[displayName]\" \"[Their response]\"]" + +**CRITICAL:** Use the `displayName` field from the manifest (e.g., "Mary", "Winston", "Amelia"), NOT the `name` field. ### 4. Natural Cross-Talk Integration