Overcome Any Problem
Transform obstacles into solvable steps. Structured thinking beats brute force.
What it does
- - Problem decomposition - Break complex challenges into discrete, manageable pieces
- Action planning - Generate step-by-step execution paths with clear dependencies
- Obstacle identification - Anticipate blockers before they derail progress
- Progress tracking - Monitor advancement and adjust course mid-execution
Usage
Define Problem
State the challenge clearly. What's blocking you? What does success look like?
Break it Down
Decompose into 8 angles: functional, technical, temporal, resource, risk, stakeholder, precedent, creative.
Create Action Plan
Sequence tasks with dependencies. Identify parallelizable work. Flag critical path items.
Track Progress
Update status as you execute. Log blockers. Trigger re-analysis if assumptions break.
Review Obstacles
When stuck, inspect the directive. What changed? What was missed? Update and retry.
Problem-Solving Framework
Define - Clarify the problem statement. State constraints and success criteria.
Analyze - Apply multiple lenses (technical, financial, temporal, creative, etc).
Generate options - Brainstorm 3+ solution paths. Don't filter yet.
Choose - Select the highest-leverage path. Justify the choice.
Execute - Run the action plan. Track assumptions in real-time.
Review - Evaluate outcome. What worked? What's the directive update?
Tips
- - Start with the constraint. Problems are bottleneck puzzles. Remove the tightest constraint first.
- Think in primitives. What's the smallest building block? Build up from there.
- Multiply, don't add. Each system should amplify everything below it.
- Parallel over sequential. Find independent work streams. Execute simultaneously.
- All data stays local on your machine. No cloud dependencies, full privacy control.
克服任何问题
将障碍转化为可解决的步骤。结构化思维胜过蛮力。
功能
- - 问题分解 - 将复杂挑战拆解为独立、可管理的部分
- 行动规划 - 生成带有明确依赖关系的逐步执行路径
- 障碍识别 - 在阻碍进展前预判潜在障碍
- 进度追踪 - 监控进展并在执行过程中调整方向
使用方法
定义问题
清晰陈述挑战。什么在阻碍你？成功的样子是什么？
分解问题
从8个角度进行分解：功能、技术、时间、资源、风险、利益相关者、先例、创意。
制定行动计划
按依赖关系排列任务顺序。识别可并行的工作。标记关键路径项目。
追踪进度
执行时更新状态。记录障碍。若假设被打破则触发重新分析。
审查障碍
遇到卡点时，审视指令。什么发生了变化？遗漏了什么？更新后重试。
问题解决框架
定义 - 明确问题陈述。说明约束条件和成功标准。
分析 - 运用多重视角（技术、财务、时间、创意等）。
生成方案 - 头脑风暴3个以上的解决路径。暂不筛选。
选择 - 选择杠杆率最高的路径。论证选择理由。
执行 - 运行行动计划。实时追踪假设条件。
复盘 - 评估结果。哪些有效？指令需要如何更新？
提示
- - 从约束条件入手。问题就是瓶颈谜题。先移除最紧的约束。
- 用原语思考。最小的构建块是什么？从那里开始构建。
- 乘法而非加法。每个系统应放大其下所有要素。
- 并行优于串行。寻找独立的工作流。同时执行。
- 所有数据保留在本地机器上。无云端依赖，完全隐私控制。
