sagas-garcia-molina-salem-1987

Define compensating actions and save-points for long-running transactional workflows.

2|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/curiositech/port-daddy --skill sagas-garcia-molina-salem-1987
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sagas-garcia-molina-salem-1987
Source: https://github.com/curiositech/port-daddy/tree/main/skills/sagas-garcia-molina-salem-1987
Command: npx skills add https://github.com/curiositech/port-daddy --skill sagas-garcia-molina-salem-1987

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents multi-step agent and distributed workflows from leaving systems in inconsistent partial states by providing a compensation-based pattern and recovery taxonomy. It addresses the core risk of long-lived operations: resource blocking, irrecoverable side effects, and the exponential increase in deadlock and failure exposure as task scope grows.

Core Features & Use Cases

  • Compensation design: How to specify compensating actions for each step so partial executions can be semantically undone.
  • Recovery policies: Decision frameworks for forward (checkpoint-and-retry), backward (compensate), and mixed recovery, plus save-point placement guidelines.
  • State and schema guidance: "Funds in transit" principle — externalize intermediate state so workflows are observable, recoverable, and auditable.
  • Orchestration pattern: Saga daemon pattern and instrumentation rules for wrapping skills so orchestration can drive recovery without native support from underlying systems.
  • Use cases: Agent orchestration, multi-step payments and reservations, staged code integration, large-data transformations, and scheduled batch jobs that must be resilient to crashes.

Quick Start

Ask the assistant to decompose your multi-step task into discrete saga steps, list a compensating action for each step, and recommend save-points and in-transit state representations.

Frequently Asked Questions about sagas-garcia-molina-salem-1987

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

FAQPage Schema
How do I handle distributed transaction recovery for long-running workflows?

Distributed transaction recovery for long-running workflows uses a compensation-based pattern with checkpointing save-points and externalized in-transit state, enabling both backward recovery through compensating actions and forward recovery through retries to maintain semantic consistency.

What is the best way to design compensation for multi-step agent orchestration?

Designing compensation for multi-step agent orchestration involves decomposing tasks into discrete saga steps and specifying a compensating action for each step, ensuring partial executions can be semantically undone without leaving external systems in inconsistent states.

Why does long-running workflow execution leave systems in inconsistent partial states?

Long-running workflow execution leaves inconsistent partial states because resource blocking, irrecoverable side effects, and deadlock exposure increase exponentially as task scope grows, making partial execution visible to other processes without compensation handling or save-point placement.

How do I externalize in-transit state for distributed workflow observability?

Externalize in-transit state for distributed workflow observability by applying the funds-in-transit principle, which surfaces intermediate state externally so workflows become observable, recoverable, and auditable by other processes during partial execution.

When should I use backward recovery vs forward recovery in distributed systems?

Use backward recovery with compensating actions when partial side effects must be semantically undone, and use forward recovery with checkpoint-and-retry when transient failures occur; mixed recovery combines both approaches based on save-point placement guidelines.

Can I use the saga pattern for scheduled batch jobs without native recovery support?

Yes, the saga daemon pattern wraps underlying systems with instrumentation rules to orchestrate recovery without native support, enabling scheduled batch jobs and large-data transformations to remain resilient to crashes through externalized state and compensation.