* feat(plan-phase): --research-phase flag absorbs deleted /gsd-research-phase + scrub stale refs (#3042, #3044) #3042 (orphaned research-phase): /gsd-research-phase had a workflow file but no slash-command stub. Rather than restore the orphan, the research- only capability is now a flag on /gsd-plan-phase: /gsd-plan-phase --research-phase <N> When set, the workflow scopes to phase N, runs the research step (Section 5 of the existing plan-phase workflow), then early-exits before the planner/plan-checker/verifier chain. Per RCA against the deleted standalone, the flag adds two modifiers to fully cover the original surface (Option B from the RCA discussion): - --view : print existing RESEARCH.md to stdout, no spawn. Cheapest mode for the correction-without-replanning loop the issue reporter explicitly called out. Errors with a clear hint if RESEARCH.md is missing. - --research : reuse the existing "force re-research" semantics. In research-only mode this skips the existing-RESEARCH.md prompt and re-spawns unconditionally. - Neither flag, RESEARCH.md exists : prompt update/view/skip. Mirrors the deleted standalone's existing-artifact menu (#3042 RCA). #3044 (stale slash-command refs): scrubbed five deleted commands from all user-facing surfaces, including English docs, 4 localized doc sets (ja-JP, ko-KR, zh-CN, pt-BR), workflows, templates, and references. /gsd-check-todos → /gsd-capture --list /gsd-new-workspace → /gsd-workspace --new /gsd-status → /gsd-progress /gsd-plan-milestone-gaps → table rows / orphan sections removed (PR #3038 only scrubbed workflows/agent; missed the docs surfaces this PR covers) /gsd-research-phase → /gsd-plan-phase --research-phase Includes a fix to docs/issue-driven-orchestration.md (PR #3036) which itself referenced /gsd-new-workspace 4 times — self-correction. Removed: - get-shit-done/workflows/research-phase.md (orphan, capability absorbed into --research-phase flag) Tests: - tests/bug-3042-3044-research-flag-and-stale-refs.test.cjs — 46 structural-IR tests across both bugs: - argument-hint advertises --research-phase + --view - workflow parses --research-phase, sets RESEARCH_ONLY, early-exits before planner - --view prints RESEARCH.md without spawning - --research forces refresh in research-only mode - existing-RESEARCH.md prompt path with update/view/skip - workflows/research-phase.md is removed - 5 deleted slash-commands absent from 17 English user-facing surfaces + 16 localized doc surfaces (4 locales × 4 docs each) - replacement command tokens present where deleted ones lived 6950/6950 full suite pass. Lints clean. Closes #3042 Closes #3044 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix: address all 8 CR findings on PR #3045 Major (3): - get-shit-done/workflows/plan-phase.md:344 — added explicit early-exit guard at Section 5.1: "Skip if RESEARCH_ONLY=true". Without it, an LLM could fall through "use existing, skip to step 6" → planner spawn, violating the research-only contract. The guard makes the early-exit unreachable from any non-research-only branch. - get-shit-done/references/continuation-format.md (3 examples) + zh-CN/.../continuation-format.md (3 examples) — pointed to `/gsd-plan-phase --research-phase` but docs/COMMANDS.md didn't document the flag. Added a full --research-phase + --view + --research modifier section to the /gsd-plan-phase flag table in COMMANDS.md so the canonical reference matches the continuation examples. Minor (5): - docs/FEATURES.md:1632 — `/gsd-plan-phase --research-phase` → `/gsd-plan-phase --research-phase <N>` (include required arg). - get-shit-done/templates/README.md:46 — NN-VALIDATION.md producer reverted from `/gsd-plan-phase --research-phase` (Nyquist) to plain `/gsd-plan-phase` (Nyquist). VALIDATION.md is created during normal Nyquist flow, not research-only mode — the bulk replacement was wrong for that line. - get-shit-done/workflows/help.md:89 — signature line was missing `--research`; added it alongside `--research-phase` and `--view`. - tests/bug-3042-3044-...:197 — promptHasView/promptHasSkip were tautological (matched anywhere in 1700-line workflow). Tightened to a proximity check anchored on "RESEARCH.md already exists" prompt header within a 600-char window. Updated workflow to emit that literal phrase. - tests/feat-2840-...:95 — workspace assertion used `/gsd-workspace` but the documented replacement is `/gsd-workspace --new`. Tightened to require both tokens (in 3 places: requiredCommands list, regex in conceptPairs, error message). 6950/6950 full suite pass. Lint clean. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
Tom Boucher
@@ -123,6 +123,8 @@ Research, plan, and verify a phase.
|
||||
| `--auto` | Skip interactive confirmations |
|
||||
| `--research` | Force re-research even if RESEARCH.md exists |
|
||||
| `--skip-research` | Skip domain research step |
|
||||
| `--research-phase <N>` | Research-only mode: spawn researcher for phase `<N>`, write RESEARCH.md, exit before planner. Replaces the deleted `gsd-research-phase` standalone command (#3042). |
|
||||
| `--view` | Research-only modifier: when used with `--research-phase`, print existing RESEARCH.md to stdout and exit (no spawn). |
|
||||
| `--gaps` | Gap closure mode (reads VERIFICATION.md, skips research) |
|
||||
| `--skip-verify` | Skip plan checker verification loop |
|
||||
| `--prd <file>` | Use a PRD file instead of discuss-phase for context |
|
||||
@@ -134,12 +136,20 @@ Research, plan, and verify a phase.
|
||||
**Prerequisites:** `.planning/ROADMAP.md` exists
|
||||
**Produces:** `{phase}-RESEARCH.md`, `{phase}-{N}-PLAN.md`, `{phase}-VALIDATION.md`
|
||||
|
||||
**Research-only mode (`--research-phase <N>`):**
|
||||
- No modifier: prompts `update / view / skip` if RESEARCH.md already exists.
|
||||
- With `--research`: force-refresh — re-spawn researcher unconditionally, no prompt.
|
||||
- With `--view`: print existing RESEARCH.md to stdout, no spawn. Errors if RESEARCH.md missing.
|
||||
|
||||
```bash
|
||||
/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 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 --research-phase 4 # Research only on phase 4 (prompts if RESEARCH.md exists)
|
||||
/gsd-plan-phase --research-phase 4 --view # Print existing RESEARCH.md, no spawn
|
||||
/gsd-plan-phase --research-phase 4 --research # Force-refresh research, no prompt
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
@@ -449,7 +449,6 @@
|
||||
- REQ-MILE-08: New milestone MUST follow same flow as new-project (questions → research → requirements → roadmap)
|
||||
- REQ-MILE-09: New milestone MUST NOT reset existing workflow configuration
|
||||
|
||||
**Gap Closure:** `/gsd-plan-milestone-gaps` creates phases to close gaps identified by audit.
|
||||
|
||||
---
|
||||
|
||||
@@ -865,7 +864,7 @@ continues. Drift detection cannot fail verification.
|
||||
|
||||
### 29. Todo Management
|
||||
|
||||
**Commands:** `/gsd-add-todo [desc]`, `/gsd-check-todos`
|
||||
**Commands:** `/gsd-add-todo [desc]`, `/gsd-capture --list`
|
||||
|
||||
**Purpose:** Capture ideas and tasks during sessions for later work.
|
||||
|
||||
@@ -1630,7 +1629,7 @@ Test suite that scans all agent, workflow, and command files for embedded inject
|
||||
|
||||
### 65. Claim Provenance Tagging
|
||||
|
||||
**Part of:** `/gsd-research-phase`
|
||||
**Part of:** `/gsd-plan-phase --research-phase <N>`
|
||||
|
||||
**Purpose:** Ensure research claims are tagged with source evidence and assumptions are logged separately.
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
{
|
||||
"generated": "2026-05-02",
|
||||
"generated": "2026-05-03",
|
||||
"families": {
|
||||
"agents": [
|
||||
"gsd-advisor-researcher",
|
||||
@@ -163,7 +163,6 @@
|
||||
"reapply-patches.md",
|
||||
"remove-phase.md",
|
||||
"remove-workspace.md",
|
||||
"research-phase.md",
|
||||
"resume-project.md",
|
||||
"review.md",
|
||||
"scan.md",
|
||||
|
||||
@@ -162,7 +162,7 @@ These six routers are descriptor-only entries that the model picks first; the bo
|
||||
|
||||
---
|
||||
|
||||
## Workflows (85 shipped)
|
||||
## Workflows (84 shipped)
|
||||
|
||||
Full roster at `get-shit-done/workflows/*.md`. Workflows are thin orchestrators that commands reference internally; most are not read directly by end users. Rows below map each workflow file to its role (derived from the `<purpose>` block) and, where applicable, to the command that invokes it.
|
||||
|
||||
@@ -211,12 +211,11 @@ Full roster at `get-shit-done/workflows/*.md`. Workflows are thin orchestrators
|
||||
| `milestone-summary.md` | Milestone summary synthesis — onboarding and review artifact from milestone artifacts. | `/gsd-milestone-summary` |
|
||||
| `new-milestone.md` | Start a new milestone cycle — load project context, gather goals, update PROJECT.md/STATE.md. | `/gsd-new-milestone` |
|
||||
| `new-project.md` | Unified new-project flow — questioning, research (optional), requirements, roadmap. | `/gsd-new-project` |
|
||||
| `new-workspace.md` | Create an isolated workspace with repo worktrees/clones and an independent `.planning/`. | `/gsd-new-workspace` |
|
||||
| `new-workspace.md` | Create an isolated workspace with repo worktrees/clones and an independent `.planning/`. | `/gsd-workspace --new` |
|
||||
| `next.md` | Detect current project state and automatically advance to the next logical step. | `/gsd-progress --next` |
|
||||
| `node-repair.md` | Autonomous repair operator for failed task verification; invoked by `execute-plan`. | `execute-plan.md` (recovery) |
|
||||
| `note.md` | Zero-friction idea capture — one Write call, one confirmation line. | `/gsd-capture --note` |
|
||||
| `pause-work.md` | Create structured `.planning/HANDOFF.json` and `.continue-here.md` handoff files. | `/gsd-pause-work` |
|
||||
| `plan-milestone-gaps.md` | Create all phases necessary to close gaps identified by `/gsd-audit-milestone`. | `/gsd-plan-milestone-gaps` |
|
||||
| `plan-phase.md` | Create executable PLAN.md files with integrated research and verification loop. | `/gsd-plan-phase`, `/gsd-quick` |
|
||||
| `plan-review-convergence.md` | Cross-AI plan convergence loop — replan with review feedback until no HIGH concerns remain. | `/gsd-plan-review-convergence` |
|
||||
| `plant-seed.md` | Capture a forward-looking idea as a structured seed file with trigger conditions. | `/gsd-capture --seed` |
|
||||
@@ -227,7 +226,6 @@ Full roster at `get-shit-done/workflows/*.md`. Workflows are thin orchestrators
|
||||
| `reapply-patches.md` | Reapply local modifications after a GSD update. | `/gsd-update --reapply` |
|
||||
| `remove-phase.md` | Remove a future phase from the roadmap and renumber subsequent phases. | `/gsd-remove-phase` |
|
||||
| `remove-workspace.md` | Remove a GSD workspace and clean up worktrees. | `/gsd-remove-workspace` |
|
||||
| `research-phase.md` | Standalone phase research workflow (usually invoked via `plan-phase`). | `/gsd-research-phase` |
|
||||
| `resume-project.md` | Resume work — restore full context from STATE.md, HANDOFF.json, and artifacts. | `/gsd-resume-work` |
|
||||
| `review.md` | Cross-AI plan review via external CLIs; produces REVIEWS.md. | `/gsd-review` |
|
||||
| `scan.md` | Rapid single-focus codebase scan — lightweight alternative to map-codebase. | `/gsd-scan` |
|
||||
|
||||
@@ -669,7 +669,7 @@ Workstreams let you work on multiple milestone areas concurrently without state
|
||||
|
||||
Each workstream maintains its own `.planning/` directory subtree. When you switch workstreams, GSD swaps the active planning context so that `/gsd-progress`, `/gsd-discuss-phase`, `/gsd-plan-phase`, and other commands operate on that workstream's state. Active context is session-scoped when the runtime exposes a stable session identifier, which prevents one terminal or AI instance from repointing another instance's `STATE.md`.
|
||||
|
||||
This is lighter weight than `/gsd-new-workspace` (which creates separate repo worktrees). Workstreams share the same codebase and git history but isolate planning artifacts.
|
||||
This is lighter weight than `/gsd-workspace --new` (which creates separate repo worktrees). Workstreams share the same codebase and git history but isolate planning artifacts.
|
||||
|
||||
---
|
||||
|
||||
@@ -900,7 +900,6 @@ The gate is non-blocking: any internal failure logs and the phase continues.
|
||||
|
||||
```bash
|
||||
/gsd-audit-milestone # Check requirements coverage, detect stubs
|
||||
/gsd-plan-milestone-gaps # If audit found gaps, create phases to close them
|
||||
/gsd-complete-milestone # Archive, tag, done
|
||||
```
|
||||
|
||||
@@ -932,10 +931,10 @@ Work on multiple repos or features in parallel with isolated GSD state.
|
||||
|
||||
```bash
|
||||
# Create a workspace with repos from your monorepo
|
||||
/gsd-new-workspace --name feature-b --repos hr-ui,ZeymoAPI
|
||||
/gsd-workspace --new --name feature-b --repos hr-ui,ZeymoAPI
|
||||
|
||||
# Feature branch isolation — worktree of current repo with its own .planning/
|
||||
/gsd-new-workspace --name feature-b --repos .
|
||||
/gsd-workspace --new --name feature-b --repos .
|
||||
|
||||
# Then cd into the workspace and initialize GSD
|
||||
cd ~/gsd-workspaces/feature-b
|
||||
@@ -1359,7 +1358,6 @@ If the installer crashes with `EPERM: operation not permitted, scandir` on Windo
|
||||
| Lost context / new session | `/gsd-resume-work` or `/gsd-progress` |
|
||||
| Phase went wrong | `git revert` the phase commits, then re-plan |
|
||||
| Need to change scope | `/gsd-add-phase`, `/gsd-insert-phase`, or `/gsd-remove-phase` |
|
||||
| Milestone audit found gaps | `/gsd-plan-milestone-gaps` |
|
||||
| Something broke | `/gsd-debug "description"` (add `--diagnose` for analysis without fixes) |
|
||||
| STATE.md out of sync | `state validate` then `state sync` |
|
||||
| Workflow state seems corrupted | `/gsd-forensics` |
|
||||
|
||||
@@ -23,7 +23,7 @@ gates.
|
||||
## Why this exists
|
||||
|
||||
GSD has the building blocks for issue-driven AI development —
|
||||
`/gsd-new-workspace`, `/gsd-manager`, `/gsd-autonomous`, `/gsd-verify-work`,
|
||||
`/gsd-workspace --new`, `/gsd-manager`, `/gsd-autonomous`, `/gsd-verify-work`,
|
||||
`/gsd-review`, `/gsd-ship`, plus `STATE.md` and the phase artifact suite
|
||||
— but no guide that walks through how to drive them from a single tracker
|
||||
issue without writing custom orchestration scripts. Without that guide
|
||||
@@ -47,7 +47,7 @@ Symphony docs, blog posts, or third-party orchestration write-ups.
|
||||
| Symphony concept | GSD primitive |
|
||||
|---|---|
|
||||
| `WORKFLOW.md` (top-level intent) | `ROADMAP.md` (project intent), `STATE.md` (live status), phase `CONTEXT.md` (per-phase scope), phase `PLAN.md` (executable steps) |
|
||||
| One isolated agent workspace per task | `/gsd-new-workspace --strategy worktree` |
|
||||
| One isolated agent workspace per task | `/gsd-workspace --new --strategy worktree` |
|
||||
| Agent dispatch and concurrency | `/gsd-manager` (interactive dashboard), `/gsd-autonomous` (unattended) |
|
||||
| Per-phase plan and discuss steps | `/gsd-discuss-phase` → `/gsd-plan-phase` → `/gsd-execute-phase` |
|
||||
| Proof-of-work / test evidence | `/gsd-verify-work` (UAT.md persisted across `/clear`) |
|
||||
@@ -76,7 +76,7 @@ tracker issue end-to-end. Replace bracketed placeholders before running.
|
||||
`/gsd-insert-phase`. Capture the tracker issue URL in the phase's
|
||||
`CONTEXT.md` so traceability survives compaction.
|
||||
3. **Create an isolated workspace.** Run
|
||||
`/gsd-new-workspace --strategy worktree <slug>` to spin up a git
|
||||
`/gsd-workspace --new --strategy worktree <slug>` to spin up a git
|
||||
worktree with an independent `.planning/` directory. The worktree is
|
||||
the safety boundary: any exploration, partial commits, or aborted
|
||||
plans stay outside `main`.
|
||||
@@ -110,7 +110,7 @@ When the PR merges, the loop closes. Auto-close keywords in the PR body
|
||||
|
||||
The loop is safe because four invariants hold by construction:
|
||||
|
||||
- **Isolated worktrees.** Every issue runs in a `/gsd-new-workspace`
|
||||
- **Isolated worktrees.** Every issue runs in a `/gsd-workspace --new`
|
||||
worktree, so partial work, aborted plans, and exploratory commits
|
||||
never touch `main`. `gsd-local-patches/` is the recovery surface if a
|
||||
worktree's hand-edits need to come back across an update.
|
||||
|
||||
@@ -32,7 +32,7 @@
|
||||
|
||||
---
|
||||
|
||||
### `/gsd-new-workspace`
|
||||
### `/gsd-workspace --new`
|
||||
|
||||
リポジトリのコピーと独立した `.planning/` ディレクトリを持つ分離されたワークスペースを作成します。
|
||||
|
||||
@@ -52,9 +52,9 @@
|
||||
**生成物:** `WORKSPACE.md`、`.planning/`、リポジトリコピー（worktreeまたはclone）
|
||||
|
||||
```bash
|
||||
/gsd-new-workspace --name feature-b --repos hr-ui,ZeymoAPI
|
||||
/gsd-new-workspace --name feature-b --repos . --strategy worktree # 同一リポジトリの分離
|
||||
/gsd-new-workspace --name spike --repos api,web --strategy clone # フルクローン
|
||||
/gsd-workspace --new --name feature-b --repos hr-ui,ZeymoAPI
|
||||
/gsd-workspace --new --name feature-b --repos . --strategy worktree # 同一リポジトリの分離
|
||||
/gsd-workspace --new --name spike --repos api,web --strategy clone # フルクローン
|
||||
```
|
||||
|
||||
---
|
||||
@@ -412,15 +412,8 @@
|
||||
/gsd-list-phase-assumptions 2 # フェーズ2の前提を確認
|
||||
```
|
||||
|
||||
### `/gsd-plan-milestone-gaps`
|
||||
|
||||
マイルストーン監査のギャップを解消するフェーズを作成します。
|
||||
|
||||
```bash
|
||||
/gsd-plan-milestone-gaps # 各監査ギャップに対してフェーズを作成
|
||||
```
|
||||
|
||||
### `/gsd-research-phase`
|
||||
### `/gsd-plan-phase --research-phase`
|
||||
|
||||
詳細なエコシステム調査のみを実行します（単体機能 — 通常は `/gsd-plan-phase` を使用してください）。
|
||||
|
||||
@@ -429,7 +422,7 @@
|
||||
| `N` | いいえ | フェーズ番号 |
|
||||
|
||||
```bash
|
||||
/gsd-research-phase 4 # フェーズ4のドメインを調査
|
||||
/gsd-plan-phase --research-phase 4 # フェーズ4のドメインを調査
|
||||
```
|
||||
|
||||
### `/gsd-validate-phase`
|
||||
@@ -610,12 +603,12 @@ GSDの保証付きでアドホックタスクを実行します。
|
||||
/gsd-add-todo "Consider adding dark mode support"
|
||||
```
|
||||
|
||||
### `/gsd-check-todos`
|
||||
### `/gsd-capture --list`
|
||||
|
||||
保留中のTodoを一覧表示し、取り組むものを選択します。
|
||||
|
||||
```bash
|
||||
/gsd-check-todos
|
||||
/gsd-capture --list
|
||||
```
|
||||
|
||||
### `/gsd-add-tests`
|
||||
|
||||
@@ -386,7 +386,6 @@
|
||||
- REQ-MILE-08: 新しいマイルストーンは new-project と同じフロー（質問 → リサーチ → 要件 → ロードマップ）に従わなければならない
|
||||
- REQ-MILE-09: 新しいマイルストーンは既存のワークフロー設定をリセットしてはならない
|
||||
|
||||
**ギャップクローズ:** `/gsd-plan-milestone-gaps` は監査で特定されたギャップを埋めるためのフェーズを作成します。
|
||||
|
||||
---
|
||||
|
||||
@@ -763,7 +762,7 @@
|
||||
|
||||
### 29. Todo 管理
|
||||
|
||||
**コマンド:** `/gsd-add-todo [desc]`、`/gsd-check-todos`
|
||||
**コマンド:** `/gsd-add-todo [desc]`、`/gsd-capture --list`
|
||||
|
||||
**目的:** セッション中にアイデアやタスクをキャプチャし、後で作業できるようにします。
|
||||
|
||||
@@ -1516,7 +1515,7 @@ Claude が GSD ワークフローコンテキスト外でファイル編集を
|
||||
|
||||
### 65. クレーム出所タグ付け
|
||||
|
||||
**対象:** `/gsd-research-phase`
|
||||
**対象:** `/gsd-plan-phase --research-phase`
|
||||
|
||||
**目的:** リサーチのクレームにソースエビデンスのタグを付け、仮定を別途記録します。
|
||||
|
||||
|
||||
@@ -313,7 +313,7 @@ React/Next.js/Vite プロジェクトの場合、UI リサーチャーは `compo
|
||||
|
||||
各ワークストリームは独自の `.planning/` ディレクトリサブツリーを維持します。ワークストリームを切り替えると、GSD はアクティブなプランニングコンテキストを入れ替え、`/gsd-progress`、`/gsd-discuss-phase`、`/gsd-plan-phase` などのコマンドがそのワークストリームの状態に対して動作するようにします。
|
||||
|
||||
これは `/gsd-new-workspace`（別のリポジトリワークツリーを作成）より軽量です。ワークストリームは同じコードベースと git 履歴を共有しつつ、プランニングアーティファクトを分離します。
|
||||
これは `/gsd-workspace --new`（別のリポジトリワークツリーを作成）より軽量です。ワークストリームは同じコードベースと git 履歴を共有しつつ、プランニングアーティファクトを分離します。
|
||||
|
||||
---
|
||||
|
||||
@@ -417,8 +417,7 @@ GSD はマークダウンファイルを生成し、それが LLM のシステ
|
||||
| `/gsd-insert-phase [N]` | 緊急作業を挿入（小数番号） | マイルストーン中の緊急修正 |
|
||||
| `/gsd-remove-phase [N]` | 将来のフェーズを削除して番号を振り直す | 機能のスコープ縮小 |
|
||||
| `/gsd-list-phase-assumptions [N]` | Claude の意図するアプローチをプレビュー | プランニング前に方向性を確認 |
|
||||
| `/gsd-plan-milestone-gaps` | 監査ギャップに対するフェーズを作成 | 監査で不足項目が見つかった後 |
|
||||
| `/gsd-research-phase [N]` | エコシステムの深いリサーチのみ | 複雑または不慣れなドメイン |
|
||||
| `/gsd-plan-phase --research-phase [N]` | エコシステムの深いリサーチのみ | 複雑または不慣れなドメイン |
|
||||
|
||||
### ブラウンフィールドとユーティリティ
|
||||
|
||||
@@ -429,7 +428,7 @@ GSD はマークダウンファイルを生成し、それが LLM のシステ
|
||||
| `/gsd-debug [desc]` | 永続状態を持つ体系的デバッグ | 何かが壊れた時 |
|
||||
| `/gsd-forensics` | ワークフロー障害の診断レポート | 状態、アーティファクト、git 履歴が破損していると思われる場合 |
|
||||
| `/gsd-add-todo [desc]` | 後でやるアイデアを記録 | セッション中にアイデアが浮かんだ時 |
|
||||
| `/gsd-check-todos` | 保留中の TODO を一覧表示 | 記録したアイデアのレビュー |
|
||||
| `/gsd-capture --list` | 保留中の TODO を一覧表示 | 記録したアイデアのレビュー |
|
||||
| `/gsd-settings` | ワークフロートグルとモデルプロファイルを設定 | モデル変更、エージェントのトグル |
|
||||
| `/gsd-set-profile <profile>` | クイックプロファイル切り替え | コスト/品質トレードオフの変更 |
|
||||
| `/gsd-update --reapply` | アップデート後にローカル変更を復元 | ローカル編集がある場合の `/gsd-update` 後 |
|
||||
@@ -642,7 +641,6 @@ claude --dangerously-skip-permissions
|
||||
|
||||
```bash
|
||||
/gsd-audit-milestone # 要件カバレッジを確認、スタブを検出
|
||||
/gsd-plan-milestone-gaps # 監査でギャップが見つかった場合、フェーズを作成して埋める
|
||||
/gsd-complete-milestone # アーカイブ、タグ付け、完了
|
||||
```
|
||||
|
||||
@@ -672,10 +670,10 @@ claude --dangerously-skip-permissions
|
||||
|
||||
```bash
|
||||
# モノレポからリポジトリを含むワークスペースを作成
|
||||
/gsd-new-workspace --name feature-b --repos hr-ui,ZeymoAPI
|
||||
/gsd-workspace --new --name feature-b --repos hr-ui,ZeymoAPI
|
||||
|
||||
# フィーチャーブランチの分離 — 独自の .planning/ を持つ現在のリポジトリのワークツリー
|
||||
/gsd-new-workspace --name feature-b --repos .
|
||||
/gsd-workspace --new --name feature-b --repos .
|
||||
|
||||
# ワークスペースに移動して GSD を初期化
|
||||
cd ~/gsd-workspaces/feature-b
|
||||
@@ -795,7 +793,6 @@ Windows でインストーラーが `EPERM: operation not permitted, scandir`
|
||||
| コンテキストの喪失 / 新セッション | `/gsd-resume-work` または `/gsd-progress` |
|
||||
| フェーズが失敗した | フェーズのコミットを `git revert` して再プランニング |
|
||||
| スコープ変更が必要 | `/gsd-add-phase`、`/gsd-insert-phase`、または `/gsd-remove-phase` |
|
||||
| マイルストーン監査でギャップを発見 | `/gsd-plan-milestone-gaps` |
|
||||
| 何かが壊れた | `/gsd-debug "description"` |
|
||||
| ワークフロー状態が破損している可能性 | `/gsd-forensics` |
|
||||
| ターゲットを絞った修正 | `/gsd-quick` |
|
||||
|
||||
@@ -32,7 +32,7 @@
|
||||
|
||||
---
|
||||
|
||||
### `/gsd-new-workspace`
|
||||
### `/gsd-workspace --new`
|
||||
|
||||
격리된 워크스페이스를 생성합니다. 저장소 복사본과 독립적인 `.planning/` 디렉터리가 포함됩니다.
|
||||
|
||||
@@ -52,9 +52,9 @@
|
||||
**생성 파일:** `WORKSPACE.md`, `.planning/`, 저장소 복사본 (worktree 또는 clone)
|
||||
|
||||
```bash
|
||||
/gsd-new-workspace --name feature-b --repos hr-ui,ZeymoAPI
|
||||
/gsd-new-workspace --name feature-b --repos . --strategy worktree # 동일 저장소 격리
|
||||
/gsd-new-workspace --name spike --repos api,web --strategy clone # 전체 클론
|
||||
/gsd-workspace --new --name feature-b --repos hr-ui,ZeymoAPI
|
||||
/gsd-workspace --new --name feature-b --repos . --strategy worktree # 동일 저장소 격리
|
||||
/gsd-workspace --new --name spike --repos api,web --strategy clone # 전체 클론
|
||||
```
|
||||
|
||||
---
|
||||
@@ -412,15 +412,8 @@
|
||||
/gsd-list-phase-assumptions 2 # 페이즈 2 가정 사항 확인
|
||||
```
|
||||
|
||||
### `/gsd-plan-milestone-gaps`
|
||||
|
||||
마일스톤 감사에서 발견된 갭을 보완하는 페이즈를 생성합니다.
|
||||
|
||||
```bash
|
||||
/gsd-plan-milestone-gaps # 각 감사 갭에 대한 페이즈 생성
|
||||
```
|
||||
|
||||
### `/gsd-research-phase`
|
||||
### `/gsd-plan-phase --research-phase`
|
||||
|
||||
심층 에코시스템 조사만 수행합니다 (독립 실행 — 일반적으로 `/gsd-plan-phase`를 사용하세요).
|
||||
|
||||
@@ -429,7 +422,7 @@
|
||||
| `N` | 아니오 | 페이즈 번호 |
|
||||
|
||||
```bash
|
||||
/gsd-research-phase 4 # 페이즈 4 도메인 조사
|
||||
/gsd-plan-phase --research-phase 4 # 페이즈 4 도메인 조사
|
||||
```
|
||||
|
||||
### `/gsd-validate-phase`
|
||||
@@ -610,12 +603,12 @@ GSD 보증을 갖춘 임시 작업을 실행합니다.
|
||||
/gsd-add-todo "Consider adding dark mode support"
|
||||
```
|
||||
|
||||
### `/gsd-check-todos`
|
||||
### `/gsd-capture --list`
|
||||
|
||||
보류 중인 할 일 목록을 표시하고 작업할 항목을 선택합니다.
|
||||
|
||||
```bash
|
||||
/gsd-check-todos
|
||||
/gsd-capture --list
|
||||
```
|
||||
|
||||
### `/gsd-add-tests`
|
||||
|
||||
@@ -386,7 +386,6 @@
|
||||
- REQ-MILE-08: 새 마일스톤은 new-project와 동일한 흐름을 따라야 합니다(질문 → 연구 → 요구사항 → 로드맵).
|
||||
- REQ-MILE-09: 새 마일스톤은 기존 워크플로우 구성을 초기화해서는 안 됩니다.
|
||||
|
||||
**갭 해소.** `/gsd-plan-milestone-gaps`는 감사에서 식별된 갭을 해소하는 페이즈를 생성합니다.
|
||||
|
||||
---
|
||||
|
||||
@@ -763,7 +762,7 @@
|
||||
|
||||
### 29. Todo Management
|
||||
|
||||
**명령어:** `/gsd-add-todo [desc]`, `/gsd-check-todos`
|
||||
**명령어:** `/gsd-add-todo [desc]`, `/gsd-capture --list`
|
||||
|
||||
**목적:** 세션 중 나중에 처리할 아이디어와 작업을 캡처합니다.
|
||||
|
||||
@@ -1516,7 +1515,7 @@ Claude가 GSD 워크플로우 컨텍스트 밖에서 파일 편집을 시도하
|
||||
|
||||
### 65. 주장 출처 태깅
|
||||
|
||||
**대상:** `/gsd-research-phase`
|
||||
**대상:** `/gsd-plan-phase --research-phase`
|
||||
|
||||
**목적:** 연구 주장에 출처 증거를 태깅하고 가정을 별도로 기록합니다.
|
||||
|
||||
|
||||
@@ -313,7 +313,7 @@ React/Next.js/Vite 프로젝트에서 `components.json`이 없으면 UI 조사
|
||||
|
||||
각 워크스트림은 자체 `.planning/` 디렉터리 하위 트리를 유지합니다. 워크스트림을 전환하면 GSD가 활성 계획 컨텍스트를 교체하여 `/gsd-progress`, `/gsd-discuss-phase`, `/gsd-plan-phase` 및 기타 명령어가 해당 워크스트림의 상태로 동작합니다.
|
||||
|
||||
이는 `/gsd-new-workspace`(별도 저장소 worktree를 생성)보다 가볍습니다. 워크스트림은 동일한 코드베이스와 git 히스토리를 공유하지만 계획 아티팩트를 격리합니다.
|
||||
이는 `/gsd-workspace --new`(별도 저장소 worktree를 생성)보다 가볍습니다. 워크스트림은 동일한 코드베이스와 git 히스토리를 공유하지만 계획 아티팩트를 격리합니다.
|
||||
|
||||
---
|
||||
|
||||
@@ -417,8 +417,7 @@ GSD는 LLM 시스템 프롬프트가 되는 마크다운 파일을 생성합니
|
||||
| `/gsd-insert-phase [N]` | 긴급 작업 삽입 (소수점 번호 체계) | 마일스톤 중간의 긴급 수정 시 |
|
||||
| `/gsd-remove-phase [N]` | 미래 페이즈 제거 및 재번호 | 기능 범위 축소 시 |
|
||||
| `/gsd-list-phase-assumptions [N]` | Claude의 예상 접근 방식 미리 확인 | 계획 전 방향 검증 시 |
|
||||
| `/gsd-plan-milestone-gaps` | 감사 갭을 위한 페이즈 생성 | 감사에서 누락 항목이 발견된 후 |
|
||||
| `/gsd-research-phase [N]` | 심층 에코시스템 조사만 수행 | 복잡하거나 익숙하지 않은 도메인 |
|
||||
| `/gsd-plan-phase --research-phase [N]` | 심층 에코시스템 조사만 수행 | 복잡하거나 익숙하지 않은 도메인 |
|
||||
|
||||
### 브라운필드 및 유틸리티
|
||||
|
||||
@@ -429,7 +428,7 @@ GSD는 LLM 시스템 프롬프트가 되는 마크다운 파일을 생성합니
|
||||
| `/gsd-debug [desc]` | 지속적인 상태를 유지하는 체계적인 디버깅 | 문제가 발생했을 때 |
|
||||
| `/gsd-forensics` | 워크플로우 실패에 대한 진단 보고서 | 상태, 아티팩트, git 히스토리가 손상된 것 같을 때 |
|
||||
| `/gsd-add-todo [desc]` | 나중을 위한 아이디어 캡처 | 세션 중에 생각이 날 때 |
|
||||
| `/gsd-check-todos` | 보류 중인 할 일 목록 | 캡처된 아이디어 검토 시 |
|
||||
| `/gsd-capture --list` | 보류 중인 할 일 목록 | 캡처된 아이디어 검토 시 |
|
||||
| `/gsd-settings` | 워크플로우 토글 및 모델 프로필 설정 | 모델 변경, 에이전트 토글 시 |
|
||||
| `/gsd-set-profile <profile>` | 빠른 프로필 전환 | 비용/품질 트레이드오프 변경 시 |
|
||||
| `/gsd-update --reapply` | 업데이트 후 로컬 수정사항 복원 | 로컬 편집이 있는 상태에서 `/gsd-update` 이후 |
|
||||
@@ -642,7 +641,6 @@ claude --dangerously-skip-permissions
|
||||
|
||||
```bash
|
||||
/gsd-audit-milestone # Check requirements coverage, detect stubs
|
||||
/gsd-plan-milestone-gaps # If audit found gaps, create phases to close them
|
||||
/gsd-complete-milestone # Archive, tag, done
|
||||
```
|
||||
|
||||
@@ -672,10 +670,10 @@ claude --dangerously-skip-permissions
|
||||
|
||||
```bash
|
||||
# Create a workspace with repos from your monorepo
|
||||
/gsd-new-workspace --name feature-b --repos hr-ui,ZeymoAPI
|
||||
/gsd-workspace --new --name feature-b --repos hr-ui,ZeymoAPI
|
||||
|
||||
# Feature branch isolation — worktree of current repo with its own .planning/
|
||||
/gsd-new-workspace --name feature-b --repos .
|
||||
/gsd-workspace --new --name feature-b --repos .
|
||||
|
||||
# Then cd into the workspace and initialize GSD
|
||||
cd ~/gsd-workspaces/feature-b
|
||||
@@ -795,7 +793,6 @@ Windows에서 설치 프로그램이 `EPERM: operation not permitted, scandir`
|
||||
| 컨텍스트 손실 / 새 세션 | `/gsd-resume-work` 또는 `/gsd-progress` |
|
||||
| 페이즈가 잘못됨 | 페이즈 커밋에 `git revert` 후 재계획 |
|
||||
| 범위 변경 필요 | `/gsd-add-phase`, `/gsd-insert-phase`, 또는 `/gsd-remove-phase` |
|
||||
| 마일스톤 감사에서 갭 발견 | `/gsd-plan-milestone-gaps` |
|
||||
| 무언가 고장남 | `/gsd-debug "description"` |
|
||||
| 워크플로우 상태 손상 의심 | `/gsd-forensics` |
|
||||
| 빠른 목표 수정 | `/gsd-quick` |
|
||||
|
||||
@@ -39,7 +39,6 @@ Para detalhes completos de flags avançadas e mudanças recentes, consulte tamb
|
||||
| `/gsd-insert-phase [N]` | Insere trabalho urgente entre fases |
|
||||
| `/gsd-remove-phase [N]` | Remove fase futura e reenumera |
|
||||
| `/gsd-list-phase-assumptions [N]` | Mostra abordagem assumida pelo Claude |
|
||||
| `/gsd-plan-milestone-gaps` | Cria fases para fechar lacunas de auditoria |
|
||||
|
||||
## Brownfield e Utilidades
|
||||
|
||||
|
||||
@@ -251,7 +251,6 @@ claude --dangerously-skip-permissions
|
||||
|
||||
```bash
|
||||
/gsd-audit-milestone
|
||||
/gsd-plan-milestone-gaps
|
||||
/gsd-complete-milestone
|
||||
```
|
||||
|
||||
|
||||
@@ -515,7 +515,6 @@ lmn012o feat(08-02): 创建注册端点
|
||||
| `/gsd-insert-phase [N]` | 在阶段之间插入紧急工作 |
|
||||
| `/gsd-remove-phase [N]` | 删除未来阶段，重新编号 |
|
||||
| `/gsd-list-phase-assumptions [N]` | 规划前查看 Claude 的预期方法 |
|
||||
| `/gsd-plan-milestone-gaps` | 创建阶段以填补审计发现的差距 |
|
||||
| `/gsd-autonomous [--from N] [--to N] [--only N]` | 自主执行所有剩余阶段（`--to N` 执行到阶段 N 停止，`--only N` 只执行单个阶段） |
|
||||
| `/gsd-analyze-dependencies` | 检测阶段间依赖关系并建议 ROADMAP.md 的 `Depends on` 条目 |
|
||||
|
||||
@@ -533,7 +532,7 @@ lmn012o feat(08-02): 创建注册端点
|
||||
| `/gsd-settings` | 配置模型配置文件和工作流代理 |
|
||||
| `/gsd-set-profile <profile>` | 切换模型配置文件（quality/balanced/budget） |
|
||||
| `/gsd-add-todo [desc]` | 捕获想法留待后用 |
|
||||
| `/gsd-check-todos` | 列出待处理事项 |
|
||||
| `/gsd-capture --list` | 列出待处理事项 |
|
||||
| `/gsd-debug [desc] [--diagnose]` | 带持久状态的系统化调试（`--diagnose` 仅诊断不修复） |
|
||||
| `/gsd-quick [--full] [--discuss] [--research]` | 用 GSD 保证执行临时任务（`--full` 启用全部阶段，`--discuss` 先收集上下文，`--research` 规划前调查方法） |
|
||||
| `/gsd-health [--repair]` | 验证 `.planning/` 目录完整性，用 `--repair` 自动修复 |
|
||||
|
||||
@@ -209,8 +209,7 @@
|
||||
| `/gsd-insert-phase [N]` | 插入紧急工作（小数编号） | 里程碑中途紧急修复 |
|
||||
| `/gsd-remove-phase [N]` | 删除未来阶段并重新编号 | 移除某个功能 |
|
||||
| `/gsd-list-phase-assumptions [N]` | 预览 Claude 的预期方法 | 规划前，验证方向 |
|
||||
| `/gsd-plan-milestone-gaps` | 为审计缺口创建阶段 | 审计发现缺失项后 |
|
||||
| `/gsd-research-phase [N]` | 仅深度生态研究 | 复杂或不熟悉的领域 |
|
||||
| `/gsd-plan-phase --research-phase [N]` | 仅深度生态研究 | 复杂或不熟悉的领域 |
|
||||
| `/gsd-autonomous [--from N] [--to N] [--only N]` | 自主执行剩余阶段（`--to N` 到阶段 N 停止） | 批量自动处理 |
|
||||
| `/gsd-analyze-dependencies` | 检测阶段间依赖关系 | `/gsd-manager` 前分析 |
|
||||
|
||||
@@ -231,7 +230,7 @@
|
||||
| `/gsd-quick` | 带 GSD 保证的临时任务 | Bug 修复、小功能、配置更改 |
|
||||
| `/gsd-debug [desc] [--diagnose]` | 带持久状态的系统化调试（`--diagnose` 仅诊断） | 出问题时 |
|
||||
| `/gsd-add-todo [desc]` | 捕获想法留待后用 | 会话期间想到什么 |
|
||||
| `/gsd-check-todos` | 列出待处理事项 | 查看捕获的想法 |
|
||||
| `/gsd-capture --list` | 列出待处理事项 | 查看捕获的想法 |
|
||||
| `/gsd-settings` | 配置工作流开关和模型配置 | 更改模型、切换代理 |
|
||||
| `/gsd-set-profile <profile>` | 快速切换配置 | 更改成本/质量权衡 |
|
||||
| `/gsd-update --reapply` | 更新后恢复本地修改 | 如果你有本地编辑，在 `/gsd-update` 后 |
|
||||
@@ -390,7 +389,6 @@ claude --dangerously-skip-permissions
|
||||
|
||||
```bash
|
||||
/gsd-audit-milestone # 检查需求覆盖率，检测存根
|
||||
/gsd-plan-milestone-gaps # 如果审计发现缺口，创建阶段来填补
|
||||
/gsd-complete-milestone # 归档，标记，完成
|
||||
```
|
||||
|
||||
@@ -481,7 +479,6 @@ node gsd-tools.cjs state sync # 从磁盘重建 STATE.md
|
||||
| 丢失上下文 / 新会话 | `/gsd-resume-work` 或 `/gsd-progress` |
|
||||
| 阶段出错 | `git revert` 阶段提交，然后重新规划 |
|
||||
| 需要更改范围 | `/gsd-add-phase`、`/gsd-insert-phase` 或 `/gsd-remove-phase` |
|
||||
| 里程碑审计发现缺口 | `/gsd-plan-milestone-gaps` |
|
||||
| 出问题了 | `/gsd-debug "描述"` |
|
||||
| STATE.md 不同步 | `state validate` 然后 `state sync` |
|
||||
| 快速针对性修复 | `/gsd-quick` |
|
||||
|
||||
@@ -99,7 +99,7 @@
|
||||
|
||||
**也可选：**
|
||||
- `/gsd-discuss-phase 2` — 先收集上下文
|
||||
- `/gsd-research-phase 2` — 调查未知项
|
||||
- `/gsd-plan-phase --research-phase 2` — 调查未知项
|
||||
- 审查路线图
|
||||
|
||||
---
|
||||
@@ -128,7 +128,7 @@
|
||||
|
||||
**也可选：**
|
||||
- `/gsd-discuss-phase 3` — 先收集上下文
|
||||
- `/gsd-research-phase 3` — 调查未知项
|
||||
- `/gsd-plan-phase --research-phase 3` — 调查未知项
|
||||
- 回顾阶段 2 构建的内容
|
||||
|
||||
---
|
||||
@@ -149,7 +149,7 @@
|
||||
|
||||
**先讨论上下文：** `/gsd-discuss-phase 3`
|
||||
|
||||
**研究未知项：** `/gsd-research-phase 3`
|
||||
**研究未知项：** `/gsd-plan-phase --research-phase 3`
|
||||
|
||||
<sub>`/clear` 优先 → 全新上下文窗口</sub>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user