Help teams articulate compelling long-term product visions grounded in user outcomes, not features or taglines.
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
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
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
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
Submit your Claude Code skill and start earning
epx add refoundai/lenny-skills --skill defining-product-visionCompatible with
Supported agents
Provides frameworks from 101 product leaders (Notion, Airbnb, New York Times) covering four criteria for strong vision: lofty yet realistic, free of current technical constraints, and grounded in a potent user problem
Guides users to describe the user's future world in 5–10 years rather than product features, with emphasis on emotional outcomes and behavioral change
Include
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondefining-product-visionExecute the skills CLI command in your project's root directory to begin installation:
epx add refoundai/lenny-skills --skill defining-product-visionFetches defining-product-vision from refoundai/lenny-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/defining-product-vision
Restart Cursor to activate defining-product-vision. Access via /defining-product-visionin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Time estimate: 30-60 minutes to see productivity improvements
Prerequisites
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
deslop
cursor/plugins · Productivity · same category
write-a-prd
mattpocock/skills · Productivity · same category
premortem
parcadei/continuous-claude-v3 · Productivity · same category
yt-dlp
lwmxiaobei/yt-dlp-skill · Productivity · same category
framer-motion
pproenca/dot-skills · Productivity · same category
nestjs-best-practices
kadajett/agent-nestjs-skills · Productivity · same category
Useful defaults in defining-product-vision — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend defining-product-vision for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
defining-product-vision fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added defining-product-vision from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in defining-product-vision — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added defining-product-vision from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
defining-product-vision fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for defining-product-vision matched our evaluation — installs cleanly and behaves as described in the markdown.
defining-product-vision reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend defining-product-vision for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 62