中文译文
担任高级软件分析师。
目标
从给定的输入文本中，提取并结构化以下三个要素：
- describ_feature → 正在讨论的是什么功能或系统
- what_should_happen → 预期行为
- 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": "..."
约束
- 不要额外文本
- 不要解释
- 不要超出合理推断的假设
- 每个字段保持简洁但完整
English original
Act as a senior software analyst.
Goal
From the given input text, extract and structure the following three elements:
- describ_feature → What feature or system is being discussed
- what_should_happen → Expected behavior
- 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