afk-wavelisted
Install: claude install-skill Warshoow/afk.sh
# /afk-wave
Between two runs. It reads what the spec still asks for, what the repo **really**
contains, and opens the next wave's tickets.
We do not slice everything up front because we cannot: a wave's tickets depend on the
code the previous wave actually wrote, not on the code we imagined.
## 0 — The guard, before anything else
```bash
git fetch -q origin && git switch -q dev && git pull -q
diff <(git show afk-spec:docs/spec.md | sed 's/\[x\]/[ ]/g') <(sed 's/\[x\]/[ ]/g' docs/spec.md)
```
Any difference other than boxes → **stop and say so**. The spec has drifted: from then
on nothing judges the loop, it awards itself its own victory. It is a stop, not a
warning.
No `afk-spec` tag → the repo has not been through `/afk-spec`. Stop too.
## 1 — What is left
```bash
grep -n '^- \[ \]' docs/spec.md # the unchecked criteria
grep -n '^## Milestone' docs/spec.md
gh issue list --state open --json number,title,labels,milestone
```
The **current milestone** is the first one that still has an unchecked criterion. We
only work on that one. All checked in every milestone → **there is nothing to open**,
say so and stop: that is the loop's normal end.
## 2 — What the repo really contains
The spec says what we want; it does not say what exists. Before slicing:
```bash
git log --oneline afk-spec..dev | head -40
git diff --stat afk-spec..dev
```
A ticket written against an imagined repo goes looking for files that do not exist and
burns its session. That is the differen