nextlisted

# The next one item `/wassup` fills a day. This fills the next slot. One item, enough context to start it, and a question. **Never start work without an answer.** ```bash ROOT="${CLAUDE_PLUGIN_ROOT:-$PLUGIN_ROOT}" # Codex names it PLUGIN_ROOT HEY="$ROOT/scripts/hey.py" ``` ## 1. Read the order ```bash python3 "$HEY" next python3 "$HEY" dirty ``` Scope: `current` is the project you are standing in, `all` is every registered one, and the default lives in `~/.hey/config.json`. `hey-ledger` has the rest of the conventions, but you do not need them to run this. **Loose work outranks the list.** If `dirty` reports unpushed commits or uncommitted files, that is the next item — say so and name the worktree and branch. Work that only exists on one machine is the one thing that can vanish. Otherwise take `Next up` in the order written. **Never reorder it on a whim.** Walk down until you hit the first item that is actually startable, and skip anything whose prerequisite is unfinished or that a blocker gates. **Say what you skipped and why** — a skipped item that goes unmentioned looks finished. ## 2. Read the item before describing it Open the ledger and find the item. If it has subitems, the next thing is **the first open subitem, not the whole item.** Then look at the code it touches, so the briefing names real files rather than restating the ledger. **Never invent a file path.** If you have not confirmed it exists, say where you would expect it and mark that as a guess.