writing-skills

Test-driven documentation applies TDD principles to process documentation by writing failing test cases first, creating the documentation to pass those tests, and verifying that agents comply with the specified requirements.

You implement the RED-GREEN-REFACTOR cycle for documentation by writing failing pressure scenarios, developing the process documentation to make them pass, and refactoring the content to ensure accurate requirement reflection.

Yes, you can apply Test-Driven Development to skill creation by using pressure scenarios as test cases, authoring the skill documentation, and verifying agent compliance to ensure the skill accurately reflects necessary processes.

The best way to ensure process documentation accurately reflects requirements is using a test-driven approach where you write failing test cases first, then develop the documentation until agents comply with the specified processes.

Test-driven documentation does not require external testing frameworks, as it uses pressure scenarios as test cases and verifies agent compliance directly against the authored skill documentation without any dependencies.

You should avoid using a TDD approach for documentation when your process lacks clear, testable requirements, as the RED-GREEN-REFACTOR cycle depends on writing specific failing test cases before developing the documentation.