run-train

Coordinates multi-repo release trains with draft PRs, review, and sequential merges.

2|1|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/Consiliency/agent-harness --skill run-train-consiliency
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: run-train
Source: https://github.com/Consiliency/agent-harness/tree/main/phase-loop-skills/run-train
Command: npx skills add https://github.com/Consiliency/agent-harness --skill run-train-consiliency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating a release that spans multiple repositories is error-prone: PRs must open in dependency order, merges must respect upstream changes, and a failed downstream integration can silently break the train. This Skill provides the entry point to the phase-loop run-train coordinator, which automates draft PR creation, train-level review, and sequential merging with downstream re-verification. ## Core Features & Use Cases - Topo-ordered draft PRs: Opens draft PRs across all train nodes in dependency order after a preflight check, stopping before any PR is opened if preflight fails. - Governed merge phase: With --governed, runs train-level review, then merges upstream nodes first and re-verifies each downstream node against the upstream merged SHA. - Crash-resumable ledger: Inspect state with phase-loop train-status and resume interrupted runs; already-merged nodes are skipped and blocked nodes retried. - Use Case: A platform team ships a breaking API change across five service repos. They define a train roadmap with node dependencies, run the coordinator to open all draft PRs, gather one train-level review, then merge sequentially with automatic downstream re-verification. ## Quick Start Ask the assistant to run the release train by invoking phase-loop run-train --train <train-roadmap-file> --governed against your train roadmap Markdown file.

Frequently Asked Questions about run-train

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

FAQPage Schema
How do I run a multi-repo release train with phase-loop?▼

Run `phase-loop run-train --train <train-roadmap-file>` to open draft PRs across all nodes in topological order. Add `--governed` to proceed through train-level review, sequential merge, and downstream re-verification.

What format does a train roadmap file need?▼

The train roadmap is a Markdown file with a `## Nodes` section listing `### Node: <repo> / <plan>` entries. Each node declares `**Depends on:**` and `**Channel:**` fields that drive ordering and merge behavior.

Can I resume an interrupted release train run?▼

Yes, the coordinator is crash-resumable. Re-invoke the same command with `--governed`; the ledger skips already-merged nodes, re-verifies partially merged ones, and retries blocked nodes. Use `--ledger <path>` for an explicit ledger location.

What happens when a downstream re-verify fails during merge?▼

The run enters `merge_halted` status: the failed node and its dependents are blocked, while already-merged upstream nodes stay merged under the forward-only guard. Fix the integration issue and resume the same command.

Should I use phase-loop run or run-train for a multi-repo roadmap?▼

Use `run-train` for multi-repo trains. Invoking `phase-loop run` on a train roadmap file triggers the per-repo loop, which does not orchestrate cross-repo draft PRs, train-level review, or sequential merges.