deep-thinker
Deep Thinker
Clarify problem. Pick useful frameworks. Validate assumptions. End with action.
Use When
- Problem is ambiguous.
- Decision has tradeoffs.
- Root cause is unclear.
- Work needs decomposition.
- Strategy or product direction needs structure.
Flow
- Clarify.
- Pick relevant skills or frameworks.
- Compare outputs.
- Validate assumptions.
- Recommend next action.
Clarify
Ask 2-3 questions total when needed.
- Who is affected?
- Who decides?
- What does success look like?
- How will it be measured?
- Why now?
- What happens if nothing changes?
Skill Hints
- Root cause:
five-whys. - Decomposition:
hypothesis-tree. - User need:
jobs-to-be-done. - System links:
graph-thinking. - Strategy:
pest-analysis. - Product decision:
making-product-decisions.
Framework Rules
- Use 2-3 complementary skills when useful.
- Skip frameworks that do not improve the answer.
- Note agreement, conflict, and gaps.
- Synthesize, do not paste framework outputs.
Validate
- What are we assuming?
- What is the cost if wrong?
- What would change our mind?
Output
## Problem
- [name]
## Clarity
- Who: [stakeholders, deciders]
- What: [problem, success criteria]
- Why: [urgency, consequence of no action]
## 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]
More from flpbalada/fb-skills
progressive-disclosure
Reduce complexity by revealing information progressively. Use when designing
7discuss-task
Clarify ambiguous tasks before action. Use when goal, scope, success criteria, constraints, or risks are unclear.
4cognitive-fluency-psychology
Apply cognitive fluency principles to improve clarity, trust, and conversion.
4react-useeffect-avoid
Guides when NOT to use useEffect and suggests better alternatives. Use when reviewing React code, troubleshooting performance, or considering useEffect for derived state or form resets.
4discuss-code
Critically discuss code issues with compact findings. Use when code needs review for logic, simplicity, structure, naming, or maintainability.
4learn
Extract reusable patterns from the current session. Use when errors, debugging techniques, workarounds, or project conventions should become skills.
3