Skip to main content
command CX Codex

whats-next · glittercowboy — Claude Code command: what it does, how to install

whats-next analyzes the current conversation and writes a detailed handoff document to resume work in a fresh context.

MIT ★ 1,988 updated 2026-04-01

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add glittercowboy/taches-cc-resources
/plugin install taches-cc-resources@taches-cc-resources
Open on GitHub

What whats-next does

The command scans everything discussed in the active session and compiles a transfer document into whats-next.md. It records the initial objective, completed work with specific file paths and tool runs, failed attempts, and the remaining checklist with ordering requirements.

The output organizes findings under dedicated tags: <original_task>, <work_completed>, <work_remaining>, <attempted_approaches>, <critical_context>, and <current_state>. The prompt prioritizes thoroughness over brevity so that a fresh agent instance picks up the exact state without losing edge cases or temporary workarounds. To inspect context and compile files, it relies on Read, Write, Bash, WebSearch, and WebFetch.

The generated document writes directly to whats-next.md in your current working directory, meaning an existing file with the same name will be overwritten.

What it helps with

  • preserve session context before resetting Claude Code
  • document dead ends and errors to avoid repeating failed approaches
  • outline remaining tasks with strict dependencies and targets
  • record architectural decisions and temporary workarounds in markdown

Example prompts for the agent

  • /whats-next
  • /whats-next create a handoff document for the next session
  • /whats-next summarize current state and remaining tasks

How to install whats-next

1Plugin marketplace

/plugin marketplace add glittercowboy/taches-cc-resources
/plugin install taches-cc-resources@taches-cc-resources

2Manually: put the files in place

.claude/commands/whats-next.md

Call it with /whats-next. For all projects use ~/.claude/commands/

Questions about whats-next

How to install whats-next in Claude Code?

Add the marketplace source with /plugin marketplace add glittercowboy/taches-cc-resources, then run /plugin install taches-cc-resources@taches-cc-resources.

What does whats-next do?

It inspects your session history and compiles a structured handoff document into whats-next.md to restart work cleanly.

Where does whats-next save its output?

The command writes directly to whats-next.md inside your current working directory using XML tags for each section.

Source text

whats-next.md · MIT
---
name: whats-next
description: Analyze the current conversation and create a handoff document for continuing this work in a fresh context
allowed-tools:
  - Read
  - Write
  - Bash
  - WebSearch
  - WebFetch
---

Create a comprehensive, detailed handoff document that captures all context from the current conversation. This allows continuing the work in a fresh context with complete precision.

## Instructions

**PRIORITY: Comprehensive detail and precision over brevity.** The goal is to enable someone (or a fresh Claude instance) to pick up exactly where you left off with zero information loss.

Adapt the level of detail to the task type (coding, research, analysis, writing, configuration, etc.) but maintain comprehensive coverage:

1. **Original Task**: Identify what was initially requested (not new scope or side tasks)

2. **Work Completed**: Document everything accomplished in detail
   - All artifacts created, modified, or analyzed (files, documents, research findings, etc.)
   - Specific changes made (code with line numbers, content written, data analyzed, etc.)
   - Actions taken (commands run, APIs called, searches performed, tools used, etc.)
   - Findings discovered (insights, patterns, answers, data points, etc.)
   - Decisions made and the reasoning behind them

3. **Work Remaining**: Specify exactly what still needs to be done
   - Break down remaining work into specific, actionable steps
   - Include precise locations, references, or targets (file paths, URLs, data sources, etc.)
   - Note dependencies, prerequisites, or ordering requirements
   - Specify validation or verification steps needed

4. **Attempted Approaches**: Capture everything tried, including failures
   - Approaches that didn't work and why they failed
   - Errors encountered, blockers hit, or limitations discovered
   - Dead ends to avoid repeating
   - Alternative approaches considered but not pursued

5. **Critical Context**: Preserve all essential knowledge
   - Key decisions and trade-offs considered
   - Constraints, requirements, or boundaries
   - Important discoveries, gotchas, edge cases, or non-obvious behaviors
   - Relevant environment, configuration, or setup details
   - Assumptions made that need validation
   - References to documentation, sources, or resources consulted

6. **Current State**: Document the exact current state
   - Status of deliverables (complete, in-progress, not started)
   - What's committed, saved, or finalized vs. what's temporary or draft
   - Any temporary changes, workarounds, or open questions
   - Current position in the workflow or process

Write to `whats-next.md` in the current working directory using the format below.

## Output Format

```xml
<original_task>
[The specific task that was initially requested - be precise about scope]
</original_task>

<work_completed>
[Comprehensive detail of everything accomplished:
- Artifacts created/modified/analyzed (with specific references)
- Specific changes, additions, or findings (with details and locations)
- Actions taken (commands, searches, API calls, tool usage, etc.)
- Key discoveries or insights
- Decisions made and reasoning
- Side tasks completed]
</work_completed>

<work_remaining>
[Detailed breakdown of what needs to be done:
- Specific tasks with precise locations or references
- Exact targets to create, modify, or analyze
- Dependencies and ordering
- Validation or verification steps needed]
</work_remaining>

<attempted_approaches>
[Everything tried, including failures:
- Approaches that didn't work and why
- Errors, blockers, or limitations encountered
- Dead ends to avoid
- Alternative approaches considered but not pursued]
</attempted_approaches>

<critical_context>
[All essential knowledge for continuing:
- Key decisions and trade-offs
- Constraints, requirements, or boundaries
- Important discoveries, gotcas, or edge cases
- Environment, configuration, or setup details
- Assumptions requiring validation
- References to documentation, sources, or resources]
</critical_context>

<current_state>
[Exact state of the work:
- Status of deliverables (complete/in-progress/not started)
- What's finalized vs. what's temporary or draft
- Temporary changes or workarounds in place
- Current position in workflow or process
- Any open questions or pending decisions]
</current_state>
```

© Lex Christopherson · MIT · glittercowboy/taches-cc-resources

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

whats-next by other authors comes first.

From the same set48

The whole set →
check-todos check-todos — a command to view outstanding tasks from TO-DOS.md and pick one to work on. Streamlines task selection by matching work to project workflows and inviting the right skill if available. CX Codex +1 ★ 1,988repo stars add-to-todos add-to-todos appends tasks to TO-DOS.md with conversation context, file references, and line numbers without derailing ongoing work. CX Codex +1 ★ 1,988repo stars ask-me-questions ask-me-questions is a Claude Code command that gathers requirements before a task begins. It asks about missing details and waits for the user to approve execution. CX Codex +1 ★ 1,988repo stars heal-skill heal-skill — a command to update skill documentation based on errors discovered during execution. Shows proposed changes, waits for approval, then applies edits with optional commit. CX Codex +1 ★ 1,988repo stars the-pirate-bay Search The Pirate Bay through its JSON API and retrieve magnet links. Use it to find torrents, browse popular uploads, or check seed counts. CX Codex +1 ★ 1,988repo stars setup-ralph setup-ralph lays out Geoffrey Huntley's Ralph Wiggum loop in a directory: file structure, planning and build prompts, and gates that reject bad work. CX Codex +1 ★ 1,988repo stars run-plan run-plan executes a PLAN.md file directly without loading planner skill overhead. It routes tasks to subagents and keeps most of the context window free. CX Codex +1 ★ 1,988repo stars build-macos-apps build-macos-apps is a Claude Code skill for building native macOS apps with SwiftUI and AppKit. It routes work on new apps, bugs, tests, performance, and releases to a matching workflow. CX Codex +1 ★ 1,988repo stars

Project sponsors

Companies that keep this analytics open