Testing strategy
Plans tests around real end-to-end flows and writes down how things could fail before any isolated test gets added.
When to use it
- You are about to add tests for a feature.
- You want coverage of real user flows and error paths.
- Unit tests keep being written after the code instead of before it.
A practical example
You ask
“Plan how we should test the new password-reset flow.”
Your agent does
It lists the ways the flow could fail, then proposes end-to-end checks that cover them and produce a rerunnable record.
What gets installed
A single instruction file, SKILL.md, which the agent reads when the skill applies.
- SKILL.md2,332 bytes
Credit and license
Written for this catalog.