What problem does it solve? Teams often jump to solutions before agreeing on the actual problem, producing requirements docs that smuggle in features, confuse business pain with user pain, or mistake symptoms for root causes. This Skill guides product managers through framing a problem from the user's perspective so the team aligns before anyone proposes a solution. ## Core Features & Use Cases - Structured narrative drafting: Builds the five-line I am / Trying to / But / Because / Which makes me feel narrative, with a dedicated test for each line, including the root-cause check that catches the commonest failure. - Facilitated discovery with collapse rule: Runs a question-budgeted facilitation loop, but collapses to extraction when a proto-persona or research summary already exists upstream, asking only about the missing root cause. - Validation gates and quality checks: Enforces five framing checks (solution smuggling, user-vs-business, root cause, emotion provenance, specificity) plus a read-aloud gate where the pass condition is "yes, exactly" from people who live the problem. - Use Case: A PM at a bank uses the Skill to frame why first-time disputers feel abandoned after reporting fraud, producing a Problem Framing Canvas whose root cause (an ops-only back-office queue) directly shapes the architecture discussion. ## Quick Start Use the problem-statement skill to draft a problem framing canvas for our cardholders who cannot see the status of their fraud disputes.
