writing-skills

You can automate skill documentation by writing a failing RED baseline test, implementing a minimal GREEN skill draft, and performing REFACTOR checks to validate readiness, safety, and dependencies before deployment.

Progressive disclosure in skill writing is a pattern that structures documentation to reveal information incrementally. Apply it when authoring complex skills to maintain concise descriptions and manage rationalization tracking effectively.

Yes, test-driven development applies to editing existing skills and verifying readiness. The workflow enforces YAML frontmatter validation, checks safety constraints, and validates dependencies to ensure units are deployment-ready.

The best way to enforce required YAML frontmatter fields is using a test-driven validation workflow that checks for mandatory metadata, maintains concise structured descriptions, and flags missing safety or dependency information during refactoring.

No external dependencies are required. The TDD skill drafting workflow runs autonomously to validate safety constraints, check optional resources, and enforce documentation standards using built-in templates and checklists.