Back to Details

problem-statement

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Problem Statement

问题陈述

Create a 
PROBLEM.md
document that clearly defines what problem is being solved and what success looks like.
创建一份
PROBLEM.md
文档，清晰定义要解决的问题以及成功的标准。

Workflow

工作流程

1. Gather Input

1. 收集输入

Ask the user for one of:
  • Jira ticket: Use the Atlassian MCP tools to fetch ticket details (
    mcp__plugin_atlassian_atlassian__getJiraIssue
    )
  • Document link: Fetch and extract relevant context
  • Text description: User provides details directly
If input is sparse, ask clarifying questions:
  • Who is affected by this problem?
  • What's the current behavior vs expected behavior?
  • Why does this matter now?
请用户提供以下其中一种输入：
  • Jira工单：使用Atlassian MCP工具获取工单详情（
    mcp__plugin_atlassian_atlassian__getJiraIssue
    ）
  • 文档链接：获取并提取相关背景信息
  • 文本描述：用户直接提供详细信息
若输入内容不够详细，询问以下澄清问题：
  • 哪些群体受该问题影响？
  • 当前行为与预期行为有何差异？
  • 为何现在需要解决这个问题？

2. Generate PROBLEM.md

2. 生成PROBLEM.md

Create the document at project root using this structure:
markdown
undefined
在项目根目录创建该文档，采用以下结构：
markdown
undefined

Problem Statement: [Concise Title]

Problem Statement: [Concise Title]

Problem

Problem

What's broken or missing? Who is affected? Be specific.
What's broken or missing? Who is affected? Be specific.

Context

Context

Background information. Current state. Why this matters now. Include relevant technical context if applicable.
Background information. Current state. Why this matters now. Include relevant technical context if applicable.

Desired Outcome

Desired Outcome

What does success look like? What should be true when this is done? Describe the end state, not the solution.
What does success look like? What should be true when this is done? Describe the end state, not the solution.

Success Criteria

Success Criteria

Measurable or verifiable conditions that confirm the problem is solved.
  • Criterion 1
  • Criterion 2
  • Criterion 3
Measurable or verifiable conditions that confirm the problem is solved.
  • Criterion 1
  • Criterion 2
  • Criterion 3

Out of Scope

Out of Scope

What this work does NOT address. Helps prevent scope creep.
undefined
What this work does NOT address. Helps prevent scope creep.
undefined

3. Open in Typora

3. 在Typora中打开

After creating PROBLEM.md, open it for the user:
bash
open -a Typora PROBLEM.md
创建PROBLEM.md后，为用户打开该文档：
bash
open -a Typora PROBLEM.md

4. Offer Next Steps

4. 提供后续选项

After opening the document, ask the user:
"I've created PROBLEM.md. Would you like me to:
  1. Review for gaps - Check for unclear areas, missing context, or weak success criteria
  2. Expand to PRD - Run 
    /prd
    to create a full Product Requirements Document
  3. Done - Proceed with the problem statement as-is"
If review is requested:
  • Check that the problem is clearly articulated (not solution-focused)
  • Verify success criteria are measurable/verifiable
  • Identify any ambiguous terms or assumptions
  • Suggest improvements and offer to update the document
打开文档后，询问用户：
"我已创建PROBLEM.md文档。请问您需要我：
  1. 检查遗漏内容 - 检查表述模糊、背景缺失或成功标准不够明确的地方
  2. 扩展为PRD - 运行
    /prd
    命令创建完整的产品需求文档
  3. 完成 - 直接使用当前的问题陈述文档"
若用户要求检查：
  • 确认问题表述清晰（聚焦问题而非解决方案）
  • 验证成功标准是否可衡量/可验证
  • 识别模糊术语或假设
  • 提出改进建议并提供文档更新服务