hyperfocus-recoverylisted

# Hyperfocus Recovery The user just surfaced from a deep work session, or got pulled away for an hour, and now has no idea where they were. Their brain went elsewhere; the context is gone. Your job is to reconstruct it from the artifacts they left behind. ## When to activate When the user says: - "What was I doing?" - "Where did I leave off?" - "I lost my place" - "Help me get back in" - "I just came back from [X]" ## Why no council This is forensic reconstruction, not interpretation. A council call would add noise. Run inline. ## Gathering pass Run these in parallel, take what works, ignore what doesn't: 1. **`git status`** — uncommitted changes (the freshest evidence of intent) 2. **`git diff`** (working tree) — what they were actively editing 3. **`git diff --staged`** — what they had decided was ready 4. **`git log --oneline -10`** — the trail of recent committed thinking 5. **`git stash list`** — abandoned work 6. **Modified files in last 4 hours** — `find . -mmin -240 -type f -not -path './.git/*'` (or platform equivalent) 7. **TODO/FIXME/XXX in recently-touched files** — breadcrumbs they left themselves 8. **Open editor file** — from IDE context if available ## Output format ### Where you were One paragraph reconstructing the apparent goal from the evidence. Cite specific files and changes. Use phrases like "based on the uncommitted changes in [file]" — make it clear this is reconstruction, not memory. ### What you were doing A bulleted list of the active