Files
msd-core/commands/msd/phase.md
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

2.1 KiB

name, description, argument-hint, allowed-tools
name description argument-hint allowed-tools
msd:phase Multi-phase management — add, insert, remove, or edit phases in ROADMAP.md (roadmap phase CRUD) [--insert | --remove | --edit] <phase-name-or-number>
Read
Write
Bash
Glob
Grep
Manage phases in ROADMAP.md with a single consolidated command.

Mode routing:

  • default (no flag): Add a new integer phase to the end of the current milestone → add-phase workflow
  • --insert: Insert urgent work as a decimal phase (e.g., 72.1) between existing phases → insert-phase workflow
  • --remove: Remove a future phase and renumber subsequent phases → remove-phase workflow
  • --edit: Edit any field of an existing phase in place → edit-phase workflow
Flag Action Workflow
(none) Add new integer phase at end of milestone add-phase
--insert Insert decimal phase (e.g., 72.1) after specified phase insert-phase
--remove Remove future phase, renumber subsequent remove-phase
--edit Edit fields of existing phase in place edit-phase

<execution_context> @/.claude/msd-core/workflows/add-phase.md @/.claude/msd-core/workflows/insert-phase.md @/.claude/msd-core/workflows/remove-phase.md @/.claude/msd-core/workflows/edit-phase.md </execution_context>

Arguments: $ARGUMENTS

Parse the first token of $ARGUMENTS:

  • If it is --insert: strip the flag, pass remainder (format: ) to insert-phase workflow
  • If it is --remove: strip the flag, pass remainder (phase number) to remove-phase workflow
  • If it is --edit: strip the flag, pass remainder (phase-number [--force]) to edit-phase workflow
  • Otherwise: pass all of $ARGUMENTS (phase description) to add-phase workflow

Roadmap and state are resolved in-workflow via init phase-op and targeted reads.

1. Parse the leading flag (if any) from $ARGUMENTS. 2. Load and execute the appropriate workflow end-to-end based on the routing table above. 3. Preserve all validation gates from the target workflow.