writing-skills

Use a RED-GREEN-REFACTOR workflow to write and validate skill documentation, ensuring consistent, testable SKILL.md entries with verifiable tests and guardrails against rationalization and drift.

Test-driven development for writing skills applies software TDD principles to process documentation, enforcing discipline, guardrails, and consistent outcomes when creating reusable agent behaviors in SKILL.md entries.

Create a new SKILL.md by adding YAML frontmatter with name and description, then writing a concise body following required sections, testing patterns, and deployment criteria to keep skills consistent, searchable, and loadable.

Prevent skill duplication and drift by guiding ongoing maintenance, refactoring, and cross-skill references within the skill library, ensuring all SKILL.md entries remain consistent, testable, and free of rationalization.

Yes, you can edit and verify existing skills before production deployment by validating frontmatter constraints, required sections, and testing patterns to ensure all SKILL.md entries meet deployment criteria and guardrails.

Using TDD for process documentation requires strict adherence to RED-GREEN-REFACTOR cycles and frontmatter constraints; SKILL.md entries that skip required sections or testing patterns will fail verification and block production deployment.