Milestone & Deadline Tracker with Slip Alerts
Build an internal tool that watches your milestone target dates and the tasks feeding them, flags which milestones are at risk or already slipping, and alerts the owner before the date arrives - with a PM approval gate before anything is communicated.
A private, login-protected tracker that imports your milestones and tasks, computes slip risk, shows an at-risk list, and only sends alerts (and writes a revised date) after the PM reviews and approves.
Before you start
- A free Supabase account
- A free Resend account
- A milestone list with target dates (CSV or Google Sheet)
- A task list with statuses and due dates (CSV or Google Sheet)
The problem this kills
Milestones rarely slip overnight. They slip quietly: a feeder task stalls, a due date passes, and nobody connects the dots until the milestone date is already on top of you. By then the conversation is "we missed it" instead of "we're at risk - here's the plan."
Most teams track this in a spreadsheet that can't tell the difference between at risk and already slipped, can't see which incomplete tasks are dragging a milestone down, and certainly can't tap the owner on the shoulder a week early. So slips get discovered in status meetings, not before them.
This tool watches the dates and the tasks for you, does the math every day, and surfaces exactly the milestones that need attention - while there's still time to do something about it.
What you'll build
A small, private web app - just for your team - that:
- Imports your milestone list (name, owner, target date) and your task list (which milestone it feeds, status, due date) from CSV or a Google Sheet.
- Computes a slip-risk status for every milestone: on track, at risk, or slipped - based on remaining days and how many feeder tasks are still incomplete or overdue.
- Shows the project manager a clean at-risk list - what's wrong with each milestone and why.
- Lets the PM review and approve an alert (and optionally a revised target date) before anything goes out.
- Sends the alert by email to the owner, logs what happened, and exports a CSV of statuses for your system of record.
- Doesn't nag: it won't re-alert the same unchanged milestone day after day.
What's inside the Implementation Plan
- A copy-paste runbook you hand to an AI coding agent (Claude Code) - it does the building, you steer.
- It opens by interviewing you about your business - your milestones, your task fields, your naming and ID conventions, your typical and peak volumes, and your real slip rules - so the tracker is tailored to how you actually run projects, not a generic template. It reads a short spec back to you and waits for your thumbs-up before building.
- Step-by-step build instructions, each ending in a ready-to-paste prompt.
- The full slip-risk logic, the PM approval flow, the email alerts, and the CSV import/export.
- A "No API yet?" fallback so you can ship today using spreadsheets - no integration with your existing PM tool required.
The governance it includes (this is the point)
This isn't a toy. The plan bakes in the controls that make an internal tool safe to actually use:
- Login so only your team can open it.
- Row-level security so each organization only ever sees its own milestones and tasks.
- A complete audit trail - who approved which alert, what date was changed, and when.
- A human-in-the-loop approval gate - the tool drafts the at-risk list and the alert; a person reviews, and only then does it send the email or write a revised date. Nothing leaves the building automatically.
- Duplicate guards - milestones dedupe on their ID, and the tool won't re-alert the same unchanged milestone over and over.
Who it's for
Project managers, program managers, and delivery leads who own a set of milestones and are tired of finding out about slips too late. If you can keep a milestone list and a task list in a spreadsheet, you can run this.
You've got this - paste the first prompt and let the agent interview you.