Review User Stories with AI: Find Gaps in Acceptance Criteria
The cheapest bug is the one you catch before anyone writes code. In this lesson you will learn to review user stories with AI, find gaps in acceptance criteria and turn them into clear questions for your team. This is one of the fastest ways for a tester to add value.
📖 What You’ll Learn
- What makes a user story easy or hard to test
- Five kinds of gaps to look for
- How to ask AI for a useful story review
- How to turn findings into good team questions
💡 Why Review a Story Before Testing?
Explain Like I’m 5: Story Review
Imagine: Before a treasure hunt, you read the map. If the last step is missing, you ask for help before you start digging.
What it really means: Reviewing a story finds missing details before work begins.
In testing: A small question today can stop a large defect later.
A user story describes what a user wants and why. Acceptance criteria are the conditions that must be true for the story to be accepted. Together, they tell the team what “done” means.
🔍 How to Review User Stories with AI
Explain Like I’m 5: AI Story Review
Imagine: A friend reads your homework and asks, “What does this word mean?” The friend helps you see what is unclear.
What it really means: AI can point out vague wording and possible gaps.
In testing: It can ask what “quickly” means in a performance rule.
AI is good at spotting unclear language. It does not know your product decisions, so treat every finding as a question to check.
🧩 Five Kinds of Gaps
| Gap type | Example in a story | Question to ask |
|---|---|---|
| Vague words | “The page loads quickly” | How many seconds is acceptable? |
| Missing errors | No failure message is defined | What does the user see if it fails? |
| Missing limits | “User can upload a file” | Which types and what maximum size? |
| Missing roles | “User can delete a report” | Which roles are allowed? |
| Missing states | No rule for an expired session | What happens when the session ends? |
🌍 Real-Life Example: Saving a Delivery Address
User story: As a shopper, I want to save my delivery address so that checkout is faster.
Acceptance criteria: The user can add an address. The user can choose a saved address at checkout.
A careful review could raise these questions:
- How many addresses can one shopper save?
- Which fields are required, and what format does the postal code need?
- Can a shopper edit or delete an address?
- What happens to an order if its address is later deleted?
- Do guest shoppers get this feature?
Notice that these are questions, and not new requirements. Only the team can decide the answers.
📌 Good Questions Get Good Answers
Explain Like I’m 5: Asking Good Questions
Imagine: “Is it fun?” is hard to answer. “Can we play outside after lunch?” is easy.
What it really means: A good question is specific and easy to answer.
In testing: Offer options, such as “Should the limit be 5 or 10 addresses?”
Group your questions by priority. Raise the ones that block testing first, and remove anything already answered. Your product owner will thank you for a short, focused list.
Check for conflicts too
Ask whether two criteria disagree. AI can miss conflicts across many stories, so review related stories together, and read them yourself.
🧪 Try It Yourself
- Pick a feature on the Dummy E-commerce Website.
- Write a short user story and two acceptance criteria for it.
- Write your own list of questions first.
- Run the prompt below in a new chat.
- Compare the lists, and keep only the questions that really matter.
📋 Ready-to-Copy Prompt
You are a senior QA engineer reviewing a user story before development.
User story:
[paste user story]
Acceptance criteria:
[paste acceptance criteria]
Review it for vague wording, missing error handling, missing limits,
missing roles and missing states.
Return a table with: Gap Type, Quote from the Story, Why It Matters,
Question for the Product Owner, Priority (High, Medium or Low).
Rules:
- Do not invent requirements or answers.
- Base each finding on the text above.
- If the story is clear on a point, do not raise it.⚠️ Common Mistakes
- Treating AI’s questions as confirmed requirements
- Sending a long unfiltered list to your product owner
- Reviewing one story and ignoring related stories
- Pasting confidential requirements into an unapproved tool
- Waiting until test execution to ask questions
🎯 Key Takeaways
- Finding a gap before coding is cheaper than finding a bug later.
- Look for vague words, missing errors, limits, roles and states.
- AI raises questions, and your team supplies the answers.
- A short, prioritised list gets better responses.
🎤 Interview Questions
1. How can AI help with requirement analysis?
Model answer: AI can find vague wording, missing error handling, limits and roles, then suggest questions. I give it the story and criteria, review its findings, and take only the relevant questions to the product owner. It supports the analysis, but it cannot decide business rules.
2. What makes acceptance criteria testable?
Model answer: They need clear, observable outcomes with defined conditions and limits. “The page loads quickly” is not testable, while “search results appear within 2 seconds for a defined load” can be measured.
3. What would you do if a requirement is ambiguous?
Model answer: I would write a specific question, explain the risk and suggest possible options. I would raise it early with the product owner and record the decision, so that development and testing share one understanding.
4. What are the limits of using AI to review requirements?
Model answer: It lacks product history and domain decisions, and it can miss contradictions across many stories. It may also raise irrelevant points. I treat its output as a checklist of possible issues and verify each one myself.
5. What is shift-left testing?
Model answer: Shift-left means starting quality activities earlier in development. Reviewing stories before coding is a good example, because it finds misunderstandings when they are still cheap to fix.
📝 Assignment
Choose three user stories, real or made up, with no confidential details. Review each by yourself and then with AI. Record how many useful questions each approach found, and note one question that only you thought of.
❓ FAQ
Can AI write the acceptance criteria too?
It can draft them, but your product owner must confirm them. A draft is useful only after someone who knows the product has approved it.
Do I need the whole requirements document?
Share only the part that is relevant and approved for your AI tool. Follow the rules from AI Data Privacy for Testers.
🚀 Next Steps
Well done on finishing this lesson. Complete the assignment, then continue with Create a Test Plan with AI: A Practical Guide for Testers.