idempotency-retry-design

What problem does it solve?

This Skill prevents duplicate side effects caused by retries, timeouts, and at-least-once delivery by designing a strict idempotency and bounded retry contract.

Core Features & Use Cases

• Idempotency key design for write boundaries: Specify a key that combines operation identity and a payload hash, and define how to reject payload mismatches.
• Bounded retry policies: Enforce max attempts, total deadline, exponential backoff with full jitter, and a precise terminal state for permanent failures.
• Timeout and unknown-outcome recovery: Define reconciliation steps before retrying when the caller cannot distinguish “no response” from “no commit”.

Quick Start

Use the idempotency-retry-design skill to define how your payment capture, order creation, webhook delivery, and async consumers store idempotency keys, retry safely, and route failures to a dead-letter queue.