executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
value-propositionCraft a sharp value proposition that says who it's for, the outcome, and why you over the alternative. Use when asked to write a value prop, a value proposition, a one-liner, or to clarify 'what do we even say we do?'. Produces a primary value-prop statement, a plain-language one-liner, 3 benefit-led variations, and the before→after transformation it promis…
Independent GitHub snapshot · Automated classification · Original documentation governs
A value proposition is the single sentence that makes someone think "that's for me." Most are vague
feature-soup ("the all-in-one platform for modern teams"). This skill writes one that names the
audience, the outcome they actually want, and why you beat the alternative — the foundation every
landing page, ad, and pitch is built on. (For the category/competitive frame, pair with
product-positioning-doc; this writes the words.)
Ask for these only if they aren't already provided:
1. Primary statement — the canonical form:
For [audience] who [need/struggle], [product] is the [category] that [key outcome]. Unlike [alternative], it [differentiator].
2. One-liner — the plain-language version a customer would say to a friend (≤12 words, no jargon). This is the headline candidate.
3. Three variations — benefit-led alternates in different angles (outcome-led, pain-led, identity-led), so you can A/B them.
4. Before → After — the transformation in two columns (their world without you → with you). This is what the copy dramatizes.
| Without [product] | With [product] |
|---|---|
| [the painful status quo] | [the better state] |
5. What to avoid — the generic phrasings to cut (e.g. "all-in-one", "seamless", "next-generation") because they say nothing.
Value-proposition design (Osterwalder) + April Dunford positioning as the upstream frame.