Dispatch Tickets

Contract

Run one safe round: classify every candidate, dispatch every safe implementation ticket, collect all results, verify handoffs, and report a ledger. Do not merge PRs/MRs, move drafts to ready, or loop; use the autopilot-tickets skill for those responsibilities.

Set no skill-level concurrency cap; native capacity limits simultaneous calls only.

Select Issues

Use the configured tracker and forge.

1. Run git status --short --branch; resolve the repo root; identify base/current branches, remotes, tracker, and forge.
2. Read applicable AGENTS.md and CLAUDE.md guidance; consult context, README, and other docs only as needed to assess the selected scope.
3. Query open candidates within the requested scope (default: ready-for-agent); read their labels, criteria, dependencies, and recent comments. Follow linked dependencies and blockers as needed to establish readiness.
4. Classify every implementation candidate in this round as selected or unselected with a reason. A parent Spec/PRD/map link supplies scope only: its open state is not a dependency. Treat only unfinished implementation-level dependencies and explicit decision/review/policy gates as blockers; treat dirty files that overlap expected edits as a dispatch risk unless clearly unrelated.

Dispatch an issue only when all are true: