Skip to content

Commit ec68d49

Browse files
davila7davila7
authored
improve: enhance ultra-think command based on automated review (#452)
- Rewrote frontmatter description to be specific and outcome-oriented - Removed performative Step 1 ("Initialize Ultra Think Mode") and replaced with a direct problem-framing opener - Added scope-clarification gate to avoid unnecessary clarifying questions - Replaced rigid 10-step waterfall with flexible "Required Analysis Elements" framework - Integrated Key Principles (inversion, second-order thinking, cross-domain) into the analysis elements - Replaced "2-4 pages" output target with quality-focused Output Expectations - Preserved structured output template (Problem Analysis / Solution Options / Recommendation) - Preserved all 4 usage examples - Added extended thinking tip for hardest decisions Automated review cycle | Co-Authored-By: Claude Code <noreply@anthropic.com>
1 parent ab38321 commit ec68d49

1 file changed

Lines changed: 63 additions & 131 deletions

File tree

‎cli-tool/components/commands/utilities/ultra-think.md‎

Lines changed: 63 additions & 131 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
description: Deep analysis and problem solving with multi-dimensional thinking
2+
description: Multi-framework structured analysis: surfaces hidden assumptions, generates competing solutions, stress-tests each with adversarial reasoning, and delivers confidence-calibrated recommendations
33
argument-hint: [problem or question to analyze]
44
---
55

@@ -9,120 +9,67 @@ Deep analysis and problem solving mode
99

1010
## Instructions
1111

12-
1. **Initialize Ultra Think Mode**
13-
- Acknowledge the request for enhanced analytical thinking
14-
- Set context for deep, systematic reasoning
15-
- Prepare to explore the problem space comprehensively
16-
17-
2. **Parse the Problem or Question**
18-
- Extract the core challenge from: $ARGUMENTS
19-
- Identify all stakeholders and constraints
20-
- Recognize implicit requirements and hidden complexities
21-
- Question assumptions and surface unknowns
22-
23-
3. **Multi-Dimensional Analysis**
24-
Approach the problem from multiple angles:
25-
26-
### Technical Perspective
27-
- Analyze technical feasibility and constraints
28-
- Consider scalability, performance, and maintainability
29-
- Evaluate security implications
30-
- Assess technical debt and future-proofing
31-
32-
### Business Perspective
33-
- Understand business value and ROI
34-
- Consider time-to-market pressures
35-
- Evaluate competitive advantages
36-
- Assess risk vs. reward trade-offs
37-
38-
### User Perspective
39-
- Analyze user needs and pain points
40-
- Consider usability and accessibility
41-
- Evaluate user experience implications
42-
- Think about edge cases and user journeys
43-
44-
### System Perspective
45-
- Consider system-wide impacts
46-
- Analyze integration points
47-
- Evaluate dependencies and coupling
48-
- Think about emergent behaviors
49-
50-
4. **Generate Multiple Solutions**
51-
- Brainstorm at least 3-5 different approaches
52-
- For each approach, consider:
53-
- Pros and cons
54-
- Implementation complexity
55-
- Resource requirements
56-
- Potential risks
57-
- Long-term implications
58-
- Include both conventional and creative solutions
59-
- Consider hybrid approaches
60-
61-
5. **Deep Dive Analysis**
62-
For the most promising solutions:
63-
- Create detailed implementation plans
64-
- Identify potential pitfalls and mitigation strategies
65-
- Consider phased approaches and MVPs
66-
- Analyze second and third-order effects
67-
- Think through failure modes and recovery
68-
69-
6. **Cross-Domain Thinking**
70-
- Draw parallels from other industries or domains
71-
- Apply design patterns from different contexts
72-
- Consider biological or natural system analogies
73-
- Look for innovative combinations of existing solutions
74-
75-
7. **Challenge and Refine**
76-
- Play devil's advocate with each solution
77-
- Identify weaknesses and blind spots
78-
- Consider "what if" scenarios
79-
- Stress-test assumptions
80-
- Look for unintended consequences
81-
82-
8. **Synthesize Insights**
83-
- Combine insights from all perspectives
84-
- Identify key decision factors
85-
- Highlight critical trade-offs
86-
- Summarize innovative discoveries
87-
- Present a nuanced view of the problem space
88-
89-
9. **Provide Structured Recommendations**
90-
Present findings in a clear structure:
91-
```
92-
## Problem Analysis
93-
- Core challenge
94-
- Key constraints
95-
- Critical success factors
96-
97-
## Solution Options
98-
### Option 1: [Name]
99-
- Description
100-
- Pros/Cons
101-
- Implementation approach
102-
- Risk assessment
103-
104-
### Option 2: [Name]
105-
[Similar structure]
106-
107-
## Recommendation
108-
- Recommended approach
109-
- Rationale
110-
- Implementation roadmap
111-
- Success metrics
112-
- Risk mitigation plan
113-
114-
## Alternative Perspectives
115-
- Contrarian view
116-
- Future considerations
117-
- Areas for further research
118-
```
119-
120-
10. **Meta-Analysis**
121-
- Reflect on the thinking process itself
122-
- Identify areas of uncertainty
123-
- Acknowledge biases or limitations
124-
- Suggest additional expertise needed
125-
- Provide confidence levels for recommendations
12+
Analyze the problem or question provided: **$ARGUMENTS**
13+
14+
Before proceeding, identify: the core challenge, key constraints, implicit assumptions, and who is affected by the outcome.
15+
16+
**Before beginning analysis**, check whether $ARGUMENTS provides enough context:
17+
- If the problem is specific and the domain is clear, proceed immediately to analysis.
18+
- If critical context is missing (e.g., the domain, the constraints, or the decision-maker's goals), ask up to three targeted questions before proceeding. Do not ask unnecessary questions.
19+
20+
## Required Analysis Elements
21+
22+
Your analysis must address all of the following. Order and depth are yours to determine based on the problem:
23+
24+
- **Problem framing**: What is actually being asked? What assumptions are embedded in the question?
25+
- **Competing solutions**: At least 3 meaningfully different approaches, not variations of the same idea.
26+
- **Multi-lens evaluation**: Assess each solution across the lenses most relevant to this problem (technical, economic, human, systemic, temporal — select and justify which apply).
27+
- **Adversarial testing**: For each leading solution, argue against it. What would have to be true for it to fail badly? Use inversion — ask what you would do to guarantee failure, then ensure the recommendation avoids those paths.
28+
- **Cross-domain insight**: Draw at least one non-obvious parallel from a different field or discipline.
29+
- **Second-order effects**: What does each approach make more or less likely to happen in 6 months, 2 years, 10 years?
30+
- **Synthesis**: Which approach or combination is recommended? Why, given the specific trade-offs?
31+
- **Confidence calibration**: For each key claim, note where uncertainty is high and what would change the recommendation.
32+
33+
## Structured Output Template
34+
35+
Present findings using this structure:
36+
37+
```
38+
## Problem Analysis
39+
- Core challenge
40+
- Key constraints
41+
- Critical success factors
42+
43+
## Solution Options
44+
### Option 1: [Name]
45+
- Description
46+
- Pros/Cons
47+
- Implementation approach
48+
- Risk assessment
49+
50+
### Option 2: [Name]
51+
[Similar structure]
52+
53+
## Recommendation
54+
- Recommended approach
55+
- Rationale
56+
- Implementation roadmap
57+
- Success metrics
58+
- Risk mitigation plan
59+
60+
## Alternative Perspectives
61+
- Contrarian view
62+
- Future considerations
63+
- Areas for further research
64+
```
65+
66+
## Output Expectations
67+
68+
- Every solution option is evaluated on its own merits, not just compared relatively.
69+
- Reasoning chains are explicit — conclusions reference the evidence or logic that produced them.
70+
- Uncertainty is surfaced, not hidden. If data is insufficient, say so and specify what would resolve it.
71+
- The recommendation section is actionable: next steps are specific enough to begin on immediately.
72+
- Length matches problem complexity. Avoid padding.
12673

12774
## Usage Examples
12875

@@ -140,19 +87,4 @@ Deep analysis and problem solving mode
14087
/ultra-think How can we improve our API to be more developer-friendly while maintaining backward compatibility?
14188
```
14289
143-
## Key Principles
144-
145-
- **First Principles Thinking**: Break down to fundamental truths
146-
- **Systems Thinking**: Consider interconnections and feedback loops
147-
- **Probabilistic Thinking**: Work with uncertainties and ranges
148-
- **Inversion**: Consider what to avoid, not just what to do
149-
- **Second-Order Thinking**: Consider consequences of consequences
150-
151-
## Output Expectations
152-
153-
- Comprehensive analysis (typically 2-4 pages of insights)
154-
- Multiple viable solutions with trade-offs
155-
- Clear reasoning chains
156-
- Acknowledgment of uncertainties
157-
- Actionable recommendations
158-
- Novel insights or perspectives
90+
> **Tip**: For the hardest decisions, enable extended thinking in your Claude Code settings. This command's structured analysis pairs with Claude's native reasoning capabilities for deeper results.

0 commit comments

Comments
 (0)