workflow-init▌
vercel/workflow · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
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/.
How to use workflow-init on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add workflow-init
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches workflow-init from GitHub repository vercel/workflow and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate workflow-init. Access the skill through slash commands (e.g., /workflow-init) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★72 reviews- ★★★★★Charlotte Gonzalez· Dec 28, 2024
Keeps context tight: workflow-init is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Alexander Ndlovu· Dec 24, 2024
Solid pick for teams standardizing on skills: workflow-init is focused, and the summary matches what you get after install.
- ★★★★★Diego Agarwal· Dec 24, 2024
workflow-init reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Pratham Ware· Dec 20, 2024
Keeps context tight: workflow-init is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Ishan Verma· Dec 16, 2024
workflow-init is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Aisha Wang· Dec 12, 2024
Keeps context tight: workflow-init is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Chinedu Mensah· Dec 12, 2024
workflow-init is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Nikhil Flores· Nov 23, 2024
Keeps context tight: workflow-init is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Hassan Patel· Nov 15, 2024
We added workflow-init from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Ava Wang· Nov 15, 2024
workflow-init is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 72