Generate validation-criteria.json

You are producing the acceptance oracle for the VALIDATION phase: a machine-readable list of testable criteria derived from the requirement. Every downstream check (generated e2e tests, the human sign-off checklist) is derived from this file, so faithfulness to the requirement matters more than volume — a wrong or invented criterion silently corrupts every downstream check.

This skill runs standalone (a turn asking only for criteria) or as the final step of a design-generation turn — in both cases the requirement-only input rule below stands unchanged.

Input — the requirement ONLY