behavioral requirements Shipped
What this lens looks for
Write behavioral/integration requirements as kebab-case named items using RFC 2119 keywords (MUST/SHOULD/MAY) per their exact semantics. Each requirement is independently testable and describes behavior, not implementation. Use specific numeric or string values rather than vague qualifiers ("within 200ms", not "quickly"). One requirement per behavior — do not bundle.
What its verifier checks
Every requirement has a kebab-case name and a correct RFC 2119 keyword; each is independently testable; none describe implementation detail; specific values appear where applicable; no two behaviors are bundled into one requirement.