Practical Application

Build the AFK workflow in stages:

1. Maintain backlog items as local markdown files or work-tracking issues with clear scope

and dependencies.

1. Write a runner that injects the backlog and a concise implementation prompt into a new

coding-agent session.

1. Define how the agent identifies eligible work and what it outputs when no work remains.
2. Require repository exploration before editing.
3. Require TDD and named feedback loops.
4. Require a commit and completion summary for each successful task.
5. Run the process once with a human watching.
6. Tune the prompt until one iteration behaves predictably.
7. Only then place it inside an unattended loop and sandbox it.

Task prioritization can be explicit. A queue may prefer critical bug fixes, development infrastructure, tracer-bullet issues, polishing work, quick wins, and refactors in a defined order. The exact priority is less important than making the selection rule visible and controllable.