writing-skills

Test-driven documentation is creating documentation by first writing tests to define expected behavior, then writing the documentation to address those failures. This ensures your documentation is clear, consistent, and applicable to the documented process.

To write documentation for agents, start by writing a failing test that defines the behavior you want to encourage or prevent. Then, write the skill content to address the specific failures observed in the test.

The best way to ensure process documentation is effective is to apply test-driven development principles. By writing tests first, you validate that the documentation meets necessary requirements and remains easy for agents to follow.

Yes, test-driven documentation provides guidelines for skill authoring best practices. It offers examples and patterns for different skill types, ensuring your documentation is concise, well-structured, and tested for agent comprehension.

You need test-driven documentation when creating comprehensive documentation that must be effective and applicable. It is designed for agents to understand and implement practices, ensuring clarity and consistency across the entire process from writing tests to finalizing.