milestone_create write

Add a milestone to a project: one chunk of work in the project's ordered sequence. Milestones are an ordered sequence, not dated buckets; a milestone belongs to exactly one project, groups issues without owning them, and may carry a target date. Read roadmap://conventions before creating one, for the team's rules about what a milestone is here. A milestone with no issues is no_issues, which is not complete, and it holds its project back from being delivered, deliberately: an empty milestone is work nobody has written down.

Arguments

Name	Type	Description
`name` required	string	the milestone name, such as Issues endpoints
`position`	null \| integer	where to insert it in the project's sequence, counting from 1; appended to the end when omitted. Out-of-range values are clamped to the ends
`project` required	string	a project key like ENG, or a ULID
`target_date`	string	a calendar date as YYYY-MM-DD, such as 2026-09-01. No time and no timezone

Input schema

Exactly what tools/list serves.

input schema
{
  "additionalproperties": false,
  "properties": {
    "name": {
      "description": "the milestone name, such as Issues endpoints",
      "type": "string"
    },
    "position": {
      "description": "where to insert it in the project's sequence, counting from 1; appended to the end when omitted. Out-of-range values are clamped to the ends",
      "type": [
        "null",
        "integer"
      ]
    },
    "project": {
      "description": "a project key like ENG, or a ULID",
      "type": "string"
    },
    "target_date": {
      "description": "a calendar date as YYYY-MM-DD, such as 2026-09-01. No time and no timezone",
      "type": "string"
    }
  },
  "required": [
    "project",
    "name"
  ],
  "type": "object"
}