writing-skills

Test-driven development for skill documentation applies a RED-GREEN-REFACTOR workflow to writing, starting with a baseline RED test to surface failures, then crafting a minimal GREEN skill and iterating until no rationalizations remain.

The best way to structure skill documentation for quality assurance is enforcing YAML frontmatter with required fields like name and description, followed by clear sections for Overview, Rules, and Validation steps.

Start creating a new skill by writing a baseline RED test to surface documentation failures, then craft a minimal GREEN skill and re-run the RED-GREEN-REFACTOR cycle until all rationalizations are eliminated.

Skill documentation fails in real usage when it is unverified and poorly structured, lacking iterative refinement across multiple stress scenarios and discipline-enforcing validation steps to catch edge cases.

Yes, the RED-GREEN-REFACTOR cycle enforces YAML frontmatter requirements by testing for required fields like name and description with length limits, ensuring skills meet quality standards before deployment.

Track rationalizations during the skill writing process when iterating through RED-GREEN-REFACTOR cycles, using them as red flags to identify discipline-enforcing content gaps and ensure complete documentation before deployment.