Review the tasks you were given. Decide the order and which tasks can run at the same time. Make a short plan.
Complete each task in two phases. Keep working without waiting for the user while any task can make progress.
Independent tasks may start together. Start a dependent task after every prerequisite has an open pull request, an independent
verdict of
, and no known blocking finding. Stack dependent work on the prerequisite branch. If several unmerged prerequisites feed one task, stack those prerequisite branches in dependency order before branching the dependent task. When a prerequisite branch or pull request base changes, update every dependent branch to that reviewed state and repeat
and
. Retarget each stacked pull request to the default branch after its prerequisite merges, then repeat the proof against that base.
If the user asked you to merge the pull requests, merge them in dependency order after their automated checks pass, the final
verdict is
, required approvals are present, and no review thread is unresolved. Explicitly naming
, or explicitly telling its coordinator that agents may merge, is a merge request for only the issues in its supplied batch. Automatic skill selection is not merge authority. After each prerequisite merges, retarget its dependents to the default branch, update them to that base, and repeat
,
, CI, and automated review before merging them. Never bypass repository rules. Wait until GitHub reports each pull request as merged before marking its ticket complete when possible. Otherwise, leave it open.
Continue with every task that can make progress. Stop when every task has a pull request with all available checks passing and no unresolved automated review findings. When merge was requested, stop only after every in-scope pull request is merged and its ticket is complete when possible. If no remaining task can move forward, explain what is needed.