OrchestKit · /ork:swarm-migrate playground

Paste a spec, see the topology DAG and the simulated ledger. Spec format: swarm-specs/<name>.yaml. Docs in SKILL.md.

Why this skill

275-session insights audit showed 25 sessions burned coordinating cross-repo PR cascades manually (M164 deploy-migration, M17 yg-mcp-core extraction, @v1 reusable workflow across 14 repos). The shape was always the same: pick a repo, branch, transform, push, watch CI, repeat. /ork:swarm-migrate turns the coordinator into a YAML file and the workers into parallel subagents.

1. Paste your spec

Use the example or your own. One transform per spec; topology via upstream edges.

—

2. Topology (waves)

waiting for spec…

3. Simulated execution ledger

What the live .swarm-state.json would look like at the moment wave 1 starts. merged CI pending blocked-on-upstream novel-failure-paused

repo	wave	status	PR	CI	last action

4. What this skill does NOT do

Does NOT merge PRs. Workers open them; humans (or gh pr merge --auto) merge.
Does NOT force-push. Conflicts surface to the coordinator.
Does NOT roam outside the spec's repos[]. Even if the transform would help elsewhere.
Does NOT auto-resolve merge conflicts — the most common place auto-fixers ship broken code.