What problem does it solve?
Writing skills without seeing real failures leads to vague rules that agents can rationalize around. This Skill applies a rigorous test-driven approach to process documentation so you identify concrete failure modes first, then iteratively harden the Skill until agents comply even under pressure.
Core Features & Use Cases
- RED-GREEN-REFACTOR for Skills: Run baseline tests without the Skill, capture exact rationalizations, then write minimal rules and refactor to close loopholes.
- Pressure Scenario Design: Craft realistic, multi-pressure scenarios (time, sunk cost, authority, exhaustion) that force explicit choices and expose true failure modes.
- Rationalization Tables & Red Flags: Systematically record excuses, add explicit negations, and update descriptions with violation symptoms to prevent backsliding.
- Use Case: Hardening a TDD enforcement Skill so agents consistently choose to delete code written before tests, citing the Skill under maximal time and sunk-cost pressures.
Quick Start
Run a baseline pressure scenario without the target Skill, document the agent’s rationalizations verbatim, then enable this Skill and iterate until the agent consistently complies under the same pressures.