problem-validation

Validate startup problem existence, pain level, and solvability during customer discovery interviews.

3|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/The13thNode/VibeCorp_PromptCEO --skill problem-validation-the13thnode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-validation
Source: https://github.com/The13thNode/VibeCorp_PromptCEO/tree/main/skills/public/problem-validation
Command: npx skills add https://github.com/The13thNode/VibeCorp_PromptCEO --skill problem-validation-the13thnode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It ensures startups do not build products without a validated, painful problem by guiding founders through pressure‑aware customer discovery, pain analysis, and feature prioritization.

Core Features & Use Cases

  • Pressure‑Aware Problem Hypothesis: Templates to map organizational, role, personal, and temporal pressures before interviews.
  • Interview Structure & Question Bank: Ready‑to‑use scripts for 30‑45 minute discovery calls, including pressure‑focused opening questions.
  • Signal Strength Guide: Framework to classify strong, weak, and red‑flag signals from interviewees.
  • Must‑Have vs Nice‑to‑Have Prioritization: Matrices and templates to rank features and determine MVP scope.
  • Willingness‑to‑Pay Tests: Van Westendorp pricing questions and commitment ladder assessments.
  • Investor Evidence Summary: Structured sections to compile interview data into investor‑ready documentation.

Quick Start

Ask the problem-validation skill to create a pressure‑aware interview guide for my target customer segment.

Frequently Asked Questions about problem-validation

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

FAQPage Schema
How do I validate a startup problem during customer discovery interviews?

Problem validation ensures you do not build products without a validated, painful problem. It guides founders through pressure-aware customer discovery, pain analysis, and feature prioritization to confirm real market needs before development.

How do I prioritize features for an MVP based on customer discovery data?

Prioritize features for an MVP by applying must-have versus nice-to-have matrices to your customer discovery data. This framework ranks features based on interview signals to determine the exact scope of your minimum viable product.

What is pressure-aware discovery and how does it map organizational and personal pressures?

Pressure-aware discovery is a framework that maps organizational, role, personal, and temporal pressures before interviews. It uses targeted opening questions to understand the exact contexts driving a customer's pain and willingness to pay.

Can I test willingness to pay without external tools during early customer interviews?

You can test willingness to pay without external tools by applying Van Westendorp pricing questions and commitment ladder assessments. These structured templates integrate directly into 30-45 minute discovery calls.

How do I classify strong and weak signals from user interview responses?

Classify strong, weak, and red-flag signals from user interviews by applying a structured signal strength guide. This framework helps objectively evaluate interviewee responses to determine true problem fit and urgency.

What is the best way to compile interview data into investor-ready documentation?

The best way to compile interview data into investor-ready documentation is to use a structured evidence summary framework. This organizes pressure profiles, signal classifications, and willingness-to-pay data into clear sections for investor review.