workflow-orchestration-patterns

Orchestrate durable distributed system workflows with Temporal.

Updated May 1, 2026
One-click install
npx skills add https://github.com/jcarrenogallego/kogi-kids --skill workflow-orchestration-patterns-jcarrenogallego
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-orchestration-patterns
Source: https://github.com/jcarrenogallego/kogi-kids/tree/main/.junie/skills/workflow-orchestration-patterns
Command: npx skills add https://github.com/jcarrenogallego/kogi-kids --skill workflow-orchestration-patterns-jcarrenogallego

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides solutions for designing and orchestrating durable workflows for distributed systems, helping users manage long-running processes, distributed transactions, and microservice orchestration.

Core Features & Use Cases

  • Design Durable Workflows: Offers a framework for creating workflows using Temporal, addressing challenges like state management and determinism.
  • Critical Design Decisions: Discusses the distinction between workflows and activities, ensuring users understand the architecture for their systems.
  • Core Workflow Patterns: Covers essential patterns like Saga Pattern, Entity Workflows, and Fan-Out/Fan-In for parallel execution.

Quick Start

Execute a workflow orchestration pattern using Temporal's features.

Frequently Asked Questions about workflow-orchestration-patterns

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

FAQPage Schema
What is the Saga pattern for distributed transactions in microservices?

The Saga pattern manages distributed transactions by orchestrating multi-step processes across microservices, coordinating compensating actions to maintain consistency if a workflow step fails.

How do I orchestrate long-running workflows with automatic state persistence?

Orchestrate long-running workflows using Temporal to automatically persist execution state, ensuring distributed processes recover seamlessly from failures without manual state tracking.

Does Temporal support Fan-Out/Fan-In patterns for parallel microservice execution?

Temporal supports Fan-Out/Fan-In patterns for parallel execution, allowing distributed systems to dispatch multiple concurrent activities and aggregate their results within a single durable workflow.

When do I need durable workflows for distributed systems?

Durable workflows are needed for distributed systems requiring resilience, error handling, and idempotency in long-running processes or complex multi-step microservice orchestration.

How do I distinguish between workflows and activities in Temporal?

Workflows define deterministic state and orchestration logic, while activities handle external side effects; separating them ensures state management remains robust during distributed execution.