diff --git a/prompts/coding/details_of_the_given_bug_1724.md b/prompts/coding/details_of_the_given_bug_1724.md
new file mode 100644
index 0000000..9049a78
--- /dev/null
+++ b/prompts/coding/details_of_the_given_bug_1724.md
@@ -0,0 +1,69 @@
+---
+title: "details of the given bug"
+contributor: "@anonymous"
+tags: #coding, #anonymous
+---
+
+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