From 155c08facfed172a14fbd204ab75c841c706d1f9 Mon Sep 17 00:00:00 2001 From: Rezolv Date: Fri, 24 Jul 2026 12:47:53 -0400 Subject: [PATCH] docs(#2197): drop --validate docs for /gsd-plan-phase and /gsd-execute-phase (#2574) * 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 --- .changeset/quick-cats-travel.md | 5 +++++ docs/COMMANDS.md | 6 +----- docs/CONFIGURATION.md | 4 ++-- docs/how-to/debug-a-failed-execution.md | 6 ------ docs/how-to/execute-a-phase.md | 12 ------------ docs/how-to/plan-a-phase.md | 10 ---------- docs/ja-JP/COMMANDS.md | 6 +----- docs/ja-JP/how-to/debug-a-failed-execution.md | 6 ------ docs/ja-JP/how-to/execute-a-phase.md | 12 ------------ docs/ja-JP/how-to/plan-a-phase.md | 10 ---------- docs/ko-KR/COMMANDS.md | 6 +----- docs/ko-KR/how-to/debug-a-failed-execution.md | 6 ------ docs/ko-KR/how-to/execute-a-phase.md | 12 ------------ docs/ko-KR/how-to/plan-a-phase.md | 10 ---------- docs/pt-BR/COMMANDS.md | 6 +----- docs/pt-BR/CONFIGURATION.md | 4 ++-- docs/pt-BR/how-to/debug-a-failed-execution.md | 6 ------ docs/pt-BR/how-to/execute-a-phase.md | 12 ------------ docs/pt-BR/how-to/plan-a-phase.md | 10 ---------- docs/zh-CN/COMMANDS.md | 6 +----- docs/zh-CN/CONFIGURATION.md | 4 ++-- docs/zh-CN/how-to/debug-a-failed-execution.md | 6 ------ docs/zh-CN/how-to/execute-a-phase.md | 12 ------------ docs/zh-CN/how-to/plan-a-phase.md | 10 ---------- 24 files changed, 16 insertions(+), 171 deletions(-) create mode 100644 .changeset/quick-cats-travel.md diff --git a/.changeset/quick-cats-travel.md b/.changeset/quick-cats-travel.md new file mode 100644 index 000000000..01fd06c62 --- /dev/null +++ b/.changeset/quick-cats-travel.md @@ -0,0 +1,5 @@ +--- +type: Fixed +pr: 2574 +--- +**`--validate` is no longer documented for `/gsd-plan-phase` and `/gsd-execute-phase`** — both commands silently ignored the flag (only `/gsd-quick` implements it), so the docs promised a state-validation step that never ran. The false flag-table rows, CLI examples, and the `manager.flags.execute: "--validate"` config example are removed across the English docs and the ja-JP/zh-CN/ko-KR/pt-BR mirrors; the config example now shows `--cross-ai` (a flag execute-phase actually parses). `/gsd-quick`'s `--validate` docs are unchanged. (#2197) diff --git a/docs/COMMANDS.md b/docs/COMMANDS.md index 62b172571..54e91e9de 100644 --- a/docs/COMMANDS.md +++ b/docs/COMMANDS.md @@ -208,7 +208,6 @@ Research, plan, and verify a phase. | `--ingest ` | Use ADR file(s) instead of discuss-phase for context synthesis | | `--ingest-format ` | Optional ADR parser format override for `--ingest` | | `--reviews` | Replan with cross-AI review feedback from REVIEWS.md | -| `--validate` | Run state validation before planning begins | | `--bounce` | Run external plan bounce validation after planning (uses `workflow.plan_bounce_script`) | | `--skip-bounce` | Skip plan bounce even if enabled in config | | `--mvp` | MVP enrichment on top of the default tracer-first ordering — frames the phase goal as a user story and, on Phase 1 of a new project with no prior phase summaries, also emits `SKELETON.md` (Walking Skeleton). Vertical slicing is now the default (see `--no-tracer`); `--mvp` no longer turns it on. Can be persisted on a phase via `**Mode:** mvp` in ROADMAP.md, which applies `--mvp` automatically without the flag. | @@ -240,7 +239,6 @@ See [Package Legitimacy Gate in the User Guide](USER-GUIDE.md#package-legitimacy /gsd-plan-phase 1 # Research + plan + verify phase 1 /gsd-plan-phase 3 --skip-research # Plan without research (familiar domain) /gsd-plan-phase --auto # Non-interactive planning -/gsd-plan-phase 2 --validate # Validate state before planning /gsd-plan-phase 1 --bounce # Plan + external bounce validation /gsd-plan-phase 2 --ingest docs/adr/0010.md # ADR express path for context synthesis /gsd-plan-phase 2 --ingest 'docs/adr/00*.md' --ingest-format auto @@ -298,7 +296,6 @@ Execute all plans in a phase with wave-based parallelization, or run a specific |----------|----------|-------------| | `N` | **Yes** | Phase number to execute | | `--wave N` | No | Execute only Wave `N` in the phase | -| `--validate` | No | Run state validation before execution begins | | `--cross-ai` | No | Delegate execution to an external AI CLI (uses `workflow.cross_ai_command`) | | `--no-cross-ai` | No | Force local execution even if cross-AI is enabled in config | @@ -310,7 +307,6 @@ Execute all plans in a phase with wave-based parallelization, or run a specific ```bash /gsd-execute-phase 1 # Execute phase 1 /gsd-execute-phase 1 --wave 2 # Execute only Wave 2 -/gsd-execute-phase 1 --validate # Validate state before execution /gsd-execute-phase 2 --cross-ai # Delegate phase 2 to external AI CLI ``` @@ -714,7 +710,7 @@ Configure per-step flags in `.planning/config.json` under `manager.flags`. These "flags": { "discuss": "--auto", "plan": "--skip-research", - "execute": "--validate" + "execute": "--cross-ai" } } } diff --git a/docs/CONFIGURATION.md b/docs/CONFIGURATION.md index ac567ec49..388e1bb9f 100644 --- a/docs/CONFIGURATION.md +++ b/docs/CONFIGURATION.md @@ -1019,7 +1019,7 @@ Configure per-step flags that `/gsd-manager` appends to each dispatched command. |---------|------|---------|-------------| | `manager.flags.discuss` | string | (none) | Flags appended to discuss-phase commands (e.g., `"--auto"`) | | `manager.flags.plan` | string | (none) | Flags appended to plan-phase commands (e.g., `"--skip-research"`) | -| `manager.flags.execute` | string | (none) | Flags appended to execute-phase commands (e.g., `"--validate"`) | +| `manager.flags.execute` | string | (none) | Flags appended to execute-phase commands (e.g., `"--cross-ai"`) | **Example:** @@ -1029,7 +1029,7 @@ Configure per-step flags that `/gsd-manager` appends to each dispatched command. "flags": { "discuss": "--auto", "plan": "--skip-research", - "execute": "--validate" + "execute": "--cross-ai" } } } diff --git a/docs/how-to/debug-a-failed-execution.md b/docs/how-to/debug-a-failed-execution.md index d72e4c784..7c597453e 100644 --- a/docs/how-to/debug-a-failed-execution.md +++ b/docs/how-to/debug-a-failed-execution.md @@ -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` diff --git a/docs/how-to/execute-a-phase.md b/docs/how-to/execute-a-phase.md index 7a528853b..c18ba93f2 100644 --- a/docs/how-to/execute-a-phase.md +++ b/docs/how-to/execute-a-phase.md @@ -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: diff --git a/docs/how-to/plan-a-phase.md b/docs/how-to/plan-a-phase.md index 124adbbba..acd4a8c43 100644 --- a/docs/how-to/plan-a-phase.md +++ b/docs/how-to/plan-a-phase.md @@ -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:** diff --git a/docs/ja-JP/COMMANDS.md b/docs/ja-JP/COMMANDS.md index 8a232972b..02b448508 100644 --- a/docs/ja-JP/COMMANDS.md +++ b/docs/ja-JP/COMMANDS.md @@ -171,7 +171,6 @@ GSD ワークスペースを管理 — リポジトリコピーと独立した ` | `--ingest ` | コンテキスト統合に discuss-phase の代わりに ADR ファイルを使用 | | `--ingest-format ` | `--ingest` のオプション ADR パーサーフォーマットの上書き | | `--reviews` | REVIEWS.md のクロス AI レビューフィードバックで再計画 | -| `--validate` | 計画開始前に状態検証を実行 | | `--bounce` | 計画後に外部プランバウンス検証を実行（`workflow.plan_bounce_script` を使用） | | `--skip-bounce` | 設定で有効になっている場合でもプランバウンスをスキップ | | `--mvp` | 垂直 MVP モード — プランナーはタスクを水平レイヤーではなく機能スライス（UI→API→DB）として整理します。以前のフェーズサマリーがない新規プロジェクトのフェーズ1では、`SKELETON.md`（Walking Skeleton）も生成します。ROADMAP.md の `**Mode:** mvp` でフェーズごとに永続化でき、フラグなしで `--mvp` が自動適用されます。 | @@ -200,7 +199,6 @@ WebSearch から取得したパッケージは `[ASSUMED]`（`[VERIFIED]` では /gsd-plan-phase 1 # フェーズ1のリサーチ + 計画 + 検証 /gsd-plan-phase 3 --skip-research # リサーチなしの計画（既知のドメイン） /gsd-plan-phase --auto # 非インタラクティブな計画 -/gsd-plan-phase 2 --validate # 計画前に状態を検証 /gsd-plan-phase 1 --bounce # 計画 + 外部バウンス検証 /gsd-plan-phase 2 --ingest docs/adr/0010.md # コンテキスト統合のための ADR エクスプレスパス /gsd-plan-phase 2 --ingest 'docs/adr/00*.md' --ingest-format auto @@ -258,7 +256,6 @@ WebSearch から取得したパッケージは `[ASSUMED]`（`[VERIFIED]` では |----------|----------|-------------| | `N` | **Yes** | 実行するフェーズ番号 | | `--wave N` | No | フェーズ内の波 `N` のみを実行 | -| `--validate` | No | 実行開始前に状態検証を実行 | | `--cross-ai` | No | 外部 AI CLI に実行を委任（`workflow.cross_ai_command` を使用） | | `--no-cross-ai` | No | 設定でクロス AI が有効な場合でもローカル実行を強制 | @@ -270,7 +267,6 @@ WebSearch から取得したパッケージは `[ASSUMED]`（`[VERIFIED]` では ```bash /gsd-execute-phase 1 # フェーズ1を実行 /gsd-execute-phase 1 --wave 2 # 波2のみを実行 -/gsd-execute-phase 1 --validate # 実行前に状態を検証 /gsd-execute-phase 2 --cross-ai # フェーズ2を外部 AI CLI に委任 ``` @@ -588,7 +584,7 @@ Nyquist 検証ギャップを事後的に監査して埋めます。 "flags": { "discuss": "--auto", "plan": "--skip-research", - "execute": "--validate" + "execute": "--cross-ai" } } } diff --git a/docs/ja-JP/how-to/debug-a-failed-execution.md b/docs/ja-JP/how-to/debug-a-failed-execution.md index 7bf894561..18eb5e062 100644 --- a/docs/ja-JP/how-to/debug-a-failed-execution.md +++ b/docs/ja-JP/how-to/debug-a-failed-execution.md @@ -114,12 +114,6 @@ GSD はすでに `SUMMARY.md` が存在するプランをスキップし、残 /gsd-execute-phase 1 --wave 2 ``` -dispatching 前に `.planning/` の整合性を検証したい場合： - -```bash -/gsd-execute-phase 1 --validate -``` - --- ## `/gsd-undo` でロールバックする diff --git a/docs/ja-JP/how-to/execute-a-phase.md b/docs/ja-JP/how-to/execute-a-phase.md index 497d1a803..ae799b862 100644 --- a/docs/ja-JP/how-to/execute-a-phase.md +++ b/docs/ja-JP/how-to/execute-a-phase.md @@ -45,18 +45,6 @@ GSD はウェーブ 2 のプランのみを実行します。実行前に前の --- -## 実行前に状態を検証する - -クラッシュや前の実行の中断後など、`.planning/` ディレクトリがファイルシステムと同期がとれていない可能性がある場合は `--validate` を指定します: - -```bash -/gsd-execute-phase 1 --validate -``` - -GSD はエグゼキュータを起動する前に状態の一貫性チェックを実行します。検出されたずれを報告し、続行前に受け入れるか修正するかを選択できます。 - ---- - ## 停止した実行を再開する クォータエラー、ネットワーク切断、セッションのクラッシュなどで実行が途中停止した場合、ウェーブレベルの進捗は保持されています。GSD は各プランの `SUMMARY.md` ファイルを確認し、すでに存在するプランは再実行時に自動的にスキップされます: diff --git a/docs/ja-JP/how-to/plan-a-phase.md b/docs/ja-JP/how-to/plan-a-phase.md index aa5809001..629d05871 100644 --- a/docs/ja-JP/how-to/plan-a-phase.md +++ b/docs/ja-JP/how-to/plan-a-phase.md @@ -128,16 +128,6 @@ node gsd-tools.cjs config-set workflow.tdd_mode true --- -## プランニング開始前にプロジェクト状態を検証する - -```bash -/gsd-plan-phase 2 --validate -``` - -リサーチャーを起動する前に状態検証を実行します。ROADMAP.md や STATE.md がずれている可能性がある場合に使用してください。 - ---- - ## プランニング後に外部バウンス検証を実行する **`workflow.plan_bounce_script` が設定されており、完成したプランに対して外部検証を行いたい場合:** diff --git a/docs/ko-KR/COMMANDS.md b/docs/ko-KR/COMMANDS.md index 8ed4b4758..313b0b1fb 100644 --- a/docs/ko-KR/COMMANDS.md +++ b/docs/ko-KR/COMMANDS.md @@ -171,7 +171,6 @@ GSD 워크스페이스 관리 — 리포지토리 복사본과 독립적인 `.pl | `--ingest ` | 컨텍스트 합성을 위해 discuss-phase 대신 ADR 파일 사용 | | `--ingest-format ` | `--ingest`에 대한 선택적 ADR 파서 형식 재정의 | | `--reviews` | REVIEWS.md의 크로스 AI 리뷰 피드백으로 재계획 | -| `--validate` | 계획 시작 전 상태 검증 실행 | | `--bounce` | 계획 후 외부 계획 바운스 검증 실행 (`workflow.plan_bounce_script` 사용) | | `--skip-bounce` | 설정에서 활성화되어 있어도 계획 바운스 생략 | | `--mvp` | 수직 MVP 모드 — 계획자가 수평 레이어 대신 기능 슬라이스(UI→API→DB)로 작업을 구성합니다. 이전 단계 요약이 없는 새 프로젝트의 단계 1에서는 `SKELETON.md`(Walking Skeleton)도 생성합니다. ROADMAP.md에 `**Mode:** mvp`를 추가하여 단계별로 지속시킬 수 있으며, 플래그 없이 자동으로 `--mvp`가 적용됩니다. | @@ -200,7 +199,6 @@ WebSearch에서 가져온 패키지는 `[ASSUMED]`(`[VERIFIED]`가 아님)로 /gsd-plan-phase 1 # 단계 1 리서치 + 계획 + 검증 /gsd-plan-phase 3 --skip-research # 리서치 없이 계획 (친숙한 도메인) /gsd-plan-phase --auto # 비대화형 계획 수립 -/gsd-plan-phase 2 --validate # 계획 전 상태 검증 /gsd-plan-phase 1 --bounce # 계획 + 외부 바운스 검증 /gsd-plan-phase 2 --ingest docs/adr/0010.md # 컨텍스트 합성을 위한 ADR 익스프레스 경로 /gsd-plan-phase 2 --ingest 'docs/adr/00*.md' --ingest-format auto @@ -258,7 +256,6 @@ WebSearch에서 가져온 패키지는 `[ASSUMED]`(`[VERIFIED]`가 아님)로 |----------|----------|-------------| | `N` | **예** | 실행할 단계 번호 | | `--wave N` | 아니요 | 단계에서 웨이브 `N`만 실행 | -| `--validate` | 아니요 | 실행 시작 전 상태 검증 실행 | | `--cross-ai` | 아니요 | 외부 AI CLI에 실행 위임 (`workflow.cross_ai_command` 사용) | | `--no-cross-ai` | 아니요 | 설정에서 크로스 AI가 활성화되어 있어도 로컬 실행 강제 | @@ -270,7 +267,6 @@ WebSearch에서 가져온 패키지는 `[ASSUMED]`(`[VERIFIED]`가 아님)로 ```bash /gsd-execute-phase 1 # 단계 1 실행 /gsd-execute-phase 1 --wave 2 # 웨이브 2만 실행 -/gsd-execute-phase 1 --validate # 실행 전 상태 검증 /gsd-execute-phase 2 --cross-ai # 단계 2를 외부 AI CLI에 위임 ``` @@ -592,7 +588,7 @@ Nyquist 검증 갭을 소급하여 감사하고 보완합니다. "flags": { "discuss": "--auto", "plan": "--skip-research", - "execute": "--validate" + "execute": "--cross-ai" } } } diff --git a/docs/ko-KR/how-to/debug-a-failed-execution.md b/docs/ko-KR/how-to/debug-a-failed-execution.md index ce57bf2db..06afb4c07 100644 --- a/docs/ko-KR/how-to/debug-a-failed-execution.md +++ b/docs/ko-KR/how-to/debug-a-failed-execution.md @@ -114,12 +114,6 @@ GSD는 이미 `SUMMARY.md`가 존재하는 플랜을 건너뛰고 나머지 플 /gsd-execute-phase 1 --wave 2 ``` -디스패치하기 전에 `.planning/` 무결성을 검증하려면: - -```bash -/gsd-execute-phase 1 --validate -``` - --- ## `/gsd-undo`로 롤백 diff --git a/docs/ko-KR/how-to/execute-a-phase.md b/docs/ko-KR/how-to/execute-a-phase.md index 7202e4580..227031f5a 100644 --- a/docs/ko-KR/how-to/execute-a-phase.md +++ b/docs/ko-KR/how-to/execute-a-phase.md @@ -45,18 +45,6 @@ GSD는 웨이브 2 계획만 실행합니다. 먼저 이전 웨이브가 완료 --- -## 실행 전 상태 검증 - -충돌이나 이전 실행이 중단된 후 `.planning/` 디렉터리가 파일 시스템과 동기화되지 않았을 것으로 의심되는 경우 `--validate`를 사용하세요: - -```bash -/gsd-execute-phase 1 --validate -``` - -GSD는 실행자를 실행하기 전에 상태 일관성 검사를 실행합니다. 감지된 드리프트가 보고되며 진행 전에 수락하거나 수정할 수 있습니다. - ---- - ## 중단된 실행 재개 실행이 도중에 중단된 경우(할당량 오류, 네트워크 끊김, 세션 충돌 등) 웨이브 레벨 진행 상황은 보존됩니다. GSD는 각 계획의 `SUMMARY.md` 파일을 확인합니다. 이미 파일이 있는 계획은 재실행 시 자동으로 건너뜁니다: diff --git a/docs/ko-KR/how-to/plan-a-phase.md b/docs/ko-KR/how-to/plan-a-phase.md index 1231f3061..1a749f539 100644 --- a/docs/ko-KR/how-to/plan-a-phase.md +++ b/docs/ko-KR/how-to/plan-a-phase.md @@ -128,16 +128,6 @@ node gsd-tools.cjs config-set workflow.tdd_mode true --- -## 기획 시작 전 프로젝트 상태 검증 - -```bash -/gsd-plan-phase 2 --validate -``` - -리서처를 실행하기 전에 상태 검증을 실행합니다. ROADMAP.md 또는 STATE.md가 최신 상태와 맞지 않다고 의심되는 경우 사용하세요. - ---- - ## 기획 후 외부 바운스 검증 실행 **`workflow.plan_bounce_script`가 설정되어 있고 완성된 계획의 외부 검증을 원하는 경우:** diff --git a/docs/pt-BR/COMMANDS.md b/docs/pt-BR/COMMANDS.md index b57685880..c670dbbf2 100644 --- a/docs/pt-BR/COMMANDS.md +++ b/docs/pt-BR/COMMANDS.md @@ -171,7 +171,6 @@ Pesquisa, planeja e verifica uma fase. | `--ingest ` | Usa arquivo(s) ADR em vez de discuss-phase para síntese de contexto | | `--ingest-format ` | Substituição opcional do formato do parser ADR para `--ingest` | | `--reviews` | Replaneja com feedback de revisão cross-AI do REVIEWS.md | -| `--validate` | Executa validação de estado antes de iniciar o planejamento | | `--bounce` | Executa validação de bounce externo após o planejamento (usa `workflow.plan_bounce_script`) | | `--skip-bounce` | Ignora o bounce do plano mesmo se habilitado na configuração | | `--mvp` | Modo MVP vertical — o planejador organiza tarefas como fatias de funcionalidade (UI→API→DB) em vez de camadas horizontais. Na Fase 1 de um novo projeto sem resumos de fases anteriores, também emite `SKELETON.md` (Walking Skeleton). Pode ser persistido em uma fase via `**Mode:** mvp` no ROADMAP.md, o que aplica `--mvp` automaticamente sem a flag. | @@ -200,7 +199,6 @@ Consulte o [Portão de Legitimidade de Pacotes no Guia do Usuário](USER-GUIDE.m /gsd-plan-phase 1 # Pesquisa + plano + verificação da fase 1 /gsd-plan-phase 3 --skip-research # Planejar sem pesquisa (domínio familiar) /gsd-plan-phase --auto # Planejamento não interativo -/gsd-plan-phase 2 --validate # Valida estado antes do planejamento /gsd-plan-phase 1 --bounce # Plano + validação de bounce externo /gsd-plan-phase 2 --ingest docs/adr/0010.md # Caminho expresso via ADR para síntese de contexto /gsd-plan-phase 2 --ingest 'docs/adr/00*.md' --ingest-format auto @@ -258,7 +256,6 @@ Executa todos os planos de uma fase com paralelização baseada em waves, ou exe |-----------|-------------|-----------| | `N` | **Sim** | Número da fase a executar | | `--wave N` | Não | Executa somente a Wave `N` da fase | -| `--validate` | Não | Executa validação de estado antes de iniciar a execução | | `--cross-ai` | Não | Delega a execução para uma CLI de IA externa (usa `workflow.cross_ai_command`) | | `--no-cross-ai` | Não | Força execução local mesmo se cross-AI estiver habilitado na configuração | @@ -270,7 +267,6 @@ Executa todos os planos de uma fase com paralelização baseada em waves, ou exe ```bash /gsd-execute-phase 1 # Executa a fase 1 /gsd-execute-phase 1 --wave 2 # Executa somente a Wave 2 -/gsd-execute-phase 1 --validate # Valida estado antes da execução /gsd-execute-phase 2 --cross-ai # Delega a fase 2 para CLI de IA externa ``` @@ -590,7 +586,7 @@ Configure flags por etapa em `.planning/config.json` sob `manager.flags`. Essas "flags": { "discuss": "--auto", "plan": "--skip-research", - "execute": "--validate" + "execute": "--cross-ai" } } } diff --git a/docs/pt-BR/CONFIGURATION.md b/docs/pt-BR/CONFIGURATION.md index c13b3ca6e..8b742641b 100644 --- a/docs/pt-BR/CONFIGURATION.md +++ b/docs/pt-BR/CONFIGURATION.md @@ -734,7 +734,7 @@ Configure flags por etapa que `/gsd-manager` acrescenta a cada comando despachad |---------|------|---------|-------------| | `manager.flags.discuss` | string | (nenhum) | Flags acrescidas a comandos de discuss-phase (por exemplo, `"--auto"`) | | `manager.flags.plan` | string | (nenhum) | Flags acrescidas a comandos de plan-phase (por exemplo, `"--skip-research"`) | -| `manager.flags.execute` | string | (nenhum) | Flags acrescidas a comandos de execute-phase (por exemplo, `"--validate"`) | +| `manager.flags.execute` | string | (nenhum) | Flags acrescidas a comandos de execute-phase (por exemplo, `"--cross-ai"`) | **Exemplo:** @@ -744,7 +744,7 @@ Configure flags por etapa que `/gsd-manager` acrescenta a cada comando despachad "flags": { "discuss": "--auto", "plan": "--skip-research", - "execute": "--validate" + "execute": "--cross-ai" } } } diff --git a/docs/pt-BR/how-to/debug-a-failed-execution.md b/docs/pt-BR/how-to/debug-a-failed-execution.md index 1611870a4..e50081923 100644 --- a/docs/pt-BR/how-to/debug-a-failed-execution.md +++ b/docs/pt-BR/how-to/debug-a-failed-execution.md @@ -114,12 +114,6 @@ Se precisar executar novamente apenas uma onda específica: /gsd-execute-phase 1 --wave 2 ``` -Se quiser validar a integridade de `.planning/` antes de despachar: - -```bash -/gsd-execute-phase 1 --validate -``` - --- ## Reverter com `/gsd-undo` diff --git a/docs/pt-BR/how-to/execute-a-phase.md b/docs/pt-BR/how-to/execute-a-phase.md index 7ea493bb3..8f3b3156e 100644 --- a/docs/pt-BR/how-to/execute-a-phase.md +++ b/docs/pt-BR/how-to/execute-a-phase.md @@ -45,18 +45,6 @@ O GSD Core executa apenas os planos da Onda 2. Ele primeiro verifica se todas as --- -## Validar o estado antes da execução - -Se você suspeitar que o diretório `.planning/` está fora de sincronia com o sistema de arquivos — por exemplo, após uma falha ou uma execução anterior interrompida — passe `--validate`: - -```bash -/gsd-execute-phase 1 --validate -``` - -O GSD Core executa uma verificação de consistência de estado antes de criar qualquer executor. Desvios detectados são relatados e você pode aceitá-los ou corrigi-los antes de prosseguir. - ---- - ## Retomar uma execução paralisada Se a execução parar no meio — um erro de cota, uma queda de rede ou uma sessão travada — o progresso no nível de onda é preservado. O GSD Core verifica a existência de um arquivo `SUMMARY.md` para cada plano; planos que já possuem esse arquivo são ignorados automaticamente ao reexecutar: diff --git a/docs/pt-BR/how-to/plan-a-phase.md b/docs/pt-BR/how-to/plan-a-phase.md index 75fd2b061..4225098a5 100644 --- a/docs/pt-BR/how-to/plan-a-phase.md +++ b/docs/pt-BR/how-to/plan-a-phase.md @@ -128,16 +128,6 @@ A pesquisa é ignorada; o planejador lê as lacunas de verificação diretamente --- -## Validar o estado do projeto antes de iniciar o planejamento - -```bash -/gsd-plan-phase 2 --validate -``` - -Executa a validação de estado antes de acionar o pesquisador. Use isso se suspeitar que o ROADMAP.md ou STATE.md derivou. - ---- - ## Executar uma validação externa de bounce após o planejamento **Se `workflow.plan_bounce_script` estiver configurado e você quiser validação externa do plano concluído:** diff --git a/docs/zh-CN/COMMANDS.md b/docs/zh-CN/COMMANDS.md index 691e4d2d4..0f2333820 100644 --- a/docs/zh-CN/COMMANDS.md +++ b/docs/zh-CN/COMMANDS.md @@ -171,7 +171,6 @@ v1.40 中，六个命名空间路由器作为第一阶段入口点随附发布 | `--ingest ` | 使用 ADR 文件代替 discuss-phase 进行上下文综合 | | `--ingest-format ` | `--ingest` 的可选 ADR 解析器格式覆盖 | | `--reviews` | 根据 REVIEWS.md 中的跨 AI 审查反馈重新规划 | -| `--validate` | 在规划开始前运行状态验证 | | `--bounce` | 规划完成后运行外部计划弹回验证（使用 `workflow.plan_bounce_script`） | | `--skip-bounce` | 即使配置中已启用也跳过计划弹回 | | `--mvp` | 垂直 MVP 模式 — 规划器将任务组织为功能切片（UI→API→DB），而非水平分层。在无先前阶段摘要的新项目第 1 阶段使用时，还会生成 `SKELETON.md`（行走骨架）。可通过在 ROADMAP.md 中设置 `**Mode:** mvp` 持久化应用于某阶段，届时无需标志即可自动应用 `--mvp`。 | @@ -200,7 +199,6 @@ v1.40 中，六个命名空间路由器作为第一阶段入口点随附发布 /gsd-plan-phase 1 # 研究 + 规划 + 验证阶段 1 /gsd-plan-phase 3 --skip-research # 无需研究直接规划（熟悉的领域） /gsd-plan-phase --auto # 非交互式规划 -/gsd-plan-phase 2 --validate # 规划前验证状态 /gsd-plan-phase 1 --bounce # 规划 + 外部弹回验证 /gsd-plan-phase 2 --ingest docs/adr/0010.md # 使用 ADR 快速通道进行上下文综合 /gsd-plan-phase 2 --ingest 'docs/adr/00*.md' --ingest-format auto @@ -258,7 +256,6 @@ v1.40 中，六个命名空间路由器作为第一阶段入口点随附发布 |----------|----------|-------------| | `N` | **是** | 要执行的阶段编号 | | `--wave N` | 否 | 仅执行阶段中的第 `N` 波 | -| `--validate` | 否 | 在执行开始前运行状态验证 | | `--cross-ai` | 否 | 将执行委托给外部 AI CLI（使用 `workflow.cross_ai_command`） | | `--no-cross-ai` | 否 | 即使配置中启用了跨 AI 也强制本地执行 | @@ -270,7 +267,6 @@ v1.40 中，六个命名空间路由器作为第一阶段入口点随附发布 ```bash /gsd-execute-phase 1 # 执行阶段 1 /gsd-execute-phase 1 --wave 2 # 仅执行第 2 波 -/gsd-execute-phase 1 --validate # 执行前验证状态 /gsd-execute-phase 2 --cross-ai # 将阶段 2 委托给外部 AI CLI ``` @@ -588,7 +584,7 @@ ROADMAP.md 中阶段的 CRUD 操作 — 通过单一合并命令添加、插入 "flags": { "discuss": "--auto", "plan": "--skip-research", - "execute": "--validate" + "execute": "--cross-ai" } } } diff --git a/docs/zh-CN/CONFIGURATION.md b/docs/zh-CN/CONFIGURATION.md index d236615c1..0155fc139 100644 --- a/docs/zh-CN/CONFIGURATION.md +++ b/docs/zh-CN/CONFIGURATION.md @@ -712,7 +712,7 @@ gsd-tools query config-set features.thinking_partner false |---------|------|---------|-------------| | `manager.flags.discuss` | string | （无） | 追加到 discuss-phase 命令的标志（如 `"--auto"`） | | `manager.flags.plan` | string | （无） | 追加到 plan-phase 命令的标志（如 `"--skip-research"`） | -| `manager.flags.execute` | string | （无） | 追加到 execute-phase 命令的标志（如 `"--validate"`） | +| `manager.flags.execute` | string | （无） | 追加到 execute-phase 命令的标志（如 `"--cross-ai"`） | **示例：** @@ -722,7 +722,7 @@ gsd-tools query config-set features.thinking_partner false "flags": { "discuss": "--auto", "plan": "--skip-research", - "execute": "--validate" + "execute": "--cross-ai" } } } diff --git a/docs/zh-CN/how-to/debug-a-failed-execution.md b/docs/zh-CN/how-to/debug-a-failed-execution.md index 522b16508..00d3b7bde 100644 --- a/docs/zh-CN/how-to/debug-a-failed-execution.md +++ b/docs/zh-CN/how-to/debug-a-failed-execution.md @@ -114,12 +114,6 @@ GSD 会跳过 `SUMMARY.md` 已存在的计划，仅为剩余计划分派执行 /gsd-execute-phase 1 --wave 2 ``` -如果您想在分派前验证 `.planning/` 的完整性： - -```bash -/gsd-execute-phase 1 --validate -``` - --- ## 使用 `/gsd-undo` 回滚 diff --git a/docs/zh-CN/how-to/execute-a-phase.md b/docs/zh-CN/how-to/execute-a-phase.md index 043fcfc4f..75fc90596 100644 --- a/docs/zh-CN/how-to/execute-a-phase.md +++ b/docs/zh-CN/how-to/execute-a-phase.md @@ -45,18 +45,6 @@ GSD Core 仅执行第 2 波次的计划。它会首先检查所有较早波次 --- -## 执行前验证状态 - -如果你怀疑 `.planning/` 目录与文件系统不同步——例如在崩溃或上一次运行中断之后——请传入 `--validate`： - -```bash -/gsd-execute-phase 1 --validate -``` - -GSD Core 在生成任何执行器之前运行状态一致性检查。检测到的偏差会被上报，你可以在继续之前接受或纠正。 - ---- - ## 恢复停滞的执行 如果执行中途停止——配额错误、网络断开或会话崩溃——波次级别的进度会被保留。GSD Core 会检查每个计划的 `SUMMARY.md` 文件；已有该文件的计划在重新运行时会自动跳过： diff --git a/docs/zh-CN/how-to/plan-a-phase.md b/docs/zh-CN/how-to/plan-a-phase.md index 017f99c51..8c18f9f07 100644 --- a/docs/zh-CN/how-to/plan-a-phase.md +++ b/docs/zh-CN/how-to/plan-a-phase.md @@ -128,16 +128,6 @@ node gsd-tools.cjs config-set workflow.tdd_mode true --- -## 在规划开始前验证项目状态 - -```bash -/gsd-plan-phase 2 --validate -``` - -在启动研究代理前运行状态验证。如果怀疑 ROADMAP.md 或 STATE.md 已发生偏移，请使用此选项。 - ---- - ## 规划完成后运行外部弹跳验证 **如果已配置 `workflow.plan_bounce_script` 且需要对完成的计划进行外部验证：**