Individual skill
workspace
Multi-repo campaign coordinator. Same lifecycle as fleet -- scope claims, discovery relay, wave-based execution -- but the unit of work is a repo, not a file. Coordinates campaigns across repositories with shared context.
skills/workspace/SKILL.md
Source commit e1a3d45697a0f323aaedcbea0ab6a0387b5fe722
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 927
- Repository last updated
- Nov 5, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-orchestration Repository topic
- agent-workflow Repository topic
- ai-agents Repository topic
- claude-code-plugin Repository topic
- claude-plugins Repository topic
- codex-plugin Repository topic
- developer-tools Repository topic
- mcp Repository topic
- marketing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 7,509 bytesSKILL.mdcore · 7,509 bytesSKILL.mdcore · 7,509 bytesSKILL.mdcore · 7,509 bytesSKILL.mdcore · 7,509 bytesSKILL.mdcore · 7,509 bytes__benchmarks__/multi-repo-direction.mddoc · 1,102 bytes__benchmarks__/no-repos-configured.mddoc · 739 bytes
Read excerpt
# /workspace -- Multi-Repo Campaign Coordinator
## When to Use
- Adding infrastructure that spans repos (new database, shared service, API contract)
- Coordinating changes across a frontend repo, backend repo, and infra repo
- Breaking a monolith into services (each service becomes a repo-scoped campaign)
- Any task where changes in repo A depend on or inform changes in repo B
**Do not use when:**
- All work is in one repo (use `/fleet` or `/archon`)
- The repos are truly independent with no shared contracts (just run separate campaigns)
## Protocol