Thinking Frameworks

Thinking Frameworks for Agent Teams

Overview

This skill implements structured thinking methodologies as multi-agent teams. Each framework decomposes into specialized agent roles that produce stronger outputs through cognitive diversity and structured tension.

Four frameworks, five composition patterns, and a triage system.

Quick Selection: Which Framework?

Read this table first. Pick the framework, then read its reference file.

Decision Logic

Is there a clear binary choice (X vs Y)?
  YES → Dialectical (3 agents: Advocate → Challenger → Integrator)

Do we need comprehensive, multi-stakeholder analysis?
  YES → Six Hats (7 agents: Blue orchestrator + 6 perspective agents)

Are we questioning inherited complexity or assumptions?
  YES → First Principles (3 agents: Archaeologist → Architect → Evaluator)

Are we stuck and need a creative breakthrough?
  YES → Collision-Zone (existing skill)

Is the problem too complex for a single framework?
  YES → Read composition-patterns.md for multi-framework orchestration

Not sure what we're dealing with?
  → Use the Cynefin Classifier (Pattern 4 in composition-patterns.md)

Framework Summaries

Dialectical Thinking (3 Agents)

Core idea: Truth emerges from structured intellectual conflict.

• Advocate builds the strongest case FOR a position
• Challenger systematically dismantles it and proposes an alternative
• Integrator transcends both into something stronger than either

Best for: binary decisions, architecture debates, RFP responses, technology selection. Cycle time: fast (3 sequential agent calls).

Read references/dialectical.md for the full process, output formats, and agent prompts.

Six Thinking Hats (7 Agents)

Core idea: Parallel thinking beats adversarial thinking for comprehensive coverage.

Six cognitive modes, each worn one at a time:

• 🔵 Blue (Process) — orchestrates the sequence, synthesizes results
• ⚪ White (Facts) — data, information gaps, confidence levels
• 🔴 Red (Intuition) — feelings, hunches, stakeholder sentiment
• ⬛ Black (Caution) — risks, failure modes, compliance gaps
• 🟡 Yellow (Optimism) — benefits, value, strategic positioning
• 🟢 Green (Creativity) — alternatives, wild cards, assumption challenges

Best for: go/no-go decisions, post-mortems, cross-functional analysis, project evaluation. Cycle time: medium (7 sequential agent calls, some parallelizable).

Read references/six-hats.md for hat sequences, output formats, and agent prompts.

First Principles Decomposition (3 Agents)

Core idea: Most complexity is inherited, not necessary. Strip to fundamentals, rebuild.

• Archaeologist digs through assumption layers to find bedrock truths
• Architect builds from ONLY those truths (never sees the original system)
• Evaluator compares the reconstruction against the original

The information barrier is critical: the Architect must never see the current implementation. This prevents anchoring bias.

Best for: legacy modernization, architecture simplification, challenging "best practices." Cycle time: medium (3 sequential, deep-thinking agent calls).

Read references/first-principles.md for the full process, domain-specific patterns, and agent prompts.

Composition Patterns (Multi-Framework)

When a single framework isn't enough, composition patterns chain them together with defined data flows and information barriers.

Read references/composition-patterns.md for complete orchestration specs, data flow rules, information barriers, and anti-patterns.

Claude Code Implementation

Spawning Agent Teams with Task

Each agent in a framework runs as a Claude Code Task (subagent). The orchestration pattern is always:

1. Load the relevant reference file for agent prompts
2. Spawn each agent sequentially, passing outputs forward
3. Enforce information barriers (some agents must NOT see certain data)
4. Final agent produces the recommendation

Basic Task Pattern

# Dialectical example
thesis = Task(
    prompt=f"{advocate_prompt}\n\nPROBLEM: {problem}",
    description="Dialectical: Build thesis"
)

antithesis = Task(
    prompt=f"{challenger_prompt}\n\nTHESIS:\n{thesis}",
    description="Dialectical: Challenge thesis"
)

synthesis = Task(
    prompt=f"{integrator_prompt}\n\nTHESIS:\n{thesis}\n\nANTITHESIS:\n{antithesis}",
    description="Dialectical: Synthesize"
)

CLAUDE.md Integration

Add this block to any project's CLAUDE.md to enable thinking framework agent teams:

## Thinking Frameworks

For complex decisions, use the thinking-frameworks skill:
- "Use dialectical analysis for [problem]" → Advocate → Challenger → Integrator
- "Run six hats on [problem]" → Blue orchestrates 6 perspective agents
- "Apply first principles to [problem]" → Archaeologist → Architect → Evaluator
- For multi-framework: read composition-patterns.md and select a pattern

Context Management Rules

Each agent should receive:

1. Its role-specific system prompt (from the framework's reference file)
2. The problem statement
3. Outputs from previous agents in the chain
4. Optional domain context (project docs, policies, technical specs)

Keep agent context intentionally focused. What an agent CANNOT see is as important as what it can see. The reference files specify information barriers for each framework.

Practical Applications

Reference Files

Read the appropriate reference file BEFORE building agent prompts:

Red Flags That a Thinking Framework Is Needed

• "We've already decided" → Dialectical (challenge the decision)
• "Everyone agrees" → Six Hats (find what's missing)
• "That's how it's always been done" → First Principles (strip assumptions)
• "We've tried everything" → Collision-Zone (force novel connections)
• "It's too complex to change" → First Principles (separate necessary from inherited)
• "I don't know where to start" → Cynefin Triage (classify, then route)