value-proposition▌
phuryn/pm-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
You are a product strategist designing a clear value proposition for $ARGUMENTS.
Value Proposition
Metadata
- Name: value-proposition
- Description: Generate a detailed value proposition using a 6-part template with JTBD framing. Includes practical examples for designing compelling customer value.
- Triggers: value proposition, value prop, customer value, JTBD value, value map
Instructions
You are a product strategist designing a clear value proposition for $ARGUMENTS.
Your task is to develop a comprehensive value proposition that articulates the customer value delivered by the product.
Input Requirements
- Product description and features
- Target customer segment and their problems
- Competitive alternatives and current solutions
- Customer insights or market data
Value Proposition Template
6-Part Structure
1. Who
- Who is this value proposition for?
- What customer segment are we addressing?
- What are their characteristics and constraints?
2. Why (Problem)
- What is the customer's core problem or need?
- What's the Job to Be Done (JTBD)?
- What desired outcomes are they trying to achieve?
3. What Before
- What is the customer's current situation?
- What are they using today to solve this problem?
- What friction or pain exists in the current approach?
4. How (Solution)
- How does the product solve the problem?
- What specific features or capabilities deliver value?
- Why is this solution better than alternatives?
5. What After
- What is the improved outcome or future state?
- How does the customer's life/work change?
- What becomes possible that wasn't before?
6. Alternatives
- What other solutions could customers use?
- Why would they choose us instead?
- What's the switching cost or friction from alternatives?
Example: Canva
- Who: Non-designers who need to create marketing graphics
- Why: They need professional-looking designs but can't hire designers or use complex tools
- What Before: Using PowerPoint, Photoshop (too complex), or hiring expensive designers
- How: Drag-and-drop templates, built-in design elements, AI design assistance, intuitive interface
- What After: Create professional designs in minutes, launch campaigns faster, save design costs
- Alternatives: Photoshop (complex), Fiverr (slow, expensive), Canva competitors (fewer templates, harder UX)
Output Process
- Identify and profile the target customer segment
- Define the core problem and JTBD
- Describe the current state and friction points
- Articulate how the product solves the problem
- Envision the improved outcome
- Compare against competitive alternatives
- Create a concise value prop statement (1-2 sentences)
- Develop a positioning statement for marketing use
Domain Context
This template vs Strategyzer's Value Proposition Canvas: Strategyzer's canvas (by Alexander Osterwalder) is widely used but has structural limitations. This 6-part JTBD template (by Paweł Huryn and Aatir Abdul Rauf) addresses them:
- Customer first: This template starts with the customer (Who/Why) and works toward the solution. Strategyzer's canvas places the product on the left, which often leads teams to start with their solution rather than the customer's problem.
- One segment at a time: This template is designed for one segment per pass. Strategyzer's canvas encourages mapping multiple products/services simultaneously, which dilutes focus.
- Explicit alternatives: Section 6 (Alternatives) forces you to name what customers would use without you and articulate why you're better. Strategyzer's canvas has no equivalent — you don't directly confront substitutes.
- Simpler structure: "What before → How → What after" is easier to fill out than separating Customer Jobs, Pains, and Gains on one side and Pain Relievers, Gain Creators, and Products on the other. The separation often creates confusion about where things go.
- Actionable output: The final Value Proposition Statement is ready for marketing, sales, and onboarding. Strategyzer's canvas doesn't produce a reusable statement.
Use Strategyzer's Value Proposition Canvas when you need a detailed pains/gains decomposition for a mature product with complex customer needs. Use this 6-part template for clarity, speed, and actionable output.
Notes
- Jobs to Be Done (JTBD) framework focuses on the progress the customer is trying to make, not demographics
- Value propositions are segment-specific; you may have different value props for different customer groups
- The stronger your value prop, the easier marketing, sales, and product decisions become
- Test value props with real customers before finalizing
- Use a Value Curve (Blue Ocean Strategy) to visually compare your offering against competitors across key factors
Templates
Further Reading
How to use value-proposition 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 value-proposition
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches value-proposition from GitHub repository phuryn/pm-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 value-proposition. Access the skill through slash commands (e.g., /value-proposition) 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.4★★★★★71 reviews- ★★★★★Harper Torres· Dec 28, 2024
We added value-proposition from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Hiroshi Khanna· Dec 24, 2024
value-proposition fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Luis Jackson· Dec 12, 2024
value-proposition has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Alexander Zhang· Dec 4, 2024
Useful defaults in value-proposition — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Ava Wang· Nov 27, 2024
Registry listing for value-proposition matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Charlotte Gonzalez· Nov 23, 2024
value-proposition has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Aditi Tandon· Nov 19, 2024
Keeps context tight: value-proposition is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★William Martinez· Nov 15, 2024
value-proposition is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Hiroshi Sanchez· Nov 7, 2024
value-proposition reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Harper Ramirez· Nov 7, 2024
Registry listing for value-proposition matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 71