Autopilot Tickets

Ownership

• dispatch-tickets owns per-ticket readiness, branch/worktree setup, worker prompting, and subagent lifecycle.
• autopilot-tickets owns fresh-state looping, blocker detection, draft promotion, merge gates, and stopping.

Use configured tracker/forge tools. Delegate to the dispatch-tickets skill; if unavailable, manually apply its readiness/lifecycle rules and report the fallback. Subagent dispatch is delegated to dispatch-tickets. If the harness cannot dispatch subagents, stop the loop after reporting the missing capability — do not simulate workers in the parent session unless the user explicitly requests fallback inline work.

Loop

Repeat from fresh state:

Invoking this skill grants standing authorization for the full run to promote and immediately merge every in-scope PR/MR once all Merge Gates pass. Execute the merge without requesting per-PR confirmation. This authorization does not waive Merge Gates or authorize out-of-scope changes. Replace unavailable workers, send targeted follow-ups, and repair loop-created changes within the same ticket scope autonomously.