AI Prompt Template - Review a Story to improve Quality
03 Dec 2025
In this moment:
Gary Hawkes
As per https://club.ministryoftesting.com/t/using-ai-prompting-as-a-shift-left-tool-coaching-tool/86925 , I thought I'd share wider the prompt template I use to help Quality Engineers, Developers and Product Managers to help ensure that the acceptance criteria and story construction is fit for use. Its a great shift left tool as I can leave this with product managers and they can use this when they write their stories, before submitting them for refinement. Here's the prompt:
"You are a highly experienced quality engineer with 10 years experience. You have a reputation for ensuring clear and unambiguous requirements in the {industry} sector. I want you to help me analyse a User Story for this {product} which is used for {product use} and list where the requirements in the story need to be clarified to ensure the acceptance criteria will be understood. The user story details are {story details}.
{Industry}:
{Product}:
{product use}:
{story details}:"
The prompt is trying to ensure a Quality focus when reviewing the story and give guidance as to what I want reported. You then have the additional variables to enhance the success and relevance of the answers:
{Industry}: A good description of the industry that is relevant to the product. This hopefully give the LLM context on the language that the story may contain
{Product}: The name of the product (or a useful name that will help the LLM)
{product use}: Go as descriptive as you like here, but describe the purpose of the product and the business benefit to it
{story details}: A copy of the story details
"You are a highly experienced quality engineer with 10 years experience. You have a reputation for ensuring clear and unambiguous requirements in the {industry} sector. I want you to help me analyse a User Story for this {product} which is used for {product use} and list where the requirements in the story need to be clarified to ensure the acceptance criteria will be understood. The user story details are {story details}.
{Industry}:
{Product}:
{product use}:
{story details}:"
The prompt is trying to ensure a Quality focus when reviewing the story and give guidance as to what I want reported. You then have the additional variables to enhance the success and relevance of the answers:
{Industry}: A good description of the industry that is relevant to the product. This hopefully give the LLM context on the language that the story may contain
{Product}: The name of the product (or a useful name that will help the LLM)
{product use}: Go as descriptive as you like here, but describe the purpose of the product and the business benefit to it
{story details}: A copy of the story details
Gary Hawkes
QA Lead
He/Him
Software QA Lead and tester who loves to see people grow, processes continuously improve and help organisations understand and support Quality Engineering
Sign in
to comment
With servers in >250 cities around the world, check your site for localization problems, broken GDPR banners, etc.
Explore MoT
Unleash the power of generative AI to boost your software testing and day-to-day tech tasks
Into the MoTaverse is a podcast by Ministry of Testing, hosted by Rosie Sherry, exploring the people, insights, and systems shaping quality in modern software teams.