workspace

Coordinate multi-repo campaigns with wave-based execution and cross-repo discovery.

820|78|Updated Mar 20, 2026

Search Tags:#automation #workflow #discovery #orchestration #multi-repo #campaign #cross-repo

Ready to run

npx skills add https://github.com/SethGammon/Citadel --skill workspace-sethgammon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workspace
Source: https://github.com/SethGammon/Citadel/tree/main/skills/workspace
Command: npx skills add https://github.com/SethGammon/Citadel --skill workspace-sethgammon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates cross-repo orchestration, enabling teams to plan, coordinate, and execute campaigns that span multiple repositories without losing context between steps.

Core Features & Use Cases

Cross-repo campaign planning and wave-based execution across backend, frontend, and infra repos
Discovery relay and momentum context propagation between campaigns
Per-repo agent campaigns that run in isolated working trees with deterministic branching

Quick Start

Describe your cross-repo objective to Citadel and initiate a workspace campaign to synchronize work across repos.

Frequently Asked Questions about workspace

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

FAQPage Schema

How do I coordinate cross-repo campaigns across multiple repositories?▼

Cross-repo campaigns are coordinated by orchestrating wave-based execution across repositories, persisting context and applying cross-repo discovery to synchronize work across backend, frontend, and infra repositories.

What is the best way to automate multi-repo workflows for shared infrastructure?▼

Automating multi-repo workflows involves initiating a workspace campaign to plan, coordinate, and execute large-scale tasks like introducing shared infrastructure without losing context between automated steps.

How does wave-based execution work for cross-repo tasks?▼

Wave-based execution works by running per-repo agent campaigns in isolated working trees with deterministic branching, propagating momentum context and discovery relays between each campaign wave.

Can I synchronize API contracts across backend and frontend repos without losing context?▼

Yes, you can synchronize API contracts across repositories by using planning sessions and cross-repo contracts to maintain momentum context, ensuring coordinated feature toggles and infrastructure changes stay aligned.

Do I need isolated worktrees for deterministic multi-repo orchestration?▼

Isolated worktrees are required for deterministic multi-repo orchestration, allowing per-repo agent campaigns to execute with deterministic branching and prevent conflicts across coordinated repository changes.