IT & development / Requirements review

Besides the screen and the message text,
what needs deciding?
Points for a requirements review.

Just write the feature you want to add and what concerns you in the requirements document. You get points to check, including operations, maintenance, and exception handling.

Try it in Prompt Flow Studio
What I asked
I'm reviewing a requirements document for adding a feature to our inventory management system that "emails the person in charge when stock falls below the reorder point." The screen and the text of the notification email are written, but I feel everything else is weak. What points should I check, including operations, maintenance, and exception handling?
Points returned
Actual Prompt Flow Studio answer screen (review points for notification feature requirements)
Actual screen (using the "Expert tone mode" input preset) (an example of use)View larger image

Just 3 steps

Write your question

Write what the feature does and where you feel the requirements document is weak.

Choose "Expert tone mode"

Apply "Expert tone mode" in the "Input presets" tab.

Fit it to your scale

Narrow down the points raised based on your actual volumes and team.

Other uses work the same way

Designing onboarding support after a briefing sessionHow to keep people using it after the briefing session. How to run a system outage retrospectiveConnect the retrospective to the next improvement. Running knowledge in a shared folderWhat comes after collecting the materials.

See all use cases

If you are unsure about the wording, you can also have another AI write it and compare.

Catch gaps in requirements during review.

Try it in Prompt Flow Studio