problem-statement
Write a user-centered problem statement with who is blocked, what they are trying to do, why it matters, and how it feels
Install / Use
npx skills add deanpeters/Product-Manager-Skills --skill problem-statementInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of problem-statement
problem-statement scores 95/100 on our quality scale, 356th of 4,698 Development & Engineering skills we index (top 8%).
Its SKILL.md is 11 KB long, well organised into 29 sections with 4 code examples: a thorough specification that gives an agent plenty to work with.
With 7,063 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 3 months ago, so problem-statement is actively maintained.
- Our last check on 2026-11-15 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-28. Automated pattern scan on 2026-09-28. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
problem-statement compared with similar skills
All 4 of these similar skills score higher than problem-statement; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| problem-statement (this skill)by deanpeters | 95 | 7.1k | 3mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install problem-statement?
- Run
npx skills add deanpeters/Product-Manager-Skills --skill problem-statement. The install tabs above show the steps for each supported agent. - Which AI agents does problem-statement work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is problem-statement safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is problem-statement still maintained?
- The repository was last updated about 3 months ago, so problem-statement is actively maintained.
Skill content
View source on GitHubname: problem-statement argument-hint: "[user and their struggle]" description: Write a user-centered problem statement with who is blocked, what they are trying to do, why it matters, and how it feels. Use when framing discovery, prioritization, or a PRD. intent: >- Articulate a problem from the user's perspective using an empathy-driven framework that captures who they are, what they're trying to do, what's blocking them, why, and how it makes them feel. Use this to align stakeholders on the problem before jumping to solutions, and to frame product work around user outcomes rather than feature requests. type: component theme: discovery-research best_for:
- "Framing a problem before anyone proposes a solution"
- "Getting a team to agree on who is blocked and why it matters"
- "Turning a vague complaint into something a team can act on" scenarios:
- "The team keeps jumping to solutions and we've never written down the actual problem"
- "I need a crisp problem statement for a PRD that a skeptical exec will read" estimated_time: "10-20 min"
Purpose
Articulate a problem from the user's perspective using an empathy-driven framework that captures who they are, what they're trying to do, what's blocking them, why, and how it makes them feel. Use this to align stakeholders on the problem before jumping to solutions, and to frame product work around user outcomes rather than feature requests.
This is not a requirements doc—it's a human-centered problem narrative that ensures you're solving a problem worth solving.
Input
Works best with: Who the user is and what they're struggling to do. Also useful: What's blocking them, why it matters, how it feels, and supporting evidence.
Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.
Arriving empty-handed? That works too. The skill asks for the user and their goal first — a problem statement without a specific 'who' is a solution looking for cover.
Example invocation: Problem statement: clinic schedulers double-book exam rooms because the calendar doesn't show equipment availability.
Key Concepts
The Problem Framing Framework
Based on Jobs-to-be-Done and empathy mapping, the framework structures problems as:
Problem Framing Narrative:
- I am: [Describe the persona experiencing the problem]
- Trying to: [Desired outcomes the persona cares about]
- But: [Barriers preventing the outcomes]
- Because: [Root cause of the problem]
- Which makes me feel: [Emotional impact]
Context & Constraints:
- [Geographic, technological, time-based, demographic factors]
Final Problem Statement:
- [Single, concise, empathetic summary]
Why This Structure Works
- Persona-centric: Forces you to see the problem through the user's eyes
- Outcome-focused: "Trying to" emphasizes desired results, not tasks
- Root cause analysis: "Because" pushes past symptoms to underlying issues
- Emotional validation: "Makes me feel" humanizes the problem and builds empathy
- Contextual: Constraints acknowledge real-world limitations
Anti-Patterns (What This Is NOT)
- Not a solution in disguise: "The problem is we lack AI-powered analytics" = sneaking in a solution
- Not a business problem: "Our revenue is down" isn't a user problem (it's a symptom)
- Not a feature request: "Users need a dashboard" isn't a problem (what are they trying to do?)
- Not generic: "Users want better UX" is too vague to be actionable
When to Use This
- Kicking off discovery or problem validation work
- Aligning stakeholders before solutioning
- Socializing a problem with engineering, design, or exec teams
- When you have feature requests but unclear underlying problems
- Pitching why a problem is worth solving
When NOT to Use This
- When you haven't done any user research yet (don't guess—interview first)
- For internal operational problems (this is for user-facing problems)
- As a substitute for a PRD (this frames the problem; PRD defines the solution)
Application
Use template.md for the full fill-in structure.
Step 1: Gather User Context
Before drafting, ensure you have:
- User interviews or research: Direct quotes, observed behaviors, pain points
- Jobs-to-be-Done insights: What users are "hiring" your product to do (reference
skills/jobs-to-be-done/SKILL.md) - Persona clarity: Who specifically experiences this problem (reference
skills/proto-persona/SKILL.md) - Constraints data: Geographic, tech, time, demographic limitations
If missing context: Run discovery interviews, contextual inquiries, or user shadowing. Don't fabricate problems.
Step 2: Draft the Problem Framing Narrative
Fill in the template from the persona's point of view:
## Problem Framing Narrative
**I am:** [Describe the key persona, highlighting 3-4 key characteristics]
- [Key pain point or characteristic 1]
- [Key pain point or characteristic 2]
- [Key pain point or characteristic 3]
**Trying to:**
- [Single sentence listing the desired outcomes the persona cares most about]
**But:**
- [Describe the barriers preventing the persona from achieving outcomes]
- [Job-to-be-done or outcome obstruction 1]
- [Job-to-be-done or outcome obstruction 2]
- [Job-to-be-done or outcome obstruction 3]
**Because:**
- [Describe the root cause empathetically]
**Which makes me feel:**
- [Describe the emotions from the persona's perspective]
Quality checks:
- "I am" specificity: Can you picture this person? Or is it generic ("busy professionals")?
- "Trying to" clarity: Is this an outcome (measurable) or a task (activity)?
- "But" depth: Are these real barriers or just inconveniences?
- "Because" honesty: Is this the root cause or just a symptom?
- "Makes me feel" authenticity: Do these emotions come from research or assumptions?
Step 3: Document Context & Constraints
## Context & Constraints
- [Enumerate geographic, technological, time-based, or demographic factors]
- [e.g., "Must work offline in rural areas with limited connectivity"]
- [e.g., "Used by non-technical users unfamiliar with complex software"]
- [e.g., "Time-sensitive: decisions must be made within 24 hours"]
Quality checks:
- Relevance: Do these constraints directly impact the problem?
- Specificity: Are they concrete enough to inform design decisions?
Step 4: Craft the Final Problem Statement
Synthesize the narrative into one powerful sentence:
## Final Problem Statement
[Single, concise statement that provides a powerful and empathetic summary]
Formula: [Persona] needs a way to [desired outcome] because [root cause], which currently [emotional/practical impact].
Example: "Enterprise IT admins need a way to provision user accounts in under 5 minutes because current processes take 2+ hours with manual approvals, which causes project delays and frustrated end-users."
Quality checks:
- One sentence: If it requires multiple sentences, the problem isn't crisp yet
- Measurable: Can you tell if you've solved it?
- Empathetic: Does it resonate emotionally?
- Shareable: Could you say this in a meeting and have stakeholders nod?
Step 5: Validate and Socialize
- Test with users: Read it aloud to people who experience the problem. Do they say "Yes, exactly!"?
- Share with stakeholders: Product, engineering, design, exec. Does it align everyone?
- Iterate based on feedback: If anyone says "I don't think that's the real problem," dig deeper.
Examples
See examples/sample.md for full examples (good and bad problem statements).
Mini example excerpt:
**I am:** A software developer on a distributed team
**Trying to:** Communicate in real-time with my team without losing context
**But:** Email is too slow and IM is ephemeral
**Because:** No tool combines real-time chat with searchable history
**Which makes me feel:** Frustrated and disconnected
Common Pitfalls
Pitfall 1: Solution Smuggling
Symptom: "The problem is we don't have [specific feature]"
Consequence: You've predetermined the solution without validating the problem.
Fix: Reframe around the user's desired outcome, not the feature. Ask "What are they trying to achieve?"
Pitfall 2: Business Problem Disguised as User Problem
Symptom: "Users want to increase our revenue" or "The problem is our churn rate"
Consequence: These are company problems, not user problems. Users don't care about your metrics.
Fix: Dig into why users churn or what would make them spend more. Frame it from their perspective.
Pitfall 3: Generic Personas
Symptom: "I am a busy professional trying to be more productive"
Consequence: Too broad to be actionable. Every product claims to help "busy professionals."
Fix: Get specific. "I am a sales rep managing 50+ leads manually in spreadsheets, trying to prioritize follow-ups without missing high-value opportunities."
Pitfall 4: Symptom Instead of Root Cause
Symptom: "Because the UI is confusing"
Consequence: You're describing a symptom, not the underlying issue.
Fix: Ask "Why is the UI confusing?" Keep asking "why" until you hit the root cause (e.g., "Because users have no mental model for how the system works").
Pitfall 5: Fabricated Emotions
Symptom: "Which makes me feel empowered and delighted"
Consequence: These sound like marketing copy, not real user emotions.
Fix: Use actual quotes from user interviews. Real emotions: "frustrated," "overwhelmed," "anxious," "stuck."
References
Related Skills
skills/jobs-to-be-done/SKILL.md— Informs the "Trying to" and "But" sectionsskills/proto-persona/SKILL.md— Defines the "I am" personaskills/positioning-statement/SKILL.md— Problem statement informs positioningskills/user-story/SKILL.md— Problem statement guides story prioritization
External Frameworks
- Clayton Christensen, Jobs to Be Done — Origin of outcome-focused problem framing
- Osterwalder & Pigneur, Value Proposition Canvas — Customer pains/gains/jobs
- Dave Gray, Empathy Mapping — Emotional framing techniques
Dean's Work
- [Link to relevant Dean Peters' Substack articles if applicable]
Provenance
- Adapted from
prompts/framing-the-problem-statement.mdin thehttps://github.com/deanpeters/product-manager-promptsrepo.
Skill type: Component
Suggested filename: problem-statement.md
Suggested placement: /skills/components/
Dependencies: References skills/jobs-to-be-done/SKILL.md, skills/proto-persona/SKILL.md
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
