Back to catalog / Developer tools
Saga orchestration: model cross-service transactions as recoverable state machines
Make steps, deadlines, idempotency, and compensation explicit for long-running workflows.
Skills
Identify participants, commands, success events, and irreversible side effects. Persist each step’s state, deadline, transient/permanent failure classification, and bounded retries. Give compensation actions their own idempotency keys and document effects that cannot be reversed. Choose orchestration or choreography and handle out-of-order/duplicate messages, timeout detection, dead-letter queues, and manual recovery. Test partial failures and prove redelivery cannot double-charge or double-reserve. Before rollout, present the side-effect inventory and rollback boundary.
Permissions
Prerequisites
- For long-running cross-service transactions where shared database transactions are unavailable.
- Provide service boundaries, step effects, timeout/retry policies, and consistency requirements.
Permissions
- May write saga coordinators, message handlers, persisted state, and compensation logic.
- Compensation triggers a separate business action; make retries and message replays idempotent and review their external effects.
Limitations
Define per-step deadlines, transient/permanent failures, DLQ, and manual recovery; review each compensation for idempotency.
Pinned upstream source
- Repository
- wshobson/agents
- File path
- plugins/backend-development/skills/saga-orchestration/SKILL.md
- Pinned commit
46891e7e60da0e52baf1050b7b6391b64e84c6d9- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: MIT
Compatible tools
Saga state machine · Message broker · Compensation handlers
Main topic
Take a coding Agent change from context to verification