with-anti-rationalization

Anti-Rationalization Enforcement Skill

Overview

This skill operates as a composable modifier that wraps any task with explicit anti-rationalization enforcement. It implements the Gate Enforcement architectural pattern—every phase transition requires evidence, every completion claim requires proof—with Pressure Resistance embedded to prevent quality erosion under time or social pressure.

This skill is not a substitute for domain-specific methodologies (debugging, refactoring, testing have their own skills). Instead, it layers anti-rationalization checks on top of whatever task you're executing. It adds intentional overhead for safety on critical work where shortcuts cause harm.

---

Instructions

Phase 1: LOAD PATTERNS

Goal: Load all anti-rationalization patterns relevant to the task before starting work.

Constraint: Full pattern loading is mandatory because domain-specific patterns catch rationalizations that the core set misses.

Step 1: Identify task domain

Classify the task to determine which domain-specific patterns apply:

Domain	Pattern to Load
Any task	anti-rationalization-core.md
Code review	anti-rationalization-review.md
Testing	anti-rationalization-testing.md
Security	anti-rationalization-security.md
Multi-phase work	gate-enforcement.md
User pressure detected	pressure-resistance.md
Pre-completion	verification-checklist.md

Step 2: Load and acknowledge patterns

Read the identified shared-pattern files. Internalize the rationalization tables and enforcement rules. Constraint: State explicitly which patterns were loaded and why—this creates accountability and prevents performative checking.

Gate: All relevant patterns are loaded and acknowledged. Proceed only when you can articulate why each pattern applies. Rubber-stamp gate checks fail the purpose of the skill, so explain why each pattern is relevant before moving on.