Verification Before Completion

It forces a specific sequence: identify the command that would prove your claim, run it fresh and complete, read the actual output, then state your claim with evidence or admit it's not ready. The skill includes structured slots for what you checked, what you didn't, residual risk, and a confidence grade. It's surprisingly hard to follow when you're tired and just want the task over, which is exactly when you need it most. The paranoia extends to goal closure, workspace integrity checks, and explicit accounting of covered versus uncovered scope. If you've ever pushed code assuming the tests passed, this is the guardrail you were missing.