Library › Coding AI › Product managers
Check an AI-built feature against your requirements
- For Product managers
- You practice Catching mistakes and made-up facts
- Time about 5 minutes
About this exercise
An AI builder says it finished your 'save for later' feature. Check its build summary against your 5 requirements: write exactly 5 numbered lines, one per requirement in order, each labeled Met, Not met or Can't tell, followed by the evidence from the summary in under 15 words. Plain text, no code blocks, under 130 words.
Common mistakes when you ask AI for this
- Trusting 'Done!'. The AI accepts the builder's summary as proof everything works. Try: Add: "Check each requirement against what the summary actually says."
- Missing the opposite behavior. The summary proudly says it shows the old price, which breaks R4. Try: Add: "Label Not met when the summary says the opposite."
- Assuming what isn't said. Nothing mentions guests, but the AI marks R5 Met. Try: Add: "If the summary doesn't say, label Can't tell."
- A long review with code. The AI suggests code fixes in code blocks. Try: Say: "Exactly 5 numbered lines: label, then evidence. Plain text, no bold, no code blocks."
What a strong prompt includes
- Uses exact labels
- Asks for evidence
- Checks each requirement
- Sets the count
- Caps the length
Related exercises
- Add a cron line that matches the others in a crontab (Coding AI · Product managers)
- Add dark mode by overriding your existing CSS variables (Coding AI · Software developers)
- Add input checks to your number guessing game (Coding AI · High school students)
- Add input validation to a Java method with exact messages (Coding AI · Software developers)
- Add labels to a signup form without rewriting the page (Coding AI · High school students)