What problem does it solve? Untested skill documentation often fails in practice because agents rationalize around rules under time, sunk-cost, or authority pressure, and authors cannot know whether a skill actually changes agent behavior without observing baseline failures first. ## Core Features & Use Cases - TDD-based skill authoring: Applies the RED-GREEN-REFACTOR cycle to documentation by running baseline pressure scenarios with subagents, writing minimal skills that address observed failures, and closing rationalization loopholes iteratively. - Discovery optimization (CSO): Provides rules for writing trigger-focused descriptions, keyword coverage, naming conventions, and token-efficient skill structure so agents can find and load the right skill. - Testing methodology references: Includes guidance on pressure scenario design, rationalization tables, persuasion principles, and Anthropic's official authoring best practices. - Use Case: Before deploying a new discipline-enforcing skill like a TDD requirement, run combined-pressure scenarios (time + sunk cost + exhaustion) against subagents without the skill, capture verbatim rationalizations, then write and refactor the skill until agents comply under maximum pressure. ## Quick Start Ask the agent to create a new skill for a recurring technique, first running baseline pressure scenarios with subagents and then writing the SKILL.md following the RED-GREEN-REFACTOR checklist.
