skills.rest
viktorbezdek
viktorbezdekCOMMUNITY
Explore all skills by this author →
𝕏@viktorbezdekGitHub

problem-definition

Frame solution-shaped product briefs into Who/Context/Job/Current/Gap/Why now/Assumptions/Not-goals problem statements.

10|2|Updated Mar 12, 2026
Search Tags:#assumptions#root-cause#5-whys#problem-framing#problem-statement#jtbd
One-click install
npx skills add https://github.com/viktorbezdek/skillstack --skill problem-definition-viktorbezdek
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: problem-definition
Source: https://github.com/viktorbezdek/skillstack/tree/main/product-thinking/skills/problem-definition
Command: npx skills add https://github.com/viktorbezdek/skillstack --skill problem-definition-viktorbezdek

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Many teams leap from a brief to a proposed solution without clarifying the underlying problem, which leads to wasted engineering effort and misaligned outcomes. This Skill helps teams separate symptoms from problems, surface hidden assumptions, and produce a concise problem statement that names who is affected, the context, the job to be done, the measurable gap, and why action is urgent now.

Core Features & Use Cases

  • Symptom vs Problem Separation: Distinguish observable symptoms (metrics or complaints) from the root problem that must be solved.
  • JTBD Framing: Convert briefs into When/I-want-to/So-I-can job statements covering functional, emotional, and social dimensions.
  • 5-Whys Ladder: Run a disciplined five-whys escalation to surface structural constraints and stop conditions.
  • Problem Statement Template: Produce a Who/Context/Job/Current/Gap/Why now/Assumptions/Not-goals template for clear decision criteria.
  • Red Flags & Anti-patterns: Call out common failures (solution-shaped briefs, vague segments, missing triggers) and recommend next steps.
  • Use Cases: Reframe feature-shaped PM requests, align teams debating designs, clarify churn/signal-root causes before ideation.

Quick Start

Use the problem-definition skill to turn a solution-shaped brief into a Who/Context/Job/Current/Gap/Why now/Assumptions/Not-goals problem statement and run a 5-whys ladder to surface the root constraint.

Frequently Asked Questions about problem-definition

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

FAQPage Schema
How do I write a clear problem statement from a vague product brief?▼

To write a clear problem statement from a vague brief, frame the request using a Who/Context/Job/Current/Gap/Why now/Assumptions/Not-goals template to separate observable symptoms from the underlying root constraint and align team outcomes.

What is the 5-whys technique for root-cause analysis in product discovery?▼

The 5-whys technique for root-cause analysis runs a disciplined escalation ladder asking 'why' repeatedly to surface structural organizational or product constraints, moving past surface metrics like churn to find the true problem to solve.

How do I separate product symptoms from the actual root problem?▼

Separating product symptoms from the actual root problem requires distinguishing observable metrics or complaints from the structural constraint causing them, using a disciplined 5-whys ladder and JTBD framing to validate underlying assumptions.

When should I use Jobs-to-be-Done framing for product discovery?▼

Use Jobs-to-be-Done framing during product discovery when converting ambiguous or solution-shaped briefs into When/I-want-to/So-I-can statements, ensuring you capture functional, emotional, and social dimensions of the user's job.

What are common anti-patterns when defining a product problem statement?▼

Common anti-patterns when defining a product problem statement include starting with solution-shaped briefs, targeting vague customer segments, and missing contextual triggers, which lead to wasted engineering effort and misaligned outcomes.

How do I align teams debating design decisions during product discovery?▼

Align teams debating design decisions by framing the discussion around a shared problem statement template that names who is affected, the job to be done, the measurable gap, and explicit not-goals to set clear decision criteria.

Related Skills

Explore More Product & Management Skills→
supermalangsupermalang

discovery

Clarify product requirements and generate a structured PRD.

Community
Advanced
cagdotincagdotin
36

to-prd

Generate a complete PRD document from conversation and codebase context.

Community
Advanced
Celia-12Celia-12

design-thinker

Apply design thinking frameworks to define user problems and generate validated solutions.

Community
Intermediate
v1bh0rv1bh0r

nw-opportunity-mapping

Map customer insights to prioritized opportunities and solution ideas.

Community
Intermediate