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. Use when framing discovery, prioritization, or a PRD.
Install
With your agent
Install OMGSkills skill "deanpeters/product-manager-skills:problem-statement" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/deanpeters/Product-Manager-Skills /tmp/Product-Manager-Skills && ln -s /tmp/Product-Manager-Skills/skills/problem-statement ~/.claude/skills/problem-statementFrom README
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.
More from this repo
acquisition-channel-advisor
Evaluate acquisition channels using unit economics, customer quality, and scalability.
ai-shaped-readiness-advisor
Assess whether your product work is AI-first or AI-shaped.
altitude-horizon-framework
Understand the PM-to-Director transition through altitude and horizon thinking.