problem-framing
A framework to clarify project goals by defining user needs, creating 'How Might We' questions, and validating against personas.
Install
mkdir -p .claude/skills/problem-framing && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5102" && unzip -o skill.zip -d .claude/skills/problem-framing && rm skill.zipInstalls to .claude/skills/problem-framing
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Frame problems using JTBD Job Stories, HMW questions, and persona validationKey capabilities
- →Define a Job Story with context, motivation, and outcome
- →Reframe a problem into a How Might We question
- →Fetch user persona details from a Notion database
- →Validate a problem against functional, emotional, and social dimensions
- →Output a structured problem framing document
How it works
The skill guides problem definition through a multi-phase process, starting with a Job Story, then reframing it into an HMW question, and finally validating it against user personas and three job dimensions.
Inputs & outputs
When to use problem-framing
- →Defining new product feature requirements
- →Reframing user pain points into opportunities
- →Aligning team members on project goals
About this skill
Problem Framing Skill
Frame problems effectively using Jobs-to-be-Done, How Might We questions, and persona validation from Notion.
When to Use
- At the start of DIVERGE loop (Ask mode)
- When exploring a new feature or problem space
- Before ideation to ensure clear problem definition
Instructions
Phase 1: Job Story Definition
Create a Job Story in this format:
When [situation/context],
I want to [motivation/action],
So I can [expected outcome/benefit].
Example:
When I'm managing multiple client workspaces,
I want to switch between them quickly,
So I can respond to urgent requests without losing context.
Phase 2: How Might We (HMW) Question
Reframe the problem as an opportunity question:
How might we [opportunity that addresses the job story]?
Guidelines:
- Start broad, then narrow if needed
- Avoid suggesting solutions in the question
- Focus on the user's goal, not the feature
Example:
How might we help users navigate between workspaces seamlessly?
Phase 3: Persona Lookup (Notion MCP)
Fetch relevant personas from Notion database:
-
Search for personas database:
API-post-search with query "Personas" or "User Personas" -
Query the database:
API-query-data-source with database_id from search results -
Get persona details:
API-retrieve-a-page + API-get-block-children for each relevant persona
Extract these fields:
- Name
- Role / Job Title
- Goals (what they want to achieve)
- Pain Points (what frustrates them)
- Context (environment, constraints)
Phase 4: Three Dimensions Check
Validate the problem addresses all three job dimensions:
| Dimension | Question | Example |
|---|---|---|
| Functional | What task are they completing? | "Switch between workspaces" |
| Emotional | How do they want to feel? | "In control, not overwhelmed" |
| Social | How do they want to be perceived? | "Responsive, professional" |
Output Format
After running this skill, output:
## Problem Framing
### Job Story
When [situation],
I want to [motivation],
So I can [outcome].
### How Might We
How might we [opportunity]?
### Relevant Personas
| Persona | Role | Goals | Pain Points |
|---------|------|-------|-------------|
| [Name] | [Role] | [Goals] | [Pain Points] |
### Three Dimensions
| Dimension | Definition |
|-----------|------------|
| Functional | [Task] |
| Emotional | [Feeling] |
| Social | [Perception] |
Invocation
Invoke manually with "use problem-framing skill" or follow Ask mode DIVERGE loop which references this skill's phases.
Related Skills
design-context- Run after problem-framingcompetitor-scan- Research how others solve this problem
Prerequisites
How it compares
This skill provides a structured, multi-faceted approach to problem definition, integrating user personas from Notion, unlike a manual process that might overlook critical validation steps.
Compared to similar skills
problem-framing side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| problem-framing (this skill) | 1 | 7mo | No flags | Beginner |
| product-manager-toolkit | 32 | 7mo | Review | Beginner |
| wayfinder | 0 | 29d | No flags | Advanced |
| spec-kit-workflow | 11 | 8mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by WellApp-ai
View all by WellApp-ai →You might also like
product-manager-toolkit
davila7
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
wayfinder
yqy2026
Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
notion-spec-to-implementation
openai
Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.
f2s-req-clarify
Lands-1203
针对 PRD/需求反问直到清楚,再可用 f2s-req-tech 出技术方案;触发:需求澄清、PRD 澄清
discovery-step-7-prd-authoring
nakamura1201
製品要求仕様書(PRD)を作成するスキル。背景と目的、ユーザーストーリー、機能要件、非機能要件、成功指標に加えて事業性(獲得チャネル・収益仮説・主要リスク)を統合する。開発着手前の最終仕様化依頼時に使う。