gsd-new-workspace

To create isolated multi-repo workspaces, you provide a workspace name and optional repositories to spin up an environment containing copies of repos as git worktrees or clones, each with independent state to prevent cross-repo interference during parallel development.

Managing independent planning data across multiple git repositories requires a dedicated .planning directory within each isolated workspace, ensuring workspace-specific state and planning decisions are kept separate from other parallel development efforts.

For multi-repo orchestration, git worktrees and clones serve as selectable strategies to replicate repositories within a workspace. Both provide independent state, but the chosen strategy dictates how the isolated workspace is structured and entered.

Yes, you can document included repositories and configuration when spinning up a new workspace. The process automatically generates a WORKSPACE.md manifest detailing the workspace configuration and repos for future reference.

No external dependencies are required to set up multi-repo git worktree environments. You simply provide a workspace name and optional repos, then run the workflow to initialize the isolated workspace with its dedicated .planning directory.

You should use isolated workspaces for multi-repo orchestration when teams need parallel development across repositories safely. This approach prevents cross-repo interference by maintaining workspace-specific state and independent planning areas for experimentation.