gsd-new-workspace

Yes, you can manage parallel work across multiple repositories by creating an isolated workspace. It sets up a worktree or clone for each repo with its own planning context, enabling you to work on a subset of repos concurrently without interfering with other project states.

The best way to isolate planning data for concurrent feature branches is to generate a workspace with an independent .planning directory. This ensures that each project subset maintains its own isolated GSD state, keeping planning sessions separate across your repositories.

You can set up a new workspace by running the command with flags like --repos to specify your Git repositories and --branch to define the target branch. Additional flags like --path and --strategy allow you to customize the clone or reference behavior for your project.

Yes, multi-repo workspace automation supports generating a manifest file. When you create the workspace, it automatically generates a WORKSPACE.md manifest alongside the per-repo work areas, documenting the configuration and structure of your isolated development environment.

You should not use an isolated workspace for repo management if your task involves working on a single repository or does not require isolated planning sessions. It is specifically designed for multi-repo orchestration and parallel work where independent GSD state and separate planning data are necessary.