create-milestone

Create Milestone

Create a GitHub milestone on the current repository and return its number for downstream use.

Backlog MCP reference: use backlog_list_milestones and backlog_create_milestone for milestone operations.

Arguments

• Empty — guided intake via AskUserQuestion
• quick {title} — use remainder as title, ask only for description

Workflow

Step 1: Collect Fields

Guided mode (no args) — ask in sequence:

Q1: Milestone title?  (e.g. "v1.1 — Milestone Workflow", "2026-Q1 Grooming")
Q2: Description? (one sentence, or skip)

Quick mode (quick {title}) — ask only Q2 (description).

Title is required. Description is optional. Due date is never prompted — only set if the user explicitly provides it in arguments (e.g., quick {title} --due 2026-04-30).

Step 2: Duplicate Check

Call backlog_list_milestones(state="open") and scan the returned list for any entry where title matches the requested title (case-insensitive).

If an open milestone with the same title already exists, report it and ask: "Use existing or create new?" via AskUserQuestion.

If user chooses existing: print its number and stop.

Step 2.5: Wave Ordering (when items are known)

When a milestone is being created alongside a set of known backlog items (not just a blank milestone), plan the execution order before creating the milestone. Use mcp__sequential_thinking__sequentialthinking to structure the analysis.

flowchart TD
    Start(["Items known for this milestone?"]) --> Q{"Items provided<br>or identified?"}
    Q -->|"No — blank milestone"| Skip["Skip to Step 3"]
    Q -->|"Yes — items listed"| Dep["Dependency Mapping"]
    Dep --> Classify["Classify into waves"]
    Classify --> Restart["Identify restart points"]
    Restart --> Record["Record wave plan in description"]
    Record --> Step3["Proceed to Step 3"]

Dependency Mapping — for each item, answer:

1. What does this item need to exist before it can be built?
2. What does this item enable once it exists?