| name | wdad-test-adversary-review |
| description | Use for a skeptical review of the tests after implementation. Looks for shallow coverage, over-mocking, and ways the implementation could still be wrong while tests pass. |
Skill: Test-adversary review
Purpose
Find gaps between claimed behavior and actual test evidence.
Mode
Read-only/planning mode.
Required inputs
- wave acceptance checks
- changed tests
- relevant implementation files
TESTING.md
Procedure
- Map acceptance checks to concrete evidence.
- Look for happy-path-only tests.
- Look for tautological or over-mocked tests.
- Identify missing regression, integration, or edge-case coverage.
- Treat acceptance checks moved to follow-up, deferral, non-goal, or out-of-scope language without explicit user signoff as not covered.
- Recommend the smallest meaningful additions.
Output
- acceptance coverage summary
- weak or shallow tests
- missing tests
- merge readiness from a testing perspective