| name | refocus |
| description | Refresh the plan to focus on the task at hand. Use when context grew, completed steps muddy it, or you want to clear context and continue in auto mode. |
| args | [focus directive (optional free text)] |
| argument-hint | [optional: what to focus on, e.g. 'the API layer, ignore docs work'] |
| allowed-tools | Read, Grep, Glob, Bash(git status *), Bash(git log *), Bash(git diff *), TodoWrite, ExitPlanMode |
| created | "2026-06-08T00:00:00.000Z" |
| modified | "2026-06-15T00:00:00.000Z" |
| reviewed | "2026-06-15T00:00:00.000Z" |
/project:refocus
Refresh the plan so it focuses only on the task that remains, then surface it for approval so the user can clear context and continue in auto mode from a clean slate.
When to Use This Skill
| Use this skill when... | Use the alternative when... |
|---|
| Context has grown and the completed early steps now muddy it | Resuming after a break with no live context to trim → /project:continue |
| You want a tightened, forward-only plan before continuing | Capturing session learnings into rules/recipes → /project:distill |
| You want to clear context and continue in auto mode without losing the thread | Entering an unfamiliar codebase needing orientation → /project:discovery |
| The user says "refresh the plan", "refocus", "let's focus on what's left", "trim the context" | Picking the next blueprint action → /blueprint:execute |
The output is deliberately self-contained: it must survive a context clear. Approving it from the ExitPlanMode dialog is where Claude Code offers "clear context and continue in auto mode."
Context
- Current branch: !
git branch --show-current
- Working tree: !
git status --porcelain=v2 --branch
- Recent commits: !
git log --format='%h %s' --max-count=8
- Active todos: review the current TodoWrite list (if any) for done-vs-remaining state
Parameters
Parse $ARGUMENTS as an optional free-text focus directive that biases what
counts as Remaining vs Stale and what the Objective emphasizes (e.g. "focus on
the API layer, ignore the docs work").
- No directive → behave deterministically from conversation + git as today; do not invent a focus.
- Directive given → treat it as steering, not override. It re-weights the bucketing and phrasing; it does not cancel a genuine in-flight boundary the user set earlier ("don't push until I review", "keep the old endpoint"). When a directive appears to contradict a live boundary, keep the boundary and note the tension in the plan rather than silently dropping it.
Execution
Execute this plan-refresh workflow. Reason over the , not just git — git grounds what landed on disk; the conversation holds the decisions and the remaining intent.
