GS

gsd-new-workspace

Initializes a separate, isolated workspace for project tasks.

Install

mkdir -p .claude/skills/gsd-new-workspace && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12898" && unzip -o skill.zip -d .claude/skills/gsd-new-workspace && rm skill.zip

Installs to .claude/skills/gsd-new-workspace

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Create an isolated workspace with repo copies and independent .planning/
72 charsno explicit “when” trigger
Beginner

Key capabilities

  • Create an isolated workspace directory
  • Copy specified git repositories
  • Create an independent `.planning/` directory
  • Support multi-repo orchestration
  • Support feature branch isolation

How it works

This skill creates a new directory, populates it with copies of specified git repositories either as worktrees or clones, and sets up an independent `.planning/` directory for isolated GSD sessions.

Inputs & outputs

You give it
Workspace name, optional repo paths, target path, strategy, branch, and auto-skip flag
You get back
A new workspace directory with repo copies, a `WORKSPACE.md` manifest, and an independent `.planning/` directory

When to use gsd-new-workspace

  • Creating isolated dev workspaces
  • Setting up sandboxes
  • Initializing new project instances

About this skill

<codex_skill_adapter>

A. Skill Invocation

  • This skill is invoked by mentioning $gsd-new-workspace.
  • Treat all user text after $gsd-new-workspace as {{GSD_ARGS}}.
  • If no arguments are present, treat {{GSD_ARGS}} as empty.

B. AskUserQuestion → request_user_input Mapping

GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:

Parameter mapping:

  • headerheader
  • questionquestion
  • Options formatted as "Label" — description{label: "Label", description: "description"}
  • Generate id from header: lowercase, replace spaces with underscores

Batched calls:

  • AskUserQuestion([q1, q2]) → single request_user_input with multiple entries in questions[]

Multi-select workaround:

  • Codex has no multiSelect. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.

Execute mode fallback:

  • When request_user_input is rejected (Execute mode), present a plain-text numbered list and pick a reasonable default.

C. Task() → spawn_agent Mapping

GSD workflows use Task(...) (Claude Code syntax). Translate to Codex collaboration tools:

Direct mapping:

  • Task(subagent_type="X", prompt="Y")spawn_agent(agent_type="X", message="Y")
  • Task(model="...") → omit (Codex uses per-role config, not inline model selection)
  • fork_context: false by default — GSD agents load their own context via <files_to_read> blocks

Parallel fan-out:

  • Spawn multiple agents → collect agent IDs → wait(ids) for all to complete

Result parsing:

  • Look for structured markers in agent output: CHECKPOINT, PLAN COMPLETE, SUMMARY, etc.
  • close_agent(id) after collecting results from each agent </codex_skill_adapter>
<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> @/Users/Code/EchoLearn/.codex/get-shit-done/workflows/new-workspace.md @/Users/Code/EchoLearn/.codex/get-shit-done/references/ui-brand.md </execution_context>

<process> Execute the new-workspace workflow from @/Users/Code/EchoLearn/.codex/get-shit-done/workflows/new-workspace.md end-to-end. Preserve all workflow gates (validation, approvals, commits, routing). </process>

When not to use it

  • When the user wants to work directly in the existing repository
  • When the user does not need an isolated GSD session
  • When the user wants to modify the current `.planning/` directory

Limitations

  • The `--name` flag is required
  • The skill creates copies of repositories, not symlinks
  • After creation, the user must `cd` into the workspace and run `$gsd-new-project` to initialize GSD

How it compares

This skill automates the creation of a fully isolated development environment with its own GSD state, unlike manual setup which requires separate repository cloning and configuration.

Compared to similar skills

gsd-new-workspace side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
gsd-new-workspace (this skill)04moNo flagsBeginner
setup121moNo flagsBeginner
tmux202moReviewIntermediate
macos-cleaner162moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry