Agent skill

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.

product-on-purposegithub.com/product-on-purposeGitHub ↗
claude-codecodexApache-2.0
Install
npx skills add product-on-purpose/pm-skills --skill define-problem-statement --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 6
SKILL.md size: 4 KB
Bundled scripts: none
Version: 2.1.0
Declared author: product-on-purpose
Path: skills/define-problem-statement/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 518
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

<!-- 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 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 aske

What's inside
Steps it walks through
  1. When to Use
  2. When NOT to Use
  3. Instructions
  4. Output Format
  5. Quality Checklist
  6. Examples
Ships with 5 files
  • HISTORY.md
  • evals/output-scenarios/checkout-abandonment.md
  • evals/trigger-fixtures.json
  • references/EXAMPLE.md
  • references/TEMPLATE.md
More from pm-skills
All skills →
About this skill
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 it?

Run `npx skills add product-on-purpose/pm-skills --skill define-problem-statement --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From product-on-purpose/pm-skills, a repository with 518 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going