Add orch Codex launch bridge workflow

skills/orch/SKILL.md

@@ -33,6 +33,7 @@ Use the bundled `./assets/orch` CLI to control leader-side orchestration through
 - Prefer `--json` whenever another agent or script will read the output.
 - Initialize a new database path once through the bundled `inbox init` command before the first real run.
 - Use `status` as the main operational view. It reconciles worker thread state first, then returns run, task, latest-attempt, and latest-message context.
+- For Codex worker launch, standardize the handoff through `./assets/orch-worker-brief` instead of improvising the worker prompt every time.
 - Use this skill for leader-side scheduling and control-plane actions, not worker-side lease or progress updates.
 
 ## Rules
@@ -56,6 +57,36 @@ Use the bundled `./assets/orch` CLI to control leader-side orchestration through
 5. Launch or reuse a separate worker runtime or worker agent that uses `skills/inbox/` against the same DB path.
 6. Use `status`, `wait`, `blocked`, `answer`, `retry`, `reassign`, and `cleanup` to operate the run until the required tasks are complete.
 
+## Dispatch-And-Launch Workflow
+
+Use this when the leader wants durable `orch` state plus a worker sub-agent launched from the current Codex thread.
+
+1. save the dispatch output:
+
+```bash
+./assets/orch --db ./coord.db --json dispatch --run RUN_ID --task TASK_ID > TMPDIR/dispatch.json
+```
+
+2. render a standardized worker brief:
+
+```bash
+./assets/orch-worker-brief --dispatch-json TMPDIR/dispatch.json --db ./coord.db > TMPDIR/worker-brief.txt
+```
+
+3. spawn one worker sub-agent with:
+   - `skills/inbox/`
+   - the generated worker brief
+   - the repo defaults from `AGENTS.md`
+     - model `gpt-5.4`
+     - reasoning effort `xhigh`
+     - `fork_context: true` first
+4. keep the leader on `orch wait`, `orch status`, `orch blocked`, `orch answer`, `orch retry`, or `orch reassign`
+
+See:
+
+- `./references/leader-dispatch-and-launch-checklist.md`
+- `./references/worker-brief-template.md`
+
 ## Worker Handoff Contract
 
 - The worker side should use `skills/inbox/`, not this skill.
@@ -72,8 +103,10 @@ Use the bundled `./assets/orch` CLI to control leader-side orchestration through
 ./assets/orch --db ./coord.db --json task add --run blog_mvp_001 --task T2 --title "Summarize flaky tests" --summary "Read logs and report next steps" --default-to qa-worker --acceptance-json '{"kind":"analysis"}'
 ./assets/orch --db ./coord.db --json dep add --run blog_mvp_001 --task T2 --depends-on T1
 ./assets/orch --db ./coord.db --json ready --run blog_mvp_001
-./assets/orch --db ./coord.db --json dispatch --run blog_mvp_001 --task T1 --to foundation-worker --base-ref main --workspace-root .orch/worktrees --strict-worktree --body-file tasks/t1.md
-./assets/orch --db ./coord.db --json dispatch --run blog_mvp_001 --task T2 --to qa-worker --body "Read the failing test logs and summarize the root cause."
+./assets/orch --db ./coord.db --json dispatch --run blog_mvp_001 --task T1 --to foundation-worker --base-ref main --workspace-root .orch/worktrees --strict-worktree --body-file tasks/t1.md > /tmp/t1-dispatch.json
+./assets/orch-worker-brief --dispatch-json /tmp/t1-dispatch.json --db ./coord.db > /tmp/t1-worker-brief.txt
+./assets/orch --db ./coord.db --json dispatch --run blog_mvp_001 --task T2 --to qa-worker --body "Read the failing test logs and summarize the root cause." > /tmp/t2-dispatch.json
+./assets/orch-worker-brief --dispatch-json /tmp/t2-dispatch.json --db ./coord.db > /tmp/t2-worker-brief.txt
 ./assets/orch --db ./coord.db --json status --run blog_mvp_001
 ./assets/orch --db ./coord.db --json wait --run blog_mvp_001 --for task_blocked,task_done,task_failed --after-event 0 --timeout-seconds 900
 ./assets/orch --db ./coord.db --json blocked --run blog_mvp_001
@@ -104,6 +137,7 @@ Use the bundled `./assets/orch` CLI to control leader-side orchestration through
 
 - `dispatch` supports `--repo-path`, `--workspace-root`, `--strict-worktree`, and `--base-ref` for worktree-backed code execution.
 - When worktree flags are omitted, code-like task metadata can still auto-enable strict worktree mode. Non-code tasks stay on the normal thread-only path.
+- `./assets/orch-worker-brief` is the supported way to turn a saved dispatch JSON response into a stable worker prompt for a spawned sub-agent.
 - `answer` supports `--payload-json` for structured decisions, not just freeform text.
 - `status` is the full run view; `run show` is the lighter aggregate view.
 - If the bundled binary cannot execute on the current host, stop and report the compatibility issue instead of guessing a replacement path or workflow.