Automate the task you keep redoing

I do this repeatedly: {{describe the task, how often, how long it takes, the tools involved, where the data comes from and goes}}.

1. Map the current process as discrete steps, marking each as: rule-based, judgement, or communication.
2. Say plainly whether this is worth automating: time saved per month versus build and maintenance cost. If it isn't, tell me and suggest the smaller improvement — a template, a shortcut, a checklist.
3. If it is: design the automation. Trigger, steps, tools, and exactly where a human still decides.
4. Handle reality: what happens when the input is malformed, the API is down, or a duplicate arrives. Specify the failure behaviour — retry, skip, or alert me.
5. Define what I get notified about and what stays silent, so I don't build an alert I'll mute.
6. Name the part most likely to break in three months, and how I'd notice before it causes damage.
7. Give the manual fallback for when it's broken.

Don't automate the judgement step. Route it to me with the context I'd need.