writing-skills

You can use test-driven development for skill creation by applying the RED-GREEN-REFACTOR cycle to documentation. This enforces rigorous baseline testing and minimal skill writing to iteratively refine agent behavior.

The best way to prevent rationalization is to define pressure scenarios that test skill compliance under constraints like time pressure. This identifies and blocks common excuses agents use to bypass rules.

The RED-GREEN-REFACTOR cycle applies to documentation by requiring rigorous baseline tests first, writing minimal skill content to pass those tests, then iteratively refactoring to close loopholes and prevent rationalization.

No dependencies are required to apply this test-driven skill creation framework. It operates independently using built-in references to guide you through generating test scenarios and countermeasures.

Testing under pressure scenarios ensures skills remain effective and compliant even when agents are tempted to skip steps. It validates that your documentation successfully resists rationalization under stress.

This approach requires rigorous baseline testing and iterative refactoring, which demands strict adherence to the cycle. You must continuously close loopholes in documentation to prevent agents from finding rationalization workarounds.