Menu
Use when a unit of work has no executable acceptance (no test, no verifiable output) and you need to construct one - golden files, property tests, metamorphic relations, snapshot tests - or prove it infeasible.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use during any Hyperworkflows delivery merge phase - single-merger protocol, MERGE_TOKEN lifecycle, full-suite gating, and revert-and-quarantine rules.
Use when rendering any Hyperworkflows result to a human - the mandatory report format with verified/unverified/quarantined+grey buckets, coverage arithmetic, and evidence links.
Use when a contested set needs rulings - court procedure (advocate/skeptic/risk-officer), evidence requirements, sequential fallback, and escalation rules.
Use before building or auditing against acceptance contracts - systematically finds missing acceptance dimensions so "all green but wrong" cannot ship through contract holes.
| name | oracle-forging |
| description | Use when a unit of work has no executable acceptance (no test, no verifiable output) and you need to construct one - golden files, property tests, metamorphic relations, snapshot tests - or prove it infeasible. |
A missing oracle is a work item, not a label. Forge executable acceptance in this preference order — strongest first:
diff <(cmd) fixtures/golden.txt; exit code 0. Strongest oracle; brittle only if the output legitimately varies.f(x) == f(shuffle(x)), count(filter(p)) <= count(all), decode(encode(x)) == x.Rules: