The AFK loop

How the team runs AFK agents: which work to hand over, how to dispatch it, what to check when a pull request lands, and what to do when a run goes wrong.

Your repo's AGENTS.md is the other half of this. It states the contract an agent works to; this skill is the human procedure around it.

Dispatch is manual on purpose. A team member assigns each Ready for Agent issue to Copilot by hand while we dogfood the coding agent's cost and performance. No workflow fires when a project field changes, so there is nothing to automate against yet in any case. Once agents pick work off the frontier themselves, this file loses its reader and should be deleted rather than maintained.

Work state is the Status field on the board — see the issue-tracker skill.

Copilot or Claude Code

Can the work run unattended?