writing-skills

Prevent agents from bypassing compliance in skill documentation by applying test-driven development to process writing, using subagent pressure scenarios to verify rules hold under time, sunk-cost, authority, or exhaustion incentives.

The RED-GREEN-REFACTOR workflow for skill authoring requires observing baseline documentation failures first, writing minimal rule-focused updates to fix them, adding explicit loophole counters, and running verification re-tests with subagents to ensure compliance.

Bulletproof agent skills against rationalization by capturing agent rationalizations verbatim during pressure testing, adding explicit negations and counters to the documentation, and re-verifying with subagents until compliance remains stable under pressure.

Improve Claude Search Optimization for agent skills by writing a third-person, trigger-focused description in the documentation and ensuring comprehensive keyword coverage that matches how users search for the skill's core task.

Yes, you need subagents to pressure test agent skill compliance because they simulate scenarios where agents have incentives to rationalize away rules, allowing you to observe baseline failures and verify that documentation updates remain effective.

Use test-driven development for writing agent skills whenever creating, editing, or deploying any Skill where compliance could be rationalized away under pressure, ensuring the documentation stays correct and resists agent rationalization.