Define Problem Statement

Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.

819 stars 104 forksFinance & Crypto Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add product-on-purpose/pm-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add product-on-purpose/pm-skills --skill define-problem-statement
Manual install
git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git /tmp/pm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-skills/skills/define-problem-statement ~/.claude/skills/define-problem-statement

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# 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 provide context

## When NOT to Use

- The problem is already agreed and engineering needs the spec -> use `deliver-prd`
- You want to propose and compare solution approaches -> use `develop-solution-brief`
- You are capturing customer motivation rather than a business problem -> use `define-jtbd-canvas`
- The "problem" is really an unvalidated assumption -> frame it with `define-hypothesis` and test it before committing a team to it

## Instructions

When asked to create a problem statement, follow these steps:

1. **Identify the User Segment**
   Ask who is experiencing this problem. Get specific about the user persona, role, or segment. Avoid vague descriptions like "users" - instead target "mobile shoppers completing checkout" or "enterprise admins managing 50+ users."

2. **Understand the Pain Points**
Read the full skill on GitHub

Details

Skill name
define-problem-statement
Path
skills/define-problem-statement/SKILL.md
License
Apache-2.0
Repo updated
17 November 2026

FAQ

What does the Define Problem Statement skill do?

Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.

How do I install the Define Problem Statement skill?

Claude Code plugin: /plugin marketplace add product-on-purpose/pm-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Define Problem Statement popular?

It lives in product-on-purpose/pm-skills, which has 819 GitHub stars and 104 forks, and is included in 2 curated skill lists.

Related skills

<phase or Classification Skill Name>

819

product-on-purpose/pm-skills

<single-line 20-100 word description; include trigger keywords and do not use folded YAML>

Skill & Plugin AuthoringIn 2 lists104

Define Hypothesis

819

product-on-purpose/pm-skills

Defines a testable hypothesis with clear success metrics and a validation approach. Use when forming assumptions to test or aligning a team on what success looks like, before any experiment is designed. To design the A/B test or experiment that will validate the hypothesis, use measure-experiment-design.

Finance & CryptoIn 2 lists104

Define Jtbd Canvas

819

product-on-purpose/pm-skills

Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job. Use when deeply understanding customer motivations, designing for jobs, or reframing product positioning.

Frontend & DesignIn 2 lists104

Backlog Refinement

1.2k

borghei/Claude-Skills

Grade stories against INVEST, split them vertically or as tracer bullets, and enforce Definition of Ready and Done. Use when refining a backlog, splitting an oversized story, or checking sprint readiness.

Finance & CryptoIn 1 list217

Define Opportunity Tree

819

product-on-purpose/pm-skills

Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery. Use when structuring scattered feature ideas or communicating how the roadmap traces to outcomes. For ranking an existing flat list of candidates, use define-prioritization-framework instead; this skill discovers the list, it does not score one.

Finance & CryptoIn 2 lists104

Board Deck Builder

1.2k

borghei/Claude-Skills

Assembles board and investor update decks by pulling perspectives from all C-suite roles. Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives.

Finance & CryptoIn 1 list217

Browse the most popular Claude skills, all finance & crypto skills, or write your own with the skills generator.