writing-skills

Test-driven development for process documentation uses a RED-GREEN-REFACTOR cycle to drive baseline testing, implement requirements, and refine structured content. This ensures SKILL.md files remain robust before deployment.

To write a skill using the RED-GREEN-REFACTOR workflow, document baseline failures first, implement the skill to address those failures, and then refine to close loopholes. Explicit frontmatter and structured sections guide this process.

Yes, you can verify skills before deployment across agent types by applying targeted scenarios and iterative refinement. This test-driven approach ensures the documentation standards are resistant to common rationalizations.

Structured skill documentation requires explicit rationalization tables and red flags to guide future agents. These elements prevent common rationalizations and ensure the process documentation remains robust.

The TDD approach for skill writing is limited to discipline-enforcing, technique, or reference skills that benefit from formal testing. It requires explicit frontmatter and structured sections, making it heavy for simple tasks.

The best way to document baseline failures when editing a skill is to apply the RED phase of the RED-GREEN-REFACTOR cycle. This captures existing requirements and failures before implementing fixes and refining content.