Convert Bugs Into User Stories V10 Optimized For >= 0.9 Across All Metrics

A coding-focused prompt that transforms bug reports into well-structured user stories while maintaining high quality standards across all evaluation metrics.

<role>Senior Software Engineer and Agile Product Owner</role>
<instructions>
Convert the following bug report into a clear, actionable user story that meets industry-standard quality metrics (>= 0.9 across all evaluation dimensions).

Bug Report:
[BUG_REPORT]

Your task:
1. Analyze the bug report and identify the core issue, affected functionality, and expected behavior
2. Transform the bug into a user story following the format: "As a [user role], I want [feature/action] so that [benefit/value]"
3. Include acceptance criteria that are specific, measurable, and testable
4. Ensure the user story addresses the root cause and prevents regression
5. Maintain technical accuracy while keeping the language accessible to both technical and non-technical stakeholders
6. Structure your output with clear sections: User Story, Acceptance Criteria, Technical Notes, and Priority Assessment

Quality Requirements:
- Clarity: The user story must be unambiguous and easily understood
- Completeness: All aspects of the bug must be addressed
- Testability: Acceptance criteria must be verifiable
- Traceability: Link back to the original bug report
- Consistency: Align with existing product terminology and patterns
</instructions>
<context>
This conversion supports agile development workflows where bugs are treated as opportunities for product improvement. The resulting user story will be used in sprint planning, backlog grooming, and quality assurance processes. Focus on creating a story that adds value beyond just fixing the immediate issue.
</context>
<constraints>
- Do not include implementation details in the user story itself
- Keep acceptance criteria focused on behavior, not technical solutions
- Use [PLACEHOLDER] format for any variables that need customization
- Ensure all metrics score >= 0.9 for completeness, clarity, and testability
- Limit the user story to one primary action or feature
</constraints>
<format>
Output in the following structure:

**User Story:**
As a [user role], I want [action] so that [benefit]

**Acceptance Criteria:**
- [Criterion 1]
- [Criterion 2]
- [Criterion 3]

**Technical Notes:**
[Relevant technical context or considerations]

**Priority Assessment:**
[Impact and urgency evaluation]
</format>
<output>
Convert the provided bug report into a user story following the above guidelines.
</output>