writing-skills

Create skill documentation using TDD by drafting a SKILL.md with YAML frontmatter, implementing a minimal GREEN version to pass RED-GREEN-REFACTOR baseline tests, and planning REFACTOR steps to close loopholes.

The RED-GREEN-REFACTOR workflow for skill creation defines failing tests first, implements a minimal GREEN version to address baseline failures, and refactors SKILL.md to close loopholes and ensure verifiable guidance.

Agents ignore process documentation when it lacks verifiable triggers and discipline enforcement. Applying TDD principles to skill writing provides repeatable, trigger-focused descriptions that prevent rationalizations and ensure agent compliance.

Yes, you need YAML frontmatter in SKILL.md files to define the name and a concise, trigger-focused description, ensuring the documentation meets baseline testing requirements and enables proper skill automation.

The best way to prevent rationalizations in agent workflows is enforcing TDD discipline during skill creation, using a RED-GREEN-REFACTOR process to maintain repeatable, verifiable guidance and close documentation loopholes.

You should not use TDD for documentation when a skill requires rapid prototyping without verifiable tests or lacks baseline failures to address, as the RED-GREEN-REFACTOR workflow targets bulletproof, tested skill creation.