msd-core/commands/msd/new-milestone.md at b7e36d5d386cb392fda09b697956dad24537d3d4

Files

Jakub Zych a9a7a328e6 refactor: hard-fork GSD -> MSD (Make Software Done)

Mechanical rename produced by scripts/msd-rename.cjs: gsd/Gsd/GSD -> msd/Msd/MSD
across contents and paths, upstream package/repo coordinates -> @golem15/msd-core
and golem15com/msd-core. Deep links into upstream history, sibling upstream
packages, the GSD-2 import feature, CHANGELOG.md and .changeset/ are kept as-is.

Hand edits on top: MSD block-letter banner and logos, LICENSE copyright line,
package/plugin identity, regenerated lockfile, install-tree fixtures, derived
registries and benchmark baseline; migration checksum baseline re-locked
(MSD keeps its own install state, so no install had applied the old sums);
sort-order and regex-escaped expectations in tests adjusted.

2026-10-06 01:47:40 +02:00

1.7 KiB

Raw Blame History

name, description, argument-hint, allowed-tools, requires

name

description

argument-hint

allowed-tools

requires

msd: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

Grep

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: /msd:plan-phase [N] to start execution.

<execution_context> @~~/.claude/msd-core/workflows/new-milestone.md @~~/.claude/msd-core/references/questioning.md @~~/.claude/msd-core/references/ui-brand.md @~~/.claude/msd-core/templates/project.md @~/.claude/msd-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).

1.7 KiB Raw Blame History

1.7 KiB

Raw Blame History