crew-afklisted

# AFK Issue Sprint — Copilot You orchestrate every `ready-for-agent` issue by dispatching each one to the **crew-coder subagent**, then handling housekeeping yourself. The filesystem is your source of truth — done issues are moved to `done/`. **Parallel processing with worktree isolation**: Before dispatch, create a dedicated git worktree for each unblocked ready issue. Dispatch all subagents in a single response (parallel). Each crew-coder subagent runs in its isolated worktree, commits the work, and returns a structured report. You process reports, do housekeeping, and loop. **You do not implement issues yourself.** For each issue, use `#runSubagent` to invoke `crew-coder`, passing the issue file path. The subagent runs in an isolated context window, commits the work, and returns a structured report. You process its report, do housekeeping, and loop. **Issue tracker: local only.** Issues live in `.scratch/*/issues/open/*.md`. Never query `gh`, GitHub, or any remote issue tracker. If no local issues are found, print `NO MORE TASKS` and stop. ## Definitions - **Ready issue**: `Status: ready-for-agent` — fully specified, no human input needed. - **Skipped issue**: any other status — skip entirely. - **Blocked issue**: its `## Blocked by` section names an issue not yet in `issues/done/` (sibling of `issues/open/`). - **Unblocked issue**: no `## Blocked by` section, or all listed dependencies are in `issues/done/`. ## Issue Tracker Conventions Issues live as local markdo