writing-skills

Test-Driven Development for agent documentation applies the RED-GREEN-REFACTOR cycle to skill creation, ensuring instructions are written only after observing agent failures and explicitly addressing those failure points.

Preventing rationalization in agent documentation requires identifying and countering common excuses agents use to bypass instructions, ensuring skills are robust, discoverable, and reliably followed under pressure.

You need test-driven documentation when creating or editing any skill documentation to ensure it is rigorously tested, preventing ambiguity and ensuring agents can reliably follow instructions.

Ensuring agent skills are robust requires adherence to specific testing protocols and documentation structures, applying TDD rigor to solve the problem of poorly documented or untested skills.

Yes, test-driven documentation works for maintaining existing skills by applying the RED-GREEN-REFACTOR cycle to updates, ensuring documentation evolves with the same rigor as code.

Agents fail to follow complex instructions due to poorly documented or untested skills, which test-driven documentation solves by explicitly addressing observed failure points during the creation process.