get_status
Retrieves a project's complete status in one call: progress overview, milestone goals, task counts by status, open tasks with blockers, and recently completed work for a cold start.
Instructions
Use it first when you start on a project, and when the user asks where it stands (progress, what's left, what's in progress).
The resume: everything an agent needs to pick a project up cold, in one call. The
latest year's overview (goal / now / target / checklist); per period its milestone goal
and status (a period without a milestone has no goal and reports active while open, done
once closed), task counts by status, whether it is closed, and `open_tasks` — every
todo / blocked / in_progress task with its title, tags, branch, one-line content and
`waiting_on`; and `recent_done` — the ten most recently finished tasks across every period, newest
first, each with its content, its `check` and when it completed. Closed periods are
included.
`recent_done` is what the project already has, in the words of whoever built it, and
`check` is what they said proves it. Both are claims: confirm against the code before
building on one. Older finished work and cancelled tasks are list_tasks; the plan as
written is get_roadmap.
Call it once at the start of a session; there is nothing to poll for afterwards.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes |