Help teams articulate compelling long-term product visions grounded in user outcomes, not features or taglines.
Works with
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:
Fetches 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:
Restart Cursor to activate defining-product-vision. Access via /defining-product-vision in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
2
total installs
2
this week
616
GitHub stars
0
upvotes
Run in your terminal
2
installs
2
this week
616
stars
Help the user create compelling product visions using frameworks from 101 product leaders who have defined visions at companies from Notion to Airbnb to the New York Times.
When the user asks for help with product vision:
Melissa Perri: "I once asked all the executive team at a healthcare company, what's the vision for this company? And they said, to be the backbone of healthcare. And I said, what does that mean? And they couldn't elaborate." A vision must be a concrete description of what the company will manifest in 5-10 years.
Ebi Atawodi: "It has to be lofty, it has to be realistic, it has to be devoid of any tech or limitations of today, and it has to be grounded in a very clear and potent problem." Balance aspiration with attainability while ignoring current technical constraints.
Ivan Zhao (Notion): "Our realization is actually let's hide our vision, which is everybody can create their software, in the form factor that people do care. So what kind of tool do people use every day? Productivity software." Package a radical long-term vision inside a familiar, high-utility form factor.
Ben Williams: "The vision is the nirvana state that you aim to enable for your users and customers in five to 10 years... It should not mention your company, your product, or anything solution related at all." Prefix vision statements with 'In the future...' to maintain long-term focus.
Chip Conley: "Ultimately, we came up with the idea that we were in the belong anywhere business. Airbnb was not in home sharing, we were in belonging anywhere." A powerful vision moves beyond the functional 'what' to the emotional 'why.'
Cam Adams (Canva): "We need mock-ups. We need prototypes. You need to get that idea out of your head and present it in a visual form that helps you talk about and communicate about it." Communicate vision through tangible prototypes, not just abstract documents.
Ami Vora: "If we all agree that the feeling of something should be, I'm sitting in Dolores Park with my friends on a sunny Saturday, then people will just naturally build something that feels more consistent." Use emotional metaphors to create a shared understanding that guides decisions without micromanagement.
Chandra Janakiraman: "Product strategy sits between the mission and vision and the plan... It forces choice to deploy scarce resources to generate maximum impact." Strategy is the connective tissue between the aspirational vision and the tactical roadmap.
For all 143 insights from 101 guests, see references/guest-insights.md
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
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