validate-product-problem

Installation
SKILL.md

Validate Product Problem

Contract

Validate the problem before defending a solution. Treat frequency, severity, workarounds, willingness to change, and strategic fit as separate claims. A not-yet verdict is valid.

Workflow

  1. Write the problem in a situation, actor, barrier, and consequence form without a solution.
  2. Define the decision and evidence threshold proportional to the bet's cost and reversibility.
  3. Inventory evidence across behavior, direct voice, product or market data, support, sales, and existing alternatives.
  4. Evaluate dimensions separately: occurrence, intensity, affected segment, current workaround, switching trigger, willingness to invest, and strategic fit.
  5. Search for disconfirming cases, successful workarounds, non-consumption, and segments where the problem does not matter.
  6. Score confidence in each claim based on source quality and diversity, not the enthusiasm of respondents.
  7. Choose validated, promising but unproven, not supported, or out of scope; specify the next evidence that could change the verdict.

BuildBetter Acceleration

If BuildBetter MCP is available, search organization skills first. Use calls, direct customer signals, survey responses, people or account context, documents, and aggregates. Record filters and IDs. Do not treat synthetic persona output as validation of real demand.

Installs
1
GitHub Stars
4
First Seen
Oct 27, 2026