writing-skills

Test-driven documentation for skill creation involves generating pressure scenarios for subagents, iteratively refining the skill's process documentation, and verifying it passes all tests to ensure robustness against rationalization.

The best way to verify process documentation is by creating pressure scenarios for subagents. You iteratively test and refine the documentation until the skill is bulletproof and resists rationalization during execution.

To create test cases for subagent testing, run the skill generation process to define pressure scenarios first. You then iterate on the skill's implementation based on subagent feedback until it meets all requirements.

Yes, subagent testing skills are required. The documentation process relies on creating pressure scenarios for subagents to validate the process and ensure the final skill is robust against rationalization.

Use test-driven documentation when editing existing skills to ensure modifications do not introduce rationalization vulnerabilities. It validates changes through subagent pressure scenarios and iterative refinement.

Skills fail under subagent pressure scenarios when the process documentation lacks iterative refinement. Test-driven documentation addresses this by continuously testing against scenarios until the skill becomes bulletproof.