vercel / workflow

The core workflow skill teaches durable, resumable workflows that survive restarts, pause for external events, retry on failure, and coordinate multi-step operations over time. workflow-init installs and configures the SDK before it exists in node_modules, across Next.js, Express, Hono, Fastify, NestJS, Nitro, Nuxt, Astro, SvelteKit, and Vite. migrating-to-workflow-sdk is the porting skill: it maps Temporal's Activities, Workers, and Signals, Inngest's step.run() and step.waitForEvent(), Trigger.dev's tasks and wait.forToken/triggerAndWait, and AWS Step Functions' ASL state machines onto the Workflow SDK's own model.

The fourth skill, internal-dev-workbench, is not for adopters at all — it wires up a portless-plus-tmux dev session with worktree-isolated <branch>.<name>.localhost URLs and a Claude statusline, and its own description says explicitly not to trigger it for the ordinary "start the dev server" request. It only makes sense if you are working inside Vercel's own workflow repository. For anyone else, this package is really three skills wide: write workflows, install the SDK, or migrate onto it from an existing durable-execution tool.

READ THE FULL ANALYSIS＋

Read the docs site, not this repository, for the details. The README here is mostly badges and links — it points to workflow-sdk.dev for the actual API documentation rather than describing the SDK's behavior itself. Three of the four skills also assume something is already set up locally (the package installed, or a matching dev environment) before they help; only one works from a completely clean start. It is an official Vercel package under the Apache-2.0 license, with the initial engineering team credited by name in the README.