Before a usability study, so you test the interface, not the instructions.
Design [N] tasks for a usability test of [feature]. Each task should be written as a goal (not step-by-step instructions), with a success criterion and a stopping rule.
Anything in square brackets is meant to be replaced. The builder turns those into fields you can type into.
Tired of re-pasting the same context into every new chat? That is what the Unimatrix MCP server is for.