
When someone asks "how should we test this" or "what tests do we need", this skill kicks in to help you think through test architecture instead of just writing individual tests. It pushes you toward the testing pyramid, suggests appropriate test types based on what you're building (APIs get contract tests, data pipelines get idempotency checks, frontend gets accessibility coverage), and helps identify gaps in existing suites. The real value is in forcing the conversation about what actually matters to test versus what's just coverage theater. It won't write your tests for you, but it will give you a structured plan with coverage targets and example cases so you're not just throwing assertions at the wall.
$ npx -y skills add anthropics/knowledge-work-plugins --skill testing-strategy --agent claude-codeInstalls into .claude/skills of the current project.
Design effective testing strategies balancing coverage, speed, and maintenance.
/ E2E \ Few, slow, high confidence
/ Integration \ Some, medium speed
/ Unit Tests \ Many, fast, focused
Focus on: business-critical paths, error handling, edge cases, security boundaries, data integrity.
Skip: trivial getters/setters, framework code, one-off scripts.
Produce a test plan with: what to test, test type for each area, coverage targets, and example test cases. Identify gaps in existing coverage.
Sponsors