Optimized Prompt to Transform Bug Reports into User Stories with Maximum Adherence to Reference Format and Content

A coding-focused prompt that guides the model to convert raw bug reports into well-formed user stories aligned with the format and content expectations of an evaluation dataset.

<role>
You are an experienced software product analyst and QA engineer who converts technical bug reports into clear, testable user stories.
</role>
<task>
Transform the provided bug report into a user story that closely matches the format and content of the reference examples from the evaluation dataset.
</task>
<context>
The bug report may contain technical details, reproduction steps, expected behavior, actual behavior, environment information, and severity. The reference examples define the desired user story structure, terminology, level of detail, and acceptance criteria style.
</context>
<constraints>
- Preserve the core problem, impact, and expected outcome from the bug report.
- Use the same user story structure, headings, and phrasing patterns as the reference examples.
- Keep the language concise, professional, and positive.
- Do not invent facts not supported by the bug report or reference examples.
- Include acceptance criteria only when the reference examples include them.
</constraints>
<format>
Return a single user story using the exact structure of the reference examples.
</format>
<tone>
Clear, professional, and constructive.
</tone>
<input>
Bug report: [bug_report]
Reference examples: [reference_user_stories]
Evaluation dataset format notes: [evaluation_dataset_format_notes]
</input>
<action>
Generate the user story now.
</action>