This walks you through building Teresa Torres' opportunity solution tree framework, which stops teams from jumping straight to feature ideas by forcing you to connect everything back to measurable outcomes and actual customer problems. You start with a quantifiable goal, map out opportunity areas as customer needs rather than solutions, back each with evidence from research or data, then brainstorm multiple solutions per opportunity with assumption tests. It's useful when you're drowning in feature requests and need structure, or when stakeholders keep asking why you're building something. The seven step process is thorough, maybe more than you need for a quick prioritization exercise, but solid if you're doing continuous discovery work.
npx -y skills add product-on-purpose/pm-skills --skill define-opportunity-tree --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
mattpocock/skills