Kit
Every project’s real state — and what’s at risk before the deadline is.
Every project's real state — not the state from the last status meeting. Tell Osprey about each project once — what it is, who has it, when it's meant to land — and the next few milestones between here and there; from then on, mention a date, a slip or a milestone landed in any conversation and the board moves. Each project on one table with its owner, its status and its next milestone; every milestone drawn as a run on a timeline, ending on the day it is due; the milestones by status and by owner; and, every Monday, what is at risk this week — due within seven days and not progressing, or flagged — written up before the deadline does it for you. Ask for a status note before a meeting and it is written from the record, in plain words, into your vault. The work under each milestone is a list you tick on the board, what waits on what is kept and drawn, and the risks and issues stay on record until they are dealt with. The budget and what has been spent are kept as you give them, and the Monday sweep counts what each person has open, as a count and never a verdict. A kick-off brief at the start, an update drafted for you to send, and a look back at the end are written from the record, and a check-in on a project's milestones is a button on the board. Osprey never re-plans a project or hands out work: after a slip it records the dates you give. Nothing here reads a project tool unless you enable one by name, and nothing ever writes to one.
1 agent, 1 routine, 1 dashboard, 4 datasets, 5 skills. Installing ends with Meet Osprey — a short conversation sets it up, and everything can be retimed or paused after.
| Northwind rebrand | active · Alice · next: brand guidelines signed off | in 9 days |
| Customer portal launch | at risk · Bob · next: beta build to testers | in 5 days |
| Billing migration | active · Dana · next: invoices cut over | in 23 days |
each milestone, from the day it was set to the day it is due
one at risk, and it is the one due first
Beta build to testers — Customer portal launch
due in 5 days · at risk · BobCustomer portal launch
project marked at risk · target in 16 daysThe crew
Osprey
Sees every project from height, and speaks only when one is about to slip.
Patient, unhurried, sees the whole plot from height; moves only when something is about to slip.
What else it installs
One row per project — who has it, where it stands, when it lands, and what comes next.
Every milestone, one row each, against its project — when it started, when it is due, and how it stands.
The work under each milestone, one row per task — whose it is, when it is due, and whether it is done.
What might go wrong and what already has, against each project — whose it is, what is being done, and whether it is closed.
"The beta slipped to the 24th" — and the board moves.
"Where are we on the rebrand?" — a plain status note, written from the record, into your vault.
"For the beta we still need the login fix and the tester guide" — the work under a milestone, on a list you tick.
"The payment provider might not sign off in time" — on record against the project until it is dealt with.
A kick-off brief at the start and a look back at the end, both written from what you said and what the record holds.
Every project's real state on one table, what is at risk this week, the work and the worries under it, and every milestone on a timeline.
Mondays — reads what has been said, moves what the evidence moves, and writes up what is at risk this week.
Runs mondays · 7am
The mechanics of this kit, plainly — what runs and when, where the data lands, and what you look at.
Data/Projects in your vault — yours to open, search, and edit like any other file.Data/Milestones in your vault — yours to open, search, and edit like any other file.Data/Project Tasks in your vault — yours to open, search, and edit like any other file.Data/Project Risks in your vault — yours to open, search, and edit like any other file.The wiring, in one breath: Project capture writes to Projects · Project capture writes to Milestones · Projects shown by Projects · Milestones shown by Projects · Projects kept fresh by Project sweep · Project sweep run by Osprey · Osprey holds Project capture · Osprey holds Status note · Osprey holds Milestone tasks · Milestone tasks writes to Tasks · Tasks shown by Projects · Osprey holds Risks and issues · Risks and issues writes to Risks and issues · Risks and issues shown by Projects · Osprey holds Kick-off and look back.
A kit earns its place when it changes what you look at and what you say, not when it is installed. This is the rhythm that makes it pay.
Nothing here is fixed. The pieces are ordinary agents, routines, datasets and dashboards, so anything you know about shaping those applies. Retire whatever earns nothing.
Say any of these in chat, or edit them on the kit’s page in the app.
Installing starts a short setup conversation — not a form. Answer roughly, correct later.
Watch the first pass, then tell it what you would have done differently — that correction teaches it more than any setup could.
Learning, preferences and run costs work the same in every kit — so they are covered once, in the Kits guide.
Install it, run it once against something that already happened, and see whether what comes back sounds like you.
Try it freeEverything it installs can be retimed, paused, or removed.
Last reviewed