writing-skills

Test-driven development for documentation maps the RED-GREEN-REFACTOR cycle to skill creation, ensuring you baseline agent behavior before writing instructions to produce bulletproof process documentation.

Agents often rationalize away critical instructions under time, sunk cost, or authority pressures. You can prevent this by pressure testing skills with realistic scenarios and building rationalization tables to close loopholes.

The RED-GREEN-REFACTOR cycle for skill authoring involves baselining agent behavior before writing instructions, writing the skill to address observed failures, and refactoring documentation with red flag lists to maintain compliance.

You create realistic pressure scenarios by introducing time constraints, sunk cost pressures, and authority pressures that expose rationalizations, allowing you to identify and close loopholes in your skill documentation.

Yes, you can use subagents within RED-GREEN-REFACTOR testing cycles to verify that coding agents comply with your process documentation under pressure scenarios before deployment.

Rationalization tables document agent rationalizations under pressure, providing patterns to close loopholes and create red flag lists that keep agents compliant with critical instructions during deployment.