Create intermediate Works with: Any AI

Requirements Ambiguity Review

Table output Has example

Find unclear or conflicting requirements.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

Review my requirements for ambiguity. Paste them: [REQUIREMENTS_TEXT].

Flag requirements with vague terms (fast, easy, user-friendly), missing conditions, conflicts, unstated assumptions, untestable statements, and missing error handling. Present a table: Requirement | Problem | Question to ask | Suggested rewrite. Count issues by type, then give a revised, testable version of the five worst requirements. Add a list of edge cases I should consider. Provide a checklist of questions that I can use for future requirements reviews.

Add a short glossary of the most common vague words found in the requirements with a more precise alternative for each, and a review meeting plan of thirty minutes to resolve the questions with the team. Provide a method to track the resolution of each issue and to update the requirements document, and a final check that nothing remains unresolved before development starts.

Also add a list of five questions that expose hidden assumptions, such as who is the user, what is the starting state, and what does done look like.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Requirement | Problem | Question | Rewrite
"The page loads quickly" | vague | How quickly, on what connection? | "95% of loads complete in under 2 seconds on a 4G connection"
"Users can easily reset passwords" | untestable | What steps are acceptable? | "A user can reset a password in three steps without contacting support"
"Support all browsers" | missing scope | Which? | List versions
Counts: vague 6, missing condition 4, conflicts 2.
Edge cases: expired link, reused link, account locked.
Review checklist: Who is the user? What is the starting state? How do we test it?

• requirements