skills.rest
thecomputer07
thecomputer07COMMUNITY
Explore all skills by this author →
GitHub

qsd-new-workspace

Create isolated workspaces with .planning directories and per-repo worktrees or clones.

Updated Apr 13, 2026
Search Tags:#automation#git#planning#devops#worktree#workspace#clone
One-click install
npx skills add https://github.com/thecomputer07/qsd --skill qsd-new-workspace
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qsd-new-workspace
Source: https://github.com/thecomputer07/qsd/tree/main/skills/qsd-new-workspace
Command: npx skills add https://github.com/thecomputer07/qsd --skill qsd-new-workspace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create isolated, reproducible workspaces for multi-repo development by provisioning independent .planning directories and per-repo copies (worktrees or clones).

Core Features & Use Cases

  • Multi-repo orchestration: work on a subset of repos in parallel with isolated qsd state
  • Feature-branch isolation: create a dedicated workspace for a feature branch with its own planning context
  • Independent planning: each workspace maintains its own .planning directory and manifest

Quick Start

Run /qsd-new-workspace --name <name> [--repos repo1,repo2] [--path /target] to create the workspace and then cd into it

Frequently Asked Questions about qsd-new-workspace

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

FAQPage Schema
How do I set up isolated git workspaces for multi-repo development?▼

You can create isolated git workspaces for multi-repo development by running a single command with a specified name and target repositories. The process provisions an independent .planning directory alongside per-repo worktree or clone copies.

What is the difference between git worktrees and clones in a parallel development workspace?▼

Git worktrees allow you to check out multiple branches of the same repository simultaneously without duplicating the entire commit history, whereas clones create entirely separate repository copies for isolated development.

Can I maintain independent planning contexts for each feature branch?▼

Yes, you can maintain independent planning contexts for each feature branch. Each generated workspace maintains its own dedicated .planning directory and manifest to isolate project state from other branches.

Does this workspace automation tool require any prior dependencies to run?▼

No prior dependencies are required to run this workspace automation tool. It operates independently to provision workspaces, requiring only the target repositories and a specified workspace name to execute the setup.

When should I use a dedicated workspace for multi-repo orchestration?▼

You should use a dedicated workspace for multi-repo orchestration when you need to work on a subset of repositories in parallel. This approach isolates your qsd state and planning context from your main working directory.

Related Skills

Explore More Software Engineering Skills→
ewtwdewtwd

github-skills-publisher

Publish the local workspace skills directory to a GitHub repository.

Community
Advanced
TruCol270TruCol270
1

gsd-new-workspace

Create isolated git workspaces with worktrees or clones and a .planning/ directory.

Community
Advanced
adaptive-enforcement-labadaptive-enforcement-lab
3

hub-and-spoke

Coordinate a central hub to spawn and manage parallel spokes.

Official
Advanced
TheFJKTheFJK
2

using-git-worktrees

Create and manage isolated git worktrees for feature branches.

Community
Advanced