golem15/msd-core
4
0
Fork 0
Code Issues 1 Pull Requests Actions 3 Packages Projects Releases Wiki Activity

docs(#2197): drop --validate docs for /gsd-plan-phase and /gsd-execute-phase (#2574)

Browse Source 
* docs(#2197): drop --validate docs for /gsd-plan-phase and /gsd-execute-phase

These two commands never parse --validate (silent no-op); the flag is
real only for /gsd-quick. Remove the false flag-table rows and CLI
examples across COMMANDS.md and the how-to guides (en + ja-JP/zh-CN/
ko-KR/pt-BR mirrors), and correct the manager.flags.execute example
from --validate to --cross-ai (a flag execute-phase actually parses).
/gsd-quick's real --validate docs are left untouched.

Ref #2197

* docs(#2197): add changeset for --validate docs removal

---------

Co-authored-by: CI Rebase Check <ci@gsd-redux>
This commit is contained in:
Rezolv
2026-07-24 12:47:53 -04:00
committed by GitHub
parent 3b15a1e3cc
commit 155c08facf
24 changed files with 16 additions and 171 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/how-to/debug-a-failed-execution.md
View File

@@ -114,12 +114,6 @@ If you need to re-execute only a specific wave:
/gsd-execute-phase 1 --wave 2
```
If you want to validate `.planning/` integrity before dispatching:
```bash
/gsd-execute-phase 1 --validate
```
---
## Roll back with `/gsd-undo`

12
docs/how-to/execute-a-phase.md
View File

@@ -45,18 +45,6 @@ GSD executes only Wave 2 plans. It first checks that all earlier waves are compl
---
## Validate state before execution
If you suspect the `.planning/` directory is out of sync with the filesystem — for example after a crash or an interrupted previous run — pass `--validate`:
```bash
/gsd-execute-phase 1 --validate
```
GSD runs a state consistency check before spawning any executors. Detected drift is reported and you can accept or correct it before proceeding.
---
## Resume a stalled execution
If execution stops partway through — a quota error, a network drop, or a crashed session — the wave-level progress is preserved. GSD checks for a `SUMMARY.md` file for each plan; plans that have one are skipped automatically when you re-run:

10
docs/how-to/plan-a-phase.md
View File

@@ -154,16 +154,6 @@ Research is skipped; the planner reads the verification gaps directly.
---
## Validate project state before planning begins
```bash
/gsd-plan-phase 2 --validate
```
Runs state validation before spawning the researcher. Use this if you suspect ROADMAP.md or STATE.md has drifted.
---
## Run an external bounce validation after planning
**If `workflow.plan_bounce_script` is configured and you want external validation of the finished plan:**