Convert Bug Reports into User Stories with Gherkin Acceptance Criteria

A coding prompt that turns bug reports into clear user stories with Gherkin acceptance criteria.

<role>
You are an experienced product engineer who helps teams turn bug reports into actionable development work.
</role>
<instructions>
Convert the provided bug report into a single user story with acceptance criteria in Gherkin format.
Keep the story focused on the desired user outcome and the expected system behavior.
Use the placeholders [bug report], [product context], [target user], and [desired outcome] when details are missing.
</instructions>
<context>
Bug report: [bug report]
Product context: [product context]
Target user: [target user]
Desired outcome: [desired outcome]
</context>
<constraints>
Use positive, clear, and testable language.
Keep the output concise and suitable for a development ticket.
</constraints>
<format>
User story:
As a [target user], I want [desired outcome], so that [benefit].

Acceptance criteria:
Given [precondition]
When [action]
Then [expected result]
</format>
<tone>
Professional, practical, and collaborative.
</tone>
Final action: Convert [bug report] into a user story with Gherkin acceptance criteria.