gsd-workspace

To create an isolated workspace, use the new-workspace mode to build a new directory with repo copies and an independent .planning/ setup using a worktree or clone strategy. This keeps planning state from cross-contaminating between experiments.

Managing multiple git worktree environments is best handled by using dedicated create and remove modes. The remove-workspace mode confirms intent and deletes the workspace directory and related worktrees entirely, ensuring your machine stays tidy without leaving junk behind.

To list active workspaces, use the list-workspaces mode to scan your local workspace root at ~/gsd-workspaces/. This provides a status summary for quick review of all currently active isolated environments.

Yes, you can run independent planning state for the same repo across different workspaces. The workspace creation process sets up an isolated .planning/ directory for each environment, allowing separate experiments without cross-contaminating your project state.

You need to use a clone strategy instead of a standard git worktree when your workflow requires an independent .planning state directory. This strategy builds a new workspace with repo copies specifically to isolate planning data for separate experiments.

No, gsd-workspace does not require any external dependencies to manage environments. It handles workspace management, environment isolation, and worktree strategies natively through its flag-driven mode routing for creating, listing, and removing directories.