swarmspace

Use when a task spans multiple repos or can be split into N independent scopes that an agent could chase in parallel — diagnosing a cross-service bug, locating a code path across several services, auditing who still uses a deprecated API, running a coordinated refactor or migration across a workspace, or any question that starts with "across these repos…". Triggers on phrases like "across all our services", "which repo emits…", "find where X happens in any of…", "refactor Y everywhere", "who still uses…", "parallel investigation", "swarm". This skill teaches the orchestrator (you) how to launch `ws investigate` (read-only evidence-gathering) or `ws swarm` (executor peers) with the right pre-launch contract, peer count, backend CLI, and post-run synthesis — instead of sequentially grepping repos one at a time or spawning a single Task agent for work that is embarrassingly parallel.

Use when the user is working with a multi-repo **workspace directory** (a parent dir holding several cloned repos side by side) and wants routine multi-repo git or shell operations — cloning a set of repos together, pulling them all, checking branch/dirty/ahead-behind status across everything, running the same command in all or some of them, or doing an advisory pre-action check before touching shared branches. Triggers on phrases like "clone these N repos", "pull all my repos", "status across all the services", "run X in every repo", "run this in just auth and billing", "which repos are dirty", "check before I push". This skill teaches the orchestrator (you) the `ws workspace|status|preflight|pull-all|each|some` commands, their quoting rules, and the safety boundaries between read-only polling and fan-out execution. Use this skill for routine multi-repo ops; for parallel *investigation* or coordinated *refactors*, hand off to `orchestrating-swarms`.