Best for
- Projects that outgrew a to-do list
- Founders who need 'where are we?' answered in one read
- Keeping AI-built work mapped to business milestones
What you give it
- Your requirements or goals, and the order you care about
- News from reality: something finished, slipped or changed
What you get back
- Milestones with plain-language 'done' definitions
- A work breakdown where every task maps to a milestone
- An honest status view — done, in progress, blocked and why
How it works
- Reads the requirements and the current plan files, if any exist.
- Groups work into milestones a stakeholder would recognise as progress.
- Breaks milestones into tasks small enough to finish inside one working session.
- Records status changes with dates, so the plan is also the history.
- Flags orphan work — tasks that map to no milestone — instead of hiding it.
Example
You: We have the requirements for the booking change. Plan it, and fold in that payments work is half-finished.
Result: Two milestones with done-criteria, nine tasks mapped under them, the half-finished payment task split into its done and remaining halves, and the next three actions named.
Limits — please read
- It plans and tracks; it does not execute the tasks.
- Estimates are structural (order and dependency), not promises of hours.
- It is as current as the news you give it — silent changes make silent drift.