afk-fleet

An unattended fleet that implements a decomposed GitHub-issue backlog by itself, and keeps running for days in one session that can be compacted at any point and lose nothing. Two roles hold a context:

Role	What it is	Lifetime
launcher	The interactive session you invoke `/afk-fleet` in. It bootstraps once, then loops: run one cycle (`afk cycle`) → answer the judgments it hands back → sleep → repeat.	Long-lived. A cycle leaves a few compact JSON objects behind; auto-compaction bounds that, and takes nothing the run needs.
worker	A fire-and-forget autonomous coding agent (Claude Code or qoderclicn — the run's runtime), one per issue: orca creates its worktree + branch, then starts it with the run's worker launch command so it runs on the same runtime as the launcher. Its outcome travels only through GitHub (its PR, and issue comments); the one thing it says to the launcher directly is a contentless wake.	Independent of the launcher — never read by it.

A tick is not a third role and holds no context: it is one reconciliation pass against GitHub, run in code inside afk cycle. The launcher makes the call and gets back the cycle's state, sleep and progress line — and the few judgments code cannot make.

This skill only consumes a backlog. It does not decompose a PRD/epic into issues — that is upstream work, and epics are explicitly excluded from dispatch. Assume the issues already exist, worker-sized, labelled, and dependency-ordered.