gsd-new-workspace

To set up an isolated git workspace, you need to generate a workspace manifest, select target repositories, provision worktrees or clones, assign branches, and pass validation gates for safe handoff. This creates separated state and workspace boundaries for parallel sessions.

The best way to isolate feature branches across multiple git repositories is to create a dedicated workspace directory with its own independent planning state, using worktrees or clones to detach branch-specific environments from your main local setup and prevent state collisions.

You need a separate workspace directory with independent planning state when running parallel GSD sessions that require multi-repo orchestration. It prevents shared planning file conflicts and keeps execution scoped strictly to one isolated workspace boundary.

Workspace provisioning uses both git worktrees and clones for repo isolation. The choice depends on how much separation you need: worktrees share underlying object databases for lightweight branching, while clones create entirely separate repository copies for complete detachment.

Yes, you can coordinate changes across several repos while keeping planning scoped to one workspace. The workspace creation process builds a dedicated directory with its own manifest, ensuring multi-repo orchestration remains isolated without affecting your main local setup.