Autopilot Issues

Purpose

Run a controlled issue-draining loop: refresh state, merge only tracked PRs/MRs that pass every gate, dispatch one safe batch when nothing is mergeable, and stop when the queue or safety conditions require it.

Delegation

• $dispatch-issues owns per-issue readiness, branch/worktree setup, $implement subagent prompting, and subagent lifecycle.
• $autopilot-issues owns loop state: refreshing tracker/forge data, detecting new blockers, deciding when to dispatch, converting verified drafts to ready-for-review, applying merge gates, and stopping.

Do not bypass $dispatch-issues unless unavailable. If unavailable, apply the same readiness and lifecycle rules manually and report the fallback.

Treat $dispatch-issues's <project-root>/.worktrees/<branch-name> layout as a hard invariant when verifying ledgers and merge gates. Do not accept or create issue worktrees elsewhere.

Use the repo's configured tracker and forge tools.

Loop