gsd-new-workspace

Create isolated git workspaces with per-repo worktrees and a WORKSPACE.md manifest.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-new-workspace-dobrinz123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-new-workspace
Source: https://github.com/dobrinz123/claude-skills-share/tree/main/skills/gsd-new-workspace
Command: npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-new-workspace-dobrinz123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create isolated workspaces that contain copies of selected git repositories and an independent .planning directory so parallel Get Shit Done (GSD) sessions do not interfere with each other and workspace-specific planning state remains local.

Core Features & Use Cases

  • Workspace creation: Assemble a physical workspace directory with per-repo worktrees or full clones and a dedicated .planning/ directory for isolated project state.
  • Manifesting & branching: Generate a WORKSPACE.md manifest, create or checkout a workspace-specific branch, and support both lightweight worktrees and fully independent clones.
  • Use Case: Orchestrate multi-repo feature development across several services while keeping planning artifacts, approvals, and commits scoped to the workspace.

Quick Start

Create a workspace named backend-feature for repos api,web using the worktree strategy at ~/gsd-workspaces/backend-feature.

Frequently Asked Questions about gsd-new-workspace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create isolated multi-repo workspaces for parallel feature development?

To create isolated multi-repo workspaces, assemble a directory with per-repo git worktrees or clones alongside a dedicated .planning directory so parallel sessions remain independent. A WORKSPACE.md manifest coordinates the repositories and preserves workflow validation gates.

What is the difference between git worktrees and full clones for workspace isolation?

Git worktrees provide lightweight branch isolation sharing a single repository, while full clones create completely independent repository copies. Both strategies produce a workspace with a .planning directory and a WORKSPACE.md manifest to coordinate multi-repo development.

How do I set up a workspace manifest for multiple git repositories?

Setting up a workspace manifest generates a WORKSPACE.md file that coordinates selected git repositories within an isolated directory. This manifest supports branch selection, tracks per-repo worktrees or clones, and maintains workflow validation gates for the workspace.

Can I automate workspace creation non-interactively for multi-repo feature branches?

Yes, workspace creation supports non-interactive automation for multi-repo feature branches. You can specify the workspace name, target repositories, and worktree or clone strategy programmatically, allowing branch selection and manifest generation to run without manual input.

Why do I need a separate .planning directory for each workspace?

A separate .planning directory keeps planning artifacts, approvals, and commits scoped to the specific workspace so parallel development sessions do not interfere with each other. This isolation preserves independent project state across multiple repositories.

When should I avoid using git worktrees for multi-repo workspace isolation?

Avoid git worktrees when repositories require fully independent states that cannot share underlying git objects, or when workflow validation gates demand complete repository separation. In these cases, full clones provide the necessary isolation for multi-repo feature development.