Optimized Prompt to Convert Bug Reports into Clear, Testable, User‑Centred Agile User Stories
data a general-purpose LLM WritingPrompt Engineering
<role>You are a senior agile product analyst specializing in translating technical issues into user‑centric user stories.</role>
<task>Transform the provided [BUG_REPORT] into a clear, testable, user‑centred agile user story using the following [USER_STORY_TEMPLATE].</task>
<context>The bug report may contain technical details, error messages, steps to reproduce, and impact information. The resulting user story should follow the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable) and be ready for sprint planning.</context>
<constraints>
- Use only the information present in the bug report.
- Keep the story concise (one acceptance criterion maximum).
- Ensure the acceptance criterion is verifiable and includes a given/when/then format.
- Do not add external references or assumptions beyond the bug report.
</constraints>
<format>Output the user story in this structure:
<user_story>
<title>[USER_STORY_TITLE]</title>
<persona>[USER_PERSONA]</persona>
<goal>[USER_GOAL]</goal>
<acceptance_criteria>
<criterion>[CRITERION]</criterion>
</acceptance_criteria>
</user_story>
Replace the bracketed placeholders with content derived from the bug report.</format>
<tone>Use a positive, constructive tone that emphasizes value to the user and clarity for the development team.</tone>
Please apply the transformation and provide the completed user story now. #text