problem-validation

Score problem frequency, intensity, workarounds, and willingness to pay.

54|4|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/assimovt/productskills --skill problem-validation-assimovt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-validation
Source: https://github.com/assimovt/productskills/tree/main/skills/problem-validation
Command: npx skills add https://github.com/assimovt/productskills --skill problem-validation-assimovt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you rigorously validate whether a problem is truly worth solving by assessing its frequency, intensity, existing workarounds, and willingness to pay, ensuring you invest resources wisely.

Core Features & Use Cases

  • Quantitative Problem Scoring: Assigns a score based on four key dimensions (Frequency, Intensity, Workarounds, Willingness to Pay).
  • Evidence-Based Validation: Emphasizes the use of observed behavior, spending, and direct quotes over opinions.
  • Go/No-Go Decision Framework: Provides clear criteria for deciding whether to proceed with a solution, investigate further, or abandon the problem.
  • Use Case: Before building a new feature, use this Skill to score the problem of users struggling to export data from your application, ensuring it's a significant pain point that warrants development effort.

Quick Start

Validate the problem of users struggling to export data from our application by assessing its frequency, intensity, workarounds, and willingness to pay.

Frequently Asked Questions about problem-validation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate user pain points before building a new product feature?

Problem validation assesses product discovery viability by scoring user pain points across frequency, intensity, workarounds, and willingness to pay. It emphasizes observed behavior and direct quotes over opinions to ensure significant issues warrant development effort.

What is the best way to assess market validation and willingness to pay for a solution?

Evaluate market validation by scoring problem frequency, intensity, and willingness to pay using evidence-based criteria. This approach requires observed behavior and spending data to provide clear go/no-go decisions for product development.

How do I score the significance of a user problem to prioritize my product backlog?

Prioritize your product backlog by scoring the significance of user problems across frequency, intensity, workarounds, and willingness to pay. This quantitative scoring uses evidence-based criteria to ensure resources target viable pain points.

When should I use a go/no-go decision framework for problem discovery?

Use a go/no-go decision framework during product discovery before building new features. It helps rigorously validate whether a user problem is truly worth solving by assessing market viability and ensuring wise resource investment.

Why does evidence-based problem validation require observed behavior over user opinions?

Evidence-based problem validation prioritizes observed behavior and spending over user opinions because actual actions indicate true problem intensity. This ensures frequency and willingness to pay scores accurately reflect market viability for go/no-go decisions.