bmad-party-mode

Multi-agent conversation orchestration coordinates discussions across diverse BMAD agents to harness their collective expertise. It uses manifest-driven agent roster loading and frontmatter state management to maintain coherent cross-talk and converge on recommendations.

To coordinate a BMAD brainstorming session, initiate party mode to load the complete agent roster from the manifest. The workflow applies deterministic agent selection and managed cross-talk to guide the multi-agent conversation toward strategic recommendations.

Yes, multi-agent orchestration supports cross-domain problem solving by merging diverse agent personalities from the manifest. This builds a roster capable of addressing a wide range of topics and strategic decision making.

The best way to manage conversation state in a multi-agent workflow is using frontmatter state management. This tracks the ongoing discussion, supports graceful exits, and provides session-level takeaways for future iteration.

Yes, a manifest is required to run a multi-agent BMAD conversation. Manifest-driven agent roster loading is essential for merging agent personalities and building the diverse roster needed for coordinated discussions.

To exit party mode, follow the guided activation-exit workflow which supports graceful exits. This process tracks the conversation state and provides session-level takeaways for future iteration and analysis.