Os Whats Next
ALWAYS invoke this skill when the user asks what to do next, what is left, or what is...
Install
npx skills add kharmanskyi/open-steps --skill os-whats-next -g -a claude-code -y- Repository
- kharmanskyi/open-steps1.3k
- Category
- Engineering
- Updated
- 1mo ago
- License
- MIT
- Context cost
- Mediumabout 1,663 tokens
- Runs scripts
- No, instructions only
What it does
ALWAYS invoke this skill when the user asks what to do next, what is left, or what is blocked - "what's next", "what now", "what should we work on", "anything I can do" - in any language. This skill picks the next piece of work; when the user asks HOW to do a thing or says they do not understand what to do, that is os-step-by-step. Reads the last report, local changes, open pull requests and always the backlog. First finishes what is finished: verified-ready pull requests merge in the same pass. Then sorts the rest into doable-alone and needs-you, ending with one recommended next task in plain words - what it closes or unblocks. Never invents tasks.
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.
-
The last report -
~/.claude/open-steps/reports/<project>/latest.md: a handover written for exactly this moment. -
Local state - uncommitted changes, unpushed commits, current branch.
-
Open pull requests - one call:
gh pr list --json number,title,mergeStateStatus,reviewDecision,isDraft. -
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-picturekeeps 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 inventing work, which rule 4 below forbids. A row under "Worth retiring" is a real candidate, but it is a decision to put to the user, never a task to start.
