writing-skills

To create bulletproof documentation using TDD, you apply the RED-GREEN-REFACTOR cycle to skill creation by writing subagent pressure scenarios first to validate agent compliance before finalizing the process documentation.

TDD for documentation is a process where you write subagent pressure scenarios as tests to see how agents fail without the skill, then write the skill to fix those specific failures, ensuring robustness.

You close loopholes in agent compliance documentation by systematically applying TDD principles to identify common rationalizations agents might exploit, then rewriting the skill to address those specific pressure scenarios.

Yes, using a TDD approach for skill creation works with existing process documentation by applying the RED-GREEN-REFACTOR cycle to editing, validating effectiveness through subagent pressure scenarios before and after implementation.

You should use TDD for writing skills instead of standard documentation when you need to ensure strict agent compliance and robustness, systematically addressing common rationalizations and loopholes that agents might exploit under pressure.

Your agent skips process documentation requirements under pressure because the skill contains loopholes allowing rationalization; applying TDD to skill creation systematically identifies and closes these compliance gaps using subagent pressure scenarios.