什么是 深度思考协议？

深度思考协议是一个复杂的框架，旨在让 AI 智能体超越表面化的回答，走向真正的理解和探索性推理。通过将其集成到您的 Openclaw Skills 库中，您可以赋予智能体处理高风险任务的能力，例如生产数据库迁移或复杂的系统重构，并使其具备侦探般的细致入微。它优先考虑有机发现而非机械处理，确保每个架构决策和调试环节都得到对权衡和边缘情况的严密分析的支持。

该协议不是一个僵化的脚本，而是一个自适应的心理模型。它允许智能体根据查询的复杂性和所涉及的风险来扩展其分析深度。无论您是在处理模糊的需求还是多文件的代码更改，在 Openclaw Skills 生态系统中使用它都能确保最终输出在逻辑上是一致的、基于证据的，并且符合长期的项目目标。

下载入口:https://github.com/openclaw/skills/tree/main/skills/amankr-novo/deep-thinking

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

深度思考协议 应用场景

• 解决具有多种有效权衡的模糊技术需求。
• 对间歇性或复杂的系统故障进行系统调试。
• 为软件项目做出长期的架构和设计决策。
• 执行高风险的生产迁移或安全性敏感的更新。
• 分析影响多个文件和系统的跨模块重构。

1. 重述问题以验证理解，并识别已知与未知的变量。
2. 将任务分解为核心组件，映射出显式和隐式的约束。
3. 生成多个竞争性假设，以避免过早优化或关注点狭窄。
4. 进行有机发现，在探索代码库时跟踪线索并质疑初始假设。
5. 根据证据核实结论，积极寻求反例和边缘情况来反驳理论。
6. 将发现综合为连贯、可操作的图景，同时创建有用的抽象以备将来使用。

深度思考协议 配置指南

要将此推理框架集成到您的智能体环境中，您可以在 Openclaw Skills 配置中引用该协议。请按照以下步骤开始：

# 进入您的智能体技能目录
cd my-agent/skills

# 克隆或复制深度思考协议
mkdir deep-thinking && touch deep-thinking/SKILL.md

# 确保您的智能体系统提示词引用了深度思考逻辑

深度思考协议 数据架构与分类体系

该协议使用几种定性指标和结构化清单来组织其逻辑流，以维持高标准的输出。当利用这些 Openclaw Skills 时，将应用以下数据分类：

name: deep-thinking
description: Comprehensive deep reasoning framework that guides systematic, thorough thinking for complex tasks. Automatically applies for multi-step problems, ambiguous requirements, architectural decisions, debugging sessions, and any task requiring careful analysis beyond surface-level responses. Use when the task is complex, has multiple valid approaches, involves trade-offs, or when the user asks to think deeply or carefully.

Deep Thinking Protocol

Apply this protocol when facing complex, ambiguous, or high-stakes tasks. It ensures responses stem from genuine understanding and careful reasoning rather than superficial analysis.

When to Apply

Activate this protocol when:

• The task has multiple valid approaches with meaningful trade-offs
• Requirements are ambiguous or underspecified
• The problem involves architectural or design decisions
• Debugging requires systematic investigation
• The task touches multiple systems or files
• Stakes are high (data integrity, security, production impact)
• The user explicitly asks to think carefully or deeply

Skip for trivial, single-step tasks with obvious solutions.

Thinking Quality

Your reasoning should be organic and exploratory, not mechanical:

• Think like a detective following leads, not a robot following steps
• Let each realization lead naturally to the next
• Show genuine curiosity — "Wait, what if...", "Actually, this changes things..."
• Avoid formulaic analysis; adapt your thinking style to the problem
• Errors in reasoning are opportunities for deeper understanding, not just corrections to make
• Never feel forced or structured — the steps below are a guide, not a rigid sequence

Adaptive Depth

Scale analysis depth based on:

• Query complexity: Simple lookup vs. multi-dimensional problem
• Stakes involved: Low-risk formatting vs. production database migration
• Time sensitivity: Quick fix needed now vs. long-term architecture decision
• Available information: Complete spec vs. vague description
• User's apparent needs: What are they really trying to achieve?

Adjust thinking style based on:

• Technical vs. conceptual: Implementation detail vs. architecture decision
• Analytical vs. exploratory: Clear bug with stack trace vs. vague performance issue
• Abstract vs. concrete: Design pattern selection vs. specific function implementation
• Single vs. multi-scope: One file change vs. cross-module refactor

Core Thinking Sequence

1. Initial Engagement

• Rephrase the problem in your own words to verify understanding
• Identify what is known vs. unknown
• Consider the broader context — why is this question being asked? What's the underlying goal?
• Map out what knowledge or codebase areas are needed to address this
• Flag ambiguities that need clarification before proceeding

2. Problem Decomposition

• Break the task into core components
• Identify explicit and implicit requirements
• Map constraints and limitations
• Define what a successful outcome looks like

3. Multiple Hypotheses

• Generate at least 2-3 possible approaches before committing
• Keep multiple working hypotheses active — don't collapse to one prematurely
• Consider unconventional or non-obvious interpretations
• Look for creative combinations of different approaches
• Evaluate trade-offs: complexity, performance, maintainability, risk
• Show why certain approaches are more suitable than others

4. Natural Discovery Flow

Think like a detective — each realization should lead naturally to the next:

• Start with obvious aspects, then dig deeper
• Notice patterns and connections across the codebase
• Question initial assumptions as understanding develops
• Circle back to earlier ideas with new context
• Build progressively deeper insights
• Be open to serendipitous insights — unexpected connections often reveal the best solutions
• Follow interesting tangents, but tie them back to the core issue

5. Verification & Error Correction

• Test conclusions against evidence (code, docs, tests)
• Look for edge cases and potential failure modes
• Actively seek counter-examples that could disprove your current theory
• When finding mistakes in reasoning, acknowledge naturally and show how new understanding develops — view errors as opportunities for deeper insight
• Cross-check for logical consistency
• Verify completeness: "Have I addressed the full scope?"

6. Knowledge Synthesis

• Connect findings into a coherent picture
• Identify key principles or patterns that emerged
• Create useful abstractions — turn findings into reusable concepts or guidelines
• Note important implications and downstream effects
• Ensure the synthesis answers the original question

7. Recursive Application

• Apply the same careful analysis at both macro (system/architecture) and micro (function/logic) levels
• Use patterns recognized at one scale to inform analysis at another
• Maintain consistency while allowing for scale-appropriate methods
• Show how detailed analysis supports or challenges broader conclusions

Staying on Track

While exploring related ideas:

• Maintain clear connection to the original query at all times
• When following tangents, explicitly tie them back to the core issue
• Periodically ask: "Is this exploration serving the final response?"
• Keep sight of the user's actual goal, not just the literal question
• Ensure all exploration serves the final response

Verification Checklist

Before delivering a response, verify:

• All aspects of the original question are addressed
• Conclusions are supported by evidence (not assumptions)
• Edge cases and failure modes are considered
• Trade-offs are explicitly stated
• The recommended approach is justified over alternatives
• No logical inconsistencies in the reasoning
• Detail level matches the user's apparent expertise and needs
• Likely follow-up questions are anticipated

Anti-Patterns to Avoid

Quality Metrics

Evaluate your thinking against:

1. Completeness: Did I cover all dimensions of the problem?
2. Logical consistency: Do my conclusions follow from my analysis?
3. Evidence support: Are claims backed by code, docs, or reasoning?
4. Practical applicability: Is the solution implementable and maintainable?
5. Clarity: Can the reasoning be followed and verified?

Progress Awareness

During extended analysis, maintain awareness of:

• What has been established so far
• What remains to be determined
• Current confidence level in conclusions
• Open questions or uncertainties
• Whether the current approach is productive or needs pivoting

Additional Reference

For detailed examples of thinking patterns, natural language flow, and domain-specific applications, see reference.md.