domains / families / software-engineering / saga-orchestration

saga-orchestration

combined

Implement saga patterns for distributed transactions and cross-aggregate workflows. Use when coordinating multi-step business processes, handling compensating transactions, or managing long-running workflows. Patterns for managing distributed transactions and long-running business processes.

When to use

• Coordinating multi-service transactions
• Implementing compensating transactions
• Managing long-running business workflows
• Handling failures in distributed systems
• Building order fulfillment processes
• Implementing approval workflows

When not to use

• The task is unrelated to saga orchestration
• You need a different domain or tool outside this scope
• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The first copy (rmyndharis) contains the actual implementation procedure, including a Python base class for a Saga Orchestrator, state definitions, and step execution logic. The second copy (sickn33) is a wrapper that explicitly defers to an external 'detailed-guide.md' file and adds safety/risk constraints ('risk: critical', 'Limitations') that are absent from the first copy. Because the second copy contains mandatory safety constraints and a reference to a guide that the first copy lacks, and the first copy contains the concrete code that the second copy omits, crowning one would hide either the implementation or the safety protocol. They overlap in scope but each has material steps/constraints the others lack.