think-tank

Name: think-tank
Availability: InStock
Author: cookys

Coordinate six role perspectives into a consolidated Decision Brief.

10|Updated Mar 18, 2026

Search Tags:#architecture #strategy #decision-making #product-management #stakeholders #think-tank #multirole

Ready to run

npx skills add https://github.com/cookys/autopilot --skill think-tank-cookys

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: think-tank
Source: https://github.com/cookys/autopilot/tree/main/skills/think-tank
Command: npx skills add https://github.com/cookys/autopilot --skill think-tank-cookys

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Think Tank Skill provides a structured, multi-role framework to generate diverse strategic perspectives on a single decision, reducing bias and surfacing tradeoffs.

Core Features & Use Cases

Parallel 6-role analysis: Architect, Product Director, UX Advocate, QA Devil, Ops/SRE, Customer Advocate each provide independent viewpoints.
Cross-collision synthesis: combines perspectives to create a Decision Brief with consensus, divergences, collision insights and recommendations.
Escalation path: supports optional escalation to think-tank-dialectic for low-consensus, high-stakes decisions.

Quick Start

Provide a topic and context, then dispatch all six roles simultaneously to generate parallel analyses and a consolidated Decision Brief.

Frequently Asked Questions about think-tank

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I get diverse stakeholder perspectives for a product strategy decision?▼

Multi-role debate for strategic decisions works by dispatching six independent role analyses simultaneously, then synthesizing their viewpoints into a consolidated Decision Brief that highlights consensus, divergences, and collision insights.

What is the best way to analyze architectural trade-offs and risk assessment?▼

The best way to analyze architectural trade-offs is running a parallel multi-role assessment where independent viewpoints cross-collide, synthesizing architectural, UX, and operations perspectives into a structured Decision Brief with actionable recommendations.

How do I conduct multi-role analysis to reduce bias in scope decisions?▼

Conduct multi-role analysis for scope decisions by providing topic context to dispatch six standardized role prompts simultaneously, allowing cross-collision synthesis to reduce individual bias and generate a structured recommendation.

Can I resolve low-consensus stakeholder viewpoints for high-stakes decisions?▼

You can resolve low-consensus stakeholder viewpoints by using an optional escalation path to dialectic analysis, which further processes high-stakes collisions when the initial six-role synthesis fails to reach adequate agreement.

Does cross-collision synthesis work for customer impact and UX advocacy trade-offs?▼

Cross-collision synthesis works for customer impact and UX advocacy by independently capturing these viewpoints alongside architectural and product constraints, then combining them to surface trade-offs and consensus within the Decision Brief.