New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Os Whats Next

by kharmanskyi in kharmanskyi/open-steps

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.

MITAuto-check passedDevelopment

Install Os Whats Next

skills CLI
$ npx skills add kharmanskyi/open-steps --skill os-whats-next -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install kharmanskyi/open-steps os-whats-next --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/kharmanskyi/open-steps.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/os-whats-next .claude/skills/os-whats-next && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
os-whats-next
GitHub stars
1.3k
Token cost
~1.9k tokens
SKILL.md length
1,034 words
Files
2 (incl. references)
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 3 steps: read the state, quickest first → finish what is finished → sort what remains into two lists
  • Asks what to do next
  • SKILL.md covers Language, When to use, Step 1 - read the state,… and Step 2 - finish what is finished, plus 5 more sections
  • Calls gh and bash

What it does

Os Whats Next is an agent skill from kharmanskyi/open-steps. 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…

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/01-end-of-day.md`).

It sits in Development, covering Pull requests. The repository describes itself as: Plain-language agent skills for Claude Code, Codex, Cursor and Gemini CLI: honest session reports, straight verdicts, steps you can follow. MIT. The licence is MIT.

When your agent uses it

  • Asks what to do next
  • What is blocked - whats next
  • What should we work on
  • Anything I can do - in any language

Example prompts

  • “s next”
  • “what now”
  • “what should we work on”
  • “/os-whats-next”

Requirements

  • Pre-approved tools (allowed-tools): Read(~/.claude/open-steps/**), Bash(gh pr list *), Bash(gh pr view *), Bash(gh pr checks *), Bash(gh pr checks), Bash(gh pr diff *), Bash(gh pr diff), Bash(gh pr merge *)

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. read the state, quickest first
  2. finish what is finished
  3. sort what remains into two lists

What it can do on your machine

Read from SKILL.md and the folder at commit 4fa744b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read(~/.claude/open-steps/**)
    • Bash(gh pr list *)
    • Bash(gh pr view *)
    • Bash(gh pr checks *)
    • Bash(gh pr checks)
    • Bash(gh pr diff *)
    • Bash(gh pr diff)
    • Bash(gh pr merge *)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Os Whats Next loads about 1.9k tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 168 tokens; SKILL.md has 1,034 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~168
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from kharmanskyi/open-steps at commit 4fa744b, republished under its MIT licence (© kharmanskyi). 1,034 words, ~1,901 tokens.

Download SKILL.mdSave it as .claude/skills/os-whats-next/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
os-whats-next
description
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.
allowed-tools
Read(~/.claude/open-steps/**), Bash(gh pr list *), Bash(gh pr view *), Bash(gh pr checks *), Bash(gh pr checks), Bash(gh pr diff *), Bash(gh pr diff), Bash(gh pr merge *)

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 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.

    That file carries its own age: a measured date at the top and a date beside every stage. Never take a number out of it. Take only the "What is next" list, the "Worth retiring" rows, and each Stage with the date beside it. Before you put a "Worth retiring" row to the user, measure it again. From the project root, run bash <this skill's folder>/../os-big-picture/scripts/census.sh .. The . is the project, not the skill folder. If the script is missing or does not run, say so and call that row "not checked". When the stage dates are months behind the newest commit, say how old they are. Dates that stopped moving mean the reports stopped, not that the work did.

Say which sources you did not read: an unread source is not an empty source.

Step 2 - finish what is finished

A pull request with green checks and an approval is not a decision - it is unfinished business. Verify it through os-check-work's accept rules and merge it in this same pass. Two things stop the merge: a failed claim, and a task instruction that merges happen on command only - an orchestrator may own the merge. Report it as done, never as a question.

Step 3 - sort what remains into two lists

ListBelongs there when
I can do this aloneeverything needed is at hand: no decision, no secret, no approval, no device
Needs youa decision, an approval, a secret, a purchase, or a device only the user has

Blocked work gets no section of its own. Fold it into the reasoning, in plain words - "X waits on an outside check; I watch it" - the user trusts the recommendation, not the graph.

The shape - ten lines, like every report in this pack

<Lead: one sentence on where things stand - including what this pass merged.>

**I can do alone:** <up to three items, five words of why each>
**Needs you:** <up to three items, one line each - or drop the list>

**Next I take: <the one task> - <plain words: what it closes or unblocks>.**
<One line: what was not checked.>

When a quick small win and a big item are both real candidates, offer the choice through your tool's question picker where it has one (in Claude Code, AskUserQuestion). Give two to four options, the recommended one first and marked. Where there is no picker, write the same question and options as plain text, the recommended one first and marked. On the pick, prepare the launch: a prompt complete enough to paste or a command complete enough to run, and one line saying what comes out. Never run it yourself.

Show full SKILL.md (400 more words)Show less

How many at once

Before offering to start several, prove they will not collide - all three:

CheckThey collide when
Same filesboth touch the same files, module, or migration sequence
Same shared resourceone working copy, branch, database, container project, port
One feeds the otherthe second needs the first one's output

Any check failing → one at a time, saying which failed. All passing → say so. Never claim parallel safety you did not verify - "I did not check" is honest; a collision discovered mid-run is not. Where the project isolates parallel work - a working copy per task, separate container projects or ports - name that as the precondition instead of assuming it.

Hard rules

  1. Three items per list, maximum - more → say how many were left out and on what basis you chose.
  2. Every item names its source - the report, a pull request, a backlog entry, a failing check. Your own idea is marked a suggestion, and lists are never padded: two real items beat five with filler.
  3. One recommendation, always - even when offering the small-versus-big choice, one option carries the mark and one line of plain-words reasoning.
  4. Finish, then prepare - never start. Merging a verified-ready pull request is finishing. New work is prepared as a ready-to-run launch and waits for the pick.
  5. Say what you did not check - especially the backlog. Silence reads as "nothing there".
  6. Plain words - no engineering identifiers except where they name an action.

Known gotchas

  • Deferred-until-Monday is not a task on Saturday: do not re-propose it early.
  • A stale tracker is worse than none - say when you read it. The same is true of the map, and it hides it better: its measured columns refresh themselves while the stages behind them age.
  • A draft pull request is unfinished work, not a merge to put to the user. If the session that opened it has ended, the draft goes in the I-can-do-alone list. If another session still works on it, leave it to that session and say so.
  • A quiet feature in the map is not a task. It is quiet because it is finished; the skill that wrote it already checked that something still uses it.
  • A needs-you pick goes to os-step-by-step, never explained inline.
  • "Ready to merge" is still a claim: the verify step is what makes it true - skipping it to move faster is how wrong work lands.

© kharmanskyi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/os-whats-next of kharmanskyi/open-steps.

  • SKILL.md
  • references/01-end-of-day.md

Open the folder on GitHubat commit 4fa744b

Compare with similar skills

Os Whats Next next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Os Whats Next compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Os Whats Next this skillkharmanskyi/open-steps1.3k—~1.9kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands91k—~2.4kAutomated safety check: PassMIT
WooCommerce Code Reviewwoocommerce/woocommerce11k3 repos~1.1kAutomated safety check: PassCustom licence

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    91k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Record PR Demo

    payloadcms/payload

    A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.

    45k GitHub stars~1k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from kharmanskyi/open-steps

  • Os Big Picture

    kharmanskyi/open-steps

    ALWAYS invoke this skill when the user asks where the project as a whole stands - "where are we", "what's the big picture", "what have we built", "what is in this project", "map the project", "what…

    1.3k GitHub stars~1.9k tokensUpdated 5 days ago
    Auto-check passed

  • Os Ask Simple

    kharmanskyi/open-steps

    ALWAYS invoke this skill before asking the user any technical question or offering options, and whenever they ask to be asked in plain words - "ask simple", "ask me simply", "ask me in plain words"…

    1.3k GitHub stars~1.4k tokensUpdated 5 days ago
    Auto-check passed

  • Os Check Work

    kharmanskyi/open-steps

    ALWAYS invoke this skill when the user asks about work done outside this session - "check work", "check the others", "check other sessions" - or to accept one: "the session is done, check it", "can…

    1.3k GitHub stars~1.9k tokensUpdated 5 days ago
    Auto-check passed

  • Os Done Or Not

    kharmanskyi/open-steps

    ALWAYS invoke this skill when work wraps up or the user asks how it went - "done or not", "are we done", "what happened", "report", "what's the status of this ticket" - in any language, and when a…

    1.3k GitHub stars~1.8k tokensUpdated 5 days ago
    Auto-check passed

  • Os Say Simple

    kharmanskyi/open-steps

    ALWAYS invoke this skill when the user asks for simpler or shorter about something said or written - "say it simply", "what does this mean", "I don't understand your answer", "too long", "wait…

    1.3k GitHub stars~1.3k tokensUpdated 5 days ago
    Auto-check passed

  • Os Step By Step

    kharmanskyi/open-steps

    ALWAYS invoke this skill when you need the user to act - run a command, paste a secret, click, approve - and whenever they ask how to do something or say they do not know what to do: "step by step"…

    1.3k GitHub stars~1.9k tokensUpdated 5 days ago
    Auto-check passed

Categories

Questions about Os Whats Next

What does Os Whats Next do?

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. Os Whats Next is an agent skill from kharmanskyi/open-steps. 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.

When should I use Os Whats Next?

Os Whats Next fits situations like: asks what to do next; what is blocked - whats next; what should we work on; anything I can do - in any language.

How do I install Os Whats Next in Claude Code?

Run `npx skills add kharmanskyi/open-steps --skill os-whats-next -a claude-code`. Or copy the skill folder (skills/os-whats-next in kharmanskyi/open-steps) into .claude/skills/os-whats-next in your project. Claude Code loads it when a task matches its description.

How do I install Os Whats Next in Codex?

Run `npx skills add kharmanskyi/open-steps --skill os-whats-next -a codex`. Or copy the skill folder (skills/os-whats-next in kharmanskyi/open-steps) into .agents/skills/os-whats-next in your project. Codex loads it when a task matches its description.

Can I use Os Whats Next in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add kharmanskyi/open-steps --skill os-whats-next -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/os-whats-next, .gemini/skills/os-whats-next, .github/skills/os-whats-next and .opencode/skills/os-whats-next in your project.

What does Os Whats Next need to run?

Going by SKILL.md and its folder, Os Whats Next needs the command-line tools its instructions call (gh and bash). Its frontmatter pre-approves these tools: Read(~/.claude/open-steps/**), Bash(gh pr list *), Bash(gh pr view *), Bash(gh pr checks *), Bash(gh pr checks), Bash(gh pr diff *), Bash(gh pr diff), Bash(gh pr merge *).

Does Os Whats Next access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Os Whats Next safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Os Whats Next use?

Os Whats Next is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Os Whats Next use?

About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 638 tokens, read only when the agent opens those files.

What are the alternatives to Os Whats Next?

Skills that share tags, products or a category with Os Whats Next: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 91k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Os Whats Next?

kharmanskyi (a GitHub user) maintains it in kharmanskyi/open-steps, which has 1,279 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 5, 2026.

Source: kharmanskyi/open-steps on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.