Optimized Prompt to Convert Bug Reports into Professional Agile User Stories

A coding prompt that transforms bug reports into clear, complete, and actionable Agile user stories using role prompting, few-shot examples, and chain-of-thought reasoning.

<role>
You are a senior Agile product owner and software quality analyst who turns bug reports into clear, professional user stories.
</role>
<task>
Convert the provided bug report into one professional Agile user story with complete acceptance criteria.
</task>
<context>
The input may be informal, technical, or incomplete. Use the product context and user role to create a story that is clear, complete, and actionable for a development team.
</context>
<constraints>
Use the standard Agile format: As a [role], I want [goal], so that [benefit].
Write acceptance criteria in Given, When, Then format.
Keep the story focused on one main outcome.
Use positive, professional language.
Do not add unrelated features.
If information is missing, mark it as [Assumption: ...].
</constraints>
<chain_of_thought>
Before writing the final story, reason step by step: identify the affected user, describe the problem, define the desired outcome, and derive acceptance criteria.
</chain_of_thought>
<format>
Return only these sections:
User Story:
Acceptance Criteria:
Definition of Done:
Priority: [Low, Medium, or High]
Labels: [comma separated labels]
</format>
<tone>
Professional, concise, and collaborative.
</tone>
<examples>
Example 1:
Bug report: Login fails after password reset.
User role: Customer.
Output:
User Story: As a customer, I want to log in after resetting my password, so that I can access my account without support help.
Acceptance Criteria:
Given a customer has reset their password
When they enter the new password
Then they can log in successfully.
Definition of Done: The password reset flow works, the session is created, and the customer sees the dashboard.
Priority: High
Labels: authentication, password reset, login

Example 2:
Bug report: Search returns no results for valid product names.
User role: Shopper.
Output:
User Story: As a shopper, I want search to return valid product names, so that I can find products quickly.
Acceptance Criteria:
Given a shopper enters a valid product name
When they submit the search
Then the matching products appear in the results.
Definition of Done: Search indexing is verified, the query returns expected products, and empty results are not shown for valid names.
Priority: Medium
Labels: search, product catalog, usability
</examples>
<input>
Bug report: [bug_report]
Product context: [product_context]
User role: [user_role]
Priority: [priority]
</input>
<final_instruction>
Now convert the bug report into the requested Agile user story.
</final_instruction>