writing-skills

Test-driven development for skill documentation is enforced by defining pressure-scenario tests that demonstrate baseline violations, then authoring the minimum documentation needed to achieve compliance. A RED-GREEN-REFACTOR loop validates that agents follow instructions.

Agents rationalize skipping required steps in process documentation by treating instructions as non-binding guidance under pressure. This behavior is countered by identifying specific excuses and adding explicit negations, counter-rules, and red flags to close loopholes.

A pressure scenario in skill authoring is a test case designed to demonstrate baseline violations where agents are likely to rationalize skipping steps or treating instructions as optional. It validates that documentation closes loopholes via re-testing.

Optimizing skill discovery using YAML frontmatter requires enforcing specific conventions for the `name` and `description` fields, alongside strong third-person "Use when..." trigger descriptions and keyword coverage to improve search visibility.

Yes, you can use a RED-GREEN-REFACTOR loop for prompt compliance testing to verify documentation-based skills. It identifies baseline violations, authors minimum documentation for compliance, and closes loopholes through rationalization bulletproofing and re-testing.

Preventing agents from treating documentation as optional guidance requires defining pressure scenarios that demonstrate baseline violations, adding explicit loophole-closing counters, and validating compliance through re-testing within a RED-GREEN-REFACTOR loop.