create-milestonelisted

# Create Milestone This skill bridges the gap between tranche-level shaping and feature-level delivery. Use it when `/shape` clarified work that requires multiple independent PRDs — the result is too large or too decomposable for one PRD. The goal is to create just enough GitHub-native structure to sequence feature bets, pick a tracer bullet, and let the selected feature re-enter the normal pipeline with a researchable brief. > **One question per turn.** When confirming the branch, reviewing bets, or asking the user anything, ask one question at a time and wait for the answer before asking the next. Never batch questions into a list. > > **Prefer single-select.** Use single-select multiple choice when the user is choosing one direction, one priority, or one next step. > > **Use multi-select rarely.** Reserve it for compatible sets — goals, constraints, non-goals, success criteria — that can all coexist. If prioritization matters, follow up asking which selected item is primary. > > **Use the platform's question tool when available.** In Claude Code, use `AskUserQuestion`; in Codex, `request_user_input`; in Gemini, `ask_user`. Otherwise, present numbered options in chat and wait for the user's reply before proceeding. ## Invocation Position This is a primary planning branch that follows `/shape` only when the shaped work is too large for a single PRD. Use `/create-milestone` when: - `/shape` already produced a closing summary with choices, assumptions, impositions, and st