U

Ultra Think Command

Activates deep analysis mode that forces extended chain-of-thought reasoning before producing any output. Use for complex architectural decisions, debugging tricky issues, or designing systems where getting it right matters more than speed.

CommandCommunitydevelopmentv1.0.0MIT
0 views0 copies

Command

/ultra-think

Description

Engages Claude in a structured, extended reasoning process before answering. Instead of jumping to a solution, Claude systematically explores the problem space, considers alternatives, identifies risks, and only then produces a well-reasoned response. Best used for complex decisions where a wrong answer is costly.

Behavior

When invoked with a problem statement, Claude follows this reasoning framework:

Phase 1: Problem Decomposition

  • Restate the problem in precise terms
  • Identify what is known, unknown, and assumed
  • Break the problem into sub-problems
  • Determine the evaluation criteria for a good solution

Phase 2: Solution Exploration

  • Generate at least 3 distinct approaches
  • For each approach, analyze:
    • Pros -- What makes this approach strong?
    • Cons -- What are the risks and downsides?
    • Complexity -- Implementation effort and maintenance burden
    • Precedent -- Where has this approach worked/failed before?

Phase 3: Deep Analysis

  • Stress-test the top approach against edge cases
  • Consider failure modes and recovery strategies
  • Identify hidden dependencies and assumptions
  • Check for second-order effects

Phase 4: Recommendation

  • Present the recommended approach with full justification
  • Include an implementation plan with ordered steps
  • List key risks and mitigations
  • Define success metrics

Output Format

# Deep Analysis: [Problem Statement] ## Problem Decomposition [Structured breakdown] ## Approaches Considered ### Approach A: [Name] | Dimension | Assessment | |-----------|------------| | Pros | ... | | Cons | ... | | Complexity | Low/Medium/High | | Risk | Low/Medium/High | ### Approach B: [Name] [Same structure] ### Approach C: [Name] [Same structure] ## Recommendation: [Chosen Approach] **Why this approach:** [Justification] ### Implementation Plan 1. [Step 1] 2. [Step 2] ... ### Risks & Mitigations | Risk | Likelihood | Impact | Mitigation | |------|-----------|--------|------------| | ... | ... | ... | ... | ### Success Metrics - [Metric 1]: [Target] - [Metric 2]: [Target]

Examples

/ultra-think Should we migrate our REST API to GraphQL?
/ultra-think How should we handle multi-tenancy in our SaaS database?
/ultra-think What's the best caching strategy for our product catalog?
/ultra-think Evaluate monorepo vs polyrepo for our 5-team organization
Community

Reviews

Write a review

No reviews yet. Be the first to review this template!

Similar Templates