Defect follow-up tracker
Chases open defects and snag items by owner and due date, and drafts polite follow-ups for the overdue ones.
RunsEvery Monday at 9 AM
Cron
0 9 * * 1Works withAny agent, any stack
Open the defect register at <REGISTER LOCATION>. List every defect that is not closed, with ID, location, description, responsible contractor, date raised and due date. Group by contractor. Mark items overdue, due this week, or missing a due date or owner. For each contractor with overdue items, draft a short, polite follow-up email that lists their defect IDs, locations and original due dates and asks for a revised completion date. Show me the drafts; do not send them and do not edit the register.Replace anything in <ANGLE BRACKETS> with your own details. Review outputs before letting an agent send, buy or delete anything.
How to run this
Works with any agent
⏱TriggerEvery Monday at 9 AM
✦Any agentRuns the prompt
✓OutputResult for you to review
Steps
- Copy the prompt and fill in the parts in angle brackets.
- Paste it into whatever agent you already use: a chat assistant, a coding agent, an automation tool, or a script that calls any model API.
- Schedule it (every monday at 9 am). Use the agent's own scheduler if it has one, otherwise run it from cron with the expression below.
- Give it only the access it needs (inbox, calendar, repo, sheet) and keep sends, purchases and deletes behind your approval.
- Review the first two runs, tweak the prompt, then let it run.
See how this fits a full operations stack in the interactive deck.