Thinking Framework

Thinking Framework v4.0 - Multi-Agent Systematic Problem-Solving

Purpose: Decompose complex problems and derive optimal solutions using structured thinking methods with multi-agent orchestration.

When to Use

• Complex problem-solving requiring systematic decomposition
• Root cause analysis (finding the "why" behind issues)
• Strategic planning (strengths/weaknesses, competitive analysis)
• Decision-making under uncertainty
• Innovation requiring creative breakthroughs

Multi-Agent Architecture (v4.0)

Agent Tiers

Complexity-Based Routing

Clear-Thought Tool Mapping

Execution Routines

A. Divide & Conquer (Complex Only)

When: Systemic problems with 5+ interdependent factors

Agent Flow:

Orchestrator → ProblemDefiner → MethodExecutor(s) [parallel] → StrategyArchitect → Orchestrator

Process:

1. Orchestrator: Assess complexity, dispatch ProblemDefiner
2. ProblemDefiner: Define problem, decompose into ≤5 sub-problems
3. MethodExecutor(s): Analyze sub-problems in parallel
   • Each executor uses appropriate Clear-Thought tool
4. StrategyArchitect: Synthesize findings, create action plan
5. Orchestrator: Quality gate, final integration

Output:

## Problem Definition
[Clear statement from ProblemDefiner]

## Sub-Problem Analyses
| Sub-Problem | Method | Root Cause | Recommendation |
|-------------|--------|------------|----------------|
| SP1 | [method] | [cause] | [action] |

## Integrated Strategy
[From StrategyArchitect]

## Quality Assessment
- Confidence: [%]
- Uncertainties: [list]

## Core Insight
[One sentence]

B. Method Selection (All Cases)

When: Any problem, especially Simple-Medium complexity

Agent Flow:

• Simple: Orchestrator only (direct method application)
• Medium: Orchestrator → MethodExecutor → Orchestrator

Process:

1. Classify problem type
2. Select method using matching matrix
3. Execute with appropriate Clear-Thought tool
4. Output optimized format

Method-Problem Matching:

C. Strategy Routine (Strategic Decisions)

When: Strategic planning with strengths/weaknesses analysis

Agent Flow:

Orchestrator → ProblemDefiner → MethodExecutor (SWOT) → StrategyArchitect → Orchestrator

Process:

1. Diagnose: Strengths (with evidence) + Weaknesses (root cause via 5 Why)
2. Analyze: Use decisionframework for SWOT evaluation
3. Strategize: StrategyArchitect creates 2x2 matrix
4. Plan: GAP Analysis → Action items

2x2 Matrix (MANDATORY):

           │ Maximize Strengths │ Address Weaknesses │
───────────┼────────────────────┼────────────────────┤
High       │   DO FIRST         │   REMOVE RISK      │
Priority   │   (Invest now)     │   (Critical fix)   │
───────────┼────────────────────┼────────────────────┤
Low        │   LONG-TERM R&D    │   STRATEGIC IGNORE │
Priority   │   (Future bet)     │   (Accept risk)    │

Core Strategy Template:

"Maximize [strength] through [method], address [weakness] via [action], to achieve [goal]."

Quality Gates

Gate Protocol:

• Complex: All gates mandatory
• Medium: G2 + G4
• Simple: G4 only

Output Guidelines

Format Selection:

• Structured comparisons → Markdown tables
• Sequential processes → Numbered lists
• Problem decomposition → Mermaid diagrams
• Strategic decisions → 2x2 Matrix

Always Include:

• Complexity assessment (pre-flight)
• Method selection justification
• Confidence score
• One-sentence summary

Quick Reference

• Agent Prompts: agents/
• Method Catalog: reference/INDEX.md
• 60-sec Selector: reference/QUICK_SELECTOR.md
• Multi-Method Workflows: reference/METHOD_COMBINATIONS.md
• Agent Patterns: reference/AGENT_PATTERNS.md
• Practical Examples: GUIDE.md

Anti-Patterns

Meta

After analysis, briefly reflect:

• What worked? What could improve?
• Was method optimal? Was tool mapping effective?
• Agent coordination smooth?