writing-skills

Automate Skill creation by applying a RED-GREEN-REFACTOR cycle to documentation: capture baseline failures, implement a minimal SKILL.md, and close loopholes through iterative testing. This test-driven writing process enforces documentation quality and validates guidance before deployment.

Progressive disclosure in SKILL.md documentation organizes content by separating core guidance from optional tooling directories like scripts, references, and assets. This structure keeps the context lean and targeted, preventing information overload while maintaining comprehensive process documentation.

Structure YAML frontmatter for SKILL.md files by including only the required name and description fields. This quality gate enforces strict metadata requirements, ensuring process documentation remains standardized and valid before Skill deployment.

Validate Skills documentation by applying test-driven writing workflows that enforce frontmatter requirements and structured guidance sections. The RED-GREEN-REFACTOR cycle captures baseline failures and iteratively closes loopholes, ensuring a quality guarantee before deployment.

No dependencies are required to write and edit SKILL.md files. The test-driven writing process operates independently, using built-in quality gates to validate YAML frontmatter and progressive disclosure structures without external tooling.

Avoid test-driven development for documentation when creating highly exploratory or non-reusable guides lacking repeatable validation criteria. This approach formalizes structured SKILL.md workflows, so it may add unnecessary overhead to simple, informal notes or one-off content.