Agent skill · product strategy · rmyndharis
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
Why this skill is useful
Provides specific design patterns and best practices for implementing durable workflows with Temporal that the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-02. 1,255 stars on the source repository.
What this skill does
Workflow Orchestration Patterns Master workflow orchestration architecture with Temporal, covering fundamental design decisions, resilience patterns, and best practices for building reliable distributed systems. Use this skill when Working on workflow orchestration patterns tasks or workflows Needing guidance, best practices, or checklists for workflow orchestration patterns Do not use this skill when The task is unrelated to workflow orchestration patterns You need a different domain or tool outside this scope Instructions Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes. Provide actionable steps and verification. When to Use Workflow Orchestration Ideal Use Cases (Source: docs.temporal.io) Multi-step processes spanning machines/services/databases Distributed transactions requiring all-or-nothing semantics Long-running workflows (hours to years) with automatic state persistence Failure recovery that must resume from last successful step Business processes: bookings, orders, campaigns, approvals Entity lifecycle management: inventory tracking, account management, cart workflows Infrastructure automation: CI/CD pipelines, provisioning, deployments Human-in-the-loop systems requiring timeouts and escalations When NOT to Use Simple CRUD operations (use direct API calls) Pure data processing pipelines (use Airflow, batch processing) Stateless request/response (use standard APIs) Real-time streaming (use Kafka, event processors) Critical Design Decision: Workflows vs Activities The Fundamental Rule (Source: temporal.io/blog/workflow-engine-principles): Workflows = Orchestration logic and decision-making Activities = External interactions (APIs, databases, network calls) Workflows (Orchestration) Characteristics: Contain business logic and coordination MUST be deterministic (same inputs → same outputs) Cannot perform direct external calls State automatically preserved across failures Can run for years despite infrastruct …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills rmyndharis/workflow-orchestration-patterns