What problem does it solve? Teams often commit engineering effort to ideas built on untested assumptions about user pain, frequency, and urgency. This Skill turns an assumption-heavy problem statement into a structured validation plan with testable claims, research methods, and go/no-go decision thresholds before any code is written. ## Core Features & Use Cases - Assumption Mapping: Separates known facts from unsupported claims and prioritizes the riskiest assumptions about problem existence, audience, frequency, and willingness to pay. - Evidence Method Selection: Matches each uncertainty to the lightest credible research method, such as user interviews, support-ticket analysis, concierge tests, or landing page demand tests. - Decision Thresholds & Bias Controls: Defines explicit validated/inconclusive/invalidated criteria plus safeguards against leading questions, confirmation bias, and solution enthusiasm. - Use Case: A founder has an idea for a freelancer invoicing tool but no proof the pain is real. Use this Skill to produce an interview script, participant criteria, evidence thresholds, and a decision path before scoping an MVP. ## Quick Start Use the problem-validation-planner skill to design a discovery and validation plan for my product idea before we start building it.
