gsd-workspace

Create, list, and remove isolated GSD workspace environments with repo copies.

1|Updated Sep 6, 2015

Search Tags:#automation #worktrees #cleanup #workspace management #workflow routing #gsd #repo setup

Ready to run

npx skills add https://github.com/deerawan/dotfiles --skill gsd-workspace-deerawan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-workspace
Source: https://github.com/deerawan/dotfiles/tree/main/claude/skills/gsd-workspace
Command: npx skills add https://github.com/deerawan/dotfiles --skill gsd-workspace-deerawan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Creating, tracking, and deleting isolated GSD workspace environments can become tedious and error-prone when you need reproducible repo copies and clean state for planning workflows.

Core Features & Use Cases

Create isolated workspaces: Provision a new workspace with repo copies and an independent .planning workflow so runs don’t interfere.
List active workspaces: Scan your workspace directory (~/gsd-workspaces/) and summarize each workspace’s status.
Remove workspaces safely: Confirm and remove a workspace directory while cleaning up worktrees to avoid leftover state.
Use Case: When you need to test different planning strategies across multiple repo variants, create a separate workspace for each experiment, list them to monitor status, then remove them when finished.

Quick Start

Create a new isolated workspace by running: gsd-workspace --new <workspace-name>

Frequently Asked Questions about gsd-workspace

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

FAQPage Schema

How do I create isolated workspaces for testing different repo variants?▼

Isolated workspaces are created using the --new command flag, which provisions a fresh directory with repo copies and an independent .planning workflow state to prevent interference between concurrent experiments.

What is the best way to manage and track active worktrees?▼

Managing active worktrees is done by listing workspace statuses from the ~/gsd-workspaces/ directory. This scans and summarizes each workspace's current state to provide visibility into active workflow automation environments.

How do I safely remove a workspace directory and clean up worktrees?▼

Safely remove a workspace directory by running the command with the --remove flag. This initiates a confirmation step and cleans up associated worktrees to prevent leftover state in your repo setup.

Do I need any dependencies to automate my GSD workspace setup?▼

No dependencies are required to automate GSD workspace setup. The Skill operates independently to route commands based on flags like --new, --list, and --remove for end-to-end workflow execution.

When do I need isolated repo copies for planning workflows?▼

Isolated repo copies are needed when testing different planning strategies across multiple variants. They ensure reproducible workspace setups and maintain clean state so workflow runs do not interfere with each other.