writing-skills

Test-driven development for skill documentation applies a RED-GREEN-REFACTOR cycle to create, verify, and refactor skills. This enforces verifiable quality through evidence-based testing and explicit rationalization tracking.

Writing a SKILL.md file requires strict YAML frontmatter for name and description, followed by a concise, non-narrative body. Progressive disclosure organizes content into inline guidance with references and tools loaded on demand.

Ensuring quality assurance during skill creation involves maintaining explicit rationalization tables, checking for red flags, and validating deployment readiness criteria to guarantee safe and repeatable deployment.

Yes, you can apply the RED-GREEN-REFACTOR cycle to existing skill documentation. This validates current requirements through evidence-based testing, verifies safety checks, and cleans up rationalization tracking.

Rationalization tracking is needed during skill writing when documenting verification and refactoring cycles. It maintains quality assurance by explicitly recording decisions, flagging safety risks, and ensuring deployment readiness.

Progressive disclosure scales for complex skill creation by organizing detailed content into on-demand references and tools. This keeps the core SKILL.md concise while ensuring comprehensive guidance remains accessible.