testing-skills-with-subagents

To validate process documentation using test-driven development, you apply a RED, GREEN, and REFACTOR cycle to skills. You document baseline failures, create a GREEN skill to address them, and perform REFACTOR validations to confirm improvements.

Pressure testing for skills evaluates whether documentation remains robust under real-world constraints. You need it to ensure quality assurance before sharing or upstreaming skills, specifically testing scenarios involving time constraints, sunk cost, exhaustion, and authority.

To start the RED GREEN REFACTOR cycle for skills validation, define 3-5 baseline debugging scenarios and perform RED without any skill. Next, write a GREEN skill addressing observed failures, then run REFACTOR tests to validate improvements and stability.

Yes, you can use subagents to test skills under time constraints and exhaustion. The skill applies pressure-tested scenarios to evaluate whether process documentation remains robust and effective when facing these specific real-world pressures.

A limitation of pressure testing process documentation is that it requires defining 3-5 baseline debugging scenarios upfront to perform RED. Without these observed baseline failures, you cannot accurately create a GREEN skill or perform REFACTOR validations.

Testing skills with subagents works for quality assurance by applying test-driven development to process documentation. It ensures skills are robust and validated through REFACTOR cycles and pressure-tested scenarios before sharing or upstreaming.