Turn Vague Requests Into Reliable Agent Work

A first run without an example shows whether direct instructions are enough. If the email keeps hiding the risk behind cheerful filler, two past updates that state different problems calmly can clarify the missing pattern.

Variety is what makes the pair teach. One delayed approval and one failed test both state the risk, explain its effect, and say what happens next without blame, so the shared pattern is visible without inviting the agent to copy one email.