A Claude Code plugin. It changes how Claude's reply to you ends: instead of a long report at the end, it finishes with a short report and a question/suggestion you respond to by selecting one of two to four options.

By kvit. Free and MIT licensed — read why a reply should end with a choice.

When Claude finishes a piece of work, the thing you have to act on — do this next, or answer that, or it stopped because of this — sits inside prose. You read the paragraph, then type "what's next" or "continue", and pay for another round trip to get back to where the work was already pointing.

Claude Code already has the right widget for this: the AskUserQuestion tool

draws a card of labelled options, keyboard-selectable, with free text always

available. This plugin makes that call the way a reply that

changed something ends, and checks that it happened.

A reply is everything Claude does between your message and the moment it stops and waits for you. Along the way it may read twenty files, run the tests and make a dozen edits, and none of those steps ends the reply. The card appears once, at that final stop, in place of the closing report Claude would have written anyway. Nothing is added between tool calls. A reply that only read files and answered a question ends in ordinary prose, with no card.

/plugin marketplace add https://github.com/kvitapp/kvit-plugins.git

/plugin install whats-next@kvit

That is all. The next session starts with the convention in force, and removing the plugin removes it.

Installing copies the plugin's files into

~/.claude/plugins/cache/<marketplace>/whats-next/<version>/, and that

copy stays at the commit it was taken from until it is updated. On a machine

where the plugin is already installed, two commands bring it up to date:

claude plugin marketplace update kvit

claude plugin update whats-next@kvit

Reordering works and survives a restart.

- Moved the reorder logic into

internal/order, hidden rows keep their slots.- Tests:

go test ./internal/order— 14/14 pass.

followed by a card:

Reordering works, 14/14 tests pass. How to proceed? [Next]

-> Commit (Recommended) Commit the reorder implementation now.

Changelog too Add the changelog entry, then commit.

Stop here Leave it uncommitted; nothing more runs.

Picking an option resumes the session.

Each of these can be set in the environment, in an env block in a project's

.claude/settings.json, or in ~/.whats-next/config.json for a machine-wide

answer that does not belong to any one agent:

{ "REPORT_GATE": "off" }MIT. See LICENSE.