gsd-new-workspace

Create isolated multi-repo workspaces with git worktrees or clones and .planning/ directories.

1|Updated Aug 17, 2025
One-click install
npx skills add https://github.com/DuySeu/StockMind --skill gsd-new-workspace-duyseu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-new-workspace
Source: https://github.com/DuySeu/StockMind/tree/main/.agent/skills/gsd-new-workspace
Command: npx skills add https://github.com/DuySeu/StockMind --skill gsd-new-workspace-duyseu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of isolated multi-repo development workspaces with independent planning directories.

Core Features & Use Cases

  • Create a workspace directory containing copies of specified repos as either git worktrees or clones.
  • Provide an isolated .planning/ directory per workspace for GSD sessions.
  • Configure workspace name, target path, repos, and branch via CLI flags for repeatable setups.

Quick Start

Create a new workspace by providing a name and one or more repos, then open the created directory to proceed with GSD setup.

Frequently Asked Questions about gsd-new-workspace

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

FAQPage Schema
How do I create isolated multi-repo workspaces for parallel development?

Multi-repo isolated workspaces are generated by providing a workspace name and target repositories via CLI flags. This creates a dedicated directory containing copies of the specified repos alongside an isolated .planning/ directory.

What is the difference between using git worktrees and clones for workspace management?

Git worktrees and clones are optional strategies for workspace management. Worktrees link multiple working directories to a single repository for lightweight branching, while clones create entirely separate repository copies for fully isolated experimentation.

Can I configure a specific branch when setting up a multi-repo workspace?

Yes, you can configure a specific branch when setting up a multi-repo workspace. The process accepts CLI flags to define the target branch and repository path, ensuring reproducible setups across your repositories.

Do I need an isolated planning directory for each new development workspace?

You get an isolated .planning/ directory automatically per workspace. This ensures independent planning sessions for teams managing multiple git repositories, keeping project planning separate from the main repository structure.

How do I automate workspace manifests for reproducible experimentation environments?

Automating workspace manifests involves configuring workspace name, target path, repos, and branch via CLI flags for repeatable setups. This generates isolated development environments designed for parallel work and reproducible experimentation.