Writing Skills

Test-driven documentation for reusable Gemini skills requires creating a directory under .gemini/skills/, adding a SKILL.md file with frontmatter, and running baseline pressure scenarios with subagents to validate behavior before deployment.

The red-green-refactor process for skill writing applies test-driven development to documentation by defining pressure scenarios, validating them with subagents, and iterating on the SKILL.md structure to ensure repeatability and bulletproof results.

To structure a Gemini skill directory, create a root folder under .gemini/skills/ containing a SKILL.md file with frontmatter, and add optional scripts, references, and assets directories to support complex workflows.

Yes, verifying process documentation before deployment requires using subagents to run pressure scenarios, ensuring the test-driven documentation produces accurate and repeatable results in your skills library.

A SKILL.md file in the skills library requires frontmatter that includes at least the skill name and description to enforce consistent structure and enable test-driven validation.

Yes, you can apply test-driven development to improve existing process documentation by defining new pressure scenarios, validating outputs with subagents, and refactoring the workflow to achieve process improvement.