workflow-orchestration-patterns

Design Temporal workflow orchestration with activities, compensations, and retries.

Updated May 16, 2026

Search Tags:#workflow #orchestration #distributed-systems #idempotency #saga #temporal #retry

Ready to run

npx skills add https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory --skill workflow-orchestration-patterns-p-o-ke-nae

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workflow-orchestration-patterns
Source: https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory/tree/main/.github/skills/workflow-orchestration-patterns
Command: npx skills add https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory --skill workflow-orchestration-patterns-p-o-ke-nae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you design reliable Temporal workflows that coordinate distributed work without losing progress, violating determinism, or mishandling failures.

Core Features & Use Cases

Workflow vs. activity separation: Keep orchestration logic in workflows and external calls in activities.
Resilience patterns: Apply saga compensation, retries, heartbeats, and idempotency for failure-safe execution.
Common use cases: Model multi-step business processes, entity lifecycles, parallel fan-out/fan-in jobs, and async approval flows.

Quick Start

Use the workflow-orchestration-patterns skill to outline a Temporal workflow for a long-running distributed process with activities, compensations, and retry rules.

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 a Temporal workflow for a long-running distributed process?▼

To design a Temporal workflow for a long-running distributed process, separate orchestration logic into workflows and external calls into activities. This enforces deterministic execution and automatic state recovery for reliable multi-step coordination.

What's the best way to handle saga compensation flows in distributed systems?▼

Saga compensation flows in distributed systems are handled by defining rollback activities for each step in a Temporal workflow. This ensures failure-safe execution by automatically reversing completed operations when a downstream process fails.

How do I implement idempotency and retries for external calls in Temporal workflows?▼

Idempotency and retries for external calls in Temporal workflows are implemented by isolating side effects in activities. You configure retry policies on activities to automatically handle transient failures while ensuring operations remain idempotent.

When do I need workflow orchestration for distributed processes?▼

Workflow orchestration for distributed processes is needed when coordinating multi-step business processes, parallel fan-out/fan-in jobs, or human-in-the-loop callbacks. It prevents losing progress and ensures state consistency across long-running operations.

Can I use Temporal workflows for parallel fan-out and fan-in jobs?▼

Temporal workflows support parallel fan-out and fan-in jobs by dispatching multiple activities concurrently and waiting for their completion. This pattern allows efficient distributed processing while maintaining automatic state recovery.

Why does my Temporal workflow lose state during long-running executions?▼

Temporal workflows lose state during long-running executions if external calls are placed directly in workflow logic instead of activities. Moving non-deterministic operations into activities enforces determinism and enables automatic state recovery.