problem-definition

Guide users through structured problem-framing exercises to articulate user struggles.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/PSkinnerTech/lenny-skills --skill problem-definition-pskinnertech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-definition
Source: https://github.com/PSkinnerTech/lenny-skills/tree/main/skills/problem-definition
Command: npx skills add https://github.com/PSkinnerTech/lenny-skills --skill problem-definition-pskinnertech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Problem Definition helps teams articulate user problems clearly before moving to solutions, using proven frameworks from industry leaders.

Core Features & Use Cases

  • Structured problem framing: learn to separate problem from solution and identify the real user needs
  • Evidence-backed insight: leverage guest insights and user observation to ground problem statements
  • Use Case: when scoping a new feature, validating a product idea, or avoiding shiny-object traps

Quick Start

Prompt the user to articulate the current framing and run a structured problem framing exercise to identify the user's struggles.

Frequently Asked Questions about problem-definition

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define a product problem before building a solution?

To define a product problem, you must separate the problem from the solution and identify real user needs using structured problem framing frameworks. This ensures teams articulate user struggles clearly before scoping features.

What is structured problem framing in product management?

Structured problem framing is a product management process that uses proven frameworks to articulate user problems clearly. It helps teams identify struggling moments, validate urgency, and ground problem statements with evidence-backed insights.

How do I avoid shiny-object traps when scoping new features?

Avoid shiny-object traps by applying problem-framing frameworks to validate product ideas before development. This workflow enforces questions to identify real user struggles and validate urgency, ensuring features address actual needs.

How do I validate product opportunity and user urgency?

Validate opportunity and urgency by running a structured problem framing exercise that leverages guest insights and user observation. This process grounds problem statements in evidence to confirm the struggling moments are real.

Can I use problem framing to align cross-functional teams on feature scope?

Yes, problem framing aligns cross-functional teams by documenting clear problem statements before solutions are designed. Applying proven frameworks ensures all stakeholders understand the user needs and scope features accordingly.