What problem does it solve? Product teams routinely solve the wrong problem: feature requests get restated as problems, symptoms like churn get treated as causes, and business goals like "increase revenue" pose as user problems. This Skill turns a vague prompt, signal, metric, or feature request into a clear, testable problem statement that separates the real user gap from solutions, symptoms, goals, and constraints. ## Core Features & Use Cases - Problem framing core: Applies the always-true rules — a problem is a gap not a feature, root cause over symptom, specific and measurable, grounded in user evidence, and bridging user and business impact. - Context-gated decisions: Surfaces trade-offs for which definition tool to use (5 Whys, personas, journey maps, assumption mapping), how much measurability to add, reasoned vs. validated causes, and scope granularity. - Validation hand-offs: Routes the finished statement to assumption-rigor and metric-validity audits, and connects downstream to discovery, hypothesis testing, and spec writing. - Use Case: A stakeholder says "we need a better search feature." The Skill reframes it as "new users can't find relevant products because categories don't match how they think, so 40% leave without buying" — a falsifiable statement ready for validation. ## Quick Start Ask the assistant to turn your feature request or vague product concern into a proper problem statement using the problem statement skill.
