problem-statement

Create a structured problem framing narrative from user research inputs.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/MiDouTech/myTapd --skill problem-statement-midoutech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-statement
Source: https://github.com/MiDouTech/myTapd/tree/main/.claude/skills/problem-statement
Command: npx skills add https://github.com/MiDouTech/myTapd --skill problem-statement-midoutech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams articulate a clear, user-centered problem narrative that explains who is blocked, what they are trying to achieve, what barriers they face, the root cause, and the emotional impact. It prevents jumping to solutions too early and aligns product, design, and engineering around measurable user outcomes.

Core Features & Use Cases

  • Problem Framing Template: A structured "I am / Trying to / But / Because / Which makes me feel" narrative to capture persona-driven problems.
  • Context & Constraints Guidance: Prompts to document geographic, technical, time, and demographic limits that affect the problem and potential solutions.
  • Examples & Quality Checks: Example good/bad statements and checklists to validate specificity, root-cause focus, and emotional authenticity for discovery, prioritization, and PRD alignment.

Quick Start

Draft a concise problem statement using the Problem Framing Narrative for a persona from recent user interviews, capturing persona, desired outcome, barriers, root cause, and emotional impact in one clear sentence.

Frequently Asked Questions about problem-statement

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

FAQPage Schema
How do I write a user-centered problem statement for a PRD?

A user-centered problem statement articulates who is blocked, their desired outcome, barriers faced, root cause, and emotional impact. Using a structured narrative template ensures teams align around validated user outcomes rather than premature solutions.

What is the best way to frame a problem from user research interviews?

Framing a problem from user research involves applying an "I am / Trying to / But / Because / Which makes me feel" narrative template. This translates raw interview quotations into a structured narrative capturing persona, barriers, root causes, and emotional authenticity.

How do I translate feature requests into validated user outcomes during discovery?

Translating feature requests into validated user outcomes requires articulating a single-sentence problem statement that captures persona context and barriers. This shifts product discovery focus from requested solutions toward underlying root causes and emotional impacts.

Can I document technical and demographic constraints when defining a problem statement?

Yes, you can document geographic, technical, time, and demographic constraints when defining a problem statement. Capturing these limits provides necessary context that affects the problem space and guides potential solution discovery.

Why does my team struggle with stakeholder alignment on product discovery?

Stakeholder alignment fails when teams lack a concise, empathetic problem narrative. Without documenting persona barriers, root causes, and emotional impacts, stakeholders often jump to premature solutions instead of aligning around measurable user outcomes.

How do I check if my problem statement is specific enough for prioritization?

To check if a problem statement is specific enough for prioritization, validate it against quality checklists for specificity, root-cause focus, and emotional authenticity. Comparing against good and bad examples ensures it accurately frames the user's barriers.