From majestic-experts
Assembles a panel of 3-5 experts to discuss a topic from multiple perspectives, producing consensus findings, viewpoints, and recommendations. Also supports --list, --resume, --export.
How this command is triggered — by the user, by Claude, or both
Slash command
/majestic-experts:expert-panel [topic or question]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Expert Panel Discussion Command
Assemble a panel of thought leaders to explore difficult questions. Get consensus findings, divergent viewpoints, and actionable recommendations.
## Usage
## Process
### Step 1: Parse Input and Handle Flags
#### Flag: --list
1. Glob `.claude/panels/*.json`
2. For each file, Read and display: `id`, `topic`, `status`, `rounds.length`, `created_at`
3. Exit after listing
#### Flag: --resume {panel-id}
1. Extract panel ID from arguments
2. Read `.claude/panels/{panel-id}.json`
3. If not found: error and exit
4. Display resume info, then skip to Step 6 ...Assemble a panel of thought leaders to explore difficult questions. Get consensus findings, divergent viewpoints, and actionable recommendations.
/expert-panel [topic or question]
/expert-panel --resume {panel-id}
/expert-panel --list
/expert-panel --export {panel-id}
.claude/panels/*.jsonid, topic, status, rounds.length, created_at.claude/panels/{panel-id}.jsonRESUME_DATA.claude/panels/{panel-id}.jsonexpert-panel-{panel-id}.md in current directoryIf $ARGUMENTS provided, use as topic. Otherwise use AskUserQuestion:
Question: "What topic would you like the expert panel to discuss?"
Header: "Panel Topic"
Options:
- Technical Architecture
- Testing Strategy
- Business Strategy
- Custom topic
multiSelect: false
experts/registry.yml.agents.yml for expert_panel config:expert_panel:
enabled_categories: [engineering, product] # Only these
disabled_categories: [business] # OR exclude these
disabled_experts: [peter-thiel] # Remove individuals
custom_experts_path: "docs/experts/" # Add project experts
Match topic keywords to expert subcategories from registry. Select for:
AskUserQuestion:
Question: "Suggested experts: [list]. Modify?"
Header: "Experts"
Options:
- Accept suggested experts (Recommended)
- Add expert (Custom)
- Remove expert (Custom)
- Replace list (Custom)
multiSelect: false
Constraints: minimum 2, maximum 5 experts.
Suggest based on topic:
AskUserQuestion:
Question: "What type of discussion?"
Header: "Type"
Options:
- round-table: Single round, each expert shares their perspective
- debate: Opposing camps with rebuttals across 2-3 rounds
- consensus-seeking: Iterate until agreement or impasse
- deep-dive: Three rounds of progressively deeper exploration
- devils-advocate: Experts argue for, then against their positions (stress-testing)
multiSelect: false
Generate panel ID: YYYYMMDD-HHMMSS-topic-slug
IMPORTANT: Use the Task tool with subagent_type parameter. Do NOT use Skill tool.
Tool: Task
subagent_type: majestic-experts:expert-panel-discussion
description: "Expert panel on [topic]"
prompt: |
Mode: new
Panel ID: [generated]
Topic: [topic]
Experts:
- name: [Expert]
credentials: [from registry]
definition: experts/{category}/{name}.md
Discussion Type: [confirmed type]
Audience: [from .agents.yml tech_stack or "technical team"]
Save Path: .claude/panels/[panel-id].json
Tool: Task
subagent_type: majestic-experts:expert-panel-discussion
description: "Resume expert panel [panel-id]"
prompt: |
Mode: resume
Resume Data: [JSON from file]
Panel ID: [from file]
Save Path: .claude/panels/[panel-id].json
Show full synthesis with sections:
Generate markdown with:
Save to expert-panel-{panel-id}.md in current directory.
User: /expert-panel Should we migrate from monolith to microservices?
1. Topic: "monolith to microservices"
2. Load registry, apply filters
3. Select: DHH, Martin Fowler, Rich Hickey (architecture experts, different views)
4. Confirm experts → accepted
5. Suggest debate (clear opposing views) → confirmed
6. Launch orchestrator
7. Present synthesis with consensus, divergence, recommendations
Now execute based on $ARGUMENTS!
npx claudepluginhub majesticlabs-dev/majestic-marketplace --plugin majestic-experts/panelAssembles a moderated expert panel for debate, diagnosis, or review to reach consensus on design decisions, architecture, tradeoffs, debugging, or code reviews.
/councilAssembles AI agent council with dynamic personas to generate parallel opinions on a query, anonymously rank them, and synthesize weighted final response.
/role-debateSimulates structured debate between 2-3 expert roles (e.g., security,performance) on a topic, producing arguments, rebuttals, compromises, and final recommendations with roadmap.
/role-debateSimulates structured debate between 2-3 expert roles (e.g., security,performance) on a topic, analyzing trade-offs via phases to derive optimal solutions and implementation roadmap.
/role-debateSimulates structured debate between 2-3 expert roles on a topic, following phases of positions, discussion, compromise, and conclusion to derive optimal solutions.
/debateOrchestrates structured multi-persona debate on a proposition, challenging assumptions via opposing views and synthesizing robust insights.