What problem does it solve? When an agent hits a failure — a timeout, a build error, a missing tool — it often just reports the error and stops. This Skill gives every squad agent a shared playbook for adapting to failures instead of dead-ending, so tasks keep moving or escalate with useful context. ## Core Features & Use Cases - Five Recovery Patterns: Retry with Backoff, Fallback Alternatives, Diagnose-and-Fix, Escalate with Context, and Graceful Degradation, each with clear triggers and step-by-step procedures. - Failure-Type Selection Guide: A mapping table that pairs common failure types (network, build, auth, missing data) with primary and fallback recovery patterns. - Charter Integration: Guidance for embedding these patterns into each agent's charter under an Error Recovery section, tailored to that agent's domain. - Use Case: An agent's API call returns 429 Too Many Requests. Instead of failing the task, it retries with exponential backoff up to 3 times, then escalates to the coordinator with the exact errors and a root-cause hypothesis. ## Quick Start Apply the error-recovery patterns to handle any failure you encounter during this task, retrying transient errors and escalating with full context if recovery attempts are exhausted.
