resilience-and-fault-tolerance

Design resilient systems with timeouts, retries, circuit breakers, and bulkheads.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/Tiepbm/software-engineering-agent --skill resilience-and-fault-tolerance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resilience-and-fault-tolerance
Source: https://github.com/Tiepbm/software-engineering-agent/tree/main/skills/resilience-and-fault-tolerance
Command: npx skills add https://github.com/Tiepbm/software-engineering-agent --skill resilience-and-fault-tolerance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designs resilient systems with timeouts, retries, backoff, circuit breakers, bulkheads, graceful degradation, failover, and failure containment.

Core Features & Use Cases

  • Guidance for defining timeout budgets, retry strategies, circuit breaker behavior, and bulkheads.
  • Practical patterns for graceful degradation, failover, and containment in regulated environments.
  • Architecture-level guidance for high-value workflows such as payments, claims processing, onboarding, and data ingestion.

Quick Start

Define timeout budgets, configure bounded retries with jitter, and implement circuit breakers for all external dependencies to ensure graceful degradation.

Frequently Asked Questions about resilience-and-fault-tolerance

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

FAQPage Schema
How do I implement circuit breakers and bulkheads for critical workflows like payments processing?

Implement circuit breakers and bulkheads for payments processing to isolate external dependency failures and prevent cascading system collapse. This Skill provides architecture-level guidance for configuring bulkhead isolation and circuit-breaker behavior in regulated environments.

What is the best way to define timeout budgets and retry strategies for data ingestion?

Define timeout budgets for data ingestion by mapping end-to-end latency limits to individual service calls. This Skill guides configuring bounded retries with jitter and idempotent retry strategies to ensure reliable runtime without overwhelming downstream systems.

How does graceful degradation work when handling onboarding and claims processing failures?

Graceful degradation works by maintaining partial system functionality during partial failures in onboarding and claims processing. This Skill provides practical patterns for defining degradation modes, failover mechanisms, and failure containment strategies.

Can I use this guidance for architecture and platform teams handling critical workflows?

Yes, this guidance applies directly to architecture, platform, and development teams handling critical workflows. It satisfies requirements for timeout budgets, circuit-breaker behavior, bulkhead isolation, observability, runbooks, and recovery procedures.

When do I need to configure backoff and failure containment for external dependencies?

Configure backoff and failure containment for external dependencies when high-value workflows face intermittent failures or network instability. This Skill helps define bounded retries with jitter and containment patterns to protect system reliability.