writing-skills

You use TDD for skill development by adapting the RED-GREEN-REFACTOR cycle to author and validate documentation skills, starting with a failing test scenario before writing the skill logic.

The best way to prevent rationalization is to apply countermeasures that close loopholes, testing skills under realistic constraints like sunk cost and authority to ensure agents do not bypass requirements.

You pressure test agent behavior by simulating realistic constraints such as time pressure, sunk cost, and authority, which uncovers rationalizations and ensures the skill remains robust under stress.

Yes, you can apply TDD principles to enforce code review policies by writing test scenarios that simulate pressure, like an urgent deadline, to ensure agents follow the new skill even when tempted to skip it.

Agents skip documentation requirements under deadline pressure due to rationalizations; this skill addresses this by defining pressure testing methodologies and countermeasures to enforce compliance.

No dependencies are required to start creating skills with TDD; you only need to follow the RED-GREEN-REFACTOR cycle and define test scenarios to validate agent behavior and documentation compliance.