writing-skills

Test-driven development for skills means running pressure scenarios first to document how agents fail or rationalize, then writing skill documentation to make them comply, and refactoring to close loopholes. This RED-GREEN-REFACTOR cycle ensures your skills are bulletproof and consistently adopted.

Document agent rationalizations during pressure scenarios, then add explicit counters to your skill documentation. Re-test after each refactor to catch new workarounds. This iterative approach closes gaps agents use to justify non-compliance.

Apply TDD to skill documentation whenever you need agents to follow rules reliably under pressure. It's essential for internal team skills where consistency matters and agents might rationalize exceptions. Testing before writing catches failures early and reduces deployment errors.

Yes. TDD applies across creating, editing, and validating skills. Run pressure scenarios against your current skill, document failures and rationalizations, update the documentation to address them, and iterate until compliance is achieved.

Your skill is deployment-ready when agents pass all pressure scenarios without rationalizing exceptions. Run tests before writing, enforce the RED-GREEN-REFACTOR lifecycle, and iterate until both compliance and robustness are verified.