writing-skills

Test-driven process documentation involves defining pressure scenarios first, then writing and iteratively refining the skill until agents consistently follow the documented rules under verification.

Rationalization resistance ensures documented practices are impervious to common rationalizations agents might use to bypass rules, achieved by testing scenarios that expose vulnerabilities and iteratively closing loopholes.

Review baseline pressure scenarios without the skill, then iteratively write and refine the process documentation until agents consistently follow the documented rules without bypassing them.

You need test-driven verification when developing discipline-enforcing skills like TDD compliance, where test scenarios expose vulnerabilities in process documentation and iterative refactoring closes loopholes.

Yes, pressure scenarios validate discipline-enforcing skills by exposing vulnerabilities in the documented practices and enabling iterative refactoring to close loopholes that agents might exploit through rationalizations.

Process documentation fails when it lacks rationalization resistance, meaning practices are not validated through pressure scenarios and iterative refactoring to close loopholes agents might use to bypass rules.