---
name: status
description: Re-orient at the start of a session, answer "what is this project, where did we leave off, and what's next" from CLAUDE.md, PROJECT_PLAN.md, and recent git history, and flag stale docs. Use when the user asks "where are we", "what's next", "remind me what this project is", "how is it proceeding", "summarise where we've got to", or opens a session cold. Read-only, changes nothing. Invoke as /status.
---

# Project status: session re-orientation

Answer three questions fast: **what is this project, where did we leave off, and what's next.** READ-ONLY: never modify code, docs, or git state.

## Step 1: Gather (quick, parallel)

From the current project root (if run outside a project, ask which project):

1. **CLAUDE.md**: the What-this-is / overview section, any current-state block or Next Steps / Open items section, and the People & comms / Business context sections if present. (A "Recent Updates" section here is the legacy shape; read it only if the project has no dated plan entries.)
2. **PROJECT_PLAN.md / project_plan.md**: the newest dated update entry (this is where the last session's work lives), plus current phase and what's marked done vs pending (skim; don't read 1,000 lines for a status).
3. **Git** (skip silently if not a repo):
   - `git log --oneline -15 --date=relative --pretty="%h %ad %s"`: what actually shipped recently and when.
   - `git status -s`: uncommitted work left behind.
   - Current branch; whether it's ahead/behind origin (`git status -sb`).
4. **Liveness signals:** deploy model from CLAUDE.md (auto-deploy? parked? local-only), dev port from the Stack/Commands section, and whether a dev server is already running on it (`lsof -i :<port>`: report, don't kill).

## Step 2: Cross-check for staleness

Compare the docs against git reality:

- Last commit date vs the newest dated update entry in PROJECT_PLAN.md. If commits are **newer than the docs**, flag it: "docs look stale: last updated X, but Y commits since; consider /wrapup next time."
- Uncommitted changes from a previous session → list them and ask nothing; just surface.
- Anything in CLAUDE.md's Next Steps or the plan's open tasks that git history shows already done → note the mismatch.

## Step 3: Report

A compact briefing, in this order:

1. **What this is**: two or three sentences max, from the docs (not re-derived from code).
2. **Where we left off**: the last session's work (docs + recent commits), plus anything uncommitted or parked (un-pushed commits, parked deploys, pending migrations).
3. **What's next**: the documented next steps, minus anything already done, with the top 1 to 2 highlighted.
4. **Flags**: stale docs, uncommitted work, dev server already running, port conflicts, anything that would trip up the session.

Keep the whole briefing under ~250 words. No headers-for-the-sake-of-headers if the project is simple: a few tight paragraphs beat a form. End by asking nothing; the user decides what to do with it.

## Guidelines

- **Docs are the source of intent, git is the source of truth for what happened.** When they disagree, say so rather than guessing which is right.
- Do not start work, fix anything, or update docs from this skill: it orients only. If docs are stale, recommend running /wrapup at the end of the session rather than fixing them now.
- If the project has no CLAUDE.md at all, say so and offer to create one as a separate follow-up task.
