Problem Statement: AI Skill for Product Management
Problem Statement is an AI skill that turns vague prompts, feature requests, and moving metrics into clear, evidence-grounded problem statements. No solutions in disguise, no symptoms mistaken for causes.
npx skills add Uxcel-Lab/product-skills --skill pm-problem-statement
What this skill does
Turns prompts, requests, and moving metrics into a statement of the real problem before anyone builds a solution.
- Checks whether you hold a validated problem or a signal that only looks like one.
- Separates the problem from solutions, symptoms, goals, and constraints.
- Traces symptoms to the root cause with 5 Whys reasoning.
- Names who is affected, when it happens, and the concrete obstacle.
- Adds a measurable element so success is checkable and scope is bounded.
- Grounds the statement in interviews, support tickets, analytics, and session replays.
- Connects the user difficulty to its business impact.
- Hands off to metric-validity and assumption-rigor checks before you commit resources.
When to use it
Use it when you need an AI assistant to:
- write a problem statement from a vague prompt;
- turn a feature request into the problem beneath it;
- trace a moving metric to its root cause;
- frame a problem before writing a spec;
- sharpen a problem for an interview or case study;
- review a statement for solutions in disguise.
Decisions this skill helps you make
| Decision | Options |
|---|---|
| Definition tool | 5 Whys, the 4 Ws, journey map, empathy map, or assumption mapping |
| Measurability now | Add a metric once validated; skip guessed numbers in early framing |
| Cause rigor | Reasoned cause for early framing, evidence-validated before real resources |
| Assume vs. ask | State grounded assumptions; ask only what changes the framing |
| Scope | One group, situation, and difficulty, with room for several solutions |
How the skill works
1
Establish what you have
The skill checks whether you hold a validated problem or a signal, request, or metric.
2
Apply the core
It separates the problem from solutions and symptoms, then makes it specific, measurable, and evidenced.
3
Surface trade-offs
It presents the definition tool, measurability depth, and scope choices with a recommendation for each.
Try it with
Related skills
1.0.0
MIT
Product Management
Foundations
