afk-fleet
Installation
SKILL.md
afk-fleet
An unattended fleet that implements a decomposed GitHub-issue backlog by itself, and keeps running for days without any session's context growing without bound. Three roles, each context-bounded:
| Role | What it is | Lifetime |
|---|---|---|
| launcher | The interactive session you invoke /afk-fleet in. It authorizes once, then loops: spawn a tick → ingest a one-line summary → pace → repeat. |
Long-lived, but only accumulates ~one compact summary per tick (auto-compaction keeps it flat). |
| tick | A fresh-context [Agent] subagent that does exactly one reconciliation pass against GitHub, then returns a compact structured summary and dies. | Short. Its bulky context is discarded on return. |
| worker | A fire-and-forget autonomous Claude Code, one per issue: orca creates its worktree + branch, then starts it with the run's worker launch command so it runs on the same provider as the launcher. Communicates only through GitHub (its PR, and issue comments). | Independent of the coordinator — never read by it. |
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.