Agent skill

Whats Next

by petarzarkov in petarzarkov/dunx

Write or refresh HANDOFF.md - a compact resume point holding completed objectives, live file paths, approaches already tried and rejected, and the exact next steps, placed against the roadmap in…

MITAuto-check passedAgent Workflows

Install Whats Next

skills CLI
$ npx skills add petarzarkov/dunx --skill whats-next -a claude-code

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

GitHub CLI
$ gh skill install petarzarkov/dunx 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/petarzarkov/dunx.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/whats-next .claude/skills/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
whats-next
GitHub stars
100
Token cost
~819 tokens
SKILL.md length
369 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Write or refresh HANDOFF.md - a compact resume point holding completed objectives, live file paths, approaches already tried and rejected, and the exact next steps, placed against the roadmap in…

  • Tasks that involve Context engineering
  • SKILL.md covers Gather, Write, Rules and After writing
  • Calls git

What it does

Whats Next is an agent skill from petarzarkov/dunx. Write or refresh HANDOFF.md - a compact resume point holding completed objectives, live file paths, approaches already tried and rejected, and the exact next steps, placed against the roadmap in docs/ROADMAP.md. Use before /compact or /clear, at the end of a task block, when the context window crosses ~50%, or when asked "what's next", "where were we", "hand this off", or "resume".

Its SKILL.md is about 820 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Context engineering. The repository describes itself as: fastest web DI framework. NestJS-style structure at Bun speed. Constructor DI with no reflect-metadata, no experimentalDecorators, no JavaScript router. The licence is MIT.

When your agent uses it

  • Tasks that involve Context engineering

Example prompts

  • “s next”
  • “where were we”
  • “hand this off”
  • “/whats-next”

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

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

  • Network

    No URLs in SKILL.md. Its commands use git, 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

Whats Next loads about 819 tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 369 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~99
When it runs · the whole SKILL.md, loaded when a task matches
~819

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 petarzarkov/dunx at commit d8be36b, republished under its MIT licence (© petarzarkov). 369 words, ~819 tokens.

