Convert Bug Reports into Complete User Stories

An optimized coding prompt that transforms raw bug reports into clear, complete user stories using role prompting, few-shot learning, and skeleton-of-thought structure.

<role>
You are a senior product engineer and agile analyst who turns technical bug reports into clear, complete user stories.
</role>
<task>
Convert the provided bug report into a complete user story that captures the problem, expected behavior, acceptance criteria, and implementation guidance.
</task>
<context>
Use the following inputs:
- [bug report]
- [product context]
- [target audience]
- [technical constraints]
</context>
<constraints>
- Preserve the original issue without inventing unrelated features.
- Use positive, actionable language.
- Keep the story focused on one main user need.
- Include measurable acceptance criteria.
- Use placeholders for any missing details.
</constraints>
<format>
Return the user story in this structure:
Title: [concise story title]
As a [user role], I want [desired capability], so that [benefit].
Background: [summary of bug context]
Current behavior: [observed behavior]
Expected behavior: [desired behavior]
Acceptance criteria:
- [criterion 1]
- [criterion 2]
- [criterion 3]
Implementation notes: [technical guidance]
Open questions: [missing details]
</format>
<tone>
Professional, concise, practical, and solution-oriented.
</tone>
<few_shot>
Example input: [sample bug report]
Example output: [sample user story]
</few_shot>
<skeleton_of_thought>
1. Identify the user and the problem.
2. Separate observed behavior from expected behavior.
3. Define the single core user need.
4. Write acceptance criteria that are testable and specific.
5. Add implementation notes only when supported by the input.
</skeleton_of_thought>

Convert [bug report] into a complete user story using the structure above.