
Layers Product Strategy
A comprehensive framework for connecting user needs to business outcomes through opportunity solution trees and structured experimentation. Walks you through choosing measurable outcomes, mapping opportunities anchored to journey moments, generating multiple solution bets per opportunity, and designing cheap experiments to test risky assumptions. The disciplines are sharp: opportunities must pass a flip test to avoid being disguised features, every bet names its riskiest assumption, experiments take days not months. Includes a decision matrix for when to use Impact Mapping, Wardley, Kano, or other techniques instead of the default OST. Best when you need to make strategic choices explicit rather than let them stay implicit in a backlog.
- skills.sh installs
- 2K
- GitHub stars
- 314
- last updated
- Aug 21, 2026
Install
$ npx -y skills add jamiemill/layers-skills --skill layers-product-strategy --agent claude-codeInstalls into .claude/skills of the current project.
Files
/layers-product-strategy
Assumes /layers-intro has been loaded. This skill is a library of techniques, not a script — see "How to use these skills" there.
Strategy is the first layer of the solution space — where problem-space understanding converts into deliberate decisions about scope and direction. It is about choices: which user needs to serve, and which business outcomes to target.
The decisions this layer makes
- The business outcome this work serves
- Which user opportunities (needs, pains, desires) genuinely connect to that outcome
- What solution bets we're placing on those opportunities
- How to test the riskiest assumptions cheaply
- Which bets to pursue first, and why
If the outcome and the bets are already clear, don't rebuild the tree for its own sake.
Disciplines — what keeps strategy honest
Sponsors
Details
- Repository
- github.com/jamiemill/layers-skills
- Category
- Testing & QA
- First seen
- Jun 3, 2026