gsd-new-milestone

name	gsd-new-milestone
description	Start a new milestone cycle update PROJECT.md and route to requirements
argument-hint	[milestone name, e.g., 'v1.1 Notifications']
allowed-tools	Read, Write, Bash, Task, AskUserQuestion

Start a new milestone: questioning → research (optional) → requirements → roadmap.

Brownfield equivalent of new-project. Project exists, PROJECT.md has history. Gathers "what's next", updates PROJECT.md, then runs requirements → roadmap cycle.

Creates/Updates:

• .planning/PROJECT.md — updated with new milestone goals
• .planning/research/ — domain research (optional, NEW features only)
• .planning/REQUIREMENTS.md — scoped requirements for this milestone
• .planning/ROADMAP.md — phase structure (continues numbering)
• .planning/STATE.md — reset for new milestone

After: {{COMMAND_PREFIX}}plan-phase [N] to start execution.

<execution_context> @{{PLATFORM_ROOT}}/get-shit-done/workflows/new-milestone.md @{{PLATFORM_ROOT}}/get-shit-done/references/questioning.md @{{PLATFORM_ROOT}}/get-shit-done/references/ui-brand.md @{{PLATFORM_ROOT}}/get-shit-done/templates/project.md @{{PLATFORM_ROOT}}/get-shit-done/templates/requirements.md </execution_context>

Milestone name: $ARGUMENTS (optional - will prompt if not provided)

Project and milestone context files are resolved inside the workflow (init new-milestone) and delegated via <files_to_read> blocks where subagents are used.

Execute the new-milestone workflow from @{{PLATFORM_ROOT}}/get-shit-done/workflows/new-milestone.md end-to-end. Preserve all workflow gates (validation, questioning, research, requirements, roadmap approval, commits).