What problem does it solve? Writing effective agent skills without testing leads to documentation that agents ignore, misinterpret, or rationalize away under pressure, resulting in unreliable behavior. ## Core Features & Use Cases - TDD-Based Skill Authoring: Applies the RED-GREEN-REFACTOR cycle to documentation by running baseline pressure scenarios with subagents before writing any skill content. - Skill Discovery Optimization: Provides rules for writing descriptions, naming conventions, keyword coverage, and token efficiency so agents can find and load skills correctly. - Rationalization Bulletproofing: Includes techniques like rationalization tables, red flag lists, and persuasion principles to close loopholes agents exploit under time or sunk-cost pressure. - Use Case: When creating a new discipline-enforcing skill like a TDD requirement, run pressure scenarios with subagents first, document their verbatim excuses, then write the skill to counter those specific rationalizations. ## Quick Start Ask the agent to create a new skill following the test-driven development process, starting with baseline pressure scenarios before writing any documentation.
