← ClaudeAtlas

dispatch-juniorlisted

Builder-only recipe to hand a ticket's implementation to a junior pane on another runtime (Grok first) and take the tree back for review, simplify and the arm. Fires only when the Builder's Junior row in .agents/orchestrator.md names a runtime. Covers the pane, the launcher, the brief, the wait, the read-back and the close.
thientranhung/astragentic · ★ 4 · Code & Development · score 70
Install: claude install-skill thientranhung/astragentic
# Dispatch to a junior **Who:** the Builder, inside its own ticket, after the red tests are committed. Thomas never dispatches a junior; a junior never reports to Thomas. **When:** `.agents/orchestrator.md` → `## Junior` → the `builder` row names a runtime. `none` or no row means you implement alone and this skill does not fire. The runtime names the supplement the junior reads: `.agents/roles/junior-<runtime>.md`. A runtime with no supplement file in the worktree is a misconfigured row: STOP and tell Thomas. **What stays yours:** every phase in `builder.md` except the typing. the red tests of `astra-implement-with-tdd`, both reviews, simplify, the arm, the markers, the handback and the push are the Builder's, run over the junior's commits exactly as over your own. The mod's gates read your pane, not the junior's, so nothing about them changes. ## 1. The pane — in your tab, beside you ```bash herdr pane split --current --direction right --no-focus # read result.pane.pane_id (Orca: `orca terminal split`, then `terminal send` text and Enter as two calls; dispatch-ticket/ORCA.md) herdr pane rename <pane-id> "junior:<ticket-id>" ``` The pane's cwd is your worktree, because yours is. Never a new tab, never a new worktree: one worktree, two writers in sequence, never at once (below). ## 2. Launch — the row decides the flags ```text grok → herdr agent start "junior-<id>" --kind grok --pane <pane-id> --timeout 60000 \ -- --model <row: Model> --reasoning-effort