problem-statement

Frame user research data into a problem narrative and final statement.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/EchoNoReturn/task-manager --skill problem-statement-echonoreturn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-statement
Source: https://github.com/EchoNoReturn/task-manager/tree/main/.agents/skills/problem-statement
Command: npx skills add https://github.com/EchoNoReturn/task-manager --skill problem-statement-echonoreturn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams articulate a user-centered problem by guiding them through a narrative structure that centers the user's perspective, clarifies barriers, emotions, and root causes, and yields a crisp, shareable problem statement to align stakeholders before solutioning.

Core Features & Use Cases

  • Guided problem framing: Step-by-step prompts to populate persona, outcomes, barriers, root causes, and emotional impact.
  • Context capture: Collects constraints and contextual factors to ensure realism and feasibility.
  • Single-sentence final problem statement: Produces a concise, empathetic problem statement that is easy to share with teams.
  • Applied templates and examples: Includes templates and examples to accelerate discovery sessions.

Quick Start

Provide user research context and personas to generate a complete problem framing narrative and a concise final problem statement.

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 problem statement from user research data?

Frame a user-centered problem statement from research data by capturing the persona, goals, blockers, root cause, and emotions into a narrative, then distill it into a single concise sentence for stakeholder alignment.

What is problem framing in product management?

Problem framing in product management is the process of structuring user research into a narrative that clarifies barriers and root causes, producing a concise problem statement to guide discovery, prioritization, and PRD contexts before solutioning begins.

How do I align stakeholders on a user problem before writing a PRD?

Align stakeholders before writing a PRD by generating a complete problem framing kit that includes a narrative, context and constraints, and a final shareable problem statement to ensure shared understanding.

What should a good problem statement include?

A good problem statement should include the user persona, their goals, specific barriers or blockers, the root cause of the issue, emotional impact, and relevant contextual constraints to ensure realism and empathy in product discovery.

Can I use guided templates for discovery sessions to frame user problems?

Yes, you can use applied templates and step-by-step prompts during discovery sessions to guide teams through populating personas, outcomes, barriers, and root causes, accelerating the creation of a final problem statement.