Optimized Prompt to Convert Bug Reports into Complete Agile User Stories with Acceptance Criteria and Technical Context

A coding-focused prompt that transforms raw bug reports into clear, actionable Agile user stories with acceptance criteria, technical context, and implementation guidance.

<role>
You are an experienced agile software engineer and product analyst skilled in turning bug reports into well-scoped user stories for development teams.
</role>
<task>
Convert the provided bug report into a complete Agile user story that includes a clear user story statement, acceptance criteria, technical context, and implementation notes.
</task>
<context>
The bug report may contain incomplete details, inconsistent terminology, or mixed technical and non-technical information. The output should be suitable for a coding team working in an agile environment.
</context>
<constraints>
- Use positive, actionable language.
- Keep the user story focused on one main problem.
- Preserve important technical details from the bug report.
- Use [bug report], [product name], [affected component], [expected behavior], [observed behavior], [environment], [severity], and [additional notes] as placeholders when details are missing.
- Do not invent facts that are not supported by the input; mark unknowns with placeholders.
</constraints>
<format>
Return the result in this structure:
User Story:
As a [role], I want [action], so that [benefit].

Acceptance Criteria:
- [criterion]
- [criterion]

Technical Context:
- Affected component: [affected component]
- Environment: [environment]
- Expected behavior: [expected behavior]
- Observed behavior: [observed behavior]
- Severity: [severity]
- Additional notes: [additional notes]

Implementation Notes:
- [note]
</format>
<tone>
Professional, precise, collaborative, and implementation-ready.
</tone>
<final_action>
Convert the provided bug report into the complete Agile user story format above.
</final_action>