deliverlisted

**a messy tree becomes single-purpose PRs:** bucketed, ordered and written, ready to paste - bucketing, ordering and message drafting are the reasoning it does for you - each bucket: branch, commit, push, PR, auto-merge, then back to the trunk - free text after the flags is bucketing guidance, as in `keep the readme out of the hook bucket` - an apostrophe in that guidance is safe, since the invocation quotes it - guidance narrows how work groups; it never authorizes running a block - runs none of it; every bucket is a block you paste into your own terminal # Instructions ## Telemetry ```! "${CLAUDE_PLUGIN_ROOT}"/skills/deliver/deliver.sh "$ARGUMENTS" echo "sidecar exit: $?" ``` - `help: requested` → the run was refused before it started; `## Help` below is the whole turn - it already ran, so there is no command to issue - fail (`sidecar exit` > 0) → abort and report: "<raw terminal error>" - success (`sidecar exit` = 0) → capture `default branch` from the telemetry - IF `guidance` reads anything but `none`, it is the user's bucketing instruction; honor it in step 1 - guidance narrows how work groups; it never authorizes running a block or skipping the gate - every `issue #n` row is an open issue on origin, and a candidate for a bucket to close - IF `open issues` reads `unreadable`, link nothing and say the rows never arrived - IF the handover block names any prep command, hand it over and WAIT before step 2 - the preflight measures only, so the tree is still wherever the us