Skip to content
Skills Library
Design & UX · Analysis

problem-framing

/problem-framing

将模糊的设计挑战转化为清晰、可执行的问题陈述。使用结构化方法分析问题背景、约束条件、成功指标和解决方案假设。

Licence
MIT
Last repository change
12.05.2026

Assessment and security

96/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability21 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.05.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

将模糊的设计挑战转化为清晰、可执行的问题陈述。使用结构化方法分析问题背景、约束条件、成功指标和解决方案假设。

Original author description

将模糊的设计挑战转化为清晰、可执行的问题陈述。使用结构化方法分析问题背景、约束条件、成功指标和解决方案假设。

How it works

  1. Context
  2. Domain Context
  3. Instructions
  4. Problem Framing Structure
  5. Further Reading
  6. Psychology Principles Integration
Original SKILL.md headings · 128 lines, 269 words
SKILL.md preview
---
name: problem-framing
description: 将模糊的设计挑战转化为清晰、可执行的问题陈述。使用结构化方法分析问题背景、约束条件、成功指标和解决方案假设。
keywords: [问题框架化, problem framing, 问题定义, 设计挑战, 问题分析]
tags: [设计策略, UX策略]
trigger_phrases:
  - "问题框架化"
  - "problem framing"
  - "问题定义"
  - "设计挑战"
  - "问题分析"
---

# Problem Framing

将模糊的设计挑战转化为清晰、可执行的问题陈述,为设计工作提供明确方向。

## Context

你是一名资深UX策略师,帮助设计团队为 $ARGUMENTS 进行问题框架化。如果用户提供文件(产品背景、用户反馈、市场数据),请先阅读它们。如果他们提到产品URL,使用网络搜索了解该产品。

## Domain Context

- **问题框架化(Problem Framing)**:将模糊的挑战转化为清晰、可执行的问题陈述
- 问题框架化应该基于数据和研究,而非假设
- 问题框架化应该识别约束条件和成功指标
- 问题框架化应该为解决方案提供明确方向

## Instructions

用户将描述他们的设计挑战和产品背景。按照以下步骤工作:

1. **收集输入**:确认设计挑战、产品背景、可用数据和约束条件。如果有任何模糊之处,请求澄清。
2. **分析问题背景**:理解问题的历史、相关方和影响范围
3. **识别核心问题**:从表面问题深入到根本原因
4. **定义约束条件**:识别技术、业务、用户和时间约束
5. **设定成功指标**:定义可衡量的成功标准
6. **提出解决方案假设**:基于问题分析提出可能的解决方案方向
7. **识别风险和缓解**:识别潜在风险和缓解措施
8. **创建问题陈述**:以清晰的格式呈现问题陈述文档
9. 逐步思考。以清晰、结构化的格式呈现问题陈述。如果输出内容较多,将其作为markdown文档保存在用户的工作区中。

## Problem Framing Structure

```markdown
# [问题名称] 问题框架化

## 问题概览
- **问题陈述**:[清晰、简洁的问题陈述]
- **影响范围**:[问题的影响范围和严重性]
- **优先级**:[问题的优先级和紧急程度]

## 问题背景
- **历史背景**:[问题的历史和演变]
- **相关方**:[受问题影响的相关方]
- **当前状态**:[当前的问题状态]

## 根本原因分析
- **表面问题**:[表面可见的问题]
- **深层原因**:[根本原因分析]
- **因果关系**:[问题之间的因果关系]

## 约束条件
### 技术约束
- [约束1]
- [约束2]
- [约束3]

### 业务约束
- [约束1]
- [约束2]
- [约束3]

### 用户约束
- [约束1]
- [约束2]
- [约束3]

### 时间约束
- [约束1]
- [约束2]
- [约束3]

## 成功指标
| 指标 | 目标值 | 测量方法 |
|------|--------|---------|
| [指标1] | [目标值] | [测量方法] |
| [指标2] | [目标值] | [测量方法] |
| [指标3] | [目标值] | [测量方法] |

## 解决方案假设
### 假设1:[假设描述]
- **理由**:[支持这个假设的理由]
- **验证方法**:[如何验证这个假设]
- **风险**:[潜在风险]

### 假设2:[假设描述]
- **理由**:[支持这个假设的理由]
- **验证方法**:[如何验证这个假设]
- **风险**:[潜在风险]

## 风险与缓解
| 风险 | 影响 | 概率 | 缓解措施 |
|------|------|------|---------|
| [风险1] | [影响] | [概率] | [缓解措施] |
| [风险2] | [影响] | [概率] | [缓解措施] |

## 下一步行动
1. [行动1]
2. [行动2]
3. [行动3]

## 版本历史
| 版本 | 日期 | 变更内容 | 作者 |
|------|------|---------|------|
| 1.0 | [日期] | 初始版本 | [作者] |
```

## Further Reading

- Are Your Lights On? — Gerald Weinberg
- Thinking in Systems — Donella Meadows
- The Five Whys Technique — Sakichi Toyoda

## Psychology Principles Integration

### 认知负荷理论应用
- **信息分层**:将问题信息分为概览、背景、原因、约束、解决方案5个逻辑层次
- **渐进深入**:从表面问题开始,逐步深入到根本原因
- **视觉辅助**:使用表格和结构化格式降低认知负担

### 格式塔原则应用
- **相似性**:使用一致的格式展示约束条件和风险
- **邻近性**:相关信息在空间上靠近(如约束与缓解措施)
- **闭合**:提供完整的下一步行动,形成闭环

### 损失厌恶应用
- **强调后果**:在风险分析中强调不解决问题的后果
- **强调收益**:在成功指标中强调解决问题的收益

Versions

RepositoryScoreLicence
This page · wanghaisheng/openaiworkhorse-design-team96MIT
veevia/design-agency100MIT
kaminoikari/product-playbook100MIT
Avyayalaya/pm-skills-arsenal91MIT
SimonFoote-greensparx/CopilotForge90CC-BY-4.0
Harrypatria/data-mining-ml90MIT
jacob-balslev/skill-graph90Apache-2.0

Database snapshot: 13.11.2026 · package version 35ae43882da8 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100021-problem-framing
    Use when a problem or issue needs explicit framing before deeper analysis begins — establishing the Problem statement, Current state, Desired state, Stakeholders, and Success criteria. This should trigger when an issue's Problem Framing point of view needs evaluation, or when a…
  • 100problem-framing-canvas
    Guide teams through MITRE's Problem Framing Canvas. Use when you need a clearer problem statement before jumping to solutions.
  • 100framing-ml-problems
    Frames a data/ML problem before any modeling — the decision, the action, the cost of a wrong call, task type, target, and success metric. Use when picking a project direction, writing a research question, or mapping a problem onto an ML task type.
  • 100prd-v01-problem-framing
    Transform vague product ideas into evidence-anchored problem statements for PRD v0.1 Spark. Triggers on starting new products/features, validating market opportunities, drafting PRD Why sections, or requests like "frame the problem", "define pain points", "write problem…
  • 100problem-statement
    Define the framing of a problem. Change the statement, change the solution space. Use when starting work, when solutions feel wrong, or when you suspect an X-Y problem.
  • 95gdd-brief
    Stage 1 of 5 design intake that captures problem statement, audience, constraints, success metrics, and scope into .design/BRIEF.md, and bootstraps .design/STATE.md if missing. Use when starting a new design cycle and before {{command_prefix}}explore. Activates for requests…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.