agentsclimarketplace
Sign in

Product opportunity tree

Skill jpoindexter/product-management-skills/skills/product-opportunity-tree

Build or critique an Opportunity Solution Tree linking a measurable outcome to customer opportunities, alternative solutions, assumptions, and tests. Use when a team is converging too early, has a feature list without rationale, needs to compare options, or wants a discovery map.From its SKILL.md

Install
npx -y skills add jpoindexter/product-management-skills --skill product-opportunity-tree

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 24 days oldThe repository was created 24 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.5 KB, 416 tokens by cl100k_base, as published. Nobody here has run it

Product Opportunity Tree

Represent multiple evidence-backed paths from one desired outcome to customer opportunities, possible solutions, critical assumptions, and small tests.

Inputs

  • One desired outcome and baseline
  • Target customer and situation
  • Interview stories, telemetry, or support evidence
  • Candidate opportunities and solutions
  • Constraints and decision horizon

Build the tree

  1. Place one measurable outcome at the root. Separate customer behavior from the business result it supports.
  2. Extract opportunities from customer stories. Express needs, pain points, and desires in customer language.
  3. Group related opportunities without erasing meaningful differences. Preserve evidence links.
  4. Select a target opportunity using importance, reach, evidence, strategic fit, and current satisfaction.
  5. Generate several materially different solutions for the target opportunity.
  6. For each solution, list assumptions across value, usability, feasibility, and viability.
  7. Identify the assumption that is both essential and weakly supported.
  8. Attach a small assumption test and a precommitted interpretation rule.
  9. Compare paths; do not score a single favored branch in isolation.

Output contract

Return a text tree plus:

  • Outcome definition and baseline
  • Opportunity evidence and source
  • Selection rationale
  • Alternative solutions
  • Critical assumption per solution
  • Test, evidence threshold, and next decision
  • Pruned branches with reasons

Quality gate

  • The root is an outcome, not a project.
  • Opportunities are not solution wording.
  • More than one opportunity and solution are considered when evidence permits.
  • Tests target assumptions rather than full-product delivery.
  • Every branch is traceable to evidence or explicitly labeled assumed.

Avoid

  • A decorative tree created after a decision
  • Vague roots such as “increase engagement” without behavior, segment, and horizon
  • Treating tree depth as certainty
  • Deleting contradictory branches to simplify the story
  • Using one composite score as the decision

Source grounding

Operational synthesis informed by Teresa Torres's Opportunity Solution Tree and compare-and-contrast practices in Continuous Discovery Habits.

What ships with it: 1 file

233 B alongside SKILL.md

agents/

Keep looking

Skills are one crate of 326,401. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.