afkkitlisted

# afkkit The **away-from-keyboard** orchestrator. Hand it a groomed `ready` issue and it drives the middle of the dev workflow — the part that needs no human judgment once the issue is well-specified — from an isolated worktree to an open pull request: implement, commit, review, fix, write a manual QA plan, open the PR, and flip the issue to `in-review`. The human gates stay where judgment lives: planning and grilling happen *before* (the `ready` label is the entry contract), review and merge happen *after*. afkkit adds **no** worktree, tracker, or PR behavior of its own. It **sequences** companion kits — implementkit, commitkit, reviewkit, qakit, prkit — plus a manual, human-run orcakit step at the very front, and owns exactly one thing they don't: the **escalation policy** that decides, at every step, whether to keep going or stop cleanly and leave the issue for a human. It is the autonomous sibling of statuskit: statuskit tells a human what to do next; afkkit does the next several things itself and stops at the boundary where a human is genuinely required. ## The contract - **Input:** an issue whose worktree the human has already created manually. A human runs `orcakit start <n>` themselves — which refuses anything not labeled `ready`, flips `ready → in-progress`, and creates the worktree off fresh `origin/main` — then switches into that worktree and launches (or resumes) the afkkit conductor session from inside it. That manual step is the whole safety property: an iss