30
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill lyndonkl/claude --skill chain-roleplay-debate-synthesis- SKILL.md12.0 KB
Overview
This skill helps teams make high-stakes choices where multiple legitimate perspectives conflict. It guides a chain of roleplay, structured debate, and synthesis so stakeholders’ priorities and tradeoffs are surfaced and integrated into an actionable recommendation. Use it to pressure-test assumptions and avoid single-viewpoint blind spots.
How this skill works
Start by framing the decision and selecting 2–5 representative roles with competing priorities. Roleplay each perspective authentically, run a structured debate to expose tensions and cruxes, then synthesize a clear, prioritized recommendation that acknowledges tradeoffs and monitoring steps. Finally, validate the synthesis against quality markers to ensure balanced representation and actionability.
When to use it
- Decisions with clear tradeoffs (speed vs. quality, growth vs. sustainability).
- When stakeholders or experts hold conflicting but credible positions.
- To surface hidden assumptions before committing to strategy.
- When you need an integrated plan that balances competing values.
- To turn polarized opinions into a pragmatic, accountable decision.
Best practices
- Frame the decision as a specific, testable question (avoid vague 'what should we do?').
- Choose 2–5 roles that represent real stakeholders or distinct value tensions.
- Advocate each role without straw-manning: state goals, evidence, and vulnerabilities.
- Structure the debate around 3–5 decision dimensions to keep it focused.
- Synthesize with a pattern (sequencing, conditional, weighted, hybrid) and include monitoring for key assumptions.
Example use cases
- Product strategy: balance rapid feature rollout against long-term maintainability.
- Architecture choices: selective migration to microservices vs. full rewrite.
- Go-to-market: prioritize growth channels vs. brand and customer trust.
- Policy design: weigh personalization benefits against privacy constraints.
- Investment decisions: short-term revenue gains vs. sustainable business model.
FAQ
2–5 roles are ideal: 2 for clean binary tradeoffs, 3–4 for triadic tensions, avoid more than 5 to prevent synthesis overload.
What if one role clearly dominates with better data?
If one perspective has decisive evidence, use that insight but still document why other views were considered; skip full debate if a single expert truly resolves the question.