What problem does it solve? Writing effective agent skills without testing leads to documentation that agents ignore, misinterpret, or rationalize away under pressure. This Skill applies test-driven development to skill authoring so every skill is verified against real agent behavior before deployment. ## Core Features & Use Cases - TDD-Based Skill Authoring: Follows the RED-GREEN-REFACTOR cycle, running baseline pressure scenarios with subagents before writing any skill content. - Rationalization Bulletproofing: Provides techniques to close loopholes, build rationalization tables, and create red-flag lists that keep agents compliant under time, sunk-cost, and authority pressure. - Discovery Optimization (CSO): Defines rules for names, descriptions, keywords, and token efficiency so future agents can find and correctly trigger the skill. - Use Case: When creating a new discipline-enforcing skill like TDD or verification-before-completion, run baseline scenarios without the skill, document the agent's exact excuses, then write minimal content that counters those specific rationalizations and re-test until bulletproof. ## Quick Start Ask the agent to create a new skill for a recurring technique, requiring baseline pressure-scenario testing with subagents before writing the SKILL.md file.