writing-skills

To document skills using test-driven development, apply RED-GREEN-REFACTOR cycles: draft baseline RED scenarios, implement a minimal skill to pass GREEN, and refactor to close loopholes and verify deployment readiness.

Rationalization tracking in skill validation is maintaining a formal table to surface and close loopholes during the REFACTOR phase, ensuring skill documentation resists rationalizations before deployment.

Validate SKILL.md content before deployment by running baseline tests without the skill, implementing the minimal skill to pass those tests, and executing deployment readiness checks with proper frontmatter.

Yes, skill creation requires running baseline tests without the skill to establish RED scenarios that fail initially, providing the test-driven foundation for implementing and validating the minimal skill.

The best way to structure skill documentation for progressive disclosure is incorporating proper frontmatter and a structured body during the REFACTOR phase, closing loopholes while maintaining deployment-ready steps and references.

Skill documentation fails deployment readiness checks when it lacks proper frontmatter, misses progressive-disclosure structure, or contains unresolved loopholes in the rationalization table that were not closed during the REFACTOR cycle.