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
2026-10-06 01:47:40 +02:00
parent fe069b2a56
commit a9a7a328e6
2763 changed files with 78465 additions and 78434 deletions

View File

@@ -2,23 +2,23 @@
**Goal:** Turn phase decisions and research into an atomic, verifiable task plan ready for execution.
**Prerequisites:** `.planning/ROADMAP.md` exists. A `{phase}-CONTEXT.md` from `/gsd-discuss-phase` is strongly recommended but not required.
**Prerequisites:** `.planning/ROADMAP.md` exists. A `{phase}-CONTEXT.md` from `/msd-discuss-phase` is strongly recommended but not required.
---
## Run the standard planning flow
```bash
/gsd-plan-phase 2
/msd-plan-phase 2
```
This runs three stages in sequence:
1. **Research** — A `gsd-phase-researcher` subagent investigates the domain and writes `{phase}-RESEARCH.md`.
2. **Plan** — A `gsd-planner` subagent reads context, research, and requirements, then writes one or more `{phase}-{N}-PLAN.md` files.
3. **Verify** — A `gsd-plan-checker` subagent validates plan quality across eight dimensions and triggers a revision loop (up to three iterations) until quality gates pass.
1. **Research** — A `msd-phase-researcher` subagent investigates the domain and writes `{phase}-RESEARCH.md`.
2. **Plan** — A `msd-planner` subagent reads context, research, and requirements, then writes one or more `{phase}-{N}-PLAN.md` files.
3. **Verify** — A `msd-plan-checker` subagent validates plan quality across eight dimensions and triggers a revision loop (up to three iterations) until quality gates pass.
If no phase number is given, the `/gsd-plan-phase` orchestrating workflow reads `ROADMAP.md` and targets the next unplanned phase. This detection happens in the workflow/LLM layer, not in the `gsd-tools.cjs` CLI — its phase-lookup commands require an explicit phase number.
If no phase number is given, the `/msd-plan-phase` orchestrating workflow reads `ROADMAP.md` and targets the next unplanned phase. This detection happens in the workflow/LLM layer, not in the `msd-tools.cjs` CLI — its phase-lookup commands require an explicit phase number.
---
@@ -27,34 +27,34 @@ If no phase number is given, the `/gsd-plan-phase` orchestrating workflow reads
**If the domain is familiar and you do not need new research:**
```bash
/gsd-plan-phase 3 --skip-research
/msd-plan-phase 3 --skip-research
```
**If RESEARCH.md already exists but you want to force a refresh:**
```bash
/gsd-plan-phase 3 --research
/msd-plan-phase 3 --research
```
**If you want to run research only** — write RESEARCH.md and exit before planning:
```bash
/gsd-plan-phase --research-phase 4
/msd-plan-phase --research-phase 4
```
If RESEARCH.md already exists, you are prompted to update, view, or skip. To force-refresh without the prompt:
```bash
/gsd-plan-phase --research-phase 4 --research
/msd-plan-phase --research-phase 4 --research
```
To print existing RESEARCH.md to stdout without spawning the researcher:
```bash
/gsd-plan-phase --research-phase 4 --view
/msd-plan-phase --research-phase 4 --view
```
Note: `--research-phase <N>` is a flag on `/gsd-plan-phase`. There is no standalone research-phase command — the removed standalone research command was retired in favour of this flag.
Note: `--research-phase <N>` is a flag on `/msd-plan-phase`. There is no standalone research-phase command — the removed standalone research command was retired in favour of this flag.
---
@@ -63,13 +63,13 @@ Note: `--research-phase <N>` is a flag on `/gsd-plan-phase`. There is no standal
**If you want fewer, larger tasks** for a simple or well-understood phase:
```bash
/gsd-plan-phase 2 --granularity coarse
/msd-plan-phase 2 --granularity coarse
```
**If you want more, smaller tasks** for tighter control over a risky or complex phase:
```bash
/gsd-plan-phase 2 --granularity fine
/msd-plan-phase 2 --granularity fine
```
`--granularity` accepts `coarse`, `standard`, or `fine`. It overrides all granularity config keys (`granularities.planning`, `granularity`, `planning.granularity`) for this invocation only — no config edit required. Invalid values are rejected immediately with an error.
@@ -85,13 +85,13 @@ If you want this granularity applied permanently, set it in config — see [CONF
To opt out and plan horizontal layers (the legacy default):
```bash
/gsd-plan-phase 1 --no-tracer
/msd-plan-phase 1 --no-tracer
```
`--mvp` layers MVP enrichment on top of tracer-first — it frames the phase goal as a user story and, on Phase 1 of a new project with no prior phase summaries, also produces `SKELETON.md` (a Walking Skeleton covering project scaffold, routing, one real DB read/write, one real UI interaction, and dev deployment):
```bash
/gsd-plan-phase 1 --mvp
/msd-plan-phase 1 --mvp
```
You can persist MVP enrichment for a phase without the flag by adding `**Mode:** mvp` to that phase's entry in ROADMAP.md.
@@ -103,13 +103,13 @@ You can persist MVP enrichment for a phase without the flag by adding `**Mode:**
**If you want TDD enforcement** — each behaviour-adding task begins with a failing test before implementation:
```bash
/gsd-plan-phase 1 --tdd
/msd-plan-phase 1 --tdd
```
Composable with `--mvp`:
```bash
/gsd-plan-phase 1 --mvp --tdd
/msd-plan-phase 1 --mvp --tdd
```
This produces vertical slices where every behaviour-adding task follows RED → GREEN → REFACTOR. The planner applies `type: tdd` to eligible tasks (business logic, API endpoints, data transformations) and uses standard `type: execute` for UI, configuration, and glue code.
@@ -117,17 +117,17 @@ This produces vertical slices where every behaviour-adding task follows RED →
TDD mode can also be persisted in config:
```bash
node gsd-tools.cjs config-set workflow.tdd_mode true
node msd-tools.cjs config-set workflow.tdd_mode true
```
---
## Replan using cross-AI review feedback
**If you have run `/gsd-review --phase N` and a `REVIEWS.md` exists:**
**If you have run `/msd-review --phase N` and a `REVIEWS.md` exists:**
```bash
/gsd-plan-phase 3 --reviews
/msd-plan-phase 3 --reviews
```
The planner reads `REVIEWS.md` and revises plans to address the feedback. Cannot be combined with `--gaps`.
@@ -135,7 +135,7 @@ The planner reads `REVIEWS.md` and revises plans to address the feedback. Cannot
**If you want an automated loop** — replan and re-review until no HIGH concerns remain:
```bash
/gsd-plan-review-convergence 3
/msd-plan-review-convergence 3
```
The convergence loop runs plan → review → replan → re-review cycles (up to three by default). Use `--max-cycles N` to override the cap.
@@ -147,7 +147,7 @@ The convergence loop runs plan → review → replan → re-review cycles (up to
**If `VERIFICATION.md` exists with unresolved gaps and you want to replan against those gaps only:**
```bash
/gsd-plan-phase 3 --gaps
/msd-plan-phase 3 --gaps
```
Research is skipped; the planner reads the verification gaps directly.
@@ -159,13 +159,13 @@ Research is skipped; the planner reads the verification gaps directly.
**If `workflow.plan_bounce_script` is configured and you want external validation of the finished plan:**
```bash
/gsd-plan-phase 1 --bounce
/msd-plan-phase 1 --bounce
```
To skip bounce even if it is enabled in config:
```bash
/gsd-plan-phase 1 --skip-bounce
/msd-plan-phase 1 --skip-bounce
```
---
@@ -173,7 +173,7 @@ To skip bounce even if it is enabled in config:
## Suppress interactive confirmations
```bash
/gsd-plan-phase --auto
/msd-plan-phase --auto
```
Skips all prompts. Useful in automated pipelines. Research is skipped if `research_enabled` is false in config.
@@ -197,7 +197,7 @@ For the full field reference see [PLAN.md schema](../reference/plan-md.md).
### Plan quality dimensions
The `gsd-plan-checker` validates plans across eight dimensions before allowing execution:
The `msd-plan-checker` validates plans across eight dimensions before allowing execution:
1. Task atomicity — each task is a single concern
2. Dependency correctness — wave ordering is consistent
@@ -217,7 +217,7 @@ The revision loop runs up to three times. If quality gates have not passed after
If a phase has `VERIFICATION.md` with `status: passed`, it is considered closed. Attempting to replan it stops with an error. If the closeout was incorrect, override with `--force`:
```bash
/gsd-plan-phase 2 --force
/msd-plan-phase 2 --force
```
A warning is emitted into the transcript and any committed plan docs.