Orchestrate T3

Fan issues out to T3 Code threads — one thread per group of issues, each assigned its own execution worktree — and drive every issue to a test-backed end state. You are the orchestrator: you read, group, create worktrees, launch, monitor, and report; the threads implement.

Inputs

Never guess an input.

• SPEC_REF or ISSUES — a parent issue whose open sub-issues become the work, or an explicit list of issues. Linear PRWL-100 / ABC-123, or a GitHub issue URL or number. From skill args or the request; neither present → ask.
• AGENT — inherit the builder harness, provider and model from the user-started session, unless the user explicitly overrides them; resolve and verify them against the live catalog.
• RUNTIME_MODE — the T3 Code permission mode every thread runs in.
• TRACKER / TRACKER_TAG — workspace tracker of record (G / L), derived per Resolve in references/tracker-map.md, which holds the per-tracker commands cited by bold section name below.

T3 Code tool calls are cited by bold section name from references/t3-tools.md.

Rules