ultrathink-orchestrator

# Ultrathink Orchestrator Skill

## Purpose

This skill provides automatic orchestration for development and investigation tasks. It detects the task type from keywords and delegates to the appropriate workflow skill (investigation-workflow or default-workflow).

Auto-activation priority is LOW (5) to allow more specific skills to match first. When activated, this orchestrator selects between investigation-workflow and default-workflow based on the user's request keywords.

This skill acts as a thin wrapper around the canonical ultrathink command, following the amplihack pattern of single-source-of-truth for command logic.

## Canonical Sources

**This skill is a thin wrapper that references canonical sources:**

- **Primary Command**: `.claude/commands/amplihack/ultrathink.md` (278 lines)
- **Workflow Sources**:
  - Development: `.claude/workflow/DEFAULT_WORKFLOW.md`
  - Investigation: `.claude/workflow/INVESTIGATION_WORKFLOW.md`

The canonical command contains complete task detection logic, complexity estimation, and orchestration patterns for both investigation and development workflows.

## ⛔ MANDATORY EXECUTION PROCESS (5 Steps)

When this skill is activated, you MUST follow this exact 5-step process:

### Step 1: Read Canonical Command (MANDATORY)
```
Read(file_path=".claude/commands/amplihack/ultrathink.md")
```
**Validation Checkpoint**: Confirm ultrathink.md content is loaded before proceeding.

### Step 2: Detect Task Type (MANDATORY)
Analyze user request using keywords from canonical command:
- **Q&A keywords**: what is, explain briefly, quick question, how do I run, simple question
- **Investigation keywords**: investigate, explain, understand, analyze, research, explore
- **Development keywords**: implement, build, create, add feature, fix, refactor, deploy
- **Hybrid tasks**: Both investigation and development keywords present

**Validation Checkpoint**: Task type must be determined (Q&A, Investigation, Development, or Hybrid).

### Step 3: Invoke Work