writing-skills

Test-driven documentation validates agent skills by writing a failing pressure scenario, capturing rationalizations, authoring a minimal SKILL.md, and re-running it to verify compliance. This enforces process discipline before deployment.

Pressure scenarios are test cases that verify discipline-enforcing skills under combined time, sunk-cost, and authority pressures. They force agents to prove compliance and prevent rationalization when following strict processes.

Convert tribal knowledge into reusable skills by applying red-green-refactor workflows to author minimal SKILL.md files. This transforms informal processes into tested, discoverable skills that agents reliably follow.

Yes, subagent-based tests verify skill compliance by running pressure scenarios against authored SKILL.md files. This validates that agents enforce process discipline and delete untested code when required.

Structure discovery-optimized metadata using specific name and description conventions with progressive disclosure. This ensures skills load only when relevant, maximizing discoverability while minimizing unnecessary context loading.

Rationalization tables document exact failure rationalizations captured during initial pressure scenario testing. They are needed when hardening discipline-enforcing skills to prevent agents from bypassing required processes under pressure.