writing-skills

Test-driven documentation captures baseline failures by writing a failing skill first, then implementing a minimal SKILL.md using the RED-GREEN-REFACTOR workflow to verify compliance. You re-run tests after implementation to confirm agent behavior matches requirements.

A rationalization table tracks loopholes and edge-case justifications during skill writing to close gaps and demonstrate robust behavior. It enforces disciplined test-driven documentation by recording baseline failures and subsequent compliance verification.

Progressive disclosure structures skill documentation with YAML frontmatter containing name and description, followed by a structured multi-section description. Heavy references load only when needed, ensuring baseline failures and rationalizations remain verifiable.

Yes, test-driven development ensures skills are deployed only after successful testing. You write a failing baseline skill, implement a minimal version using RED-GREEN-REFACTOR, then re-run tests to confirm agent compliance before deployment.

Skill documentation fails under pressure testing when it lacks disciplined test-driven practices, leading to inconsistent behavior and unverified deployment readiness. Capturing baseline failures and maintaining a rationalization table closes loopholes and demonstrates robust behavior.

Write a failing baseline skill first, then implement a minimal SKILL.md with YAML frontmatter and a structured multi-section description using the RED-GREEN-REFACTOR workflow. Re-run tests to confirm agent compliance and verify rationalizations are tracked.