This does the unsexy but critical work of forcing you to articulate what problem you're actually solving before you build anything. It walks you through identifying a specific user segment (not just "users"), connecting their pain to business impact, and defining success metrics with baselines. The output follows a structured template covering user impact, business context, constraints, and open questions. Honestly, the best use case is when a project has drifted and you need to realign everyone, or when you're about to present to leadership and realize you can't clearly explain why this matters. It's built on frameworks like triple diamond and design thinking, which means it's opinionated about separating problem from solution.
npx -y skills add product-on-purpose/pm-skills --skill define-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