Migrating To Workflow Sdk

This does the heavy lifting when you're porting existing orchestration code from Temporal, Inngest, Trigger.dev, or AWS Step Functions into the Workflow SDK. It knows how to map Activities to steps, Signals to hooks or webhooks, wait-for-event patterns to the right resume surface, and state machines to workflow functions. The routing logic is strict: it picks between internal hooks with deterministic tokens, auto-acknowledged webhooks, or manual-response webhooks based on what your prompt actually requires, and it fails the draft if you mix primitives that don't belong together. Worth using when you have working orchestration elsewhere and need a clean migration path that respects idempotency, streaming, retries, and the use-workflow versus use-step boundary.

skills.sh installs: 776
GitHub stars: 2.5K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add vercel/workflow --skill migrating-to-workflow-sdk --agent claude-code

Installs into .claude/skills of the current project.

Files

Migrating to the Workflow SDK

Use this skill when converting an existing orchestration system to the Workflow SDK.

Intake

Identify the source system:
- Temporal
- Inngest
- Trigger.dev
- AWS Step Functions
Identify the target runtime:
- Managed hosting -> keep examples focused on start(), getRun(), hooks/webhooks, and route handlers.
- Self-hosted -> also read references/runtime-targets.md and explicitly say the workflow/step code can stay the same, but deployment still needs a World implementation and startup bootstrap.
Extract the source constructs:
- entrypoint
- waits / timers
- external callbacks / approvals
- retries / failure handling
- child workflows / fan-out
- progress streaming
- external side effects