Automation handoff example.

Automation work should not end with "the script exists." A useful handoff proves the workflow can run, explains what triggers it, and says how a normal person would notice a failure.

Weak version.

Automate the daily report and send me a notification.

Stronger handoff.

Goal:
Create an automation that [does task] every [schedule or trigger] and sends [plain-English result] to [destination].

Do not touch:
Production data, customer messages, billing tools, or notification channels unless they are explicitly part of the test.

Done means:
The automation has run once against the real target or a clearly named test target, and the result is visible where the user expects it.

Proof required:
Show the last run time, the trigger or schedule, the exact output received, and the failure path. If only a dry run happened, say that clearly.

Proof to ask for.

• The real run result, not just the code or schedule.
• The next scheduled run time or trigger condition.
• The exact message, file, row, or notification created.
• Where errors will appear if the automation breaks.
• Whether the run touched live data or a test target.

Use the generator to rewrite this for your own automation task.