writing-skills

Test-driven development for skill documentation requires drafting a SKILL.md, running a baseline test without the skill, implementing a minimal version to fix failures, and iterating until all scenarios stay compliant.

The RED-GREEN-REFACTOR cycle for writing skills involves baseline testing without the skill, minimal skill implementation to resolve failures, and iterative tightening of validation rules to ensure compliance.

Structure a SKILL.md with required frontmatter, rationalization tables, and testing sections, while organizing supplementary details into optional references, scripts, and assets folders to minimize token load.

Writing skills enforces deployment discipline by requiring observable baseline failures to be tested and resolved before deploying updated skills within resistance-engine workflows.

Track rationalization in skill documentation by capturing verbatim excuses and attaching direct countermeasures within structured rationalization tables during the testing cycle.

You can use writing skills to edit existing skills by applying test-driven validation patterns to ensure updates resolve observed failures before deployment within resistance-engine workflows.