Design a detailed value proposition using a 6-part JTBD template — Who, Why, What before, How, What after, Alternatives. Use when creating a value proposition, analyzing customer value delivery, or articulating why customers should choose your product.
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.
1. Who
2. Why (Problem)
3. What Before
4. How (Solution)
5. What After
6. Alternatives
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:
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.
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/value-proposition · pinned to the source commit
# Run from your project root
git clone https://github.com/phuryn/pm-skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 18468a95b427e70e258b51389796367c6f684e7d
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/pm-product-strategy/skills/value-proposition" ".claude/skills/"
rm -rf .skillboard-tmpReview the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
sudo apt update && sudo apt install -y gitnpm install -g @anthropic-ai/claude-code# Run from your project root
git clone https://github.com/phuryn/pm-skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 18468a95b427e70e258b51389796367c6f684e7d
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/pm-product-strategy/skills/value-proposition" ".claude/skills/"
rm -rf .skillboard-tmpDestination: .claude/skills/value-proposition
Scanner static-checks@0.1.0 · commit 18468a95b427. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.