newmindsgroup Saga Orchestration
Patterns for managing distributed transactions and long-running business processes.
When to Use
- The request matches the skill description: Patterns for managing distributed transactions and long-running business processes.
- The task needs the implementation patterns, examples, validation checks, or edge cases listed in the topic map.
- The work would benefit from the complete guidance preserved in
references/full-guidance.md.
Core Workflow
- Confirm the request matches this skill's trigger, scope, and risk profile.
- Use the topic map to identify the relevant pattern, checklist, or example before writing detailed guidance or code.
- Load
references/full-guidance.mdwhen implementation details, examples, anti-patterns, validation checks, or edge cases are needed. - Apply only the relevant guidance instead of loading or repeating the entire reference by default.
- Verify the result against any validation checks, limitations, security notes, or platform constraints in the reference.
Topic Map
- Do not use this skill when
- Instructions
- Use this skill when
- Core Concepts
- Saga Types
- Saga Execution States
- Templates
- Template 1: Saga Orchestrator Base
- Template 2: Order Fulfillment Saga
- Template 3: Choreography-Based Saga
- Template 4: Saga with Timeouts
- Durable Execution Alternative
- Best Practices
- Do's
- Don'ts
- Related Skills
- Resources
Reference Map
references/full-guidance.mdpreserves the complete original guidance, including examples and detailed edge cases.
Limitations
- 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.
Progressive Loading
Keep this SKILL.md as the compact routing and workflow entrypoint. Load the reference file only when the user task requires the deeper implementation material.