writing-skills

Test-driven skill documentation applies RED-GREEN-REFACTOR discipline to process docs by running baseline pressure scenarios first, updating rules to enforce compliance, then re-testing until no rationalizations appear.

Pressure scenarios in documentation testing are designed situations involving time constraints, sunk cost, authority, or exhaustion that reveal when agents attempt to bypass skill rules and rationalize noncompliant behavior.

Anti-rationalization hardening builds explicit negations, rationalization tables, and red flags into skill documentation to close discovered loopholes and ensure rules remain enforced under real operational pressure.

TDD for skill authoring is needed when documentation must enforce specific behavior rather than serve as passive reference, catching rationalizations that cause agents to bypass rules under real pressure.

Existing skill documentation can be edited using test-driven development by running a baseline pressure scenario without the updated rules, then modifying the skill to make the same scenario comply and re-testing.

Skill documentation fails under pressure when it lacks explicit negations and documented baseline failures, allowing agents to rationalize rule bypasses that pressure scenarios involving time, authority, or sunk cost reveal.