IDMYPOS — Show Position 🧭
Doom: IDMYPOS = it prints your coordinates on the map. Here: a fast status report of where you stand — so during a long task or after a break you can reconnect in seconds.
This is a CHEAP mode: it doesn't work, doesn't modify, it just shows the state. Don't overdo it — a few scannable lines is the goal, not a report.
Teeth: run the script for the "where"
Don't guess the location/git state — the skill bundles a deterministic read-only script that pulls real data (branch, uncommitted file count, last commit, upstream distance, or for a non-git folder the most recently modified files). Run it from this skill's base directory:
& "<skill-dir>\scripts\position.ps1"
The script gives the "Where" line factually; you fill the Task/Done/Next/Block
lines from session context and relevant memory. (Non-Windows: git status -sb +
git log -1 --oneline by hand.)
What to gather
Only what's needed to orient:
- Where: working dir; if a git repo, current branch + whether there are uncommitted changes (briefly). If not a repo, just the directory.
- Task: the current task / mission this session.
- Done: what's been done so far — the important steps, not every detail.
- Next: the next step(s), open questions, blockers.
- Context: if relevant, the project's current status from memory (but only if it actually belongs here).
Readout — POSITION
═══ POSITION ═══
📂 Where: <dir · branch / state, if any>
🎯 Task: <what we're working on now>
✅ Done: <the main steps completed>
⏭️ Next: <next step / open question>
🚧 Block: <any obstacle; else "—">
════════════════
After the readout, stop — this is orientation, not action. The user decides where
next (and can call another cheat, e.g. /idclev to warp or /idclip if we're stuck).