ucsc-vlaa/visualclaw/exec-check-requirement-audit

Audit the Output Against Every Stated Requirement

1. List the requirements: Re-read the task and extract every explicit requirement — required keys, required assertions, required citations, value formats, output path.
2. Check each one: For every requirement, point to where the produced file satisfies it. If you cannot, the file is not done.
3. Treat "must" / "include" / "at least N" as hard constraints: These are check-script conditions, not suggestions.
4. Verify before declaring done: Do not end the round until every listed requirement is accounted for.

Example: Task says "list charge codes A, B, C and cite the clip" — confirm all three codes are present AND a clip citation exists before finishing.

Anti-pattern: Producing a plausible-looking file that silently omits one required field, assertion, or citation.