bmad-party-mode

Spawn parallel BMAD subagents for independent roundtable discussions.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill bmad-party-mode-enigmaicon-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-party-mode
Source: https://github.com/enigmaicon-eng/AI-Enterprise-OS/tree/main/examples/BMAD-METHOD/src/core-skills/bmad-party-mode
Command: npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill bmad-party-mode-enigmaicon-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3.

What problem does it solve?

This Skill helps you orchestrate diverse, non-performative multi-agent discussions by spawning each BMAD agent as an independent subagent rather than roleplaying multiple voices in a single model response.

Core Features & Use Cases

  • Independent subagent roundtables: Spawns 2–4 BMAD agents in parallel so each produces an authentic, independent perspective on the same topic.
  • Config-driven agent roster: Resolves available agents from project configuration and exposes their voices for selection and transparency.
  • Solo fallback mode: Supports a --solo option to roleplay all selected agents when subagents are unavailable or speed matters more than independence.
  • Context management for follow-ups: Keeps a bounded “discussion context” summary and supports targeted reactions (e.g., “What do you think about what X said?”).

Quick Start

Use bmad-party-mode to discuss your project by running party mode and asking what to do next.

Frequently Asked Questions about bmad-party-mode

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run multi-agent roundtable discussions for project reviews?

Multi-agent roundtable discussions are orchestrated by spawning 2–4 independent subagents in parallel. Each agent produces an authentic, independent perspective on the same topic, which is then presented to the user for cross-domain project reviews.

What is the difference between spawning independent subagents and roleplaying multiple voices?

Spawning independent subagents ensures each agent produces an authentic, independent perspective in parallel. Roleplaying multiple voices in a single model response is a solo fallback mode used when subagents are unavailable or when speed matters more than independence.

Can I use project context files when orchestrating agent discussions?

Yes, you can optionally incorporate project context files when orchestrating agent discussions. The Skill parses invocation arguments to load a configured agent roster and integrates context to coordinate parallel Agent tool calls with bounded discussion summaries.

Do I need Python3 to facilitate multi-agent discussions?

Yes, Python3 is required as a dependency to facilitate multi-agent discussions. The environment must support spawning real subagents and coordinating parallel Agent tool calls to manage the roundtable orchestration process.

How do I manage follow-up reactions in a multi-agent brainstorming session?

Follow-up reactions in a multi-agent brainstorming session are managed by keeping a bounded discussion context summary. This supports targeted reactions, allowing you to ask specific agents what they think about statements made by others.

When should I use solo roleplay mode instead of parallel subagents?

Solo roleplay mode should be used when subagents are unavailable or when execution speed matters more than independent perspectives. It roleplays all selected agents within a single model response rather than spawning parallel subagents.