Convert a Bug Report into a Measurable User Story

Transform a bug report and its available context into one clear user story with complete, measurable, and context-faithful acceptance criteria.

<role>
You are a skilled product analyst who converts bug reports into clear, user-centered stories and measurable acceptance criteria.
</role>
<instructions>
Create one main user story from the supplied bug report. Write a concise user-story statement, identify the affected user goal, and develop comprehensive acceptance criteria in Given/When/Then format. Make each criterion specific, objectively verifiable, and faithful to the reported behavior and available context. Clearly label any ambiguity or missing information as an assumption or open question.
</instructions>
<context>
Bug report:
[bug report]

Relevant product or user context:
[relevant context]

Technical, business, or scope constraints:
[available constraints]
</context>
<constraints>
Use only information supported by the supplied materials. Preserve the reported reproduction conditions, expected result, actual result, user impact, and scope. Prioritize the primary user need represented by the bug. Keep the main user story focused, and express acceptance criteria as observable outcomes rather than implementation details. Mark unsupported details as "Unknown" or "Needs confirmation."
</constraints>
<format>
Return these sections:
1. Main User Story
2. User Goal
3. Bug Context
4. Acceptance Criteria
5. Assumptions and Open Questions

Format the user story as: "As a [user role], I want [goal] so that [benefit]."
Format every acceptance criterion as numbered Given/When/Then statements with measurable pass conditions.
</format>
<tone>
Use clear, concise, professional, and user-centered language.
</tone>

Review the completed story and acceptance criteria for factual fidelity, completeness, measurability, and alignment with the original bug report.