relay
Dev Relay
Execute the plan → dispatch → review cycle. Stop at ready_to_merge unless the user explicitly asks to merge. Follow ALL steps below in order.
Role Defaults
| Role | Default | Override |
|---|---|---|
| Orchestrator | unknown until explicitly stamped |
RELAY_ORCHESTRATOR env |
| Executor | Codex | --executor flag |
| Reviewer | unknown until explicitly stamped |
--reviewer flag, RELAY_REVIEWER env |
Standard Codex path: stamp RELAY_ORCHESTRATOR=codex and run review through review-runner --reviewer codex. Assigned manifest roles stay immutable; the acting reviewer for a round is recorded separately under review.last_reviewer and the review_apply event.
Step 0: Re-Anchor
Always run before every task — standalone or batch. Ensures current state, not stale context.
git fetch origin— check for divergence from remote
More from sungjunlee/dev-relay
relay-merge
Merge a reviewed PR, clean up worktree/branch, and close GitHub issues. Use after relay-review returns LGTM.
17relay-dispatch
Dispatch implementation tasks via worktree isolation. Use when delegating work to an executor, running background dispatches, or parallelizing independent tasks.
17relay-plan
Synthesize task intent, explicit AC when present, repo signals, and task risk into a scored rubric for autonomous iteration. Always used before relay-dispatch — rubric depth scales with task size.
16relay-review
Independent PR review against Done Criteria in a fresh context, free from planning bias. Use after dispatch completes and a PR exists.
16relay-intake
Shape a raw request into one-or-more relay-ready leaf contracts with frozen Done Criteria snapshots. Use before relay-plan when the task is ambiguous, oversized, or missing a stable review anchor.
10