How do I install the Whats Next skill?

Run npx skillmds@latest add luw2007/whats-next in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Whats Next safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Whats Next?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Whats Next free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Whats Next?

luw2007 (@luw2007) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Whats Next by luw2007 — Agent Skill

Name: Whats Next
Rating: 4.666666666666667 (3 reviews)
Author: luw2007

Whats Next

Re-orient the user after they return to a session — or after they open a FRESH context pointed at a worktree/branch — and let them decide the next step by answering lightweight questions through the host's structured-question tool (Yes/No, A/B/C/D) instead of facing a blank prompt. Trigger when the user invokes /whats-next (optionally naming a worktree, branch, or repo path), or asks "接下来做什么", "下一步是什么", "我该做什么", "这个 worktree/分支做到哪了、下一步呢", "what's next", "what should we do next", "帮我决定下一步", or returns after a long gap and wants to resume work with minimal typing. Works with zero conversation history: state is then rebuilt from git evidence (diffs, branch commits, uncommitted changes) and handoff/task docs. NOT for pure recap with no decision needed (that is a recap request — answer it directly or use a context-rebuild skill if available), and NOT for questions about a specific file or piece of code.

luw2007 Updated Sep 10, 2026

File contents

What's Next

The user runs many sessions in parallel and comes back after hours away. They cannot remember where this conversation stands. The job: rebuild the state FOR them, then hand them a small set of concrete, clickable decisions — never a blank prompt to fill in.

Match the language of the conversation.

Required reference

Read references/workflow.md before acting — it holds the full step-by-step (evidence source → state reconstruction → recap → fork points → optional external context → structured question → act) plus edge cases (nothing pending, external waits, cold-start worktree, substantive user-only decisions).

Workflow overview

Pick evidence — warm session: use conversation + a cheap git status/diff check. Cold start / named worktree/branch: rebuild entirely from git evidence and handoff docs.
Reconstruct state silently — DONE / IN FLIGHT / BLOCKED / PLANNED, each graded by evidence strength; never fabricate status for anything still running.
Recap in 3–5 lines, always leading with an explicit close-session verdict.
Identify real fork points — decisions that actually change what happens next, not already-decided or fake choices.
Optionally enrich with external context (PR/CI, issue tracker, running work) only when it would change an existing fork.
Ask via the host's structured-question tool — 1–3 questions, 2–4 concrete clickable options each, recommended option first.
Act immediately on the answer, no re-confirmation.

---name: whats-nextdescription: Re-orient the user after they return to a session — or after they open a FRESH context pointed at a worktree/branch — and let them decide the next step by answering lightweight questions through the host's structured-question tool (Yes/No, A/B/C/D) instead of facing a blank prompt. Trigger when the user invokes /whats-next (optionally naming a worktree, branch, or repo path), or asks "接下来做什么", "下一步是什么", "我该做什么", "这个 worktree/分支做到哪了、下一步呢", "what's next", "what should we do next", "帮我决定下一步", or returns after a long gap and wants to resume work with minimal typing. Works with zero conversation history: state is then rebuilt from git evidence (diffs, branch commits, uncommitted changes) and handoff/task docs. NOT for pure recap with no decision needed (that is a recap request — answer it directly or use a context-rebuild skill if available), and NOT for questions about a specific file or piece of code.license: MIT---# What's NextThe user runs many sessions in parallel and comes back after hours away. They cannotremember where this conversation stands. The job: rebuild the state FOR them, then handthem a small set of concrete, clickable decisions — never a blank prompt to fill in.Match the language of the conversation.## Required referenceRead [references/workflow.md](references/workflow.md) before acting — it holds the fullstep-by-step (evidence source → state reconstruction → recap → fork points → optionalexternal context → structured question → act) plus edge cases (nothing pending, externalwaits, cold-start worktree, substantive user-only decisions).## Workflow overview1. **Pick evidence** — warm session: use conversation + a cheap `git status`/diff check. Cold start / named worktree/branch: rebuild entirely from git evidence and handoff docs.2. **Reconstruct state silently** — DONE / IN FLIGHT / BLOCKED / PLANNED, each graded by evidence strength; never fabricate status for anything still running.3. **Recap in 3–5 lines**, always leading with an explicit close-session verdict.4. **Identify real fork points** — decisions that actually change what happens next, not already-decided or fake choices.5. **Optionally enrich with external context** (PR/CI, issue tracker, running work) only when it would change an existing fork.6. **Ask via the host's structured-question tool** — 1–3 questions, 2–4 concrete clickable options each, recommended option first.7. **Act immediately** on the answer, no re-confirmation.

Frequently asked questions