cross-repolisted

# Cross-repo features Order, concurrency, and links for multi-repo work. **Kind** reference · **Used by** orchestrator · [architect](../../agents/architect.md) · [releaser](../../agents/releaser.md) · **When** the plan spans more than one repo (develop-flow step 3) · **Ends with** a repo order, a parallel/sequential call, and PRs linked in dependency order One lane/branch/PR per repo. Multi-area single-repo work stays one lane. ## Order: providers before consumers Use profile dependency order. Same-level independent repos may run in parallel. Skip untouched levels. ## Shared libraries released by tag Pinned libraries require a release and consumer pin bump: - The change lands in the library first. - Each consumer bumps the pin and refreshes its lockfile in its own PR. - **The release must exist before the consumer merges**, not before its PR opens. A consumer PR pointing at an uncut version fails CI at dependency resolution — mark it blocked rather than guessing a version. - Pins drift between consumers. Check each one rather than assuming they match, and bump only the ones the plan touches. ## Parallel vs sequential Pinned contract permits parallel development; otherwise follow dependency order. ## Link the PRs Every PR after the first declares its upstream PR(s) in the body ([pr-template](../pr-template/SKILL.md)). Use one ticket key across all branches and PRs so they group on the ticket ([tracker](../tracker/SKILL.md)). On the ticket, comment the full PR chain