skills.rest
azure-id
azure-idCOMMUNITY
Explore all skills by this author →
GitHub

orc-poly

Plans one change spanning multiple repositories with a frozen interface contract.

6|1|Updated Jul 4, 2026
Search Tags:#api design#microservices#claude code#orchestration#interface contract#cross-repo planning#poly-repo
One-click install
npx skills add https://github.com/azure-id/orc --skill orc-poly-azure-id
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orc-poly
Source: https://github.com/azure-id/orc/tree/main/templates/skills/orc-poly
Command: npx skills add https://github.com/azure-id/orc --skill orc-poly-azure-id

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? A single feature often lands in two or more repositories at once — a backend endpoint and the frontend screen that calls it, or a service and its gRPC consumer. Planned separately, the two halves drift: one side assumes a field or status the other never provides. This Skill plans all repos together once and freezes the shared boundary into an interface contract every repo's plan is pinned to. ## Core Features & Use Cases - Cross-repo intake and resolution: Identifies the HOST repo and resolves each PEER repo by filesystem path or crosslink node slug, auto-deriving the relation between repos. - Read-only recon with a question loop: Reads wiki, crosslink boundary tags, and pointed-at source files across all repos, then asks batched questions until the boundary shape, auth, errors, and versioning are fully pinned. - Source-of-truth doc set: Writes poly-context.md, interface-contract.md, and a machine-readable poly-spec.md into poly-repo-implementation/<slug>/ in the HOST repo. - Split handoff: Dispatches the planner to emit one implementation plan per repo, each embedding the frozen contract, so later per-repo /orc builds cannot drift. - Use Case: You need a new "saved carts" endpoint in shop-api plus a screen in shop-web. Run /orc-poly, paste the peer repo path, answer the scoping questions, and receive two contract-pinned plans to build separately. ## Quick Start Run /orc-poly in your host repository and paste the path of each peer repo to plan a cross-repo change with a frozen interface contract.

Frequently Asked Questions about orc-poly

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

FAQPage Schema
How do I plan a feature that spans multiple repositories?▼

Run /orc-poly from the host repository and provide each peer repo as a filesystem path or crosslink node slug. The skill gathers cross-repo context, asks questions until the boundary is pinned, then writes a frozen interface contract and one implementation plan per repo.

What is an interface contract in cross-repo planning?▼

An interface contract is a frozen document describing the exact shared boundary: endpoint or RPC shape, request and response fields, error codes, auth, and versioning. Every repo's implementation plan is pinned to it so the two sides fit together on the first build.

Does orc-poly modify code in peer repositories?▼

No. Peer repository source is strictly read-only. The only write ever made into a peer repo is its handoff implementation plan file during the split phase; the skill never edits peer source, commits, or pushes in any repo.

Can orc-poly work if a repository has no wiki?▼

Yes. A missing wiki is never a blocker. The skill asks you which folders, files, or keywords to dig into for that repo instead of running a blind repo-wide scan, and stale wiki docs may still be used as hints.

Does orc-poly build or implement the code itself?▼

No. It is a planner, not a builder. After splitting, you open each repo in its own session and run /orc or /orc-mini on that repo's plan, which carries the same frozen contract so no repo drifts from the others.

Related Skills

Explore More Software Engineering Skills→
VKirillVKirill
15

gitnexus-cli

Build and refresh repository knowledge graph indexes for Claude Code context.

Community
Intermediate
siarhei-belavussiarhei-belavus
2

hydrate-child-packet

Creates a child task packet with imported context and bootstrap metadata before planning begins.

Community
Intermediate
FourthWizFourthWiz
2

discover

Scan project repositories and store inventory, architecture, and dependency maps in memory.

Community
Intermediate
DVNghiemDVNghiem
20

multi-repo

Coordinate multi-repo changes with dependency ordering and conflict resolution.

Community
Advanced