bmad-party-mode

Orchestrate multi-agent roundtable discussions among installed BMAD agents.

1|Updated Dec 22, 2022
One-click install
npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-party-mode-rinzler78
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-party-mode
Source: https://github.com/Rinzler78/osmosis-launcher/tree/main/.agents/skills/bmad-party-mode
Command: npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-party-mode-rinzler78

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you coordinate a realistic group discussion across multiple BMAD agents so you can get diverse, independent perspectives instead of a single blended answer.

Core Features & Use Cases

  • Multi-agent orchestration: Spawns the right mix of agents for a topic and presents each voice separately.
  • Solo fallback: Can roleplay the selected agents in one response when subagents are unavailable or speed matters more than independence.
  • Discussion management: Handles follow-ups, cross-talk, contrarian viewpoints, and topic shifts while keeping context manageable.
  • Use Case: Ideal for product debates, design reviews, technical tradeoffs, or any situation where you want several expert viewpoints in one roundtable.

Quick Start

Ask the skill to start party mode on your topic and include whether you want solo mode or a specific model.

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 a multi-agent roundtable discussion for project debates?

Solo roleplay fallback allows the system to roleplay selected agents in a single response when subagents are unavailable. This ensures faster output while still simulating multiple expert viewpoints in one roundtable.

Can I manage follow-up questions and cross-talk during multi-agent discussions?

Multi-agent discussion management handles follow-ups, cross-talk, contrarian viewpoints, and topic shifts while keeping context manageable. This maintains coherent multi-expert exchanges throughout extended project debates.

What's the best way to get multiple expert perspectives for a technical tradeoff review?

Agent manifest loading, context summarization, roster selection, and controlled response formatting without tool use in agent replies are required. This ensures structured, independent expert viewpoints during cross-functional reviews.

Does multi-agent orchestration work without spawning separate subagents?

Solo fallback mode roleplays the selected agents in one response when subagents are unavailable or speed matters more than independence. This provides multiple viewpoints in a single output without separate agent spawning.