syzkillall/comprehensive-thinking-skill
comprehensive-thinking
VerifiedUse when Codex must make a high-quality judgment on any complex problem, not only technical problems. Trigger when a question has high complexity, uncertainty, cost of being wrong, long-term impact, value tradeoffs, possible structural causes, or when the user asks for 全面思考, 深度理解, 系统性分析, 帮我想清楚, 从根上看, 这件事到底怎么看, 方法论, 复杂问题拆解, 系统方案, 架构判断, 策略判断, or 根因分析. Also trigger for project and engineering high-risk scenarios such as multi-module, multi-environment, multi-data-source, multi-state, financial truth, live trading, ledger, revenue, customer assets, order governance, broker interfaces, online availability, major solution selection, and system closure.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 24.7 KB |
| agents/openai.yaml | config | 654 B |
| examples/prompts.md | markdown | 1.6 KB |
| references/master-theory-research.md | markdown | 4.2 KB |
examples/prompts.md
View on GitHub# 示例提示词
这些示例用于测试或演示 `comprehensive-thinking` 的触发方式。它们不是固定模板,只是帮助使用者理解什么类型的问题适合调用全面思考。
## 复杂判断
```text
请用全面思考帮我判断:我现在是否应该把这个产品从工具型产品转向平台型产品?
```
适合观察:
- 是否重新定义了表层问题背后的真实目标。
- 是否识别了关键矛盾,而不是只列优缺点。
- 是否给出最强反方意见和前提分析。
- 是否说明结论的边界与验证方式。
## 工程架构
```text
请用全面思考分析:这个多模块系统是否应该重构为事件驱动架构?
```
适合观察:
- 是否区分了当前痛点、长期演进、系统边界和故障域。
- 是否引入了合适的工程理论或成熟实践。
- 是否说明哪些事实会推翻当前判断。
- 是否落到验证、测试、迁移或回滚路径。
## 研究问题
```text
请用全面思考帮我理解:这个研究方向到底有没有长期价值?
```
适合观察:
- 是否把“有没有价值”拆成学术价值、应用价值、可验证性和资源约束。
- 是否比较了竞争解释,而不是只给乐观判断。
- 是否标注未知与待查证事实。
- 是否把结论降级到合适的置信度。
## 个人或组织决策
```text
请用全面思考帮我想清楚:我是否应该投入一年时间做这个方向?
```
适合观察:
- 是否识别真实目标和机会成本。
- 是否区分短期收益、长期路径和不可逆代价。
- 是否提出最强反方意见。
- 是否给出阶段性验证信号和转向条件。
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |