writing-skills

Test-Driven Documentation applies a TDD-like cycle to writing process documentation, using baseline testing and refactoring to close loopholes. This ensures documentation is clear, discoverable, and adhered to by agents under pressure.

Start by writing failing test scenarios to identify what agents do without the skill, then write minimal documentation to address those scenarios, and finally refactor to close any compliance loopholes.

Optimize skill discovery by writing rich descriptions, ensuring broad keyword coverage, and using descriptive naming. This makes process documentation easier for agents to find and apply correctly.

Yes, applying persuasion principles like authority, commitment, and social proof is required to ensure agents follow the documentation consistently, especially when operating under pressure.

Yes, you can refactor existing skill documentation by identifying baseline test scenarios and closing loopholes. This refactoring step minimizes documentation while maximizing agent compliance.

Documentation may lack persuasion principles like authority and social proof. Applying these techniques ensures skills are followed even under pressure, closing compliance loopholes through refactoring.