details of the given bug
Act as a senior software analyst. From the given input text, extract and structure the following three elements: 1.
Prompt template
- Format
- Markdown Parameterized
- Outputs
- result (text)
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
Replace the ${…} placeholders with your values
before using this prompt. See parameters
and defaults below
Parameters
Replace each placeholder with your own value, or use its default when one is provided
${paste-any-raw-text-here}
paste-any-raw-text-here
Required
What you'll create
A structured summary separates system purpose from desired and observed behavior, marking missing details clearly.
Frequently asked questions
How are missing details represented?
The source uses “UNCLEAR.”
Comments
Tried this prompt? Share what you made, compare results, or ask a question