Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tobihagemann/create-test-plan
Analyze what changed and generate a structured test plan at .turbo/test-plans/<slug>.md covering four escalating levels: basic functionality, complex operations, adversarial testing, and cross-cutting scenarios.
Passed 3 of 10 test cases with the skill, and 3 of 10 without it.
and 2 more in the full report
5 fixed3 passed either way11 still failing5 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to plan testing for 'Order History Export'. The target file `.turbo/test-plans/order-history-export.md` already exists in the file system from an earlier change. How should the output path collision be resolved?
| Checked | Without skill | With skill |
|---|---|---|
| Appends a numeric suffix like `-2` to resolve the filename collision. | Missed | Passed |
The instructions your model reads when the skill loads.
Analyze what changed and generate a comprehensive test plan covering four escalating levels of testing depth.
Resolve scope using the first match:
If the resolved scope spans more than one git branch and the user named no single branch, cover each of them instead of only the branch currently checked out. Include scenarios that exercise them together where the branches can be combined in the working tree the plan's executor will have, and state the required branch state in each such scenario's steps.
Always check for project-specific testing skills or MCP tools first. Use the fallbacks below when nothing project-specific is available:
$agent-browser skill if available, otherwise Codex browser automationcomputer-use MCPPick a slug for the test plan from the change under test:
If the work is anchored to an existing plan at .turbo/plans/<slug>.md, reuse that plan's slug verbatim.
The user may pass an explicit slug or output path; honor it.
Resolve a collision at .turbo/test-plans/<slug>.md by how the slug was chosen. A slug generated from the change under test takes -2, -3, and so on until the path is free; do not overwrite. For a slug reused from an anchoring artifact, use request_user_input to offer overwrite or a different slug, since a numeric suffix would break its pairing with that artifact. For a slug or path the user supplied, use request_user_input to offer overwrite, a numeric suffix, or a different slug.
test cases passed, vs 3 / 10 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.