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.
This commit is contained in:
Jakub Zych
@@ -2,7 +2,7 @@
|
||||
|
||||
**Goal:** Recover when a phase execution fails, stalls, or produces incomplete work — and resume cleanly without losing progress or repeating work that already succeeded.
|
||||
|
||||
**Prerequisites:** You have run `/gsd-execute-phase N` and the execution stopped before writing `VERIFICATION.md`, or you see unexpected output, missing files, or a stalled spinner.
|
||||
**Prerequisites:** You have run `/msd-execute-phase N` and the execution stopped before writing `VERIFICATION.md`, or you see unexpected output, missing files, or a stalled spinner.
|
||||
|
||||
---
|
||||
|
||||
@@ -12,15 +12,15 @@ Before taking any recovery action, determine what actually happened.
|
||||
|
||||
### If you see "Spawning…" with no output after 1–5 minutes
|
||||
|
||||
This is normal, not a freeze. GSD subagents run in an isolated context window. The liveness note on the spawn line confirms this. Do not interrupt the session.
|
||||
This is normal, not a freeze. MSD subagents run in an isolated context window. The liveness note on the spawn line confirms this. Do not interrupt the session.
|
||||
|
||||
If it has been more than 10 minutes with no result, check the Claude Code sidebar. If the agent task shows as completed but no output appeared, the result may have been lost in a context switch — re-run the same command:
|
||||
|
||||
```bash
|
||||
/gsd-execute-phase 1
|
||||
/msd-execute-phase 1
|
||||
```
|
||||
|
||||
GSD checks for `SUMMARY.md` files before dispatching executors. Plans that already have one are skipped automatically.
|
||||
MSD checks for `SUMMARY.md` files before dispatching executors. Plans that already have one are skipped automatically.
|
||||
|
||||
### If execution stopped mid-wave with an error message
|
||||
|
||||
@@ -34,7 +34,7 @@ Plans that committed their work will have an entry such as `feat(01-02): …`. P
|
||||
|
||||
### If the executor committed code but did not write SUMMARY.md
|
||||
|
||||
GSD detects this at the next run and surfaces a safe-resume gate with three options:
|
||||
MSD detects this at the next run and surfaces a safe-resume gate with three options:
|
||||
|
||||
- **Close out manually** — inspect the commits yourself, write `SUMMARY.md`, then re-run.
|
||||
- **Re-execute from scratch** — revert or supersede the partial commits before dispatching a new executor.
|
||||
@@ -43,11 +43,11 @@ GSD detects this at the next run and surfaces a safe-resume gate with three opti
|
||||
### If you see a "frontmatter opens with `---` but never closes" warning
|
||||
|
||||
```
|
||||
gsd: warning — /path/.planning/STATE.md: frontmatter opens with "---" but never closes; metadata was NOT applied. (#1879)
|
||||
msd: warning — /path/.planning/STATE.md: frontmatter opens with "---" but never closes; metadata was NOT applied. (#1879)
|
||||
```
|
||||
|
||||
The named file was written only partly — typically a crash, a full disk, or a killed process
|
||||
between the opening fence and the closing one. GSD read it as having **no** metadata and carried
|
||||
between the opening fence and the closing one. MSD read it as having **no** metadata and carried
|
||||
on, so any phase, plan, or state value that file was supposed to supply is missing from this run.
|
||||
|
||||
1. Open the named file and check whether its frontmatter block is closed by a `---` line of its
|
||||
@@ -60,7 +60,7 @@ on, so any phase, plan, or state value that file was supposed to supply is missi
|
||||
The warning cannot be turned off, and it never changes what a command returns or its exit code —
|
||||
it only tells you a file could not be used.
|
||||
|
||||
**A file can still be truncated without this warning.** GSD stays silent when the partial block
|
||||
**A file can still be truncated without this warning.** MSD stays silent when the partial block
|
||||
carries fewer than two fields, or when the text after the opening `---` reads as prose rather than
|
||||
frontmatter, because a Markdown document that opens with a horizontal rule is indistinguishable
|
||||
from one of those. If a run behaves as though metadata is missing and you see no warning, inspect
|
||||
@@ -70,12 +70,12 @@ the file anyway.
|
||||
|
||||
## Diagnose the root cause
|
||||
|
||||
### Run `/gsd-debug --diagnose`
|
||||
### Run `/msd-debug --diagnose`
|
||||
|
||||
If execution produced wrong output, stubbed code, or a verification failure, use the diagnosis-only mode to investigate without applying any fixes:
|
||||
|
||||
```bash
|
||||
/gsd-debug --diagnose "Phase 2 executor produced stubs instead of real code"
|
||||
/msd-debug --diagnose "Phase 2 executor produced stubs instead of real code"
|
||||
```
|
||||
|
||||
`--diagnose` stops at root cause without touching your files. It creates a session file at `.planning/debug/<slug>.md` so you can pick up the investigation later if needed.
|
||||
@@ -83,36 +83,36 @@ If execution produced wrong output, stubbed code, or a verification failure, use
|
||||
To start a full debug session that also applies a fix:
|
||||
|
||||
```bash
|
||||
/gsd-debug "Login middleware not handling 401 correctly after phase 3"
|
||||
/msd-debug "Login middleware not handling 401 correctly after phase 3"
|
||||
```
|
||||
|
||||
GSD gathers symptoms, runs a structured investigation using the scientific method, and proposes a fix. If `tdd_mode: true` is set in your config, it requires a failing test before applying any fix.
|
||||
MSD gathers symptoms, runs a structured investigation using the scientific method, and proposes a fix. If `tdd_mode: true` is set in your config, it requires a failing test before applying any fix.
|
||||
|
||||
### Check active debug sessions
|
||||
|
||||
```bash
|
||||
/gsd-debug list
|
||||
/msd-debug list
|
||||
```
|
||||
|
||||
Shows all open sessions with their current hypothesis and next action. To resume a specific session:
|
||||
|
||||
```bash
|
||||
/gsd-debug continue <slug>
|
||||
/msd-debug continue <slug>
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Run a post-mortem with `/gsd-forensics`
|
||||
## Run a post-mortem with `/msd-forensics`
|
||||
|
||||
If the cause is not clear from the error output — for example, plans reference nonexistent files, execution produced unexpected results, or state seems corrupted — run a forensic investigation:
|
||||
|
||||
```bash
|
||||
/gsd-forensics "Phase 3 execution stalled after wave 1"
|
||||
/msd-forensics "Phase 3 execution stalled after wave 1"
|
||||
```
|
||||
|
||||
GSD analyses git history, `.planning/` artifact completeness, STATE.md consistency, uncommitted work, and orphaned worktrees. It writes a structured report to `.planning/forensics/report-<timestamp>.md` and surfaces recommended remediation steps.
|
||||
MSD analyses git history, `.planning/` artifact completeness, STATE.md consistency, uncommitted work, and orphaned worktrees. It writes a structured report to `.planning/forensics/report-<timestamp>.md` and surfaces recommended remediation steps.
|
||||
|
||||
`/gsd-forensics` is read-only — it never modifies your project files.
|
||||
`/msd-forensics` is read-only — it never modifies your project files.
|
||||
|
||||
**What it detects:**
|
||||
|
||||
@@ -129,46 +129,46 @@ GSD analyses git history, `.planning/` artifact completeness, STATE.md consisten
|
||||
Once the underlying issue is resolved, re-run the execute command:
|
||||
|
||||
```bash
|
||||
/gsd-execute-phase 1
|
||||
/msd-execute-phase 1
|
||||
```
|
||||
|
||||
GSD skips plans whose `SUMMARY.md` already exists and dispatches executors only for the remaining plans.
|
||||
MSD skips plans whose `SUMMARY.md` already exists and dispatches executors only for the remaining plans.
|
||||
|
||||
If you need to re-execute only a specific wave:
|
||||
|
||||
```bash
|
||||
/gsd-execute-phase 1 --wave 2
|
||||
/msd-execute-phase 1 --wave 2
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Roll back with `/gsd-undo`
|
||||
## Roll back with `/msd-undo`
|
||||
|
||||
If execution produced code you want to discard entirely, roll back using the plan manifest rather than manual `git revert`:
|
||||
|
||||
### Roll back a single plan
|
||||
|
||||
```bash
|
||||
/gsd-undo --plan 03-02
|
||||
/msd-undo --plan 03-02
|
||||
```
|
||||
|
||||
Reverts all commits for plan `02` of phase `3`. GSD shows a confirmation gate before writing any change.
|
||||
Reverts all commits for plan `02` of phase `3`. MSD shows a confirmation gate before writing any change.
|
||||
|
||||
### Roll back an entire phase
|
||||
|
||||
```bash
|
||||
/gsd-undo --phase 03
|
||||
/msd-undo --phase 03
|
||||
```
|
||||
|
||||
Reverts all commits for phase `3`. GSD checks whether any subsequent phases depend on this phase and warns you before proceeding.
|
||||
Reverts all commits for phase `3`. MSD checks whether any subsequent phases depend on this phase and warns you before proceeding.
|
||||
|
||||
### Pick interactively from recent commits
|
||||
|
||||
```bash
|
||||
/gsd-undo --last 5
|
||||
/msd-undo --last 5
|
||||
```
|
||||
|
||||
Shows the five most recent GSD commits and lets you select which to revert.
|
||||
Shows the five most recent MSD commits and lets you select which to revert.
|
||||
|
||||
---
|
||||
|
||||
@@ -177,7 +177,7 @@ Shows the five most recent GSD commits and lets you select which to revert.
|
||||
If you have returned to the project after a context reset or a new session:
|
||||
|
||||
```bash
|
||||
/gsd-resume-work
|
||||
/msd-resume-work
|
||||
```
|
||||
|
||||
Restores your full session context from the last handoff, including the current phase, blockers, and where execution stopped.
|
||||
@@ -185,7 +185,7 @@ Restores your full session context from the last handoff, including the current
|
||||
Alternatively, to see your current position and auto-advance to the correct next step:
|
||||
|
||||
```bash
|
||||
/gsd-progress --next
|
||||
/msd-progress --next
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
Reference in New Issue
Block a user