writing-skills

Test-driven documentation automates verification of skill definitions by running pressure scenarios with subagents to surface baseline failures before writing. This RED-GREEN-REFACTOR workflow ensures your skill meets frontmatter constraints and SKILL.md structure requirements while closing compliance gaps.

Yes. Test-driven skill documentation works across agent-specific directories by applying pressure scenarios to validate rules and structure. The workflow automates testing during skill creation, editing, and verification phases to ensure discoverable and maintainable skills.

RED-GREEN-REFACTOR evolves documentation alongside verification: RED tests expose failures, GREEN compliance brings the skill into spec, and REFACTOR closes loopholes. This cycle ensures skills satisfy frontmatter constraints and SKILL.md structure while remaining testable and discoverable.

Template-driven documentation defines a SKILL.md structure and frontmatter constraints that skills must satisfy. Run pressure scenarios with subagents to validate your skill against these templates; refactor based on failures until your documentation passes all compliance checks.

Pressure scenarios with subagents surface baseline failures and compliance gaps that manual review misses. This testing approach reveals whether your skill definition is discoverable, testable, and maintainable before deployment.

You need a skill definition ready for documentation, access to subagent testing infrastructure, and familiarity with SKILL.md structure and frontmatter constraints. The TDD framework then automates verification of your documentation against these standards.