e535f94325
Style Guide Additions: - Add Reference Structure section with 6 document types (Index, Catalog, Deep-Dive, Configuration, Glossary, Comprehensive) - Add Glossary Structure section with table-based format leveraging Starlight's right-nav for navigation - Include checklists for both new document types Reference Docs Updated: - agents/index.md: Catalog format, universal commands tip admonition - configuration/core-tasks.md: Configuration format with admonitions - configuration/global-config.md: Table-based config reference - workflows/index.md: Minimal index format - workflows/core-workflows.md: Catalog format - workflows/document-project.md: Deep-dive with Quick Facts admonition - workflows/bmgd-workflows.md: Comprehensive format, removed ~30 hr rules Glossary Rewritten: - Converted from 373 lines with ### headers to 123 lines with tables - Right nav now shows 9 categories instead of 50+ terms - Added italic context markers (*BMGD.*, *Brownfield.*, etc.) - Alphabetized terms within categories - Removed redundant inline TOC All Docs: - Remove horizontal rules (---) per style guide - Remove "Related" sections (sidebar handles navigation) - Standardize admonition usage - Archive deleted workflow customization docs Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
3.8 KiB
title
| title |
|---|
| Party Mode: Multi-Agent Collaboration |
Get all your AI agents in one conversation.
What is Party Mode?
Ever wanted to gather your entire AI team in one room and see what happens? That's party mode.
Type /bmad:core:workflows:party-mode (or *party-mode from any agent or at key workflow junctions when asked), and suddenly you've got all your AI agents in one conversation. PM, Architect, DEV, UX Designer and more that you can choose from.
Why it's useful:
- After complex workflows - Debrief with the whole team about what worked, what didn't
- Big decisions with tradeoffs - Get technical, creative, and strategic perspectives simultaneously
- Brainstorming sessions - Watch ideas evolve through cross-pollination
- When things go wrong - Call out failures, watch agents defend their decisions, let them debate whose fault it was (oddly therapeutic)
- Sprint retrospectives - Party mode powers the retrospective workflow
- Sprint planning - Multi-agent collaboration for planning sessions
How It Works
The basics:
- Party mode reads
_bmad/_config/agent-manifest.csv - Loads ALL installed agents (already includes your customizations from install)
- BMad Master orchestrates - picks 2-3 relevant agents per message based on topic
- Agents respond in character, can agree/disagree/build on each other's ideas
- Discussion continues until you type "exit" or reach natural conclusion
That's it. No complex merging, no runtime magic. Just agents talking.
Quick Start
/bmad:core:workflows:party-mode
*party-mode
/bmad:core:workflows:party-mode and include also in the party Santa Clause and Einstein
Ask questions, respond to agents, direct the conversation
Type: exit
Fun Examples
Example 1: Calling Out Bad Architecture
You: "Okay team, our last sprint was a disaster. The authentication service went down three times. Who screwed this up?"
Architect (Winston): "The design was sound - distributed authentication with proper fallbacks. If implementation deviated from the spec..."
DEV (Amelia): "I followed the architecture doc exactly. The spec didn't account for concurrent session invalidation race conditions."
PM (John): "Both of you missed the bigger issue - we didn't validate session management requirements in the PRD. This is on me for not catching it."
TEA (Murat): "And I should've caught this in integration tests. The test scenarios didn't cover concurrent invalidation."
(Watch them debate whose fault it really was - it's therapeutic)
Example 2: Creative Brainstorming
You: "How do we make onboarding feel magical instead of boring?"
UX Designer (Sally): "Start with progressive disclosure - reveal features as users need them, not all at once in a tutorial."
Storyteller (CIS): "What if onboarding was a story? Each step reveals a character's journey - the user IS the hero."
Innovation Strategist (CIS): "Take it further - gamify with unlockable achievements. But make them meaningful, not arbitrary badges."
Game Designer: "Building on that - what if the first 'quest' is actually solving a real user problem? They learn by doing something valuable."
(Ideas cross-pollinate and evolve)
Example 3: Technical Decision
You: "Monolith or microservices for MVP?"
Architect: "Start monolith. Microservices add complexity you don't need at 1000 users."
PM: "Agree. Time to market matters more than theoretical scalability."
DEV: "Monolith with clear module boundaries. We can extract services later if needed."
Innovation Strategist: "Contrarian take - if your differentiator IS scalability, build for it now. Otherwise Architect's right."
(Multiple perspectives reveal the right answer)
:::tip[Better Decisions] Better decisions through diverse perspectives. Welcome to party mode. :::