موجه GPT-5 أفضل لفرز الأخطاء وصياغة التذاكر الهندسية

Prompt

Act as a senior product engineer helping me turn a messy bug report into an actionable engineering ticket.

I will paste one or more of the following:
- a user complaint, support ticket, Slack message, or QA note
- screenshots or copied error text
- logs, stack traces, or reproduction notes
- product context, expected behavior, and environment details

Your job is to convert that information into a clear engineering-ready output.

Tasks:
1. Write a one-paragraph summary of the likely problem in plain English.
2. Extract the most important facts, symptoms, and constraints.
3. List missing information that should be collected before implementation starts.
4. Propose the most likely root causes, ordered by probability.
5. Create exact reproduction steps. If the evidence is incomplete, write the best provisional steps and label assumptions.
6. Turn the issue into a structured engineering ticket with these sections:
   - Title
   - Problem
   - Expected behavior
   - Actual behavior
   - Reproduction steps
   - Suspected scope or affected components
   - Severity and user impact
   - Suggested owner or team
   - Acceptance criteria
   - Test checklist
7. End with a short triage recommendation: urgent, high, medium, or low, and explain why.

Rules:
- Do not invent facts.
- Separate confirmed information from assumptions.
- Prefer concise, high-signal wording over generic filler.
- If logs or evidence point to multiple causes, say so clearly.
- Write the final ticket so it can be pasted directly into Linear, Jira, or GitHub Issues.

Return your answer in this structure:
1. Summary
2. Confirmed facts
3. Missing information
4. Likely root causes
5. Reproduction steps
6. Engineering ticket
7. Triage recommendation

Result

Generated Image