subagent-testing

# Subagent Testing - TDD for Skills Test skills with fresh subagent instances to prevent priming bias and validate effectiveness. ## When NOT To Use - Writing the skill under test (use `abstract:skill-authoring`) - A static quality audit with no execution (use `abstract:skills-eval`) ## Overview **Fresh instances prevent priming:** Each test uses a new Claude conversation to verify the skill's impact is measured, not conversation history effects. ## Why Fresh Instances Matter ### The Priming Problem Running tests in the same conversation creates bias: - Prior context influences responses - Skill effects get mixed with conversation history - Can't isolate skill's true impact ### Fresh Instance Benefits - **Isolation**: Each test starts clean - **Reproducibility**: Consistent baseline state - **Measurement**: Clear before/after comparison - **Validation**: Proves skill effectiveness, not priming ## Testing Methodology Three-phase TDD-style approach: ### Phase 1: Baseline Testing (RED) Test without skill to establish baseline behavior. ### Phase 2: With-Skill Testing (GREEN) Test with skill loaded to measure improvements. ### Phase 3: Rationalization Testing (REFACTOR) Test skill's anti-rationalization guardrails. ## Quick Start ```bash # 1. Create baseline tests (without skill) # Use 5 diverse scenarios # Document full responses # 2. Create with-skill tests (fresh instances) # Load skill explicitly # Use identical prompts # Compare to baseline # 3. Create ratio...