VibeSpec Score 25: Negative Phrasing
VibeSpec Score 25: Negative Phrasing
Score 25 applies when requirements are written in a “don’t do” format. While technically correct, negative wording often hides what the system should actually accomplish.
Example requirements
- “The user interface must not confuse the operator.”
- Developer interpretation: Basic layout will suffice as long as there are no major errors.
- Tester interpretation: Interface must be self-explanatory for first-time users.
- Fix: “Design the user interface so operators can complete common tasks without external help.”
- “The process should not take too long.”
- Developer interpretation: A minute or two might be acceptable.
- Manager interpretation: Expects near-instant results.
- Fix: “The process should finish within 30 seconds for standard workloads.”
- “The logs must not be hard to read.”
- Developer interpretation: Minimal formatting is enough.
- Support interpretation: Needs clear timestamps and error levels.
- Fix: “Provide structured logs with timestamps and severity labels.”
How VibeSpec detects and explains
VibeSpec encourages writers to flip negative statements into positive ones. It explains that describing the intended behaviour makes validation easier and removes uncertainty about edge cases.
Why interpretations differ
A developer might assume “not too long” means under a minute, whereas a tester might expect mere seconds. Similarly, what seems “not confusing” to an experienced engineer could still baffle a new user. Highlighting these viewpoints helps teams rephrase in clear, positive terms.
