defining-product-vision

refoundai/lenny-skills · updated May 28, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/refoundai/lenny-skills --skill defining-product-vision
0 commentsdiscussion
summary

Help teams articulate compelling long-term product visions grounded in user outcomes, not features or taglines.

  • 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
skill.md

Defining Product Vision

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.

How to Help

When the user asks for help with product vision:

  1. Clarify the scope - Determine if they need a vision (long-term aspiration), strategy (how to win), or roadmap (what to build)
  2. Focus on the user's future - Help them describe the world 5-10 years out, not the product features
  3. Test for specificity - Push back on vague taglines that don't change behavior
  4. Make it visual - Encourage prototypes and concrete artifacts over abstract documents

Core Principles

Vision is not a tagline

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.

Four criteria for strong vision

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.

Hide radical vision in familiar utility

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.

Vision describes the user's world, not your product

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.

Move from 'what' to 'why'

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.'

Use visual artifacts

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.

Vision guides decentralized decisions

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.

Strategy forces choice

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.

Questions to Help Users

  • "If you can't elaborate on your vision in specific terms, is it actually a vision or just a tagline?"
  • "What does the world look like in 5-10 years if you succeed?"
  • "What user problem is so potent that it makes you 'batshit crazy' that it still exists?"
  • "Can someone on your team make a good decision using only your vision as a guide?"
  • "What would your product look like if you didn't have today's technical constraints?"
  • "What's the emotional state you want users to feel?"

Common Mistakes to Flag

  • Vague taglines - "Be the backbone of healthcare" without specific elaboration
  • Feature lists as vision - Describing what you'll build, not what user's lives will be like
  • Mentioning the product - Vision should describe the user's world, not the solution
  • Ignoring current constraints - Good vision transcends today's technology limitations
  • No behavioral change - If the vision doesn't change team priorities, it's not useful

Deep Dive

For all 143 insights from 101 guests, see references/guest-insights.md

Related Skills

  • Writing North Star Metrics
  • Prioritizing Roadmap
  • Setting OKRs & Goals
  • Competitive Analysis
how to use defining-product-vision

How to use defining-product-vision on Cursor

AI-first code editor with Composer

1

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 defining-product-vision
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/refoundai/lenny-skills --skill defining-product-vision

The skills CLI fetches defining-product-vision from GitHub repository refoundai/lenny-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/defining-product-vision

Reload or restart Cursor to activate defining-product-vision. Access the skill through slash commands (e.g., /defining-product-vision) 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

GET_STARTED →

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. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 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

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.562 reviews
  • Ama Robinson· Dec 12, 2024

    Useful defaults in defining-product-vision — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Layla Bhatia· Dec 8, 2024

    I recommend defining-product-vision for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Yusuf Gill· Dec 8, 2024

    defining-product-vision fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Dhruvi Jain· Dec 4, 2024

    We added defining-product-vision from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Arjun Thompson· Nov 27, 2024

    Useful defaults in defining-product-vision — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Omar Rao· Nov 27, 2024

    We added defining-product-vision from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Oshnikdeep· Nov 23, 2024

    defining-product-vision fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Layla Farah· Nov 15, 2024

    Registry listing for defining-product-vision matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Camila Smith· Nov 11, 2024

    defining-product-vision reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Ama Choi· Nov 3, 2024

    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

1 / 7