skills.rest
mferris77
mferris77COMMUNITY
Explore all skills by this author →
GitHub

workspace

Coordinate multi-repository campaigns with wave-based execution and cross-repo contract verification.

Updated Aug 27, 2026
Search Tags:#git#workflow#integration#coordination#multi-repo#campaign#cross-repo
One-click install
npx skills add https://github.com/mferris77/SpringBoard --skill workspace-mferris77
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workspace
Source: https://github.com/mferris77/SpringBoard/tree/main/vscode-citadel-harness/skills/workspace
Command: npx skills add https://github.com/mferris77/SpringBoard --skill workspace-mferris77

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates and synchronizes cross-repository development campaigns so that dependent changes, shared contracts, and multi-repo infrastructure rollouts are planned, executed, and verified in waves rather than ad-hoc per-repo edits.

Core Features & Use Cases

  • Repo-scoped Campaigns: Decomposes a high-level direction into repo-specific campaigns with scoped branches and per-repo agents.
  • Wave-based Execution: Groups repo-campaigns into waves respecting dependencies and runs them in controlled sequences.
  • Cross-repo Contracts & Verification: Specifies producer/consumer contracts, verifies outputs (types, routes, files), and halts consumers on contract failures.
  • Session-based State: Persists workspace sessions under .planning/workspace/session-{slug}.md to resume, track waves, and record discovery relays.
  • Use Case: Coordinating a shared cache and API contract across backend, frontend, and infra repositories with staged rollout and verification.

Quick Start

Run the workspace skill with a direction like "Coordinate a campaign to add a Redis cache and update frontend clients across backend, frontend, and infra repos" to create per-repo branches, spawn repo agents, and execute wave 1.

Frequently Asked Questions about workspace

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

FAQPage Schema
How do I coordinate dependent changes across multiple git repositories?▼

To coordinate multi-repo changes, this Skill decomposes high-level directions into repo-specific campaigns with scoped branches and per-repo agents. It synchronizes dependent updates by grouping repositories into execution waves that respect cross-repo dependencies.

What is the best way to synchronize cross-repo API and type contract updates?▼

Synchronizing cross-repo API contracts requires specifying producer and consumer relationships, verifying outputs like types and routes, and halting consumers on contract failures. This Skill automates contract verification across local git-accessible repositories during staged rollouts.

How do I manage a multi-repo rollout for breaking a monolith into services?▼

Managing multi-repo rollouts for decomposing monoliths uses wave-based execution to run campaigns in controlled sequences. The Skill creates isolated per-repo branches, executes dependent changes in order, and runs per-repo build and type checks to verify each wave.

Do I need local git-accessible repositories to coordinate cross-repo campaigns?▼

Yes, coordinating cross-repo campaigns requires local git-accessible repositories. The workflow depends on per-repo branching, isolated build and type checks, and session files stored under .planning/workspace to track waves and persist state for resuming operations.

How does session-based state work for tracking multi-repo development workflows?▼

Session-based state persists workspace sessions under .planning/workspace/session-{slug}.md. This mechanism tracks wave execution, records discovery relays, and allows you to resume multi-repo campaigns if execution halts or requires staged rollbacks.

Can I run build and type checks in isolation for each repository during a cross-repo campaign?▼

Yes, the workflow runs isolated per-repo build and type checks during wave execution. This ensures that each repository in the campaign passes its specific verification before downstream consumers in dependent repositories are triggered.

Related Skills

Explore More Software Engineering Skills→
SethGammonSethGammon
820

workspace

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

Community
Advanced
krzemienskikrzemienski
2

intelligent-do

Automate context-aware planning, specification generation, and wave-based execution via Serena MCP.

Community
Advanced
jackspacejackspace
16

multi-repository-orchestrator

Orchestrate synchronized branching and batch commits across multiple Git repositories.

Community
Advanced
Lifecycle-Innovations-LimitedLifecycle-Innovations-Limited
22

ops-orchestrate

Automate multi-project orchestration, auditing, and PR shipping across registries.

Official
Advanced