map-product-opportunities

Installation
SKILL.md

Map Product Opportunities

Contract

Keep outcomes, opportunities, solutions, and experiments at distinct levels. An opportunity describes unmet customer progress or friction, not a feature. Branches may compete; the map is a learning model, not a promise tree.

Workflow

  1. Define one measurable customer or business outcome and the relevant segment.
  2. Gather source evidence and extract opportunities in customer language.
  3. Group opportunities by causal relationship to the outcome. Split overlapping jobs and preserve contradictory evidence.
  4. Attach evidence strength, prevalence within the searched set, severity, segment, and key assumptions to each node.
  5. Generate multiple solution approaches only for the best-supported opportunities; include operational or policy changes where relevant.
  6. Identify desirability, usability, feasibility, viability, and ethical or compliance assumptions for each approach.
  7. Attach the cheapest decisive test to the riskiest assumption. Mark decisions and updates as evidence changes.

BuildBetter Acceleration

If BuildBetter MCP is available, search organization skills first. Use signals, survey responses, calls, documents, and project context for opportunities and supporting evidence. Preserve evidence IDs; use synthetic personas only as hypothesis generators, never as proof of real demand.

Installs
1
GitHub Stars
4
First Seen
Oct 27, 2026