blindspot

# Blindspot The user is about to work in territory they don't know. They may not know what questions to ask, what good looks like, what prior art exists, or which potholes are waiting. Survey the territory for them, then hand back a map they can prompt with. This is not a tutorial (teach the minimum needed to prompt well) and not a plan (that comes after, from the sharpened prompt). ## Workflow ### 1. Calibrate If the invocation doesn't already say, ask one `AskUserQuestion` round covering: what they're trying to do, and their familiarity with the involved domain, tool, or codebase area. Skip this step entirely when their prompt already answers both. Never stretch calibration into a full interview (that's the grilling skill's job). ### 2. Survey the territory Ground everything in current sources, not training data: - **Repo prior art**: search the codebase for existing patterns, conventions, and adjacent solutions. Use an Explore agent for broad sweeps. - **Tools and libraries**: invoke `find-docs` for current APIs and config. Add a `WebSearch` for pitfalls ("X gotchas", "X common mistakes"): pitfalls live in issue threads and post-mortems, not getting-started docs. For terrain dominated by one tool's setup choices, delegate the sweep to the `best-practices` skill instead. It covers both halves with parallel subagents. - **Non-code domains** (design, audio, infra concepts): `WebSearch` for how practitioners judge quality in this domain. ### 3. Terrain briefing Repor...