Leverage Claude Opus 4.5's extended thinking capabilities for deep reasoning, complex analysis, and multi-step synthesis. Use when problems require thorough deliberation before response.
This skill guides optimal use of Claude Opus 4.5's extended thinking capabilities - the model's ability to reason deeply before responding, leading to more thoughtful, accurate, and nuanced outputs.
Extended thinking allows Opus 4.5 to:
Extended thinking engages automatically when:
Before answering, take time to:
1. Consider the problem from multiple angles
2. Identify potential pitfalls or edge cases
3. Weigh different approaches
4. Then provide your best response
Question: [Your complex question]
I need a thorough analysis of [topic].
Please consider:
- The technical perspective
- The business/practical perspective
- The user/human perspective
- Potential risks and downsides
- Long-term implications
Take your time to reason through each before synthesizing.
Walk me through your reasoning on this problem step by step.
Don't jump to conclusions - show your work.
Problem: [Complex problem]
For each step, explain:
- What you're considering
- Why you're making that choice
- What alternatives you rejected and why
I'm planning to [action/decision].
Before you help me execute this:
1. Steelman the opposing view - what's the best argument against?
2. What am I potentially missing or underweighting?
3. What would make this fail?
4. Only then, if it still seems right, help me proceed.
I have [number] different sources/perspectives on [topic]:
[List them]
Please synthesize these into a coherent understanding that:
- Identifies where they agree
- Explains where they conflict and why
- Weighs the evidence/arguments
- Provides your reasoned conclusion
Prompt pattern:
"Help me think through [strategic decision].
Consider: current state, desired outcome, constraints,
multiple paths, risks of each, second-order effects.
Don't rush to a recommendation - reason through thoroughly first."
Prompt pattern:
"I'm deciding between [Option A] and [Option B] for [system].
Before recommending, analyze:
- Scalability implications
- Maintenance burden
- Team capability fit
- Migration complexity
- What we might regret in 2 years"
Prompt pattern:
"I want to create [creative work] about [theme].
Before writing, explore:
- Different narrative approaches
- Tonal variations
- Structural options
- What makes this theme resonate
Then develop the direction that feels most promising."
Prompt pattern:
"[System/situation] is exhibiting [problem].
Don't jump to the obvious cause.
Consider:
- What are all possible causes?
- What evidence supports/refutes each?
- What's the most likely root cause?
- What would I need to verify to be sure?"
Prompt pattern:
"Help me understand [complex topic].
I need you to:
- Break down the key concepts
- Explain how they relate
- Identify what's well-established vs debated
- Note what's commonly misunderstood
- Synthesize into a coherent mental model"
Bad: "Write me a function that does X"
Better: "I need a function that does X. Before coding,
let's consider: edge cases, error handling,
interface design, testing approach."
Bad: "What's the best database for my app?"
Better: "What database should I use for [specific requirements]?
Consider multiple options, tradeoffs between them,
and what factors should weight most heavily."
Bad: "Should I do A or B?"
Better: "I'm choosing between A and B, but I'm open to
alternatives I haven't considered. What's the
best path forward given [context]?"
Bad: "Tell me the answer to [complex question]"
Better: "Help me understand [complex question].
Be explicit about what's certain vs uncertain,
and what evidence supports different views."
Use these phrases to encourage deeper deliberation:
Analytical Triggers:
Critical Triggers:
Synthesis Triggers:
Signs extended thinking is working well:
Signs it might need more prompting:
"First, think through the best approach to [task].
Consider alternatives and tradeoffs.
Once you have a clear plan, execute it autonomously,
but note any decision points where you chose between options."
"Draft an initial approach to [problem].
Then critique your own draft - what could be better?
Revise based on your critique.
Show me both the final version and key improvements you made."
"Analyze [situation] and identify the key decision points.
For each decision, explain the tradeoffs.
Before proceeding, I'll tell you my priorities,
then you can recommend the path that fits best."
Some tasks benefit from quick, direct responses:
For these, don't add complexity. Just ask directly.
Opus 4.5 specifically excels at:
Use extended thinking for:
Extended thinking is about quality of cognition, not length of output. The best responses come from genuine deliberation - use these patterns to unlock that capability.
npx skills add frankxai/opus-extended-thinking下载完整 Skill 目录,包含 SKILL.md 及所有相关文件
Search for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Start voice calls via the OpenClaw voice-call plugin.
Notion API for creating and managing pages, databases, and blocks.
Gemini CLI for one-shot Q&A, summaries, and generation.
Category:developer