Inputs

• Env: optional RELAY_SKILL_ROOT defaults to skills; Step 7/8 examples use RUN_ID.
• Files: relay-ready handoff, task file, issue/user text, optional local harness context (AGENTS.md, CLAUDE.md, CHARTER.md, spec/capabilities.md, active sprint notes), optional /tmp/done-criteria-<N>.md, /tmp/dispatch-<N>.md, and /tmp/rubric-<N>.yaml.
• Sibling scripts: ${RELAY_SKILL_ROOT:-skills}/relay-dispatch/scripts/reliability-report.js, ${RELAY_SKILL_ROOT:-skills}/relay-plan/scripts/probe-executor-env.js, ${RELAY_SKILL_ROOT:-skills}/relay-plan/scripts/persist-done-criteria.js, ${RELAY_SKILL_ROOT:-skills}/relay-dispatch/scripts/dispatch.js.

Relay Plan

Use when

• Building the review anchor, scored rubric, and dispatch prompt for a relay run
• Converting task intent, explicit AC, repo signals, and risk into reviewable Done Criteria
• Persisting planner-authored Done Criteria before dispatch

Do not use when

• Shaping an ambiguous task before planning — use relay-ready
• Delegating implementation to an executor — use relay-dispatch
• Reviewing executor output — use relay-review
• Merging a reviewed PR — use relay-merge