writing-skills

Test-driven development for agent skill documentation applies a structured RED-GREEN-REFACTOR cycle to author and maintain process guides. You first define a failing pressure scenario, document the required behavior, and iterate to close loopholes.

To prevent rationalization in agent process guides, implement baseline failure testing and explicit rationalization counters during skill creation. This technique blocks agent excuses and enforces discipline under pressure by iteratively closing identified loopholes.

The best way to test agent documentation before deployment is defining a failing pressure scenario first. This test-driven approach verifies that process guides are robust, compliant, and resistant to agent rationalization under pressure before actual use.

You need test-driven development for process documentation when creating discipline-enforcing, technique, or pattern-based skills that require high reliability under pressure. It ensures compliance and robustness through baseline failure testing and iterative loophole closure.

Yes, test-driven documentation works for refactoring existing skills. By applying the RED-GREEN-REFACTOR cycle, you can update process guides, verify compliance through baseline failure testing, and explicitly close any new agent loopholes introduced during updates.