value-proposition
by phurynUse the value-proposition skill to build a clear customer value statement with a 6-part JTBD structure: Who, Why, What before, How, What after, and Alternatives. It fits Product Management, launches, strategy docs, and cases where you need to explain why customers should choose your product.
This skill scores 78/100, which means it is a solid listing candidate for directory users: it has a clear trigger, a real workflow, and enough structure to reduce guesswork versus a generic prompt, though it still lacks supporting assets and implementation extras that would make adoption easier.
- Clear triggerability: metadata names value proposition, value prop, customer value, and JTBD value, making it easy for agents to activate correctly.
- Operational workflow: the SKILL.md provides a 6-part JTBD-based template (Who, Why, What before, How, What after, Alternatives) plus input requirements.
- Substantive content: 5.5kB body with 7 H2s, 4 H3s, and no placeholder markers suggests a real instruction set rather than a stub.
- No support files, references, scripts, or resources, so users must rely on the text alone for guidance and validation.
- No install command or examples in the repo evidence, which limits immediate adoption and makes edge-case execution less discoverable.
Overview of value-proposition skill
The value-proposition skill helps you turn product facts into a clear customer value statement using a 6-part JTBD structure: Who, Why, What before, How, What after, and Alternatives. It is best for Product Management and strategy work where you need to explain why a customer should choose a product, not just list features.
What this skill is for
Use the value-proposition skill when you need a sharper value proposition for a launch page, pitch deck, internal strategy doc, or roadmap discussion. It is especially useful when the problem is not “what does the product do?” but “what change does it create for a specific customer segment?”
Why it stands out
The main advantage of this value-proposition skill is its JTBD framing. It forces you to separate the customer’s current state, the desired outcome, and the alternatives they already use. That usually produces stronger positioning than a generic benefit list.
Best-fit situations
Choose value-proposition install if you already have a product concept, audience hypothesis, or competitive context and want a structured narrative from it. It is a poor fit if you only want slogan ideas or if you have no idea who the customer is.
How to Use value-proposition skill
Install and first read
Install the value-proposition skill with npx skills add phuryn/pm-skills --skill value-proposition. Then read SKILL.md first, because this repo has no helper scripts or companion resources to interpret the workflow for you. In practice, the value-proposition guide lives in that one file.
Prepare the right input
The skill works best when you give it four things: product description, target segment, current workaround, and alternatives. A weak prompt says, “Write a value proposition for my app.” A stronger prompt says: “Write a value proposition for a B2B dashboard used by operations managers at mid-market logistics firms. Their current workaround is spreadsheets and weekly calls. Competing options are Airtable templates and an in-house BI report.”
Prompt pattern that works
To get better value-proposition usage, structure your request around the template:
- Who is the customer?
- Why do they care now?
- What do they do before using this product?
- How does the product change that?
- What outcome happens after?
- What do they compare it against?
If you already have research, include exact phrases customers use. That improves the output more than adding more feature bullets.
Suggested workflow
Start broad, then tighten the scope. First ask for a draft value proposition. Next, ask the model to rewrite it for a specific channel, such as homepage hero copy, investor summary, or Product Management review. Finally, pressure-test the alternatives section so the positioning is credible rather than generic.
value-proposition skill FAQ
Is this just a generic prompt?
No. The value-proposition skill gives you a repeatable structure, which matters when you need consistency across teams or products. A generic prompt often skips the “before” state and alternatives, which weakens the final positioning.
Do I need research before using it?
You do not need a full research deck, but you do need enough input to identify the customer, problem, and alternatives. If you skip those, the model can still write something, but the result will be broad and less decision-useful.
Is it suitable for beginners?
Yes, if you can describe a product in plain language. It is also useful for non-PM roles because the template is easy to follow. The main beginner mistake is giving only feature lists and expecting the skill to infer the market context.
When should I not use it?
Do not use this value-proposition skill when the goal is purely copywriting polish, tagline brainstorming, or brand voice exploration. It is designed for strategy-first positioning, especially when you need a defensible value proposition for Product Management.
How to Improve value-proposition skill
Give sharper customer context
The biggest quality jump comes from clearer segmentation. Instead of “small businesses,” specify the type, size, workflow, and constraint. For example: “10–50 person agencies that track utilization manually and miss billable hours.”
Include real alternatives, not placeholders
The value-proposition guide works best when alternatives are concrete: spreadsheets, internal tools, incumbent vendors, or doing nothing. If you only say “competitors,” the output tends to become vague and less persuasive.
Ask for one outcome at a time
A common failure mode is trying to support too many promises in one pass. If your first draft feels unfocused, ask for a version centered on one primary outcome, such as speed, accuracy, risk reduction, or revenue lift. That usually improves the logic more than adding more adjectives.
Iterate on the weakest part
After the first output, ask for revisions by section: “tighten the Who,” “make What before more specific,” or “rewrite Alternatives to sound credible.” That keeps the value proposition grounded and helps you use the skill as a working Product Management tool, not a one-shot summary.