---

name: enforcement description: "Use when implementing hooks that BLOCK invalid actions, creating quality gates for state transitions, or enforcing tested:true verification. Load when designing enforcement mechanisms. Uses exit code 2 to block, JSON permissionDecision:deny, or updatedInput modification. Rules are instructions; hooks are enforcement." keywords: hooks, blocking, quality-gates, verification, exit-code-2, deny

Enforcement

Runtime mechanisms that block invalid actions.

Core Principle

"Rules are instructions, not enforcements. Systems need verification gates, not more documentation."

Instructions

1. Identify what needs enforcement (not just documentation)
2. Choose hook timing: PreToolUse, PermissionRequest, SubagentStop
3. Implement blocking logic: scripts/block-*.sh
4. Test with invalid action → verify block

Blocking Mechanisms

Hook Timing

References