writing-skills

Test-driven development for skill documentation applies the RED-GREEN-REFACTOR cycle to validate guidance before deployment. It requires baseline testing to ensure descriptions, structure, and frontmatter reliably validate discovery and harden skills against misuse.

To write a SKILL.md using the RED-GREEN-REFACTOR cycle, create a minimal file with YAML frontmatter containing only name and description, write concise inline instructions, then run pressure-scenario templates to validate and refactor the documentation loop.

Test-driven documentation improves skill reliability by codifying evaluation patterns and rationalization tracking. It uses pressure-scenario templates to harden skills against misuse and ensures frontmatter validates discovery before deployment.

Yes, you need baseline tests before writing skill documentation. The test-driven approach requires establishing baseline testing first to validate the structure, descriptions, and frontmatter before proceeding with the actual skill creation or editing.

The best way to structure skill documentation without bloating is using modular organization. Keep the main SKILL.md concise with inline instructions, and use references, scripts, and assets to manage heavy content separately.

Skill documentation lacks testability and repeatability when it misses clear evaluation criteria and structured testing. Applying test-driven development codifies the RED-GREEN-REFACTOR cycle to validate guidance and enforce structured frontmatter.