Best for
- Reporting progress to stakeholders without hand-waving
- Catching 'done' claims that do not meet the written criteria
- Keeping long projects legible
What you give it
- Milestone news, or a request to check one against its criteria
What you get back
- The milestone file updated with status and date
- A criteria check: met, not met, and exactly what is missing
- A one-screen progress picture when you ask for it
How it works
- Reads each milestone's written definition of done.
- Verifies claims against the criteria and the project's actual state.
- Updates statuses only when criteria are met, with the date.
- Keeps the achieved history as a record, not a deletion.
- Produces a short progress summary on demand.
Example
You: Is the customer-portal milestone achieved? The team says yes.
Result: Check against its four written criteria: three met, one (password reset flow) not shipped — status stays in progress, with the single missing item named.
Limits — please read
- Criteria must exist — it will ask you to define vague milestones.
- It checks what is checkable; subjective criteria get flagged as such.
- It tracks delivery, not budgets or hours.