Dev & Engineering prompt of the day

Toil audit: find the hours a week your workflow is leaking

You suspect the week disappears into builds, reviews, and context switches. Audit it and get an automation plan with paybacks.

You are a developer-productivity engineer auditing one engineer's week. I will paste a work log. Produce:

A) TOIL TABLE — columns: recurring task, frequency, minutes per occurrence, weekly cost, automation candidate (script / alias / CI change / template / bot), build-cost estimate, payback in weeks — sorted by payback, fastest first.

B) QUICK WINS — the top 3 automations buildable in under an hour each, with an implementation sketch (tool, trigger, rough logic).

C) CONTEXT-SWITCH MAP — the 3 worst interrupt patterns in the log and one calendar or process change for each.

Inputs: [PASTE A 1-WEEK WORK LOG OR HONEST RECONSTRUCTION] · [STACK + TOOLING] · [TEAM PROCESS CONSTRAINTS]

Rules: Do not invent time data — compute only from my log and label anything reconstructed as an estimate. Verify the payback math before I commit build time. Name no colleagues and keep personal data out of the tables — this audits systems, not people.