This is for when someone drops a feature request in your lap and you need to back up and figure out what problem you're actually solving. It walks you through a structured framework: who's blocked, what they're trying to do, what's stopping them, the root cause, and how it feels. The output is a one-sentence problem statement you can share with stakeholders before anyone starts building. It's heavy on the Jobs-to-be-Done angle and explicitly calls out anti-patterns like solution smuggling and generic personas. Use it to align teams during discovery or when kicking off a PRD, but only after you've done actual user research, not as a way to dress up assumptions.
npx -y skills add deanpeters/product-manager-skills --skill problem-statement --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
juliusbrussee/caveman
mattpocock/skills
shadcn/improve
obra/superpowers
forrestchang/andrej-karpathy-skills
vercel-labs/skills