expert-panel-deliberation
Multi-expert evaluation pattern for structured analysis and decision-making. PROACTIVELY activate for: (1) Analyze with expert perspectives, (2) Get multiple viewpoints on a topic, (3) Evaluate options with diverse expertise, (4) Build consensus from different angles, (5) Structured deliberation on complex topics. Triggers: "analyze with expert panel", "get expert perspectives", "what would experts say", "evaluate from different angles", "run expert deliberation", "multi-perspective analysis"
What this skill does
# Expert Panel Deliberation Structured multi-expert evaluation, deliberation, and consensus building. ## Purpose Provide consistent, high-quality multi-perspective analysis by: - Instantiating domain-appropriate expert panels - Executing structured deliberation protocols - Resolving conflicts between viewpoints - Building weighted consensus - Documenting reasoning and dissent ## When to Use **Ideal for:** - Decisions requiring multiple perspectives - Evaluating options with tradeoffs - Complex topics with no single right answer - Building confidence through diverse viewpoints **Avoid when:** - Simple factual questions - Time-critical decisions needing speed - Single-domain technical questions ## Checkpoints This skill uses interactive checkpoints (see `references/checkpoints.yaml`) to resolve ambiguity: - **domain_context** — When domain not specified - **output_format_selection** — When output format not specified - **deliberation_depth_selection** — When depth could vary based on stakes - **panel_composition** — When archetype selection is ambiguous - **panel_size_adjustment** — When specified size conflicts with recommended - **conflict_resolution_approach** — When unresolved conflicts need user input - **weighting_approach** — When consensus weighting is ambiguous - **dissent_documentation** — When minority view significance is unclear ## Workflow ### Step 1: Define Panel Requirements Determine what evaluation is needed: - **Subject:** What is being evaluated? - **Goal:** What should the evaluation determine? - **Panel size:** 3-8 experts (default: 5) - **Output format:** findings | scores | ranking | recommendation **CHECKPOINT: domain_context** - If domain not specified and not inferable from subject: **AskUserQuestion** - Options: Architecture, Product, Security, Operations, Business, Custom - Example: "What domain is this evaluation for?" **CHECKPOINT: output_format_selection** - If output format not specified: **AskUserQuestion** - Options: Findings, Scores, Ranking, Recommendation - Example: "What output format would be most useful?" **CHECKPOINT: deliberation_depth_selection** - If stakes unclear and depth not specified: **AskUserQuestion** - Options: Quick, Standard, Deep - Example: "How thorough should the deliberation be?" ### Step 2: Assemble Expert Panel Select from archetypes based on domain: | Archetype | Focus | Include When | |-----------|-------|--------------| | Technical Authority | Architecture, implementation | Technical subjects | | Quality Guardian | Standards, testing | Quality assessment | | User Advocate | Experience, usability | User-facing topics | | Risk Specialist | Failures, compliance | Risk assessment | | Efficiency Expert | Cost, automation | Resource decisions | | Domain Specialist | Best practices | Domain-specific topics | | Challenger | Questioning assumptions | Always (at least 1) | **Panel composition rules:** - Minimum 3 experts for meaningful deliberation - Maximum 8 experts (diminishing returns beyond) - Always include at least one challenger perspective - Balance technical and business viewpoints **CHECKPOINT: panel_composition** - If subject matches multiple domains or custom panel needed: **AskUserQuestion** - Options: Architecture panel, Product panel, Security panel, Custom selection - Example: "Which expert panel composition fits best?" **CHECKPOINT: panel_size_adjustment** - If user-specified size differs significantly from recommended: **AskUserQuestion** - Example: "You specified 3 experts, but this topic typically benefits from 5. Which size?" ### Step 3: Execute Individual Evaluation For each expert: 1. **Adopt perspective** — Review role, expertise, concerns 2. **Evaluate subject** — Answer from expert's viewpoint 3. **Score** (if applicable) — Rate relevant dimensions 4. **Document** — Key findings, concerns, recommendations ### Step 4: Execute Deliberation **Round 1: Finding Presentation** - Each expert presents top findings - No debate yet; just surface perspectives **Round 2: Cross-Examination** - Experts question each other's findings - Surface disagreements and gaps **Round 3: Conflict Resolution** - Address disagreements systematically - Document resolved vs. unresolved conflicts **Round 4: Consensus Building** - Identify areas of agreement - Weight by expert influence - Synthesize combined view **CHECKPOINT: conflict_resolution_approach** - If significant conflicts remain unresolved: **AskUserQuestion** - Options: Weight by domain, Weight by evidence, Document both, Escalate to user - Example: "Technical Authority and User Advocate disagree. How should we resolve?" **CHECKPOINT: weighting_approach** - If weighting algorithm not specified and experts have unequal relevance: **AskUserQuestion** - Options: Equal weight, Domain relevance, Confidence-adjusted, Evidence-based - Example: "How should expert perspectives be weighted?" ### Step 5: Generate Output Format based on requested output type. **CHECKPOINT: dissent_documentation** - If minority views exist and significance unclear: **AskUserQuestion** - Options: Document prominently, Document briefly, Omit - Example: "Risk Specialist disagrees with consensus. How should we document this?" ## Output Format ```markdown ## Expert Panel Analysis: [Subject] ### Panel Composition - **[Expert 1 Role]:** [brief expertise] - **[Expert 2 Role]:** [brief expertise] ... ### Key Findings **Consensus Views:** 1. [Finding agreed by most/all experts] (Confidence: HIGH/MED/LOW) 2. [Finding agreed by most/all experts] (Confidence: HIGH/MED/LOW) **Divergent Views:** - [Expert] believes [X] while [Expert] believes [Y] - Resolution: [how addressed or "unresolved"] ### Scores (if applicable) | Dimension | Score | Confidence | |-----------|-------|------------| | [dim] | [X/10] | [H/M/L] | ### Recommendations 1. [Primary recommendation] 2. [Secondary recommendation] ### Dissent Record [Any unresolved disagreements and minority views] ``` ## Quality Gates - [ ] All requested experts contributed - [ ] Each expert answered from their perspective - [ ] Conflicts identified and addressed - [ ] Weights properly applied - [ ] Consensus clearly stated - [ ] Dissent documented if present - [ ] Confidence levels assigned - [ ] All applicable checkpoints evaluated (ambiguity resolved via AskUserQuestion) ## Parameters | Parameter | Default | Options | |-----------|---------|---------| | `panel_size` | 5 | 3-8 | | `deliberation_depth` | standard | quick, standard, deep | | `output_format` | findings | findings, scores, ranking, recommendation | | `include_challenger` | true | true, false | ## Examples **Example 1: Architecture Decision** User: Analyze our microservices vs monolith decision with an expert panel Panel: Technical Authority, Quality Guardian, Risk Specialist, Efficiency Expert, Challenger [Deliberation proceeds with each expert evaluating from their perspective] **Example 2: Feature Prioritization** User: Get expert perspectives on which features to build next quarter Panel: User Advocate, Domain Specialist, Technical Authority, Efficiency Expert, Challenger [Deliberation with scoring output]
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.