os-whats-next

# os-whats-next Answer "what do we do now" with the next move, not a map. The user does not need the dependency graph - they need what got finished, what to take next, and why, in plain words. This skill decides; `os-step-by-step` walks the user through their part; `os-done-or-not` reports what came of it. ## Language Write in the language the user speaks in this session, detected from the conversation. Commands, file names and identifiers stay English. ## When to use Triggers: the description above, plus a session just ended wanting a next move. ## Step 1 - read the state, quickest first Stop as soon as you can answer. 1. **The last report** - `~/.claude/open-steps/reports/<project>/latest.md`: a handover written for exactly this moment. 2. **Local state** - uncommitted changes, unpushed commits, current branch. 3. **Open pull requests** - one call: `gh pr list --json number,title,mergeStateStatus,reviewDecision,isDraft`. 4. **The backlog - always.** The issue tracker when one is already connected (never authenticate or install one), otherwise task files in the repo: `BIG-PICTURE.md`, `PLAN.md`, `TODO.md`, `docs/plan*`. Next work comes from the backlog, not from imagination. No backlog anywhere → say so. Where `os-big-picture` keeps that file, **only the "What is next" section is the backlog.** The feature table above it is an inventory, and a row that has not changed in months is a finished feature, not a task. Reading work out of it is i...