gsd:new-workspace
Create an isolated workspace with repo copies and independent .planning/
Profile →npx skills add davepoon/buildwithclaude --skill new-workspace --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
<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> @${CLAUDE_PLUGIN_ROOT}/workflows/new-workspace.md @${CL
What does the gsd:new-workspace skill do?
Create an isolated workspace with repo copies and independent .planning/
How do I install it?
Run `npx skills add davepoon/buildwithclaude --skill new-workspace --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From davepoon/buildwithclaude, a repository with 3,251 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.