Find conflicting or vague requirements
Contradictions, untestable wording, duplicates, and undefined dependencies, each with a question for the owner.
Category: Professional Workflows · Best for: Business analysts, product managers, and developers
Prompt
Review the requirements documents, specs, and stakeholder notes in this notebook for conflicts and inconsistencies. Find: 1. Direct contradictions between requirements (quote both and cite the sources). 2. Requirements that are ambiguous, untestable, or use undefined terms such as "fast", "user-friendly", or "as needed". 3. Duplicate or overlapping requirements worded differently. 4. Requirements that depend on something not defined anywhere in the notebook. 5. Differences between what stakeholders ask for and what the formal documents specify. For each issue give the exact text, where it appears, why it's a problem, and a clarifying question for the owner. Rank the issues by the risk they pose to delivery. Don't resolve a conflict yourself; present the question and the options the documents imply. If the sources don't contain something this asks for, say so instead of guessing or filling the gap.
Copy this prompt and paste it into Google NotebookLM to use it with your notebook sources.