problem-definition

Generate a Problem Definition Pack with JTBD, evidence, metrics, and scope.

51|8|Updated Jan 22, 2026

Search Tags:#user research #requirements gathering #scope definition #product discovery #problem definition #jtbd

Ready to run

npx skills add https://github.com/liqiongyu/lenny_skills_plus --skill problem-definition-liqiongyu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: problem-definition
Source: https://github.com/liqiongyu/lenny_skills_plus/tree/main/skills/problem-definition
Command: npx skills add https://github.com/liqiongyu/lenny_skills_plus --skill problem-definition-liqiongyu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill transforms vague user needs or business signals into a crisp, actionable Problem Definition Pack, ensuring alignment and focus before solutioning.

Core Features & Use Cases

Problem Framing: Clearly articulate the user problem, JTBD, and context.
Evidence & Assumptions: Log knowns and unknowns, with plans to validate.
Scope Definition: Set clear boundaries, success metrics, and guardrails.
Use Case: A product manager receives a vague request to "improve user engagement." They use this Skill to define the specific problem, identify the target user, map current alternatives, and propose a learning plan to validate hypotheses before building features.

Quick Start

Use the problem-definition skill to define the problem space for a new feature.

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 features?▼

To define a product problem before building features, you frame the user context, identify Jobs To Be Done (JTBD), and map current alternatives. This generates a structured Problem Definition Pack to ensure team alignment and focus prior to solutioning.

What is a Problem Definition Pack in product discovery?▼

A Problem Definition Pack in product discovery is a comprehensive artifact that articulates problem statements, logs evidence and assumptions, sets scope boundaries, and outlines prototype plans. It transforms vague business signals into actionable product requirements.

How do I gather requirements for a vague user engagement request?▼

To gather requirements for a vague user engagement request, identify the target user, map current alternatives, and define specific success metrics. Logging knowns and unknowns helps validate hypotheses and clarify scope before committing to feature development.

When do I need to use Jobs To Be Done for scope definition?▼

You need to use Jobs To Be Done (JTBD) for scope definition when receiving vague requests that require clear problem framing. JTBD helps articulate the specific user problem and context, allowing you to set guardrails and boundaries to prevent scope creep.

Best way to document assumptions and evidence during product discovery?▼

The best way to document assumptions and evidence during product discovery is to log knowns and unknowns systematically alongside your problem statement. This creates a validation trail and directly informs your proposed learning plans and success metrics.

Does problem framing work without clear success metrics and boundaries?▼

Problem framing does not work effectively without clear success metrics and boundaries. Defining scope guardrails and measurable success criteria is critical to ensure the problem statement remains focused and actionable for the product team.