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.
27 lines
1.1 KiB
Markdown
27 lines
1.1 KiB
Markdown
---
|
|
id: 14
|
|
title: Auto-Advance (Next)
|
|
group: Planning Features
|
|
---
|
|
|
|
**Command:** `/msd-progress --next`
|
|
|
|
**Purpose:** Automatically detect current project state and advance to the next logical workflow step, eliminating the need to remember which phase/step you're on.
|
|
|
|
**Requirements:**
|
|
- REQ-NEXT-01: System MUST read STATE.md, ROADMAP.md, and phase directories to determine current position
|
|
- REQ-NEXT-02: System MUST detect whether discuss, plan, execute, or verify is needed
|
|
- REQ-NEXT-03: System MUST invoke the correct command automatically
|
|
- REQ-NEXT-04: System MUST suggest `/msd-new-project` if no project exists
|
|
- REQ-NEXT-05: System MUST suggest `/msd-complete-milestone` when all phases are complete
|
|
|
|
**State Detection Logic:**
|
|
| State | Action |
|
|
|-------|--------|
|
|
| No `.planning/` directory | Suggest `/msd-new-project` |
|
|
| Phase has no CONTEXT.md | Run `/msd-discuss-phase` |
|
|
| Phase has no PLAN.md files | Run `/msd-plan-phase` |
|
|
| Phase has plans but no SUMMARY.md | Run `/msd-execute-phase` |
|
|
| Phase executed but no VERIFICATION.md | Run `/msd-verify-work` |
|
|
| All phases complete | Suggest `/msd-complete-milestone` |
|