From test-plan
Use when deciding what to test for a change. Covers the test pyramid, risk-based prioritization, boundary and equivalence partitioning, the edge cases worth checking, and — just as important — what not to test.
How this skill is triggered — by the user, by Claude, or both
Slash command
/test-plan:test-design-heuristicsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The goal of a test is to catch a regression that matters, cheaply. Optimize for **signal per
The goal of a test is to catch a regression that matters, cheaply. Optimize for signal per test, not for a coverage number.
Push each behavior to the lowest level that can meaningfully exercise it.
Test first where a bug would hurt most and is most likely: money, auth, data loss, irreversible actions, and the code that just changed. Don't spend the same effort on a log-formatting helper as on a payment path.
A test plan that says "this part needs no test, here's why" is more credible than one that tries to test everything.
Provides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.
npx claudepluginhub meaganewaller/rosetta --plugin test-plan