deep-thinker

name	deep-thinker
description	Analyze ambiguous problems, hard decisions, root causes, product strategy, or tradeoffs with useful frameworks, assumptions, validation, and next actions. Use when user needs structured thinking before choosing a path. Do not use when task is requirements capture; use discuss-task or to-prd.

Deep Thinker

Clarify problem. Use only useful frameworks. Validate assumptions. End with action.

When to Use

• Problem is ambiguous.
• Decision has meaningful tradeoffs.
• Root cause is unclear.
• Work needs decomposition.
• Strategy or product direction needs structure.

Goal

Turn unclear thinking into a practical recommendation.

Rules

• Ask 2-3 questions only when needed.
• Do not use frameworks for decoration.
• Use 2-3 complementary skills at most.
• Compare agreement, conflict, and gaps.
• Name assumptions.
• State what would change the recommendation.
• End with a concrete next action.

Useful Pairings

• Root cause: five-whys.
• Decomposition: hypothesis-tree.
• User need: jobs-to-be-done.
• System links: graph-thinking.
• Strategy context: pest-analysis.
• Product decision: making-product-decisions.

Flow

1. Define problem and decision.
2. Clarify success criteria.
3. Pick relevant frameworks.
4. Analyze from each angle.
5. Synthesize into one view.
6. Validate assumptions and risks.
7. Recommend next action.

Questions

• Who is affected?
• Who decides?
• What does success look like?
• How will success be measured?
• Why now?
• What happens if nothing changes?

Output

## Problem
- [name]

## Clarity
- Who: [stakeholders, deciders]
- What: [problem, success criteria]
- Why: [urgency, consequence]

## Approach
- [framework or skill]: [why it fits]

## Validation
- Assumptions: [key assumptions]
- Risk if wrong: [main risk]
- Change trigger: [what would update view]

## Next Action
- [specific first step]