スキル一覧に戻る
Tempuss

thinking-framework

by Tempuss

4🍴 0📅 2026年1月11日
GitHubで見るManusで実行

SKILL.md


name: thinking-framework description: Use this when complex problem-solving, root cause analysis, strategic decision-making, or systematic thinking is needed. Applies 15 thinking methods with multi-agent orchestration and Clear-Thought MCP integration for enhanced analysis quality.

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

TierAgentRoleClear-Thought Tools
1OrchestratorWorkflow coordination, complexity routingdecisionframework, metacognitivemonitoring
2ProblemDefinerProblem clarification, decompositionsequentialthinking, mentalmodel
2MethodExecutorThinking method executionMethod-specific (see mapping)
2StrategyArchitectStrategic synthesis, action planningcollaborativereasoning, decisionframework

Complexity-Based Routing

ComplexityIndicatorsAgent ConfigurationTime
SimpleSingle cause, 1-2 steps, clear pathOrchestrator only<30s
Medium3-5 factors, some ambiguity+ 1 Specialist (sequential)30-60s
Complex5+ factors, high interdependencies+ 2-3 Specialists (parallel)60s+

Clear-Thought Tool Mapping

MethodPrimary ToolSecondary Tool
5 Whysequentialthinking-
Fishbonecollaborativereasoningvisualreasoning
First Principlesmentalmodelsequentialthinking
SWOTdecisionframework-
OODA Loopscientificmethodsequentialthinking
Dialecticstructuredargumentation-
Design Thinkingcollaborativereasoningmentalmodel
Paretodecisionframeworkmentalmodel
PDCAscientificmethod-
GAP Analysisvisualreasoningdecisionframework
Kepner-Tregoedecisionframeworkstructuredargumentation
TRIZmentalmodeldesignpattern
SCAMPERcollaborativereasoning-
DMAICscientificmethodmetacognitivemonitoring

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:

Problem TypeMethodsClear-Thought Tool
root_cause5 Why, Fishbonesequentialthinking, collaborativereasoning
creative_innovationSCAMPER, TRIZ, Design Thinkingcollaborativereasoning, mentalmodel
strategic_planningSWOT + 2x2, GAP Analysisdecisionframework, visualreasoning
process_improvementPareto, PDCA, GAPdecisionframework, scientificmethod
decision_makingOODA Loop, Kepner-Tregoescientificmethod, decisionframework

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

GateStageCheckTool
G1Problem DefinitionClarity, specificity, boundednessmetacognitivemonitoring
G2Method SelectionProblem-method fitdecisionframework
G3AnalysisDepth, evidence, logicmetacognitivemonitoring
G4IntegrationCoherence, completeness, actionabilitymetacognitivemonitoring

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


Anti-Patterns

PatternProblemSolution
Over-engineeringA Routine for simple problemsUse complexity assessment
Under-analysisSimple method for complex problemsProper routing
Tool mismatchWrong Clear-Thought tool for methodFollow mapping table
Skip quality gatesMissing validationEnforce gate protocol
Sequential when parallelSlow complex analysisUse parallel agents

Meta

After analysis, briefly reflect:

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

スコア

総合スコア

50/100

リポジトリの品質指標に基づく評価

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

0/10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

レビュー

💬

レビュー機能は近日公開予定です