problem-statement

Articulate user problems using an empathy-driven persona framework.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/MMXC/openclaw-back --skill problem-statement-mmxc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-statement
Source: https://github.com/MMXC/openclaw-back/tree/main/pm-skills/skills/problem-statement
Command: npx skills add https://github.com/MMXC/openclaw-back --skill problem-statement-mmxc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you clearly articulate a user's problem from their perspective, ensuring that solutions are focused on genuine user needs and outcomes.

Core Features & Use Cases

  • Empathy-Driven Framework: Structures problems using a persona-centric narrative (I am, Trying to, But, Because, Makes me feel).
  • Contextualization: Incorporates relevant constraints and environmental factors.
  • Use Case: Before starting a new feature development, use this Skill to draft a concise problem statement that aligns the entire team on why the problem is important and who it affects.

Quick Start

Use the problem-statement skill to draft a problem framing narrative for a user who is trying to book a flight but is frustrated by complex interfaces.

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 problem statement for product discovery?

To write a user problem statement, articulate the user's perspective using an empathy-driven framework that captures the persona, desired outcomes, barriers, root causes, and emotional impact. This ensures solutions target genuine user needs.

What is the best way to align stakeholders on user-centered problems?

The best way to align stakeholders on user-centered problems is to draft a concise problem framing narrative that defines who the problem affects and why it matters, ensuring shared understanding before solutioning begins.

How do I use jobs to be done to frame a problem statement?

To use jobs to be done for framing a problem statement, provide structured input on user context and persona details. This generates a narrative capturing the user's goals, barriers, and emotional impact during product discovery.

When do I need to use an empathy-driven problem statement framework?

You need an empathy-driven problem statement framework before starting new feature development. It helps articulate user problems empathetically, ensuring the team focuses on genuine user needs and outcomes rather than premature solutioning.

What input is required to generate a concise problem statement?

Generating a concise problem statement requires structured input on user context, jobs-to-be-done, and persona details. This information structures the narrative to capture barriers, root causes, and emotional impact accurately.

Can I use this approach for stakeholder alignment without user empathy?

No, this approach relies heavily on user empathy to facilitate stakeholder alignment. It structures problems using a persona-centric narrative to ensure the team understands user constraints, barriers, and emotional impacts before solutioning.