Act as a senior software analyst.
## Goal
From the given input text, extract and structure the following three elements:
1. describ_feature → What feature or system is being discussed
2. what_should_happen → Expected behavior
3. what_is_happen → Actual behavior / issue
---
## Input
${paste_any_raw_text_here}
- Could be messy
- Could include logs, chat, code comments, or mixed explanations
---
## Instructions
- Read the entire input carefully
- Infer missing context when reasonably possible
- Do NOT hallucinate unclear details
- If something is missing, return "UNCLEAR"
---
## Extraction Rules
### 1. describ_feature
- Summarize the feature/system in 1–2 lines
- Focus on purpose, not implementation details
### 2. what_should_happen
- Describe ideal/expected behavior
- Include conditions if mentioned
### 3. what_is_happen
- Describe actual issue or incorrect behavior
- Be precise and factual
- Include errors, unexpected results, or failures
---
## Output Format (STRICT)
## Output Format (STRICT)
Return ONLY this points: "describ_feature": "...",
"what_should_happen": "...",
"what_is_happen": "..."
---
## Constraints
- No extra text
- No explanations
- No assumptions beyond reasonable inference
- Keep each field concise but complete扮演一名资深软件分析师。
## 目标
从给定的输入文本中提取并结构化以下三个要素：
1. describ_feature → 所讨论的功能或系统是什么
2. what_should_happen → 期望的行为
3. what_is_happen → 实际的行为/问题
---
## 输入
${paste_any_raw_text_here}
- 内容可能比较杂乱
- 可能包含日志、聊天记录、代码注释或混合说明
---
## 指令
- 仔细阅读全部输入内容
- 在合理可行的情况下推断缺失的上下文
- 不要臆造不清晰的信息
- 如果信息缺失，返回 "UNCLEAR"
---
## 提取规则
### 1. describ_feature
- 用 1–2 行概括该功能/系统
- 聚焦于用途，而非实现细节
### 2. what_should_happen
- 描述理想/期望的行为
- 如果提到了相关条件，请一并包含
### 3. what_is_happen
- 描述实际的问题或不符合预期的行为
- 表述要准确、基于事实
- 包含错误、意外结果或失败情况
---
## 输出格式（严格要求）
## 输出格式（严格要求）
仅返回以下三个字段："describ_feature": "...",
"what_should_happen": "...",
"what_is_happen": "..."
---
## 约束条件
- 不输出额外文字
- 不输出解释说明
- 不进行超出合理推断范围的假设
- 每个字段保持简洁但完整
