wyattowalsh/panel-debate-skill
panel-debate
VerifiedHosts 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.3 KB |
| assets/.gitkeep | other | 117 B |
| examples/README.md | markdown | 1.1 KB |
| examples/architecture-decision.md | markdown | 7.3 KB |
| examples/business-strategy.md | markdown | 4.5 KB |
| examples/security-implementation.md | markdown | 2.8 KB |
| references/expert-generation.md | markdown | 28.8 KB |
| references/output-formats.md | markdown | 35.3 KB |
| references/research-foundations.md | markdown | 11.3 KB |
| references/synthesis-patterns.md | markdown | 32.1 KB |
| references/turn-taking.md | markdown | 27.1 KB |
examples/architecture-decision.md
View on GitHub# Example: Architecture Decision
**Topic**: "Should we adopt microservices or stick with our monolith?"
**Complexity Score**: 11 (Medium-High)
- Stakeholders: 4 (dev, ops, business, users)
- Trade-offs: 2 (complexity vs flexibility, speed vs reliability)
- Time horizon: Years
- Reversibility: Difficult
- Domain breadth: Cross-functional
**Panel Size**: 5 experts
**Rounds**: 2
---
## Panel Header
╭─ Panel Discussion: Microservices Migration Strategy ──────╮
│ Experts: Dr. Chen (Distributed Systems), Rashida Okoye │
│ (Engineering Ops), Kai Lindström (Platform), │
│ Sophia Martinez (Product), Dr. Nwosu (CTO) │
╰───────────────────────────────────────────────────────────╯
## Diversity Score: 75/100
| Category | Score | Details |
|----------|-------|---------|
| Archetype Diversity | 35/40 | All required present, 5 distinct |
| Domain Diversity | 25/30 | 4 domains represented |
| Perspective Diversity | 15/30 | Optimist + Skeptic present |
---
## Round 1: Opening Statements
🎤 Dr. Marcus Chen (Distributed Systems Specialist):
"Microservices offer clear benefits for scaling and team autonomy, but
they require significant investment in infrastructure, observability,
and distributed systems expertise. The question isn't 'microservices
vs. monolith' but 'what problem are we solving?'"
🎤 Rashida Okoye (VP Engineering Operations) [Skeptic]:
"From an operational perspective, I'm skeptical. We've seen teams
underestimate the debugging complexity and cognitive load. How many
of your engineers have production experience with distributed systems?"
🎤 Kai Lindström (Platform Architect) [Contrarian]:
"I want to challenge the premise. A well-structured modular monolith
gives you most benefits of microservices without the operational
overhead. You can always extract services later when you have clear
scaling bottlenecks."
🎤 Sophia Martinez (Principal Product Engineer) [Synthesizer]:
"Both perspectives are valid. What matters is: how fast do we need
to ship features, and what's our team structure? Service boundaries
should follow team boundaries."
🎤 Dr. Amara Nwosu (CTO) [Optimist + Strategic]:
"Taking the 3-year view: where do we want to be? If we anticipate
significant scale and team growth, investing in microservices now
prevents painful migration later."
---
📋 Round 1 Synthesis:
• Agreement: Architecture choice depends on specific context
• Agreement: Team capability is a critical factor
• Tension: Invest now vs. migrate when needed
• Tension: Operational complexity vs. future flexibility
• Open question: What is the team's distributed systems experience?
• Open question: What are the specific scaling requirements?
---
## Round 2: Cross-Examination with Contrarian Protection
🎤 Moderator:
"Before we continue, Kai, as our contrarian voice: what are we missing?
What's the strongest argument against our emerging consensus?"
🎤 Kai Lindström (Contrarian Challenge):
"Everyone's assuming microservices is the destination. But Netflix,
Amazon—they evolved there over decades with thousands of engineers.
For a 50-person team, the modular monolith isn't a stepping stone,
it might be the right final answer. We need to question whether
microservices is even appropriate for our scale."
🎤 Rashida Okoye (building on Kai):
"Exactly. And I've seen the hidden costs: 3x monitoring complexity,
network debugging nightmares, deployment coordination overhead.
With our current 15 engineers, 3 with microservices experience,
I'd strongly advocate modular monolith first."
🎤 Dr. Chen (responding to Rashida):
"I hear the caution, but consider: 10x traffic growth in 2 years is
significant. A monolith won't scale horizontally without major
refactoring. Perhaps a hybrid—modular monolith with 1-2 extracted
services for the highest-scale components?"
🎤 Dr. Nwosu (synthesizing):
"The hybrid approach resonates. Start modular, extract surgically.
But we need clear triggers: when do we know it's time to extract?"
🎤 Sophia Martinez (agreeing, adding criteria):
"Triggers should be measurable: resource utilization divergence,
deployment blocking, database connection exhaustion. Not aspirational."
---
📋 Round 2 Synthesis:
• Emerging consensus: Modular monolith with selective extraction
• Agreement: Team capability building is essential
• Agreement: Identify 1-2 highest-scale components for early extraction
• Agreement: Triggers should be measurable, not aspirational
• Tension: Timeline for extraction (proactive vs. reactive)
• Resolved: Binary choice is false—hybrid approach preferred
• Minority position (Kai): Modular monolith may be permanent answer
---
## Final Report
╔═══════════════════════════════════════════════════════════╗
║ PANEL CONCLUSIONS ║
╠═══════════════════════════════════════════════════════════╣
║ Topic: Microservices Migration Strategy ║
║ Experts: 5 | Rounds: 2 | Consensus: STRONG ║
╚═══════════════════════════════════════════════════════════╝
### Executive Summary
Panel recommends modular monolith architecture with selective service
extraction for highest-scale components. This balances shipping velocity
with scalability preparation while building team distributed systems
capability incrementally.
### Consensus Points (Confidence-Weighted)
1. **Modular Monolith as Foundation** [High confidence: 0.95]
- Weight: Chen (0.9) + Rashida (1.0) + Kai (1.0) + Sophia (0.8) + Nwosu (0.7)
- Structure monolith with clear module boundaries from day one
2. **Selective Service Extraction** [High confidence: 0.85]
- Identify 1-2 components with clearest scaling needs
- Extract as services to build team experience
- Use measurable triggers, not aspirational timelines
### Key Trade-offs
| Trade-off | Panel Position | Dissent |
|-----------|---------------|---------|
| Invest now vs. wait | Wait with preparation | Nwosu: earlier investment |
| Full microservices vs. hybrid | Hybrid | None |
| Complexity vs. flexibility | Prioritize simplicity | Chen: flexibility has value |
### Dissenting View (Preserved)
**Kai Lindström**: "I maintain that for teams under 100 engineers,
the modular monolith may be the permanent right answer, not just a
stepping stone. Don't assume microservices is the destination."
### Actionable Recommendations
**Immediate (Week 1)**:
1. Define clear module boundaries in current architecture
2. Identify top 2 scaling bottleneck candidates
3. Establish observability baseline
**Short-term (Month 1-2)**:
1. Implement measurable extraction triggers
2. Extract first service from highest-scale component
3. Begin distributed systems training program
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| 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: 194k | Updated | Claude CodeCodex | Verified | Install |