retry-policy

Define retry policies with exponential backoff and circuit breakers for .NET applications.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/yeeehaooo/WorkSpace --skill retry-policy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retry-policy
Source: https://github.com/yeeehaooo/WorkSpace/tree/main/skills/dotnet/patterns/retry-policy
Command: npx skills add https://github.com/yeeehaooo/WorkSpace --skill retry-policy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Define explicit retry policies for handling transient failures in external dependencies.

Core Features & Use Cases

  • Provide deterministic retry behavior for transient faults in external services.
  • Support exponential backoff and circuit breaker integration to prevent retry storms.
  • Clarify separation of concerns: policy interfaces in the Application layer and implementations in the Infrastructure layer.

Quick Start

Implement an ExponentialBackoffRetryPolicy and use it to wrap external API calls.

Frequently Asked Questions about retry-policy

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

FAQPage Schema
How do I handle transient failures in .NET external service calls?

Handle transient failures in .NET by wrapping external service calls with explicit retry policies. This enforces deterministic retry behavior and applies exponential backoff to prevent retry storms when external dependencies experience temporary faults.

What is the best way to implement exponential backoff and circuit breakers in .NET?

Exponential backoff and circuit breakers in .NET are implemented by defining policy interfaces in the Application layer and concrete implementations in the Infrastructure layer. This clarifies separation of concerns while controlling retry timing and circuit breaking logic.

Where should I define retry policy interfaces in a typical .NET architecture?

Define retry policy interfaces in the Application layer of your .NET architecture. Place the concrete implementations that control backoff timing and observability in the Infrastructure layer to maintain clear separation of concerns.

How do I prevent retry storms when external dependencies fail?

Prevent retry storms by integrating circuit breakers and exponential backoff into your retry policies. This stops deterministic retry behavior from overwhelming recovering external dependencies during transient failure periods.

Can I use this retry policy to wrap external API calls in .NET applications?

Yes, you can wrap external API calls in .NET applications by implementing an ExponentialBackoffRetryPolicy. This applies deterministic retry logic to external service calls and handles transient faults across architectural layers.

Does this retry policy approach support observability across .NET architectural layers?

Yes, the retry policy approach supports observability across .NET architectural layers. The concrete implementations in the Infrastructure layer provide control over retry logic, backoff timing, and observability for external dependency calls.