Testing Skills With Subagents
Testing Skills With Subagents
Overview
Testing skills is just TDD applied to process documentation.
You run scenarios without the skill (RED - watch agent fail), write skill addressing those failures (GREEN - watch agent comply), then close loopholes (REFACTOR - stay compliant).
Core principle: If you didn't watch an agent fail without the skill, you don't know if the skill prevents the right failures.
See skills/testing/test-driven-development for the fundamental cycle. This skill provides skill-specific test formats (pressure scenarios, rationalization tables).
Complete worked example: See examples/CLAUDE_MD_TESTING.md for a full test campaign testing CLAUDE.md documentation variants.
When to Use
Test skills that:
- Enforce discipline (TDD, testing requirements)
- Have compliance costs (time, effort, rework)
More from obra/superpowers-skills
getting started with skills
Skills wiki intro - mandatory workflows, search tool, brainstorming triggers
295test-driven development (tdd)
Write the test first, watch it fail, write minimal code to pass
11brainstorming ideas into designs
Interactive idea refinement using Socratic method to develop fully-formed designs
11writing plans
Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context
9systematic debugging
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
9code review reception
Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation
8