write-skill

To create skills that resist rationalization, apply test-driven development to skill documentation by running pressure scenarios first, observing agent failures, then writing minimal counter-measures. This ensures the skill enforces discipline when agents face time, sunk cost, or authority pressures.

Test-driven development for skill documentation applies the RED-GREEN-REFACTOR cycle to skill creation. You watch agents fail without the skill to establish baseline behavior, write minimal documentation to make them pass, then close loopholes during the refactor phase.

Pressure testing AI skills involves simulating combined pressures such as time, sunk cost, authority, and exhaustion. You document verbatim agent failures during these scenarios and iteratively add counter-measures to the skill documentation until compliance is achieved.

Agents bypass discipline-enforcing skills by finding rationalizations to skip steps under pressure. You prevent loopholes by systematically identifying these rationalizations during pressure testing and iteratively closing them with explicit counter-measures in the skill documentation.

Start the skill creation lifecycle by running a pressure scenario without the skill to establish baseline behavior. Document the specific failures verbatim, then write minimal documentation addressing those exact failures to move from RED to GREEN.

Use a TDD approach for editing existing skills when you need to verify they work before deployment or when agents fail to follow them under pressure. It ensures changes resist rationalization by testing against specific pressure scenarios.