writing-skills

Test-driven development for documentation enforces a RED-GREEN-REFACTOR cycle, requiring you to baseline failing scenarios before writing minimal content that passes verification. This ensures every piece of documentation has measurable tests and verified guidance.

The RED-GREEN-REFACTOR cycle for skill creation involves baselining failing tests first, writing minimal SKILL.md content to pass those tests, and iteratively refactoring to close loopholes. This hardening process guarantees compliance before deployment.

Track rationalizations when editing process documentation by maintaining a dedicated rationalization table alongside defined red flags. This supports iterative hardening by capturing loopholes and ensuring explicit tracking across agent domains.

Yes, test-driven development applies to both creating new skills and editing existing ones. You baseline failing scenarios for the current skill, write minimal updates to pass tests, and refactor to maintain compliance before deployment.

Use progressive disclosure patterns in skill documentation when you need to keep the main body concise while still providing heavy references. This approach links to detailed references only when needed, preventing vagueness and inconsistent scope.

Skill documentation often has inconsistent scope and unverified guidance due to vague formal process writing. Applying test-driven development with pressure-based cycles and rationalization tracking closes loopholes and ensures measurable compliance.