workflow-orchestration-patterns
Design Durable Temporal Workflows
Distributed workflows fail when orchestration, external calls, and retries are mixed without clear rules. This skill guides Claude, Codex, and Claude Code through Temporal patterns for durable workflows, sagas, callbacks, and deterministic state management.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "workflow-orchestration-patterns" from https://skillstore.io/skills/wshobson-workflow-orchestration-patterns.md and its manifest at https://skillstore.io/api/skills/wshobson-workflow-orchestration-patterns/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "workflow-orchestration-patterns". A checkout workflow reserves inventory, charges payment, and creates shipment.
Expected outcome:
- Workflow boundary: the workflow coordinates the order and tracks state.
- Activities: reserve inventory, charge payment, and create shipment because they touch external systems.
- Compensations: release inventory, refund payment, and cancel shipment in reverse order.
Using "workflow-orchestration-patterns". A user approval process waits two days for a manager response.
Expected outcome:
- Pattern: async callback with a workflow signal.
- The workflow sends the approval request and waits for a signal or timeout.
- Use an activity to send the request and classify invalid approvals as non-retryable.
Using "workflow-orchestration-patterns". A workflow processes one million records through external enrichment calls.
Expected outcome:
- Use bounded fan-out with child workflows instead of one oversized workflow.
- Put enrichment calls in activities with timeouts, retry limits, and heartbeats.
- Monitor pending workflow counts, activity failures, and retry backoff behavior.
Security Audit
SafeAll static findings are false positives from markdown fences or inline code examples in documentation. The skill provides Temporal architecture guidance and no evidence of command execution, system reconnaissance, prompt injection, or data exfiltration was found.
Risk Factors
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/wshobson-workflow-orchestration-patterns/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/wshobson-workflow-orchestration-patterns?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/wshobson-workflow-orchestration-patterns?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/wshobson-workflow-orchestration-patterns/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/wshobson-workflow-orchestration-patterns.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
wshobson. (2026). workflow-orchestration-patterns security audit report (audit version 7) [Author version unspecified]. Skillstore. https://skillstore.io/skills/wshobson-workflow-orchestration-patterns/audits/7BibTeX citation
@techreport{wshobson-wshobson-workflow-orchestration-patterns-2026,
author = {wshobson},
title = {workflow-orchestration-patterns security audit report (audit version 7)},
institution = {Skillstore},
year = {2026},
number = {7},
url = {https://skillstore.io/skills/wshobson-workflow-orchestration-patterns/audits/7},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "workflow-orchestration-patterns security audit report (audit version 7)"
version: "unspecified"
type: report
authors:
- name: "wshobson"
date-released: "2026-07-08"
url: "https://skillstore.io/skills/wshobson-workflow-orchestration-patterns/audits/7"
identifiers:
- type: other
value: "skillstore:wshobson-workflow-orchestration-patterns:audit:7"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
sickn33-workflow-orchestration-patterns
2026-08-21
wshobson-workflow-orchestration-patterns
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Plan a Payment Saga
Map payment, inventory, and fulfillment steps with compensation tasks before implementation.
Model Entity Lifecycles
Design long-lived workflows for carts, accounts, inventory, or approvals that receive signals and expose queries.
Review Temporal Reliability
Check workflow boundaries, idempotency, retries, timeouts, and replay safety before launch.
Try These Prompts
Use the workflow-orchestration-patterns skill. Classify these steps as Temporal workflows or activities, and explain each boundary: [paste process].
Use the workflow-orchestration-patterns skill. Create a saga plan for [business process]. Include forward steps, compensation steps, idempotency needs, and non-retryable errors.
Use the workflow-orchestration-patterns skill. Design a bounded fan-out and fan-in workflow for [task volume]. Include child workflows, retry policies, heartbeats, and monitoring signals.
Use the workflow-orchestration-patterns skill. Review this Temporal design for determinism, replay compatibility, versioning, activity boundaries, payload limits, and operational risks: [paste design].
Best Practices
- Keep orchestration in workflows and all external calls in activities.
- Register saga compensation before each forward step executes.
- Define activity timeouts, retry limits, heartbeats, and idempotency keys.
Avoid
- Calling external APIs, databases, file systems, or network services directly from workflow code.
- Using system time, random values, global state, or non-deterministic libraries in workflows.
- Letting activities retry forever without classifying permanent business errors.