Download SKILL.mdSave it as .claude/skills/whats-next/SKILL.md (or your agent's skills folder).
name
whats-next
description
Write or refresh HANDOFF.md - a compact resume point holding completed objectives, live file paths, approaches already tried and rejected, and the exact next steps, placed against the roadmap in docs/ROADMAP.md. Use before /compact or /clear, at the end of a task block, when the context window crosses ~50%, or when asked "what's next", "where were we", "hand this off", or "resume".

/whats-next

Produce HANDOFF.md at the repo root: everything needed to resume this work in a fresh session and nothing else. It will be read cold, by a session with no memory of this one. Optimise for that reader, not for a record of what happened.

Gather

One batch, then stop:

bash
git status --short && git log --oneline -8

Read the Open items section of docs/ROADMAP.md and the file under internal/notes/roadmap/ for the item in hand, when its row links one. That is the source of truth for what "next" means. Never invent a roadmap position from the conversation.

Add what only this session knows: what you actually changed, and what you tried that did not work.

If the session is thin on state - resumed, compacted, or you were handed a HANDOFF.md rather than doing the work - do not read packages into this thread to fill the gaps. Delegate one Explore subagent per unresolved question and ask each for a one-line verdict plus file:line. The exploration stays in their context window; only the verdict comes back.

Write

Overwrite HANDOFF.md with this shape. Omit a section that has no content - never write "N/A" or "none".

markdown
# HANDOFF - <YYYY-MM-DD>

**Roadmap:** <open item> - <what remains of it>
**Branch:** <branch> @ <short sha> · <clean | n files dirty>

## Done

- <objective> - <where it landed>

## Live files

- [path](path) - <what is half-finished in it>

## Rejected - do not retry

- <approach> - <what broke>

## Next

1. <exact command, or exact edit to an exact path>

## Open questions

- <question> - <what decides it>
Show full SKILL.md (184 more words)Show less

Rules

  • Hard cap ~60 lines. This file is loaded at the start of the next session. Every line is a permanent tax on it.
  • Next steps are commands and edits, not intentions. "Add token() and inject() to packages/core/src/di/, resolving through a module-level currentInjector set around each new Klass()" - not "continue DI work".
  • Rejected is the highest-value section. It is the only content a fresh session cannot re-derive from the tree. Record the approach, the symptom, and the path it lives or lived in. Rejections already written down in docs/architecture/ belong there, not here - link, don't copy.
  • Paths as clickable relative markdown links.
  • If an open item has been delivered, say so. If docs/ROADMAP.md is stale, fix that doc - do not record the drift in HANDOFF.md.
  • No conversation summary, no restatement of the plan, no preamble.

After writing

State the path and the roadmap position in one line, then name the next move:

  • same subtask, context heavy → /compact, and say explicitly what to preserve
  • switching subtask → /clear, then continue from HANDOFF.md

HANDOFF.md is gitignored. It is session state, not a repo artifact - rewrite it freely.

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

Files

Just SKILL.md in .claude/skills/whats-next of petarzarkov/dunx.

Open the folder on GitHubat commit d8be36b

Compare with similar skills

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.

Whats Next compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Whats Next this skillpetarzarkov/dunx100—~819Automated safety check: PassMIT
Context Mode Output Sandboxmksglu/context-mode26k—~4.1kAutomated safety check: PassCustom licence
Memori Long-Term MemoryMemoriLabs/Memori17k—~2kAutomated safety check: NotesCustom licence
Picoclaw Skill Creatorsipeed/picoclaw30k—~4.4kAutomated safety check: PassMIT
Context Mode for Antigravity CLImksglu/context-mode26k—~850Automated safety check: PassCustom licence
ccc Semantic Code Searchcocoindex-io/cocoindex-code2.8k—~938Automated safety check: PassApache-2.0

Similar skills

  • Context Mode Output Sandbox

    mksglu/context-mode

    Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.

    26k GitHub stars~4.1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Memori Long-Term Memory

    MemoriLabs/Memori

    Connects Claude Code to Memori Cloud for long-term memory, recalling stored context before substantive replies and saving new context afterward.

    17k GitHub stars~2k tokensUpdated 8 days ago
    Agent WorkflowsAuto-check: notes
  • Picoclaw Skill Creator

    sipeed/picoclaw

    Guidance for creating, updating and reviewing Picoclaw skills, from the SKILL.md structure to organizing bundled scripts, references and assets.

    30k GitHub stars~4.4k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Routing rules for using context-mode MCP tools in Antigravity CLI: sandboxed code runs, file analysis, indexed search and web fetches that keep large output out of the conversation.

    26k GitHub stars~850 tokensUpdated today
    Agent WorkflowsAuto-check passed
  • ccc Semantic Code Search

    cocoindex-io/cocoindex-code

    Semantic code search and index management with the ccc CLI: the agent initializes, indexes and queries the project by concept, filtering by language or path.

    2.8k GitHub stars~938 tokensUpdated 4 days ago
    Agent WorkflowsAuto-check passed
  • Token Optimizer

    alexgreensh/token-optimizer

    Audits a Claude Code or Codex setup for context-window waste, fixes it with the user's approval, and measures the saving.

    2.5k GitHub stars~2.4k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from petarzarkov/dunx

  • Docs Pass

    petarzarkov/dunx

    Revise one documentation file so it states facts instead of performing insight, and get it under the budgets in scripts/no-slop.test.ts.

    100 GitHub stars~1.5k tokensUpdated 3 days ago
    Auto-check passed
  • New Package

    petarzarkov/dunx

    Add a workspace to the dunx monorepo - a published package under packages/, a published CLI under tools/, a private workspace under internal/, or an example under examples/ - with correct manifest…

    100 GitHub stars~1.5k tokensUpdated 3 days ago
    Auto-check passed
  • Release

    petarzarkov/dunx

    Version and publish @dunx/ packages to npm. An agent skill from petarzarkov/dunx.

    100 GitHub stars~2.4k tokensUpdated 3 days ago
    Auto-check passed
  • Spike

    petarzarkov/dunx

    Resolve an open technical question by measuring it on real Bun instead of assuming, then record the verified result in docs/architecture/constraints.md.

    100 GitHub stars~742 tokensUpdated 3 days ago
    Auto-check passed
  • Coverage Report

    petarzarkov/dunx

    Regenerate the coverage report and badges, or diagnose a wrong percentage, a 404ing badge, or a package showing 0%.

    100 GitHub stars~971 tokensUpdated 3 days ago
    Auto-check passed

Categories

Questions about Whats Next

What does Whats Next do?

Write or refresh HANDOFF.md - a compact resume point holding completed objectives, live file paths, approaches already tried and rejected, and the exact next steps, placed against the roadmap in…. Whats Next is an agent skill from petarzarkov/dunx.md.

When should I use Whats Next?

Whats Next fits situations like: tasks that involve Context engineering.

How do I install Whats Next in Claude Code?

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

How do I install Whats Next in Codex?

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

Can I use 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 petarzarkov/dunx --skill 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/whats-next, .gemini/skills/whats-next, .github/skills/whats-next and .opencode/skills/whats-next in your project.

What does Whats Next need to run?

Going by SKILL.md and its folder, Whats Next needs the command-line tools its instructions call (git).

Does Whats Next access the network?

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

Is 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 Whats Next use?

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 Whats Next use?

About 819 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Whats Next?

Skills that share tags, products or a category with Whats Next: Context Mode Output Sandbox (mksglu/context-mode, 26k stars), Memori Long-Term Memory (MemoriLabs/Memori, 17k stars), Picoclaw Skill Creator (sipeed/picoclaw, 30k stars) and Context Mode for Antigravity CLI (mksglu/context-mode, 26k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Whats Next?

petarzarkov (a GitHub user) maintains it in petarzarkov/dunx, which has 100 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 8, 2026.

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