crew-afklisted

# AFK Issue Sprint — pi The sprint is a program, not a prompt: launch it, stream its output, report what it printed. **You do not orchestrate, implement, review, merge or close anything yourself.** ```bash CREW_AFK="$(git rev-parse --show-toplevel)/.coding-crew/crew-afk/main.mjs" [ -f "$CREW_AFK" ] || CREW_AFK="$HOME/.coding-crew/crew-afk/main.mjs" node "$CREW_AFK" run --platform pi "$@" ``` Pass CLI-looking arguments straight through — `--model`, `--prd-audit`, `--fix-findings`, `--max-parallel N`, `--jira TICKET-123`, a `.scratch/<feature-slug>/…` path — never rewrite those. A bare word, typo, or free-form phrase is resolved first, below. ## Resolving the sprint target If the trailing arguments aren't CLI syntax, look up what exists first: ```bash ls -d .scratch/*/ 2>/dev/null grep -rl "Status: ready-for-agent" .scratch/*/issues/open/*.md 2>/dev/null # tracker: github — gh issue list --milestone <slug> --label ready-for-agent ``` Match against those names (exact, fuzzy/typo, then issue content). One match → `--feature-slug <slug>`, say what you inferred, then run. No match → don't run; point at `crew-grill`, `crew-brainstorm`, or `to-issues`. Multiple matches → ask which one. Never create a new `.scratch/<slug>` directory, and never guess — a wrong resolution dispatches, merges, and closes real work against the wrong feature. It owns the whole loop: a worktree and `crew-coder` process per issue, then verify → review → merge → close, then promotion, squash, cleanup a