define-problem-statement
This skill guides you through building a concise problem framing document that establishes shared understanding before solution work begins. It walks through identifying affected users, surfacing pain points, connecting to business impact, and defining measurable success criteria—ensuring your team solves the right problem rather than jumping to how.
define-problem-statement creates a structured problem framing document that aligns teams and leadership on what to solve before pursuing solutions.
AI-generated summary based on this skill's SKILL.md
Install
product-on-purpose/pm-skills/define-problem-statement · repository language: JavaScript
git clone https://github.com/product-on-purpose/pm-skills
cp -r pm-skills/skills/define-problem-statement ~/.claude/skills/define-problem-statementnpx skillfed install product-on-purpose/pm-skills/define-problem-statementFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I write a problem statement for a new project?
define-problem-statement guides you to build a concise framing document that establishes shared understanding before solution work begins. Start by identifying affected users and their pain points, then connect those to business impact. Define measurable success criteria so your team solves the right problem rather than jumping to how. The skill walks through each component systematically.
What should a problem statement include to align teams?
define-problem-statement emphasizes identifying affected users, surfacing their pain points, and connecting those to business impact. Include measurable success criteria so leadership and team members share the same definition of what winning looks like. This shared understanding prevents misalignment and ensures everyone focuses on solving the core problem before debating solutions.
How do I frame a problem for stakeholders?
define-problem-statement helps you communicate project priorities and rationale by structuring the problem with user impact and metrics. Present the affected user segments, their pain points, the business consequences, and your success metrics. This framing makes the problem tangible and justifies why solving it matters—giving stakeholders confidence in your direction.
When should I use a problem statement vs. a PRD?
define-problem-statement is your tool for establishing shared understanding before solution work begins. Use it early to align on what to solve and why. A PRD comes later, detailing how you'll build the solution. Problem statements prevent teams from drifting into the wrong solution; they're the foundation that makes your PRD more focused and effective.
How can define-problem-statement help realign a drifting project?
define-problem-statement lets you step back and reframe the core problem and intent. When projects drift, revisiting the original user pain points, business impact, and success metrics often reveals where the team lost focus. Use this skill to rebuild consensus around what you're actually solving, then course-correct before investing more effort in the wrong direction.
What role do success metrics play in a problem statement?
define-problem-statement teaches you to define measurable success criteria as part of your problem framing. Metrics transform vague goals into concrete targets—showing your team and leadership how you'll know the problem is solved. Without them, teams can't agree on what winning looks like, leading to misalignment and wasted effort.
SKILL.md
rendered from the published skill — quoted content, verbatim
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
Problem Statement
A problem statement is a concise document that frames the problem you're solving, articulates the impact on users and the business, and defines clear success criteria. It serves as the foundation for all subsequent product work by ensuring alignment on what problem to solve before jumping to how to solve it.
When to Use
- Starting a new initiative or project to establish shared understanding
- Realigning a drifted project back to its original intent
- Communicating up to leadership or stakeholders about priorities
- Evaluating whether a proposed solution actually addresses the core problem
- Onboarding new team members to
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 6 files
skills/define-problem-statement/HISTORY.md
skills/define-problem-statement/SKILL.md
skills/define-problem-statement/evals/output-scenarios/checkout-abandonment.md
skills/define-problem-statement/evals/trigger-fixtures.json
skills/define-problem-statement/references/EXAMPLE.md
skills/define-problem-statement/references/TEMPLATE.md