Verification Gate

Overview

This skill implements mandatory verification checkpoints that prevent pattern-matching from training data from overriding explicit reasoning. It enforces structural gates between hypothesis formation and action execution, ensuring actions align with verified hypotheses rather than reflexive pattern-matching responses.

When to use this skill:

• Before executing ANY implementation action (Bash, Write, Edit, NotebookEdit)
• After stating a hypothesis about what system/component has an issue
• When choosing between multiple implementation approaches
• When detecting potential pattern-matching from training data
• When error messages or observations could trigger multiple solution paths

Core principle: Verification is not advisory—it is a mandatory gate. Actions that don't align with verified hypotheses are BLOCKED.

Mandatory Pre-Action Verification Gate

Before executing ANY implementation action, complete ALL checkpoints in sequence. If any checkpoint fails, HALT and report the failure.