Orchestrate cross-frame Saga workflows with step compensation and sub-agent execution.
npx skills add https://github.com/knowlet/skills --skill saga-orchestrator
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
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.
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.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
knowletAnalyze requirements or Event Storming outputs to generate Problem Frame YAML specifications.
DbillionaerDesigns blueprints for event-sourced systems with a focus on architectural workflows and implementation details.
tomsiwikImplement Effect-TS patterns for scheduling periodic tasks and managing event streams.
DVNghiemCoordinate distributed transactions with saga patterns and compensating actions.
