writing-skills

To create and validate Skills, draft a SKILL.md with mandatory frontmatter and implement the body using a Red-Green-Refactor workflow for quality assurance. This test-driven documentation process ensures your Skills are concise, discoverable, and verifiable before release.

The Red-Green-Refactor workflow is a test-driven cycle for skill creation that captures repeatable patterns. You draft tests, implement the Skill body to pass them, and refine the documentation to close loopholes, ensuring progressive disclosure and deployment discipline.

Structure SKILL.md files by defining mandatory frontmatter like name and description, then implement the body with progressive disclosure patterns. This structure enforces quality assurance and ensures discoverability across the Skill library.

Skill documentation fails to survive edits when it lacks test-driven validation and structured frontmatter. Applying a Red-Green-Refactor workflow during skill creation establishes repeatable patterns that prevent premature or poorly defined documentation across projects.

Yes, you can refine existing Skill documentation by applying the Red-Green-Refactor workflow to validate content and enforce progressive disclosure. This test-driven process closes loopholes and ensures your Skills remain verifiable and safe for deployment.

Without a test-driven workflow, Skill documentation risks becoming premature, poorly defined, and difficult to discover. Managing Skills without structured frontmatter and validation loops prevents repeatable patterns and breaks deployment discipline across the library.