blindspotlisted

## Pre-computed context Current branch: !`git branch --show-current 2>/dev/null || echo "unknown"` Project root: !`git rev-parse --show-toplevel 2>/dev/null || echo "unknown"` These values orient this session only; resolve files against the project root while working. ## Purpose Every mode of `/discovery:explore` builds the AGENT's local knowledge and hands off an `EXPLORE.md` artifact. Blindspot mode builds the USER's knowledge and hands off a better prompt — a different audience and a different deliverable, which is why it is its own skill. Run it when the user is about to work in territory they don't know — an unfamiliar codebase area OR an unfamiliar domain vocabulary — and the goal is to surface what their framing didn't account for so they can write a sharper implementation prompt. The output is calibrated to the user's disclosed starting point, not to a fixed depth. Local counterpart discipline to `/discovery:explore` (what IS in the codebase) and `/discovery:research` (what SHOULD BE from external sources): blindspot borrows from both lanes but serves the user's understanding rather than the agent's. ## Workflow 1. **Intake** — ask the user's starting point first (one question). Blindspot output calibrates to that disclosure — what they already know bounds which gaps are worth surfacing. 2. **Scan** — two lanes, chosen by what is unfamiliar: - **Codebase lane** — read the target area (the codebase-reading, git-history, and project-structure dimensio