write_milestone
Create or update a project milestone with a one-line goal, ordered acceptance checks, and position; rename, reorder, or delete it, including synced Linear/GitHub milestones.
Instructions
Write one of the project's milestones, or change it when one with this name exists
(names are unique). Each milestone ships something a person can check: goal says what in
one line, checks are its acceptance checks, [{"check": "",
"expect": "", "for": "person"?}]. A check is the crew's (the default):
the crew runs it and records it when the milestone's last ticket merges. Mark for: "person"
only a step a person must do themselves (look at a screen, try a flow in the console); those
reach the person to accept.
position orders them (a new one goes last). To rename one, pass its current name or id as
id and the new name. Give tickets a milestone with write_ticket(milestone=). When
the project's tickets live in Linear or GitHub (link_tickets), a new milestone is created
there, one per call, and a repeat of the same name finds it again; goal goes to Linear or
GitHub as its description and checks stay here. Rename, reorder and delete a milestone in
Linear or GitHub (position is ignored there).
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"name": "<name>"
},
"name": "write_milestone"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | ||
| goal | No | ||
| name | Yes | ||
| checks | No | ||
| project | No | ||
| position | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |