ultrathink_core

Guides deep analysis of complex problems through hypothesis generation and critical evaluation.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/jvsandhu/agentic-skills --skill ultrathink-core-jvsandhu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ultrathink_core
Source: https://github.com/jvsandhu/agentic-skills/tree/main/skills/ultrathink_core
Command: npx skills add https://github.com/jvsandhu/agentic-skills --skill ultrathink-core-jvsandhu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Complex architectural decisions, performance bottlenecks, and system design questions often get shallow, first-answer treatment. This Skill enforces a structured deep-thinking protocol so the agent decomposes problems, generates multiple hypotheses, and critically evaluates them before acting. ## Core Features & Use Cases - Phased Deep Analysis: A three-phase workflow covering problem decomposition, multi-hypothesis generation with mental simulation, and rubric-based decision making. - Calibrated Depth Levels: Four depth tiers (Light, Medium, Deep, Ultra) match analysis effort to problem complexity, with explicit guidance on when NOT to use deep thinking. - Structured Reasoning Artifacts: Provides a Knowledge Map template (knowns, unknowns, assumptions) and an XML-based AoT tag structure (thinking, plan, reflection) for auditable reasoning. - Use Case: When deciding between a monolith and microservices architecture, the agent maps dependencies, generates three candidate approaches, stress-tests each against edge cases, and selects one using performance, risk, and sustainability criteria. ## Quick Start Analyze whether we should migrate our monolithic app to microservices using the deep analysis protocol with hypothesis generation and risk evaluation.

Frequently Asked Questions about ultrathink_core

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

FAQPage Schema
How do I structure deep analysis for a complex technical decision?

Use a three-phase workflow: decompose the problem into atomic parts with dependency mapping, generate at least three hypotheses and simulate their edge-case behavior, then select the best option using performance, risk, and sustainability criteria.

When should I use deep analysis versus quick execution?

Use deep analysis for architectural decisions, system-wide changes, and complex bugs like race conditions. Skip it for simple bug fixes, single-file changes, or tasks solvable in five minutes, where overthinking wastes time.

What is the AoT tag structure for AI reasoning?

AoT uses XML tags to separate reasoning stages: a thinking tag for hypothesis exploration without code, a plan tag for numbered steps, and a reflection tag for critiquing the plan and analyzing risks.

How do I avoid analysis paralysis on engineering tasks?

Calibrate depth to complexity using defined levels: Light (3-5 steps) for simple decisions up to Ultra (50+ steps) for critical architecture. Checkpoint questions verify you have not fallen into the overthink trap.

Can deep analysis protocols help debug race conditions?

Yes. Race conditions are a listed use case: the protocol maps dependencies between components, generates competing hypotheses about the failure cause, and mentally simulates each against edge cases before proposing fixes.