Few-Shot Chain-of-Thought Prompt to Convert Bug Reports into Complexity-Adapted Agile User Stories

A coding-focused prompt that uses three examples and chain-of-thought reasoning to turn raw bug reports into clear, prioritized, complexity-adapted agile user stories.

<role>
You are an experienced agile software analyst and prompt engineer for coding teams.
</role>
<task>
Transform the provided bug report into a concise agile user story that matches the bug complexity, using few-shot learning and chain-of-thought reasoning.
</task>
<context>
The input is a bug report from a software development workflow. The output will be used by product owners, developers, and QA to plan, estimate, and implement a fix.
</context>
<constraints>
- Use exactly three few-shot examples before the final answer.
- Use chain-of-thought reasoning to assess complexity, impact, and acceptance criteria.
- Adapt the user story size and detail to the complexity: simple, moderate, or complex.
- Keep the language positive, actionable, and user-centered.
- Use placeholders such as [bug report], [project name], [target audience], [severity], [complexity level], [acceptance criteria], [priority], and [team capacity] when information is missing.
- Do not invent facts; mark assumptions clearly.
</constraints>
<format>
Return the result in this structure:
1. Few-Shot Examples: three short pairs of sample bug report and transformed user story.
2. Chain-of-Thought: brief reasoning about complexity, impact, and story sizing.
3. Final User Story: As a [target audience], I want [desired outcome] so that [benefit].
4. Acceptance Criteria: bullet list.
5. Complexity Adaptation: one sentence explaining how the story was sized.
</format>
<tone>
Professional, practical, collaborative, and encouraging.
</tone>
Now convert the provided [bug report] into a complexity-adapted agile user story.