positioning-messaging▌
refoundai/lenny-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Craft compelling product positioning and messaging using frameworks from 58 product leaders.
- ›Guides users through understanding target audience, identifying competitive frames, finding differentiated value, and testing message resonance
- ›Emphasizes positioning as foundational to all marketing, with weak positioning creating pipeline friction and customer confusion
- ›Flags common mistakes: feature-first messaging, positioning by generic adjectives, trying to appeal to everyone, and compa
Positioning & Messaging
Help the user craft compelling product positioning and messaging using frameworks from 58 product leaders and marketers.
How to Help
When the user asks for help with positioning and messaging:
- Understand the target audience - Ask who specifically they're trying to reach and what those people care about
- Identify the competitive frame - Determine what alternatives customers are comparing them against
- Find the differentiated value - Help them articulate what's uniquely true and valuable about their offering
- Test message resonance - Guide them toward language that reflects how customers describe their own problems
Core Principles
Positioning dictates everything
Arielle Jackson: "I really believe that positioning dictates so much of your marketing and should always be the first thing you do. I had a student in my last class... He goes, I'll never write a line of code without doing positioning first." Positioning is the foundational element of marketing that should precede product development and all other marketing activities.
Weak positioning creates pipeline friction
April Dunford: "Weak positioning hurts you in the early stages of pipeline in that people don't really get what you are, so they're not responding to your marketing the way they should. And you'll get this sluggishness in the middle of your pipeline." Monitor for customers asking sales reps to "back up and start over" during pitches - this signals positioning problems.
Communication is defined by the receiver
Gina Gotthilf: "Communication isn't about being able to convey a message, it's about being able to convey a message in a way that the listener receives it, and understands it, and remembers it." Effective communication is defined by the listener's ability to understand and remember the message, not just the act of sending it.
Use pattern matching for press
Emilie Gerber: "You can get so in the weeds with your own messaging that you want to set up this massive problem statement... but if you're very straightforward and you're pattern matching, it's generally actually going to work." Straightforward pattern matching is more effective for press than complex problem statements or trend stories.
Brand sets expectations
Jessica Hische: "The cover of the book should tell people what to expect from the thing that they're about to engage with." A brand's visual identity should serve as a symbiotic preview that sets the correct expectations and tone for the product experience.
Start with the struggling moment
Bob Moesta: "A struggling moment causes demand. And you start to realize that in some cases that struggling moment exists and can exist for a long time and nobody solved it." Great positioning starts with understanding the specific context where users feel stuck, not with product features.
Differentiation requires sacrifice
April Dunford: "You can't be everything to everyone." True positioning requires explicitly deciding who you're NOT for and what you're NOT offering.
Questions to Help Users
- "When a customer switches to your product, what are they switching FROM? What were they doing before?"
- "If your product disappeared tomorrow, what would your best customers miss most?"
- "What do your happiest customers say when they recommend you to a friend?"
- "Who is specifically NOT a good fit for your product, and why?"
- "What competitive alternative are you explicitly positioning against?"
- "Can everyone in your company describe what you do consistently?"
Common Mistakes to Flag
- Feature-first messaging - Leading with what the product does rather than what customers achieve
- Positioning by adjectives - Using words like "powerful" or "easy-to-use" that every competitor also claims
- Trying to appeal to everyone - Refusing to narrow the target audience for fear of missing opportunities
- Complex problem statements - Over-explaining the problem instead of using straightforward pattern matching
- Company-centric language - Using internal jargon or product names that mean nothing to prospects
Deep Dive
For all 106 insights from 58 guests, see references/guest-insights.md
Related Skills
- problem-definition
- product-taste-intuition
- pricing-strategy
How to use positioning-messaging 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 positioning-messaging
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches positioning-messaging from GitHub repository refoundai/lenny-skills 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 positioning-messaging. Access the skill through slash commands (e.g., /positioning-messaging) 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.6★★★★★49 reviews- ★★★★★Chinedu Bansal· Dec 24, 2024
positioning-messaging is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Tariq Abebe· Dec 8, 2024
Useful defaults in positioning-messaging — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Zara Ndlovu· Dec 8, 2024
Keeps context tight: positioning-messaging is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Amina Choi· Nov 27, 2024
positioning-messaging is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Yusuf Tandon· Nov 27, 2024
I recommend positioning-messaging for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Ren Okafor· Nov 15, 2024
Useful defaults in positioning-messaging — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Yusuf Verma· Nov 11, 2024
Solid pick for teams standardizing on skills: positioning-messaging is focused, and the summary matches what you get after install.
- ★★★★★Diego White· Oct 18, 2024
Keeps context tight: positioning-messaging is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Yusuf Gupta· Oct 18, 2024
Useful defaults in positioning-messaging — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Ren Jackson· Oct 6, 2024
I recommend positioning-messaging for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 49