skills.rest
CodeAlive-AI
CodeAlive-AIOFFICIAL
Explore all skills by this author →
WebsiteGitHub

problem-definition

Clarify product problems using structured framing and struggling-moment analysis.

3|Updated Mar 22, 2026
Search Tags:#product strategy#product discovery#problem framing#feature scoping#customer pain#jobs to be done
One-click install
npx skills add https://github.com/CodeAlive-AI/ceo-ai-os --skill problem-definition-codealive-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: problem-definition
Source: https://github.com/CodeAlive-AI/ceo-ai-os/tree/main/skills/problem-definition
Command: npx skills add https://github.com/CodeAlive-AI/ceo-ai-os --skill problem-definition-codealive-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams define the real problem before committing to a solution, especially when feature ideas are vague, technology-led, or not yet validated.

Core Features & Use Cases

  • Clarifies the user's struggling moment and desired outcome.
  • Separates customer pain from business goals so you avoid building customer-hostile solutions.
  • Guides feature scoping, product discovery, and idea validation using Jobs to Be Done and other product frameworks.
  • Example: Use it when a founder wants to add AI but cannot explain which user pain the feature solves.

Quick Start

Ask the problem-definition skill to help you turn your feature idea into a clear customer problem, then test whether it is urgent, specific, and worth solving.

Frequently Asked Questions about problem-definition

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

FAQPage Schema
How do I define the real user problem before committing to a feature solution?▼

Problem framing in product discovery clarifies the user's struggling moment and desired outcome, separating customer pain from business goals to produce an actionable problem statement before committing to a solution.

How do I validate a product idea using Jobs to Be Done?▼

Validating a product idea with Jobs to Be Done involves analyzing the customer's struggling moment and testing whether the pain is urgent, specific, and worth solving before committing development resources to the feature.

What is the best way to scope a feature when the idea is technology-led?▼

The best way to scope a technology-led feature is to apply customer-versus-business qualification, using structured problem framing to identify the actual user pain and desired outcome before defining the solution scope.

When do I need problem framing in product strategy?▼

You need problem framing in product strategy when feature ideas are vague, technology-led, or unvalidated, and you must clarify the struggling moment to avoid building customer-hostile solutions that lack real user pain.

How do I separate customer pain from business goals during product discovery?▼

Separate customer pain from business goals during product discovery by applying customer-versus-business qualification, which evaluates the user's struggling moment against business objectives to prevent customer-hostile solutions.

Related Skills

Explore More Product & Management Skills→
Lev-itLev-it

summarize-interview

Summarize customer interview transcripts into structured insights with Jobs to Be Done and action items.

Official
Intermediate
dhar174dhar174
1

prd

Generate structured Product Requirements Documents for software and AI features.

Community
Advanced
ncklrsncklrs
40

product-discovery

Guide product discovery and user research using Jobs-to-be-Done and opportunity scoring.

Community
Advanced
v1bh0rv1bh0r

nw-opportunity-mapping

Map customer insights to prioritized opportunities and solution ideas.

Community
Intermediate