Heyvhuang/copybook-skills / standalone/coordinator/skills/coordinator
coordinator
FlaggedCoordinate an ongoing software delivery run when the user assigns this session the coordinator role or asks it to manage worker handoffs, gates, release approvals and progress. Use when starting, supervising or resuming that run, including a run with one active lane. Lanes run as Herdr workers (parallel-goal-fleet) on Claude or Codex, from whichever harness coordinates; T3 Code child tasks are the fallback. Do not start a coordinator run for discussion, a read-only review of the workflow, a standalone quick second opinion or an ordinary single-session edit.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.8 KB |
| references/example-run.md | markdown | 3.4 KB |
| references/herdr.md | markdown | 7.7 KB |
| references/lessons.md | markdown | 6.9 KB |
| references/models.md | markdown | 4.9 KB |
| references/pipeline.md | markdown | 6.1 KB |
| references/situations.md | markdown | 3.4 KB |
| references/t3.md | markdown | 4.9 KB |
| scripts/gemini.mjsexecutable | script | 2.3 KB |
| scripts/heavy.shexecutable | script | 829 B |
| scripts/status.shexecutable | script | 2.0 KB |
| scripts/watch-ready.shexecutable | script | 2.0 KB |
| templates/lane-brief.md | markdown | 1.5 KB |
| templates/release-packet.md | markdown | 1.4 KB |
| templates/run-record.md | markdown | 1.2 KB |
| templates/ship.md | markdown | 1.1 KB |
references/t3.md
View on GitHub# T3 Code adapter
Fallback runtime: use when Herdr is down, a lane keeps failing on a Herdr-only problem, or the user asks for T3 (SKILL.md, Runtime). Briefs, READY lines, the run record, gates and shipping stay as in SKILL.md; this page only maps the lane mechanics. Facts below were measured on one machine in November 2026 unless marked unverified.
## Once per run
- Call `orchestrator_capabilities` once (again only after an error or a provider change). It lists providers, models and option ids. Option ids differ per provider: Claude `effort`, Codex `reasoningEffort`.
- Record in the run record header: host T3 Code, the coordinator thread (`$T3CODE_THREAD_ID`), and for each lane its `taskId`, `childThreadId` and `link`.
## Mapping
| Coordinator step | T3 Code |
| --- | --- |
| Start a lane | `delegate_task`: `task` = "Read <run-dir>/<brief>.md and follow it; end with the READY line it names", `title` = lane name, `role`, `target` = `{providerInstanceId, model, options}`. Writer lanes add `isolation: "worktree"`. Default `mode` is async; keep it. |
| Watch | Completion wakes your thread at the end of your turn, so end the turn. This lane needs no watcher or polling (keep `watch-ready.sh` running for the Herdr lanes), and no `task_status` while it runs. |
| Collect | `task_status` (reading it marks it delivered), then the hand-over file and the checks, as in SKILL.md. |
| Follow-up to the same lane | `t3_thread_send` to its `childThreadId` (`auto` queues or steers). A send to a finished child starts a new task with a new `taskId`; update the lanes table. |
| Change of course | `t3_thread_send` with `steer`, or `restart` to drop the current turn. |
| Review or re-check | A new `delegate_task` every time, carrying the brief, the findings and any objections; never reuse an old reviewer thread. |
| Stuck lane | `t3_thread_read` with `view: "activity"`, a low `limit` and `maxCharsPerItem`. |
| Stop | `task_cancel`. Never `t3_thread_interrupt` on a child. |
| PRs | Lanes open PRs and stop; children never watch PRs. The coordinator links each PR (`link_pull_request`) and watches checks with `watch_pull_request`, and unwatches before handing back. |
| Close | After its PRs ship: `t3_thread_organize` `settle` on the child thread, then `git worktree remove` its `worktreePath` (from `t3_thread_read`) and delete the merged branch. |
| Show the user | Each child's `link`, verbatim. |
## Worktrees
- `isolation: "worktree"` checks out the coordinator thread's current commit at `~/.t3/worktrees/<repo>/t3-<id>`. Uncommitted edits stay out, and the child picks the branch name (`t3/...`). When the lane needs a fresher base than that commit, the brief's first step is `git fetch origin && git switch -c <lane-branch> <base-sha>` (safe in a fresh worktree).
- The worktree has no `node_modules`. The lane installs with the project's package manager before checks (for pnpm: `pnpm install --frozen-lockfile --prefer-offline`).
- Claude Opus and Codex Sol each committed in their T3 worktree without help.
## Limits seen
- Each `delegate_task` call took about 6 s to return, and calls sent in one message ran one after another: 8 lanes took 45 s to start. Start the lanes that gate others first.
- Completion only reaches you when your turn ends; a long coordinator turn delays collection.
- `executedModel` was filled for Claude lanes and empty for Codex lanes, so the record shows the requested model there, not proof of the one that ran.
- T3 does not limit machine load: heavy checks still go through `scripts/heavy.sh`.
- Unverified: which quota T3 child tasks draw on, behaviour past about 10 concurrent lanes, long lanes that compact, `schedule_task` as an overnight tick, and lanes on another machine through T3 environment links. Remote machines stay on Herdr.
## Benchmark (one run per cell, medium effort, same tasks)
Seconds from dispatch to the lane's last command, including worker start. Query = find `formatCredits` and count the files that use it; Commit = add one file and commit in the lane's own worktree. All answers were correct.
| Lane | T3 Code | Herdr |
| --- | --- | --- |
| Query, Opus 5.5 | 15.9 | 13.9 |
| Query, Sonnet 5.5 | 7.1 | 10.3 |
| Query, Codex Sol | 35.1 | stalled about 3 min on a dialog; 16.3 after Esc and a resend |
| Query, Codex Astra | 23.7 | stalled; 17.3 after Esc and a resend |
| Commit, Opus 5.5 | 15.3 | 16.3 |
| Commit, Codex Sol | 22.9 | stalled; 15.2 after Esc and a resend |
Claude lanes took about the same time on either host. The T3 gain was reliability: no lane stalled or needed a keypress. In each new Herdr pane, Codex CLI 0.169 opened a hook-review dialog that swallowed the task while Herdr reported `working`. Herdr started workers faster: six were ready within 4 to 8 s of each other, against T3's serial 6 s per dispatch.
After the fix, the Codex hooks were trusted once and a fresh Codex pane ran a one-line task 10.2 s from workspace create, no dialog. With that gap closed, Herdr became the default runtime.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |