How to do AFK Coding

<TLDR items={[ “1–3 story-point tickets fit in one Opus 4.7 or GPT 5.5 shot. 5+ pointers don’t. The context fills, the model auto-compacts, and the refactor never happens.”, “AFK coding is HITL at the edges, AFK in the middle. You align on the spec, you review the PR. Everything between runs without you.”, “The pipeline: spec → vertical-slice sub-tickets → Ralph loop per slice with TDD red-green-refactor → dedicated refactor pass → agent-browser QA → PR.”, “You’re a manager now: review, QA, and several pipelines in parallel.”, ]} /> The Pipeline The workflow I use to ship a 5-point ticket while I’m away from the keyboard: Six phases. The first and last are human, the middle four run on their own. 1. Align on spec ── HITL ── business + dev + AI interviewer 2. Slice the ticket ── AFK ── vertical slices, one per sub-ticket 3. Ralph loop per slice ── AFK ── fresh context, TDD red-green-refactor 4. Refactor pass ── AFK ── the step LLMs always skip 5. Agentic QA ── AFK ── agent-browser…