Skip to content

wyattowalsh/panel-debate-skill

panel-debate

Verified

Hosts interactive expert panel discussions on any topic. Dynamically generates diverse master-level expert personas, facilitates structured multi-round debate using Hegelian dialectic patterns, and synthesizes actionable consensus. Useful for exploring complex topics, making architectural decisions, evaluating trade-offs, or seeking diverse expert perspectives on strategic questions.

examples/business-strategy.md

View on GitHub
# Example: Business Strategy

**Topic**: "Should we build or buy our CRM system?"

**Complexity Score**: 13 (High)
- Stakeholders: 6+ (sales, IT, finance, customer success, engineering, executives)
- Trade-offs: 4+ (cost, customization, time, risk, vendor lock-in)
- Time horizon: Years
- Reversibility: Difficult (significant investment either way)
- Domain breadth: Cross-functional

**Panel Size**: 6 experts
**Rounds**: 3 (deep panel)

---

## Diversity Score: 82/100

| Category | Score | Details |
|----------|-------|---------|
| Archetype Diversity | 40/40 | 6 distinct archetypes, all required present |
| Domain Diversity | 27/30 | 5 domains (finance, sales, engineering, IT, org change) |
| Perspective Diversity | 15/30 | Skeptic + Pragmatist + Contrarian strong |

---

## Key Insight: Reframing

๐ŸŽค Jordan Park (Customer Success) [Contrarian]:
   "I want to challenge the framing. Do we even need a traditional CRM?
   Our customer relationships are built on product engagement, not sales
   tracking. Maybe we need a customer data platform that integrates with
   product analytics."

**This reframe changed the entire discussion trajectory.**

---

## Final Report Excerpt

### Consensus Level: CONTEXT-DEPENDENT

The panel reveals this isn't a simple build vs. buy decision. After
Jordan's reframing, consensus emerged on a hybrid approach:

โ•ญโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ
โ”‚                    CONSENSUS TOPOLOGY                      โ”‚
โ”œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ค
โ”‚                                                            โ”‚
โ”‚  โœ… STRONG CONSENSUS                                       โ”‚
โ”‚  โ”œโ”€โ”€ Buy standard CRM ยทยทยทยทยทยทยทยทยท [All except Jordan]       โ”‚
โ”‚  โ””โ”€โ”€ Build health platform ยทยทยทยท [All experts]             โ”‚
โ”‚                                                            โ”‚
โ”‚  โšก CONTESTED                                               โ”‚
โ”‚  โ””โ”€โ”€ CRM vendor choice                                     โ”‚
โ”‚      โ”œโ”€โ”€ Salesforce ยทยทยทยทยทยทยทยทยทยทยท [Robert, Aisha]           โ”‚
โ”‚      โ””โ”€โ”€ HubSpot ยทยทยทยทยทยทยทยทยทยทยทยทยทยท [Leila, Dmitri]           โ”‚
โ”‚                                                            โ”‚
โ”‚  ๐Ÿ“‹ CONTEXT-DEPENDENT                                      โ”‚
โ”‚  โ””โ”€โ”€ Build timeline                                        โ”‚
โ”‚      โ”œโ”€โ”€ IF resources available โ†’ Parallel build          โ”‚
โ”‚      โ””โ”€โ”€ IF constrained ยทยทยทยทยทยทยท โ†’ Sequential (CRM first)  โ”‚
โ”‚                                                            โ”‚
โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ

### Expert Position Matrix

โ•ญโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ
โ”‚ Topic         โ”‚ Robert โ”‚ Leila  โ”‚ Dmitri โ”‚ Aisha  โ”‚ Jordan โ”‚ Nina   โ”‚
โ”œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ผโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ผโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ผโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ผโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ผโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ผโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ค
โ”‚ Buy CRM       โ”‚   โœ“    โ”‚   โœ“    โ”‚   โœ“    โ”‚   โœ“    โ”‚   ~    โ”‚   โœ“    โ”‚
โ”‚ Build health  โ”‚   โœ“    โ”‚   โœ“    โ”‚   โœ“    โ”‚   โœ“    โ”‚   โœ“    โ”‚   โœ“    โ”‚
โ”‚ Salesforce    โ”‚   โœ“    โ”‚   โœ—    โ”‚   โœ—    โ”‚   โœ“    โ”‚   ~    โ”‚   ~    โ”‚
โ”‚ HubSpot       โ”‚   โœ—    โ”‚   โœ“    โ”‚   โœ“    โ”‚   โœ—    โ”‚   ~    โ”‚   ~    โ”‚
โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ
Legend: โœ“ agree  โœ— disagree  ~ context-dependent

### Actionable Hybrid Recommendation

1. **Buy**: Standard CRM for sales pipeline (HubSpot or Salesforce based on
   integration requirements)
2. **Build**: Custom customer health scoring platform integrated with product
   analytics
3. **Connect**: Clean API integration layer between systems
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall