gsd-new-workspace

Create an isolated GSD workspace with copied git repos and independent .planning/ state.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-new-workspace-artriv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-new-workspace
Source: https://github.com/ArtRiv/game-topicos-especiais/tree/main/.github/skills/gsd-new-workspace
Command: npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-new-workspace-artriv

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of mixing GSD planning state across multiple repos or iterations by creating an isolated physical workspace with its own independent .planning/ directory.

Core Features & Use Cases

  • Isolated multi-repo orchestration: Create a dedicated workspace directory that contains specified git repos, so parallel GSD sessions don’t collide on planning state.
  • Branch/worktree isolation: Generate a separate workspace that checks out the desired branch (defaulting to workspace/<name>) to keep feature work independent.
  • Configurable copy strategy: Use worktree for lightweight isolation or clone for fully independent repo copies, and optionally run without interactive prompts via --auto.

Quick Start

Create an isolated workspace named "acme-q2" for repos "repo-a,repo-b" at the default target path and proceed with GSD initialization in that workspace.

Frequently Asked Questions about gsd-new-workspace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I isolate planning state when working across multiple git repositories?

You isolate planning state by creating a dedicated GSD workspace directory containing copies of specified git repos alongside an independent .planning/ directory, preventing parallel sessions from colliding on shared state.

What is the best way to set up an isolated workspace for parallel feature development?

The best way to set up an isolated workspace for parallel feature development is to generate a dedicated directory that checks out the desired branch (defaulting to workspace/<name>), keeping independent feature work separate.

Does this workspace setup support git worktree or do I need to clone repos?

This workspace setup supports both git worktree for lightweight branch isolation and clone for fully independent repo copies, giving you flexible options for multi-repo orchestration.

How do I automate multi-repo workspace creation without interactive prompts?

You can automate multi-repo workspace creation without interactive prompts by using the --auto flag, which runs the new-workspace workflow end-to-end while satisfying required command-line flags and preserving workflow gates.

Can I specify a custom target path and branch when orchestrating repo copies?

Yes, you can specify an optional target path and branch selection when orchestrating repo copies, allowing the workspace to check out the desired branch (defaulting to workspace/<name>) at your chosen location.

Why should I use a separate workspace directory instead of working directly in my repos?

You should use a separate workspace directory to prevent mixing GSD planning state across multiple repos or iterations, ensuring parallel feature development maintains independent .planning/ states without collision.