problem-statement

Generate user-centered problem statements with YAML frontmatter and narrative sections.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/RebelHawk-TK/DeepThinkTrader --skill problem-statement-rebelhawk-tk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-statement
Source: https://github.com/RebelHawk-TK/DeepThinkTrader/tree/main/.agents/skills/problem-statement
Command: npx skills add https://github.com/RebelHawk-TK/DeepThinkTrader --skill problem-statement-rebelhawk-tk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frame user problems in a structured, empathetic way to guide discovery and PRD work by translating user pain into an actionable problem framing narrative.

Core Features & Use Cases

  • Generates a complete Problem Framing Narrative from a user persona, including I am, Trying to, But, Because, and Which makes me feel sections.
  • Provides Context & Constraints and a Final Problem Statement to align stakeholders across teams.
  • Supplies a reusable Quick Start prompt to bootstrap immediate problem framing sessions.

Quick Start

Draft a complete problem framing narrative using the provided template.

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 product discovery?

A user-centered problem statement is generated by creating a structured narrative with sections for user identity, goals, obstacles, root causes, and emotional impact. This format translates user pain into actionable problem framing to align stakeholders during product discovery.

What is a problem framing narrative and when do I need it for a PRD?

A problem framing narrative is a structured empathy-driven format capturing who the user is, what they are trying to achieve, and the blockers they face. You need it for a PRD to ensure stakeholders share a clear understanding of the user problem before defining solutions.

How do I align stakeholders around a shared user problem?

Align stakeholders by generating a standardized problem framing narrative that includes user context, constraints, and a final problem statement. This structured approach translates empathy into a clear narrative, ensuring all teams understand the exact user pain being addressed.

Can I use a structured problem statement template for prioritization?

Yes, you can use a structured problem statement template for prioritization. By generating a clear narrative with defined user context and constraints, teams can evaluate and prioritize which user problems to address first based on the structured problem framing.

What is the best way to frame user pain into actionable product requirements?

The best way to frame user pain is by applying a standardized narrative template that captures user identity, goals, obstacles, root causes, and emotional impact. This approach translates empathy into a final problem statement ready for product requirements.