party-mode

Orchestrates multi-agent roundtable discussions by spawning BMAD agents as independent subagents.

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/chrissstellee/Movix --skill party-mode-chrissstellee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: party-mode
Source: https://github.com/chrissstellee/Movix/tree/main/.agents/skills/party-mode
Command: npx skills add https://github.com/chrissstellee/Movix --skill party-mode-chrissstellee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Getting genuinely diverse perspectives from multiple AI agents is hard when a single model roleplays every voice, since the opinions tend to converge and feel performative. This Skill solves that by spawning each BMAD agent as an independent subagent so every participant thinks for itself. ## Core Features & Use Cases - Independent Subagent Spawning: Each selected agent runs as its own subagent process via the Agent tool, producing authentic disagreement and domain-specific insight. - Dynamic Roster Resolution: Loads the available agent roster from layered TOML config files using a resolver script, so the discussion always reflects the agents actually installed. - Flexible Modes: Supports a --model flag to control subagent model choice and a --solo flag to roleplay all agents in a single response when subagents are unavailable. - Use Case: A product team debating a trade-off (e.g., escrow contract design vs. backend reconciliation) can ask for a roundtable and receive unfiltered takes from an architect, a PM, and a QA agent, then direct follow-up questions at specific agents. ## Quick Start Start party mode and have the installed agents discuss the trade-offs of our current escrow release flow.

Frequently Asked Questions about party-mode

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

FAQPage Schema
How do I run a multi-agent discussion with independent AI agents?▼

Invoke party mode and describe your topic. The orchestrator picks 2-4 relevant agents from the resolved roster and spawns each as an independent subagent via the Agent tool, so every response reflects genuinely separate reasoning rather than one model roleplaying all voices.

What is the difference between party mode subagent mode and solo mode?▼

Subagent mode spawns each agent as an independent process for authentic, divergent perspectives. Solo mode (--solo) skips spawning and has one model roleplay all agents in a single response, which is faster but produces less independent thinking.

Can I choose which model the discussion agents use?▼

Yes. Pass --model followed by a model name (for example --model haiku or --model opus) to force all subagents onto that model. Without the flag, the orchestrator matches model weight to the depth of each round.

How does party mode know which agents are available?▼

It runs a resolver script that merges four TOML config layers (team base, user base, team custom, personal custom) and reads the agents key. Each entry provides the agent's name, title, icon, description, module, and team used to build the roster.

What are the limitations of multi-agent roundtable discussions?▼

Long conversations require summarizing prior rounds to keep each subagent's context under roughly 400 words. Agents can also converge on similar opinions, in which case the orchestrator should bring in a contrarian voice or reframe the prompt.