Back to Details

problem-framing

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Problem Framing

问题框架

Transform raw product ideas into structured context that coding agents can execute on.
将原始产品想法转化为编码Agent可执行的结构化上下文。

Why This Exists

设计初衷

Extracts fuzzy product ideas from the user's head and structures them into clear problem statements, target users, and assumptions that coding agents can execute against.
从用户的想法中提取模糊的产品思路，将其结构化成为清晰的问题陈述、目标用户和假设，供编码Agent执行使用。

Workflow

工作流

Step 1: Gather Raw Input

步骤1：收集原始输入

Ask the user to share their idea in any form—plain text, voice dump, bullet points, or existing notes. Accept whatever they have.
请用户以任意形式分享他们的想法——纯文本、语音转写内容、要点列表或是现有笔记均可，接纳用户提供的所有内容。

Step 2: Run the Question Flow

步骤2：执行提问流程

Work through these questions conversationally. Skip or adapt based on what the user has already provided.
QuestionPurpose
What are you trying to build?Get the raw idea out
Who specifically is this for?Force specificity—"everyone" = no one
What problem does this solve for them?Separate solution from problem
What are they doing today without this?Reveals current alternatives, competition
When does this problem hit hardest?Identifies trigger moments, urgency
What assumptions are you making?Surfaces risks early
How will you know this worked?Defines success criteria
Questioning style:
  • Ask one question at a time
  • Probe vague answers ("Can you be more specific about who?")
  • Reflect back what you hear to confirm understanding
  • Don't overwhelm—adapt based on what's already clear
以对话形式梳理以下问题，根据用户已经提供的内容跳过或调整相关问题。
问题目的
你想要构建什么产品？梳理出原始想法
这款产品的具体目标人群是谁？强制明确针对性——“所有人”等于没有目标人群
它为目标人群解决了什么问题？区分解决方案和实际问题
没有这款产品的话，他们当前是怎么处理相关需求的？挖掘现有替代方案、竞品情况
这个问题在什么时候表现得最突出？明确触发场景、紧急程度
你做了哪些假设？提前暴露风险
你如何判断产品是否达成目标？定义成功标准
提问风格：
  • 一次只提一个问题
  • 针对模糊的回答进一步追问（“你能更具体地说明目标人群是谁吗？”）
  • 复述你接收到的信息来确认理解是否正确
  • 不要给用户造成负担——根据已经明确的内容灵活调整

Step 3: Generate Output

步骤3：生成输出

Once you have enough context, generate the structured output below. Automatically save it to 
design/01-problem-framing.md
using the Write tool while continuing the conversation naturally.
当你获取到足够的上下文后，生成下方的结构化输出。使用Write工具自动将其保存到
design/01-problem-framing.md
，同时自然地继续对话。

Output Format

输出格式

markdown
undefined
markdown
undefined

Problem Framing: [Project Name]

Problem Framing: [Project Name]

Problem Statement

Problem Statement

[One clear sentence: WHO has WHAT problem WHEN]
[One clear sentence: WHO has WHAT problem WHEN]

Target User

Target User

[Specific description—not "everyone" or "users"]
[Specific description—not "everyone" or "users"]

Jobs to Be Done

Jobs to Be Done

  • Functional: [What they're trying to accomplish]
  • Emotional: [How they want to feel]
  • Social: [How they want to be perceived]
  • Functional: [What they're trying to accomplish]
  • Emotional: [How they want to feel]
  • Social: [How they want to be perceived]

Current Alternatives

Current Alternatives

[What they do today without your solution]
[What they do today without your solution]

Trigger Moments

Trigger Moments

[When does this problem hit hardest?]
[When does this problem hit hardest?]

Key Assumptions

Key Assumptions

  • [Assumption 1]
  • [Assumption 2]
  • [Assumption 3]
  • [Assumption 1]
  • [Assumption 2]
  • [Assumption 3]

Success Criteria

Success Criteria

  • [How you'll measure if this works]
  • [How you'll measure if this works]

Open Questions

Open Questions

  • [Anything still unclear or needing validation]
undefined
  • [Anything still unclear or needing validation]
undefined

Handoff

交接

After presenting the output, ask:
"This captures your problem framing. Ready to move to 
/user-modeling
, 
/solution-scoping
, or 
/prd-generation
, or want to refine anything first?"
Note: File is automatically saved to 
design/01-problem-framing.md
for context preservation.
展示输出内容后，询问用户：
“以上内容梳理了你的问题框架。你是想要继续进行 
/user-modeling
、
/solution-scoping
或是 
/prd-generation
，还是先调整优化现有内容？”
注意： 文件会自动保存到
design/01-problem-framing.md
以保留上下文。