← ClaudeAtlas

afk-preflightlisted

Rereads the batch of ready-for-agent tickets just before an afk run, and fixes what would cost the night — a freeze from an out-of-run blocker, criteria no gate can check, a ticket too big for its time budget. It also re-slices the batch: cut a ticket that does not fit in one session, serialise two tickets writing into the same files, hand out the numbers (ADR, migration) before the run. Run between /triage and ./afk.sh, on already published tickets whatever their origin. Triggers: /afk-preflight, "are my tickets ready for afk?", "reread the batch before launching", "re-slice the batch for afk", "why would this ticket be frozen?".
Warshoow/afk.sh · ★ 3 · AI & Automation · score 69
Install: claude install-skill Warshoow/afk.sh
# /afk-preflight A badly written ticket does not cost five minutes, it costs `MAX_ATTEMPTS × TIMEOUT` of the night — and if it blocks the others, it costs their night too. This skill rereads the batch before the run and returns a list of corrections. `./afk.sh -n` already gives the whole mechanism: waves, bases, stacks, frozen, effective gate per ticket. **Do not redo it.** This skill judges the *content* of the tickets, which the script cannot do. ## 1 — Prerequisites ```bash test -f .afk.env || echo "no .afk.env — run /afk-setup first" ``` No `.afk.env` → the gate will be a pnpm monorepo's, wrong everywhere else. Stop there. ## 2 — The plan ```bash ./afk.sh -n # the whole ready-for-agent batch ./afk.sh -n 43 48 49 # or an explicit batch ``` Read from it, without recomputing: the **frozen** tickets, the **waves** (who runs at the same time as whom), the **bases** (who stacks on whom), and the `Verify:` / `Timeout:` / `Model:` / `Effort:` lines the tickets gave themselves. ## 3 — The bodies ```bash gh issue view <n> --json title,body,labels -q '.title, .body' ``` One ticket per call, for the whole batch. It is the raw material for everything else. ## 4 — What to look for | What you see | What will happen | Fix | |---|---|---| | **Frozen — blocker open outside the run** | the ticket does not start, and neither do its dependants | three cases: (a) the blocker is done but its ticket was never closed → close it; (b) it has an open PR → `STACK_ON_OPEN_PR=