sitreplisted

# Situational report Answer one question: **where does this project actually stand right now?** The value is in the gap between what the project's own documents claim and what the repository shows. Report the gap; never launder a stale document into a current fact. ## 0. Defer to the repository first `Glob` for `.codex/prompts/*sitrep*.md`, `.codex/prompts/*status*.md`, and the same patterns under `.claude/commands/` — they catch variants such as `project-sitrep.md`. If one matches, `Read` it, follow its instructions instead of the steps below, and say which file you used. If several match, pick the closest name and say which. Otherwise continue here. ## 1. Learn the project's conventions Read `AGENTS.md` and `CLAUDE.md` if present; they usually state the handoff or logging convention. Fall back to `README.md` for orientation. Then find the project's own memory: `HANDOFF.md`, `CODEX_HANDOFF.md`, `STATUS.md`, `SESSION_LOG.md`, `NOTES.md`, or a `logs/` directory with dated entries. Use what the project has. If it keeps none, say so plainly — do not invent a format it does not use. ## 2. Check live state ``` git status --short git log --oneline -n 8 git branch --show-current git status -sb | head -1 ``` Two failure modes are worth the extra commands. **A detached or behind branch:** if `git status -sb` shows divergence from the upstream, run `git fetch` and report the true position — a local branch can be many commits behind while the working tree looks clean. **Working