Files
msd-core/commands/gsd/new-milestone.md
Tom Boucher 71180983a0 fix(#3423): standardize on <required_reading>, retire the files_to_read emit tag (#3432)
* fix(#3423): standardize on required_reading, retire files_to_read emit tag

* test(#3423): flip tag assertions, extend consistency guard to spawner surfaces

* fix(#3423): sweep capabilities fragments, regen registry+skills, anchor executor test

* chore(#3423): acknowledge tag-rename emitted ripples and workflow growth

* chore(#3423): broaden emitted-ripple acknowledgment to all embedders

* chore(#3423): settle emitted-drift acks post-rebase (merge 3004/1689-owned keys)

* chore(#3423): drop stale ripple acks, ack execute-phase growth

* chore(#3423): restore pristine 3004 fragment, keep only consumed appends

* chore(#3423): backfill changeset pr number

* chore(#3423): settle emitted-drift acks post-merge (move code-review-fix ripple into 3190, tag-rename ripples into 3191/3297)

* chore(#3423): re-arm 3324 ack for execute-phase.md tag-rename ripple

* fix(#3423): trim 8 bytes from execute-phase model note to hold ADR-857 margin, re-arm 3370 ack for net +4 growth

---------

Co-authored-by: sim <sim@local>
2026-08-14 16:03:48 -04:00

1.6 KiB

name, description, argument-hint, allowed-tools, requires
name description argument-hint allowed-tools requires
gsd:new-milestone Start a new milestone cycle — update PROJECT.md and route to requirements [milestone name, e.g., 'v1.1 Notifications'] [--ws <name>] [--reset-phase-numbers]
Read
Write
Bash
Agent
AskUserQuestion
new-project
phase
plan-phase
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: /gsd:plan-phase [N] to start execution.

<execution_context> @/.claude/gsd-core/workflows/new-milestone.md @/.claude/gsd-core/references/questioning.md @/.claude/gsd-core/references/ui-brand.md @/.claude/gsd-core/templates/project.md @~/.claude/gsd-core/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 <required_reading> blocks where subagents are used.

Execute end-to-end. Preserve all workflow gates (validation, questioning, research, requirements, roadmap approval, commits).