What problem does it solve?
Writing or editing process documentation often leads to unclear, unused, or loophole-ridden skills that agents ignore under pressure. This Skill applies Test-Driven Development to documentation so you create concise, discoverable, and enforceable skills that actually change behavior.
Core Features & Use Cases
- TDD for Documentation: RED-GREEN-REFACTOR cycle using subagents to create failing baselines, write minimal guidance, and close rationalization loopholes.
- Discovery & Token Efficiency: Rich, symptom-focused descriptions, keyword strategy, naming conventions, and strict brevity to keep frequently-loaded skills lightweight.
- Testing Playbooks: Tailored test strategies for discipline, technique, pattern, and reference skills, plus checklists, rationalization tables, and red-flag heuristics.
- Use Case: Before adding a new “condition-based-waiting” technique, you run subagent pressure scenarios to observe failures, write the minimal SKILL.md addressing those gaps, and iterate until agents consistently comply.
Quick Start
Ask the assistant to run a baseline subagent scenario without any skill, capture the failures and rationalizations, then write the minimal SKILL.md and re-test until it passes under pressure.