session-nextlisted
Install: claude install-skill matshoppenbrouwers/session-flow
# Session Next
Pick up and execute the next ready task from the sequence backlog.
**Announce:** "Using session-next to implement the next task from the sequence."
## Non-Negotiables
1. **Only execute entries with a valid linked breakdown.** An entry marked `(needs breakdown)` or with a dangling link is not ready. Skip it and offer `/session-groom`.
2. **Mark `[x]` on completion.** Always update the entry in `SEQUENCE.md`. For a per-task breakdown, also set `**Status**: [x]` in the file. (A phase-file anchor has no per-task `**Status**` line — `/session-delegation` marks the phase tasks `[x]`; you just close the entry.) Do not batch — a backlog reader must see live state.
3. **Respect order and priority.** Pick the topmost open entry; among equals, prefer lower P-number (P1 before P3). At equal priority, a manual entry outranks one marked `[auto]` — a bot's enqueue never jumps ahead of what the user asked for. Don't cherry-pick the easy one.
4. **Hand off multi-task breakdowns.** If the link points to a `session-task-planning` phase file, dispatch via `/session-delegation` — do not try to do a whole phase as one task.
5. **One task per invocation unless told otherwise.** Finish, report, and suggest the next. Don't silently churn through the whole backlog.
## Path Resolution
1. Read `.session-flow.json` for `paths.sequence`, `paths.tasks`, `paths.todo`.
2. If missing, detect `{todo}/SEQUENCE.md` and `{todo}/tasks/`.
3. If no sequence file exists, say so and suggest `/sess