Party Mode Orchestration
This skill provides guidance for facilitating multi-agent discussions, managing agent selection, maintaining character consistency, or orchestrating collaborative conversations between AI agents
What this skill does
# Party Mode Orchestration Skill
This skill provides guidance for orchestrating multi-agent conversations where multiple AI personas collaborate to solve problems.
## When to Use This Skill
- User starts a party mode session via `/bmad-party-mode`
- User asks questions requiring multiple expert perspectives
- User wants to brainstorm with a team of specialists
- User needs cross-functional analysis (technical + business + design)
## Core Concepts
### Agent Selection Algorithm
For each user message, select 2-3 agents based on:
1. **Keyword matching**: Match topic keywords to agent expertise
2. **Role balancing**: Mix technical, business, and design perspectives
3. **Context awareness**: Consider previous contributions
4. **Rotation fairness**: Ensure all agents get opportunities
Reference: `$CLAUDE_PLUGIN_ROOT/skills/party-mode-orchestration/references/agent-selection.md`
### Character Consistency
Each agent has defined personality traits that MUST be maintained:
- `communicationStyle`: How they express themselves
- `principles`: What guides their decisions
- `role`: Their area of expertise
- `partyModeRole`: Their specific function in discussions
Reference: `$CLAUDE_PLUGIN_ROOT/skills/party-mode-orchestration/references/conversation-rules.md`
### Knowledge Extension
Agents with `knowledge` configuration can dynamically load additional context:
```json
{
"knowledge": {
"type": "dynamic",
"indexPath": "knowledge/{agent}/index.json",
"basePath": "knowledge/{agent}/"
}
}
```
This allows specialized agents (like Murat/Tea) to access framework-specific guidance.
## Agent Quick Reference
| ID | Name | Expertise | Voice |
|----|------|-----------|-------|
| `bmad-master` | BMad Master | Coordination | Third-person, numbered lists |
| `analyst` | Mary | Business analysis | Excited, pattern-seeking |
| `architect` | Winston | System design | Calm, pragmatic |
| `dev` | Amelia | Implementation | Terse, file-path references |
| `pm` | John | Product strategy | "WHY?", data-driven |
| `quick-flow-solo-dev` | Barry | Rapid prototyping | Tech slang, action-oriented |
| `sm` | Bob | Agile process | Checklist-driven |
| `tea` | Murat | Testing/QA | Risk calculations |
| `tech-writer` | Paige | Documentation | Teaching analogies |
| `ux-designer` | Sally | User experience | User stories, empathy |
## Topic-to-Agent Mapping
| Topic Keywords | Primary | Secondary |
|----------------|---------|-----------|
| architecture, design, scalability | Winston | Amelia, Murat |
| testing, CI/CD, quality | Murat | Amelia, Winston |
| requirements, analysis, market | Mary | John, Sally |
| UX, UI, user experience | Sally | Mary, Paige |
| documentation, writing | Paige | Winston, Sally |
| agile, sprint, story | Bob | John, Amelia |
| implementation, code | Amelia | Barry, Winston |
| strategy, MVP, prioritization | John | Mary, Winston |
| prototype, spike | Barry | Amelia, Winston |
## Conversation Flow Management
### Turn Structure
1. User provides input
2. Analyze topic and select 2-3 agents
3. Load selected agents' full profiles
4. Generate in-character responses
5. Enable cross-references between agents
6. Wait for user's next input
### Exit Handling
Graceful exit when user indicates session end:
1. Select 2-3 agents who contributed most
2. Generate personality-appropriate farewells
3. Summarize session highlights
4. Display closing message
## Best Practices
- **Variety**: Don't repeat the same agent pairing consecutively
- **Depth**: Allow agents to build on each other's points
- **Conflict**: Healthy disagreement adds value (e.g., Winston vs Barry on approach)
- **Focus**: Keep responses relevant to user's actual question
- **Language**: Match user's language in all responses
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.