idempotency-retry-design

FoundationJIT only

analysis-agent/task-agent/review-agent: use when retries, idempotency, deduplication, timeout, or replay safety affects side effects; skip when operations cannot repeat.

Group: Backend engineering
Supported roles: MainAnalysisTaskReview
Source: SKILL.md

Use when

Trigger signals that make this skill the right owner

design idempotency keys retries backoff deduplication and replay safety

Do not use when

Anti-triggers — as binding as the triggers above

no task-local idempotency retry design decision is required

Required inputs

What must be supplied before this skill can decide anything

current task contract
selected primary Professional Skill
task-local trigger evidence

Output contract

What this skill owes the next role

operation identity and retry contract with record/effect coordination, crash boundaries, concurrent states, unknown and late replay behavior, aggregate budget, and owned terminal resolution

Escalation signals

When this skill must hand the decision back

Unsafe retries cause duplicate writes or permanent partial failure

Loaded by

This skill never owns a task. These professionals may pull it in as Layer 3.

Targeted references

Each reference carries its own load condition. None of them enter context by default.

Reference	Load when	Do not load when	Required by
checklist.mddecision-checklist	Concurrency crash windows retention replay or terminal ownership spans multiple boundaries.	Root rules resolve one bounded repeat path without cross-boundary crash late-replay or terminal ambiguity.	AnalysisTaskReview
evidence-patterns.mdevidence-pattern	Duplicate safety unknown outcome isolation recovery or terminal-resolution claims need fresh proof.	No replay-safety isolation recovery or terminal-resolution claim awaits validation.	AnalysisTaskReview
industry-benchmarks.mdbenchmark-pattern	Competing identity coordination retry or late-replay patterns remain viable.	Current operation and authority evidence determine one safe pattern.	AnalysisTaskReview