skills.rest
remiconnesson
remiconnessonCOMMUNITY
Explore all skills by this author →
GitHub

migrating-to-workflow-sdk

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

Updated Apr 29, 2026
Search Tags:#migration#orchestration#temporal#inngest#trigger.dev#workflow-sdk
One-click install
npx skills add https://github.com/remiconnesson/nuxt-minimal-starter-v0-template --skill migrating-to-workflow-sdk-remiconnesson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrating-to-workflow-sdk
Source: https://github.com/remiconnesson/nuxt-minimal-starter-v0-template/tree/main/.agents/skills/migrating-to-workflow-sdk
Command: npx skills add https://github.com/remiconnesson/nuxt-minimal-starter-v0-template --skill migrating-to-workflow-sdk-remiconnesson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating existing orchestration systems to the Workflow SDK to simplify maintenance, unify execution models, and unlock modern runtime capabilities.

Core Features & Use Cases

  • Identify source workflows and target runtime.
  • Generate a migration plan with source/target mappings, migrated code, and app boundary guidance.
  • Provide concrete examples for hooks/webhooks, resume strategies, and child workflows across frameworks.
  • Offer framework-agnostic guidance and explicit boundary recommendations based on prompts.

Quick Start

Describe your source workflow and I will generate a Workflow SDK migration plan.

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 orchestration code to the Workflow SDK?▼

Migrating orchestration code to the Workflow SDK involves generating a structured migration plan that includes source-to-target mappings, migrated code, app boundary guidance, resume endpoints, and a verification checklist.

Can I port Temporal workflows to the Workflow SDK?▼

Yes, you can port Temporal workflows to the Workflow SDK. The migration process supports Temporal, Inngest, Trigger.dev, and AWS Step Functions, providing framework-agnostic guidance and explicit app boundary recommendations for your source workflows.

What is included in a Workflow SDK migration plan?▼

A Workflow SDK migration plan includes source-to-target mappings, migrated code, app boundary and resume endpoints, a verification checklist, and open questions to guide porting orchestration work.

Does the Workflow SDK migration support AWS Step Functions?▼

Yes, the Workflow SDK migration supports AWS Step Functions. It provides concrete examples for hooks, webhooks, resume strategies, and child workflows to help port AWS Step Functions orchestration work effectively.

What is the best way to handle app boundaries when porting Trigger.dev workflows?▼

The best way to handle app boundaries when porting Trigger.dev workflows is to use the generated migration plan, which provides explicit app boundary guidance and resume endpoint strategies to ensure correct execution model transitions.

Related Skills

Explore More Software Engineering Skills→
srstompsrstomp
8

architecture-review

Audit TypeScript/JavaScript projects for circular dependencies and god modules.

Community
Advanced
cloudflarecloudflare
2.6k

sandbox-sdk

Automate secure sandboxed environment creation and code execution via the @cloudflare/sandbox API.

Official
Advanced
myriosMinmyriosMin

migrating-to-workflow-sdk

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

Community
Advanced
1uc4sm4theus1uc4sm4theus
20

code_review

Analyze source files and git history to generate implementation plans and root cause analysis.

Community
Advanced