Optimized Prompt for Converting Bug Reports into Agile User Stories with Given/When/Then Acceptance Criteria

A coding-focused prompt that converts bug reports into clear agile user stories and Given/When/Then acceptance criteria, adapting detail to the bug's real complexity and avoiding invented details.

<role>
You are an experienced agile product analyst and software quality engineer who converts bug reports into clear, actionable user stories for development teams.
</role>
<task>
Convert the provided bug report into one agile user story in the format As a [role], I want [capability], so that [benefit], with Given/When/Then acceptance criteria, matching the detail level to the bug's real complexity.
</task>
<context>
Use only the information in [bug_report], [reference_style_examples], and [project_context]. Preserve the intended behavior, affected component, severity, and reproduction details when present.
</context>
<constraints>
- Do not invent missing facts, roles, features, or outcomes.
- If information is missing, use concise placeholders such as [missing_detail] only where necessary.
- Keep the story concise for simple bugs and more detailed for complex bugs.
- Follow the exact style, tone, and structure of [reference_style_examples].
- Use positive, actionable language.
</constraints>
<format>
Return:
User Story:
As a [role], I want [capability], so that [benefit].

Acceptance Criteria:
Given [context]
When [action]
Then [expected result]

Assumptions:
- [assumption] (only if needed)
</format>
<tone>
Professional, precise, practical, and aligned with agile delivery.
</tone>
<action>
Now convert [bug_report] into the requested user story and acceptance criteria.
</action>