problem-statement

Articulate a user-centered problem statement with persona context and constraints.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Articulate a user-centered problem statement from the user's perspective, capturing who they are, what they want to achieve, what's blocking them, why it matters, and how it feels.

Core Features & Use Cases

  • Structured narrative templates that frame the problem from the user’s point of view.
  • Guidance for context, constraints, and a final one-sentence problem statement suitable for alignment across teams.
  • Practical workflows for discovery, prioritization, and PRD framing.

Quick Start

Fill in the Problem Framing Narrative template to generate a user-centered problem statement.

Frequently Asked Questions about problem-statement

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

FAQPage Schema
What is a user-centered problem statement in product discovery?

A user-centered problem statement captures the user's perspective, desired outcomes, constraints, and feelings to align product teams. It defines who the user is, what they want to achieve, what blocks them, and why it matters.

How do I frame a problem statement for a PRD?

To frame a problem statement for a PRD, use a structured narrative template to articulate user context, constraints, and desired outcomes, culminating in a single one-sentence problem statement for team alignment.

How do I write a problem framing narrative for product teams?

Writing a problem framing narrative involves structuring the user's perspective into who they are, their goals, blockers, and emotional context, ensuring a structured narrative suitable for discovery and prioritization.

When do I need to use a structured problem statement during discovery?

You need a structured problem statement during discovery when aligning product teams on what to build. It ensures prioritization captures the user's actual perspective and constraints rather than assumptions.

What is the best way to align teams on a user problem?

The best way to align teams is generating a single final problem statement from a structured narrative. This captures the user's context and desired outcomes, ensuring clear communication across product teams.