orchestrate

Run a pre-specced feature across parallel /implement agents, each on its own worktree. Threads first, subagents as fallback.

Rule Zero

Never slice or map the work yourself. The parent issue's sub-issues ARE the work packages: fetch them, hand each verbatim to one /implement agent. Sub-issues missing or unclear → stop and ask the owner; do not invent packages. Process fidelity is a requirement — a correct deliverable produced off the pre-specced path gets rejected.

Roles

• Orchestrator (you): read-only + gh + spawning. Never edit src/. Your job: sequencing, relay, verification between phases, merges, cleanup, ops sidecar (see ops.md).
• Agents: full /implement flow — native claim, own worktree, TDD, /code-review, own PR. Duplicate none of it here.
• Mechanical tail (merge order, CI watch, branch/worktree cleanup) belongs to the orchestrator. Agents end at "PR open + report".

Agent transport

Start each agent as a thread when your host offers threads. Fall back to a background subagent only when it does not. A thread is visible and steerable by the owner, and its /code-review children report to the thread agent itself — no relay hop.

Either way: one agent per sub-issue, its own worktree, branch <type>/<description>, the package prompt as its task.

Ledger