relay-readylisted

## Inputs - Env: optional `RELAY_SKILL_ROOT` defaults to `skills`. - Files: `/tmp/relay-ready-contract.json` with request, handoff, leaf, and Done Criteria fields; generated request artifacts under `~/.relay/requests/<repo-slug>/`. - Sibling scripts: `${RELAY_SKILL_ROOT:-skills}/relay-ready/scripts/persist-request.js`, `${RELAY_SKILL_ROOT:-skills}/relay-dispatch/scripts/dispatch.js`. # Relay Ready ## Use when - `/relay` cannot safely bypass straight to planning - The request is ambiguous, too broad, or may need multiple ordered leaves - No stable Done Criteria or review anchor exists yet ## Do not use when - Authoring rubrics or dispatch prompts — use `relay-plan` - Delegating implementation work — use `relay-dispatch` - Reviewing executor output — use `relay-review` - Landing a reviewed GitHub change — use `relay-merge` ## Readiness Judgment No script scores readiness. Judge the request yourself against these factors, reading only text outside fenced code blocks — a fenced example is not a signal. - **Clarity** is low when any of these hold: a vague verb (`improve`, `enhance`, `clean up`, `polish`); no explicit target (no file path, no `function()`); a body under roughly 200 characters. It is high only when an explicit target and an observable end state both appear in the opening paragraph. - **Granularity** is low when any of these hold: a top-level `and` joining two action clauses in the opening line; a multi-verb opener spanning more than one subsystem;