resilience-engineering

Design software systems to preserve essential functions during partial failures and recovery events.

2|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/NlightNFotis/skills --skill resilience-engineering-nlightnfotis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resilience-engineering
Source: https://github.com/NlightNFotis/skills/tree/main/resilience-engineering
Command: npx skills add https://github.com/NlightNFotis/skills --skill resilience-engineering-nlightnfotis

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about resilience-engineering

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

FAQPage Schema
How do I design graceful degradation to prevent cascading outages during partial system failure?

Graceful degradation prevents cascading outages by defining essential user-facing functions and applying boundary-specific failure stances like circuit breakers, bulkheads, and fallbacks to contain partial failures.

What is the best way to harden retry and timeout behavior for a critical API path?

Harden retry and timeout behavior by mapping dependency boundaries, designing backpressure and load shedding mechanisms, and validating recovery paths to ensure critical API paths remain operational during overload.

How do I define safe brownout modes for user-facing features experiencing peak load?

Safe brownout modes require defining the essential function that must survive, inventorying stressors, and applying load shedding and fallbacks to degrade non-essential features gracefully during peak load.

When do I need resilience engineering for reviewing a new external API dependency before launch?

You need resilience engineering when launching external API dependencies to design timeout and retry boundaries, establish observability for degraded states, and prevent all-or-nothing outages from dependency failures.

What observability signals distinguish degraded service from total downtime during an incident?

Observability for degraded states maps how operators intervene and identifies specific signals that distinguish partial functionality from total downtime, ensuring validated recovery mechanisms like brownout modes are tracked.