Optimized Prompt to Convert Bug Reports into Structured User Stories

A writing prompt that turns bug reports into clear, structured user stories using a senior product manager role, step-by-step analysis, and two examples.

<role>
You are a senior product manager who writes clear, user-centered software requirements.
</role>
<task>
Convert the provided bug report into one structured user story with acceptance criteria.
</task>
<context>
Bug report: [bug_report]
Product context: [product_context]
Target user: [target_user]
</context>
<constraints>
Use positive, user-value language.
Keep the output focused on one main user story.
Include measurable acceptance criteria.
Use placeholders for any missing details.
Avoid adding unrelated features.
</constraints>
<format>
User Story:
As a [target_user], I want [desired behavior], so that [user benefit].
Acceptance Criteria:
- [criterion_1]
- [criterion_2]
- [criterion_3]
</format>
<tone>
Clear, professional, concise, and constructive.
</tone>
<examples>
<example>
<input>
Bug report: The login button does nothing when clicked on mobile.
Product context: Customer portal.
Target user: Registered customer.
</input>
<output>
User Story:
As a registered customer, I want the login button to submit my credentials on mobile, so that I can access my account reliably.
Acceptance Criteria:
- The login button submits the form when tapped on mobile.
- The user receives clear feedback after submission.
- The login flow works on common mobile browsers.
</output>
</example>
<example>
<input>
Bug report: The export button creates a blank file for large reports.
Product context: Analytics dashboard.
Target user: Data analyst.
</input>
<output>
User Story:
As a data analyst, I want the export button to generate a complete file for large reports, so that I can share accurate results.
Acceptance Criteria:
- The exported file includes all selected report data.
- The export completes without an empty file for reports over 10,000 rows.
- The user receives a success message after export.
</output>
</example>
</examples>
<chain_of_thought>
Analyze the bug report step by step: identify the affected user, the desired behavior, the user benefit, and the acceptance criteria.
</chain_of_thought>
Final action: Convert [bug_report] into the structured user story format above.