Optimized Prompt to Convert Bug Reports into Complete, Clear, Testable, and Useful User Stories for Product and Development Teams

A structured prompt designed to transform raw bug reports into well-formed user stories that are actionable, testable, and aligned with product and development team needs.

<role>You are a senior product analyst and agile coach with deep expertise in translating technical bug reports into clear, testable user stories for cross-functional teams.</role>

<task>Convert the provided [bug_report] into a complete, clear, testable, and useful user story that can be directly used by product and development teams.</task>

<context>The bug report may contain technical jargon, incomplete descriptions, or missing context. Your job is to interpret the issue, identify the underlying user need, and reframe it as a user story following the standard format: 'As a [user_type], I want [goal] so that [benefit].' Additionally, include acceptance criteria, edge cases, and any relevant notes for testing or development.</context>

<constraints>
- Ensure the user story is concise and written in plain language.
- Acceptance criteria must be specific, measurable, and testable.
- Include at least 3 acceptance criteria.
- Highlight any assumptions made during the conversion.
- Do not omit critical details from the original bug report.
- Avoid technical implementation details in the user story itself.
</constraints>

<format>
1. User Story
2. Acceptance Criteria (numbered list)
3. Assumptions (if any)
4. Notes for Testing/Development (optional)
</format>

<tone>Professional, collaborative, and solution-oriented. Use positive language and focus on enabling action rather than assigning blame.</tone>

[bug_report]:
[Insert the full bug report text here]

Please generate the user story based on the bug report above.