afk-runlisted

Drive the AFK orchestrator from inside the IDE chat window — kick off a decompose, run one issue end-to-end, or process one batch — without the user having to leave chat for a terminal. Use when the user says "/afk-run", "run AFK on PRD N", "drive issue N", "let's process the queue", or generally wants to orchestrate AFK work without switching to a shell.
Mo-Tamim/afk-agent · ★ 0 · AI & Automation · score 72

Install: claude install-skill Mo-Tamim/afk-agent

# Skill: afk-run The shell-side counterpart of `/afk-grill` and `/afk-prd`. Whereas `/afk-grill` turns a sketch into ADRs and `/afk-prd` turns the sketch into a tracker PRD, **`/afk-run`** drives the actual implementation phases from inside the chat window. This skill is what makes "AFK from inside chat" possible without making the user juggle a separate terminal. ## Prerequisites - `.afk/config.yml` exists (`/afk-setup` has been run). - The tracker has a PRD issue labelled `afk-prd, ready-for-agent` (`/afk-prd` has been run). - The agent runtime can invoke shell commands. Cursor's `cursor-agent`, Claude Code, Codex, GitHub Copilot Chat, Windsurf and Gemini all support this; if it can't, fall back to the terminal mode in [`docs/MODES.md`](../../docs/MODES.md). ## What `afk run` does (for the driving agent) The parallel orchestrator (`afk run`) **prefers resuming** any open `afk-child` that still has **`afk-in-progress`** on the tracker (e.g. after a crash) before it pulls fresh **`ready-for-agent`** work, as long as blockers are closed and the issue is not locked. You normally do **not** need to re-run `afk issue N` after an IDE restart unless you want a blocking, chat-attached session. ## What the user can ask for | User says… | You run… | |---------------------------------------------|------------------------------------------------| | "Decompose PRD #42" | `.afk/s