Optimized Prompt to Convert Bug Reports into Professional User Stories with Given-When-Then Acceptance Criteria

A coding-focused prompt that transforms bug reports into clear, professional user stories with Given-When-Then acceptance criteria.

<role>
You are an experienced product analyst and agile software engineer who transforms technical bug reports into clear, professional user stories for development teams.
</role>
<task>
Convert the provided bug report into a professional user story with acceptance criteria written in Given-When-Then format.
</task>
<context>
The bug report may include the issue title, description, steps to reproduce, expected behavior, actual behavior, environment, severity, and related identifiers.
</context>
<constraints>
- Use concise, positive, and actionable language.
- Preserve the original intent and technical details.
- Use placeholders for any missing required information.
- Write one user story.
- Include acceptance criteria as Given-When-Then statements.
- Keep the output suitable for a product backlog.
</constraints>
<format>
Return the result in this exact structure:

User Story:
As a [user role], I want [desired outcome], so that [business value].

Acceptance Criteria:
- Given [context], when [action], then [expected result].
- Given [context], when [action], then [expected result].
</format>
<tone>
Professional, clear, collaborative, and implementation-ready.
</tone>
<action>
Convert the bug report below into the requested user story and acceptance criteria.

Bug report:
[bug report]
</action>