a9a7a328e6
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.
21 lines
998 B
Markdown
21 lines
998 B
Markdown
---
|
|
id: 8
|
|
title: Milestone Management
|
|
group: Core Features
|
|
---
|
|
|
|
**Commands:** `/msd-audit-milestone`, `/msd-complete-milestone`, `/msd-new-milestone [name]`
|
|
|
|
**Purpose:** Verify milestone completion, archive, tag release, and start the next development cycle.
|
|
|
|
**Requirements:**
|
|
- REQ-MILE-01: Audit MUST verify all milestone requirements are met
|
|
- REQ-MILE-02: Audit MUST detect stubs, placeholder implementations, and untested code
|
|
- REQ-MILE-03: Audit MUST check Nyquist validation compliance across phases
|
|
- REQ-MILE-04: Complete MUST archive milestone data to MILESTONES.md
|
|
- REQ-MILE-05: Complete MUST offer git tag creation for the release
|
|
- REQ-MILE-06: Complete MUST offer squash merge or merge with history for branching strategies
|
|
- REQ-MILE-07: Complete MUST clean up UI review screenshots
|
|
- REQ-MILE-08: New milestone MUST follow same flow as new-project (questions → research → requirements → roadmap)
|
|
- REQ-MILE-09: New milestone MUST NOT reset existing workflow configuration
|