Writing Skills

This is test-driven development applied to writing documentation. Instead of testing code, you're testing whether agents actually follow your instructions. You write pressure scenarios with subagents, watch them fail without your skill present, then write the skill document to address those specific failure modes. The approach catches the gap between what you think you communicated and what agents actually understood. It includes solid guidance on skill structure, Claude search optimization, and when skills are worth creating versus just putting notes in project files. The TDD mapping table alone makes the mental model click.