saga-orchestrator

Orchestrate cross-frame Saga workflows with step compensation and sub-agent execution.

2|Updated Dec 24, 2025

Search Tags:#workflow #orchestration #event-driven #saga

Ready to run

npx skills add https://github.com/knowlet/skills --skill saga-orchestrator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: saga-orchestrator
Source: https://github.com/knowlet/skills/tree/main/skills/saga-orchestrator
Command: npx skills add https://github.com/knowlet/skills --skill saga-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates long-running, multi-step business processes that span multiple frames (CBF, RIF, IDF) using Saga/Choreography patterns to ensure eventual consistency and recoverability.

Core Features & Use Cases

Saga step orchestration: coordinate multiple sub-agents across frames.
Compensation & retries: define step-level compensations and retry strategies.
Cross-frame workflow design: layout multi-step processes with events.

Quick Start

Provide a docs/specs/{saga-name}.yaml to define steps; then invoke saga-orchestrator to run the steps in order and handle compensations if failures occur.

Frequently Asked Questions about saga-orchestrator

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

FAQPage Schema

How do I orchestrate workflows that span multiple frame types?▼

Saga orchestration coordinates cross-frame workflows by decomposing complex business processes into sequenced steps across different Frame types (CBF, RIF, IDF), with compensation logic and error recovery to maintain eventual consistency.

What is the Saga/Choreography pattern and when should I use it?▼

Saga/Choreography is a distributed transaction pattern that breaks long-running processes into coordinated steps with compensations. Use it for multi-step workflows spanning multiple systems where traditional transactions aren't feasible and eventual consistency is acceptable.

How do I define steps and compensation logic for event-driven workflows?▼

Define steps and compensations in a YAML specification file (docs/specs/{saga-name}.yaml) that sequences tasks, specifies compensation actions for each step, and configures retry strategies, then invoke the orchestrator to execute and handle failures.

Can I coordinate sub-agents across different workflow frames?▼

Yes, saga orchestration enables coordinated sub-agent execution across multiple Frame types via runSubagent delegation, allowing you to decompose workflows into steps that execute across CBF, RIF, and IDF frames with centralized error recovery.

What happens if a step fails in a multi-step workflow?▼

When a step fails, the orchestrator triggers compensation logic defined for that step to roll back partial state, then applies retry strategies or halts execution based on your configuration, maintaining recoverability for long-running processes.

Do I need existing sub-agents to use workflow orchestration?▼

Yes, saga orchestration requires pre-existing sub-agents to delegate tasks to; it coordinates their execution across frames rather than creating agents, so you must have agent implementations for each workflow step.