wherearewelisted

# Where Are We — Inbound Context Recovery Find and present the current state of a project. This is the "fill me in" skill -- you're arriving at a project and need to understand what's happening. **This is the reader. `/whereweare` is the writer.** - `/wherearewe` — "What's going on?" (find and present existing context) - `/whereweare` — "Let's capture this." (write a snapshot for the future) ## When to Use - **Returning to a project** after time away - **Starting a new session** and want the quick picture - **Checking in** on a project you haven't touched recently - **Before making decisions** -- get grounded in current state first ## Inputs - `$ARGUMENTS`: Optional focus area or question (e.g., "what's the CI status?", "what issues are open?", "what was the last thing we worked on?") - If no arguments, do a general project state scan ## Process ### Step 1: Find Existing WhereWeAre Docs ```bash # Check for WhereWeAre snapshots in this project (most recent first) ls -t private/claude/*whereweare* 2>/dev/null | head -5 # Also check other active projects for cross-project awareness. # CLAUDE_CODE_ROOTS: space-separated list of your project root dirs. # Defaults to ~/code and /c/code, so it works unconfigured on a POSIX box # and on Windows where projects live under C:\code. Set it in your shell # profile or settings env to scan somewhere else instead. for root in ${CLAUDE_CODE_ROOTS:-"$HOME/code" /c/code}; do for dir in "$root"/*/private/claude "$root"/*/*/private/clau