cross-repo-orchestrationlisted

# Cross-Repo Orchestration When a project spans multiple repositories, the practices that work within a single repo — specification-driven development, harness enforcement, compound learning — must extend across repo boundaries. This skill teaches two patterns for cross-repo coordination, each suited to a different maturity level. This skill does not cover single-repo agent orchestration (see the orchestrator agent), CI/CD pipeline design, or monorepo tooling. For worked examples and the sync workflow, consult `references/sync-patterns.md`. ## When to Use | Situation | Pattern | | ----------- | --------- | | Syncing skills, templates, or hooks from a framework repo to a plugin repo | L4: Git-mediated | | Propagating harness changes to downstream consumers | L4: Git-mediated | | Rolling out a new convention across 2-5 related repos | L4: Git-mediated | | Managing shared standards across 10+ repos in a portfolio | L5: Specification-mediated | | Aggregating health snapshots across an organisation | L5: Specification-mediated | | Designing platform-level harness policies | L5: Specification-mediated | ## Pattern 1: Git-Mediated Coordination (Level 4) A single agent (or human) applies changes from an upstream repo to one or more downstream repos using git's standard workflow. ### The Workflow 1. **Identify what changed upstream** — review the changelog, diff, or commit log to determine which exported artefacts were modified 2. **For each downstream repo:** a. Check