ultrathink

Enforce question-driven deep planning for complex features and epics.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor --skill ultrathink-sjdjdiejdrirhdkjej
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ultrathink
Source: https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor/tree/main/.claude/skills/ultrathink
Command: npx skills add https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor --skill ultrathink-sjdjdiejdrirhdkjej

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ultrathink addresses the risk of shallow planning by enforcing a rigorous, question-driven deep planning process that reveals uncertainties and reduces rework.

Core Features & Use Cases

  • Assumption inventory and rigorous questioning to surface hidden risks.
  • Codebase soul analysis to extract guiding patterns and design principles.
  • Ruthless simplification to architect minimal viable designs for complex features or epics.
  • Use Case: Applied to multi-sprint initiatives or features with 30+ tasks, or when planning is auto-enabled.

Quick Start

To activate ultrathink, run the deep planning workflow with the --deep flag or trigger ultrathink through epic features, then perform the three steps: think differently, obsess over details, and plan like Da Vinci. This will generate an assumptions inventory, document codebase insights, and produce a simplified architecture plan.

Frequently Asked Questions about ultrathink

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce deep planning for complex software architecture?

Deep planning for complex software architecture is enforced by activating a rigorous, question-driven exploration to reveal uncertainties and minimize rework. You trigger this by enabling the deep planning workflow or setting planning.auto_deep_mode.

When do I need to perform an assumption inventory for my codebase?

An assumption inventory is needed when planning complex features, multi-sprint epics, or architectures with 30+ tasks. It rigorously questions and surfaces hidden risks and uncertainties before you commit to a specific design.

What is the best way to simplify a complex feature architecture?

The best way to simplify a complex feature architecture is through ruthless simplification, which architects minimal viable designs. This process relies on extracting guiding patterns and design principles via a codebase soul analysis.

Can I use deep planning for smaller features or only multi-sprint epics?

Deep planning is designed for complex features, multi-sprint epics, and tasks totaling 30 or more. However, you can apply it to smaller features by manually triggering the deep planning mode via user preferences or workflow triggers.

Why does my software planning fail to account for hidden codebase patterns?

Software planning fails to account for hidden patterns when it skips a rigorous codebase soul analysis. Deep planning solves this by explicitly extracting guiding patterns and design principles before architectural design.