What problem does it solve?
This Skill helps you design and review software systems so they keep delivering their essential function during overload, dependency failures, bad data, operator mistakes, and other stressful conditions. It prevents all-or-nothing outages by turning vague reliability goals into concrete degradation, containment, and recovery decisions.
Core Features & Use Cases
- Essential Function Framing: Defines the one thing that must keep working so resilience work stays focused on user-critical behavior.
- Failure Pattern Design: Guides decisions for timeouts, retries, circuit breakers, bulkheads, backpressure, load shedding, brownouts, and fallbacks at specific boundaries.
- Recovery and Observability Planning: Maps how degraded systems recover, how operators intervene, and which signals distinguish degraded service from total downtime.
- Use Cases: Review a new external API dependency before launch, redesign a system after a cascading outage, harden retry and timeout behavior for a critical path, or define safe brownout modes for user-facing features during peak load.
Quick Start
Use the resilience-engineering skill to review a critical user flow, name its essential function, identify likely stressors, and design graceful degradation and recovery paths.