writing-skills

Skill documentation uses a RED-GREEN-REFACTOR workflow to ensure it guides agent behavior. You capture baseline failures first, write a minimal Skill to fix them, and re-test to verify compliance before refactoring.

The RED-GREEN-REFACTOR cycle for skill writing involves documenting a baseline failure, implementing a minimal Skill to pass the test, and rationalizing the closure. This verifies that documentation actively guides agent behavior.

You verify Skill documentation guides agent behavior through test-driven verification and baseline failure capture. By testing against a RED scenario and confirming a GREEN pass, you ensure the documentation is functional.

Yes, test-driven development supports multi-phase Skill architectures. It provides guidance on when to separate orchestrator and phase commands, ensuring scalable and structured multi-phase documentation.

A standardized SKILL.md template requires specific frontmatter and structured sections. It enforces compliance with these requirements to ensure the documentation meets the baseline for test-driven verification.

Documenting baseline failures before writing a Skill establishes a RED scenario that proves the current state is insufficient. This test-driven approach ensures you write a minimal GREEN Skill specifically targeted to fix the verified gap.