writing-skills

Test-driven documentation for skills uses a RED-GREEN-REFACTOR cycle to draft, validate, and refine SKILL.md files by enforcing baseline failures before deployment. You establish failing tests, write minimal documentation to pass them, and then refactor iteratively.

Subagent pressure scenarios are iterative testing sessions that uncover rationalizations and close loopholes in skill documentation. They validate the SKILL.md structure by actively probing the documentation for weaknesses before final deployment.

YAML frontmatter for skill writing requires strict discipline to ensure concise descriptions and an actionable SKILL.md structure. You must define metadata fields accurately during the drafting phase to pass the baseline validation checks.

The best way to verify skill documentation is running a RED-GREEN-REFACTOR workflow with subagent pressure scenarios. This process targets the creation, editing, and verification of skills to ensure bulletproof documentation through iterative testing.

No dependencies are required to start writing test-driven skills. You only need to draft a minimal SKILL.md that addresses observed failures and then run the RED-GREEN-REFACTOR cycle to verify compliance.

You should use a test-driven workflow for skill updates whenever editing or creating skills to prevent error-prone documentation. It codifies a disciplined testing loop to validate changes and ensure bulletproof documentation before deployment.