vr-statuslisted

# /vr-status — Project Status Report Give the user a fast, honest snapshot of the project. No fluff. ## Steps 1. Read `.claude/PROJECT_NOTES.md` — the phase tracker and "What to do next" section are the source of truth. 2. Cross-check reality vs the notes: - Does `unity/` contain a Unity project yet? (Look for `unity/Assets/` and `unity/ProjectSettings/`.) - Do `models/source/` or `models/exports/` contain any captures? - Does `docs/CAPTURE_LOG.md` have real entries (not just the template)? - Any uncommitted git changes worth mentioning? 3. If the notes and reality disagree, say so explicitly — stale notes are worse than no notes. ## Output format ``` ## Phase: <N — name> (<status>) **Done recently:** <1-3 bullets> **In flight:** <what's actually being worked on> **Blocked on:** <anything waiting — hardware, decisions, API keys — or "nothing"> ## Next action (do this literally next) <one concrete step, e.g. "Install Unity Hub from unity.com/download"> ``` ## Rules - One next action, not five. The plan already lists everything; this skill picks the *next* thing. - Respect phase discipline: never suggest a Phase N+1 task while Phase N lacks its deliverable. - If an open question from PROJECT_NOTES.md is now blocking (e.g. "which location?" blocks Phase 1 capture), surface it as the next action.