workflow-init▌
vercel/workflow · updated Apr 8, 2026
Initial setup of Vercel Workflow SDK before workflow is installed. Fetch the official getting-started guide for the user's framework.
workflow-init
Initial setup of Vercel Workflow SDK before workflow is installed. Fetch the official getting-started guide for the user's framework.
Decision Flow
0) Sanity check
Read package.json. If workflow is already a dependency, tell the user to use /workflow instead (it reads versioned docs from node_modules/workflow/docs/). Only continue if workflow is missing.
1) Determine the framework
Non-interactive: If the user named a framework in their prompt, use it directly.
Auto-detect: Inspect package.json deps and config files. Use the first match:
- Next.js -
nextdep ornext.config.* - Nuxt -
nuxtdep ornuxt.config.* - SvelteKit -
@sveltejs/kitdep orsvelte.config.* - Astro -
astrodep orastro.config.* - NestJS -
@nestjs/coredep ornest-cli.json - Nitro -
nitrodep ornitro.config.* - Express -
expressdep - Fastify -
fastifydep - Hono -
honodep - Vite -
vitedep (and not matched above)
If no match or multiple matches, ask the user to pick.
2) Fetch and follow the getting-started guide
Fetch exactly one of these URLs and follow the guide step-by-step:
Each guide covers: install deps, configure framework, create first workflow, create route handler, run + verify.
3) Verify setup
- Start the dev server per the guide.
- Trigger the example endpoint with the provided
curl. - Confirm logs show the workflow and steps executing.
- Optional:
npx workflow webornpx workflow inspect runs.
4) No framework yet?
If no framework exists, ask what the user wants:
- Web app: Next.js / Nuxt / SvelteKit / Astro
- API server: Express / Fastify / Hono
- Minimal server: Nitro or Vite
Then follow the "Create Your Project" section of the chosen guide.
Concept questions (pre-install)
If the user asks conceptual questions before installing, fetch:
- https://useworkflow.dev/docs/foundations/workflows-and-steps
- https://useworkflow.dev/docs/foundations/common-patterns
Handoff
When setup is complete, tell the user: Use /workflow for ongoing development - it reads the versioned docs bundled in node_modules/workflow/docs/.
Ratings
4.5★★★★★10 reviews- ★★★★★Shikha Mishra· Oct 10, 2024
workflow-init is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Piyush G· Sep 9, 2024
Keeps context tight: workflow-init is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Chaitanya Patil· Aug 8, 2024
Registry listing for workflow-init matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Sakshi Patil· Jul 7, 2024
workflow-init reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Ganesh Mohane· Jun 6, 2024
I recommend workflow-init for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Oshnikdeep· May 5, 2024
Useful defaults in workflow-init — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Dhruvi Jain· Apr 4, 2024
workflow-init has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Rahul Santra· Mar 3, 2024
Solid pick for teams standardizing on skills: workflow-init is focused, and the summary matches what you get after install.
- ★★★★★Pratham Ware· Feb 2, 2024
We added workflow-init from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Yash Thakker· Jan 1, 2024
workflow-init fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.