Skip to main content
ClaudeWave
Skill17k estrellas del repoactualizado 6d ago

value-proposition

The value-proposition skill generates a structured value proposition using a six-part Jobs to Be Done framework covering customer segment, core problem, current situation, solution approach, improved outcomes, and competitive alternatives. Use this skill when creating or refining value propositions, analyzing how products deliver customer value, or developing messaging that articulates why customers should choose a particular solution over alternatives.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/value-proposition && cp -r /tmp/value-proposition/pm-product-strategy/skills/value-proposition ~/.claude/skills/value-proposition
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# 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
1. Identify and profile the target customer segment
2. Define the core problem and JTBD
3. Describe the current state and friction points
4. Articulate how the product solves the problem
5. Envision the improved outcome
6. Compare against competitive alternatives
7. Create a concise value prop statement (1-2 sentences)
8. 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

- [Value Proposition Template (PPTX)](https://docs.google.com/presentation/d/1RXH1Udj71aXQJzGeqYSOStnfQ-6dNz14/edit?slide=id.g2a98aeea3b1_0_247#slide=id.g2a98aeea3b1_0_247)

---

### Further Reading

- [How to Design a Value Proposition Customers Can't Resist?](https://www.productcompass.pm/p/how-to-design-value-proposition-template)
- [How to Achieve Product-Market Fit? Part I: Market and Value Proposition](https://www.productcompass.pm/p/how-to-achieve-the-product-market)
- [Jobs-to-be-Done Masterclass with Tony Ulwick and Sabeen Sattar](https://www.productcompass.pm/p/jobs-to-be-done-masterclass-with) (video course)
- [Product Innovation Masterclass](https://www.productcompass.pm/p/product-innovation-masterclass) (video course)
intended-vs-implementedSkill

The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.

shipping-artifactsSkill

The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.

ab-test-analysisSkill

Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.

cohort-analysisSkill

Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.

sql-queriesSkill

Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.

brainstorm-okrsSkill

Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.

create-prdSkill

Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

dummy-datasetSkill

Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.