skills.rest
myriosMin
myriosMinCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

migrating-to-workflow-sdk

Migrate legacy orchestration workflows from Temporal, Inngest, Trigger.dev, and AWS Step Functions to the Workflow SDK.

Updated Apr 24, 2026
Search Tags:#migration#orchestration#webhook#temporal#start#inngest#workflow-sdk
One-click install
npx skills add https://github.com/myriosMin/godiva --skill migrating-to-workflow-sdk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrating-to-workflow-sdk
Source: https://github.com/myriosMin/godiva/tree/main/claude-managed-agents/.agents/skills/migrating-to-workflow-sdk
Command: npx skills add https://github.com/myriosMin/godiva --skill migrating-to-workflow-sdk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrates legacy orchestration workflows (Temporal, Inngest, Trigger.dev, and AWS Step Functions) to the Workflow SDK to unify execution semantics across runtimes and tooling.

Core Features & Use Cases

  • Provides a concrete plan to port activities, workers, signals, step.run(), step.waitForEvent(), and child workflows to the Workflow SDK.
  • Guides both managed and self-hosted deployments, including how to model a World interface and startup routines.
  • Clarifies resume surfaces (hook vs webhook) and app-boundary patterns for a smooth migration from existing frameworks.

Quick Start

Use this skill to guide a migration of orchestration flows to the Workflow SDK and begin using start(), createHook/createWebhook, and getWritable for progress.

Frequently Asked Questions about migrating-to-workflow-sdk

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

FAQPage Schema
How do I migrate Temporal workflows and activities to the Workflow SDK?▼

To migrate Temporal workflows, port activities, workers, signals, and child workflows to the Workflow SDK by enforcing use workflow and use step contexts, which unifies execution semantics across both managed and self-hosted runtimes.

What is the best way to port Inngest step.run() and step.waitForEvent() to the Workflow SDK?▼

Porting Inngest step.run() and step.waitForEvent() to the Workflow SDK involves mapping them to the unified step context, using createHook or createWebhook to determine the appropriate resume surface for your event-driven orchestration flows.

How do I convert AWS Step Functions ASL state machines to the Workflow SDK?▼

Converting AWS Step Functions ASL state machines to the Workflow SDK requires mapping your state machine logic to the start() pattern, using use workflow contexts to unify execution semantics across your existing managed runtimes.

Does migrating orchestration flows to the Workflow SDK support self-hosted deployments?▼

Yes, migrating to the Workflow SDK supports self-hosted deployments by requiring a minimal World interface and specific startup routines to properly model execution semantics and resume surfaces for your orchestration flows.

How do I handle hooks versus webhooks when porting Trigger.dev tasks to the Workflow SDK?▼

When porting Trigger.dev tasks to the Workflow SDK, the migration clarifies resume surfaces by determining whether to use createHook or createWebhook, along with getWritable for progress, to properly define app-boundary patterns.

Related Skills

Explore More Software Engineering Skills→
remiconnessonremiconnesson

migrating-to-workflow-sdk

Migrate orchestration code to the Workflow SDK with a structured plan.

Community
Advanced
anukkrit149anukkrit149

workflow

Build durable Vercel Workflow orchestration with pause/resume hooks and retryable steps.

Community
Advanced
JoyanLabsJoyanLabs

inngest

Orchestrate asynchronous background tasks with Inngest event functions.

Official
Advanced
tloncorptloncorp
4

tlon

Retrieve Urbit profiles, channels, messages, and ship data via tlon-run.

Official
Advanced