gsd-new-workspace

Create isolated git workspaces with worktrees or clones and a .planning/ directory.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/TruCol270/salty-pickle --skill gsd-new-workspace-trucol270
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-new-workspace
Source: https://github.com/TruCol270/salty-pickle/tree/main/.claude-skills/gsd-new-workspace
Command: npx skills add https://github.com/TruCol270/salty-pickle --skill gsd-new-workspace-trucol270

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing multiple git repositories for feature work or experiments creates context bleed and scattered planning state. This Skill creates isolated workspaces by copying specified repos as either worktrees or independent clones and provides a separate .planning/ directory for GSD sessions.

Core Features & Use Cases

  • Create a new workspace with copies of selected repos as worktrees or independent clones.
  • Provide an isolated .planning/ directory to hold GSD session data and manifests.
  • Supports interactive repo selection when --repos is omitted; enables per-workspace isolation for parallel work.
  • After setup, users can cd into the workspace and start a new GSD project.

Quick Start

Call gsd-new-workspace with a name and optional repos to create a new isolated workspace ready for GSD sessions.

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 an isolated git workspace for multiple repositories?

Create an isolated git workspace by specifying a workspace name, target path, and repo list to clone or generate worktrees. This produces a ready-to-use directory structure with an independent workspace manifest for parallel multi-repo development.

What is the difference between using git worktrees and cloning repos for feature branching?

Git worktrees link a new workspace to an existing local repository, sharing commit history, while cloning creates a completely independent copy. Choosing between these strategies depends on whether you need shared history or full branch isolation for your experiments.

Why do I need a dedicated .planning directory in a multi-repo workspace?

A dedicated .planning directory prevents context bleed by holding isolated session data and manifests. It ensures that planning state remains separate for each parallel experiment or feature branch within your multi-repo development workflow.

How do I set up a new workspace for parallel multi-repo experiments?

Set up a workspace by defining a name, target path, strategy (worktree or clone), and branch naming convention. You can also enable auto mode to quickly generate the independent directory structure needed for parallel experiments.

Can I automate workspace creation without specifying every repository manually?

Yes, you can omit the repo list to trigger interactive repo selection. The workspace setup will prompt you to choose specific repositories, allowing per-workspace isolation for parallel feature work without manually specifying every repo upfront.