problem-framinglisted

## Purpose Produce a **Problem Definition Document** — a structured artifact that decomposes a vague or assumed problem into an evidence-graded problem statement with identified stakeholders, quantified opportunity size, mapped constraints, and prioritized sub-problems. This is the upstream skill that feeds every downstream PM activity: Discovery, Competitive Analysis, Spec Writing, and Metric Design. The output is not a brief or a pitch — it is a rigorous decomposition that forces the question "What exactly are we solving and for whom?" to be answered with evidence, not assumption. ## When to Use / When NOT to Use **Use this skill when:** - A stakeholder says "we should build X" and you need to determine whether X solves a real problem - You have a vague problem area ("user retention is bad") that needs decomposition into solvable sub-problems - Multiple teams disagree on what the real problem is — you need a shared, evidence-graded definition - You are starting a new product initiative and need to define the problem space before Discovery or Competitive Analysis - A feature request arrives disguised as a problem statement and you need to peel back to the actual user pain - You need to prioritize across multiple candidate problems with limited resources - An existing product is underperforming and nobody agrees on why **Do NOT use this skill when:** - The problem is already well-defined and validated — you need a spec, not more framing (use Spec Writing) - You need to un