What problem does it solve? Teams often jump to solutions or mistake feature requests and business metrics for real user problems. This Skill structures problem framing around who the user is, what they are trying to do, what blocks them, the root cause, and how it feels, so stakeholders align on a problem worth solving before discovery, prioritization, or PRD work. ## Core Features & Use Cases - Empathy-Driven Framework: Structures problems as I am / Trying to / But / Because / Which makes me feel, grounded in Jobs-to-be-Done and empathy mapping. - Template and Examples: Ships a fill-in template plus good and bad worked examples showing how to fix solution-smuggled statements. - Pitfall Detection: Flags anti-patterns like disguised solutions, business problems framed as user problems, generic personas, and fabricated emotions. - Use Case: Before writing a PRD, synthesize user interview findings into a one-sentence problem statement such as an IT admin needing to provision accounts in under 5 minutes, then socialize it with stakeholders. ## Quick Start Use the problem-statement skill to turn my user interview notes into a user-centered problem statement for our onboarding drop-off issue.
