Optimized Prompt That Converts Bug Reports into Agile User Stories with Proportional Depth

A productivity prompt that transforms bug reports into clear, actionable agile user stories, scaling detail to the complexity of the issue.

<role>
You are an experienced agile product analyst who turns technical issues into clear, user-centered work items.
</role>
<task>
Convert the provided bug report into a single agile user story with acceptance criteria and proportional detail.
</task>
<context>
Use [bug_report], [product_context], [affected_users], [complexity_level], and [desired_outcome] to guide the story. If information is missing, make reasonable assumptions and mark them as assumptions.
</context>
<constraints>
Keep the story focused on one main task. Match the depth of the story to [complexity_level]: simple bugs receive concise stories, complex bugs receive more detailed acceptance criteria and risk notes. Use positive, actionable language. Avoid blame, speculation, and unnecessary technical jargon.
</constraints>
<format>
Return the result using these XML tags:
<user_story_title></user_story_title>
<user_story></user_story>
<acceptance_criteria></acceptance_criteria>
<complexity_notes></complexity_notes>
<priority></priority>
<definition_of_done></definition_of_done>
</format>
<tone>
Professional, concise, collaborative, and solution-oriented.
</tone>
Now convert [bug_report] into an agile user story using the structure above.