where-i-am

Where I Am

Answer "where am I on this project?" in a short, scannable report instead of a wall of text. Built for switching between long-running projects without losing the thread.

Read-only. This skill writes nothing and consumes nothing — pure orientation.

Output shape

Open with a one-line punchline, then the four sections in order:

**Right now →** <what you're actively doing / waiting on this moment, and your immediate next move>

## ✅ Done — and what it means
- <completed work> → <why it matters / what it unblocks>

## ⏳ In progress
- <work actively moving> — <state / owner: crew fixing, waiting on CI, mid-refactor>

## ▶️ Next
- ⬜ <the next not-yet-started step(s)>

## ⚠️ Watch
- <blockers, fragile state, gotchas, "don't forget", contradictions between sources>

Status markers — use inline when listing the steps of a track: ✅ done · ⏳ in progress · ⬜ not started.

Rules for the report:

• Right now → is the most important line — the fast-orientation cue. Always include it; one line.
• Bullets, not paragraphs. A handful per section, most-relevant first.
• Each Done bullet pairs what happened with why it matters (→). A commit without significance is noise.
• In progress vs Next: ⏳ is work already moving (a crew is on it, a branch is open, you're mid-edit); ⬜ Next is not yet started. Don't conflate them — the whole point is knowing what's live vs queued.
• Multi-track projects (e.g. a feature track + a bugfix track running in parallel): group bullets under bold track labels (**Reorg track:**, **Bug-fix track:**) inside the sections.
• If a section is genuinely empty, write - — nothing rather than padding.
• Synthesize, don't dump. Never paste raw git log / observation lists — distill them.

Source priority (current → durable)

Lead with the live session; use durable sources to fill gaps and cross-check.

1. Current session context — primary. What this conversation has done, decided, and left open. Freshest signal, especially mid-task.
2. claude-mem recent observations — the narrative across prior sessions (use the mem-search skill, or the recent-context already injected at session start).
3. Handoff + latest daily-log — explicit nextSteps / blockedItems / decisions and Tomorrow / Blocked.
4. git — ground truth of where the code actually sits.