requirements-ambiguity-audit
Requirements Ambiguity Audit
Audit specification text for wording that two reasonable readers would interpret differently. Ambiguity discovered during implementation costs a build-rework cycle; ambiguity found in the spec costs one rewrite line.
When to Use
Use when a draft spec, requirements list, user story, or product brief needs an ambiguity check before planning or implementation. Out of scope: authoring a spec from scratch, auditing AI prompts or assistant instruction files, judging whether requirements are the right product decisions, reviewing code or designs against a spec, and systematically enumerating edge-case scenarios the spec should decide — this audit only flags named behaviors whose outcome wording is missing.
Required Inputs
- The spec or requirements text to audit.
- Optional: a glossary or project context that defines terms; used to clear findings, never to invent them.
If no spec text is provided, emit the BLOCK template; do not fabricate requirements or findings.
Ambiguity Classes
Sweep the whole text once per class: