problem-statement

Guide teams to describe personas, outcomes, blockers, causes, and emotions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nv-minh/superpower-agent --skill problem-statement-nv-minh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-statement
Source: https://github.com/nv-minh/superpower-agent/tree/main/templates/base/Product-Manager-Skills/skills/problem-statement
Command: npx skills add https://github.com/nv-minh/superpower-agent --skill problem-statement-nv-minh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams turn fuzzy requests into empathetic problem statements that call out who is blocked, what outcome they need, what gets in the way, why it matters, and how it feels, so the work stays grounded in real user outcomes.

Core Features & Use Cases

  • Structured narrative: Walks through persona, desired outcome, blockers, root cause, and emotional impact to align stakeholders before jumping to solutions.
  • Context & constraints: Encourages documenting geographic, technical, time, or demographic factors so decisions respect real-world limitations.
  • Validation guidance: Includes quality checks and a one-sentence synthesis to confirm the problem resonates with research and collaborators.

Quick Start

Draft a narrative by identifying the persona, outcomes, blockers, root cause, emotions, and a concise final summary to align everyone on the problem before solutioning.

Frequently Asked Questions about problem-statement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an empathetic problem statement for user research?

An empathetic problem statement clarifies who is blocked, their desired outcomes, blockers, root causes, and emotional impact. Structuring this narrative aligns stakeholders on real user outcomes before jumping to solutions.

What is the best way to align stakeholders during product discovery?

Stakeholder alignment during product discovery requires a structured narrative covering personas, outcomes, blockers, causes, and emotions. Synthesizing this into a concise problem statement keeps work focused on validated user needs.

How do I frame user problems using personas and root causes?

Framing user problems involves documenting the persona, desired outcome, technical blockers, and root cause. Adding context constraints like geographic or demographic factors ensures decisions respect real-world limitations.

Can I use a structured problem statement for PRDs and prioritization?

Yes, applying a structured problem statement during prioritization and PRDs keeps teams focused on user outcomes. It validates that documented blockers and emotional impacts resonate with research before solutioning begins.

What context constraints should I include when documenting user blockers?

Documenting user blockers should include geographic, technical, time, or demographic context constraints. Capturing these factors ensures that prioritization and solution decisions respect real-world limitations faced by the persona.

How do I validate a problem statement against user research?

Validating a problem statement involves running quality checks and synthesizing a one-sentence summary. This confirms the documented blockers, root causes, and emotional impacts resonate with collaborators and user research.