Claude Skills by madduck-tech

Adversarial review of a claim before it is published. Use before publishing a diagnosis, an explanation of a mechanism, a conclusion that implies work, or a retelling of another review, including saying "the cause is X", "this is not our bug", "the class is closed", or "this will prevent it".

Discover and verify this project's real Stage 1 and Stage 2 mechanics, then record them in gopnik.json so Gopnik does not guess. Use during installation, when the config still has placeholders, or when delivery changed.

Adversarial verification before claiming a change works. Use before saying "done", "it works", "deployed and working" or "all green" about anything that executes — backend, runtime, UI, data schema. Use before any readiness claim about an executable change, whether requested or reached independently.