What problem does it solve?
Confidence-based escalation prevents an AI agent from repeatedly failing at the same task level by moving to a more capable tier when clear failure signals appear.
Core Features & Use Cases
- Escalation Tiers: Defines a Haiku → Sonnet → Opus workflow with a one-attempt-per-tier rule to avoid skipping directly to the highest tier.
- Never Skip Tiers Rule: Forces progression Haiku → Sonnet → Opus (unless the task is explicitly known to require Opus).
- Signal-Driven Escalation: Triggers escalation on test failures, irreconcilable lint warnings, wrong output schemas, repeated tech-lead blocks, timeouts, and repeated enforcement-hook blocks.
- Clear Non-Escalation Conditions: Avoids escalation for size-only problems, missing context (instead add instructions), and infrastructure errors (retry).
- Escalation Protocol & Tracking: Provides a decision workflow and instructs logging escalations to claude-mem for routing optimization.
Quick Start
In your agent run, follow the escalation signals to move the task from Haiku to Sonnet or Opus after a failed attempt that matches one of the defined criteria, while logging the reason for future routing improvements.