writing-skills

Test-driven development for skill documentation means writing test cases (pressure scenarios) first, watching them fail with baseline behavior, then writing the skill to pass tests, and refactoring to close loopholes. This ensures your skill resists rationalization and agent bypass attempts before deployment.

Bulletproof skills by explicitly closing rationalization loopholes through pressure-scenario testing with subagents, building rationalization tables that address "spirit vs. letter" arguments, and enforcing RED-GREEN-REFACTOR cycles. This proactive approach makes skills resistant to bypass and compliance drift.

Optimize skill discoverability by writing rich descriptions with targeted keywords, using domain vocabulary in naming, and structuring documentation for search intent. The writing-skills approach guides keyword placement and naming conventions to increase findability for users searching related tasks.

Formalize a technique into a skill when you've identified a reusable pattern that solves a recurrent problem. Use test-driven documentation to validate the pattern under pressure scenarios, ensure clarity for discovery, and bulletproof it against rationalization before publishing for others to adopt.

Yes. Apply TDD retrospectively by writing pressure-scenario tests against existing documentation, identifying gaps where agents might rationalize exceptions, refactoring the documentation to close those gaps, and verifying compliance through subagent testing cycles.

Clear documentation explains what a skill does; bulletproof documentation anticipates how agents might rationalize bypassing it and explicitly closes those loopholes. Test-driven refinement surfaces rationalization vectors through pressure scenarios, transforming clarity into resistance to agent drift.