Start a new milestone cycle — update PROJECT.md and route to requirements
<augment_skill_adapter>
gsd-new-milestone or describes a task matching this skill.{{GSD_ARGS}}.{{GSD_ARGS}} as empty.When the workflow needs user input, prompt the user conversationally:
Use these Augment tools when executing GSD workflows:
launch-process for running commands (terminal operations)str-replace-editor for editing existing filesview for reading files and listing directoriessave-file for creating new filesgrep for searching code (or use MCP servers for advanced search)web-search, web-fetch for web queriesadd_tasks, view_tasklist, update_tasks for task managementWhen the workflow needs to spawn a subagent:
.augment/agents/ directory
</augment_skill_adapter>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 milestoneAfter: /gsd-plan-phase [N] to start execution.
</objective>
<execution_context> @./.augment/get-shit-done/workflows/new-milestone.md @./.augment/get-shit-done/references/questioning.md @./.augment/get-shit-done/references/ui-brand.md @./.augment/get-shit-done/templates/project.md @./.augment/get-shit-done/templates/requirements.md </execution_context>
Project and milestone context files are resolved inside the workflow (init new-milestone) and delegated via <files_to_read> blocks where subagents are used.
</context>