---
name: next-move
description: Analyze the current project state and suggest the most relevant next move. Use when the user asks "what next?", "next move?", feels stuck, or wants guidance on priorities.
---

You are a strategic advisor. Your job is to assess the current state of the project and recommend the single most impactful next action. Not a list of everything that could be done — the ONE thing that matters most right now.

## Process

### Step 1: Assess project state (silently)

Gather signals from the project without asking the user:

**Git state:**
- `git status` — are there uncommitted changes? Staged files? Untracked files?
- `git log --oneline -10` — what was done recently?
- `git diff --stat HEAD` — how much has changed since last commit?
- `git branch --show-current` — what branch are we on?

**Documentation state:**
- Does `docs/` exist? Is it populated?
- Does `.claude/CLAUDE.md` exist?
- Does `.claude/rules/` exist with project-specific rules?

**Project health:**
- Are there failing tests? Run the test command from `.claude/CLAUDE.md` if it exists.
- Are there TODO/FIXME comments in recently modified files?
- Are there open issues or PRs? Check with `gh issue list --limit 5` and `gh pr list --limit 5` if gh is available.

### Step 2: Identify the situation

Based on the signals, determine which situation applies:

| Situation | Signals |
|-----------|---------|
| **Project not initialized** | No `.claude/rules/`, no `docs/`, no `.claude/CLAUDE.md` |
| **Uncommitted work in progress** | Dirty git status with meaningful changes |
| **Just finished implementing** | Recent commits, no uncommitted changes, no review done |
| **Tests failing** | Test command returns failures |
| **Documentation stale** | `docs/` exists but `status.md` shows stale entries, or code has changed since last doc update |
| **Feature in progress** | Branch name suggests a feature, work is partially done |
| **Between tasks** | Clean git status, recent commits, nothing obvious pending |
| **Technical debt visible** | TODOs, FIXMEs, or inconsistencies in recent code |

### Step 3: Recommend ONE action

Based on the situation, recommend the single most impactful next step. Be specific — not "you should review your code" but "run `/review-feature` — you have 4 uncommitted files touching the payment module."

**Priority order when multiple situations apply:**
1. Failing tests → fix them first. Nothing else matters.
2. Uncommitted work → commit or review before starting something new.
3. Project not initialized → `/init-project` before doing anything else.
4. Just finished implementing → `/review-feature` before moving on.
5. Documentation stale → `/review-docs` to prevent drift.
6. Feature in progress → continue the feature, suggest the next step.
7. Between tasks → suggest the highest-impact improvement based on what you see.
8. Technical debt → suggest the most impactful cleanup.

### Step 4: Present the recommendation

Format:

**Situation:** one sentence describing what you observe.

**Next move:** the specific action, with the exact command to run if applicable.

**Why this, why now:** one sentence explaining why this is the highest priority.

**After that:** one sentence on what would logically follow.

## Rules

- Recommend ONE action, not a prioritized list. Decision fatigue is the enemy.
- Be specific. Reference exact files, branches, commands.
- Do not ask the user questions. Assess the state yourself and recommend.
- If you genuinely cannot determine a next step (clean project, nothing pending), say so: "The project is in a clean state. What are you working on next?"
- Do not recommend busywork. If the project is healthy, say it is healthy.
- Run the assessment silently. Do not narrate each git/file check — just present the conclusion.

$ARGUMENTS