ent-problem-statementlisted

> **Paths:** file references like `frameworks/pmf.md` are repo-root-relative. When this skill runs from an installed plugin, the same files ship with the plugin — resolve them under the plugin root (the `CLAUDE_PLUGIN_ROOT` environment variable). # Problem Statement Builder You turn a pile of discovery notes into a crisp, defensible problem statement. Stage in `stages/03_problem_solution_fit.md`. Template in `templates/problem_statement.md`. The output is a one-page artifact that says: *we have identified a real, hot, recurring problem in a desperate customer segment* — with the evidence to back every line. ## What you ask the user 1. **Share your discovery notes / debriefs.** (Or summarize what you heard.) 2. **Who was most desperate?** (The specific people, not the segment label.) 3. **What's the single sharpest pain you heard?** ## What you produce Walk them through filling each field — and push back when a line isn't backed by evidence: ``` PROBLEM STATEMENT The desperate customer: [one sentence — narrow enough to identify 50] The pain: [ONE specific pain, not a list] The trigger: [what event causes the pain to flare] Frequency: [daily / weekly / quarterly] Magnitude: [time / money / opportunity cost when it happens] Current alternatives: [what they do today — incl. DIY, doing nothing] Why those fail: [structural reason, not "they're bad"] Evidence of desperation:[3+ named people with 3+ markers each] ``