workflow-orchestration-patterns

Design Temporal workflows with saga and async patterns for long-running processes.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/ekremmkasap/jarvis --skill workflow-orchestration-patterns-ekremmkasap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-orchestration-patterns
Source: https://github.com/ekremmkasap/jarvis/tree/main/server/agent_prompts/wshobson/plugins/backend-development/skills/workflow-orchestration-patterns
Command: npx skills add https://github.com/ekremmkasap/jarvis --skill workflow-orchestration-patterns-ekremmkasap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Temporal enables reliable design of long-running, distributed workflows by coordinating steps, state, and retries.

Core Features & Use Cases

  • Saga-pattern compensation for distributed transactions
  • Entity/workflow patterns for long-lived stateful processes
  • Async callbacks and parallel execution with reliable guarantees

Quick Start

Describe a Temporal-based workflow design using saga and async patterns for long-running business processes.

Frequently Asked Questions about workflow-orchestration-patterns

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

FAQPage Schema
How do I design Temporal workflows for long-running distributed processes?

To design Temporal workflows for long-running distributed processes, use this skill to outline robust architectures that coordinate steps, state, and retries with strict determinism for reliable business process execution.

What is the saga pattern and how does it handle workflow compensation?

The saga pattern handles workflow compensation by defining rollback actions for each step in a distributed transaction. This skill provides guidance to implement saga compensation, ensuring reliable failure recovery when long-running processes encounter errors.

How do I manage state persistence and retries in complex business orchestrations?

Manage state persistence and retries in complex business orchestrations by enforcing workflow determinism and applying the state management and retry guidance outlined by this skill for long-lived stateful processes.

When do I need deterministic workflows for multi-service orchestration?

You need deterministic workflows for multi-service orchestration when coordinating complex business processes like order processing or insurance claims that require strict reliability, state persistence, and automated failure recovery across distributed services.

Does this approach support async callbacks and parallel execution?

Yes, this workflow orchestration approach supports async callbacks and parallel execution with reliable guarantees, allowing you to coordinate long-running distributed processes efficiently while maintaining state persistence and failure recovery.

What are the best practices for versioning and safety in workflow design?

Best practices for workflow versioning and safety include enforcing determinism in workflows, applying proper state management, and following the safety practices outlined in this skill to prevent errors during long-running distributed process execution.