writing-skills

Apply TDD to process documentation by establishing a failing baseline scenario, implementing the skill minimally to pass that test, and refactoring to close loopholes before deployment. This enforces a RED-GREEN-REFACTOR cycle for bulletproof agent documentation.

A RED-GREEN-REFACTOR workflow for skill documentation means writing a pressure scenario that fails without the skill, implementing the skill minimally to make it pass, and refactoring the documentation to eliminate rationalizations and close loopholes before deployment.

Verify process documentation by documenting testing with subagents. You write a pressure scenario to baseline behavior without the skill, implement the skill, and re-test with subagents until all baselines pass before deploying to Claude-like agent workflows.

Structure a SKILL.md file by including frontmatter with the name and description, followed by a body with clear guidance. Maintain one SKILL.md per skill and use progressive disclosure to ensure agents receive validated, structured instructions.

Yes, skill-writing uses subagent testing to verify frontmatter validation and overall effectiveness. Testing with subagents ensures the frontmatter contains the required name and description, and that the skill behaves correctly before deployment.

Process documentation drifts when rationalizations and test results are not explicitly recorded during iteration. Using an evidence-based TDD approach reduces drift by documenting test outcomes and closing loopholes before the skill is deployed.