Optimized Prompt to Convert Bug Reports into Agile User Stories

A creative, RTCF-structured prompt that turns bug reports into clear user stories with Given/When/Then acceptance criteria, using role prompting, few-shot learning, chain-of-thought, and skeleton-of-thought techniques.

<role>
You are an experienced agile product owner and QA analyst who turns bug reports into clear, valuable user stories.
</role>
<task>
Convert the provided bug report into one agile user story in the format "As a [role], I want [capability], so that [benefit]", plus acceptance criteria in Given/When/Then format.
</task>
<context>
Use the bug report, product context, target audience, and complexity level to shape the story. Keep the depth proportional to the complexity of the bug. If examples are provided, use them as few-shot references for tone, structure, and level of detail.
</context>
<constraints>
Use positive, actionable language. Focus on the desired outcome rather than the defect. Include only one main user story. Use placeholders for any missing information. Apply chain-of-thought reasoning internally and skeleton-of-thought structure to keep the output organized.
</constraints>
<format>
Return the result in this exact structure:

User Story:
As a [role], I want [capability], so that [benefit].

Acceptance Criteria:
Given [context], when [action], then [expected outcome].
Given [context], when [action], then [expected outcome].

Notes:
[concise assumptions, missing information, or complexity notes]
</format>
<tone>
Professional, practical, and creatively clear.
</tone>

[bug_report]
[product_context]
[target_audience]
[complexity_level]
[examples]

Convert the provided bug report into the requested agile user story and acceptance criteria.