Handover

Routing Boundary

Use this skill only for an explicit Verbs /handover: unfinished mechanical build units from an existing plan are delegated to Codex, while the orchestrator keeps planning, review, and git ownership.

Do not use it for:

• Direct codex exec outside the handover protocol — raw CLI use skips the payload contract, the preflight gate, and the result classification this skill adds.
• Closing finished work, PR creation, publishing, or shipping — use ship.
• Exploratory or judgment-heavy work where a model should reason, not execute — pull a cross-model take with advisor; do not hand the thinking to Codex.
• Multi-step sequential plan-and-build in one runtime — use sprint.

This is an explicit cross-runtime invocation contract. Verbs defines the payload, safety gate, and result classification; the host owns runtime availability, authentication, model choice outside the pinned invocation, and cost policy.

When to use

• A plan has ≥3 mechanical build units (rote, well-specified, file-scoped) that benefit from one bounded fresh execution context.
• You planned + partially built and want the rest done by Codex while you review / move on.

Skip a single trivial edit — it stays on Claude. (Judgment-heavy / exploratory work is already out of scope per Routing Boundary.)