writing-skills

Testable documentation is written by aligning content with RED-GREEN-REFACTOR cycles, establishing baseline tests, and hardening guidance through refactoring to ensure it remains concise and verifiable.

Progressive disclosure organizes skill documentation using frontmatter, inline guidance, and optional references to keep context minimal and reusable, which is essential when managing large instructional documents.

Structure SKILL.md files by enforcing frontmatter requirements, applying domain-focused organization, and keeping references one-level deep to ensure deployment readiness and consistent naming across collections.

Writing testable guidance requires no external dependencies or frameworks; it uses a test-driven approach applied directly to the documentation content to verify conciseness and robustness.

The limitation of a test-driven approach for skill writing is its strict enforcement of one-level deep references and frontmatter requirements, which may restrict highly complex, deeply nested documentation structures.