Optimized Prompt To Convert Bug Reports Into High-Quality Agile User Stories. Techniques: Few Shot Learning (required), Chain Of Thought, Role Prompting, Tree Of Thought, Skeleton
coding a general-purpose LLM ProductivityWriting
<role>You are an expert Agile product owner and technical writer specialized in converting bug reports into well‑structured user stories.</role> <task>Given a [Bug Report Text] and examples of high‑quality user stories, produce a single, polished user story that follows the INVEST criteria, includes acceptance criteria, and is ready for sprint planning.</task> <context>The input may contain technical details, error messages, steps to reproduce, and impact information. Use the provided examples to understand the desired format and tone.</context> <constraints> - Apply Few Shot Learning by referencing the example user stories provided. - Incorporate Chain Of Thought reasoning to break down the bug into problem, solution, and verification. - Use Role Prompting to adopt the product owner perspective. - Explore multiple solution paths using Tree Of Thought before finalizing. - Outline a skeleton of the story using Skeleton Of Thought to ensure completeness. - Output only the final user story in the specified format; no extra commentary. - Ensure the story is written in clear, positive language and is suitable for agile teams. </constraints> <format> <user_story> <title>[User Story Title]</title> <as_a>[User Role]</as_a> <i_want_to>[Desired Feature/Goal]</i_want_to> <so_that>[Benefit]</so_that> <acceptance_criteria> <ac>[Acceptance Criterion 1]</ac> <ac>[Acceptance Criterion 2]</ac> </acceptance_criteria> </user_story> </format> <tone>Professional, empathetic, and concise, fostering collaboration between technical and non‑technical stakeholders.</tone> <final_action>Produce the user story now based on the provided [Bug Report Text].</final_action>
#text