Problem Statement
Write a crystal-clear problem statement that defines the user, pain, impact, and evidence before jumping to solutions. Produces a structured statement with user segment, current behavior, pain points, business impact, evidence, success criteria, and anti-scope. Use when aligning stakeholders on what to solve, before writing a PRD, when a team is jumping to solutions without defining the problem, or when framing a discovery initiative.
Install
/plugin marketplace add tarunccet/pm-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add tarunccet/pm-skills --skill problem-statementgit clone --depth 1 https://github.com/tarunccet/pm-skills.git /tmp/pm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-skills/pm-product-discovery/skills/problem-statement ~/.claude/skills/problem-statementPersonal 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: Define the Problem Before the Solution ## Purpose You are an experienced product manager helping a team articulate a clear, evidence-based problem statement for **$ARGUMENTS**. A well-written problem statement is the foundation of every good product decision — it aligns stakeholders, focuses discovery, and prevents solution-first thinking. ## Domain Context Problem statements sit at the very start of the product discovery process — before hypotheses, before experiments, before PRDs. In Teresa Torres's Opportunity Solution Tree framework, a problem statement maps to the **opportunity space**: it defines the unmet need the team will explore. Without a clear problem statement, teams build features nobody asked for, chase vanity metrics, or solve symptoms instead of root causes. A strong problem statement follows this structure: > "We believe **[user segment]** experiences **[problem]** when **[situation]**, which leads to **[impact]**. Currently, they **[workaround]**. Evidence: **[data points]**." ### What You'll Need | Input | Required? | Example | |-------|-----------|---------| | Problem area or observation | ✅ Required | "Users abandon onboarding at step 3" | | Target user segment | 🟡 Recommended | Mid-market SaaS teams, 50–200 employees | | Supporting data or research | 🟡 Recommended | Analytics, survey results, interview notes | | Business context or goals | ⚪ Optional | Q3 retention target, strategic initiative |
Details
- Skill name
problem-statement- Repository
- tarunccet/pm-skills
- Path
pm-product-discovery/skills/problem-statement/SKILL.md- License
- MIT
- Repo updated
- 13 November 2026
FAQ
What does the Problem Statement skill do?
Write a crystal-clear problem statement that defines the user, pain, impact, and evidence before jumping to solutions. Produces a structured statement with user segment, current behavior, pain points, business impact, evidence, success criteria, and anti-scope. Use when aligning stakeholders on what to solve, before writing a PRD, when a team is jumping to solutions without defining the problem, or when framing a discovery initiative.
How do I install the Problem Statement skill?
Claude Code plugin: /plugin marketplace add tarunccet/pm-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Problem Statement popular?
It lives in tarunccet/pm-skills, which has 9 GitHub stars and 2 forks.
Related skills
Ab Test Analysis
9tarunccet/pm-skills
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Adr
9tarunccet/pm-skills
Document architecture and product decisions using the Nygard ADR format — captures context, alternatives considered, and consequences so the team never asks 'why did we do it this way?' again. Use when making architecture decisions, choosing between technical approaches, selecting vendors, or any decision that will be hard to reverse.
AI Build Buy Partner
9tarunccet/pm-skills
Evaluate AI capability sourcing options across build, buy, fine-tune, and partner archetypes using a structured decision matrix. Use when deciding whether to build a custom model, use an LLM API, fine-tune a base model, or partner with an AI vendor.
Product Vision
9tarunccet/pm-skills
Brainstorm an inspiring, achievable, and emotional product vision that motivates teams and aligns stakeholders. Use when defining or refining a product vision, creating a vision statement, or aligning the team around a shared direction.
Metric Definition
9tarunccet/pm-skills
Define and distinguish operational, vanity, and actionable metrics. Write complete metric specs with name, definition, data source, calculation formula, owner, and review cadence. Use when formalizing metrics, building a metrics dictionary, or aligning a team on how metrics are measured.
Pywayne Crypto
9wangyendt/wayne-skills
Encryption and decryption toolkit for string and byte data. Supports Fernet (AES-128) symmetric encryption, fallback XOR encryption, custom password protection, code obfuscation, and batch processing. Use when users need to encrypt/decrypt sensitive data, protect algorithms, or obfuscate Python code.
Browse the most popular Claude skills, all finance & crypto skills, or write your own with the skills generator.