gsd-new-workspace · git:20260914.e75f220 · 2026-09-14 · sha256 49cf453dfb58ec4f
gsd-new-workspace git:20260914.e75f220A
Immutable. This exact content is served forever at /api/v1/blob/49cf453dfb58ec4f.
--- name: gsd-new-workspace description: "Use when you need an isolated copy of one or more repos with its own .planning/, or want to work on several repos in parallel. Creates worktrees or clones plus WORKSPACE.md; then run /gsd-new-project inside." argument-hint: "--name <name> [--repos repo1,repo2] [--path /target] [--strategy worktree|clone] [--branch name] [--auto]" allowed-tools: - Read - Bash - Write - AskUserQuestion --- <context> **Flags:** - `--name` (required) — Workspace name - `--repos` — Comma-separated repo paths or names. If omitted, interactive selection from child git repos in cwd - `--path` — Target directory. Defaults to `~/gsd-workspaces/<name>` - `--strategy` — `worktree` (default, lightweight) or `clone` (fully independent) - `--branch` — Branch to checkout. Defaults to `workspace/<name>` - `--auto` — Skip interactive questions, use defaults </context> <objective> Create a physical workspace directory containing copies of specified git repos (as worktrees or clones) with an independent `.planning/` directory for isolated GSD sessions. **Use cases:** - Multi-repo orchestration: work on a subset of repos in parallel with isolated GSD state - Feature branch isolation: create a worktree of the current repo with its own `.planning/` **Creates:** - `<path>/WORKSPACE.md` — workspace manifest - `<path>/.planning/` — independent planning directory - `<path>/<repo>/` — git worktree or clone for each specified repo **After this command:** `cd` into the workspace and run `/gsd-new-project` to initialize GSD. </objective> <execution_context> @$HOME/.claude/get-shit-done/workflows/new-workspace.md @$HOME/.claude/get-shit-done/references/ui-brand.md </execution_context> <process> Execute the new-workspace workflow from @$HOME/.claude/get-shit-done/workflows/new-workspace.md end-to-end. Preserve all workflow gates (validation, approvals, commits, routing). </process>